AirfieldpathOrlando Sanford International

3.14 · The RFP and the plan · Phases

Phase 1: Initiation and requirements validation

Phase 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 requirements, the asset-class priority order, the baselines, the live register and the grant reading.

No picture for this component.

Plan · The RFP and the plan · Phases

Phase 1: Initiation and requirements validation

Phase 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 requirements, the...

  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

Phase 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 requirements, the asset-class priority order, the baselines, the live register and the grant reading. It ends with the Project Implementation Plan approved by the Authority (DEP-20) by 2027-03-05. It builds no product code, so its units are project records, each with a named owner, date and written acceptance step.

Dates
2027-02-02 to 2027-03-05
Requirements delivered
9
Work units
8
Needs
Needs nothing earlier
Work units (8)
UnitTitleDatesRFPNeeds
WU-1-1Authorization gate and project kickoff2027-02-02 to 2027-02-12C 4.1, RFP 3, RFP 6.15DEP-01, DEP-02, DEP-03
WU-1-2Grant agreement reading and acceptance schedule2027-02-10 to 2027-02-26B vi, RFP 3DEP-21
WU-1-3Site walk and systems inventory with sensing register2027-02-15 to 2027-02-26C 4.1, C 6.1, C 6.9DEP-03, DEP-11
WU-1-4Validation of the 70 Sanford requirements2027-02-15 to 2027-02-26C 4.2DEP-02
WU-1-5Asset-class priority order2027-02-22 to 2027-02-26C 1.3, RFP 6.16DEP-02
WU-1-6Measure baselines from Authority records2027-02-22 to 2027-03-05C 2.3, C 3.1, RFP 3DEP-04
WU-1-7Risk and dependency register2027-02-10 to 2027-03-05B III, B iii, RFP 6.2DEP-02
WU-1-8Project Implementation Plan submission and approval2027-03-01 to 2027-03-05C 7.1, RFP 2.9DEP-20
WU-1-1: Authorization gate and project kickoff

Record the Authority's written authorization (REQ-IMP-001) and hold the kickoff covering every C 4.1 item with stakeholders named (REQ-IMP-002).

Depends on
none
Authority dependencies
DEP-01, DEP-02, DEP-03
Traces to
REQ-SFB-001
Functional requirements
4
WU-1-2: Grant agreement reading and acceptance schedule

Depends on
WU-1-1
Authority dependencies
DEP-21
Traces to
none
Functional requirements
3
WU-1-3: Site walk and systems inventory with sensing register

Inventory each C 6.9 system with owner, version, connectivity and interface, and record one decision (integrate, extend, retire or add) per existing sensing source (REQ-IMP-003).

Depends on
WU-1-1
Authority dependencies
DEP-03, DEP-11
Traces to
REQ-SFB-011
Functional requirements
4
WU-1-4: Validation of the 70 Sanford requirements

Confirm or change each of the 70 E2 requirements with the Authority and name the efficiency and workflow opportunities in a traced validation record (REQ-IMP-004).

Depends on
WU-1-1
Authority dependencies
DEP-02
Traces to
REQ-SFB-002
Functional requirements
3
WU-1-5: Asset-class priority order

Record the order of the five asset classes with who set it, in a form that lets later changes proceed without rework (REQ-IMP-005).

Depends on
WU-1-3, WU-1-4
Authority dependencies
DEP-02
Traces to
REQ-SFB-005
Functional requirements
4
WU-1-6: Measure baselines from Authority records

Record baseline values with source and date for availability, response and repair times, planned versus reactive work and work order aging, drawn from Simplify i3 and other Authority records (REQ-IMP-006).

Depends on
WU-1-5
Authority dependencies
DEP-04
Traces to
REQ-SFB-058
Functional requirements
4
WU-1-7: Risk and dependency register

Stand up the live register of assumptions, exclusions, constraints, dependencies, third-party needs, risks and Authority resource needs, each with an owner and date, and keep it current to the end of the phase (REQ-IMP-007).

Depends on
WU-1-3, WU-1-6
Authority dependencies
DEP-02
Traces to
REQ-SFB-004
Functional requirements
4
WU-1-8: Project Implementation Plan submission and approval

Compile and submit the Project Implementation Plan from the register, baselines and grant reading, and obtain the Authority's signed approval under DEP-20 by 2027-03-05 (REQ-IMP-009).

Depends on
WU-1-2, WU-1-6, WU-1-7
Authority dependencies
DEP-20
Traces to
REQ-SFB-003
Functional requirements
4
Requirements delivered (9)
IdRequirementAcceptanceEvidence
REQ-IMP-001Start on the Authority's written authorization: the contract executed and the authorization to proceed received before any service begins.the written authorization is on file before the first working day.the signed contract and the authorization letter.
REQ-IMP-002Project kickoff: objectives confirmed, stakeholders named, the existing systems and documentation reviewed, the implementation approach and schedule presented.the kickoff record covers each item of C 4.1.the kickoff pack and its minutes.
REQ-IMP-003Site walk and systems inventory: each system of C 6.9 with its owner, version, connectivity and interface, and each existing sensor or controller given one decision (integrate, extend, retire or add) with who decided and why.every C 6.9 system has a row, and every existing sensing source has its decision.the systems inventory and the sensing register.
REQ-IMP-004Requirements validation: the 70 Sanford requirements confirmed or changed with the Authority, without an extensive consulting study, and the efficiency and workflow opportunities named.a validated requirement list traced to E2.the validation record.
REQ-IMP-005Priorities and the order of the five asset classes set with the Authority, recorded so a later change needs no rework.the order is recorded with who set it.the priority record.
REQ-IMP-006Baselines for the measures recorded from the Authority's own records: equipment availability, response and repair times, planned against reactive work and work order aging.each measure has a baseline value, its source and its date.the baseline sheet.
REQ-IMP-007The register of assumptions, exclusions, constraints, dependencies, third-party needs, risks and Authority resource needs, each with an owner, kept current to the end.each entry has an owner and a date.the risk and dependency register.
REQ-IMP-008each deliverable names its written acceptance step.the deliverables and acceptance schedule.
REQ-IMP-009The Project Implementation Plan submitted and approved: approach, priorities, phases, schedule, milestones, integrations, responsibilities, testing and deployment.the Authority approves the plan.the signed plan.