AirfieldpathOrlando Sanford International

Six explainers

How it works

Six short explainers on how the parts of the twin work. Each has one diagram, plain text, and links to where it is shown: the screens, the sheets, the component pages and the requirements rows.

The Exploder showing an escalator lifted apart into its parts, each part a tagged item1Asset tagsWhat a tag carries, how it is attached in the Exploder, and where its record shows.The Sources screen of the proof of concept: the systems of record and where each value comes from2DataWhere the twin's data comes from, and which system owns each value.The Exploder layer for live events and analysis, an orbit of the airport with event markers3EventsHow events arrive, how they show as layers, and what an event can start.The Interchange screen of the proof of concept: a work order and its status flow4The InterchangeOurs, at the centre. It carries one work order out to the owner's system and its status back.Sheet A-04, Off the shelf: Jira and Confluence on the platform side feeding the Interchange5JiraOff the shelf, on the platform side, feeding the Interchange.The Predictive Maintenance screen of the proof of concept: a trend, a proposal and a question to the twin6AnalyticsThe loop from reporting to decision to analytics to events to action, and what exists today.

Components Why this is different