Managing Complex Digital Process with Event Driven Intelligent Business Process Management Architecture (ed-iBPM)

1. Managing Complex Digital Process with Event Driven Intelligent Business
Process Management Architecture (ed-iBPM)
Traditional Business Process Management processes are built on Request driven
architectures such data is captured on a form which is in-turn liked to a work-step on
the process, on submit of the data captured over the form, validation are triggered
and date is persisted. After satisfying all the data conditions the work-item moves to
the next step and the process continues. Such processes are impossible
to reuse when organizations want to add new channels and partners.
Logical view of request-driven architecture:
Fig 1. Logical view of request-driven architecture.
Digital Business Model: Today’s digital business models demand managing a mix
of multiple digital moments and digital events which involve customers,
organizational staff, business processes and things working dynamically together to
produce increased and highly predictable value. These digital events call for specific
business action to be performed such that an automated decision can be achieved
which eventually delivers a product or service directly to the end consumer.
Fig 2. Digital Business Model.
Automated
DecisionEvent
Driven
Digital
Business
User
Experience Change
Averse
Situational
Awareness
Manage
Moments

2. Event Driven Business Processes Management: Every process is event driven
irrespective if it is initiated by the user of the process or system, i.e. Event thinking
can drive change in the way business processes are built. Event driven starts with
the assumption that the course of action is determined at runtime and can be
influenced by the context of changing business conditions, policies and procedures.
Even though request driven processes are highly predictable but are very rigid in
responding to changing business conditions, policies and procedures.
Consider the below diagram, by building Event driven business process
management process, the advantages that a business can achieve is immense, for
ex. channel agnostic, core integration layer agnostic, high flexibility for change, agile
time to market.
Fig 3. Event Driven Business Process Management.
ed-iBPM – Platform as a Service: The process is architected and developed in a
highly flexible way that a single hook can be exposed to any internal or third part
application or systems. This front facing application can be designed based on the
desired UX/UI to suite the customer/user demands whereas the entire back-end is
available as a platform to be consumed. Any new products or services that needs to
be added in the future can be promptly added to the platform without much difficulty
and readily delivered to the customers or users.
BPM- Event Broker and Core Service Integration Framework: This is where the
entire design flexibility comes into play, traditionally IT systems are directly
integrated to the core systems using an ESB or an API gateway, and this leads to a
Customer
On-Boarding
Process
Account
Opening
Process
Credit Card
Issuance
Process
Loan
Disbursal
Process
Investment
Account
Process
Core API’s (Internal systems or External reference data sources)
Customer
Screening
Credit Bureau BRMS Business Decision
Management
Product Processor
API
Core Systems
Event Driven intelligent Business Process Management
Platform as a Service (ed-iBPMaaS)
Bank Manged
Channels
Aggregator
Channels
Branch based
systems
Field Sales Force
Platforms
BMP – Event Broker & Core Service Integration Framework

3. highly inflexible for a BPM platform such that every process on the BPM is tightly
integrated to the core services.
In the new approach which we have been implementing, a BPM-Event broker plays
a vital role between the business process layer and the core service integration
framework, i.e. the event broker can orchestrate different calls based on desired
actions demanded from the events generated on the process layer to the underline
services and thus removing the need for every process to integrate directly with the
core systems.