Have a question about this requirement?

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Requirement

Test environment where changes can be trialed before committing to production

Functional Area

Administration

Industries
All
DETAILS

Description

A test environment, also known as a sandbox, is an isolated space where changes, updates, or new features can be tested to assess their impact on the existing system and data before committing them to the live or the production environment. This allows for error detection and prevention, avoiding potential disruptions or losses in the corporate performance management process.

Example Use Case

Scenario: A multinational banking corporation plans to integrate a new financial model into their CPM software. The model, however, is complex and may have far-reaching implications on the existing data and reporting.

Solution: The corporation uses a test environment to trial the new model. It allows them to assess how the model impacts existing performance metrics, reporting layout, and data visualization before deciding to incorporate it into the live environment. Any potential issues or incompatibilities are addressed in the test environment, ensuring seamless integration in the production environment.

Considerations

A sandbox environment is a must when purchasing a CPM solution, especially in the first year. The model will evolve a bit as the users learn the power and limitations of the tool and as such changes will be made that will impact the production environment. It is bad practice to experiment with additions or major changes to a model in the production, otherwise known as primary instance of the application.

Questions to Ask a Vendor

  • Availability: Does your CPM software offer a dedicated test or sandbox environment for trialing changes?
  • Access Control: Who can access the test environment? Can access be restricted to select users?