PLC Control System Design: Process and Requirements (2026 Update)

PLC Engineering · Engineering Notes · 2026 Update

By KOEED Engineering Team · 2026-07-03 · 8 min read · Engineering Notes

Two years on, the core process for designing a PLC control system is unchanged — define objectives, pick hardware, build logic, simulate, commission — but the toolbox has shifted. IEC 61131-3 fourth edition, vendor-neutral simulation, OPC UA over TSN, and PLCopen-style motion blocks now sit alongside the ladder logic of 2024. This Engineering Note refreshes our 2024 walkthrough for engineers designing Allen-Bradley ControlLogix, Siemens SIMATIC S7-1500, and Mitsubishi MELSEC iQ-R systems in 2026.

AI Summary

• The six-step design process from 2024 still applies: define objectives, pick hardware, build logic, configure I/O, commission, document.
• IEC 61131-3 fourth edition (2025) and OPC UA over TSN are now baseline expectations for new PLC projects, not optional extras.
• Vendor-neutral digital twin simulation is replacing chassis-bound emulation: a 2026 design should be validated before any module ships.
• Reliability, scalability, and cybersecurity are the three design pillars — functional safety (IEC 61508) and cyber hardening sit next to them, not behind.
• Document as you go: cyber and safety deliverables now need a living record for audit, not a final report.

In 2026 a PLC control system is a software-defined asset. The six steps are stable; the tools, networks, and audit trail underneath them are not.

Step 1 — Define control objectives and requirements

Start with a written URS (User Requirements Specification). For a 2026 project that means capturing the control narrative, I/O count with at least 20 percent spare, response-time budgets, and the safety integrity level (SIL per IEC 61508 or PL per ISO 13849) you intend to reach. Pull in operations, maintenance, EHS, and cybersecurity — the latter is new since 2024: IEC 62443-3-3 defines a Security Level target (SL-T) for every zone, and that target now shapes network and module choices downstream.

When the URS is signed off, freeze it. Any change after this point should run through a formal MOC (Management of Change) record. See our KOEED daily PLC news for examples of how missing URS records derail field retrofits.

Step 2 — Select the appropriate PLC hardware

Hardware selection in 2026 is no longer just "compact vs. modular." The relevant dimensions are:

• Program portability: does the runtime claim IEC 61131-3 fourth edition (2025) support, including the new object-oriented extensions and the harmonized function-block libraries?
• Network stack: native OPC UA over TSN, or do you need a separate gateway? For greenfield plants, assume TSN is required.
• Cybersecurity hardware: secure boot, signed firmware, hardware-rooted identity (TPM-style modules). The 2024 baseline of "an admin password" no longer passes audit.
• Lifecycle status: avoid series that have already issued an EOL notice. KOEED keeps legacy stock of the Allen-Bradley SLC 500 (1747) family and Siemens S7-300 (6ES7 3xx) for in-place repair while you plan a migration.
• Environmental class: temperature, vibration, conformal coating for corrosive atmospheres, and (increasingly) marine or rail certification.

Step 3 — Develop the program logic

Ladder logic (LD) and function block diagram (FBD) remain the workhorses. What changed since 2024 is the mix:

• Structured text (ST) is now first-class for math, batch recipes, and any algorithm that does not map cleanly to contacts and coils.
• Object-oriented IEC 61131-3 methods (introduced in the third edition, expanded in the fourth) let you write reusable function blocks with encapsulation — the same way a software engineer thinks about classes.
• PLCopen motion blocks are the de-facto way to drive servos, including on Yaskawa Sigma-7 and Mitsubishi MR-J5 axes.
• Continuous integration is finally practical: GIT-backed projects in Studio 5000, TIA Portal V20, and GX Works3 allow you to merge, branch, and review code the way a software team would.

Version everything. The 2024 walkthrough said "test the program before implementation." In 2026 that means automated unit tests, code review, and signed builds. We walk through this pattern in our Engineering Notes series.

Step 4 — Configure and test the I/O system

Connect the I/O modules to the PLC and verify every point against the URS, not just "is it on the right terminal." In 2026 that means:

• Each input has a name, a tag, a scaling rule, and a fault state.
• Each output has a name, a tag, a watchdog, and a safe-state value (de-energize vs. hold-last).
• Field wiring is documented per the IEC 61131-3 fourth-edition naming conventions; signal type and SL-T are visible at the terminal level.
• Vendor-neutral simulation runs against the same tag database the controller will load — a single source of truth from panel CAD through HMI.

Step 5 — Simulate, commission, and perform start-up tests

"Start-up tests" used to mean energize, watch, pray. The 2026 version runs in three phases:

1. Software-in-the-loop (SIL): load the program into a vendor-neutral digital twin (or the vendor's own simulator) and exercise every URS line. Catch logic errors before any I/O is wired.
2. Hardware-in-the-loop (HIL): with the real PLC and a simulated plant, prove the network, scan time, and I/O behaviour. This is where OPC UA over TSN gets validated.
3. Site acceptance test (SAT): on the real machine, against the real load. Sign off the safety function tests here, not at the panel builder's shop.

Step 6 — Document the system

Documentation in 2026 is a living artifact, not a final PDF. Capture:

• URS, FDS, and SAT reports — linked to the controller's tag database.
• Network topology, security zones, and SL-T per zone (IEC 62443).
• Safety case: SIL target, proof-test interval, and the bypass / override log.
• EOL roadmap: when each module is scheduled for retirement, and the cross-reference to its modern equivalent. KOEED's All collection index keeps active and legacy series visible side by side.
• Change log: every program revision, every MOC, every firmware update.

Requirements for a 2026 PLC control system

The four 2024 requirements (reliability, scalability, efficiency, maintainability) are still in force. Three new ones now sit alongside them:

What changed since 2024

A 2024 engineer would have written the same six steps, but the supporting cast has moved. The three most consequential shifts:

1. IEC 61131-3 fourth edition (2025) harmonizes function-block libraries, deepens the object-oriented profile, and locks in a vendor-neutral way to write motion, safety, and recipe code. If your 2024 program was ladder-only, the 2026 migration is the right time to introduce ST and reusable FB classes.
2. OPC UA over TSN is the default greenfield plant network. In 2024, "OPC UA" usually meant a side-channel to the SCADA; in 2026, the controller's I/O can ride the same TSN backbone as the safety devices.
3. Cybersecurity is no longer optional. IEC 62443-3-3 is now a procurement line item. Expect a Security Level target (SL-T) per zone, a zone & conduit diagram, and a patch cadence — all of which the 2024 process did not need to capture.

The 2024 walkthrough also did not anticipate how fast vendor-neutral simulation matured. Tools like PLCsim Advanced, Siemens S7-PLCSIM, and open-source CODESYS simulation now let a small team run a full SIL pass before a single module ships to site. If you have not added a simulation stage to your V-model, 2026 is the year.

Common pitfalls on a 2026 project

• URS missing safety or cyber sections, with the SL-T target defined only at FAT.
• Mixing OPC UA Classic and TSN in the same plant — the controllers will pass commissioning, but the SCADA team will not be able to consume both data models.
• Skipping the digital twin and only doing bench tests; scan-time and I/O timing issues show up only at SAT.
• Buying EOL hardware (e.g. 1747-ASB for SLC 500) for a greenfield project instead of planning a cross-reference to ControlLogix 1756-DNB.
• Forgetting the proof-test interval for safety functions; SIL 2 / SIL 3 ratings are not valid without periodic verification.

Frequently asked questions

Is the six-step PLC design process from 2024 still valid in 2026?

Yes. The six steps are still complete: define, select, develop, configure, commission, document. What changed is the depth at each step, especially around cyber and functional safety.

Do I need OPC UA over TSN for a new plant in 2026?

For most greenfield plants, yes. TSN gives you deterministic Ethernet for control and safety, and OPC UA gives a vendor-neutral model up to MES. A gateway is still fine for brownfield.

What is the difference between IEC 61131-3 third and fourth editions?

The fourth edition (2025) harmonizes function-block libraries, deepens object-oriented features, and adds cyber-secure deployment guidance. Most 2026 controllers claim a subset; check release notes.

Can I still buy spare parts for an EOL PLC like the SLC 500 or S7-300?

Yes. KOEED keeps active and legacy stock side by side. Send your BOM to Moritta@KOEED.COM and we will quote new, refurbished, and cross-referenced parts within 24 hours.

Do I still need to document my PLC system if I have a digital twin?

Yes. The twin is part of the documentation, not a replacement. Auditors (IEC 62443, IEC 61511) still expect a URS, a zone-and-conduit diagram, a safety case, and a change log.

Related on the KOEED Blog: Engineering Notes · Daily PLC News · AI Diagnostic Tool