An early function of the IT is to establish a preliminary CA ACF2 for z/VM implementation schedule. This may only include the major points, such as the test IPL (Initial Program Load), the production installation and IPL, and migration to ABORT mode. As the team reviews the CA ACF2 for z/VM documentation and identifies additional tasks it needs to perform, add them to the schedule. A good implementation schedule includes a detailed list of tasks, target completion dates for each, and the name of the person responsible for completing that task. The IT should monitor the progress in each area, resolve conflicts, and periodically update the schedule as necessary.
We have provided an example of a good implementation schedule below. We have also provided general time frames for chronological reference but you should use specific completion dates wherever possible. However, we have not included responsibility assignments in this example because they vary from site to site, depending on the type and number of persons available for the project and the size of the task. Add more detailed tasks as you define them.
Important! This is an CA ACF2 for z/VM implementation schedule, not an installation schedule. The installation of CA ACF2 for z/VM is merely the activation of the code on your computer. The implementation of a security system includes much more, whether the tool to help automate the security process is CA ACF2 for z/VM, or some other product. That is why the planning process is so important and why you should use a team of knowledgeable people rather than the one or two persons needed to just install the package.
|
Copyright © 2009 CA Technologies.
All rights reserved.
|
|