---
title: "[BCM] [SAESL] [E3] [CBF] [1] Chapter 10: Business Continuity Recovery Procedure for CBF-1"
description: "SAESL recovery procedure for CBF-1 engine MRO: preparedness, the first 24 hours and restoration, with roles and times, aligned with ISO 22301 and ISO 22361."
---

[BCM v2](https://blog.bcm-institute.org/bcm-v2)

# [\[BCM\] \[SAESL\] \[E3\] \[CBF\] \[1\] Chapter 10: Business Continuity Recovery Procedure for CBF-1](https://blog.bcm-institute.org/bcm-v2/bcm-saesl-e3-cbf-1-chapter-10-business-continuity-recovery-procedure-for-cbf-1)

 Written by [Dr Goh Moh Heng](https://blog.bcm-institute.org/bcm-v2/author/dr-goh-moh-heng) | Nov 17, 2026, 3:43:02 AM

**\[BCM\] \[SAESL\] \[E3\] \[CBF\] \[1\] Chapter 10: Business Continuity Recovery Procedure for CBF-1**

## Introduction

Strategies and resources do not recover an organisation on their own. People do, by following a clear procedure under pressure. This chapter turns the work of chapters 1 to 9 into a Business Continuity Recovery Procedure for CBF-1, Engine Maintenance, Repair and Overhaul (MRO) Operations, at Singapore Aero Engine Services Private Limited (SAESL). It is written so that a recovery team leader could pick it up in the middle of an incident and know what to do next.

The procedure forms part of SAESL's business continuity plan (BCP). The plan sets out who has authority and how the organisation responds as a whole. This procedure covers one critical business function in detail: the actions, the order, the owners and the decisions. It follows guidance in ISO 22301 and ISO 22313 for continuity, ISO 22361 for crisis management, and Singapore business continuity good practice, always keeping in mind the airworthiness approvals that SAESL holds.

The procedure has four linked phases. **Preparedness** is the work done before anything goes wrong. **Response** is the first reaction to a disruption: making people safe and understanding what has happened. **Recovery** restores Sub-Critical Business Functions (Sub-CBFs) to their minimum level within their recovery time objectives (RTOs). **Restoration** is the return to normal operations and the learning that follows. Parts 2 to 4 follow these phases.

Recovery activities must be assigned before a disruption, not during it. Every step below therefore names a role, not a person. SAESL should fill each role with a named person and a deputy. All times are indicative planning assumptions, measured from the moment of disruption (T+0), and SAESL should validate them.

**Guidance Notes for Implementing Critical Business Function: Chapter 10: Business Continuity Recovery Procedure for CBF-1 Engine Maintenance, Repair and Overhaul (MRO) Operations**

## Part 1: Purpose and Importance of CBF-1 Engine Maintenance, Repair and Overhaul (MRO) Operations

CBF-1 covers the work that turns a used Rolls-Royce Trent engine into a certified, serviceable one: induction, planning, strip, inspection, component repair, materials, build, test, release, shipment, records and customer support. Chapter 1 divides it into 12 Sub-CBFs, CBF-1.1 to CBF-1.12.

Its business purpose is to return engines to customers on time, in a condition they can trust, under SAESL's airworthiness approvals. It is critical for three reasons. Customers judge SAESL on turnaround time. Every engine leaves under approvals from 13 airworthiness bodies, including the Civil Aviation Authority of Singapore (CAAS). And the work is safety-critical.

The major outcomes are certified engines, complete record packs, repaired components and informed customers. The main stakeholders are airline customers, the joint-venture partners Rolls-Royce Plc and SIA Engineering Company, SAESL staff, suppliers and the approving authorities. Regulatory obligations include maintaining approvals, certification standards and the quality, safety and environmental management certificates that SAESL lists. Specific notification duties should be confirmed by Quality Assurance and marked \[verify\].

SAESL states that it can repair and overhaul over 300 Trent engines a year. At any moment, many engines sit at different stages of one flow, so even a short interruption leaves several engines at risk at once. That makes the order of recovery as important as its speed, and it is why the procedure restores Sub-CBFs by RTO rather than by department.

## Part 2: Pre-Crisis Preparedness for CBF-1 (Reduce Phase)

### Objective

Preparedness reduces the chance of a disruption and the time it takes to recover if it does occur. The aim is that, on the day of a disruption, roles are filled, resources are in place, systems are recoverable, and people have practised.

### How

### Governance and recovery team responsibilities

The board or its delegate approves the procedure, the minimum business continuity objectives from chapter 2 and the RTOs from chapter 4. The business continuity management (BCM) coordinator keeps the plan current. A CBF-1 recovery team leader commands the recovery, supported by a process owner for each Sub-CBF. Quality Assurance holds authority over any matter touching certification, and no one else may waive it. The main roles are:

- **Crisis Management Team:** sets direction and approves major decisions such as alternative sites, subcontracting and external statements.
- **CBF-1 recovery team leader:** commands the recovery of CBF-1 and allocates resources.
- **Sub-CBF process owners:** run their own recovery steps and report every four hours (indicative).
- **Quality Assurance:** decides all certification matters and oversees record integrity.
- **Information and communications technology (ICT) lead:** recovers systems and records and keeps remote access working.
- **Communications lead:** issues approved messages to staff, customers and authorities.

### Succession, training and awareness

Each role needs a named deputy who can act at any hour. Staff should know the procedure in outline and their own tasks in detail. Cross-training is the most valuable preparedness measure in CBF-1: at least two planners (CBF-1.2), two authorised signatories for each engine type (CBF-1.9) and cross-trained technicians in strip and build (CBF-1.3, CBF-1.7).

### Resource and workplace readiness

Recovery resources from chapter 9 should be identified, stocked and checked. These include spare calibrated instruments for inspection (CBF-1.4), redundant data loggers and sensors for the test cell (CBF-1.8), buffer stock for materials (CBF-1.6), paper job cards and induction packs, and authentication tokens. Alternate shop-floor areas should be surveyed, approved for use and kept clear of permanent obstruction.

### ICT and disaster recovery readiness

ICT should keep replication to the recovery site working, test the switch-over, and keep offline copies of the schedule and the list of authorisations. The system RTOs in chapter 5 are the targets. Remote access for planners, signatories and engineers should be tested before it is needed.

### Supplier and dependency readiness

Dependencies from chapter 6 should be verified at least once a year (indicative): contacts, contract terms and alternatives for parts suppliers, calibration laboratories, utility providers, logistics providers, subcontract repair providers and test facility partners. Arrangements that depend on approval or customer consent should be agreed in advance, since they cannot be agreed at T+4.

### Communication, contacts and records

An emergency contact list should cover staff, customers of priority engines, suppliers, authorities and the media contact, with at least two ways to reach each. Message templates for customers and staff save time. Vital records from chapter 7 should be copied, tested and listed in a register, with custodians named. Document management rules should require controlled copies of this procedure on paper and in a second location.

### Preventive controls, testing and readiness checks

Preventive controls reduce the likelihood of disruption: preventive maintenance of the test cell and gantry equipment, calibration schedules, utility resilience, fire protection and cyber security. Testing proves the arrangements. SAESL should run a desktop exercise for each Sub-CBF at least once a year (indicative), a technical test of record and system recovery, and a full exercise of the procedure on a regular cycle. Findings feed improvement, as ISO 22301 clause 8.5 and clause 10 expect.

A short readiness checklist should be reviewed each quarter (indicative).

- Are all recovery roles filled and deputies named?
- Are contact lists tested and current?
- Are spare instruments, tokens, job cards and buffer stock in place?
- Has the last record and system restore test passed?
- Are supplier and approval arrangements current?
- Have open actions from the last exercise been closed?

## Part 3: Within T+24 Hours for CBF-1 (Response, Recovery and Resume Phase)

### Objective

The first 24 hours decide whether a disruption becomes a short interruption or a lasting loss. The aim is to protect people, understand the damage, restore the Sub-CBFs with the shortest RTOs and keep customers and authorities informed, without lowering any certification standard.

### How

The steps below are in chronological order. Times are measured from T+0.

1. **T+0 to T+1 hour: notify.** Whoever discovers the disruption informs the duty manager, who records the time, the location, and what is known, then alerts the CBF-1 recovery team leader and the BCM coordinator.
2. **T+1 hour: activate.** The recovery team leader judges the scale against agreed criteria and, if needed, activates the BCP and convenes the Crisis Management Team. Record activation, including the time and the person who gave it.
3. **T+1 to T+2 hours: safety assessment.** People come first. Evacuate or shelter as needed, account for all staff and visitors, and make the area safe, particularly around the test cell, lifting equipment and process lines. No recovery work starts in an unsafe area.
4. **T+2 to T+4 hours: damage assessment.** Teams assess people, premises, equipment, systems and records. They list every engine in work, its stage, and its location, and quarantine any engine, part, or record that may have been affected so traceability is not lost. Quality Assurance advises on anything that may affect certification.
5. **T+2 to T+4 hours: resource mobilisation.** The recovery team leader activates the Sub-CBF recovery teams and releases the resources set out in chapter 9, in the priority order below.
6. **By T+4 hours: communicate.** One voice speaks for SAESL. Staff are told what to do and where to go. Customers of priority engines are told that an incident has occurred and when to expect the next update. Suppliers and logistics providers are alerted. Approving authorities are notified where SAESL's approvals require it, as confirmed by Quality Assurance.
7. **By T+8 hours: restore planning and records (CBF-1.2 and CBF-1.11).** Planners work from the offline schedule and issue a priority list. ICT switches the records system to the recovery site and the shop moves to numbered paper job cards while it does so.
8. **By T+12 hours: restore release (CBF-1.9).** Authorised signatories confirm their availability, use the offline list of authorisations and review records through secure remote access. No engine is released on incomplete records.
9. **By T+24 hours: restore the 24-hour group (CBF-1.3, 1.4, 1.6, 1.7, 1.8 and 1.12).** Strip and build move to alternate areas if needed. Inspection uses spare calibrated instruments. Materials draw on buffer stock. The test cell restores data capture with spares, and the Crisis Management Team decides whether to use an alternative test facility. Customer support moves to templated email and telephone.
10. **Throughout: prioritise.** Priority engines come first: engines in test or final inspection, and those with customer-critical commitments. Non-priority work pauses, as the objectives in chapter 2 allow.
11. **Throughout: coordinate suppliers.** Process owners contact the dependencies listed in chapter 6, request expedited supply or relief, and log the answers.
12. **Throughout: report and escalate.** Process owners report progress to the recovery team leader every four hours (indicative). Any Sub-CBF that has used three-quarters of its RTO (indicative) without recovery is escalated to the Crisis Management Team.
13. **Throughout: decide and record.** The Crisis Management Team decides on alternative sites, subcontract repair, customer notices and external communications. Quality Assurance alone decides anything that touches certification. Every decision, action and time is written in a log.

### Rules for manual workarounds

Manual methods are used only where Chapter 8 allows them, and always under four rules.

- **Controlled forms:** use numbered paper forms issued from a log, never loose paper.
- **Contemporaneous entries:** record each step at the time of the work, signed and dated.
- **Second-person check:** keep it for every safety-critical step.
- **Reconcile before release:** no engine is released until manual entries have been entered into the system and verified.

**Table 10: Business Continuity Recovery Procedure for CBF-1 Engine Maintenance, Repair and Overhaul (MRO) Operations**

| **Time Window (Indicative)** | **Sub-CBFs Restored to Minimum Level** | **Key Actions** |
| --- | --- | --- |
| **T+0 to T+4 hours** | **None yet; response only** | **Notify, activate, make safe, assess damage, mobilise, communicate** |
| **By T+8 hours** | **CBF-1.2 Production Planning; CBF-1.11 Technical Records** | **Offline schedule and priority list; switch to recovery site; paper job cards** |
| **By T+12 hours** | **CBF-1.9 Final Inspection and Release** | **Confirm signatories; offline authorisations; remote record review** |
| **By T+24 hours** | **CBF-1.3, 1.4, 1.6, 1.7, 1.8, 1.12** | **Alternate areas; spare instruments; buffer stock; test cell spares or alternative facility; templated status emails** |
| **By T+48 hours** | **CBF-1.1 Induction; CBF-1.10 Shipment** | **Paper induction pack; preserved storage; alternative carriers** |
| **By T+72 hours** | **CBF-1.5 Component Repair** | **Subcontract to approved providers with customer consent** |

The table is illustrative. Times follow the RTOs fixed in chapter 4.

## Part 4: After T+24 Hours for CBF-1 (Restore and Return Phase)

### Objective

Restoration returns CBF-1 to normal operation, closes the gaps that emergency methods left, and captures what the incident taught. It is as important as the first 24 hours, because errors made in haste appear later as record gaps and quality escapes.

### How

The activities below are in logical sequence.

1. **Complete recovery of the remaining Sub-CBFs.** Induction and shipment follow by T+48 hours, and component repair by T+72 hours, using the strategies in chapter 8.
2. **Restore ICT services and records.** ICT returns systems to the primary environment in a planned way. Recover or replace damaged originals, and bring the archive back to a controlled state.
3. **Reconcile manual work.** Paper job cards, tag books and handwritten logs are entered into the system and checked by a second person. Nothing is destroyed until it has been verified.
4. **Validate data integrity.** Restored data is compared with replicated copies and paper originals. Life-limited part life status and test data receive particular attention.
5. **Return to the primary workplace.** Teams leave alternate areas only when the primary area is safe, inspected and approved. Equipment, tools and instruments are checked for calibration before use.
6. **Reinstate normal staffing.** Surge arrangements stand down in stages. Manage fatigue, and staff who worked extended hours receive rest.
7. **Normalise suppliers and reconcile finances.** Emergency arrangements are closed or converted. Record and reconcile extra costs, penalties, and claims, and start any insurance claim.
8. **Communicate and report.** Customers receive revised delivery dates and a final account of the incident. Regulatory reports are made where required, as confirmed by Quality Assurance.
9. **Monitor performance.** Turnaround time, quality and record completeness are tracked against pre-incident levels until the Crisis Management Team confirms a return to normal.
10. **Review and learn.** A post-incident review is held within two weeks (indicative). It examines what happened, what worked and what did not, and records lessons learned.
11. **Act and improve.** Corrective actions have owners and dates. The BCP and this procedure are updated, training is improved, and exercises are adjusted. This supports the continual improvement required by ISO 22301 clause 10.

Restoration is complete only when the exit criteria are met. Suggested criteria (indicative) are that all Sub-CBFs meet normal service levels, all manual records are reconciled, no quarantine remains unexplained, customers have received revised dates, and the post-incident review is booked. The Crisis Management Team signs off the stand-down in writing.

## Conclusion

The recovery procedure turns the analysis of the earlier chapters into action. It supports the business continuity plan by giving each Sub-CBF an owner, a sequence and a time. Without it, SAESL would have good strategies and no way to activate them.

Preparation before a disruption matters most. Cross-trained people, working spares, tested backups and agreed arrangements with partners decide how fast recovery can go. Disciplined execution during recovery comes next: following the sequence, keeping a log, escalating early, and never trading away a certification standard for speed. Continual improvement after restoration closes the loop, because every incident and exercise shows how the next response can be better.

The first step for SAESL is practical: name a person and a deputy for every role in this procedure, confirm the time targets with the process owners, and run a desktop exercise on the first 24 hours. A tested imperfect procedure is worth more than an untested perfect one.

Documented procedures strengthen resilience by replacing improvisation with practice. Successful recovery depends upon preparation, coordination, communication and continual improvement.

**Continue reading:** explore BCM Institute's ISO 22301 courses and certifications at [blog.bcm-institute.org/certification](https://blog.bcm-institute.org/certification).

[View full post](https://blog.bcm-institute.org/bcm-v2/bcm-saesl-e3-cbf-1-chapter-10-business-continuity-recovery-procedure-for-cbf-1)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Dr Goh Moh Heng"
  },
  "dateModified" : "2026-11-17T03:43:02.013Z",
  "datePublished" : "2026-11-17T03:43:02Z",
  "headline" : "[BCM] [SAESL] [E3] [CBF] [1] Chapter 10: Business Continuity Recovery Procedure for CBF-1",
  "image" : {
    "@type" : "ImageObject",
    "height" : 60,
    "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
    "width" : 60
  },
  "mainEntityOfPage" : "https://blog.bcm-institute.org/bcm-v2/bcm-saesl-e3-cbf-1-chapter-10-business-continuity-recovery-procedure-for-cbf-1",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "BCM v2"
  }
}
```