DR to AlwaysOn: Disaster Recovery (DR), Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are history. AlwaysOn is the new norm. The infrastructure environment is coded with auto-scale and auto-recover mechanisms. This enables scaling out the service on demand or relocate itself to a new region in disaster scenarios.
Human labor to digital labor: Tower-based headcount for operations is history. Bots enabled by artificial intelligence would completely invalidate the tower-based model for operations. The digital labor in an estate would be measured and enhanced more than human labor. Automation moves from tasks/process level to cognitive levels
RFP/PO-free sourcing and fulfillment: Self-service enabled sourcing and automated fulfillment across multiple providers will slowly eliminate long RFP and PO processes.
Waterfall to agile: Most Infrastructure automation and operations work will move away from a Waterfall to Agile model. The team composition, hence, has to be in small 8-10 cross-skilled members and aligned to services than towers.
In-source to crowd-source: The idea of ‘jobs’ is changing from full-time-employment to task-based-employment. As services get more and more commoditized, there will be more opportunities to atomize the jobs into smaller chunks which are delivered by people without being employed full time.
Key components of Design2operate paradigm
Like any other major transformation, all three aspects of people-process-technology need to be sufficiently considered to implement Design2operate paradigm. The specifics of these three aspects may vary based on the maturity levels of the organizations, but irrespective of the quantum of the change, there is a need for a shift in thinking about the operational model.
Some of the key technologies that enable Design2operate are:
- A strong infrastructure as code practice
- Marketplace and service catalog with automated aggregation, intermediation and arbitration of services across different providers
- DevOps technologies
- Real time infrastructure based operations that uses wire data enabled dynamic models and baselines to avoid incidents
- Digital labor pool
Organization structure has to significantly change to adapt a Design2operate paradigm (See figure 2). Some of the new skills required are:
- Patterns and practices
- Integrated IT finance management
- Infrastructure developers, site reliability engineers
- Agile practitioners
- Job atomizers
- Incidence avoidance analysts