---
title: "[BCM] [SAESL] [E3] [CBF] [1] Chapter 1: Sub-Critical Business Functions for CBF-1"
description: "Starting the SAESL business impact analysis: 12 Sub-Critical Business Functions that deliver CBF-1 engine MRO operations, aligned with ISO 22301 clause 8.2.2."
---

.

[![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\] \[11\] Aerospace Maintenance Operations Briefing](https://blog.bcm-institute.org/hs-fs/hubfs/SAESL%20Graphic%20Folder/BB%20SAESL/%5BBB%5D%20%5BSAESL%5D%20%5B11%5D%20Aerospace%20Maintenance%20Operations%20Briefing.png?width=1536&height=1024&name=%5BBB%5D%20%5BSAESL%5D%20%5B11%5D%20Aerospace%20Maintenance%20Operations%20Briefing.png "[BB] [SAESL] [11] Aerospace Maintenance Operations Briefing")

# \[BCM\] \[SAESL\] \[E3\] \[CBF\] \[1\] Chapter 1: Sub-Critical 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)

The chapter follows *Understanding Your Organisation for SAESL* (eBook 1), which identified SAESL's Critical Business Functions, and *Implementing Business Continuity Management for SAESL* (eBook 2). It opens the business impact analysis (BIA) that ISO 22301 expects under clause 8.2.2: a structured study of how disruption harms an organisation over time. The chapter uses public information from the SAESL [website](https://www.saesl.com.sg/) and states its own assumptions where that information ends.

[![\[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 1: Sub-Critical 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)

## 1. Introduction

[![\[BCM\] \[SAESL\] \[E3\] \[BIA\] \[DP\] \[CBF\] \[1\] Engine Maintenance, Repair and Overhaul (MRO) Operations](https://no-cache.hubspot.com/cta/default/3893111/6c1c7491-d6f6-48d5-ad46-a55390fc3307.png)](https://cta-redirect.hubspot.com/cta/redirect/3893111/6c1c7491-d6f6-48d5-ad46-a55390fc3307)Singapore Aero Engine Services Private Limited (SAESL) is a Rolls-Royce Trent Centre of Excellence in Singapore, providing engine overhaul and component repair for the Trent engine family. Its engine maintenance, repair and overhaul (MRO) operations are the core of that business. This chapter breaks that function, designated CBF-1, into the 12 processes that deliver it from the moment an engine arrives to the moment it ships.

The chapter follows *Understanding Your Organisation for SAESL* (eBook 1), which identified SAESL's Critical Business Functions, and *Implementing Business Continuity Management for SAESL* (eBook 2). It introduces the business impact analysis (BIA) that ISO 22301 expects under clause 8.2.2: a structured study of how disruption harms an organisation over time. The chapter uses public information from the SAESL [website](https://www.saesl.com.sg/) and states its own assumptions where that information ends.

### What CBF-1 involves at SAESL

A critical business function (CBF) is a service whose disruption would quickly cause unacceptable harm to customers, breach regulatory obligations or damage trust. CBF-1, Engine Maintenance, Repair and Overhaul (MRO) Operations, covers the work that turns a used Trent engine into a certified, serviceable one.

SAESL supports the Trent 500, 700, 800, 900, 1000 and XWB. It offers three levels of work scope: hospital, check and repair, and full refurbishment. Strip and build uses both gantry and traditional methods. An in-house test facility handles engines up to 140 inches in diameter and 150k pounds of thrust. SAESL states that it can repair and overhaul over 300 Trent engines a year, with over 1,000 skilled people, for customers on six continents.

The engines SAESL overhauls power aircraft including the A330, A340, A350, A380, Boeing 777 and Boeing 787. Customers therefore depend on SAESL to return engines on time and in a condition they can trust.

### Why CBF-1 is a Critical Business Function

Three features make CBF-1 critical. First, customers measure SAESL on turnaround time. SAESL's own mission links best quality with turnaround time, so a stalled engine is a visible failure. Second, every engine leaves under airworthiness approvals. SAESL lists approvals from 13 airworthiness bodies, including the Civil Aviation Authority of Singapore (CAAS). A gap in the work or the records puts those approvals, and the right to release engines, at risk. Third, the work is safety-critical. An error in assembly, inspection or test can reach an aircraft in service.

For these reasons, CBF-1 cannot be judged as one block. A short interruption to one part of it may be tolerable. A short interruption to another may halt every release.

### What a Sub-Critical Business Function is

A Sub-Critical Business Function (Sub-CBF) is a distinct, assessable process that, together with the others, delivers a CBF. The word "sub" means "component of". It does not mean "less critical". Some Sub-CBFs are among the most critical activities SAESL performs.

A relay race offers a useful comparison for board readers. The team wins or loses the race as a whole, but each leg has its own runner, its own baton hand-over and its own chance of a dropped baton. A BCM programme that studies only the whole race will miss where the baton is most likely to fall.

### Why decomposition matters in BCM

Business continuity management (BCM) is the discipline of keeping critical activities running, or restoring them in time, when disruption occurs. Decomposition supports it in four ways.

- **Different tolerance:** the parts of CBF-1 tolerate disruption differently. Loss of the test cell stops engine release far sooner than a delayed customer status update stops the shop.
- **Visible dependencies:** a process that looks self-contained often relies on tooling, records, parts, or people elsewhere. Splitting the function exposes them.
- **Clear ownership:** each Sub-CBF can have a named owner who answers for its continuity.
- **Specific plans:** the maximum tolerable period of disruption (MTPD) and the recovery time objective (RTO) can be set for each process instead of once for the whole function.

Consider two disruptions of equal length. In the first, the customer status portal is unavailable for a day. Engines keep moving, and staff can update customers by email. In the second, the test cell is unavailable for a day. Built engines queue behind it, slots slip, and every later stage waits. Both are one-day outages, yet they matter very differently to CBF-1. The example is illustrative, but it shows why one figure for the whole function would mislead.

The list in this chapter becomes the unit of analysis for chapters 2 to 10. Chapter 2 sets a minimum service level for each Sub-CBF. Chapters 3 to 7 complete the BIA. Chapters 8 and 9 turn the results into recovery strategies and minimum resources. Chapter 10 converts them into a recovery procedure.

This chapter does not set RTOs, MTPDs, impact ratings, resource needs or strategies. Those belong to later chapters.

### How the 12 Sub-CBFs were chosen

The list follows an engine's path through the shop, from induction to shipment, using the services SAESL describes publicly: engine overhaul at every work scope level, component repair, testing, and engineering support. Each process appears in exactly one Sub-CBF, so no activity is counted twice, and none is left out.

Before the list was fixed, it was checked against 13 areas of MRO work, from engine receipt and planning to records and customer reporting. Tooling and calibration control was the one area placed outside CBF-1, and section 3 explains why. Section 4 records the assumptions that SAESL should confirm.

## 2. Sub-Critical Business Functions of CBF-1

The table lists the 12 Sub-CBFs in the order an engine passes through the shop. Names are processes, not departments or job titles, so the list holds even if SAESL changes its organisation chart. Each description states what the process does, when it starts and what it produces. Each example shows how a disruption might be handled, without lowering any standard.

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

| **Sub-CBF Code** | **Sub-Critical Business Function** | **Description of Process / Activity** | **Example (SAESL Context)** |
| --- | --- | --- | --- |
| **CBF-1.1** | **Engine Induction and Work Scope Agreement** | **Receives each engine from the customer, checks the engine and its accompanying records on arrival, and agrees the work scope (hospital, check and repair, or full refurbishment) with the customer. It starts whenever an engine arrives, or a customer requests a slot. It produces a logged induction, an incoming inspection report, an agreed work scope and a unique work order, which together trigger planning and production for that engine.** | **An engine arrives with its records after removal from an aircraft. SAESL might inspect it on arrival, compare the findings with the removal report, and propose a check-and-repair scope. The customer approves the scope by electronic message, and the engine passes to planning. If the records are incomplete, induction is held until the customer supplies the missing documents.** |
| **CBF-1.2** | **Production Planning and Turnaround Control** | **Sequences engines, modules and components through the shop against agreed turnaround-time commitments. It runs continuously, with daily and weekly planning cycles, and reconciles labour, parts, tooling and test cell availability. It produces the production schedule, priority lists, revised delivery forecasts for customers, and early escalations whenever a milestone is at risk of being missed.** | **A late parts delivery puts one engine behind schedule. Planning might re-sequence work so that a second engine uses the idle strip area, update the forecast delivery date, and warn the customer before the committed date is at risk. The decision, and the reason for it, are recorded so that later reviews can trace what was traded off.** |
| **CBF-1.3** | **Engine Disassembly and Module Strip** | **Strips the engine into modules and then into parts, using gantry and traditional methods, and records the condition and location of every part. It starts when planning releases an engine to the strip area. It produces a documented set of cleaned and tagged parts, ready for inspection, with any damage or deviation recorded against the work order and reported to engineering.** | **A technician removes a module and finds unexpected wear. The finding is recorded on the work order, the parts are tagged and held in a controlled location, and engineering is alerted so that the work scope can be reviewed with the customer. Stripping of other modules continues, so the engine does not wait for the decision.** |
| **CBF-1.4** | **Part Inspection and Non-Destructive Testing** | **Cleans and inspects parts against approved limits, using visual, dimensional and non-destructive testing (NDT) methods such as fluorescent penetrant and magnetic particle inspection. It runs for every part of every engine before repair or reuse. It produces serviceable, repairable or scrap decisions, non-conformance reports and inspection records that support later certification of the engine.** | **A batch of compressor parts is inspected for cracks. Parts that pass return to the engine kit, parts needing repair go to component repair, and any part beyond limits is quarantined and reported so that it cannot re-enter the supply chain. The inspection record for each part is linked to the work order before the batch moves on.** |
| **CBF-1.5** | **Component Repair and Special Processes** | **Repairs components and applies special processes such as heat treatment and chemical processing, including work by the Centres of Excellence for fan blades, compressor blades, nozzle guide vanes, compressor stator vanes, and front combustion liners. It starts when an inspected part is routed for repair. It produces repaired components with process records, ready for the engine kit or for other customers.** | **Fan blades awaiting repair queue behind a failed processing line. SAESL might move the work to a qualified alternate line, apply the approved process cards, and record the change, so that repaired blades still arrive in time for engine build. Any move to a line that lacks the required approval would not be considered.** |
| **CBF-1.6** | **Materials and Life-Limited Part Management** | **Orders, receives, stores and issues the parts, materials and consumables an engine needs, and manages the exchange and fitting of life-limited parts (LLPs), whose permitted life is strictly limited. It runs continuously against the production plan. It produces parts kits delivered to the build area, with the approved source, life status, and traceability of every part fully recorded.** | **A build kit is short of one LLP. Materials staff might locate an approved stock item or exchange unit, check its life status and paperwork, and deliver it with the kit, so that the build starts on schedule without any gap in traceability. A part with missing or doubtful paperwork stays in quarantine until the gap is closed.** |
| **CBF-1.7** | **Engine Build and Module Assembly** | **Assembles modules and the complete engine from serviceable parts, using gantry and traditional build methods, calibrated tools and approved procedures. It starts when a complete kit reaches the build area. It produces a built engine with signed build records, torque and clearance measurements, and a list of any open items that must be closed before the engine goes to test.** | **A build stage needs a calibrated tool that is past its calibration date. The stage is paused, the tool is replaced from a controlled store, and the affected steps are repeated, so that the build record remains complete and defensible. The event is logged so that quality can review how the out-of-date tool reached the bench.** |
| **CBF-1.8** | **Engine Test Cell Operations** | **Runs each built engine in the test facility to verify performance, conduct a vibration survey, and, where needed, investigate faults. It starts when a built engine is ready, and a test slot is available. It produces test data, a pass or fail result, any troubleshooting findings, and the test cell records needed for final inspection, which no other process can replace.** | **An engine is scheduled for a performance run when an instrumentation fault appears. The test team might stop the run, replace or recalibrate the affected sensor, repeat the run, and log the delay for planning, rather than accept data that cannot be trusted. The next engine in the queue is told its revised slot as soon as it is known.** |
| **CBF-1.9** | **Final Inspection, Certification and Release to Service** | **Reviews the complete engine and its records after test, confirms that all work has been done to approved standards, and issues the release-to-service certification under SAESL's airworthiness approvals. It starts when the engine passes test, and the records are complete. It produces a certified engine and the certification documents that customers and regulators rely on, which only authorised staff may sign.** | **A final records review finds one missing signature on a build step. The release is held until the record is corrected through the approved process, the cause is logged, and the customer is told the revised hand-over date. The engine is not released early to protect the schedule, because the certificate depends on a complete record.** |
| **CBF-1.10** | **Engine Preservation and Shipment** | **Inhibits and preserves the engine for storage or transport, packs it, arranges collection or dispatch, and completes shipping documents. It starts once the engine is released. It produces an engine ready for handover to the customer or its carrier, with transport documents completed and the customer notified of the shipment, including the expected arrival time at its destination.** | **A carrier misses a collection slot. SAESL might keep the engine in preserved storage, re-check that the preservation remains valid, rebook transport through an alternative carrier, update the shipping documents, and tell the customer the new collection time. If storage is extended, the preservation record is updated so the engine arrives in the certified condition.** |
| **CBF-1.11** | **Technical Records and Airworthiness Documentation** | **Creates, controls and archives the work orders, inspection and test records, part traceability data and certification documents for every engine. It runs throughout the engine's time in the shop and after release. It produces a complete, retrievable record pack that proves the work was done correctly and supports audits, customer queries and the investigation of any later in-service event.** | **The electronic records system becomes unavailable during a build. Staff might switch to controlled paper job cards, number and log them, and enter the data into the system after recovery, with a second-person check to ensure no entries were lost. The paper cards are retained until the electronic record has been verified as complete.** |
| **CBF-1.12** | **Customer Status Reporting and Engineering Support** | **Provides customers with regular engine status updates, including web-based reporting, and provides engineering advice, concession reviews, and modification support when findings or customer questions arise. It runs daily during the engine's stay. It produces status updates, technical dispositions, and agreed changes to the work scope, keeping customers informed and allowing decisions to be made in time to protect the schedule.** | **The customer status portal becomes unavailable. The customer support team might send a daily status summary by email, answer urgent technical queries by telephone, and log each response, so that customers still receive timely and consistent information. Once the portal returns, the summaries are reconciled with the portal data to remove any differences between the two.** |

All descriptions and examples are illustrative. SAESL should confirm or correct them, and its process owners should check that each description matches how the work is actually done, before the list is used for planning.

## 3. Interfaces with Other Functions

Some processes that CBF-1 depends on are owned elsewhere. They are named here as interfaces and are not decomposed. Later chapters treat them as dependencies.

- **Tooling, equipment and calibration control:** tools and test equipment must be in calibration before use, so loss of this service can stop assembly and test.
- **Quality and regulatory compliance management:** approvals, audits and the management system certificates sit here, and every release depends on them.
- **Facilities and utilities:** power, gas, water and building services support the strip, repair, build and test areas.
- **Information and communications technology (ICT):** production, records and customer reporting systems rely on networks, applications and support.
- **Human resources and training:** competent, authorised staff are a precondition for certifying work.
- **Finance and procurement:** purchasing and payment keep parts, materials and subcontract services flowing.
- **Sales and contract management:** customer agreements set the commitments that planning must meet.
- **Safety, health and environment:** safe working conditions and environmental controls apply to every area.

## 4. Key Assumptions

The following assumptions underpin this chapter. SAESL management should confirm or correct each one.

1. The list of 12 Sub-CBFs is an illustrative draft prepared from public information. SAESL's own CBF register was not available.
2. Component repair, including the Centres of Excellence, sits inside CBF-1. If SAESL manages it as a separate CBF, CBF-1.5 becomes an interface.
3. The same 12 Sub-CBFs apply to every Trent variant and every work scope level.
4. Every engine passes through all 12 Sub-CBFs, although the depth of work varies by work scope.
5. Release to service is the final control. No continuity measure may bypass inspection, testing or certification.
6. SAESL runs one on-site engine test facility.
7. Technical records are held partly in electronic systems and partly on paper.
8. Tooling and calibration, quality management, facilities, ICT, human resources, finance and sales sit outside CBF-1.
9. Process owners will be assigned by role, not by name, during validation.
10. The list makes no assumption about the number of engines in the shop at any one time.

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

## 5. Conclusion

CBF-1 is too broad to analyse in one piece. The 12 Sub-CBFs give SAESL a shared, process-level view of how an engine moves from induction to shipment, and of where disruption would hurt most. The sections below show how the list will be used.

### Business impact analysis

The BIA will assess each Sub-CBF separately. For each one, it will estimate how impact grows with time, then set an MTPD and an RTO. A process such as test cell operations will probably show a very different profile from customer status reporting. Without the decomposition, one average figure would hide both. The same list will also keep later tables consistent, because every impact, system, dependency and record is tied to a Sub-CBF code.

### Risk assessment

Clause 8.2.3 of ISO 22301 asks organisations to assess the risks of disruption to prioritised activities. With the Sub-CBF list, SAESL can ask specific questions: what could stop the strip area, the test cell or the records system, and how likely is it? The answers are far more useful than a general view of risk to engine overhaul. Threat scenarios can then be written against a named process, making them easier to test in an exercise.

### Business continuity strategy

Clause 8.3 covers the choice of strategies and solutions. A process that depends on one person, one machine or one supplier needs a different answer from a process that depends on a shared system. The list lets SAESL match each strategy to the process it protects, and to the time that process can tolerate.

### Business continuity plans

Clause 8.4 requires documented plans and procedures. Each Sub-CBF can have its own owner, recovery steps, and contact list. Chapter 10 of this eBook shows how those steps are organised before, during and after a disruption.

### Operational resilience and regulatory assurance

SAESL operates under approvals from CAAS and 12 other airworthiness authorities. Without quoting any requirement, it is reasonable to expect these bodies to value evidence that SAESL knows its critical processes, understands their dependencies and can protect certification and records during a disruption. A documented Sub-CBF list is the first piece of that evidence. It also helps the board see which processes, if lost, would put approvals and customer commitments at risk. Conversations with regulators then start from documented evidence rather than from general assurance.

### Next steps

SAESL should validate the list before using it. A short workshop with the production, quality, engineering, and test cell leads can confirm each name and boundary, assign a role-based owner, and decide whether component repair belongs inside CBF-1. Once agreed, the codes should be fixed under document control, because every later BIA table refers to them. Changes after that point should follow the same change process as any other controlled document.

Chapter 2 builds on this list by setting a minimum business continuity objective for each Sub-CBF: the lowest safe level of service that must continue during a disruption.

**Continue reading:** Chapter 2, *Sub-Critical Business Functions and Minimum Business Continuity Objectives for CBF-1*, sets the minimum level of service that each Sub-CBF must keep running during a disruption.

---

## **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-17T01:59:18.947Z",
  "datePublished" : "2026-11-17T01:59:18.000Z",
  "headline" : "[BCM] [SAESL] [E3] [CBF] [1] Chapter 1: Sub-Critical Business Functions for CBF-1",
  "mainEntityOfPage" : {
    "@id" : "https://blog.bcm-institute.org/bcm-v2/bcm-saesl-e3-cbf-1-chapter-1-sub-critical-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"
  }
}
```