Data Products/Integrations

gunnergraves
Giga Expert

We have a use case where we want to begin tracking Data Products and Ownership throughout our organization.  The idea is to be able to be able to view the dependencies and relation among Business Applications in APM.  I've been thinking about how this would fit into the CSDM. 

At first I wondered if they should be Information Objects, but it seems that the Information Objects have a strong tie to the Database Class that made me feel it wasn't made for quite what I'm trying to achieve.  

I am thinking now that these data products may fit better into technical services and offerings.  

Can I get some thoughts from the community on this use case?  

7 REPLIES 7

hi Dan,

I considered these classes as well but as I added so many specific functional, governance and documentation specific attributes, I decided to create a new class, extended from cmdb_ci, to describe an integration between 2 Business Applications.

@gunnergraves : feel free to send me a meeting invite so that I can showcase what I'm building.

regards, bruno

 

Bruno De Graeve,
Principal Platform Architect, Customer Success, ServiceNow

wheels
Tera Contributor

We are in same boat, asked to populate Data Products. At present we do capture them as Business Applications, but this appears overkill for the effort we have in maintaining business applications due to our regulatory requirements. I am in agreement with capturing these as a technical service and creating their own category. we have done this with MFE/BFF prior to servicenow providing API classes. Our Data Products will have a technical service with offerings which will then have application services which provide various environments for these Data Products.

Bruno De Graeve
ServiceNow Employee
ServiceNow Employee

version 1.64 of the CMDB CI Class Models, introduced the new service class: 

  •  Data Service Instance (cmdb_ci_data_service_instance)

A Data Service Instance is extended from Service Instance and represents a logical instance of a data service that can persist structured and unstructured data, process data (pipeline) or retrieve data (data, search, query, etc).

I wouldn't create Data Products as Business Apps and rather follow the idea of making them a Service with Offerings per data product.


What is missing or limiting us to use the Information Objects ?


My personal 2 cents.

Bruno De Graeve,
Principal Platform Architect, Customer Success, ServiceNow