2. page 2
July 26, 2025
Agenda
• Evolución y madurez
• Disponibilidades
• Mediciones
• ¿Qué es ITIL?
• Modelo de referencia
• Metodología
3. page 3
July 26, 2025
evolución
evolución
Administración de redes
IT SERVICE MANAGEMENT
Elementos, tareas, servicios
Administración de sistemas
Administración Ctros C
Elementos, tareas
Experiencia total
del cliente
Soporte a los procesos de negocio
ITM Orgánico
Infraestructura federada
4. page 4
July 26, 2025
• Ahorro en costos es
estratégico – siempre
• Servicio & soporte, es el
mayor gasto para los
CIOs
• 80% de tiempo caido no
planeado es causado
por operaciones o
aplicaciones mal
administradas
servicio & soporte
mayor costo
para los CIOs
LAN
2%
Hardware
15%
Software
6%
Servicios
& Soporte
77%
Fuente: GartnerGroup
5. page 5
July 26, 2025 Gartner Group, 1998
Causas de paros no planeados
7. page 7
July 26, 2025
El valor correcto, entregado al cliente
correcto y en el tiempo correcto reduce los
costos. Pero, los niveles de servicio no es
algo sexy, es mas sobre compromiso. Los
niveles de servicio no es sobre una
revolución, sino sobre una evolución.
8. page 8
July 26, 2025
Disponibilidad punta a punta
= 91.96%
= 89.89%
9. page 9
July 26, 2025
Fijación de expectativas
Fijación de expectativas
50% 90% 93% 96% 99% 99.9%
Availability
Cost
Realidad actual
Garantía
Meta
Necesidad
Deseado
Disponibilidad
Costo
10. page 10
July 26, 2025
Resolución de problemas punta-a-punta
Redes
Sistemas Bases de datos
Aplicaciones
Help Desk
Correlación Visual
Tiempo de respuesta
11. page 11
July 26, 2025
Qué debe ser medido?
Procesos de negocio
Entrada de órdenes
Canal Web
Canales no Web
Métricas de negocio
Métricas servicio IT
• Disponibilidad: Tiempo operando
Porcentaje disponibilidad
Bajas, minutos, razones, impacto
• Rendimiento: Tiempo respuesta
transacciones abortadas
% tiempo de Batch jobs
• Capacidad & Volúmenes
Requerimientos integración aplicaciones
• Ingresos por canal (web, non-web)
• Costos por canal
• Productividad por empleado
• Satisfacción de clientes
• Tiempos de entrega de órdenes
12. page 12
July 26, 2025
¿Es este su mundo?
“Línea de Negocio”
“Operaciones de TI”
Dirección de TI
“No están cubriendo mis
necesidades!”
“Mis servidores están
corriendo en cinco 9’s —
¿cuál es el problema?”
16. page 16
July 26, 2025
Sin una visión clara,
Sin una visión clara,
se hace difícil
se hace difícil
determinar...
determinar...
• El estado actual de TI con
respecto a la Administración de
Servicios de TI (el “As-Is”)
• El estado futuro de TI (el “To-
Be”)
• La brecha entre el “As-Is” y el
“To-Be”
• Los pasos necesarios para
cubrir las brechas y lograr los
resultados deseados
Modelo de
Referencia de
ITSM
17. page 17
July 26, 2025
Propósito del Modelo de Referencia de HP
ITSM
• Define las áreas de enfoque, procesos de TI, y las
interrelaciones requeridas para administrar el ciclo de vida de
los servicios de TI
• Permite definir los mapas de procesos de TI
– Organización y gente para la ejecución y control
– Administración de Tecnología para la automatización,
estandarización, simplificación, integración, modularidad, y
consistencia
• Permite el “benchmarking” y la mejora continua de TI
• Sobre la base de IT Infrastructure Library (ITIL), tendencias de
industria, y mejores prácticas de HP
20. page 20
July 26, 2025
Flujo de Actividad de Procesos
Security Management
Service Build & Test
Release To Production
Operations Management
IT Business Assessment
Service Level Management
Continuity Management
Availability Management
Capacity Management
Financial Management
Problem Management
Incident & Service
Request Management
Change Management
Configuration
Management
IT Strategy & Architecture Planning
Customer Management
Service Planning
FASE I
21. page 21
July 26, 2025
Propuesta de valor: calidad de los servicios,
satisfacción del cliente, alineación al
negocio
unidades
de
negocio
productos
&
servicios
administración servicios TI
infrastructura
Continuidad de negocio
servicios ti
servicios ti
configuration
m.
incident
m.
problem
m.
change
m.
service
level
m.
aplicacione
s
server
s
router
s
documento
s
et
c.
22. page 22
July 26, 2025
Niveles de Diseño
• NIVEL 1
Modelo de Referencia ITSM
• NIVEL 2 (Diseño lógico) ( 1)
Flujo de Procesos R-B / Diagramas RACI
• NIVEL 3 (Diseño físico) (1.1)
Tareas / Actividades / Nombres de
Procedimientos
• NIVEL 4 (1.1.1)
Instrucciones de trabajo
23. page 23
July 26, 2025
Resumen de diseño lógico
Definiciones del proceso
Definir estrategia de implantación
Definir los equipos de trabajo para la
implantación y operación del proceso
Definir funcionalidades de software
para habilitar el proceso
Identificar responsables de desarrollar
procedimientos
Definir arquitectura tecnológica
Identificar necesidades de capacitación
Aseguramiento de Calidad
Tipos de Diseño y Puntos que
Analiza
Diseño Lógico Diseño Físico
Misión y objetivos
Consideraciones para el diseño
Mejores Prácticas de ITIL
Flujo de proceso
Roles y responsabilidades
Identificación de procedimientos
Desarrollo de políticas
Relaciones con otros procesos
Métricas básicas
Requerimientos de tecnología
M
a
n
e
j
o
d
e
l
C
a
m
b
i
o
24. page 24
July 26, 2025
Puntos que Analiza el Desarrollo e
Implantación
Especificar pantallas, formas y reportes
Plan de auditoria
Desarrollo de procedimientos
Desarrollar interfaces
Parámetros de configuración
Desarrollar planes de pruebas y pilotos
Instalar, adecuar y configurar herramientas e
infraestructura asociada
Carga de datos
Capacitación
Comunicación
Liberación a producción
Mejora continua
M
a
n
e
j
o
d
e
l
C
a
m
b
i
o
Desarrollo e Implantación
25. page 25
July 26, 2025
Factores críticos
• Identificar adecuadamente los servicios que la compañía provee a sus
usuarios y clientes
• Compromiso e involucramiento de la alta dirección
• Compromiso e involucramiento de personal clave de la compañía
• Objetivos, metas y visión claramente definidas
• Planteamiento de expectativas claras
• Plan de comunicación y Manejo de Cambio Organizacional
26. page 26
July 26, 2025
Beneficios y Riesgos
Beneficios
• Administración de Servicios con un enfoque a los usuarios del negocio de
la compañía y a los clientes (ejecutivos)
• Comparada con las mejores prácticas de la industria plasmadas en
ITIL/ITSM
• Control de los Servicios y la Calidad con la que se entregan a los usuarios /
clientes
Posibles Riesgos
• Que la compañía no provea información actualizada y en tiempo para las
actividades que dependen de ello
• Que personal clave de la compañía no se involucre en las actividades que
dentro del plan de trabajo se le requieran
27. page 27
July 26, 2025
Beneficios Operacionales para el cliente
• Menos apaga-fuegos, más tiempo para proyectos
– Movernos de reactivos a proactivos
• Mejora en la comunicación y coordinación entre
departamentos
• Conocer más las demandas de negocio y los planes en lugar
de reaccionar
• Menos problemas, mejor información para administrar la
infraestructura
• Menos llamadas después de los horarios de servicio
• Menores costos
• Mejorar la eficiencia
• Menos “downtimes” (mejor disponibilidad)
• Reducción del tiempo de resolución
28. page 28
July 26, 2025
• Las mejores prácticas
son clave para la
reducción de costos
• Importancia estratégica
con implementación
táctica
CIOs siempre
están buscando
las mejores
prácticas para
bajar costos
$0
$1,000
$2,000
$3,000
$4,000
$5,000
$6,000
$7,000
$8,000
$9,000
No Best
Practices
All Best
Practices
Downtime
End User
Operations
Administration
Operations
Hardware and
Software
Annual
Cost
per
User
(in U.S.$)
Source: GartnerMeasurement
Total Potential Savings:
48%
29. page 29
July 26, 2025
ITSM es un hecho real…
Resultados en HP con ITSM Services
El reto:
la mayor fusión
tecnológica
9 meses después:
Mejoras en calidad de
servicio
9 meses después:
Reducción de costos
1,200+ sites en red
215,000 desktops
7,000+ aplicaciones
900+ web servers &
infrastructura
21,671 servers
49,000 dispositivos de red
228,000 mailboxes
26 millones e-mails por
semana
30 millones mensajes B2B
mensuales
+ Incremento participación
mercado
Clientes interactuando con 1
compañía:
• Tiempo promedio espera 8 segundos
• Indice satisfacción cosnsistentemente
alto
• 24x7 soporte
• Una sola interface e-business
(hp.com)
Nuestros productos y servicios van
al mercado como uno solo:
to market as “one”:
• Cadena suministro integrada
Fuerza laboral operando como una
sola empresa:
• Serviciso RH centrales- un solo portal
• Sistemas financieros integrados
• Mailboxes combinados 2000,000+
Crecimiento acelerado
• Crecimiento mercado en todos
segmentos
• 3000 nuevas patentes
• 367 nuevos productos
$3 billones en ahorros
$1.3 billones en ahorros
integración de la cadena
suministro
26% reducción costos
manufacutra a la orden en costos
de PCs
$20 millones ahorros anuales en
procesamiento transacciones
financieras
24% reducciones gnerales en
costos
29% reduccion en aplicaciones
#5:Unplanned Downtime
To pick up on the last point, if we now look at the unplanned application downtime chart, we can see that 40% of it is caused by operator errors.
This is far higher than most people imagine.
And the obvious conclusion is that training, procedures, and the right skills are every bit as important as the technology itself.
#6:In fact, most IT organizations are waking up to the fact that poor service delivery has as little to do with the technologies IT is or is not using, as it does with poorly designed or "missing" critical IT processes, along with poorly defined roles, responsibilities and metrics, and the underlying culture. In fact, technology investment represents only 15% - the tip of the iceberg – of total IT spend.
It is the people, process, and technology that enables an IT Department to operate in an efficient and effective manner in meeting the business needs of it's clients.
IT Service Management is now recognized as one of the top key focus areas for CIOs as a means to reduce and/or control IT costs, improve the quality of service delivery, and improve IT's real and perceived value to the business.
#9:How will IT organizations with distributed heterogeneous environments evolve to service level management?
Service levels to end users reflect the interworking of many components, services, and frequently, management domains. The end result reflects the ability of the infrastructure to deliver service, but also depends on the requirements of the business application, the design of the application, and the other services being delivered by shared resources. Wishful thinking by either those delivering or consuming the service will not guarantee availability levels. As a synchronization exercise, IT organizations should consider five points of availability when discussing service levels with business managers. The first level is the desire from business managers. This expectation is frequently padded with uncertainty and a margin of safety, and not be tied to the cost of delivery. The real need may fall somewhat lower than the desire, but still may fall above what can be delivered. From the IT department’s point of view, there is the current reality of what can be delivered, given the infrastructure in place, other demands on resources, and the maturity of the organization. Service level goals should be improved through targeted process improvements and investments, however guarantees to business managers should be set slightly below what can be delivered. This approach helps synchronization by forcing businesses to more carefully understand their needs, and by using business justification to fund improvements in what IT can deliver.
Action Item: IT organizations should strive to understand what can be delivered, then set service level guarantees slightly below that level, and goals slightly above.
#10:In 1999, there is a frenzy among vendors to deliver solutions to help measure and manage service levels. Weeding through the hype however, is not easy. Business applications make use of many shared resources, and it is not easy to always track which resources come together to provide the service. While many vendors claim to have service level management tools, no vendor solves the whole problem. Tools are available to monitor individual component service levels, but do not correlate service levels to a topology of components making up a service, or relate to the actual user performance seen. The correlation issue is particularly bad when working with tools from different vendors. Enterprises need tools that can correlate components with services and users, then diagnose user problems to predict when degraded components will effect users. Some enterprises have already build this process manually, using tactical tools and business interviews to determine application topology, then using visual correlation across tools, along with event management systems, to discover probable root causes. Success with these techniques is best in less complex and bounded service environments. The good news is the emergence of end-user response time tools. Service operation staffs now have a way to discover service issues more quickly, which should lead to faster mean time to repair.
#12:Key points:
The CIO is between the proverbial rock and a hard place.
He has the line of businesses on one side facing increasing pressure to deliver quality and to deliver quickly on the new initiatives that business is waiting for. The line of business people are usually not happy because of issues.
The other side of it is the IT operations teams—the traditional people within IT who are simply saying my server is running fine, everything is fine.
The CIO has to sit between those two worlds.
#13:The Business Perspective book will cover a range of issues concerned with understanding and improving IT service provision, as an integral part of an overall business requirement for high quality IS management. These issues include:
Business Continuity Management
partnerships and outsourcing
surviving Change
transformation of business practice through radical Change.
The Service Delivery book looks at what service the business requires of the provider in order to provide adequate support to the business Users. To provide the necessary support the book covers the following topics:
Capacity Management
Financial Management for IT Services
Availability Management
Service Level Management
IT Service Continuity Management
Customer Relationship Management.
The Service Support book is concerned with ensuring that the Customer has access to the appropriate services to support the business functions. Issues discussed in this book are:
Service Desk
Incident Management
Problem Management
Configuration Management
Change Management
Release Management.
The ICT Infrastructure Management book includes:
Network Service Management
Operations Management
Management of Local Processors
Computer Installation and Acceptance
Systems Management. (covered here for the first time).
#14:To clarify how the concepts within ITIL work together, OGC produced a set of process models to describe the makeup of ITIL - a high-level process model for Service Support can be found at Appendix F. These process models have been used in practice and enhanced since first produced and now form the cornerstones of the ITIL core books. The process elements for management of services can be defined precisely. However, in practice, when analysing the processes in more detail, elements overlap. This situation illustrates the need for both consistency across the guidance, and advice on how to deal with management problems that may arise. The cause of these management problems may be the result of boundaries drawn that perhaps have more to do with the span of control than with logical grouping of related processes
#17:Introducing the HP IT Service Management Reference Model
To help its customers, HP invested considerable time and energy to develop an IT Service Management model that could be used as an enterprise reference for corporate IT organizations. Based on IT Infrastructure Library (ITIL) best practices, the HP IT Service Management Reference Model functions as a high-level, fully integrated IT process relationship map. This model has proven to be invaluable to companies around the world as they seek to understand their “people, process, and technology” problems and consider possible solutions.
The HP ITSM Reference Model development team adopted all of the ITIL best practices that could be applied to the enterprise and integrated them into the HP ITSM Reference Model. In addition, the team leveraged the extensive experience of HP consultants who have developed and implemented IT service management solutions within HP and for HP customers around the world. This includes over eight years of experience developing and implementing ITSM-based IT processes represented in the model. As a result, the model is backed up by a broad range of client-tested methodologies for training, defining roles and responsibilities, as well as documents such as detailed process guides, process flow diagrams, and RACI matrices. (As a result, our consultants typically start consulting engagements with 80 percent of what any company needs to transform a specific process, and have to customize only 20 percent to fit their unique needs, environment, and culture. This unique “Directed Design” approach to process implementation dramatically accelerates progress and reduces costs).
Additionally, while many ITIL terms and definitions are used throughout the model, HP has added others to reflect HP experience and perspective. The result is a common glossary of terms, definitions, and concepts that are used globally and designed to improve organizational communication.
Note: RACI = responsible, accountable, consulted, informed. RACI matrix is a tool for assigning cross-functional responsibilities.
#27:Here are just some benefits your customers will realize by implementing ITSM best practices.
#29:To prove that ITSM is the real deal, let’s look at how HP used ITSM in its own organization. This slide shows HP’s results from the recent merger activity.
Both pre-merger companies have been helping customers make their enterprises more adaptive by increasing business agility for years. However, the merger made it a matter of survival for the new HP. So, we applied the experience and intellectual property of both companies to this challenge—on a scale others will probably never face.
Here is a snap shot of what we have been able to achieve in just nine months.
The new HP has:
A combined workforce which operates as one company (QoS)
The ability for customers to interact with us as one company—24x7 (mitigate risk)
Reduced overall IT costs by 24% (reduce costs)
Deployed the largest HR PeopleSoft application in the world across 4 legacy companies (agility)
The fact that we could do this in such a short time is an example of HP’s new agility. But even more important, HP’s Adaptive Enterprise has also been a business enabler, allowing us to
Increase market share in all key segments
Register 3,000 new patents
Introduce 367 new products ranging from $49 ink jet printers to performance leading Itanium 2 Superdome servers