Maintenance & Repair

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Dimension & namespace

• EXTEND `world.actAction` (K2): maintenance acts specialize the atomic act with condition effect
• REFERENCE `world.ownership` (S1): the asset and its owner are resolved through the ownership register, never duplicated here
• REFERENCE `world.planAndSchedule` (K7): maintenance intervals and windows bind to schedules
• REFERENCE `world.practiceMethodAndProcedure` (K6): task procedures behind work orders
• REFERENCE `world.service` (K4): contracted maintenance delivered as a service offering
• REFERENCE `world.organization` (O1): contracted operators and part suppliers
• imports: iso-55000 (ALIGN): asset management vocabulary and lifecycle framing
• imports: en-13306 (ALIGN): maintenance terminology for acts, strategies and failures

Canon, patches & standards

• EXTEND `world.actAction` (K2): maintenance acts specialize the atomic act with condition effect
• REFERENCE `world.ownership` (S1): the asset and its owner are resolved through the ownership register, never duplicated here
• REFERENCE `world.planAndSchedule` (K7): maintenance intervals and windows bind to schedules
• REFERENCE `world.practiceMethodAndProcedure` (K6): task procedures behind work orders
• REFERENCE `world.service` (K4): contracted maintenance delivered as a service offering
• REFERENCE `world.organization` (O1): contracted operators and part suppliers
• imports: iso-55000 (ALIGN): asset management vocabulary and lifecycle framing
• imports: en-13306 (ALIGN): maintenance terminology for acts, strategies and failures

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

• `maintenanceServiceAgreement`: an owner engages a contracted operator to maintain defined assets to a plan and response times
• `conditionDataSharing`: condition histories are shared with insurers, buyers or engineers under the owner's terms
• `warrantyClaimSupport`: acts, parts and deltas for a covered asset are disclosed to a warrantor for a claim

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The asset owner owns the maintenance record; a contracted operator holds delegated write access for the assets it services. All access flows from owner grants under the catalogue's ownership and access models (S1/S2), with audit via S4.

Objects

• `conditionAssessment`: a dated judgement of an asset's state; key attributes: asset reference, method, measured values, condition grade
• `defect`: an identified fault; key attributes: asset reference, description, severity, detection date, status
• `failureMode`: a recurring pattern of degradation; key attributes: name, mechanism, symptoms, affected asset classes
• `maintenancePlan`: the upkeep strategy for an asset or class; key attributes: strategy kind (preventive, condition based, corrective), intervals, triggers
• `workOrder`: an authorized maintenance task; key attributes: asset reference, task, priority, planned window, assigned performer
• `maintenanceAct`: performed maintenance work; key attributes: work order reference, performer, start and end, findings
• `conditionDelta`: the state change an act produced; key attributes: prior grade, posterior grade, measures, residual issues
• `sparePartUsage`: material consumed in an act; key attributes: part identifier, quantity, source lot, cost basis

Relationships

• `conditionAssessment` -> assesses -> `asset` (many-to-one): the owned thing whose state is judged, resolved via the ownership register
• `defect` -> exhibits -> `failureMode` (many-to-one): the pattern a fault instantiates
• `workOrder` -> plannedBy -> `maintenancePlan` (many-to-one): the strategy that generated the task
• `maintenanceAct` -> executes -> `workOrder` (many-to-one): the performance of the ordered task
• `maintenanceAct` -> remedied -> `defect` (many-to-many): faults the intervention addressed
• `conditionDelta` -> resultOf -> `maintenanceAct` (one-to-one): the effect of the work on the asset's state
• `sparePartUsage` -> consumedIn -> `maintenanceAct` (many-to-one): materials the work used

Events

• `assessmentPerformed`: an asset's condition was inspected and graded
• `defectDetected`: a fault was found and logged
• `workOrderIssued`: a maintenance task was authorized and scheduled
• `maintenanceCompleted`: an intervention finished with findings recorded
• `conditionDeltaRecorded`: the before and after state change was captured
• `partReplaced`: a component was exchanged during an intervention
• `assetReturnedToService`: the asset resumed operation after work

Projections

• `assetHealthDashboard`: current condition grades and open defects across a portfolio; omits work order internals
• `backlogView`: open and overdue work orders by priority; omits historical acts
• `historyLog`: the full intervention and condition record of one asset; omits other assets