CSDM + BCM + All those attributes!

[Phillip1]

Here's the use case: the organization has unfortunately adopted over the years that the Business Application record is the "Master" record. Hence, they want to see all kinds of special attributes on that record from various other process. The biggest of these is BCM attributes, RTO, RPO, etc. I know I need to get them to think differently about that Business Application record, but if they do want to have a single view of that type of information, I'm wondering if the Service Instance (Application Instance) would be the place where I potentially expose those other attributes via related lists of sorts. What I don't want to do is have them continue to treat the cmdb_ci_business_application table as the master records for their operations. We all know that's not it's intended purpose and most certainly those records are NOT supposed to be used in ITSM.
--> Thoughts/Ideas?

[Mark Laucus]

My past organization we were an early adopter of ServiceNow and chose to extend the service table to store the BCM attributes.   This was before the Business Applicaiton table existed and we used it to store Service or application table depending on who entered records.   I would consider storing BCM information in the Service Instance table.

[Peter Kindbom]

How about a Service Management- maturity campaign and introducing Business Services with Service Offerings for the most important Business Applications?