00 — Overview

Demonstration prototype. SCRM is a member of the Work & Supply reference network — a fictional multi-app integration where an orchestrator routes events between sibling apps (amia asset master, mwem work execution, msam materials, psam procurement, and this app for shutdown/campaign readiness, plus cwia/psba/soim). Every campaign, scope item, work package, contractor and material in the demo data is fictional and illustrates the data model and the cross-app "golden thread" only.

What SCRM is

The Shutdown & Campaign Readiness Manager turns the run-up to a shutdown, outage or turnaround into a structured, evidence-backed readiness register. A work package is not "ready" because a planner says so — it is ready when its scope is frozen, its dependencies are satisfied, and every readiness requirement (material, labour, contractor, permit, isolation, document, tool) is met. SCRM holds each of those links so a campaign's readiness state is always demonstrable, and rolls them up into point-in-time readiness snapshots.

The domain

Major maintenance events are won or lost before they start. The hard parts are scope discipline (what is in, frozen, and why it changed), readiness (is every prerequisite actually in place for each package), and integration (the material, work package, supplier and permit a package needs usually live in other systems). SCRM models all three, and links out to sibling apps by stable canonical_ref identifiers rather than owning their data.

The 12 models by area

Reference Data (1) - SiteRef — the site/facility a campaign runs at; carries the shared site canonical_ref.

Campaign & Scope (3) - Campaign — the central record: a shutdown / outage / turnaround / project window, with planned dates, a scope-freeze date and a lifecycle status. - ScopeItem — a piece of work brought into the campaign, sourced from a work requirement, external work package, project, inspection or entered manually; carries priority (MUST_DO / SHOULD_DO / OPPORTUNITY) and scope status. - ScopeChange — a requested change to scope (add / defer / remove), with reason, impact and a decision.

Packages & Readiness (3) - CampaignWorkPackage — an executable package delivering a scope item; carries a readiness state and an execution status, and may reference an external work package. - Dependency — an ordering / resource / access / material constraint between two work packages (predecessor → successor), with type, lag and status. - ReadinessRequirement — one prerequisite for a work package (material, labour, contractor, tool, access, permit, isolation, document, engineering, logistics), with a required-by date and a status; may reference an external record.

Mobilisation & Milestones (3) - ContractorMobilisation — a contractor being mobilised to the campaign, with personnel count, date, a supplier reference and a readiness status. - CampaignMilestone — a schedule checkpoint (scope freeze, material freeze, mobilisation, shutdown start, mechanical complete, commissioning start, return to service, closeout) with planned / forecast / actual dates. - ReadinessSnapshot — a point-in-time roll-up of campaign readiness (total / ready / blocked packages, open materials / procurement / contractors) with an overall state and an explanation.

Integration (2) - ExternalRecordLink — a link from a local record to an authoritative record in another system, with an authority mode (LOCAL / SHARED / EXTERNAL_ERP) and sync metadata.

The demo scenario

The SD-2027-01 demonstration shutdown at the Demonstration Facility (with a second, frozen North-plant compressor OUT-2026-11 outage for contrast). Scope items are drawn from mwem work packages (workpkg:wp-1001…wp-1004). The golden thread runs through WP-1001, a MUST_DO scope item to replace the P-101 pump bearing:

  • Its CampaignWorkPackage (CWP-P101) is only PARTIAL ready.
  • Because its ReadinessRequirement for bearing BRG-6208 (material:brg-6208) is NOT_READY — that bearing is short in msam (materials) and on order in psam (procurement).
  • So the campaign's ReadinessSnapshot is AT_RISK: WP-1001 blocked on bearing delivery, E-301 contractor not yet confirmed.

29 rows across the 10 operational models (the two Integration models are unseeded) — enough to show the scope → package → readiness spine in both a "ready" and an "at-risk" state, plus a pending scope change and two contractor mobilisations.