
Give each identifier a clear meaning before building a report. A part number, a tray position and a unique physical unit can be related, but they are not interchangeable references.
Describe the entities separately
Write down what identifies the part design, production batch, physical position and inspection run. Establish whether individual unit identity exists in the process. Do not create an apparent serial number that users later mistake for a permanent mark on the part.
Define the relationships
Explain how a run refers to the inspected item and the setup used. Consider what happens when a part is inspected again or moved to another tray. The record should preserve enough context to distinguish a new observation from a duplicate transfer.
Agree formatting and ownership
Name the system that creates each reference and the team responsible for its rules. Review collisions, missing values and changes to formatting with the receiving application owner. Keep these decisions in the interface specification rather than scattered across informal messages.
Test retrieval with a realistic question
Ask someone to locate the result for an identified item and explain what the record proves. Our inspection data integration guide connects identifiers to the rest of the data flow.
Frequently asked questions
Is a part number enough to identify one physical item?
A part number usually identifies a design or type. Establish separately whether the process tracks individual units.
How should a repeat inspection be distinguished?
Define an inspection-run reference and its relationship to the item so a new observation is not confused with a duplicate message.
Who should decide identifier formats?
The teams responsible for the source process and receiving systems should agree the meaning, format and ownership together.