A PLC I/O list should define every signal, address, terminal, range, alarm and commissioning status so electrical design, PLC code, HMI screens and FAT records share one source of truth.
Key Questions
- Which physical and calculated points are required?
- How are tag names synchronized across drawings, code and SCADA?
- How will FAT and commissioning status be recorded?
Implementation Path
- 1Create tag, signal, range, unit, address and terminal columns.
- 2Link every point to alarms, interlocks and HMI or SCADA usage.
- 3Use the same list for FAT, site I/O check and final handover.
Related Systems and Entities
What a useful I/O list must contain
A useful I/O list includes tag name, signal type, range, unit, PLC address, cabinet terminal, field device, cable, alarm requirement, interlock role and commissioning status.
Keep engineering names consistent
The tag name used in drawings, PLC code, HMI screens, SCADA alarms and test records should be consistent. Inconsistent naming is one of the fastest ways to create commissioning confusion.
Use the point list as a commissioning tool
During FAT and site commissioning, the I/O list becomes a live checklist. Each point is checked for wiring, scaling, alarm behaviour and control effect, then marked as accepted with evidence.
FAQ
When should the PLC I/O list be created?
Create it during control-scope definition and keep updating it through design, panel build, FAT and commissioning.
Is a SCADA point list different from a PLC I/O list?
Yes. The PLC I/O list focuses on physical and controller points; the SCADA point list also includes calculated values, alarms, trends, reports and user-facing names.
Industrial Software, Remote O&M & Legacy Upgrade
Remote service, SCADA access, smart factory visualization, energy management and practical upgrades for aging control systems.