AirfieldpathOrlando Sanford International

3.15 · The RFP and the plan · Phases

Phase 2: Environments, sign-in and the core platform

P2 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 alarm and restore drills.

No picture for this component.

Plan · The RFP and the plan · Phases

Phase 2: Environments, sign-in and the core platform

P2 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 alarm and...

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Plan
Status
not linked
Airport layer
not linked
Airport area
not linked
System
not linked
Sensor type
not linked

Open the detail

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

P2 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 alarm and restore drills. It connects sign-in to the Authority's identity provider with roles and audit logging, and hands over the repository, pipeline and runbooks so a capable team can carry on. It also configures the source and point registry, the supplier standard and the object model, so the P3 integrations have somewhere to land.

Dates
2027-02-15 to 2027-03-26
Requirements delivered
7
Work units
9
Needs
Needs P1
Work units (9)
UnitTitleDatesRFPNeeds
WU-2-1Infrastructure-as-code templates and development environment2027-02-15 to 2027-02-19B ii, C 5.10DEP-06
WU-2-2Repository, pipeline and test baseline2027-02-15 to 2027-03-19B v, C 7.2
WU-2-3Staging environment with alarm drill2027-02-22 to 2027-03-05B ii, B v, C 5.9DEP-06
WU-2-4Authority identity provider sign-in, roles and audit log2027-03-01 to 2027-03-12C 4.3, C 5.9DEP-05
WU-2-5Production environment with two-zone database and backups2027-03-08 to 2027-03-19B ii, C 5.10, C 5.9DEP-06, DEP-07
WU-2-6Production restore drill and record2027-06-21 to 2027-06-23B iii, C 7.1DEP-19
WU-2-7Object model and asset hierarchy2027-03-15 to 2027-03-26C 4.3, C 7.1DEP-04
WU-2-8Source and point registry with supplier standard2027-03-01 to 2027-03-19C 2.7, C 3.6, C 6.1DEP-04
WU-2-9Handover documentation and runbooks2027-02-15 to 2027-03-19B v, C 7.2
WU-2-1: Infrastructure-as-code templates and development environment

Author the shared infrastructure-as-code templates and deploy the development environment from them with a healthy deploy log (REQ-IMP-010).

Depends on
none
Authority dependencies
DEP-06
Traces to
REQ-SFB-069
Functional requirements
3
WU-2-2: Repository, pipeline and test baseline

Set up the repository structure, deployment pipeline and the tests the pipeline runs so every environment deploys through one controlled path (first part of REQ-IMP-014).

Depends on
none
Authority dependencies
none
Traces to
REQ-SFB-049, REQ-SFB-069
Functional requirements
3
WU-2-3: Staging environment with alarm drill

Deploy staging from the same templates and prove its alarms fire in a recorded drill (REQ-IMP-011).

Depends on
WU-2-1, WU-2-2
Authority dependencies
DEP-06
Traces to
REQ-SFB-069
Functional requirements
0
WU-2-4: Authority identity provider sign-in, roles and audit log

Connect sign-in to the Authority's identity provider with role mapping, administrative controls and an audit log, verified on development and staging (REQ-IMP-013).

Depends on
WU-2-1
Authority dependencies
DEP-05
Traces to
REQ-SFB-046
Functional requirements
4
WU-2-5: Production environment with two-zone database and backups

Deploy production from the same templates with a two-zone database and 35-day backups, behind the Authority's DMZ and network rules (REQ-IMP-012).

Depends on
WU-2-3
Authority dependencies
DEP-06, DEP-07
Traces to
REQ-SFB-069
Functional requirements
0
WU-2-6: Production restore drill and record

Run a restore from backup on production and file the restore record that P7 go-live drills build on.

Depends on
WU-2-5
Authority dependencies
DEP-19
Traces to
REQ-SFB-069
Functional requirements
0
WU-2-7: Object model and asset hierarchy

Configure the site, building, floor, space, system and asset hierarchy from the Simplify i3 hierarchy and spatial data so every read asset has one place (REQ-IMP-016).

Depends on
WU-2-3
Authority dependencies
DEP-04
Traces to
REQ-SFB-009, REQ-SFB-010
Functional requirements
0
WU-2-8: Source and point registry with supplier standard

Configure the source and point registry and publish the supplier standard with its conformance test so new points register and are approved without code (REQ-IMP-015).

Depends on
WU-2-7, WU-2-4
Authority dependencies
DEP-04
Traces to
REQ-SFB-011, REQ-SFB-041
Functional requirements
4
WU-2-9: Handover documentation and runbooks

Write the README, deployment and drill runbooks, and verify a person outside the project can clone and deploy staging from them (completion of REQ-IMP-014).

Depends on
WU-2-6, WU-2-8
Authority dependencies
none
Traces to
REQ-SFB-049, REQ-SFB-069
Functional requirements
4
Requirements delivered (7)
IdRequirementAcceptanceEvidence
REQ-IMP-010The development environment stood up from the templates in its own account and run through phase 1.the environment deploys from the templates and reports healthy.the deploy log.
REQ-IMP-011The staging environment stood up from the same templates and run through phase 1, with its alarms firing in a drill.the staging stack deploys and its alarms fire in a drill.the deploy log and the drill record.
REQ-IMP-012The production environment stood up from the same templates, with the database across two zones and 35-day backups, and run through phase 1.production deploys from the templates and a restore from backup succeeds.the deploy log and the restore record.
REQ-IMP-013Sign-in through the Authority's identity provider, with roles, administrative controls and audit logging.a user signs in through the Authority's identity provider and lands in the right role.the security configuration.
REQ-IMP-014The repository, the pipeline and the infrastructure as code handed over in a form a capable team can carry on without us: a README that starts it, the tests the pipeline runs, and the runbooks.a person outside the project clones it and deploys staging from the README.the clone-and-deploy record.
REQ-IMP-015The source and point registry configured, and the supplier standard published: the buses, the read-only rule, the asset ID rule, the licences a fitter must hold and the conformance test.a new system's points are registered and approved without code.the registry export and the published standard.
REQ-IMP-016The object model and asset hierarchy configured from the CMMS hierarchy and the spatial data: site, building, floor, space, system, asset.every terminal asset read so far sits in one place in the hierarchy.the object model export.