← Back to catalogue
Published

Work Order

vr.wm-act-007 · wm-act-007-work-order

Represent an authoritative, versioned instruction that authorizes and constrains one or more units of work while preserving boundaries to requests, procedures, schedules and performed-work evidence.

World Models Activities and processes ACT.WO
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

6 bundles · 17 layers · 34 findings · 102 questions

Authority and origin Establishes what the order is, why it exists and who is empowered to issue it.

Order identity

Stable identity and classification of the governed order.

Authoritative identity

The master-system identifier, aliases and revision-qualified identity of the work order.

  1. What is the governed value of authoritative identity for this work order? identity
  2. Who or what authoritative source establishes authoritative identity for this work order? spatial
  3. How is authoritative identity validated, changed and historically preserved? measurement

Classification and kind

The governed order class, profile and criteria that distinguish this order from neighboring instruction types.

  1. What is the governed value of classification and kind for this work order? classification
  2. Who or what authoritative source establishes classification and kind for this work order? authority
  3. How is classification and kind validated, changed and historically preserved? retention

Request and rationale

The initiating demand and reason for converting it into authorized work.

Originating request

Reference to the demand, request or triggering condition from which the order was derived.

  1. What is the governed value of originating request for this work order? relationship
  2. Who or what authoritative source establishes originating request for this work order? process
  3. How is originating request validated, changed and historically preserved? definition

Business or operational rationale

The stated need, risk, obligation or desired benefit that justifies ordering the work.

  1. What is the governed value of business or operational rationale for this work order? decision
  2. Who or what authoritative source establishes business or operational rationale for this work order? evidence
  3. How is business or operational rationale validated, changed and historically preserved? state

Authorization

The issuer's authority, effective scope and limitations.

Issuing authority

The person, organization or delegated role that issued the authoritative revision and the basis of that authority.

  1. What is the governed value of issuing authority for this work order? authority
  2. Who or what authoritative source establishes issuing authority for this work order? security
  3. How is issuing authority validated, changed and historically preserved? ownership

Authorization scope

The work, targets, resources, period and limits covered by the issued authority.

  1. What is the governed value of authorization scope for this work order? constraint
  2. Who or what authoritative source establishes authorization scope for this work order? exception
  3. How is authorization scope validated, changed and historically preserved? event
Ordered work definition Defines the authorized scope, intended outcome, task composition and target context.

Scope and outcome

Authorized inclusions, exclusions and expected result.

Authorized scope

The explicit work boundary, including included and excluded activities and affected subjects.

  1. What is the governed value of authorized scope for this work order? composition
  2. Who or what authoritative source establishes authorized scope for this work order? definition
  3. How is authorized scope validated, changed and historically preserved? security

Required outcome

The deliverable, condition or service level that the authorized work is expected to produce.

  1. What is the governed value of required outcome for this work order? requirement
  2. Who or what authoritative source establishes required outcome for this work order? composition
  3. How is required outcome validated, changed and historically preserved? decision

Task composition

Contained task references and immutable work-master bindings.

Contained task references

Ordered references to tasks with order-local parameters and dependency bindings, without importing task execution state.

  1. What is the governed value of contained task references for this work order? composition
  2. Who or what authoritative source establishes contained task references for this work order? lifecycle
  3. How is contained task references validated, changed and historically preserved? relationship

Procedure or work-master reference

A pinned reference to the approved procedure, recipe or work-master version governing execution.

  1. What is the governed value of procedure or work-master reference for this work order? interoperability
  2. Who or what authoritative source establishes procedure or work-master reference for this work order? provenance
  3. How is procedure or work-master reference validated, changed and historically preserved? ownership

Target context

The affected subject and the operational place in which the instruction applies.

Subject or target reference

Reference to the asset, product, case, service or other object whose state or condition is to be changed.

  1. What is the governed value of subject or target reference for this work order? relationship
  2. Who or what authoritative source establishes subject or target reference for this work order? requirement
  3. How is subject or target reference validated, changed and historically preserved? process

Location and operational context

Applicable site, functional location, hierarchy boundary and operating conditions relevant to execution.

  1. What is the governed value of location and operational context for this work order? spatial
  2. Who or what authoritative source establishes location and operational context for this work order? event
  3. How is location and operational context validated, changed and historically preserved? validation
Planning and constraints Captures order-level priority, timing, dependencies and mandatory controls.

Priority and time

Priority, criticality and authorized planning window.

Priority and criticality

The ranked urgency, consequence class and authority responsible for prioritization or escalation.

  1. What is the governed value of priority and criticality for this work order? classification
  2. Who or what authoritative source establishes priority and criticality for this work order? quality
  3. How is priority and criticality validated, changed and historically preserved? interoperability

Planned window and deadline

Earliest and latest start, due time, commitment window and the timezone basis for those values.

  1. What is the governed value of planned window and deadline for this work order? temporal
  2. Who or what authoritative source establishes planned window and deadline for this work order? retention
  3. How is planned window and deadline validated, changed and historically preserved? composition

Dependencies and holds

Predecessors, release conditions, permits and quality or safety gates.

Predecessors and blockers

Referenced orders, tasks, events or conditions that must be satisfied before release or continuation.

  1. What is the governed value of predecessors and blockers for this work order? relationship
  2. Who or what authoritative source establishes predecessors and blockers for this work order? interoperability
  3. How is predecessors and blockers validated, changed and historically preserved? spatial

Permit, safety and quality constraints

Applicable permits, isolations, safety controls, inspection points and quality gates bound to the order.

  1. What is the governed value of permit, safety and quality constraints for this work order? security
  2. Who or what authoritative source establishes permit, safety and quality constraints for this work order? identity
  3. How is permit, safety and quality constraints validated, changed and historically preserved? constraint
Resource requirements Defines responsibility and the capabilities, equipment, materials and commercial bounds required by the order.

Responsibility

Accountability, assignment and acknowledgement.

Responsible party

The accountable organizational unit, role or party for delivery and order administration.

  1. What is the governed value of responsible party for this work order? ownership
  2. Who or what authoritative source establishes responsible party for this work order? relationship
  3. How is responsible party validated, changed and historically preserved? quality

Assignment and acknowledgement

Assignee references and their time-stamped acceptance, refusal or reassignment response.

  1. What is the governed value of assignment and acknowledgement for this work order? event
  2. Who or what authoritative source establishes assignment and acknowledgement for this work order? temporal
  3. How is assignment and acknowledgement validated, changed and historically preserved? exception

Required resources

Capabilities and consumable or reusable resources needed for execution.

Personnel capability requirements

Required roles, competencies, certifications, quantities and availability constraints without duplicating worker records.

  1. What is the governed value of personnel capability requirements for this work order? requirement
  2. Who or what authoritative source establishes personnel capability requirements for this work order? ownership
  3. How is personnel capability requirements validated, changed and historically preserved? classification

Equipment, material and asset requirements

Required equipment classes, tools, materials, quantities, units and reservation references.

  1. What is the governed value of equipment, material and asset requirements for this work order? measurement
  2. Who or what authoritative source establishes equipment, material and asset requirements for this work order? constraint
  3. How is equipment, material and asset requirements validated, changed and historically preserved? temporal

Commercial bounds

Estimated effort, authorized cost bounds and governing agreements.

Estimated effort and cost bound

Order-level estimates, ceilings, currencies, approval thresholds and uncertainty, not a replacement for cost transactions.

  1. What is the governed value of estimated effort and cost bound for this work order? measurement
  2. Who or what authoritative source establishes estimated effort and cost bound for this work order? evidence
  3. How is estimated effort and cost bound validated, changed and historically preserved? requirement

Service contract reference

Pinned reference to the agreement, entitlement, warranty or service level governing the ordered work.

  1. What is the governed value of service contract reference for this work order? relationship
  2. Who or what authoritative source establishes service contract reference for this work order? validation
  3. How is service contract reference validated, changed and historically preserved? evidence
Lifecycle and change control Governs administrative state, release, revisions, suspension, cancellation and exceptions.

Order state

Administrative lifecycle state and dispatch interface.

Lifecycle state

The current administrative state, allowed transition, responsible actor and effective transition event.

  1. What is the governed value of lifecycle state for this work order? state
  2. Who or what authoritative source establishes lifecycle state for this work order? access
  3. How is lifecycle state validated, changed and historically preserved? exception

Release and dispatch

The controlled release to an execution context, dispatch destination and acknowledgement reference.

  1. What is the governed value of release and dispatch for this work order? process
  2. Who or what authoritative source establishes release and dispatch for this work order? decision
  3. How is release and dispatch validated, changed and historically preserved? identity

Change control

Immutable revisions and controlled termination or temporary inhibition.

Revision and supersession

Revision identity, changed scope, reason, approver and explicit predecessor or successor relation.

  1. What is the governed value of revision and supersession for this work order? lifecycle
  2. Who or what authoritative source establishes revision and supersession for this work order? classification
  3. How is revision and supersession validated, changed and historically preserved? temporal

Suspension, cancellation and expiry

Authority, reason, time and residual obligations when authorization is paused, withdrawn or expires.

  1. What is the governed value of suspension, cancellation and expiry for this work order? lifecycle
  2. Who or what authoritative source establishes suspension, cancellation and expiry for this work order? state
  3. How is suspension, cancellation and expiry validated, changed and historically preserved? authority

Exception management

Deviation, escalation and conflicting-order handling.

Deviation and escalation

Requested or approved deviations, unresolved blockers, escalation paths and disposition deadlines.

  1. What is the governed value of deviation and escalation for this work order? exception
  2. Who or what authoritative source establishes deviation and escalation for this work order? spatial
  3. How is deviation and escalation validated, changed and historically preserved? measurement

Conflict and duplicate resolution

Relations to duplicate or contradictory orders and the authoritative resolution decision.

  1. What is the governed value of conflict and duplicate resolution for this work order? decision
  2. Who or what authoritative source establishes conflict and duplicate resolution for this work order? authority
  3. How is conflict and duplicate resolution validated, changed and historically preserved? retention
Acceptance, closure and governance Connects completion evidence to acceptance and closure while preserving provenance, ownership, access and retention controls.

Completion interface

References to performed work and the criteria for acceptance.

Completion claim reference

Reference to a work-performance, work-record or completion claim and the issuer and time of that claim.

  1. What is the governed value of completion claim reference for this work order? evidence
  2. Who or what authoritative source establishes completion claim reference for this work order? process
  3. How is completion claim reference validated, changed and historically preserved? definition

Acceptance criteria

Measurable conditions, tolerances, evidence requirements and verifier authority used to evaluate completion.

  1. What is the governed value of acceptance criteria for this work order? validation
  2. Who or what authoritative source establishes acceptance criteria for this work order? evidence
  3. How is acceptance criteria validated, changed and historically preserved? state

Closure and disposition

Acceptance decision, rejection, rework and final retention disposition.

Acceptance or rejection

The authorized evaluation decision, defects, exceptions and referenced corrective or rework order.

  1. What is the governed value of acceptance or rejection for this work order? decision
  2. Who or what authoritative source establishes acceptance or rejection for this work order? security
  3. How is acceptance or rejection validated, changed and historically preserved? ownership

Closure and retention

Closure reason, unresolved obligations, retention class, legal hold and tombstone or erasure authority.

  1. What is the governed value of closure and retention for this work order? retention
  2. Who or what authoritative source establishes closure and retention for this work order? exception
  3. How is closure and retention validated, changed and historically preserved? event

Evidence and access

Provenance, quality, ownership, disclosure and scoped access.

Provenance and quality

Source lineage, capture method, freshness, confidence and validation results for order facts and attached evidence.

  1. What is the governed value of provenance and quality for this work order? provenance
  2. Who or what authoritative source establishes provenance and quality for this work order? definition
  3. How is provenance and quality validated, changed and historically preserved? security

Ownership, disclosure and access

Record owner, stewardship, delegated writers, disclosure policy, access scopes and approved exceptions.

  1. What is the governed value of ownership, disclosure and access for this work order? access
  2. Who or what authoritative source establishes ownership, disclosure and access for this work order? composition
  3. How is ownership, disclosure and access validated, changed and historically preserved? decision

Classifiers Filled

Family
World Models
Category
Activities and processes
Entry kind
aggregate
Navigation path
NAV.ACT.WO
Domain
ACT.WO
Industry
Cross-industry
Tags
workorderact.wo
Also called
K11

What it is Filled

Owns order identity, authorization, scope, requirements, administrative lifecycle, change control, acceptance criteria and closure disposition; references execution and domain records governed elsewhere.

In scope

  • Order identity, class, authority, scope, requirements, constraints and order-level planning commitments
  • Administrative state transitions, revisions, cancellation, acceptance decision, closure and governance metadata
  • Typed references to tasks, procedures, targets, resources, contracts, schedules and performed-work evidence

Out of scope

  • Task execution semantics, detailed scheduling, inventory transactions, cost accounting, access enforcement and proof that physical work occurred
  • Lifecycle ownership of referenced assets, people, organizations, locations, contracts, procedures or evidence records

Why it exists Filled

Represent an authoritative, versioned instruction that authorizes and constrains one or more units of work while preserving boundaries to requests, procedures, schedules and performed-work evidence.

Distinguishing features Filled

  • An authorized instruction to perform defined work, distinct from the work request that asked for it.
  • Holds scope, acceptance criteria and closure disposition, while task execution and time records live elsewhere.
  • Changes after authorization go through change control, unlike a free-form task list.
  • Closure records whether work was accepted, cancelled or deferred, not the asset state that resulted.

What robots and AI may and may not do Filled

Must not

  • Release or authorize a work order without the authority to do so.
  • Expand scope or cost beyond the authorized limit without approved change.
  • Close a work order as complete when acceptance criteria were not met.
  • Skip permit-to-work, isolation or lockout requirements recorded for the job.
  • Delete a closed work order needed for maintenance history or audit.

Only with a human decision

  • Authorizing work with safety, cost or contractual impact.
  • Accepting completed work against the criteria.
  • Cancelling a work order already in progress.

May

  • Draft a work order from an approved request with scope, location and acceptance criteria.
  • Report status and link completed work records.
  • Propose changes to scope or schedule as change requests.
  • Flag work orders past their due date or missing safety prerequisites.

Moral aspects Filled

  • Hazardous work depends on the order carrying correct isolation and permit information; errors can injure workers.
  • Work order data is used to measure technicians and can be used unfairly without context.
  • Deferring safety-relevant work affects people who rely on the asset.

Who is affected

  • Technicians and contractors who perform the work
  • Occupants and users of the asset being worked on
  • Requesters and budget holders

Owners Filled

Steward

Declare the Dimension owner, accountable stewards and authority delegation chain.

Roles

Dimension owner
Own namespace, mastership, retention, access and delegation policy for work-order records.
Order issuer
Authorize scope and effective revision within documented authority.
Order steward
Maintain classification, references, lifecycle integrity and conflict resolution.
Assignee or executing party
Acknowledge assignment and publish execution claims to the proper performed-work model.
Verifier or acceptor
Evaluate evidence against acceptance criteria and record an authorized disposition.
Auditor
Review provenance, authorization, access, changes, retention and unresolved exceptions without editing operational truth.

Links to other meta-models Filled

composes

  • WM-ACT-006 Task - Groups typed task references and order-local parameters without claiming ownership of task execution semantics.

references

  • Procedure or work-master model - Pins the executable instruction version while keeping reusable procedure content outside the order.
  • Schedule or calendar model - Delegates detailed sequencing and capacity allocation while retaining order-level timing commitments.
  • Asset, location, person, organization, material and inventory models - Uses authoritative domain identities without copying their properties or lifecycles.
  • Contract, entitlement and cost models - Binds governing agreements and commercial limits without turning the order into a ledger.
  • Performed-work and evidence models - Separates authorization from claims and proof of actual execution.

aligned

  • ISA-95, OPC UA ISA-95, PLCS and UN/EDIFACT concepts - Maintains documented semantic mappings without claiming conformance to any one implementation profile.

neighbor

  • Work request - A request proposes or demands work and can be rejected; a work order is an authorized instruction with controlled scope and lifecycle.
  • Task or procedure - The order may contain task references and pin procedure versions, but task execution semantics and reusable instructions remain in their own models.
  • Work performance or work record - A work order authorizes work; performed-work records and evidence establish what actually happened and are only referenced here.
  • Schedule - The order may carry windows and commitments, but resource-level sequencing and calendar optimization belong to a schedule model.

contains

  • WM-ACT-006

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Authoritative master-system work-order identifier and immutable issued-revision identifier.
  • Governed globally resolvable IRI or federation identifier.
  • Adopting-Dimension UUID or ULID when no authoritative external identifier exists.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • A work order has an order number, an authorizer, a work location or asset, a scope statement and a status.
  • It is confused with a work request, a purchase order and a maintenance task procedure.

Capabilities and actions required Filled

  • Create draft order: Establish a proposed order identity, origin and scope without granting authority.
  • Validate order boundary: Check required order facts, external references and separation from request, procedure and execution records.
  • Authorize order: Issue an immutable revision under a verified authority and effective scope.
  • Release order: Expose an authorized revision to its declared dispatch or execution context.
  • Revise order: Create a traceable successor without overwriting an issued revision.
  • Suspend or resume order: Temporarily inhibit or restore administrative availability under named authority and reason.
  • Cancel order: Withdraw remaining authorization while preserving evidence and residual obligations.
  • Record completion claim: Bind external performed-work evidence without silently asserting acceptance.
  • Accept or reject result: Evaluate referenced evidence against the issued acceptance criteria and record the authorized decision.
  • Close order: Finalize disposition, unresolved exceptions and retention metadata after an authorized decision.

Hazards and failure modes required Filled

  • Injury when isolation or permit requirements are missing or ignored.
  • Work done on the wrong asset because of an ambiguous reference.
  • Unauthorized spend through scope growth.
  • Duplicate orders causing repeated or conflicting work.

Standards and interfaces required Filled

  • ISO 14224 for maintenance data in petroleum and natural gas industries.
  • IEC 62264 (ISA-95) for work and operations management.
  • EN 13306 maintenance terminology.
  • MIMOSA OSA-EAI for asset management information exchange.

Context of use required Filled

  • No universal legal retention period, signature method, worker-qualification rule, safety permit regime or tax treatment is assumed.

Sources Filled

  1. ANSI/ISA-95.00.05-2018 preview: Business-to-Manufacturing Transactions - International Society of Automation
  2. ISA-95 Standard overview - International Society of Automation
  3. OPC UA for ISA-95, Part 4: Job Control - OPC Foundation
  4. PLCS WorkOrder template - OASIS Open
  5. PLCS concept model definitions - OASIS Open
  6. PLCS Aviation Maintenance DEX information model - OASIS Open
  7. PLCS Referencing Task template - OASIS Open
  8. UN/EDIFACT Job Order message (JOBOFF) - United Nations Economic Commission for Europe

Open questions

  • Validate exact state mappings and mandatory properties against current maintenance, manufacturing, field-service and public-sector implementation profiles.
  • Pin mature sibling model IDs and cardinality contracts for procedures, schedules, resources, contracts, evidence, performed work, access control and audit trails.
  • Review the generated question wording with practitioners and replace generic evidence forms with profile-specific artifacts where authoritative standards require them.
  • Industry and jurisdiction profiles must supply exact state code lists, mandatory signatures, permit semantics, retention periods and cancellation effects.
  • Exact sibling catalogue IDs for schedules, procedures, performed work, contracts, resources and access/audit bindings remain to be pinned as those models mature.
  • The candidate relation to WM-ACT-006 is represented as COMPOSE rather than lifecycle ownership and needs later cross-model harmonization.

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-007-work-order/spec.yaml, ver-cy/world-models/card-supplements/wm-act-007-work-order.json