Industrial Automation Glossary of Terms

This page defines the core technical vocabulary used across industrial automation disciplines, from control systems and field devices to networking protocols and safety standards. The terms collected here span discrete manufacturing, process industries, and hybrid environments — covering both legacy plant-floor terminology and modern concepts tied to Industrial Internet of Things (IIoT) and digital integration. Precise terminology reduces specification errors, supports cross-disciplinary communication, and anchors compliance with standards published by ISA, IEC, and NIST.

Definition and scope

An industrial automation glossary is a structured reference that assigns bounded, consensus-based definitions to technical terms used in the design, operation, and maintenance of automated industrial systems. The scope of such a glossary extends across hardware, software, control theory, safety engineering, and communications — reflecting the interdisciplinary character of modern automation practice.

The International Society of Automation (ISA) and the International Electrotechnical Commission (IEC) maintain the two most widely adopted standardized vocabularies for this domain. ISA-5.1 covers instrumentation symbols and identification; IEC 61131-3 standardizes programming language terminology for programmable controllers. Where these sources diverge from common shop-floor usage, this glossary notes the distinction.

The terms below are grouped functionally rather than alphabetically, reflecting how practitioners encounter them: control architecture first, then field devices, then communications, then safety and compliance.

How it works

A well-structured automation glossary operates through four layers of definition:

  1. Term identification — The term is stated in its canonical form, including common abbreviations (e.g., PLC for Programmable Logic Controller, DCS for Distributed Control System).
  2. Normative definition — The definition is drawn from or reconciled with a named standard or authoritative body, with any deviations noted.
  3. Functional context — The term is placed within a system context: where it appears in a control hierarchy, what it interfaces with, and how it behaves under normal versus fault conditions.
  4. Boundary conditions — Distinctions are drawn between closely related terms (e.g., setpoint vs. process variable, interlock vs. permissive) to prevent conflation in specification documents.

This structure mirrors the approach used in NIST SP 800-82 (Guide to Industrial Control Systems Security), which maintains a formal glossary as an appendix to its ICS security framework — a practice that signals how definitional precision directly supports operational and regulatory outcomes.

Common scenarios

Control Architecture Terms

Field Device and Instrumentation Terms

Safety and Compliance Terms

Networking and Communication Terms

Decision boundaries

Selecting the correct term in a specification or procurement document requires distinguishing terms that are often used interchangeably but carry different normative meanings:

PLC vs. DCS
PLCs are optimized for high-speed discrete control (scan times under 10 milliseconds are common) and are dominant in discrete manufacturing such as automotive assembly. DCS platforms are optimized for continuous process control, providing tighter integration of historian, alarming, and loop tuning functions at the plant level. The distinction matters for vendor selection, software licensing, and ISA-18.2 alarm management compliance. Detailed comparison is available at Process Automation vs. Discrete Automation.

SCADA vs. DCS
SCADA systems typically supervise geographically distributed assets (pipelines, power grids, water networks) over wide-area communications links, while DCS systems manage a single plant or unit operation over a local network. The two architectures increasingly overlap as IIoT connectivity expands, but their security perimeters, redundancy models, and latency tolerances remain distinct — a boundary that CISA addresses directly in its ICS security advisories (CISA ICS Advisories).

SIS vs. Basic Process Control System (BPCS)
IEC 61511 requires that safety instrumented systems be independent of the basic process control system to the degree required by the target SIL. Sharing sensors, logic solvers, or final elements between the BPCS and SIS is permissible only when a formal risk assessment demonstrates no compromise of the required SIL. This independence requirement is among the most commonly misunderstood boundaries in process safety engineering.

Interlock vs. Permissive
These two terms are frequently conflated in P&ID documentation. An interlock is triggered by an abnormal condition and acts to stop or redirect the process. A permissive is a prerequisite condition for a normal operation to begin. Confusing the two in control narratives leads to logic errors that may not surface until a fault condition occurs.

For standards governing how these terms appear in official documentation, the Industrial Automation Standards and Regulations reference page provides the governing bodies and document numbers relevant to US industrial facilities.

References

Explore This Site

Regulations & Safety Regulatory References Tools & Calculators Website Performance Impact Calculator