Maintaining Traceability and Evidence
Use this process to maintain manufacturing facts, individual-item history, and supporting evidence after batches and instances have been registered. The result is an inspectable chain from approved specification through actual production to later events, with measurements and declarations scoped to the correct subjects.
Put each fact in its owning record
| Question | Record |
|---|---|
| What was the approved definition? | Product Release and Product Composition |
| Which factory made this quantity? | Production Batch |
| Which individual item is this? | Product Instance and issuer serial |
| Which actual component was installed? | Component Use |
| What happened and who had custody afterward? | Product Lifecycle Event |
| What was measured on this item? | Instance Observation |
| Which assertion is supported for this scope/period? | Evidence Statement |
| Who holds responsibility in a jurisdiction? | Product Operator Assignment |
| Which company registration was checked? | Company Regulatory Registration |
| Which market/shipping declaration applies? | Trade Declaration or Transport Declaration |
| What is available in the warehouse? | Warehouse Stock Report |
Manufacturing origin, current location, custody, stock ownership, and seller identity can differ. Recording one does not establish the others.
1. Maintain actual component provenance
A Production Manager or authorized delegated production user opens Production → Component Use and records the exact output, actual component source, quantity/unit, position, installation time, and supporting document where applicable.
For a replacement, enter removal time on the earlier use and create a use for the replacement component. Record the applicable lifecycle event. Preserve the old component's provenance. Serialized components cannot have overlapping installations; assembly cycles are rejected.
2. Report and accept events
A user with event-management authority reports the exact batch/instance, type, actual occurrence time, performer, facilities, custodians, and applicable quantity. It starts Pending. Use Lifecycle decision → Accept or Reject, enter a reason, and choose Apply decision.
Inspect effective history afterward. A late report belongs at its actual event time. A partial batch movement does not establish that the whole batch moved. A warehouse receipt does not replace the original factory.
Correct accepted mistakes with a new event identifying Corrects Event and its reason. Repurposing/rebuilding can link an approved resulting configuration while preserving original manufacturing identity.
3. Prepare and review item measurements
An evidence contributor opens Logistic → Quality → Instance Observation for exact item, metric, value/unit, time, method, conditions, and retained source. Submit the draft; an authorized evidence approver checks and approves or rejects it. Product Editors typically contribute, and Product Governance Managers typically review. Production permission alone does not include evidence approval.
Do not store one item's residual capacity or cycle count as nominal Product attributes. Create a later observation for a later measurement; use Supersedes Observation for a correction to the same item/metric.
4. Keep evidence scope and documents accurate
In Logistic → Quality, prepare Evidence Statements for the true release, release-at-factory, batch, or instance and applicable period. Cite exact retained document revision/page. Explain the method and limits in the assertion or report; the current evidence form has no separate Method input.
Apply Submit and obtain evidence approval separately from product approval. Independent verification requires a different verifier, genuine retained evidence, and authority. A sample report is not evidence that each manufactured item was individually tested.
Use Supersedes Evidence for corrections to the same requirement/scope and separate records for different factories or batches. Check audience restrictions on both statements and supporting downloads. Review validity before consumption.
5. Maintain responsibilities and declarations
In Logistic → Compliance, governance staff review operators and company registrations when mandates, contacts, jurisdiction, validity, or responsibility change. Operator assignments and registrations start Pending. Registration Verify requires retained evidence.
Declaration preparers maintain market-specific Trade Declarations and exact-configuration Transport Declarations, then obtain the appropriate approval. Preserve earlier approved records and avoid overlapping competing declarations. A factory address does not automatically establish origin; one shipping pack does not cover every configuration.
6. Inspect affected outputs and refresh consumers
Open the batch or instance and choose Manufacturing traceability to inspect component inputs and affected outputs. Refine results when scope/traversal limits are shown. Absence from a limited result is not proof that another output is unaffected.
Refresh and review affected passport drafts; separately refresh/preflight applicable catalog content. A correction does not silently republish either workflow. Earlier passport publications retain their original snapshots and document checksums.
Reload and compare current facts after a version conflict rather than retrying an obsolete approval. Keep accepted history and retained evidence when operational records become inactive.
Related topics
Component use · Product lifecycle events · Instance observations · Evidence statements · Digital product passports · Warehouse stock reports