If a question arises about a part or shipment, it should be possible to connect it to relevant records: material, drawing revision, manufacturing stages, and inspection results. This connection helps define the scope of a nonconformity review.

Monitoring examines process status and trends; traceability concerns product identity and connections among its records. To use either, it must be clear what data are recorded, what they mean, and which decision they will support.

Traceability Begins with Identifiers and Linked Records

The GS1 framework links critical events in a product's journey to the data describing them; receiving, packing, and shipping are examples of such events. [1] For a production order, define the stages to be traced and the data required at each stage from the outset.

An identifier should connect to a retrievable history. It may refer to a melt, production batch, container, order, or individual part; these levels are not equivalent. If parts are mixed or divided from one container into several, also define how their link to prior history is preserved.

Which Records Need to Be Connected?

The table below is a discussion template for defining project needs; it does not prescribe a fixed implementation scope for every order.

RecordHow It Supports Product Review
Part specification and revisionIdentifies the design and requirements valid during production
Material and linked melt codeProvides access to data and review results for the material used
Production period and resourcesNarrows the investigation to relevant time and conditions
Inspection result and acceptance statusShows the recorded disposition of the product
Shipment and deliveryConnects shipped product to its previous records

For example, recording a production date without being able to connect it to the container or shipment in question may not provide a sufficient answer. The identification method should account for handling, separation, finishing operations, and packaging; wherever the link is lost, follow-up becomes more difficult.

  1. 1Material and melt identifier
  2. 2Order and process revision
  3. 3Production records
  4. 4Inspection results
  5. 5Packing and shipping
  6. 6Follow-up and corrective action
Educational view of the decision path; return to earlier stages when refinement is needed. The actual linkage level among these records must be defined for each project.Original diagram based on the stages described in this article.

Monitoring Must Link to a Defined Question and Response

Every data item should have a defined use. Production count, downtime, inspection result, and machine condition provide different information. Define the meaning, unit, recording time, and person responsible for responding so comparisons among shifts and orders are meaningful.

Displaying a trend is not automatically statistical process control (SPC). A control chart requires a method and statistical rules for interpreting variation. Control limits describe process behavior; specification limits express acceptance requirements for a product characteristic. NIST explains this distinction in its discussion of control charts and process-capability assessment. [2][4] A stable chart therefore does not prove that every part conforms. Product decisions should be based on the criteria and controls defined for that part.

When a Nonconformity Appears, Review Records Alongside the Part

A review begins with a clear problem definition: which characteristic fails which criterion, and how are the parts in question identified? Relevant records are then examined to clarify investigation scope, the status of available product, and required action. The outcome should remain linked to the decision owner and product-acceptance status.

Two events occurring at the same time do not by themselves prove causation. A change in process data alongside a nonconforming result, for example, creates an investigation question; a conclusion requires review of evidence, measurement conditions, and other influential factors. The method for checking corrective-action effectiveness should also be defined.

Production-information recording system from the company archiveImage source: Novin Industrial Group archive

Preserve Data Quality and the Controlled Revision

In research by Hedberg and colleagues, a graph-based method for linking design, manufacturing, and quality data was tested. [3] For a production order, the practical question is whether an inspection report can be linked to the drawing revision and manufacturing records that were valid at the time of production.

Also define how incomplete or incorrect data will be corrected. The recorder, reviewer, and change history should be known. Connections among files and identifiers require maintenance; collecting information in one software system does not by itself prove that the links are complete.

State Traceability Needs in the Project Request

State the required traceability level, report contents, and retention period in the RFQ. Define which identifier should retrieve the history and what information is needed at delivery. Customer access and report format should also be agreed.

Novin Industrial Group retains selected production and inspection records for order follow-up and quality review. The report details available are defined during the technical review of each order. See the Laboratory & Quality Control page for related stages, or state the order requirement through Start a Project .

Traceable-Records Checklist

  • Define the required traceability level: part, batch, container, or shipment.
  • Define how identification is preserved through finishing and packaging.
  • Link the controlled drawing revision and specification to the record.
  • Identify required data and who records and reviews them.
  • Record acceptance status and disposition of nonconforming product.
  • Agree on the available report and record-retention period.

Frequently Asked Questions

Does traceability mean every part must have an individual number?

Not necessarily. Traceability may operate at part, batch, container, or shipment level. The required level and method of linking it to records should be defined for the application and project requirements.

Does an online chart show that every part conforms?

A chart presents data about the monitored status or trend. Product acceptance still depends on the criteria, controls, and decisions defined for the part.

What should we specify when requesting a traceability report?

State the lookup identifier, required information, report format, delivery timing, and retention period. The project reviewer can clarify feasibility and the committable scope.

References and Further Reading

  1. GS1 — What is the GS1 Traceability Standard? ↗Critical traceability events and the key data associated with them.
  2. NIST/SEMATECH e-Handbook — What are Control Charts? ↗Use of control charts to examine process variation.
  3. Hedberg, T. D.; Bajaj, M.; Camelio, J. A. (2019 online) — Using graphs to link data across the product lifecycle for enabling smart manufacturing digital threads ↗Research method for linking design, manufacturing, and quality data across the product lifecycle.2019 · DOI: 10.1115/1.4044921
  4. NIST/SEMATECH e-Handbook — What is Process Capability? ↗Comparison of stable process variation with product specification limits.

Define the Order's Reporting Requirements

State the required level of tracking and reporting at order start. The feasible scope and available records should be defined in the technical review and project agreement.

View the Related Capability → Send Project Information and Start a Review

Related Articles

From Prototype to Series-Production ApprovalCommon Die-Casting Defects: Causes and InvestigationWhat Information Should You Prepare for a Production RFQ?

Back to All Insights →