Biotechnology has been growing exponentially across all segments of the industry. It is estimated that the global market will command $727.1 Billion USD by 2025.
ToxSorb’s project objective was ambitious: Design a cost-effective, high quality chemistry control sequence while managing the full process, from design to commissioning, in-house. And the kicker? With no in-house control engineers, ToxSorb’s process engineers would have to do it all.
Unilever faced many challenges when it came time to replace and upgrade the PLCs in their critical water softening system, from obsolete technology, to compatibility issues, to lack of system documentation.
The biotech industry is filled with educated and innovative professionals. And with the stakes in terms of human life and capital investment so high, who better to take control of automation requirements for their industry than the scientists who built the biotech industry?
A key challenge for biotech companies is the progression from research to scale production. There are a number of reasons biotech companies find it challenging to industrialize, but all of them can be overcome with the right automation partner.
Consistent methodology within complex systems is all around us. And finding a methodology for developing and programming software for PLCs shouldn’t be an exception.
PLC code is much more about software than it is about electrical engineering. In fact, the root cause of many industrial control system failures and incidents lies in failure to understand that we are dealing with software.
Control engineers have been coding PLCs the same way for a long (long) time. With the arrival of younger engineers and the spread of Industry 4.0, we’re finally on the verge of real change.
There is a serious disconnect between process and control engineering. Improving knowledge transfer between the two disciplines would have a measurable effect on efficiency, safety, and productivity.
Industrial safety has come a long way in the last forty years but further improvement is still needed. For instance, programming flaw accounted for 20% of the root causes of processing accidents!