Skip to content
Enterprise Architecture — one company, five architectures, one decision system: ESA, ETA, ECA, EPA and ERRA on one enterprise state, unified as UETA and optimized through GEOP

Enterprise Architecture

One company, five descriptions.

DCT describes a company in five ways: its wiring, its moves, its capital, its performance and its exposure. Then it insists that the five describe one company. The architectures stand on one skeleton and read one state, a register records what passes between them, and the decision problem sits on top of all five.

ESAVol I, Ch 9AS

Enterprise State Architecture (ESA)

What depends on what?

What it is

The Enterprise State Architecture describes the company as wiring rather than as an organization chart (Vol I, Ch 9, Def 9.1). It has three parts. The components are the units that carry a state of their own: divisions, shared functions, treasury, and also the market the company faces and the governance that sets its policy. The arrows say whose results move whose, and each arrow has a type. The constraints are the limits the company must respect, and each one has a scope: the components it binds.

An arrow is a dependency that can be tested; a missing arrow is a claim as well, that one unit ignores another (Thm 9.1). Each component has an interface, the readings it lets the others see, and an arrow is sound only when the reading it carries is on its source's interface (Def 9.2). The book separates four kinds of dependency: dynamic, resource flow (cash, people and materials, which are conserved), informational (signals and policy) and constraint coupling (Def 9.3, Table 9.2).

A constraint whose scope is a single component is local, and its owner can sign it off. A constraint that binds several components couples them, and the constraint graph joins any two components that share one (Def 9.7). Complexity is read from a panel of measures (size, density, cycles, feedback mass, depth), each with what it cannot see, never from one score (Def 9.10, Table 9.5).

Meridian's wiring: drivers, a feeder and one feedback core (seed 26109)
Ch. I.9 Meridian's wiring: drivers, a feeder and one feedback core (seed 26109)

The board questions it answers

  • How soon could a demand shock reach the loan covenant?
  • Can a given shock reach a given unit at all, and what would it take to insulate it?
  • Where are the self-reinforcing loops, and do they match the org chart?
  • Can we trust the two-box summary map the board looks at?
  • Which limits must be reviewed jointly, rather than unit by unit?
  • Can our model answer the question we are putting to it?

What the book proves

  • Thm 9.1 The canonical wiring is minimal and sufficient; a missing arrow is a claim of independence.
  • Thm 9.2 A shock moves no faster than the links it crosses. It travels only along the arrows, so the number of links between two units is a floor on arrival time, never a forecast.
  • Thm 9.2(iii), Prop 9.3 Feedback lives in cores. Outside them the company falls into a one-way order of layers, from the drivers to the core.
  • Thm 9.3 A summary map can be trusted one way only. Rolling units up never hides a real route, but it can invent one that does not exist.
  • Thm 9.4 Cycles defeat bilateral checks. Where the constraint graph has a cycle, every pair can sign off while the joint limit fails; on a tree, bilateral sign-off is safe. Each cycle needs one joint review.
  • Thm 9.5 Completeness is a coverage check: the architecture can answer a question only if the readings that question needs are in it, and every aggregation spends some of that coverage.

Meridian, the book’s worked company

Meridian, the book's worked company, is wired as Vol I, Worked Example 9.1 sets out.

  • Seven components: three divisions (Industrial Systems, Digital, Materials), shared engineering, treasury, the market and governance. Fourteen typed arrows: demand from the market to each division, cash from each division to treasury, funding from treasury to Industrial Systems and Digital (Materials funds itself), capability both ways between engineering and the two divisions it serves, and policy from governance to treasury and to Digital. (Vol I, WE 9.1; Fig 9.1)
  • The feedback core is Industrial Systems, Digital, engineering and treasury, with six directed loops. The market and governance drive it; Materials feeds it. The condensation has depth 2. (Vol I, WE 9.1 Step 2; OA 9.B.Ex.7)
  • A demand shock reaches the three divisions in one quarter and treasury, where the covenant sits, in two; governance is never reached. Five distinct paths run from the market to treasury, and the minimum cut is 3 arrows, for example the three cash arrows. (Vol I, Table 9.7; WE 9.1 Step 3)
  • The complexity panel: 7 components, 14 arrows, density 0.333, cycle measure 8. (Vol I, §9.8; OA 9.B.Ex.7)
  • The constraint graph is a triangle of the three divisions under the strategic-risk ceiling of 75, plus a branch between engineering and Digital for the capability floor of 55: exactly one joint review, then one bilateral check. The review matters: strategic risk peaks at 73.6 around month 11, inside the ±6 measurement error of the ceiling. (Vol I, WE 9.1 Step 4; OA 9.B.Prop.6)
  • The board's reading: the covenant has a one-quarter reaction window along three separate routes, so headroom, not insulation, is the defence. (Vol I, WE 9.1)

Explore it

Meridian's wiring

Seven components and fourteen typed arrows (Vol I, WE 9.1, Fig 9.1), in their causal layers: drivers, feeder and the feedback core, whose four components are outlined. Select a component or an arrow, on the drawing or in the list below it, to read what it is, its role and Meridian's reading.

Driversoutside the loopsFeederfeeds the coreFeedback coreevery member reaches every otherMarketMKTGovernanceGOVMaterialsMAT · divisionEngineeringENG · sharedIndustrialSystemsIND · divisionDigitalDIG · divisionTreasuryTRS

KeyDemandCashFundingCapabilityPolicy

Components

Arrows

How it goes wrong

  • The org chart is taken for the wiring, and a shock arrives by a route nobody drew.
  • Every unit signs off its own share of a limit that binds a loop; each bilateral check passes, and the joint limit is breached (Thm 9.4).
  • A summary map shows a connection that exists only on the map (Thm 9.3). On Meridian's two-box map the centre appears to reach Materials, which no arrow does (Fig 9.2).
  • An arrow is drawn with no reading behind it, or a unit relies on a reading its source never exposes: an interface gap (Def 9.8).
  • A question is put to a model that lacks the readings to answer it: Meridian's can bound when a shock reaches the covenant, not whose orders fall first (§9.7).

What a company must declare

  • Components: code, name, kind (division, shared function, treasury, market, governance), owner, the readings each holds and the readings it exposes.
  • Arrows: from, to, type, the reading each carries, and a witness: a situation in which the dependency is active.
  • Constraints: the statement, its reading, sense and level, its scope (the components it binds), its class, who can change it (board, lenders, regulator) and its owner.
  • The hierarchy: what each component rolls up to.
  • Where useful, the questions the architecture must answer and the readings each one needs.

How AXIOM uses it

AXIOM's architecture module (in development) takes components, typed arrows and scoped constraints as a declaration and is being built to read arrival floors, feedback cores, minimum cuts and the joint reviews they imply from that declaration, so the wiring behind every other number can be inspected.

Best Practices

Practices from the Corporate Transformation Best Practices knowledgebase that bear on this architecture.

Cases

Further reading

Read it on the DCT MapIn the LexiconRead the chapter: Vol I, Ch 9

Where to go next