Has anyone tried (or is anyone) attempting to model their Epic platform according to the CSDM?

[dwilcher]

Just curious if anyone out there has taken a crack at modeling their Epic platform according to the Common Services Data Model (CSDM)?

I attended the "Applying the CSDM" session at K19 given by Scott Lemm (CSDM Product Manager at SN), and was intrigued how we'd model Epic (particularly in the Service Portfolio Management module after the updates coming in New York). Also, in light of this recent post and the comments from Scott, we're wondering if we would treat Epic as a "platform use case" that he talks about.

Anywho, just curious what folks thoughts are. If you're doing it already, looking at doing it, etc. I included a couple of quick sketches we did (didn't have an orange marker handy for the infrastructure CIs, but hopefully the idea is clear with green and blue as services & business). Would love to know what folks have tried themselves or what your support teams are thinking.

The only real difference between the two is the level of granularity we have around service offerings. I suspect this may be customer dependent on how granular folks want to do things like availability, etc. around offerings. 

*PS, we're aware of the UNC on-demand webinar around Epic & SN ITOM, but that was quite some time ago and it seems that the CSDM is bringing some significant changes.

[Lorenzo Pizarro]

We are embarking on a conversation to Epic from Soarian, eCW, et al, so this thread is of interest. Closer to home, we are looking at a CMDB 2.0 initiative, so the three - Epic conversion, CMDB 2.0, and CSDM compliance has synergistic opportunities.

[ettawilson]

Hello,

We're starting to map Epic starting with the business applications using the CSDM 2.0 framework.  I set Epic as the platform host.  As you can see from the attachment, when you look at the related list for Epic, the application/modules are listed. I also brought in the idea, demand, and project in the related list. The instance we're using is New York.  

I plan to share the business applications list with the group when I'm finished. 

If you or anyone else wants to provide feedback or join the party, I can schedule something so we can all work on this together.  

Etta

[dwilcher]

Hi Etta,

Totally agree - especially with the latest guidance from the CSDM 2.0 whitepaper, the platform approach seems ideal for Epic.

Right now our main source of debate internally is more in the Service Portfolio world when it comes time to build out the Service offerings (and how deep to go with the Service Offerings). So in my two earlier photos we've tried approaches where the offerings are (largely) a 1:1 match with the Business Applications, and we've considered a "deeper" scenario where we'd have a much more extensive Service Offering build. Have you been doing any work in this area yet?

Best,

David

[Oanh K Nguyen]

Hi Etta,

Thank you for your post!  It's similar to what we try to do at our organization.  We also use Epic Platform and different region has different Business Application.  Then each Business Application breaks into smaller modules (Caboodle, Cadence, etc.).  Then Change Mgmt wants it even more granular to the instance of these modules.  Does your company also have instance level?  If so, how do you plan to map it?  Is it Application Services would be appropriate to map for these instances? 

[chadh]

Etta -- Thank you for your post and sharing.  I'd love to see what you eventually settled on.  I'm over Epic applications at Baylor in Houston and have been looking at these concepts with our larger IT team.  Business Application is where I think we should "list" all of the Epic Modules we use.  Can you share how you ended up using the CSDM to document your environment?

I'm also interested in tracking demands, projects, incidents, changes, etc. relative to these applications.  Of course we have others outside of Epic, but they'll be much easier once I determine how to track Epic.

Thanks,

Chad