BIAN Reference

Implementations

1 Copyright BIAN 2020 | Banking Industry Architecture Network

 Known BIAN Implementations – 20201

Service BIAN Service

Domain APIs BOM
Management2
• SPD Bank (& IBM)
• PNC • PNC
• ABSA Bank (&TCS)
• Santander • IBM
• SPD Bank (&IBM) • SPD Bank (& IBM)3
• CIBC • ABSA Bank (& TCS)3
• ABSA Bank (& TCS) • Santander
• RedHat Devops CI/CD
• PNC
• RedHat
• SwaggerHub (&GitHub) – API
Compliance Tools
Open Banking
• IBM SD Mapping

Certification4
• Pilot
• Temenos
• DXC
1Implementations that we are aware of through webinars, working groups and discussions; likely to be more in reality. • Interested
2Application Landscape Heatmaps, Application Portfolio management, Business Architecture, Business Capabilities.
3Further implementations are possibly underway, that can’t be disclosed for confidentiality or other reasons.
• Intellect
4Certification (DRAFT) Working Paper & Questionnaire (Spreadsheet) have been produced, being reviewed. Design
• Union Bank
of Philippines
2
https://bian.org/participate/bian-webinars/ Copyright BIAN 2020 | Banking Industry Architecture Network
 PNC
ABSA (&TCS)
IBM
SPD Bank (& IBM)
RedHat
Santander
CIBC
Solution Certification
API Governance, Compliance & Feedback

HIGHLIGHTS

3 Copyright BIAN 2020 | Banking Industry Architecture Network

PNC
July 28, 2020
ADOPTION OF BIAN APIS
BIAN Inspired APIs
Moving from fine-grained endpoints to logical endpoints representing business functionality

From: To:
Experience

API Consumer API Consumer

Orchestration

Payment Account

Payment – Inner API Account – Inner API

Ecosystem
Open API

Reg. Payment Payment Financial ACH Position

Compliance Order Execution Gateway Fulfillment Keeping

Bill Pay System of Record Bill Pay System of Record Bill Pay System of Record Bill Pay System of Record

13
Adoption of BIAN APIs
PNC’s new architecture strategy includes ‘Inner APIs’ which perform a single function and align to BIAN standards

New PNC Architecture

Experience
Fine-grained representation of a user interaction. Specific user function,
DOMAIN MICROAPP
only concerns itself with performing that function as best as possible

Experience Experience

Outer API
Tightly coupled to the UI, provides the data necessary for display purposes
by the UI. It is the Outer APIs job to filter out unnecessary data and to
orchestrate invocations across many Inner.
Outer Outer

Inner API (BIAN Inspired)

Exposes all functionality and data contained within a SOR to the
enterprise. The Inner API's evolution is tied to the evolution of the SOR
and should only perform one function, allowing for abstraction from the
SOR Inner Inner Inner Inner

Inner APIs are inspired from the BIAN API Model and leverage the BIAN
Object Model (BOM) to model their inputs/outputs

▪ To avoid vendor lock-in and provide a BIAN inspired Inner API, we must
build our own Inner APIs
▪ This principle is important to abstract out Vendor Systems of Record
▪ An Inner API will need to be built that calls the Vendor’s proprietary API SOR SOR SOR SOR

14
DEVELOPING WITH BIAN
 Developing with BIAN
PNC has developed a number of tools to integrate the BIAN framework and data modeling standards across the
development lifecycle
API Discovery
Innerpedia
Description
Catalog of endpoints, inspired
by the BIAN endpoint console,
for individuals to discover in-
development and completed
endpoints
▪ Promotes re-use
Benefits
▪ Provides all Inner APIs in
one unified location
▪ Allows users to understand
how to leverage and call
specific services
API Toolkit
Endpoint Catalog & API model
Mechanism for users to select
BIAN-inspired PNC endpoints
and build their payload from
already modeled entities and
properties
▪ Improves time-to-market by
accelerating development
cycles
▪ Enables seamless integration
and data sharing across
systems
Generator & Validator
Swagger Generator & Validator
Tools that generates and auto-
populates swaggers with data
from the API Toolkit while
ensuring adherence to BIAN
and PNC standards
▪ Accelerates modeling and
development time in-line
with contract-based
development
▪ Enables users to better self-
serve and check for
adherence to standards
Pipeline Enforcement
GitOps Pipeline
Pipeline outfitted with various
enforcement capabilities to
ensure standards are enforced
▪ Automated pipeline checks
ensure applications meet our
set standards
▪ Enforcement mechanism to
ensure applications not
modeled correctly do not
reach production
Compliance Dashboard
Compliance Dashboard
Compliance dashboard
aggregates microservices’
adherence to leading practices
▪ Increased visibility into
application compliance
▪ Alerts simplify management of
‘drifted’ applications
16
 Innerpedia
Innerpedia is PNC’s central repository for inner APIs, allowing users to search and understand the capabilities of each of API
while promoting re-use and adherence to BIAN naming conventions

Searching
Type keywords here to search for
any existing APIs that perform the
service you are looking for
Inner API Naming
Applications follow the
standard naming
convention of: ‘BIAN
Service Domain - SOR’

Descriptions
Descriptions of the service domain
have been provided, as well as
examples of use to provide specific
use cases for each microservice

17
Swagger Generator & Validator
The Swagger Generator and Validator were built to help users model their services uniformly and in adherence with PNC and
BIAN standards

Swagger Generator Swagger Validator

▪ Mechanism for users to build swaggers (contracts)in
accordance with PNC standards
▪ Includes stored BIAN and API model data so that fieldsauto-
populate and restrict the user from deviating from modeling
guidelines
▪ The validator provides users the opportunity to check
that their swagger is compliant, providing feedback for
any errors
▪ The tool checks to ensure naming conventions, BIAN
standards, and other modeling rules are adhered to

18
Compliance Dashboard
The compliance dashboard allows both development teams and managers to monitor adherence to modeling and swagger
standards

▪ The compliance dashboard displays compliance checks that are performed when applications are built and deployed

▪ Provides a mechanism to check for adherence to specific standards, like swagger and data modeling compliance

19
PNC AND BIAN PARTNERSHIP
BIAN-Inspired Innovation & Partnership
The API Toolkit, a combination of the Endpoint Catalog and API Model, is a key enabler in ensuring BIAN standards are
adhered to at PNC and provides PNC a mechanism to enhance the BIAN industry framework
Endpoint Catalog Extending the Model | PNC and BIAN Partnership
Universe of all BIAN-inspired endpoints mapped to service domains and their corresponding
The work and analysis conducted to develop the Endpoint
SORs
Catalog and API Model provide a mechanism for PNC to
Endpoint Catalog contribute to the BIAN model by extending both the
framework’s endpoint list and Business Object Model (BOM)
▪ Ensures all endpoints developed
leverage BIAN standards
▪ Identifies areas to extend BIAN Feedback Loop:
endpoints to meet PNC
requirements ❶ Leverage the existing BIAN endpoint list and customize
them for PNC’s use cases and transactions

❷ Understand PNC SOR capabilities and map them to the

API Model BIAN model
A collection of ER models that details entity and property relationships for each service
domain, depicted in logical ER diagrams and provided to users in a JSON format ❸ Host working sessions to ensure PNC-inspired
endpoints and models align to the BIAN framework
ER Model

❹ Extend the BIAN framework to meet PNC requirements

▪ Provides modeled out entities and properties for
each BIAN service domain
❺ Contribute back the delta between PNC requirements
▪ Allows for automated population of swaggers to
ensure standardized modeling and naming and the existing model to help grow, enhance, and
conventions are used across development teams evolve the overall framework

21
Absa (&TCS)
Table of Contents

Context - Absa Introduction & Vision statement

Absa Existing Architecture
BIAN Adopted Architecture
Absa BIAN Journey
Value Delivered
Context
About Absa

Absa is a truly African brand committed to finding local solutions for uniquely local challenges and everything they do is focused on
adding value. To this end Absa offer all clients across the continent a range of retail, business, corporate and investment, and
wealth management solutions as well as ensure a positive impact in all the countries where it operates in.

Vision : To become digital bank of choice.

Primary Drivers for BIAN Adoption

• The aim of the bank is to become the digital bank of choice across the African continent with customer centricity at the core. Absa wanted
to achieve this by ensuring the faster launch of digital products and features for its customers. The bank had a vision to Lego-fy its
banking services by repackaging services into reusable building blocks which would guarantee them success in their digital
transformation journey.
• Decompose existing legacy middleware into API, Microservices.
• Introduce new age digital channels and establish DevOps, CI/CD for faster Time To Market.
Our new Microservices/API platform - Way Forward - Principles
The new platform is not a like-for-like replacement for existing ESB middleware
• Service will not be built to retrofit existing channels.
• Not just a protocol change i.e. SOAP to REST.

The new platform is more than a “gateway”, it provides :-

• Decoupling and abstraction from the core banking and other backend services.
• Standardization and governance via its use of the BIAN Framework.
• Orchestration where it is required.
Vendor applications and in-house developed solutions needs to comply with the BIAN-based Absa standards that have been
adopted when competing for business.

Designed with a Microservices architectural style to :-

• Decouple complex systems from business functions like with SOA (Service-oriented Architecture) but with more service
independence and more resilience.
• Leverage of AGILE and best practice principles coming out of our industry.
The new platform seeks to adopt a standardized approach by implementing ‘common’ architecture principles across the Absa
Regional Operations landscape.
The new platform is designed to decouple back-end solutions so that that a “plug-n-play” approach can be adopted to replacing
back-end applications.
Existing Architecture
New Product Summary
Core banking model: Single point of entry for all channels, Common middleware
Single transaction flowchart driving all ARO countries, Built in Flexibility enabled by plug
and play of core applications by countries independently
without impacting other countries

Unstable Monolith, Time & effort intensive to introduce new

Business features

Fintech SOR 1

SOR 2
CORE
BANKING
SOR 3

Merchants

SOR 4

Third Party
Aggregators

Applications ARO Multiple Integrations Core Banking Integrating

Core
Apps Integrations through with internal applications
Banking
with Core banking multiple languages
BIAN Adopted Architecture
Core banking model:
Single transaction flowchart Sample BIAN APIs
with BIAN API Savings Account API, Party
Reference Data Directory API,
New Product Payment Initiation API, Customer
Event History API, Product Directory
API
SOR 1

C O R E B A N K I NG
Digital
SOR 2
BIAN CORE
API
BANKING
Merchants
SOR 3

Summary
SOR 4
Compliance to BIAN standards enables Lego-fication of Core Banking model with Single
Fintech / Third Party
Aggregators point of entry for all channels, Common middleware driving all ARO countries, Built in
Flexibility enabled by plug and play of core applications by countries independently
without impacting other countries

Secure, Reusable, Standardized enabling cost and effort efficient introduction of

Business features

ARO SINGLE Integrations Integrations through Core Banking Integrating

Applications Core Banking
Apps with Core banking using BIAN API SINGLE BIAN with internal applications
Program Approach
MVP – Current Approach Big Bang Hybrid – Suggested Approach
•Focused on onboarded channel only •Consider all channel needs at once • Consider requirements for existing key
channels and uplift APIs for new
Pros: Pros: requirements on need basis

• Faster TAT (Turn around time) for channels
• Zero wastage
Cons:
• Additional cost due to continuous
engagement with SORs and Channels
• Lack of reusability. Need enhancement
every time
• Zero rework as all requirements analysis Pros:
completed before start of development
• Build right first time
Cons: • Zero or minimal re-work
• Reduce cost for SMEs support
• Can lead to wastage due to un-used APIs • Faster Time to market of channels
• Increase in time to market of new introduction
channels
• Disconnect between business needs and Cons:
solution offered
• Not able to gain competitive advantage • None

• Adopted green field implementation approach to maximize benefits of agile architecture.

• Targeted new Channels to be onboarded first on the new platform followed by transformations of existing channels.
• MVP approach followed for quick onboarding of transactional Chat Banking channel and now we are looking at
analysing existing capabilities of all digital channels.
BIAN Adoption trends & recent experiences
Multiple customers
Speed to Market – Launch products, features, capability faster Few customers
Very Few customers

Business - IT Alignment & Enterprise/ LoB Blueprinting Moving away from ESBs to Standardized APIs and Microservices on Cloud

Application portfolio rationalization to identify gaps, overlaps and misaligned Legacy modernization / Core systems repurposing and moving towards coreless
applications banking

Create DDD based right sized services for any greenfield / brownfield
Match and select vendor solutions/COTS/Fintech for business capabilities implementations

During M&A process to select competing capabilities from the merged

organization Innovation - Customer journey creation / re- imagination

Business - IT alignment
Application portfolio rationalization

Advisory

Legacy/Core modernization,
Enterprise/LoB blueprinting Domain Driven Design, MSA/ API

Implementation

COTS/Fintech selection
Customer Journey creation / re-imagination
The Journey – We started with an execution approach …

TCS BIAN Assets Templates Enablers Best Practices

Pre- work Analyse Align & Adopt

• Understand back end

applications & services in • Understand the business
scope processes in scope- entire
• For BIAN aligned DDD
Activities

• Identify stakeholders – All process flow from channel

to SORs. services, create Service
Post PoC SMEs and reviewers needed URIs & Contracts.
Implementation, for the project. • Collaborate with
stakeholders for thorough • Present to Stakeholders
a detailed • Confirm level of BIAN API for review and signoff
adoption. analysis.
execution • Review Understanding
• Agree on a timeline for
approach was put
execution.
together for the
entire program
Deliverable

• Mapping of existing •
• Detailed proposal (scope, BIAN based service
services to DDD based specifications along with
execution plan, teams
BIAN service Domains and URIs and contracts .
involved and timeline)
create service catalog.
Identified the right API Adoption pattern & delivered artefacts…
API Align Service Align Service * Align Service Domain, “Helped consolidate multiple
adoption Domain & URI Domain, URI and URI and Control record services providing same capabilities.
pattern Control record as well as BIAN BOM
Eg. 20 payment services were
Channel API to BIAN API to consolidated to 4”
Impact Consumers will Request response Entire data model has to SOR service mapping
have to be made will have to be be aligned with BIAN.
aware of changes changed, mapping
in the URI. dictionary to be
maintained for “Helped identify reuse across
data elements.
channels “ Mapping multiple
channels to BIAN API

Increasing Level of alignment

“Helped create future ready
Channel APIs to BIAN
* Pattern adopted for Absa services, channel agnostic
URI mapping services “

BIAN Operation & BIAN APIs & request response

Analyze & Map to
BIAN Service Domains
BIAN Operations “Helped provide the right level of
BIAN Payload Level
Level Mapping
Mapping abstraction thereby ensuring SOR mapping to SOR services
changes are not impacting the request / response
channels.”
Handling few challenges faced during adoption….
BIAN provided Payment initiation semantic API has this URI for initiation operation-
/payment-initiation/{sd-reference-id}/payment-initiation-transaction/initiation
Challenges
While implementing for Absa we added multiple sub qualifiers for the various business scenarios as
shown
/v1/payment-initiation/payment-initiation-transaction/ fund-transfers/domestic/initiation
• BIAN semantic APIs will serve as reference APIs hence during
/v1/payment-initiation/payment-initiation-transaction/ fund-transfers/international/initiation implementation journey, for all the needs specific to banks we need to
/v1/payment-initiation/payment-initiation-transaction/ bill-payments/initiation introduce the right sub-qualifiers in the service operations so that they are
discrete and non-overlapping and rightly mirror the banks context.
• Most of the Bank’s data elements were mapped to BIAN BOM, for the ones
which were not available in BIAN BOM were added and Bank’s own custom
data model extending BIAN BOM was created. This exercise needs a lot of
domain expertise as well as in-depth knowledge of BIAN BOM. It is quiet
time consuming, so we have created a framework to automate some
aspects of this data mapping exercise.

• Synchronizing with latest BIAN releases have to follow a well -defined

process so that there is no impact to execution timeline and also ensures
the latest BIAN updates are incorporated.

Sample updates in BIAN version 9

Service Domain Name Changes

• Fraud AML/Resolution => Fraud Resolution
• Credit/Charge Card => Credit Card
• Customer Product/Service Eligibility => Customer Product and Service Eligibility
• Document Services => Document Library
• Party Data Management => Legal Entity Directory
• Customer Reference Data Management => Party Reference Data Directory
• Contact Dialogue => Session Dialogue
Critical success factors that helped ….
Collaboration with all stakeholders like
Business team, technology team,
operations team and EA team.
Roadmap & right execution approach –start
with PoC or MVP for single LoB or entire LoB
before scaling at a larger level.
Critical
BIAN implementation requires a
success thorough knowledge of BIAN framework
Sample feedback shared with BIAN
For a business scenario, we have a situation to handle Memo for
transaction processing within a Current/Savings account service
domain. We have not come across memo handling capability. Can it
be added?
In BQ Association instance record of Party reference Data directory
SD, we have 'Proxy/Representative/Power of Attorney Reference'
element to capture associated reference details . Can we extend it to
capture address, email etc.
We need a field in credit card control record to store reference to 3rd Party
who acquired this customer. Can this be added?
TCS BIAN

factors so we deploy a team with prior

experience that regularly connects with
Adoption
Assessment
(API)
TCS Data TCS Product
BIAN. mapping specific
Automation reference
framework architectures

TCS Assets &

Accelerate adoption by usage of Enablers
templates, assets, automation frameworks
TCS BIAN
etc. TCS API
Business
mapping
scenario
template
custommodel

TCS BIAN /
DDD expertise
Delivered the below benefits to the bank…
Standardization & Scalability
Speed To Market Increased revenue • Standardization of architecture capability definition &
• Quicker information model,
• Capability to leverage ecosystem
Integration due to • Leaner application stack, Optimized calls to the core
players leading to new revenue
standardization. • Discrete Business functionalities driven by Modular
stream
• Plug & play service domain design
• Seamlessly integrate with fintech and
integration • BIAN aligned APIs with clarity of purpose
partners to deliver new features &
capabilities. • Scalability and availability as per business needs
products
• Avoidance of • Enabled Cloud readiness
Vendor –lock in.
• API catalog re-
used across the
enterprise leading
to quicker
development
• CI/CD to improve
TAT
• Enabled API
Marketplace
business model

Cost reduction & Reuse Customer satisfaction

• API re-use across the enterprise. • Improved customer
• Cost reduction due to reduced API satisfaction due to quicker
footprint. launch of products.
28 Copyright BIAN 2020 | Banking Industry Architecture Network
Open Banking Reference Architecture

Channel Applications TPP Applications

Common External API Gateway Outside of

Capabilities the Bank
Open Banking API s & Services

UXDesign Product Payment Developer Portal Sandbox Open

Banking
Account Customer Authentication TPP Management Directories
DevOps
ATM Branch Consent Management Metrics / Reporting / Audit
I dentity
Security Registries
I nternal API Gateway
Data & AI Business Services Business
Partners
Customer Customer Servicing
DataCache Current Savings Position Credit Product
Reference Position
Data Account Account Keeping Card Directory Mandate
Regulatory
Governance Bodies
Core Applications and Systems of Record
Cloud Payment
I nfrastructure Customer Deposit Credit Card Product Networks

IBM Global Solution Center, Dallas / © 2020 IBM Corporation 36

Open Banking APIs – Products and Accounts

Business Scenarios or Apps

Account Account Account Product
• Bank plays the TPP role for customers Monitoring Aggregation Porting Comparison
• Innovative use cases

Third Party Provider (TPP)

Open Banking APIs

• Orchestrate multiple Business Services Products
• Transform to target messages
Accounts
• Expose target endpoints

Business Services
Customer
• Based on BIAN service domains Product/ Credit /
Customer Current Savings Position Product Servicing
• Microservices implementation Position Service Account Charge
Account Keeping Card Directory Mandate
• Cache for performance (CQRS) Eligibility

Cache Layer

Systems of Record(SoRs) SoR

SoR SoR SoR
Credit
Customer Deposit Product
Card

IBM Global Solution Center, Dallas / © 2020 IBM Corporation 37

Account Aggregation – Better Customer Insights

Account Aggregation Service & API

Account
• Customer position aggregated from multiple Aggregation
financial institutions
• Used by channel applications

Retrieve customerposition

BIAN Based Business Services Customer

• Customer Position maintains … Customer Customer Customer Customer
Behavioral Behavior Event Product / Customer
• Customer insights from analytical models Position Service Offer
Insights Models History
• Offers to customer Eligibility
Customer
Position

Consent

Account Access to other banks

• Account Access to multiple banks
• Using FinTech offering to simply the Account Account Account
Access Access Access
Account Aggregation
integration Service by FinTech
Bank 1 Bank 2 Bank N

IBM Global Solution Center, Dallas / © 2020 IBM Corporation 38

BIAN Based APIs and Microservices

Control Record

Behavior Behavior Behavior

Qualifier Qualifier Qualifier

Sub Qualifier Sub Qualifier Sub Qualifier

Swagger Models API Developer Portal

BIAN Service Domains 3 UML Models for 4 API Design Models Generate &
Messages BIAN SDs + Message publishAPIs

UML Models for API First (B2B/B2C & A2A)

1
BIAN Service Domains

UML Models for Microservices First (A2A)

2
Conceptual (BOM)
UML Models for Microservices Models Generate &
Physical Models BIAN SDs + Physical deploy
Industry Models 5
ISO 20022 6
Service Models Container Environment
Roll Your Own (OpenShift)

IBM Global Solution Center, Dallas / © 2020 IBM Corporation

39
BIAN and Domain Driven Design (DDD)

IBM Global Solution Center, Dallas / © 2020 IBM Corporation 40

BIAN Service Landscape – Matrix vs. Value Chain Layout
Reference Data
Party
Party Data Management
Customer Profile
External Agency
Information Provider Admin
Syndicate Management
Interbank Relationship Mgmt
Correspondent Bank Rel Mgmt
Correspondent Bank Data Mgmt
Sub Custodian Agreement
Product Service Agency
Product Broker Agreement
Contractor/Supplier Agreement
Market Data
Information Provider Operation
Market Information Mgmt
Financial MarketAnalysis
Financial MarketResearch
Quant Model
Market Data Switch Adm Market
Data Switch Ops Financial Instr
Ref DataMgmt
Counterparty Administration
Public Reference Data Mgmt
Location Data Management
ProductManagement
Product Design
Product Deployment
Product Training
Product Quality Assurance
Discount Pricing
Product Directory
Special Pricing Conditions
IBM Global Solution Center, Dallas / © 2020 IBM Corporation
Sales &Service
Channel Specific
Branch Location Management
Contact Center Management Business Development
Branch Network Mgmt
E-Branch Management
Advanced Voice Services Mgmt
AT M Network Management
Contact Center Operations
Branch Location Operations
E-Branch Operations
Advanced Voice Services Ops
AT M Network Operations
Branch Currency Management
Branch Currency Distribution
Product Inventory Item Mgmt
Product Inventory Distribution
Card Terminal
Card T erminal Operation
Cross Channel
Party Authentication
Transaction Authorization
Point of Service Servicing
Expert Sales Support
Event History
Servicing Activity Analysis
Contact Routing
Contact Dialogue
Interactive Help Contact
Handler
Customer Workbench
Customer Prod./Service Eligibility
Customer Event History Custmer
Reference Data Mgmt Customer
BIAN Service Landscape V8.0
Marketing
Loans&Deposits
Brand Management
Advertising
Promotional Events
Prospect Campaign Mgmt
Prospect Campaign Design
Corporate Current Account
Customer Campaign Mgmt
Customer Campaign Design
Customer Surveys
Sales
Prospect Campaign Execution
Party Lifecycle Management
Lead/Opportunity Management
Customer Campaign Execution
Customer Offer
Sales Planning
Underwriting Commission
Agreement Commissions
Product Matching Product
Product Sales Support
Sales Product
ConsumerServices
Corporate T rustServices
Customer Mgmt
Customer Relationship Mgmt
Bank Drafts & Trvl. Checks
Customer Agreement
Sales Product Agreement
Customer Access Entitlement
Consumer Advisory Services
Customer Behavioral Insights
Customer Credit Rating Account
Recovery
Proposition
Servicing
Financial Message Analysis
Servicing Issue
Customer CaseManagement
Case Root Cause Analysis
Customer Case
Card Case
Servicing Order
Payment Order
Servicing Mandate
Card F inancial Settlement
Collateral Admin.
Collateral AllocationMgnt
Collateral Asset Administration
Matrix layout
Operations &Execution
Product Specificfulfillment
Loan
Leasing
Current Account
Deposit Account
Consumer Loan
Corporate Loan
Corporate Deposits
Corporate Lease
Merchandising Loan
Mortgage Loan
Fiduciary Agreement
Savings Account
Cards
Credit/Charge Card
Card Authorization
Card Capture
Card Billing &Payments
Merchant Relations
Merchant Acquiring
Card Network Participant
Payment Initiation
Currency Exchange
Brokered Product
Consumer Investments
Customer T axHandling
Trust Services
Service Product
Cross ProductOperations
Payments
Payments Execution
Financial Gateway
Correspondent Bank
Cheque Processing
Central Cash Handling
ACH F ulfillment Card
eCommerce
Card Clearing
Collections
Business Areas
Investment
Management
Investment Portfolio Planning
Investment Portfolio Analysis
Investment Portfolio Mgmt
Investment Account
eT rading Workbench
WholesaleTrading
Trading Book Oversight
Trading Models
Dealer Workbench
Quote Management
Suitbility Checking
Credit Risk Operations
Market Making
ECM/DCM
Program T rading Traded
Position Management
Market Order Market
Order Execution
Market Operations
Mutual F und Administration
Hedge F und Administration
Unit T rustAdministration Trade
Confirmation Matching Order
Allocation
Settlement Obligation Mgmt.
Securities Dlvry & Receipt Mgmt
Securities F ails Processing
Trade/Price Reporting
Custody Administration
Corporate Events
Financial Instrument Valuation
Account Management Operational Services
Position Keeping Securities
Position Keeping Reward
Points Account Accounts
Receivable Account
Reconciliation Counterparty
Risk Position Management
Fraud Evaluation
Fraud Decisioning
Transaction Engine
Product Combination
Customer Position
Risk &
Compliance
Bank Portfolio &
Trade Banking Treasury
Corporate T reasury Analysis
Letter ofCredit
Corporate T reasury Asset
Bank Guarantee
Securitization
Trade Finance
Asset & Liability Management
Credit Management
Bank Portfolio Analysis Bank
Credit F acility
Portfolio Administration Stock
Project Finance
Lending/Repos
Limit & Exposure Management
Syndicated Loan
Models
Cash Mgmt& Account Svs
Market Risk Models
Direct Debit Mandate
Direct Debit Cheque
Financial Inst.Valuation Models
Gap Analysis
Lock Box Factoring
Credit Risk Models
Liquidity Risk Models
Corporate Financing Economic Capital
& AdvisoryServices Business RiskModels
Corporate F inance Customer Behavior Models
Fraud Models Credit/Margin
M&AAdvisory
Management Production Risk
Corporate T axAdvisory
Models Operational Risk
Public Offering
Models Contribution Models
Private Placement
BusinessAnalysis
Segment Direction
Product Portfolio
Customer Portfolio
Branch Portfolio
Channel Portfolio
Competitor Analysis
Market Research Market
Analysis Contribution
Analysis
Regulations&
Compliance
Guideline Compliance
Regulatory Compliance
Issued Device Admin
Compliance Reporting
Issued Device Tracking
Regulatory Reporting
Disbursement
Fraud Resolution
Open Item Management
F inancial Accounting
Leasing Item Administration
Customer Billing
Rewards Points Awards &Red.
Channel Activity Analysis
Channel Activity History Card T
ransaction Switch Delinquent
Account Handling Card
Collections
Business Support
IT Management
IT Systems Direction IT
Stds &Guidelines
Systems Administration
Development Environment Enterprise T ax Administration
Development
Production Release
System Deployment
Systems Operations
Platform Operations
Systems HelpDesk
Systems Assurance
Internal Network Operation
Non IT andHR
Enterprise Services
Legal Compliance
Internal Audit
Security Advisory
Security Assurance
Approved Supplier Directory
Procurement
Company Billing &Payments
FixedAsset Register
Buildings, Equipment Knowledge Exchange
and Facilities
Corporate Relations
Property Portfolio
Site Operations Site
Administration
Equipment Administration
Equipment Maintenance
Utilities Administration
Building Maintenance
BusinessCommandBusinessDirection
Corporate Strategy
&Control
Organizational Direction Business
Unit F inancial Analysis Business
Unit Financial Ops Business Unit
Accounting
Business UnitDirection
Business Unit Management Document Mgmt&
Service Domains
Finance
F inancial Statements
Financial Control
F inancial Compliance
System
HumanResource
Management
HR Direction
Employee Assignment
Employee Data Management
Employee/Contractor Contract
Employee Certification
Employee Evaluation
Employee Payroll &Incentives
Travel & Expenses
Employee Access
Employee Benefits
Workforce Training
Recruitment
Knowledge &IP
Management
Management Manual
Intellectual Property Portfolio
Corporate Communications
Corporate Alliance/Stakeholder
Corporate Relationship
Regulatory & Legal Authority
Investor Relations
Corporate Policies
Product & Service Direction
Business Architecture
Continuity Planning
Archive
Document Services
Archive Services
Correspondence
BusinessDirection
Corpo rate Services Bu siness Directio n
Legal Compliance
Internal Audit
Security Advisory
Security Assurance Product & Service Direction
Continuity Planning
Corporate
Rel ations
Investor Relations
Corporate Relationship
Corp Alliance/Stakeholder
Corporate Communications
ResourceManagement
Unit Management
Business Unit Direction Business Unit Financial Ops
Business Unit ManagementBusiness Unit Accounting
Business Unit FinAnalysis
Human Resources
Recruitment
Employee Assignment
Employee Evaluation
Employee Certification Travel & Expenses
Empl/Contractor Contract Employee Access
Employee Data Mgmt
Platform Operations
Systems Assurance Internal Network Operation System
Deployment Platform Operations
Systems Operations
Buildings & Equipment
Fixed Asset Register
Procurement
Equipment Administration Building Maintenance
Equipment Maintenance SiteAdministration
IP & Know ledge
Intellectual Property Port
Management Manual
Business Architecture
Knowledge Exchange
Business Domains
Draft Value Chain Layout – V8.0
Finance& RiskManagement Group Treasury Market Risk Regul ati ory
Corporate Policies Compli ance
Corporate Strategy Financial Control Operational Risk Credit Risk
Corporate Treasury Corporate Credit/Margin Management Regulatory & Legal Authority
Organizational Direction Treasury Analysis Bank Gap Analysis Regulatory Compliance
Financial Control CompanyBilling &Payments Business Risk Models Credit Management
Financial Compliance Approved Supplier Directory Operational Risk Models Portfolio Admin Limit & Exposure Mgmt Counterparty Risk Regulatory Reporting Guideline
HRDirection
Financial Statements Enterprise Tax Admin Production RiskModels Bank Portfolio Analysis Position Management Fraud Resolution
Compliance Compliance
IT SystemsDirection
Asset Securitization Economic Capital
Reporting
Asset &Liability Mgmt
Property Portfolio
Operations Products Customers Channels
Clearing & Settlement(Payments)
Market Operations Market Trading Party Reference Informtn. Prov iders
Settlement Obligation Mgmt.Cheque Processing Order Party Data Management Public Reference Data Mgmt
Allocation ACH Fulfillment
Trading Book Oversight Credit Risk Operations Traded Position Mgmt QuoteManagement
Custmer RefData Mgmt Financial Instr Ref Data Mgmt
Trade Confirmation Matching Securities Fails Processing Market Order Market Making Location DataManagement Financial MarketResearch
Corresp.Bank Data Mgmt Transaction Engine
Securities Dlvry &Rcpt MgmtFinancial Inst Valuation Market Order Execution Program Trading Financial Market Analysis
Counterparty Administration Payment Order
Correspondent Bank Payments Execution
Trade/Price Reporting Corporate Events Dealer Workbench Stock Lending/Repos
Inv estment Svs
Consumer Investments
MarketInformation Mgmt Market
Data Switch Ops Information
Card eCommerceGateway Card Clearing Card Financial Suitbility Checking Investment Account eTrading Workbench Provider Ops
Settlement
Investment Portfolio Planning
Cross Channel
Investment Portfolio Analysis
Custody, Collateral & Documents Investment Products Advisory Services Investment Portfolio Mgmt Customer Workbench
Custody Administration Collections Collateral Allocation Contact Handler Contact
ECM/DCM Unit Trust Administration Private Placement
M&AAdvisory Corporate Tax Advisory Routing Contact
MgntDocument Services Collateral Asset Admin Archive
Hedge Fund Administration Corporate Finance Consumer Advisory Services
Relation ship Mgmt
Dialogue Customer
Services Customer Relationship Mgmt
Profile Party
Public Offering Mutual Fund Administration Customer Behavioral Insights
Account Recovery
Customer Credit Rating
Authentication
Empl Payroll &Incentives Customer Access Entitlement
Accounting Services Trade Banking Customer Agreement
Employee Benefits Sales Product Agreement Cust
Transaction Authorization
WorkforceTraining
Position Keeping Customer Tax Handling Trade Finance Letter ofCredit Channel Activity History
Prod./Service Eligibility
Customer Position Commissions Bank Guarantee Bank Drafts& Trvl.Checks
Accounts Receivable Fraud Evaluation
Loans & Deposits Customer Proposition Channel Specific
Loan Consumer Loan
Customer Event History AT M NetworkOperations
Financial Accounting Fraud Decisioning
Reward Points Account Account Reconciliation Corporate Loan MortgageLoan
Branch Location Operations
Securities Position Keeping
Corporate Banking Sal es Advanced Voice Svs Ops E-
Corporate Lease Merchandising Loan Cust Campaign Execution Branch Operations Financial
Corporate Current Account Direct Debit Mandate Cash Mgmt &
Gateway
Operational Services Leasing Item Administration Leasing
Account Svs Direct Debit
Lead/Opportunity Mgmt
Card Terminal Admin. Card
Prospect Campaign Exec
Customer Billing ProductCombination Syndicated Loan Deposit Account
Corporate Trust Services Cheque Lock Box Credit Facility Party Lifecycle Management Terminal Operation
Fiduciary Agreement Savings Account
Disbursement RwdPoints Awards &Red. Factoring Product Sales Support Product
Open Item Management Issued Device Admin Underwriting Corporate Deposits Expert Sales Support Product Serv icing
Systems Help Desk
Project Finance Matching Contact Center Operations
Delinquent Account Handling Issued Device Tracking Card
Customer Offer Spec/Discount Point of Service
Collections Card Transaction Switch
Pricing Conds Interactive Help
External Agency Cards Consumer Banking Servicing Issue
Utilities Administration Customer Orders Servicing Event History
Credit/Charge Card MerchantRelations Current Account TrustServices
Interbank Relationship MgmtProductBroker Agreement Servicing Order
Site Operations
Card Authorization MerchantAcquiring Brokered Product Payment Initiation
Corresp Bank Rel MgmtSub Custodian Agreement Servicing Mandate Distribution
Card Capture Card Network Participant Service Product Currency Exchange Customer Case Mgmt Product Inventory Distribution
Syndicate Management CommissionAgreement
Customer Case Branch Currency Distribution
Product Service Agency Contractor/Supplier Agmt Card Billing &Payments Sales Product
Card Case Correspondence
BusinessDevelopment Marketing & Development Ch annel Management
Business Development Market Research Channel Portfolio Branch Location Mgmt
Models & Analytics Quant Model Solution Devel. Product Management Customer Portfolio Market Analysis
Branch Portfolio AT M NetworkMgmt ContactCenter
Contribution Models Trading Models Customer Behavior IT Stds & Guidelines Product Portfolio Product Quality Assurance Management Branch NetworkMgmt
Contribution Analysis Competitor Analysis
Models Fin Inst.Valuation Models Systems Administration Product Design Product Training Segment Direction Customer Campaign Mgmt Servicing Activity Analysis Advanced Voice Svs Mgmt
Credit Risk Models Market RiskModels Development Environment Production Release Case Root Cause Analysis Brand Management Customer Campaign Design Financial Message Analysis E-Branch Management
Fraud Models Liquidity Risk Models System Development Product Deployment Product Directory Sales Planning Prospect Campaign Mgmt Channel Activity Analysis Product Inventory Item Mgmt
Advertising Prospect Campaign Design Information Provider Admin Central Cash Handling MarketData
Promotional Events Customer Surveys Switch Adm Branch Currency Mgmt
Value Chain layout
41
BIAN Value Chain Landscape and Scopes of APIs

Business Areas:
• Operations – cross-product operations
• Products – synergistic product / service combinations
• Customers – integrating customer insights & preferences
• Channels - governing access – both at the contact & servicing mandate / relationship levels

Business
Finance &RiskManagement
Direction
The BIAN Service Landscape V8.0
Custome
r
Resource
A2A
Management
Operations Products Customers Channels B2C

Business Development 3rd Party

B2B Provider B2B2C

IBM Global Solution Center, Dallas / © 2020 IBM Corporation

43
Channels – External Access Control

Channels
Customer
Retrieve
Reference
DataMgmt Party Issued Issued
Evaluate
Authenti- Retrieve
Device Retrieve Device
Customer cation Admin. Tracking
Retrieve
Access
Entitlement
Customer Contact
Provide
Retrieve
Prod/Svs Routing
Retrieve Customer Eligibility
Profile
Record

Customer Execute
E-Branch Initiate Contact Request Broker Retrievet
Servicing
Workbench Operations Handler Agreement Mandate
Initiate

Pointof
Service
Initiate

Contact Customer Transaction

Dialogue
Request
Agreement
Evaluate Authori-
Initiate zation
Servicing
Key real-time Capture Capture Capture Order
“orchestrators” Current
for the contact Execute
Account
Channel Servicing Customer
Activity Event Event Initiate
Initiate Initiate
History History History

Retrieve Fraud Fraud Fraud

Channel
Activity Evaluation Diagnosis Resolution
Execute
Analysis Retrieve

Retrieve Retrieve
Retrieve

Customer Fraud Fraud

Behavior
Insights Models
Models
Capture Capture Capture

IBM Global Solution Center, Dallas / © 2020 IBM Corporation

44
Customers – Positions and Insights

Customers

Consolidated financial
Customer
position (cash flows,
holdings
collateral, credit)
Historical analysis
Financial
Advisory
Investment Services
Portfolio
Management Custody Customer
Admin. Position Party Data Life-time relationship
Collateral Management
Asset Collateral Customer development history
Admin. Allocation Reference
Management DataMgmt.
and plan

Customer Customer
Relationship history Credit Relationship Party Life-
and maintained and Rating Management cycle
Management
developed insights Customer
Insights Customer
Customer Broker
Behavior Agreement
Customer Agreement
Models Customer
Event Prod/Service Servicing
Mandate Reward
History Eligibility Points
Customer Customer
Access Profile
Product/service Entitlement Bank and 3rd Party
usage – current and contracts and
desired mandates

IBM Global Solution Center, Dallas / © 2020 IBM Corporation

45
Value Chain Decoupling and Integration – New Business Models

Monolithic to Vertically Integrated Bank

Production Distribution
De-coupled Flexible Model

Operations Products API Customers Channels API

Operations Products API Customers Channels API

Production Distribution
3rd Party

IBM Global Solution Center, Dallas / © 2020 IBM Corporation 46

 Contents
1. Open Banking Practice
2. Panoramic Banking Planning
3. Scenario Twins
4. Ecosystem Security

15
1
5
 Panoramic Banking Concept and Vision

Panorama banking means that bank builds platform-based ecosystem around the needs of customer life cycle and production cycle,
sharing brand, channel, customer, technology and other resources with business partners, uses data intelligence dynamically perceiving
customer requirements, provids integrated financial and non-financial products and services, so as to create value adding and achieve
best experience for customers

Facing "all users", running through "all time", providing "all services" and realizing "all links"

All Food and Beverage

C Side B Side G Side F Side

Users Service Education Culture Retail Medical Car Smart Financial

...
Training Tourism Industry Industry Manufacturing City Industry

Dynamically Awareness
A variety of scenarios associated with different timing points throughout the user's full life cycle
All Purchase Realty Custom
Home Home Appliance Domestic
...

Intelligent Guidance
Property Decoration Purchase Service Service Travel
Time
Procurement Production Sales Warehousing Logistics After-sales ...
... All
Links
Payment and
Catering Service Tourism Products
All Settlement
Mortgage Consumer Finance Real Estate Brokerage

Accurately Offering
Services Business Loans Transaction Banking ... Investment and
Financing Consultat ion Legal Advice ...
Financial Services Non-financial Services
Financial and non-financial services that meet the needs of users in different scenarios throughout their life cycle

Intelligent Core

Panoramic Banking

40
 Panoramic Banking Features

1 2 3

User Based on Target on

Experience Trust Value
Driven Rebuilding Co-creation

• Focus on understanding and
solving user’s pain points
• Integrate internal and external
resources to meet user needs,
provide quality services and
improve user experience
• Improve the overall digital level
of related parties
• Build digital credit system, reduce
the information asymmetry
between customer and financial
institution and build trust of them
• Open capabilities, enable ecosystem
partners achieve win-win
cooperation
• Aims on value adding for users and
partners, instead of playing zero-
sum game

41
 Panoramic Banking Basic Value Point

Traditional Banking Business Remodelling Grid Panoramic Banking

• Realized value: Customers buy
financial products or make
According to the combination of IQ and EQ, business remodeling grid has four • Realized value: Customers
main "value Spaces" production and consume life
financial transactions
EQ cycle serving
• The bank sells products or
services to customers as an • Start from customer needs,
independent distribution channel. constructs financial and non-
Such banks typically have high Open
financial scenarios to support
cost/revenue ratios and are prone Partnership Panoramic
to become infrastructure if lacking Ecosystem Banking ecosystem parties to interact.
scale advantages Reduce the information
asymmetry of parties and promote
Closed Bundled win-win cooperation. Provide

User Experience
Partnership
Ecosystem
Banking intelligent services, enable
Digital Banking effic6ient interaction and improves
• Realized value: Customers buy
Digital profitability
Product Banking
financial products or make and
financial transactions Service

• Most banks are in the process of Traditional Bundled Banking

transforming from traditional Banking
banking to digital banking. They Product • Realized value: Customers achieve
use digitalization to upgrade their financial goals
traditional business model and • Build open banking capabilities,
enhance user experience. Banks in Intelligent IQ integrate fintech products, and provide
Traditional Distribution Data-driven Distribution
this range are still product Service
Participation customers with better services. With the
distribution channels, profits have Intelligence progress of technology, the distribution
begun to shrink will be transformed from "data-driven"
into "intelligent participation"

42
 Industry Co-construction and Co-prosperity

Industry Research
Regulators Association Institutions • The proposition of the Open
Financial Union
• BIAN • University and academy
Centre Bank State Supervisor • Internet Engineering Task Force • Industry Institution • Pan-financial mutual assistance
platform
• OpenID Foundation • Enterprise Research
Local Supervisor Municipal Financial • ... • ... • Gather, create and share good
Office
resources
• Create value for users and related
parties

• The main services of the Open

The Open Financial Union Financial Union
• Technology sector: Promote the
sharing of open banking platforms
Members of the such as API Echange and technical
Organization Third Party Partner
platforms
Banks and other financial institutions • Business sector: Promote extensive
app platform app platform cooperation among members in
connection
various fields of business operation
Bank Insurance Securities Fund ... app platform app platform
• Ecosystem sector: Realize the
Internet apps Fintech app sharing of ecosystem operation
capability, enhance ecosystem
vitality, and realize scale advantage
Bank User User consent, multi-factor authentication
Direct access By third party access

43
 Panoramic Banking Construction Framework

Panoramic Banking
Construction Framework

Panoramic
Banking Planning Planning
Business Mode Roadmap Planning Technology Framework

Scenario Twins Design

Business Scenario Capability Library
Co-operation Platform
Model Banking, Technology, Ecosystem Business
Technology
Transforma
Innovation Implementation tion
Biz Scenario
APIX Platform Dev API Development
Construction

Ecosystem Security
Measurement Operation
Security
TPP Management Platform Management
Management

Adopting a set of completed and standardized methods to enhance

panoramic banking core competitive capability.
44
 Contents
1. Open Banking Practice
2. Panoramic Banking Planning
3. Scenario Twins
4. Ecosystem Security

21
2
1
 Scenario Twins

Scenario twins implementation includes scenario modeling, user journey design, open API design and capability
construction.

By structuring the scenario information

such as actor, action, objective
environment and service platform etc., the
basic elements are standardized and the
scenario is modeled

Design user journey template base on

the model, constructs and normalizes
the user journey data to twins the user
activity in real world

Carry out semantic decomposition of user

journey supporting services to make open
API requirement, then develop APIs,
forming the panoramic banking capability

46
 Panoramic Banking Technic Combination

1 User Journey Design

Based on BIAN standard, introduces the concept of user
journey design, expands the ser vice domain and
business capability model, describes the scenario twins.
2 API Semantic Specification
With the help of BIAN semantic API specification,
adapts to Chinese local requirements and creates the
API design specification.
3 API Technical Specification
Using OPENAPI standard and RESTful API best
practices, creates API technical specification.

4 Capability Library
Be compatible with the Commercial Bank Application
Program Interface Security Management Specification
issued in 2020, builds panoramic banking capability
directory.

5 Tools and Development Method

Swagger Editor tool is used to define API and
generate microservice framework code. DevOps
pipeline is used to standardize the process of
design, development, testing and production.

47
 User Journey Model
Service demand comes from customer's activities in
ecosystem. The activities are not totally alone, some
of them are closely related with each other even
when they belong to different industries. To make
the service more smart and pleasant to customer,
User Journey the service provider should not care only about the
activities themselves, but also the relationship and
Customer the environment of the activities
d
Deman

Methods & Tools

(Human Being or Thing)
Servicing Context The information of the linked activities to
Journey, Activity, Action and Environment accomplish a goal and their environmental
a
Dat

Servicing Capabilities information assembly is user journey.

e
Servic

Banking With user journey information, the bank could get

Fintech Eco-Industry
(BIAN) deep insight of customer, then could possibly serve
the personalized, contextual demand.
User Journey Model is base on User Journey Map
and is enhanced with completed information. It is
the structured information mirroring the customer's
behavior and its background in real world.

48
 User Journey Map
Industry Travel Bank Retail

User
Journey Travel Journey (context: Travel Itinerary, Budget, Social Event)

Foreign
User Book Travel Travel Shopping Travel Reverse FX
Task Exchange
Anna
User
"I want a Action #1 #2 #3 #4 #5 #6
Seamless
Travel and Action
Context
shopping
experience
abroad" Touch
Point
As a sales of a big
firm. Anna travels
Travel agency app Travel agency app
periodically. She Travel agency app
Or via bank api
Bank app Merchant o2o Bank app
via tax api
Bank app

manages work life

balance by making User
H $ $ R H $
the most pleasant Achievement
experience each stop
of the way. Travel Wow, I got my
Frustrated, shopping Wow, bank
should not be most wanted bag
receipts should be automatically
in 50% discount in Wow, bank helped
stressful experience. Wow, only Wow, saved a
suggested mall on mitigate paper-less and convert excess
spend 15min lot of exchange foreign currency
User finish all fee without wasting potential FX risks automated tax
refund for me for me at
shopping time.
User Persona Experience booking seamlessly optimal rate

Expectation
49
 BIAN SD Extention for User Journey

50
 BIAN BOM Extention for User Journey

51
 API Library

Banking Technology Ecosystem

t
Transpor
e
Insuranc
t
Paymen

Commer
)
Security

Pay Tech

d
Rewar
s
Analysi
FX Ccy

t
Mgm

l
Trave
t
Inves

y
Notif

d
Clou

e
Estat
n
Loa

r
Info

n
Chai
k
Bloc
Acc

Data

R
OC

Real
.
..

I
A

.
..
.
..

c e
Banking: Traditional Banking product and
Classify align with current business line
Service

Technology: Not relate to banking directly, Focus on new technology, include OCR, Face
base on digital technology, aims to improve Recognition, Block Chain, Big Data, Cloud etc.
performance

Eyes on ecosystem, such as Transport, Real

Ecosystem: Not belongs to banking and Estate, Food, E-commerce, Logistic etc.
finance serving ecosystem

52
 INTRODUCTION

The Red Hat Journey

Examine considerations for the technical implementation of the

BIAN standard needed for production applications.

Q1: Can we interpret the BIAN Q2: What is the ideal technical Q3: What does a community
model? architecture? need?

test
5
3
 CONFIDENTIAL Designator

Answering Q1: Can we Interpret the BIAN Model?

5
4
 EXPLORING THIS NEW APPROACH TO APPLICATION DEVELOPMENT

BIAN in context of Red Hat enterprise open source

• Red Hat is used for:

○ mission critical applications
○ supporting services-based communications
○ highly distributed & automated production environments
•BIAN model design ensures:
○ partitions are generic (while varying in their detail of implementation)
○ ensuring standardized definition for distinctive roles for each functional module
•Conclusion: Red Hat’s open modular platform can support the what is needed for
BIAN-based application development and execution

Business As Usual – activity seen as predefined business Business As Unusual – activity as collectionof
processes/workflows that are automated specialist capabilities linked in a looselycoupled
network
Business activity is viewed as a series of linked
decisions and actions…
Traditional Business
ProcessBased Shared Database
Component
Model Model Shared
Message
Vocabulary

4
…the connections employ a common business
…and the design usually assumes access to a common vocabulary, each ‘encapsulates’ its own processing
‘shared’ view of all processing data data
 EXPLORING THIS NEW APPROACH TO APPLICATION DEVELOPMENT

Open specification ⇨ open source collaboration ⇨ enterprise

5
6 Visit https://www.redhat.com/en/about/open-source-program-office/contributions for details on Red Hat’s community involvement, which spans span software foundations,
operating systems, containers, application services and identity, security, developer tools, storage and compute, desktop, and operations
 EXPLORING THIS NEW APPROACH FOR AN OPEN SOURCE DEVELOPMENTMODEL

Industrialized financial services business modules & ecosystem

“Upstream”
BIAN
FinServ
marketplace

5
7 Visit https://www.redhat.com/en/about/open-source-program-office/contributions for details on Red Hat’s community involvement, which spans span software foundations,
operating systems, containers, application services and identity, security, developer tools, storage and compute, desktop, and operations
 CAN WE INTERPRET THE BIANMODEL

What is the role of the bank and providers in response to natural disaster
A BIAN perspective

1 2

Disaster Immediate Re-establish Short Term Recovery Back to a

Readiness Assistance Access Actions Arrangement New Normal

7
CAN WE INTERPRET THE BIANMODEL

Modeling the story with BIAN service domains

 CAN WE INTERPRET THE BIANMODEL

Modeling the story with BIAN service domains ..

Re-establish Access

9
 CAN WE INTERPRET THE BIANMODEL

Extending the development team with partners

Scenario: Customer subscribes to building support service, subsequently a builder submits their invoice
Bank
Contact Session Customer Information
Correspon-
dence
Current
Account
Payment
Order
Payment
Execution
Position
Keeping
Servicing
Order Prod/Service
Brokered
Product Provider TPP processing
Handler Dialogue Eligibility Operation
Update
Notify
Register customer
product usage Initiate
Notify TPPservice Register new customer details,
Sendmessageto send out service contact
external agency
details/request

Retriev Initiate

e
Get request from
Confirm Customer still
TPP
Check customer
still registered
subscribed

Initiate
Initiate Get request from Submit invoice for customer
Initiate (Bill Pay)
Initiate a “Bill Pay”
TPP payment
Send an alert to the request tothe current
customer account holder (the
customer)

Initiate Customer logs in to process bill pay

Exchan
Customer logs in ge request. Notification is sent to
to respond to alert Custo(mBielrPaacyc)esses merchant when bill pay approved by
Initiate and approves Bill Pay customer. (Two mechanismsare
Notify
Confirmation message (Bill Pay) shown – one option is
send tomerchant as Brokered Product has Initiate correspondence – in red, the other
requested in invoice(bill Initiate subscribed to is by a notification alert from
Initiate Sendmessageto
10 pay request)
Payment order Captnuorteification service for external agency Current Account to Brokered
when the customer
initiated Paymentexecution
Debit reaqpuperosvtes payment to a
Product)
Einxictiahtaedn
postedBill Pay request Payment is handled by internal
ge account transfer from customer’sto
Obtain merchant’s account
authorization/confirmati
Customer’s on Capture
account fE
orxpcohsa
tinng Crebit request
posted
Builder’s
ge
account Obtain authorization/confirmation
for posting
 CAN WE INTERPRET THE BIANMODEL

Building a working demonstration, collaboratively

62
 CONFIDENTIAL Designator

Answering Q2: What is the ideal

technical architecture?

63
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

From a monolithic to a component architecture

End User Applications

Channel Device Channel Device Channel

External Access APIs

User Access Control/GUI
Front End Applications

Management Information
Security & Control

Management Control & Analytics

App 1 App 2 App 3 App 4 App 5 Environment
Services
Service
Code Exchange
Internal Access APIs Management Handling

Core Functions
Product Fulfillment (SOR) Security
& Logic API
Manage-ment.
Services
SOR 1 SOR 3 Specialised
Utilities
SOR 2 Business
Services
CI/CD
(BIAN
Type 3)

Service
Assurance/M Eventing platform
Utility 1 Utility 2 Utility 3 Utility 4 Utility 5 onitoring

Application Utilities
Data Services (Caching, Database,
Data Integration)

64
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

Red Hat perspective

Third party / Channel / Front-office

Identity API
Provider API Management
Management

RH-SS
O
Business Services
Runtimes
Integration
Hybrid
Service
Cloud Service Service Service Automation
Domain
Plat f orm Istio Domain Domain Domain
(Legacy
Service (3rd Party) (Greenfield) (Composite)
Wrapper)
Openshift Mesh
Eventing platform Messaging

Ansible JDG, CDC,

RHEL Data Services (Caching, Database, Data Integration) Data
Virtualization
Storage
14
Legacy Systems (Mainframe, SoR)
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

Our journey with the BIAN framework

66
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

Minimal Viable Product (MVP) wireframe

Retrieve Product
Directory

Customer
Offer

Request Execute Product

Deployment

Customer
ServicingApp

Evaluate

Customer
Update Product/Service
Eligibility

67
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

API generation using the BIAN specification

68
 CONFIDENTIAL to Red Hat and Partners

WHAT IS THE IDEAL TECHNICALARCHITECTURE under NDA

MVP Business Scenario

Bank 3rd Party

69
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

From business scenario to design sequence

70
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

From design sequence to technical architecture

Eligibility Rules

1.Evaluate
API Eligibility Customer
Gateway Product
Service
Eligibility

6.Update
Product
Customer Service Servicing Order Usage
ExternalAPIs 3.Initiate
Representative Offer 5.Create
Deployment Product
Deployment

Customer
Offer

Product
Directory

71
WHAT IS THE IDEAL TECHNICALARCHITECTURE

Demo in action
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

Anatomy of a business service domain

All Red Hat and 3rd party

ISV stack parts available
Standard Reusable
Business Service Domain Standard Discovery, Naming, API and Eventing

API Integration,
SDs communicate over Service Mesh, Eventing
Eventing, API, Event Stream
Business
Customer Automation
Campaign
Accessible via STD API & Eventing Execution 3rd party
Discovery, Naming, Routing cert. software

API and Eventing Runtimes Storage

Service
Order k8s Business Service pod

Bounded Context: Operational/Transactional

22 business module boundary
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

Technologies utilized
Eligibility Rules
(Red Hat Decision Manager)

1.Evaluate Customer
API
Eligibility Product
Gateway Service
Eligibility
(Red Hat
Fuse)

6.Update
Product
Customer Service Servicing Order 3.Initiate Usage
ExternalAPIs
Representative (Quarkus) Offer 5.Create Product
Deployment Deployment
(Red Hat
Fuse)
Customer
Offer
(Red Hat
(Red Hat Fuse)
3Scale)

Product
Directory
(Red Hat
Fuse)

Service Mesh
Red Hat Openshift
74
 WHAT IS THE IDEAL TECHNICALARCHITECTURE

Production ready with Continuous Integration/Continuous Delivery (CI/CD)

75
WHAT IS THE IDEAL TECHNICALARCHITECTURE

CI/CD in action
 CONFIDENTIAL Designator

Answering Q3: What would a community need?

77
 WHAT DOES A COMMUNITY NEED

Shared Understanding

An MVP approach in selected service domains can jump start adoption

Repeatable steps:
1. Define specific business activity
2. Identify supporting service domains & service exchanges
3. Develop minimal internal function and establish relevant service connections
4. Automate CI/CD
5. Implement feedback look from deployment to incrementally expand functional
content

78
 BIAN Semantic APIs Enable Community Development CONFIDENTIAL designator

Applying the BIAN Concepts and Exchange Types

Real time ✓ Notification on Update ✓ Delayed Response

Request-Reply (Sync/Async) Event Sourcing implemented using Process Management (Async) often
requiring A2A integration, APIs, Change Data Capture and involves Human Tasks supported by
and Messaging. Messaging/Streaming workflow management and intelligent
decisioning.

Best-time ✓ Instant/Concurrent Scheduled Synchronization

Request-Reply (Sync/Async) Shared Database for inter Batch Processing and
requiring mostly Messaging domain communication using ETL usually supported by
(includes Streaming) Data Gateways / Services Data
Integration tools.

28
V0000000
 WHAT DOES A COMMUNITY NEED

A collaborative environment

Scenario: Customer subscribes to building support service, subsequently a builder submits their invoice
Bank
Customer
Contact Session Information
Correspon-
dence
Current
Account
Payment
Order
Payment
Execution
Position
Keeping
Servicing Prod/Servic Brokered
Order e Product Provider TPP processing
Handler Dialogue Operation
Eligibility
Update
Notify
Register customer
product usage Initiate
Notify TPPservice Register new customer details,
Sendmessageto send out service contact
external agency
details/request

Retriev Initiate

e
Get request from
Confirm Customer still
TPP
Check customer
still registered
subscribed

Initiate
Initiate Get request from Submit invoice for customer
Initiate (Bill Pay)
Initiate a “Bill Pay”
TPP payment
Send an alert to the request tothe current
customer account holder (the
customer)

Initiate Customer logs in to process bill pay

Exchan
Customer logsin ge request. Notification is sent to
to respond to alert Custo(mBielrPaacyc)esses merchant when bill pay approved by
Initiate and approves Bill Pay customer. (Two mechanismsare
Notify
Confirmation message (Bill Pay) shown – one option is
send tomerchant as Brokered Product has Initiate correspondence – in red, the other
requested in invoice(bill Initiate subscribed to is by a notification alert from
Initiate Sendmessageto
pay request)
Payment order Captnuorteification service for external agency Current Account to Brokered
when the customer
initiated Paymentexecution
Debit reaqpuperosvtes payment to a
Product)
Einxictiahtaedn
postedBill Pay request Payment is handled by internal
ge account transfer from customer’sto
Obtain merchant’s account
authorization/confirmati
Customer’s on Capture
account fE
orxpcohsa
tinng Crebit request
posted
Builder’s
ge
account Obtain authorization/confirmation
for posting

3rd Party
Epiphany One

Epiphany ONE is a modular platform

designed around an open collaboration concept:
focused on enabling co-creation between banks
and external partners to
deliver new digital services
EPIPHANY ONE – An advanced open development
environment leveraging the BIAN business
component model…

3rd Party & The foundation

Customer Epiphany ONE for a banking
Integration industry “App
❑
❑
External access flows
FAPI/OIDC/Oauth2.0… ❑ Covers the entire banking ecosystem: store”
❑ banking transaction fulfillment;
❑ customer facing applications; and,
❑ third party (Fintech) integration.
❑ Leveraging BIAN to define standard
business application ‘components’.
❑ Cloud resident, container based, with Development &
Library of Core
support for rapid, incremental Deployment
Banking System development and deployment ❑ Rich SKD, including…
APIs/Adaptors ❑ …Developer Sandbox
❑ Powerful Testing &
Deployment Services
WHAT DOES A COMMUNITY NEED

A place to practice and meetup

On-demand lab environment

● We established a platform
supporting team development
● Automated provisioning
available on-demand
● Easily extendable to a wider
community
● Interested in lessons learned by
other firms who have deployed
Confidential

Santander
BIAN as a functional language - the journey (so far!) toward fully
compliant Domain Driven landscape.

21st October 2020

84
Confidential
View of Generic Banking Institution
NOTE – not intended to be an
exact representation of Santander

Santander is a complex
global, multi-entity
organization.
For purpose of
demonstrating, this is a
an example of the
generic global bank
view across the
customer and product
dimensions

85
Confidential
Example BIAN Use Case 1
BIAN AS A FUNCTIONAL LANGUAGE TO ORGANIZE IT LANDSCAPE
• In a complex global, multi-entity organization such as Santander Group, BIAN
provides value as a common functional language to organize and manage the
FUNCTIONAL Applications Portfolio.
LANGUAGE FOR
IT • Key IT portfolio tools are being updated to include BIAN Service Landscape as a
new dimension to manage our assets.
• This also provides a view into opportunities such as simplification of the
BIAN
Coverage
application landscape, reducing costs, decommissioning.

86
Confidential
Example BIAN Use Case 2
BaaS - API FUNCTIONAL REFERENCE FRAMEWORK
• A reference architecture framework has been defined in order to provide common
standards across the group.
API DESIGN
• API Functions are published in the Intranet API Portal

• Enables more efficient identification of required APIs, also preventing inadvertent

duplication.

Domain Driven • Each API is classified under its corresponding BIAN Service Domain.
Design

• API Design: Each API must expose functions from only one BIAN Service Domain.
• Also recognises, in some cases, a service domain may have more than one API

• An API can delegate responsibility to another API, matching the Service Domain model
of delegating responsibilities to other service domains. This is hidden from the
consumer.

87
Confidential
Example BIAN Use Case 2
BaaS - API FUNCTIONAL REFERENCE FRAMEWORK
• Banking as a Service (BaaS) APIs can be reused and have business logic that is
common for many applications according to its BIAN Service Domain (Capability) which
sets the logical boundaries and scope of functionality and data (I.e. Domain Driven
API DESIGN
Design)

• BaaS APIs are Touchpoint, Customer Journey or Customer Service Channel

UK Application
capabilities
Experience API
Domain Driven • Each BaaS API must exclusively manage it’s Experience API
Design Service Delivers a
own data, for the whole lifecycle of that business
function
data. Service Domain 1 Service Domain 2

BaaS API #1 BaaS API #2

BaaS API #1 Service BaaS API Service #2

Simple
orchestration

System Service API

System Service System Service System Service

Backends, Domains/Processors 28
Confidential

Direction of travel towards service orientated fully compliant landscape

29
 Model Management Practice
BIAN @ CIBC Overview
Enterprise Architecture
October 22, 2020

Internal
Our models are framed around the Architecture
11

stack and represents a view to each layer

Business Area,
BIAN Service Business Domain
Coarse Landscape Service Domain
grained Business Architecture
Data Architecture Banking Industry Data Model
Common Info
(data objects & metadata)
Application Architecture Model
Fine Technology Architecture
grained
Reference Data Architecture Microservices
Sales & Service Framework Service-Oriented Architecture
Operations & Execution
Risk & Compliance
Business Support Infrastructure,
Technology & Security & Utility
Security Model Services & Products

BIAN is technology and implementation agnostic and focuses solely on the business capability
level; capabilities that support the realization of our banking products and services and that
help us run as a bank.
Our vision is to leverage models that are fit for
purpose and inform our strategic decisions.
12

Conceptual View
▪ Which business capabilities are being realized?
Architect Business ▪ Do Gaps, Redundancies, Overlaps exist?
Governance ▪ Are there opportunities for simplification, rationalization, re-use?
Leverage Capability View
models

BIAN Technology
Leverage
models Capability View
API Marketplace Technology
& Security
What data is being Model
APIs exposed (internally,
externally)? • What are the standard
Common technologies?
Info • What is the underlying technology
composition of the application?
Model
▪ What data is being moved between internal systems?
Data ▪ What data is being shared with external parties?
▪ What data is implicated in new initiatives?
Capability
Internal View
 BIAN Solution Certification
Certification Working Group, September 2020

93 Copyright BIAN 2020 | Banking Industry Architecture Network

 Solution Certification – Overview

Pilot agreed
Certification Tests
• Definition of Test requirements for each BIAN
Artefact Type
• Service Domains • Temenos Infinity
• Business Capabilities • Digital Front Office Solution
• Business Information (BOM, CR, BQ) • Greenfield Banking system
• Service Operations / APIs
• Business Scenarios / Wireframes
• Definition of Mandatory v Optional Status
requirements.
• DRAFTs being reviewed • DXC Celeriti
• Product Certification
• Enterprise Banking & Lending
questionnaire (spreadsheet)
• Product Certification working Solution
paper (document). • Incumbent Core Banking system
Application Clusters

For an Application to be certified as BIAN compliant Interested

• Identify relevant BIAN functional building Members
blocks (Service Domains)
• Identify the role of each Service Domain: Key,
Proxy, Utility, External, Peripheral
• Identify all BIAN artefacts in scope of the • Run some tests based on Pilot, distinction between self certification &
Cluster and apply the relevant Certification confirmation of the self certification – Q1 2021
Tests • Produce recommendations for Production testing – Q2 2021

94 Wiki: https://biancoreteam.atlassian.net/wiki/spaces/CER/overview
Copyright BIAN 2020 | Banking Industry Architecture Network
 Certification Tests – Mapped to BIAN Artefacts

Business
Service Domains
Capability?
Confirm Organizational
Alignment
✓ Component architecture
✓ Service ownership/re-use
✓ Thorough externalization &
✓ Encapsulation/governance
✓ Control record structure
(BQs)

Business Information Service Business

(BOM & CR/BQ) Operations/APIs
Check Information Ensure Service/API
Quality Coverage
✓ Content completeness ✓ Aligned Services/APIs
✓ Consistency in definitions ✓ Completeness of key
✓ Standards alignment (ISO) actions
✓ Control Record coverage ✓ Concise services (scope)
✓ Completeness of content
✓ Control Record content
Scenarios/Wireframes
Evaluate Functionality
✓ Coverage of primary
events/capabilities
✓ Compatibility with service
based operations
✓ Adaptable/Extensible

Semantic API Specs

Recognize Limited
Scope of BIAN
✓ Alignment
✓ Classification/naming
✓ Extensible to physical
implementation

95 Copyright BIAN 2020 | Banking Industry Architecture Network

 Application Clusters

Example Application Cluster for Current, Savings, Retirement & Term Deposit Accounts Offering
- Including Service Domain Roles

Application Cluster showing Core/Utility/Proxy Roles

Customer Contract Product Support Facilities

Key: Service Domain Roles Sales Product Customer Financial Issued Device Issued Device Payment
Agreement Agreement Payment Order
Accounting Tracking Administration Execution

Service Core = Service Domain

Domain
wholly contained Customer Execute
Retrieve
Retrieve Document
within cluster Record Services
Interaction Execute
Retrieve
Product
Fulfillment
Customer
Service Proxy = Local instance Customer Update Initiate
Reference
Domain Access
Retrieve
synchronised with Current Account Correspon-
Entitlement Cross-product dence
master Retrieve Party Data Processing
Management

Initiate Term Execute

Position Keeping
Service Utility = Local Deposit

Domain Customer Customer Market Data

instance, no need to Offer Reference Data
Management Switch
Transaction Operation
synchronise Execute
Savings Account Engine Update
Update

Service External = First order Retrieve

Domain Contact Execute Retirement Product
service operation Dialogue Account Update Execute Directory
connections
Update Execute Retrieve
Service Peripheral = Second BIAN Service
Domain Customer
order dependencies – Order Product Management Operation
‘Action’ Term
for reference Product
Systems Product Design
Operations Portfolio

Key Questions
✓ Correct/meaningful content (rules – e.g. performance/security XACML – CIA, integration)
✓ Clearly defined roles within the system being certified (include Externalization is followed) see guide
✓ Map governed information to the scope of the associated control record – check ability to decouple
✓ External coordination/synchronization interfaces correctly implemented (including master/proxy coordination)
✓ Complete scope of external connections (requires first order connections for transactional & referential
dependencies) in order to identify all required Service Operations (checking extracted information Copyright
content) BIAN 2020 | Banking Industry Architecture Network
 API Governance Compliance &
Feedback
DRAFT – Being looked into

97 Copyright BIAN 2020 | Banking Industry Architecture Network

 API Governance, Compliance & Feedback

Functionality Possible use cases

• Compare implemented APIs against the BIAN standard APIs

• OAS domains – Data type compliance eg. currency,
• When members / non-members give us API feedback
DateTime etc.
from real implementations
• API Standardization – Out-of-the-box rules
• Compliance / Certification
• Custom rules – using Regex
• Provide a starter pack for users, to start a BIAN compliant
• Webhooks & registry API scripting
implementation*

Industry Adoption
• Widely used for Swagger JSON / YAML
• Specific Industries
• SWIFT / ISO20022 – Payments
• HL7 / FIHR – Healthcare
• IATA – Airline
• TMF Forums – Telecoms
• UN Standards

98

Copyright BIAN 2020 | Banking Industry Architecture Network

 DevOps CI/CD SmartBear / Swaggerhub tool

BIAN
Validation
This type of Tooling is
already used by:

SWIFT
HR7 (Healthcare)
IATA (Airlines)
UN

BIAN
API’s
BIAN
compliant
testcases

99 Copyright BIAN 2020 | Banking Industry Architecture Network

 Thank you

100 Copyright BIAN 2020 | Banking Industry Architecture Network