What instruments and devices appear as cable sources?

Every device on the I/O list that requires a cable run: transmitters, switches, on / off valves, modulating valves, motors, panels, and field junction boxes. Hand-operated valves and pure indicators with no signal are excluded.

How is the destination cabinet and card slot assigned?

The destination cabinet comes from the I/O list assignment if it has been filled. If the I/O list is still un-assigned, Tagsight groups cables by area and signal class and proposes a marshalling cabinet split - editable in review.

Where do cable specs come from?

From the cable type register you upload. The register lists the available spec codes (2c-1.5-ind, 4c-2.5-ind, fo-4c-SM, etc.) with cores, cross-section, shielding, and voltage class. Each row is matched to a spec from the register based on the source device kind.

Are cable lengths estimated?

When tray routing data is uploaded, lengths are computed from the routing. When only the cabinet layout is available, the length is left blank and filled during construction. Tagsight does not invent lengths.

Can I cross-reference the schedule against an existing cable register?

Yes. Upload an existing cable register as an Excel reference file. Tagsight cross-references the extracted schedule against the register and flags cables that appear in one but not the other.

What export formats are available?

Excel and CSV. The cable schedule sits on its own sheet inside the same workbook as the I/O list and the JB schedule, so one file covers all three controls documents together.

Cable schedule.

Every field-to-marshalling-cabinet conductor. Cable tag, source instrument, destination cabinet card slot and channel, length, cross-section, and the cable spec the conductor was drawn from.

Extract a cable schedule See the I/O list

Cable scheduleread

CableFromTo

C-PT101PT-101MC-01 A1.3

C-FV204FV-204MC-01 B2.1

C-TT118TT-118MC-02 A1.7

C-LSH330LSH-330MC-02 B3.2

C-FT205FT-205MC-01 A2.4

5 of 210 cables·.xlsx .csv

Read one of your own drawings.

Drop a P&ID, instrument index, or schedule. Tagsight reads it to the tag and opens a workspace you keep when you sign in.

PDF · DWG · DXF · TIFF · PNG · XLSX

Browse filesor drop a file anywhere on this card

Schema.

#	Column	Type	Origin	Description
01	Cable tag	string	drawing	Cable tag per the project naming convention. Carried verbatim from the cable register or generated from the source instrument tag when none exists.
02	From device	string	drawing	Source instrument, motor, or panel tag. Read from the I/O list cross-reference.
03	From terminal	string	drawing	Terminal number on the source device when annotated. Blank when the drawing does not specify.
04	To cabinet	string	drawing	Destination marshalling cabinet, MCC bucket, or PLC card frame.
05	To card / slot	string	downstream	PLC card slot inside the destination cabinet. Owned by controls during the I/O assignment pass.
06	To channel	integer	downstream	Channel number within the card. Same downstream pass.
07	Kind	enum	drawing	Signal, control, power, or comms. Classified from the source device and the cable spec.
08	Spec	string	cable register	Cable construction spec: cores, cross-section, shielding, jacket. Pulled from the cable type register.
09	Cores	integer	cable register	Conductor count. Reads from the cable spec or the cable type register.
10	Length	number	cable register	Estimated cable length in metres. Computed from tray routing when available, blank otherwise.
11	Voltage class	enum	cable register	ELV, LV, or MV. Resolved from the kind and the cable spec.
12	Tray / conduit	string	downstream	Tray, conduit, or duct routing identifier. Owned by electrical during routing.
13	Notes / revisions	string	audit	Revision marker, MOC reference, follow-up note.

From instrument to cabinet.

01UploadP&ID set + I/O list
02PairInstrument to cabinet
03ResolveSpec from register
04ExportExcel or CSV

Sources.

The cable schedule is built from the I/O list cross-reference and the cabinet layout, then enriched with cable specs from your type register.

Run it on your drawings.

Upload a P&ID set with your I/O list, get every field cable paired to its destination cabinet, export Excel or CSV.

Start a workspace Pricing

Schema.

#	Column	Type	Origin	Description
01	Cable tag	string	drawing	Cable tag per the project naming convention. Carried verbatim from the cable register or generated from the source instrument tag when none exists.
02	From device	string	drawing	Source instrument, motor, or panel tag. Read from the I/O list cross-reference.
03	From terminal	string	drawing	Terminal number on the source device when annotated. Blank when the drawing does not specify.
04	To cabinet	string	drawing	Destination marshalling cabinet, MCC bucket, or PLC card frame.
05	To card / slot	string	downstream	PLC card slot inside the destination cabinet. Owned by controls during the I/O assignment pass.
06	To channel	integer	downstream	Channel number within the card. Same downstream pass.
07	Kind	enum	drawing	Signal, control, power, or comms. Classified from the source device and the cable spec.
08	Spec	string	cable register	Cable construction spec: cores, cross-section, shielding, jacket. Pulled from the cable type register.
09	Cores	integer	cable register	Conductor count. Reads from the cable spec or the cable type register.
10	Length	number	cable register	Estimated cable length in metres. Computed from tray routing when available, blank otherwise.
11	Voltage class	enum	cable register	ELV, LV, or MV. Resolved from the kind and the cable spec.
12	Tray / conduit	string	downstream	Tray, conduit, or duct routing identifier. Owned by electrical during routing.
13	Notes / revisions	string	audit	Revision marker, MOC reference, follow-up note.

Cable schedule.

Read one of your own drawings.

Schema.

From instrument to cabinet.

Sources.

More on the cable schedule.

Run it on your drawings.

Cable schedule.

Read one of your own drawings.

Schema.

From instrument to cabinet.

Sources.

More on the cable schedule.

Run it on your drawings.