Make a Project Initiation Document ("PID")
Primary goal is thinking with you to come to a thorough and solid project approach.
In general we will start a possible collaboration with a stocktaking and the making of a PID. This PID contains the detailed plan of the scope, the configuration, the planning and the budgeting. This document serves as a basis for a possible implementation.
ERP implementation touches organisation processes.
Implementing new ERP is partly ICT but also have a business management aspect.
The chance of having a successful implementation increases when the business processes are thoroughly defined. Which processes are there, who are working on it, what is the function and with what other processes do they need to integrate. One of the most important reasons to start to use an ERP system is the interaction between the various business processes.
A pragmatic approach
Our project approach is based on Agile and Prince2, as a tool not a goal.
Our project organisation is based on two fundamentals: one proven method to approach and execute an implementation project and on a good teamwork from all people involved. Teamwork, quality, and passion form important points of attention of our approach. Business knowledge, empathy, and knowledge of your processes characterize the people of B-informed. That's what makes the difference, that is why we will surprise you.
Excellent teamwork to get to excellent results.
Teamwork, quality and passion form important spear-points of our approach.
Our implementation method is purpose based on realizing milestones. All aimed to meet your goals in time. Functionality, acceptance and budget are key. Together with everyone in the organisation we will make sure we get excellent results. During but also after implementation.Taking care of an optimal functionality, that is what we aim for!
Our developers deliver what is needed, based on a ROI.
Good software is flexible. We develop what really adds value to your organisation.
Before developing customized wishes we will discuss together with you what the consequences are, what alternatives there are and what it will add. Preferences will be the standard unless it adds more value otherwise.
To develop the customized wishes in Odoo We will include all the end users in a an early stage. We describe the processes, demands and wishes in a functional design. During the development we will test this continuously, together with the users.
We'll train your people "on the job"
Our broad experience makes that we can focus in trainings on what is needed is the daily job.
The training set up is customized. Our experience learns us that “training on the job” gives the best results. In that case we will help employees with their daily work or in a specific project. In other case it can be more efficient to train a group employees at the same time, where we specially focus on using Odoo, tips and tricks etc. This combined with practical examples and exercises about daily practice.
Good preparation, hands on guidance and intensive follow-up.
Always exciting. With good planning, accepting, testing and the guarantee of hands on guidance, it will succeed!
We will make a planning, a go-live plan and if necessary a migration plan. We will get a good insight in the steps and risks of the go-live. After an accepting-test we will plan and execute the go-live based on the plans.
The first weeks after going live are critical. During the first use there are always bugs that need fixing. Despite testing, every go-live has unforeseen bugs. Users will accept these, if they are solved quickly.
When you start working with your new ERP system, you will discover what else can be improved.
Does it run as expected or is there optimization required and how can we achieve this?
After a few weeks it is good to evaluate. Where do processes run smoothly and as expected where can we optimize these or run smoother in Odoo. Also in functionality little improvements can lead to better user friendliness.