-Awesomation-
  • Home
  • IT Transformation Basics
  • Decision Helper
  • HyperAutomation
  • DATA AI ML
  • The Fusion: Au-AI
  • Low Code World
  • Journeys & UseCases
  • Get in touch
  • External Useful Resources

A *Beta* resource that is getting ready to navigate the Digital Tech!

-Awesomation-
  • Home
  • IT Transformation Basics
  • Decision Helper
  • HyperAutomation
  • DATA AI ML
  • The Fusion: Au-AI
  • Low Code World
  • Journeys & UseCases
  • Get in touch
  • External Useful Resources

The importance of Categorization

One size doesn't fit all!

Java can automate. So can Python.

Ansible can automate. So can Terraform.

Pega can automate. So can ServiceNow.

Powertools can automate. So can UiPath.

Macros can automate. So can Shell scripts. 


Most of the tools can execute steps.  The tools can perform tasks. The tools can talk to APIs. Even the languages can give you those results if the code is written that way.


Does that mean we are good if we have one tool or a team that can develop Python based apps quickly?


The technical team will say yes. They will get new experience.

The finance will love it because there is no additional spending (CAPEX & OPEX).

The management will love it. A known devil is better than an unknown one.


Now, what matters is to know what fits where and what fails where.


For example:

RPA tools (UiPath, BluePrism etc) fail where

  • Process is not standard
  • Process is very complex 
  • The data is not structured
  • The volume of transactions is high
  • Bots are used for lift and shift and heavy lifting
  • Where scalability is a must
  • Abused as a one stop shop
  • Missing the human element
  • Mobile interfaces


BPM tools (Pega, Mendix etc) fail where

  • Process is not standard
  • Process is horizontal across organization
  • Process integrations are many and complex
  • Long running processes
  • Target system out of reach
  • Where scalability is a must
  • Technical Processes Vs Business Processes and the tools used
  • Missing the human element
  • Mobile interfaces


Similarly, technical orchestrators (Ansible) fail where the steps are simple and need intuitive UI/UX.

Then, there is a whole category of network orchestration tools like Netcracker, which have specific tasks of network automation.

And there are platform of platforms like ServiceNow, which can do it all (at least it says so). But more suitable for Hybrid processes.


The more you go deeper, the bigger is the classification. The decision maker section helps more on this aspect.


As a result, a categorization of Automation targets help choose the right set of 2-3 tools.


But, it is extremely important that the automation decisions are not tool driven.

IT Transformation Basics

<< Go Back

Awesomation

IT's not rocket science!

Copyright © 2024 Awesomation - All Rights Reserved.

Disclaimer: The content is based on experience of the author. May not contain some areas specific to certain aspects of technology usage. 

May also seem very similar to such publications at places.

Powered by Passion

Hello World!

Awesomation is a work-in-progress Beta resource! 

Knowledge is being updated to make it awesome for you :)

The skeleton is ready and good to paint a Mind-Map of Digital Transformation, HyperAutomation, AI/ML & Low Code!

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

Accept