DPLAT: Deployed Platform
A deployed instance of a platform type, representing a specific live environment with its software version, ownership, and costs.
DPLAT 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 DPLAT.Entity properties
| Property | Value |
|---|---|
| Entity code | DPLAT |
| Display name | Deployed Platform |
| Plural | Deployed Platforms |
| Level | 6000 |
Use cases
DPLAT represents a concrete, deployed instance of a platform -- for example, a specific production Cisco router cluster or a live AWS-hosted analytics platform. It links to PLAT (the abstract platform type catalogue) via an objectLookup with comboKey, and to DPLATSW (the software version running on it) via a filtered objectLookup that scopes versions to the selected platform. The status lifecycle (Active, Inactive, Planned, In Deployment, Retired, Deprecated) tracks the deployment through its full operational lifetime. Deployment model (Physical, OnPrem, OnPrem-Virtual, OnPrem-Software, Cloud, Hybrid) captures the infrastructure hosting pattern, which drives cost models and operational processes. Ownership fields (responsible department via DEPT, OEM vendor via VEN, platform owner, architect, operations owner as user lookups) establish clear accountability. Governance adds criticality and data classification for risk management, plus freeform tags. The Support Costs panel uses the costs row type with editable actuals tied to spend types, vendors, and contracts, enabling detailed FinOps tracking per platform instance. The context flag getPlatformHealth enables runtime health data fetching for this entity.
Fields
Basics
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Ref. Read only. | |
name | text | Yes | Name. |
plat | reference → PLAT | Yes | Platform type. |
status | enum | Yes | Valid ids: active (Active), inactive (Inactive), planned (Planned), deployment (In Deployment), retired (Retired), deprecated (Deprecated). |
Description
| Field | Type | Required | Notes |
|---|---|---|---|
description | text (multi-line) | Description. |
Technical Detail
| Field | Type | Required | Notes |
|---|---|---|---|
model | enum | Yes | Valid ids: physical (Physical), onprem (OnPrem), onpremv (OnPrem - Virtual), onpremsw (OnPrem - Software), cloud (Cloud), hybrid (Hybrid). |
hypCluster | reference → HYPCLUSTER | Virtualisation cluster this platform runs on | |
k8sCluster | reference → K8SCLUSTER | Kubernetes cluster this platform runs on |
Version
| Field | Type | Required | Notes |
|---|---|---|---|
platform | reference → DPLATSW | Software version. |
Ownership & Vendor
| Field | Type | Required | Notes |
|---|---|---|---|
domain | reference → DEPT | Yes | Responsible dept.. |
vendor | reference → VEN | Yes | OEM. |
platowner | reference → user | Platform Owner. | |
architect | reference → user | Architect. | |
ops | reference → user | Operations owner. |
Governance
| Field | Type | Required | Notes |
|---|---|---|---|
criticality | enum | Valid ids: low (Low), medium (Medium), high (High), critical (Critical). | |
dataClassification | enum | Valid ids: public (Public), internal (Internal), confidential (Confidential), restricted (Restricted). | |
tags | array of text | Tags. |
Relationships
- Lookup:
plat(reference →PLAT). - Lookup:
hypCluster(reference →HYPCLUSTER). - Lookup:
k8sCluster(reference →K8SCLUSTER). - Lookup:
platform(reference →DPLATSW). - Lookup:
domain(reference →DEPT). - Lookup:
vendor(reference →VEN). - Related list:
COMPINV, related list. - Related list:
HYPCLUSTER, related list.
Creating a Deployed Platform via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DPLAT",
"level": 6000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"plat": "",
"status": "active",
"model": "physical"
} Listing Deployed Platforms records
GET /v1/entities/DPLAT/SUB:<your-sub-id>