AirfieldpathOrlando Sanford International

2.52 · Proof of concept · Prove

Safety Management Real

Hazards, their risk and what is being done about them.

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

Screen · Proof of concept · Prove

Safety Management

Hazards, their risk and what is being done about them.

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

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

Safety Management, a capture of the screen
Capture of the screen: Safety Management. Dark and light modes.

Narration line

It shows the hazards in the safety reporting system with their risk, place and state.

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

Group
Prove
Status as the app labels it
Real
Basis
The screen runs. Data: carefully crafted and curated test data for common use cases.
What the screen must do (5)
  • Show the hazards in the safety reporting system with their risk, place and state (REQ-FUNC-104)
  • Run a safety risk assessment with severity and likelihood and record the mitigation (REQ-FUNC-105)
  • Show safety assurance: the measures, audits and their trend (REQ-FUNC-106)
  • Show safety promotion: training and communication records (REQ-FUNC-107)
  • Show the SMS implementation plan's deadlines from the rule (REQ-FUNC-108)
Requirements matrix rows that name this screen (1)
RowRFP sectionRequirementStatus
M-147Beyond the RFPPart 139 records: self-inspection, condition reporting and NOTAM drafts, SMSpartly met