SL 5.0 Release Note 1.0

BIAN Service Landscape 5.
0 Release Note
Banking Industry
Architecture Network
BIAN
Release Note
Service Landscape 5.0
© 2016 BIAN e.V. | P.O. Box 16 02 55 | 60065 Frankfurt am Main | Germany Page 1 of 16
BIAN Service Landscape 5.0 Release Note
Organization
Authors
Role Name Company
BIAN Architect Jack Lowe BIAN
Version
No Comment / Reference Date
0.1 1st Draft based on V4.5 Release Note 19th Sept 2016
1.0 First published version 21st Sept 2016
Page 2 of 16 © 2016 BIAN e.V. | P.O. Box 16 02 55 | 60065 Frankfurt am Main | Germany
Copyright
© Copyright 2016 by BIAN Association. All rights reserved.

THIS DOCUMENT IS PROVIDED "AS IS," AND THE ASSOCIATION AND ITS MEMBERS, MAKE
NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
NONINFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THIS DOCUMENT ARE SUITABLE FOR ANY
PURPOSE; OR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY
PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
NEITHER THE ASSOCIATION NOR ITS MEMBERS WILL BE LIABLE FOR ANY DIRECT,
INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR
RELATING TO ANY USE OR DISTRIBUTION OF THIS DOCUMENT UNLESS SUCH DAMAGES ARE
CAUSED BY WILFUL MISCONDUCT OR GROSS NEGLIGENCE.
THE FOREGOING DISCLAIMER AND LIMITATION ON LIABILITY DO NOT APPLY TO, INVALIDATE,
OR LIMIT REPRESENTATIONS AND WARRANTIES MADE BY THE MEMBERS TO THE
ASSOCIATION AND OTHER MEMBERS IN CERTAIN WRITTEN POLICIES OF THE ASSOCIATION.
Table of contents
1 Overview of Release 5.0.................................................................... 5
2 SL 4.5/5.0 Features ........................................................................... 7
2.1 Naming of Generic Artifacts ...................................................................................... 7
2.2 Naming of Functional Patterns, Control Records and Service Operations ................ 7
2.3 Business Information ................................................................................................ 8
2.4 TOGAF and Archimate ............................................................................................10
2.5 BIAN Web Application .............................................................................................11
2.6 Vocabulary ..............................................................................................................11
2.7 Additional Service Domains .....................................................................................11
2.8 Service Operation Connections ...............................................................................13
2.9 Additional Business Scenarios.................................................................................15
2.10 How-to Guides ....................................................................................................16
1 Overview of Release 5.0

This overview summarizes
Introduction
The BIAN Service Landscape 4.5 release was an intermediate release where many
new deliverables were added to the model. The main objective of the release was to
add 600+ candidate business scenarios which have been, to a great extent,
harvested by the BIAN central team and aided by the individual working groups.
Release 5.0 is a more formal release and includes revised user documentation,
additional content and improvements to the web app productivity tool. Some review
and revision of the 4.5 content has been conducted by the BIAN service definition
working groups, however, most of the initial content is still pending review and is in
‘Provisional’ status. It is intended that content will continue to undergo review/revision
and that updated content will be made available via frequent minor releases.
Business information is now associated with Service Domains via the Service
Domain Control Records. This business information is a comprehensive set of
semantic information and is available for every Service Domain. The SL 4.0 Service
Operations are replaced by SL 4.5/5.0 Service Operations which contain this new
business information.
Relationships between Service Domains are now recorded in the form of information
exchanges, comprising the BIAN action term and a freeform description of the
purpose of the exchange, e.g. ‘RetrieveGet correspondent bank details’ where
‘Retrieve’ is the BIAN action term.
As an add-on to the BIAN Service Landscape 4.5/5.0, a productivity tool has been
built which enables the BIAN Working Groups to define new information exchanges
and create new business scenarios. The same tool includes a business vocabulary
which defines BIAN terms. This tool will be made available to BIAN members only.
Content
The following new deliverables are included in the BIAN Service Landscape 4.5/5.0
release:
- Updated UML model and metamodel
o Business information associated with Service Domain Control Records
o Service Operations have been replaced and include this new business
information
- Additional business scenarios
o Over 900 new candidate business scenarios have been defined.
- Vocabulary
o A vocabulary has been created and populated with initial information.
This will be extended on a continual basis and is available to members
via the web app productivity tool https://bian.w38.io/sl5/.
- Additional Service Domains
o 18 new candidate Service Domains (and their associated Control

Records & Service Operations) have been identified and included in the
4.5/5.0 model.
o Easier mapping to Archimate, and the St Gallen/CC Sourcing models.
Mapping of terminology with TOGAF.
Limitations to use
Some of the Release 5.0 deliverables will only be available to BIAN members,
however, the following will be made available on the public bian.org site:
 V 5.0 user documentation in the form of How-to Guides
 HTML rendition of the V5.0 UML model and metamodel
Some content in Release 5.0 is in ‘Provisional’ status. Provisional status materials

have not undergone a formal review and approval cycle. The vast majority of
business events, scenarios and service connections that have been newly introduced
in version 4.5/5.0 are in Provisional status pending further review and approval by the
service definition working groups.
The new scenarios show ‘first order’ connections only. For a given Service Domain, a
scenario shows the connection/exchange between the calling Service Domain and
the given Service Domain plus the connections/exchanges between the given
Service Domain and those that it calls directly. The scenario does not show second
(& subsequent) order connections where the called Service Domain delegates to
other Service Domains.
- .
2 SL 4.5/5.0 Features
2.1 Naming of Generic Artifacts
Some Generic Artifact names have been changed. The revised names are
highlighted below:
SL 4.0 Generic Artifact SL 4.5/5.0 Generic Artifact

AdministrativePlan AdminstrativePlan
Agreement Agreement
Allocation Allocation
Analysis Analysis
Assessment Assessment
Specification Specification
DevelopmentPlan DevelopmentProject
Strategy Strategy
Enrollment Membership
ProductArrangement FulfillmentArrangement
MaintenanceAgreement MaintenanceAgreement
ManagementPlan ManagementPlan
Measurement Measurement
OperatingSession OperatingSession
Procedure Procedure
Registration Directory
Account/Log Log
Transaction Transaction
2.2 Naming of Functional Patterns, Control Records and Service

Operations
The naming of Functional Patterns has been made more consistent such that all
names are verbs rather than nouns. The new names are shown below:
SL 4.0 Functional Pattern SL 4.5/5.0 Functional

Pattern
Administration Administer
Agreement Agree Terms
Allocation Allocate
Analysis Analyze
Assessment Assess
Design Design
Development Develop
Direction Direct
Enrollment Enroll
Fulfillment Fulfill
Maintenance Maintain
Management Manage
Measurement Monitor
Operation Operate
Processing Process
Registration Register
Account/Log Track
Transaction Transact
Service Domain Control Records have been renamed. In SL 4.0, the naming
convention was <AssetType><FunctionalPattern>. In SL 4.5/5.0, the naming
convention is <AssetType><GenericArtifactType>. Examples of new names are
shown below. Note that in some cases, the new and old names are identical despite
the naming convention since some SL 4.0 Functional Pattern names are the same as
some SL 4.5/5.0 Generic Artifact Types.
SL 4.0 Control Record Name SL 4.5/5.0 Control

Record Name
BusinessUnitAccountingAccount/Log BusinessUnitAccountingLog
BrokerAgreement BrokerAgreement
SegmentDirection SegmentStrategy
CreditRiskModelDesign CreditRiskModelSpecification
Since the Control Records have been renamed, some Service Operation names are
changed. For example, the service operation ‘notifyPointOfServiceOperation’ has
been replaced with the service operation ‘notifyPointOfServiceOperationSession’. As
with Control Records, some Service Operation names will be unchanged.
2.3 Business Information

A set of Business Information is now associated with Service Domain Control
Records. The Business Information is classified according to its type of use as per
these examples:
The Business Information associated with a Service Domain Control Record is partly
determined by its Functional Pattern. Most of the information is generic across all
Service Domains but some is Functional Pattern Specific (see the above example).
For example, the Control Record for the Service Domain ‘Building Maintenance’ has
a functional pattern of ‘Maintain’ and includes the business information item
‘resourceType’ whereas the Control Record for Service Domain ‘Currency Exchange’
has a functional pattern of ‘Transact’ and includes the Business Information item
‘financialTransaction’.
The SL 4.5/5.0 Service Operations provide access to this Business Information as

Input/Output parameters.
2.4 TOGAF and Archimate
BIAN concepts have been mapped to Archimate and TOGAF. This mapping is
detailed in an Excel file on the Wiki at
https://biancoreteam.atlassian.net/wiki/display/SL/Documents. At the same location is
a webcast that explains this mapping.
Sample contents from the mapping file is shown below:
2.5 BIAN Web Application

A web app has been written for BIAN and is accessible to BIAN members only at
https://bian.w38.io/sl5. In SL 5.0, it has two main areas:
 Content development for service definition working groups
 Vocabulary
For guidelines on using this web app, study the online help files within the app or
reference the quick start guide on the Wiki at
https://biancoreteam.atlassian.net/wiki/display/SL/Documents.
.
2.6 Vocabulary
A Vocabulary is being created for BIAN concepts and is accessible via the BIAN web
app. The goals of the vocabulary (for SL 5.0) are limited to providing definitions of
BIAN specific terms. The vocabulary does not attempt to provide a full glossary of
banking terms, neither does it attempt to define IT technology terms other than those
which are directly relevant to BIAN.
The Vocabulary has a limited set of content at this time but will be extended over
time.
2.7 Additional Service Domains

18 new Service Domains have been included in SL 4.5/5.0. These are all in
‘Provisional’ status pending further review and approval by the service definition
working groups.
The new Service Domains and their related service definition working groups are
shown below:
Service Definition Business Service Domain Service Role

Working Group Domain
Retail Banking & Consumer Consumer Advisory Provide consumer financial advice
Consumer Finance Services Services
Retail Banking & Loans and Savings Account Fulfill a savings account
Consumer Finance Deposits
Retail Banking & Consumer Trust Services Provide trust services
Consumer Finance Services
Retail Banking & Account Customer Position Maintain a consolidated financial
Consumer Finance Management position of a customer
Retail Banking & Customer Customer Precedents Maintain/track the status of customer
Consumer Finance Management precedents
Retail Banking & Customer Customer Reference Maintain customer reference
Consumer Finance Management Data Management information
Product & Price Account Product Combination Product Combination is executing all
Management combined product facilities which
cannot be allocated to a single product
in the product bundle. The fulfillment
will mainly focus on (but is not limited
to) the bundled pricing of the Product
Combination resulting into fees, charges
and equivalents such as bonus points.
Product & Price Product Product Directory Keep information about the basic
Management product building blocks, represented as
Product Components with Functions
and Features, as well as the completed
product specification from SD Product
Design.
Product & Price Product Special Pricing Maintain a price list or single conditions
Management Conditions (with ranges and optional terms) by
various dimensions, e.g. customer
segment (e.g. employee conditions), for
exceptional product independent pricing
conditions that override standard
pricing derived from the pricing product.
Product & Price Customer Customer Proposition Example of use: The bank implements a
Management service fee waiver that applies to all of
the products for a customer. General
Comment:
The Service Domain maintains various
servicing and fulfillment obligations for
a customer that apply across all
products. This supports a further layer
of customer specific fulfillment for
products based on the customer and/or
customer type. For example, the

Customer Proposition may define an
'across the board' fee reduction, applied
interest rate margin or waived servicing
fee type. These obligations are
referenced by all applicable product
fulfillment Service Domains where the
proposition is enforced.
x
Product & Price Consumer Service Product Represent the general facility at the
Services core of the consumer and small business
banking activity. The fulfillment will
focus on the pricing of the Service
Product resulting in fees , charges, and
equivalents such as bonus points
Payments Payments ACH Fulfillment Operate the ACH access gateway

Retail Loans and Consumer Loan Fulfillment of a range of loan products
Deposits for consumer clients
Retail Loans and Corporate Loan Fulfillment of a range of loan products
Deposits for corporate clients
Retail Loans and Corporate Lease Fulfillment of a range of loan products
Deposits for corporate clients for the purpose of
leasing
Retail Loans and Merchandising Loan Fulfillment of a range of loan products
Deposits intended for the purchase of a larger
merchandise item such as a car or boat.
The item may be treated as collateral for
the loan
Retail Loans and Mortgage Fulfillment of a range of loan products
Deposits for the purpose of property purchase
Retail Loans and Fiduciary Agreement Fulfillment of a range of loan products

Deposits on behalf of a fiduciary
2.8 Service Operation Connections

Service Operation Connections have been defined for hundreds of exchanges
between Service Domains. In the BIAN web app, connections can be viewed, added
or edited and appear as per this example:
An Excel extract of the BIAN UML model lists all of the known connections for a
Service Domain as per this example:
More connections will be discovered over time as new business scenarios are
defined.
Known connections are made visible when new business scenarios are built. In this
example, a business scenario is being created with ‘Collateral Allocation
Management’ as the primary Service Domain. Based on known connections, the user
is presented with all Service Domains which may call or be called by the primary
Service Domain:
When a Service Domain is selected for one of the steps in the scenario, the BIAN
web app will show all known connections between the Primary Service Domain and
the selected Service Domain and the user can choose the appropriate connection for
this scenario step.
2.9 Additional Business Scenarios

Over 900 Business Scenarios have been created. In SL 4.5/5.0, the new scenarios
show ‘first order’ connections only. For a given Service Domain, a scenario shows
the connection/exchange between the calling Service Domain and the given Service
Domain plus the connections/exchanges between the given Service Domain and
those that it calls directly. The scenario does not show second (& subsequent) order
connections where the called Service Domain delegates to other Service Domains.
Full details of each scenario can be viewed in the BIAN web app including the
interaction diagram:
For a given Service Domain, the Excel extract of the BIAN UML model lists all
scenarios where it is included.
2.10 How-to Guides

The BIAN How-to Guides (HTGs) have been re-written and are available to BIAN
members on the BIAN Wiki and as downloadable files on the bian.org public site.

SL 5.0 Release Note 1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SL 5.0 Release Note 1.0

Uploaded by

Copyright:

Available Formats

BIAN Service Landscape 5.

Service Landscape 5.0

© Copyright 2016 by BIAN Association. All rights reserved.

1 Overview of Release 5.0

o 18 new candidate Service Domains (and their associated Control

Some content in Release 5.0 is in ‘Provisional’ status. Provisional status materials

SL 4.0 Generic Artifact SL 4.5/5.0 Generic Artifact

2.2 Naming of Functional Patterns, Control Records and Service

SL 4.0 Functional Pattern SL 4.5/5.0 Functional

SL 4.0 Control Record Name SL 4.5/5.0 Control

2.3 Business Information

The SL 4.5/5.0 Service Operations provide access to this Business Information as

2.4 TOGAF and Archimate

Sample contents from the mapping file is shown below:

2.5 BIAN Web Application

2.7 Additional Service Domains

Service Definition Business Service Domain Service Role

customer type. For example, the

Payments Payments ACH Fulfillment Operate the ACH access gateway

Retail Loans and Fiduciary Agreement Fulfillment of a range of loan products

2.8 Service Operation Connections

2.9 Additional Business Scenarios

2.10 How-to Guides

You might also like