AirfieldpathOrlando Sanford International

2.64 · Proof of concept · Set up

Implementation and Roadmap Real

The plan from award to go-live, and what comes after.

Picture: Headless capture of poc/index.html?v=roadmap&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.

Screen · Proof of concept · Set up

Implementation and Roadmap

The plan from award to go-live, and what comes after.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
partly met, target, met
Airport layer
Screens: the POC story and the spines
Airport area
not linked
System
not linked
Sensor type
not linked
SheetA-10

Open the screen · 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

Open this screen in the proof of concept

Implementation and Roadmap, a capture of the screen
Capture of the screen: Implementation and Roadmap. Dark and light modes.

Narration line

It shows StellarView's own plan for Sanford: twelve phases and a hundred work units, phase one of the project from award to the end of June 2027.

Source: poc/bearings/roadmap.json, beat "What it shows"

Group
Set up
Status as the app labels it
Real
Basis
The screen runs. The E3 plan exported from StellarView (staging/e3-sanford-implementation/stellarview-plan.json).
What the screen must do (5)
  • Show the proposed phases from kickoff to go-live, with the Implementation Plan to approve (REQ-SFB-001, REQ-SFB-003, REQ-SFB-005)
  • Show the Authority's participation and the data support offered (REQ-SFB-004, REQ-SFB-055)
  • Show training, documentation and the process repository (REQ-SFB-047, REQ-SFB-049, REQ-SFB-050)
  • Show acceptance, transition, support and ongoing services (REQ-SFB-052, REQ-SFB-053, REQ-SFB-054)
  • Show the future roadmap and how it expands by configuration (REQ-SFB-056, REQ-SFB-057, REQ-SFB-026)
Requirements matrix rows that name this screen (34)
RowRFP sectionRequirementStatus
M-005RFP 1.2A foundation for a long-term capability that evolvespartly met
M-012RFP 3, objective 6A sustainable platform that expands through integrations and use casestarget
M-014RFP 3, objective 8A formal process repository for post-project operation and maintenancetarget
M-022RFP 3, planningProject initiation; validate priorities; implementation approach and scheduletarget
M-027RFP 3, use casesUse cases for asset performance, maintenance optimization, status visibility, decision supportpartly met
M-029RFP 3, trainingFormal O&M processes, training and knowledge transfertarget
M-030RFP 3, documentationImplementation, configuration, integration and user documentationtarget
M-031RFP 3, ongoingOngoing professional services for enhancementstarget
M-037RFP 6.2Identify material assumptions, exclusions, constraints, dependencies, third-party requirements, risks and Authority resourcesmet
M-044RFP 6.12, 6.16Non-exclusive; no guaranteed work; priorities may changemet
M-045RFP 6.15No work before contract and written authorizationmet
M-064B iiiRecommend initial scope, priorities, systems, assets, integrations, use cases and spatial capabilitiespartly met
M-066B iiiPhases, schedule, milestones, sequencing, testing and acceptance, deployment, transitiontarget
M-067B iii; C 4.5Approach, staffing, effort and Authority participation for data collection and consolidation; data readiness riskstarget
M-068B iiiAuthority resources, third parties, assumptions, exclusions, constraints, dependencies, risks, mitigationspartly met
M-069B iiiFuture roadmap for expansionpartly met
M-071B v; RFP 10.4.5Training for administrators and user groupspartly met
M-072B vDocumentation and knowledge transfer for routine administration, users and dashboardstarget
M-077B viData support labour categories, rates and hours; optional services priced separatelytarget
M-083C 1.1An ecosystem that grows with integrations, enhanced analytics including intelligent visual analytics, and use casestarget
M-084C 1.2Work collaboratively; initial and ongoing professional servicestarget
M-085C 1.3Phased implementation focused on performance monitoring, preventive, corrective and predictive maintenance, awareness and decision supportpartly met
M-086C 1.3Five initial asset classes; sequence refined at initiationpartly met
M-102C 4.1Project initiation activitiestarget
M-103C 4.2Requirements validation without an extensive studytarget
M-106C 4.5Identify, configure, test and implement interfaces; data support on request with job descriptions and ratestarget
M-112C 4.10Initial use cases (fifteen listed)partly met
M-113C 4.11Training and knowledge transfer for each grouptarget
M-129C 5.10Expansion to more systems, facilities, terminals, assets, dashboards, workflows, analytics, use cases, emerging technologiestarget
M-136C 6.7Additional systems may be recommended: VMS, security, fire alarm, electrical, utility, passenger and flight information, energytarget
M-139C 7.1Deliverables: Implementation Plan, configured platform, object models, dashboards, workflows, reports, rules, integrations, security, user acceptance supporttarget
M-140C 7.2Concise documentation (configuration, integration, procedures, guidance, architecture, interfaces, training)target
M-141C 7.3Training for administrators, engineering, facilities, maintenance, operations, IT, executivestarget
M-142C 7.4Ongoing enhancement and sustainment services (dashboards, workflows, integrations, use cases, AI, performance, UI, configuration, spatial, support, knowledge transfer, roadmap planning)target
Requirement identifiers (14)

REQ-SFB-001, REQ-SFB-003, REQ-SFB-004, REQ-SFB-005, REQ-SFB-026, REQ-SFB-047, REQ-SFB-049, REQ-SFB-050, REQ-SFB-052, REQ-SFB-053, REQ-SFB-054, REQ-SFB-055, REQ-SFB-056, REQ-SFB-057