A rollout project can be part of either implementation or enhancement or the consequence of activities such as an acquisition or growth into new markets. The rollout may be covering multiple countries, regions or businesses or be a combination of these.
Typically the configuration associated with rollouts can be characterised into one of three types:
For many rollouts there may be more than one “master” entity, each reflecting a different aspect of the business, and for each master entity there may be multiple other entities that should be configured in a consistent way to its master, save for any unique requirements.
While many of the core challenges for rollouts are common with implementation or enhancement additional challenges include:
These challenges can be further accentuated when there are different project teams responsible for different entities.
Managing the roll out of new entities can be significantly streamlined using ConfigSnapshot compared to traditional methods.
The current setup of both the master entity and common configurations can be flexibly reported and reviewed to enable project teams to assess which areas will be affected by the new entity. For entity level data they can determine what should mirror the master entity and what should be specific to the new entity.
ConfigSnapshot planning can be used to prepare setup for the new entity as well as any necessary changes or additions to common configuration; most data can be loaded directly to the plan from an existing environment. Entity level data for the master entity can be loaded to the plan, filtered where applicable. Once loaded this can be quickly copied to the new entity within the plan. Entity specific values can be prepared by using transformation or by integrating with Excel to make any necessary changes. Once complete, comparison between the new and master entities within the plan helps ensure all necessary setup for the new entity has been completed.
ConfigSnapshot migration allows most data to be automatically loaded from the plan to each target environment; including the creation of the new entity itself. This can dramatically reduce the time to deploy setup as well as increasing its accuracy. Comparison between the environment and the plan confirms data has migrated successfully.
Baselines can be used to track the project over time enabling teams to keep tight control over the full lifecycle by being able to identify change during any specific phase and ensuring all planned changes have been applied and any unexpected difference has been identified and addressed.
You can try a trial version of ConfigSnapshot absolutely FREE
Register now to receive your access code or get in touch by phone or email:
"We used ConfigSnapshot as part of the integration of two R12 instances as part of a merger and it proved to be a valuable tool throughout the project. The ability to quickly document and compare between multiples instances was central to ensuring the project progressed on schedule through to Go-Live - despite the substantial levels of new configuration required. On completion of the project, we were also able to very quickly produce the required documentation for auditors of all configuration changes made - saving significant amounts of time. We would definitely recommend the product."
Finance Project Manager, International Sports Betting and Gaming Operator