As a US banking institution in the west coast, the client wanted to modernize its IT infrastructure and applications to prepare for business expansion. It relied heavily on manual effort for governance and third-party interactions.
The bank’s existing business processes had minimal automation and required significant human intervention. It needed a solution that could automate routine, frequent, and repetitive tasks. The solution also had to be compatible for integrating with the bank’s existing systems.
We, at Mphasis, automated various business processes of client onboarding and services using Appian business process management (BPM) and integrated different banking systems using enterprise service bus (ESB) – thereby reducing coupling. Our team deployed 250 services in production (TIBCO) and achieved the following:
• Integrated with crucial banking applications (core banking, document management system, brokerage applications, and so on)
• Established governance through a designed methodology; thus, making a best practices template as part of an integration competency center (ICC)
• Created interfaces for accessing third-party services (e.g., credit bureau, address validation, and so on)
• Established various frameworks/utilities for integration: code review, deployment automation, logging, and error handling
• Implemented client onboarding, loan services, enterprise metric management process, and risk data governance process automation using Appian. Business processes in Appian used TIBCO layer for integration
• Developed core components to build reusable artifacts in Appian
Using TIBCO, we helped the client by:
• Automating processes in various lending, deposits, and wealth management lines of businesses (LoBs), bringing efficiencies and speed
• Establishing ICC to leverage resources, optimize assets, implement best practices, and reuse services to the maximum extent
• Ensured that new channels benefitted from re-use of services designed for Phase 1
• Forming integration governance model
• Increasing IT agility (e.g., catering to quicker changes) due to lose coupling of systems through ESB-based architecture
• Reducing the cost of rework through proper design and reuse of services