Cable Schedule Template for Instrumentation

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. For the term itself and the fields it carries in electrical work, see what a cable schedule is.

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.

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.

Worked example rows

Three cables from the separator skid example, covering different signal types and installation conditions.

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.

Following one signal from the field device to the panel terminal

A cable schedule looks like a list of cables. It reads better as one path cut into segments at every point where a conductor lands on a terminal. Take FT-101, a 4-20mA flow transmitter on the separator skid in Unit 34, in a Zone 1 IIB T4 area, reporting to an AI channel in the system cabinet.

At the field device. The cable enters the transmitter through a certified gland sized to the cable outside diameter and matched to the enclosure protection concept. Two conductors land on the transmitter terminals, and the screen drain is landed or cut back depending on which end the site standard earths. The schedule carries gland type and size and the terminal numbers at that end.

Field cable to the local junction box. One pair, typically 18 AWG twisted and individually screened with a drain wire. This is INST-0145, from FT-101 to JB-A-03, terminals 7 and 8 on TB-1. One row.

The junction box terminal strip. This is where the cable tag changes. The conductor is broken, so what leaves the box is a different physical cable with a different tag carrying the same signal. The screen passes through on a dedicated terminal rather than bonding to the enclosure.

Multicore trunk back to the marshalling cabinet. INST-0146 is not FT-101's cable. It is a 12-pair overall screened trunk serving every instrument on JB-A-03, and FT-101 occupies pair 3. One row, with twelve instrument tags against it or a pairs table attached.

Marshalling terminal, barrier, and I/O channel. The trunk pair lands on TB-2, terminals 14 and 15 in MCC-101, then cross-wires into the hazardous side of the IS barrier or galvanic isolator and out of the safe side into the system cabinet, where it terminates at a rack, slot and channel address. Cross-wiring inside a cabinet usually carries no cable tag and belongs on the termination schedule, which is where signals go missing at commissioning.

Why one signal makes several rows. A cable tag identifies a physical length of cable between two terminations, not a signal. Every time the conductor is broken at a terminal strip the cable ends and a new one begins, so the row count follows the terminations rather than the instruments. Carry the instrument tag on every segment row, because it is the one column that stitches the path back into a single signal.

Screen earthing at one end only. The site standard names the end. Whichever end it names, every segment of the same signal must agree, and the junction box screen terminal must float rather than bond to the enclosure so the drain reaches the earthed end as one continuous conductor. Record the intent on every segment row, and record what was actually installed at as-built.

Spare core policy. Trunks are bought with spare pairs, commonly one pair in five, rounded up to the next standard size. Spares only survive if they are scheduled. Give each spare pair its own row against the trunk cable tag, marked SPARE, with the terminals it lands on at both ends. A spare that exists only in the cable specification gets consumed at commissioning and never recorded.

IS segregation sets the trunk count, not the box count. An intrinsically safe pair never shares a multicore with a non-IS pair, so a junction box serving both needs two trunks, two terminal strips with the specified separation, and two rows. Assign the segregation group before junction box assignments are frozen, or the box sizing is wrong.

Drum lengths against routed lengths. Procurement buys drums. Forty cables at 145 m each is a cutting problem, not 5,800 m of cable: a 1,000 m drum yields six 145 m runs and 130 m of offcut. Issue a drum schedule mapping drum numbers to the cable tags cut from them, and keep estimated length and as-routed length in separate columns. Procurement settles against the estimate; the IS capacitance check is re-run against the as-routed value.

Reconciliation against the I/O list and the loop diagram. Three checks at every issue, keyed on instrument tag and terminal rather than on cable tag. Every I/O list row has at least one cable schedule row naming its tag. Every cable schedule row naming an instrument tag finds that tag on the I/O list. The loop diagram shows the same terminal numbers at both ends of every segment. The failures this catches are consistent: a deleted instrument whose cable is still scheduled and already ordered, a signal moved to another junction box without the trunk pair count being updated, and a reassigned I/O channel with the marshalling cross-wire not redrawn.

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.

1. One cable per analog instrument, AI or AO, typically 18, 2 TSP
2. One cable per discrete instrument, DI or DO, typically 16, 4 multi-core or shared multi-pair
3. Cable tag from a project-specific numbering scheme, e.g. INST-<sequential>
4. Pre-populated cable type from the site class library, keyed on signal class
5. 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
• Reading cable schedules. Working from a schedule someone else issued
• 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
• Cable schedule template. The 12-column schedule described above, pre-formatted, with the signal-class column enforced

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.

Further reading

• junction box schedule template