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.

UETAVol I, Chs 13–14UE

Unified Enterprise Transformation Architecture (UETA)

Do the five descriptions make one company?

What it is

The Unified Enterprise Transformation Architecture holds the five descriptions together (Vol I, Chs 13–14; Def 13.1). It rests on three principles: one shared skeleton, the state architecture; one state, so that every layer is a readout of the same trajectory (Def 13.2); and declared coupling, so that whatever passes between layers is written down.

The coupling register records each channel from one layer to another: the component, arrow or constraint it runs through, its functional form and its declaration (Def 13.1). Its gains make up an interaction matrix: the diagonal blocks are each layer's own gains, the off-diagonal blocks are the couplings, and a zero block is itself a declaration that someone must own (Def 13.5). Even an empty register is a claim, and a falsifiable one (Prop 13.1).

Five compatibility conditions make the five descriptions one company (Def 13.4): every carrier, support and write set is a component of the state architecture; an indicator shared by two layers has one measurement contract; every risk buffer names the capital stock that funds it, and that identity is in the register; the joint feasible region is not empty; and each move's domain is cut down to that region. Chapter 14 then asks whether the unified model is fit to optimize: whether it is stable, well conditioned and viable over the horizon.

Every layer passes its own test, the whole fails (seed 26113)
Ch. I.13 Every layer passes its own test, the whole fails (seed 26113)

The board questions it answers

  • Do our five models describe one company?
  • Are "fully funded" and "fully buffered" true together?
  • When will each ledger feel this programme, and which ledgers can it never reach?
  • Can every office pass its stress test while the company fails?
  • Can we afford a new synergy link?
  • What does deciding separately cost us?

What the book proves

  • Thm 13.1 Unifying keeps every existing model and drops none: each layer survives unchanged, and none is redundant.
  • Thm 13.3(ii) The whole needs the interaction matrix's spectral radius below one. Every layer passing its own test is necessary, never sufficient.
  • Thm 13.3(iii) No route of positive gain means no effect: an insulation certificate exactly as strong as the register is honest.
  • Thm 13.4(iii) Confinement: no ledger responds before its distance from the programme's write set.
  • Thm 13.5 Consistency is necessary, cycles defeat bilateral checks, and every funded company has a cycle running through capital, performance and risk.
  • Prop 13.5 Integrated decisions beat separated ones by exactly what the couplings carry.
  • Thm 14.3 The register is a stability budget: its ceilings bound the true dynamics, and a single new link can break the budget.

Meridian, the book’s worked company

Vol I runs Meridian's programme through all five ledgers at once.

  • Three ledgers, three clocks: liquidity bottoms at $482m at month 21 against the $350m floor; the scorecard bottoms at 32.1 at month 11 and is back at 37.0 at month 29; strategic risk peaks at 73.55 at month 11 against its ceiling of 75. A review at month 11 sees failure in one ledger and comfort in another. (Vol I, Fig 13.1; OA 13.B.Ex.4)
  • Confinement: the programme writes to Digital and engineering; treasury and Industrial Systems are one step away; Materials, the market and governance are unreachable, so crediting Materials with the programme is refuted by the wiring. (Vol I, Thm 13.4(iii); OA 13.B.Ex.3)
  • The joint check: the programme's draw of $138m at quarter 7 and the closure buffer of $187m are both claims on the same $270m of cash above the floor. Together they come to 325, short by $55m, although each office signed off its own claim. The standby line and the phased build together pass by $94m; alone, the line leaves 12.4% breach odds and phasing 13.1%; only both reach 3.0%. (Vol I, WE 13.1; Table 13.6)
  • The risk core: a gain of 0.40 on each of its arrows gives ρ = 0.80, a half-life of 3.11 quarters and an amplification of 5. A new link between Industrial Systems and Digital at 0.40 lifts ρ to 1.0246, so a synergy every office would approve makes the core unstable. The board's rule of a half-life of at most four quarters caps ρ at 0.8409. (Vol I, WE 14.1; OA 14.B.Prop.1)
  • The register's channels are named block by block; Vol I prints numeric gains only for the risk core. (Vol I, Table 13.2)

Explore it

The coupling register

The channels of Vol I, Table 13.2, as Meridian instantiates them, from the layer they leave to the layer they enter, with the risk core as the one block whose gains the book prints. Select a channel for its form, what it runs through and the book's values.

Fromthe layer that sendsCoupling registerMeridian's channelsTothe layer that receivesAT​ · TransformationsendsAT​ · TransformationreceivesAC​ · CapitalsendsAC​ · CapitalreceivesAP​ · PerformancesendsAP​ · PerformancereceivesAR​ · RisksendsAR​ · RiskreceivesRisk core G0.40 per arrow · ρ 0.80K1 · funding couplingK2 · buffer identityK3 · joint checkK4 · target–exposure linkK5 · domain restrictionK6 · stocks enlarge the menuK7 · conversion billK8 · J-curveK9 · rentK10 · retained flows build stocksK11 · shortfalls are lossesK12 · shocks deplete stocksK13 · dents and recoveriesK14 · exposure during the programmeK15 · review windowsK16 · standby line

Layers

Channels

Add the new link

Meridian's risk core with a gain of 0.40 on each arrow (Vol I, Fig 12.2; WE 14.1). Add the proposed link between Industrial Systems and Digital and the spectral radius, computed here from the gain matrix, moves from 0.80 to 1.0246.

EngineeringENGIndustrialSystemsINDTreasuryTRSDigitalDIG
Spectral radius ρ
0.80
Half-life
3.11 quarters
Amplification
5.00
Board's rule (half-life ≤ 4 quarters)
ρ ≤ 0.8409: passes

Computed here from the gain matrix; Vol I prints 0.80 and 1.0246 (WE 14.1; OA 14.B.Prop.1).

How it goes wrong

  • Every layer passes its own stress test while the whole is unstable (Thm 13.3(ii); Fig 13.2).
  • The same cash is promised to two purposes (WE 13.1).
  • A single synergy, one every office would approve, pushes the company past its stability edge (WE 14.1).
  • A blank in the register is read as "no coupling" rather than as a claim nobody made (Prop 13.1).
  • A risk buffer is declared without the capital stock that funds it (Def 13.4, C3).

What a company must declare

  • Each channel: the layer it leaves and the layer it enters, what it runs through in the state architecture, its form (identity, inequality, linear gain or domain restriction) and, where it is linear, its gain, sign and lag; its owner and source.
  • For each of the twenty off-diagonal blocks: declared zero, with its owner and reason, or the channels it carries.
  • The gains of the risk core.
  • Owners for the analytical assumptions of Table 14.1.

How AXIOM uses it

AXIOM computes the stability of the risk core (ρ, half-life, amplification and the repairs that meet the board's half-life rule), audits measured gains against the register's ceilings, and checks the joint feasibility of the cash commitments, the test of WE 13.1. The full coupling register, the five compatibility conditions and the ledger clocks belong to AXIOM's architecture module (in development).

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 LexiconCoupling register, in the LexiconRead the chapter: Vol I, Chs 13–14

Where to go next