CSDM 5.0

[Erick18]

When will CSDM 5.0 be released? 

Thanks,

Erick

[Community Alums · Accepted solution]

I was in the K24 and fortunate to take a picture on CSDM 5 Draft at the CSDM booth on the expo floor. Interesting to see the Gen AI + Domain-LLM in the BUILD domain. @Mark Bodman, I missed both of your sessions at K24 but would be grateful if you can share some content about CSDM 5.0.

[Miklos Palfi]

Fully agree, Environment is also not good enough, I would also not recommend it.

"Product" as a name is currently so much overloaded with all those Product Models (which are in reality just (object/CI) models) that it needs to be sorted out first.

The proposed "Service Instance" seems to be a good compromise for me. (But it could also be just "Instance", which would be generic enough.)

[Peter Kindbom]

Yes. Just Instance is a good name. Keep it simpel. And use the term service when it applies and can be reasonably explained so basic service management principles can be used. 

[Michael Dul]

To me the biggest problem with any data model is that the more it grows, the harder it is to understand it. Taxonomy is the key. Every customer I worked with we had to spend a lot of effort to align on the terms like Offering, Service, Product, Application. 

In the end with the ambition to cover more than IT, System term could be limiting. As majority of us is coming out of IT, we have a bias towards IT naming. I don't think this is going to be the last evolution of that name. Service Instance is as good name as any to depict "the bunch of stuff working together technically". I actually like a term used by one of my customers, they used to call all of them "things" and there was a "thing catalogue".

Anyway, excited about the new changes, but fully aware that with the introduction of those, we will need to ensure we hide majority of it to most of our platform users and to keep talking to them in the language they understand and keep the complex academic discussions under the hood.

[PatriciaP]

All valid comments and feedback.
I started off really overwhelmed by the Data Model, but, it is such an important part of the ServiceNow eco system that it is worth and necessary to spend time trying to understand it, time to explore it in our own instances and, believe me, in time, it all comes together.
I think that it is particularly important for those that guide implementations to become familiar and versed in the model - I have seen the awful consequences of renaming, straying away from it.

And the model WILL keep growing, so the sooner we embrace it, the better our guidance to our customers will be 🙂

On the naming topic of "Application Services", I must admit it is confusing so I would actually go with the clear, simple name of "Application Instance" or "Environment Instance".

[stevenswink]

I remember years ago when our company was partnering with Sun Microsystems to develop an OS offering.  In describing their internal code collation and release processes, they used the term "WOS" frequently.  When I asked for an explanation, I was told it stood for "Wad of Stuff", as they had no better way to describe it.  8-)