00 — Overview

R9 reference application. Built from the v0.14 Work & Supply reference pack to prove that two DSLCore applications and the orchestrator can run a business process together (reference flows R1 and R2). The demo data is fictional.

What Work Management is

Work Management holds the execution record of maintenance work. A work order says what must be done to an asset and why; tasks break it down; assignments and time entries say who did it and for how long. Before work can start it may need materials (from Inventory, or bought through Purchasing), tools, safety documents and an isolation. When it is finished the app keeps the proof: what was removed, what evidence was captured, which tests passed, when the asset went back into service, who verified the work and how it was closed out.

The domain

Maintenance work fails in predictable places: it starts without the parts, it cannot start because something outside the crew's control is missing, or it is "done" without evidence anyone can check later. Work Management makes each of those explicit — material requirements and dependencies hold the order (awaiting_parts, awaiting_isolation), and closure is a chain of evidence, test, return to service and verification rather than a status change.

The 21 models by area

Work Orders (6) - WorkOrder — the central record: asset, type, priority, status, plan and actuals. - WorkTask — an ordered step (action, inspection, measurement, test, sign-off). - WorkAssignment — a person or contractor organisation on the work, with their role. - WorkTimeEntry — labour time against the order or a task. - WorkStatusHistory — every status change, with reason and (for network changes) the message that caused it. - WorkDependency — what the order is waiting for: material, access, isolation, outage, other work, an external constraint.

Materials & Tools (2) - WorkMaterialRequirement — a part the work needs: catalogue item, quantity, required-by date, and the reservation / purchase requirement that will satisfy it. - ToolRequirement — special tools, lifting gear and test equipment, with certification.

Safety & Isolation (2) - SafetyDocumentReference — SWMS / JSEA / permits the crew must accept. - IsolationReference — the isolation the work depends on, from request to restoration.

Completion & Evidence (7) - RemovedComponent — what came off, its condition and disposition (repair, warranty, scrap), and the unit's main SMU at removal. - InstalledComponent — what went on, where (SMCS code + modifier), when, and the unit's main SMU. - Evidence — photos, documents and test sheets captured during the work. - TestResult — functional tests and their result. - ReturnToService — the checks before the asset goes back into operation. - Verification — independent acceptance of the work. - Closeout — failure/cause/repair codes, downtime and first-time-fix.

Templates (3) - MaintenanceTemplate, MaintenanceTemplateTask, MaintenanceTemplateTool — routine work defined once and copied into work orders. A template is keyed by maintenance group + SMCS, found by other applications with work.search_maintenance_templates, and may be flagged oil_change. The 250 h, 500 h and 1000 h services are cumulative tiers (each includes the tasks of the one below). A sample is a task inside the template.

People & Organisations (2) - Organisation — operator, contractor, service provider. - Person — planners, supervisors, technicians.

The demo scenario

Three work orders tell one story with the Inventory app (shared network ids):

New requirements created while the network runs (see networks/work_supply/RUNBOOK.md) repeat R1 / R2 live: Inventory answers through the orchestrator within seconds and the requirement shows the reservation (RES-…) or the unavailability.