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
Every requirement of the RFP, and where the work stands on each.
- Sources
- Interchange
- Twin
- Screens
- 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
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
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)
| Row | RFP section | Requirement | Status |
|---|
| M-033 | RFP 3, final paragraph | Base the solution on Attachment C; provide software, licences, configuration, integration, documentation, training, support | met |
| M-048 | RFP 8.5; A 11 | Interviews and demonstrations 2027-01-11 and 12 for shortlisted firms; key personnel attend | partly met |
| M-049 | RFP 9 | Evaluation weights 15, 25, 20, 15, 10, 15 with page limits | met |
| M-063 | B ii; B III | Identify which capabilities are standard, configured, integrated third-party, custom or conceptual; justify custom work | met |
| M-081 | A 7 | Submit through the portal by the deadline | target |
| M-103 | C 4.2 | Requirements validation without an extensive study | target |
Requirement identifiers (2)