2 replies to this topic

[FoodSafetyJunkie]

We are looking at different digital plant management platforms to get away from physical paperwork and binders.  Are there any recommendations on the best one? 

 

We are looking in automating our supplier approval program first and then our SQF system and programs.  The QA plant paperwork/checks will be the last phase.

[tahoeskier]

Protocol Foods is a start up and has some AI technology as well. It is very reasonably priced.

jeff@protocolfoods.com

 

Jeff Sigel is the contact.  Feel free to use me as referral - Quality Smartz Consulting.

[GMO]

I've used a few including the complex and embedded in ERP (SAP) and the simple (I think was a bespoke system).  There are a few bits I learned on the way.

The things to look for are:

 

1. Customisability.  You don't want to be paying a fortune for changes later.  And you WILL realise later there's something you missed.
2. Capturing the name of the person doing checks.  This needs to be secure or at least as secure as paperwork, e.g. card scanner or password (that's obviously NOT shared and autologs out which is why card scan might be better as it's quicker).
3. Logic.  You need any trace logic to be accurate to usage.  I'm going to die on this hill, there is NO WAY to automatically consume (backflush) ingredients or packaging without risking making an error with what really happens on the shop floor.  The only exception would be silos and then "mixing" logic needs to be built in.  Usage and trace needs to be recorded by the team.  They WILL mess up doing this.
4. To the above, realise that you WILL need to do regular stock takes and correct errors for the above.  Ideally daily depending on the size of your operation.
5. Again to the above; understand all of this.  Don't rely on someone else to understand the system or what you might have on paper (e.g. a rock solid looking trace) is actually a load of crap.
6. Ideally make sure it's all future proof and can "talk" to other devices.  I.e. if you have a system to track performance, don't have this completely isolated from that as otherwise you will have short interval control meetings not discussing quality issues.
7. Escalation functionality.  This is really helpful for failed results or incidents.  
8. Security of devices.  You don't want your team watching screening services (or worse, yes, I've been there) on your tablets or screens.
9. Food safety of devices.  Are they cleanable etc.
10. Putting in a system like this is time hungry and needs cross functional involvement even if you're only looking at QFS records for now.  Resource it appropriately and make sure you see lots of systems so you can genuinely choose the best.