How to optimize space in Anaplan by unifying versions without affecting the production model?

Hello everybody!
We are working on optimizing a model in Anaplan with the goal of freeing up more space. For this, we are evaluating the possibility of eliminating some versions that are not in use and unifying them into more functional versions. Currently, the model includes many versions, such as FPC 2022 - I and FPC 2022 - II, among others, because each year has multiple versions. We now seek to reduce this to only four versions, linking them to the corresponding years.
However, we are concerned that these changes may affect the production environment, as it contains critical information. Therefore, we are looking for recommendations on how to execute this optimization efficiently and safely, minimizing the risk to the production model.
Also, if anyone has implemented a similar solution or knows of other ways to free up space without deleting versions, we would be very grateful for your help.

This is an example of all the versions we have:

And we want to achieve something like that: that there are only 3 or 4 versions that relate to each year

Best Answer

  • kristy236lewis
    edited October 25 Answer ✓

    Optimizing an Anaplan model while ensuring the integrity of your production environment is crucial. Here are some recommendations to approach this process safely and efficiently: StarbucksSecretMenu

    1. Assessment and Documentation

    • Inventory Versions: Create a detailed inventory of all current versions, noting which are in use and which can be considered for deletion.
    • Impact Analysis: Assess how the removal of certain versions might impact reports, dashboards, and any dependent calculations. Document these dependencies.

    2. Stakeholder Consultation

    • Engage Users: Consult with users and stakeholders to confirm which versions are critical and which can be unified or removed. Gathering feedback helps in making informed decisions.

    3. Sandbox Environment

    • Use a Sandbox: Clone the production model into a sandbox environment. Perform your version consolidation and optimizations here first to see how changes affect the model without impacting production.
    • Testing: Validate that all necessary functionalities, reports, and dashboards work as intended after the changes.

    4. Version Consolidation Strategy

    • Merge Similar Versions: Identify versions that can be consolidated. Create a plan for how to merge data, ensuring that you retain essential historical data in the new versions.
    • Data Migration: Use Anaplan’s data import/export features to migrate relevant data from old versions to the new consolidated versions.

    5. Rollback Plan

    • Backup: Ensure you have backups of all critical data before making changes in the production model.
    • Rollback Strategy: Develop a plan to revert changes quickly if unforeseen issues arise after implementing the new version structure.

    6. Incremental Changes

    • Phased Approach: Consider implementing changes in phases. Start with non-critical versions or a smaller subset to monitor the impact before proceeding with more significant changes.

    7. Monitor and Review

    • Post-Implementation Review: After implementing changes, monitor the model’s performance and user feedback closely. Be ready to make adjustments if necessary.

    8. Alternative Solutions for Space Optimization

    • Archiving: Instead of deleting versions, consider archiving them if they may be needed in the future. This could involve transferring them to a separate model or creating a historical archive.
    • Module Optimization: Review existing modules for redundant calculations or data points that can be simplified or removed.

    9. Documentation and Training

    • User Documentation: Update documentation to reflect the new version structure and inform users of any changes in access or usage.
    • Training Sessions: Conduct training or information sessions to familiarize users with the new versions and any altered processes.

Answers

  • Ideally, you should have used Fake Versions, if you will be creating these many versions. But I can see multiple years as well. See if that can be reduced as well. Use Time Ranges. Review it Module by Module, checking which modules we can reduce the years, We can't create Versions Subset so if we delete the versions, it will be deleted from all modules. Seek out more options to reduce the size of the model, like

    • Check line item without reference, if not used anywhere, delete them.
    • Turn off Summary if not used.
    • Delete users who left the organization.

  • I greatly appreciate the time you took to share your recommendations and suggestions.

    After reading your responses, a few additional questions came to mind. In particular, I would like to know if there are specific ways to identify which line items are not being used at all. Are there any clues or key elements within Anaplan that can help me easily identify which modules, actions or lines items are not in use? This would allow me to streamline the cleanup and optimization process.

    Again, thank you for your help and I look forward to any further guidance.

  • Hi all,

    I have seen this talk useful for a similar case. The model I have has many versions that were made wrong at the time. Each of them has the year included in the version, identical to what Lruiz shows. I would like to have only three versions already, but I do not know how to do this process without losing information because in all reports, I have those versions.

  • Hi, the current versions are still somewhat incomplete. I agree with @scruz, I also want only 3 versions.

    For any questions, please contact email: eggy carfishingtested@gmail.com