Metadata in the system (dimensions, tags, definitions) can be managed in the admin interface by a non-IT user

Description

The ability for non-IT users to manage metadata like dimensions, tags and definitions within the admin interface of a CPM software. This requirement entails the ability for business users, such as finance and operational teams, to modify and maintain metadata within the system without needing technical or IT support.

Example Use Case

Scenario: A mid-market manufacturing company uses CPM software to manage performance metrics and data. The operations team, which is not technically savvy, needs to regularly update product dimensions and tags related to different manufacturing lines due to changes in the product mix and production tactics.

Solution: The CPM software offers a user-friendly, straightforward admin interface that allows the operations team to easily update product dimensions and tags, accommodating product mix and production changes quickly, without needing technical intervention. This empowers the team and streamlines the data management process.

Considerations

Certain metadata can be at the heart of a CPM product, defined all the structure, the reporting capabilities, how data is imported and so on. Changing this, such as modifying dimensions, can have catastrophic and unforeseen consequences in certain systems - while being no big deal in others. In short, it certainly sounds nice to have this power but it does expose the user to a certain amount of risk depending on the product.

In some cases the need might not be specific to modifying the underlying metadata. The need might instead be satisfied by creating an alternate hierarchy or aliasing some of the accounts. Make sure your requirement is specific to changing metadata structure before including this in your evaluation.

Questions to Ask a Vendor

• Usability: How user-friendly is the admin interface for metadata management? Can you demonstrate how a non-technical user can update dimensions and tags?
• Consequences: What are the potential downsides if, for example, we add a new dimension to the system? Or we take one away? What if we simply add members to a dimension, like new product groups to our Product dimension?
• Visualization & Reporting: Can users see the effects of changes to metadata on reports or other data visualizations immediately?