Sharing real World CSDM Data?

[Tone1]

Someone eager to share real world data of their CSDM Tech Services/Offerings?

Over time i saw a lot of different approaches how to model the Technical part of the CSDM and more i know the more i get confused. Is someone willing to share some excel exports of the Service Delivery part?

[GlideFather]

Hi @Tone1,

do you mean CMDB data?

CSDM is just a framework, a set of recommendations and best practices on how to manage the condiguration data. But CSDM as such doesn't have any data at all. 

Check this:

• CSDM Overview 
• CSDM Whitepaper 

Let me know what do oyu think about these resources and eventually please define what data would oyu like to talk about..

Have a wonderful day, 

[Stig Brandt]

On now create you find  CSDM examples ppt for all different technologies.

good luck with the journey.

[Mathew Hillyard]

@Tone1 

Are you looking for examples of Service offerings or the technical CSDM map of a service modelled from the Service offering downwards?

If the first then I always recommend people look at it from a portfolio perspective. Get a copy of the TBM and visualise the elements as service portfolio taxonomy layers with the services that contain offerings at the lowest level. It then becomes quite simple to work out what sort of offerings a given service might contain.

If however it's the second option, then @Stig Brandt's recommendation of the CSDM examples PPT on NowCreate is ideal.

I hope this helps!

Mat 

[Tone1]

Hi everyone,

I’m currently in a bit of a heated debate with our integrator. We’re implementing CSDM from the ground up, and he suggests using prefixes to identify services, for example “AS- …” for Application Services, “BS- …” for Business Services, and so on.

This would lead to names like:
“AS - OnPrem Microsoft Exchange - Production”.

I come from a CMDB background (not exclusively ServiceNow), and over the years I’ve learned that duplicating metadata in the name field is a bad practice and usually creates more problems than it solves.
Since the class of the record already clearly identifies the object type, adding prefixes feels redundant, and in my opinion, it also makes the names harder for end users to read and understand.

That's why i asked for "real world data", i want to see the naming conventions others used in the past.

But my main questions are:

Are these prefixes considered common or recommended?
Should I actually use them in a CSDM-aligned implementation?

Thanks in advance for your insights!