There are several key differences between automation solution and enterprise integration projects; the latter have several challenges that can be daunting for companies that aren't aware of the scope and testing required.
Alarms keep production running smoothly and safely, but how can you cut through the clutter and respond in an effective way?
Alarms are a critical part of every production process — but not all of them are created equal. An alarm could indicate an immediate source of pressing concern. It could flag a potentially damaging machine or process issue that could derail production and cause serious safety concerns. However, with alarms sounding all the time and from all directions, it’s easy for even the most experienced operator to get overwhelmed and miss critical corrective action steps.
In my last discussion on OEE I mentioned that when I’m asked the question “where should I get started with improvements on the shop floor?” I usually answer that OEE is the best place to start.
I recently sat down with an automation manager responsible for a subsection of a large manufacturing business. His company is embarking on an effort to standardize the use of process control narratives for all automation projects. To my surprise, the concept of process narratives was new to him. He didn't understand their purpose. But he was intrigued and asked many good questions I was happy to answer.
When I’m asked the question, “Where should I get started with improvements on the shop floor?” there is not necessarily an easy answer. There are lots of places to start and it can be very complicated.
Everybody makes a wrong turn now and then on a project. Most of the time you can correct the wrong turn and get the project back on track pretty easily. Sometimes it’s a lot harder to get the project back on track and sometimes the project can’t be recovered at all.