Published

Production Run

vr.wm-act-010 · wm-act-010-production-run

Describe one bounded manufacturing execution that transforms materials into goods, with evidence-qualified inputs, outputs, resources and outcomes.

World Models Activities and processes ACT.PRD

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 · 12 findings · 36 questions

Execution boundary Identity and selected definition evidence.

Run identity and scope

Proposed boundary record separates the occurrence from order, response, lot and record identities. An ongoing or failed attempt is representable without inventing an output.

Recognizable execution boundary

Proposed boundary record separates the occurrence from order, response, lot and record identities. An ongoing or failed attempt is representable without inventing an output.

Which master namespace and identifier distinguish this execution from its order and reports? identity
Which production mode and segmentation rule make this one run? classification
What evidence establishes actual execution rather than only planned intent? evidence

Definition binding

Proposed selection history records what was applicable and what was actually used. A controlled mid-run change creates a new interval or segment; it does not rewrite earlier execution evidence.

Selected definition revisions

Proposed selection history records what was applicable and what was actually used. A controlled mid-run change creates a new interval or segment; it does not rewrite earlier execution evidence.

Which external product, work-master, bill and routing revisions were selected for each segment? relationship
What evidence authorizes the selection or deviation from the intended definition? authority
When did each selected revision apply and what was executed before a change? temporal

Participation and progression Accountability, resource use and observed progression.

Responsibility and resources

Proposed participation ledger distinguishes allocated requirements from actual use. It records responsible roles and resource intervals without acquiring the equipment or personnel master.

Actual resource participation

Proposed participation ledger distinguishes allocated requirements from actual use. It records responsible roles and resource intervals without acquiring the equipment or personnel master.

Which adopting owner and accountable production role govern this run record? ownership
At which site and work centre did each execution segment occur? spatial
Which personnel roles, equipment and assets actually participated and what evidence supports their use? composition

Execution progression

Proposed event history retains the source state vocabulary, occurrence time, observation time and uncertainty. Missing end evidence remains unknown; an imported completion claim is not a quality release.

State and timing evidence

What is the latest evidenced execution state under the selected profile? state
Which actual start, pause, resume and end times are known, estimated or disputed? temporal
How are retries, partial completion and an aborted attempt distinguished from a resumed run? lifecycle

Material transformation Input consumption and output lineage.

Material inputs

Proposed input ledger records consumption, return, sampling and corrections distinctly. Planned bill quantities cannot substitute for observed actuals. Partial consumption does not erase the input lot.

Consumption assertions

Which material identities and granularity identify the consumed inputs? identity
What quantity was consumed or returned on which measurement basis? measurement
Which source records and corrections substantiate each input assertion? provenance

Outputs and genealogy

Proposed output and genealogy assertions preserve incomplete evidence and distinguish possible contribution from measured allocation. Transformations, packaging aggregation and mere movement are different relations. Scrap, byproducts and work in progress are not silently lost.

Transformation evidence graph

Which output identities and output categories were actually observed for this run? composition
What transformation evidence links inputs to outputs and how precise is the claim? relationship
How are split, merged, reworked or unidentified materials represented without double counting? exception

Observations and accounting Qualified measurements and explicit accounting bases.

Measurements and observations

Proposed observation index links run-specific measurements to their methods and conditions. The run has duration and output measures; dimensions and material properties belong to the measured subject, not to an abstract execution identifier.

Qualified process observations

Which property of which subject was measured with what value, unit and uncertainty? measurement
Which method, instrument and conditions qualify the observation? quality
Which criteria revision and acceptance rule were applied without treating missing measurements as passing? validation

Output accounting

Proposed accounting snapshot states the boundary, units, numerator and denominator for every yield. Piece yield and mass balance are not interchangeable; zero or unknown denominators prevent a numeric ratio. Missing flow or rework evidence remains an unresolved balance.

Qualified yield reconciliation

What quantities and accounting boundary define this reported yield? measurement
Which conversions, tolerances and category rules make the totals comparable? constraint
Which residuals, carry-over or repeated rework quantities prevent a reconciled result? exception

Exceptions and quality Deviation history and externally authorized dispositions.

Deviations and interruptions

Proposed exception record links interruptions and deviations to affected segments and policy decisions. Local annotation cannot override a safety interlock, authorize a changed recipe or establish that physical remediation occurred.

Scoped exception history

Which interruption or deviation was observed and which segment or material was affected? event
Which external decision governs continuation, segregation or a changed execution basis? decision
Which unresolved safety or controlled-production restriction blocks an agent action? security

Quality and disposition links

Proposed inspection index retains sample scope, criteria and disposition references separately. An observed pass or a successful production result does not by itself authorize release, sale or recall.

Inspection and release evidence

Which inspection or sample evidence applies to which run outputs? evidence
Who is authorized to make the referenced disposition and what scope was decided? authority
Which outputs remain pending, held or disputed despite production completion? state

Continuity and exchange Record provenance and controlled projections.

Evidence and correction

Proposed correction lineage preserves attribution and distinguishes revision of a record from reversal of the physical transformation. Preserve history subject to lawful retention and access limits, with scoped tombstones after permitted payload disposal.

Record continuity and provenance

Which source and actor made each run assertion and which record revision is being read? provenance
How are duplicate deliveries and conflicting corrections resolved without changing the original claim silently? validation
Which retention, hold and disposal rules govern run evidence and residual references? retention

Controlled exchange

Proposed export projection discloses only authorized run fields and reports mapping losses. Role assignment, read access and export authority are distinct. The local projection operation has no transmission side effect.

Recipient-qualified run projection

Which recipient purpose permits access to which run fields and artifacts? access
How are worker details, confidential recipes and restricted material facts minimized? privacy
Which pinned exchange profile preserves run, order, response and material identities and reports losses? interoperability

Classifiers Filled

Family: World Models
Category: Activities and processes
Entry kind: event
Navigation path: NAV.ACT.PRD
Domain: ACT.PRD
Industry: Cross-industry
Tags: productionrunact.prd
Also called: K8

What it is Filled

An execution occurrence with stable run identity and an explicit temporal and process boundary, represented before completion, while ongoing, or after termination. A planned reservation does not assert that execution happened. The root is the production occurrence, not the order, a recipe, a material lot, a telemetry message or the record describing it. Continuous production needs a declared window and carry-over rules. All hierarchy and functions below are proposed local research design, not executable industrial control.

In scope

Run identity, actual execution boundary, selected definition revisions and accountable roles
Actual resource participation, material transformation, scoped genealogy and unit-aware output accounting
Observed progression, interruption, deviations, inspection and disposition references, record corrections and qualified reporting

Out of scope

Master authoring of product specifications, recipes, bills of materials, routings, orders, schedules, equipment, organizations and material lots
Machine commands, safety interlocks, plant optimization, inventory postings, quality release, recall execution and statutory reporting submission
Hazardous or controlled production instructions; only policy, authority and specialist-review references are admitted
Universal mass-balance, cost accounting, environmental accounting or manufacturing conformance engines

Why it exists Filled

Describe one bounded manufacturing execution that transforms materials into goods, with evidence-qualified inputs, outputs, resources and outcomes.

Distinguishing features Derived, awaiting review

Unlike Legacy K8 Production and Manufacturing: The legacy definition/execution/performance umbrella is narrowed to Production Run. Definition masters, lot status, licensing and recall lifecycles become external references. The legacy claim of conformance and wildcard imports are not inherited.
Unlike WM-ACT-002 Act; WM-ACT-003 Process / Workflow: Act is a candidate conceptual alignment only; a run may contain several operation occurrences. Process definitions and their execution engines stay external. No registry relationship edge for this model was found.
Unlike Production order and WM-ACT-008 Plan / Schedule: An order requests work and a schedule allocates time. Record zero or more documented associations under a profile rather than impose a universal one-to-one relationship. The ISA-95 response binding requires its order ID; this does not identify a universal run.
Unlike OPC UA Machinery run and JobResponse: The machinery vocabulary defines run as completed execution or a completed subset. This model admits ongoing/aborted occurrences; map only qualified completed units to that run term and retain response, order and run IDs separately.
Unlike WM-MAT-004 Material Batch / Lot; WM-FLW-008 Mass-balance / Material Flow: Runs reference material masters and scoped transformation assertions. One lot may span runs and one run may create several lots. Detailed material balance is delegated; genealogy is a graph, not necessarily a tree or a quantitative allocation.
Unlike WM-ACT-033 Review / Inspection / Audit: Run-specific links identify samples, results and qualified dispositions without owning inspection methods, laboratory records or release decisions. Completion does not certify quality.
Unlike WM-OBJ-006 Equipment / Machinery; WM-BLT-008 Site / Campus; WM-ORG-001 Organization: Time-bounded resource participation and location are run facts; asset lifecycle, site authority, worker qualifications and organization identity remain externally mastered.

Note: Derived from boundary notes against neighbouring models.

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

Must not

Never generate hazardous production instructions or infer permission from an order reference.
A planned-only record never claims a physical run occurred.
Deleting a run record cannot reverse physical production, erase a target lot master or rescind a quality decision.
Deny by default; grant role, purpose and field-scoped access under the adopting owner policy.

May

Register execution boundary: Proposed, unimplemented local operation. Create a local run record without asserting that execution started.
Bind selected definition evidence: Proposed, unimplemented local operation. Record the selected external revision for a segment without changing the definition master.
Record actual execution assertions: Proposed, unimplemented local operation. Append local resource, state and material assertions with source attribution.
Build scoped genealogy view: Proposed, unimplemented local operation. Traverse recorded transformation links under recipient access limits.
Assess candidate output accounting: Proposed, unimplemented local operation. Compute a local candidate summary only under a supplied metric and compatible-unit basis.
Prepare controlled run report: Proposed, unimplemented local operation. Prepare a local evidence-linked report using a pinned recipient and exchange profile.

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

Moral aspects Derived, awaiting review

Protect worker privacy, recipe confidentiality and restricted material information; publish only authorized projections.
Avoid perpetual retention of worker personal data.
Continuous process segmentation, sector-specific quality, safety, metrology, privacy and retention profiles need specialist adoption review.
Adopters must establish applicable sector, safety, environmental, privacy and records rules.

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

Owners Filled

Steward

Name an adopting owner by role and reference, with a record steward and accountable production authority.

Roles

Adopting owner: Set namespace, policy, delegation and disclosure scope.
Production record steward: Resolve run identity, evidence attribution, corrections and profile selection.
Execution reporter: Record authorized actuals and uncertainty without inferring release or changing masters.
Quality decision authority: Own external inspection/disposition decisions and their scoped evidence.
Safety authority: Own applicable safety restrictions and escalation rules outside local record functions.
Authorized reviewer: Inspect evidence, mapping losses and residual conflicts under recipient scope.

Links to other meta-models Filled

aligned

WM-ACT-002 - Candidate act alignment only; multi-operation execution is not asserted to be atomic.
OPC UA ISA-95 Job Control 2.00.0 - Map order and response fields through a tested profile; do not equate run and response IDs.
OPC UA Machinery Job Management 1.0.1 - Qualify completed units for its narrower run definition; ongoing occurrence mapping needs an extension.
GS1 EPCIS 2.0 and CBV 2.0 - Map eligible transformation evidence and controlled terms without asserting conformance or exact lineage allocation.
W3C PROV-O - Map the occurrence to Activity and records/materials to distinct Entities with qualified responsibility.

references

WM-ACT-003 - Candidate reference to process definition and routing context; engine and process lifecycle external.
WM-ACT-009 - Candidate reference to governed work instructions and method revisions.
WM-ACT-008 - Candidate schedule context; planned time does not establish actual execution.
WM-MAT-004 - Candidate material lot master binding; consumption and output links do not own lot release or recall.
WM-OBJ-006 - Candidate equipment identity and qualification reference; no machine control.
WM-BLT-008 - Candidate plant and work-centre location binding.
WM-ORG-001 - Candidate producer identity and responsibility reference; no corporate master ownership.
WM-ACT-033 - Candidate inspection evidence reference; results and disposition authority stay external.
WM-FLW-008 - Candidate detailed material balance reference; local yield is a qualified projection only.

neighbor

Legacy K8 Production and Manufacturing - The legacy definition/execution/performance umbrella is narrowed to Production Run. Definition masters, lot status, licensing and recall lifecycles become external references. The legacy claim of conformance and wildcard imports are not inherited.
WM-ACT-002 Act; WM-ACT-003 Process / Workflow - Act is a candidate conceptual alignment only; a run may contain several operation occurrences. Process definitions and their execution engines stay external. No registry relationship edge for this model was found.
Production order and WM-ACT-008 Plan / Schedule - An order requests work and a schedule allocates time. Record zero or more documented associations under a profile rather than impose a universal one-to-one relationship. The ISA-95 response binding requires its order ID; this does not identify a universal run.
OPC UA Machinery run and JobResponse - The machinery vocabulary defines run as completed execution or a completed subset. This model admits ongoing/aborted occurrences; map only qualified completed units to that run term and retain response, order and run IDs separately.
WM-MAT-004 Material Batch / Lot; WM-FLW-008 Mass-balance / Material Flow - Runs reference material masters and scoped transformation assertions. One lot may span runs and one run may create several lots. Detailed material balance is delegated; genealogy is a graph, not necessarily a tree or a quantitative allocation.
WM-ACT-033 Review / Inspection / Audit - Run-specific links identify samples, results and qualified dispositions without owning inspection methods, laboratory records or release decisions. Completion does not certify quality.
WM-OBJ-006 Equipment / Machinery; WM-BLT-008 Site / Campus; WM-ORG-001 Organization - Time-bounded resource participation and location are run facts; asset lifecycle, site authority, worker qualifications and organization identity remain externally mastered.

What else AI and robots need to interact with it Incomplete

Sources Filled

OPC UA for ISA-95 - Part 4: Job Control, 6.3.4 Job Order - OPC Foundation
OPC UA for ISA-95 - Part 4: Job Control, 6.3.5 Job Response - OPC Foundation
OPC UA for Machinery - Part 3: Job Management - OPC Foundation
EPCIS Standard - GS1
Core Business Vocabulary Standard - GS1
PROV-O: The PROV Ontology - World Wide Web Consortium
Enabling the Digital Thread for Smart Manufacturing - National Institute of Standards and Technology
The International System of Units, SI Brochure - Bureau International des Poids et Mesures

Open questions

Complete direct source retrieval, response hashing, version-label reconciliation, licensing and current-applicability review without treating HTTP success as substantive verification.
Develop executable profiles and fixtures for planned-only records, abort without output, multi-definition segments, continuous carry-over, partial input consumption, rework, restricted lineage and disputed release evidence.
Restore independent external review and qualified adoption testing before any canonical or publishable-draft promotion.
Independent external review absent; local Codex audit is not a second provider.
Direct HTTP and byte-level source/version verification unattempted under owner-reported sandbox block; coordinator checker required.
Executable nested instance schemas, mapping code, vocabulary/state conformance and adversarial fixtures not implemented.
Continuous process segmentation, sector-specific quality, safety, metrology, privacy and retention profiles need specialist adoption review.
No full ISA-95/IEC 62264 or ISO quality certification claimed; evidence is limited to the accessible cited sections.

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-010-production-run/spec.yaml