Odoo • Tekst en afbeelding

Our Odoo professionals

are ready to help you

Request a free demo



Implementation

Implementing an ERP environment goes beyond merely technology; it means achieving innovation and progress within your organisation. Transitioning your business processes to Odoo will deliver a real contribution to your business development. Not only for a short time but specifically for the long term.

The first step 

Proof of Concept and creating a Project Initiation Document

The primary objective is to work together and come to a sound and well-founded project approach.

We generally start a potential collaboration by doing an assessment (Proof of Concept) and creating a Project Initiation Document (PID). This PID specifies the scope, configuration, schedule, and budgeting. This document will then serve as a decision document for possible implementation.

More than ICT

An ERP implementation also affects organization processes

The implementation of an ERP system is partly ICT and partly business management.

Successful implementation is more likely if business processes are clearly defined. What processes are there, who works with them, what is the function, and what other processes should they integrate with. After all, one of the main reasons for changing to an ERP system is the interaction between different business processes.

Project approach

A pragmatic and firmly grounded approach

Our project approach is based on Agile and Prince2, but then as an instrument and not as means to an end.

Our project organisation is based on two principles: a proven methodology for approaching and carrying out an implementation project and excellent cooperation between all stakeholders. Working together, quality, and passion are key priorities of our approach. Business know-how, empathy, and knowledge of your processes is what characterises the people of B-informed. That's how we make the difference and how we impress.

The implementation

Extensive collaboration to achieve something beautiful

Working together, quality, and passion form key priorities of our approach.

Our implementation methodology is targeted at achieving milestones. Everything is focused on achieving your goals in time, functionality, acceptance, and budget. Together with the entire organisation to achieve the desired result. Ensuring optimal performance together. That's what we aim for.

Your own wishes

Our developers create what you need based on an ROI

Good software blends with the environment. We develop that which really adds value to your organization.

Before developing customer-specific needs, we will work with you to first see what the consequences are, what the alternatives are, and what the benefits are. Preference must always be the default, unless it clearly adds value.

In order to develop customer-specific needs in Odoo, we involve end-users at an early stage. We describe the processes, demands and wishes in a functional design. During development, we're constantly testing this with the users.

Training

We give your people on-the-job training

Through our extensive practical experience, we know how to focus training on what is needed for everyday work.

The type of training will be tailored to your specific needs. Our experience shows that training on the job is the best result. That being the case, we're guiding employees in their day-to-day work or on a specific project. In other cases, it is more efficient to train a group of employees at once, zooming in on the general operation and application of Odoo, tips, and tricks, etc. This is combined with examples and exercises on day-to-day practice.

Go live with Odoo

Good preparation, hands-on guidance, and an intensive aftercare

Always an exciting moment. It will work with good real-time planning, acceptability testing, and the guarantee of hands-on guidance!

We set up a planning and going-live schedule, and if necessary a migration plan. This gives us a good understanding of the steps and risks of the going-live process. After an acceptability test, the going-live is scheduled and run according to the planning.

The first weeks following the going-live are critical. During initial use, matters should always be identified and resolved as soon as possible. Despite testing, every live walk has points that no one has foreseen. Users accept them provided they resolve quickly and visibly.

After live optimization

The more you work with it, the more you discover what Odoo can still improve.

Are the processes running as expected? Where can more process-optimization or functional improvement be achieved?

After the first weeks, it is good to conduct an evaluation. Where are the processes running well and as expected, and where can we optimise them or make them run more smoothly in Odoo? Also, often small improvements can lead to greater user convenience, and which users can enjoy for years to come.

   

Design

Odoo + afbeelding en tekst

   Functional design


Based on a Project Initiation Document and the Company Process, a functional work environment and an Operational Design is defined. This is done based on standard B-informed templates that include the standard Odoo functionality. This will enable a clear understanding of the demands, wishes, and fit-gap to be rapidly identified on a detailed level. The workflow is as depicted here.

Elements in an Operational Design are:

  • Process flow and approval matrix

  • Views

  • Parameters and settings

  • Configuration

  • Functionality to be expanded

  • Menus

  • Dashboards

  • User rights

  • Reports

  • Lay-outs of prints and emails

    Technical design  


DTAP (Develop, Test, Acceptance and Production environment)

A DTAP street will be set up for the implementation process. When setting up the DTAP street, B-informed follows the guidelines as outlined here below. It will be structured as shown here.

In the DTAP street, the development line runs from left to right and the data line runs from right to left. This naturally includes source control based on release data.

Github

B-informed uses Github for the source code and module development. The source codes for all the developments are all available to the client.

Odoo project issue management

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

Odoo • Tekst en afbeelding
Odoo + afbeelding en tekst

   Installation of Odoo


Odoo can be installed either on a private server or on a hosted one. Odoo will be installed at the start of the project.

Hosted

Odoo can be hosted if preferred. This can be done through your provider, by Odoo at Odoo.sh, and also by a B-informed managed environment. If required, the installation can be run and managed by B-informed at DeltaBlu, high availability Cloud Solutions. This is a dedicated platform for Odoo and is highly 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, that you always store your data in your own country. An automatic backup procedure is set up during the installation, and is backed up daily to another remote data center.


For more complex environments, we advise delta.blue 

For a more standard set up, we like to use  odoo.sh


On a private server 

Odoo can be fully installed on a private server if preferred.

   

Maintenance and Support

Maintenance

B-informed distinguishes between the following maintenance types:

  • Corrective maintenance and questions after Go Live

  • Extensions and/or additions

  • Updates or upgrades

A service level agreement (SLA) guarantees the client availability and involvement of B-informed to follow up on any required improvements and extensions and to ensure the continuity of the Odoo production environment.




Odoo dashboard of support tickets on a yodeck screen platform

Support 

B-informed uses Odoo for the registration and management of bugs, issues, features, actions, and planning.

Issues can be reported through a platform that's accessible to certain people only. These issues can be reported on a priority basis. Of course, direct telephone contact can also be made.

During the process, one or a few administrators will be granted access to this system.


Within the SLA B-informed understands the following classification of urgency:

Immediately: Issues that need to be resolved immediately because work has stopped. B-informed responds immediately and starts work immediately.

Urgent: Issues that need to be resolved quickly because the work is disrupted. B-informed responds within 1 day and starts work within 2 days.

High: Issues that need to be resolved quickly but that do not disturb the work. B-informed responds within 1 day and starts work within 4 days.

Normal: Issues that need to be resolved but do not have direct consequences for the work.B-informed responds within 1 week and starts work within 2 weeks.

Low: Issues to be resolved if there are no urgent issues. B-informed will carry out the work when the issues with a higher priority have been resolved.

Nice to have: Issues that should not be resolved but that can be worked on if there are no other issues. B-informed will carry out the work once the other issues have been resolved