One of the most important findings from Miradore’s partnerships with managed service providers has been that they value easy implementation. This is quite natural since they expect to carry out a lot of system deployments, so fast and easily reproducible implementation can bring them even significant competitive advantage.
Miradore has responded to this customer challenge in the area of product development, but also by developing an implementation concept to industrialize the deployment process. Miradore implementation concept is covered in the two main implementation tools:
1. MSP project guide, and
2. Customer rollout template
MSP project guide focuses on the one-off project of setting up the Miradore environment and service capability, whereas Customer rollout template focuses on the repetitive service implementation to the end customers. As customer rollouts are done even dozens of times, especially Customer rollout template can become a highly valuable tool for a managed service provider.
Customer rollout template
The idea of the Customer rollout template is quite simple: It is a guide that steers you through the required implementation steps, at the same time serving you as a checklist to concretize your progress. In the beginning its role will be more a guide’s role, but as the implementation process becomes business as usual, it will function more as a checklist.
As pictures are worth a thousand words, the screenshots below will do the most of the talking. Some clarifying comments are added below each screenshot though.
The cover page of the template shows an overview of the rollout phases as well as the overall status of the rollout. Note that in this example we have finished the first two phases and are just about start the third phase, i.e. the installation.
The initiation phase is all about decisions and setting the frame for the rollout. The idea is to collect here all such topics that possibly need to be discussed with the end customer (depending on the service delivery model). After this phase, no need to bother them anymore!
The preparations phase is – as the name says – all about preparing for the actual rollout. Some basic information needs to be collected, operative decisions made, and last but not least: the delivery capacity needs to be in place. And especially remember to verify the connectivity!
During the installations phase the needed servers and services are set up, Miradore instance installed and configured, and client deployment tested. When the preparations phase has been carried out properly, this is a mere formality.
Client deployments are launched in the implementation phase, followed by configuring the feature-specific settings (depending on what features are in the scope). And now the Miradore environment is up and running!
What is left to do in the closing phase is to ensure that everything has been done, the service handed over to production, and that the end customer doesn’t have anything to complain about. Well, that is highly unlikely anyway, since they probably did not even notice anything, as from their point of view this is just a background process.
Wait! Don’t start the rollout yet, there is one more thing…
Managed service providers have different service delivery models, so this template most likely has to be adjusted a bit to fit the respective service delivery model. But we are glad to help, if that is needed. Happy rollouts!