Programmable Logic Controller, PLC
A programmable logic controller, PLC is a ruggedized industrial computer that scans inputs, executes user logic, and updates outputs on a fixed deterministic cycle, typically 1 to 50 milliseconds. PLCs dominate machine control, batch operations, packaging lines, water treatment, and skid-mounted process equipment.
Read one of your own drawings.
Drop a P&ID, instrument index, or schedule. Tagsight reads it to the tag and opens a workspace you keep when you sign in.
PDF · DWG · DXF · TIFF · PNG · XLSX
Bedford Associates and Dick Morley shipped the first PLC, the Modicon 084, in 1969 to replace the relay panels then used on General Motors assembly lines. The architecture, scan every input, execute the control program, write every output, repeat, is unchanged in 2026 platforms. What changed is scale, language diversity, and connectivity. A modern Rockwell ControlLogix or Siemens S7-1500 rack runs structured-text math, communicates over Profinet or EtherNet/IP to remote I/O and variable-frequency drives, bridges to historians over OPC UA, and simultaneously executes IEC 61131-3 sequential function chart batch phases. PLCs differ from a DCS primarily in architecture. A PLC is a standalone controller assembled with third-party HMI, historian, and alarm tools. A DCS comes as an integrated vendor stack. Many large facilities run both. DCS on the main process units, PLCs on skid packages, compressors, air separation units, packaged heat exchangers that arrive with their own controller from the skid vendor. The I/O list captures every signal regardless of which system it terminates in, and the PLC, DCS split is carried as a system-flag column.
Anatomy of a PLC scan.
Every cycle. Read all inputs, execute the user program top to bottom, write all outputs. Cycle time runs from sub-millisecond on small PLCs to tens of milliseconds on large rack-mounted systems. The deterministic cycle is what makes PLCs suitable for safety-relevant interlock logic. Worst-case response time is computable from the cycle time and the logic length. IEC 61131-3, first ratified in 1993 and revised most recently as IEC 61131-3. 2013, codifies the five PLC programming languages. Ladder diagram, function block diagram, structured text, instruction list, and sequential function chart.
Major PLC platforms.
Allen-Bradley, Rockwell ControlLogix, CompactLogix, and the legacy PLC-5, SLC-500. Siemens SIMATIC S7, S7-1200 for small machine control, S7-1500 for line-level and process. Schneider Electric Modicon, the original line, still maintained. Mitsubishi MELSEC iQ-R and iQ-F. Omron Sysmac NX, NJ. B&R Automation X20. Each has its own programming environment, Studio 5000, TIA Portal, EcoStruxure Control Expert, GX Works, Sysmac Studio, its own tag-database structure, and its own preferred fieldbus, EtherNet/IP for Rockwell, Profinet for Siemens, Modbus TCP as the lowest-common-denominator. Tag-database import formats differ. Rockwell projects use L5X, Siemens projects use TIA Portal XML, and most other platforms accept a CSV import that maps to the vendor's tag schema.
PLC I/O cards and how the I/O list drives hardware selection.
A PLC chassis holds a processor and a set of I/O cards. Analog input cards accept 4-20 mA, 0-10 V, or thermocouple signals. Analog output cards drive 4-20 mA positioners and variable-frequency drives. Digital input cards read dry contacts, proximity switches, and motor run-feedback relays. Digital output cards drive solenoid coils, relay coils, and motor-starter contactors. HART-capable AI cards add a digital communication layer on the same 4-20 mA wiring. The I/O list is the direct input to I/O card selection. The quantity of each signal class, plus any HART or safety-rated requirements, determines the card count and chassis sizing. An I/O list error at this stage, a wrong signal class or a missed tag means ordering the wrong card type, which is a long-lead procurement mistake. Engineering workspaces such as Tagsight read the I/O list directly from the P&ID set and export it to TIA Portal XML for Siemens S7 projects or Rockwell L5X for ControlLogix and CompactLogix projects, so the controls integrator imports tag names and data types straight into the PLC tag database rather than re-typing from Excel.
PLC vs DCS, the practical dividing line.
The DCS distinction is less about technical capability in 2026 and more about scope and integration model. A DCS integrates controller, I/O, HMI, alarm management, historian, and engineering tools under one vendor. A PLC provides the controller and I/O. The integrator assembles the rest from separate vendors. As a rule of thumb the lifecycle-cost crossover sits between ~300 I/O channels, below which PLC plus third-party HMI is typically lower lifecycle cost and ~5000 channels, above which an integrated DCS is typically lower lifecycle cost. On a 200-point skid package, assembling from components is straightforward. On a 15,000-point refinery process unit with 24, 7 operator presence, tight alarm integration, and a multi-decade maintenance horizon, the integrated DCS reduces lifecycle cost even at higher per-channel capex. Plants with a Siemens S7-based BPCS are sometimes described as PLC-controlled even though an S7-1500 in TIA Portal with WinCC HMI is functionally equivalent to a small DCS.
PLC vs PAC vs IPC, the practical dividing lines.
The PAC label, programmable automation controller was coined by ARC Advisory Group in 2001 to describe controllers that blend PLC reliability with PC-style data handling, motion control, and high-language programming. In practice every modern flagship PLC, ControlLogix, S7-1500, MELSEC iQ-R meets the PAC definition. The term is used in marketing more than in specification. An IPC, industrial PC is a hardened x86 or ARM computer running a real-time operating system or a soft-PLC runtime, CODESYS, Beckhoff TwinCAT, B&R Automation Runtime. IPCs replace dedicated PLC hardware on motion-heavy machines and on equipment where the same box also runs vision processing, OPC UA aggregation, or edge analytics. The practical rule. A fixed-function PLC remains the lowest-risk choice for safety-relevant interlocks and long-lifecycle process control. An IPC becomes interesting when one piece of hardware needs to handle control plus a heavy second workload.
What goes wrong when the I/O list and the PLC configuration diverge.
The PLC tag database is typically built by importing the I/O list. If the I/O list is incomplete or carries the wrong signal class, the tag database is wrong from the start. An AI tag imported as DI means the channel is configured for dry-contact detection, not 4-20 mA. The transmitter signal will never read correctly. A tag in the I/O list that was assigned to the wrong rack and slot means the physical wiring and the software wiring go to different cards. Both failures cause commissioning delays. The technician witnesses a loop test, sees the wrong behavior, and has to trace back to find whether it is wiring, configuration, or the I/O list that is the root cause. A clean, fully-classified I/O list is the single most effective pre-commissioning investment.
PLC vs DCS at a glance.
The two dominant control-system architectures. The lines have blurred over the last decade. This table is the practical decision frame.
| Aspect | PLC | DCS |
|---|---|---|
| Sweet spot | Discrete and hybrid. Packaging, assembly, machinery, balance-of-plant, smaller process | Continuous process. Refining, petrochemicals, power, pulp and paper, pharma |
| Scan time | Sub-millisecond to 10 ms typical | 20 to 100 ms typical, optimized for stability not speed |
| Programming | IEC 61131-3, ladder, function block, structured text, SFC per vendor IDE | Function-block oriented in a unified engineering environment, e.g. DeltaV Explorer, PCS 7 Engineering, Experion ControlEdge |
| Operator HMI | Separate SCADA, HMI package, FactoryTalk, WinCC, Ignition | Integrated DCS operator station, alarm management, and historian |
| Redundancy | Optional, requires explicit configuration | Built-in. Controller, network, and power redundancy as standard |
| Asset count | 10 to a few thousand I/O typical | Tens of thousands of I/O across one plant |
| Vendors | Siemens, Rockwell, Mitsubishi, Schneider, Omron, B and R, ABB AC500 | Emerson DeltaV, Honeywell Experion, Yokogawa CENTUM, ABB 800xA, Siemens PCS 7 |
| Cost shape | Lower entry cost, scales linearly with I/O | Higher entry cost, scales sub-linearly with I/O |
Frequently asked.
When was the PLC invented.
The first PLC, the Modicon 084, was shipped by Bedford Associates in 1969 to a General Motors Hydra-Matic assembly line. It replaced a relay-logic panel and was designed by Dick Morley, who is widely credited as the inventor of the PLC. The scan-cycle architecture he chose, read inputs, execute logic, write outputs, repeat, has remained the architecture of every commercial PLC since.
What programming languages does a PLC use.
Five languages are codified in IEC 61131-3, first published 1993, current revision 2013. Ladder diagram, LD, function block diagram, FBD, structured text, ST, instruction list, IL, and sequential function chart, SFC. Most legacy code is ladder. Modern projects mix ladder, structured text, and sequential function chart depending on what the logic needs. Instruction list is deprecated in the current edition but remains in legacy programs.
Is a PLC an alternative to a DCS or a complement.
Both. Below roughly 300 I/O channels, a PLC plus a third-party HMI is usually the lower-lifecycle-cost choice. Above roughly 5000 channels on a continuous-process plant, an integrated DCS wins on operator-interface integration, alarm management, and lifecycle maintenance. Many plants run both. A DCS for the main process units and PLCs for skid packages, compressors, air separation, packaged heat exchangers and balance-of-plant equipment.
How do I/O list exports from P&ID extraction get imported into a PLC engineering tool.
The two dominant import paths are TIA Portal XML for Siemens S7 projects and Rockwell L5X for Allen-Bradley ControlLogix or CompactLogix projects. Both formats import tag names, data types, and descriptions directly into the PLC tag database, eliminating the manual re-entry step that typically accounts for a significant portion of controls-configuration labor on large projects. CSV import covers most other platforms, Schneider EcoStruxure, Mitsubishi GX Works, Omron Sysmac via vendor-specific column mappings.
What is a safety PLC and how does it differ from a standard PLC.
A safety PLC, also called a safety-rated logic solver or fail-safe PLC is a controller whose hardware and firmware are designed and certified against IEC 61508, first published 1998 for use in safety instrumented functions. Examples include the Rockwell GuardLogix, Siemens ET 200SP F-CPU, and Pilz PSS 4000. The safety processor runs safety-rated program elements in a segregated execution context alongside standard control logic, with independent watchdog circuits and high internal diagnostic coverage. Standard PLCs cannot be used for SIL-classified SIS functions. The IEC 61508 certification is a hard gate.
How is PLC scan time relevant to SIS response-time requirements.
The PLC scan time, plus the I/O card scan delay, plus the time for the final element to complete its action, valve stroke time, must add up to less than the required response time, RRT that IEC 61511 specifies for each safety instrumented function. On fast-acting services such as gas-compressor surge protection or high-integrity pressure protection, the scan-time budget is tight. Safety PLCs on these services typically run dedicated safety tasks at cycle times of 10 to 50 milliseconds to meet RRTs of 250 ms or shorter.
Can the same PLC run both BPCS and SIS scope.
Technically yes, with a safety-rated PLC that partitions standard and safety execution contexts, such as the Rockwell GuardLogix or the Siemens S7-1500F. IEC 61511 clause 9.5 lists the conditions. Faults in the standard partition must not corrupt the safety partition, the safety I/O must be physically separate, and the design must be reviewed against the clause-9.5 independence requirements. Many operating companies prohibit this architecture in their internal standards regardless of the IEC's technical allowance, because the maintenance and modification risk is higher than a fully-separated BPCS-plus-dedicated-SIS layout.