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 & Check List
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 and is Built Optimally
All requirements have been gathered through:
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 )
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.
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.
... View more
When copying or importing a model to a different workspace within the same tenant, it’s important to understand all the pieces that are impacted by this action. It's commonly thought of as 'moving' a model. However, the reality is that a completely new model is being created with a new model guide.
Understanding the implications outlined below will help you collect the direct impacts that copying/importing your model will have on the Connected Planning ecosystem.
NOTE: This article is for moving a model within a tenant and not across tenants. If you need to move a model from one tenant to another, please reach out to email@example.com
Below are the main considerations when moving a model to a new workspace. There are also considerations for other purposes such as testing or demoing in the other considerations section.
Import Actions between Models: All imports from downstream models that are using your model as a source will need to be remapped. Since copying or importing a model essentially creates a completely new model, the Import Data Source will still be connected to the old model and will need to be remapped to the new copied model.
NUX Apps: Copying or importing a model does not create a copy of any apps or pages linked to the model. Existing pages will need to be remapped to the new copied or imported model through the NUX interface. NOTE: Remap all Apps to the new model BEFORE making any changes in the model. Making name changes to module or line item names that are referenced in the app will make it more difficult to map.
Automatic Data Imports: If you're using any systems like Informatica to automate data pulls, you will need to update the logic to reference the new model, or create new automated loads if both new and old model will continue to exist
History Logs: History Logs will not be copied over to the new copied or imported model.
Copying to Set-Up ALM: If making a copy for testing or sandbox purposes, always use the copy for the Development version and keep the original model for production.
ALM Version Tags: If you're using ALM, the version tags will not be copied over to the new copied or imported model. There is no way to copy these to the new model currently.
... View more
Hi, everyone! Join me on December 9 for Anaplan Live! The event has sessions for new learners and experts alike. In my live session, I'll be discussing the 5 foundational functions in Anaplan. These are the most common functions and understanding them will allow you to start building and planning with Anaplan. My request: I'd like to add a 6th surprise function that you would like to learn more about. Please leave a comment below telling me which function you'd like me to cover in the segment. (If you haven't done so yet, register for the free event now! The live event is created with model builders, end-users, and new learners in mind.) See you there!
... View more
Hi, everyone! Join me on December 9 for Anaplan Live! In my session, I'll be discussing the 5 foundational functions in Anaplan. These are the most common functions and understanding them will allow you to start building and planning with Anaplan. I'd like to add a 6th surprise function that you would like to learn more about. To do that, I'd love it if you could leave a comment below telling me which function you'd like me to cover in the segment. (If you haven't done so yet, register for the free event now! The live event is created with model builders, end-users, and new learners in mind.)
... View more