Process Control System (PCS): Definition, DCS vs. MES

What is a Process Control System (PCS)?

A Process Control System (PCS) is an industrial automation platform that continuously monitors, regulates and controls a physical production process in real time. It sits at Level 2 of the ISA-95 automation pyramid, between field instrumentation (sensors, actuators, PLCs) and manufacturing operations (MES, ERP), and keeps process variables like temperature, pressure, flow, level and concentration inside defined setpoints.

In continuous and batch industries such as chemicals, food and beverage, pharma packaging, pulp and paper or refining, the PCS is the system that actually runs the plant. Closed-loop controllers adjust valves, pumps and heaters thousands of times per second so a reactor stays at 82.5 °C or a filling line hits its fill weight tolerance.

Large, plant-wide installations are usually called a Distributed Control System (DCS). A DCS is a specific architecture of PCS: controllers are distributed across the plant, connected via a redundant process bus to engineering and operator stations. The terms PCS and DCS are often used interchangeably, but DCS typically implies redundancy, hot-standby controllers and a unified engineering environment for continuous and batch logic.

A PCS keeps the process running safely. A Manufacturing Execution System decides what to run, tracks how well it ran and closes the loop to the business. Both layers are needed, and the value of a modern cloud MES like SYMESTIC grows the moment it is fed with clean PCS signals.

PCS vs. SCADA vs. MES vs. ERP

PCS, SCADA, MES and ERP are often thrown into the same sentence, but they sit on different floors of the automation stack and solve different problems.

The quick rule of thumb: SCADA watches, PCS controls, MES orchestrates. SCADA can exist without closed-loop control. PCS cannot, because control is its reason to exist.

Core components of a PCS

A modern PCS is not a single product but an integrated set of hardware and software layers engineered for availability, determinism and operator safety.

Two principles shape every serious PCS deployment: redundancy (controllers, networks and power are duplicated to eliminate single points of failure) and segregation (the safety system runs on its own controllers per IEC 61511, never on the basic process control layer).

How a PCS connects to the MES

A PCS is designed to keep the process stable, not to answer business questions like "What was the OEE on line 3 last night?" or "Which batch contained raw material lot 4711?" Those answers live in the MES, and they need data the PCS already owns.

The connection between PCS and MES usually runs along three data paths:

The recommended interface is OPC UA. It is vendor-neutral, tunnels through firewalls, supports authentication and certificates, and is natively supported by every major DCS (Siemens PCS neo, ABB 800xA, Emerson DeltaV, Honeywell Experion) as well as the SYMESTIC Cloud Gateway. For brownfield plants with older controllers, an edge gateway bridges PROFIBUS or proprietary protocols into OPC UA without touching the PCS configuration.

At Brita, for example, digital machine signals and OPC UA alarms from modern lines are pulled into SYMESTIC to capture true output and downtime reasons. The PCS keeps running the filling process; the MES turns its data into KPIs that shift leaders and plant management act on the next morning.

What a modern PCS deployment looks like in practice

Most PCS projects fall into one of three scenarios. Knowing which one you are in decides the integration strategy far more than any vendor slide deck.

The brownfield path is where cloud MES earns its keep. We connect SYMESTIC to a 15-year-old PCS without touching a single function block, without re-validating anything and without new cabinet hardware inside the control room. Two to four hours per machine, a few OPC UA subscriptions, and the plant has the same real-time transparency a greenfield line gets out of the box.

FAQ

Is a PCS the same as a DCS?
Practically yes, with a nuance. DCS (Distributed Control System) describes a specific architecture with distributed, often redundant controllers and a unified engineering environment. Every DCS is a PCS; not every PCS is marketed as a DCS. Siemens PCS 7/PCS neo, ABB 800xA, Emerson DeltaV, Honeywell Experion and Yokogawa CENTUM are all DCS products used as the process control system of a plant.

Do I need a PCS if I already have PLCs and SCADA?
For discrete manufacturing, usually no. PLCs plus SCADA cover most automotive, metal working and assembly use cases. For continuous or batch process industries (chemicals, food, beverage, pharma, pulp), a PCS is standard because you need ISA-88 batch logic, tight closed-loop control, safety integration per IEC 61511 and engineered redundancy that generic PLC+SCADA stacks do not provide cleanly.

Can a cloud MES replace a PCS?
No, and it should not try. A PCS controls the process in milliseconds and must run deterministically, often with SIL-rated safety functions. A cloud MES like SYMESTIC lives one layer above, consuming PCS data to manage orders, OEE, batch genealogy and process data analytics. The two systems solve different problems and are designed for different failure modes.

What is the fastest way to get PCS data into an MES?
Expose an OPC UA server on the PCS (all modern DCS products support this natively), define the tags you need for counts, states and key process values, and subscribe from the MES gateway. In a typical SYMESTIC project this takes a day of configuration once the tag list is agreed. For older PCS versions without OPC UA, an edge gateway translates the native protocol read-only, so the PCS project and its validation stay untouched.

Related: SCADA · OPC UA · ISA-95 · MES · Process Data · Alarms

About the author

Martin Brandel

MES Consultant at SYMESTIC. 30+ years in industrial automation, including process control systems for beverage and wood-processing plants, Simatic S5/S7/TIA retrofits and OPC UA integration of brownfield DCS installations. · LinkedIn