← Catalogue
World Models · legacy example

Equipment & Machinery

This meta-model describes industrial and household machinery as working assets: what a machine is and how it is configured, what it is rated to do and how much it has worked, and how it is maintained, inspected and certified. It is its own model because the maintenance-and-assurance life of a machine (plans, states, certificates) is a semantic world of its own that generic item tracking does not carry, and because capability ratings are what other models match against when work needs doing.

AI YAMLAGENTS.mdSource
IDworld.m6-equipment-and-machinery
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainmatter-artifacts
Tagsequipment, machinery
Data structure

Bundles and layers

Bundle

asset

The machine as an identified, configured asset

Layers

machineIdentity`: type, model, serial, commissioning data, site reference · `configuration`: installed options, attachments and settings that change what the unit is

Bundle

operation

What the machine can do and how much it has done

Layers

capability`: rated capacities, performance envelopes, supported operations · `utilization`: operating hours, cycles, load history

Bundle

assurance

Keeping the machine fit and provably safe

Layers

maintenanceState`: plans, due work, current serviceability standing · `inspectionAndCertification`: inspections, conformity certificates, their validity

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.

Service layers

How this specification operates

Dimension & namespace

  • EXTEND `world.physicalItem` (M2): a machine is an item; identity, custody and location semantics are inherited.
  • REFERENCE `world.deviceHardware` (M8): condition-monitoring sensors and controllers attached to the unit are devices whose streams describe it.
  • REFERENCE `world.materialSubstance` (M1): consumables, lubricants and process media resolve to substance classes.
  • REFERENCE `world.place` (P1): installation sites resolve to place identities.
  • ALIGN `world.vehicle` (M7): self-propelled work machines sit on the boundary; they are modelled here for their work function and there for their transport function, with field equivalences declared instead of duplication.
  • imports: eclass (REFERENCE): classification and property dictionary for machine models and capabilities.
  • imports: iso-55000 (ALIGN): asset management lifecycle vocabulary.

Canon, patches & standards

  • EXTEND `world.physicalItem` (M2): a machine is an item; identity, custody and location semantics are inherited.
  • REFERENCE `world.deviceHardware` (M8): condition-monitoring sensors and controllers attached to the unit are devices whose streams describe it.
  • REFERENCE `world.materialSubstance` (M1): consumables, lubricants and process media resolve to substance classes.
  • REFERENCE `world.place` (P1): installation sites resolve to place identities.
  • ALIGN `world.vehicle` (M7): self-propelled work machines sit on the boundary; they are modelled here for their work function and there for their transport function, with field equivalences declared instead of duplication.
  • imports: eclass (REFERENCE): classification and property dictionary for machine models and capabilities.
  • imports: iso-55000 (ALIGN): asset management lifecycle vocabulary.

Artifact formats & serial data

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

Policies & accepted processes

  • `serviceProviderAccess`: owner-granted read and write access for a maintainer to the assurance bundle of named units.
  • `certificateVerification`: query contract confirming that a unit holds a valid certificate of a given scheme.
  • `fleetVisibility`: aggregated read access over an owner's fleet for an insurer, lessor or auditor.

Read / add / edit / delete

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

Ownership, roles & access

Each machine record is stewarded by the machine's owner per the catalogue's S1 ownership model; maintainers, insurers and inspectors see it only under grants issued through S1/S2, and assurance events carry S4 audit traceability.

Existing assembly

Objects, relationships, events and projections

Objects

  • `machine`: one individual machine; key attributes: serial reference, model reference, commissioning date, site reference.
  • `machineModel`: the class the machine instantiates; key attributes: maker reference, model code, classification code.
  • `capabilitySpec`: one rated capability; key attributes: capability kind, rated value, unit, conditions.
  • `configurationItem`: an installed option or attachment; key attributes: kind, identifier, installed date.
  • `utilizationRecord`: a usage measurement over a period; key attributes: metric (hours, cycles), value, period.
  • `maintenancePlan`: scheduled upkeep the machine is under; key attributes: plan reference, interval basis, tasks.
  • `maintenanceState`: current serviceability standing; key attributes: state, due items, last service date.
  • `certificate`: an inspection or conformity certificate; key attributes: scheme, issuer reference, validity period, scope.

Relationships

  • `machine` -> instanceOf -> `machineModel` (many-to-one): the unit inherits its model's baseline description.
  • `machine` -> ratedFor -> `capabilitySpec` (1..*): effective ratings, possibly narrowed by configuration or wear.
  • `machine` -> configuredWith -> `configurationItem` (0..*): current installed options and attachments.
  • `machine` -> maintainedUnder -> `maintenancePlan` (0..*): plans in force for the unit.
  • `machine` -> standsIn -> `maintenanceState` (exactly one current): the unit's serviceability at any moment.
  • `machine` -> certifiedBy -> `certificate` (0..*): certificates held, each with its own validity.
  • `machine` -> partOf -> `machine` (0..1): lines, installations and machine trains.

Events

  • `machineCommissioned`: the unit entered service at a site.
  • `utilizationRecorded`: a usage reading extended the utilization history.
  • `maintenancePerformed`: planned or corrective work was completed on the unit.
  • `breakdownReported`: the unit failed or was taken out of service unexpectedly.
  • `inspectionPassed`: an inspection concluded with a positive result.
  • `certificateExpired`: a certificate's validity lapsed without renewal.
  • `machineDecommissioned`: the unit permanently left service.

Projections

  • `operatorView`: capability, configuration and current serviceability; omits commercial and certificate internals.
  • `insurerRiskView`: utilization, breakdown history and certificate standing; omits configuration detail.
  • `resaleView`: identity, hours, maintenance history summary and certificates; omits site and operational data.