Programmable Logic Controllers (PLCs) in Electrical Contracting Projects
How programmable logic controllers (plcs) are selected, sized, and integrated in electrical contracting projects.
Programmable Logic Controllers (PLCs) in Electrical Contracting Projects
Programmable logic controllers (PLCs) are the core control layer in many industrial electrical contracting projects, bridging field devices, motor starters, drives, safety circuits, and SCADA/HMI systems. In contracting practice, PLC selection is not just a brand preference exercise; it is a design, compliance, integration, and commissioning decision that affects panel architecture, wiring density, network topology, cybersecurity, maintainability, and lifecycle support. For European projects, the PLC must fit within the machine or process conformity route under the EU Machinery Directive/Regulation framework, while the complete control system must align with IEC/EN standards for electrical equipment, functional safety, and EMC.
1. How PLCs are selected in contracting scope
The first selection step is defining the control role. A PLC for a compact packaging skid is very different from one for a water treatment plant, a conveyor line, or a process utility plant. Contractors typically evaluate the following:
- I/O count and mix: digital inputs/outputs, analog I/O, temperature modules, high-speed counters, motion axes.
- Determinism and scan time: especially for interlocks, sequencing, and motion-related tasks.
- Communications: PROFINET, EtherNet/IP, Modbus TCP, Profibus, IO-Link, OPC UA, serial gateways.
- Safety integration: standard PLC versus integrated safety PLC or safety CPU.
- Environmental and enclosure constraints: temperature, vibration, EMC, IP rating, panel space.
- Vendor support and spares strategy: local availability, lifecycle status, and replacement compatibility.
Common vendor families in contracting projects include Siemens SIMATIC S7-1200/S7-1500, Schneider Electric Modicon M241/M251/M340/M580, Rockwell Automation CompactLogix/ControlLogix, ABB AC500, Beckhoff CX series, and WAGO PFC controllers. Selection is often driven by the project’s installed base, preferred network standard, and the customer’s maintenance capability.
For European machine projects, the PLC is part of the control system that contributes to compliance with EN ISO 13849-1 for safety-related parts of control systems or IEC 62061 for functional safety, depending on the risk reduction approach. If the PLC is part of a machine control panel, the panel builder must also consider IEC 60204-1 for electrical equipment of machines, especially protective bonding, control circuits, emergency stop behavior, and documentation.
2. Sizing the PLC and its power budget
PLC sizing in electrical contracting is usually done in three dimensions: CPU capacity, I/O capacity, and power supply capacity. A practical rule is to avoid designing at the edge of module limits, because spare capacity is needed for commissioning changes, future expansion, and spare channels.
For power, the panel designer should calculate the 24 VDC load. A simplified sizing expression is:
$$I_{PSU} \\ge \\frac{\\sum I_{loads}}{\\eta} \\times 1.25$$
where $\\sum I_{loads}$ is the total steady-state current of PLC CPU, I/O modules, relays, sensors, communication devices, and fieldbus couplers, $\\eta$ is the power supply efficiency factor, and the 1.25 multiplier provides engineering margin. In practice, the total load must also consider inrush current and output group simultaneity.
For example, if a PLC rack and associated electronics draw 6.4 A at 24 VDC, a conservative supply selection would be at least:
$$6.4 \\times 1.25 = 8.0\\text{ A}$$
So a 10 A or 12 A industrial PSU is often selected, provided thermal dissipation and short-circuit coordination are acceptable. IEC 60204-1 requires proper protection and control circuit arrangement, while IEC 61439 principles are often used by panel builders for assembly verification of low-voltage switchgear and controlgear assemblies.
3. Integration with panels, networks, and field devices
PLCs are integrated into the contracting package as part of the electrical panel architecture. The physical layout should separate power wiring, switching devices, and communication cabling to reduce EMC issues. IEC 61000-6-2 and IEC 61000-6-4 are commonly used for industrial immunity and emission expectations, and good panel practice includes segregating analog signals, using shield termination strategy, and maintaining proper PE bonding.
Network integration is now a major part of PLC scope. Contractors should define whether the PLC is the cell controller, edge gateway, or SCADA node. Ethernet-based industrial protocols dominate, but the choice must match the customer’s architecture and support model. For example, Siemens projects often standardize on PROFINET; Rockwell-heavy sites may use EtherNet/IP; process plants may require Modbus TCP or OPC UA gatewaying to a DCS or historian. Where remote access is included, IEC 62443 principles should guide zoning, conduit, and access control, especially under EU NIS2-driven cybersecurity expectations for essential and important entities.
Functional integration must also address safety. If safety functions are handled by a safety PLC, the contractor should verify the required Performance Level or Safety Integrity Level. Typical standards include EN ISO 13849-1, especially clauses on category, MTTFd, DCavg, and CCF, and IEC 62061 for SIL-related machine control functions. Emergency stop circuits remain governed by IEC 60204-1 and must be validated during commissioning.
4. Vendor family decision points
| Vendor family | Typical strength | Best fit in contracting | Watch-outs |
|---|---|---|---|
| Siemens SIMATIC S7-1200/1500 | Strong EU market share, PROFINET, broad ecosystem | Machine panels, OEM skids, plant utilities | Licensing and engineering software discipline required |
| Schneider Modicon M241/M251/M580 | Good integration with EcoStruxure, Modbus heritage | Process utilities, infrastructure, mixed legacy sites | Confirm module availability and long-term support |
| Rockwell CompactLogix/ControlLogix | Common in North America, EtherNet/IP, strong motion options | Global plants with Allen-Bradley standardization | Higher cost and regional support strategy matter |
| Beckhoff CX / WAGO PFC | Flexible, modular, strong open automation approach | Compact skids, distributed I/O, IIoT-oriented systems | Requires disciplined architecture and software governance |
The best choice is not always the most powerful PLC; it is the one that best aligns with the client standard, the engineering team’s competence, and the plant’s maintenance and spare parts model.
5. Factory testing, site testing, and handover
PLCs should be tested as part of the full control system, not as isolated hardware. At FAT, contractors verify I/O mapping, interlocks, alarm handling, communications, and safety logic. At SAT, they confirm field wiring, device polarity, instrument scaling, motor rotation, network addressing, and HMI/SCADA tags. IEC 60204-1 and IEC 61439-oriented documentation practices support this verification process, while ISA-88 or ISA-95 concepts may be used for batch or enterprise integration structures where applicable.
Commissioning checklists should include:
- CPU firmware version and backup image
- Program upload/download and password control
- 24 VDC supply stability under load
- Safety chain validation and reset behavior
- Network redundancy or failover tests, if specified
- Alarm and event log confirmation
- As-built documentation and tag list reconciliation
For contractual closeout, the PLC deliverable should include software source files, hardware BOM, network topology, test records, and a maintenance philosophy. That is what turns a PLC from a component into a supportable asset.
6. Practical contracting takeaway
In electrical contracting projects, PLC selection is a multidisciplinary decision spanning compliance, panel design, power engineering, software structure, and lifecycle support. A well-chosen PLC family reduces commissioning risk, simplifies spares, and improves maintainability. A poorly chosen one creates hidden cost in software complexity, panel rework, and long-term support.
If you are defining PLC scope for a new machine, utility skid, or plant automation package, we can help you align the control architecture with IEC/EN compliance, network strategy, and commissioning requirements—discuss the project via /contact.
Other components for Electrical Contracting
Other services using Programmable Logic Controllers (PLCs)
Frequently asked questions
What is the role of a PLC in an electrical contracting project, and how does it differ from a remote I/O system or SCADA?
A PLC is the real-time control layer that executes logic, interlocks, sequencing, and alarm handling for machines, skids, utilities, and process units. Remote I/O extends field signals to a controller, while SCADA is primarily the supervisory layer for monitoring, alarming, trending, and operator control; in most projects, these are integrated but not interchangeable. For European projects, PLC architecture and interfaces are commonly aligned with IEC 61131-3 for programming and IEC 60204-1 or IEC 61439 where machine control panels and assemblies are involved.
What standards should an electrical contractor verify when supplying PLC panels for a European project?
At minimum, contractors should verify the applicable panel assembly, wiring, and machine-control standards, typically IEC 61439 for low-voltage switchgear and controlgear assemblies and IEC 60204-1 for electrical equipment of machines. For functional safety and control system design, IEC 61508 and IEC 62061 may apply, depending on the safety functions and risk assessment. If the project includes operator interfaces and alarm management in a supervisory system, ISA-18.2 is often used alongside site-specific alarm philosophy documents.
How should PLC control panels be coordinated with MCCs, VFDs, and motor starters in a contracting package?
The contractor should define clear control responsibilities, hardwired interlocks, start/stop permissives, fault feedback, and communication architecture between the PLC, MCC, VFDs, and starters. In many global projects, motor control is split between hardwired safety/permissive circuits and fieldbus control using protocols such as PROFINET, EtherNet/IP, or Modbus TCP, with the final arrangement driven by availability and maintainability requirements. Coordination must also consider short-circuit ratings, protective device selectivity, and conformity of the assembly to IEC 61439 and the machine electrical design requirements of IEC 60204-1.
What should be included in PLC I/O lists and cause-and-effect matrices for EPC projects?
A complete I/O list should identify tag number, signal type, voltage level, normal state, fail state, cable reference, marshalling point, and whether the point is hardwired, safety-rated, or networked. The cause-and-effect matrix should define initiating events, logic conditions, outputs, resets, bypass rules, and alarm priorities so the contractor can test the system consistently during FAT and SAT. For process and alarm integration, ISA-18.2 and IEC 61131-3 are commonly used to structure logic and alarm behavior in a verifiable way.
How do European compliance requirements affect PLC cabinet design, wiring, and documentation?
European compliance typically requires attention to CE conformity, EMC, protective bonding, segregation of circuits, and proper technical documentation, not just the PLC hardware itself. Panel design commonly references IEC 61439, IEC 60204-1, and EMC-related requirements such as IEC 61000 series standards, with wiring, labeling, and terminal identification aligned to the project specification and applicable EN adoptions. Contractors should also provide schematics, terminal plans, cable schedules, software backups, and validation records to support the technical file and handover.
What are the best practices for PLC network design on multi-vendor industrial projects?
Best practice is to separate control, safety, and supervisory traffic, define a deterministic industrial Ethernet topology, and specify managed switches, VLANs, redundancy, and addressing rules early in the project. Multi-vendor sites should standardize protocol gateways and data mapping to avoid undefined behavior between PLCs, SCADA, historians, and third-party packages. Where interoperability and lifecycle support matter, the contractor should document protocol ownership, network ownership, and cybersecurity responsibilities in the design basis and commissioning plan.
How should PLC software be managed during construction, FAT, SAT, and commissioning?
PLC software should be version-controlled from the start, with a controlled baseline for logic, HMI graphics, alarm configuration, and network settings before FAT. Changes during SAT and commissioning must follow formal management of change, with traceable revisions, test evidence, and rollback capability so the as-built software matches the final field conditions. IEC 61131-3 is the main programming reference, while ISA-88 is often used when batch or modular process structures are involved.
What cybersecurity controls are expected for PLCs connected to SCADA or remote access systems?
For connected PLC systems, contractors should implement network segmentation, least-privilege access, secure remote access, logging, backup/restore procedures, and asset inventory controls. IEC 62443 is the primary industrial cybersecurity standard family used on automation projects, and it is especially relevant when PLCs interface with SCADA, historians, gateways, or vendor remote support tools. Cybersecurity requirements should be defined in the project specifications, not added after commissioning, because retrofits are more expensive and often less effective.