building the future of banking services - bian · compliance reporting market risk models gap...
TRANSCRIPT
BIAN Service Lanscape V5.0
Webinar
16th November 2016
Hans Tesselaar Guy Rackham
BIAN Chief Executive BIAN Chief Architect
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
Contents
Agenda
BIAN Service Landscape V5.0
Welcome and Introduction
1. Context
V3.0, V4.0 & V5.0
Design Foundation
Summary of V4.0 Approach
Summary of V5.0 Approach
2. Key Changes/Additions to the Standard
Wireframe/First Order Connections
Generic Artifacts
Service Domain Business Events
Service Domain Information Profile
3. V5.0 Deliverables and Status
4. V5.0 Tooling
5. Direction for V6.0 – Options under consideration
2
Copyright BIAN 2014 | Banking Industry Architecture Network
A Warm Welcome to YOU –
Dialing in From all around the globe!
3
Copyright BIAN 2014 | Banking Industry Architecture Network
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:
• By leading banks sharing their requirements for banking services
• By leading software and services vendors to implement them based
on standard semantics.
74 Members
• 27 Financial Institutions
• 43 Software Vendors / Service Providers
• 4 Academic Partners
The Power of Joint Standardization: BIAN
Copyright BIAN 2014 | Banking Industry Architecture Network
Introduction | BIAN & Partners + Academics
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
Contents
Agenda
BIAN Service Landscape V5.0
1. Context
V3.0, V4.0 & V5.0
Design Foundation
Summary of V4.0 Approach
Summary of V5.0 Approach
2. Key Changes/Additions to the Standard
Wireframe/First Order Connections
Generic Artifacts
Service Domain Business Events
Service Domain Information Profile
3. V5.0 Deliverables and Status
4. V5.0 Tooling
5. Direction for V6.0 – Options under consideration
7
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
1. Context
The V5.0 Release continues the rapid development of the BIAN standard
The BIAN Working Groups continue to ratify and expand the content..
February
2013
March
2014
Q1-2
2015
SL 2.0~270 Service
Domains ‘Identified’,
63 Service Domains
‘Invoked’
Metamodel Aligned
All deliverables
available in
HTML and UML
SL 3.0Total of 214 Service
Domains ‘Invoked’
(All bank
functionality)
Banking Domains
Completed
Metamodel Aligned
Results of new
Working Groups
and Harvesting
activity
New Set-up of the
“How to Guide”
SL 4.0All 280+ Service
Domains
Service
Operations
‘complete’
All Business
Domains
addressed
Metamodel
Aligned
September
2013
SL 2.5Total of 93
Service
Domains
‘Invoked’
Metamodel
Aligned
All
deliverables
available in
HTML and
UML
October
2014
SL 3.5Around 100
Service
Domains
‘Complete’
Metamodel
Aligned
Substantial
set of
message
definition
(IFX - ISO)
available
Terms (V3):
Identified
Invoked
Complete
Service Domain
Service Domain
Service Domain
Terms (V4):
Candidate
Reviewed
Mapped
Service Domain
Service Domain
Service Domain
Q2/3
2016
SL 4.5/5.0~300 Service
Domains with
default Service
Operations
‘provisional’
1000+ Business
Events & Associated
Business Scenarios
Terms (V5):
Provisional
Reviewed
NA
Service Domain
Service Domain
Service Domain
8
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
1. Context
9
Reference Data Sales & Service Business SupportRisk &
ComplianceOperations & Execution
Product Specific fulfillment
Non IT and HR Enterprise Services
Business Analysis
Bank Portfolio & Treasury
Regulations & Compliance
Models
IT Management
Trade BankingLetter of Credit
Bank Guarantee
Trade Finance
Corporate Financing & Advisory Services
Corporate Finance
M&A Advisory
Corporate Tax Advisory
Public Offering
Private Placement
Investment Management
Investment Portfolio Planning
Investment Portfolio Analysis
Investment Portfolio Mgmt
eTrading Workbench
Consumer Services
Currency Exchange
Remittance
Corporate Trust Services
Brokered Product
Bank Drafts & Trvl. Checks
Consumer Investments
CardsCredit/Charge Card
Card Authorization
Card Capture
Merchant Relations
Card Billing & Payments
Business Command & Control
Business Unit Financial Analysis
Business Unit Financial Ops
Business Unit Accounting
Organizational Direction
Business Unit Direction
Business Unit Management
Finance Financial Statements
Financial Control
Financial Compliance
Enterprise Tax Administration
Buildings, Equipment and Facilities
Property Portfolio
Site Operations
Site Administration
Equipment Administration
Equipment Maintenance
Utilities Administration
Building Maintenance
Internal Audit
Procurement
Fixed Asset Register
Legal Compliance
Approved Supplier Directory
Company Billing & Payments
Market Research
Customer Portfolio
Segment Direction
Market Analysis
Competitor Analysis
Product Portfolio
Branch Portfolio
Channel Portfolio
Stock Lending/Repos
Corporate Treasury Analysis
Corporate Treasury
Asset Securitization
Asset & Liability Management
Bank Portfolio Analysis
Bank Portfolio Administration
Guideline Compliance
Regulatory Compliance
Compliance Reporting
Market Risk Models
Gap Analysis
Credit Risk Models
Customer Behavior Models
Credit/Margin Management
Production Risk Models
Operational Risk Models
Fraud Models
Liquidity Risk Models
Economic Capital
Business Risk Models
Systems Administration
IT Systems Direction
IT Stds & Guidelines
Development Environment
System Development
Production Release
System Deployment
Systems Operations
Platform Operations
Systems Help Desk
Systems Assurance
Internal Network Operation
Human Resource Management
Business Direction
Knowledge & IP Management
Corporate Relations
Document Mgmt & Archive
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
Corporate Strategy
Corporate Policies
Product & Service Direction
Business Architecture
Continuity Planning
Management Manual
Intellectual Property Portfolio
Knowledge Exchange
Corporate Communications
Corporate Alliance/Stakeholder
Corporate Relationship
Regulatory & Legal Authority
Investor Relations
Document Services
Archive Services
Correspondence
Security Advisory
Security Assurance
Financial Inst.Valuation Models
Regulatory Reporting
Financial Accounting
Contribution Analysis
Contribution Models
Loans & Deposits
Current Account
Deposit Account
Loan
Leasing
Credit Facility
Cash Mgmt & Account Svs
Cheque Lock Box
Factoring
Direct Debit Mandate
Direct Debit
Syndicated Loan
Credit Management
Limit & Exposure Management
Project Finance
Market OperationsMutual Fund Administration
Hedge Fund Administration
Unit Trust Administration
Order Allocation
Settlement Obligation Mgmt.
Securities Fails Processing
Trade/Price Reporting
Custody Administration
Corporate Events
Financial Instrument Valuation
Security Dlvry & Receipt Mgmt
Trade Confirmation Matching
Customer Tax Handling
Wholesale Trading Trading Book Oversight
Dealer Workbench
Market Making
ECM/DCM
Program Trading
Traded Position Management
Market Order
Quote Management
Suitbility Checking
Credit Risk Operations
Market Order Execution
Trading Models
Cross Product Operations
PaymentsPayments Execution
Collateral Administration
Collateral Allocation Mgnt
Collateral Asset Administration
Collections
Account Management Operational Services
Transaction Engine
Position Keeping
Position Management
Accounts Receivable
Account Reconciliation
Fraud Detection
Reward Points Account
Issued Device Admin
Counterparty Risk
Dunning
Open Item Management
Disbursement
Channel Activity Analysis
Rewards Points Awards & Red.
Customer Billing
Leasing Item Administration
Issued Device TrackingFinancial Message Analysis
Financial Gateway
Correspondent Bank
Cheque Processing
Central Cash Handling
Channel Activity History
Fraud/AML Resolution
Corporate Current Account
Product Combination
Marketing
Servicing
Customer Mgmt
Sales
Channel Specific
Product Management
Market Data
Party
External Agency
Business Development
Brand Management
Advertising
Promotional Events
Prospect Campaign Mgmt
Prospect Campaign Design
Customer Campaign Mgmt
Customer Campaign Design
Customer Surveys
Servicing Issue
Customer Case Management
Case Root Cause Analysis
Customer Case
Card Case
Customer Relationship Mgmt
Prospect Campaign Execution
Customer Campaign Execution
Prospect Management
Commission Agreement
Commissions
Product Matching
Sales Planning
Customer Offer
Underwriting
Product Expert Sales Support
Contact Center Management
Branch Currency Distribution
Product Inventory Item Mgmt
Product Inventory Distribution
Branch Network Mgmt
E-Branch Management
Advanced Voice Services Mgmt
ATM Network Management
Contact Center Operations
Branch Location Operations
E-Branch Operations
Advanced Voice Services Ops
ATM Network Operations
Branch Currency Management
Product Design
Product Deployment
Product Training
Product Quality Assurance
Discount Pricing
Information Provider Admin
Party Data Management
Customer Profile
Syndicate Management
Correspondent Bank Data Mgmt
Sub Custodian Agreement
Product Broker Agreement
Product Service Agency
Contractor/Supplier Agreement
Correspondent Bank Rel Mgmt
Cross Channel
Point of Service
Servicing Activity Analysis
Contact Routing
Contact Dialogue
Interactive Help
Servicing Event History
Customer Order
Party Authentication
Transaction Authorization
Payment Order
Branch Location Management
Sales Product
Information Provider Operation
Market Information Mgmt
Financial Market Analysis
Financial Market Research
Quant Model
Market Data Switch Adm
Market Data Switch Ops
Financial Instr Ref Data Mgmt
Public Reference Data Mgmt
Counterparty Administration
Location Data Management
Customer Prod./Service Eligibility
Interbank Relationship Mgmt
Lead/Opportunity Management
Product Sales Support
Customer Agreement
Customer Access Entitlement
Customer Event History
Customer Behavioral Insights
Customer Credit Rating
Account Recovery
Sales Product Agreement
Contact Handler
Customer Workbench
Product Directory
Special Pricing Conditions
Customer Precedents
Custmer Reference Data Mgmt
Customer Proposition
Corporate Loan
Corporate Lease
Consumer Loan
Merchandising Loan
Fiduciary Agreement
Savings Account
Mortgage
Consumer Advisory Services
Trust Services
Service Product
Customer Position
ACH Fulfillment
Service Landscape V5.0
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
1. Context
V3.0, V4.0 & V5.0 – Evolution of the BIAN standard – key stages
In simple terms the BIAN standard has evolved significantly over the major releases:
V3.0 V4.0 V5.0 V6.0+
Defined
Candidate
Service
Domains
Service Domains’
Default Service
Operations
(Offered)
Service
Domains’ Default
‘First Order’
Connections ?
10
?
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
1. Context
Design Foundation
A Service Domain’s business purpose/role is to apply a pattern of behavior to a type of
asset. A ‘Control Record’ tracks this activity from start to finish. BIAN has defined a
general breakdown of assets and standard behaviors:
18 standard functional patterns of behavior have
been identified and refined in use
Assets are identified using a “MECE” decomposition
hierarchy
One Asset
Type
One
Pattern
11
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
1. Context
Register
Initiate
Activate
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Actions to set-up, establish a new control record instance
Actions to access/update/influence an established instance
Actions to extract details and subscribe to updates
Terminate
Create
Configure
Record the details of a newly identified entity
Return information/report as requested
Begin an action including any required initialization tasks
Commence/open an operational or administrative service
Change the value of some (control record) properties
Perform a check, trial or evaluation
Assign or allocate resources or facilities
Execute a task or action on an established facility
Provide details against a predefined notification agreement
Request the provision of some service
Allow the execution of a transaction/activity
Capture transaction or event details associated with a life cycle step
Conclude, complete activity
Manufacture and distribute an item
Change the operating parameters for an ongoing service/capability
A new customer's details are captured
An account balance is obtained and a report covering activity analysis requested
A payment transaction is intiiated
The ATM network operation is actived
A customer's reference details are updated with a change of address
The eligibility to sell a product is checked against the customer’s existing agreement
A branch requests an allocation of cash for its tellers
A payment is applied to a charge card
A unit subscribes to update notifications from the customer agreement service domain
A customer requests that a standing order is set up on the current account
Regulatory compliance authorises a product design feature
An employee logs time spent working on a project against the plan
The use of a product version is terminated
A new analytical model design is created
The on-line ATM's in the network are changed to take machines out of service
Maintain & Analyze (delegation only – no action terms apply)
Description Example
Initia
lise &
Regis
ter
Invocation &
Execution
Report
&
N
otify
Action Terms A Service Domain is
accessed through its
offered service
operations. A
selection from a
standard set of
service operations is
matched to the
specific functional
pattern
Service Operation Actions Terms
A Service Domain combines an Asset Type with a Functional Behavior
Design Foundation
A service Domain has one associated Functional Pattern and offers (and consumes) a
collection of service operations each characterised by an action term..
12
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
1. Context
Summary of V4.0 Approach
The V4.0 candidate service operation technique was developed to accelerate the definition
of service operations – creating ~2000 candidate service operation descriptions
Register
Initiate
Create
Administer
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
PL
AN
MA
NA
GE
AD
MIN
IST
ER
DE
SIG
N
AS
SU
RE
CO
NF
IGU
RE
AN
ALY
SE
EN
RO
LL
AG
RE
E
TE
RM
S
INV
EN
TO
RY
DE
PL
OY
AL
LO
CA
TE
DIR
EC
TO
RY
QU
AL
IFY
TR
AC
K
OP
ER
AT
E
MA
INT
AIN
FU
LF
ILL
TR
AN
SA
CT
BU
ILD
/
EN
HA
NC
E
Init
iali
se &
R
eg
iste
r In
vo
ca
tio
n &
Ex
ec
uti
on
R
ep
ort
&
No
tify
Terminate
Execute Perform a
transaction/task
Evaluate Measure,
assess, test
Record Capture
insights/activity
Provide Deliver, allocate
or assign
Administer Handle day to
day tasks
Authorise Approve or
allow
Create Make somthing
Request Ask for some
service/aupport
Initiate Start a process
Terminate Conclude, bring
to a close
Register Capture details
of an entity
Notify Subscribed to
updates
Retrieve Respond to
reads/queries
BIANServiceDomain
DIRECTORY ASSURE OPERATE
Option 1 – Create a new specialised service operation with a qualifier added to the name
requestCurrentAccountFulfillmentStandingOrder
Option 2 – List service types as a selection list in the “control” input parameterith a qualifier added to the name
requestCurrentAccountFulfillment…Control parameter: {obtain statement, setup sweep,
setup lien, standing order, etc…}
“li
fe-c
yc
le” s
erv
ice
op
era
tio
ns
This was then used to define
~2000 candidate service
operations descriptions for
all 280 BIAN Service Domains
Service Operation Descriptions
Each Functional Pattern was matched to a default set of Service Operations
13
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
1. Context
Summary of V5.0 Approach
The V5.0 Approach was defined to accelerate the development of Business Scenarios in
order to capture the service operation connections between Service Domains. An
interative seven-step approach was developed. Steps 1-6 are completed to develop a
foundation and only revisted as necessary during subsequent business scenario
generation cycles.
1. WG – Review/Update Wireframe
2. WG – Agree Product/Service List – ‘Primary’ Service Domains
3. WG – Identify Business Events (defines Business Scenarios)
4. WG – Describe Business Scenarios
5. WG – Define Service Domain Business Information Profile
6. WG – Identify Calling & Delegated Service Domains
7. WG – Develop Business Scenarios
8. Loop
Mostly
completed
in the first
cycle
1- Review
Wireframe
2- Agree
Product/
Service List
3 – Identify
Business
Events
4 – Describe
Business
Scenarios
5 – Define SD
Information
Profile
6 – Service
Operation
Connections
7 – Develop
Business
Scenarios
14
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
Contents
Agenda
BIAN Service Landscape V5.0
1. Context
V3.0, V4.0 & V5.0
Design Foundation
Summary of V4.0 Approach
Summary of V5.0 Approach
2. Key Changes/Additions to the Standard
Wireframe/First Order Connections
Generic Artifacts
Service Domain Business Events
Service Domain Information Profile
3. V5.0 Deliverables and Status
4. V5.0 Tooling
5. Direction for V6.0 – Options under consideration
15
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
Wireframes/First Order Connections
Wireframes are used internally for defining the connections between Service Domains. For
V5.0 they provided a framework for quickly identifying business events and deriving the
associated service exchanges to develop Business Scenarios.
First Order connections for a Service
Domain identify the known calling and
called service operation connections….
The wireframe captures the service
operation connections between a
selection of Service Domains
16
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
17
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Terminate
Register
Co
nfig
ure
Initiate
Activate
Create
Service DomainInternal actions
Wireframes/First Order Connections
For V5.0 a more detailed pattern of the connections has been used to define the service
operation connections between every Service Domain:Any Service Domain can offer a
selection from a standard set of
actions terms/service operations
Steady State
New
Insta
nces
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
18
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Terminate
Register
Co
nfig
ure
Initiate
Activate
Create
Co
nfig
ure
Initiate
Activate
Create
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Terminate
Register
Service DomainInternal actions
Delegated action handling
Wireframes/First Order Connections
For V5.0 a more detailed pattern of the connections has been used to define the service
operation connections between every Service Domain:A Service Domain’s can also
delegate to any other Service
Domain calling on its offered
service operatiions
Steady State
New
Insta
nces
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
19
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Terminate
Initiate
Activate
Create
Initiate
Activate
Create
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Terminate
Data Items, Forms/Reports, Scans,Topics & Analysis
Service DomainInternal actions
Delegated action handling
Wireframes/First Order Connections
For V5.0 a more detailed pattern of the connections has been used to define the service
operation connections between every Service Domain:The Service Domain’s Functional
pattern defines a default set of
offered service operations
Register
Co
nfig
ure
Co
nfig
ure
Register
Steady State
New
Insta
nces
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
20
Contact Dialogue
Payment Order
Account Recovery
Regulatory Compliance
TreasuryAdministration
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Terminate
Initiate
Activate
Create
Initiate
Activate
Create
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Terminate
Customer Offer
Account Recovery
Data Items, Forms/Reports, Scans,Topics & Analysis
Service DomainInternal actions
Delegated action handling
Wireframes/First Order Connections
For V5.0 a more detailed pattern of the connections has been used to define the service
operation connections between every Service Domain:Showing all identified ‘first order’
service connections to the
associated Service Domains – first
calling Service Domains
Register
Co
nfig
ure
Co
nfig
ure
Register
Steady State
New
Insta
nces
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
21
Contact Dialogue
Payment Order
Account Recovery
Regulatory Compliance
TreasuryAdministration
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Terminate
Initiate
Activate
Create
Initiate
Activate
Create
Update
Evaluate
Provide
Retrieve
Execute
Notify
Request
Authorise
Record
Terminate
Customer Offer
Account Recovery
Correspon-dence
Document Services
Customer Event
History
Corporate Treasury
Open Item Management
Position Keeping
Payment Order
Financial Accounting
Position Keeping
Information Provider
Operations
Collateral Management
Data Items, Forms/Reports, Scans,Topics & Analysis
Service DomainInternal actions
Delegated action handling
Wireframes/First Order Connections
For V5.0 a more detailed pattern of the connections has been used to define the service
operation connections between every Service Domain:Showing all identified ‘first order’
service connections to the
associated Service Domain – and
finally the delegated calls
Register
Co
nfig
ure
Co
nfig
ure
Register
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
Wireframes/First Order Connections
Wireframes are defined for selections of Service Domains and capture the known service
operation connections that are discovered/ratified using business event and business
scenario analysis…
The wireframe shows the
service operations,
detailing the types of
connection and action
terms for each…
With this detail in the tool it
is possible to quickly
develop Business
Scenarios…
22
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
Generic Artifacts – an update to the Control Record
The ‘Control Record’ was defined to be the concatenation of the Asset Type and the
Functional Pattern. The Functional Pattern takes the verb form and so the Control Record
was found to be too abstract. An associated generic “artifact” was defined for each
functional pattern. This term is now used in the Control Record – note: this changes the
default service operation names
Administer
Agree Terms
Allocate
Functional Pattern
Analyze
Assess
Design
Develop
Direct
Enroll
Fulfill
Maintain
Manage
Monitor
Operate
Process
Register
Track
Transact
Generic Artifact
Adminnistrative Plan
Agreement
Allocation
Analysis
Assessment
Specification
Development Project
Strategy
Membership
Fulfillment Arrangement
Maintenance Agreement
Management Plan
Measurement
Operating Session
Procedure
Directory
Log
Transaction
23
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
Service Domain Business Events
Business Events define the key business activities for each primary Service
Domain. Each event is developed into a corresponding ‘First Order’ Business
Scenario
Note: the terms used in
earlier releases to group
service operations have been
simplified and used to also
categorise business events:
Initialise & Register
becomes Origination
Invoke & Execute
becomes Invocation
Maintain & Analyse
becomes Delegation
Reporting & Notification
becomes Reporting
Example Primary Service Domain
Business Events
24
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
Semantic Business Information Profile
Records ReportsItems
Service Domain Control Record
Artifact
Name Active status Balance/positions Account type Currency Start date Credit/debit transaction Standing order transaction etc…
Application form Account statement Standing order request Balance/account inquiry Tax statement
Digitised signature/photograph
Customer document scans
Current Account Current Account
Fulfillment
Current account facility
arrangementService Domain Analytical & Historical Views
Service DomainPortfolio ViewsIndividual Control Record Views
Average balance (yearly) Key facility usage events Account activity trend analysis
Active/dormant account portfolio analysis
Account utilization portoflio analysis Account type portfolio make-up
Current Account
Service Domain Information Profile
The Service Domain’s Control Record is used to help define create an ‘Information Profile’.
In V5.0 general information content has been described based on the functional patterns.
(Note: alignment to Semantic APIs)
25
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
2. Key Changes/Additions to the Standard
Service Domain Information Profile
The Service Domain’s service operation ‘Action Terms’ are then used to extract the service
operation payload (detail for reference only)
RegisterInitiate
Activate
Update
EvaluateProvide
Retrieve
Execute
Notify
RequestAuthorize
Record
Terminate
Create
Configure
NA
NA
NA
Extract artifact properties
Extract artifact properties
Extract artifact properties
Extract artifact properties/NA
Extract artifact properties
Extract artifact properties/NA
Extract artifact properties
Extract artifact properties
Extract artifact properties
Extract artifact properties
NA
Extract artifact properties
Origination
Invocation
Reporting
Service Operation
TypeAction Term
Likely Service Operation Payload - REQUEST
Complete artifact
Compete artifact
Complete artifact
Selected artifact elements
Subject details for evaluation/NA
Provision request details/NA
NA
Transaction content/NA
NA
Service request details/NA
Subject details for authorization/NA
Recorded activity details/NA
NA
Complete artifact
Selected artifact elements
Identifiers Depiction Instructors Analyses
Registration parameters
Initiation parameters
Activation parameters
Update parameters
Evaluation (&) parameters
Provisioning parameters
Report selection parameters
Transaction (&) parameters
Notification parameters
Request (&) parameters
Authorization (&) parameters
Record (&) parameters
Termination parameters
Creation parameters
Configuration parameter
NA
NA
NA
NA
NA
NA
Analysis/Report Type/NA
NA
Analysis/Report Type/NA
NA
NA
NA
NA
NA
NA
RegisterInitiate
Activate
Update
EvaluateProvide
Retrieve
Execute
Notify
RequestAuthorize
Record
Terminate
Create
Configure
Extract artifact properties
Extract artifact properties
Extract artifact properties
Action reference
Action reference
Action reference
Action reference
Action reference
Action reference
Action reference
Action reference
Action reference
Action reference
Extract artifact properties
Action reference
Origination
Invocation
Reporting
Service Operation
TypeAction Term
Likely Service Operation Payload - RESPONSE
Registered details
Initiation details
Activation details
NA
Evaluation analysis/report
Provisioning details
Analysis/report content
NA
Analysis/report content
Request analysis/report
Authorization report
NA
NA
Creation details
NA
Identifiers Depiction Instructors AnalysesRegistration result
Initiation result
Activation result
Update result
Evaluation result
Provisioning result
Selection result
Transaction result
Notification result
Request result
Authorization result
Record result
Termination result
Creation result
Configuration result
NA
NA
NA
NA
NA
NA
Analysis/Report Type
NA
Analysis/Report Type
NA
NA
NA
NA
NA
NA
26
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
Contents
Agenda
BIAN Service Landscape V5.0
1. Context
V3.0, V4.0 & V5.0
Design Foundation
Summary of V4.0 Approach
Summary of V5.0 Approach
2. Key Changes/Additions to the Standard
Wireframe/First Order Connections
Generic Artifacts
Service Domain Business Events
Service Domain Information Profile
3. V5.0 Deliverables and Status
4. V5.0 Tooling
5. Direction for V6.0 – Options under consideration
27
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
3. V5.0 Deliverables and Status
The V5.0 Release Process was adapted over the year
The approach evolved over the year as the approach and tooling was refined
Working
Groups
Harvesting
1st Iteration
Scenarios
2nd Iteration
Scenarios
3rd Iteration
Scenarios
1st Iteration
Scenarios
2nd Iteration
Scenarios
3rd Iteration
Scenarios
Central
service
operation &
vocabulary
development
V5.0(End off
2nd Qtr.)
Initial
Refinement Semantic
Services
Mostly
completed
in the first
cycle
1- Review
Wireframe
2- Agree
Product/
Service List
3 – Identify
Business
Events
4 – Describe
Business
Scenarios
5 – Define SD
Information
Profile
6 – Service
Operation
Connections
7 – Develop
Business
Scenarios
1. WG – Review/Update Wireframe
2. WG – Agree Product/Service List
3. WG – Identify Business Events (defines Business Scenarios)
4. WG – Describe Business Scenarios
5. WG – Define Service Domain Business Information Profile
6. WG – Identify Calling & Delegated Service Domains
7. WG – Develop Business Scenarios (using defaults/patterns)
8. Loop
The Plan
Working
Groups
Core Team
1st
Iteration
WG interaction &
Final Aug/Sept Review
Continual Content Development
Central service
operation &
vocabulary
development
Initial
Refinement Semantic
Services
V4.5(End off
2nd Qtr.)
V5.0(End off
3nd Qtr.)
Actual: After first roadshow, WG involvement was
through the scheduled WG bi-weekly sessions
Central team developed provisional content
WG tool based reviews initiated in Aug/Sept
28
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
3. V5.0 Deliverables and Status
Reference Formats
ServiceLandscape
Metamodel Guide
UML Based Repository &
ToolingISO20022 based
Web-tool Business Scenarios & Wireframes
HTML Service Landscape & Business Scenarios
How To Guides &
Training
Presentations
BIAN Service Landscape – Release 5.0 Components
The BIAN specifications are accompanied by a How To Guide to explain the BIAN Design
Concepts & Principles, Content Development and emerging Deployment Approaches
Being piloted: BIAN Business
Vocabulary
Service Operations
Business Scenarios
Excel ModelExtract
‘Value Chain’ Layout - Internal
29
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
Contents
Agenda
BIAN Service Landscape V5.0
1. Context
V3.0, V4.0 & V5.0
Design Foundation
Summary of V4.0 Approach
Summary of V5.0 Approach
2. Key Changes/Additions to the Standard
Wireframe/First Order Connections
Generic Artifacts
Service Domain Business Events
Service Domain Information Profile
3. V5.0 Deliverables and Status
4. V5.0 Tooling
5. Direction for V6.0 – Options under consideration
30
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
4. V5.0 Tooling
Tooling
BIAN uses an integrated collection of tools. The addition of the Web Tool fills out the range
of available tools. The membership will be polled to determine if and how the initial tooling
should be enhanced
Reporting &
Version
Management
Web Tool
UML
Interface(Magicdraw)
UML
MagicDraw
Repository(Magicdraw)
UML
Download
HTML
Browser
MS Excel
Extract
BIAN
Wiki
JIRA
Workflow
31
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
4. V5.0 Tooling
Tooling – Web tool – used to generate content
A checklist of business events is defined under categories origination/invocation/reporting
& delegation for each primary Service Domain. Each business event provides the basis for
deriving a first order business scenario:
Business Events for a ‘primary’ Service Domain are
defined under four general categories:• Origination – creates a new Control Record
(CR) instance
• Invocation – acts on an existing CR instance
• Reporting – get details of current CR instances
• Delegation – calls to other Service Domains
Each Business Event is translated into a
corresponding Business Scenario that shows the
triggering caller and any dependent delgations made
by the ’primary’ Service Domain’. These are defined
to the ‘First Order’ interactions for the event
Primary
SD
32
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
4. V5.0 Tooling
Tooling – Web tool – used to generate content
The tool is web based with largely automated upload capabilities to the UML database
where integrity checks are performed and an HTML view and Excel Extract is supported
3 – Business Events and the associated
‘First Order’ Business Scenarios are
outlined for each Primary Service Domain
4 – The tool organizes the Business Scenarios
for each Primary Service Domain
2 – Primary & Secondary Service Domain
selections focus the design work…
1 - Provisional content was developed for
all active Working Groups…
33
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
4. V5.0 Tooling
Tooling – Web tool – used to generate content
The tool is web based with largely automated upload capabilities to the UML database
where integrity checks are performed and an HTML view and Excel Extract is supported
7 – The tool enabes the user to quickly select
triggering and delegated Service Domains
8 – Finally the user selects the most appropriate service
operations and the tool generates the Business Scenario
6 – Service Operation connections are predefined
but easily added when necessary
5 – A general description and name is generated and
the Wireframe shown for the selected Business Event
34
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
5. Direction for V6.0 – Options Under Consideration
Agenda
BIAN Service Landscape V5.0
1. Context
V3.0, V4.0 & V5.0
Design Foundation
Summary of V4.0 Approach
Summary of V5.0 Approach
2. Key Changes/Additions to the Standard
Wireframe/First Order Connections
Generic Artifacts
Service Domain Business Events
Service Domain Information Profile
3. V5.0 Deliverables and Status
4. V5.0 Tooling
5. Direction for V6.0 – Options under consideration
35
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN Service Landscape V5.0 – November 2016
5. Direction for V6.0 – Options Under Consideration
The prioirities for V6.0 will be
discussed at the upcoming
BIAN Board Meeting
36
Copyright BIAN 2014 | Banking Industry Architecture Network
BIAN’s Internal Wiki and Official Homepage
37
Copyright BIAN 2016 | Banking Industry Architecture Network
BIAN is a member driven organization
38
Intellectual Property
BIAN Intellectual
property policy
WG membership
triggers IPR Policy
Members surrender IP
on contributions to
WG’s
Members warrant that
all WG contributions
are their IPR
BIAN deliverables are
royalty free
Fees (annual membership)
Software / Tech vendors /
Integrators (250 employees
or more)
EUR 30.000,-
• Banks / FI’s that are not
vendors
EUR 20.000,-
• Software / Tech vendors /
Integrators (less than 250
employees)
EUR 10.000,-
Software / Tech vendors /
Integrators
(less than 50 employees)
EUR 5.000,-
Federal Banks / Central
Banks
EUR 10.000,-
Academic Partners EUR
0,-
Copyright BIAN 2014 | Banking Industry Architecture Network39
Model for Gradually Increased Engagement in BIAN
See above – in addition:
Active engagement in 1 Service Definition Working Group / 1 Architecture
Working, for example:
Service Definition Group: WG Business Partner or Lending
Architecture: Service Landscape (alternatively: Architecture Framework and
Foundation)
Active engagement in
area relevant to
Member
In addition approx. 10
PDs*) per working group per
year (mainly virtual
collaboration once every 2 -
3 weeks for 1 - 1.5 hrs)
*) PDs = Person Days
Engagement Level 3: Active Contribution
6-9 PDs*) per member
representative per year
Member contributing membership fee to support funding of third party
resources
Access to BIAN internal wiki, including work in progress (e.g. documents
currently under review)
Engagement limited to participation in physical BIAN Core Team Meetings
Next event: November 29 -31, 2016 at PNC bank, Pittsburgh, USA
Engagement Level 1: Membership and Limited Engagement Financial and Marketing
Support
Network
See above – in addition:
Participation in Document reviews – Contribution to Quality Assurance
Virtual or physical review sessions with other subject matter experts
Recently finalized documents prior to final approval and publication
Guidance through
Participation in Reviews
In addition approx. 2
PDs*) per expert review:
Prep., guidelines, review)
Engagement Level 2: Participation in (virtual) Reviews