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
Groups
Command 4
No. Page What it holds 2.1 Command Center The whole airport at a glance: its pulse, a gauge for each system, and today against normal. 2.2 Local Controllers Each functional area's own controller, built from the screens it already owns. 2.3 Security Console Camera feeds by area, detections a person confirms, the security drone and the incidents. 2.4 Nightly Round Simulated After hours, the perched caged drone flies its round on thermal and fills its checklist.
Terminal 10
No. Page What it holds 2.5 Terminal Assets Now What is working in the terminal right now, and what needs a person, in plain words. 2.6 Terminal Flow What is moving in the terminal now, how much each system can carry, and where it is slowing. 2.7 The Terminal in 3D The terminal as a model you can turn, with its lifts, bridges, baggage and air handling placed on it. 2.8 Vertical Transportation Whether people can move between floors, and which lift or escalator needs a person. 2.9 Boarding Bridges Which of the 16 boarding bridges are ready for the next flight. 2.10 Baggage Handling Whether bags are moving, and where a jam or fault needs a person. 2.11 HVAC and Building Management Whether the terminal's heating, cooling and air are healthy, read from the building management system. 2.12 Point Registry Every reading the twin uses, where it comes from, and who owns it. 2.13 Predictive Maintenance Problems the twin sees coming, each proposed as a repair for a person to approve. 2.14 Sensor Gaps (concept) A proposed way to add sensors where no equipment maker's data reaches. A design, not built.
Maintenance 6
No. Page What it holds 2.15 Asset Record One asset's full record: where it sits, what it is, its readings, its schedule and its history. 2.16 Work Orders The repairs and inspections in hand, as the maintenance team sees them. 2.17 PM Calendar The planned maintenance for the month, and how much of it is done on time. 2.18 Backlog How much work is waiting, and how long it has waited. 2.19 Trends and Alarms The readings over time, the alarms they raised and who answered them. 2.20 Maintenance KPIs Whether maintenance is getting better, in the measures maintenance managers use.
Connect 6
No. Page What it holds 2.21 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. 2.22 Sensors on the Map Every sensing point at its place; click one for its quick look, its views and anything the twin wants to ask. 2.23 Sensor Catalogue What to measure on each kind of asset, the sensor and bus that do it, and the collector it plugs into. 2.24 Existing Sensors What SFB already owns, and the decision on each: integrate, extend, retire or add. 2.25 Operations and Performance How the platform itself is doing: service health, data health, latency end to end, capacity, cost and the logs. 2.26 Model Library Every 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. Page What it holds 2.27 Drone Operations Simulated Drones that could help inspect the airfield, and the airspace rules they must meet. Not in the RFP's scope today. 2.28 Inspection Mission Simulated How a drone inspection is planned from an asset and held until it is safe to fly. 2.29 Drone Cockpit Simulated What a drone pilot would see during an inspection. A concept. 2.30 Corridors and Protected Areas Simulated Where a drone may and may not fly on the airfield, and when. 2.31 Survey and Evidence Simulated What the drones found, each in the medium that proves it. 2.32 Close Inspection Simulated Every exit, every heat source and any flame, checked up close.
Operate 9
No. Page What it holds 2.33 Airfield Now The state of the runways and taxiways right now, and what needs a person. 2.34 Runway History A runway drawn to scale with its layers and its history, and any past work order replayed in place. 2.35 Self-Inspection The daily airfield inspection the FAA requires, with each problem sent to the work order system. 2.36 Condition and NOTAMs Airfield conditions and the notices pilots receive, drafted here and filed by a person. 2.37 Airfield Lighting Which airfield lights are out, and the repair each one needs. 2.38 Wildlife and FOD Birds and debris on the airfield, and the reports the FAA asks for. 2.39 Construction Safety Work zones on the airfield and the safety plan for each. 2.40 ARFF and the Emergency Plan The airport fire and rescue service against the FAA's rules. 2.41 Storm Plan A storm or emergency plan run as work orders, with what the twin finds and what is escalated.
Prove 6
No. Page What it holds 2.52 Safety Management Hazards, their risk and what is being done about them. 2.53 Accountability and Records The records the airport must keep, and the ones it must protect. 2.54 Duties and Deadlines Every recurring duty, who owns it, when it is next due and the evidence held. 2.55 Role Dashboards Each team sees its own page; the executive page says it in plain words. 2.56 Workflows How a fault becomes a repair: who is told and who approves it, and where the work is recorded. 2.57 Shift Briefing A shift briefing that walks the screens and asks a person to confirm each action.
Set up 11
No. Page What it holds 2.58 Rules and Data Library Every body of rules and data the platform has loaded, and what each one drives. 2.59 Glossary Every airport term the screens use, with one line and its source. 2.60 Systems of Record Every system the twin reads, and proof that each one stays the record. 2.61 Intake Documents and data loaded, checked and verified by a person. 2.62 Open Standards The open standards the twin speaks, so the Authority is never locked in. 2.63 Security and Administration Who can see what, and a record of everything anyone does. 2.64 Implementation and Roadmap The plan from award to go-live, and what comes after. 2.65 Environments and Operations Where the service would run, how it would be watched and kept safe, and how staff learn it. A target, not deployed. 2.66 Support How staff get help, and how a problem found in use becomes a reviewed fix. 2.67 Platform Family The sister products this one is built beside, and what each actually holds. 2.68 RFP Compliance Every requirement of the RFP, and where the work stands on each.
Reference 2
No. Page What it holds 2.69 Glossary terms 333 terms the screens use, each with a citation and a confidence word. 2.70 Narration clips 403 recorded narration lines the screens and the References entries play.