A DOCTOR FOR YOUR BOTS AND AUTOMATION ENVIRONMENT
As Automation technology advances to greater maturity with the infusion of AI, combining process orchestration, data and event processing through Workflow, image and document processing, BOTs are becoming the key constituent of digital workforce of the enterprise.
Building and Operating BOTs are 2 sides of the same coin, Both these activities must be successfully executed for the overall success of the Automation Initiative. With growing number of BOTs in the estate, there is pressing need to manage the digital workforce effectively and at a reduced OpEx.
Introducing Dr. BOT, a BOT that manages all the Bots in the farm, a BOT that learns and develops, nurtures and shepherds the multitude of Bots deployed at the enterprise. Dr. BOT essentially automates the automation support and monitoring.
Dr. Bot conceptually is a highly customizable Super BOT comprising various traditional and intelligent automation toolkits and a web-based interface to help manage the growing digital workforce.
Bot Management & Monitoring
Enable and Disable Bot Triggers
Identify continuous failures of a scheduled job, take corrective action and send alerts.
Bot Status check
Identify unresponsive Bots and perform basic sanity checks like restart of services to fix or notify for further action.
Dr. Bot agents to check RPA issues or Monitor Jobs
Identify common errors across automations and alert if the number of failures exceeds the configured threshold. It also analyzes the Bot logs using AI & ML to identify anomalies.
RPA Dashboards can be built that provide real-time business insights along with task execution status of the robotic processes. This dashboard is platform-independent and can be accessed remotely.
Insight Dashboard help organizations:
Interfacing with ITSM & Stakeholder Interactions
Create Incident Tickets & Assignment
Identify any issues resulting in BOT failures and notify the respective business or technical teams for corrective action. This effectively reduces ~30% of overall manual efforts.
VDI Creation Request
VDI requests can be created by BOTs. For example, post completion of SIT, the Bot will automatically place the required number of VDI request.
Service Account Creation
Proactive creation of Bot service accounts as per agreed naming convention. Dr. Bot ensures seamless availability of production service accounts for new processes which needs to be deployed into production.
Basic Access & Policy Exemptions Creation
Dr. Bot can be configured to create request tickets to provision access to basic applications like office 365, share drive access etc. Dr. Bot can request for policy exemptions such as MFA, Password, and account expiry etc.
Dr. Bot can work 24/7 to monitor server health such as CPU & memory utilization, disk space, temp file clean-up, rollback of windows patches (if required) and take corrective action. Dr. Bot can perform scheduled restart of servers as part of routine maintenance.
Proactively monitor the Bot licenses and identify unused licenses and inactive users.
Maintain & Manage Business Objects
Perform the in-scope application login and availability checks before the actual automation execution. If the application’s availability check fails, then the BOT creates ITSM tickets and disables the schedules.
Actively check the new passwords to ensure they are working as expected and notify if any issues are identified.
Dr. Bot helps increase Both tangible and non-tangible benefits by improving overall efficiency of RPA. Mphasis has successfully deployed Dr. Bot at multiple client organizations. Dr. Bot deployment usually follows successful delivery of an automation engagement resulting in hundreds of BOTs in the Estate.
Below are some of the benefits delivered by Dr. BOT in some of the large Automation Engagements across Clients.
One of the Leading Real Estate Management Firms based out of NA reported ~27K savings per month with successful implementation of Dr. BOT.
Mphasis helps an American Commercial Real Estate Services and Investment Firm decrease operational costs by RPA implementation