Ncaea2019 Bian
Ncaea2019 Bian
Presented by:
Parimah Mohammadpour (New Product Development (NPD) Department Manager at Sadad Informatics Corporation)
Customer Experience The sum total experience that enables customers to self-serve, in real time, via multiple devices, with environmental context
that results in a personal and relevant experience. This requires online access to all products and services as well as the real-time customer intelligence
to be able to provider relevant, contextualized and personalized content and offers at the right time and on the right device.
Execution Experience The sum total experience that enables organizations to deliver on-demand services with minimal human involvement via
straight-through-processing whilst enabling internal bank users to serve clients via offline channels and continuously improve products and processes.
This requires an end to end digital platform and architecture.
Response to customer needs: Ranked as the most important trend in each of the last 4 years in research done by
the Digital Banking Report financial institutions need to shift from physical interactions to digital engagement. For
banks and credit unions that digitize customer journeys, there can be a significant benefit in revenues, cost
reductions and customer satisfaction.
Optimization of costs: Because of the efficiencies of digital-only competition, banks and credit unions will need to
consider divesting from non-core operations and leveraging intelligent automation. In addition, organizations will
need to reinvent back office processes and replace aging infrastructure.
Creation of new revenue streams: Open banking and the use of APIs will open new opportunities for both cost
reduction and revenue growth. As the banking ecosystem expands beyond traditional banking services, new
products will be developed and segments served that will provide differentiated offerings and monetization
opportunities.
Development of security and compliance systems: With customer data becoming a ‘product’ for many financial
institutions, the need for enhanced security and advanced insights (AI) will become a differentiator from both a
compliance and customer trust perspective. This can lead to reduced costs and potential business growth.
Business Architecture
Information Architecture
Application Architecture
Technology Architecture
Introduction
BIAN Introduction
BIAN Organisation
The Problem BIAN Seeks to Solve
Process Model Vs Capability Model
BIAN Artifacts
How to Guide Series
Digital Repository
BIAN Release
BIAN Overview
Founded in 2008, the Banking Industry Architecture Network (BIAN) is a global, not-for-profit
organization that seeks to develop standard Service Landscape and Semantic IT Service (A2A)
Definitions for the Banking industry. BIAN will enable the next generation of banking industry solutions
developed either in-house or commercially:
Business architects do not have the organizing equivalent of the town plan
Many Bank’s application portfolios suffer from such fragmentation. They contain a high level of
redundancy. Worse, as most connections are unique, they present highly complex maintenance and
enhancement challenges
Advances in design techniques, technology and awareness mean that the migration to well architected
solutions can be incremental
At the outset, the applications in a conventional ‘process based’ application portfolio can be drawn as a
criss-cross network of overlapping processes.
Analysis of the BIAN Service Domains can be used to target those areas that are the main
bottlenecks…
As the early Service Domains are stabilized behind more complete service boundaries, additional
areas can be addressed
Over time more of the traffic is handled between the rationalized and stable service centers and more
of the legacy is wrapped, replaced or rendered obsolete/replaced
Eventually the migration to a service based architecture replaces the significant majority of the portfolio.
Operational capability re-use enables new business needs to be addressed with incremental changes
rather than completely new stand alone solutions…
Process based views of busines activity have been used very effectively
But the very flexibility of process modeling limits how it can be used to define canonical standards for
service operations – the allowed variations mean only the most common procedures or commodity type
activities can have a standard process definition
Process monthly
billings
Process due Get balance, determine Generate and send Process Check for late
accounts minimum payment out invoice payments payment status
Run month Filter any Identify Get account Calculate Get billing Print Add sales & Stuff and Receive Post Update Check for
end due cards in customer activity history minimum address & billing marketing send out inbound payment account payments
card extract suspense account # (30 days) payment details invoice materials letters payment to account status received
Billing Application
Processing steps at the lowest level could be
implemented as software elements/modules.
They can be assembled to create a stand- Choreography implemented as a dependent procedural flow of
alone/monolithic billing application tightly coupled service couplets that ‘exist’ for the life of the
transaction itself
Process analysis automates a tightly coupled sequence of “Input/Process/Output” (IPO) activities that
can be implemented as software
Get billing
Choreography
implemented as
Customer
address & Agreement
details
an
Get account
activity history
Post
payment
Update
account
Check for
payments
Cash asynchronous
Accounts
(30 days) to account status received series of loose
coupled service
Print Add sales & Stuff and
billing
invoice
marketing
materials
send out
letters
Correspondence interactions
between
Receive Post Payment
persistent
inbound payment
payment to account
Order
Service
Domains
The process
is remodeled
Get account
Run daily Filter any Identify Calculate Get billing Print Add sales & Stuff and Receive Post Update Check for
activity
30 day due cards in customer minimum address & billing marketing send out inbound payment to account payments
history (30
card extract suspense account # payment details invoice materials letters payment account status received
days)
Service center design removes the dependent ‘Input/Process/Output’ sequencing allowing for more
flexible patterns of collaboration…
Correspondence
Cards
Payment
Customer Order
Agreement
Cash
Accounts
Many busness activities are not well represented as a repeatable, sequence of predefined activities as
implied by a process model. Some analysts have estimated as little as 5% of business behavior is well
characterised using conventional process model designs
Correspondence
Cards
Payment
Customer Order
Agreement
Cash
Accounts
BIAN Architecture Layers BIAN - the link between business and technical architectures
Service Domain
Service Operation
Service Landscape
Business Scenario
Wireframe
Clustering
Services
Offered
Full
Lifecycle
Instances
Consumed
Services
Local State
Asset Types
Functional Pattern
Generic Artifact
Behavior Qualifiers Types
Control Record
Features of Service Domain
Service Operations
Building Business
Architecture Architecture
Hotel Consumer
Complex Division
Entertainment Business
Floor Development
Furnishing, Meetings,
Doors, Reports,
Windiws Tasks
The execution of the Service Domain’s role for the full life cycle is tracked/managed using an instance of
its ‘control record’. A Service Domain applies one pattern of behavior (functional pattern) to one asset
type. Its control record combines the functional pattern’s generic artifact with the asset type.
The discrete business functional capacity partition represented by a Service Domain can be considered
as being broadly equivalent to an organizational unit of the enterprise that combines the ‘people, process
and technology’.
SHARED
Alliance Partner Customer SOLUTIONS
Agent
Equities
Retail Corporate Institution
Broker
Pick the ENTERPRISE Service Domains Too General
level ALIGNMENT Derviatives
Custodian Card SMB MM
HNW
Options SWAPS
With the recent introduction of the behavior qualifier type and Service Domain specific behavior qualifier
definitions, the service operations and their information content can be defined to a finer level of detail.
The primary purpose for each service operation call is reflected in its action term. BIAN has identified a
standard set of action terms to select from and each service operation uses one of these action terms.
Business Area
The design elements of the BIAN SOA Design Framework are supported and enabled by some key
standard specifications, guides and tooling. These include:
One-to-One
One-to-Many
Many-to-One
One to One
Less commonly it may be that the Service Domain defines a business function that typically brings
together a collection of business applications.
This can occur when the function exploits an array of tooling and support that may be implemented by
different specialized applications.
One to Many
Sadad Informatics Corporation
Copyright New Product
BIAN 2011 | Banking Industry Architecture Network Development Group
Applying BIAN Content
Mapping Service Domain to Business Applications
Byfar the most common mapping will be where several Service Domains are contained within a
business application.
Many to One
Externalizationis an approach used to determine what a Service Domain should do itself and when it
should call on or ‘delegate to’ the services of another Service Domain. Externalization ensures that each
Service Domain performs a single discrete function and so enforces the encapsulation principle.
Duplication:
The most obvious is where two or more business applications perform the role of the same
Service Domain.
Gaps: It may also be possible to see which legacy applications are the best candidates to expand to
cover these requirements.
Misalignment:The problem can be that an application designed to support one function can become
compromised when it tries to support many additional and potentially conflicting operational
requirements.
Point Solutions
Describes the typical steps that can be followed to apply the BIAN designs in the context of a targeted or
point solution:
Business Case
Business Scenarios
Wireframe
Requirement
Solution Mapping
Customization/Development
Deployment Planning