become-itil-foundation-certified-abhinav-kaiser(www.ebook-dl.com)

Chapter 6 ■ Service Transition
The DML is ideally designed during the service design lifecycle phase and the
following are considered during the planning stages:
• Medium to be used and the location for the master copies to
be stored
• Security arrangements for both online and offline storage
• Access rights, who has access, and how it is controlled
• Naming convention for the stored media to help in easy retrieval
and tracking
• What types of software go into the DML, for example, source
codes or packages
• Retention period
• Audit plan, checklist, and process
• Service continuity of DML if disaster strikes
Definitive spares (DS) is a repository for storing hardware spares. Generally, all
organizations store a certain amount of stock, mostly pieces of critical infrastructure,
to be use to quickly replace hardware in case of an incident. And then there are stocks
that are needed for the operational consumption and ever increasing demands of the
customer.
Like DML, DS must be secured, tracked, managed, and controlled. However, change
management generally does not get involved in controlling the items that go in and out
of DS, as the gravity of compromising intellectual property and master copies of licensed
versions can be very messy as compared to hardware spares. SACM process oversees the
overall functioning of the DS.
6.4.3.5 Objectives of Service Asset and Configuration Management
The SACM process exists to ensure that the service assets that deliver the services are
governed, controlled, managed, and tracked across their lifecycles. All attributes of
service assets and CIs, including relationships, come under the ambit of SACM.
The objectives of SACM are:
• Ensure service assets are identified and are managed
• Identify, control, record, report, audit, and verify configuration items
• Maintain CI versions, baselines, attributes, and relationships
• Ensure CIs are controlled through change management, and only
authorized changes can trigger changes to CIs
• Ensure CIs are accounted for, managed, and protect the integrity of it
• Maintain all CIs including their correct statuses, relationships,
and attributes in the configuration management database
141