PelegIT IITL Foundation Guide 4 3

8/2/2019 PelegIT IITL Foundation Guide 4 3

http://slidepdf.com/reader/full/pelegit-iitl-foundation-guide-4-3 1/80

ITIL v3 (2011)ITIL Foundation Study Guide

Lite Version

Revision 4.3 (November 15, 2011)

Written by. Peleg Holzmann, MS, CISSP, ITIL v3 Expert

All rights reserved.

Full version coming in December 2011 – January 2012 to Amazon.com



Peleg Holzmann, MS, CISSP, ITIL v3 Expertwww.pelegit.com All Rights Reserved

1

Table of Contents

ITIL v3 (2011) ....................................................................................................................................................... 0

Table of Contents ................................................................................................................................................ 1

Table of Figures ................................................................................................................................................... 4

Introduction ......................................................................................................................................................... 5

Service Strategy ................................................................................................................................................. 12

Service Design .................................................................................................................................................... 25

Service Transition .............................................................................................................................................. 34

Service Operation .............................................................................................................................................. 45

Continual Service Improvement ........................................................................................................................ 52

Glossary ............................................................................................................................................................. 67

Capability: ...................................................................................................................................................... 67

Resource: ....................................................................................................................................................... 67

Asset: ............................................................................................................................................................. 67

Service Portfolio Management (SPM): .......................................................................................................... 67

Risk Assessment ............................................................................................................................................ 68

Supplier .......................................................................................................................................................... 68

Supplier Service Improvement Plan (SSIP): ................................................................................................... 68

Supplier Survey Reports: ............................................................................................................................... 68

Supplier & Contract Performance Reports: ................................................................................................... 68

(Supplier & Contract Database - SCD) ........................................................................................................... 69

Supplier and Contract Management Information System (SCMIS): .............................................................. 69

Service Level Agreement (SLA): ..................................................................................................................... 69

Operational Level Agreement (OLA): ............................................................................................................ 69

Underpinning Contract (UC): ......................................................................................................................... 69

Availability: .................................................................................................................................................... 70

Service Knowledge Management System (SKMS) ......................................................................................... 70

Definitive Media Library ................................................................................................................................ 70

Standard Change ........................................................................................................................................... 70

Normal Change .............................................................................................................................................. 71




2

Emergency Change ........................................................................................................................................ 71

Configuration Item (CI) .................................................................................................................................. 71

Event .............................................................................................................................................................. 71

Event Management ....................................................................................................................................... 71

Alert ............................................................................................................................................................... 72

Incident .......................................................................................................................................................... 72

Incident Record ............................................................................................................................................. 72

Incident Management ................................................................................................................................... 72

Problem ......................................................................................................................................................... 72

Problem Management: ................................................................................................................................. 73

Workaround: ................................................................................................................................................. 73

Known Error: .................................................................................................................................................. 73

Known Error Database (KEDB) ....................................................................................................................... 73

Service Catalogue: ......................................................................................................................................... 73

Governance: .................................................................................................................................................. 74

Minor Release ................................................................................................................................................ 74

Major Release ................................................................................................................................................ 74

Emergency Release ........................................................................................................................................ 74

Pattern of Business Activity (PBA): ................................................................................................................ 74

User Profile (UP) ............................................................................................................................................ 75

Key Performance Indicator (KPI): .................................................................................................................. 75

Critical Success Factor (CSF): ......................................................................................................................... 75

Information Security Management System (ISMS): ...................................................................................... 75

Mean Time Between Failures (MTBF): .......................................................................................................... 76

Vital Business Function .................................................................................................................................. 76

Business Capacity Management .................................................................................................................... 76

Component Capacity Management............................................................................................................... 76

Business Continuity Management (BCM) ...................................................................................................... 77

Business Impact Analysis (BIA) ...................................................................................................................... 77Risk Assessment ............................................................................................................................................ 77

Change ........................................................................................................................................................... 77

Standard Change ........................................................................................................................................... 77

Normal Change .............................................................................................................................................. 78




3

Emergency Change ........................................................................................................................................ 78

Remediation .................................................................................................................................................. 78

Change Advisory Board (CAB)........................................................................................................................ 78

Emergency Change Advisory Board (ECAB) ................................................................................................... 78

Data ............................................................................................................................................................... 79

Information .................................................................................................................................................... 79

Knowledge ..................................................................................................................................................... 79

Wisdom .......................................................................................................................................................... 79




4

Table of FiguresFigure 1 Example list for organizing a service lifecycle. ...................................................................................... 6

Figure 2- Continual Service Improvement and the Service Lifecycle (Introduction) ........................................... 7

Figure 3 - How customers perceive value (Introduction) .................................................................................... 8Figure 4 - Integration across the Service Lifecycle (Introduction) ....................................................................... 9

Figure 5 - Process Model (Introduction) ............................................................................................................ 10

Figure 6 - Value of a service in terms of return on assets for the customer (Introduction) ............................. 11

Figure 7 - Components of Value (Service Strategy) ........................................................................................... 13

Figure 8 - Example of codified pattern of business activity (PBA) ..................................................................... 14

Figure 9 - User Profile (UP) matched to Pattern of Business Activity (PBA) ...................................................... 14

Figure 10 - Phases of Service Portfolio Management (SPM) (Service Strategy) ............................................... 15

Figure 11 - Service Portfolio and its contents (Service Strategy) ...................................................................... 16

Figure 12 - SPM Process (Service Strategy) ...................................................................................................... 17

Figure 13 - 4 Major steps of SPM (Service Strategy) ......................................................................................... 18Figure 14 - Service Portfolio review of existing services (Service Portfolio) ..................................................... 21

Figure 15 - Capacity Management Sub-Processes (Service Design) .................................................................. 26

Figure 16 - Types of Contracts (Service Design) ................................................................................................ 27

Figure 17 - Multi-Level SLA (Service Design) ..................................................................................................... 28

Figure 18 - Service Design - the Big Picture (Service Design) ............................................................................ 29

Figure 19 - Data in SKMS (Service Transition) ................................................................................................... 35

Figure 20 - Early Life Support Activities (Service Transition) ............................................................................. 36

Figure 21 - Flow from Data to Wisdom (Service Transition) ............................................................................. 38

Figure 22 - Interface between change management and SACM (Service Transition) ...................................... 39

Figure 23 - Phases of release and deployment management (Service Transition) ........................................... 39

Figure 24 - Process for Standard Operational Change Request (Service Transition) ........................................ 39

Figure 25 - Process for Standard Deployment Request (Service Transition) .................................................... 40

Figure 26 - Process of Normal Change (Service Transition) .............................................................................. 41

Figure 27 - Relationship of the CMDB, the CMS and SKMS (Service Transition) ............................................... 42

Figure 28 - The Scope of Service Transition (Service Transition) ...................................................................... 43

Figure 29 - 7 R’s of Change Management (Service Transition) ......................................................................... 44

Figure 30 - Access Management Process Flow (Service Operation) ................................................................. 46

Figure 31 - Event Management Process (Service Operation) ............................................................................ 47

Figure 32 - Incident Management Process (Service Operation)........................................................................ 48

Figure 33 - Problem Management Process Flow (Service Operation) .............................................................. 49

Figure 34 - Request Fulfillment Process (Service Operation) ............................................................................ 50

Figure 35 - CSI Approach (CSI Model) ................................................................................................................ 53

Figure 36 - Deming Cycle ................................................................................................................................... 54

Figure 37 - 7 Step Improvement Process .......................................................................................................... 59




5

Introduction




6

Service Strategy Service Design Service Transition Service OperationContinual Service

Improvement

Budgets

Architectures Changes Incidents Ideas

Customers Standards Releases Problems Experiences

Services OLAs CIs Events Statistics

Assessments Contracts Data Technicians Options

Capabilities Suppliers Information Service/Help Desk Critics

Resources Relationships Knowledge Functions Customer Feedback

Assets Partners Projects Processes Statistics

Opportunities SLAs

Figure 1 Example list for organizing a service lifecycle.




7

Figure 2- Continual Service Improvement and the Service Lifecycle (Introduction)




8

Figure 3 - How customers perceive value (Introduction)




9

Figure 4 - Integration across the Service Lifecycle (Introduction)




10

Figure 5 - Process Model (Introduction)




11

Figure 6 - Value of a service in terms of return on assets for the customer (Introduction)




12

Service Strategy




13

Figure 7 - Components of Value (Service Strategy)




14

Service Usage Code: PBA10

Service Messaging

Activity Level

High …………………………………………………………….. Low

Activity

Remote access of the service X

Bandwidth requirements X

Remote technical support X

Onsite technical support X

Impact by service interruption X

Seasonal variation in service utilization X

Processed transactions X

Secure use via wireless mobile devices X

Figure 8 - Example of codified pattern of business activity (PBA)

User Profile PBA Profile for user PBA service usage codes

Senior Executiives Highly mobile

High service disruption impact

No seasonal variation

Wireless device service access

High remote technical support use

PBA10

Figure 9 - User Profile (UP) matched to Pattern of Business Activity (PBA)




15

Figure 10 - Phases of Service Portfolio Management (SPM) (Service Strategy)




16

Figure 11 - Service Portfolio and its contents (Service Strategy)




17

Figure 12 - SPM Process (Service Strategy)




18

Figure 13 - 4 Major steps of SPM (Service Strategy)

Steps of Service Portfolio Management 4 Major Steps

Define Analyze

ApproveCharter




19

Define

Used to validate portfolio data in terms of: • Potential Benefits • Recourses and Capabilities Required • Enables service provider to define what

it can do • Enables service provider to define what

it cannot do (due to maturity levels,

capabilities, risks, etc.)

Analyze

Maximize portfolio value, align, prioritize and

balance supply and demand. Questions asked

are: • What are the long term goals of the service

organization?

• What services are required to meet these

goals? • What capabilities and resources are

required to deliver and support those

services? • How will we get there?

Approve Finalize proposed portfolio; authorize services

and resources needed to deliver services.




20

Charter

Plans and tracks the progress of service

investments across the portfolio and allocates

required resources. Used to schedule and

manage: • Design of Services •

Transition of Services • Change of Services • Retirement of Services




21

Figure 14 - Service Portfolio review of existing services (Service Portfolio)

Renew

Replace

Retain

Retire

Refactor Often services that meet technical and functional criteria of the

organization display fuzzy processes or system boundaries. In these cases,

the service can be refactored to include only the core functionality, with

common services used to provide the remainder.

Rationalize Used to address portfolios that offer services which in fact are composed

of multiple releases of the same operating system, service or application

etc.

These services meet functional fitness criteria, but fail technical fitness. These services have unclear and overlapping business functionality. Largely self -contained, with well-defined asset, process and system

boundaries. These services are well aligned and relevant to theorganizational strategy.

Retired services do not meet minimum levels of technical and functional

fitness.




22

Venture Transform the

Business (TTB)

Growth Grow the

Business

(GTB) Discretionary

Core Run the

Business (RTB) Non-Discretionary

Transform the Business (TTB) TTB investments are focused on

indicatives to enter new market

spaces with new capabilitiesbeing created.

Grow the Business (GTB) GTB are investments intended to

grow the organizations scope of

services.

Run the Business (RTB) RTB are investments centered on

Service Operations or maintaining

the Status-Quo.

R i s k




23

Service Strategy Activities

Define the Market Understand the relationship between services and strategies, understand the customers,

understand the opportunities and classify and visualize the services.

The development of the offering Create a service portfolio that represents the opportunities and readiness of a service

provider to serve the customer and the market.

The development of strategic assets Define the value network and improve capabilities and resources (service assets) to increase

the service performance and potential.

Preparation for execution Strategic assessment, setting objectives, defining Critical Success Factors (CSF), prioritizing

nvestments, etc.




24

3 Main Types of Service Providers

Type 1: Internal Service Provider …embedded within a business unit. There may be several type 1 service

providers within an organization.

Type 2: Shared Services Unit An internal service provider what provides shared IT services to more than

one business unit.

Type 3: External Services Provider A service provider that provides IT services to external customers.




25

Service Design




26

Figure 15 - Capacity Management Sub-Processes (Service Design)




27

Figure 16 - Types of Contracts (Service Design)




28

Figure 17 - Multi-Level SLA (Service Design)




29

Figure 18 - Service Design - the Big Picture (Service Design)




30

Service Design Package




31

SMART:(ITIL Service Design, SD, Continual Service Improvement, CSI)

An acronym for helping to remember that targets in service level

agreements and project plan should be:




32




33

People Products / Technology Processes

Partners / Suppliers

4 P’s




34

Service Transition




35

Figure 19 - Data in SKMS (Service Transition)




36

Figure 20 - Early Life Support Activities (Service Transition)




37




38

Figure 21 - Flow from Data to Wisdom (Service Transition)




39

Figure 22 - Interface between change management and SACM (Service Transition)

Figure 23 - Phases of release and deployment management (Service Transition)

Figure 24 - Process for Standard Operational Change Request (Service Transition)




40

Figure 25 - Process for Standard Deployment Request (Service Transition)




41

Figure 26 - Process of Normal Change (Service Transition)




42

Figure 27 - Relationship of the CMDB, the CMS and SKMS (Service Transition)




43

Figure 28 - The Scope of Service Transition (Service Transition)




44

Figure 29 - 7 R’s of Change Management (Service Transition)

• Who RAISED the change?1

• What is the REASON for the change?2

• What is the RETURN required from the change?3

• What are the RISKS involved in the change?4

• What RESOURCES are required to deliver the change?

5• Who is RESSPONSIBLE for the build, test and implementation of the change?6

• What is the RELATIONSHIP between this change and other changes?7

7 R’s of Change Management




45

Service Operation




46

Figure 30 - Access Management Process Flow (Service Operation)




47

Figure 31 - Event Management Process (Service Operation)




48

Figure 32 - Incident Management Process (Service Operation)




49

Figure 33 - Problem Management Process Flow (Service Operation)




50

Figure 34 - Request Fulfillment Process (Service Operation)




51

Service Desk Structure

Service Desk Types




52

Continual Service

Improvement




53

Figure 35 - CSI Approach (CSI Model)




54

Figure 36 - Deming Cycle




55

What is the

vision?

This question should be asked by the IT service

provider to understand what the ultimate and long

term aims are.

Business vision,

mission, goals and

objectives




56

Where are

we now?

This is a question every business should start

out asking as this creates a baseline of data for

services currently being delivered.

Baseline

Assessments




57

How do

we get

there? What improvement initiatives are required in

the short, medium and long term? These

initiatives should be logged in the CSI

Register.

Service and Process

Management

CSI Register: A DB or structured document used to record and manage

improvement opportunities throughout their lifecycle. (Not on exam – ITIL

Foundation)




58

Did we get

there?

This is documented through monitoring, reporting and

reviewing of service level achievements and actual

performance against targets identified by the business

requirements.

Measurements

and Metrics




59

Figure 37 - 7 Step Improvement Process




60

1. Identify the strategy for

improvement • Vision •

Business need • Strategy • Tactical Goals • Operational Goals

Identify the overall vision, business need, the strategy and tactical

operational goals.




61

SS and SD should have identified this information early in the lifecycle.

CSI can then start its cycle all over again at “Where are we now?” and

“Where do we want to be?”

This identifies the ideal situation for both the business and IT; CSI can

conduct a gap analysis to identify opportunities for improvements as

well as answering the question “How do we get there?”

2. Define what you

will measure




62

In order to properly answer the question “Did we get there?” data must first

be gathered (usually through SO).

Data can be gathered from many different sources based on goals and

objectives identified. At this point the data is raw and no conclusions are

drawn.

2. Define what you

will measure

3. Gather the data •

Who? How? When?

• Criteria to evaluate integrity of

data • Operational Goals • Service Measurement




63

Here the data is processed in alignment with the critical success factors (CSF’s)

and Key Performance Indicators (KPI’s) specified. This means that timeframes

are coordinated, unaligned data is rationalized and made consistent, and gaps

in the data are identified. The simple goal of this step is to process data from multiple disparate sourcesto give it context that can be compared. Once we have rationalized the data we

can begin analysis.

4. Process the data • Frequency? • Format? • Tools and systems? • Accuracy?




64

As we bring the data more and more into context, it evolves from raw data into

information which we can start to answer questions about who, what, when,

where and how as well as trends and impact on the business.

It is this analyzing step that is most often overlooked or forgotten in the rush to

present data to management.

5. Analyze the information and data • Trends? • Targets? • Improvements Required?




65

Here the answer to “Did we get there?” is formatted and

communicated in whatever way necessary to present to the

various stakeholders an accurate picture of the results of the

improvement efforts. Knowledge is presented to the business in a form and manner that

reflects their needs and assists them in determining the next steps.

5. Analyze the information and data • Trends? • Targets? • Improvements Required?

6. Present and use the information • Assessment summery • Action plans • Etc.




66

The knowledge gained is used to optimize, improve and correct

services and processes. Issues have been identified and now

solutions are implemented – wisdom is applied to the knowledge.

The improvements that need to be taken to improve the service orprocess are communicated and explained to the organization.

Following this step the organization establishes new baselines and

the cycle begins anew.

1. Identify the strategy for

improvement •

Vision

• Business need • Strategy • Tactical Goals • Operational Goals

7. Implement Improvement




67

Glossary

Capability:

(ITIL Service Design, SD)

The ability of an organization, person, process, application, IT service or other CI to carry out an

activity. Capabilities are assets of an organization. Capabilities represent an organizations ability to

coordinate, control and deploy resources to produce value.

Resource:

(ITIL Service Strategy, SS)

A generic term that includes IT infrastructure, people, money or anything else that might help to

deliver an IT service. Resources are considered to be assets of an organization.

Asset:

(ITIL Service Strategy, SS)

Any resource or capability; the assets of a service provider include anything that could contribute

to the delivery of a service. Assets can be one of the following types:

• Management • Applications • Organization • Infrastructure • Process • Financial Capital • Knowledge • People • Information

Service Portfolio Management (SPM):

(ITIL Service Strategy, SS)The process responsible for managing the service portfolio; Service Portfolio Management (SPM)

ensures that the service provider has the right mix of services to meet required business outcomes

at an appropriate level of investment. Service Portfolio Management (SPM) considers services in

terms of the business value that they provide.




68

Risk Assessment


Evaluates Assets, threats and vulnerabilities that exist to business processes, IT services, IT and

infrastructure and other assets.

Supplier:(ITIL Service Strategy, SS & Service Design, SD)

A third party responsible for supplying goods and services that are required to deliver IT services.

Examples of suppliers include commodity hardware and software vendors, network and telecom

prodders, and outsourcing organizations. See also supply chain and underpinning contracts.

Supplier Service Improvement Plan (SSIP):(ITIL Service Design, SD)

Used to record all improvement actions and plans agreed between suppliers and service providers.

Supplier Survey Reports:


Feedback gathered from all individuals that deal directly with suppliers throughout their day to dayroles. Results are collated and reviewed by Supplier Management to ensure consistency in quality

of service provided by suppliers in all areas.

Supplier & Contract Performance Reports:


Used as input for the Supplier Contract review meetings to manage the quality of the service

provided by suppliers and partners. This should include information on shared risk when

appropriate.




69

(Supplier & Contract Database - SCD)

Supplier and Contract Management Information

System (SCMIS):


A set of tools, data and information that is used to support supplier management. See also ServiceKnowledge Management System (SKMS).

Service Level Agreement (SLA):

(ITIL Continual Service Improvement, CSI)

An agreement between an IT service provider and a customer; A SLA describes the IT service,

documents service level targets, and specifies the responsibilities of the IT service provider and

the customer. A single agreement may cover multiple IT services or multiple customers. (OLA)

Operational Level Agreement (OLA):

(ITIL Service Design, SD & ITIL Continual Service Improvement, CSI)

An agreement between an IT service provider and another part of the same organization; It

supports the IT service provider’s delivery of IT services to customers and defines the goods and

services to be provided and the responsibilities of both parties. For example there could be an OLA: • Between the IT service provider and a procurement department to obtain hardware in

agreed time frame • Between the service desk and a support group to provide incident resolution in agreed

times

Underpinning Contract (UC):


A contract between service provider and a third party; the third party provides goods and servicesthat support delivery of an IT service to the customer. The UC defines targets and responsibilities

that are required to meet agreed service level targets in one or more SLA’s.




70

Availability:


Ability of an IT service to other configuration item to perform its agreed function when required.

Availability is determined by reliability, maintainability, serviceability, performance and security.

Service Knowledge Management System (SKMS)

(ITIL Service Transition, ST)

A set of tools and databases that is used to manage knowledge, information and data; The SKMS

includes the CMS as well as other DB and information systems. The SKMS includes tools for

collecting, storing, managing, updating, analyzing and presenting all the knowledge, information

and data that a service provider will need to manage the full lifecycle of IT services.

Definitive Media Library


One or more locations in which the definitive and authorized versions of all software configuration

items are securely stored. The definitive media library may also contain associated configuration

items such as licenses and documentation. It is a single logical storage area even if there are

multiple physical storage locations. The DML is controlled by services asset and configuration

management and is recorded in the CMS.

Standard Change


A pre-authorized change that is LOW risk, relatively common and follows a procedure or work

instruction – for example a password reset or provision of standard equipment to a new employee.

Requests for Change (RFC) are not required to implement a standard change, and are logged and

tracked using a different mechanism, such as a service request.

Availability (%) = Agreed Service Time (AST) - Downtime

Agreed Service Time (AST)

Downtime is defined as the service being unavailable only during Agreed Service Time (AST)




71

Normal Change


A change that is not an emergency change or standard change. Normal changes follow defined

steps of the change management process.

Emergency Change


A change that must be introduced as soon as possible – for example, to resolve a major incident or

implement a security patch. The change management process will normally have a specific

procedure for handling emergency changes.

Configuration Item (CI)(ITIL Service Transition, ST)

Any component or other service asset that needs to be managed in order to deliver an IT service.

Information about each CI is recorded in a configuration record within the Configuration

Management System (CMS) and is maintained throughout its lifecycle by Service Asset and

Configuration Management (SACM).

Event(ITIL Service Operation, SO)

A change in the state that has significance for the management of an IT service or other

configuration item (CI). The term is also used to mean an alert or notification created by any IT

service, configuration Item (CI) or monitoring tool. Events typically require operations personnel to

take action, and often lead to incidents being logged.

Event Management

(ITIL Service Operation, SO)

The process responsible for managing events throughout their lifecycle. Even Management is one of

the main activities of IT operations.




72

Alert


A notification that a threshold has been reached, something has changed, or a failure has

occurred. Alerts are often created and managed by system management tools and are managed by

the event management process.

Incident


An unplanned interruption to an IT service or reduction in quality of an IT service. Failure of a CI

that has NOT yet affected service is also an incident – for example failure of a disk to mirror.

Incident Record (ITIL Service Operation, SO)

A record containing the details of an incident. Each incident record documents the lifecycle of a

single incident.

Incident Management


The process responsible for managing the lifecycle of all incidents. Incident management ensures

that normal service operation is restored as quickly as possible and the business impact is

minimized.

Problem


A cause of one or more incidents. The cause is not usually known at the time the problem record is

created, and the problem management process is responsible for further investigation.




73

Problem Management:


The process responsible for managing the lifecycle of all problems. Problem management

proactively prevents incidents from happening and minimizes the impact of incidents that cannot

be prevented.

Workaround:


Reducing or eliminating the impact of an incident or problem for which a full resolution is not yet

available – for example by restarting a failed CI. Workarounds for problems are documented in

known error records. Workarounds for incidents that do not have associated problem records are

documented in incident records.

Known Error:


A problem that has a documented root cause and a workaround. Known errors are created and

managed throughout their lifecycle by problem management. Known errors may also be identified

by development and suppliers.

Known Error Database (KEDB)


A database containing the details of a known error. Each known error record documents the

lifecycle of a known error, including the status, root cause and workaround. In some

implementations, a known error is documented using additional fields in a problem record.

Service Catalogue:


A written statement of available IT services, default levels, options, prices and identification of

which business processes or customers use them.




74

Governance:

Ensures that policies and strategy are actually implemented, and that required processes are

correctly followed. Governance includes defining roles and responsibilities, measuring and

reporting, and taking actions to resolve any issues identified.

Minor Release


Normally contain small enhancements and fixes, some of which may already have been issued as

emergency fixes.

A minor upgrade or release usually supersedes all preceding emergency fixes.

Major Release


Normally contain large areas of new functionality some of which may eliminate e temporary fixes to

problems.

A major upgrade or release usually supersedes all preceding minor upgrades, release and

emergency fixes.

Emergency Release(ITIL Service Transition, ST)

Normally contain corrections to a small number of know errors, or sometimes an enhancement to

meet a high priority business requirement.

Pattern of Business Activity (PBA):

(ITIL Service Strategy)

A workload profile of one or more business activities; Patterns of business activity are used to help

the IT service provider understand and plan for different levels of business activity. See also user

profile




75

User Profile (UP)

(ITIL Service Strategy)

A pattern of user demand for IT services. Each user profile includes one or more patterns of

business activity (PBA’s).

Key Performance Indicator (KPI):

(ITIL Service Design, SD & ITIL Continual Service Improvement (CSI))

A metric that is used to help manage an IT service, process, plan, project or other activity. Key

performance indicators are used to measure the achievement of critical success factors (CSF) many

metrics may be measured, but only the most important of these are defined as key performance

indicators and used to actively manage and report on the process, IT service or activity. They should

be selected to ensure that efficiency; effectiveness and cost effectiveness are all managed.

Critical Success Factor (CSF):

Something that must happen if an IT service, process, plan, project or other activity is to succeed.

Key performance indicators (KPI) are used to measure the achievement of each critical success

factor.

For example, a critical success of “protect IT services when making changes” could be measured by

key performance indicators (KPI) such as “percentage reduction of unsuccessful changes”,

“percentage reduction in changes causing incidents” etc.

Information Security Management System

(ISMS):


The framework of policy, processes, functions, standards, guidelines and tools that ensures an

organization can achieve its information security management objectives.




76

Mean Time Between Failures (MTBF):


A metric for measuring and reporting reliability. MTBF is the average time that an IT service or

other configuration item can perform its agreed function without interruption.

Vital Business Function


The business critical elements of the business process supported by an IT service. Typically this will

be where more effort and investments will be spent to protect these vital business functions.

Business Capacity Management

• Manages capacity to meet future business requirements for IT services • Identifies changes occurring in the business to assess how they might impact capacity and

performance of IT services.

• Plans and implements sufficient capacity in an appropriate timescale • Should be included in Change Management and Project Management activates.

Service Capacity Management • Focuses on managing ongoing service performance as detailed in the Service Level

Agreements (SLA) • Establishes baselines and profiles for use of Services, including all components and sub-

services that affect the user experience.

Component Capacity Management

• Identifies and manages each of the individual components of the IT infrastructure (CPU,

Memory, Disks, Network Bandwidth, and Server Load etc.) • Evaluates NEW technology and how it might be leveraged • Balances loads across resources for optimal performance of services.




77

Business Continuity Management (BCM)


Strategies and actions to take place to continue Business Processes in the case of a disaster.

Business Impact Analysis (BIA)


Quantifies the impact of loss of IT services would have on the business.

Risk Assessment


Evaluates Assets, threats and vulnerabilities that exist to business processes, IT services, IT and

infrastructure and other assets.

Change


The addition, modification or removal of anything that could have an effect on IT services. The

scope should include changes to architectures, processes, tools, metrics and documentation, as

well as changes to IT services and other CI’s

Standard Change


A pre-authorized change that is LOW risk, relatively common and follows a procedure or work

instruction – for example a password reset or provision of standard equipment to a new employee.

Requests for Change (RFC) are not required to implement a standard change, and are logged and

tracked using a different mechanism, such as a service request.




78

Normal Change


A change that is not an emergency change or standard change. Normal changes follow defined

steps of the change management process.

Emergency Change(ITIL Service Transition, ST)

A change that must be introduced as soon as possible – for example, to resolve a major incident or

implement a security patch. The change management process will normally have a specific

procedure for handling emergency changes.

Remediation

Actions taken to recover after a failed change or release. Remediation may include back-out,

invocation or service continuity plans, or other actions designed to enable the business process to

continue.

Change Advisory Board (CAB)


A group of people that support the assessment, prioritization, authorization and scheduling or

changes. A change advisory board is usually made up of representatives from: all areas within the IT

service provider; the business; and third parties such as suppliers.

Emergency Change Advisory Board (ECAB)


A subgroup of the change advisory board that makes decisions about emergency changes.

Membership may be decided at the time a meeting is called, and depends on the nature of the

emergency change.



Data

Data is a set of discreet facts. Most organizations capture significant amounts of data every day.

Information

Information comes from providing context to the data. This usually requires capturing varioussources of data and applying some meaning or relevance to the set of facts.

Knowledge

Knowledge is composed of the experiences, ideas, insights and judgments from individuals. This

usually requires the analysis of information, and is applied in such a way to facilitate decision

making.

Wisdom

Wisdom gives the ultimate discernment of the material and having the application and contextual

awareness to provide a strong sense of judgment. The use of wisdom ultimately enables an

organization to direct its strategy and growth in competitive market spaces.

Date post:	05-Apr-2018
Category:	Documents
Upload:	shenbaga-gurunathan
View:	216 times
Download:	0 times

PelegIT IITL Foundation Guide 4 3

Documents