AirfieldpathOrlando Sanford International

2.68 · Proof of concept · Set up

RFP Compliance Real

Every requirement of the RFP, and where the work stands on each.

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

Screen · Proof of concept · Set up

RFP Compliance

Every requirement of the RFP, and where the work stands on each.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
met, partly met, target
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

RFP Compliance, a capture of the screen
Capture of the screen: RFP Compliance. Dark and light modes.

Narration line

It lets you count every requirement of the RFP and its attachments by status and by capability class, from the matrix.

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

Group
Set up
Status as the app labels it
Real
Basis
The screen runs. Read from docs/rfp/requirements-matrix.md at build (poc/build/assemble.py).
What the screen must do (3)
  • Count every requirement of the RFP and its attachments by status and by capability class, from the matrix (REQ-FUNC-118, REQ-SFB-002)
  • Show every placeholder and where it waits in the kit (REQ-FUNC-118)
  • Show the key dates of the solicitation (REQ-FUNC-119, REQ-SFB-051)
Requirements matrix rows that name this screen (6)
RowRFP sectionRequirementStatus
M-033RFP 3, final paragraphBase the solution on Attachment C; provide software, licences, configuration, integration, documentation, training, supportmet
M-048RFP 8.5; A 11Interviews and demonstrations 2027-01-11 and 12 for shortlisted firms; key personnel attendpartly met
M-049RFP 9Evaluation weights 15, 25, 20, 15, 10, 15 with page limitsmet
M-063B ii; B IIIIdentify which capabilities are standard, configured, integrated third-party, custom or conceptual; justify custom workmet
M-081A 7Submit through the portal by the deadlinetarget
M-103C 4.2Requirements validation without an extensive studytarget
Requirement identifiers (2)

REQ-SFB-002, REQ-SFB-051