[OR] [P2] [S2] [MII] [C6] Step 3 – Develop Mapping Framework

[P2] [S2] Chapter 6

Step 3 – Develop Mapping Framework

Introduction

With the scope defined and data sources identified, the next step is to develop a structured mapping framework. This framework provides the blueprint for how interconnections and interdependencies will be organised, visualised, and analysed.

Without a clear framework, mapping efforts risk becoming:

• Inconsistent across business units
• Difficult to interpret and analyse
• Misaligned with operational resilience objectives

A well-designed framework ensures that mapping is:

• Structured and scalable
• Consistent across the organisation
• Aligned to Critical Business Services (CBS)
• Usable for downstream activities such as scenario testing and recovery planning

Purpose of the Chapter

The purpose of this chapter is to:

• Define the structure of interconnection mapping
• Establish how CBS are broken down into manageable components
• Introduce key elements such as data flows, system interfaces, and relationships
• Provide a framework for capturing dependencies and connectivity

Defining the Mapping Structure

Hierarchical Structure

At the core of the mapping framework is a hierarchical structure that organises service delivery into logical layers:

CBS → Sub-CBS → Processes → Resources

Critical Business Services (CBS)

• Represents the end-to-end service delivered to customers or stakeholders
• Serves as the anchor point for all mapping activities

Example:

• Payments & Funds Transfer Services

Sub-CBS

• Breaks down CBS into distinct service components or functional segments
• Enables more granular analysis

Example:

• Payment Initiation
• Authentication & Authorisation
• Clearing & Settlement

Processes

• Defines the activities required to deliver each Sub-CBS
• Includes workflows, decision points, and execution steps

Example:

• Transaction validation
• Fraud screening
• Funds availability check

Resources

• Represents the assets required to execute processes, including:
• People
• Technology
• Data
• Facilities
• Third parties

Benefits of the Hierarchical Structure

• Provides clarity and organisation
• Enables traceability from CBS to underlying components
• Supports structured analysis of dependencies

Including Key Mapping Elements

Beyond the hierarchical structure, the framework must capture how components interact and depend on each other.

Data Flows

Definition

Data flows represent:

• Movement of data between systems, processes, and entities

Importance

• Identifies critical data dependencies
• Highlights data integrity and availability risks

Examples

• Customer data flowing from front-end applications to backend systems
• Transaction data transmitted to payment networks

System Interfaces

Definition

System interfaces describe:

• Points of interaction between applications and systems

Importance

• Identifies integration dependencies
• Highlights potential points of failure

Examples

• API connections between mobile banking and core systems
• Integration between payment engines and external networks

Upstream and Downstream Relationships

Definition

• Upstream: Components that provide inputs to a process
• Downstream: Components that depend on the outputs of a process

Importance

• Enables understanding of dependency chains
• Identifies cascading impact pathways

Examples

• Upstream: Authentication system
• Downstream: Payment processing system

Framework Components

The mapping framework must incorporate key components that enable comprehensive analysis.

Dependency Layers

Definition

Dependency layers categorise components into distinct groups, such as:

• People
• Processes
• Technology
• Data
• Facilities
• Third parties

Purpose

• Provides structured classification of dependencies
• Enables consistent mapping across CBS

Connectivity Flows

Definition

Connectivity flows describe:

• How components interact and exchange information

Types of Flows

• Process flows
• Data flows
• System interactions

Purpose

• Visualises relationships between components
• Identifies paths through which disruptions may propagate

Interaction Points

Definition

Interaction points are:

• Specific locations where components connect or interact

Examples

• API endpoints
• System integration points
• Manual handoffs between teams

Purpose

• Highlights critical points of dependency
• Identifies potential failure points

Building the Framework

Step-by-Step Approach

Organisations should:

• Define CBS and Sub-CBS structure

• Map processes supporting each Sub-CBS

• Identify resources required for each process

• Capture data flows and system interfaces

• Map upstream and downstream relationships

• Categorise dependencies into layers

Ensuring Consistency

To ensure consistency:

• Use standard templates and definitions
• Align with organisational taxonomy
• Apply the same framework across all CBS

Validation

The framework should be validated through:

• Stakeholder workshops
• Cross-functional reviews
• Alignment with actual operations

Practical Illustration

A simplified framework example:

CBS: Payments & Funds Transfer

→ Sub-CBS: Payment Processing

→ Process: Transaction validation

→ Resources:

• Technology: Payment engine
• Data: Transaction database
• People: Operations team
• Third party: Payment network

Connectivity:

• Data flow between systems
• API integration with external network
• Upstream authentication system

Developing a structured mapping framework is a critical step in operational resilience implementation, providing the foundation for consistent and effective interconnection mapping.

By defining:

• A clear hierarchical structure (CBS → Sub-CBS → Processes → Resources)
• Key elements such as data flows, system interfaces, and relationships
• Core components including dependency layers, connectivity flows, and interaction points

Organisations can create a framework that is:

• Comprehensive
• Scalable
• Aligned with operational realities

This framework enables organisations to move beyond fragmented mapping efforts and develop a coherent, end-to-end view of service delivery, supporting deeper analysis and resilience planning.

In the next chapter, we will explore Step 4: Map Processes and Resources, where this framework is applied to capture detailed operational dependencies across CBS.

C1	C2	C3	C4	C5	C6
C7	C8	C9	C10	C11	C12
C13	C14	C15	C16	C17	C18
C19	C20	C21	C22

 

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.

	If you have any questions, click to contact us.