[BCM] [SJ] [E3] [BIA] [T3] [CBF] [1] Project Design and Engineering Services

[Business Impact Analysis] [Critical Business Function] [T3] Part 5

BIA Questionnaires

Part 5: Inter-dependencies

CBF-1: Project Design and Engineering Services

In a multidisciplinary engineering and infrastructure consultancy like Surbana Jurong (SJ), the effective delivery of Project Design and Engineering Services (CBF 1) depends heavily on a network of internal and external inter-dependencies.

These inter-dependencies span across various departments, business units, strategic partners, and client stakeholders.

Each sub-process within this critical business function—ranging from project intake and scope definition to post-delivery support—requires seamless collaboration with specific stakeholders to ensure service continuity, quality assurance, and timely delivery.

Some dependencies serve as upstream inputs, such as initial client requirements and budget estimates; others are downstream, such as regulatory compliance, asset handover, and operational readiness.

There are also mutual dependencies where ongoing coordination is required throughout the lifecycle of the design and engineering process.

This chapter aims to identify and document these inter-dependencies for each Sub-CBF under CBF 1, highlighting the type and direction of the dependencies, the nature of collaboration required, and the potential impact on project continuity should any dependency be disrupted.

Based on the high-level critical business function CBF 1: Project Design and Engineering Services for Surbana Jurong (SJ), and using the structure and definitions from BCMpedia – Part 5: Inter-dependencies, the following table outlines the inter-dependencies for each Sub-CBF.

Table: Inter-dependencies for CBF-1 Project Design and Engineering Services

Sub-CBF Code	Sub-CBF	Name of Business Unit or Vendor/ Supplier/ Outsource Partner	Type of Depend-ency – Internal	Type of Depend-ency – External	Dependency Direction (Upstream / Downstream / Mutual)	Description of Nature of Dependency
1.1	Project intake & scope definition	Business Development, Clients, Regional Operations	✓	✓	Upstream	Business Development gathers project opportunities and initiates project scoping in collaboration with clients and local ops teams.
1.2	Conceptual design & cost estimating	Cost Consultancy, Architecture, Engineering, Clients	✓	✓	Mutual	Internal design teams work iteratively with cost consultants and client stakeholders to refine scope and budget.
1.3	Multidisciplinary design engineering	Civil, Structural, M&E, Transport Planning Units	✓	Internal	Coordination between multidisciplinary in-house teams to produce integrated designs.
1.4	Virtual coordination (VDC/CAVE)	BIM Team, IT, External VDC Consultants	✓	✓	Mutual	Internal and external parties use digital platforms (e.g., BIM, CAVE) for real-time coordination and clash detection.
1.5	Digital delivery & QA compliance	QA/QC Unit, IT Department, Clients, Regulatory Authorities	✓	✓	Downstream	QA/QC ensures deliverables meet internal and external standards; coordination with regulatory bodies for approval.
1.6	Handover & asset ops readiness	Facility Management, Clients, Asset Owners	✓	✓	Downstream	Coordination with FM teams and clients to ensure a smooth transition from construction to the operation phase.
1.7	Post‑delivery support	Client Services, Maintenance Teams, Contractors	✓	✓	Downstream	Ongoing support relies on feedback loops and coordination with contractors for defect rectification or enhancements.
1.8	Innovation & continuous improvement	R&D, Knowledge Management, Tech Partners	✓	✓	Upstream	Inputs from R&D and technology partners feed into design methodology and digital innovations.

Summing Up ... Part 5

Understanding the inter-dependencies within CBF 1: Project Design and Engineering Services enables Surbana Jurong to proactively manage risks and disruptions that could affect critical project milestones.

By mapping the internal and external relationships for each Sub-CBF, the organisation gains more profound insight into the flow of information, decision-making processes, and service handoffs.

This structured overview of dependencies not only supports continuity planning and recovery efforts but also strengthens coordination between departments, enhances communication with clients and external partners, and aligns with the organisation’s commitment to delivering integrated and sustainable solutions.

As we advance, these insights can be used to optimise process resilience further and ensure uninterrupted service in the face of crises or operational challenges.

[Business Impact Analysis] [Critical Business Function] [T3] Part 6

BIA Questionnaires

Part 6: Vital Records

CBF-1: Project Design and Engineering Services

In the context of Business Continuity Management (BCM), vital records are defined as documents, data, and information critical to the continued operation and recovery of an organisation’s essential functions.

For Surbana Jurong (SJ), the Critical Business Function (CBF) of Project Design and Engineering Services plays a pivotal role in delivering multidisciplinary infrastructure and urban development projects.

The safeguarding of vital records associated with this CBF ensures that SJ can maintain service delivery, meet regulatory and contractual obligations, and restore operations efficiently in the event of a disruption.

This section identifies and documents the vital records for each sub-process (Sub-CBF) under CBF 1.

These records encompass architectural and engineering designs, client agreements, QA documentation, BIM models, and handover deliverables, among others.

They are often irreplaceable or costly to reproduce and are crucial for ensuring continuity of design integrity, project compliance, and client satisfaction.

The table in this chapter outlines the Sub-CBF code and description, the type of vital records associated with each sub-process, the media in which these records are stored, their physical or digital locations, and the designated custodians responsible for their safekeeping.

This mapping serves not only as a compliance requirement under ISO 22301 but also as an operational guide for record preservation and recovery planning.

Vital Records Table for CBF 1: Project Design and Engineering Services

Sub‑CBF Code	Sub‑CBF	Description of Vital Records	Media Type	Location	In Whose Care
1.1	Project intake & scope definition	Signed client briefs, project scope agreements, and requirement documentation	Digital documents, scanned PDFs	Project SharePoint: secure cloud repository	Project Manager / PMO
1.2	Conceptual design & cost estimating	Cost estimates, conceptual sketches, feasibility reports, and preliminary budget approvals	CAD files, Excel, PDF reports	Design servers; project workspace	Lead Cost Estimator
1.3	Multidisciplinary design engineering	Finalised design drawings (architectural, structural, MEP), consulting engineer reports, and design review sign‑offs	CAD/BIM files, signed PDFs	BIM platform; design document management system	Design Coordinator / Engineering Lead
1.4	Virtual coordination (VDC/CAVE)	VDC models, clash detection reports, and coordination meeting minutes	BIM models, reports	BIM collaboration platform	VDC Manager
1.5	Digital delivery & QA compliance	QA checklists, digital delivery packages, approval certificates (e.g. ISO or internal QA), submission records	PDFs, digital QA logs, video logs	QA system; document management repository	QA Lead / Compliance Officer
1.6	Handover & asset ops readiness	As‑built drawings, handover documentation, asset tags list, operation & maintenance manuals	CAD/BIM files, PDFs, spreadsheets	Asset management system; shared drive	Handover Manager / Operations Lead
1.7	Post‑delivery support	Warranty documentation, service report records, and client support correspondence	PDF documents, email threads	CRM or support ticketing system; email archive	Support Manager or Helpdesk Team
1.8	Innovation & continuous improvement	Process improvement proposals, lessons‑learned reports, and innovation project documentation	Word/PDF reports, presentations	Internal innovation repository; intranet	Innovation Lead / Knowledge Manager

Notes on Template Application

Description of Vital Records: Includes critical, original documents essential for each Sub‑CBF (e.g., signed agreements, unique models, QA approvals) consistent with BCMpedia guidance.
Media Type, Location, and In Whose Care columns reflect typical digital and storage practices. Actual details should align with SJ’s internal systems, platforms (like SharePoint, BIM systems), and staff roles.
Purpose: Identifying records that are unique/irreplaceable and critical for restoration or legal/operational continuity in disruptions.

Summing Up ... Part 6

The identification and protection of vital records for CBF 1: Project Design and Engineering Services are fundamental to ensuring Surbana Jurong’s resilience and ability to respond swiftly to disruptions.

By systematically cataloguing critical records across all stages of the design and engineering lifecycle—from project intake through to post-delivery support—SJ strengthens its capacity to safeguard intellectual property, uphold project commitments, and resume business operations with minimal downtime.

This structured approach to vital records management enhances not only the effectiveness of BCM implementation but also fosters a culture of accountability and preparedness among project teams.

These records must be regularly reviewed, securely stored, and integrated into both operational workflows and business continuity strategies to ensure their accessibility and integrity in any crisis scenario.

Business Continuity Planning at Surbana Jurong: A Strategic Approach
eBook 3: Starting Your BCM Implementation
MBCO	P&S	RAR T1	RAR T2	RAR T3	BCS T1	CBF

CBF 1: Project Design and Engineering Services
DP	BIAQ T1	BIAQ T2	BIAQ T3	BCS T2	BCS T3	PD

More Information About Business Continuity Management Courses

To learn more about the course and schedule, click the buttons below for the BCM-300 Business Continuity Management Implementer [B-3] course and the BCM-5000 Business Continuity Management Expert Implementer [B-5].