. .

From Complexity to Clarity: Mapping Interconnections and Interdependencies for Operational Resilience
OR BB P2S2_MII_01

[OR] [P2] [S2] [MII] [C17] Case Study – Banking Sector CBS Mapping

Operational Resilience eBook Series Full Banner

To translate theory into practice, this chapter presents a banking sector case study illustrating how to map interconnections and interdependencies for Critical Business Services (CBS). The objective is to demonstrate how mapping moves from high-level identification to end-to-end dependency visibility, enabling actionable operational resilience outcomes.

The case study focuses on two commonly identified CBS in banks:

  • CBS-1: Deposit & Account Services
  • CBS-2: Payments & Funds Transfer Services

These services are foundational to banking operations and are typically prioritised by regulators and institutions due to their customer impact, systemic importance, and regulatory significance.

New call-to-action

Moh Heng Goh
Operational Resilience Certified Planner-Specialist-Expert

New call-to-action

[P2] [S2] Chapter 17

Operational Resilience eBook Series Full Banner

Case Study – Banking Sector CBS Mapping

Introduction

0017 OR War Room cinematic photograph

To translate theory into practice, this chapter presents a banking sector case study illustrating how to map interconnections and interdependencies for Critical Business Services (CBS). The objective is to demonstrate how mapping moves from high-level identification to end-to-end dependency visibility, enabling actionable operational resilience outcomes.[OR] [P2] [S2] [MII] [C17] Case Study – Banking Sector CBS Mapping

The case study focuses on two commonly identified CBS in banks:

  • CBS-1: Deposit & Account Services
  • CBS-2: Payments & Funds Transfer Services

These services are foundational to banking operations and are typically prioritised by regulators and institutions due to their customer impact, systemic importance, and regulatory significance.

Purpose of the Chapter

OR Mapping Interconnections and Interdependencies BCMPedia

The purpose of this chapter is to:

  • Provide a practical illustration of CBS mapping
  • Demonstrate end-to-end dependency mapping
  • Show how interconnections span people, processes, technology, and third parties
  • Highlight how mapping supports operational resilience analysis

 

 

Overview of Selected CBS

CBS-1: Deposit & Account Services

This CBS includes services related to:

  • Customer onboarding and account opening
  • Deposit and withdrawal transactions
  • Account maintenance and servicing
  • Balance reporting and statements

Key Characteristics:

  • High customer dependency
  • Continuous availability expectations
  • Regulatory reporting requirements

 

CBS-2: Payments & Funds Transfer Services

This CBS includes services related to:

  • Domestic and cross-border payments
  • Fund transfers between accounts
  • Bill payments and standing instructions
  • Clearing and settlement processes

Key Characteristics:

  • Time-critical processing
  • Integration with external payment networks
  • High systemic importance

 

End-to-End Mapping Approach

For both CBS, mapping follows an end-to-end service delivery approach, covering:

  1. Service initiation
  2. Processing and validation
  3. Execution and settlement
  4. Completion and reporting

Each stage is supported by:

  • Processes
  • People
  • Technology
  • Data
  • Third-party providers

 

CBS-1: Deposit & Account Services – Dependency Mapping

Sub-CBS Structure

Sub-CBS Code

Sub-CBS

1.1

Customer Onboarding & Account Application

1.2

Customer Identification & Verification (KYC/CDD)

1.3

Account Approval & Opening

1.4

Deposit Transactions Processing

1.5

Withdrawal & Funds Access Processing

1.6

Account Servicing & Maintenance

1.7

Statement & Balance Reporting

 

Sample Dependency Mapping

Sub-CBS

Dependency Type

Dependency Detail

Connectivity

Customer Onboarding

Process

Customer data collection workflow

Initiates onboarding process

KYC Verification

Technology

KYC System

Validates customer identity via API

Account Opening

People

Operations Officer

Approves and activates account

Deposit Processing

Technology

Core Banking System

Processes deposit transactions

Withdrawal Processing

Third Party

ATM Network

Enables cash withdrawal

Account Servicing

Data

Customer Database

Supports updates and maintenance

Reporting

Technology

Reporting System

Generates statements

 

Key Observations

  • Heavy reliance on core banking systems (shared dependency)
  • Integration with external networks (ATM, KYC providers)
  • Sequential dependencies across onboarding → approval → activation
  • Potential concentration risk in centralised systems and data platforms

 

CBS-2: Payments & Funds Transfer – Dependency Mapping

Sub-CBS Structure

Sub-CBS Code

Sub-CBS

2.1

Payment Initiation

2.2

Authentication & Authorisation

2.3

Fraud Detection & Risk Screening

2.4

Funds Availability Check

2.5

Payment Routing & Processing

2.6

Clearing & Settlement

2.7

Transaction Posting & Notification

 

Sample Dependency Mapping

Sub-CBS

Dependency Type

Dependency Detail

Connectivity

Payment Initiation

Technology

Mobile Banking App

Captures customer request

Authentication

Technology

Authentication System

Verifies user identity

Fraud Screening

Technology

Fraud Detection Engine

Screens transactions

Funds Check

Data

Account Balance Database

Validates funds availability

Payment Processing

Technology

Payment Engine

Executes transactions

Clearing & Settlement

Third Party

Payment Network

Processes interbank settlement

Notification

Technology

Notification System

Sends transaction alerts

 

Key Observations
  • Strong reliance on external payment networks (external dependency)
  • Multiple real-time system integrations (API connectivity)
  • Sequential dependencies with high time sensitivity
  • Concentration risk in authentication and payment processing systems

 

End-to-End Interdependency Illustration

Combined Dependency Flow

An example of end-to-end interconnection for a payment transaction:

  1. Customer initiates payment via mobile app
  2. Authentication system verifies identity
  3. Fraud detection engine screens transaction
  4. Core banking system checks funds
  5. Payment engine processes transaction
  6. External payment network performs clearing
  7. Settlement occurs between banks
  8. Notification system confirms transaction

 

Interdependency Characteristics
  • Sequential Dependencies: Each step must occur in order
  • Shared Dependencies: Core banking and authentication systems support multiple CBS
  • External Dependencies: Payment networks and third-party providers
  • Data Dependencies: Continuous data flow across systems

 

Key Risks Identified

Single Points of Failure

  • Core banking system
  • Authentication platform

Critical Dependencies

  • Payment processing engine
  • KYC system
  • Customer database

Concentration Risks

  • Single cloud or infrastructure provider
  • Centralised data centres
  • Shared third-party vendors

 

Link to Operational Resilience

 Impact Tolerance
  • Mapping identifies critical points affecting downtime thresholds
  • Helps define acceptable disruption levels

 

Scenario Testing
  • Enables design of realistic scenarios such as:
    • Payment network outage
    • Core banking system failure
    • Cyberattack on authentication systems

 

Recovery Planning
  • Supports prioritisation of recovery actions
  • Ensures restoration of end-to-end service delivery

 

Lessons Learned

1. Service-Centric Mapping is Critical

Focusing on CBS ensures alignment with customer outcomes and regulatory expectations.

2. Interdependencies are Complex and Multi-Layered

Dependencies span across internal systems, external providers, and data flows.

3. External Dependencies Drive Risk Exposure

Third-party and ecosystem dependencies significantly influence resilience.

4. Mapping Enables Actionable Insights

Identifies vulnerabilities, concentration risks, and recovery priorities.

 

New call-to-action

This case study demonstrates how interconnection and interdependency mapping can be applied in a banking context to provide end-to-end visibility of Critical Business Services.

By mapping:

  • CBS-1: Deposit & Account Services
  • CBS-2: Payments & Funds Transfer Services

organisations can clearly understand how services are delivered, where dependencies exist, and how disruptions may propagate.

The outcome is a comprehensive and actionable view of operational resilience, enabling:

  • Better risk identification
  • More effective scenario testing
  • Stronger recovery planning

Ultimately, this practical illustration reinforces the central theme of this eBook—moving from complexity to clarity, ensuring that interconnections and interdependencies are not only mapped, but fully understood and effectively managed.

 

Operational Resilience eBook Series Thin Banner

C1 C2 C3 C4 C5 C6
[OR] [P2] [S2] [MII] [C1] Introduction to Interconnections and Interdependencies [OR] [P2] [S2] [MII] [C2] Why Mapping is Critical for Operational Resilience [OR] [P2] [S2] [MII] [C3] Core Components of Interconnections and Dependencies [OR] [P2] [S2] [MII] [C4] Step 1 – Define Scope of Mapping [OR] [P2] [S2] [MII] [C5] Step 2- Identify Data Sources [OR] [P2] [S2] [MII] [C6] Step 3 – Develop Mapping Framework
C7 C8 C9 C10 C11  C12
[OR] [P2] [S2] [MII] [C7] Step 4 – Map Processes and Resources [OR] [P2] [S2] [MII] [C8] Step 5 – Map Interconnections and Interdependencies [OR] [P2] [S2] [MII] [C9] Step 6 – Validate Mapping [OR] [P2] [S2] [MII] [C10] Step 7 – Analyse Mapping Outputs [OR] [P2] [S2] [MII] [C11] Mapping Tools and Techniques [OR] [P2] [S2] [MII] [C12] Standard Templates and Data Structures
C13 C14 C15 C16 C17  C18
[OR] [P2] [S2] [MII] [C13] Integration with Operational Resilience Framework [OR] [P2] [S2] [MII] [C14] Mapping Third-Party and Supply Chain Dependencies [OR] [P2] [S2] [MII] [C15] Mapping for Digital and Cloud Environments [OR] [P2] [S2] [MII] [C16] Common Challenges and Pitfalls [OR] [P2] [S2] [MII] [C17] Case Study – Banking Sector CBS Mapping [OR] [P2] [S2] [MII] [C18] Governance and Ownership of Mapping
C19 C20 C21 C22    
[OR] [P2] [S2] [MII] [C19] Using Mapping for Scenario Testing [OR] [P2] [S2] [MII] [C20] Maintaining and Updating Mapping [OR] [P2] [S2] [MII] [C21] Key Takeaways and Future Direction [OR] [P2] [S2] [MII] [C22] Back Cover    

 

More Information About OR-5000 [OR-5] or OR-300 [OR-3]

To learn more about the course and schedule, click the buttons below for the OR-300 Operational Resilience Implementer course and the OR-5000 Operational Resilience Expert Implementer course.

BL-OR-3 Register Now BL-OR-3_Tell Me More BL-OR-3_View Schedule
BL-OR-5_Register Now BL-OR-5_Tell Me More  [BL-OR] [3-4-5] View Schedule
[BL-OR] [3] FAQ OR-300

If you have any questions, click to contact us.Email to Sales Team [BCM Institute]

FAQ BL-OR-5 OR-5000
OR Implementer Landing Page

New call-to-action

New call-to-action

 

Comments:

 

CTA Banner_OR

CTA Banner_ORA

CTA Banner_BCM

CTA Banner_ITDR

CTA Banner_CM