DemandFlow Support Centre

POWERCIRCUIT: Power Circuit

ReferenceEntity Reference16/04/2026Updated 16/04/2026
The POWERCIRCUIT entity represents an electrical circuit feeding a rack, tracking voltage, amperage, phase, upstream feed path, and real-time load.

POWERCIRCUIT: Power Circuit

The POWERCIRCUIT entity represents an electrical circuit feeding a rack, tracking voltage, amperage, phase, upstream feed path, and real-time load.

Default definition. This article describes the default POWERCIRCUIT 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 POWERCIRCUIT.

Entity properties

PropertyValue
Entity codePOWERCIRCUIT
Display namePower Circuit
PluralPower Circuits
Level275

Use cases

Power Circuit represents an individual electrical circuit feeding a rack, bridging the gap between room-level power infrastructure (RPPs, panel boards) and rack-level PDUs. It is a child of RACK via comboKeyEntity - matching the existing relatedlist already defined on RACK's Power panel (which expects name, voltage, amperage, phase fields). The upstream feed fields (sourcePanel, sourceBreakerPosition, feedPath) trace the circuit back to its panel board and identify which power path (A/B/STS) it belongs to - critical for understanding redundancy. connectedPdu links to COMPINV because PDUs are physical assets that should be tracked in the asset register. The Metering panel provides readonly fields for integration with intelligent PDU or BMS data, plus threshold-based alerting. Connector types cover both North American (NEMA) and international (IEC 60309) standards plus busway tap-off for overhead busbar systems.

Fields

General

FieldTypeRequiredNotes
nametextYesUnique circuit identifier (e.g., A1-C01, RPP-B-12).
circuitLabeltextLabel as shown on the panel board or breaker.
statusenumYesStatus. Valid ids: 1 (Active), 2 (Planned), 3 (Reserved), 4 (Maintenance), 5 (Faulted), 6 (Decommissioned).
circuitPurposeenumPurpose. Valid ids: 1 (Primary), 2 (Redundant), 3 (Maintenance), 4 (Emergency).
descriptiontext (multi-line)Description.
voltagenumberYesVoltage (V).
amperagenumberYesAmperage (A).
phaseenumYesPhase. Valid ids: 1 (Single Phase), 2 (Three Phase).
ratedCapacityKwnumberMaximum design load for this circuit.
connectorTypeenumConnector Type. Valid ids: 1 (NEMA L5-30), 2 (NEMA L6-20), 3 (NEMA L6-30), 4 (NEMA L6-50), 5 (NEMA L14-30), 6 (NEMA L15-30), 7 (NEMA L21-30), 8 (IEC 60309 16A), 9 (IEC 60309 32A), 10 (IEC 60309 63A), 11 (IEC 60309 125A), 12 (Hardwired), 13 (Busway Tap).
wireGaugetexte.g., 10 AWG, 6 AWG, 4mm².
breakerSizenumberBreaker Size (A).
sourcePaneltextPanel board or RPP this circuit originates from.
sourceBreakerPositiontextPosition in panel board (e.g., Slot 12, Breaker 3).
feedPathenumFeed Path. Valid ids: 1 (A Feed (Utility)), 2 (B Feed (UPS/Generator)), 3 (C Feed), 4 (STS (Static Transfer Switch)).
connectedPdureference → COMPINVPDU asset this circuit feeds.
pduInlettextWhich inlet on the PDU (e.g., Inlet 1, Inlet A).

Metering

FieldTypeRequiredNotes
measuredLoadKwnumberMeasured Load (kW). Read-only.
measuredLoadAmpsnumberMeasured Load (A). Read-only.
loadPercentagenumberPercentage of rated capacity in use. Read-only.
lastReadingDatedatetimeLast Reading. Read-only.
powerFactornumberPower Factor. Read-only.
warningThresholdPercentnumberAlert when load exceeds this percentage.
criticalThresholdPercentnumberCritical alert when load exceeds this percentage.
peakLoadKwnumberPeak Load (kW). Read-only.
peakLoadDatedatetimePeak Load Date. Read-only.
averageLoadKwnumberAverage Load (kW). Read-only.

Maintenance

FieldTypeRequiredNotes
installDatedateInstallation Date.
lastInspectionDatedateLast Inspection.
nextInspectionDatedateNext Inspection.
lastThermographyDatedateLast infrared thermography inspection.
notestext (multi-line)Notes.

Relationships

  • Lookups: connectedPdu points at COMPINV record.

Creating a Power Circuit via the API

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

{
  "entity":   "POWERCIRCUIT",
  "level":    275,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "status": 1,
  "voltage": 100,
  "amperage": 100
}

Listing POWERCIRCUIT records

# All power circuits in your tenant
GET /v1/entities/POWERCIRCUIT/SUB

See also

powercircuitpower circuitpower circuitspowercircuit

Was this article helpful?

← Back to Knowledge Base