---
title: "[BCM] [SAESL] [E3] [CBF] [1] Chapter 4: Impact Over Time of Business Functions for CBF-1"
description: "SAESL impact over time for CBF-1: scored impact from 4 hours to 60 days, with RTO, MTPD and vulnerable periods for 12 engine MRO Sub-CBFs under ISO 22301."
---

.

[![BCMIWhiteLogo.png](https://blog.bcm-institute.org/hs-fs/hubfs/Blog%20Testing/BCMIWhiteLogo.png?width=556&name=BCMIWhiteLogo.png "BCMIWhiteLogo.png")](http://www.bcm-institute.org/)

- [Home](https://www.bcm-institute.org/)
- [About Us](https://www.bcm-institute.org/about-us-3/) 
    - [A President’s Perspective](https://www.bcm-institute.org/about-us/a-presidents-perspective/)
    - [Our History](https://www.bcm-institute.org/about-us/our-history/)
    - [Our Advisory Council](https://www.bcm-institute.org/about-us/our-advisory-council/)
    - [Customers’ Testimonials](https://www.bcm-institute.org/about-us/customers-testimonials/)
    - [Credential Verification](https://www.bcm-institute.org/about-us/credential-verification/)
- [Courses](https://blog.bcm-institute.org/blog/course-fees-for-blended-learning-courses-master-catalog) 
    - [ISO 22301 Business Continuity Management System Audit](https://blog.bcm-institute.org/audit/business-continuity-management-audit-courses)
    - [ISO 22301 Business Continuity Management](https://blog.bcm-institute.org/bcm/business-continuity-management-courses)
    - [Crisis Communication](https://blog.bcm-institute.org/crisis-communication/crisis-communication-courses)
    - [Crisis Management](https://blog.bcm-institute.org/en/crisis-management/courses)
    - [IT Disaster Recovery](https://blog.bcm-institute.org/it-disaster-recovery/courses)
    - [Operational Resilience](https://blog.bcm-institute.org/operational-resilience/courses)
    - [Operational Resilience Audit](https://blog.bcm-institute.org/operational-resilience-audit/courses)
- [Certification](https://blog.bcm-institute.org/certification/types-of-certifications-offered) 
    - [ISO 22301 BCMS Audit Certification](https://blog.bcm-institute.org/certification/business-continuity-management-audit-certification)
    - [ISO22301 Business Continuity Management Certification](https://blog.bcm-institute.org/bcm/business-continuity-management-certification)
    - [Crisis Communication Certification](https://blog.bcm-institute.org/crisis-communication/crisis-communication-certification)
    - [Crisis Management Certification](https://blog.bcm-institute.org/en/crisis-management/crisis-management-certification)
    - [IT Disaster Recovery Planning Certification](https://blog.bcm-institute.org/it-disaster-recovery/it-disaster-recovery-certification)
    - [Operational Resilience Certification](https://blog.bcm-institute.org/operational-resilience/operational-resilience-certification)
    - [Operational Resilience Audit Certification](https://blog.bcm-institute.org/operational-resilience-audit)
- [Seminars](https://blog.bcm-institute.org/meet-the-expert/mte-webinar-mainpage)
- [Store](https://www.bcm-institute.org/store-2/)
- [Contact Us](http://www.bcm-institute.org/about-us/contact-us/)

- <https://www.facebook.com/BCMInstitute/>
- <https://www.linkedin.com/company/business-continuity-management-institute-bcm-institute>

###### Building Resilient Operations: Implementing Business Continuity Management at SAESL

![\[BB\] \[SAESL\] \[1\] Precision Turbine Blade Inspection](https://blog.bcm-institute.org/hs-fs/hubfs/SAESL%20Graphic%20Folder/BB%20SAESL/%5BBB%5D%20%5BSAESL%5D%20%5B1%5D%20Precision%20Turbine%20Blade%20Inspection.png?width=1536&height=1024&name=%5BBB%5D%20%5BSAESL%5D%20%5B1%5D%20Precision%20Turbine%20Blade%20Inspection.png "[BB] [SAESL] [1] Precision Turbine Blade Inspection")

# \[BCM\] \[SAESL\] \[E3\] \[CBF\] \[1\] Chapter 4: Impact Over Time of Business Functions for CBF-1

[![New call-to-action](https://no-cache.hubspot.com/cta/default/3893111/c9d0ea0f-9f66-4232-97e2-6be3fe001e05.png)](https://cta-redirect.hubspot.com/cta/redirect/3893111/c9d0ea0f-9f66-4232-97e2-6be3fe001e05)

Chapter 3 estimated the impact of disrupting each Sub-Critical Business Function (Sub-CBF) of CBF-1 for one fixed period of seven days. Real disruptions do not stop at seven days. This chapter shows how the impact on Singapore Aero Engine Services Private Limited (SAESL) grows as a disruption continues, from four hours to 60 days, and uses that growth to set recovery targets.

[![\[Logo\] \[BCM\] Certification Transparent](https://no-cache.hubspot.com/cta/default/3893111/7789ece9-0b11-4cae-9f32-d34d7eb1688a.png)](https://cta-redirect.hubspot.com/cta/redirect/3893111/7789ece9-0b11-4cae-9f32-d34d7eb1688a)

[Dr Goh Moh Heng](https://blog.bcm-institute.org/bcm-v2/author/dr-goh-moh-heng) Nov 17, 2026

**\[BCM\] \[SAESL\] \[E3\] \[CBF\] \[1\] Chapter 4: Impact Over Time of Business Functions for CBF-1**

## [![New call-to-action](https://no-cache.hubspot.com/cta/default/3893111/c9d0ea0f-9f66-4232-97e2-6be3fe001e05.png)](https://cta-redirect.hubspot.com/cta/redirect/3893111/c9d0ea0f-9f66-4232-97e2-6be3fe001e05)

## Introduction

Chapter 3 estimated the impact of disrupting each Sub-Critical Business Function (Sub-CBF) of CBF-1 for one fixed period of seven days. Real disruptions do not stop at seven days. This chapter shows how the impact on Singapore Aero Engine Services Private Limited (SAESL) grows as a disruption continues, from four hours to 60 days, and uses that growth to set recovery targets.

[![\[BCM\] \[SAESL\] \[E3\] \[BIA\] \[T3\] \[CBF\] \[1\] Engine Maintenance, Repair and Overhaul (MRO) Operations](https://no-cache.hubspot.com/cta/default/3893111/e026c0e6-d46c-4f69-a275-f50e02677791.png)](https://cta-redirect.hubspot.com/cta/redirect/3893111/e026c0e6-d46c-4f69-a275-f50e02677791)Impact rises over time for a simple reason: the consequences add up. A single late engine is a nuisance. Several late engines strain customer relationships. A long stoppage raises questions about approvals, staffing and contracts. Looking at impact over time shows when each process crosses from tolerable to unacceptable, which is the information needed for recovery priorities under clause 8.2.2 of ISO 22301.

Three terms are derived from the table. The **recovery time objective (RTO)** is the target time by which a Sub-CBF is restored, at its minimum level, before impact becomes unacceptable. The **maximum tolerable period of disruption (MTPD)** is the longest disruption SAESL can accept before the viability of CBF-1 is seriously threatened. It is always longer than the RTO. The **vulnerable period** is a time when disruption would do the most harm.

Scores run from 1 (very low), 2 (low), 3 (moderate), 4 (high), to 5 (very high). Scores rise or stay level over time. In this table, the MTPD is set between the first score of 4 and the first score of 5. All scores and targets are illustrative planning assumptions for SAESL to validate. Vulnerable periods are described as conditions, not calendar dates.

## How the Targets Were Set

The same four steps were applied to every Sub-CBF.

1. **Score the impact:** use the impact area from chapter 3 as the lens and score each interval from 1 to 5.
2. **Set the MTPD:** choose a point after impact first reaches High and no later than the point it first reaches Very High.
3. **Set the RTO:** choose a target well inside the MTPD, leaving time to put a recovery strategy to work.
4. **Describe the vulnerable period:** name the conditions in which a disruption would do the most harm.

## Impact Over Time Table

**Table 4: Impact Over Time of Business Functions for CBF-1 Engine Maintenance, Repair and Overhaul (MRO) Operations**

| **Sub-CBF Code** | **Sub-Critical Business Function** | **Highest-Impact Area** | **4 Hours** | **8 Hours** | **1 Day** | **2 Days** | **3 Days** | **5 Days** | **7 Days** | **10 Days** | **14 Days** | **21 Days** | **30 Days** | **60 Days** | **Recovery Time Objective (RTO)** | **Maximum Tolerable Period of Disruption (MTPD)** | **Vulnerable Period** |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| **CBF-1.1** | **Engine Induction and Work Scope Agreement** | **Customer / Stakeholder** | **1** | **1** | **1** | **2** | **2** | **3** | **3** | **4** | **4** | **5** | **5** | **5** | **48 hours** | **14 days** | **Weeks when several engines arrive together or customers hold committed induction slots** |
| **CBF-1.2** | **Production Planning and Turnaround Control** | **Operational** | **2** | **2** | **3** | **3** | **4** | **4** | **5** | **5** | **5** | **5** | **5** | **5** | **8 hours** | **3 days** | **Start of each weekly planning cycle, and when many engines reach the same production stage** |
| **CBF-1.3** | **Engine Disassembly and Module Strip** | **Operational** | **1** | **2** | **2** | **3** | **3** | **4** | **4** | **5** | **5** | **5** | **5** | **5** | **24 hours** | **7 days** | **Peaks when several engines are inducted close together and queue for the strip area** |
| **CBF-1.4** | **Part Inspection and Non-Destructive Testing** | **Regulatory** | **2** | **2** | **3** | **3** | **4** | **4** | **5** | **5** | **5** | **5** | **5** | **5** | **24 hours** | **5 days** | **Weeks before a scheduled regulatory surveillance audit, and when large batches of parts await inspection** |
| **CBF-1.5** | **Component Repair and Special Processes** | **Operational** | **1** | **1** | **2** | **2** | **3** | **3** | **4** | **4** | **5** | **5** | **5** | **5** | **72 hours** | **10 days** | **Peaks in blade and vane repair demand, and windows when special process lines are due for maintenance** |
| **CBF-1.6** | **Materials and Life-Limited Part Management** | **Third-Party Dependency** | **2** | **2** | **3** | **3** | **3** | **4** | **4** | **5** | **5** | **5** | **5** | **5** | **24 hours** | **7 days** | **Periods of heavy build activity, and when exchange life-limited parts are needed for several engines at once** |
| **CBF-1.7** | **Engine Build and Module Assembly** | **Financial** | **1** | **2** | **3** | **3** | **4** | **4** | **5** | **5** | **5** | **5** | **5** | **5** | **24 hours** | **5 days** | **Weeks when several engines are due to complete build against fixed customer delivery dates** |
| **CBF-1.8** | **Engine Test Cell Operations** | **Financial** | **2** | **3** | **3** | **4** | **5** | **5** | **5** | **5** | **5** | **5** | **5** | **5** | **24 hours** | **3 days** | **When many engines are ready for test together, and around planned test cell maintenance or calibration windows** |
| **CBF-1.9** | **Final Inspection, Certification and Release to Service** | **Regulatory** | **2** | **3** | **3** | **4** | **4** | **5** | **5** | **5** | **5** | **5** | **5** | **5** | **12 hours** | **3 days** | **Month-end and quarter-end, when delivery milestones and billing cycles coincide, and before surveillance audits** |
| **CBF-1.10** | **Engine Preservation and Shipment** | **Customer / Stakeholder** | **1** | **1** | **1** | **1** | **2** | **2** | **3** | **3** | **4** | **5** | **5** | **5** | **48 hours** | **14 days** | **Periods when several engines are ready to ship together and carrier capacity is tight** |
| **CBF-1.11** | **Technical Records and Airworthiness Documentation** | **Information** | **2** | **2** | **3** | **3** | **3** | **4** | **4** | **5** | **5** | **5** | **5** | **5** | **8 hours** | **7 days** | **Planned system upgrade or migration windows, and the weeks before an audit or approval renewal** |
| **CBF-1.12** | **Customer Status Reporting and Engineering Support** | **Reputation** | **1** | **1** | **2** | **2** | **2** | **3** | **3** | **3** | **4** | **4** | **5** | **5** | **24 hours** | **14 days** | **Around customer-requested scope changes, and at induction and release when customers expect most updates** |

Scores: 1 = very low, 2 = low, 3 = moderate, 4 = high, 5 = very high. All scores, RTOs and MTPDs are illustrative. Dates for vulnerable periods are to be confirmed by SAESL. The RTO and MTPD for each Sub-CBF are reused unchanged in chapters 5, 8 and 9.

## [![New call-to-action](https://no-cache.hubspot.com/cta/default/3893111/b5945536-415f-4c64-9e05-c7b4d4f26c76.png)](https://cta-redirect.hubspot.com/cta/redirect/3893111/b5945536-415f-4c64-9e05-c7b4d4f26c76)

## Conclusion

The table shows three groups of Sub-CBFs. Planning (CBF-1.2), test cell operations (CBF-1.8) and release to service (CBF-1.9) have the shortest MTPD, at three days. Inspection (CBF-1.4) and build (CBF-1.7) follow at five days. Induction (CBF-1.1), shipment (CBF-1.10) and customer status reporting (CBF-1.12) tolerate 14 days, because physical work and certification continue while they are down. RTOs range from 8 hours for planning and records to 72 hours for component repair. Later chapters reuse these figures, so any change agreed during validation must be carried through to chapters 5, 8 and 9.

Impact-over-time analysis supports the business impact analysis (BIA) by turning opinions into comparable evidence. It helps set recovery priorities: the Sub-CBFs with the shortest MTPD are restored first, and those with the longest can wait. It also guides recovery strategy development. A process with an RTO of 8 hours needs a ready alternative, such as a manual method. A process with an RTO of 72 hours can rely on a slower solution, such as subcontract repair.

Vulnerable periods influence contingency planning and resource allocation. SAESL may hold extra staff, spare parts or a standby arrangement during the periods when disruption would do most harm, such as before an audit or when many engines reach test together. This analysis contributes to resilience by ensuring the effort follows the risk and giving the board a clear basis for accepting or reducing exposure. SAESL should validate each score with the process owner, and check that each RTO is achievable with the resources available, before it becomes a commitment.

**Continue reading:** Chapter 5, *Supporting IT Systems and Applications for CBF-1*, identifies the systems and equipment each Sub-CBF depends on and sets recovery point objectives and system recovery targets that support these RTOs.

---

## **Comments**

![CTA Banner\_OR](https://blog.bcm-institute.org/hubfs/CTA%20Banner%20for%20Blog/CTA%20Banner_OR.jpg "CTA Banner_OR")

---

![CTA Banner\_ORA](https://blog.bcm-institute.org/hubfs/CTA%20Banner%20for%20Blog/CTA%20Banner_ORA.jpg "CTA Banner_ORA")

---

![CTA Banner\_BCM](https://blog.bcm-institute.org/hubfs/CTA%20Banner%20for%20Blog/CTA%20Banner_BCM.jpg "CTA Banner_BCM")

---

![CTA Banner\_ITDR](https://blog.bcm-institute.org/hubfs/CTA%20Banner%20for%20Blog/CTA%20Banner_ITDR.jpg "CTA Banner_ITDR")

---

![CTA Banner\_CM](https://blog.bcm-institute.org/hubfs/CTA%20Banner%20for%20Blog/CTA%20Banner_CM.jpg "CTA Banner_CM")

![BCMIWhiteLogoSmall.png](https://blog.bcm-institute.org/hs-fs/hubfs/Blog%20Testing/BCMIWhiteLogoSmall.png?width=72&name=BCMIWhiteLogoSmall.png "BCMIWhiteLogoSmall.png")

All rights reserved. Copyright 2026

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Dr Goh Moh Heng",
    "url" : "https://blog.bcm-institute.org/bcm-v2/author/dr-goh-moh-heng"
  },
  "dateModified" : "2026-11-17T02:11:36.403Z",
  "datePublished" : "2026-11-17T02:11:36.000Z",
  "headline" : "[BCM] [SAESL] [E3] [CBF] [1] Chapter 4: Impact Over Time of Business Functions for CBF-1",
  "mainEntityOfPage" : {
    "@id" : "https://blog.bcm-institute.org/bcm-v2/bcm-saesl-e3-cbf-1-chapter-4-impact-over-time-of-business-functions-for-cbf-1",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://blog.bcm-institute.org/hubfs/BCMI%20Logo.png"
    },
    "name" : "BCMI Pte Ltd"
  }
}
```