Cable Schedule Template for Instrumentation.
What belongs in an instrumentation cable schedule, how to structure it for E&I design and procurement, and how to build the first draft directly from a P&ID I/O list.
The cable schedule is where instrumentation design meets construction. E&I designers use it to route cables and locate junction boxes. Procurement uses it to purchase cable and glands. Commissioning uses it to trace terminations. Done well, it is the single source of truth for every instrument signal path in the plant. Done poorly, it is a drain on the entire project.
This covers what belongs in an instrumentation cable schedule, how to structure it so downstream users actually use it, and how to build the first draft directly from an I/O list.
Essential columns
Every cable schedule should include these columns at minimum.
| Column | Purpose | Example |
|---|---|---|
| Cable tag | Unique identifier for the cable | INST-0145 |
| From | Originating end, field device or junction box | FIT-101 |
| To | Terminating end, junction box or marshalling | JB-A-03 |
| Instrument tag | The instrument the cable serves, for multi-pair cables, list each pair's instrument | FIT-101 |
| Signal class | AI, AO, DI, DO, fieldbus | AI |
| Cable type | Per site cable class library | Type A: 18/2 TSP |
| Size | Conductor gauge | 18 AWG |
| Cores, pairs | Number of pairs or cores in the cable | 2 pair |
| Length | As-routed or estimated | 145 m |
| Routing | Tray or conduit reference | Tray T-103 |
| IS barrier | Intrinsic safety barrier, if applicable | MTL 7787+ |
| Notes | Special installation notes | 30 mV immunity required |
Full column reference
A complete instrumentation cable schedule has more columns than the minimum set. The additional columns are not optional on regulated or hazardous-area installations.
| # | Column | Description | Who populates it |
|---|---|---|---|
| 1 | Cable tag | Project-unique identifier. Format. Prefix plus sequential number, such as INST-0145 or C-A-0145. Primary key for junction box schedules and installation drawings. | E&I designer |
| 2 | From equipment | The originating field device tag, junction box tag, or marshalling cabinet reference. Use the exact equipment tag, FIT-101, JB-A-03, not a description. | E&I designer |
| 3 | To equipment | The terminating junction box, marshalling cabinet, or panel reference. Same format rule. Exact tag. | E&I designer |
| 4 | From terminal | Terminal number at the originating end. JB-A-03, terminal 7 plus. Without this, installation crews can't make the connection without back-checking the junction box schedule. | E&I designer |
| 5 | To terminal | Terminal number at the terminating end. MCC-101, TB-2, terminal 14 plus. | E&I designer |
| 6 | Instrument tag | The instrument served by this cable. For a multi-pair cable, this lists each instrument served. Join key back to the I/O list. | I&C engineer |
| 7 | Signal class | AI, AO, DI, DO, or fieldbus designation. Drives cable type selection and segregation group. | I&C engineer |
| 8 | Function | What the signal does. Transmitter signal, valve positioner, solenoid control, position feedback, HART communication, power supply. More descriptive than signal class alone. | I&C engineer |
| 9 | Cable type | Code from the site cable class library, Type A 18, 2 TSP, Type B 16, 4, Type C fieldbus. Never free text. | E&I designer |
| 10 | Conductor count | Number of conductors or pairs. A 4-conductor cable is listed as 4C or 2P depending on the site convention. | E&I designer |
| 11 | Conductor size | AWG or mm2. 18 AWG, 1.5 mm2. Required for voltage drop calculations on long runs. | E&I designer |
| 12 | Estimated length | Length derived from a preliminary route on the plot plan. Used for procurement. Replaced by as-routed length after construction. | E&I designer |
| 13 | As-routed length | Final measured length after cable installation, from drum records or field measurement. Updates the estimated length at as-built stage. | Construction |
| 14 | Cable drum | Drum number from the purchase order. Used to trace which physical drum was installed where. Important for as-built records and spare-length documentation. | Construction |
| 15 | Tray, conduit route | The cable tray or conduit reference the cable runs through. T-103, C-045. Used for tray fill calculations and fire zone documentation. | E&I designer |
| 16 | Segregation group | Which segregation group the cable belongs to. See segregation rules below. | E&I designer |
| 17 | Fire rating | Whether the cable is fire-resistant or circuit-integrity rated. Required for critical safety circuits. FP-rated, MICC, or XLPE-FR per site specification. | E&I designer |
| 18 | Shield grounding | How the cable shield is grounded. One-end ground, instrument end is standard for analog signals. Both-end ground creates ground loops. Document the actual termination. | E&I designer |
| 19 | IS classification | Intrinsic safety classification if applicable. Ex ia IIC, Ex ib IIC. Ties to the barrier schedule. | IS engineer |
| 20 | IS barrier tag | Tag of the zener barrier or galvanic isolator in the marshalling cabinet that protects this circuit. Blank for non-IS circuits. | IS engineer |
| 21 | Status | Design status. Preliminary, issued for procurement, issued for construction, as-built. Tracks the cable through the project lifecycle. | Document control |
| 22 | Notes | Special requirements, deviations from standard, open items. "Requires separate tray from power cables", "Confirm gland size with vendor". | Engineer |
Worked example rows
Three cables from the separator skid example, covering different signal types and installation conditions.
| Cable tag | From | To | From terminal | To terminal | Inst. Tag | Class | Function | Type | Cores | Length | Seg. Group | Fire rated | Shield ground |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| INST-0145 | FT-101 | JB-A-03 | , | TB-1, 7 plus | FT-101 | AI | Flow transmitter signal | 18, 2 TSP | 2 | 145 m | IS-A | No | Instrument end |
| INST-0146 | JB-A-03 | MCC-101 | TB-1, 7 plus | TB-2, 14 plus | FT-101 | AI | Flow transmitter signal | 18, 2 TSP | 2 | 62 m | IS-A | No | Instrument end |
| INST-0201 | PT-2034A | MCC-101 | , | TB-3, 22 plus | PT-2034A | AI | Pressure transmitter | 18, 2 TSP | 2 | 210 m | GP-B | No | Instrument end |
| INST-0302 | LSH-405 | SIS-101 | , | TB-4, 6 | LSH-405 | DI | SIS high-high level trip | 16, 2 TSP | 2 | 195 m | IS-A | Yes | Instrument end |
FT-101 uses two cable rows because it runs from the field device to junction box JB-A-03 and then from the junction box to the marshalling cabinet MCC-101. Each physical cable is one row. LSH-405 runs directly to the SIS cabinet and is fire-rated because it is a safety trip circuit.
Segregation rules
Cable segregation prevents electrical noise on one circuit from interfering with another. Most instrumentation specifications define at least three segregation groups.
**IS Group, intrinsically safe. ** Circuits associated with equipment in hazardous areas under the IS system. These cables must run in dedicated IS cable trays, colored blue throughout most jurisdictions, and must not share a tray with any general-purpose or power cable. The maximum cable capacitance and inductance are constrained by the barrier parameters.
**General Purpose Signal Group, GP. ** Analog and discrete instrument signals in non-hazardous areas or in Zone 2, Division 2 areas without IS classification. These run in dedicated instrument signal trays, separated from power cables by the minimum distance specified in the cable layout specification, commonly 300 mm for cables over 240V.
**Power Group. ** Instrument power supplies, solenoid drivers above 24VDC, and motor cables. These run in power cable trays and must not share trays with signal cables.
**SIS Circuits. ** Some specifications create a fourth segregation group for SIS wiring, with dedicated trays and conduit separate from BPCS signal cables. This is required on high-SIL systems and is a common finding during functional safety audits when not done.
For cables that must cross between groups, for example, a signal cable crossing a power cable tray route, the crossing should be at 90 degrees and documented in the routing notes.
Handling multi-core cables
A multi-core cable carries several instrument signals in a single jacket. The cable schedule lists it as one row, with the core count reflecting the total number of conductors. Each pair within the cable is assigned to a specific instrument tag, noted in the Instrument Tag column or in a separate pairs schedule attached to the cable schedule.
The advantage is reduced tray fill and lower cable procurement cost. The risk is that if one pair develops a fault, all instruments on that cable may need to be taken out of service simultaneously. For SIS signals, multi-core cables shared with BPCS signals are prohibited. Each SIS circuit requires a dedicated cable.
For discrete signals, it is common to assign multiple DI or DO points to a single multi-core cable. Each pair carries one signal. The cable schedule row shows the total core count. The junction box schedule or a pairs table maps each pair number to an instrument tag.
Junction box assignment
Junction boxes consolidate field wiring before it runs back to the marshalling cabinet. The cable schedule drives junction box design in two ways. Each cable going to a junction box contributes to the terminal count, and each cable entering or leaving a junction box appears as a row in the cable schedule with that junction box as the From or To reference.
To size a junction box, count all cable entries from the cable schedule for that junction box tag, sum the terminal counts, one terminal per conductor for most installations, add 20% spare, and select the enclosure size from the site standard.
For large plants, junction box assignments should be made on the cable schedule before detailed design begins. Instruments that are physically close should share a junction box. Instruments scattered across a process area may need multiple junction boxes. The cable schedule is the working tool for this optimization.
Length estimation methods
Cable lengths on the preliminary cable schedule are estimates used for procurement. Three common estimation methods.
**Plot plan scaling. ** Measure the straight-line distance on the plot plan between the instrument location and the nearest junction box or marshalling cabinet. Apply a multiplying factor, commonly 1.25 to 1.4 to account for vertical runs, routing around obstructions, and cable tray curvature. This is the most common method and is accurate enough for procurement at a 10-15% tolerance.
**3D model extraction. ** When a 3D plant model exists, the cable routing tool extracts routed lengths from the model. This is the most accurate method and is used for issued-for-construction cable schedules on large EPC projects.
**Historical ratios. ** For early-stage estimates where no plant layout is available, historical data from similar projects provides a length per instrument type, for example, 150 m average per analog transmitter in a typical refinery unit. This is used for feasibility studies only. It is not accurate enough for procurement.
Build the first draft from the I/O list
The I/O list contains. Tag, signal class, description, connected equipment, source P&ID page. That is enough to generate a first-pass cable schedule entry per instrument.
- One cable per analog instrument, AI or AO, typically 18, 2 TSP
- One cable per discrete instrument, DI or DO, typically 16, 4 multi-core or shared multi-pair
- Cable tag from a project-specific numbering scheme, e.g.
INST-<sequential> - Pre-populated cable type from the site class library, keyed on signal class
- Routing left blank for detailed design
Detailed design still owns routing and junction box assignment, but the metadata side of the schedule, instrument tag, signal class, cable type, core count can be populated from the I/O list in one shot. If the I/O list needs to be structured with signal-class, area-classification, and protocol columns before that transfer, the I/O list creation guide covers the column conventions that make this population step reliable.
See P&ID to I/O list for the extraction workflow that generates the I/O list the cable schedule is built against.
Version control
Cable schedules change through design. Each revision should be issued against the corresponding P&ID revision. When the P&ID adds an instrument, the cable schedule gains a row. When the P&ID removes an instrument, the cable schedule should mark the corresponding cable as removed rather than deleting it silently. Construction may have already procured that cable.
For brownfield projects that retrofit existing plants, the cable schedule for new-work cables lives alongside an as-built cable schedule for existing wiring that is being reused. Mixing these on a single sheet causes mistakes during installation.
Related
- P&ID to I/O list. The source the cable schedule is built against
- Cable schedule template. Pre-formatted Excel template with all columns
- 4-20mA vs HART vs fieldbus. Signal type determines cable type
- PLC tag naming conventions. Consistent tags across I/O list and cable schedule
- Commissioning loop check plan. Cable schedule drives termination verification
- API RP 552 instrument requirements. Segregation and sizing requirements that shape the cable schedule on API-governed projects
FAQ
How do I document shield grounding on the cable schedule.
Add a Shield Grounding column with a controlled vocabulary. "instrument end", "cabinet end", "both ends", "none", or "N, A", for unshielded cables. For analog 4-20mA signals, instrument-end grounding is standard practice because it prevents ground loops that cause offset errors. Cabinet-end grounding is sometimes specified for safety circuits. Both-end grounding is prohibited for analog signals in most specifications. Document what was actually installed at as-built stage, because field crews sometimes deviate from the design and the as-installed ground configuration affects troubleshooting.
What is the difference between a cable schedule and a termination schedule.
The cable schedule documents the cable itself. Its tag, route, type, and both ends. The termination schedule, or wiring schedule documents each individual wire within a cable. The wire number, the from-terminal, the to-terminal, and the function. The cable schedule is used for procurement and routing. The termination schedule is used by electricians for making connections. On simple projects, the two are combined in one document. On complex projects, they are separate, with the termination schedule referencing the cable schedule by cable tag.
When should IS circuit lengths be verified against the barrier entity parameters.
Before the cable schedule is issued for construction. Every IS circuit has a maximum allowable cable capacitance and inductance specified by the barrier or isolator manufacturer. The installed cable has a capacitance and inductance per meter. Multiply by the cable length to get the total for that circuit and verify it falls within the barrier limit. If the design length exceeds the limit, the circuit must use a lower-capacitance cable type or the barrier must be changed. This check is typically done by the IS engineer using the entity parameter certificates for the transmitter and the barrier.
How are fieldbus segment cables documented in the cable schedule.
Each physical cable on a fieldbus segment is one row, with the signal class set to the bus designation, PROFIBUS PA, Foundation Fieldbus, or similar. The Instrument Tag column lists all devices on that segment, separated by commas, or references a segment schedule. The cable type must match the fieldbus standard, for example, PROFIBUS PA requires type A cable. 18 AWG shielded twisted pair with a characteristic impedance of 100 ohms. Segment length limits apply to the total segment, so the cable schedule for a fieldbus segment should note the cumulative segment length, not just the individual trunk cable length.
What fire rating is required for SIS cables.
It depends on the applicable standard and the facility's fire protection specification. IEC 61511 requires that SIS cables maintain circuit integrity during a credible fire event for long enough that the safety function can be executed. In practice this means fire-resistance-rated cables, FP or FR designation for SIS trip circuits that run through fire-risk areas, or mineral insulated cables, MICC for the highest-rated installations. The fire zone classification for each tray section should be documented in the routing notes column, and the cable fire rating should be specified per fire zone, not as a blanket project requirement.