Based on a Project Initiation Document and the Business Process, a Functional Design is determined for each functional work area. This is done based on Cravit's standard templates in which the standard Odoo functionality is included. This allows a clear picture of the requirements, wishes and the fit-gap to be quickly determined at a detailed level.

DTAP (Development, Test, Acceptance and Production Environment)

An DTAP street will be set up for the implementation process. For the setup of the DTAP street, Cravit uses the guidelines as shown below. It will be constructed as shown here. 

In the DTAP street the development line runs from left to right and the data line from right to left. This of course with versioning based on release dates.

Github

For the source code and module development Cravit uses Github. The source codes of all developments are also fully available to the client.

Odoo project issue management

For the registration and management of bugs, issues, features, actions and planning, Cravit uses the Odoo Projects module. This environment is accessible to all those directly involved. This environment is also used for support.

Odoo can either be installed on your own server or hosted. An installation of Odoo will be realized at the start of the project.

Hosted

Odoo can preferably be hosted. This can be either with your own provider or with Odoo at Odoo.sh and also by an environment managed by Cravit. The installation can be done if desired and managed by Cravit at DeltaBlue, high availability Cloud Solutions. This is a platform specifically designed for Odoo and is very flexible and scalable. DeltaBlue can maintain your Odoo environment on many server providers around the world (AWS, Digital Ocean, Google and many others). We recommend for legal reasons to always store your data domestically. At installation, an automatic backup procedure is set up that makes a daily backup to another external data center.

On an own server

Odoo can also be installed on your own server if you wish.

Cravit distinguishes the following maintenance types:

• Corrective maintenance and questions after Go Live
• Extensions and/or additions
• Updates or upgrades

Thanks to a service level agreement (SLA), the customer has a guarantee of availability and commitment from Cravit to follow up on any requested improvements and enhancements and ensure the continuity of the Odoo production environment.

For the registration and management of bugs, issues, features, actions and scheduling, Cravit uses Odoo.

Through a platform, accessible to certain people, issues can be reported. These issues can be reported based on a priority. Of course, direct telephone contact is also possible.

In the process, one or a number of administrators will be given access to this system.

Within the SLA, Cravit has the following classification of urgency:

• Immediately: Issues that need to be resolved immediately because work has stopped. Cravit responds immediately and starts work right away.
• Urgent: Issues that need to be resolved quickly because work is disrupted. Cravit responds within a 1 day and starts work within 2 days.
• High: Issues that need to be resolved quickly but are not disruptive to work. Cravit responds within 1 day and starts work within 4 days.
• Normal: Issues that need to be resolved but do not directly affect work. Cravit responds within 1 week and starts work within 2 weeks.
• Low: Issues that need to be resolved when there are no urgent issues. Cravit will perform the work when the higher priority issues are resolved.
• Nice to have: Issues that do not need to be resolved but can be worked on if there are no other issues. Cravit will perform the work if the other issues are resolved.