A connected record for every product journeyIdentity / Events / Evidence

TraceGrid / Product information

Field notes for connected product data.

Three short product-data principles illustrated by the fictional TraceGrid demonstration.

Keep the original reference

A material lot may acquire an internal code during receipt. Preserve the supplier code and its issuer context so the record can still answer a question raised using the original reference.

In the sample journey, AL-2048 remains connected to the production run and output batches after manufacturing.

Record the relationship, not just the status

A completed production run is an activity. Its genealogy also needs the relationship between consumed inputs and created outputs. A status alone cannot show which downstream batches use a suspect input.

Show evidence gaps precisely

A delivery event can be recorded before the signed receipt is reviewed. State what exists and what remains pending. A general success badge can conceal the difference.

Inspect the sample event record and select the receiving step to see this distinction.