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.

ERRAVol I, Ch 12AR

Risk, Resilience and Robustness (ERRA)

What can it lose, absorb and recover from?

What it is

The Enterprise Risk, Resilience and Robustness Architecture separates four questions that boards ask with one word (Vol I, Ch 12; Def 12.3, Table 12.1). Risk is how likely a loss is and how bad. Vulnerability is where a given shock hurts, and when. Robustness is the armor: the smallest shock that breaks a limit. Resilience is how far the company can be pushed and how fast it springs back. Each has its own object and its own number, and all four live on the state architecture.

Risk starts from loss channels, each a shortfall against a target, a floor or a covenant (Def 12.1). The book lists ten: financial, operational, strategic, technological, cyber, governance, legal and regulatory, environmental, reputational and ESG, each with its supports and a typical measure (Table 12.2). For each channel the company declares either a distribution, where odds are warranted, or a set of possible disturbances, where they are not (Def 12.2).

Robustness is a radius: the distance from today's state to the nearest wall, on a scale the company declares (Def 12.7). Resilience takes two numbers, a margin and a rate of return (Def 12.8). Propagation is carried by a gain matrix on the wiring, which says how much of a shock each arrow passes on (Def 12.11).

The armor thins: $132 million of cash, 1.4 points of risk (seed 26112)
Ch. I.12 The armor thins: $132 million of cash, 1.4 points of risk (seed 26112)

The board questions it answers

  • How likely is a breach, and how deep would it be?
  • Where would this shock hurt, and when?
  • What is guaranteed, and which wall is nearest?
  • How far can we be pushed, and how fast do we come back?
  • What are the odds the next shock arrives before we have healed?
  • Does a shock die out in the core, or echo?

What the book proves

  • Thm 12.1 Expected loss and expected shortfall are coherent measures; value at risk is not, and under it a combined book can look riskier than its parts.
  • Thm 12.2 The reverse stress test is the thinnest slack on the declared scale: it names the wall to watch first.
  • Thm 12.3 Resilience is two numbers. Recovery is to a band, never to the point, and a sustained stress moves the equilibrium itself.
  • Thm 12.4 Survival is a product of hazards, and the race between the next shock and recovery from the last has odds of 1 − e^(−λT). When armor is thin, the race is won with armor, not with speed.
  • Thm 12.5 A cascade dies out only when the core's spectral radius is below one, and the multiplier says how much a shock grows on its way round.

Meridian, the book’s worked company

Meridian's readings on the four questions are set side by side in Vol I, Table 12.1.

  • Risk: a 24.6% chance that the digital programme breaches the liquidity floor. Vulnerability: a demand shock reaches the divisions in one quarter and treasury in two. Robustness: $270m of cash above the floor today and $132m at the programme's low point. Resilience: Industrial Systems back in its band about three quarters after a $90m shock. (Vol I, Table 12.1)
  • On the declared scale the cash wall reads 0.44, the covenant 0.32 and the strategic-risk ceiling 0.11, with the risk index 11 points under its limit of 75. The thinnest armor is the risk ceiling, and it is measured with an error of ±6. (Vol I, §12.4; WE 12.1 Step 1)
  • Along the plan, armor falls from $270m to $132m at quarter 7. A phased build keeps it at $181m or more. (Vol I, WE 12.1 Step 2; OA 12.B.Ex.6)
  • A closure of the funding window lands in the plan's seven thin quarters with a probability of about 16%, and after the low point armor is rebuilt only slowly, so the race must be won with armor. For regulatory interventions at 0.15 a year and seven quarters to recover, the race is 23%. (Vol I, WE 12.1 Step 4; §12.6)
  • A $100m standby line cuts the breach chance to 12.4%, a phased build to 13.1%, and the two together to 3.0%. (Vol I, Table 12.6)
  • With a gain of 0.40 on each arrow of the four-unit core, the spectral radius is 0.80 and the total multiplier is 5, against 1.8 in a register of direct exposures. (Vol I, Fig 12.2; OA 12.B.Ex.4)

Explore it

Four questions, ten channels

The four questions of Vol I, Table 12.1, and the ten loss channels of Table 12.2 joined to the Meridian components that support them. Select a question for Meridian's reading, or a channel for its support and typical measure.

Four questionsTable 12.1Ten loss channelsTable 12.2SupportsMeridian's componentsRiskHow likely, and how bad?VulnerabilityWhere does it hurt, andwhen?RobustnessWhat is guaranteed?ResilienceHow far, how fast?FinancialRF​OperationalRO​StrategicRS​TechnologicalRT​CyberRC​GovernanceRG​Legal and regulatoryRL​EnvironmentalRE​ReputationalRR​ESGRESG​MarketMKTGovernanceGOVIndustrial SystemsINDMaterialsMATDigitalDIGEngineeringENGTreasuryTRS

Four questions

Ten loss channels

Supports

How it goes wrong

  • One word, risk, is used for four questions, and the answer to one is read as the answer to another (Table 12.1).
  • Value at risk is added across units, and consolidation appears to raise risk, or hides it (Thm 12.1).
  • A likelihood-times-impact register multiplies independent odds for shocks that share a cause (Thm 12.5(iv)).
  • Resilience is reported as one score, so a fast but shallow company and a slow but deep one look alike (Thm 12.3).
  • Recovery speed is relied on where the next shock is likely to arrive first (Thm 12.4).
  • A feedback core is treated as a list of direct exposures, and the echo is missed (Thm 12.5).

What a company must declare

  • For each risk: its channel, the objective, floor or covenant it measures a shortfall against, and its support components.
  • Its mode (distribution or set), its measure and the level at which it is read.
  • For distributions, event rates and severities and the persistence and size of deviations; for sets, the declared disturbance bounds.
  • The walls: each reading, its limit and the scale on which armor is measured.
  • Resilience: the rate and margin of each mode, and any common causes shared between risks.

How AXIOM uses it

AXIOM computes the breach odds, value at risk and expected shortfall, the reverse stress test on the cash floor, armor along the plan and the multiplier of the risk core. The recovery clock, the race and the full channel register 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 LexiconRisk appetite, in the LexiconRead the chapter: Vol I, Ch 12

Where to go next