How to classify embedded software and scripting languages in ServiceNow CMDB

[Declan Donovan]

Hi, everyone!

My team is currently working with a client to clean-up and mature how their CMDB is organized today so that records are properly classified and relationships can be better defined for impact analysis. I'm looking for some guidance around best practices for how embedded software and scripting / programming languages (Java, C++, Python) should be managed and classified in the CMDB. For example for each of these, what CI Classes are these typically aligned to? Are there certain attributes that are used to manage and report on these?

For scripting and programming languages, should these be captured as their own records in the CMDB, or instead captured as an attribute on the application or infrastructure CIs?

Thank you!

[Declan Donovan]

Rather than firmware or middleware, the types of embedded software in discussion are around the applications that run on the operating system, use or interact with the middleware and firmware, and are the primary focus of the embedded systems’ target function.

For example with the aerospace and defense industry, this is often seen in-flight entertainment systems, sensors, flight management systems, engine control, etc. The applications that use the embedded systems within the plane itself are where we want to decide how these should be classified in the CMDB.

I agree with Stig that these can be classified as Business Applications (and broken out into unique Application Services), but am wondering if there is some sort of attribute to call out that these are embedded rather than everyday applications that run on people's PCs, or a typical class that these are aligned to.

Thanks!

[Stig Brandt]

Hi 

I would recommend, that you are thinking in the direction of

- embedded application is a business application, mapped to an application model, this is a logical record

- installed embedded application, is an application service instance prod, test, dev, this is also a logical record

- the embedded application- executable should be in the application ci, with respective software model etc.

I think in the future a business application record will be you product record, but just a thought.

br

Stig