2.56 · Proof of concept · Prove
Workflows Real How a fault becomes a repair: who is told and who approves it, and where the work is recorded.
Picture: Headless capture of poc/index.html?v=workflows&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale. Clip: Capture of poc/index.html?v=workflows&m=light, 4 seconds of the screen as it runs, 10 frames a second. No sound.
Screen · Proof of concept · Prove
How a fault becomes a repair: who is told and who approves it, and where the work is recorded.
Sources Interchange Twin Screens Plan
Kind Screen
Status 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: Workflows. Dark and light modes.
Narration line Open work sits on a board by status, in the language of the work order system.
Source: poc/bearings/workflows.json, beat "The board"
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 (7) List each configurable workflow with its RFP section and how it runs (REQ-SFB-030) Hand work to Simplify i3 where it belongs (REQ-SFB-031) Notify by role and rule, with escalation (REQ-SFB-032) Draw each workflow as a swimlane flow: who does what, in order, with its gates Show the work order as the familiar form and open work on a board by status, in standard CMMS language Use ISO 14224 style problem, cause and remedy codes and the SMRP measures Map fields, statuses and codes to Simplify i3's once its interface is in hand, and say so until then
Requirements matrix rows that name this screen (11) Row RFP section Requirement Status M-003 RFP 1.1 Enhanced visualization, analytics, dashboards, workflows and decision support partly met M-011 RFP 3, objective 5 Configurable dashboards, spatial visualizations, workflows, analytics and reporting partly met M-023 RFP 3, configuration Configure asset models, dashboards, workflows, reports, notifications, security and user interfaces partly met M-062 B ii Capabilities for visualization, dashboards, workflows, reports, notifications, AI, security, administration, scalability partly met M-075 B v Long-term maintainability, cost-effective administration, configuration-based expansion target M-092 C 2.6 Timely information for decisions through dashboards, workflows, notifications, analytics partly met M-097 C 3.4 Configuration before customization target M-104 C 4.3 Configure object models, hierarchy, spatial, dashboards, rules, workflows, UI, notifications, reports, administration, security partly met M-111 C 4.9 Configurable workflows for PM, corrective, requests, coordination, inspections, assessments, outages, notifications, approvals, tasks, follow-up, monitoring partly met M-114 C 5.1 Enterprise asset visualization, spatial asset management, dashboards, roles, workflows, analytics, reports, notifications, integration, expansion partly met M-127 C 5.8 Workflow management with approvals and escalation partly met
Requirement identifiers (3) REQ-SFB-030, REQ-SFB-031, REQ-SFB-032
Previous Role DashboardsNext Shift Briefing