Robot / Autonomous Machine
Describe one identifiable physical robot or autonomous machine through configuration, contextual capabilities, observations and linked assurance evidence.
Bundle → Layer → Finding → Questions Filled
3 bundles · 4 layers · 6 findings · 12 questions
Identity and configuration Which machine it is and how it is configured.
Machine and configuration
Model, serial number, tooling and software.
Unit identity
The individual machine with its type and serial number.
- Which make, model and serial number does this machine have?
- Which end effectors, sensors and payloads are fitted now?
Control software
The software and versions that control it.
- Which control software and versions run on the machine?
- When was the software last changed, and was the change validated?
Safety and autonomy What the machine may do and how it is kept safe.
Operating envelope
Workspace, autonomy level and limits.
Autonomy and mode
The current mode and level of autonomy.
- Is the machine in manual, collaborative, supervised or autonomous mode?
- Which tasks may it perform without human confirmation?
Safety functions
Protective stops, zones and speed limits.
- Which safety functions, zones and speed or force limits are configured?
- When were the safety functions last tested?
Conformity
Risk assessment and certification.
Risk assessment and conformity
The documented risk assessment and declarations.
- Is there a current risk assessment for this installation and use?
- Which safety standards and conformity declarations apply?
Operation and events What the machine did.
Operating log
Tasks, faults and incidents.
Incident record
Faults, near misses and collisions with their causes.
- Which faults, near misses or contacts with people occurred, and when?
- What was the cause, and what was changed afterwards?
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- entity
- Navigation path
- NAV.PHY.OBJ.ROB
- Domain
- PHY.OBJ.ROB
- Industry
- Cross-industry
- Tags
- robotautonomousmachinephy.obj.rob
What it is Filled
A robot or autonomous machine is physical equipment that senses its surroundings and moves or acts in the physical world under programmed or learned control, with some degree of autonomy. It includes industrial arms, mobile robots, service robots and autonomous ground or aerial machines. Ordinary machinery without autonomous control belongs to equipment, and the software agent that may direct it is a separate subject.
In scope
- Machine identity and classification with evidence and disputed matches
- Time-qualified component, controller and software configuration references
- Measured physical properties, observation quality and coordinate context
- Declared capabilities, operating context, authority and reported behaviour
- Links to application risk assessments, safety validation, incidents and maintenance records
Out of scope
- Pure software agents, AI model internals and training data governance
- Ordinary equipment without a supported robotic or autonomous classification
- Fleet orchestration, route planning, task execution, motion commands and safety control
- Generic asset ownership transactions, vehicle registration and maintenance execution
- Certification, legal advice and detailed jurisdiction-specific operational rules
- Weapon, detention and controlled-item operations; only policy restrictions and authority references may be represented
Why it exists Filled
Describe one identifiable physical robot or autonomous machine through configuration, contextual capabilities, observations and linked assurance evidence.
Distinguishing features Filled
- Senses and acts in the physical world with some autonomy, unlike ordinary machinery driven step by step by an operator.
- Physical equipment, distinct from the software agent or AI system that may plan its actions.
- Its safety depends on the installation and mode as much as on the machine type.
- Unlike a vehicle in the transport sense, its main purpose is work, though autonomous vehicles overlap.
What robots and AI may and may not do Filled
Must not
- Disable, bypass or weaken safety functions, zones or limits.
- Command motion while people are in the hazard zone outside collaborative limits.
- Change control software or safety configuration without validation and authorisation.
- Operate the machine outside its conformity or risk assessment.
- Conceal incidents or delete operating logs.
Only with a human decision
- Switching to a higher level of autonomy or a new task class.
- Restarting after a safety incident.
- Approving a new installation or a change to its risk assessment.
May
- Read the machine's status, configuration, mode and logs.
- Plan and submit tasks within the configured operating envelope.
- Stop the machine through its normal stop function when a hazard is detected.
- Report faults, near misses and maintenance needs.
Moral aspects Filled
- Robots can injure people, so safety must outrank throughput and convenience.
- Automation changes jobs, and workers need a voice in how it is introduced.
- Robots with cameras and microphones collect data about people around them.
Who is affected
- Workers and bystanders near the machine
- Operators and integrators
- People whose work is automated
Owners Filled
Steward
The operator of the installation, who answers for its risk assessment, safe use and maintenance together with the manufacturer.
Roles
- Asset steward
- Resolve physical identity and master references without determining operational safety.
- Installation operator
- Provide context and externally authorized role and use records.
- Qualified safety reviewer
- Review application-specific evidence and record unresolved scope or configuration gaps externally.
- Maintainer or integrator
- Supply installation and service evidence through the designated master systems.
- Information custodian
- Apply access, retention and integrity policies to evidence and personal data.
- Local model agent
- Record and validate authorized assertions; refuse control, certification and unsupported factual inference.
Master systems
- Asset management system
- Fleet management system
- Maintenance management system
Links to other meta-models Filled
aligned
- WM-OBJ-006 - Candidate registry parent: specialize robot context while preserving generic equipment identity and lifecycle in the asset master; pin a revision before use.
- OPC 40010-1 v1.02 - Conceptual motion-device/controller/safety-state mapping; no NodeSet conformance or control implementation.
- VDA 5050 - Optional mobile-fleet interface alignment. Overview lists 3.0.0; deployed revision, patch and actual mappings require verification.
- W3C SSN/SOSA 2017 - Conceptual observation and actuation evidence vocabulary; does not make an observed result reliable or authorize actuation.
references
- WM-OBJ-012 - Candidate assembly binding for installed components and revision history; no assembly lifecycle copied.
- WM-OBJ-008 - Candidate device references for sensors, controllers and compute hardware; device master remains authoritative.
- WM-OBJ-007 - Optional vehicle profile for a mobile or aerial machine; one physical identity, separately reviewed transport authority.
- WM-ACT-013 - Candidate maintenance evidence and impact links; work execution remains activity-owned.
neighbor
- WM-OBJ-006 Equipment / Machinery - Registry parent retained as candidate alignment. Generic asset identity and lifecycle stay in the asset master; this specialization stores robot-specific assertions and master references. No executable inheritance is pinned.
- WM-OBJ-012 Assembly Instance / As-built BOM - Reference installed components and configuration revisions; do not reproduce the assembly occurrence master or imply one robot equals one controller.
- WM-OBJ-008 Device / Sensor / Compute HW - Sensors and controllers can have separate identities; observations and installed-role bindings do not transfer ownership of device lifecycle.
- WM-OBJ-007 Vehicle - A mobile or aerial instance can also reference a vehicle profile. Do not create a second physical identity or infer transport authorization from robotic classification.
- WM-ACT-013 Maintenance - Carry maintenance evidence references and machine impact. Work scheduling, permits, isolation and physical repair remain external.
- Software, AI and fleet systems - Installed control software is part of the configuration, but software release identity, mission lifecycle and execution remain separately mastered. Physical embodiment does not require learned AI.
parent
- WM-OBJ-006
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by manufacturer, model and serial number on the rating plate.
- Fleet and asset systems assign internal asset identifiers.
- Unmanned aircraft may carry a registration or remote identification number under aviation rules.
Direct properties required Filled
- Payload in kilograms and reach or working range in metres.
- Speed in metres per second and force or power limits in newtons where collaborative operation applies.
- Mass in kilograms and dimensions in metres.
- Battery capacity in watt-hours and operating time in hours for mobile robots.
- Positioning repeatability in millimetres under stated conditions.
Recognition required Filled
- Recognised by its articulated arm, mobile base or airframe, sensors, and rating plate.
- Often confused with remote-controlled machines, fixed automation without autonomy, or the software controlling it.
Capabilities and actions required Filled
- Perceives its surroundings through sensors and localises itself.
- Moves and manipulates objects within its working envelope.
- Executes tasks autonomously or under supervision and reports status.
Hazards and failure modes required Filled
- Collision with or crushing of people within its workspace.
- Unexpected motion after software faults or restarts.
- Dropped payloads and battery fires.
Standards and interfaces required Filled
- ISO 10218 and ISO/TS 15066 for industrial and collaborative robot safety.
- ISO 13482 for personal care robots.
- OPC UA companion specifications for robotics and VDA 5050 for mobile robot fleet communication.
Context of use required Filled
- Used in manufacturing, logistics, agriculture, healthcare, inspection and households.
- Regulated by machinery safety law, and for some uses by aviation or road rules.
Sources Filled
- ISO 8373:2021 - Robotics - Vocabulary - International Organization for Standardization
- ISO 10218-2:2025 - Robotics - Safety requirements - Part 2: Industrial robot applications and robot cells - International Organization for Standardization
- OPC UA for Robotics - Part 1: Vertical Integration - OPC Foundation
- Autonomy Levels for Unmanned Systems Framework, Volume II: Framework Models - National Institute of Standards and Technology
- Guide to Operational Technology Security - National Institute of Standards and Technology
- OSHA Technical Manual, Section IV, Chapter 4: Industrial Robot Systems and Industrial Robot System Safety - Occupational Safety and Health Administration
- Semantic Sensor Network Ontology - World Wide Web Consortium
- VDA 5050 - Interface for communication between mobile robots and central master control systems - German Association of the Automotive Industry
- ISO 8373 Robotics - Vocabulary, International Organization for Standardization
- ISO 10218 Robotics - Safety requirements for industrial robots, International Organization for Standardization
- Regulation (EU) 2023/1230 on machinery, European Union
Open questions
- Verify full licensed standards, source editions, exact protocol patches and the adopting sector/jurisdiction applicability profile.
- Develop nested answer schemas and tested mappings with fixtures for shared controllers, rebuild identity, tool changes, stale telemetry, unknown isolation, conflicting authority and sensitive-data deletion.
- Restore independent external review before promotion beyond a noncanonical reviewable draft.
- Full ISO texts, legal applicability and licensed clause review remain incomplete.
- Nested answer schemas, controlled vocabularies, cardinality profiles and adversarial instance fixtures are not implemented.
- Calibration traceability, human factors, energy hazards and sector-specific assessment methods need profile work.
- Exact neighbor versions, protocol patches, mapping loss and operational runtime conformance need verification.
- Independent external review and direct HTTP source checks are absent.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-obj-024-robot-autonomous-machine/spec.yaml, ver-cy/world-models/card-supplements/wm-obj-024-robot-autonomous-machine.json