become-itil-foundation-certified-abhinav-kaiser(www.ebook-dl.com)
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 6 ■ Service Transition<br />
When the release and deployment management provides ample proof that the testing<br />
has been successful, the change management provides authorization to store the code/<br />
software in the DML. DML is explained in detail later in this chapter.<br />
6.4.2.3.3 Deployment<br />
The results of the release and deployment testing are brought before the CAB once again,<br />
and the results are vetted for possible <strong>com</strong>plications and unseen bugs. When the CAB<br />
and change management are happy with what they see, they authorize it for deployment<br />
during the planned change window.<br />
Deployment is a <strong>com</strong>mon term for implementation. It could include retiring of<br />
services or transferring services to another service provider as well. For simplicity, I’ll just<br />
refer to it as deployment.<br />
Deployment of release packages is a specialized skill and calls for alignment of a<br />
number of parameters. There are a number of approaches to the release package. The<br />
big-bang approach is used when all the CIs are targeted to receive the package at the<br />
same time. Say there are 10,000 workstations that need to be pushed with a security<br />
patch. All 10,000 systems will receive the release package during the same window.<br />
This method is rarely employed as it has the ability to choke the network. And, if there<br />
are any mishaps, all the targeted systems could be affected, causing severe damage<br />
for the customer. The most popular approach is a phased approach, where the release<br />
is staggered through multiple phases to minimize <strong>com</strong>plications and avoid network<br />
choke. In the same example involving 10,000 systems, it could be phased to target 1,000<br />
systems a day, and to run the entire release cycle for ten days. Further details on release<br />
deployment is outside the scope of ITIL Foundation exam and this book.<br />
6.4.2.3.4 Review and Close<br />
After deployment, the release and deployment management process conducts a review to<br />
check the performance of the release and assesses the targets achieved. Lessons learned<br />
are documented in the KMDB. The release is closed after the review.<br />
6.4.3 Service Asset and Configuration Management<br />
Service asset and configuration management (SACM) is one of the most critical processes<br />
in the ITIL Framework. This process acts as a <strong>foundation</strong>/prerequisite for all other<br />
operational and transitional processes to carry out their respective objectives.<br />
6.4.3.1 Service Assets and Configuration Items<br />
There are two parts to this process: service assets and configuration items.<br />
Service assets are individual elements that make up a service. In Chapter 2, I<br />
discussed service assets. The ten service assets are managed under this process. The<br />
entire lifecycle of the service assets, beginning with initiation, the changes it undergoes,<br />
136