DemandFlow Support Centre

TOW: Tower

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A telecommunications tower with sections, faces, mount points, capacity tracking, and EMF readings.

TOW: Tower

A telecommunications tower with sections, faces, mount points, capacity tracking, and EMF readings.

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

Entity properties

PropertyValue
Entity codeTOW
Display nameTower
PluralTowers
Level35000

Use cases

A telecommunications tower with sections, faces, mount points, capacity tracking, and EMF readings.

TOW is the top-level entity in the tower infrastructure hierarchy (TOW > TOWSEC > TOWFACE > MOUNTPOINT > MOUNTEQP). Each tower belongs to a parent SITE and is located by lat/lon for map rendering (viewOptions supports both map and grid views). Classification uses three lookups: TOWTYPE (monopole, lattice, guyed, etc.), TOWSTATUS (operational, planned, damaged, etc.), and TOWRATING (structural capacity class). Foundation type is an inline indexedSelect since the options are universal. The Asset section tracks manufacturer (VEN), model, serial number, purchase/book value, manufacture date, and depreciation for financial asset management. Specifications capture physical dimensions (elevation, height), structural limits (max load, wind/ice/seismic ratings), and dates (construction, structural analysis). Maintenance tracks inspection schedules with pastCheck for overdue alerts. Capacity tracks current vs available load in kg, utilisation percentage, wind load rating, and mount point counts (total, available, reserved, occupied). The Tower Faces panel shows child TOWFACE records via comboKeyEntity. The Tower Sections related list shows child TOWSEC records sorted by heightFrom for vertical ordering. Custom row types towerlayout and emfReadings provide visual tower diagram and electromagnetic field measurement displays.

Fields

General

FieldTypeRequiredNotes
nametextYesTower Name.
towerCodetextTower Code.
sitereference → SITEYesSite.
latnumberYesLAT.
lonnumberYesLON.
towerTypereference → TOWTYPETower Type.
statusreference → TOWSTATUSTower Status.
ratingreference → TOWRATINGTower Rating.
foundationenumValid ids: 1 (Concrete pad), 2 (Caisson), 3 (Spread footing), 4 (Rock anchor), 5 (Micro pile), 6 (N/A).

Asset

FieldTypeRequiredNotes
oemreference → VENManufacturer.
modeltextModel number.
price1numberPurchase price.
price2numberCurrent book value.
serialtextSerial number.
manufactureDatedateManufacture Date.
depreciationtext (multi-line)Depreciation schedule.

Specifications

FieldTypeRequiredNotes
elevationnumberElavation (meters).
heightnumberHeight (meters).
maxLoadCapacitynumberMax Load Capacity (kg).
windRatingKmhnumberWind Rating (Km/h).
iceRatingCmnumberIce Rating (cm).
seismicRatingtextSeismic rating.
constructionDatedateConstruction Date.
structuralAnalysisDatedateStructural Analysis Date.

Maintenance

FieldTypeRequiredNotes
lastInspectionDatedateLast Inspection Date.
nextInspectionDatedateNext Inspection Date.
maintenanceNotestext (multi-line)Maintenance Notes.

Load Status

FieldTypeRequiredNotes
currentLoadnumberCurrent Load (kg).
availableCapacitynumberAvailable Capacity (kg).
capacityUtilizationnumberCapacity Utilization (%).
windLoadRatingtextWind Load Rating.

Mount Points

FieldTypeRequiredNotes
totalMountPointsnumberTotal Mount Points.
availableMountPointsnumberAvailable Mount Points.
reservedMountPointsnumberReserved Mount Points.
occupiedMountPointsnumberOccupied Mount Points.

Relationships

  • Lookups: site points at a SITE record; towerType points at a TOWTYPE record; status points at a TOWSTATUS record; rating points at a TOWRATING record; oem points at a VEN record.
  • Related lists: TOWSEC via comboKeyEntity; TOWFACE via comboKeyEntity.

Creating a Tower via the API

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

{
  "entity":   "TOW",
  "level":    35000,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example name",
  "site": "",
  "lat": 0,
  "lon": 0
}

Listing Towers

GET /v1/entities/TOW/SUB

See also

towtowertowers

Was this article helpful?

← Back to Knowledge Base