DemandFlow Support Centre

CABLEPATHWAY: Cable Pathway

A physical cable routing pathway (tray, conduit, riser, penetration) with capacity tracking and fire compliance.

Default definition. This article describes the default CABLEPATHWAY definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches CABLEPATHWAY.

Entity properties

Property	Value
Entity code	`CABLEPATHWAY`
Display name	Cable Pathway
Plural	Cable Pathways
Level	278

Use cases

Cable Pathway models the physical routing infrastructure that cables travel through - cable trays, conduits, under-floor pathways, overhead ladder racks, vertical risers, and wall/floor penetrations. This fills the gap between knowing that two ports are connected (CONNECTION entity) and understanding HOW the cable gets there physically. Each pathway has a start and end location using ROOM lookups - a pathway can be within a single room (e.g., overhead tray from row A to row B) or span between rooms/floors (e.g., a vertical riser from Floor 1 to Floor 3).

Fields

General: Pathway Identification

Field	Type	Required	Notes
`name`	text	Yes	Unique identifier (e.g., CT-FL1-A01, RISER-B-1-3)
`pathwayName`	text		Descriptive name (e.g., Main East-West Overhead Tray, Riser B Floors 1-3)
`pathwayType`	enum	Yes	Pathway Type. Valid ids: `1` (Cable Tray - Ladder), `2` (Cable Tray - Wire Mesh), `3` (Cable Tray - Solid Bottom), `4` (Cable Tray - Channel), `5` (Under-Floor Pathway), `6` (Raised Floor Plenum), `7` (Overhead Basket Tray), `8` (Conduit - Rigid Metal (RMC)), `9` (Conduit - EMT), `10` (Conduit - Flexible), `11` (Conduit - PVC), `12` (Vertical Riser), `13` (Floor Penetration), `14` (Wall Penetration), `15` (Cable Duct / Raceway), `16` (J-Hook Run), `17` (Underground Duct Bank), `18` (Aerial / Overhead), `19` (Rack Drop).
`pathwayTypeRef`	reference → `CABLEPATHWAYTYPE`		Product catalog reference - populates default dimensions
`status`	enum	Yes	Status. Valid ids: `1` (Active), `2` (Planned), `3` (Under Construction), `4` (Maintenance), `5` (Full), `6` (Decommissioned).
`mediaCarried`	multiselect		NEC requires separation of power and data in some pathway types
`description`	text (multi-line)		Description.

General: Route

Field	Type	Notes
`startRoom`	reference → `ROOM`	Start Room.
`startPoint`	text	e.g., Rack Row A, North wall patch panel, Floor penetration FP-01
`endRoom`	reference → `ROOM`	End Room.
`endPoint`	text	e.g., Rack Row D, MDF closet, Building entrance
`startFloor`	reference → `FLOOR`	For vertical risers spanning multiple floors
`endFloor`	reference → `FLOOR`	For vertical risers spanning multiple floors
`lengthMeters`	number	Length (m).
`heightAboveFloor`	number	For overhead pathways
`depthBelowFloor`	number	For under-floor pathways
`connectsToA`	reference → `CABLEPATHWAY`	Adjacent pathway segment at the A end
`connectsToB`	reference → `CABLEPATHWAY`	Adjacent pathway segment at the B end
`rack`	reference → `RACK`	Target rack for Rack Drop segments Visible when `pathwayType` = `19`.

General: 3D Route

Field	Type	Notes
`parentRoom`	reference → `ROOM`	Room this pathway segment lives in (required for 3D rendering)
`elevation`	enum	Installation Level. Valid ids: `1` (Overhead), `2` (Under-Floor), `3` (Wall-Mounted), `4` (Rack-Mounted), `5` (Ceiling-Mounted).
`startX`	number	mm from room origin
`startY`	number	mm from room origin
`startZ`	number	Height above finished floor (e.g. 2400 for overhead, -200 for underfloor)
`endX`	number	End X (mm).
`endY`	number	End Y (mm).
`endZ`	number	End Z (mm).
`renderColor`	text	Hex color for 3D rendering. Defaults by pathway type if empty Placeholder: #FFA726.

General: Physical Specifications

Field	Type	Notes
`widthMm`	number	Width (mm).
`heightMm`	number	Height / Depth (mm).
`material`	enum	Material. Valid ids: `1` (Galvanized Steel), `2` (Stainless Steel), `3` (Aluminium), `4` (Wire Mesh / Basket), `5` (PVC), `6` (Fiberglass (FRP)), `7` (Concrete).
`fireRating`	enum	Fire barrier rating for penetrations and enclosed pathways Valid ids: `1` (None), `2` (1 Hour), `3` (2 Hour), `4` (3 Hour), `5` (Plenum Rated).
`manufacturer`	reference → `VEN`	Manufacturer.
`model`	text	Model / Part No..

Capacity: Cable Fill

Field	Type	Notes
`maxCableCount`	number	Estimated max cables based on pathway cross-section and cable diameters
`currentCableCount`	number	Current Cable Count.
`crossSectionArea`	number	Internal usable cross-section area
`usedArea`	number	Used Area (mm²).
`fillRatioPercent`	number	NEC Article 392 limits: 50% for one cable, 40% for signal cables, 40% for power cables
`maxFillPercent`	number	Site-specific or code-mandated maximum fill percentage

Capacity: Cable Breakdown

Field	Type	Notes
`copperDataCount`	number	Copper Data Cables.
`fiberCount`	number	Fiber Cables.
`powerCableCount`	number	Power Cables.
`coaxialCount`	number	Coaxial Cables.
`otherCableCount`	number	Other Cables.
`abandonedCableCount`	number	NEC 800.25 requires removal of abandoned cables in plenums

Load & Compliance: Structural Load

Field	Type	Notes
`maxLoadKg`	number	Max Load Capacity (kg).
`currentLoadKg`	number	Current Load (kg).
`loadPerMeterKg`	number	Load per Metre (kg/m).
`supportSpacingM`	number	Distance between support brackets or hangers
`supportCount`	number	Support/Hanger Count.

Load & Compliance: Compliance & Fire Stop

Field	Type	Notes
`hasFireStop`	boolean	Fire barrier sealant at penetrations
`fireStopType`	text	Fire Stop Type / Product.
`lastFireStopInspection`	date	Last Fire Stop Inspection.
`necCompliant`	boolean	NEC Compliant.
`complianceNotes`	text (multi-line)	Compliance Notes.

Maintenance: Installation & Maintenance

Field	Type	Notes
`installDate`	date	Installation Date.
`lastInspectionDate`	date	Last Inspection.
`nextInspectionDate`	date	Next Inspection Due.
`condition`	enum	Condition. Valid ids: `1` (Excellent), `2` (Good), `3` (Fair), `4` (Poor), `5` (Failed).

Maintenance: Notes & Documentation

Field	Type	Required	Notes
`notes`	text (multi-line)		Notes.
`diagramUrl`	text (URL)		Routing Diagram.

Relationships

Lookups: pathwayTypeRef points at a CABLEPATHWAYTYPE record; startRoom points at a ROOM record; endRoom points at a ROOM record; startFloor points at a FLOOR record; endFloor points at a FLOOR record; connectsToA points at a CABLEPATHWAY record; connectsToB points at a CABLEPATHWAY record; rack points at a RACK record; parentRoom points at a ROOM record; manufacturer points at a VEN record.
Related lists: CABLEROUTEPT (format SUB|CABLEPATHWAY), CONNECTION (via cablePathway), CABLEPATHWAY (via connectsToA), CABLEPATHWAY (via connectsToB).

Creating a Cable Pathway via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "CABLEPATHWAY",
  "level":    278,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Pathway ID",
  "pathwayType": "1",
  "status": "1",
  "description": "Description"
}

Listing Cable Pathways records

GET /v1/entities/CABLEPATHWAY/SUB

DemandFlow Support Centre

CABLEPATHWAY: Cable Pathway

CABLEPATHWAY: Cable Pathway

Entity properties

Use cases

Fields

Relationships

Creating a Cable Pathway via the API

Listing Cable Pathways records

See also

Was this article helpful?