Human Defined Services – Disaster case study

Disaster case studyCase study #3

A medium size software development company had its own datacenter. Accidentally, a fire destroyed the data center. Fortunately backup of the important data was in the safe place. How the company should restore data access?

IT department has to find the solution to restore access to development tools and data as soon as possible.

Service description
Description
Consumer Software development company
Stakeholders Tim Allen – CIO
Job statement Restore access to development tools and data
Provider IT department

Continuous serviceExplore  Service of access to data and tools is Continuous.

Push service  Computing, network and storage resources were purchased and located in the data center. They are Push resources.

Synchronous communication  Work with development tools was online, so that is Synchronous communication.
Chaotic  After the disaster, employees are in a panic. That is Chaotic Cynefin domain.

Service initial characteristics
Initial characteristics
Type of service Continuous
Resource delivery Push
Communication Synchronous
Touchpoints Human-Machine
Cynefin domain Chaotic

ComplexCreate  Manager of IT department agreed to get the task of recovery after the disaster. His first idea was to lease some servers, network switches and disk arrays from system integration company. He decided to use one of the rooms in the main office as a temporary data center.

Where to place equipment
Where to place equipment?

That is Co-creative

ChaoticReflect  Unfortunately, after detailed analysis of the office plan, two significant problems were detected. The conditioner in the room didn’t have enough power to chill all equipment. Service lift in the building was broken. So it was a problem to lift heavy cabinets with servers and disk array on the 15th floor.
ComplexCreate  IT manager decided to discuss the situation with CIO. “Why do we need to create our infrastructure? Is it possible to use cloud resources?” asked CIO.

Let’s use a cloud
Let’s use a cloud

That is Holistic

Complicated  IT manager found Platform as a Service (PaaS, 2014) cloud provider and discussed with experts conditions of their service usage. The solution didn’t require any CAPEX and was cheaper in perspective of OPEX in comparison to their own infrastructure.
Implement  Migration to PaaS took about 4 days. The company recovered after the disaster.

Service final characteristics
Initial characteristics
Type of service Continuous
Resource delivery Push
Communication Synchronous
Touchpoints Human-Machine
Cynefin domain Chaotic
other

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s