Cable schedule software for instrumentation IO lists
By Saad, practising automation engineer · Updated 2026-09-25
Every field cable, junction box, and marshalling strip accounted for.
Cable scheduling from the same IO list as the loop diagrams: auto-assign cables, junction boxes, terminals, and marshalling points from your project standards, then export a schedule that matches the issued drawings.
Assignment engine
Tell the app your rules — card capacities, strip sizes, cable core counts — and it assigns JBs, terminals, and cables while respecting them.
Consistent naming
Cable IDs, terminal numbers, and strip references follow your project conventions, so the schedule reads like your client expects.
Register-linked
The cable schedule is a view over the same loop and signal data as the Loop Register. No separate spreadsheet to keep in sync.
One row per field cable, not per signal
When several signals share a cable ID, from, and to, they collapse to one schedule row. Core count is the shared declared count, never a sum of signals. Mixed types on one ID leave type blank so you do not ship a lie.
Where cable IDs come from
If the IO list already has a field cable column, that value is kept. Otherwise auto-assignment fills IDs from the project cable template. Changing a tag later does not renumber a cable you already issued.
Free tool versus the project schedule
The public cable-schedule tool is ten rows and a CSV. The issued schedule in the package is built from every wired signal on the project. Start with the free template if you do not have a vendor list yet.
What cable schedule software does here
A cable schedule is one row per field cable: Cable ID, type, core count, from, to, loop tag, optional length and route. Cable scheduling is not a tray-fill or 3D routing package. SchematicForge fills the instrumentation schedule from loop data so the drawing, register, and schedule cannot disagree.
Worked row: C-F-1001, Instrument, 2 cores, From JB-01, To PT-1001, Loop PT-1001, 120 m, Tray T1. If PT-1001 and a spare pair share that ID, they stay one row. Core count stays 2 — never 2 + 2.
Start without an account
Need a blank sheet today? Download the ungated cable schedule Excel template. Need ten cables in a CSV? Use the free generator. Need the project schedule that matches issued loop diagrams? Upload the IO list on the homepage.