RACKMOUNTPOINT: Rack Mount Point
The RACKMOUNTPOINT entity represents an individual U-position slot (front or rear) within a rack for mounting or reserving equipment.
RACKMOUNTPOINT 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 RACKMOUNTPOINT.Entity properties
| Property | Value |
|---|---|
| Entity code | RACKMOUNTPOINT |
| Display name | Rack Mount Point |
| Plural | Rack Mount Points |
| Level | 275 |
Use cases
RACKMOUNTPOINT represents a single mountable position within a RACK, identified by U position number (1 from bottom) and side (Front/Rear). The name is auto-generated as RackName-U##-Side. Status tracks availability (Available, Occupied, Reserved, Blocked, Maintenance) and mount type handles full-width or half-width (left/right) configurations. Assignment links to a COMPINV asset currently mounted at this position, with assetGroup and isPrimary fields supporting multi-U equipment that spans several mount points. Reservation fields (reservedFor, reservedUntil, project) enable capacity planning by pre-allocating positions for upcoming deployments. Physical constraints capture obstructions (cable management, PDU, structural, cooling), maximum equipment depth, and position-specific weight limits. Power & Connectivity records the nearest PDU outlet reference, available power capacity, cable access availability and sides. This granular per-U tracking enables rack elevation visualisation, space utilisation calculations, and precise asset placement planning across the data centre.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Auto-generated: RackName-U##-Side. Read-only. |
rack | reference → RACK | Yes | Parent Rack. |
uPosition | number | Yes | Position from bottom (1) to top. |
side | enum | Yes | Side. Valid ids: 1 (Front), 2 (Rear). |
status | enum | Yes | Status. Valid ids: 1 (Available), 2 (Occupied), 3 (Reserved), 4 (Blocked), 5 (Maintenance). |
mountType | enum | Mount Type. Valid ids: 1 (Full Width), 2 (Half Width - Left), 3 (Half Width - Right). | |
asset | reference → COMPINV | Asset currently mounted at this position. | |
assetGroup | text | Groups mount points for multi-U assets. | |
isPrimary | boolean | Primary position for multi-U assets. | |
assignedDate | date | Assignment Date. | |
reservedFor | reference → COMPINV | Reserved For Asset. | |
reservedUntil | date | Reserved Until. | |
project | reference → ag_deliveryproject | Related Project. |
Physical
| Field | Type | Required | Notes |
|---|---|---|---|
hasObstruction | boolean | Cable management or other obstruction. | |
obstructionType | enum | Obstruction Type. Valid ids: 1 (Cable Management), 2 (PDU), 3 (Structural), 4 (Cooling), 5 (Other). | |
maxDepth | number | Maximum depth available at this position. | |
weightLimit | number | If different from rack default. | |
nearestPowerOutlet | text | PDU outlet reference. | |
powerCapacity | number | Maximum power available. | |
hasCableAccess | boolean | Cable Access. | |
cableAccessSide | multiselect | Cable Access Side. |
Notes
| Field | Type | Required | Notes |
|---|---|---|---|
notes | text (multi-line) | Any special considerations for this mount point. |
Relationships
- Lookups:
rackpoints atRACKrecord;assetpoints atCOMPINVrecord;reservedForpoints atCOMPINVrecord;projectpoints atag_deliveryprojectrecord.
Creating a Rack Mount Point via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "RACKMOUNTPOINT",
"level": 275,
"comboKey": "SUB:<your-sub-id>|ENT:",
"rack": "",
"uPosition": 100,
"side": 1,
"status": 1
} Listing RACKMOUNTPOINT records
# All rack mount points in your tenant
GET /v1/entities/RACKMOUNTPOINT/SUB