Traceability
Complete material and process traceability – goods in to goods out
The minimum requirement of a solution, in order to provide traceability is that all batches which enter, are stored
within, or leave a site are uniquely identified, and that the relationship between each ID is stored in a retrievable
manner. This means that if a batch with an ID of "A" is split into 2 batches "B" and "C", the solution should make
it possible for an operator to query the solution about batch "C" and know that it came from batch "A" and that
"B" was created from "A" and is a sibling of "C".
This section discusses functionality which exceeds this "required minimum", but which is also considered under the term "Traceability". This additional functionality is included as it provides customers with additional benefits that are provided as a by-product of introducing traceability. Traceability is not in its own right a desirable piece of functionality, but simply a way of complying with new legislation. It is, therefore, important to consider additional functionality which will add value to the overall solution.
In order to trace a batch from the supply chain back to inbound raw materials requires that all batches are identified at point of goods inwards and tracked through the customer site to point of dispatch.
Traceability Main Features:
- Tracking of raw ingredients from delivery to site to dispatch as finished product
- Manipulation of end product shelf life calculation as a result of tracked ingredient quality
- Ability to report on all end products containing ingredients from an identified delivery
- Tracking of time a product or raw ingredient spends in un-chilled transit between specified locations
- Identification of ingredients which have exceeded a defined life with the site, and cannot be used for final product
- Tracking of valuable, critical or hazardous substances in and out of storage
A central database is used to store and analyse all of the corresponding data, while remote terminals (using fixed or wireless scanning/control devices) are used to track materials in and out of each stage of production.
Downtime is kept to a minimum, since a new terminal can be started up and configured in minutes, or an existing wireless terminal used in its place until a new terminal is installed.
The resulting final material can then be scanned into production, and the batch code carried through to the AutoCoding Line control system, where it can be coded onto the primary, secondary and tertiary packaging before dispatch.
Product Recalls
A product recall is initiated at some point downstream of the customer in the supply chain, and could be caused by one of the following reasons:1. The finished product is of substandard quality.
2. The finished product is incorrectly coded.
3. The finished product is contaminated with foreign matter.
4. The finished product is incorrectly packaged.
The customer must be notified of the need to recall finished product from the supply chain and given details of the batch identification, SSCC number or product coding data on the finished goods or logistics units found to be at fault.
The product coding data must include Production/Packaging line ID, Production Date and product code, but could also include the Batch ID if coding space permitted the coding of the ID onto the finished goods. The customer should benefit from the ability to limit the amount of finished product which needs to be recalled, by acquiring a finite list of effected product.
The customer should also benefit from been able to supply the supply chain with a distinct list of effected SSCC codes and Product coding data details to be removed from the supply chain.
Batch Recall/Discard Check
Once a contaminated batch is identified by the customer or via the downstream supply chain, the customer must
determine the extent of the recall/discard.
This involved determining 2 key parameters:
1. The first process at which contaminated batches where detectable.
2. All batch ID's which are descendents of the process identified above.