AirfieldpathOrlando Sanford International

2.46 · Proof of concept · Assets

Asset Registry Real

Every asset, its condition and the system that holds its record.

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

Screen · Proof of concept · Assets

Asset Registry

Every asset, its condition and the system that holds its record.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
not linked
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

Asset Registry, a capture of the screen
Capture of the screen: Asset Registry. Dark and light modes.

Narration line

It lists every asset with its class, its place, its condition and the system of record that owns it.

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

Group
Assets
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)
  • List every asset with its class, its place, its condition and the system of record that owns it (REQ-FUNC-054, REQ-DATA-004)
  • Show each asset's history: work orders, inspections, condition readings and documents (REQ-FUNC-055)
  • Say plainly when an asset has no owning system or its system has gone stale (REQ-FUNC-056)
  • Show assets by condition and by age against their planned life (REQ-FUNC-057)
  • Show identification, location, attributes, relationships, status, condition, history and lifecycle per asset (REQ-SFB-009, REQ-SFB-010)
Requirement identifiers (2)

REQ-SFB-009, REQ-SFB-010