BIAN. Service Landscape 4.5

Transcription

1 Banking Industry Architecture Network BIAN Release Note Service Landscape BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 1 of 15

2 Organization Authors Role Name Company BIAN Architect Jack Lowe BIAN Version No Comment / Reference Date Draft Updated following review feedback Updated following second iteration of review feedback 28 th June th July th July BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 2 of 15

3 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 BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 3 of 15

4 Table of contents 1 Overview of Release SL 4.5 Features Naming of Generic Artifacts Naming of Functional Patterns, Control Records and Service Operations Business Information BIAN Web Application Vocabulary Additional Service Domains Service Operation Connections Additional Business Scenarios How-to Guides BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 4 of 15

5 1 Overview of Release 4.5 This overview summarizes Introduction The BIAN Service Landscape 4.5 release is an intermediate release where many new deliverables are added to the model. The main objective of the release has been to add 600+ candidate business scenarios which have been, to a great extent, harvested by the BIAN central team aided by the individual working groups. These candidate business scenarios will be verified and refined in the working groups in the time up to the BIAN Service Landscape 5.0 release. 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 4.0 Service Operations are replaced by 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, 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 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 700 new candidate business scenarios have been defined. These will be further reviewed & refined up to the release of the BIAN Service Landscape 5.0 release in September. - Vocabulary o A vocabulary has been created and populated with initial information. This will be extended in the 5.0 release - Additional Service Domains o 17 new candidate Service Domains (and their associated Control Records & Service Operations) have been identified and included in the 4.5 model. These will be verified and formally included in the 5.0 release BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 5 of 15

6 Limitations to use The Release 4.5 deliverables will only be available to BIAN members. All content in Release 4.5 is considered to be candidate status. Candidate status materials have not undergone a formal review and approval cycle. Content and tooling is liable to change prior to formal release in release 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. BIAN Service Landscape 5.0 release: The next major upgrade is SL 5.0 and is due for release in September SL 5.0 will incorporate all the deliverables included in the SL 4.5 release with a further refinement of business scenarios, the productivity tool, the vocabulary and business information. The following new deliverables will be included in the BIAN Service Landscape 5.0 release: - All the deliverables included in the SL 4.5 release with a further refinement of business scenarios, the productivity tool, the vocabulary and business information. - Enhanced functionality in the productivity tool enabling it to be used for navigation in the BIAN Service Landscape. - Easier mapping to Archimate, and the St Gallen/CC Sourcing models. Mapping of terminology with TOGAF BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 6 of 15

7 2 SL 4.5 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 AdministrativePlan Agreement Allocation Analysis Assessment Specification DevelopmentPlan Strategy Enrollment ProductArrangement MaintenanceAgreement ManagementPlan Measurement OperatingSession Procedure Registration Account/Log Transaction SL 4.5 Generic Artifact AdminstrativePlan Agreement Allocation Analysis Assessment Specification DevelopmentProject Strategy Membership FulfillmentArrangement MaintenanceAgreement ManagementPlan Measurement OperatingSession Procedure Directory Log 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 Functional Pattern Administration Agreement Allocation Analysis Assessment Design Development Direction Enrollment Fulfillment Maintenance Management Measurement Operation Administer Agree Terms Allocate Analyze Assess Design Develop Direct Enroll Fulfill Maintain Manage Monitor Operate 2016 BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 7 of 15

8 Processing Registration Account/Log Transaction Process Register Track Transact Service Domain Control Records have been renamed. In SL 4.0, the naming convention was <AssetType><FunctionalPattern>. In SL 4.5, 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 Generic Artifact Types. SL 4.0 Control Record Name SL 4.5 Control Record Name BusinessUnitAccountingAccount/Log BrokerAgreement SegmentDirection CreditRiskModelDesign BusinessUnitAccountingLog BrokerAgreement SegmentStrategy 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: 2016 BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 8 of 15

9 2016 BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 9 of 15

10 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 Service Operations provide access to this Business Information as Input/Output parameters. 2.4 BIAN Web Application A web app has been written for BIAN and is accessible to BIAN members only at This app will be extended prior to the SL 5.0 release and make it a more powerful tool for discovery and searching of the BIAN landscape. In SL 4.5, 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. 2.5 Vocabulary A Vocabulary is being created for BIAN concepts and is accessible via the BIAN web app. The goals of the vocabulary (for SL 4.5) 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 to be reasonably complete prior to SL Additional Service Domains 17 new Service Domains have been included in SL 4.5. These are candidates insofar as they are subject to review and revision before they will be approved for inclusion in SL 5.0. The new Service Domains and their related service definition working groups are shown below: Service Definition Working Group Business Domain Service Domain Service Role Retail Banking & Consumer Finance Retail Banking & Consumer Finance Consumer Services Loans and Deposits Consumer Advisory Services Savings Account Provide consumer financial advice Fulfill a savings account 2016 BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 10 of 15

11 Retail Banking & Consumer Finance Consumer Services Trust Services Provide trust services Retail Banking & Consumer Finance Account Management Customer Position Maintain a consolidated financial position of a customer Retail Banking & Consumer Finance Customer Management Customer Precedents Maintain/track the status of customer precedents Retail Banking & Consumer Finance Customer Management Customer Reference Data Management Maintain customer reference information Product & Price Account Management Product Combination Product Combination is executing all 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 Management Product Directory Keep information about the basic 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 Management Special Pricing Conditions Maintain a price list or single 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 Consumer Services Service Product Represent the general facility at the 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 Retail Loans and Deposits Loans and Deposits Corporate Loan Corporate Lease Fulfillment of a range of loan products for corporate clients Fulfillment of a range of loan products for corporate clients for the purpose of leasing 2016 BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 11 of 15

12 Retail Loans and Deposits Merchandising Loan Fulfillment of a range of loan products 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 Deposits Mortgage Fulfillment of a range of loan products for the purpose of property purchase Retail Loans and Deposits Fiduciary Agreement Fulfillment of a range of loan products on behalf of a fiduciary 2.7 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: 2016 BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 12 of 15

13 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 BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 13 of 15

14 2.8 Additional Business Scenarios Over 700 Business Scenarios have been created. In SL 4.5, 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 BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 14 of 15

15 2.9 How-to Guides The BIAN How-to Guides (HTGs) are being re-written. The guides will undergo review and revision internally prior to publication in the SL 5.0 release BIAN e.v. Platz der Einheit Frankfurt am Main Germany Page 15 of 15