DemandFlow Support Centre

SITE: Site

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A physical site or data centre location with buildings, capacity, security, and operational metrics.

SITE: Site

The SITE entity: A physical site or data centre location with buildings, capacity, security, and operational metrics.

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

Entity properties

PropertyValue
Entity codeSITE
Display nameSite
PluralSites
Level40000

Use cases

SITE is the top-level node in the physical infrastructure hierarchy (SITE > BUILDING > FLOOR > ROOM > RACK). It captures the geographic location (address, lat/lon for map rendering), physical attributes (area, building count), and capacity metrics (power, cooling, racks). Lookup references to SITESTATUS, SITETYPE, and SITEOWN classify the site's operational state, purpose, and ownership model.

The isWarehouse flag differentiates storage/logistics sites from data centres. Contacts link to PPL records for operational roles (primary, manager, emergency, security, tech, vendor). Security & Compliance tracks Uptime Institute tier certification, ISO/SOC/PCI/HIPAA/LEED compliance, audit schedules, and security level classification.

Fields

General

FieldTypeRequiredNotes
nametextYesName
siteIdtextSite ID
siteCodetextSite Code
statusreference → SITESTATUSSite status
sitetypereference → SITETYPESite type
siteownreference → SITEOWNSite ownership
descriptiontext (multi-line)Description
isWarehousebooleanWarehouse

Location

FieldTypeRequiredNotes
pri_add_street1textStreet 1
pri_add_street2textStreet 2
pri_add_street3textStreet 3
pri_add_citytextCity
pri_add_countytextCounty
pri_add_postcodetextPostcode
pri_add_countryreference → COUNTRYCountry
latnumberLatitude
lonnumberLongitude

Physical Attributes

FieldTypeRequiredNotes
totalAreanumberTotal Area (sq ft)
usableAreanumberUsable Area (sq ft)
whiteSpaceAreanumberWhite Space (sq ft)
numBuildingsnumberNumber of Buildings
numFloorsnumberNumber of Floors
yearBuiltdateYear Built
lastRenovateddateLast Renovated

Capacity

FieldTypeRequiredNotes
totalPowerCapacitynumberTotal Power Capacity (kW)
availablePowerCapacitynumberAvailable Power (kW)
totalRackCapacitynumberTotal Rack Capacity
availableRackCapacitynumberAvailable Rack Capacity
totalCoolingCapacitynumberTotal Cooling Capacity (tons)
availableCoolingCapacitynumberAvailable Cooling (tons)

Site contacts

FieldTypeRequiredNotes
contact_primaryreference → PPLPrimary contact
contact_managerreference → PPLSite manager
contact_emergencyreference → PPLEmergency contact
contact_securityreference → PPLSecurity manager
contact_techreference → PPLTech. support manager
contact_vendorreference → PPLVendor / service manager

Online Resources

FieldTypeRequiredNotes
contact_websitetext (URL)Primary website for this facility
contact_portaltext (URL)Client access portal URL
contact_docstext (URL)Link to site documentation repository
contact_supporttext (URL)Support ticket system URL

Security

FieldTypeRequiredNotes
securityLevelenumSecurity Level Classification Valid ids: 1 (Level 1 (Basic)), 2 (Level 2 (Enhanced)), 3 (Level 3 (Advanced)), 4 (Level 4 (High)), 5 (Level 5 (Maximum)).
physicalAccessReqtext (multi-line)Physical Access Requirements
securitySystemsarray of references → SITESECSecurity Systems

Certifications & Compliance

FieldTypeRequiredNotes
uptimeTierenumUptime Institute Tier Valid ids: 1 (Tier I), 2 (Tier II), 3 (Tier III), 4 (Tier IV).
certificationsarray (enum)Certifications Valid ids: 1 (ISO 27001), 2 (SSAE 18/SOC 2), 3 (PCI DSS), 4 (HIPAA), 5 (LEED).
lastAuditDatedateLast Audit Date
nextAuditDatedateNext Scheduled Audit
complianceStatusenumCompliance Status Valid ids: 1 (Compliant), 2 (In Progress), 3 (Non-Compliant), 4 (Exempt).

Efficiency Metrics

FieldTypeRequiredNotes
puenumberPUE (Power Usage Effectiveness)
wuenumberWUE (Water Usage Effectiveness)
carbonFootprintnumberCarbon Footprint (tons CO2)
energyEfficiencyRatingenumEnergy Efficiency Rating Valid ids: 1 (A++), 2 (A+), 3 (A), 4 (B), 5 (C), 6 (D).

Cost Metrics

FieldTypeRequiredNotes
operationalCostMonthlynumberMonthly Operational Cost
maintenanceCostMonthlynumberMonthly Maintenance Cost
energyCostMonthlynumberMonthly Energy Cost
costPerKwhnumberCost per kWh

Maintenance Information

FieldTypeRequiredNotes
maintenanceScheduletext (multi-line)Maintenance Schedule
lastMaintenanceDatedateLast Maintenance Date
nextMaintenanceDatedateNext Maintenance Date
maintenanceProviderreference → COMMaintenance Provider
maintenanceNotestext (multi-line)Maintenance Notes

Disaster Recovery Systems

FieldTypeRequiredNotes
backupPowerTypearray of references → POWERBackup Power Type
backupPowerCapacitynumberBackup Power Capacity (kW)
fireSuppTypearray of references → POWERFire Suppression Type

Risk Assessment

FieldTypeRequiredNotes
floodRiskenumFlood Risk Valid ids: 1 (Low), 2 (Medium), 3 (High).
earthquakeRiskenumEarthquake Risk Valid ids: 1 (Low), 2 (Medium), 3 (High).
hurricaneRiskenumHurricane/Tornado Risk Valid ids: 1 (Low), 2 (Medium), 3 (High).
drPlanUrltext (URL)Link to disaster recovery plan document

Additional panels

  • Map panel rendered from latitude/longitude fields.

Relationships

  • Lookups: status points at a SITESTATUS record; sitetype points at a SITETYPE record; siteown points at a SITEOWN record; pri_add_country points at a COUNTRY record; contact_primary points at a PPL record; contact_manager points at a PPL record; contact_emergency points at a PPL record; contact_security points at a PPL record; contact_tech points at a PPL record; contact_vendor points at a PPL record; securitySystems points at a SITESEC record; maintenanceProvider points at a COM record; backupPowerType points at a POWER record; fireSuppType points at a POWER record.
  • Related lists: BUILDING (format comboKeyEntity), INFRAUNIT (format link).

Creating a Site via the API

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

{
  "entity":   "SITE",
  "level":    40000,
  "comboKey": "SUB:|ENT:",
  "name":    "Example name",
  "siteId":    "Example value",
  "siteCode":    "Example value",
  "status":    ""
}

Listing Sites records

GET /v1/entities/SITE/SUB

See also

sitesitesentitydefinitionreference

Was this article helpful?

← Back to Knowledge Base