---
title: "[BCM] [SAESL] [E3] [CBF] [1] Chapter 5: Supporting IT Systems and Applications for CBF-1"
description: SAESL IT systems, RPOs, system RTOs and special equipment behind 12 engine MRO Sub-CBFs in CBF-1, set to support business RTOs 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\] \[13\] SAESL Engine Overhaul Briefing-1](https://blog.bcm-institute.org/hs-fs/hubfs/SAESL%20Graphic%20Folder/BB%20SAESL/%5BBB%5D%20%5BSAESL%5D%20%5B13%5D%20SAESL%20Engine%20Overhaul%20Briefing-1.png?width=1536&height=1024&name=%5BBB%5D%20%5BSAESL%5D%20%5B13%5D%20SAESL%20Engine%20Overhaul%20Briefing-1.png "[BB] [SAESL] [13] SAESL Engine Overhaul Briefing-1")

# \[BCM\] \[SAESL\] \[E3\] \[CBF\] \[1\] Chapter 5: Supporting IT Systems and Applications 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)

Almost every Sub-Critical Business Function (Sub-CBF) of CBF-1 relies on information systems. Engines are tracked by work order, parts are traced by barcode, test data is captured by instruments and certificates are signed electronically. At Singapore Aero Engine Services Private Limited (SAESL), a business process cannot be restored on time if the underlying technology is not restored first. This chapter identifies those technology dependencies and sets recovery targets for them.

[![\[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 5: Supporting IT Systems and Applications 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

Almost every Sub-Critical Business Function (Sub-CBF) of CBF-1 relies on information systems. Engines are tracked by work order, parts are traced by barcode, test data is captured by instruments and certificates are signed electronically. At Singapore Aero Engine Services Private Limited (SAESL), a business process cannot be restored on time if the underlying technology is not restored first. This chapter identifies those technology dependencies and sets recovery targets.

[![\[BCM\] \[SAESL\] \[E3\] \[BIA\] \[T4\] \[CBF\] \[1\] Engine Maintenance, Repair and Overhaul (MRO) Operations](https://no-cache.hubspot.com/cta/default/3893111/b29cf834-b1d5-46ed-886c-49d0ef61f532.png)](https://cta-redirect.hubspot.com/cta/redirect/3893111/b29cf834-b1d5-46ed-886c-49d0ef61f532)Business continuity planning (BCP) and IT disaster recovery (ITDR) work together. BCP decides how quickly each process must return and at what level. ITDR decides how the supporting systems will be rebuilt in time to meet that need. The business impact analysis (BIA) links the two, because the business recovery time objectives (RTOs) set in chapter 4 become the ceiling for system recovery.

Two targets are set for each Sub-CBF. The **recovery point objective (RPO)** is the acceptable amount of data loss, measured as the time between the last good copy of the data and the disruption. The **system recovery time objective (system RTO)** is the target time to restore the supporting system. A system RTO must be equal to or shorter than the business RTO, because the process needs time to catch up after the system returns.

Specialised equipment is included because a restored database is of little use without the scanners, instruments, tokens or terminals that feed it. The systems named below are categories. SAESL might rely on them, but none is claimed as a fact about SAESL. All targets are illustrative and for SAESL to validate.

## Supporting Systems Table

**Table 5: Supporting IT Systems and Applications for CBF-1 Engine Maintenance, Repair and Overhaul (MRO) Operations**

| **Sub-CBF Code** | **Sub-Critical Business Function** | **Supporting IT Systems and Applications** | **Recovery Point Objective (RPO)** | **System Recovery Time Objective (System RTO)** | **Supporting Special Equipment / Resources** | **Remarks** |
| --- | --- | --- | --- | --- | --- | --- |
| **CBF-1.1** | **Engine Induction and Work Scope Agreement** | **Enterprise resource planning (ERP) work order module; email and collaboration platform for customer correspondence** | **1 hour** | **24 hours** | **Secure network connectivity; barcode scanners for engine and record intake** | **Paper induction forms bridge an outage; work orders are entered after recovery. Business RTO is 48 hours.** |
| **CBF-1.2** | **Production Planning and Turnaround Control** | **Shop-floor production control and scheduling system; ERP; reporting and analytics platform** | **1 hour** | **4 hours** | **High Availability infrastructure; shop-floor terminals; printed priority lists** | **Most dependent on live data. An offline copy of the schedule, refreshed each shift, supports a manual fallback. Business RTO is 8 hours.** |
| **CBF-1.3** | **Engine Disassembly and Module Strip** | **Shop-floor production control; part tagging and traceability system** | **1 hour** | **12 hours** | **Barcode scanners; shop-floor terminals; label printers** | **Controlled tag books let stripping continue; tags are entered after recovery. Business RTO is 24 hours.** |
| **CBF-1.4** | **Part Inspection and Non-Destructive Testing** | **Quality management and non-conformance reporting system; inspection data capture; NDT instrument software** | **1 hour** | **12 hours** | **NDT instruments; calibrated measuring equipment; controlled workstations** | **Results must be recorded at the time of inspection, so numbered paper forms are the fallback. Business RTO is 24 hours.** |
| **CBF-1.5** | **Component Repair and Special Processes** | **Process control and repair record systems for special processes; ERP** | **4 hours** | **48 hours** | **Process line controllers; furnace and chemical line monitoring; calibration records** | **Process lines may run under local controls if records are kept by hand and verified. Business RTO is 72 hours.** |
| **CBF-1.6** | **Materials and Life-Limited Part Management** | **ERP inventory and materials management; life-limited part (LLP) life-tracking and traceability database; supplier portals** | **Less than 15 minutes** | **8 hours** | **Barcode or radio-frequency identification (RFID) scanners; secure supplier connectivity; backup media** | **LLP life data is the most sensitive item here, so a replicated off-site copy is advised. Business RTO is 24 hours.** |
| **CBF-1.7** | **Engine Build and Module Assembly** | **Shop-floor production control; build record and torque-data capture; tool control and calibration system** | **Less than 15 minutes** | **12 hours** | **Digital torque tools and data loggers; calibrated tool store scanner; shop-floor tablets** | **Build records are signed at the time of the work; paper job cards cover a short outage. Business RTO is 24 hours.** |
| **CBF-1.8** | **Engine Test Cell Operations** | **Test cell data acquisition and control system; test data archive; engineering analysis software** | **Real-time** | **12 hours** | **Test cell instrumentation; redundant data loggers; uninterruptible power supply (UPS) units; secure network for data transfer** | **Run data is replicated to a second store. If acquisition fails mid-run, the run is repeated. Business RTO is 24 hours.** |
| **CBF-1.9** | **Final Inspection, Certification and Release to Service** | **Technical records and certification system; electronic signature and authorisation management; identity and access management (IAM)** | **Less than 15 minutes** | **6 hours** | **Digital signature infrastructure; authentication tokens; secure printing for certificates** | **Authorised signatories need working credentials, so an offline list of authorisations is kept. Business RTO is 12 hours.** |
| **CBF-1.10** | **Engine Preservation and Shipment** | **ERP shipping module; logistics booking portals; email** | **4 hours** | **24 hours** | **Label printers; secure internet connectivity; mobile devices** | **Paper shipping documents and email bookings are workable fallbacks. Business RTO is 48 hours.** |
| **CBF-1.11** | **Technical Records and Airworthiness Documentation** | **Technical records system; document management; database management systems; backup and archive** | **Less than 15 minutes** | **4 hours** | **High Availability storage; disaster recovery site; high-speed scanners; backup media; numbered paper job cards** | **The most critical data asset in CBF-1. Paper fallback plus a tested restore protect it. Business RTO is 8 hours.** |
| **CBF-1.12** | **Customer Status Reporting and Engineering Support** | **Customer web portal; ERP status feeds; email and collaboration platforms; engineering document management** | **4 hours** | **12 hours** | **Secure portal hosting; video conferencing systems; mobile devices** | **Email summaries bridge a portal outage and are reconciled afterwards. Business RTO is 24 hours.** |

Every system RTO is equal to or shorter than the business RTO from chapter 4. All figures are illustrative.

## [![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

Supporting systems enable CBF-1 at every step, from the work order opened at induction to the certificate signed at release. Identifying them during the BIA prevents a common failure: a business plan that assumes a system will be back in a day when the ITDR plan says three.

The RPO and system RTO give ITDR planners their targets. The shortest data-loss tolerances apply to test data, LLP life records, and the technical records system, which are hard or impossible to recreate. The shortest system RTOs sit with records (4 hours), planning (4 hours) and release (6 hours), which also have the shortest business RTOs.

In practice, the RPO decides how often data is copied and where the copy is kept. The system RTO determines whether a system can be rebuilt from backup, failed over to a standby, or bridged manually. A tight RPO and a short system RTO cost more, so they should be reserved for the Sub-CBFs where the BIA shows the greatest harm. SAESL should confirm each target with its information and communications technology (ICT) lead and test it in an exercise before relying on it.

Specialised equipment belongs in business continuity plans because it is often overlooked in IT planning. Torque tools, test cell loggers, authentication tokens and scanners must be listed, stocked or replaceable, or the restored systems cannot be used. Understanding technology dependencies strengthens resilience by showing where a manual method is a sound fallback and where it is not.

**Continue reading:** Chapter 6, *Inter-dependencies for CBF-1*, maps the internal and external parties that each Sub-CBF relies on, and the direction of each dependency.

---

## **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:13:56.985Z",
  "datePublished" : "2026-11-17T02:13:56.000Z",
  "headline" : "[BCM] [SAESL] [E3] [CBF] [1] Chapter 5: Supporting IT Systems and Applications for CBF-1",
  "mainEntityOfPage" : {
    "@id" : "https://blog.bcm-institute.org/bcm-v2/bcm-saesl-e3-cbf-1-chapter-5-supporting-it-systems-and-applications-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"
  }
}
```