Upgrading server hardware
Calbro Services has discovered that a mission-critical server is almost reaching capacity. They must replace the current server with a model that has more capacity. Mary Mann, the change coordinator, schedules and plans the change request. Ian Plyment, who part of Mary's Front Office Support team, then implements the tasks in the change request.
The Calbro business process has predefined that this type of change request requires standard approvals to move the project forward.
The following table describes the typical steps involved in this user scenario.
Upgrading server hardware
The change coordinator creates a change request from BMC Atrium Impact Simulator:
Mary Mann, the change coordinator, runs a simulated impact analysis on the CI. She verifies what devices and applications in the network would be affected if she takes the server offline. Mary then creates a change request from the Atrium Impact Simulator. The CI is automatically related to the change request.
Mary uses a predefined change template that supports the business process and accelerates the change request process. It prepopulates fields on the change request with information.
This change template also includes a predefined Task Group template (Upgrade Server Hard Drive). The Task Group template contains three predefined Tasks Templates that are individual work items.
The change coordinator schedules the change request and runs collision detection:
Mary opens the change calendar to see if there are any conflicting change requests or business events. She uses the Schedule Assist tool to schedule the start and end dates. Mary then determines if this change request collides with other changes.
Change coordinator and change manager
The change coordinator adds task assignments:
Mary adds the task and task assignments. She then views the tasks relates to the change request and makes adjustments if needed. A predefined process is already set up for this type of change, which speeds the planning and process.
Mary sees that Ian Plyment has been predefined as the task implementer assigned to work on this change.
Mary has additional opportunity to review change plans, schedules, and so on.
From Approval Central, the change approver approves the change request.
If approvers are mapped to any approval phases, the change approver must approve the change to move it forward. Otherwise, the change manager can move the change request to the next status.
When the change request reaches the Implement stage, the task moves to Assigned status and the task implementer can start working on the first task.
The task implementer completes the Backup System task:
Ian Plyment, the task implementer, opens the first task in the task group, relates the server CI to it, and then completes the task.
The task implementer completes the Uninstall Hard Drive task:
Ian opens the second task, relates the server CI to it, and then completes the task.
The task implementer completes the Install Hard Drive task:
Ian opens the third task, relates the server CI to it, and then completes the task.
When the last task is closed, the status of the Upgrade Server Hard Drive task group changes to Closed.
The change coordinator completes the change request:
Mary completes and closes the change request.