Maintenance Work Execution Manager (MWEM)

Turn a maintenance need into safe, resourced, executed work — from the site and asset, through the work requirement and the plannable work package, its labour / material / tool / access readiness, the work order (local or external-ERP authority), to execution, verification and the formal return to service.

Its central question:

For each work package, is it ready to execute — are the people, parts, tools and access all confirmed — under whose authority does the order run, and once done, has the work been verified and the asset formally returned to service?

mwem is a demonstration prototype and a member of the Work & Supply reference network: it owns the work execution & readiness slice and shares stable canonical_ref identifiers with sibling apps (amia, msam, psam, scrm, cwia, psba, soim) so a package, asset or material links across apps. All data is fictional.

The work-execution spine

SiteRef / AssetRef → WorkRequirement → WorkPackage → (Labour / Material / Tool / Access requirements) → WorkOrder → ExecutionRecord → VerificationRecord → ReturnToService, with ExternalRecordLink carrying the cross-app integration (events go out through the integration layer's own outbox).

The documents

Page What's in it
00 — Overview What the app is, the domain, the 14 models by area, the demo scenario
01 — Quick Reference Menu map, every model, status vocabularies, canonical_ref conventions, how to run/seed/regenerate
02 — System Diagram The work-execution data model as a diagram (+ interactive viewer) and the cross-app golden thread

Status

Built: all 14 models render as an AI-Safe CRUD register, seeded with one coherent work-execution scenario — a package blocked on a cross-app parts shortage (P-101 bearing) and a package taken cleanly through to return to service (C-401 coupling).

Prototype system; draft. All sites, assets, requirements, packages, orders and records in the demo data are fictional; values demonstrate structure only and are not real maintenance records.