By Tony Parker, PE, PMP, senior project manager, Polytron
A large global brand snack baker suffered excessive production losses and inferior financials at one plant for far too long. Low yield, poor dough quality and unplanned downtime all were created by the problematic batch control system for its 12 mixing stations and ingredient delivery systems.
To complicate things, the existing code was inaccessible and “locked-down” as a precaution of the proprietary software. Frustration mounted daily as everyone knew what the problem was, but recognized the implications of untangling it while maintaining the business’ pace. Undue stress, worry and weak performance eventually brought management to its knees.
Do Nothing or Do Something?
They seemed to have only two options. One, do nothing and continue to suffer the ills of the aging system, poor production, inefficiency “tax” and lack of flexibility to upgrade. Two, shut down each of the 12 mixing stations one by one over a long and drawn-out transition period, replacing and testing code in each of the 14 individual programmable automation controllers (PACs) and hope, after several months of change, that production for the entire plant would improve.
The Third Option
But what if there were a third option? What if all the code for the 14 PACs, all the human-machine interface (HMI) stations and a new batch management solution could be written and tested on a running system — offline?