Introduction to NonStop Operations Management

Operations Management and Continuous
Improvement
Introduction to NonStop Operations Management–125507
13-9
Implementing an Operations-Management
Improvement Program
•
TACL macros were used to monitor available disk space and processor processes.
However, because the macros had limited functions, they had to be recoded each
time there were system configuration changes. In addition, operators had to execute
and analyze the macros manually. Often when a serious problem occurred, operators
were unavailable to execute the macros.
•
Other aspects of the physical environment included an inadequate telephone system
and insufficient work space, the latter making it hard to look at operator manuals
and product documentation.
Step 2—Developing a Vision
The next step for the improvement team was to develop a vision of the processes they
wanted to have in place. They began by outlining three general goals:
•
Improve the quality of end-user services by improving application availability.
•
Reduce the complexity of operator tasks.
•
Lower the cost of ownership by improving operator productivity.
To accomplish these goals, the improvement team developed the following list of
objectives:
•
Handle all system and application messages through a standard console-
management service.
•
Define application-design standards to be followed by all development groups and
projects.
•
Use a management tool to convert text messages in applications that were coded
before the standards were established.
•
Document all major system components, their configurations, and how they deliver
services. Define the procedures to be taken when problems occur.
•
Automate recovery tasks for routine (recurring) problems.
•
Automate object-state monitoring, resource monitoring, and performance
monitoring. Make automatic reporting and trend analysis available on demand.
•
Define change management procedures.
•
Develop a model of the management process.
•
Document the operation organization’s structure and responsibilities.
Step 3—Developing an Action List
After establishing the improvements they wanted to make, the improvement team
decided which tasks were most important and determined the sequence in which to
implement them. The result was the following action list:
1. Manage system messages.
2. Manage application messages.