OEG Best Practice: Model cut-over checklist

AnaplanOEG
AnaplanOEG
edited August 19 in Best Practices

Introduction

There are many ways to go about building a new model or rebuilding an existing model. The most important piece is the proper transition and cut-over. This checklist is a starting point to help you begin gathering all impacts building or rebuilding a model will have on the Connected Planning Ecosystem within your organization. You can modify this checklist to match the specific nuances and needs of your ecosystem and ways of working.

Transition guide and check list

Getting started

  • Identify and notify all relevant stakeholders of the planned new model build to ensure:

    • All related content, documentation, etc. can be updated appropriately
    • All stakeholders are aware to help identify areas of risk across the business such as the timing of critical business activities such as accounting close, bonus cycle, etc.
  • Select the proper workspace for the new model to live in

NOTE: If you end up having to move the model to a new workspace, you’ll also need to take into consideration the impacts of copying or importing a model.

  • Identify all models that are connected to the model through Imports/Exports and identify the model owners of the plan to transition to a new model
  • Post in any communication channels you may have to make sure no stakeholders or areas of risk have been missed

During the Build

  • The model follows best practices outlined in the Anaplan Planual

  •  All requirements have been gathered through:

    • End-user Interviews
    • Posting and getting feedback through the communication channels available to you
    • Talking with the downstream model owners regularly to understand their needs throughout the build (Anaplan Way)

Before Cutover

  • All testing has been completed including calculations, functionality, imports, model performance, and downstream impacts

NOTE: If downstream models cannot adjust to the new model during the allocated time, an approach to allow for more flexibility on timing is to feed data from the new model into the old model. This allows the team to use the functionality in the new model while providing more time for downstream models to transition. This can reduce the risk to critical downstream models/processes.

  • All integrations have been reviewed and signed off
  • The go-live plan has been communicated to all stakeholders and impacted model owners
  • Functional Lead/Model Owner has signed off on using the new model

After cut-over

  • The model performance continues to be monitored and all updates should be implemented
  • Downstream models have updated their imports from the new model and are working as expected
  • The old model has been archived

Author Abby Pederson.

Tagged:

Categories