AirfieldpathOrlando Sanford International

5.1 · The Interchange · Overview

How the Interchange sits between the platform and the owner

The Interchange is the developed component in the middle. The platform side feeds it. The owner's systems of record sit on the far side.

Level 2 of 3 This component, complete on its own. Its files, sources and tests are the detail below. Open the detail

Platform side

  • The twin and the Exploders
  • Jira, through the Jira side of the Interchange
  • The SDLC tools the platform uses: Git and Confluence
  • The Collector and its relay units: sensors, controllers, PDFs, spreadsheets, video

The Interchange

  • Stores the original with its sha256
  • Verifies the signature and classifies by data rules
  • Checks against the catalogue, de-duplicates and orders
  • Chooses a path by rule: alert, ticket, work order, analysis
  • A person confirms before a work order leaves

The owner's side

  • Simplify i3, the system the RFP names (interface to confirm, Q-35)
  • Other systems of record
  • No real i3 has been called, but we will be ready.

Existing systems keep performing their functions and stay the authoritative systems of record (RFP 2027-006, Attachment C, 1.1 Overview). The Interchange copies and links. It changes a record in another system only where a rule says so and a person has acted.

State when this site was built: the Interchange runs on one machine. The Jira side, the i3 interface and the alert channels run on fixtures and stubs. Nothing at the airport is connected.