Subscribe to service Offering

[imranbasham]

Hi,

Can you please let us know the capabilities of subscriptions with respect to Service Offering.

Is this only provide gauge for this service offering to their home pages ?

We would like to know everything about Service subscriptions in ServiceNow:

• What is it used for?
• When/How  to use this?
• Who maintains this?

[Barry Kant]

Good day,

in my opinion this initially part of Service Onboarding discussions.
When designing a new Service (Offering) you identify the target audience :

• company
• department
• location
• group
• user

I think with the exception of user subscription that can be defined on Service Onboarding phase. 

User subscription use case could be something like this:

I order something (secure token) and as outcome of the request it creates a user subscription as well.


There is a Script Include:
ServiceSubscriptionUtils

that collects all Subscriptions of the logged on person. That can be used to build the catalog item structure in the portal. 
eg:
show all catalog items for Service Offering that I am entitled to

OR

make a generic record producer for incident and show the service offering field that shows only the Service Offerings that I am entitled to

BR,

Barry

[VenniMakarainen · Accepted solution]

Hey, in addition to Barry's comments, you may want to have a look at an article I wrote awhile back:

https://community.servicenow.com/community?id=community_article&sys_id=177a4a911b7db850ccc253da234bc...

The platform drives cat item visibility automatically when an offering has subscribers + cat items are associated with an offering.

Service Owner (or a role responsible for the service delivery) would be a natural role to ensure their service is setup approprietly - SLAs, service consumers, metrics etc.

[Patrick Nie_en]

I think the number of subcribers is a very useful indicator to see how much visibility and usage a service offering has.  This is in particular the case for Business Service offerings.

However, how should we use this in relation to technical service offerings?

Example:  My "Application Operating Center" obtains a server to run the app on from the "Server Operating Center".  The subcription logic that it counts people, does not strike me as obvious, because if I "purchase" 80 VMs from the server team the number of subscriptions should be 80 and not the number of engineers working in that team/dept.

Don't we need a different subscription model that reflects CIs that are purchased by departments ?

Or alternatively should subscriptions only apply to Business Services (=consume)?