How To Approach Automation in Application Support and Maintenance
How To Approach Automation in Application Support and Maintenance
automation in
application support
and maintenance
Think big, but start small. A step-by-step approach Automation: The game changer
starts with breaking down end-to-end processes
into small bits and beginning automation with & the involved challenges
simple but high-impact use cases Implementation of automation in application
support and maintenance helps tackle issues like
manual error-prone processes, high cost, and
Application support and maintenance teams face limited resources, and enables enhanced efficiency
multiple challenges on a daily basis due to the and productivity. However, automation in application
complexities involved in their operations. support comes with its own set of challenges:
Process
2
Technology The apt approach to automation
So, how do we approach automation? First and
Ever-changing IT landscape – Multiple releases
foremost, we need to understand that automation is
happening every now and then, new applications
a journey which has to start from within. The starting
getting added, addition of SaaS applications, etc.
point lies in existing tools and infrastructure. It is
can make automation challenging
essential to start with simple but high-impact use
cases. The focus should not be on automating
High degree of customization – Customizations,
end-to-end process, but breaking it down to pieces
especially in ERP environments, always increase
and beginning automation with small steps. For
the complexity when adding anything new in the
example, before a support engineer deep dives into
application
the system to investigate the issue, automation can
help him/her gather the basic information by
Considering automation as one-time activity –
traversing through multiple related transactions and
Once automation is done, people become compla-
applications. Even better would be to update the
cent. It’s important to remember that automation
ticket with all the information gathered, even before
is a journey and not a one-time activity. Continu-
he/she starts working on the ticket.
ously training and retraining the models, looking
at value delivered and identifying new automation
opportunities is the key
Self-help tools for issues Chat bots to resolve Service request automation RPA based automation to
like password resets “how to’ issues using Orchestrator reduce manual activities
Bots to correct the data Chat bots for enquiries Automation of requests based
and re-initiate the and status updates on workflow approvals, e.g.,
process access to certain
Bots to generate required applications, folders, etc.
reports themselves
User
(based on authorizations)
Figure 2 explores how automation can be enabled at each level of support ecosystem
To summarize, take a step-by-step approach. Start part of organization’s DNA and involve larger
small but think big. It will give confidence to the groups/ teams.
organization and make the journey easier. It is
important to remember that automation is not a job Lastly, automation should not be seen as a mission to
of one particular individual or group. It has to be a reduce manpower. Instead, it should be seen as a way
important to remember that automation is not a job to help humans do more value-added jobs and leave
of one particular individual or group. It has to be a repetitive and mundane jobs to bots.
3
About the Author
Anmol Srivastava
Strategic Manager,
Wipro HOLMES™