{"id":4552,"date":"2014-03-11T22:51:29","date_gmt":"2014-03-11T22:51:29","guid":{"rendered":"https:\/\/multiacademstg.wpengine.com\/20000academy\/blog\/2014\/03\/11\/service-catalogue-defining-service\/"},"modified":"2025-06-13T13:41:11","modified_gmt":"2025-06-13T13:41:11","slug":"service-catalogue-defining-service","status":"publish","type":"post","link":"https:\/\/advisera.com\/20000academy\/blog\/2014\/03\/11\/service-catalogue-defining-service\/","title":{"rendered":"Service Catalogue \u2013 Defining the service"},"content":{"rendered":"<p>Company growth is good, even desired. But usually, along with the growth of the company, the number and complexity of the services grow as well. Situations where everyone can define their own service with respective descriptions, contracts and naming nomenclature\u2026 only lead to chaos. I noticed that, looking from inside the IT organization \u2013 such chaos can exist for some time, but customers don\u2019t react to it very well. That\u2019s when management of services becomes essential.<!--more--><\/p>\n<h2 style=\"padding-top: 10px; padding-bottom: 10px;\">Properties<\/h2>\n<p>I am sure that you are familiar with the situation where you have had to define properties of the application or hardware component in order to make sure that it works (as desired). It\u2019s the same with IT services \u2013 they have to be properly defined in order to be <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=sms-related-documents&amp;doc=service-management-system-plan\" target=\"_blank\" rel=\"noopener\">managed<\/a> and to fulfill their business targets (e.g. generate profit by being ordered by the customers). Otherwise, services will be perceived as a bunch of hardware and software, i.e. as a pure IT service.<br \/>\n<div id=\"middle-banner\" class=\"banner-shortcode\"><\/div><script>loadMiddleBanner();<\/script><br \/>\n<div id=\"side-banner-trigger\" class=\"banner-shortcode\"><\/div><br \/>\nTo give you an idea of what it means to define a service, here are a few examples of service parameters:<\/p>\n<ul>\n<li>Naming the services \u2013 although it sounds simple, it could be quite confusing. If you are talking to the customer while trying to sell a service with a lot of IT vocabulary in the name\u2026 when you leave the customer\u2019s office they will not even remember that someone was there. Try to use a simple name for your service that is somehow connected with the functionality that service provides (take, for example, telecommunication companies \u2013 they sell services like \u201cMobile Internet\u201d and not GPRS, HSDPA\u2026 or whatever the technology in the background is).<\/li>\n<li>Describing the services \u2013 as we mention in <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=service-portfolio-processes&amp;doc=service-catalog\" target=\"_blank\" rel=\"noopener\">Service Catalogue<\/a>, customers speak the language of business, so such should be the description in the Business Service Catalogue (the part of the Service Catalogue which is used by customers). On the other side, the same service should have a Technical Service Catalogue that is used internally, inside the IT organization, and written in technical language.<\/li>\n<li>Establishing service hierarchy \u2013 generally,\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/blog\/2013\/03\/19\/service-catalogue-window-world\/\" target=\"_blank\" rel=\"noopener noreferrer\">Service Catalogue<\/a>\u00a0will help you organize live services, i.e. <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=sms-related-documents&amp;doc=list-of-services\" target=\"_blank\" rel=\"noopener\">services that are in use<\/a>. While creating a catalogue of services I used to implement some kind of structure, i.e. hierarchy. As suggested in the\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/blog\/2013\/03\/19\/service-catalogue-window-world\/\" target=\"_blank\" rel=\"noopener noreferrer\">Service Catalogue Management<\/a>\u00a0process, services can be divided into:\n<ul>\n<li>Customer-facing services \u2013 these are the services that the customer sees, i.e. uses. Basically, as I was told many times, with such services the customer wants to solve some of his problems i.e. satisfy some of his needs. For example, the customer wants to be able to communicate, send messages and distribute files, and we offer \u2013 e-mail service.<\/li>\n<li>Supporting services \u2013 these are the services which support, i.e. underpin, the customer-facing services. The fact is that customer-facing services can rarely exist alone, without having services that enable their existence. Let\u2019s go back to e-mail service. To be able to use e-mail service, the customer is using many other services that are \u201cinvisible\u201d to him. For example, network infrastructure, server administration\u2026 etc. They are supporting services.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p style=\"text-align: center;\"><img decoding=\"async\" class=\"aligncenter size-full wp-image-10358\" src=\"https:\/\/advisera.com\/wp-content\/uploads\/\/sites\/6\/2015\/07\/E_mail_service_support1.png\" alt=\"E mail service support\" width=\"430\" height=\"200\" \/><em>Figure: To be able to use e-mail service, the end-user uses many other (supporting) services.<\/em><\/p>\n<h2 style=\"padding-top: 10px; padding-bottom: 10px;\">Properties in real life<\/h2>\n<p>When a service is properly defined, there are a few areas where they can be of great use:<\/p>\n<ul>\n<li>Agreements, i.e. contracting \u2013 customer-facing services will use a\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/knowledgebase\/slas-olas-ucs-itil-iso-20000\/\" target=\"_blank\" rel=\"noopener noreferrer\">Service Level Agreement (SLA)<\/a>\u00a0to define the service and relationship with the customer. The <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&amp;doc=service-level-agreement-sla-\" target=\"_blank\" rel=\"noopener\">SLA<\/a> will be written in formal business language. Supporting services will use an\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/knowledgebase\/slas-olas-ucs-itil-iso-20000\/\" target=\"_blank\" rel=\"noopener noreferrer\">Underpinning Contract<\/a>\u00a0(UC) or\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/knowledgebase\/slas-olas-ucs-itil-iso-20000\/\" target=\"_blank\" rel=\"noopener noreferrer\">Operational Level Agreement (OLA)<\/a>\u00a0if they have to define relationships with some (external or internal) third party. The <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&amp;doc=operational-level-agreement-ola-\" target=\"_blank\" rel=\"noopener\">OLA<\/a> does not need to be that formal, but the <a href=\"https:\/\/advisera.com\/20000academy\/documentation\/underpinning-contract\/\" target=\"_blank\" rel=\"noopener noreferrer\">UC<\/a> is usually written in formal language. But, both of them will contain many technical details.<\/li>\n<li><a href=\"https:\/\/advisera.com\/20000academy\/blog\/2013\/12\/03\/itil-financial-management-charge-charge\/\" target=\"_blank\" rel=\"noopener noreferrer\">Charging<\/a>\u00a0\u2013 charging is the aim of all our business activities. But, having different kinds of services, there is a logical question \u2013 how? Well, that&#8217;s more complex. Essentially, there are a few options. If you are an internal service provider, you can afford to charge for both supporting as well as customer-facing services. But, to share my lessons learned with you, if you charge for supporting services directly \u201cas they are,\u201d expect to get many questions and be ready to explain technical issues in non-technical language. An alternative is that you integrate supporting services into customer-facing services and charge only for the latter. That would be the case if you are providing services to external customers.<\/li>\n<\/ul>\n<h2 style=\"padding-top: 10px; padding-bottom: 10px;\">Information sources<\/h2>\n<p>To be honest, defining the service is not an easy job. You have to see the service through the eyes of the customer. And that is your most valuable source of information. They have different views on the services than IT itself. Talk to the customers, listen and make notes. These notes are an excellent starting point for your (Business) <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=service-portfolio-processes&amp;doc=service-catalog\" target=\"_blank\" rel=\"noopener\">Service Catalogue<\/a> and service description.<\/p>\n<p><em>To implement ISO 20000 easily and efficiently, use our<\/em> <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/\" target=\"_blank\" rel=\"noopener\">ISO 20000 Documentation Toolkit<\/a> <em>that provides step-by-step guidance for full ISO 20000 compliance.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Company growth is good, even desired. But usually, along with the growth of the company, the number and complexity of the services grow as well. Situations where everyone can define their own service with respective descriptions, contracts and naming nomenclature\u2026 only lead to chaos. I noticed that, looking from inside the IT organization \u2013 such &#8230;<\/p>\n","protected":false},"author":32,"featured_media":4553,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[403,452,344,204,346],"class_list":["post-4552","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-agreement","tag-catalogue","tag-itil","tag-service","tag-service-design"],"acf":[],"_links":{"self":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts\/4552","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/comments?post=4552"}],"version-history":[{"count":3,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts\/4552\/revisions"}],"predecessor-version":[{"id":18382,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts\/4552\/revisions\/18382"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/media\/4553"}],"wp:attachment":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/media?parent=4552"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/categories?post=4552"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/tags?post=4552"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}