How to Write a PLC I/O List for a Retrofit
A PLC I/O list for a retrofit is a table with one row for every signal the new controller will read or write. Each row records the tag, description, signal type, range, location, wiring reference, alarm needs and spare status. Build the first draft from existing drawings and the old program. Then walk the plant to check each point against what is actually installed, and have operations, maintenance and the integrator sign the list off before any programming starts.
Why does a retrofit need its own I/O list?
On a new installation the I/O list comes from the design. On a retrofit it has to describe a plant that already exists, and that plant has often changed since the drawings were last updated. Instruments get swapped, spare cores get used, and temporary links become permanent.
Panel layouts, terminal plans, programming, HMI screens, loop checks and acceptance tests all depend on the I/O list. If the list is wrong, every one of those documents carries the error forward, and it usually comes to light during a shutdown window, when there is the least time to fix it.
If drawings are incomplete or missing, start with surveying a plant with missing control drawings before drafting the list.
Which columns should a PLC I/O list template include?
Keep the columns consistent across the whole project. A column that is empty for some rows still tells the reader that someone thought about it.
| Column | What it records | Why it matters |
|---|---|---|
| Tag | Unique identifier following the site naming convention | Links the point across drawings, program, HMI and historian |
| Description | Plain-language function, for example "Tank 2 outlet valve open" | Lets operators and maintenance confirm the point without reading code |
| Signal type | DI, DO, AI, AO, or a network signal, with voltage or current standard | Sets which card type is needed and how the point is wired |
| Range and units | Engineering range, units and fail direction | Drives scaling and makes faults recognisable |
| Location | Field device position and the panel or junction box it lands in | Lets someone find the point during survey, checks and faults |
| Wiring reference | Cable number, core, terminal, and old and new card and channel | Supports the cutover plan and the loop checks |
| Alarm needs | Whether the point alarms, at what condition, and its priority | Feeds alarm design and keeps alarm decisions from being left to programming |
| Spare | Whether the channel is a spare, and the spare allowance per card | Keeps capacity for later changes |
| Notes and status | Survey findings, open questions, verification status | Shows which rows have been checked and which are still assumed |
Some projects add columns for interlock or safety involvement, the source document, or the person who verified the row. Add these where they help. Keep anything that touches a safety function clearly marked, because changes to it need review by a qualified assessor. See planning a safety assessment for a machine retrofit.
What does a filled-in sample look like?
Illustrative example: a few rows from a pump skid retrofit. The tags, ranges and references are invented for illustration only.
| Tag | Description | Signal type | Range / units | Location | Wiring reference | Alarm needs | Spare |
|---|---|---|---|---|---|---|---|
| P101_RUN | Pump 101 running feedback | DI, 24 V DC | On/Off | MCC-1, starter 3 | Cable C-112 core 4, TB2-15, new DI card 1 ch 3 | Alarm if commanded on and no feedback | No |
| P101_START | Pump 101 start command | DO, 24 V DC relay | On/Off | MCC-1, starter 3 | Cable C-112 core 5, TB3-02, new DO card 1 ch 0 | None | No |
| LT201 | Tank 201 level | AI, 4–20 mA | 0–3.0 m, fails low | Tank 201 side, JB-2 | Cable C-205 pair 1, TB4-01/02, new AI card 1 ch 0 | High, high-high, low; priorities per alarm philosophy | No |
| FV202_POS | Valve 202 position command | AO, 4–20 mA | 0–100 % open | Line 2 manifold, JB-2 | Cable C-206 pair 2, TB5-03/04, new AO card 1 ch 1 | Alarm on position deviation | No |
| SPARE_AI_1_07 | Spare analogue input | AI, 4–20 mA | — | Panel CP-1 | TB4-15/16, new AI card 1 ch 7 | — | Yes |
Each row gives enough detail for someone to find the point, wire it, program it and test it without asking anyone.
How do you verify each point on a plant walk?
Treat the draft as a list of assumptions until each row has been checked against what is installed. Walk with someone from maintenance who knows the plant, and work on a printed or tablet copy you can mark up.
For each point, check:
- The field device exists, matches the description and carries a readable tag.
- The cable number and terminals at both ends match the wiring reference.
- The instrument range on the device or its configuration matches the list.
- The signal type and power source match, including whether loops are powered from the panel or the field.
- Points that exist in the field but not on the list, and points on the list with no field device.
- Wires landed on old card channels that the documentation shows as spare.
Mark each row as verified, corrected or unresolved, and note who checked it. Follow approved access and isolation procedures throughout. Do not lift wires or force signals as part of a survey.
The same walk is a good time to look at panel condition. See assessing control panel reuse for a retrofit and checking site readiness before controls installation.
How do you agree the list before programming starts?
Hold a review with operations, maintenance and the integrator, and go through the list row by row. Settle three things in that review: whether each point is needed, what it alarms on, and how much spare capacity to leave.
Then put the list under revision control. Give it a revision number, record who approved it, and send all later changes through a simple change request. The agreed list should match the functional design specification, and it becomes the reference for loop checks and acceptance testing. See performing instrument loop checks before startup.
Programming can begin on unresolved rows if they are clearly flagged. Do not let the program become the place where those questions are quietly answered.
What common mistakes should you avoid?
Copying the old program's I/O table as the final list. It shows what the old controller was configured for, which may not match what is wired.
Leaving ranges blank. If the range is missing, the scaling gets guessed, and that kind of error looks plausible on screen.
Mixing naming conventions. Agree the tag format first. Renaming points later breaks links to the HMI and historian.
Treating spares as an afterthought. Decide the spare allowance per card type during design, not when the panel is full.
Leaving alarms to the programmer. Alarm conditions and priorities are operational decisions. For background, see why operators ignore alarms.
Forgetting network and soft signals. Data exchanged with drives, other controllers or supervisory systems needs rows too, even though there is no terminal.
No owner after approval. If nobody owns the list, it stops matching the plant by commissioning.
When does this approach not apply?
For a small like-for-like controller swap, where the old program is converted directly and no wiring changes, a full re-survey may be more than you need. A targeted check of changed or doubtful points can be enough. Even then, record the verification, because the list will still be the reference for testing and handover.
Frequently asked questions
Should the I/O list be a spreadsheet or a database?
A controlled spreadsheet is enough for most retrofits. What matters is one master copy, revision control and a clear owner, not the tool.
How much spare I/O should a retrofit include?
There is no universal figure. Agree it with the plant based on expected changes, card sizes and panel space, and record the decision.
Who should own the I/O list?
Usually the integrator maintains it during the project, and the plant takes ownership at handover. Write that down so the list stays current.
Can the I/O list replace a functional design specification?
No. The list says what signals exist. The specification says how the system uses them. Each needs the other.
If you would like help preparing an I/O list or surveying a plant before a retrofit, see our services or contact us.