BCM v2

[BCM] [SAESL] [E3] [CBF] [1] Chapter 6: Inter-dependencies for CBF-1

Written by Dr Goh Moh Heng | Nov 17, 2026, 2:16:37 AM

[BCM] [SAESL] [E3] [CBF] [1] Chapter 6: Inter-dependencies for CBF-1

Introduction

No Sub-Critical Business Function (Sub-CBF) of CBF-1 works alone. Engines arrive from customers, parts come from suppliers, tools come from calibration, power comes from utilities, and approvals come from airworthiness authorities. At Singapore Aero Engine Services Private Limited (SAESL), a failure in any of these can stop an otherwise healthy process. This chapter maps the main dependencies behind each Sub-CBF.

Dependency mapping is part of the business impact analysis (BIA). It separates internal dependencies, which sit within SAESL and can be managed directly, from external dependencies, which sit with other organisations and can be managed only through contracts, relationships and alternatives. External dependencies deserve particular attention because SAESL cannot repair them itself.

Each dependency is given a direction. An upstream dependency is something the Sub-CBF needs before it can work, such as parts, information, approvals or services. A downstream dependency is an output of the Sub-CBF that another function or party needs. A mutual dependency is one in which both parties rely on each other continuously. Knowing the direction shows where a failure will start and where it will spread.

The results support business continuity planning, third-party risk management and operational resilience. The parties named are categories or roles that SAESL might rely on. They are illustrative assumptions, not statements about named contracts, and SAESL should confirm them.

Inter-dependency Table

Table 6: Inter-dependencies for CBF-1 Engine Maintenance, Repair and Overhaul (MRO) Operations

Sub-CBF Code Sub-Critical Business Function Business Unit / Vendor / Supplier / Outsourcing Partner Internal Dependency External Dependency Dependency Direction (Upstream / Downstream / Mutual) Description of the Nature of Dependency
CBF-1.1 Engine Induction and Work Scope Agreement Airline customers No Yes Upstream Customers supply the engine, its removal records and the written scope approval. Without them induction cannot start, and the delay passes to the customer's fleet plans.
CBF-1.1 Engine Induction and Work Scope Agreement Production Planning and Turnaround Control (CBF-1.2) Yes No Downstream The logged engine, agreed scope and work order are what planning uses to slot the engine. An incomplete hand-over causes sequencing errors later.
CBF-1.2 Production Planning and Turnaround Control Production areas (strip, repair, build and test) Yes No Mutual Planning issues priorities and production returns status and constraints. Loss of either flow leaves engines out of sequence and planners unaware of problems.
CBF-1.2 Production Planning and Turnaround Control Airline customers No Yes Upstream Customers set delivery commitments and priorities, and approve scope changes. Planning cannot sequence work correctly without current customer priorities.
CBF-1.3 Engine Disassembly and Module Strip Facilities and Utilities Yes No Upstream Gantry and lifting equipment, power, compressed air and lighting enable stripping. Loss stops work and can create safety risks for staff.
CBF-1.4 Part Inspection and Non-Destructive Testing Calibration laboratories No Yes Upstream Inspection and non-destructive testing instruments need in-date calibration. Without it, results cannot be accepted and inspection stops.
CBF-1.4 Part Inspection and Non-Destructive Testing Human Resources Yes No Upstream Human Resources maintains the qualification and authorisation records of inspection and non-destructive testing staff. Without current authorisations, results cannot be signed or accepted.
CBF-1.5 Component Repair and Special Processes Utility providers (power, gas, water) No Yes Upstream Special process lines need stable power and gases. An interruption can spoil parts in process and stop lines until restart checks are complete.
CBF-1.5 Component Repair and Special Processes Specialist subcontract repair providers No Yes Mutual Approved providers can take overflow or relief work and return repaired parts. SAESL relies on their capacity and approvals, and they rely on SAESL's technical data and payment.
CBF-1.6 Materials and Life-Limited Part Management Material and parts suppliers, including Rolls-Royce Plc No Yes Upstream Suppliers provide parts and exchange life-limited parts with approved paperwork. Late or non-traceable supply stops builds and cannot be bypassed.
CBF-1.6 Materials and Life-Limited Part Management Finance Department Yes No Upstream Finance approves purchases and pays suppliers. Failed payments can lead suppliers to pause deliveries.
CBF-1.7 Engine Build and Module Assembly Materials and Life-Limited Part Management (CBF-1.6) Yes No Upstream Complete, traceable kits are the starting point for every build. A missing part or record holds the build even when tooling and staff are ready.
CBF-1.7 Engine Build and Module Assembly Tooling and calibration control Yes No Upstream Calibrated tools are issued for each build step. An out-of-date tool pauses the step and can force earlier steps to be repeated.
CBF-1.8 Engine Test Cell Operations Facilities and Utilities Yes No Upstream Power, fuel handling, cooling, exhaust and fire protection make the cell safe to run. Cell safety is non-negotiable, so loss of any one stops testing.
CBF-1.9 Final Inspection, Certification and Release to Service Airworthiness authorities, including the Civil Aviation Authority of Singapore (CAAS) No Yes Mutual Approvals and oversight authorise SAESL to certify engines, and the authorities rely on SAESL's records and conduct. Loss of an approval would stop release for the affected customers.
CBF-1.9 Final Inspection, Certification and Release to Service Human Resources Yes No Upstream Human Resources maintains the competence and authorisation records of certifying staff. A missing authorisation prevents signature even when the engine is ready.
CBF-1.10 Engine Preservation and Shipment Logistics and freight providers No Yes Downstream Carriers collect and move engines. A missed collection extends storage, adds preservation checks and delays the customer.
CBF-1.11 Technical Records and Airworthiness Documentation Information and communications technology (ICT) Department Yes No Upstream ICT hosts, backs up and restores the records system. Loss limits access to records and risks data loss that would have to be reconstructed.
CBF-1.12 Customer Status Reporting and Engineering Support Airline customers No Yes Mutual Customers need status and technical answers, and SAESL needs their scope decisions and concession approvals. Silence on either side delays work.

The parties shown are illustrative. SAESL should add its actual vendors, contracts and owners during validation.

Conclusion

The map shows a pattern. Most upstream dependencies on the shop floor are internal and shared: Facilities and Utilities supports both stripping and the test cell, and ICT supports records, planning and release. A single failure in a shared service can therefore reach several Sub-CBFs at once. The external dependencies are fewer but harder to control: customers, parts suppliers, calibration laboratories, utilities, carriers and the airworthiness authorities.

Dependency mapping supports the BIA by showing which Sub-CBFs inherit risk from others, and which inherit it from outside SAESL. It improves recovery planning because a recovery time is only as good as the slowest dependency behind it. For example, a short recovery target for the test cell means little if the supporting utilities cannot be restored in the same time.

Third-party dependencies belong in business continuity plans because the plan must say who to call, what to ask for and what to do if the answer is no. Dependency analysis also supports supplier resilience by showing which suppliers deserve continuity questions or alternative sources, and enterprise risk management by linking operational weak points to named parties. In a major disruption, management can use the map to decide which dependencies to restore or replace first.

As a next step, SAESL should record a contract owner and an emergency contact for every external line, and ask the most critical suppliers and providers how they would keep serving SAESL during their own disruption. The answers feed the recovery strategies in chapter 8.

Continue reading: Chapter 7, Vital Records for CBF-1, identifies the records each Sub-CBF needs, where they are held and who is responsible for protecting them.