Implementation
During the implementation, we guide you step by step through setting up and starting to use vPlan. Together, we make sure the software fits your processes and day-to-day work.
Usually 6 to 12 weeks
7 fixed phases
Evaluation after go-live
A vPlan implementation usually takes 6 to 12 weeks, from preparation to go-live. The exact lead time differs per organisation. A relatively simple setup can be completed faster than an extensive project with multiple departments, specific processes or integrations.
During preparation, we draw up a project plan together. In it, we record the key sessions, phases and decision points.
We deliberately leave enough time between sessions, so you can get to work with vPlan yourselves, test the setup and make any improvements.
Our aim is not to go live as quickly as possible, but to make sure vPlan fits your daily practice and everyone is ready to work with it.
After go-live, we schedule an evaluation to look back on the implementation together and discuss any follow-up actions.
The complexity of your processes and desired setup.
Whether there is an integration with other systems.
The number of employees and departments that will work with vPlan.
The time available for preparation, testing and following up on actions.
The 7 phases
To keep the implementation clear, we work with seven fixed phases. For each phase, we decide together what needs to happen and when we are ready for the next step.
A good implementation starts with good preparation.
We start with a kick-off in which we get to know those involved and discuss the approach, planning and expectations. Then, during the inventory, we map out your processes, wishes and objectives.
How is planning done now? What problems do you run into? And what do you want to achieve with vPlan?
Based on this, we decide together how we will use vPlan and which steps are needed to achieve the objectives.
The result: The objectives, scope and starting points have been set, and we know what we are working towards.
Do you use another system alongside vPlan, such as an ERP or accounting package? Then an integration can make sure information is exchanged automatically and double work is avoided.
In this phase, we agree with the integration partner which data needs to be exchanged between the systems. Think of projects, employees, activities or hour budgets.
The integration partner builds the connection based on the agreements made. Once the basic integration has been delivered, we check whether the information arrives correctly in vPlan.
No integration needed? Then we skip this phase.
The result: The basic integration has been delivered and the required data is exchanged as agreed.
Time to actually set up vPlan!
During the basic setup, we translate the processes we discussed into a first setup of vPlan. Together with our consultant, we set up the most important parts and show how you can work with them.
After this session, you get to work yourselves. By testing with recognisable real-life situations, you find out whether the setup fits your daily work.
The first setup does not have to be perfect yet. It is precisely by working with it that we discover what may still need adjusting.
The result: The basic setup is in place and fits the desired way of working.
Now that the basics are in place, we continue to improve vPlan.
During the optimisation sessions, we discuss your experiences and test findings. What works well? What problems do you run into? And what could be smarter or simpler?
Based on this, we optimise the setup. If there is an integration, we can also discuss any improvements to the data exchange and have them made.
Between sessions, it is important to keep actively working with vPlan and testing it. That way we can solve bottlenecks in time and keep taking the next step.
The result: The setup and any integration have been tested and optimised, so you are ready for the next step.
Before you officially switch to vPlan, we want to be sure the new way of working works well.
During shadow running, you use vPlan alongside your existing planning. That way you can go through the most important processes in practice, without being fully dependent on the new setup straight away.
This is also the moment to prepare future users properly. Do employees know how to use vPlan? Have the most important processes been tested? And have any final points of attention been resolved?
Together, we assess whether everything is ready for go-live.
The result: The setup is final, the most important processes have been tested and the users are ready to work with vPlan.
The time has come: you officially go live with vPlan!
From this moment on, vPlan becomes the leading system for planning and you let go of the old way of planning.
Before go-live, we check together whether everything is ready. We discuss any final points of attention and make sure it is clear who is responsible for what.
In the first period after go-live, questions may of course still come up. We are happy to help you with them.
The result: vPlan has officially been put into use and forms the basis for your daily planning.
We stay involved after go-live too.
About five to six weeks after go-live, we schedule an evaluation. We look back on the implementation together and discuss how working with vPlan is going.
Have the original objectives been achieved? What is going well? And are there still points for improvement or additional wishes?
If there is a need for further optimisation, we discuss which next steps are appropriate.
The result: The implementation has been evaluated, the objectives have been discussed and any follow-up actions have been agreed.
Tips
A successful implementation is a joint effort. We guide you through setting up and using vPlan, but your own involvement is at least as important. With these five tips, together we make sure the project runs smoothly.
Tip 1
Make sure the right employees are involved from the start. Appoint an internal project lead and make clear who makes decisions, who tests the setup and who follows up on actions.
That way we keep up the pace and can act quickly when needed.
Tip 2
The implementation consists of more than just the sessions with our consultant.
Between sessions in particular, it is important to work with vPlan, test the setup and collect any questions or findings.
Our advice is to set aside about an hour a day for vPlan during the active implementation phases.
Tip 3
Use examples from your daily work to check that everything works well.
Think of planning a project, moving work or dividing capacity.
That way you find out in time whether the setup fits your practice, and we can include any improvements in the optimisation sessions.
Tip 4
A new way of planning often also means a change for employees.
So explain in good time why you are going to work with vPlan, what will change and what this means for them.
By preparing employees well and actively involving them, the switch to vPlan becomes a lot easier.
Tip 5
Agree in advance when you will officially switch to vPlan.
It is important that everyone knows from which moment vPlan is leading and the old way of planning is let go.
That way you prevent different plannings from continuing to exist side by side, and one clear way of working emerges.
Tip 6
Want to discover more about vPlan yourself during the implementation? There are several ways to expand your knowledge and become familiar with the features.
By actively building knowledge yourself, you can ask more targeted questions during the implementation sessions and get started with vPlan independently sooner.
During the implementation, we work with a joint project plan and an implementation planning in vPlan. That way you know exactly which phases we go through, which actions are open and when we are ready for the next step.
Our project manager monitors the progress and planning of the project.
Our consultant guides you through the setup of vPlan and how to use it.
Together, we make sure you not only go live successfully, but also get the most out of vPlan in the long term.
We are happy to help you further.