What a PLC is
A programmable logic controller (PLC) is an industrial computer built to run machinery and processes reliably for years. It sits in a control panel, reads signals from switches and instruments, makes decisions according to its program, and turns motors, valves and alarms on and off.
PLCs run lift stations, water treatment skids, conveyors, compressors, packaging lines, snow-melt systems and plenty of equipment you may not think of as "automated". Many owners inherit them with the building and only learn about them when something stops working.
How it thinks
A PLC does the same thing over and over: read all inputs, run through the program, set all outputs, handle communications, repeat. This scan happens many times a second, which is why it reacts quickly and predictably.
Programs are commonly written in ladder logic, which looks like an electrical drawing, or in function blocks and structured text. You do not need to read the code, but you should know where it is kept and who can change it.
The parts you will hear about
- CPU or processor: runs the program. Holds the configuration and, usually, a copy of the program in memory.
- I/O modules: the cards that connect field wiring. Digital (on/off) and analog (such as 4-20 mA).
- Power supply: feeds the rack. Often backed by a UPS so a power blip does not stop the process.
- HMI: the touchscreen or computer where operators see status, change setpoints and acknowledge alarms.
- Network: links the PLC to drives, other PLCs, SCADA, the BAS or remote access.
- Programming software and licence: needed to view or change the program. Often specific to the manufacturer and version.
What every owner should have on file
The single most useful thing you can do as an owner is make sure nobody else holds your system hostage. Keep, in a safe place you control:
- A current backup of the PLC and HMI programs, with comments, dated and labelled with the version running in the field.
- Electrical drawings for the control panel, updated to as-built.
- An I/O list showing what each input and output does.
- Passwords for the PLC, HMI and any remote access, held by the owner, not just the integrator.
- Model numbers and firmware versions of the hardware.
- A functional description in plain language of what the system is supposed to do.
Make program backups, drawings and passwords a written deliverable in any controls contract. It costs little at handover and can be very expensive to recover later.
Spares, support and lifecycle
PLC hardware has a long but finite life. Manufacturers eventually move product lines to mature and then discontinued status, after which spares get scarce and expensive. Know where your hardware sits in that lifecycle and keep critical spares, such as a CPU, power supply and common I/O cards, on the shelf if the process cannot tolerate a long outage.
If your system is already discontinued, read migrating obsolete PLCs before the next failure forces a rushed decision.
Questions to ask before buying a new system
Whether a PLC comes inside a vendor's equipment skid or is part of a custom control panel, a few questions up front save trouble later:
- Is the hardware a current product line with good local availability of spares?
- Will we receive the unlocked program, with comments, and the right to modify it?
- What software and licences do we need to view or change it, and who pays for them?
- Can the system share data with our SCADA or building automation system using open protocols?
- How will remote access be provided and secured?
- What training and documentation are included at handover?
Locked or proprietary programs are not always a deal-breaker, but you should know what you are agreeing to before the equipment arrives.
Safety and changes
Standard PLCs are not, on their own, safety devices. Emergency stops and safety functions are handled by hardwired circuits, safety relays or safety-rated controllers designed for that purpose. Any change to logic that affects equipment movement or protection should be reviewed, tested and documented.
Forcing inputs or outputs, or editing logic online, can start equipment unexpectedly. Changes should be planned, made by qualified people, and tested with the equipment in a safe state.
Our PLC systems and control panels services cover new systems, troubleshooting, documentation recovery and backups for existing equipment.
Common questions
What is the difference between a PLC and a BAS controller?
Both are programmable controllers. PLCs are built for machinery and processes with fast, deterministic control. BAS controllers are built for HVAC and building systems and use building protocols like BACnet. The line blurs, and many sites have both.
Our integrator went out of business. Can someone else support the PLC?
Usually, if you have the program backup and drawings. Without them, a technician can often upload the program from the PLC, but comments and documentation may be lost. Do this sooner rather than later.
Do we need a UPS on our PLC?
For many processes, yes. A short outage can stop a PLC or HMI and require manual restart, and a UPS rides through brief interruptions and allows a controlled shutdown on longer ones.
Can a PLC send us alarms on our phone?
Yes, through a SCADA system, a cellular gateway or a remote monitoring service. Security for that connection matters; see our guide on cybersecurity for building and plant controls.
Codes and permit rules change and every building is different. For work on your system, talk to a licensed electrician and your local permit authority.