How is Omnia implemented?
We always recommend that Omnia solutions should be established in projects aligned with our Implementation Process.
The setup and basic configuration of a new Omnia solution is done in a day or two. But establishing a digital workplace that bring value to end-users and the organization demands more work than just installing the product. Therefore, we recommend that partners and customers should plan their projects based on the following implementation model.
In this phase we recommend that our customer should be able to answer at least answer two questions, what are the purposes of the solution and how can we achieve these?
The answers will be of great value for creating a solution overview, for planning the upcoming project, deciding on the organization that will manage and drive the solution and deciding on how success can be measured. On a more operational side, within this phase, we also install Omnia in the environment appointed by the customer.
Analyze & Plan
Within this phase, a series of workshops will be conducted to analyze and prioritize business requirements and decide on how to fulfill these. The result of the workshops will be guiding the configuration of Omnia and the customer's solution. In this phase, we recommend that plans for migration, training, communication, and rollout are created.
Prepare and validate
This phase is focused on setting up a solution that is configured in a way that meets requirements and purposes. The work with realizing the solution is carried out in iterations and feedback on the solution can be gathered along the way by involving end-users in a pilot. The solution is validated and anchored within the customer organization.
Now it is time to execute the plans made previously in the project. This cover migrating and creating content, training for administrators and publishers and communicating regarding the changes to come for the organization. In this phase the governance team will be prepared and activated, starting to plan the work needed after launch.
Within this phase, the rollout plan will be executed. Besides the actual launch of the solution, this often also covers providing introduction and training and handling support for end-users. The project team should also be ready to act on any issues submitted and to adjust features to better support daily work.
Hand-over and close
Now the solution is live and hopefully providing value to end-users. Before it is time to close the implementation project, we need to check that the solution is well documented and that a proper hand-over to the governance team has been made.