This presentation was provided to Tadawul staffs during my work on ITIL process definition.

1. ITIL and Process Concepts Prepared & Presents by: Abdulaziz Q.S Al-Faify [email_address]

2. Introduction This presentation will focus on ITIL Framework and IT processes. The attendees should get complete ideas and full knowledge regarding Service Management and ITIL processes in IT organization.

4. What is the Process? ITIL Concept A connected series of procedures Performed by agents with the intent of satisfying a purpose or achieving a goal. Role: A set of responsibilities, activities, and authorization. Department A Department B Department C Objectives Results Functions Procedure Procedure START/Input END/Outcome

5. Why Processes in IT? ITIL Concept Situation Undefined processes Poor process Integration Undefined processes Unclear roles & responsibilities Outcome Multiple reworks, false starts, periodic work stoppages Communication breakdowns, duplicate work efforts Unstable service delivery, Poor customer satisfaction Accountability failure, fixing broken processes

6. ITIL Processes and people New Skill Development and Attitude Transition From Users Inward Looking Technology Focus Random Processes Best Efforts Entirely In-House Fragmented, Silos Reactive Operations Manager System Skills To Customer Outward Looking Process Focus Rationalised, Streamlined processes Measured, Accountable Processes Balanced In/Outsource Integrated, End-To-End Proactive Service Manager “ Listening” Skills

8. Improvement of Processes Organization Vision Analysis Goal & Objectives Improvement Plans Measurement & Tracking Where are we now? Where do we want to be? How do we get there? Did we get where we wanted to be? Awareness & Education Planning Implementation Operation

9. Measurement of Process Maturity ITIL Concept –Pink Elephant- If you can not measure it, You can not improve it Description Maturity Level There is absolutely no evidence of activities supporting the processes Absence 0 There are ad-hoc activities present, but we are not aware of how they relate to each other within a single process. e.g. Words but no documented objectives or plans Initiation 1 We are aware of the process but some activities are still incomplete; there is no overall control. e.g. Positions are created, but roles and responsibilities are poorly defined Awareness 2 The process is well defined, understood and implemented. e.g. Targets for quality are set and results are measured Control 3 Inputs from this process comes from well controlled process…etc. e.g. Strong communication between departments working different processes. Integration 4 The process drives quality improvements and new business opportunities beyond the process. e.g. Quality Management and continues improvement are embedded. Optimization 5

10. IT Organization IT Organisations do not trip over the mountains… BUT…

14. ITIL Process, People, and Technology People: Properly aligned, Educated, Supportive Culture Process : Transformation to Create real Value Technology to enable efficient and effective support processes across the enterprise

15. ITIL Model Business Technology Planning to implement Service Management Applications Management Business Perspective ICT Infrastructure Mgmt Service Delivery Security Management Service Support

17. Service Support & Service Delivery Service Delivery Service Support Service Level Management Service Desk (Function) Continuity Management Incident Management Availability Management Problem Management Financial Management Change Management Capacity Management Release Management Configuration Management

18. Service Support Incident Mgmt. Configuration Mgmt . Change Mgmt. Service Desk Problem Mgmt Release Mgmt

19. Service Desk Model The Service Desk is the central point of contact between the customer and the IT area in all matters concerning IT services.

20. Service Desk, Incident, & Problem Management Service Support Incident Management : Restore normal service as quickly as possible. Problem Management : Minimize the adverse affect on the business of Incidents and Problems caused by errors in the infrastructure. Service Desk : The only ITIL function. Central point of contact between Customer/Users and IT Service Management.

21. Service Desk Language A Customer: A User: Person who uses the services on a day-to-day basis Person who commissions, pays for, and owns the IT services

22. Incident Management Restore normal service as quickly as possible with minimal disruption to the business.

23. Incident Life-Cycle Incident Detecting & Recording Ownership, monitoring, tracking, and communication Service Request Procedure Yes Initial Classification & Support Investigation & Diagnosis No Service Request? Resolution & Recovery Incident Closure

24. Incident Management Goal To restore normal service operation as quickly as possible and minimize the adverse impact on users and the organization. Definition An incident is any event which causes, or may cause an interruption to, or a reduction in, the quality of a service.

26. Change Management Ensure that standardized methods are used for efficient and prompt handling of all Changes.

27. Change Management Life-Cycle Logging & filtering Classification Assessment Authorization Coordination Evaluation (PIR) RFC build / test / implement

30. Configuration Management CMDB The identification, control, reporting, relationship management, and verification of IT infrastructure components.

31. Configuration Management activities Configuration Management Database (CMDB) Identification: The selection, unique identification, description, and labeling of configuration items to be contained in the CMDB. Control: Ensure items added are authorized & identifiable, from receipt to disposal. Status Accounting: The reporting of all current and historical data concerned with configuration items. Verification & Audit: Audits to ensure that the CMDB reflects reality.

32. Release Management Plan, design, build, configure, test and deploy a risk-acceptable release consisting of related changes to the IT service infrastructure.

34. Release Management Activities Configuration Management Database (CMDB) Definitive Software Library (DSL) Release Policy Release Planning Design & get SW/HW Build & Configure Release Fit-for-Purpose Testing Release Acceptance Rollout Planning Communi-cation Prep & Training Distribution & Installation

35. Configuration, Release, and Change

36. Service Delivery Open Hrs 9-5 Service Delivery Service Level Mgmt. Financial Mgmt. for IT Services Continuity Mgmt . Capacity Mgmt . Availability Mgmt.

37. Service Level Management SLM Define, agree, monitor, manage, and gradually improve business-aligned IT service quality, at an agreed cost. Review SLAs, OLAs, UCs Review SLM process Create/ update Service Catalog Meet & Identify Service Level Reqs Draft & Negotiate SLA Formalize SLA Monitor SLA & produce reports Plan & implement improve-ments Review underpinning contracts & OLAs

38. Financial Management Budgeting Accounting Charging Provide cost-effective management of the IT assets and of the financial resources used in providing IT services, establish fair means by which to recovery cost

39. Capacity Management Ensure that IT has sufficient resources to meet the requirements of business user community—now and in the future. Business Capacity Management What are the future needs of the business (relies on trends, forecasts, and models PLUS active discussion with the business) Service Capacity Management Monitor, analyze, tune, and report on end-to-end service performance Resource Capacity Management Monitor, analyze, run, and report on utilization of infrastructure components

40. Availability Management Design, implement, monitor, and optimize the availability and recovery of defined IT services. Business Requirements Estimate Availability Availability Plan Measure Effective Availability Implement Improve-ments

41. Continuity Management Support the overall business continuity process by ensuring that required IT functions can be recovered within an agreed time frame . Operational Management Implementation Requirements & Strategy Initiation

42. “ KEY” is Service SLA SLA Name, Date, Parties, Signatures Global Statements: Contacts, Escalation, Penalties, Definitions Parties involved, Roles & responsibilities Specification of Service Levels (Spreadsheet) Quality targets, Maintenance & Support Version Number, Dates, Contents, Signatures SLA Release Management & Service Change procedures Management reporting, Review procedure

43. But SLA has to live S ervice Level Management Service Level Agreement Service Catalogue Operational Level Agreements & Contracts Service Spreadsheet Service Quality Plan Monitor, Review & Report Service Improvement Programs Customer relationship management Service Level Requirements

46. It is not just Technology Technology Tools and infrastructure Process Definition and design, compliance, and continuous improvement People Responsibilities, management, skills development, and discipline

50. Thanks a lot. Abdulaziz Q.S. Al-Faify [email_address]