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.

Overview

A note on the word “architecture”

In IT practice, enterprise architecture usually means the business, data, application and technology architectures of frameworks such as TOGAF, or the views of the Zachman framework. DCT Helix uses those layers to decide which shared programmes exist, and then decides when each one is laid and which departments it serves first.

DCT’s five architectures answer a different question: how the company itself is wired, moved, funded, measured and exposed while it changes. The practitioner frameworks supply a vocabulary of views and descriptions; DCT makes the description a mathematical object with theorems.

The architecture view in the DCT Helix white paper

The architectures, one tab each

  • 1ESAVol I, Ch 9

    Enterprise State ArchitectureAS

    What depends on what?

    The org chart says who reports to whom; the wiring says whose results move whose. A shock travels only along the wiring, and no faster than the number of links it must cross. Loops gather in a tightly coupled core, and a limit that binds units in a loop cannot be signed off unit by unit: it has to be reviewed jointly.

    Open the tab: State (ESA)

  • 2ETAVol I, Chs 6–8

    Enterprise Transformation ArchitectureAT

    What can be done, and in what order?

    Every initiative has preconditions, and outside them it cannot be taken at all. A target can be reached only along some sequence of moves, so order is a matter of feasibility, not of taste. A playbook can be repeated only if each round restores the preconditions of the next.

    Open the tab: Transformation (ETA)

  • 3ECAVol I, Ch 10

    Enterprise Capital ArchitectureAC

    What does the company have?

    Most of what makes change possible (skills, platforms, routines, relationships, position) is not on the balance sheet. Every stock has a rent, the investment needed merely to hold it, and a speed limit on how fast it can be rebuilt. Capital is fast to destroy and slow to rebuild.

    Open the tab: Capital (ECA)

  • 4EPAVol I, Ch 11

    Enterprise Performance ArchitectureAP

    What does it deliver?

    Between options that do not dominate each other, a weighted scorecard does not discover the winner: its weights choose it, and its scaling is a second set of weights. A programme that builds the company’s state is measured as underperformance first, because its costs arrive at once and its benefits later. Declaring the apparatus turns a verdict into a choice the board owns.

    Open the tab: Performance (EPA)

  • 5ERRAVol I, Ch 12

    Risk, Resilience and RobustnessAR

    What can it lose, absorb and recover from?

    Boards use one word for four questions, and each needs its own number: how likely and how bad a loss is (risk), where a shock hurts (vulnerability), how large a shock the company can take before it breaks (robustness), and how far it can be pushed and how fast it springs back (resilience).

    Open the tab: Risk, Resilience and Robustness (ERRA)

  • 6UETAVol I, Chs 13–14

    Unified Enterprise Transformation ArchitectureUE

    Do the five descriptions make one company?

    One state, five ledgers, and one register of the couplings between them. Unifying costs the existing models nothing, since each survives unchanged, but it adds what no single ledger can see: a whole that is unstable while every layer passes its own test, cash promised twice, and a single synergy that pushes the company past its stability edge.

    Open the tab: Couplings and Unification (UETA)

  • 7GEOPVol I, Ch 15

    GEOP and the Enterprise Optimization Architecture

    What is the best plan the architectures allow?

    The architectures supply every part of one decision problem, the General Enterprise Optimization Problem: the moves, the stocks, the objective, the limits, and the couplings that bind them. Feasibility is checked before optimality, and at the optimum every limit that binds has a price.

    Open the tab: GEOP and the Optimization Architecture (EOA)

Where to go next