Production & Manufacturing

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.

Dimension & namespace

• EXTEND `world.actAction` (K2): production runs and operations specialize the atomic act with industrial structure
• REFERENCE `world.site` (P5): plants and work centres as sites
• REFERENCE `world.organization` (O1): producing organizations and supply chain partners
• REFERENCE `world.processAndWorkflow` (K3): routings operationalized as executable workflows
• REFERENCE `world.practiceMethodAndProcedure` (K6): work instructions behind routing operations
• REFERENCE `world.planAndSchedule` (K7): production schedules binding runs to time
• imports: isa-95 (ALIGN): manufacturing operations terminology and level model
• imports: gs1 (REFERENCE): identifier schemes for products, lots and locations (GTIN, GLN, SSCC)

Canon, patches & standards

• EXTEND `world.actAction` (K2): production runs and operations specialize the atomic act with industrial structure
• REFERENCE `world.site` (P5): plants and work centres as sites
• REFERENCE `world.organization` (O1): producing organizations and supply chain partners
• REFERENCE `world.processAndWorkflow` (K3): routings operationalized as executable workflows
• REFERENCE `world.practiceMethodAndProcedure` (K6): work instructions behind routing operations
• REFERENCE `world.planAndSchedule` (K7): production schedules binding runs to time
• imports: isa-95 (ALIGN): manufacturing operations terminology and level model
• imports: gs1 (REFERENCE): identifier schemes for products, lots and locations (GTIN, GLN, SSCC)

Artifact formats & serial data

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

Policies & accepted processes

• `traceabilityQuery`: an authorized party traverses lot genealogy from a batch to its inputs and back, without cost or recipe detail
• `productionReporting`: aggregate output and yield are disclosed to a statistics office or supply chain partner per cadence
• `recipeLicense`: a specification, bill of materials and routing are licensed to another producer under the author's terms

Read / add / edit / delete

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

Ownership, roles & access

The producing organization owns its specifications, runs and lot records. Trace, reporting and licensing access is granted by the owner via the catalogue's ownership and access models (S1/S2), with audit via S4.

Objects

• `productSpecification`: the definition of a good; key attributes: name, identifier, required properties, unit of measure, version
• `billOfMaterials`: the component recipe; key attributes: specification reference, component lines with quantities, effectivity
• `routingOperation`: one manufacturing step; key attributes: sequence, work centre, duration standard, instructions reference
• `productionRun`: one execution of a specification; key attributes: order reference, plant reference, planned and actual quantity, start and end
• `batch`: a traceable unit of output; key attributes: lot identifier, quantity, production run reference, expiry or shelf data
• `materialConsumption`: input drawn during a run; key attributes: input lot reference, quantity, operation, time
• `yieldRecord`: the output accounting of a run; key attributes: good quantity, scrap quantity, loss reasons
• `qualityTest`: an inspection of a batch or run; key attributes: test kind, sample, result, disposition

Relationships

• `billOfMaterials` -> specifies -> `productSpecification` (many-to-one): the recipe for the good
• `routingOperation` -> sequencedFor -> `productSpecification` (many-to-one): the ordered making steps
• `productionRun` -> executes -> `productSpecification` (many-to-one): the definition a run realizes
• `productionRun` -> conductedAt -> `site` (many-to-one): the plant where making happened
• `batch` -> producedBy -> `productionRun` (many-to-one): the origin of each traceable lot
• `materialConsumption` -> drewFrom -> `batch` (many-to-one): input lot genealogy
• `qualityTest` -> inspected -> `batch` (many-to-one): quality evidence per lot
• `productionRun` -> performedBy -> `organization` (many-to-one): the producing organization

Events

• `runStarted`: a production run began against a specification and routing
• `operationCompleted`: one routing operation of a run finished
• `materialConsumed`: an input lot was drawn into a run
• `batchProduced`: a traceable output lot came into existence
• `testResultRecorded`: a quality test on a batch or run was concluded
• `runClosed`: a run ended with its yield accounted
• `batchRecalled`: a produced lot was withdrawn after release

Projections

• `genealogyTrace`: the input-to-output lot tree around a batch; omits costs and recipes
• `plantDashboard`: runs, yields and quality by line and shift; omits partner-facing identifiers
• `complianceReport`: quality results and dispositions shaped for oversight; omits commercial quantities