Availability Guide for Change Management

Introduction to Change Management
Availability Guide for Change Management125506
1-8
Change Management and the OM Model
supplement its measure of downtime by keeping records of the number of transactions it
normally processes by minute and by day of the week. If an outage occurs, for example,
at 10 a.m. on Tuesday morning and lasts for 15 minutes, the site can calculate the
average number of transactions that would normally be processed during that period.
Subsequently, the site pays a corresponding penalty to its customer.
Using this method leads to significantly different outage costs depending on the time of
day and the day of the week. An hour-long outage at 2 a.m. on Monday morning might
carry a negligible penalty when compared with a 15-minute outage at 5 p.m. on a Friday.
Change Management and the OM Model
Change management is one of the operations-management “disciplines” defined in
Tandem’s OM model. The OM model categorizes functions of the operations
environment into six industry-standard disciplines. In addition to change management,
the OM model consists of the following disciplines:
Production management—includes the day-to-day tasks performed by operations
personnel who operate and manage the production environment
Problem management—includes the tasks required to manage and administer the
problem environment
Configuration management—includes the tasks required to manage and administer
the configuration of system software and hardware, application subsystems,
communications subsystems, and application software
Security management—includes the security features necessary to implement a
secure, audited, operations environment
Performance management—includes the tasks involved with measuring system
performance, analyzing system-performance information, and optimizing the
performance of your NonStop system
Change management and configuration management are interrelated functions.
Configuration management includes the tasks required to manage and administrate the
configuration of system software and hardware, application subsystems,
communications subsystems, and application software. Configuration-management
functions include inventory control, version control, software distribution, and name
management.
The following manuals describe various aspects of the OM model:
The Introduction to NonStop Operations Management describes the OM model and
provides an overview of each of the OM disciplines.
The Availability Guide for Problem Management describes unplanned outages and
how to predict, prevent, prepare for, and recover from them.
The Availability Guide for Change Management (this manual) describes how to
manage the maintenance and growth of your NonStop system.
The Security Management Guide describes the security-performance discipline in
detail.