Phase B, Business ArchitectureDerived from TOGAF

Business Interaction Matrix

Record which organisation unit provides which business service to which other unit, so every internal handoff is written down once and owned.

All tools

Business interaction matrix: which unit provides which service to whom

Five organisation units appear as both rows and columns. A filled cell names the business service the row unit provides to the column unit, so every handoff inside the distribution business is written down once and owned.

Business interaction matrix: which unit provides which service to whom A Business Interaction Matrix, the TOGAF Standard 10 Phase B artifact, worked for London Grid Distribution, a GB electricity distributor. Five organisation units run down the side as providers and across the top as consumers. Each filled cell names the business service the row unit provides to the column unit, such as Network Operations giving planned outage windows to Connections. The diagonal stays blank and the emphasised Connections row shows a new connection touching every unit. Provider unit Connections Network Operations Asset Management Data and Digital Finance and Regulation ConnectionsEnergisationrequestsNew assethandoverConnectionrecordsConnectioncharge data NetworkOperationsPlanned outagewindowsFault and defectreportsNetwork telemetryfeedInterruptionstatistics AssetManagementCapacityassessmentsAsset ratingsand limitsAsset registerextractsInvestmentplans Data andDigitalOnline applicationportalControl systemsupportAsset analyticsserviceRegulatorydata packs Finance andRegulationChargingmethodologyOperatingbudgetsInvestmentapprovalsLicence reportingrequirements Row unit provides the named service to the column unit. Diagonal blank. Source: TOGAF Standard 10, Phase B artifacts

Read the Connections row beside the Connections column and the point appears: one new connection draws services from all four other units. An interaction that sits in no cell is an undocumented dependency, and undocumented dependencies are where handoffs fail.

In Phase B, when handoffs between units are undocumented or disputed and dependencies need to be made explicit.

What you need and what you get

You'll need

  • The organisation unit catalogue
  • The business services that cross unit boundaries

You'll get

  • A provider by consumer service grid
  • The undocumented interactions worth chasing

Taught in

No course modules linked yet.

Derived from

  • The Open GroupTOGAF Standard 10, Architecture Content: Business Interaction MatrixSource

TOGAF is a registered trademark of The Open Group in the United States and other countries. This tool is independently produced, TOGAF-aligned, and is not affiliated with, endorsed by, or certified by The Open Group.