---
title: "[BCM] [SAESL] [E3] [CBF] [1] Chapter 2: Sub-Critical Business Functions and Minimum Business Continuity Objectives for CBF-1"
description: SAESL's minimum safe service level for each of 12 engine MRO Sub-Critical Business Functions in CBF-1, set as measurable BU MBCOs 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\] \[14\] SAESL Turbine Maintenance Team-3](https://blog.bcm-institute.org/hs-fs/hubfs/SAESL%20Graphic%20Folder/BB%20SAESL/%5BBB%5D%20%5BSAESL%5D%20%5B14%5D%20SAESL%20Turbine%20Maintenance%20Team-3.png?width=1536&height=1024&name=%5BBB%5D%20%5BSAESL%5D%20%5B14%5D%20SAESL%20Turbine%20Maintenance%20Team-3.png "[BB] [SAESL] [14] SAESL Turbine Maintenance Team-3")

# \[BCM\] \[SAESL\] \[E3\] \[CBF\] \[1\] Chapter 2: Sub-Critical Business Functions and Minimum Business Continuity Objectives 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 1 splits CBF-1, Engine Maintenance, Repair and Overhaul (MRO) Operations, into 12 Sub-Critical Business Functions (Sub-CBFs) at Singapore Aero Engine Services Private Limited (SAESL). This chapter sets a minimum service level for each one. It tells SAESL, in advance, what must keep running during a disruption, at what level, and what may safely pause.

[![\[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 2: Sub-Critical Business Functions and Minimum Business Continuity Objectives 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)

## 1. Introduction

[![\[BCM\] \[SAESL\] \[E3\] \[BIA\] \[T1\] \[CBF\] \[1\] Engine Maintenance, Repair and Overhaul (MRO) Operations](https://no-cache.hubspot.com/cta/default/3893111/ac5e84b2-ea1f-46bd-a499-cb929d2dea0e.png)](https://cta-redirect.hubspot.com/cta/redirect/3893111/ac5e84b2-ea1f-46bd-a499-cb929d2dea0e)Chapter 1 split CBF-1, Engine Maintenance, Repair and Overhaul (MRO) Operations, into 12 Sub-Critical Business Functions (Sub-CBFs) at Singapore Aero Engine Services Private Limited (SAESL). This chapter sets a minimum service level for each one. It tells SAESL, in advance, what must keep running during a disruption, at what level, and what may safely pause.

The chapter continues the business impact analysis (BIA) under clause 8.2.2 of ISO 22301 and prepares the ground for the strategy work under clause 8.3. It draws on public information from the SAESL [website](https://www.saesl.com.sg/) and states its own assumptions in section 2. It is written for board readers first, without diluting technical accuracy.

### Three terms used in this chapter

- **Critical business function (CBF):** a service whose disruption would quickly cause unacceptable harm to customers, breach airworthiness approvals or other regulatory obligations, or damage trust.
- **Sub-Critical Business Function (Sub-CBF):** a distinct, assessable activity that, together with the others, delivers the CBF. "Sub" means "component of". It does not mean "less critical".
- **Business unit minimum business continuity objective (BU MBCO):** the minimum capability a Sub-CBF must keep running during a disruption so that the CBF can still be delivered safely and lawfully. It is a reduced but safe service level. It is neither normal operations nor a recovery target.

### Why CBF-1 is critical for SAESL

Chapter 1 explained why CBF-1 is critical: customers measure SAESL on turnaround time, every engine leaves under airworthiness approvals, and the work is safety-critical. This chapter adds a practical consequence. When capacity falls, SAESL cannot do everything at once. It needs to know in advance which engines and which activities come first.

This chapter uses the term "priority engines". It means engines already in test or final inspection, and engines that carry a customer-critical delivery commitment, such as a customer with an aircraft waiting for the engine.

The definition is deliberately simple. A shift manager can apply it in the middle of the night, and the board can change it when customer commitments or approvals change.

### Why the BIA works at Sub-CBF level

Chapter 1 showed that the parts of CBF-1 tolerate disruption differently. Four further benefits follow once each part is assessed on its own.

- **Visible dependencies:** each Sub-CBF shows what it needs from tooling, records, parts, systems and people.
- **Consistent assessment:** the same questions and scales apply to every process, so results can be compared.
- **Clear ownership:** every objective has a process owner who can confirm it is achievable.
- **Specific plans:** plans written for a named process are more useful than a generic plan for "engine overhaul".

Taken together, these benefits turn the BIA from a document into a working tool. A manager can read one row and know what the process is, what must continue and who answers for it.

### Why BU MBCOs are set

Without an agreed minimum, a disruption invites argument. One manager wants every engine to keep moving. Another wants only the most urgent. A BU MBCO settles the question before the event, in four ways.

- **A shared definition:** managers, the board and customers use the same words for "minimum acceptable service".
- **Protection of airworthiness and safety:** the objective sets the floor that cannot be relaxed, so pressure on turn-around time never lowers a safety standard.
- **Regulatory defensibility:** SAESL can show that it decided in advance how it would protect certification and records under stress.
- **A basis for pausing work:** it names what may be deferred, and for how long, which frees people and equipment for what cannot wait.

Each BU MBCO in this chapter states what must continue, which engines it covers, the measurable level, the safety floor and what may be deferred. Figures marked "(indicative)" are planning assumptions. They are not regulatory requirements.

For example, if a fault limited SAESL to half its normal test capacity, the objective for CBF-1.8 would already say which engines run first, which run wait, and when customers must be told. Managers would not need to negotiate those points under pressure.

### How this output is used

The BU MBCOs feed the later parts of the BIA, where recovery time objectives (RTOs) and maximum tolerable periods of disruption (MTPDs) are set. They then shape the recovery strategies in chapter 8 and the minimum resources in chapter 9. Chapter 10 turns them into a recovery procedure. Chapter 4 sets the RTOs and MTPDs. This chapter sets none.

## 2. Scope and Key Assumptions

The scope is CBF-1 only and the 12 Sub-CBFs from Chapter 1. It covers disruptions affecting people, premises, systems, suppliers and infectious disease outbreaks. Disruptions are assumed to last long enough to need a decision, so brief interruptions that a shift can absorb are out of scope. The objectives apply regardless of the cause. The following planning assumptions apply.

1. The Sub-CBF list and every BU MBCO are illustrative drafts for SAESL to validate.
2. Figures marked "(indicative)" must be validated with SAESL's production, quality and engineering leads and against the requirements of the Civil Aviation Authority of Singapore (CAAS) and the other approving authorities.
3. Airworthiness compliance, part and record traceability, calibrated tooling and test equipment, test cell safety, personnel safety and full release certification cannot be relaxed.
4. During a disruption, SAESL reduces throughput, not standards.
5. Priority engines are the engines described in section 1. The board or its delegate may change the definition.

## 3. Sub-Critical Business Functions and BU MBCOs

The table gives each Sub-CBF a short description and a BU MBCO. Read each objective as the lowest level SAESL would accept, not the level it aims for.

**Table 2: Sub-Critical Business Functions and Minimum Business Continuity Objectives for CBF-1 Engine Maintenance, Repair and Overhaul (MRO) Operations**

| **Sub-CBF Code** | **Sub-Critical Business Function** | **Description of Business Function** | **Business Unit Minimum Business Continuity Objective (BU MBCO)** |
| --- | --- | --- | --- |
| **CBF-1.1** | **Engine Induction and Work Scope Agreement** | **Activities: receives each engine and its records, carries out incoming inspection, logs the engine into the production system, and agrees the work scope in writing with the customer. Role in CBF-1: opens the production flow for every engine. Without a logged induction and an agreed scope, planning cannot release work, and the customer's expectations on content and timing are not set.** | **Every engine on site has a logged induction and a written, agreed work scope before work starts. New engines are accepted at no more than half (indicative) of normal weekly intake, with priority for customer-critical commitments. Incoming inspection is never skipped. Acceptance of routine engines may be deferred for up to 14 days (indicative).** |
| **CBF-1.2** | **Production Planning and Turnaround Control** | **Activities: builds and updates the production schedule, balances labour, parts, tooling and test cell slots, tracks milestones, and issues delivery forecasts and escalations. Role in CBF-1: links all the other Sub-CBFs so engines move in the right order, and tells customers early when commitments change, protecting trust when capacity is reduced. Its decisions are recorded so that later reviews can trace what was traded off.** | **A single priority list of engines in work is issued at least once per shift (indicative), ranking engines in test or final inspection first, then customer-critical commitments. Every customer with an affected engine receives a revised forecast within 24 hours (indicative) of a schedule change. Fine-tuning of the lower-priority schedule may be deferred for up to 7 days (indicative).** |
| **CBF-1.3** | **Engine Disassembly and Module Strip** | **Activities: strips engines into modules and parts using gantry and traditional methods, tags and records each part, and reports damage or deviations to engineering. Role in CBF-1: supplies the parts that every later stage depends on. Its records fix the engine's condition on arrival, supporting the agreed work scope and final certification. It also alerts engineering when findings change the expected work.** | **Stripping continues for priority engines, with every part tagged, recorded and placed in controlled storage at the point of removal. Safe handling and lifting checks are completed before each gantry or lifting task. Stripping of non-priority engines may pause for up to 14 days (indicative). No part is left untagged or unrecorded.** |
| **CBF-1.4** | **Part Inspection and Non-Destructive Testing** | **Activities: cleans parts, then inspects them visually, dimensionally and by non-destructive methods against approved limits, and records serviceable, repairable or scrap decisions. Role in CBF-1: acts as the main quality gate on parts. Its decisions determine what is repaired, replaced, or reused, and its records are essential evidence for engine certification. It also passes defect trends to engineering, which helps planning of later work scopes.** | **Every part of every priority engine receives its full inspection against approved limits, with results recorded at the time of inspection. Non-destructive testing uses only calibrated equipment and authorised staff. Inspection of parts for non-priority engines may be deferred for up to 14 days (indicative). No inspection step is shortened, and doubtful parts are quarantined.** |
| **CBF-1.5** | **Component Repair and Special Processes** | **Activities: repairs parts and applies special processes, including heat treatment and chemical processing, with the Centres of Excellence handling fan blades, compressor blades, guide vanes, stator vanes and front combustion liners. Role in CBF-1: returns repaired parts to the engine kit and shortens turnaround for the whole engine, reducing dependence on replacement parts. Process records for each repair form part of the engine's certification evidence.** | **Repairs needed by priority engines are completed using approved processes, qualified lines and authorised staff, with a process record for each part. Work for other customers and for stock replenishment may be deferred for up to 14 days (indicative). A repair is never carried out on a line, or by a provider, that lacks the required approval.** |
| **CBF-1.6** | **Materials and Life-Limited Part Management** | **Activities: orders, receives, stores and issues parts, materials and consumables, and manages the exchange and fitting of life-limited parts with full traceability. Role in CBF-1: makes sure complete, traceable kits reach the build area on time. A gap here stops the build, and a traceability failure can prevent release to service. It also controls quarantine of suspect parts so that they cannot enter a build.** | **Every part issued to a priority engine, including each life-limited part, has a recorded approved source and life status at the point of issue. Priority kits are completed at least one shift (indicative) before build starts. Replenishment of general stock and non-urgent consumables may be deferred for up to 7 days (indicative). No part with missing traceability is issued.** |
| **CBF-1.7** | **Engine Build and Module Assembly** | **Activities: assembles modules and the complete engine from serviceable parts, using calibrated tools and approved procedures, and records torque, clearance and other measured values. Role in CBF-1: turns parts into an engine. The quality of the build record decides whether the engine can pass test and certification. It relies on calibrated tooling and on kits that are complete and traceable when the build starts. It also raises open items for closure before the engine moves to test.** | **Build continues for priority engines, using only calibrated tools and approved procedures, with every step signed and measured values recorded at the time of the work. A second-person check is kept for all safety-critical steps. Builds of non-priority engines may pause for up to 14 days (indicative). No step is skipped, shortened or signed in advance.** |
| **CBF-1.8** | **Engine Test Cell Operations** | **Activities: runs built engines in the test facility for performance testing and vibration survey, investigates faults, and captures and reviews the test data. Role in CBF-1: proves that the engine performs to specification before release. It depends on trusted instrumentation and a safe cell, and no other Sub-CBF can replace it. Its data also supports final inspection and gives customers confidence in the result.** | **Test runs proceed only with calibrated instrumentation, a full safety crew and verified data capture. Built engines are tested in priority-list order. Troubleshooting runs for non-urgent faults may be deferred for up to 7 days (indicative). If the cell cannot operate safely, runs stop and affected customers are informed within 24 hours (indicative).** |
| **CBF-1.9** | **Final Inspection, Certification and Release to Service** | **Activities: reviews the engine and its record pack after test, resolves open items, and issues the release-to-service certificate under SAESL's airworthiness approvals. Role in CBF-1: is the last control before an engine leaves the site. It turns finished work into a certified product that customers and regulators accept. Only authorised staff may sign, so the activity depends on named, current authorisations. It also confirms that every open item from earlier stages is closed.** | **Every released engine has a complete record pack, a passed test result and a certificate signed by an authorised person. Release reviews are held daily (indicative) for engines ready for handover. Release is never given on partial records or a deferred inspection. Release of engines without a customer-critical commitment may be deferred for up to 7 days (indicative).** |
| **CBF-1.10** | **Engine Preservation and Shipment** | **Activities: inhibits and preserves engines, packs them, books transport, and completes shipping documents and customer notifications. Role in CBF-1: completes the delivery to the customer. It protects the engine's condition between release and installation and makes the turnaround-time commitment real. It also ensures that the paperwork a customer or carrier needs on arrival, such as transport and release documents, is complete and correct. Where hand-over is delayed, it keeps the engine safely preserved.** | **Every engine leaving the site is inhibited and packed to the approved standard, with transport documents complete and the customer notified before dispatch. Engines with customer-critical commitments ship first. Engines awaiting collection stay in preserved storage, checked at least weekly (indicative). Routine shipments may be deferred for up to 7 days (indicative).** |
| **CBF-1.11** | **Technical Records and Airworthiness Documentation** | **Activities: creates, controls, verifies and archives work orders, inspection and test records, traceability data and certificates for each engine. Role in CBF-1: provides the evidence that work was done correctly. Every other Sub-CBF writes to it, and the release to service depends on its completeness. It also supports audits, customer queries and any later in-service investigation, so records must stay retrievable long after the engine has left.** | **A complete, traceable record is held for every engine in work, using the electronic system or numbered paper job cards if it is unavailable. Paper entries are verified and entered within 48 hours (indicative) of the system returning. Records are never altered without authorisation. Back-scanning and archive tidying may be deferred for up to 14 days (indicative).** |
| **CBF-1.12** | **Customer Status Reporting and Engineering Support** | **Activities: provides customers with engine status, including web-based reporting, and gives engineering advice, concession reviews and modification support. Role in CBF-1: keeps customers informed, resolves technical questions that would otherwise stop work, and protects the relationship when schedules change. It also relays customer decisions on scope changes back to planning, so that engineering rulings and commercial agreements reach the shop floor without delay.** | **Customers of priority engines receive a status update at least daily (indicative) by any available channel. Urgent technical queries receive a first response within 4 hours (indicative), and only authorised engineers decide concessions. Routine status reports and modification studies may be deferred for up to 7 days (indicative).** |

All objectives and figures are illustrative planning assumptions. SAESL should validate them with the process owners before adopting them.

## 4. How These Outputs Support the BIA and Business Continuity Planning

### Support for the rest of the BIA

Each BU MBCO becomes the reference point for the remaining BIA tables. Chapter 3 assesses what would be lost if a Sub-CBF could no longer meet its objective. Chapter 4 tracks how that loss grows over time. Chapter 5 identifies the systems that the objective depends on, Chapter 6 the dependencies, and Chapter 7 the records.

Because every table uses the same Sub-CBF codes and the same objectives, results can be compared across chapters and checked for consistency.

### Minimum operating requirements

An objective is only achievable if the resources behind it exist. Each BU MBCO implies minimum staffing and skills, parts and tooling, records, and facilities. For example, a test cell objective implies calibrated instrumentation, a trained safety crew and a working data capture system. Chapter 9 turns these implications into numbers.

- **People:** authorised, current staff in the roles that inspect and sign.
- **Skills:** cross-training for roles held by only a few people.
- **Parts and tooling:** traceable parts and calibrated tools in the right place.
- **Records:** a working record system, or controlled paper that can replace it.
- **Facilities:** safe, powered working areas, including the test cell.

### Links to recovery time, strategy and planning

BU MBCOs inform the RTOs and MTPDs set in chapter 4, because a time target means little without a stated level of service to restore. They guide the choice of recovery strategy in chapter 8: a strategy that cannot deliver the objective is not a strategy. They also support resource prioritisation, as the objectives show which Sub-CBFs are protected first and which may pause. The same objectives set the content of each business continuity plan and the scenarios used in exercises. Where an objective cannot be met with the resources SAESL has today, that gap becomes a finding for the board, not a surprise during an incident.

Beyond planning, the objectives support operational resilience. They give SAESL a documented, measurable statement of how it would keep delivering safe, certified engines under pressure. That statement is useful in discussions with customers and with CAAS and the other approving authorities.

### Using the objectives in exercises

An objective that has never been exercised is a hope, not a capability. SAESL can test each BU MBCO with a short desktop exercise. The scenario might be the loss of the test cell for three days. Each process owner states what would continue, and the group checks the answer against the priority list and the safety floor. Gaps become actions. This links to the exercise programme in clause 8.5 and to continual improvement in clause 10 of ISO 22301.

### The board's role

The board, or a committee it delegates, should approve the BU MBCOs. Approval does three things. It confirms that managers may reduce throughput during a disruption without seeking permission each time. It accepts the residual risk that comes with a reduced service, such as delayed deliveries and the cost of rescheduling. It also makes clear that the safety floor stays in place, whatever the commercial pressure.

Board approval should also set a review cycle. The objectives should be reviewed at least once a year (indicative), and after any major change in customers, approvals, products or premises.

### What the objectives do not do

BU MBCOs do not set recovery times, choose strategies, or guarantee that every customer commitment will be met. They set the lowest acceptable level of service and the safety floor. Recovery time targets follow in chapter 4, and strategies in chapter 8.

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

### Next steps

1. Hold validation workshops with the production, quality, engineering and test cell leads to confirm or correct each objective.
2. Replace "(indicative)" figures with agreed values, or record why the indicative value stands.
3. Assign a process owner, by role, to each Sub-CBF.
4. Present the objectives to the board for approval.
5. Move on to the impact assessment in Chapter 3.

With the minimum service level agreed, SAESL can ask the next question: what is the business impact if a Sub-CBF cannot meet it?

**Continue reading:** Chapter 3, *Impact Area of Business Functions for CBF-1*, assesses the operational, financial, regulatory and customer impact of disrupting each Sub-CBF.

---

## **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:03:23.360Z",
  "datePublished" : "2026-11-17T02:03:23.000Z",
  "headline" : "[BCM] [SAESL] [E3] [CBF] [1] Chapter 2: Sub-Critical Business Functions and Minimum Business Continuity Objectives for CBF-1",
  "mainEntityOfPage" : {
    "@id" : "https://blog.bcm-institute.org/bcm-v2/bcm-saesl-e3-cbf-1-chapter-2-sub-critical-business-functions-and-minimum-business-continuity-objectives-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"
  }
}
```