Enterprise reference architecture of an airport group

Views in this map

1. 1
   Reference architectureEvery block the two airports need, layer by layer; dashed ones aren’t built yet.
2. 2
   Gap analysisEach block against the 2028 target: in place, partial, a gap, or retiring.
3. 3
   2028 targetBy 2028 the gaps are built, partials upgraded and three old systems retired.
4. 4
   Integration hubThree adapters and 214 hand-built routes; an event broker replaces them in 2026.

Reference architecture ‹ › Gap analysis ‹ › 2028 target · Reference architecture ▸ Integration hub

Flows to play

• ▷
  A late flight, todayPetrel Air’s Lisbon flight runs 40 minutes late: who hears, and how. In the Reference architecture view.
• ▷
  The same flight in 2028One event reaches the stand, the turnaround, the handler and the passenger. In the 2028 target view.

The model behind it

84 records of 12 types. Every box on the map is one of them, so the filters and the record panel read the same data.

• Applications 19
• Business capabilities 8
• Channels 7
• Data services 7
• Infrastructure 7
• Security services 7
• Operations services 6
• 5 more types 23

Filters

Status and Layer and Hosting and Owner domain: pick a value and everything else fades.