Workflow

Flow 42 — Recurring maintenance programmes and usage due work

Version a calendar, usage or whichever-first maintenance programme for one managed serialized instance, independently approve it, retain monotonic readings and deliberately generate due work into the existing controlled maintenance lifecycle.

Overview

Inventory meaning

Programme versions, usage readings and due evaluation create no stock and never move an identity. Only the existing maintenance start blocks the exact unrestricted serial; only its independent passing release returns that same identity to unrestricted stock.

Responsible roles

Stores Supervisor programme/meter author → different Stores Supervisor or Quality Inspector approver → Stores Officer usage recorder → Stores Supervisor due-work generator → different Stores Officer executor → separate Quality/Stores release authority → Auditor

Process

1
Register meter
Bind an hours or cycles identity to one managed instance and accountable site.
Definition only · stock unchanged
2
Version programme
Freeze trigger, baseline, interval, instructions and required task template.
Immutable DRAFT
3
Independent approval
A different release authority approves the exact SHA-256 version.
ACTIVE · no work created
4
Record usage
Append a dated, sourced, non-decreasing reading; history cannot be edited.
Evidence only
5
Generate due work
A named planner deliberately creates one due work order from the approved threshold snapshot.
PLANNED · stock unchanged
6
Execute and release
Use the existing exact-serial block, approved task checklist and independent release gates.
Blocked, then released only on PASS
READ ONLY

Role handoff

Detailed reference chapters

Recurring maintenance programmes and usage readings Assembly, recovery, maintenance, effectivity and approved alternates Shelf life and calibration roles

Detailed steps

1
Open Sustainment → Lifecycle operations and register an HOURS or CYCLES meter only when the programme needs usage evidence; assign the managed instance and accountable site.
2
Create programme v1 with CALENDAR, USAGE or WHICHEVER_FIRST trigger, anchored baseline, intervals, lead time, controlled reference, instructions and required task template. Submit it as its author.
3
As a different Stores Supervisor or Quality Inspector with release authority, approve or reject the unchanged version. A rejected version remains retained; an amendment is a new immutable version.
4
As Stores Officer, record a dated, sourced meter reading. Confirm lower, back-dated and duplicate non-idempotent mutations fail and prior readings cannot be edited or deleted.
5
When the active version is due or inside its approved calendar lead boundary, generate work as an explicit human action. Verify the generation snapshot pins programme/version, occurrence, date/usage thresholds, current usage and SHA-256 evidence.
6
Complete the generated work through the established different-planner/executor/releaser lifecycle. Use the approved programme task names exactly; calibration-controlled work still requires a valid same-instance certificate.

Field-by-field practice data

Use a disposable training tenant

Approve one whichever-first training maintenance programme, record attributable hours, generate its due work and preserve the existing independent execution/release boundary. The page shows sample set A; the workbook includes independent A, B and C values.

Download all workflow samples (.xlsx)

Field names match the current application labels. Select existing approved records where shown, leave optional values blank unless they genuinely apply, and never copy fictitious TRAIN values into live work.

Stores Supervisor

Register the usage identity

Open /catalogue-lifecycle

Select one existing non-retired managed instance and register its accountable training hours meter.

Exact field name	Requirement	Sample value A	How to use it
Managed instance	Select existing	`TRAIN-A-ASSET-001`	Select an existing serialized tool or asset.
Accountable site	Select existing	`TRAIN-A-SITE`	Use an assigned site.
Meter code	Required	`TRAIN-A-HOURS-01`	Use a stable fictitious meter identity.
Unit	Required	`HOURS`	Use HOURS or CYCLES.
Governance notes	Required	`Training A observed operating-hours evidence.`	State the trusted source boundary.

Expected result: A stable meter exists for the exact instance/site; no stock, custody or machine state changes.

Stores Supervisor

Create and submit programme v1

Open /catalogue-lifecycle

Create an immutable whichever-first definition and submit it for independent approval.

Exact field name	Requirement	Sample value A	How to use it
Title	Required	`Training A preventive service`	Describe the maintenance scope.
Trigger	Required	`WHICHEVER_FIRST`	Calendar or usage reaching its boundary makes work ready.
Calendar interval days	Required	`365`	Anchor to the approved baseline.
Usage interval	Required	`250.000000`	Use the meter unit.
Usage baseline	Required	`0.000000`	Use observed starting evidence.
Controlled reference	Required	`TRAIN-A-MRO-CARD-001`	Use the approved instruction reference.
Required task	Required	`Inspect and service exact asset`	The completion checklist must retain this exact name.

Expected result: The exact trigger, baselines, intervals, instructions and required task are SHA-256 checksummed; no work exists.

Different Stores Supervisor / Quality Inspector

Approve independently

Open /catalogue-lifecycle

Review and approve the unchanged submitted version.

Exact field name	Requirement	Sample value A	How to use it
Decision	Required	`APPROVE`	Use a different named release authority.
Attributable note	Required	`Training A intervals and task authority independently verified.`	Explain the decision.

Expected result: The programme becomes ACTIVE; self-approval is rejected and no work or stock change occurs.

Stores Officer

Record observed usage

Open /catalogue-lifecycle

Append the current sourced reading without estimating or overwriting prior evidence.

Exact field name	Requirement	Sample value A	How to use it
Reading	Required	`250.000000`	Enter the observed cumulative value.
Reading date	Required	`2026-09-02`	Do not future-date or back-date past the retained latest reading.
Source reference	Required	`TRAIN-A-LOGBOOK-250H`	Identify the controlled observation source.
Reading notes	Required	`Training A cumulative hours observed and transcribed by named operator.`	Do not claim automatic machine capture.

Expected result: The sequence advances to 1 and due status is deterministic; lower/back-dated values fail.

Stores Supervisor → different Stores Officer → separate releaser

Generate and execute due work

Open /catalogue-lifecycle

Generate occurrence 1 deliberately, then complete it through the existing exact-serial block and independent release workflow.

Exact field name	Requirement	Sample value A	How to use it
Generation note	Required	`Training A 250-hour boundary reviewed; create controlled work.`	A scheduler does not perform this action.
Controlled reference	Required	`TRAIN-A-MRO-AUTH-001`	Use the accountable work authorization.
Completion reference	Required	`TRAIN-A-MRO-COMPLETE-001`	Retain the exact maintenance result.
Maintenance result	Required	`PASS`	Use the programme task name exactly.
Attributable note	Required	`Training A task evidence supports release of the exact serial.`	A planner or executor cannot release their own work.

Expected result: One generation snapshot and work order retain the approved programme/version and thresholds; only existing start/release movements affect stock.

End state

One serialized instance has independently approved recurring maintenance authority, attributable append-only usage and deterministic due-work evidence while stock, custody, serviceability and release remain governed only by the existing maintenance lifecycle.