AirfieldpathOrlando Sanford International

How it works · 3 of 6

Events

How events arrive, how they show as layers, and what an event can start.

Events. Exploder clip: the layer "Live: events and analysis" alone, a slow orbit, 4 seconds, through the kit's film clock on the Light theme. No sound. It has no sound, so this text is its transcript: The Exploder layer for live events and analysis, an orbit of the airport with event markers.
From a source to an event to an action
A source or sensora feed, a notice, a readingCollectorkeeps the original,classifies, checks, binds tothe assetTrapa trigger names the eventRule paththe path names the action,who is told and the timingActionalert, ticket, work orderafter a person confirms,analysisA source or sensora feed, a notice, a readingCollectorkeeps the original, classifies, checks,binds to the assetTrapa trigger names the eventRule paththe path names the action, who is told andthe timingActionalert, ticket, work order after a personconfirms, analysis

Events arrive from the feeds the twin reads and from the sensors it is bound to. The Collector keeps each original untouched under its sha256, checks the fields and the unit against the type in the catalogue, and binds the device to the asset it observes.

Each arriving item is evaluated against the triggers. A match becomes a named event, such as bhs.conveyor.blocked. An item that traps nothing still goes to history. The event's name and metadata choose a path, and the choice and its reasons are written on the event.

Events show on the screens as layers and lists: Airfield Now for the state of the runways and taxiways, Condition and NOTAMs for the notices, the Storm Plan for an emergency run as work orders, and Trends and Alarms for readings over time. In the Exploder they are the Live layer.

An event can alert a person, open a ticket, draft a work order for a person to confirm, or start an analysis. It does not change a record in another system unless a rule says so and a person has acted. The Interchange is built and tested locally; nothing at the airport is connected.

Components for Events

15 components on this site relate to this explainer: 2 exploder layer, 3 document, 2 code and tests, 8 screen. The best 6 are shown.

Picture: Exploder still of the layer "Live: events and analysis" alone, through the kit's film clock on the Light theme (exploder/?film=1, setOnly).
Clip: Exploder clip: the layer "Live: events and analysis" alone, a slow orbit, 4 seconds, through the kit's film clock on the Light theme. No sound.

Picture: Exploder still of the layer "Sensors on the roads (concept)" alone, through the kit's film clock on the Light theme (exploder/?film=1, setOnly).
Clip: Exploder clip: the layer "Sensors on the roads (concept)" alone, a slow orbit, 4 seconds, through the kit's film clock on the Light theme. No sound.

Exploder layer · The Exploder

Layer: Sensors on the roads (concept)

1 items in the network group of the Exploder.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Exploder layer
Status
not linked
Airport layer
Sensors on the roads (concept)
Airport area
Landside: roads and lots
System
The road-stud sensor
Sensor type
not linked

Open in the Exploder

Picture: Headless capture of poc/index.html?v=predict&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Clip: Excerpt of poc/flybys/terminal-fault.mp4, 1.9 to 6.0 seconds. A drawing of the process: A terminal fault: trend, prediction, work order. No sound.

Screen · Proof of concept · Terminal

Predictive Maintenance

Problems the twin sees coming, each proposed as a repair for a person to approve.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
partly met
Airport layer
Screens: the POC story and the spines
Airport area
not linked
System
not linked
Sensor type
not linked

Open the screen · Open the detail

Picture: Headless capture of poc/index.html?v=inflector&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.

Screen · Proof of concept · Terminal

Sensor Gaps (concept)

A proposed way to add sensors where no equipment maker's data reaches. A design, not built.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
partly met, target
Airport layer
Screens: the POC story and the spines
Airport area
not linked
System
not linked
Sensor type
not linked
RFP rowsM-069M-145

Open the screen · Open the detail

Picture: Headless capture of poc/index.html?v=interchange&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.

Screen · Proof of concept · Connect

Sanford Interchange

Every Authority system through one hub, each still the record of what it owns, with a work order going to Simplify i3 and its status coming back.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
not linked
Airport layer
Screens: the POC story and the spines
Airport area
not linked
System
not linked
Sensor type
not linked
SheetA-10

Open the screen · Open the detail

See all 15 related components

All 15 related components by type

Exploder layer

Document

Code and tests

Screen

Where to see it

Screens

Sheets

Requirement rows that name these screens (26)

M-020M-065M-082M-147M-003

21 more rowsM-016M-017M-018M-019M-028M-112M-119M-123M-124M-126M-132M-134M-009M-027M-059M-062M-085M-091M-100M-069M-145