00 — Overview

Demonstration prototype. mwem is a reference application and a member of the Work & Supply reference network (networks/work_supply_00/system.manifest.yaml) — a demonstration multi-app integration in which an orchestrator routes events between sibling apps (amia asset master, mwem work execution, msam materials, psam procurement, scrm shutdown/campaign, plus cwia, psba, soim). It holds no real maintenance data — every site, asset, work package and order in the demo is fictional and illustrates the data model and workflow only.

What MWEM is

The Maintenance Work Execution Manager owns the work execution & readiness slice of the maintenance lifecycle: turning a maintenance requirement into a planned work package, proving that package is ready (labour, materials, tools and access all in place), issuing a work order under either local or external-ERP authority, then capturing execution, verification and the formal return to service.

A work package is not "ready" because someone says so — it is ready when every labour, material, tool and access requirement it depends on is confirmed. mwem holds each of those links so the readiness_state of a package is always demonstrable, and a work order should not be released while a required material is still SHORT.

The domain

Maintenance work arrives from many sources — defects, inspections, condition monitoring, breakdowns, planned strategy — and has to be resourced and made safe before it can be executed. The hard parts are readiness (do we actually have the people, parts, tools and permits?), authority (is this order run locally or is an external ERP the system of record?), and integration (the parts shortage that blocks a package here becomes a procurement problem in a sibling app). mwem models all three, and shares stable canonical_ref identifiers with the network so a package, asset or material links across apps.

The 14 models by area

Reference Data (2) - SiteRef — a site/facility the work belongs to (mirrors the network asset master). - AssetRef — an asset the work is performed on, with class and criticality.

Work (3) - WorkRequirement — the raw need for work (defect, inspection, condition, breakdown, planned…), triaged and approved. - WorkPackage — the plannable unit of work; carries planning status, execution window and readiness state. The hub. - WorkOrder — the authority to execute a package, run LOCAL or against an EXTERNAL_ERP, with operational status and cost.

Package Planning (4) - LabourRequirement — trade/skill, headcount and hours a package needs, and whether confirmed. - MaterialRequirement — a material a package needs (by shared material:* ref), with fulfilment status incl. SHORT. - ToolRequirement — a tool/kit a package needs, and whether confirmed. - AccessRequirement — access, isolation, permit, scaffold, crane or area release a package needs (may reference an external permit).

Execution & Verification (3) - ExecutionRecord — what was actually done on a work order: timings, completion summary, failure/repair codes. - VerificationRecord — a function test / inspection / quality / independent / operational check, with a PASS/FAIL/CONDITIONAL outcome. - ReturnToService — the formal decision (approved / rejected / conditional) to hand the asset back, with conditions and acceptor.

Integration (2) - ExternalRecordLink — a mapping from a local record to its counterpart in an external system (e.g. a simsap MaintenanceOrder), with authority mode and last-sync.

The demo scenario

A P-101 process-pump bearing shortage golden thread across the Work & Supply network, plus supporting packages at other readiness states:

  • WP-1001 — Inspect and replace P-101 pump bearing. Requirement WR-1001 (rising bearing vibration, condition-based) is packaged. Labour, tools and isolation are lined up, but bearing BRG-6208 is SHORT — so the package is BLOCKED / readiness PARTIAL. That shortage is the thread that flows out of mwem: it becomes a MaterialDemand in msam, which raises a PurchaseRequirement in psam; the same package appears as scope in a scrm shutdown campaign. WO-1001 exists but sits at CREATED.
  • WP-1004 — C-401 compressor coupling repair. A URGENT breakdown carried all the way through: WO-1004 executed, function-test PASS, return to service APPROVED, and an ExternalRecordLink ties WO-1004 to a simsap MaintenanceOrder (EXTERNAL_ERP).
  • WP-1002 / WP-1003 — a READY separator entry inspection and a PLANNING heat- exchanger bundle job, to show packages at other readiness states.

Enough rows to show the whole spine at once: a package blocked on a cross-app parts shortage and a package taken cleanly through to return to service.