DemandFlow Support Centre

NWPLATINST: Network Platform Instance

A specific deployed instance of a telecom network platform in a particular environment, with vendor, ownership, lifecycle, and dependency tracking.

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

Entity properties

Property	Value
Entity code	`NWPLATINST`
Display name	Network Platform Instance
Plural	Network Platform Instances
Level	6200

Use cases

NWPLATINST is the telecom network equivalent of DPLAT (IT deployed platforms), kept completely separate from the IT domain. Each record represents a specific deployment of a NWPLAT platform type (e. g.

Fields

Basics

Field	Type	Required	Notes
`name`	text	Yes	Name
`nwplat`	reference → `NWPLAT`	Yes	Platform Type
`environment`	enum	Yes	Environment Valid ids: `production` (Production), `dr` (Disaster Recovery), `preprod` (Pre-production), `staging` (Staging), `lab` (Lab).
`status`	enum	Yes	Status Valid ids: `planned` (Planned), `deploying` (Deploying), `active` (Active), `deprecated` (Deprecated), `decommissioning` (Decommissioning), `retired` (Retired).
`description`	text (multi-line)		Description

Technical & Lifecycle

Field	Type	Notes
`deploymentModel`	enum	Deployment Model Valid ids: `physical` (Physical), `virtual` (Virtualised), `cloudnative` (Cloud-native), `containerised` (Containerised), `hybrid` (Hybrid).
`currentVersion`	reference → `NWPLATSW`	Current Version
`criticality`	enum	Criticality Valid ids: `low` (Low), `medium` (Medium), `high` (High), `critical` (Critical).
`commissionDate`	date	Commission Date
`plannedDecomDate`	date	Planned Decommission
`supportAgreement`	reference → `SUPAGREEMENT`	Support Agreement
`hypCluster`	reference → `HYPCLUSTER`	Virtualisation cluster this platform runs on
`k8sCluster`	reference → `K8SCLUSTER`	Kubernetes cluster this platform runs on

Ownership

Field	Type	Notes
`vendor`	reference → `VEN`	Vendor
`domain`	reference → `DEPT`	Department
`owner`	reference → user	Platform Owner
`architect`	reference → user	Architect
`ops`	reference → user	Operations
`tags`	text	Tags

Activity. Activity timeline panel attached.

Additional panels. This definition also includes the following non-form panels: dashboard.

Relationships

Lookups: nwplat points at a NWPLAT record. currentVersion points at a NWPLATSW record. supportAgreement points at a SUPAGREEMENT record. hypCluster points at a HYPCLUSTER record. k8sCluster points at a K8SCLUSTER record. vendor points at a VEN record. domain points at a DEPT record.
Related lists: NWPLATDEP (format SUB|NWPLATINST), NWPLATDEP (format SUB|NWPLATINST), COMPINV, HYPCLUSTER, NWPLATSW (format SUB|NWPLATINST), NWTICKET, NWCHANGE, NWPROBLEM.

Creating a Network Platform Instance via the API

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

{
  "entity":   "NWPLATINST",
  "level":    6200,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "nwplat": "",
  "environment": "production",
  "status": "planned"
}

Listing Network Platform Instances records

# All network platform instances in your tenant
GET /v1/entities/NWPLATINST/SUB

DemandFlow Support Centre

NWPLATINST: Network Platform Instance

NWPLATINST: Network Platform Instance

Entity properties

Use cases

Fields

Relationships

Creating a Network Platform Instance via the API

Listing Network Platform Instances records

See also

Was this article helpful?