PLC I/O List Template
Quick answer: A PLC I/O list is the shared contract between process intent, controls programming, field wiring and panel construction. It should identify every channel, signal type, device, address, terminal path, cable core, electrical range and review state.
User job: Move from field-device intent to an addressable PLC and terminal documentation package.

Worked example
A small pump skid may need run feedback, overload trip, low-level switch, start command, valve output and analog pressure. The list makes signal types and fail states explicit before the schematic and terminal plan are released.
Step-by-step workflow
- Define equipment and control narratives
- Create tags and classify DI, DO, AI and AO signals
- Assign rack, slot, channel and software address
- Map field terminals, cables and cores
- Review spare capacity and export the controlled list
Outputs and deliverables
- Channel-by-channel I/O list
- PLC address map
- Field terminal and cable-core mapping
- Signal range and fail-state record
- Commissioning status column
Quality checks before issue
- Sourcing and sinking conventions match the selected module
- Analog ranges and scaling are explicit
- Safety-related signals remain in the correct system boundary
- Addresses are unique and traceable
- The list and schematic use the same tags
Current product and engineering boundaries
- A generic list cannot establish functional safety performance.
- Exact module manuals govern commons, isolation, channel limits and wiring.
- Software logic, cause-and-effect and commissioning procedures are separate controlled artifacts.
Reviewed 2026-07-30: Product capabilities are first-party facts. Engineering examples are educational and must be verified for the actual project, equipment and jurisdiction.
Frequently asked questions
What is PLC I/O List Template used for?
A PLC I/O list is the shared contract between process intent, controls programming, field wiring and panel construction. It should identify every channel, signal type, device, address, terminal path, cable core, electrical range and review state.
What does this workflow produce?
Channel-by-channel I/O list, PLC address map, Field terminal and cable-core mapping, Signal range and fail-state record, Commissioning status column.
What should be checked before using the result?
Sourcing and sinking conventions match the selected module Analog ranges and scaling are explicit Safety-related signals remain in the correct system boundary Addresses are unique and traceable The list and schematic use the same tags
What does CircuitDiagramMaker not automate here?
A generic list cannot establish functional safety performance. Exact module manuals govern commons, isolation, channel limits and wiring. Software logic, cause-and-effect and commissioning procedures are separate controlled artifacts.
Can I continue with an editable project?
Yes. The page links to the closest supported editor, template, calculator, component library, or engineering workspace action.
Open the PLC I/O starter or inspect the current product capability matrix.