1) Side by side comparisons of the history that made tmforum and ITIL
2) tmforum main Points and Summary
3) ITIL Summary main Points and Summary
1-Historical comparison:
Year
|
tmForum vs ITIL Update
|
Main Category
|
tmforum vs ITIL Details
|
What is
|
tmforum
|
tmforum: TeleManagement Forum
|
|
ITIL
|
ITIL: IT infrastructure Libraby
|
||
1980s
|
ITIL
|
How UK Government Central Computer and CCTA establishes
the IT Infrastructure LIbrary
|
Responding to growing dependence on IT, the UK Government's
Central Computer and Telecommunications Agency (CCTA) in the 1980s
developed a set of recommendations. It recognized that, without standard
practices, government agencies and private sector contracts had started
independently creating their own IT management practices.
The IT Infrastructure Library originated as a collection of books, each covering a specific practice within IT service management. ITIL was built around a process model-based view of controlling and managing operations often credited to W. Edwards Deming and his plan-do-check-act (PDCA) cycle. |
1988
|
tmforum
|
OSI/Network Management Forum Founded
|
Founded as OSI/Network Management Forum
OSI/Network Management Forum The OSI/Network Management Forum was founded in 1988 by eight companies to collaboratively solve systems and operational management issues with the OSI protocols. In 1998 the name was changed to the TeleManagement Forum. |
1989
|
ITIL
|
Library enrichment
|
After the initial publication in 1989–96, the number of books
quickly grew within ITIL v1 to more than 30 volumes.
|
2000
|
ITIL
|
ITIL V2 with Service Management Sets
|
2000-2001 ITIL v2
consolidated the publications into nine logical "sets" that grouped
related process-guidelines to match different aspects of IT management,
applications and services.
The Service Management sets (Service Support and Service Delivery) were by far the most widely used, circulated, and understood of the ITIL v2 publications |
2001
|
ITIL
|
CCTA Merge into the OGC
|
the CCTA was merged into the OGC, an office of the UK
Treasury
|
2004
|
ITIL
|
IPsphere Creation
|
IPshpere created
A group called the Infranet Initiative Council was created by Juniper Networks in April 2004. The group said it was concerned with quality, reliability and security interfaces between telecommunications service providers that were providing services for the Internet. Pradeep Sindhu used the term "infranet" to compare the public Internet to more traditional physical infrastructure. Juniper was joined by British Telecom, China Unicom, Ericsson, France Télécom, Hewlett-Packard, KT Corporation, Siemens, Telenor, and Tellabs. |
2005
|
ITIL
|
IPsphere Forum
|
The IPsphere Forum was founded in June 2005 at the Supercomm
2005 trade show in Chicago with those members. Cisco Systems and Alcatel were
added when it adopted the IPsphere name.
|
2006
|
ITIL
|
ITIL v2 glossary
|
the ITIL v2 glossary was published
|
2007
|
tmforum
|
Nippon Telegraph and Telephone Liaison
|
Nippon Telegraph and Telephone (NTT) joined in 2007, and it established a liaison with the
Tele-Management Forum later that year.
IPsphere was mentioned by executives in a trade show during 2007 |
2007
|
tmforum
|
TM Forum holds
"Content Encounters"
|
2007-2009 TM Forum held marketing events called "Content
Encounters" at the Management World trade shows.
TM Forum's work includes Frameworx, Business Process Framework (eTOM), Frameworx Shared Information/Data Model (SID) and Telecom Application Map (TAM). The Object Management Group endorsed some of the TM Forum's specifications in a telecommunications special interest group by 2004. |
2007
|
ITIL
|
ITIL v3
|
In May 2007, this organization issued version 3 of ITIL (also
known as the ITIL Refresh Project) consisting of 26 processes and functions,
now grouped into only 5 volumes, arranged around the concept of Service
lifecycle structure. Version 3 is now known as ITIL 2007 Edition.
|
2008
|
tmforum
|
TMFORM merbges with IPsphere
|
September 2008 IPsphere Forum merged with the TM Forum.
|
2009
|
tmforum
|
TMFORUM Joins Cloud Standards Coordination Working Group
|
As the term "cloud computing" became popular,
in 2009 TM Forum joined a group called the Cloud Standards Coordination
Working Group.
|
2009
|
ITIL
|
ITIL V2 Withdrawn
|
the OGC officially announced that ITIL v2 certification would be
withdrawn and launched a major consultation as per how to proceed
|
2010
|
tmforum
|
Frameworx official introduction
|
Frameworx offically introduced. as
integrated business architecture blueprint for service providers in
the communications and digital services market.
With the aim of expanding and integrating forms existing NGOSS standards, the business process, the information and the application framework into full integrated IT and Process Architecture. Also embraced major IT standards, ITIL, and TOGAFF. (Business and Information have been changed the last couple of years) |
2011
|
ITIL
|
ITIL V3 2011 Edition
|
2011 edition of ITIL was published, providing an update to the
version published in 2007.
|
2011
|
ITIL
|
OGC not owner anymore
|
The OGC is no longer listed as the owner of ITIL, following the
consolidation of OGC into the Cabinet Office.
|
2012
|
tmforum
|
TMFORUM Exceeds 900 Companies
|
The Forum had over 900 member companies in
different countries
|
2013
|
tmforum
|
Business Process and Information Framework Changes
|
Since 13.0 there is series of changes to the business process
and the information framework.
Represented as a diagram , Business process, Information , application and integration. Together forming service based integrated Business Architecture |
2013
|
ITIL
|
ITIL Owned by AXELOS
|
Since July 2013, ITIL has been owned by AXELOS, a joint venture
between Capita and the Cabinet Office. AXELOS licenses organisations to use
the ITIL intellectual property, accredits licensed examination institutes,
and manages updates to the framework.
|
2014
|
ITIL
|
Axelos owner of ITIL Certification Scheme
|
Since 2014, Axelos is the owner of the ITIL personnel
certification scheme
|
2015
|
tmforum
|
TMFORUM SIngle releases Document for SID, ETOM and TAM
|
15.0 continued alignment of the Frameworx resulting in single
release notes document for the information Frameworx , business process
framework and the application framework showing how they are being managed in
synchronized fashion
|
2- tmforum main Points and Summary
Activity
|
tmforum
|
In a Nutshell
|
Started as NGOSS to new generation OSS through the Solution
Frameworks to framework as we know it today
TM Forum Frameworx is a suite of best practices and standards that provides the blueprint for effective, efficient business operations. It enables you to assess and optimize performance using a proven, service-oriented approach to operations and integration. The practical tools available in Frameworx help improve end-to-end management of services across complex, multi-partner environments. Frameworx has been widely adopted and proven to significantly improve agility in IT and operations, resulting in increased margins, lower costs, and optimal customer experience. Frameworx is created and evolved by TM Forum members who participate in the Forum’s Collaboration Community. |
The Collaboration Program
|
The Collaboration Program is a virtual Research and
Development Consortium made up of TM Forum members from a growing array
of industries.
Goals and objectives are set by the TM Forum Board of Directors Results are Best Practices and Standards, like Frameworx, that our members use to improve their profitability. Most projects operate in time frame of 6 months |
The 3 strategic programs
|
The strategic program strengthen the tmforum strategic
proposition, to lower costs reduce risks, and improve time to market by
solving challenges that are common through the digital service provider
communities.
The programs are: 1- Agile and Virtulized 2- Open & Partner Effectively 3- Customer Centric |
V 13.5 update
|
|
1)
New ITIL Process flows in the Business Process
Framework to make it easier for ITIL users to adopt to the Business process
frameworks and ITIL
|
|
2) 3 new Rest APIs provide management functionality for
--> trouble ticketing ordering and --> catalogue management |
|
3) A view of the Business Process Framework for Digital Health,
the language used to describe and define 390 processes
|
|
4) New definitions in the information Framework that enable
modeling of evolving cloud computing models like SDN, and NFV
|
|
5) 400 new definitions in the Application Framework for discrete
functionality found in common applications
|
|
6) Substantial enhancements to Standardized interfaces
for
GPON (Gigabit Passive Optical Networks) , MPLS-TP, MTOSI (Multi-Technology Operations Systems Interface) and OSS thru Java |
|
V14 Update
|
|
1)
2 new REST APIs enable integrating capabilities for performance and service
level agreement management
|
|
2)
A new decomposition for the Application Framework defines 1000 functions to create
and more Agile environment of mapping digital services to functional
capabilities
|
|
3)
Preliminary draft of the concept of Engaged Party
in the Frameworx 14 suite outlines an example transition from Supplier /
Partner to Engaged Party which is intended to improve the management
of different types of roles in complex value chains
|
|
V14.5 Update
|
|
1)
Phase II of the Functional Model of the Application Framework was
completed, adding substantially to the number of functions available
|
|
2)
Updates to the information Framework includes a new set of test ABEs in the
common, Product, Service and Resource domains.
The final iteration of the Metric Model, new updates to the SIP validator and guidebooks for models |
|
3)
Introduction to the Digital Services Reference Architecture (DSRA): Best
practice for specifying REST based management APIs understanding
the common patterns across the ODEs (The open Digital Ecosystems APIs) Open
Digital APIs for customer managements , Party Management, SLA Managements and
more
|
|
4)
Domains added to the Business Process Framework to
increase its alignment to other frameworks making it easier for its members
to see the cross frameworks associations ,
--> new decomposition rules were added increasing the consistency of the framework and --> forth process were added in concert with the management project to expand the areas covered by the business process framework |
|
V15 Update
|
|
1)
Single Release notes document for the information framework, Business
Process Framework and Application Framework, showing how they are managed in
synchronized fashion
|
|
2)
as digital business evolved; The supplier/Partner concept
in the information Framework has now been evolved to the 'engaged party'.
This reflect the wide range of partnerships and relationships that are
needed. This will enable Frameworx to be applicable to wider range of
business models within the digital eco system
|
|
3) Taking the Application Framework to the next level of
granularity enabling common functionality to be more rapidly and accurately
identified
--> further simplification of the application procurement --> Maximum reuse and consistencies |
|
4) New assets from the privacy and security , and
customer experience management programs are now being aligned with the core
frameworks
--> Key assets from security and customer management programs are being incorporated allowing them to be more easily used by their members |
ITIL, main Points and Summary:
Activity
|
ITIL
|
In a Nutshell
|
ITIL, formerly an acronym for Information Technology
Infrastructure Library, is a set of practices for IT service management
(ITSM) that focuses on aligning IT services with the needs of business. In
its current form (known as ITIL V3), ITIL is published as a series of five
core volumes, each of which covers a different ITSM lifecycle stage. Although
ITIL underpins ISO/IEC 20000 (previously BS 15000), the International Service
Management Standard for IT service management, there are some differences
between the ISO 20000 standard and the ITIL framework.
ITIL describes processes, procedures, tasks, and checklists which are not organization-specific, but can be applied by an organization for establishing integration with the organization's strategy, delivering value, and maintaining a minimum level of competency. It allows the organization to establish a baseline from which it can plan, implement, and measure. It is used to demonstrate compliance and to measure improvement. |
itSMF-
|
itSMF-IT Service Management Forum
|
itsSMF is the only truley independent and internationally
recognised forum for IT Service Manageement Professionals worldwide.
|
|
not-for-profit organization is prominent player in the on-going
developement and promotion of IT Service Management "Best
Practice", standards and qualifications has been since 1991, when the UK
Chapter started as the foundation Chapter
|
|
IGSM now over 6000 member companies, blue chip and public sector
alike, covering excess of 40,000 individuals spread over 50+ Chapters.
|
|
itSMF concerned about promoting ITIL best practices in the IT
service management area.
|
|
AXELOS
|
A join venture between the UK government and Capita, has taken
over the management of ITIL.
Capita PLC is international business process outsourcing and professional services company headquartered in Londaon. |
Service in ITIL terminology
|
Service is a means of delivering value to customer by
facilitating outcomes that customers want to achive without the ownership of
specific costs and risks
|
ITIL Presents Service Managent as a series of phases each
of which represents a stage in the Service Management Life Cylce
|
|
The 5 ITIL Life Cycle phases
|
|
1. Service Strategy
|
|
The heart of the life cycle and service as guidance to the next
3 phases
|
|
2. Service Design
|
|
3. Service Transition
|
|
4. Serivce Operation
|
|
5. Continual Service Improvement
|
|
Stands for learning and improving and it embraces all of the
other life cycle phases.
|
|
This phase initiate service improvement and projects and
prioritizes them on strategic objectives of the organization.
|
|
Process of the 5 phases
|
1-Service Strategy, 5 processes
|
Key Activities:
|
|
--> Defining the market
|
|
--> Developement of the offer
|
|
--> Preparation for execution
|
|
1. Strategy Management for IT Services.
|
|
The objective of this process is to asses the service provider
offering, capabilities, competitors, as well as current and potential market
spaces in order to develop strategy to serve
customers
|
|
Once a strategy has been defined, strategy Management for IT
services is also responsible for the implementation of that strategy.
|
|
2. Service Portofolio Management
|
|
Objective is to manage the service portofolio,
|
|
Ensures the service provider has the right mix of services to
meet required business outcomes at an appropriate level of investment
|
|
3. Financial Management for IT Services
|
|
Objectives is to manage the service provider budgeting,
accounting, charging requirement
|
|
4. Demand Management
|
|
Objective is to understand, anticipate and influence customer
demand for services.
|
|
Demand Management works for capacity management to ensure
service provider has sufficient capacity to meet required demands.
|
|
5. Business Relation Management
|
|
Objective is to maintain positive relationship with customer,
|
|
identifies the need of existing and potential customers and
ensures that appropriate services are developed to meet those needs
|
|
2-Service Design, 11
processes
|
|
Key Activities:
|
|
--> Developement of requirements
|
|
--> Data & Information management
|
|
--> Application Management
|
|
The most important objective is to the design of new or changed
services for introduction into a production enviornment
|
|
1. Design Coordination
|
|
Objective to coordinate all design service activities ,
processes and resources
|
|
Ensures consistent and effective design of new or changed IT
Services, service management information system, architecture, technology,
processes, information and metrics
|
|
2. Service Catalog management
|
|
Objectives to ensure that a service catalog is produced and
maintained
|
|
Contains all operational services and those being prepared to run operationally.
|
|
Provides vital information for other service management
processes, Service Details, current status and services interdependencies
|
|
3. Service Level Management
|
|
Objective is to negotiate level service agreement with a
customer and to design services with agreed level service target.
|
|
Ensures all operational level agreement and underpinning
contracts are appropriate and to monitor and report on service levels
|
|
4. Risk Managements
|
|
Objective to identify, assess and control risks .
|
|
This includes analyzes of value of assets of the business. identify
threat to thoses assets, and evaluating how vulenerable each asset is to
those threats.
|
|
5. Capacity Managments
|
|
Objectives is to ensure capacity of IT services and IT
infrastructure are able to deliver the agreed service level targets in cost effective
and timely manner.
|
|
Considers all resources required to deliver the IT service and
plan for short, medium and long business requirements.
|
|
6. Availability Managment
|
|
Objective is to define, analyze, plan, meausre all aspects of
the availabilities of IT Services.
|
|
Responsible for ensuring that all IT infrastructure, processes,
tool and rule are appropriate for the agreed availability targets.
|
|
7. IT Continuity Management
|
|
Objectives to manage risks that could impact IT services.
|
|
Ensure that IT service provider can always provide minimum
agreed service level by reducing risk from disaster events to acceptable
levels, and plan the recovery of IT services.
|
|
IT SCM shuold be designed to support iT Continuity management
|
|
8. Information Security Management
|
|
Objective to ensure confidentiality, integrity and availability
of the organization information data and IT services.
|
|
Forms part of the organization security managment which has
wider scope.
|
|
9. Compliance Management
|
|
Objective is to ensure IT Services, processes and systems, omply
with entrprise policies and legal requirements
|
|
10. Architectural Management
|
|
Objective is to define blue print of the Technological landscape
taking into consideration Business Strategy and newly available technologies.
|
|
11. Supplier Management.
|
|
Objective is to ensure all contracts with suppliers support the
need of the business and that all suppliers meet their contractural
comitments.
|
|
3-Service Transition 8
processes
|
|
Key Activities:
|
|
--> Communication
|
|
--> Organizational change management
|
|
--> Stakeholder management
|
|
Servie Transition ensures that new or changed servies are better
aligned with customer business operation
|
|
1. Change Management
|
|
Objective is to control life cycle of all changes.
|
|
Most imporantly objective is to enable beneficial changes
with minimum disruption of IT Services
|
|
2. Change evaluation
|
|
Objetive is to assess mediate
changes like introduction to new service or substantial change to
existing service before these changes are allowed to proceed to the next
phase of the life cycle
|
|
3. Project Management
|
|
Objective to plan and coordicate resources to deploy major
release within the predictive costs, time and quality estimate.
|
|
4. Application Developement
|
|
Objective to make available application and systmes which
provide reuired functionality of IT
Services.
|
|
This process includes developemnt and maintenance of customer
applications as well as customization of products from software vendors.
|
|
5. Release and Deploy managements
|
|
Objective to plan, schedule and control the movements of the
releases to test in live environment.
|
|
Ensures the integrity of the life environment is protected and
that the correct components are released
|
|
6. Service Validation and testing
|
|
Objectives to ensure that the deploy releases and resulting
services meet customer expectations and to verify the IT operations is able
to support the new services.
|
|
7. Service Asset and configuration managements
|
|
Objectives is to maintain information about configuration items
requied to deliver IT Service including the relationships.
|
|
8. Knowledge managements
|
|
Objective to analyze and share knowledge of information within
an organization.
|
|
The primary purpose is to improve efficiency to reduce the need
to rediscover knowledge.
|
|
4-Service Operation 9 processes
|
|
Key Activities:
|
|
--> Monitoring & Control
|
|
--> IT Operations
|
|
--> Matching Technology to service goals
|
|
--> Facilities & data centre management
|
|
Service operation ensure that the day to day operations are
properly conducted controlled & managed
|
|
1. Events mangements
|
|
Responsible for managing events through their life cycle. it is
one of the main activies ot the IT Operations
|
|
Objectives to make sure the configuration items and services
are constantly monitored and to filter and categorize events in order to
decide the appropriate action.
|
|
2. Incidence management
|
|
Objectives, to manage life cycle of all incidence
|
|
Primary objective is to return IT services to user asap
|
|
3. Request fullfilments
|
|
Responsible for managing the life cylce of all service requests
|
|
Objectives, to fulfill service requests which in most
cases are minor (change a password or request for information)
|
|
4. Access Management
|
|
Objectives to grant authorized users right to use the service
while prventing access to unauthorized users.
|
|
Executes policies defined in the infromation security
management.
|
|
Refred to as Right Management or Identify Management
|
|
5. Problem Management
|
|
Manage the life cycle of all problems.
|
|
Primary objective is to prevents incidence from happening and to
minimize the impact of incidence that can not be prevented.
|
|
Proactive problem management analyzes incidence records and uses
records collected by other IT service management processes to identify
trends, or significants problems.
|
|
6. IT operation Control
|
|
Objective to monitor and control IT Services and their
underlying infrastructure,
|
|
Execute day to day routine tasks related to the operation of
the infrastcuture components and
applications includes job scheduling, backup, restor activities, trend and
output management and routine maintenance.
|
|
7. Facility Management
|
|
Objective to manage physical environment where IT intra is
located.
|
|
Includes all aspects of managing the physical environment;
power, cooling, bulding access management, and environmental monitoring.
|
|
8. Application Management
|
|
Responsible for managing application throught the life cycle
|
|
9. Technical Management
|
|
Provides technical expertise and support for the management of
the IT intrastructure,
|
|
5-Continual Service Improvement 4 processes
|
|
CSI measures & Monitors
|
|
--> Process compliance
|
|
--> Quality
|
|
--> Performance
|
|
--> Business Value of a process
|
|
1. service review
|
|
to review business services and infra services on regular basis.
|
|
aim is to improve business quality when necessary and to
provide economical ways to provide
servie where possible
|
|
2. Process evaluation
|
|
to evaluate processes on regular basis, includes
identifying areas where targeted
process metrics are reached and hold regular bench marks, audit, maturity
assessments and reviews.
|
|
3. Definition of CSi initiatives
|
|
Define specific initiatives in improving services and processes
based on results of service reviews and process evaluation.
|
|
The resulting initiatives are either internal initiatives
persued by service provider on his own behalf or initiative which requires
the customer cooperation.
|
|
4. Monitoring of the CSi initiatives
|
|
to verify if the improvement initiatives are moving according
to plan and to introduce corrective measures where necessary.
|
#SolutionsArchitect
#tmforum
#ITIL
1 comment:
Nice blog, If you are not ITIL qualified in any way, then
ITIL Certification in Pune will provide you ITIL course
Post a Comment