A good data collection program is absolutely critical in the food industry. Consumers want to be assured that the food they consume is of the highest quality and that it is safe. Government regulations work towards consumers demands by monitoring the food chain. Think of the common news instances in which a plant has to be closed, all product destroyed and products on the market recalled – all because inspectors could not determine if materials used during an identified period might have found their way into subsequent production days.
It is important to develop a program that protects your company from this situation. Be sure to evaluate your business objectives thoroughly, take an inventory of your current processes, and know what data you need to collect. Then, develop the program in incremental steps to minimize change-affects, maintain manageability, and meet your project goals.
The first steps
So you’ve taken on the task of developing a data collection program. Where do you begin? Start by evaluating your current system. Ask all (and I do mean all) stakeholders what they like and dislike about how information is currently captured. The person closest to the job knows the “ins-and-outs” of the process that may not be documented on paper.
Keep an eye out for ways to uncover all process steps and improve each one. If information on a process is currently being captured on paper, examine each line and ask; “How is this data used? Do we need more information than what we are capturing? Is this ‘nice-to-have’ information, or is it critical?”
Once the complete process is documented, evaluate where you can get the best return on investment. Focus on business-related goals that can be quantified by measurable results.
Here are a few examples:
- Satisfy a customer’s requirement to secure continued business.
- Improve recipe control by tracing ingredient usage.
- Reduce packaging costs by closely monitoring process waste.
- Improve scheduling, leading to a reduction of delays and improved efficiencies.
- Minimize inventories and improve allocations thereby reducing carrying costs.
A few others to consider include:
- Establish operation information, for example, yields or productivity.
- Get quick information access for improved decision making.
- Reduce paperwork in a manual process.
- Collect data for product traceability and recall.
- Meet government or customer requirements.
What information do you collect?
After developing a charter for addressing a specific issue or issues, identify where and how to collect the data. Poorly developed programs tend to collect copious amounts of data, but use only a fraction of it. This can add to costs. Ask yourself: “Is this data needed?”
Click here for a table of commonly gathered data points a food manufacturing process may need to collect. [Link to table]
The more information gathered, the more complex sharing becomes. Keep in mind that collecting common data points once, and sharing with other steps in the process, will reduce errors and costs.
Make an impact
Determine where you can make the biggest impact. You should be looking to fulfill multiple requirements while minimizing investment and providing the foundation for a data collection program that can grow as your business grows.
Consider starting by organizing your data collection to comply with FDA Bioterrorism Act traceability mandates, Country-of-Origin-Labeling (COOL), or the Produce-Traceability-Initiative (PTI).
Then identify the organized data, or report layout, you would like to have and build a “road-map” of data points you must capture to get there.
Can I use existing equipment?
Using legacy equipment will help keep costs down. New systems must be able to communicate with older devices while providing a foundation for future technology. Try to limit devices that require use of proprietary methods.
Be sure to look at your technical partners to ensure suppliers use proven vendors to augment their offerings. Also, make sure they possess a working knowledge of past, present, and future technologies that will allow you to leverage existing equipment.
Seek out vendors and organizations that can support equipment, new and old, and have multiple layers of support and service. This ensures continuity for your data collection project.
Break your implementation into small steps
A larger project should be broken into smaller, measurable and manageable steps or phases. This ensures that any process deviations not uncovered in the initial investigation can be addressed with minimal cost and disruption to the project schedule.
Also, be sure to look for qualified assistance. Seek out companies that can manage the project, provide technical equipment or assistance, and provide valuable resources and insight towards the project, allowing your company to stay focused on the core business.
Perhaps most importantly, communicate all facets of the project to all parties involved, all the time, and often. Good communication can keep distractions from having a negative influence on your schedule and keep everyone focused on task.
How much will it cost?
Costs can range widely, depending on the scope of the project, but can be controlled by implementing the project in steps or phases. Prove-out each phase of the project before proceeding to the next.
Look for systems that use solid, proven technologies while avoiding the cost of user licenses and proprietary software or hardware. Remember – the cost is based on the results of the evaluation during the investigation stage. A solid investigation at the beginning of the project will prevent any unexpected costs at the end.
Data Collection Table
|Time/date information||Origination (farm) code|
Recipe validation, batching, and blending processes
|Time/date information||Lot identification|
|Code dates||Equipment (line ID, tank ID)|
|Verifying recipe integrity|
|Code dates||Lot identification|
|Track controlled ingredients||Costing|
|Monitoring batch cycles|
|Time/date information||Lot identification|
|Equipment (line IDs, tank ID)|
Cooking, smoking and drying cycles
|Time/date||Environmental (temp, pH,)|
|Additives||Equipment (cycle times, pressures)|
|Operator||Equipment (oven ID, tank ID)|
|Time/date information||Equipment (line ID, tank ID)|
|Pallet information||Package information|
|Lot /vat/unit||Barcode type|
|Safe food handling||Establishment information|
|Time/date information||Location (room, rack, level)|
|Package information||Boxing information|
Shipping & Receiving
|Customer ID||Bill of lading (BOL)|
|Route number||Truck number|
|Country of origin||Carrier|