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.

ETAVol I, Chs 6–8AT

Enterprise Transformation Architecture (ETA)

What can be done, and in what order?

What it is

The Enterprise Transformation Architecture is the repertoire of moves the company can make (Vol I, Chs 6–8; named in Table 1.4). Each move is an operator: a declared action that takes the company from one state to another (Def 6.1). Its declaration records what it does, the resources it consumes, the part of the company it touches and where its effect comes from, whether fitted to data, engineered or assumed.

Every operator has a domain, the set of states from which it can be taken (Defs 6.2–6.4). Outside the domain there is no result at all: readiness stops meaning "should not" and starts meaning "cannot". Operators compose into programmes, so a programme is a word written in the repertoire (Defs 6.5–6.7), and the states that some word of length k can reach form the k-step reachable set (Def 6.9).

The repertoire runs on a clock. Chapter 7 adds the state equation, with the decisions the company makes, the environment it does not control and the feedback that links them; Chapter 8 adds uncertainty, so every plan carries a fan of outcomes and some events arrive as jumps. In the unified view each operator also carries a write set, the components it changes, so a move is booked in every ledger it touches (Def 13.6).

Recycled savings stop the nested domains from shrinking (seed 26106)
Ch. I.6 Recycled savings stop the nested domains from shrinking (seed 26106)

The board questions it answers

  • Can we take this action from where we are today?
  • Is the target reachable, and by which shortest sequence of moves?
  • Is this playbook a strategy we can repeat, or a trade that runs out?
  • How far will execution drift from the design?
  • What are the odds the plan breaches a floor on the way?
  • How hard should we steer a loop that answers with a delay?

What the book proves

  • Thm 6.1 An operator and a step of the company's dynamics are one subject. An effect that needs the environment's cooperation is an assumption, not a commitment.
  • Thm 6.4 A target is reachable exactly when some sequence of moves gets there, and a breadth-first search of the planning tree finds the shortest one. Some targets can be approached but never reached, and must carry a tolerance.
  • Thm 6.3 The sustainable core is the largest set from which a move can be repeated for ever. A playbook is a strategy only from inside it; outside, it is a trade that runs out.
  • Thm 6.5 Execution error compounds when a programme amplifies it and stays bounded when the programme damps it, so the same shortfall can be harmless or ruinous.
  • Thm 7.5 A loop that answers with a delay tolerates far less steering: pushing harder can make it cycle instead of converge.
  • Thm 8.5(ii) The flaw of averages: the plan run on average inputs is not the average outcome of the plan.

Meridian, the book’s worked company

Meridian's repertoire is four moves: an automation round, a digital build, and the sale of part of Industrial Systems with or without its engineers.

  • The automation round costs $120m, closes half the gap to an efficiency ceiling of 85 and adds one capability point. It can be taken only with liquidity of at least $470m and workforce capability of at least 55. (Vol I, WE 6.1; Fig 6.1)
  • From today ($620m of liquidity, technology 41, capability 58), three of the four first moves are possible: the digital build alone would leave $310m, below the board's $350m floor. Selling with the engineers leaving drops capability to 53 and is a dead end, since neither the build nor automation can follow. The target, technology of at least 50, is reached by exactly one path: sell while keeping the engineers, then build, ending at $356m, $6m above the floor. (Vol I, Fig 6.3; Thm 6.4)
  • With its savings paid out, the automation playbook fails in the third round. With savings recycled, efficiency climbs 71, 78, 81.5, 83.25 and on towards the ceiling, and the round can be repeated from any liquidity of at least $535m, so Meridian has $85m to spare. (Vol I, WE 6.1; Table 6.4)
  • The plan's liquidity trough is $482m at quarter 7, but once quarterly deviations and funding-window closures are added the chance of breaching the floor is 24.6%. A $100m standby line alone brings it to 12.4%, a phased build alone to 13.1%, and both together to 3.0%. (Vol I, WE 8.1; Table 8.5)
  • Meridian's hiring loop is stable for steering gains below 3.17; with a one-quarter delay the limit falls to 1.67, and the cautious gain of 0.5 turns out to be the fastest. (Vol I, WE 7.1; Table 7.5)

Explore it

The repertoire and the planning tree

Meridian's four moves and every sequence of up to two of them from today (Vol I, Fig 6.3). Numbers are liquidity, technology (T) and workforce capability (W). Select a move in the repertoire to read its preconditions and effects, or a branch to see why it is open or pruned.

Repertoirethe four movesTodaythe starting stateFirst moveSecond moveA · automation roundD · digital buildS · sell, engineersleaveS* · sell, engineerskeptToday$620m · T 41 · W58S$732m · T 36.9 · W 53S*$712m · T 36.9 · W 58Dnot possibleA$500m · T 41.0 · W 59S → Dnot possibleS → Anot possibleS* → D · target$356m · T 54.7 · W 58S* → A$592m · T 36.9 · W 59A → S$612m · T 36.9 · W 54A → S*$592m · T 36.9 · W 59A → Dnot possibleA → A$380m · T 41.0 · W 60

KeyPossiblePruned: a precondition fails

The repertoire

The planning tree

How it goes wrong

  • An initiative is approved whose preconditions do not hold today. It has no result, however strong its business case.
  • A target is set that no sequence of moves reaches, or that the only path reaches with no margin: Meridian's single route ends $6m above its floor.
  • A playbook is run that consumes its own precondition, and it stops in the third round.
  • A plan is judged on its average path. Meridian's planned low is $482m; the mean of its simulated lows is $384m (Thm 13.4(iv)).
  • An effect that depends on the market cooperating is booked as a commitment (Thm 6.1).

What a company must declare

  • The state readings: each with its unit, measurement source, error band, today's value, the ledger it belongs to and the component that carries it.
  • For each initiative: its effect on each reading, its preconditions (reading, sense and level), its write set and the provenance of its effect.
  • Where execution drift matters, each move's sensitivity and its expected shortfall.
  • The stochastic channels: the size and persistence of deviations, and the rate and severity of discrete events.

How AXIOM uses it

AXIOM computes the odds that a plan breaches a floor on the book's model (it reproduces Meridian's 24.6%) and the steering regimes of a delayed loop. Operator domains, the planning tree and the sustainable core 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 LexiconTransformation operator, in the LexiconRead the chapter: Vol I, Chs 6–8

Where to go next