What this category covers
This is the system layer above individual instruments: the controllers that execute logic, the I/O that collects field signals, the isolators and converters that let dissimilar systems talk, and the communication devices that carry the data. Where a single panel indicator belongs to Process Instrumentation, a rack of I/O modules belongs here, and the boundary is instrument level against system level.
Selection in this category is dominated by compatibility rather than by performance. The hardware has to fit an existing control platform, an existing network and an existing engineering workflow, and a technically superior device that does not do that is not a candidate. That is why the first question is almost always what is already installed rather than what is required.
The second constraint is lifecycle. Control hardware is installed for a decade or more and is maintained by people who were not present at commissioning, so documentation, spares availability and the programming environment matter as much as the specification sheet. A protocol named on a datasheet is a promise about interoperability, and it is worth confirming what it means for the specific platform rather than assuming.
Product types in industrial automation & control
| Product type | What it does | Usually specified for |
| PLC system | Executes deterministic logic and control loops on field inputs and outputs, with its own programming environment | Machine and process control where the sequence, the interlocks and the logic live in one place |
| PID controller | Compares a measurement against a setpoint and drives an output to close a single loop | Standalone loops, panel-mounted control and backup of a loop that the main system also handles |
| Signal isolator | Separates two circuits galvanically so that a ground loop cannot carry interference between them | Protecting an input card and breaking a ground loop between field and control system |
| Signal converter | Translates one signal form into another so that two devices with different interfaces can work together | Fitting a field device to an input that expects a different signal, and re-ranging without changing the sensor |
| Remote I/O | Moves the input and output points close to the field and communicates them back over a network | Distributed plants where long cable runs to a central cabinet are impractical or expensive |
| Industrial communication device | Routes, converts or repeats industrial network traffic between segments | Building the network itself, and joining segments that were installed at different times |
| Modbus device | Exchanges register-based data over serial or TCP links using a widely implemented protocol | Connecting instruments and meters to a controller or a supervisory system where simplicity matters |
| Industrial Ethernet device | Carries deterministic or standard Ethernet traffic on the plant network | Plant networks where several protocols and higher data volumes have to coexist |
Control modules and automation accessories are listed under this category as well.
How to choose a control system
There is rarely a single correct instrument for a duty, but there is always a
shortlist that can be justified and a set of answers that eliminates the rest. These
are the questions that decide it.
- What is already installed, first. The existing platform, network and engineering tools decide more of the answer here than the specification does anywhere else in this catalogue.
- The I/O count and type required: digital, analogue, temperature or high-speed inputs, together with the spare capacity the site expects to grow into.
- The protocol and the topology the plant already runs, since a device that speaks a different one adds a gateway and a maintenance obligation.
- Whether the control has to keep running through a fault, which introduces redundancy, watchdog behaviour and fail-safe action as requirements.
- The mounting and environment: DIN rail or rack format, cabinet or field, ambient rating, vibration and any hazardous-area requirement.
- The engineering environment: programming software, licence terms, and whether the site team can maintain the code rather than depend on an outside contractor.
- Documentation and language, including the drawings, manuals and the language the maintenance team actually works in.
- Lifecycle and spares: whether the platform will still be supported and supplied for the life of the plant, and what the lead time is for a replacement module.
- Whether the requirement is a new installation or an extension of an existing one, because extension brings compatibility constraints that a new build does not have.
Working through the selection in order
- Establish what is already installed: the platform, the network, the protocol and the engineering software in use.
- Write down the I/O count and type, including spare capacity rather than only what is needed today.
- Decide where the I/O has to sit physically - central cabinet or distributed near the field - since that shapes the architecture.
- Choose the protocol and topology with the network design in mind, not as an afterthought to the controller choice.
- Set the availability requirement: whether the process can stop, and what the control has to do if a module or a link fails.
- Confirm the environment, the mounting and the area classification at every point the hardware is installed.
- Check the engineering and documentation requirements against what the site team can actually maintain.
- Confirm lifecycle, spares and the lead time for replacement modules before committing to a platform.
Comparing the technologies
| Element | Best suited to | Limits | What it decides |
| Compact PLC | Machine-level control with an I/O count that can be fixed at the outset | Expansion is limited by the platform, so later additions may force replacement rather than extension | Logic, sequencing and interlocks |
| Modular PLC with remote I/O | Plant-level control where I/O is distributed near the field devices | Needs a network design, and the chosen protocol decides what can be distributed and at what distance | Distributed control architecture |
| Standalone PID controller | A single loop, or a loop that has to keep running when the main system does not | Panels space and faceplate conventions, plus limited logic beyond the loop itself | One control loop |
| Signal isolator | Breaking ground loops and protecting an input card from field transients | Adds a conversion step, and the isolation class has to match the installation rather than be assumed | Signal integrity between circuits |
| Signal converter | Making two devices with different interfaces work together | Its own accuracy and drift enter the measurement chain, so it is part of the uncertainty rather than outside it | Compatibility between devices |
| Protocol gateway | Joining two networks that do not share a protocol | The mapping has to be configured and maintained, and diagnostics across the boundary are usually limited | Interoperability between networks |
Parameters to confirm before ordering
What is left after the technology is chosen is a list of values that only the
installation can supply. These are the ones that change the model, the price or the
lead time:
- The platform already installed, and whether the requirement is an extension of it or a new installation.
- The I/O count and type, with the spare capacity the project expects.
- The protocol and topology the plant runs, and whether any gateway or conversion is required.
- The control function itself: sequence, interlock, loop control, or a combination.
- The availability requirement, including what the system has to do if a part of it fails.
- Mounting, cabinet space and the environment at each location, including any area classification.
- The programming and engineering software expected, and who will maintain the application.
- Documentation requirements and the language the site works in.
- Lifecycle expectations and the spares arrangement, including the modules the site wants to hold in stock.
- Any standard the installation has to satisfy, and whether the end customer has an approved-vendor list.
Figures are quoted, not assumed
Specifications vary by model and application, so no performance figure is stated on
this page. Where a parameter has not been documented for a particular model, the
product page says so rather than filling the gap with a plausible number. Send the
values above and we will return the ones the selected model actually holds.
Where these instruments are used