CSDM 5 Service Offering Definition 'rules'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
15 hours ago
Hello,
We are currently in the process implementing CSDM globally across organizations with decentralized services and have quite challenging routing use cases. As we are defining our services I'm running across the use case where we have over 100 applications that multiple locations/administrators do access fulfillment for the same application based on the requestor's site.
We have a single service catalog item for 'Application Access Requests' that points to our Service Offering table. I would be able to achieve nirvana if I formatted the Service Offerings using the format example below and exposed them to our catalog item, but we are being advised that this is not in alignment with CSDM 5 because we're using 'access request' label in the name.
Example:
ServiceNow Access Request - Seattle
ServiceNow Access Request - NYC
ServiceNow Access Request - Dallas
We could even add a layer of filtering for the end user to initially pick the business service so the picklist would be more refined.
I'd love to get feedback as it seems when I read the CSDM 5 the Service Offering is really meant to be a variant of the business services and if those are our service variants then I do not see why it cannot be used that way. Also, I'm not sure CSDM 5 was necessarily designed to solve organizational challenges and so we should be able to make it work for us in the way we need without massive reorgs.
Thank you!