A cable schedule is the master register of every cable in an installation, listing each one by its unique number along with its type, size, where it runs from and to, the routes and trays it follows, and its length. It is the single document that answers, for any cable on a project, what it is and where it goes. Electrical and instrumentation teams use it to buy cable, plan routes, manage tray fill, and drive the physical installation.
Cable Schedule in one line: A cable schedule is the master register that lists every cable by number, type, size, from-to routing, tray, and length. It drives procurement, tray fill, and installation, and it ties directly to the loop diagrams and the SCADA I/O list so every cable can be traced to the signals it carries.
The cable schedule takes the form of a table where each row is one cable and the columns capture everything the project needs to know about it. The heart of every row is the cable number, a unique identifier that will also be printed on the cable's tags in the field. Around that number sit the essential attributes: the cable type and specification, the number and size of cores, and the from and to points that state exactly where each end terminates, typically a piece of equipment, a junction box, or a panel.
Beyond the endpoints, the schedule records how the cable physically gets from one to the other. It names the trays, ducts, or trenches the cable is routed along and gives a length for each cable, which may be an estimate at design stage and a measured value once installed. Additional columns often capture segregation category, whether the cable is power, control, instrument, or signal, and any special requirements such as armour or fire rating. Together these turn the register into a complete description of the plant's wiring at the cable level.
What makes the schedule powerful is that it is comprehensive and singular. There is one authoritative list, and every cable on the project appears on it exactly once with a number that never repeats. That discipline is what lets the schedule be trusted as the source of truth: if a cable is not on the schedule it does not officially exist, and if a number appears twice something is wrong. Keeping it current as the design evolves and the installation proceeds is a continuous job, because so much else depends on its accuracy.
The most immediate use of the cable schedule is buying cable. Summing the lengths of each cable type across the register, with an allowance for wastage and terminations, tells the project how many meters of each specification to order. Because the schedule captures type and size for every run, procurement can be built directly from it rather than guessed, which reduces both shortfalls that stall installation and surplus that wastes money. The same data feeds gland and accessory counts, since each cable end needs its terminations.
The routing columns make the schedule the basis for tray fill calculations. Knowing which cables share each tray or duct, and the outside diameter of each, lets the design check that a route is not overloaded, both for physical space and, for power cables, for heat dissipation. Overfilled trays are a real installation problem, so being able to interrogate the schedule for everything on a given route is what keeps the cabling within its design limits. It also supports segregation rules, since the schedule shows whether power and signal cables are being kept on separate routes.
In the field, the cable schedule is the installation crew's worklist. Each cable is pulled from its from point to its to point along the specified route, tagged with its number, and cut to the scheduled length, then the actual installed length is fed back into the register. The schedule is how progress is tracked, how many cables are pulled, how many terminated, and how the physical work is reconciled against the design. It becomes, in effect, a live record of the installation as it is built.
The cable schedule does not stand alone; it is one corner of a web of E&I documents that must all agree. It connects most directly to the loop diagrams, which name specific cables and cores as they trace each signal from field to controller. A loop diagram pulls its cable and core numbers from the schedule, and a change in the schedule must ripple into the affected loop sheets. When the two documents match, a technician can move confidently between them; when they diverge, the field wiring is trusted by neither.
The schedule also connects to the SCADA I/O list, the register of every input and output the control system handles. Instrument cables on the schedule ultimately carry the signals that become tags in the SCADA system, so the chain runs from a cable number on the schedule, through the cores and terminals on the loop diagram, to a channel on an I/O card, to a named point on an operator's screen. Keeping the cable schedule aligned with the I/O list means every physical cable can be traced to the data it produces, and every SCADA tag can be traced back to the cable behind it.
For a cloud SCADA platform like Merobix, this traceability is what makes a field fault actionable. When a tag goes bad on the dashboard, the loop diagram identifies the loop and the cable schedule identifies the exact cable, its route, and its length, so a crew knows where to dig, which tray to open, and which run to test. A well-maintained cable schedule turns a symptom on a screen into a specific length of cable on a specific route, which is the difference between a targeted repair and a plant-wide search.
A cable schedule lists, for every cable, its unique number, type and specification, number and size of cores, the from and to termination points, the trays or routes it follows, and its length. It often also records segregation category and special requirements such as armour or fire rating. Each cable appears exactly once with a number that never repeats.
A cable schedule is the master list of every cable, giving each one's type, size, routing, and length across the whole installation. A loop diagram covers a single instrument loop and shows its complete terminal-by-terminal wiring. The schedule is the register of all cables; the loop diagram uses cable and core numbers from that schedule to draw one loop's physical path.
Because the schedule records the type, size, and length of every cable, summing lengths by specification, with an allowance for wastage and terminations, gives the exact quantity of each cable to order. It also drives gland and accessory counts, since every cable end needs terminations. Building procurement from the schedule avoids both shortfalls that stall work and costly surplus.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.