
A water pump control panel may need level switches, pressure transmitters, a variable frequency drive (VFD), an alarm beacon, and a solenoid valve. Listing those devices is straightforward. Turning them into an accurate PLC I/O list is harder. Each control function needs a defined signal, and the final selection must match both the field wiring and the PLC hardware.
This guide shows how to create a PLC I/O list, using a 12-point pump control example. You will identify digital and analog signals, prepare an I/O allocation table, calculate spare channels, and check the requirements for compatible modules. The example supports engineering review and purchasing.
1. What Is a PLC I/O List and Why Do You Need One?
A PLC input/output list, also called an I/O schedule or point list, records the signals exchanged between a controller and its field devices. A device inventory tells you what equipment exists. An I/O list tells you which signals the controller must actually read or command.
For wiring fundamentals, see CHENTUO's PLC Inputs and Outputs Explained. Here, we focus on the list and hardware planning.
What Information Should a PLC I/O List Include?
Record a unique tag, device or signal description, input/output direction, DI/DO/AI/AO classification, electrical interface, and any special conditions. Add the cabinet or field location where useful. Reserve columns for module, channel, hardware address, and review status, using TBD until approved.
For example, AI-01 | Tank level transmitter | AI | 4–20 mA | Address TBD identifies a signal. AI-01 is a project tag, not a universal hardware address.
Physical I/O Points vs. Communication Data
A physical I/O point uses a wired channel on the controller or an I/O station. Communication data travels through a supported network or serial connection. A VFD might use a wired DO for its run command, two DI points for status feedback, and an AO for its speed reference. If the PLC and drive exchange those functions through a compatible industrial network, some wired channels may no longer be required.
Keep network signals in a separate communications register or section of the schedule. Do not assume that Ethernet eliminates all hardwired signals. Required hardwiring depends on design and safety requirements.
2. Identify PLC Inputs and Outputs From Real Field Devices
Classify individual signals, not simply devices. One drive can require several points, while HMI communication may use none.
Digital Input (DI) Examples
Digital inputs report a discrete condition. A push button indicates an operator request, a limit switch indicates a position, and a proximity sensor reports detection. Float switches and configured VFD status contacts can also provide DI signals. Check voltage, contact arrangement, and PNP/NPN type.
Digital Output (DO) Examples
Digital outputs issue on/off commands to pilot lights, alarm beacons, contactor circuits, solenoid valves, or configured VFD control inputs. Verify output type, load ratings, and any interface protection. Never assume a PLC output can power a motor directly.
Analog Input (AI) and Analog Output (AO) Examples
Analog inputs receive measurements such as tank level and line pressure, often through 4–20 mA transmitters. Analog outputs send variable commands, such as a speed reference to a VFD or a position demand to a proportional actuator. Thermocouples and RTDs require inputs specifically rated or configured for those sensing elements, not just a generic 0–10 V channel.
|
Field device or signal |
Direction |
I/O type |
Typical interface |
|
Start push button |
Input |
DI |
Contact circuit |
|
Proximity sensor |
Input |
DI |
PNP or NPN |
|
Float or limit switch |
Input |
DI |
Contact circuit |
|
Tank level transmitter |
Input |
AI |
4–20 mA |
|
Pressure transmitter |
Input |
AI |
4–20 mA |
|
Pilot light |
Output |
DO |
Rated switching circuit |
|
Solenoid valve command |
Output |
DO |
Coil or interface relay |
|
VFD run command |
Output |
DO |
Drive digital input |
|
VFD fault feedback |
Input |
DI |
Configured status contact |
|
VFD speed reference |
Output |
AO |
0–10 V or 4–20 mA |
|
Proportional valve command |
Output |
AO |
Configured analog interface |
|
Thermocouple measurement |
Input |
Specialized AI |
Thermocouple-capable input |
Interfaces are illustrative; verify actual device and module specifications.
3. How to Build a PLC I/O List Step by Step
Create one traceable record per required physical signal.
Step 1: List Every Field Device and Its Function
Start with the process description, P&ID, equipment list, and control narrative. Include measuring devices, operator controls, actuators, alarms, and feedback contacts. For the pump example, "VFD" is not enough: specify whether the controller requires run command, running status, fault feedback, and speed reference. Each hardwired signal becomes an entry.
Step 2: Classify Each Signal as DI, DO, AI or AO
Assign the direction from the PLC's perspective. A status contact reporting a VFD fault is an input; a run command to the drive is an output. Then determine whether the signal is discrete or variable. Record network data separately. One device can use several points.
Step 3: Record Signal Ranges and Electrical Requirements
Write down the electrical interface while the field device documentation is available. Examples include 24 VDC DI, PNP sensor, 4–20 mA AI, and a relay-driven DO. For outputs, note the load voltage and current. For analog channels, record whether the loop is current or voltage, how it is powered, and any isolation requirements. These details determine electrical suitability.
Step 4: Assign Tags and I/O Addresses
Give each signal a consistent engineering tag, such as DI-01 or AO-01. Assign the actual rack, slot, channel, and PLC address only after the selected platform and hardware configuration are known. Tags and hardware addresses serve different purposes.
Step 5: Review Special Signals and Safety Requirements
Mark signals requiring special functionality, including RTDs, thermocouples, encoders, fast pulses, and high-speed counting. Emergency stops and protective interlocks require risk assessment and an appropriate safety architecture; a normally closed contact on a standard DI does not itself establish a safety-rated function.
Step 6: Review and Approve the I/O List
Ask the controls engineer to check command and feedback coverage, the electrical designer to verify interfaces, and the system integrator to confirm the I/O architecture. Purchasing should verify part numbers and quantities against the approved revision. Record unresolved items rather than making assumptions. Track revisions to prevent outdated purchasing lists.
4. Worked Example: PLC I/O List for a Water Pump Control System
System Requirements and Control Functions
Consider a hypothetical single-pump tank system. Its PLC reads two float switches, a level transmitter, a pressure transmitter, a low-pressure switch, an auto/manual selector, and VFD status contacts. It commands the VFD to run, provides a variable speed reference, operates an inlet solenoid, and activates an alarm beacon.
This hypothetical design assumes hardwired VFD control, not a commissioned or safety-approved project. The float switches provide separate threshold indications, while the analog level transmitter supplies a continuous measurement. The low-pressure switch provides a discrete threshold indication, distinct from the analog pressure measurement.
Example PLC I/O Allocation Table
|
Tag |
Device or signal |
Type |
Example interface |
Design note |
|
DI-01 |
Low-level float switch |
DI |
Contact |
Level threshold status |
|
DI-02 |
High-level float switch |
DI |
Contact |
Level threshold status |
|
DI-03 |
Auto/manual selector |
DI |
Contact |
Selected operating mode |
|
DI-04 |
VFD running feedback |
DI |
Status contact |
Confirm drive configuration |
|
DI-05 |
VFD fault feedback |
DI |
Status contact |
Confirm drive configuration |
|
DI-06 |
Low-pressure switch |
DI |
Contact |
Discrete pressure threshold |
|
DO-01 |
VFD run command |
DO |
Digital command |
Match drive input |
|
DO-02 |
Alarm beacon |
DO |
Switched output |
Check load rating |
|
DO-03 |
Inlet solenoid valve |
DO |
Switched output |
Check coil and protection |
|
AI-01 |
Tank level transmitter |
AI |
4–20 mA |
Verify loop power |
|
AI-02 |
Line pressure transmitter |
AI |
4–20 mA |
Verify scaling and range |
|
AO-01 |
VFD speed reference |
AO |
4–20 mA |
Confirm drive accepts current input |
The table uses engineering tags rather than invented hardware addresses. Once hardware is selected, add module, rack, slot, channel, terminal, and test references. Each record should trace to a configured channel.
How to Calculate the Required I/O Points
Count one point for each listed physical channel, then group them by type:
|
Signal type |
Required points |
|
DI |
6 |
|
DO |
3 |
|
AI |
2 |
|
AO |
1 |
|
Total physical I/O |
12 |
The system needs 12 physical points under the stated hardwired assumptions. That does not imply one 12-channel module will work. Digital inputs, digital outputs, analog inputs, and analog outputs must each have compatible capacity. Some PLC CPUs offer integrated I/O, while others require separate modules or remote I/O stations.
What Changes When the VFD Uses Industrial Ethernet?
With a supported network interface, the PLC might send the VFD run command and speed reference as communication data, while reading running and fault status through the same connection. In this example, those functions currently occupy one DO, two DI, and one AO channel. Moving them to the network can change the physical I/O schedule, provided the system design permits it.
However, the network choice must be verified against the specific drive and controller, including protocol, configuration, loss-of-communication response, and any required hardwired controls. A communication tag is not automatically an appropriate substitute for a safety function. If your project is still comparing drive interfaces, CHENTUO's variable frequency drive categories provide a relevant product starting point.
5. How Many PLC I/O Channels Should You Reserve?
Calculate Capacity by Signal Type
Work from four separate totals, not only the overall number of 12. The pump example requires six DI, three DO, two AI, and one AO. Check integrated CPU channels before selecting expansion modules. Distinguish required points from installed capacity.
Allow Spare I/O Capacity
A spare allowance can accommodate expected additions, but there is no universal percentage for every project. For illustration, apply a 20% allowance to each signal class and round upward:
|
Type |
Base requirement |
Calculation |
Planning minimum |
|
DI |
6 |
Round up 6 × 1.20 |
8 |
|
DO |
3 |
Round up 3 × 1.20 |
4 |
|
AI |
2 |
Round up 2 × 1.20 |
3 |
|
AO |
1 |
Round up 1 × 1.20 |
2 |
These planning minima total 17 channels across four types. They are not a recommended purchase list. For example, a compatible analog input module may be offered with four channels rather than three, and actual installed capacity may be higher. Choose the final spare allowance according to expansion plans, available module sizes, cabinet space, and budget.
Check Rack, CPU and Power Limits
A module can have the right channel count and still be unsuitable. Verify CPU expansion limits, rack or station configuration, backplane or field power requirements, terminal arrangements, and installation space. Verify these before releasing the bill of materials.
6. How to Select Compatible PLC I/O Modules
Match the PLC Platform Before Comparing Modules
Identify the manufacturer, controller family, CPU catalog number, and existing I/O architecture first. Then check which module family the platform actually supports. For replacements, compare the complete existing part number with manufacturer documentation, including relevant revision and configuration requirements. Matching the brand alone, or finding the same number of channels, does not prove interchangeability.
Verify Digital Input and Output Specifications
For DI, check the rated voltage, sensor interface, input thresholds, common terminals, isolation, and response characteristics. A PNP device and an NPN device do not necessarily work with the same input wiring arrangement. For DO, check whether the design calls for relay or transistor switching, the required voltage and current, the type of load, and any suppression or interface relay needed for an inductive coil. Use the exact module datasheet to confirm ratings.
Verify Analog Input and Output Specifications
Confirm supported ranges, wiring topology, loop power, resolution, accuracy, isolation, and scaling. In the pump example, both transmitters are assumed to provide 4–20 mA signals. The AO must also match the VFD's configured reference input. RTDs and thermocouples may require dedicated input capability and should not be treated as ordinary voltage sensors.
Compare Siemens and Allen-Bradley I/O Families
The correct module search starts with the installed control platform, not a generic brand filter.
|
Brand |
Platform examples |
Primary checks |
|
Siemens |
S7-1200, S7-1500, S7-300, ET 200 |
Supported module family, CPU or station interface, configuration |
|
Allen-Bradley |
ControlLogix, CompactLogix |
Supported I/O architecture, module family, revision and software requirements |
These platform names are examples, not interchangeable product lines. If you already know the controller family, browse CHENTUO's Siemens PLC modules or Allen-Bradley PLC modules. Confirm the catalog number against manufacturer documentation. Other brands appear in CHENTUO's PLC module category.
When Is Remote I/O a Better Choice?
Local I/O is practical when field devices are near the control cabinet. Remote I/O may be preferable when sensors and actuators are spread across equipment areas and long individual cable runs would complicate installation. Compare wiring, station power, network availability, environment, maintenance access, and platform support. Choose according to system layout.
7. Common PLC I/O Planning Mistakes to Avoid
Use the approved I/O list to reconcile drawings, program tags, and purchased modules.
Incorrect Signal Type or Electrical Rating
Assigning a 4–20 mA transmitter to a digital input, selecting a voltage-only AI for a current loop, or overloading a DO channel can make the installation unusable or damage hardware. Confirm signal specifications on both sides of each connection before finalizing the module list.
Incompatible Module or Insufficient Capacity
A module with eight input channels may still be incompatible with the controller rack or required field voltage. Count the usable channels by signal type and compare the complete module family, electrical specifications, expansion limits, and relevant configuration requirements.
Missing Feedback or Special I/O Requirements
A list containing only a VFD run command but no required status feedback may leave the control narrative incomplete. Check for alarms, selector switches, analog measurements, special pulse inputs, and separately specified safety functions. Compare each control requirement with a signal entry or an explicitly documented communication data item.
8. PLC I/O Module Procurement Checklist
Information to Prepare Before Requesting a Quote
A useful technical request for quotation should include:
- PLC manufacturer, controller family, and complete CPU catalog number.
- Existing module part number or proposed replacement, if known.
- Required DI, DO, AI, and AO channels, plus the planned spare capacity.
- Voltage, current, sensor interface, output load, and special input requirements.
- Rack or remote station details and relevant revisions, where applicable.
- Required quantity, delivery destination, and requested schedule.
- The latest approved I/O list or drawings when module selection is still open.
If you are buying an exact replacement, the full part number and hardware details are especially useful. For new systems, send the I/O schedule and signal specifications.
How CHENTUO Can Support Module Sourcing
You can use the Model Library to explore part-number information or browse the relevant PLC module category. When you have a target catalog number or a reviewed I/O requirement, request a quotation from CHENTUO with the model, quantity, and destination. Confirm exact compatibility and commercial terms for each request.
FAQ

How do you calculate PLC I/O points?
How much spare I/O capacity should a PLC system have?
Does a VFD require PLC input and output points?
Does an HMI consume physical PLC I/O channels?
Can a thermocouple connect to any analog input module?
How can I confirm an I/O module is compatible with my PLC?
10. Conclusion: From I/O Planning to the Right PLC Modules
A useful PLC I/O list begins with the functions your machine must perform. Identify each physical signal, record its electrical requirements, build a traceable point schedule, and calculate channel capacity separately for DI, DO, AI, and AO. Only then should you finalize compatible module families and part numbers.
The pump example provides a starting format, but the approved design and manufacturer specifications determine the final hardware. If your I/O list is ready, explore CHENTUO's PLC modules or send your module details for a quote.

