The short answer
Cable Schedules
A cable schedule is a table with one row per cable: the cable number, its type described by conductor count, size, shielding, insulation, and voltage rating, the signal class it carries, the equipment and terminal it starts from, the equipment and terminal it ends at, the route through named conduits or trays, the estimated and installed length, the spare conductors, and the status from designed through pulled, terminated, and tested. It is produced from the I/O list, the instrument list, and the drawings, it is what the contractor prices and pulls from, it is what the electrician terminates from with the interconnection diagram, and after construction it is corrected to what was installed and kept as the record that a future change consults before pulling a new cable through a conduit that is already full.
Key points
- One row per cable, with a unique number that appears on the cable tag at both ends.
- Type, class, from, to, route, length, spares, status: the columns that answer every question anyone asks about a cable.
- The signal class decides the separation; the schedule is where mixed-class conduits are caught.
- Lengths from the schedule are what gets bought; a schedule ten percent short is a project that stops for a delivery.
- Status tracks the field: pulled, terminated, tested, with dates.
- The as-built schedule is the record of what is in each conduit and which spares exist.
The columns
| Column | Content | Note |
|---|---|---|
| Cable number | Unique identifier per the convention | On the cable tag at both ends and on every drawing |
| Description | What the cable serves: the loop, the motor, the device | A person can find it without decoding |
| Type | Conductor count and size, shield, insulation type, jacket, voltage rating, armor | Enough to order it |
| Signal class | Power, motor, drive output, AC control, DC control, analog signal, communication, fiber | Decides routing and separation |
| From | Equipment tag, panel, terminal strip, and terminals | The panel end, usually |
| To | Equipment tag, junction box or device, and terminals | The field end |
| Route | Conduit or tray numbers in order | Cross-referenced to the conduit schedule |
| Length | Estimated from the route plus terminations, then measured | Buy from the estimate with margin; record the installed |
| Conductors used and spare | Which conductors carry what; which are spare | The spares are the future |
| Terminations | Shield termination point; connector types where applicable | Shield at one end for signals |
| Status | Designed, ordered, pulled, terminated, tested, with dates and initials | The construction tracker |
| Notes | Special handling, minimum bend radius, temperature rating, plenum | Anything the puller needs to know |
Numbering
A cable number encodes enough to find the cable without the schedule and is unique across the project. Common conventions build it from the destination equipment tag and a sequence, so that every cable to pump P-101 is P101-C1, P101-C2 and so on; or from the origin panel and a sequence; or from the loop number for instrument cables. The convention is stated in the project standard, the numbers are assigned in the schedule and never reused, and the tag on the cable matches the schedule exactly. A cable renamed in the field and not in the schedule is a cable that will be cut by mistake.
Class and route
The signal class of a cable is what decides where it may run: analog and communication cables away from power and drive cables, drive output cables in their own conduit, control wiring in its own. The schedule carries the class and the route, and a review of the schedule sorted by conduit finds the conduit where a drive cable and a signal cable were both assigned, before they are pulled. The conduit schedule, a companion list with one row per conduit giving its size, route, and fill, is where the fill is checked from the cables the schedule assigns to it.
Through construction
- 1
Design
The schedule produced from the I/O list, the instrument list, the motor list, and the drawings, with types and routes, and reviewed for class separation and fill.
- 2
Procurement
Lengths summed by type with a margin for terminations, slack, and mistakes; the schedule is the takeoff.
- 3
Pulling
The contractor works from the schedule, tags each cable at both ends as it is pulled, and records the pulled status and the installed length.
- 4
Termination
The electrician terminates from the schedule and the interconnection diagram, records the terminated status, and marks any conductor or terminal change on the record set.
- 5
Testing
Continuity and insulation on power cables, continuity and shield isolation on signal cables, optical loss on fiber, recorded per cable with the date.
- 6
As-built
The schedule corrected to what was installed: routes, lengths, spares, and any cable added or deleted, issued with the record drawings.
Generated from the database
Panel design and plant engineering software produce the cable schedule from the same database as the I/O list and the wiring diagrams, and a change in one appears in all. A schedule kept as a spreadsheet works for a small project when one person owns it and the discipline holds; it fails when the I/O list is changed and the schedule is not. Either way, the schedule is a controlled document with a revision, and the as-built revision is the one that is kept.
Frequently asked questions
- Do we schedule the cables inside a panel?
- No; panel wiring is on the wiring diagram. The cable schedule covers cables that leave a panel: to the field, to another panel, to a motor, to a junction box. The boundary is the panel terminal strip.
- How much spare should a multiconductor cable have?
- A pair or two per cable for instrument and control cables, landed on spare terminals at both ends, and more on long runs to remote junction boxes where pulling another cable is expensive. The schedule records which conductors are spare so that they can be used without a site visit to find out.
- Who keeps the schedule after the project?
- The utility, as a controlled document with the drawings, updated by every change record that adds, removes, or reroutes a cable. The integrator or the contractor hands over the as-built schedule; the utility keeps it true.
- What about cables that the contractor routed differently from the schedule?
- The as-built records what was done, not what was planned. The contractor marks the change, the engineer reviews it for class separation and fill, and the schedule is corrected. A route change that mixed a signal cable into a power conduit is a finding to fix, not to record.
Related topics
- Wiring DiagramsThe drawing that says where every wire goes: panel wiring and interconnection diagrams, and the conventions of wire numbers, conductor colors, terminal numbers, and cable numbers that make them readable. What belongs here versus on the schematic.
- I/O ListsThe document that ties the field to the controller: what every I/O list column means, how tags, terminals, and module channels are assigned, spare capacity rules, how the list drives the drawings and the program, and how to keep it true after commissioning.
- Instrument ListsThe index of every measuring and final control device on a project: what the instrument list records, how it grows from the P&ID into specification sheets and calibration records, the columns that matter at each stage, and how it becomes the asset register the utility maintains.
- Fiber SchedulesThe record of every fiber strand between every pair of patch panels: cable identifiers, strand numbers and the standard color sequence, fiber type, connectors, what each strand carries, splices, lengths, and test results, with the labeling that matches it.
- Cable Routing ProblemsNoise that comes from where a cable runs: signal cables sharing a conduit, tray, or wireway with power or drive cables, long parallel runs, and shallow crossings. How coupling works, the separations that prevent it, and how to find the shared path.
- Commissioning ChecklistFrom energization to handover: the sequence of commissioning activities for a control system, the prerequisites and records for each, who signs what, and the checklist that keeps a project from being declared finished while half of it has never been tested.
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.