Building Operational Resilience at Bank Julius Baer: A Strategic Implementation Guide
[BB] [FSI] Resilient Bank Digital Infrastructure

[OR] [BJB] [E2] [C10] Mapping Interconnections and Interdependencies of OR Implement Phase for Bank Julius Baer

[OR] [BJB] [Full Banner] Strengthening Banking Resilience A Practical Guide for Bank Julius BaerA critical business service is never delivered by one team or one system. It depends on a chain of people, processes, information, technology, third parties and facilities.

Mapping is the stage in which Bank Julius Baer (BJB) identifies, documents and understands that chain for each critical business service.

Interconnections are the links and handoffs between components, including data flows. Interdependencies are the internal and external reliance that each service has on resources, including third parties.

New call-to-action[Logo] [OR] Certification Transparent

Moh Heng Goh

BJB Legal Disclaimer BannerNew call-to-action

Introduction

[OR] [BJB] [E2] [P2] [S2] [C10] Mapping Interconnections and InterdependenciesA critical business service is never delivered by one team or one system. It depends on a chain of people, processes, information, technology, third parties and facilities. Mapping is the stage in which Bank Julius Baer (BJB) identifies, documents and understands that chain for each critical business service. Interconnections are the links and handoffs between components, including data flows. Interdependencies are the internal and external reliance that each service has on resources, including third parties.

Purpose of the Chapter

This chapter shows how to build a map for each service in seven steps. You should be able to decide how much detail is enough, use a standard template, find single points of failure and see how the map feeds impact tolerances and scenario tests. Mapping comes before risk assessment, because weaknesses must be known before likelihood and impact can be judged.

Keep the Scope Manageable

Do not map every process at once or in detail. Start with the critical processes behind each service, assign an owner and use a predefined template. For each service record the six resource types and the connections between them.

Implementation Steps

Step 1: Identify Stakeholders

Involve business unit leaders, technology and risk teams, and the service owner.

Step 2: Analyse Dependencies

Map the links between business units, systems, processes and external entities such as suppliers and regulators.

Illustrative example: for CBS-2 Client Payments and Cash Transfers, the chain starts with a client instruction through the digital channel or a relationship manager, passes through screening and approval, uses the core banking platform, and ends in a payment message sent through an external network.

Step 3: Assess Internal Interdependencies

Work out how a failure in one area affects the others: infrastructure, data centres, networks, shared teams.

Illustrative example: the screening tool and the payment approval workflow share one database. If it fails, both stop.

Step 4: Assess External Interdependencies

Review suppliers, cloud providers and reporting channels and estimate the effect of their disruption. Check that contracts provide for notification, recovery commitments and exit.

Illustrative example: the payment messaging provider and an outsourced hosting provider are rated as material third parties for CBS-2. Their recovery times are compared with the service tolerance [confirm with outsourcing register].

Step 5: Document

Build a structured inventory: criticality, dependencies, contacts, documentation and diagrams. Flowcharts help non-specialists see the chain.

Step 6: Set Up Communication Channels

Agree how owners of linked components coordinate, especially during a disruption.

Step 7: Review Regularly

Update the map when structures, systems, processes or suppliers change.

Choosing the Right Level of Detail

The most common failure in mapping is too much detail. A map that takes months to produce will be out of date before it is finished and nobody will use it. The right level of detail is the one that lets the bank answer three questions: what are the single points of failure, which third parties are essential, and what would have to be recovered together to restore the service? Start with the main chain of activities and add detail only where a weakness is found.

Using the Map

The map has several users. The tolerance stage uses it to check that recovery times of components add up to something that meets the tolerance. The testing stage uses it to design scenarios that attack the weakest links. Vendor management uses it to focus oversight on providers that support critical services. Technology uses it to prioritise recovery investment. The communication lead uses it to know who to contact. A good map is therefore stored where all these groups can find it.

Illustrative questions for a map review of CBS-3 Securities Trading and Settlement:

  • Which market data, order routing and settlement providers does the service use, and are any of them sole providers?
  • Which staff have the authority and the skills to operate the service, and who is their backup?
  • Which systems must be recovered in what order?
  • Which files, spreadsheets or manual steps are outside system control?
  • Which dependencies are shared with other critical services, such as CBS-2 and CBS-4?

Shared Dependencies

When several services depend on the same component, the combined exposure may be larger than any single map suggests. A shared database, a shared network or a single provider can bring down several services at once. Consolidate the maps into a simple matrix of services against dependencies to see where concentration exists, and take the matrix to the resilience forum.

Summary Table: Worked Example Resource Map for CBS-2

Table 10: Mapping Interconnections and Interdependencies of OR Implement Phase for Bank Julius Baer
Resource type Illustrative dependency for CBS-2 Possible single point of failure
People Payments operations team, approvers Two approvers in one location
Processes Screening, approval, release, reconciliation Manual reconciliation step
Information Client instructions, account balances Single data store
Technology Core banking platform, digital channel Shared database
Third parties Payment messaging provider, hosting provider Sole provider
Facilities Operations floor, alternate site Alternate site capacity

All entries are illustrative and need to be replaced with BJB's own records.

[Banner] [Summing] [OR] [E2] [C10] Map Interconnections and InterdependenciesConclusion

A good map is a working tool. It shows where one failure can stop a service and which dependencies deserve testing. It also gives the next stage the information it needs to set realistic tolerances.

Sources

Continue reading: Chapter 11, Establishing Impact Tolerance of OR Implement Phase for Bank Julius Baer, sets the limit of acceptable disruption.

 

[OR] [BJB] [34 Banner] Strengthening Banking Resilience A Practical Guide for Bank Julius Baer

eBook 2: Implementing Operational Resilience for Bank Julius Baer
C1 C2 C8 C14
[OR] [BJB] [E2] [C1] OR Planning Methodology [OR] [BJB] [E2] [P1] [S1-S5] [C2] Five Stages of the _Plan_ Phase [OR] [BJB] [E2] [P2] [S1-S5] [C8] Five Stages of the _Implement_ Phase [OR] [BJB] [E2] [P3] [C14] The Five Stages of the _Sustain_ Phase
 

Comments

CTA Banner_OR

CTA Banner_ORA

CTA Banner_BCM

CTA Banner_ITDR

CTA Banner_CM