CSDM best practice for business unit capability models and maturity assessments
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi everyone,
We’re looking for guidance on the recommended CSDM / Enterprise Architecture approach for managing a common business capability model across multiple business units.
Our requirements are to:
- Maintain a canonical enterprise capability model.
- Allow each business unit to map its own Business Applications to those capabilities.
- Allow Business Architects to assess capability maturity by People, Process and Technology and generate business unit heatmaps.
- Enable the CoE to compare maturity for the same capability across business units and create an enterprise view.
For example, Customer Management could be common across the enterprise, but have different applications and maturity scores within Business Units A and B.
What is the recommended CSDM modelling approach? Should we create separate Business Capability records for each business unit, or maintain a single canonical capability and capture the Capability × Business Unit context, application mappings and maturity assessments through another object or relationship?
We’re particularly interested in approaches that are scalable, CSDM-aligned and work well for Enterprise Architecture/APM reporting and heatmaps.
Has anyone implemented a similar federated Business Architecture model?
Thanks!