Controls: PLC, HMI, IPC

The layer everything else depends on. Platform selection, migration off obsolete controllers, code standards, and whether what gets installed is supportable after the integrator leaves.

What lives in this layer

This is ISA-95 Level 1-2: the controllers that run the machine, the operator screens that sit on it, and the industrial PCs that host anything the controller cannot. In North American plants that usually means Allen-Bradley ControlLogix and CompactLogix programmed in Studio 5000, with a long tail of PLC-5, SLC 500 and MicroLogix still in production. Siemens S7-1500 and S7-1200 in TIA Portal are common on European-built equipment, often alongside older S7-300 and S7-400 racks. At the operator level it is PanelView terminals running FactoryTalk View ME, Siemens Comfort panels, and industrial PCs running whatever visualization the OEM shipped with the machine.

Naming the layer matters, because the most expensive mistakes in modernization come from solving a problem at the wrong level of the stack. A data problem is rarely fixed by replacing a PLC, and an obsolete PLC is never fixed by adding a dashboard above it.

The problems we see most

Obsolete hardware on critical lines. The controller runs fine until it faults, and then the plant learns the processor is discontinued, the spare on the shelf has a different firmware revision, and the aftermarket price has tripled. The risk was visible for years. Nobody owned it.

Code nobody can maintain. Programs written by four integrators over twenty years, each with its own conventions, undocumented rungs, and logic that only works because of a timer someone tuned at startup. The machine runs, but every change is a gamble and troubleshooting depends on one person.

No version control. The program in the controller, the copy on the engineering laptop and the copy on the server are three different files. When something breaks after a change, there is no reliable way to tell what changed.

HMIs that hide the process. Screens that copy the panel layout of the original pushbuttons, alarms that fire constantly and get ignored, and terminals that are themselves on an obsolete platform.

The decisions this layer forces

Which platform. Our position: the platform the plant can support is usually the right one. If your maintenance team, spares and integrator base are built on Rockwell, standardize on Rockwell. If you run Siemens across the site, do not introduce a second platform to save money on one line. Mixed platforms double the training, spares and software cost for the life of the equipment.

Migrate or hold. Not every obsolete controller needs to move this year. We rank them by consequence of failure, spare availability and how much else depends on them. Some get replaced, some get a spares strategy, and some get left alone deliberately.

Convert or rewrite. Converting old logic preserves known behaviour and carries its problems forward. Rewriting fixes the structure and adds commissioning risk. We decide per machine, and we write the answer into the scope so the integrator cannot pick the cheaper option quietly.

Standards before projects. A code and HMI standard written after three projects have shipped is a document nobody follows. It has to exist before the first purchase order.

How it connects to the rest of the stack

Everything above this layer reads from it. SCADA and historians poll these controllers, plant data and MES and batch depend on the tags they expose, and the OT network is what carries that traffic. Below, the controller talks to edge devices and I/O, including legacy fieldbus like DeviceNet. How a controller scans and how a supervisory system polls it decides what data is actually trustworthy; we cover that in PLC scan cycles and SCADA polling.

Where Joltek helps

We plan and oversee PLC migration and broader control system modernization, starting with a plant systems assessment that records what is installed, what version it is on and what depends on it. As owner’s engineer we write the scope and acceptance criteria, review code and design before commissioning, and stay through commissioning support. For background, read our guides to PLC platform migration and SLC 500 migration.

Going deeper on a platform

Rockwell Automation is the platform most of this layer runs on in North America. The Rockwell Automation technology cluster covers the company, the Allen-Bradley and FactoryTalk portfolio, and the lifecycle model that decides when a plant has to move, with six system families broken down to the technical detail: programmable controllers, programming software, HMI and visualization, drives and motion, networks and FactoryTalk software.

Platform position

Vendor-independent, but not opinion-neutral. When one platform is clearly better for a given situation, we will say which and why. When the honest answer is that the existing controller is fine and the money is better spent elsewhere, that is the recommendation.