Let me introduce you to Alex, a young engineer who proved his competence and became an important member of his organization\u2019s IT Service Management (ITSM) team. He got a new assignment \u2013 to create the Service Catalogue.<\/p>\n
Although being thrilled with the respect and reward that his superior showed, very soon he asked himself \u2013 What now? Where to start? It\u2019s one thing to be involved in the operational processes and functions like Incident Management or Service Desk, but creating a Service Catalogue<\/a>\u00a0sounds like something completely different. And, it is.<\/p>\n That\u2019s (always) a good question. And an important one. Namely, you don\u2019t have to be a multinational company to have different types of customers, an extensive internal IT organization, various processes in place, etc. These days, even in smaller companies that\u2019s a common situation. Luckily, if the organization and its processes are based on ITIL<\/a>\u00a0principles or ISO 20000<\/a>\u00a0Service Management System (SMS) requirements, there will be clear interfaces as well as inputs and outputs that can be of great use while setting up the Service Catalogue. One thing is important \u2013 once you create the first version of the Service Catalogue, those people responsible for maintaining it have to be aware of all possible changes in inputs to that Service Catalogue. Four main sources to get necessary inputs are:Where to start?<\/h2>\n
\n