Our further Tool-Portals |
![]() |
|
![]() |
![]() |
|
.... ITSM excerpt .... |
||
Process Templates ITSM Process Library Implementation Kits Role Descriptions Academic Initiative |
|
||
ITSM Processes of Service Operation
|
||
from our series "Processes of IT Service Management" |
||
|
||
and thus accelerates your project remarkably and saves costs also (especially external consulting costs). |
Saving hint: complete package (all 5 process collections) with 20% price advantage
€ 280.-
including everlasting access to our ITSM Archive for free |
The purpose of this ebook is not provision of theoretical knowledge but shows the experience of numerous implementations of process oriented IT Service Management from practice. From the perspective of the ITIL® standard all subtopics have more or less the same priority - practice shows a different picture. We have built our process library described in this publication exactly to practical considerations, practical relevance has the primary focus.
Each process is described by
The glossary at the end of the document outlines detailed descriptions of
and provides checklists to key topics. |
And now i wish you a fruitful and interesting reading!
Sincerely yours
Dipl.-Ing. Walter Abel
|
![]() |
Copyright, trademarks and property rights
"Signavio" and "Signavio Process Manager" are trademarks of Signavio Gmbh, Kurfürstenstraße 111, D-10787 Berlin "ARIS" is a trademark of Software AG, Uhlandstrasse 12, D-64297 Darmstadt "ITIL®" is a registered trademark of AXELOS Limited "ITSM Process Library" is a trademark of Dipl.-Ing. Walter Abel Management Consulting, Hauptplatz 34/8A, A-2070 Retz
|
1 Content |
|
4 |
|
6 |
|
3 Service Lifecycle |
9 |
14 |
|
14 |
|
15 |
|
23 |
|
4.3.1 Event Management |
25 |
4.3.1.1 Interfaces |
26 |
4.3.1.2 Organization of Event Management |
30 |
4.3.1.3 Event Monitoring |
36 |
4.3.1.4 Event Tracking and Closure |
41 |
4.3.2 Incident Management |
46 |
4.3.2.1 Interfaces |
47 |
4.3.2.2 Organization of Incident Management |
55 |
4.3.2.3 Incident Registration |
63 |
70 |
|
4.3.2.5 Incident Resolution Second Level |
78 |
4.3.2.6 Incident Monitoring and Escalation |
85 |
4.3.2.7 Major Incidents |
91 |
4.3.2.8 Incident Tracking and Closure |
98 |
4.3.2.9 User Information |
103 |
4.3.2.10 Incident Reporting |
106 |
4.3.3 Problem Management |
109 |
4.3.3.1 Interfaces |
110 |
4.3.3.2 Problem Registration |
115 |
4.3.3.3 Problem Resolution |
120 |
4.3.3.4 Problem Tracking and Closure |
127 |
4.3.3.5 Review of Major Problems |
132 |
4.3.3.6 Problem Reporting |
136 |
4.3.4 Access Management |
139 |
4.3.4.1 Interfaces |
140 |
4.3.4.2 Enlistment and Retirement |
145 |
4.3.4.3 Management of User Profiles |
156 |
4.3.4.4 User Permission Request |
162 |
4.3.5 Service Request |
168 |
4.3.5.1 Interfaces |
169 |
4.3.5.2 Service Request |
173 |
4.3.5.3 Backup Recovery |
178 |
4.3.6 Operations Control |
186 |
4.3.6.1 Interfaces |
187 |
4.3.6.2 IT Operations Management |
192 |
4.3.6.3 Contingency Activities |
202 |
211 |
|
211 |
|
221 |
|
222 |
|
228 |
|
6 Responsibility Assignment Matrices (RACI) |
229 |
6.1 Responsibility Assignment Matrix for Event Management |
230 |
6.2 Responsibility Assignment Matrix for Incident Management |
231 |
6.3 Responsibility Assignment Matrix for Problem Management |
232 |
6.4 Responsibility Assignment Matrix for Access Management |
233 |
6.5 Responsibility Assignment Matrix for Service Request |
234 |
6.6 Responsibility Assignment Matrix for Operations Control |
235 |
7 Checklisten for Service Operation |
236 |
7.1 Checklist Request for Change |
236 |
7.2 Checklist Incident Record |
238 |
7.3 Checklist Initial Analysis of Incident |
240 |
7.4 Checklist Incident Priority |
242 |
7.5 Checklist Incident Escalation |
244 |
7.6 Checklist Incident Management Report |
245 |
7.7 Checklist Capacity Reporting |
247 |
7.8 Checklist Operational Level Agreement |
249 |
7.9 Checklist Continual Service Improvement Register |
253 |
7.10 Checklist Service Level Requirement |
255 |
7.11 Checklist Service Level Agreement |
256 |
7.12 Checklist Service Level Report |
260 |
7.13 Checklist Service Catalogue |
262 |
7.14 Checklist Service Portfolio |
263 |
7.15 Checklist Service Design Package |
266 |
7.16 Checklist Service Specifikation |
270 |
7.17 Checklist Availability Reporting |
274 |
7.18 Checklist Underpinning Contract |
276 |
7.19 Checklist Problem Record |
279 |
7.20 Checklist Problem Priority |
281 |
7.21 Checklist Problem Closing |
283 |
2 The novelties within the ITIL® V3 revision 2011Since the publication of the ITIL® V3 more than 500 improvement proposals (changes and completion) for the roles, processes and interfaces have been provided from the users and the training organizations as well. This has been major input for the description of the IT Service life cycle. Requirements from the Sarbanes-Oxley Act (SOX) have been added thus providing improved transparency of the processes. Outsourcing and cloud strategies have been requiring enhanced security management with tightened control and documentation duties.
Roles, interfaces, inputs and outputs have been harmonized within the five publications, errors and inconsistencies in text and graphics have been removed. Hence the edition 2011 is more easy to read, control, translate, implement and communicate.
The changes in detail
|
Process Responsible |
||||||
Process Content |
First level processes for efficient and effective IT Service Operation. |
|||||
Process Goal |
Efficient and benefits oriented IT Operation. |
|||||
ISO20000 relevant |
yes |
|||||
ISO9000 relevant |
yes |
|||||
SOX relevant |
yes |
|||||
Involved Organizational Units and Roles
|
|
Incident Management is responsible for the efficient resolution of all kinds of Incidents and fastest possible return to standard operation after such Incidents.
This contains basically the following subprocesses:
This process group was already part of the previous version of ITIL®.
In the following paragraphs the sub processes of this process group are described in detail.
|
4.3.2.4 Incident Resolution First LevelClick the image for a bigger view in a new window
|
Process Details |
|||||||||||||||||||||||||||||||||||||||||
Process Responsible |
|||||||||||||||||||||||||||||||||||||||||
Process Content |
Immediate Resolution of the Incident as far as possible in agreed schedule, otherwise transfer to 2nd Level Support. |
||||||||||||||||||||||||||||||||||||||||
Process Goal |
Fastest possible solution for Incidents within the agreed time frames and earliest possible handover to 2nd Level Support in case of no immediate solution possible. |
||||||||||||||||||||||||||||||||||||||||
ISO20000 relevant |
yes |
||||||||||||||||||||||||||||||||||||||||
ISO9000 relevant |
yes |
||||||||||||||||||||||||||||||||||||||||
SOX relevant |
yes |
||||||||||||||||||||||||||||||||||||||||
Involved Organizational Units and Roles |
|||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
Process Flow Incident recorded (Start Signal Event) Business Unit
Initial analysis of Incident (Task) The Incident is initially analyzed according to the criteria
Complaints are prequalified prior to handover to Feedback Management. Business Unit Accompanying Documents
Incident / Major Incident / Security Relevant Occurrence / Qualified Complaint (Data Based Exclusive Gateway) Business Unit
Forward ticket to Major Incident Team (Task) The Incident Ticket is forwarded to the Major Incident Team. Business Unit
Ticket forwarded to Major Incident Team (End Signal Event) Business Unit Glossary Item Major Incident Team (Organisation)
Forward complaint to Feedback Management (Task) The qualified complaint is forwarded to Feedback Management. Business Unit
Qualified complaint forwarded to Feedback Management (End Signal Event) Business Unit
Search for relevant documented solution hints (Task) For resolution based upon the initial analysis the knowledge base of Incident Management is searched for relevant comparable Incidents and their resolutions. Business Unit Data Repositories
Determine whether directly solvable (Task) The decision about the immediate solvability by 1st Level Support is made. Business Unit
Solvable by 1st Level Support ? (Data Based Exclusive Gateway) Business Unit
Workaround required ? (Data Based Exclusive Gateway) Business Unit
Resolve Incident causally (Task) The Incident is resolved causally. Business Unit
Check completeness and effectivity (Task) The completeness and effectivity of the workaround for Incident resolution is verified. Business Unit
Actualize Configuration Items (Task) As far as the Incident resolution changed Configuration Items they are actualized. Business Unit Data Repositories Configuration Management System
Verify immediate effectivity with Initiator (Task) The immediate effectivity of the Incident resolution is verified with the Initiator. Business Unit Additional Participants
Effective ? (Data Based Exclusive Gateway) Business Unit
Implement workaround (Task) In case the immediate resolution needs a Workaround it is implemented. Business Unit
Check completeness and effectivity (Task) The completeness and effectivity of the Workaround for Incident resolution is verified. Business Unit
Actualize Configuration Items (Task) As far as the implementation of the Workaround changed Configuration Items they are actualized. Business Unit Data Repositories Configuration Management System
Verify immediate effectivity with Initiator (Task) The immediate effectivity of the Workaround is verified with the Initiator. Business Unit Additional Participants
Capture Problem Record to Incident (Task) For the Incident resolved by Workaround (means not causally resolved) a Problem Record is captured which triggers the processing by Problem Management. Business Unit
Effective ? (Data Based Exclusive Gateway) Business Unit
Document Incident resolution (Task) The resolution of the Incident is documented in the knowledge base of Incident and Problem Management. Business Unit Data Repositories
Set Incident Status to "resolved" (Task) The status of the Incidents is set to "resolved". Business Unit Data Repositories
Inform Initiator (Collapsed Subprocess) The Initiator of the Incident is informed about the resolution. Business Unit
Incident resolved (End Signal Event) Business Unit
Check the available time for resolution (Task) In case the resolution by Workaround was not effective the residual resolution time is checked to determine a decision about handover to 2nd Level Support. Business Unit
Agreed resolution time in danger ? (Data Based Exclusive Gateway) Business Unit
Incident reported to Problem Management (End Signal Event) Business Unit
Define responsible in 2nd Level Support (Task) In case the Incident is not directly solvable by 1st Level Support the competent person or group in 2nd Level Support is identified. Business Unit Data Repositories
Forward ticket to 2nd Level Support (Task) The Incident Ticket is forwarded to 2nd Level Support. Business Unit Data Repositories
Ticket forwarded to 2nd Level Support (End Signal Event) Business Unit Glossary Item 2nd Level Support (Organisation)
Forward ticket to Security Management (Task) The Incident Ticket is forwarded to Security Management. Business Unit
Inform Security Management (Task) Security Management is informed instantaneous about the security relevant Incident. Business Unit Additional Participants
Security Relevant Occurrence forwarded to Security Management (End Signal Event) Business Unit
Involved IT Systems
|
5 Glossary5.1 Process Documents in Service Operation
Availability Management Report The Availability Management Report informs the other ITSM functions about the availability of IT Services and IT Infrastructure.
The Capacity Management Report contains all relevant information about usage and performance of the IT Services and IT Infrastructure.
Change Models define the content and the procedure for Standard Changes. These are pre-approved Changes with low risk.
The Change Record is based upon the Request for Change and documents the complete life cycle of a Change.
The Change Schedule (Forward Schedule of Changes) contains the planning of all approved Changes including their accompanying information and dependencies.
Configuration Items are the operating resources of the IT services in general. They are maintained within the Configuration Management Database (CMDB), which itself is a core component of the Configuration Management System.
Continual Service Improvement Register The Continual Service Improvement Register (CSI Register) is the basis for all potentials and initiatives for the improvement of the service quality over the service life cycle. In the cyclic CSI Register all activities to improve the service quality are documented.
An Emergency is a complex breakdown of IT Systems and / or IT Services, e.g.:
Emergency Procedures define all activities for the fastest possible restore of operation of IT Systems after emergency situations (disasters, complete breakdown of IT Services or locations, aso.). This restore has normally two steps:
The Event Correlation describes the relations between events and necessary operational interventions respective necessary error messages. The rules for the Event Correlation define the appropriate reaction to an Event.
Message about a recognized malfunction of an IT System or an IT System Component from Event Management.
The Event Record describes relevant status changes from the operation of IT Services and IT Infrastructure Components. They may be status changes but also alarm situations.
The Event Statistics shows patterns and trends of Events and allows an analysis of the efficiency of the Event Recognition.
Automated message about a recognized malfunction of an IT System or an IT System Component from the Event Management to the Service Desk System.
The Improvement Report provides information about planning and results of Continual Service Improvement for the other IT Service Management functions. It contains planned, actually executed and since the last report finished service- and process improvement activities and their expected respective achieved results. Furthermore proposals for future additional service improvement activities are provided.
The Escalation Rules for Incidents define the hierarchy levels for escalation of an Incident and the triggers therefore.
The Incident Management Report informs all involved ITSM Disciplines about occurred Incidents and their elimination.
Message by an IT Service Consumer or an IT employee about a recognized malfunction of an IT System or an IT System Component.
Incident Models describe the predefined activities to handle known and recurring types of Incidents and their effective and efficient elimination.
The Incident Record contains all information about an Incidents over its lifecycle. Typically it is documented in the Service Desk System.
The IT Budget is a rolling business period related financial plan containing a prognosis of expenses and revenues to be expected for the IT Organization. Within the IT Budget funds are allocated to the processes of the IT Service Management respective to the organizational units of the IT Service Provider.
The IT Operations Schedule contains the planning of all recurring activities for the maintenance of operation for the IT Systems and a friction free IT Operation:
An IT Requirements Request represents an application for procurement of services and/or goods from external Suppliers of the IT. The IT Requirements Request describes the contents of the demand and is transformed into a definitive purchasing requisition within the IT Procurement Process.
The IT Service Continuity Report informs about the actual status of Contingency Planning and the actual Emergency Procedures.
A Known Error is a Problem whose cause is known and documented including a documented Workaround (as far as available).
A Major Incident is an Incident with serious negative impact on the business activities of the company.
The Operational Level Agreement provides an internal contract between the IT Service Provider and another part of the IT Organization regarding the provision of an IT Service Contribution. It defines besides others:
Operational Tasks are routine tasks to maintain friction free operation of IT services:
Planned Service Outages due to the implementation of Changes by Service Transition. These Planned Service Outages are normally within the maintenance time frames according to the Service Level Agreements and thus do not reduce the contractual agreed Availability of the respective IT Services.
The Problem Management Report informs all involved ITSM Disciplines about open Problems and Problems in process and the related solutions and Workarounds.
The Problem Record contains all information of a Problem over ist lifecycle. Typically it is documented in the Service Desk System.
The Purchase Order is the binding order to the Supplier to deliver the goods and/or services specified in the purchase order under the conditions described there respective in accompanying related documents.
Recommendation for Process Quality Improvement Trigger for the optimization of the quality of IT processes as input for the process review.
Recommendation for Service Quality Improvement Trigger for the optimization of the quality of IT services and IT infrastructure services by changes in as input for the Service Review.
The release package contains all Configuration Items belonging to the respective release. Those Configuration Items may be
The Release Record documents the complete lifecycle of a Transition Project.
Notification of a detected malfunction of an IT System respective IT System Component within a externally provided IT Service respective IT Service Contribution to the external Supplier.
The Request for Change is a formal request to perform a Change required for all types of Change not defined as release free Standard Change.
The Request for User Account is an application for installation of an user access within an IT System. This installation requires an authorization by a respective User Role and the availability of licenses for the involved IT system as well.
The Request for User Permission is an application for installation, modification or deletion of User Permissions within an IT system.
The Risk Log is a rated catalogue of identified risks and accordingly defined activities for minimization and mitigation.
Message about recognized necessary activities from Risk Management.
A Security Alert serves as initial information about newly recognized or even actually occurred security threats, providing the possibility to avoid or defend the threat for the receiver.
The Security Management Report provides information about security relevant occurrences and activities and about the security situation of the IT Organization.
The Service Catalogue is the part of the Service Portfolio visible for the IT Service Consumers. It contains a complete listing of all active IT Services of the IT Service Provider including those released for deployment.
A Service Contribution is a necessary part of the provision of an IT Service (Business Service), normally IT Basic or Infrastructure Services necessary to fulfill the Service Level Arrangements of the IT Services part of which they are.
The Service Design Package describes the requirements to the development of IT Services based upon Service Level Requirements. It contains the requirements from the customer's perspective and describes how they will be realized from technical and organizational perspective.
The Service Documentation contains the complete description of the IT Services including all documentation needed for operation, maintenance and further development. This includes besides others:
The Service Landscape documents the relations between Business Services and IT Services at one hand and the relations between IT Services and IT Infrastructure at the other hand. Thus it assures the logical link from Business Service down to Configuration Items.
The Service Level Agreement defines the mutual contractual requirements regarding the IT Service. This contains besides others:
Service Level Arrangements cover all service level relevant agreements and contracts: The Service Level Report informs about the agreed service quality of the Service Providers respective Suppliers comparing the agreed and achieved Service Levels. The report furthermore provides information about the utilization of the IT Services, ongoing activities for Service Improvement and extraordinary occurrences.
The Service Level Requirement contains all requirements to an IT Service from the business perspective of the IT Service Consumers. It defines besides others:
During service designs the Service Level Requirement is the basis for the service contract and the Service Level Agreement.
The Service Portfolio contains a complete listing of all IT Services of the IT Service Provider:
Visible for the IT Service Consumers is the service catalogue (see there) as subset of the service portfolio. Not visible for the IT Service Consumers are:
Request from an IT Service Consumer or from an IT employee for:
Systematic, cyclic and operationalized long range planning of the goals of the IT Service Provider and for the IT services.
A Standard Change is a low risk recurring change, which does not need a explicit release by the Change Manager being generally released. Each standard change is described in a Change Model.
The Standard Operating Procedures contain the rules for recurring standard activities of the IT Operation and the according targets for these activities and processes.
The Transition Management Report contains information about all active and planned Transition Projects (status, milestones, finish).
An Underpinning Contract is a contract between the IT Service Provider and an external service supplier about the delivery of IT Service Contributions. It defines besides others:
Proactive information of the IT Service Consumers about
The User Permission grants a defined scope of access to defined IT services or IT systems.
The User Record contains the system specific permissions of an User besides the identifying basic data.
The User Role describes the correlation of business oriented roles of users and the corresponding defined User Permissions in IT Systems.
A Workaround is a bypass solution for an incident or a problem, where no cause eliminating solution is available so far. Goal of the workaround is to reduce or avoid the effects of the incident respective problem until a final solution is available.
5.2 Involved Organizational Units in Service OperationThe organizational unit in charge for cost accounting, calculation, budgeting, cost control and monetary decision support (internal reporting).
The responsible Service Provider.
The organizational unit or group inside the IT who is in charge for development, maintenance and support for IT applications.
The organizational unit or group inside the IT who is in charge for the IT Operation (infrastructure, operational services).
IT Facilities are all assets plus organizational and technical environment to house the IT Infrastructure:
5.3. Involved Roles in Service Operation
The responsibility of 1st Level Support is to register and classify incoming notifications. In case of incident messages he/she undertakes an immediate effort to restore a failed IT service as quickly as possible in case of foreseeable success. If no ad hoc solution can be achieved, 1st Level Support will transfer the incident to the appropriate technical support groups (2nd Level Support). 1st Level Support also processes Service Requests of Users and keeps Users informed about their notifications' status at agreed intervals or status changes.
2nd Level Support takes over incidents which cannot be solved immediately by the means of 1st Level Support. If necessary, he/she will request external support, e.g. from software or hardware manufacturers (3rd Level Support). The goal is to restore a failed IT Service as quickly as possible, if necessary by implementation of a Workaround. If no causal solution can be found, the 2nd Level Support passes on the incident to Problem Management for further processing.
3rd Level Support is typically located at external Suppliers (hardware or software manufacturers). Its services are requested by 2nd Level Support if their technical expertise is not sufficient respective additional skills are required for solving an incident or problem. The goal is to restore a failed IT Service as quickly as possible.
The Access Manager is responsible for approvals of permissions to use an IT Service, data and other IT Assets for authorized Users based upon the specifications of the IT Security Management and cares for the prevention of access for unauthorized Users at the same time.
The Application Manager is responsible for operation of, the User support resources in 2nd Level Support for and the support of further development of the applications in his area over their life cycle.
The Availability Manager is responsible for the definition, analysis, planning, measuring and improvement of all aspects of the availability of IT Services in respect to the agreed service levels. He/she is responsible for ensuring that all IT Infrastructure, processes, tools, roles and other utilized auxiliary means are appropriate for the agreed service level targets of availability (also in the future based upon known business requirements).
The Capacity Manager is responsible for ensuring that IT Services and IT Infrastructure are able to deliver the agreed service levels from capacity perspective in a cost effective manner. He/she is responsible for ensuring that all IT infrastructure, processes, tools, roles and other utilized auxiliary means are appropriate for the agreed service level targets of capacity (also in the future based upon known business requirements).
The Change Advisory Board is a team from all organizational units of the IT Service Provider, its customers and (as far as necessary) Suppliers, advising the Change Management in classifying, evaluating, prioritizing, scheduling and releasing of changes. It meets on a periodical basis.
The Change Manager authorises, documents and controls all changes in the IT services, the IT infrastructure and their components (Configuration Items (CI)) over the change lifecycle, in order to maintain a minimum amount of interruptive effects upon the running operation. In the case of further reaching changes, he/she involves the Change Advisory Board (CAB), in emergency cases the Emergency Change Advisory Board (ECAB).
The Compliance Manager's responsibility is to ensure that standards and guidelines are followed. This covers
Continual Service Improvement Manager The Continual Service Improvement Manager is responsible for managing improvements to the IT Services and the IT Service Management processes over their life cycle regarding the development of business requirements and the IT Service Strategy. He/she continually measures the performance of the IT Service Provider and designs improvements to IT Services, IT Infrastructure and IT Processes in order to increase efficiency, effectiveness, and profitability of the IT Service Provider.
Emergency Change Advisory Board The Emergency Change Advisory Board is a team consisting of members of the Change Advisory Board, called by the Change Manager on short notice in Emergency cases, who make decisions about high impact emergency changes. Selection of members of the Emergency Change Advisory Board is decided at the time a meeting is called depending on the nature of the emergency change.
The Financial Manager is responsible for managing the IT Service Provider's financials containing
The Incident Manager is primarily responsible for the fastest possible restoring of a failing IT System in case of incidents. He/she is the first stage of escalation for incidents in case they are not resolvable within the agreed service levels. Furthermore he/she is responsible for the intake and content conforming handover of customer messages of any kind (besides Incident Messages).
The Information Security Manager is responsible for ensuring the confidentiality, integrity and availability of an organization�s IT Services, IT Infrastructure, IT Assets, information and data (in all ways of presentation). He/she is usually involved in an organization wide approach to Security Management.
The IT Controller is the person in charge for the responsible Service Provider within the controlling department.
The IT Facilities Manager is responsible for the physical infrastructure housing the IT Infrastructure
Responsible manager of IT according to the organizational structure.
The IT Operations Manager has the overall responsibility for all activities of IT operations:
IT Operators are the staff who performs the ongoing operational activities:
All (internal and external) persons or organizational units, who consume the services of the IT Service Provider.
The IT Service Continuity Manager cares for the provision of the minimum service levels agreed upon in the Service Level Agreements in cases of disaster. To achieve this he/she
The group of leading persons inside the IT who are in charge for the disciplines of IT Service Management.
The Major Incident Team is an event driven arranged team of IT executives and technical experts lead by the Incident Managers concentrating on the resolution of a Major Incident (grave incident with influence on the company business).
The Problem Manager is responsible that all problems are handled over their whole lifecycle to
The Process Owner is responsible for the friction free, economical and goal oriented operation of his/her process(es) (business process, IT process). This includes
Possible future IT Service Consumers with defined demand for IT Services.
The Risk Manager is responsible for identifying, assessing and controlling risks. This includes the
The Service Catalogue Manager is responsible for developing and maintaining the service catalogue based upon the service portfolio, ensuring that all information within the service catalogue is accurate, up to date and accessible for all authorized persons.
The Service Design Manager is responsible that new respective existing services are designed that
The Service Level Manager is responsible for the setting up executable Service Level Arrangements
in a way that the goals defined in these arrangements are reachable in economic manner. The achievement of goals is controlled and reported by him/her.
The Service Owner is responsible for the management of IT Service(s) assigned to him/her over their lifecycle. He/she supports the maintenance of the Service Strategy and the Service Portfolio.
Service Request Fulfillment Group The Service Request Fulfillment Group specializes on the fulfilment of certain types of Service Requests. Typically, 1st Level Support will process simpler requests that can be answered immediately, while all others more extensive or more complex from content perspective are forwarded to the specialized fulfillment group in charge.
External suppliers of IT Services, IT Service Contributions and outsourcing services, where the scope of supply is defined in the Underpinning Contracts, external suppliers of infrastructure and operating supplies.
The responsibility of the Supplier Manager covers
The user of an IT System within the business organization (internal and external). Users are the purely operative subgroup of the IT Service Consumers.
5.4 Involved IT Systems in Service OperationThe database of Change Management documenting all relevant information (Change Records) of all stages of the life cycle of Changes.
Configuration Management System The Configuration Management System (CMS) contains a coherent logical model of the infrastructure of the IT organization. Within there is stored the information of all Configuration Items (CIs) maintained by the Configuration Management. This includes Configuration Records, Incident-, Problem- and Change - Information. The Configuration Management System may consist of a number of data bases connected via logical links.
The Event Database contains all Event Records, acquired either automated from the Monitoring System or manually.
The Knowledge Management System is the central repository of relevant knowledge information of the IT Service Providers. Ideally it is a structured document management system but may also consist of a mixture of IT supported and paper repository. In no case there should exist parallel archiving to the operational databases of the organisation but complement these seamlessly by following information categories:
The Monitoring System tracks the behaviour and the operation of IT Infrastructure Components and IT Infrastructure Services. It may be part of the monitored system or a separate surveillance system.
The Operational Systems contain the whole of IT Systems of the enterprise which provide the functionality for the IT Services.
The Service Desk System contains the database of user support including the knowledge base for Incident- and Problem Management. Normally it is part of the integrated IT Service Management system.
6.2 Responsibility Assignment Matrix for Incident ManagementClick the image for a bigger view in a new window
You want more than
know-how? |
|
![]() |
|
Free access to our ITSM Archive and update to the new release (due to the new ITIL® 4)! |
All customers of the complete package of five ITSM Process Collections will get an everlasting access to our ITSM archive (templates, KPI proposals, checklists) which we are creating during the further development of our ITSM Process Library - thus you receive always the most actual ITSM documents independent of the purchasing date for free! |
Furthermore all customers of our complete package of five ITSM Process
Collections will
get a |
|
Please also visit our other portals for process-oriented management solutions: Process-oriented tools and process collections of quality management according to ISO 9001 ITIL® is registered trademark of AXELOS Limited. |
© 2006 - 2023 Dipl.-Ing. Walter Abel Management Consulting |
Last update 2023-05-24 |
Except as expressly indicated, Digistore24 does not
endorse and is not affiliated with any third party product, service,
statement, or opinion. 2019 © Digistore24 Inc. and/or its licensors. Review legal terms of use [Here] and privacy policy [Here]. Contact us [Here] |