Data Products/Integrations

[gunnergraves]

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?  

[Dylan Veerman]

Information Objects explains what type of data is running through the application or database serving it. Therefore, this is not the place to store dependencies and relationship. To my knowledge not many relationships are created between Business Applications, though you do have some options, which you could explore in order to get them together from an APM point of view:

• Application Family
• Application Category
• Relate multiple business applications to the same business capability
• Business Application (Platform/Host) - Business Application (Application)

If a data product is an application that serves other applications in providing data, it should be modeled as an application service and have a relationship with other application services that it sends this data to / that consume the data is sends.

[Bruno De Graeve]

hello Gunner,

Do you have an example of such a "Data Product" and relations to Business Applications ? That might help us maybe. When I noticed the term Product, I thought about using an existing Product Model class, or making a dedicated one.

Myself, I'm building a custom app on top of the CMDB to track Interfaces between Business Application (describe the use case why these Business Applications exchange data (master or process data) + capture all technical, security, functional, contact details), as well it allows you to create Application Services, that can be monitored, which are environment specific instantiations of the Interface itself.

regards, Bruno

[gunnergraves]

Bruno, 

My use case sounds a lot like yours.  I was trying to determine if there was an out of the box scope that fits this use case for the Data Products instead of building our own table.  Did you spin up your own class?  

[Dan Freed]

If the data products are sold externally or subscribed to internally by business users I would consider using Business Services/Offerings. 

If they are only subscribed to internally by technical teams I would consider using Technical Services/Offerings.