become-itil-foundation-certified-abhinav-kaiser(www.ebook-dl.com)
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 5 ■ Service Design<br />
5.7.7.4 Risk Assessment<br />
I have touched on risk assessment and management in the risk management process in<br />
the service strategy lifecycle phase. The area surrounding risks is critical to organizations,<br />
and generally they hire many risk management experts to deal with risks in the<br />
organization and their mitigation. In service strategy, it is looked at from a strategic<br />
perspective. Here, I’ll delve deeper and embed risk mitigations in the design of IT<br />
services.<br />
There is a distinct difference between risk assessment and risk management. Risk<br />
assessment deals with the possibility of threats and the potential impact the risks bring<br />
to the table. It also works with various design processes to reduce risks in the system. It<br />
is somewhat like having a backup diesel generator (DG) and an uninterrupted power<br />
supply (UPS) for data centers housed in countries where power shutdowns are <strong>com</strong>mon.<br />
Risk management, on the other hand, looks at the response when risks materialize. For<br />
all the identified risks, a mitigation action (risk management responses) is identified, and<br />
when the risk materializes, the planned responses are carried out to the tee.<br />
To reduce risks, here are some countermeasures undertaken by IT service providers:<br />
1. Storage Area Network (SAN) and Network Area Storage (NAS)<br />
storage solutions for ensuring multiple resilience layers to<br />
secure data<br />
2. Full, incremental, and differential backups to ensure data are<br />
safeguarded<br />
3. Installation of diesel generators (DG) and uninterrupted<br />
power supply (UPS)<br />
4. Autofailover for IT <strong>com</strong>ponents like servers, switches, and<br />
routers<br />
5. Elimination of single point of failures in service design<br />
5.7.8 Design Coordination<br />
There are seven processes in the service design lifecycle phase, excluding the design<br />
coordination. All seven processes contribute to the design of IT services. They do not<br />
work in isolation, and yet they need to be coordinated and brought under a single<br />
umbrella for alignment with the objectives, sequencing, timelines, and synergies. The<br />
process that connects various dots in the service design lifecycle phase, that manages<br />
end-to-end design activities, and that <strong>com</strong>municates evenly with all other design<br />
processes is the design coordination process. It is like a project management process,<br />
setting objectives, tracking, measuring, and resolving conflicts if any arise.<br />
Design coordination is a small process as it does not add anything directly to the<br />
design of IT services. But it opens up <strong>com</strong>munication channels between processes and<br />
provides all the support that is needed for achieving design objectives. Although it is a<br />
small process, it is an important and integral part of service design.<br />
108