Hi folks,
Not sure if anyone remembers a post I made a while ago about how we were attempting to model Epic in accordance with the CSDM (Common Services Data Model).
I was on a ServiceNow webinar with Accenture this week (which you can view on demand here), and saw some great content I wanted to share. For those of us attempting to map out Epic via the CSDM, there are a couple of slides that you'll find pretty interesting (screenshots attached). Good news is that this lines up almost exactly with what we were thinking when we were doing our version of this. Anyway, wanted to share in case others are interested!
Best,
David
From reviewing this post, I would recommend using Application Services to represent the current list of Business Applications since Business Application cannot be used by ITSM (INC, Change, Request, MIM), however, application services can and was designed for that purpose. Business Application should be "Epic" and all usage of Epic be listed as Application Services or various usage or installation of Epic. This is in line with CSDM v2 and will also align with v3 which is in beta today.
Further more, the Business Services Offering is better place to add the environment variables since you can add SLA and OLA, setting yourself up for SPM (Service Portfolio Management) at a future date. Current design does not take the potential SPM (green section of CSMD) into consideration nor APM (Application Portfolio Management - blue section) into consideration and full use.
This is a great start for the discussion.
APM should focus on the business needs and how business understands the capabilities/offerings.
