Learning Data

Topics › Enterprise architecture › The map before the data

The map before the data

A series on enterprise architecture, and why it matters for data. Tomás, a new enterprise architect at a publicly owned energy utility, learns how the place works before he asks what its data should answer: who it serves, why it must change, what it must be able to do, how value reaches people, who does the work, and what runs it.

The films

Watch them in order: each film adds a layer to the map.

Film 1 of 11 · Why enterprise architecture

Day one

An org chart, 140 systems and a backlog: all true, none of it the place. Learn how it works before you ask the questions.

5 min · Pause and think · The map before the data

Film 2 of 11 · Customers and offerings

Who it serves, and how it pays

Edison's customers wanted light, not electricity. Who pays, who uses and who decides, and a canvas for each.

5 min · Pause and think · The map before the data

Film 3 of 11 · Motivation

Why it moves

Three letters pull the utility three ways. Who cares, what pushes, what must become true, and a principle to settle it.

4½ min · Pause and think · The map before the data

Film 4 of 11 · Capabilities

What it must be able to do

The runners changed; the ability to move a message stayed. A capability outlasts whoever does it, however and with whatever.

5½ min · Pause and think · The map before the data

Film 5 of 11 · Value streams and processes

How value reaches people

Lunch crosses Mumbai, changing hands. Power comes back to forty homes. Value from the customer's side, and detail only where order matters.

6 min · Pause and think · The map before the data

Film 6 of 11 · Actors, roles and domains

Who does it, and where meaning changes

Japan runs on two frequencies. A utility has two kinds of customer. Roles, actors, and a translation at the edge.

6 min · Pause and think · The map before the data

Film 7 of 11 · Applications, technology and the path to a target

Today, and where it's going

An imagined street in 2045. Today's 140 systems on the map. A target, and the path to it, with reasons.

5 min · Pause and think · The map before the data

Film 8 of 11 · Decisions, questions and measures

Now the questions appear

Kerala's fishermen, 1997. Forty-two requests, the skipper's test. Goals traced down to the measures that check them.

6 min · Pause and think · The map before the data

Film 9 of 11 · Objects, owners and rules

Rules with a home

Tartu's once only. A bill never corrected, and a script on the wall. Each rule written once, with an owner and a reason: tests for the data, a tracking table for the business.

8 min · Pause and think · The map before the data

Film 10 of 11 · Change, owners and contracts

When strategy moves

M-Pesa in Kenya, 2007. A social tariff for every eligible household. One change, walked down every layer to its owners, rules and contracts.

7 min · Pause and think · The map before the data

Film 11 of 11 · Keeping the map: one tool, many sources, and agents

A map people and agents can read

Hōkūleʻa, 1976. A map kept in one tool, fed by other systems, reviewed and versioned, with every view generated from it. Agents draft; people confirm.

8½ min · Pause and think · The map before the data

Take it apart, then make the call

Twelve hands-on labs, one for each film and one on ArchiMate 4, then 26 situations from every film. Your progress stays in this browser.

Take it apart: 12 hands-on labs →Make the call: 26 situations

One thread: the first weeks

Day one is a badge, an org chart, a list of 140 systems and an invitation to a meeting about “the transition program”. Film by film, Tomás builds a map of the utility, from why it exists down to what runs it. Only then can he say which questions it needs to answer, where each data rule belongs, and what a change in strategy means for the data.

Every film opens somewhere else, at another time

FilmOpens withStill true today
Day oneThe Domesday survey, England, 1086Before you can govern a place, you have to know what it is.
Who it serves, and how it paysEdison's customers on Pearl Street, 1882People buy what an offering does for them: light, not electricity.
Why it movesThe north-east blackout, 1965When no one sees the whole, shared rules hold it together.
What it must be able to doThe Inca's relay runners, the Andes, 1400sRunners and roads change; the ability to move a message stays.
How value reaches peopleMumbai's dabbawalas, since 1890Value reaches people through hand-offs, and the detail lives there.
Who does it, and where meaning changesJapan's two frequencies, 1890s and 2011The same word can mean something different on each side of a line; what crosses must be translated.
Today, and where it's goingAn imagined morning in the utility's region, 2045Where it's going is drawn as carefully as where it is, and the path between is its own drawing.
Now the questions appearKerala's fishermen, 1997A question matters when someone will act on its answer, in time.
Rules with a homeA birth in Tartu, Estonia, todayEach fact has one home and one owner, so it's asked for once.
When strategy movesM-Pesa in Kenya, 2007A strategy fits in a sentence; making it real reaches every layer, down to the counter.
A map people and agents can readHōkūleʻa's voyage to Tahiti, 1976A map lives while people use it, keep it true and can pass it on.

Who knows the place

Cyan outlines are technical; gold outlines are business.

Draws the map

Tomás, the new enterprise architect, the series' guide

Runs the network

Grace, who owns network operations

Speaks for customers

Farah, the customer advocate

Knows the rules

Ama, the regulatory lead