DemandFlow Support Centre

POWERMETER: Power Meter

The POWERMETER entity represents a power metering point in the electrical distribution chain, tracking real-time load, consumption, and cost allocation.

Entity properties

Use cases

Power Meter represents a physical or virtual metering point in the electrical distribution chain. Data centres have meters at multiple levels: utility entrance, main switchgear, UPS input/output, floor distribution boards, room panel boards (RPPs), rack PDUs, and sometimes individual circuits. This entity models WHERE each meter sits in the hierarchy and WHAT it measures, enabling power chain traceability and PUE calculation. The location uses optional objectLookups to BUILDING, FLOOR, ROOM, and RACK rather than forcing a single parent - a utility entrance meter belongs to a building but not to any room, while a PDU meter belongs to a specific rack. meterPoint (indexedSelect) classifies where in the power chain the meter sits, which is critical for PUE: the ratio between a 'Utility Entrance' meter and an 'IT Load' meter gives the facility PUE. The Readings panel is all readonly fields designed for BMS/SCADA/SNMP integration via API patches. The Billing panel tracks energy consumption and cost allocation - linking to SITE.costPerKwh for rate calculations. CT ratio and accuracy class fields are included because revenue-grade metering (Class 0.2S) vs monitoring-grade (Class 1.0) matters for utility billing disputes and compliance. The entity deliberately does not store historical readings - those belong in a time-series store - but does track rolling period consumption (daily/monthly/annual kWh) for dashboard and reporting use.

Fields

General

Readings

Consumption

Thresholds

Maintenance

Relationships

• Lookups: building points at BUILDING record; floor points at FLOOR record; room points at ROOM record; rack points at RACK record; manufacturer points at VEN record; currency points at CURRENCY record.

Creating a Power Meter via the API

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

{
  "entity":   "POWERMETER",
  "level":    277,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "meterPoint": 1,
  "status": 1,
  "meterName": "Example"
}

Listing POWERMETER records

# All power meters in your tenant
GET /v1/entities/POWERMETER/SUB

See also

• The DemandFlow Object Model
• System Fields
• comboKey: Hierarchical Relationships