AirfieldpathOrlando Sanford International

Section 3

The RFP and the plan

The requirements matrix, the RFP's own words with their lines, the plan of phases and work units, the Authority dependencies and the RFP documents.

25 pages in this section. Select a row for the full text, or the matrix for all 147 requirements.

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

The RFP 2

No.PageWhat it holds
3.1Requirements matrixAll 147 requirements of RFP 2027-006 and its Attachments A, B and C, section by section, with the screen that shows each.
3.2The RFP documentsThe four documents of RFP 2027-006 as the Authority published them.

RFP statements 8

No.PageWhat it holds
3.3RS-01: Attachment C, 1.3 Initial Implementation StrategyThe Authority recognizes that a successful Airport Digital Twin is developed incrementally through phased implementation rather than a single comprehensive deployment.
3.4RS-02: Attachment C, 1.1 Overview (repeated in 3.5 Existing Systems Remain Systems of Record)Existing systems will continue to perform their respective operational functions and remain the authoritative systems of record within their functional domains.
3.5RS-03: Attachment C, 2.7 Establish a Sustainable Enterprise PlatformImplement a commercially supported Digital Twin Platform that can continue evolving ... without extensive custom software development.
3.6RS-04: Attachment C, 2.7 Establish a Sustainable Enterprise Platform (the sentence beginning "Implement a Digital Twin Platform that remains open, vendor-agnostic")capable of evolving without proprietary customization, enabling future enterprise integrations and compatibility with emerging technologies
3.7RS-05: Attachment C, 3.4 Configuration Before Customizationthe Platform should be configured using standard graphical configuration tools rather than custom software development whenever practical.
3.8RS-06: Attachment C, 2.1 Establish an Airport Digital Twin Platforma common operational environment for visualizing ... information from selected airport systems and available spatial information
3.9RS-07: Attachment C, 4.11 Training and Knowledge TransferThe Solution Provider shall provide training and knowledge transfer services necessary to support successful adoption of the Airport Digital Twin Platform.
3.10RS-08: Attachment C, 5.9 Security and User AdministrationThe Platform shall provide role-based security appropriate for Airport operations.

The plan 3

No.PageWhat it holds
3.11The implementation plan12 phases and 100 work units, from the Authority's written authorization to go-live.
3.12Authority dependencies23 things the plan needs from the Authority, each with the date it is needed by and the RFP section it comes from.
3.13Requirement setsThe requirement sets the matrix and the plan draw on: E1 (177 identifiers), E2 (70 identifiers), E3 (141 identifiers).

Phases 12

No.PageWhat it holds
3.14Phase 1: Initiation and requirements validationPhase 1 starts only on the Authority's written authorization (RFP 6.15) and settles everything later phases build on: the kickoff, the systems inventory, the validated 70 E2...
3.15Phase 2: Environments, sign-in and the core platformP2 stands up the development, staging and production environments from one set of infrastructure-as-code templates, with production on a two-zone database and 35-day backups proven by...
3.16Phase 3: Integration proofConnects the Authority's systems to the twin and shows each one working end to end: Simplify i3 is read on a schedule and receives confirmed work requests, EcoStruxure is read through an...
3.17Phase 4: A few of each sensor type, end to endFits outbound-only edge gateways in the operational network's DMZ, then proves each of the five first asset classes (HVAC, boarding bridges, baggage, vertical transportation, airfield)...
3.18Phase 5: Spatial, dashboards, workflows, use cases and the backlogConfigures everything a person uses on the data read so far: spatial sources in plan and 3D with a GIS maturity assessment, role dashboards, maintenance workflows that hand work to...
3.19Phase 6: Training, documentation and knowledge transferPlans and delivers training to the seven Authority groups on the configured platform built in P5, and proves knowledge transfer by having Authority staff make routine administration and...
3.20Phase 7: Acceptance, go-live and the phase 1 close-outThis phase agrees the acceptance criteria with the Authority, runs user acceptance testing with the Authority's testers, and fixes each defect through the reviewed pipeline.
3.21Phase 8: Support and the next asset classes, rest of year 1It adds the next asset classes by configuration at the pace the Authority sets (DEP-22, needed by 2027-07-01), with no rebuild of phase 1, and offers data services by labour category.
3.22Phase 9: Year 2: every unit of the five classes, and the next systemsPhase 9 scales the phase 1 samples to every unit the Authority owns across HVAC, boarding bridges, baggage, vertical transportation and airfield, in the order the Authority sets.
3.23Phase 10: Year 3: the wider terminal systems and prediction across classesBrings in fire alarm, electrical, utility and energy management systems read-only through the registry, with licensed maintainers keeping control.
3.24Phase 11: Year 4: the gaps no maker sensor reaches, and more facilitiesIt surveys the assets that no maker data reaches and fills those gaps with commercial retrofit sensors first, with the Inflector offered as an option.
3.25Phase 12: Year 5: real-time data on all Airport facilitiesIt renews the roadmap with the Authority for the years after the fifth and keeps support, sustainment and professional services running to 2032-01-31.