Virtusa | Fast-track and future-proof core banking transformation leveraging BIAN

Case Study

Zafin Integral to the Success of BIAN’s Second Coreless Banking Proof of Concept

Case Study

RedHat | Build a modern core banking platform

Case Study

TCS | BIAN: Powering purpose-driven, future-ready banks

In the race to stay ahead, provide best-in-class customer service, and meet ever increasing market demands, banks have bolted on digital capabilities in an ad hoc manner introducing considerable complexity into the underlying IT architecture. Today, most traditional banks operate with a complex, unmanageable IT architecture with duplicate systems and data impeding speed-to-market for new products and services. Increasingly inflexible legacy systems have resulted in business silos and monolithic applications that hinder agility and adversely impact the pace of key transformation initiatives.

To stay relevant, incumbent banks must foray into areas beyond traditional banking spaces by stepping into their customers’ lives at the right time with the right product. This will require banks to embrace purpose-driven business models through new partnerships with larger ecosystem partners, which in turn will require architectural readiness and plug-and-play integrations to enable ecosystem play. While banking channels are increasingly adopting digitalization to deliver beyond banking services, pain points around legacy architecture remain. In our view, to address these pain points, transition to purpose-driven ecosystem models and become future-ready, banks must adopt the Banking Industry Architecture Network (BIAN) standard. This article focuses on BIAN adoption trends and journeys.

Case Study

TCS | BIAN Business IT Alignment Adoption
TCS | BIAN APIs and Microservices Adoption

Cognizant | Core Banking Transformation at a top North American bank
leveraging BIAN

Case Study

BIAN Member Case Studies

Download an overall summary of Adoption examples

Case Studies

ArchiMate’ Modeling Notation for the Financial Industry Reference Model: Banking Industry Architecture Network (BIAN)

This document provides guidance on how the ArchiMate Specification, a standard of The Open Group, can be used to exploit the value of the Banking Industry Architecture Network (BIAN) Financial Industry Reference Model.

It is designed to provide a guide to anyone involved or interested in how to manage the transition to a digital financial institution. It guides an Enterprise Architecture organization to develop an agile, lean, and stable banking architecture using the ArchiMate language and BIAN.

Patrick Derde, EnVizion, BIAN & Martine Alaerts, EnVizion

Case Study

Archi Banking Group: Combining the BIAN Reference Model, ArchiMate’ Modeling Notation, and the TOGAF’ Framework

This Case Study is a fictitious example developed to illustrate the combined use of the Banking Industry Architecture Network (BIAN) Reference Model with the ArchiMate’ modeling notation and the TOGAF’ framework (both standards of The Open Group). The ArchiMate and TOGAF concepts used in this Case Study can be applied to different situations. The use of the BIAN Reference Model supports addressing typical financial industry concerns.

Patrick Derde, EnVizion, BIAN & Martine Alaerts, EnVizion

Case Study

PNC Financial Services Group

The BIAN model fits perfectly in line with how we view enterprise architecture (EA) at PNC. One of the first steps we took as an organisation was to bring a business perspective to enterprise architecture. To us, technology is not just a collection of servers and software, but rather a set of technical solutions that are aligned to specific business capabilities and functions.

Steven Van Wyk, Executive Vice President, Head of Technology and Operations, PNC Financial Services Group Read case study

Cognizant Technology Solutions, led by Sanghosh Bhalla, Niloy Sengupta and Akshaya Bhargava from the firm’s Banking and Financial Services Consulting practice, recently helped a top three North American bank, adopt BIAN and optimize their enterprise portfolio of applications that support business functions across all of its business units.

Sanghosh Bhalla, Niloy Sengupta and Akshaya Bhargava, Cognizant Read Case Study
Asseco SEE

As a vendor that grew through acquisitions, we inherited a rich collection of applications that have their application specific interfaces. Applications that had similar scope ended up having their specific interfaces for essentially the same responsibilities. One of our strategic goals was to cut integration time and cost and over time achieve plug-and-play interoperability between different applications in our portfolio.

Aleksandar Milosevic, Chief Software Architect at banking software provider Asseco SEE Read case study