BIAN Introduction BY BABAK DARVISH ROUHANI (PHD) SALEH RAD 1 - - PowerPoint PPT Presentation

bian
SMART_READER_LITE
LIVE PREVIEW

BIAN Introduction BY BABAK DARVISH ROUHANI (PHD) SALEH RAD 1 - - PowerPoint PPT Presentation

BIAN Introduction BY BABAK DARVISH ROUHANI (PHD) SALEH RAD 1 Enterprise Architecture 2 Enterprise Architecture Enterprise Architecture (EA) To align Business and Information Technology To integrate environment for enterprise EA


slide-1
SLIDE 1

BIAN Introduction

BY BABAK DARVISH ROUHANI (PHD) SALEH RAD

1
slide-2
SLIDE 2 2

Enterprise Architecture

slide-3
SLIDE 3

Enterprise Architecture

3

Enterprise Architecture (EA)

  • To align Business and Information Technology
  • To integrate environment for enterprise

EA define :

  • As-Is Architecture
  • To-Be Architecture
  • Migration Plan
slide-4
SLIDE 4

Enterprise Architecture (Cont)

EA comprise

  • Framework
  • Methodology

4

Enterprise Architecture Framework (EAF) is

  • logical structure
  • Enterprise model

EA is designed, developed, managed, and maintained through implementation methodology. EA Implementation is effective when the intended EA’s goals are achieved.

slide-5
SLIDE 5 5

Enterprise Architecture (Cont)

slide-6
SLIDE 6

BIAN 8

6
slide-7
SLIDE 7 7
slide-8
SLIDE 8 8
  • Enterprise Management

and Controlling

  • Product and Service

Enabling

  • Enterprise Enabling
  • Bank Operation
  • Customer and Sales
  • Channels
slide-9
SLIDE 9 9
slide-10
SLIDE 10

Developer Perspective

10
slide-11
SLIDE 11 11
slide-12
SLIDE 12 BIAN Business Services DevOps Repository IFW Tooling for REST API Channel Apps Legacy Systems API Connect Tooling Swagger/Stub IFW Tooling 3rd PartyApps

API Platform

Developer Portal Scalable Runtime Security & Control Enterprise SOA Business Process Business Rules Integration withESB JavaScript/Java BPEL/WSDL/Java Linkage Deploy Banking APIs Supporting Services Customized Integration Banking Platform for APIs (Cloud or On Premise) Open Banking APIs Model Driven Development

Case Study – Model Driven Approach to BankingAPIs

slide-13
SLIDE 13 13
slide-14
SLIDE 14

Bank Perspective

14
slide-15
SLIDE 15

Overview

  • The BIAN Service Landscape provides a taxonomy of all business capabilities within a bank. Within

BIAN, each business capability is known as a Service Domain. The taxonomy enables the bank to identify what technologies are satisfying a business capability. Often, a technology will span multiple business capabilities. Depending on the desired result, this can be good or bad.

  • By leveraging interactions between Service Domains in order to satisfy a business process, banks are

able to break up the technologies that satisfy the capabilities. This results in a more component based, or service-oriented, deployment.

  • Using the Service Domains of BIAN to establish the scope of an RFI/RFP enables a bank is able to

stay focused on how various vendors satisfy the capabilities desired.

15
slide-16
SLIDE 16 16

Using The BIAN Service Landscape to Define Scope

slide-17
SLIDE 17 17

Business Scenarios

slide-18
SLIDE 18 18

Wireframes

slide-19
SLIDE 19 19

Feature Sets

Service Domain Payment Order - Payment order provides a structured service to oversee

  • ne or more payment transactions for a customer, taking into account customer specificrules

and constraints

Non-functional Operational Features Technical Architecture Features Key: Gap Needs Work Covered  Dual operations control and user access configuration  Extended office hours  Configurable workflow  High availability/security  High connectivity Payment Order Feature Description Vendor A Vendor B Feature Types Functional Initialize& Register  Automated order capture (mutiple sources)  Order details verification  Batch/scheduled payment order capture (e.g. client ACH files)  Deferred payment order capture (warehousing) Invocation & Execution  Order repair  Batch/scheduled payment order update ` `  Reversed order handling  Network availaility update Maintain & Analyze  Customer payment order entitlements/rules  Payment order return for resubmission * OFAC/regulatroy checks/  Risk/limit checks and daylight overdraft/offset rules & off-line host support  Maintain rule/format requirements (content/minimum requirements)  Payment execution with payment preferences Report & Notify  Customer payment order activity  User defined reporting and UI field definition  Notify rule/format requirements
slide-20
SLIDE 20

Using BIAN as part of an RFI/RFP process

Illustrative Bank Example

  • RFI/RFP approaches
  • “Are you BIAN compliant?”; “Are you BIAN certified?”
  • Structuring the RFI by BIAN service domains
  • Lessons learned from a vendor
  • Provides vendor a straight forward approach to understandscope
  • Quick and powerful communication vehicle for thevendor
  • Strong involvement of the bank’s architecture management teamhelpful
  • Look out for Core Banking analysts adoptingBIAN
20
slide-21
SLIDE 21
  • By leveraging the Service Landscape, Business Scenarios, Wireframes, and Feature Sets, a

Bank successfully defines scope and can assess vendor ability to meet the requirements of the

  • rganization in a component based, or service-oriented approach.
21
slide-22
SLIDE 22

Vendors Perspective

22
slide-23
SLIDE 23

Overview

  • BIAN is ready to be used as a structural element within a bank’s business transformation

journey

  • From a vendor perspective BIAN helps articulating scope and strength of a vendors solution
  • It offers vendors the opportunity to utilize BIAN as a structural element of the vendor’s architecture

framework and business transformation methodology

23
slide-24
SLIDE 24 24

The Banking Architecture Framework fromSAP: SPRINT – Leveraging BIAN

Business Architecture Business Process Message Flow Application Architecture Capability Model BIAN Service Landscape Business Object Model C u s tomer & S e g m e nt MICROSOFT CORPORATION E n t e r p r i s e S e r v i c e s P r o d u c t F a c t o r y C h a n n e l S e r v i c e s B a n k i n g S e r v i c e s a n d O p e r a t i o n s P r e
  • S
a l e s A s s i s te d C h a n n e l s D i r e c t C h a n n e l s S e r v i c i n g Payments O r i g i n a t i
  • n
S a l e s / C r
  • s
s S a l e C u s t
  • m
e r I n f
  • r
m a t i
  • n
M a n a g e m e n t O p e r a t i
  • n
a l D a t a P r
  • d
u c t S e r v i c e s M g m t . M a n a g e m e n t L e n d i n g P r
  • d
u c t s D e p
  • s
i t P r
  • d
u c t s T r a d e P r
  • d
u c t s B i l l i n g a n d M e r c h a n t P r
  • d
u c t s C a p i ta lM a r k e ts P r
  • d
u c t s S t r a t e g ya n d M a r k e t F i n a n c ea n d R i s k T e c h n
  • l
  • g
y & O p e r a t i
  • n
s S u p p
  • r
t A n a l y s i s A c c
  • u
n t i n g M a n a g e m e n t M a r k e t i n ga n d C
  • m
m u n i c a tio n s H u m a nR e s
  • u
r c e s M odel B ank -Business Capability M odel (S am pl e V i ew ONLY) This model and related content is property of SAP. Please do not distribute
  • utside
SAP. E n h an ce Foundati
  • n
al New E
  • L/
Replace Gap # Initiative Number B u s i n e s s Capability H e a t
  • M
a p P r
  • d
u cts MaturityA n a ly s is Introductory S t a g e G r
  • w
th S t a g e M a turity S t a g e DeclineS t a g e Total L ife C y c l e T im e Distribution Channels Analysis

Sales Planning Execution

Business Case& Validation Design & Blueprint Realization Run & Optimization Vision & Strategy
slide-25
SLIDE 25
  • By using the BIAN deliverables you create a common language between the Bank and the

service Provider.

  • The BIAN Service Landscape provides a comprehensive “Bank on a Page” that enables

both Banks and Vendors to clearly define their agreed migration strategy.

25
slide-26
SLIDE 26

Case Study

26
slide-27
SLIDE 27 27 Business Area Business Domain Service Domain Business Role TYPE Service Operation Full Name Input Parameters Output Parameters Comment
slide-28
SLIDE 28
slide-29
SLIDE 29
slide-30
SLIDE 30

RUP- SOMA

30
slide-31
SLIDE 31

RUP-SOMA

31
slide-32
SLIDE 32

RUP-SOMA (Cont)

32
slide-33
SLIDE 33

Discussion

33
slide-34
SLIDE 34

Bank - EA

34
slide-35
SLIDE 35

Q&A Q&A

35
slide-36
SLIDE 36 36

Thanks