Smart factory with robotic arm, conveyor and connected control panels illustrating automation standards

Automation Standard Explained: What It Is and Which Standards Actually Matter

ByAlex Morgan

Key takeaway: An automation standard is a published, shared rulebook that lets equipment, software and people from different vendors work together safely. The most important ones are ISA-95 for enterprise-to-plant integration, OPC UA for secure machine data exchange, IEC 61131-3 for PLC programming, IEC 62443 for industrial cybersecurity and ISO 10218 for robot safety.

Search “automation standard” and you meet a pile of numbers: ISA-95, IEC 61131-3, OPC UA, IEC 62443, ISO 10218. They are not competing versions of the same thing. Each answers a different question, and a factory usually needs several at once. Here is what each covers, in plain English.

What an automation standard actually is

An automation standard is a documented agreement about how things should work together. It may define shared words, the data two systems exchange, the languages a controller understands, or the safety measures a machine must have. Standards come from bodies such as the International Society of Automation (ISA), the International Electrotechnical Commission (IEC) and the International Organization for Standardization (ISO).

The payoff is interchangeability. Without shared standards, every machine and software package would need custom glue code, and replacing one vendor’s controller could mean rewiring a line. With them, a plant can mix vendors and prove safety and security were handled properly.

The main automation standards at a glance

Standard What it covers Who uses it most
ISA-95 / IEC 62264 Information exchange between enterprise systems and plant-floor controls Plant managers, MES and ERP teams
OPC UA / IEC 62541 Secure, vendor-neutral machine data exchange with shared information models Controls engineers, IIoT teams
IEC 61131-3 Programming languages and software structure for PLCs PLC programmers, integrators
IEC 62443 Cybersecurity for industrial automation and control systems OT security teams, asset owners
ISO 10218 Safety of industrial robots and their integration into work cells Robot makers, integrators

ISA-95: how the business and the plant floor share information

ISA-95, known internationally as IEC 62264 and titled “Enterprise-Control System Integration,” defines the models and terminology for connecting enterprise systems with control systems. Its best-known idea is a five-level functional hierarchy: Level 0 is the physical process, Level 1 sensing and manipulating it, Level 2 monitoring and supervisory control, Level 3 manufacturing operations management, and Level 4 business planning and logistics.

One correction matters: these levels describe responsibilities, not network cables. ISA-95 does not require one network per level. MES systems sit at Level 3 and ERP at Level 4. If your ERP and MES disagree about what was produced, ISA-95 gives both sides the same vocabulary. See also our guide to equipment automation.

OPC UA: how machines from different vendors exchange data

OPC UA (Open Platform Communications Unified Architecture) is the interoperability standard for secure, reliable exchange of industrial data. It was released by the OPC Foundation in 2008 and later adopted as IEC 62541. Unlike its predecessor OPC Classic, tied to Microsoft’s COM/DCOM technology, OPC UA is platform-independent and works across operating systems and vendors.

Its real strength is that it carries meaning, not just numbers: a temperature reading can arrive with its unit, valid range and place in the machine’s information model. That is why OPC UA appears in Industrie 4.0 architectures and ISA-95 Level 2–3 integration — it is the pipe, while ISA-95 is the shared language for what flows through it.

IEC 61131-3: how PLCs are programmed

IEC 61131-3 is the international standard for programming languages for programmable logic controllers (PLCs). Earlier editions listed five languages: Ladder Diagram (LD), Function Block Diagram (FBD), Structured Text (ST), Sequential Function Chart (SFC) and Instruction List (IL). IL was deprecated in the third edition in 2013 and removed in the fourth edition published in 2025, leaving LD, FBD and ST as the programming languages, with SFC elements used to structure programs.

The standard makes PLC skills portable: an engineer who learns Ladder Diagram or Structured Text on one vendor’s platform can read logic on another’s. The limit: it defines languages and software structure, not a universal project file downloadable unchanged into every controller. For the career side, see how to become an automation engineer.

IEC 62443: how industrial systems are secured

IEC 62443 is the family of standards for cybersecurity of industrial automation and control systems (IACS). Its core idea is zones and conduits: a zone is a group of assets sharing the same security requirements, and a conduit is the controlled communication path between zones. Each zone gets a target security level, from SL 1 (casual or coincidental violation) to SL 4 (sophisticated, well-resourced attackers).

Two traps catch newcomers. IEC 62443 is a design discipline, not a certificate you buy — the standard itself does not require certification, though a contract or regulator may. And SL 4 everywhere is not a sensible default; levels should follow a risk assessment of what happens if each zone is compromised.

ISO 10218: how industrial robots stay safe around people

ISO 10218 is the primary international standard for industrial robot safety, split into two parts with different owners. Part 1 sets safety requirements for the robot itself and applies to manufacturers, covering emergency stops, speed and force limiting, and safety-related control functions. Part 2 covers robot systems and integration and applies to integrators building work cells, requiring risk assessments, safeguarding and validation of the finished cell.

The split matters: a Part 1-compliant robot does not automatically make a compliant work cell. The integrator’s Part 2 work — guarding, interlocks and a risk assessment for that specific cell — is what makes the installed system safe. Recent editions, published in 2025, also reflect collaborative robots sharing workspace with people.

Comparison: which automation standard do you need?

Work backwards from the problem. If systems cannot exchange production data, start with ISA-95’s models and OPC UA’s transport. If control logic cannot move between vendors, IEC 61131-3 is the gap. If a networked plant has no security architecture, IEC 62443’s zones and conduits come first. If robots are being installed, ISO 10218 is non-negotiable. Most projects need at least two — for example, OPC UA for data plus IEC 62443 for securing the network it travels on.

Cost: what adopting an automation standard actually costs

The document itself is rarely the main cost, though IEC, ISO and ISA documents are typically sold rather than free. The real costs are engineering time, training, testing and any certification a customer or regulator requires. Standardising costs more up front than a one-off custom integration, but pays back later: adding a machine or swapping a vendor becomes configuration instead of a rewrite. Pilot one cell before committing a whole plant.

Prerequisites: what to have in place before you standardise

Three things are decisive: an up-to-date asset inventory, a clear statement of the problem the standard should solve, and someone with authority to enforce naming and data conventions across teams. For IEC 62443 and ISO 10218, add a risk assessment; for ISA-95, add agreement between operations and IT on which system owns each piece of data. Without those, a standard becomes shelfware.

Risks and limits: where standards do not save you

A standard is a floor, not a guarantee. Two products can both claim OPC UA support yet implement different companion specifications, and a compliant robot cell can still be unsafe if its risk assessment missed a foreseeable misuse. Standards also evolve — IEC 61131-3’s removal of Instruction List in 2025 is a reminder that code written to an old edition may need rework. Safety and security depend on implementation and maintenance, not on the purchase alone.

Analysis: start with the data model, not the document

Analysis: The pattern across all five standards is the same — winners standardise meaning before technology. Plants that buy OPC UA servers before agreeing what their production data means end up with faster pipes carrying the same confusion. The highest-return first step is the ISA-95 exercise of naming equipment, materials, personnel and production segments consistently, then choosing the transport, language, security architecture and safety regime that fit that model.

For the broader landscape, see our explainer on types of process automation.

Sources

Frequently asked questions

What is an automation standard in simple terms?

An automation standard is a published set of agreed rules that lets machines, software and teams from different vendors work together. It can define shared vocabulary, data formats, programming languages, security architecture or safety requirements.

Which automation standard should a factory adopt first?

Start from your biggest pain point. If business and plant systems disagree about production data, start with ISA-95. If machines cannot share data, start with OPC UA. If you are installing robots, ISO 10218 is mandatory groundwork, and if your control network has no security design, IEC 62443 should come first.

What is the difference between ISA-95 and OPC UA?

ISA-95 defines the models and terminology for enterprise-control integration, including its five-level hierarchy. OPC UA is the secure, vendor-neutral communication standard that moves industrial data between systems. In short, ISA-95 defines what the data means, and OPC UA defines how it travels.

Is IEC 61131-3 still relevant in 2026?

Yes. IEC 61131-3 remains the standard for PLC programming languages, and its fourth edition was published in 2025. Ladder Diagram, Function Block Diagram and Structured Text remain the programming languages, while Instruction List was removed after being deprecated in 2013.

Do small factories need IEC 62443 and ISO 10218?

They need the thinking even when the paperwork is lighter. A small plant still benefits from zones and controlled conduits, and any industrial robot cell still needs a risk assessment and safeguarding under ISO 10218. The documentation can fit the site, but the principles do not shrink with it.


Similar Posts