Significant Hyper Automation in an enterprise happens thru a large number of individual hyper automation of processes. This results in a proliferation of large number of automation projects and deployments. If these automation projects adopt and follow an Enterprise Architecture for Hyper Automation, then automation implementations can be better managed and Enterprise Level goals of high reuse, uniformity in automation, sharing of process derived knowledge across the enterprise, risk free life cycle management of automation processes or even bot workers and many other benefits can be achieved.
The Recommended Hyper Automation Enterprise Architecture has been prepared by the Patterns team using Banking Domain knowledge and Hyper Automation Experience.
The Architecture is made up of following layers:
1. Enterprise Knowledge Management Layer
2. Automation of Preparatory and Common Processes (Examples are automating processing of Customer Agreements and keeping sanction covenants ready for use by Bot Workers, Automation of Historical Unformatted Customer Mandate Information, Cleaning of Unclean Customer Specimen Signatures, etc.)
3. Automation of Risk and Compliance Processes
4. Automation of Back Office Processes (Implemented by Life Cycle of Domain Entities like Accounts, Payments, LCs, BGs, Investigations, Reconciliation, etc.)
5. Automation of Front Office Services (to Support Existing Portals and Direct to Customer Services)
Architecture also recommends common and re-used integration services, manual intervention services, manual checker services, and services to provide control, configuration and automated case browsing services.
Hyper Automation will happen over many years in Banks and Financial Organizations. Advancements in Hyper Automation technologies will keep happening at Rapid Pace and the Enterprise Architecture will have to make allowances and provisions to adopt these advancements seamlessly and quickly.
