AirfieldpathOrlando Sanford International

Section 2

Proof of concept

The 69 screens of the working proof of concept in ten groups. Each screen page shows the capture, the narration line, what the screen must do and the requirements that name it.

70 pages in this section. Select a screen for its capture, narration, requirements and the link that opens it.

Carefully crafted and curated test data for common use cases. Only the drone screens are simulated.

Level 1 of 3 This section, complete on its own. Each page below is a component with its own data and sources. Open the components

Command 4

No.PageWhat it holds
2.1Command CenterThe whole airport at a glance: its pulse, a gauge for each system, and today against normal.
2.2Local ControllersEach functional area's own controller, built from the screens it already owns.
2.3Security ConsoleCamera feeds by area, detections a person confirms, the security drone and the incidents.
2.4Nightly Round SimulatedAfter hours, the perched caged drone flies its round on thermal and fills its checklist.

Terminal 10

No.PageWhat it holds
2.5Terminal Assets NowWhat is working in the terminal right now, and what needs a person, in plain words.
2.6Terminal FlowWhat is moving in the terminal now, how much each system can carry, and where it is slowing.
2.7The Terminal in 3DThe terminal as a model you can turn, with its lifts, bridges, baggage and air handling placed on it.
2.8Vertical TransportationWhether people can move between floors, and which lift or escalator needs a person.
2.9Boarding BridgesWhich of the 16 boarding bridges are ready for the next flight.
2.10Baggage HandlingWhether bags are moving, and where a jam or fault needs a person.
2.11HVAC and Building ManagementWhether the terminal's heating, cooling and air are healthy, read from the building management system.
2.12Point RegistryEvery reading the twin uses, where it comes from, and who owns it.
2.13Predictive MaintenanceProblems the twin sees coming, each proposed as a repair for a person to approve.
2.14Sensor Gaps (concept)A proposed way to add sensors where no equipment maker's data reaches. A design, not built.

Maintenance 6

No.PageWhat it holds
2.15Asset RecordOne asset's full record: where it sits, what it is, its readings, its schedule and its history.
2.16Work OrdersThe repairs and inspections in hand, as the maintenance team sees them.
2.17PM CalendarThe planned maintenance for the month, and how much of it is done on time.
2.18BacklogHow much work is waiting, and how long it has waited.
2.19Trends and AlarmsThe readings over time, the alarms they raised and who answered them.
2.20Maintenance KPIsWhether maintenance is getting better, in the measures maintenance managers use.

Connect 6

No.PageWhat it holds
2.21Sanford InterchangeEvery 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.
2.22Sensors on the MapEvery sensing point at its place; click one for its quick look, its views and anything the twin wants to ask.
2.23Sensor CatalogueWhat to measure on each kind of asset, the sensor and bus that do it, and the collector it plugs into.
2.24Existing SensorsWhat SFB already owns, and the decision on each: integrate, extend, retire or add.
2.25Operations and PerformanceHow the platform itself is doing: service health, data health, latency end to end, capacity, cost and the logs.
2.26Model LibraryEvery use of AI and what it may see and do, with its approval and its manual path.when it is switched off.

Drones 6

No.PageWhat it holds
2.27Drone Operations SimulatedDrones that could help inspect the airfield, and the airspace rules they must meet. Not in the RFP's scope today.
2.28Inspection Mission SimulatedHow a drone inspection is planned from an asset and held until it is safe to fly.
2.29Drone Cockpit SimulatedWhat a drone pilot would see during an inspection. A concept.
2.30Corridors and Protected Areas SimulatedWhere a drone may and may not fly on the airfield, and when.
2.31Survey and Evidence SimulatedWhat the drones found, each in the medium that proves it.
2.32Close Inspection SimulatedEvery exit, every heat source and any flame, checked up close.

Operate 9

No.PageWhat it holds
2.33Airfield NowThe state of the runways and taxiways right now, and what needs a person.
2.34Runway HistoryA runway drawn to scale with its layers and its history, and any past work order replayed in place.
2.35Self-InspectionThe daily airfield inspection the FAA requires, with each problem sent to the work order system.
2.36Condition and NOTAMsAirfield conditions and the notices pilots receive, drafted here and filed by a person.
2.37Airfield LightingWhich airfield lights are out, and the repair each one needs.
2.38Wildlife and FODBirds and debris on the airfield, and the reports the FAA asks for.
2.39Construction SafetyWork zones on the airfield and the safety plan for each.
2.40ARFF and the Emergency PlanThe airport fire and rescue service against the FAA's rules.
2.41Storm PlanA storm or emergency plan run as work orders, with what the twin finds and what is escalated.

Assets 7

No.PageWhat it holds
2.42The Airport in 3DThe whole airport as a model you can turn.
2.43The Airfield in 3D, from LidarThe airport as the lidar measured it: ground, buildings and where water would gather, flown in close.
2.44Flythrough and Ground AccessA flight over the airport, and the roads and rail that reach it.
2.45Spatial EnablementWhich maps, drawings and models the twin can use today, and what to add next.
2.46Asset RegistryEvery asset, its condition and the system that holds its record.
2.47PavementThe condition of the runways and taxiways, with the state's own scores for the runways.
2.48Maintenance and Work OrdersThe repairs in progress, read from the Authority's work order system.

Fund 3

No.PageWhat it holds
2.49Grant OpportunitiesThe grants an airport can win, and which projects fit them.
2.50Grant ApplicationA grant application assembled from the airport's own records.
2.51Grant PipelineEach grant from application to closeout.

Prove 6

No.PageWhat it holds
2.52Safety ManagementHazards, their risk and what is being done about them.
2.53Accountability and RecordsThe records the airport must keep, and the ones it must protect.
2.54Duties and DeadlinesEvery recurring duty, who owns it, when it is next due and the evidence held.
2.55Role DashboardsEach team sees its own page; the executive page says it in plain words.
2.56WorkflowsHow a fault becomes a repair: who is told and who approves it, and where the work is recorded.
2.57Shift BriefingA shift briefing that walks the screens and asks a person to confirm each action.

Set up 11

No.PageWhat it holds
2.58Rules and Data LibraryEvery body of rules and data the platform has loaded, and what each one drives.
2.59GlossaryEvery airport term the screens use, with one line and its source.
2.60Systems of RecordEvery system the twin reads, and proof that each one stays the record.
2.61IntakeDocuments and data loaded, checked and verified by a person.
2.62Open StandardsThe open standards the twin speaks, so the Authority is never locked in.
2.63Security and AdministrationWho can see what, and a record of everything anyone does.
2.64Implementation and RoadmapThe plan from award to go-live, and what comes after.
2.65Environments and OperationsWhere the service would run, how it would be watched and kept safe, and how staff learn it. A target, not deployed.
2.66SupportHow staff get help, and how a problem found in use becomes a reviewed fix.
2.67Platform FamilyThe sister products this one is built beside, and what each actually holds.
2.68RFP ComplianceEvery requirement of the RFP, and where the work stands on each.

Reference 2

No.PageWhat it holds
2.69Glossary terms333 terms the screens use, each with a citation and a confidence word.
2.70Narration clips403 recorded narration lines the screens and the References entries play.