COMPANION
Vision map
Every line of Johan’s vision document, mapped to the app. Click a built feature to jump straight to it. Click a planned one to read how we’d build it.
79%
VISION REALISED
39
BUILT
4
IN PROGRESS
9
PLANNED
Purpose of the App
VISION · PURPOSE OF THE APPCore Concept
VISION · CORE CONCEPTMain Functional Requirements
VISION · MAIN FUNCTIONAL REQUIREMENTS1 · Visual Asset Overview — dashboard per location
open2 · Object-Based Maintenance Records — per-object history & profile
open3 · Intelligent Maintenance Monitoring — intervals, expiry, compliance
open4 · User Reporting — defects, damage, safety concerns
open5 · User Roles & Workflow Chain — Object → Operator → Planner → Third-party
in progress6 · Service Ordering & Maintenance Coordination
openExample Use Case — Refuel4You
VISION · EXAMPLE USE CASE – REFUEL4YOUOperator Daily Workflow
VISION · OPERATOR DAILY WORKFLOWThird-Party Maintenance Workflow
VISION · THIRD-PARTY MAINTENANCE WORKFLOWSuggested Future Features
VISION · SUGGESTED FUTURE FEATURESMain Design Priorities
VISION · MAIN DESIGN PRIORITIESOpen questions for Johan
- 01“Need for flagging” in THM Daily — what is flagging concretely?
- 02“Fboone” — what system is this? Do we integrate or just log a check?
- 03JIG-specific checkpoints for Refuel4You — can we get the real JIG lists?
- 04Third-party accounts — created by planner, or via invitation link?
- 05Sites — only Bromma initially, or are there others to seed?
- 06“Other operational equipment” — concrete examples?
- 07Photos on defects — mandatory or optional, and from which severity?
Questions & notes
STORED LOCALLY IN THIS BROWSER · MOVES TO THE DATABASE WHEN NEON LANDS
niclaslof/apron
Private repository · main