- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Is it valid to model service offering related to other service offerings? We are doing an exercise in modeling our Services and Service offerings. I got the model back and they had the following. Blue is the service and green is the service offering.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Is this representing a hierarchy of service offerings? Service offerings having child offerings?
If so, no that's not intended in CSM. Service portfolio management introduces a taxonomy structure where a portfolio can have many nodes. You potentially need to move the service up a layer, and the intermediary service offerings become services
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @brianlan25
What @Kieran Anson said - the only relationship a Service Offering should have to another service object is its parent Service. By definition a Service Offering should be unique: "a stratification of the (business or technology management) service into options including localization/geography, environment, pricing, availability, capability, support group (for incident), technical approval group (for change), and packaging options (commitments)."
This is why building out the Business and Technology Portfolios and their taxonomy layers is something organisations should do at the start of their CSDM journey. Once you have the buckets (the leaf node in the portfolio) then the next layer down (the services) become self-evident.
I hope this helps!
Mat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Is this representing a hierarchy of service offerings? Service offerings having child offerings?
If so, no that's not intended in CSM. Service portfolio management introduces a taxonomy structure where a portfolio can have many nodes. You potentially need to move the service up a layer, and the intermediary service offerings become services
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @brianlan25
What @Kieran Anson said - the only relationship a Service Offering should have to another service object is its parent Service. By definition a Service Offering should be unique: "a stratification of the (business or technology management) service into options including localization/geography, environment, pricing, availability, capability, support group (for incident), technical approval group (for change), and packaging options (commitments)."
This is why building out the Business and Technology Portfolios and their taxonomy layers is something organisations should do at the start of their CSDM journey. Once you have the buckets (the leaf node in the portfolio) then the next layer down (the services) become self-evident.
I hope this helps!
Mat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
That is what I thought base do what I saw in the CSDM documentation. Thanks for the confirmation I will let the team know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago - last edited 2 weeks ago
Yes, as part of Service Portfolio Management Premium you can create dependencies between service offerings via the OOTB related lists to indicate dependencies between your offerings.
And Service <> Offering is not a relationship, but a reference.
https://www.servicenow.com/docs/r/it-service-management/service-portfolio-management/create-or-mod-S... refer to section 11.