Service Portfolios and Service Catalogs: What's the difference?

[David Thigpen]

As the Product Manager for the IT Service Portfolio Management application in ServiceNow, I frequently hear questions that are not necessarily related to IT service portfolios, but more about IT service catalogs.  What really is the difference?  Many persons and organizations seem to use the terms interchangeably.  I’d like to take a moment and discuss their differences and how those are reflected within ServiceNow.

The IT Service Request Catalog
An IT service request catalog generally represents those things that an end user can currently request from IT. “Those things” can take many forms: access to systems, replacement consumables, new service consumption, answers to questions, and support from various IT services and processes like Incident Management.  Are all those things “IT Services?”   Generally, in some form, yes, even if they may not have been formally identified as such. If I go to the IT service catalog and order a product like a new laptop or keyboard replacement, is that part of a service as well?  I would consider it a deliverable of an IT Procurement service.  

IT service request catalogs provide a lot of value for an organization.  They help IT departments be more efficient, automate approval and procurement processes, and help standardize the interactions between IT departments and their user communities.  They also help manage expectations by letting end users know exactly what they can expect from the IT department.  Setting up an IT service request catalog is one of the first things many ServiceNow customers do.

The IT Service Portfolio
But do those items that are shown within the IT service request catalog truly represent all that IT does? Remember, the ITIL definition of an IT Service Portfolio includes: “The complete set of services that is managed by a service provider. The service portfolio is used to manage the entire lifecycle of all services, and includes three categories: service pipeline (proposed or in development), service catalogue (live or available for deployment), and retired services.“  So actually, the IT service request catalog (live, available) is only a portion of the entirety of the IT service portfolio.  

Notably, the IT service portfolio also includes IT services that are in various stages of evaluation or development.  This can include significant changes to existing services and their offerings.  Adding a new offering for an existing service is a good example. Since these new or changed services are not yet ready, they will not be shown in the service request catalog, but they still are consuming part of the iT budget and should be considered as part of the portfolio (in development.)  Also, that evaluation process is intended to make sure we don’t somehow end up with a new service capability that duplicates something we already have.  IT departments will also need to evaluate services and offerings in order to determine if they can be eliminated (retired) or sourced elsewhere.

Some services provided by an IT department may not have representation in the service request catalog simply because they do not have any end user consumable components.  These “unseen” services are still part of the IT service portfolio.

Final thoughts
A Service Request Catalog and an IT Service Portfolio are not the same thing and serve very different purposes.

IT Service Request Catalog

• Represents consumable IT service offerings, generally by the end user community
• Shows only those items that are available for consumption “right now”
• Organized in a manner that supports searching, browsing and ordering
• Built around the use cases of request and fulfillment

IT Service Portfolio

• Represents all IT services that now or historically have consumed IT budget
• Includes services that are under consideration or development
• Organized in a manner that encapsulates ownership, accountability and expenditure
• Built around the use cases of service life-cycle, executive communication and portfolio optimization

I hope this new understanding helps you get more out of your ServiceNow investment!

[Vlad24]

What I'm struggling with is the relationship between the two inside the ServiceNow's ITSM implementation. The logical layout of the two may be different but how hard should/could we try to relate the two to each other?  Im struggling sorting out the documentation in how the incidents and problems raised against a service, the requests raised against a service, and the portfolio itself all connect together in a cohesive image of the entire service.  Are there any good resources explaining the relationships?

[David Thigpen]

Hi Vlad,

As of NY we've enabled the Service Owner to create a new catalog item from an offering if proper conditions are met (offering state mostly.)  That creation process connects the offering and the catalog item.

As of Paris, we're targeting the ability to connect pre-existing catalog items and service offerings.

In both cases, this is to enable the Offering Performance model as part of the Professional level licensing.

CSDM 2.0 has some information on offerings - namely that we intend to have and leverage offering capability for all service types (technical, application, service.)  

[Steven Torok]

Hi David,

hope you are well.

I just came across this thread as I was searching for information on Service Portfolio Mgmt within Service Now.  Thanks for clearly differentiating Portfolio Mgmt vs Catalog Mgmt.

On a related note (I hope this thread is ok to ask), can you help point me to documentation which clearly outlines the ServiceNow "out of the box" process/workflow for Service Portfolio Management?

Thanks for your direction!

Cheers,

Steve

[David Thigpen]

Hi Stephen,

Thank you!

We do not yet have a recommended process/workflow "in" the product,  but we are actively working on mechanisms to better enable organizations to create or onboard new services.  

In the meantime, I'd suggest contacting the ServiceNow Customer Success organization as they can provide specific guidance related to your request.

David 

[leighmullin]

Hi David, i've been reading the documentation but can't find any training/overviews in Now Learning related to this product (SPM)?  I'm struggling to visualise the hierarchy of service/taxonomy/portfolio/node/layer??

[mahesh_vavilal1]

Here is the hierarchy

Service Portfolio --> Taxonomy Node --> Business Service --> Service Offering --> Catalog Item.

Taxonomy Nodes are defined/ configured via Taxonomy Layer Definition.

Example: if you have 2 levels between a Portfolio and Business service, you will define it as a Taxonomy Layer. This is completely configurable based on your organization process.

[Paulo Xax_]

Congratulations on the post, very enlightening and useful for everyone; for me at the moment I am responsible for implementing the IT service catalog in SERVICENOW, with the mission of using the "SERVICE PORTIFOLIO MANAGEMENT" and the service portal.

But if I have a "VPN" business service, for which we want to have a catalog item in the "VPN Access Request" portal through which end users have registered requests about it and also that users can register incidents concerning "VPN": how to have this in SERVICENOW so as to be in these incidents and requests and see this business service, and be in this business service and find these incidents and requests?

I've been looking for a manual on this in the community and in the official documentation, but to no avail.

Any suggestions or recommendations?