Published

Maintenance

vr.wm-act-013 · wm-act-013-maintenance

Describe the continuing maintenance record for one identified physical asset or explicitly delimited maintainable system.

World Models Activities and processes ACT.MNT

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

7 bundles · 14 layers · 14 findings · 42 questions

Context and responsibility Defines whose record this is and the exact maintained boundary.

Asset and record identity

Keep a stable maintenance record ID distinct from the asset reference. Replacement or boundary changes require explicit continuity decisions, not silent reuse.

Bounded maintenance identity

Keep a stable maintenance record ID distinct from the asset reference. Replacement or boundary changes require explicit continuity decisions, not silent reuse.

Which master identifiers and system boundary distinguish this maintenance record from the asset and its replaceable components? identity
How are replacement, split or merged asset boundaries linked without rewriting earlier work history? relationship
Which asset class, operating context and maintenance profile qualify the meaning of this record? classification

Stewardship and authority

Separate record custody, asset rights, technical responsibility and contracted work. Time-bounded delegation must identify scope and evidence.

Effective responsibility assignment

Separate record custody, asset rights, technical responsibility and contracted work. Time-bounded delegation must identify scope and evidence.

Who is accountable for this maintenance record during each custody period, and where are asset rights recorded? ownership
Which delegation permits a maintainer to record work, approve changes or endorse a release for the specific asset scope? authority
Which recipient may see technician, defect or commercial details, and what independent duties constrain an owner grant? access

Condition and defects Keeps observations separate from interpretation and repair conclusions.

Condition observations

An observation is an attributed, time-specific assessment with method and limitations. A dashboard latest value must not suppress conflicting or stale evidence.

Qualified assessment evidence

An observation is an attributed, time-specific assessment with method and limitations. A dashboard latest value must not suppress conflicting or stale evidence.

What was observed on which component, using which scale, unit, method and instrument qualification? measurement
When was the condition observed and recorded, and what uncertainty or operating context limits comparison? temporal
How are missing, stale or contradictory observations represented without treating absence as acceptable condition? quality

Defect interpretation

A reported anomaly, confirmed defect, failure mode and causal hypothesis remain distinguishable. Closure needs its own evidence and can be reopened.

Defect and failure attribution

A reported anomaly, confirmed defect, failure mode and causal hypothesis remain distinguishable. Closure needs its own evidence and can be reopened.

Which defect or anomaly is open on the maintained scope, and how was its severity qualified? state
What evidence supports the assigned failure mode or suspected cause, including alternative explanations? provenance
What evidence and authorized review support closure or reopening of a defect after an intervention? lifecycle

Applied programme Records why work is due and preserves approved changes.

Strategy applicability

The applied programme links a reviewed strategy to asset context. A chosen approach is not a guarantee of reliability and may vary by failure mode.

Asset-specific strategy decision

The applied programme links a reviewed strategy to asset context. A chosen approach is not a guarantee of reliability and may vary by failure mode.

Which strategy applies to each maintained function, and what risk or performance rationale supports it? decision
Which versioned instructions, obligations and procedure definitions constrain the selected maintenance strategy? requirement
How are strategy changes or deliberate deferrals justified, bounded and reviewed without hiding unresolved risk? exception

Intervals and triggers

Keep calendar, usage and condition triggers explicit. Unknown meter continuity or unavailable condition evidence yields an indeterminate result, not a safe extension.

Qualified due-work determination

Keep calendar, usage and condition triggers explicit. Unknown meter continuity or unavailable condition evidence yields an indeterminate result, not a safe extension.

Which calendar, elapsed-use or condition rule determines the next due work and its observation basis? temporal
How are meter resets, missing readings, time uncertainty and trigger conflicts handled before marking work due or overdue? validation
Who approved the planned work window or interval revision, and how are blocked or overdue tasks escalated? process

Work control Separates requested work, authority and readiness to undertake it.

Work request and order

Requests, approval and execution evidence are separate. An emergency or retrospective record is possible without inventing prior approval or a mandatory programme link.

Authorized scope and progress

Requests, approval and execution evidence are separate. An emergency or retrospective record is possible without inventing prior approval or a mandatory programme link.

Which request and work-order identifiers link the proposed task to its asset scope and initiating condition? identity
Who authorized which work scope and revision, with what priority, constraints and permitted expenditure reference? authority
How are cancellation, partial completion, blocked work and emergency retrospective registration distinguished from authorized completion? state

Competence and work controls

The record links competence, approved method and risk-control decisions. Presence of a checklist is not proof that controls are effective; dangerous procedures remain outside this model.

Evidence of readiness review

The record links competence, approved method and risk-control decisions. Presence of a checklist is not proof that controls are effective; dangerous procedures remain outside this model.

What task-specific competence and procedure revision were required, and what evidence was reviewed for each assigned role? requirement
Which authorized risk-control and permit records govern the work, and how is their current status evidenced? security
What stops or postpones the task when competence, control evidence or site coordination is missing or disputed? exception

Performed work and resources Records what actually happened without rewriting the authorized plan.

Actual intervention

An intervention can cover part of an order or reveal new work. Actual times, actors and deviations retain their own provenance; no work is inferred from a scheduled slot.

Attributed work execution record

An intervention can cover part of an order or reveal new work. Actual times, actors and deviations retain their own provenance; no work is inferred from a scheduled slot.

What maintenance action actually occurred, by whom, on which scope and against which order or emergency basis? event
Which actual activity and outage periods were observed, with what time precision and distinction from planned duration? temporal
Which deviations, interrupted steps or newly discovered defects require separate authorization or follow-up? process

Parts and resource use

Represent installed, removed, consumed and unused materials separately. Resource use links to external inventory and finance records; lot traceability depends on the item profile.

Traceable resource disposition

Represent installed, removed, consumed and unused materials separately. Resource use links to external inventory and finance records; lot traceability depends on the item profile.

Which components or materials were installed, removed or consumed, in what quantities and units? composition
Which serial, lot, supplier or suitability evidence is available, required or missing for each used item? provenance
How are labor, tools, unused parts, waste and cost references reconciled without making this record the inventory or finance master? relationship

Verification and disposition Separates evidence of results from authority to resume use.

Post-work evidence

Before and after evidence may be incomparable, unchanged or worse. A temporal association does not establish that the intervention caused the observed change.

Qualified outcome comparison

Before and after evidence may be incomparable, unchanged or worse. A temporal association does not establish that the intervention caused the observed change.

Which inspection or test evidence demonstrates the actual result against the stated acceptance criteria? validation
Are the before and after observations comparable in scope, scale and operating context, and what change can be supported? measurement
Which residual defects, failed criteria or unobserved outcomes remain visible after the work is recorded as performed? quality

Use restrictions and release

Local completion does not authorize operation. Record an external authorized decision with scope, restrictions and expiry; allow withheld, conditional or revoked disposition.

Qualified disposition decision

Local completion does not authorize operation. Record an external authorized decision with scope, restrictions and expiry; allow withheld, conditional or revoked disposition.

Who made the applicable decision to allow, restrict or prohibit further use, and on what competence and authority basis? authority
What asset configuration, operating conditions, residual issues and validity period bound the recorded release or restriction? constraint
How are a withheld, conditional or revoked release and any subsequent resumption of use recorded as distinct events? lifecycle

Learning and record continuity Supports qualified summaries and responsible preservation.

History and improvement

Summary metrics require explicit populations, durations and exclusions. Proposed programme changes remain separate decisions; no reliability improvement is promised.

Evidence-qualified maintenance review

Summary metrics require explicit populations, durations and exclusions. Proposed programme changes remain separate decisions; no reliability improvement is promised.

What population, observation window, downtime definition and exclusions underlie a maintenance or failure metric? measurement
Which missing work records, repeat defects or uncertain classifications limit the interpretation of reported performance? quality
What approved follow-up changes the programme after review, and how is its rationale linked to the supporting evidence? decision

Transfer and retention

Corrections, custody transfer and lawful disposal must preserve meaning without imposing perpetual payload retention. Different record classes may have different periods and access duties.

Controlled history continuity

Corrections, custody transfer and lawful disposal must preserve meaning without imposing perpetual payload retention. Different record classes may have different periods and access duties.

How does a corrected or imported entry identify its source, original version and superseded assertion? provenance
Which record-class retention rule, unresolved claim or hold governs disposal, including copies and personal details? retention
What authorized transfer package preserves asset and event references, code meanings, access limits and missing-history declarations? interoperability

Classifiers Filled

Family: World Models
Category: Activities and processes
Entry kind: entity
Navigation path: NAV.ACT.MNT
Domain: ACT.MNT
Industry: Cross-industry
Tags: maintenanceact.mnt
Also called: K11

What it is Filled

One persistent asset-scoped maintenance record, with qualified condition assertions, applied programme references and linked work history. The root is not a single intervention, an asset master or a portfolio maintenance policy. All hierarchy, fields and functions below are proposed local design informed by the cited sources, not prescribed standard schemas. It records evidence and decisions without performing maintenance or certifying safety.

In scope

Stable record identity and effective stewardship for one externally mastered asset or system boundary
Condition, defects, applied strategy, due rules, planned and unplanned work, competence and control evidence
Actual interventions, resources, inspection outcomes, release references, learning and controlled continuity

Out of scope

Asset, ownership, personnel, inventory, finance, contract and procedure master data
Construction, manufacture, general operation, portfolio optimization and software patch management
Physical repair instructions, dangerous-item procedures, automated safety authorization and compliance certification

Why it exists Filled

Describe the continuing maintenance record for one identified physical asset or explicitly delimited maintainable system.

Distinguishing features Derived, awaiting review

Unlike WM-OBJ-022 asset lifecycle context: The incoming candidate COMPOSE edge may expose a maintenance-history projection. It neither transfers the asset master nor makes one maintenance record compulsory for every asset.
Unlike Generic act and work order: Acts have their own event identities and orders have their own authorization histories. The persistent maintenance root does not inherit the identity or lifecycle of one act; the legacy EXTEND claim is not ratified at the root.
Unlike Ownership, service contract and organization: References identify asset rights, delegated duties and service commitments. Record stewardship can differ from legal asset ownership; a grant alone cannot settle statutory access duties.
Unlike Plan, schedule, procedure and inventory: Shared definitions and stock masters remain external. This record stores asset-specific applicability, deviations and resource-use evidence with pinned references.

Note: Derived from boundary notes against neighbouring models.

What robots and AI may and may not do Derived, awaiting review

Must not

Deny access and mutation unless the actor has an effective role, asset scope and permitted purpose; technical competence and release authority require separate evidence.

May

Register bounded maintenance context: Proposed, unimplemented local operation. Create the local record and qualified asset links.
Record an attributed assessment: Proposed, unimplemented local operation. Append an observation or defect assertion with uncertainty.
Evaluate stated due rules: Proposed, unimplemented local operation. Evaluate a supplied approved trigger as a proposed local calculation.
Link order and readiness evidence: Proposed, unimplemented local operation. Record separately authorized scope and readiness references.
Record actual work and resources: Proposed, unimplemented local operation. Append performed-work assertions and resource references.
Record qualified outcome and release: Proposed, unimplemented local operation. Link observed outcomes and an externally authorized use decision.
Prepare a scoped history projection: Proposed, unimplemented local operation. Produce an entitled-recipient view with completeness and lineage metadata.

Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.

Moral aspects Derived, awaiting review

Correct by linked supersession, retaining required evidence subject to the applicable retention and privacy rules.
Retiring a local maintenance record does not retire the asset, revoke legal decisions or justify indefinite retention of personal data.

Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.

Owners Filled

Steward

Name the accountable record steward and delegated maintainer roles with effective scope; use role names rather than company names.

Roles

Record steward: Maintain asset scope, custody and lawful access rules; coordinate retention review.
Maintenance planner: Record approved strategy, due rules, work scope and reviewed exceptions.
Competent maintainer: Submit attributed actual-work and resource evidence within authorized scope.
Technical reviewer: Assess outcome evidence and residual defects; preserve disagreement.
Release authority: Provide separately authorized, scoped and time-qualified use decisions where the applicable profile permits.
Records custodian: Control corrections, transfer packages, retention holds and authorized disposal.

Links to other meta-models Filled

references

WM-OBJ-022 - Candidate external asset lifecycle context. The incoming COMPOSE edge is a history projection, not mandatory containment or reciprocal ownership.
Asset and ownership master - Resolve asset identity and rights without copying masters. Exact registry bindings require later review.
Plan, schedule and procedure definitions - Pin approved definitions; record only applied asset scope and actual deviations locally.
Service, organization and personnel records - Resolve contract and competence evidence; do not infer release authority from employment or service assignment.
Inventory and financial records - Link material movements and approved cost evidence; ISO 14224 abstract is not a direct-cost schema.

aligned

Generic act model - Maintenance interventions may specialize activity semantics; the persistent root does not inherit an atomic act lifecycle.
ISO 55000:2024 and ISO 14224:2016 - Public overview and abstract alignment only, subject to domain and licensing review; no conformance assertion.
PROV-O and RFC 3339 - Conceptual attribution and timestamp alignment; executable mappings and validators remain deferred.

neighbor

WM-OBJ-022 asset lifecycle context - The incoming candidate COMPOSE edge may expose a maintenance-history projection. It neither transfers the asset master nor makes one maintenance record compulsory for every asset.
Generic act and work order - Acts have their own event identities and orders have their own authorization histories. The persistent maintenance root does not inherit the identity or lifecycle of one act; the legacy EXTEND claim is not ratified at the root.
Ownership, service contract and organization - References identify asset rights, delegated duties and service commitments. Record stewardship can differ from legal asset ownership; a grant alone cannot settle statutory access duties.
Plan, schedule, procedure and inventory - Shared definitions and stock masters remain external. This record stores asset-specific applicability, deviations and resource-use evidence with pinned references.

What else AI and robots need to interact with it Incomplete

Sources Filled

ISO 55000:2024 - Asset management - Vocabulary, overview and principles - International Organization for Standardization
ISO 14224:2016 - Collection and exchange of reliability and maintenance data for equipment - International Organization for Standardization
Operations and Maintenance Best Practices Guide - United States Department of Energy
Maintenance of work equipment - Health and Safety Executive
Inspection of work equipment - Health and Safety Executive
PROV-O: The PROV Ontology - World Wide Web Consortium
RFC 3339 - Date and Time on the Internet: Timestamps - Internet Engineering Task Force

Open questions

Verify live source responses and current versions outside the sandbox, obtain appropriately licensed standards text, and review the relevant sector and jurisdiction requirements.
Develop instance schemas and mappings with fixtures for replaced assets, meter reset, conflicting observations, emergency work, partial completion, failed inspection, withheld release and lawful record disposal.
Restore independent external review before promotion beyond a noncanonical reviewable draft.
Independent external review is absent; a later local self-audit cannot replace it.
Full paid ISO texts and EN 13306 terminology mapping were not reviewed; no standard-conformance certification.
Current source versions, complete errata, legal applicability and all asset-sector regimes remain unverified.
Executable nested instance schemas, event cardinalities, state machines, neighbor bindings and import mappings require fixtures.
Physical intervention methods, predictive algorithms, safety thresholds and universal maintenance intervals are deliberately excluded.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-act-013-maintenance/spec.yaml