CMDB - Three Fields/Attributes similar choices causes confusion Environment/Used for/Classification

DeonP
Tera Contributor

Has anyone else encountered the same issue as I have at the moment. While trying to formalise the structure of our CMDB according to the CSDM 5 guidance, I have encountered three Fields with the same of very similar choice values. What I am missing is clear guidance about the use of these three  so that I can properly complete my governance documentation.

1. Proper description. 2. When to use which one 3. What is the value of using all three or which one should be used primarily throughout from Business application to technical CI. 4. Which one can be repurposed with different choice values without impacting OOB behaviour and flows

 

Trying to get adoption in our environment is already difficult and without a clear description of the differences different users start populating the different Fields causing misalignment.

The closest i go to get anything of value is this extract from the cmdb_ci Server Documentation, which however is actually quite vague and lack the reference to the Environment attribute.

https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/class-s...
Attribute Description

Classification​

Type of server, such as production, development, disaster recovery, or user acceptance testing (UAT).
Firewall status

Internet or intranet facing server.
Host name

Use the Name attribute to store the host name of the server instead of the Host name attribute.
Used for Business service supported by the server, such as production, staging, or quality assurance (QA). This attribute uses the Used for choice list field from the Service [cmdb_ci_service] table.

 

Below are the OOB (Yokohama) values I have. 
Environment

  • Development
  • Test
  • Production

 

Used for

  • Staging
  • Training
  • QA
  • Disaster Recovery
  • Test
  • Production
  • Development

 

Classification

  • Development Test
  • Disaster Recovery
  • Critical Infrastructure
  • Production
  • Development
  • UAT
0 REPLIES 0