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 the standard templates from Cravit, which include the standard Odoo functionality. This allows for a quick and clear picture of the requirements, wishes, and the fit-gap at a detailed level.

OTAP (Development, Testing, Acceptance, and Production environment)

For the implementation process, an OTAP street will be set up. For setting up the OTAP street, Cravit follows the guidelines as shown below. This will be constructed as depicted next to it.

In the OTAP street, the development line runs from left to right and the data line from right to left. This is of course with version control based on release dates.

Github

For 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 directly involved parties. This environment is also used for support.

Odoo can be installed on a private server or hosted. At the start of the project, an installation of Odoo will be realized.

Hosted

Odoo can preferably be hosted. This can be done either with a private provider or with Odoo at https://odoo.sh/ and also by an environment managed by Cravit. The installation can, if desired, be executed and managed by Cravit at DeltaBlue, high availability Cloud Solutions. This is a platform specifically set up 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 in your own country. During the installation, an automatic backup procedure will be set up that makes a backup daily to another external data center.

On private server

Odoo can also be installed entirely on its own server if desired.

Cravit distinguishes the following types of maintenance:

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

Thanks to a service level agreement (SLA), the customer has a guarantee of availability and involvement from Cravit for follow-up on any requested improvements and expansions and ensuring the continuity of the Odoo production environment.

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

Through a platform accessible to certain individuals, issues can be reported. These issues can be reported based on priority. Of course, direct phone contact can also be made.

In the process, one or a few administrators will gain access to this system.

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

• Immediately: Issues that must be resolved immediately because work has stopped. Cravit responds immediately and starts working right away.
• Urgent: Issues that need to be resolved quickly because work is being disrupted. Cravit responds within 1 day and starts work within 2 days.
• High: Issues that need to be resolved quickly but do not disrupt the work. Cravit responds within 1 day and starts within 4 days with the work.
• Normal: Issues that need to be resolved but do not have immediate consequences for the work. Cravit responds within 1 week and starts within 2 weeks with the work.
• Low: Issues that need to be resolved if there are no urgent issues. Cravit will carry out the work once 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 carry out the work once the other issues are resolved.