ChatDiagram
enterprise architecture · business architecture · capability mapping

Enterprise Business Capability Map

This enterprise business capability map connects external customers and partners to sales, customer-service and finance capabilities. CRM supports sales and service, while ERP supports finance. Both applications use master data as a shared information point. It is a useful early enterprise architecture view because it connects business responsibilities to application support without becoming an organizational chart or a detailed process model.

Type Schéma fonctionnelNorme Ogata / standard controls textbook conventionMoteur schematex-blockdiagramMis à jour 24/09/2026
Enterprise Business Capability Map
Drawing preview
La demande

“Create an enterprise business capability map with customers and partners, sales, customer service and finance capabilities, CRM and ERP applications, and master data.”

Essayez ensuiteAdd a marketing capability connected to the CRM application.Add a supplier management capability connected to ERP.
Ce que contient ce dessin

Comprenez les décisions qui le sous-tendent.

01Customer scope

Start with customers and partners as external actors.

02Capability view

Separate sales, service and finance work.

03Application support

Map CRM and ERP to those capabilities.

04Shared information

Join application records through master data.

Use it for a concise business-to-application enterprise architecture view.

Voir tous les modèles de schéma fonctionnel →

FAQ

Questions fréquentes

What is a business capability map?

It organizes what an enterprise needs to be able to do, independent of its current teams or systems.

Why map capabilities to applications?

The mapping shows which systems support important business abilities and where dependencies exist.

What is master data in this view?

It is shared core information, such as customers or products, used consistently across applications.