IT AutomationGanesh Jayaraman

5th January 2015

What & Why

Areas of Automation

Framework

How to Measure

Go Forward Plan

Agenda

1

Why We Need to Automate?

Reduce Man Hours Reduce Errors

Why We Really Need to Automate?

Our VisionBusiness Value Generated by ITEngaged ResourcesCompliance

What & Why?

What is IT Automation

Any code which helps complete a routine or a run book process with no or less human intervention

Can be big or really small

Automation

Measure

&

Optimize

Design

&

Evolve

Automation Framework

2

Analysis Sources

3

Remedy Tickets Monitoring Alerts Others

Infra Team Member Inputs Business Inputs

Masked

Potential Tasks Sample After Analysis

26%

4%

33%

25%

1%5% 6%

0%

5%

10%

15%

20%

25%

30%

35%

Troubleshooting Config Request Login Requests DB/ClientInstallation

DB/Client Upgrade Backup/RestoreRequests

Connectivity Issues

4

Measuring Flavors of Automation

D No Tickets created to Infra

D Business performs encapsulated Infra operations

D Measurement Criteria Number of Tasks/requests

D Tickets Created to Infra

D Mostly Handled by L1 Team

D Measurement Criteria

Pre Vs Post Time * Requests

D Tickets Created to Infra

D Handled by Auto Job/L3

D Measurement Criteria

Pre Vs Post Time * Requests

Measurement

5

Measurement Example

Task Name Pre Time Taken by

Infra

Post Time Taken by

Infra

Pre *TAT for Business

Post *TAT For Business

Time Saved

Task1 X X1 Y Y1 TS = (X-X1) + (Y – Y1)

Ex: User Creation

5 Minutes 0 Minutes 20 Minutes 1 Minute TS = (5-0) + (20-1)

= 24 Minutes

This is per Request and we would measure Time Saved X Number of Requests to compute for whole year. *TAT = Turn Around Time

S. No Automation Audience

Type 1 Handled as Self Service directly by Business

Type 2 Handled by L1 Team

Type 3 Handled by Auto Job/L3

6

Timeline for Single Cycle of Automation

Analysis – 2 Weeks

Validate/Design

2 Weeks

Coding

1 Week

Test/Deploy

1 Week

Go Live

1 Week

7