The ability to break the system into multiple instances in Corporate Performance Management (CPM) software refers to the feature where the software can be divided into separate, independent environments. This allows different departments, teams, or business units to work independently in their own instances.
Scenario: A global retail company wants to manage its financial performance across its many branches worldwide. The complexity and distinct characteristics of each branch make it challenging to use a single instance of CPM software.
Solution: The corporate performance management software can be broken into multiple instances, creating a separate environment for each branch. This allows each branch to track its specific metrics and unique dimensions.
If multiple instances are deployed, the connectivity between them becomes incredibly important. Are they totally separate with nothing connecting them? Or do they share a common “parent” data model?
Best case scenario, the vendor does not have to propose multiple instances. It works best if the entire business can run off of one model. However, in very complex businesses like in the Use Case above, that might not be possible.
Also consider the future - will there be acquisitions? What if that acquisition runs a very different business model? Perhaps your organization is an eCommerce business, and now you are acquiring a manufacturing business, or a services arm. Can the system accommodate that situation, or will you be stuck implementing a new instance that can not connect to your master roll up?