RWS CMDB

About RWS CMDB

Implemented domain model based on the XML/UML asset hierarchy, the OT-CMDB workbook structure, and NEN 2767-4 reference data.

Implemented UML Model

Regio
1 -> 0..*
District
1 -> 0..*
Complex
1 -> 0..*
Beheerobject
1 -> 0..*
Systeem
1 -> 0..*
Systeemdeel
1 -> 0..*
Element
LayerImplemented modelsPurpose
Organisation and scope Regio, District, Complex, Beheerobject Management boundary, RBAC scope, and top-level asset grouping.
Asset decomposition Systeem, Systeemdeel, Element, Bouwdeel Canonical XML/UML and NEN-oriented hierarchy for actual asset structure.
Technical assets Apparaat, CPU, Virtueel cluster, Virtuele machine, Geometrie Technical infrastructure attached below Element or Bouwdeel.
Software and data Programmatuur, Database, Datashare, Licentie, Back-up, Document, LFV, IV Service, Netwerkcommunicatie OT-CMDB workbook entities, mostly attached from Apparaat downward.
Reference data BeheerobjectType, ElementType, BouwdeelType, MateriaalsoortType, GebrekType, Vakdiscipline NEN 2767-4 lookup data imported from Excel and used by operational records.
Physical location Locatie, Gebouw, Verdieping, Ruimte Physical placement below Complex; an Apparaat can point to a Ruimte.

Primary Hierarchy

Regio
  -> District
      -> Complex
          -> Beheerobject
              -> Systeem
                  -> Systeemdeel
                      -> Element
                          -> Bouwdeel
                          -> Apparaat
                              -> Programmatuur
                                  -> Database
                                  -> Datashare
                                  -> Licentie
                                  -> Netwerkcommunicatie
                              -> Back-up
                              -> Document
                              -> LFV
                              -> IV Service
                              -> Rollen
                              -> Locatie

Relationship Rules

CI typeAllowed hierarchy parent
SysteemNone
SysteemdeelSysteem
ElementSysteemdeel
BouwdeelElement
ApparaatElement or Bouwdeel
ProgrammatuurApparaat
Database, Datashare, Licentie, NetwerkcommunicatieProgrammatuur
Back-upProgrammatuur, Database, or Virtuele machine
DocumentApparaat or Programmatuur
CPUElement, Apparaat, or Virtuele machine
GeometrieElement
Virtueel clusterElement or Bouwdeel
Virtuele machineElement, Apparaat, or Virtueel cluster

Associative relations such as licences, documentation, backup coverage, and communication links can be stored separately from the hierarchy parent.

Reference Data

NEN 2767-4 reference tables are maintained separately from operational asset data. They answer which standardized types exist; operational records answer which actual assets exist in the environment.

Reference: BouwdeelType = Ligger
Operational: Bouwdeel = Ligger noord in Brug A

Reference data is available in admin and read-only through /api/referentie/.