AirfieldpathOrlando Sanford International

2.15 · Proof of concept · Maintenance

Asset Record Real

One asset's full record: where it sits, what it is, its readings, its schedule and its history.

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

Screen · Proof of concept · Maintenance

Asset Record

One asset's full record: where it sits, what it is, its readings, its schedule and its history.

  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

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 Record, a capture of the screen
Capture of the screen: Asset Record. Dark and light modes.

Narration line

It shows the asset hierarchy from site to component.

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

Group
Maintenance
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 (4)
  • Show the asset hierarchy from site to component (REQ-SFB-059)
  • Show nameplate, status, criticality and open work orders (REQ-SFB-059)
  • Show meters, the PM schedule, maintenance history and documents, from the systems that hold them (REQ-SFB-059, REQ-SFB-007)
  • Write failure modes in the ISO 14224 style, mapped to the Authority's codes (REQ-SFB-059)
Requirements matrix rows that name this screen (9)
RowRFP sectionRequirementStatus
M-008RFP 3, objective 2Visibility into assets, condition, status, maintenance and lifecyclepartly met
M-015RFP 3, initial scopeAsset management optimization as the first focuspartly met
M-023RFP 3, configurationConfigure asset models, dashboards, workflows, reports, notifications, security and user interfacespartly met
M-088C 2.2Visibility into utilization, condition, maintenance, performance, inspections, lifecyclepartly met
M-104C 4.3Configure object models, hierarchy, spatial, dashboards, rules, workflows, UI, notifications, reports, administration, securitypartly met
M-114C 5.1Enterprise asset visualization, spatial asset management, dashboards, roles, workflows, analytics, reports, notifications, integration, expansionpartly met
M-118C 5.3Asset identification, location, attributes, relationships, status, condition, history, inspections, maintenance history, trends, lifecyclepartly met
M-119C 5.3; C 5.4Asset records, work orders, PM calendar, backlog, trends, alarm logs and KPIs in the shape maintenance staff knowpartly met
M-131C 6.2CMMS/EAM information to present (records, hierarchies, locations, requests, orders, PM, corrective, inspections, history, condition, availability, documents)partly met
Requirement identifiers (2)

REQ-SFB-007, REQ-SFB-059