Yüklənir

Production and Traceability

Traceability connects an approved definition to manufactured quantities, individual items, actual components, and later events.

Record What it identifies
Production Batch A manufactured quantity of a particular release, with actual manufacturer, factory and production period.
Product Instance One physical item, normally linked to its release and batch and distinguished by its serial number.
Component Use The component batches, individual components or material sources actually used in an output.
Product Lifecycle Event An event such as manufacture, inspection, transfer, service or recycling.

The batch supplies common manufacturing information. The instance supplies individual identity. Component use supplies actual assembly provenance. Accepted lifecycle events supply later history, such as location, custody, and service.

These registers share relationships rather than copying the whole product definition into every row. A batch refers to its approved release; an instance refers to its original release and known batch. The factory belongs to the actual batch's manufacturing provenance. Component use and events refer to the exact output or subject they describe.

Practical example

Two factories can make batches of the same release. Their outputs share a technical definition but retain different factories and production dates. If a component batch is questioned, actual component-use records help identify affected outputs. Shipping those outputs to a warehouse changes their current location while preserving the manufacturing facts.

Who records the work?

Authorized Production Managers maintain these records in Logistic → Production. A contractor needs the appropriate company authority or accepted delegation. Company Administrators arrange access; a confirmed facility relationship alone does not authorize production commands.

New preparation selects Published concrete company products through Product Overview after choosing an associated Manufacturer/Brand Owner product-level category. Use its paging, attribute filters and Select items rather than searching the complete product database. Approved definitions are maintained in Definitions, measurements/evidence in Quality, and applicable operator/declaration information in Compliance.

Use a released product definition and applicable approved factory relationship when releasing a batch. Register instances from the correct released batch and numbering policy. Report actual component use and lifecycle events with their effective time, source, and evidence. Search and inspect the result after saving.

You need individual instances when you must identify individual items, including an Item-level passport. A Model passport or Batch passport can be prepared without registering unnecessary serials. Component use and events are maintained when applicable facts need to be traced; an empty optional register is not itself a failed passport requirement.

If provenance is unknown, keep the absence explicit in supported import/application workflows. Do not invent a batch, factory, date, or serial to make a passport look complete. A late report should preserve its true event time; it must not be presented as a newer physical event simply because it was entered later.