Published

Equipment / Machinery

vr.wm-obj-006 · wm-obj-006-equipment-machinery

Describe one industrial or household machine as a working physical unit with configuration, capability, observations and qualified assurance evidence.

World Models Physical world and living systems PHY.OBJ.EQPT

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

6 bundles · 12 layers · 18 findings · 54 questions

Identity and configuration Define the machine unit and its effective assembly.

Identification

Equipment-specific context for identification. Assertions retain evidence and unknown status.

Unit identity

Resolve one physical unit through its master identity and scoped markings. A plate reading is an observation, and an unmarked unit can remain provisionally identified.

Which master record identifies this individual machine? identity
Which product type and classification version describe the unit? classification
Which markings or recognition observations corroborate the identity without confusing a similar unit? evidence

Identity continuity

Keep asset-tag changes, corrections and replacement decisions explicit. A change of custodian does not by itself create a new machine.

Which rebuild or replacement decision preserves or terminates this unit identity? lifecycle
Which duplicate or conflicting identifiers still need reconciliation? quality
Who attested an identity correction and which earlier assertion does it supersede? provenance

Configuration

Equipment-specific context for configuration. Assertions retain evidence and unknown status.

Installed configuration

Describe the effective assembly through separately identified parts and revisions. Permanent components, temporary tools and software bindings have distinct roles.

Which components and attachments belong to the effective configuration? composition
Which configuration revision applied when the reported work or observation occurred? temporal
Which incompatible, missing or unverified component bindings prevent a complete configuration claim? constraint

Properties and capability Describe qualified physical characteristics and intended technical capability.

Physical characteristics

Equipment-specific context for physical characteristics. Assertions retain evidence and unknown status.

Physical properties

Record unit-specific dimensions, mass, interfaces and environmental requirements as qualified assertions. Class defaults and measured values remain distinguishable.

Which dimensions and mass apply to the current assembled unit? measurement
Which supply, connection and environmental requirements constrain installation? requirement
Which physical properties are measured, declared, estimated or still unknown? quality

Rated capability

Equipment-specific context for rated capability. Assertions retain evidence and unknown status.

Capability envelope

Represent intended tasks and qualified ratings as evidence-backed descriptions. A technical rating is neither a work assignment nor permission to operate.

Which intended tasks are supported by this configured machine? definition
Which rated limits and deratings apply under the stated conditions? measurement
Which proposed task requirements fall outside or cannot be compared with the documented envelope? constraint

Operation and observation Preserve operating reports and qualified measurements.

Operation history

Equipment-specific context for operation history. Assertions retain evidence and unknown status.

Operating state and mode

Keep reported operating state, operation mode, telemetry availability and safety release separate. Missing communication is not evidence of a stopped machine.

What operating state and mode were reported at the relevant time? state
How fresh and trustworthy is the state observation? quality
Which absent or contradictory reports prevent a current-state conclusion? exception

Utilization counters

Preserve metric definitions and meter lineage rather than treating every hour counter as productive work. Counter discontinuities need evidence before totals can be combined.

Which hours, cycles or other counters were read and what does each metric count? measurement
Which meter replacement, reset, rollover or correction explains a counter discontinuity? event
Which observation coverage and denominator support a derived utilization measure? validation

Condition evidence

Equipment-specific context for condition evidence. Assertions retain evidence and unknown status.

Condition observations

Link attributed evidence to the specific component, property and conditions observed. A measured signal, a fault hypothesis and a confirmed diagnosis are different assertions.

Which condition property of which unit or component was observed? measurement
When did the observed condition apply and when was its result recorded? temporal
Which sensor, calibration or diagnostic evidence supports the condition interpretation? evidence

Fault and failure reports

Preserve reported symptoms, affected functions and restriction references without manufacturing a root cause or claiming that a report changes physical state.

What fault symptoms were reported for the unit and its affected functions? event
Which diagnosis is confirmed, contested or only hypothesized? decision
Which external incident or work record addresses the reported fault? relationship

Maintenance and inspection Reference required work and evidence of its assessment.

Maintenance

Equipment-specific context for maintenance. Assertions retain evidence and unknown status.

Maintenance obligations

Reference applicable plans and unit-specific due assertions. A missing plan or unknown meter basis must not become a statement that no work is due.

Which maintenance plan revision applies to this unit and configuration? requirement
What date, usage or condition trigger makes each applicable work item due? temporal
Which overdue, deferred or indeterminate work items require review? exception

Maintenance execution evidence

Capture machine-specific links to completed, partial or failed work. Work execution, labor scheduling and procurement remain outside the model.

Which authenticated work record supports the claimed maintenance outcome? evidence
Which component or configuration changes resulted from the recorded work? composition
Which competent reviewer accepted the work evidence and what remains open? authority

Inspection

Equipment-specific context for inspection. Assertions retain evidence and unknown status.

Inspection assessments

Represent applicable inspection scope, findings and follow-up separately from manufacturer declarations or general serviceability. Frequency is profile-dependent.

Which inspection requirement and trigger apply to this unit at this location? requirement
What result and defects are recorded by the competent inspector? evidence
When is another inspection required and which event can invalidate the prior assessment? temporal

Assurance and use context Separate applicability, release evidence and responsibility.

Assurance

Equipment-specific context for assurance. Assertions retain evidence and unknown status.

Conformity document applicability

Distinguish declaration of conformity, declaration of incorporation, third-party certificate and inspection report. A document can be absent, disputed, superseded or inapplicable.

Which document kind and scheme concern this unit or product type? classification
Which evidence connects the document to this configuration and applicable regime? validation
Which expiry, withdrawal, supersession or scope limitation changes the document assessment? exception

Safety restrictions and release evidence

Store policy-level hazards, protective-measure references, restrictions and authorized release evidence. This record cannot operate equipment, implement isolation or certify safe use.

Which hazard and protective-policy references limit access or intended use? security
Who is authorized to attest restriction or return-to-service decisions for the applicable context? authority
Which unresolved safety evidence prevents a supported release assertion? constraint

Installation context

Equipment-specific context for installation context. Assertions retain evidence and unknown status.

Site and responsibility context

Keep installation, possession, operating responsibility and legal ownership as time-qualified external references. Custody and location cannot establish title.

Where was the unit installed, stored or mobile during the relevant interval? spatial
Which separate parties hold legal ownership, custody and operating responsibility? ownership
Which site or custody change triggers review of installation-dependent evidence? relationship

Continuity and exchange Preserve governed history and explicit exchange limits.

Record continuity

Equipment-specific context for record continuity. Assertions retain evidence and unknown status.

Retirement and handover

Record decisions and external disposition evidence while preserving identity continuity. Retirement of the record, physical decommissioning and disposal are different events.

Which evidence records withdrawal, transfer, dismantling or final disposition of this unit? lifecycle
Which machine history must be retained or lawfully disposed of under the adopting policy? retention
Which history and restrictions are authorized for the receiving party at handover? access

Evidence lineage and controlled views

Every local assertion has attribution, time and revision context. Recipient views must preserve safety-relevant uncertainty while minimizing personal and commercially sensitive data.

Which source activity and actor support each machine assertion? provenance
Which operator or site details can be omitted from the requested view? privacy
Which scoped grant permits this recipient to read or amend the equipment evidence? access

External binding

Equipment-specific context for external binding. Assertions retain evidence and unknown status.

Exchange bindings

Record explicit versioned mappings without asserting implemented conformance. External information models inform this proposal but do not prescribe its hierarchy.

Which pinned schema or vocabulary maps the equipment fields for an exchange? interoperability
Which losses or unresolved references must an export disclose? validation
Which conformance evidence exists for the chosen binding and which claims remain untested? quality

Classifiers Filled

Family: World Models
Category: Physical world and living systems
Entry kind: entity
Navigation path: NAV.PHY.OBJ.EQPT
Domain: PHY.OBJ.EQPT
Industry: Cross-industry
Tags: equipmentmachineryphy.obj.eqpt
Also called: M6

What it is Filled

One identified machine unit, including manual or disconnected units, persists across configuration and responsibility changes. Assemblies may reference other units. This is a proposed record model, not a controller, safety system, conformity service or universal legal machinery classification.

In scope

Unit-specific identity links, configuration, physical properties and technical capability
Operating observations, utilization, condition reports and maintenance evidence references
Inspection, conformity-document applicability, policy-level restrictions, handover and governed record continuity

Out of scope

Product catalogs, device telemetry infrastructure, generic physical-item masters, sites and material masters
Physical actuation, control commands, changing settings, isolation procedures or autonomous safety release
Work-order execution, procurement, valuation, legal title determination and certification issuance
Detailed weapons or controlled-item operation; such uses are limited to policy and authority references

Why it exists Filled

Describe one industrial or household machine as a working physical unit with configuration, capability, observations and qualified assurance evidence.

Distinguishing features Derived, awaiting review

Unlike WM-OBJ-001 Physical Item Instance: Legacy M2 EXTEND is retained as conceptual specialization only. Share the mastered physical identity, custody and location references; generic item governance is not reimplemented.
Unlike WM-OBJ-002 Product Type / Catalog Item: A repeatable product type supplies a referenced baseline; this root is one unit with its own effective configuration and observations.
Unlike WM-OBJ-008 Device / Sensor / Compute HW: Sensors and controllers retain their own identities and streams. The unit links relevant evidence and installed revisions; it does not own device administration.
Unlike WM-OBJ-007 Vehicle: A mobile work machine may share one physical identity across work and transport roles. Transport authorization, traffic operation and fleet dispatch are outside this root.
Unlike Site, material, work and authority masters: Use external references for places, consumables, work orders, parties, grants and incidents. Legacy broad place and substance aliases are not silently mapped to one narrower successor.

Note: Derived from boundary notes against neighbouring models.

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

Must not

This model cannot start, stop, configure, isolate or release machinery; record operations have no physical effects
Unknown, stale or conflicting assurance evidence cannot yield a positive serviceability assertion
Deny by default; read or write requires a named purpose and scoped role grant.

May

Register an equipment record: Proposed, unimplemented local record operation. Create a provisional or corroborated local unit record without minting a duplicate physical master.
Record configuration evidence: Proposed, unimplemented local record operation. Append an attested configuration revision without changing the physical machine or device software.
Append an equipment observation: Proposed, unimplemented local record operation. Store a qualified observation and its lineage without converting absent data into a known machine state.
Link maintenance or inspection evidence: Proposed, unimplemented local record operation. Associate externally performed work with the machine and its configuration.
Record an assurance review: Proposed, unimplemented local record operation. Record a qualified human assessment of document applicability and release evidence.
Prepare a governed handover view: Proposed, unimplemented local record operation. Create a local candidate projection for a named recipient and purpose.

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

Moral aspects Derived, awaiting review

Use recipient-specific least privilege; operator history may be personal data and site details may be sensitive

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

Owners Filled

Steward

Name an accountable adopting-Dimension steward by role or governed party reference; no fixed commercial owner

Roles

Equipment steward: Reconcile identity and maintain profile bindings without asserting legal ownership
Operator or observer: Provide attributed observations and report uncertainty or faults; cannot grant own release
Maintainer: Submit evidence of performed work within competence and grant scope
Inspector or safety reviewer: Assess scoped evidence under separately verified competence and authority
Records custodian: Apply retention, access and handover rules and preserve lawful audit references

Links to other meta-models Filled

extends

WM-OBJ-001 - Conceptual physical-item specialization sharing a master identity; executable inheritance and version binding remain unverified.

references

WM-OBJ-002 - Reference the type baseline without owning catalog lifecycle.
WM-OBJ-008 - Link sensors and controllers to equipment observations and configuration; device control remains external.
WM-OBJ-006 - Reference parent or child machines with role and effective interval; reject containment cycles and do not force one universal hierarchy.
adopting-dimension:site-master - Resolve installation and location against a profile-selected site master; legacy place alias has no automatic successor mapping.
adopting-dimension:material-master - Resolve consumables and process media externally; no chemical or material lifecycle is owned here.
adopting-dimension:work-record-master - Reference work orders and incident records while retaining only equipment-specific links and outcome assertions.
adopting-dimension:authority-policy - Resolve parties, ownership evidence, grants and review competence externally; these profile locators are not registered model IDs.

aligned

WM-OBJ-007 - Align work and transport roles of one physical unit without duplicating identity or transport authority.
OPC 40001-1 - Conceptual mapping of identification, components, states and counters; the specification does not prescribe this entity hierarchy.
SOSA/SSN and PROV-O - Conceptual observation and provenance alignments, without claiming executable RDF conformance.

neighbor

WM-OBJ-001 Physical Item Instance - Legacy M2 EXTEND is retained as conceptual specialization only. Share the mastered physical identity, custody and location references; generic item governance is not reimplemented.
WM-OBJ-002 Product Type / Catalog Item - A repeatable product type supplies a referenced baseline; this root is one unit with its own effective configuration and observations.
WM-OBJ-008 Device / Sensor / Compute HW - Sensors and controllers retain their own identities and streams. The unit links relevant evidence and installed revisions; it does not own device administration.
WM-OBJ-007 Vehicle - A mobile work machine may share one physical identity across work and transport roles. Transport authorization, traffic operation and fleet dispatch are outside this root.
Site, material, work and authority masters - Use external references for places, consumables, work orders, parties, grants and incidents. Legacy broad place and substance aliases are not silently mapped to one narrower successor.

What else AI and robots need to interact with it Incomplete

Sources Filled

OPC UA for Machinery - Part 1: Basic Building Blocks - OPC Foundation
Inspection of work equipment - Health and Safety Executive
Maintenance of work equipment - Health and Safety Executive
29 CFR 1910.147 - The control of hazardous energy - Occupational Safety and Health Administration
Semantic Sensor Network Ontology - World Wide Web Consortium
PROV-O: The PROV Ontology - World Wide Web Consortium
Regulation (EU) 2023/1230 on machinery - European Parliament and Council of the European Union
RFC 3339 - Date and Time on the Internet: Timestamps - Internet Engineering Task Force

Open questions

Restore independent external review before canonical or publishable-draft promotion.
Complete source URL, version, corrigendum, licensing and claim-level checks and review applicable sector and jurisdiction profiles.
Develop executable schemas and mappings with fixtures for duplicate serials, absent ratings, disconnected units, counter replacement, component swaps, disputed release, expired or inapplicable documents, transfer and lawful disposal.
Independent external review is absent; Claude and Grok are skipped under the owner-authorized waiver.
Direct HTTP source verification is blocked by the stated sandbox constraint and was not attempted. Browser content review is not a measured HTTP status or independent verification.
Executable nested instance schemas, mappings, pinned neighbor releases and adversarial fixtures are not implemented.
Household, legacy, custom-built, lifting, pressure, medical, hazardous-area and other specialist equipment profiles need additional evidence; workplace sources do not apply universally.
Licensed classification dictionaries and full ISO 55000, ISO 14224 and ISO 12100 texts were not read or admitted; no conformance claim is made.
Current law, amendments, applicability, translations, licensing and sector-specific inspection or retention duties need qualified review before use.

Machine files

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

Provenance

world-models research · reviewable-draft

Built from: models/wm-obj-006-equipment-machinery/spec.yaml