Relationship of a Bus App to a Tech Service Offering

[Chris Martin5]

I seem to have a contra-view in one area of the CSDM that I'd like someone to convince me why this doesn't make sense.   

Premise 1:  Business Apps can have relationships to Applications Services which represent the tech stack supporting the Bus App.

Premise 2:  Technical Services have relationships to App Services which represent the tech stack supporting the Tech Service Offering.

Premise 3:  Tech Services typically underpin business services

Premise 4:  Adopting Business Services at companies is a mature concept and (arguably) not critical to ever achieve

Conclusion:  Tech Service Offerings should be able to have a relationship to Business Apps where they are a supporting service for the Bus App (think, "shared service").  they would have their own App Service representing their infrastructure.

This is not in line with CSDM but, in truth, I think it should.  I want a way to represent technology shared services in the csdm and track which Bus Apps consume those.

[Chris Martin5]

I think I was not clear.  I am suggesting that a Bus App be linked to a Tech Service Offering called MQ Series Service.  and both the Bus App and the TSO for MQ have their own Application Services which then link to the specific infra CI's that make those up.  does that makes sense?

[Tomas Lozano]

Hello Chris

I have seen this at a larger clients.. Application Services as per the whitepaper are used in many ways, however it remains a technology component without the ability to store the necessary qualifying metadata needed. The assumption in the CSDM whitepaper is that the Business/Technical Business Service or the Business Application defines the type of Application Service type implicitly i.e. the context, however where an Application Service is shared, it's tricky to distinguish them.

Having said that, the model supports the logic in place and i would not only test the setup thoroughly with en eye on areas like SLA, availability etc. but also consider that any future change could break it.

Creating an idea (enhancement request) for the pain point or talking with your contacts at ServiceNow may be a good way for your pain point to be addressed in the future, considering the product team is looking to release CSDM 5 soon. It appears to be heavily influenced by IT4IT 3.0 and i'm personally hoping the Application Service object to morph slightly to encompass more metadata.

Best regards,

Tomas