M Bac 000000 Ge00 MPL 000002

Table of Contents
1 PURPOSE ...................................................................................................................................................4
2 DEFINITIONS............................................................................................................................................5
3 ABBREVIATIONS.....................................................................................................................................6
4 REFERENCE DOCUMENTS ....................................................................................................................6
5 INTRODUCTION ......................................................................................................................................7
5.1 GENERAL PROJECT INFORMATION ...................................................................................................................7
5.2 CONTRACTUAL BASIS .........................................................................................................................................7
5.3 DESIGN SCOPE .....................................................................................................................................................8
5.4 CIVIL WORKS JV INFRASTRUCTURE DESIGN PACKAGING AND EXECUTION .............................................8
5.4.1 CWJV Engineering Hub ................................................................................................................................... 8
5.4.2 CWJV Detailed Design Packaging .............................................................................................................. 9
5.5 TRANSIT SYSTEMS DESIGN PACKAGING AND EXECUTION ........................................................................ 10
5.6 DESIGN ORGANIZATION .................................................................................................................................. 10
5.6.1 Consortium Technical Management Team .........................................................................................10
5.6.2 Transit Systems Integration .......................................................................................................................11
5.6.3 Civil Works Engineering Delivery ............................................................................................................11
5.6.4 Civil Works Integration.................................................................................................................................11
6 RESPONSIBILITIES .............................................................................................................................. 13
6.1 DESIGN AUTHORITY ........................................................................................................................................ 13
6.2 KEY ROLES ........................................................................................................................................................ 13
6.2.1 CWJV Engineering Director ........................................................................................................................13
6.2.2 Consortium Systems Integration Manager..........................................................................................13
6.2.3 Consortium Systems Integration Manager Transit Systems.......................................................13
6.2.4 Consortium Systems Integration Manager Civils Infrastructure..............................................14
6.2.5 Consortium Design Manager......................................................................................................................14
6.2.6 Transit Systems Integration Manager...................................................................................................14
6.2.7 CWJV Integration Manager.........................................................................................................................14
6.2.8 CWJV Engineering Managers .....................................................................................................................15
7 RMP DESIGN PROCESS ....................................................................................................................... 15
7.1 DESIGN INPUTS ................................................................................................................................................ 17
7.1.1 Engineering Safety Management.............................................................................................................17
7.1.2 Standards Management ...............................................................................................................................17
7.1.3 Requirements Management........................................................................................................................18
7.1.4 Reliability, Availability and Maintainability (RAM)........................................................................18
7.1.5 Verification and Validation.........................................................................................................................19
7.1.6 EMC/EMI..............................................................................................................................................................19
7.2 DESIGN DEVELOPMENT STAGES ................................................................................................................... 19
7.2.1 General..................................................................................................................................................................19
7.2.2 Red Diamond......................................................................................................................................................19
7.2.3 60% Design Gate Review..............................................................................................................................20
7.2.4 90% Draft Final Gate Review.....................................................................................................................20
7.2.5 100% Final Design Gate Review ...............................................................................................................20
7.2.6 Issue for Construction....................................................................................................................................21
Document No. M-BAC-000000-GE00-MPL-000002 Page 2 of 37 Printed: 3 Dec. 14

Design Management Plan
Electronic documents once printed, are uncontrolled and may become out-dated. Refer to Aconex for current revision.
2013 High Commission for the Development of ArRiyadh
8 DESIGN MANAGEMENT PROCESSES AND PROCEDURES........................................................ 21
8.1 DESIGN MANAGEMENT PLAN ........................................................................................................................ 21
8.2 INTERFACE MANAGEMENT ............................................................................................................................ 22
8.3 DESIGN PROGRESS REPORTING ..................................................................................................................... 23
8.4 ENGINEERING DELIVERABLES LIST (EDL)................................................................................................. 23
8.5 DESIGN REVIEWS ............................................................................................................................................. 24
8.6 ACCEPTANCE OF DESIGN ................................................................................................................................ 25
8.6.1 Safety in Design ................................................................................................................................................25
8.6.2 Design Checks ....................................................................................................................................................27
8.6.3 Independent Design Checks ........................................................................................................................27
8.6.4 Independent Checking Engineer (ICE)...................................................................................................28
8.6.5 Independent Safety Assessor (ISA) ..........................................................................................................29
8.6.6 Design Gate Reviews.......................................................................................................................................29
8.6.7 Design Gate Review Close-out....................................................................................................................31
8.7 DESIGN TOOLS .................................................................................................................................................. 31
8.8 CONFIGURATION AND DESIGN CHANGE CONTROL .................................................................................... 33
8.8.1 Configuration Baseline..................................................................................................................................33
8.8.2 Design Change Control..................................................................................................................................33
8.9 CERTIFICATION AND RECORDS ...................................................................................................................... 34
8.9.1 Design check records......................................................................................................................................34
8.9.2 Design Gate Review Acceptance Certificate........................................................................................35
8.9.3 Requirements Compliance Matrix ...........................................................................................................35
8.9.4 Design Completion Certification...............................................................................................................35
8.9.5 Issue for Construction Documentation..................................................................................................35
8.10 DESIGN ACTIVITIES DURING INSTALLATION AND TEST & COMMISSIONING PHASES .......................... 35
9 COMPETENCY........................................................................................................................................ 36
10 RELATED DESIGN TASKS.............................................................................................................. 37
10.1 LEADERSHIP IN ENERGY AND ENVIRONMENTAL DESIGN (LEED)......................................................... 37
10.2 ASSET MANAGEMENT AND TRACEABILITY ................................................................................................. 37

1 PURPOSE
The purpose of this Design Management Plan (DMP) is to define the engineering
organisation and management processes through the whole project life cycle (Design,
Procurement, Construction, Installation, Testing and Commissioning), which will be applied
to the design of Package 1.
The BACS Consortium Technical Management Team manages the overall engineering
design process for Package 1 and the interfaces with other Consortia and local authorities.
This DMP ensures smooth and consistent design management from the high-level Line 1 &
2 project requirements down to the detailed design of the civils infrastructure, building
finishes, infrastructure system definitions, system design and associated engineering during
installation, testing and commissioning and Trial Operations.
The BACS Consortium Systems Integration Manager is responsible for this plan, its
application and updating when required.

2 DEFINITIONS
Term Definition
Employer Arriyadh Development Authority or organisations acting as its agents
(e.g. Riyadh Metro Transport Consultants RMTC)
Engineer The resident engineer or any responsible work supervisor, who may,
from time to time, be appointed by the Employer. This role is fulfilled
by RMTC for the Riyadh Metro project
Designer Entities carrying out the design
BACS The Consortium delivering the Riyadh Metro Project Package 1

(Lines 1 & 2)
Civil Works Joint A joint venture of Bechtel, Almabani and CCC responsible for the
Venture delivery of the civil infrastructure including mechanical/electrical
works
Design Package All design documentation and related Health & Safety information
required to carry out the works for the relevant construction package
in accordance with all Health & Safety requirements and legislation,
Local Authority consents and their contractual scope of work.
Transit Systems The line wide rail systems delivered by Siemens through their product
lines including:
Signalling
Rolling Stock
Communications infrastructure
Traction and high voltage power supplies
Platform Screen Doors
Depot equipment
SCADA system
Others Other organisations that are not part of the BACS RMP contract also
known as Stakeholders

3 ABBREVIATIONS
Abbreviation Definition
ADA Arriyadh Development Authority
ALARP As Low As Reasonably Practicable
BACS Bechtel, Almabani, CCC, Transit Systems
CWJV Civil Works Joint Venture
CWIM Civil works JV Integration Manager
CWEM Civil Works JV Engineering Manager
DMP Design Management Plan
DPM Design Package Manager
EMDL Engineering Master Deliverables List
IFC Issue for Construction
KAFD King Abdullah Financial District
NATM New Austrian Tunnelling Method (method of applying sprayed concrete
linings in tunnels and caverns). Also known as Sprayed Concrete Lining
RMP Riyadh Metro Project
TSIM Transit Systems Integration Manager
4 REFERENCE DOCUMENTS
Item Title Document Reference

1 Consortium System Safety Plan M-BAC-000000-GE00-MPL-000002
2 Consortium Interface Management Plan M-BAC-000000-GEIM-MPL-000001
3 ISO/IEC 15288 Systems and Software
Engineering
4 Consortium Requirements Management Plan M-BAC-000000-GE00-MPL-000045
5 Consortium Risk Management Process Number to be allocated
6 Documentation Plan M-BAC-000000-GD00-MPL-000001
7 RMP BIM Execution Plan M-BAC-000000-GEBM-MPL-000001
8 Engineering Assurance Design Gates M-BAC-000000-GE00-PRO-000010
Procedure
9 Consortium EMC Management Plan M-BAC-00000-SYEC-MPL-00001
10 Automation Plan M-BAC-000000-GI00-MPL-00001
11 Issue of Design Documentation for M-BCW-000000-GE00-PRO-000007
Construction Procedure
12 Engineering Progress Reporting Procedure M-BAC-000000-GE00-PRO-000002
13 Consortium RAM Plan M-BAC-000000-GE00-MPL-000003
14 Consortium System Validation Plan M-BAC-000000-GE00-MPL-00001
15 Consortium Configuration Control Plan M-BAC-000000-GECM-MPL-000001
16 Subcontracts and Service Requisition M-BCW-000000-GE00-PRO-000001
Procedure
17 Material Requisitions and Purchase M-BCW-000000-GE00-PRO-000002
Memorandums Procedure

5 INTRODUCTION
5.1 General Project Information

The Riyadh Metro Project comprises six Metro lines in the city of Riyadh, KSA, which form
the backbone of the future Riyadh public transport network. The Project will be
complemented by a comprehensive bus network that will be implemented by the ADA in
parallel to the Metro Project. The 6 metro lines are summarized below:
A north-south line (Line 1 / Blue Line) along Olaya-King Faisal-Batha Corridor.
An east-west line (Line 2 / Red Line) along King Abdullah Road.
An east-west line (Line 3 / Orange Line) along Al Madinah Al Munnawwarah and Prince
Saadin Abdulrahman Al Awal Roads.
An airport line (Line 4 / Yellow Line) between King Abdullah Financial District and King
Khaled International Airport.
A north-south line (Line 5 / Green Line) along King Abdulaziz Street.
A half-circular line (Line 6 / Purple Line) along Abdulrahman Bin Ouf and Sheik Hassan
Bin Ali Streets
The Project is divided into three Packages, as follows:

Package 1: Lines 1 and 2.
Package 2: Line 3.
Package 3: Lines 4, 5 and 6.
The BACS Consortium will deliver Package 1.
Package 1 will include the transit system, stations, accommodating structures, park and ride
facilities, bus interchanges, depots and Operation Control Center (OCC) for Lines 1 and 2.
The King Abdullah Financial District and Olaya Transportation Center transfer stations are
included within the BACS scope. The Package 1 scope also includes the activities required
to allow the smooth transfer of the Metro lines to the Employee r and the start of
commercial operation.
5.2 Contractual Basis

This plan forms a part of the Consortium Project Management Plan as stated in the
Employer Requirements Volume 2.1, Section 2.1.

5.3 Design Scope
The DMP applies to the design phase of the project and to the design activities required to
support construction, installation and commissioning for the Package 1 works. The DMP is
applicable to all entities undertaking design activities including the BACS Consortium
partners and their sub-contractors.
The DMP also addresses the verification and validation of the end-product design that must
ultimately meet the performance and other technical specification requirements of the
relevant elementary systems.
5.4 Civil Works JV Infrastructure Design Packaging and Execution

The Civil Works Joint Venture (CWJV) consisting of Bechtel, Almabani and Consolidated
Construction Company (CCC) will undertake the civils and mechanical/electrical design
including traffic diversions and utilities.
5.4.1 CWJV Engineering Hub

To ensure the integrity of the initial scheme design a CWJV Engineering Hub has been
created to:
Produce and gain approval from the Engineer for the Concept Designs
Prepare design packages for issue to the design centres referenced in Table 1 below
Produce a line-wide design basis to ensure consistency across the packages
Generate and maintain consistent line wide technical strategies for life safety related
items including evacuation strategy and tunnel ventilation strategy
Ensure general consistency in design approach across the packages including the
definition and coordination of common design items that apply to a number of
packages
Maintain the standards and specifications baseline

5.4.2 CWJV Detailed Design Packaging
The CWJV detailed design will be delivered in eleven major packages as shown in Table 1
below.
Design Description Designer

Package
1 Track Alignment, Depots and At Grade Track Bechtel
2 Bored Tunnels, Adits and Escape Shafts Aecom
3 Cut & Cover Tunnels Bechtel
4 Enabling Works & Olaya Batha Corridor Beautification Aecom
5 Viaducts and Elevated Stations Aecom
6 Deep Stations (1F2,1F8,1A2, 2B4, 1F4) Arup
7 Deep Stations Aecom
(1B1,1B2,1B4,1C1,1C2,1C3,1C4,1D2,1D5,1E2,1F5)
8 Shallow/At Grade Stations Bechtel
9 Park & Ride Bechtel
10 KAFD Station Zaha Hadid/
Buro Happold
11 Olaya Station Gerber Architekten/
Buro Happold
Table 1 Civil Works JV Design Package Breakdown

5.5 Transit Systems Design Packaging and Execution
The Transit Systems design is being delivered by Siemens as a Consortium partner.
Siemens is responsible for the design, delivery, installation, integration and commissioning
of the Transit systems for the two lines. The Siemens product lines are utilised to provide
the transit systems as follows:
Item Description
1
Signalling
2
Rolling Stock
3
Communications infrastructure
4
Traction and high voltage power supplies
5
Platform Screen Doors
6
Depot equipment
7
SCADA system
5.6 Design Organization

The BACS design organization is as shown in Figure 1 below.
5.6.1 Consortium Technical Management Team

The Consortium Technical Management Team (CTMT) is accountable to ensure that the
Employers requirements are met. The CTMT has the following responsibilities:
Technical governance and leadership defines the processes and procedures to be
adopted to ensure the Employer technical requirements are met through the application
of system engineering practices for verification, validation, testing, and commissioning
and safety case justifications to allow the metro system to be brought into service.
Acts as the independent receiver of technical assurance and safety related
documentation and ensures that the technical submissions are fully compliant to the
Employers requirements.
Manages the technical assurance submissions process to the Employer.
Conducts audits and surveillance activities to ensure that that the project processes,
procedures and plans are properly implemented.
Interface Management - the interfaces between the line-wide systems and the Civils
infrastructure will be managed in accordance with the Consortium Interface
Management Plan to ensure that the design interfaces are effectively coordinated and
documented through the project life-cycle enabling the commissioning of the end to end
Railway.

5.6.2 Transit Systems Integration
Led by the Transit Systems Integration Manager (TSIM), the Transit Systems Integration
Engineering team will manage the delivery of the Transit Systems elements from the Transit
Systems sub-systems to produce an integrated solution. In doing so, the TSIM will
coordinate the design with the CWIM to ensure that the final design is fully integrated with
the civil works.
5.6.3 Civil Works Engineering Delivery

CWJV Engineering delivery is coordinated by the CWJV Engineering Hub led by the CWJV
Engineering Director. The Engineering Hub will coordinate the Scheme Designs and
engineering requirements with the CWJV Engineering Managerss. The Civil Works JV
Engineering Managers (CWEM) will interface directly with the Design Package Managers in
the various design centres as detailed in Table 1 above. The CWEMs will review the design
submissions and approve the design package via the Design Assurance Gates process
described within this document.
5.6.4 Civil Works Integration

Led by the Civil Works JV Integration Manager (CWIM) the CWJV Integration Engineering
team will ensure that the CWJV design packages are fully integrated between design
packages. The CWIM will coordinate the civil works design with the TSIM to ensure that the
civil works design is fully integrated with the Transit Systems.

Figure 1 BACS Design Organization Chart

6 RESPONSIBILITIES
The roles and responsibilities of the design organization will be detailed in the projects Job
Descriptions and are summarised below:
6.1 Design Authority

The design authority for each design package rests with the Designer. The Designer is
responsible for the technical assurance for their design package scope of works. The Transit
Systems/CWJV Integration teams will be responsible for the validation of the design to ensure
that it meets the Employers Requirements and the integration of the final design.
6.2 Key Roles
6.2.1 CWJV Engineering Director

Head of the CWJV Engineering organisation.
Has responsibility for CWJV engineering design delivery and execution in accordance with
the program ensuring that the Employers requirements are met.
6.2.2 Consortium Systems Integration Manager

Leads the Consortium Technical Management Team
Provides technical guidance and governance to the project
Is responsible to ensure that the Employers requirements are met to produce an
integrated railway.
Is responsible to ensure that all Consortium plans and procedures are complied with by
the delivery teams
Carries out surveillance of project activities
6.2.3 Consortium Systems Integration Manager Transit Systems

Provides technical guidance and governance for Consortium matters to the Transit
Systems teams
Conducts TS surveillance activities on the behalf of the CSIM
Manages the team of Systems specialists including the Consortium Operations Manager,
Training Manager, Requirements Manager, Testing and Commissioning Manager, RAM
Manager, Earthing & Bonding/EMC Engineer and System Safety Manager.
Interfaces with the Consortium Systems Integration Manager Civils Infrastructure to
ensure that the Consortium requirements, processes and procedures are fully
implemented in the CWJV and meets the Employers requirements.

6.2.4 Consortium Systems Integration Manager Civils Infrastructure
Provides technical guidance and governance for Consortium matters to the CWJV design
teams
Conducts CWJV surveillance activities on the behalf of the CSIM
Manages the Interface Management team and is responsible to ensure that the CWJV
design packages are properly integrated through effective Interface Management
Interfaces with the Consortium Integration Manager Civil Infrastructure to ensure that the
Consortium requirements, processes and procedures are fully implemented in the CWJV
and meets the Employers requirements.
6.2.5 Consortium Design Manager

Manages the overall design process and deliverables.
Defines and implements design management and assurance processes.
Maintains the BACS Consortium Standards Baseline.
Manages the Design Assurance Gates process.
6.2.6 Transit Systems Integration Manager
Responsible for the Engineering of the Transit Systems scope of work to produce systems
that meet the Employers Requirements.
Acts as the Client and receiver of assurance from the Transit Systems sub-systems.
Monitors performance, progress and compliance of the design outputs.
Resolve any issues and design constraints as they arise.
Interfaces directly with the Transit Systems Product Line Integration Engineering
Managers.
6.2.7 CWJV Integration Manager
Ensures that the requirements, processes and procedures and plans issued by the
Consortium Technical Management team are fully implemented.
Interfacing with the TSIM, ensures that the Civil Works designs are fully integrated with
the Transit System design.
Ensures that the CWJV designs are fully integrated across the design packages.
Ensures that CWJV design submissions are fully coordinated with the Transit Systems
assurance deliverables.

6.2.8 CWJV Engineering Managers
Leads the CWJV Engineering Delivery team for his design package.
Acts as the CWJV Client and receiver of assurance from the relevant DPMs .
Reviews and approves design submissions in accordance with the Design Assurance
Gates process, engaging with the Consortium Technical Management team to ensure that
all Employers requirements are met.
Monitors performance, progress and compliance of the design outputs.
Ensures that design interfaces for the package are properly managed and coordinated.
Resolve any issues and design constraints as they arise.
Interface directly with the DPMs.
Coordinates and Chairs the Design Assurance Gate Reviews.
7 RMP DESIGN PROCESS
The BACS Consortium had adopted the systems engineering methodology as the basis for the
management of the design process. ISO/IEC 15288 provides additional information related to
the Systems Engineering process.
This process establishes a systematic methodology for fully identifying Employers

requirements during the concept stage and achieving those with the final design. The top level
process adopted by the BACS Consortium is shown in Figure 2 below.

Figure 2 BACS Design Process

7.1 Design Inputs
The design inputs consist of:
Requirements as stated in the Riyadh Metro Project Employers Requirements Volumes
2.1 to 2.5 inclusive. The Employers requirements will be translated into a detailed set of
requirements for allocation to individual design entities. See Consortium Requirements
Management Plan for a more detailed description for the management of requirements.
BACS consortium Standards Baseline, Plans, Procedures, Processes.
Statutory laws and regulations.
Interface Requirements both internally between CWJV and Transit Systems and externally
with the other Metro Line packages and external stakeholders
The set of design inputs will form the baseline for the verification and validation of design
output at the various development stages to determine whether the final design meets the
Employers requirements.
7.1.1 Engineering Safety Management

The Consortium Engineering Safety Manager is responsible for the preparation of the
engineering documentation that demonstrates to the Employer and the Railway Regulator that
the railway can be safely operated and maintained.
The Designers will be required to provide evidence that forms a part of the overall safety case
for their respective work packages. The engineering safety related activities will be detailed in
the Consortium Engineering Safety Management Plan [1].
7.1.2 Standards Management

The Consortium will define and maintain a Standards Baseline that meets the Employers
requirements.
If the Designer finds that a concession or derogation is needed, a request for departure will be
submitted to the BACS Consortium Standards Manager who is part of the Consortium
Compliance Team. This should be submitted at least two months prior to the 60% gate. The
request for departure will include at least the following information:
Standard from which departure is required and owner.
Details of clauses from which departure is required.
Justification for departure.
Proposed alternative arrangements.
Risk assessment demonstrating that the alternative arrangements will control risks to be
As Low As Reasonably Practicable (ALARP).

7.1.3 Requirements Management
The Employers Requirements will be maintained in a DOORS database. The DOORS
database will be used for Requirements Management, Verification and Validation and
traceability elements.
Requirements will be allocated to the Designer as agreed between the Consortium

Requirements Manager and the Designers DPM.
The Designer will be responsible for the management of requirements, verification and
validation (as appropriate) allocated to them within the DOORS database.
The Requirements Management process is described in the Consortium Requirements

Management Plan [4]
7.1.4 Reliability, Availability and Maintainability (RAM)

The works are to be designed to meet high performance criteria. To this end Reliability,
Availability, Maintainability (RAM) requirements have been established in the Employers
Requirements. The Employers Requirements related to RAM are detailed in the Consortium
RAM Plan [14].
The Designer will produce a RAM Management Plan that describes how all relevant RAM
requirements will be met. The RAM Management Plan will describe the following as a
minimum:
Organisation of RAM team, including the position within the Designers organisation for the
works;
Management of RAM-related interfaces with Others;
Identified RAM requirements (including interfaces);
Planned RAM assessments to demonstrate that the system RAM requirements are met by
the design;
RAM methods to be used;
Management of Sub-Designers RAM requirements;
Verification and validation of assessments, including data;
Validation of RAM requirements during manufacture, installation, commissioning and
maintenance;
Record keeping of RAM assessments;
List of deliverables, including interim items listed within this document;
High level schedule for deliverables.
The Designer will review and update the RAM Management Plan as necessary as the works
progress to ensure it reflects the current status of the works. The revised plan will be
submitted to the CWEM/TSIM for acceptance.

7.1.5 Verification and Validation
Verification and Validation activities are detailed in the Consortium Validation Plan [15]. The
Designers are responsible for producing verification evidence during the design development
phase and for developing the validation methodology to be applied during the implementation
phase.
The Consortium Technical Management Team will review and accept this evidence as part of
the assurance process. This includes verification and validation of secondary requirements.
Validation is intended to ensure a product, service, or system results in a product, service, or

system that meets the operational needs of the user. Validation activities will be described in
detail in the Consortium Testing and Commissioning Plan.
7.1.6 EMC/EMI
The Consortium EMC/Earthing and Bonding specialist will prepare the Consortium EMC
Management Plan that outlines the Consortium EMC and Earthing & Bonding process and
strategy [10] The Designer will produce an EMC Control Plan and Earthing & Bonding Strategy
that describes how the requirements of the Consortium EMC and Earthing & Bonding Strategy
will be met and will form an inherent part of the design and technical assurance process. The
Plan will be submitted to the CWEM/TSIM for acceptance.
7.2 Design Development Stages
7.2.1 General
The design development stages have been specified to meet the Employers Requirements for
review and comment as described below. The designs will be developed from the current
Preliminary level of design development to be fully detailed designs fit for construction. The
purpose of the Red Diamond design development stage is to evaluate the preliminary designs
to incorporate scope discussions and option selections and to enable the formation of a
baseline prior to the commencement of detailed design activities following the completion of
Red Diamond.
Red Diamond addresses the Requirements for the supply of General Arrangement Drawings
as specified in Volume 2.1 Section 9.2 General Arrangement Drawings.
Due to the nature and time phasing of the works it will be necessary to release the design in a
number of discrete packages to suit the construction schedule. All packages will be subject to
the design development requirements as stated in this plan.
7.2.2 Red Diamond
The design has been developed to show:

Design Basis - sufficient detail to convey design intent with the design assumptions clearly
stated so that they can be confirmed and fixed by the Employer.
Line-wide alignment baseline.

Space proofing fixed with layout and general arrangement drawings available.
Civils and Structural BIM Models developed with Architectural, Mechanical & Electrical
(MEP) details shown in concept only.
Initial calculations available to confirm integrity of intent.
Lines 1&2 Line-wide interface Matrix available detailing Systems to Stations/Infrastructure
interfaces.
Rolling Stock and Transit System General Arrangement Drawings and characteristics
7.2.3 60% Design Gate Review

Design has been developed to about 60% completion coinciding with:
Interface agreements in place between all Designers
All ground survey and utilities data available
Draft calculations and specifications available
Alignment with Operations Concepts and Maintenance Strategy confirmed
Long lead-time items identified and procurement plans in place
All required drawings at Preliminary issue
All Requirements verified as compliant
Full designer risk assessments completed
7.2.4 90% Draft Final Gate Review

Design has been developed to about 90% completion coinciding with:
BIM Model progressed so that clash detection of MEP services have been detected and
resolved
All discipline design drawings complete
Interface control documents signed off to show that the design package is fully
coordinated and integrated with other interfacing design packages
Accurate quantities available
Member sizes confirmed and construction sequences agreed
Calculations complete and Specifications available
Able to show that identified risks have been reduced or mitigated
Alignment with Operations Concepts and Maintenance Strategy confirmed
7.2.5 100% Final Design Gate Review

Design has been developed to 100% completion:
Final design drawings complete including schedules and detailing
Certification complete
Approvals/consents obtained from all relevant authorities
All calculations and Specifications complete
BIM Model frozen for the information being released
Only outstanding items will be fabricator shop drawings or contractor final fixing details
Risks mitigated to ALARP status
7.2.6 Issue for Construction

Design package is ready to be issued for construction:
IFC drawings, specifications and relevant details available for construction
BIM Model
All design and technical assurance documentation signed off and approved by the
Employer
8 DESIGN MANAGEMENT PROCESSES AND PROCEDURES
8.1 Design Management Plan

All designers will be required to produce and submit a Design Management Plan to the CWEM
or the TSIM as appropriate. The Design Management Plan will include as a minimum:
describe how the Designer will produce an integrated, assured, certified design that meets
the Employers Requirements;
describe the organization and the resources required that the Designer will establish to
manage and carry out engineering and design activities;
describe the tools that will be employed to produce the design such as simulation and
modelling;
describe the processes and procedures that are to be implemented in order to deliver a
fully compliant design by the contract specified milestone dates including:
- the process for planning and control of the design and its development;
- the process for systematic review, verification and (as appropriate) validation of design;
- where appropriate the process for assessment and mitigation of environmental impacts
and incorporation of environmental design requirements;
- the design review, verification and validation plans that are appropriate to each design
and development stage;
- design verification reporting;
- where appropriate, design validation testing plans, testing specifications and reporting;
co-ordination and integration of the design and management of internal design interfaces
(i.e. interfaces within the works) and with the systems provided by Others;

describe the management processes for interfaces with all the different organisations
involved in design and development to ensure effective communication and clear
assignment of responsibility;
provide for identification and management of third party approvals required;
include a process for the confirmation of the category of design check required for each
part of the works;
include a process for engineering safety management;
Identify the certification and records required to support the progressive assurance of the
works.
8.2 Interface Management
The Consortium Interface Management strategy and processes is as described in the

Consortium Interface Management Plan [2] Interface Management activities will be overseen
and coordinated by the Consortium Interface Manager.
The Designers will prepare an Interface Management Plan that describes how the Designer
will meet the requirements of the Consortium Interface Management Plan including how they
will manage internal and external interfaces with their design package.
The Designer will prepare a fully coordinated and integrated design for the works. Within this
activity the Designer will manage all interfaces with, and design inputs and outputs from others
and all interfacing organizations. Interfaces include the following:
Internal Interfaces between the main work packages e.g. Rolling Stock to Track.
External interfaces with other packages e.g. KAFD station with Package 3 Lines 4&6.
External interfaces with other projects e.g. Bus Project, Urban local development.
External interfaces with utility companies and local authorities including:
- Ministry of Transport (MoT)
- Riyadh Municipality
- Saudi Telecommunication Company(STC)
- Saudi Electric Company (SEC)
- Riyadh Water and Sewerage Authority
- Saline Water Conversion Corporation (SWCC)
- Mobile Operations (Mobily, Zein)
- Ministry of Defence (MODA)
- Saudi Aramco
- Interface coordination with operations and maintenance entities/functions.

The Consortium Interface Manager will:
Produce the Interface Management Plan - Interface scope, definition, process,
governance, responsibilities, templates and tools.
Produce a Master Project Interface Matrix and outline boundary definition.
Establish communications make agreements and define meeting/working protocols with
external interface organisations.
Allocate interface responsibility.
Coordinate interface definition and agreement activities.
Facilitate and record interface agreements and related evidence.
Conduct interface progress reviews as a part of the design management process.
The Designer will:
Review and agree the interface scope allocation with the Consortium Interface Manager
Take ownership of interfaces assigned to them and act as the interfacing partner for those
owned by other which impact them
Prepare technical packages, plans and information to meet external interface
requirements
Identify the requirements of each identified interface in conjunction with interfacing groups
and organizations mentioned above, and,
Provide suitable designs for the interfaces within its detailed design.
8.3 Design Progress Reporting

Design progress and costs will generally be reported on a monthly basis. The DPMs (Product
Line Product Managers in the case of Transit Systems) will report progress to the TSIM and
CWEM for Systems delivery and Civils works respectively.
The performance of design progress will be measured using Engineering Progress Reporting
(EPR). The EPR, produced and updated by the DPMs/Product Line Managers, identifies and
tracks progress against engineering deliverables and activities to provide an overall
percentage complete using earned value techniques.
Design progress will also be tracked against the BIM Model and deliverables.
For details on progress reporting please refer to EPR Procedure [13].
8.4 Engineering Deliverables List (EDL)

All deliverables (specifications, documents, calculations, BIM Model, drawings etc.) produced
by the Designer (from now up to project completion and handover) will be recorded in an
Engineering Deliverables List (EDL).

It is intended that the EDL should be a complete design register to show the status of design
deliverables and drawings period by period through the project and act as a record for the
deliverables for all Design Assurance Gate Reviews.
The Consortium Document Management function will produce a template for this purpose.
8.5 Design Reviews

It will be the responsibility of the Designer to self-certify their design. The Designer will
perform systematic reviews of its design in accordance with the Designers Design
Management Plan. These requirements will be applied to the Designers Sub-Designers,
suppliers or specialist designers (where relevant) and assured by checking and approval by
the Designer. The responsibility for design certification will be retained by the Designer.
All design documents will be signed by the Designers competent persons at each of the three
quality stages - Prepare, Check and Approve.
Authorisation levels are defined as:
Prepared by a competent person who produces the design document, checking their
own work complies with codes and standards governing that work.
Checked by a competent person able to undertake a formal detailed check of design
methods, codes and standards, deliverables, calculations, drawings and specifications
produced by another member of the CSJV Design Team. This role is undertaken by a
competent person of the same discipline, not the Preparer, but can be a member of the
same team.
Approved by a competent person able to undertake a review of the design output after
detail checking has taken place to validate that the design is consistent with the project
requirements. Although integration is considered at every stage this level of sign-off is
specifically intended as the final confirmation that inter disciplinary checks have been
carried out.
The Designers will invite the CWEM/TSIM and Project Managers as appropriate to attend all
design reviews together with other interface parties and independent assessors where
necessary. These design reviews will:
be undertaken by appropriately qualified and competent representatives of the functions
concerned with the design and development stages being reviewed;
Evaluate the ability of the design to meet the contract requirements.
Identify any problems and propose necessary actions.
incorporate interface and integration requirements; and
Record the results of the review and verification activities and document any necessary
actions to be taken.

8.6 Acceptance of Design
The CWEM/TSIM will accept the design through reviews of the design deliverables either as a
precursor to the Design Assurance Gate Reviews (see section 8.6.6 below) for documents
requiring approval from the Employer, or for project documents that do not require approval
from the Employer.
The Designers documentation will be produced in Projectwise and the approval of documents
by the Designer will be registered in Projectwise using the Projectwise work flow features.
Approved documents will be transmitted to BACS and the documents will be approved by the
CWEM/TSIM using the work flow features of Aconex.
Prior to design submission to the Employer BACS will provide Gate Review Reports and Gate
Certificates indicating evidence of the approval of the package by BACS. Evidence of design
acceptance will be maintained in Aconex.
The approvals process will be detailed in the Engineering Design Assurance Gates Procedure
[9].
8.6.1 Safety in Design

Safety of assets can be mostly influenced at their design phase and designing for safety
therefore is an important consideration in any design. Engineering Safety Management
requirements will be detailed within the Consortium Engineering Safety Management Plan [1]
where the general safety and rail safety legislation, environmental legislation and applicable
national and international standards to be applied by the Designer are detailed.
Designing for safety requires risks to be identified, assessed and controlled. In controlling risk,
whereby unacceptable risks are eliminated and unavoidable risks are either managed to a
level that the residual risk is either negligible or is reduced to as low as reasonably practicable
(ALARP).
The design safety management process is an iterative process conducted at each stage of the
design development. It is an integral part of the Reliability, Availability, Maintenance and
Safety (RAMS) analysis that is carried out for design.
All Designers carrying out design activities will be required to comply with the appropriate
safety codes and legislation related to their design scope as detailed in the RMP Standards
Baseline. It will be the responsibility of the Designers DPM to:
Provide all necessary liaison and coordination with Consortium Engineering Safety
Management and Health and Safety representatives for the purposes of safety in design.
Ensure the appropriate design reviews are performed and design certification is achieved,
and that adequate information on health and safety in design is provided with all supplied
information.
Review and approve design submissions.
Oversee preparation and updating of Designers Risk Register.
The Designer initially will ensure that designs prepared working down hierarchy of risk controls
will seek to eliminate, substitute or reduce risk in designs they are preparing. These designs
will consider construction, operational, maintenance and demolition or de-commissioning risks.
As part of the management of risks the design process will undertake the compilation of an
access strategy, plant replacement strategy and ensuring adequate space in plant rooms for
replacing parts. Places of work will be designed to comply with statutory regulations as
detailed in the RMP Standards Baseline.
8.6.1.1 Risk Register Workshops

Designer will take part in Risk Register workshops as required by the Consortium Technical
Management team. The Designer will utilize the Consortium Risk Management process to
ensure risks are captured and, where possible, mitigated before the subsequent stages in the
process. Even if the risk is closed out, the information will be captured for future reference.
Any residual risks will be tracked to ensure that actions detailed in the Risk Register are
completed; evidence will be provided to demonstrate compliance. Each Element/Discipline
Design Leader will take ownership for their respective section of the Risk Register.
The process for managing risk is based on the following hierarchy:

Eliminating hazards.
Reducing risks from remaining hazards.
Communication of residual risks with notes on drawings.
The Risk Registers are to be used throughout the design, construction and T&C/Handover
phases for:
Design drawings.
Health, Safety and Environment (HSE) Information/notes - where the Designer considers
the design to have a residual risk that a competent contractor may not be familiar with, this
risk should be highlighted on the drawing by the use of the HSE box system.
The risk will be reported and communicated under the following headings:
Construction Activities Risks.
Railway Operational Risks.
Railway Maintenance Risks- including cleaning.
Demolition or De-commissioning Risks.
The Designers will develop a Red, Amber & Green list (RAG list) for on-going reference on
which elements, materials or processes to eliminate or avoid and what to encourage in the
design.
Based on best practice the design team will identify design elements, materials and processes
which are either to be avoided because they are judged to represent significant risk to
construction personnel, facilities users and/or the environment or to be preferred because they
represent a reduction in such risks.
8.6.1.2 Red List Items

Red List items are hazardous elements materials or processes, which are effectively
prohibited and should be eliminated from the project excepting only where no alternative can
be found. If any Red List item is to be employed, it requires formal justification within the
design documentation.

8.6.1.3 Amber List items
If any item on the Amber List is to be employed, it requires information within the design
documentation on its minimisation and will require advice and guidance to be provided as part
of the design for the safe execution of that design.
8.6.1.4 Green List Items

Green list items are elements, materials and processes which are preferred because they
represent significant risk reduction.
8.6.2 Design Checks
8.6.2.1 Internal Design Checks

Prior to any submission of technical documentation (or data), the DPM (if he is not the author
of the document) will review the document and issue it for internal review to the checker
(Design Manager/Coordinator) and approver (Engineering Manager or other), and any other
design team member (ESM, N&V Specialist, RAM Manager, etc.) where appropriate.
The Design Leader will incorporate comments and changes and record these in a document
review sheet in accordance with the Designers processes and procedures, before formal
issue. All design documentation and drawings will be fully approved prior to submission.
8.6.2.2 Constructability Review

Ensuring the early input of construction methodology guidance and comments into the design
process is important to ensure that the design is optimised for safe and efficient construction
and to highlight any specific issues that will be required to be taken into account in the final
design. Construction Managers and Engineers from the Civil Works JV will be assigned to
each design team to ensure that this construction input is provided through the design
lifecycle. The DPMs will be responsible for ensuring that constructability reviews are
conducted as necessary through the design process.
8.6.2.3 Value Engineering

The Designer will include in its Design Management Plan a process for the identification and
development of value engineering opportunities in the design. Throughout the preparation of
the design, the Designer will advise the CWEM/TSIM of any identified value engineering
opportunities.
8.6.3 Independent Design Checks

BACS has adopted the principal of independent design checking for complex civil structures
originally developed in the UK as an effective method of engineering risk management. This is
to ensure that the Civils design will produce a structure where the risk of failure is assessed to
be as low as reasonably practicable (ALARP). Originally developed for bridge structures the
approach has also been applied to tunnelling and underground structures. The process now
addresses:

Highly demanding or large tunnels and underground structures, caverns and shafts etc.
Innovative, complex or unusual structures.
Highly demanding structures which lead to long span or highly skewed bridges.
Very large structures with high public occupancy.
The categories of design check adopted by BACS RMP follow the UK classification and are
defined as follows:
Category 0 - structures are small minor constructions and do not require formal technical
approval but should nevertheless be independently checked within the design team.
Category I - structures include bridges with spans less than 20m and other relatively small
constructions. These require formal technical approval and an independent check of the
design by an engineer who may be part of the design team.
Category II - covers all structures which do not fall into any of the other categories. Their
design will be checked by an engineer or team of engineers who must be independent of
the design team but may be from within the designers own organization.
Category III - covers complex structures requiring relatively sophisticated analysis or those
with spans greater than 50m, high skew angles, high redundancy, suspension systems,
steel orthotropic decks, moving bridges, large underground caverns and tunnels etc.
These require an independent design check by an engineer or team of engineers who are
independent of the designers organization. It is particularly important in this case that the
checker possess the necessary expertise and experience suited to the type of structure in
question.
The Designer will identify the requirement for independent design check (Category II or III) and
appoint a checker as appropriate will be decided by the Designer identified during the course
of their design risk management process. A Category III Design Check Log will be maintained
by the BACS Consortium Design Manager.
8.6.3.1 Category III Check

A Cat III check involves taking the final detail design drawings and functional specification,
developing independent load cases, calculations and analyses. By utilising a totally
independent party to carry out a check provides confidence that the design is suitable for its
intended purpose, and also viable for manufacture.
The checkers scope includes the check of the effects of the proposed construction method
and sequence, and often also a review of the durability and maintenance issues. On
completion of the Category III check, the checker will issue a Cat III Check Certificate.
8.6.4 Independent Checking Engineer (ICE)

Not to be confused with the Independent Category II and Category III checks carried out by
the Designer described in 8.6.3 above, the Employers Requirements call for an Independent
Checking Engineer (ICE) to be appointed. The ICE will be required to maintain technical
oversight of the design and support to construction activities on the project through the Design
and Build stages for both Transit Systems and Civils works to give confidence to the
Consortium Engineering Director and the Employer that:
The designs are safe with risks identified at an early stage and mitigated during the
design.
The design is compliant to contractual requirements and obligations.
The design teams have applied state of the art applicable codes and standards defined in
the baseline.
Verify that independent Design Checks on Civil Structures have been commissioned by
the CWJV designers as appropriate.
Interfaces between design packages are clearly documented and coordinated with no
scope gaps and are effectively managed.
The design is properly implemented and controlled during the Works.
The design is optimised for safe, timely and efficient construction.
Representatives of the ICE will be located with the Designers design teams and the Designer
will be required to work with the ICE to enable them to discharge their duties. The ICE will be
appointed by the BACS Consortium.
The ICE will provide a monthly report to BACS copied to the Employer highlighting any
discrepancies and non-compliances from defined requirements, processes and procedures.
The ICE will also pro-actively report any identified non-compliance to BACS for corrective
action.
8.6.5 Independent Safety Assessor (ISA)

An ISA has been appointed by BACS to meet the Employers Requirements Volume 2.1
Section 3.2.3. The ISA will conduct a safety assessment of the design, installation,
commissioning and test running of the railway, separate and independent from any system
design, development or operational personnel. They will verify that the safety requirements for
the system are appropriate and adequate for the planned application and that the system
satisfies those safety requirements. As a part of this process, the ISA will review design
submissions as a part of the Design Assurance Gate Review process.
The ISA will conduct safety audits and will submit safety reports to the Employer so that the
Authority in charge of authorising the commercial revenue service of the Metro System is able
to grant a Permit to Operate in due time.
These activities will be carried out in accordance with the Consortium Engineering Safety
Management Plan [1].
8.6.6 Design Gate Reviews

The Design Gate Review process is described within the Engineering Assurance Design
Gates Procedure [9] and is to be used by the Designer to:
Provide assurance that the design package will meet its requirements and be fit for
purpose; and,
Provide the design package of documents, drawings and models etc. that will form the
design submission to Engineer for review and approval.
Specific emphasis will be given to the proving of integration with interfacing systems both
internally within the design package and externally with other designers.
The Design Gate Review will take the form of a presentation by the DPM to the CWJV and TS
delivery teams, Transit Systems Integration Team, Consortium Technical Management team
and other specialists as appropriate.
The objective of the Design Gate Review presentation is for the Designer to present a
convincing argument to the CWEM/TSIM that the design is at the specified maturity. The
presentation will be specifically required to address the following key aspects:
That the design conforms to the specified systems related performance criteria and
Employers requirements including:
- RAM
- Engineering Safety Management
- Requirements Management
- EMC
- Earthing and Bonding
- Operations Concepts
- Testing and Commissioning activities as applicable to the design phase
That a consistent, quality controlled approach is adopted;
That the design is integrated with other parts of the contract and that they fit within the
requirements of the Works Information;
Confirming the current status of the design check process;
That specific deviations or departures from the Standards and design inputs are identified;
justified and addressed in accordance with the process;
reporting on the approval status of design changes;
reporting on the status of Configuration Items;
confirming that the proposed design provides an economic solution;
confirming whether any further independent reviews are required;
reporting on the status of document reviews by the CWEM/TSIM
identifying the status of applicable Consents and Acceptance /Approvals required from
Others throughout the design and construction process;
confirming compliance with relevant standards (BACS RMP Standards Baseline) including
standards applicable at interfaces;
identifying safety hazards, their control, and the degree of residual risk to be managed;
identifying all tests or demonstrations that are required for validation of the works of any
other relevant information and data such as progress on interface development and

design, further information on drawing and document status, areas of concern and
difficulty to the design;
Any other relevant information and data such as:
- Progress on interface development and design;
- Drawing and document status; and
- Areas of concern/difficulty (risk) to the design.
8.6.7 Design Gate Review Close-out

If the Design Gate Review is successful, the CWEM/TSIM will indicate that the review is
successful at the meeting and provide a complete Gate documentation package, including
Gate Review Report, Gate Certificate and Engineering Deliverables List (a list of documents
reviewed during that specific Gate), signed and stamped on each page by the CWEM/TSIM, to
be submitted through Aconex to BACS DCC for issuance to Engineer..
Any conditions will be specified on the Gate Pass Certificate. The CWJV Engineering
Manager/Transit Systems Integration Manager will manage the closure of any conditions in
conjunction with the DPMs.
If the Gate Review is not successful, then the CWEM/TSIM will agree a re-work programme
with the DPM and agree a re-submission program to address any issues.
8.7 Design Tools

The engineering team will deploy various tools in preparing and issuing the design. In addition,
the Designers will state in their Design Management Plans any additional/specialist tools to be
used for their aspect of the design over and above the standard tools deployed by the Project.
The Project will deploy Projectwise as the engineering environment for the production of
engineering documentation, drawings and models. All submitted documentation will be hosted
in ACONEX as the electronic Database Management System (EDMS) to retain, issue and
control project records and submissions. All project documentation is required to be stored and
controlled within the EDMS. Documentation control requirements will be as stated in the RMP
Documentation Plan. Modelling, drawing and design automation and control shall be stated in
the RMP BIM Execution Plan [8]. The principle software tools to be deployed are as follows:
ACONEX - EDMS.
Projectwise as the engineering Common Data Environment (CDE), i.e. the engineering
production database for engineering models, drawings, specifications, calculations, reports
etc.
Microstation v8.1 and AutoCAD 2014 for drafting.
REVIT Architectural, Structural and MEP.
Bentley RailTrack.
Autodesk Civil3D for civil site works, highways and utilities.
DOORS for requirement management and traceability.
The information management architecture is as shown in Figure 3 below:

Figure 3 Information Management Architecture

8.8 Configuration and Design Change Control
8.8.1 Configuration Baseline

Configuration control is based on the guidelines of standard ISO 10007. The Project
requirements are detailed in the Consortium Configuration Control Plan [16]. The Designers
and document producers are responsible to ensure that configuration management
procedures are implemented to ensure that the requirements of the Consortium Configuration
Control Plan are complied with and that configuration and change control is maintained.
The Design of each system will be based on a controlled configuration baseline of documents
including:
Employer Requirements,
Consortium Standards Baseline,
Documents and drawings produced,
Documents or requirements received by other contracts through the interface activity,
Models,
Field documents and survey reports.
Only the documents and models included in the configuration baseline will be used as input
data by the Designers.
The applicable configuration baseline will be managed by the Designers including the
following:
Documents and drawings produced and submitted on Aconex for CWJV/Transit Systems
acceptance.
All the interface documentation (Interface Control Documents and supporting data)
submitted on Aconex and signed by Designer representatives.
All the shared models on ProjectWise.
All the field documents and survey reports submitted on Aconex.
8.8.2 Design Change Control

A change control process will be applied on all documentation involving the design. A Change
Control process will be applied as follows:
Identification of change.
Evaluation of the consequences of the change.
Agree to progress the change.
Implementation of the change and verification (if approved).

All new changes identified in the design documentation or within external documentation
(e.g. interfacing requirements) will be categorized by the DPM in terms of complexity,
resources and scheduling. The change will then be evaluated for its consequences and a clear
report will be issued to the CWEM/TSIM concerning:
Technical merits of the proposed change;
Risks associated with the change;
Potential impact on contract, schedule and costs (if design costs);
The Consortium Management Team will agree whether to pursue or reject the change;
If the change is to be pursued a review will take place. Attendees at the reviews(s) for the
proposed design changes will vary depending on the nature of the change:
- Design Leaders
- Interface Manager
- Project Management representative
- For safety-related or safety-critical changes, the Consortium Engineering Safety
Manager
- For changes affecting testing or commissioning activities, a T&C representative
- The Quality Manager
- Other personnel as appropriate.
The implementation of a change will be accompanied by an action plan listing all impacted
documents to be reviewed. The action plan will be followed until all documents have been
reviewed accordingly to the change and re-submitted.
8.9 Certification and Records

The Designer will certify that its design, complies with the Employers Requirements. The
Designer will issue all certificates to the CWEM/TSIM for review and acceptance in
accordance with the EMDL. The certification requirements and process are detailed within the
Consortium Assurance Records and Certification Procedure.
In particular the Designer will provide the following Design Certification:

Design Certificates per System to certify compliance with the design scope
Design Gate Review submissions at Red Diamond, 60%, 90% and 100% design stages;
and
Design Check and Independent Design Check Certificates where required.
8.9.1 Design check records

Design checks will be recorded through the signatures (Prepared, Checked, and Approved) in
the front page of each document in accordance with the Designers quality control procedures
and on drawing title blocks in accordance with the RMP BIM Execution Plan [8]

8.9.2 Design Gate Review Acceptance Certificate
When a Design Gate Review has been successfully passed as described in section 8.6.6
above, the Consortium Design Manager will issue a Design Gate Review Acceptance
Certificate to confirm that it has been conducted and all requirements have been met and
conditions closed out.
8.9.3 Requirements Compliance Matrix

A requirements compliance matrix as referenced within the Consortium Requirements
Management Plan [4] will be produced for each system providing traceability from Employers
requirements to design documentation and evidence that requirements have been met for the
design stage.
8.9.4 Design Completion Certification

A final Design Completion Certificate signed by the DPM will be provided to CWEM/TSIM on
completion of Issue for Construction (IFC) drawings and associated documentation. The
certificate will be accompanied by a final EMDL.
8.9.5 Issue for Construction Documentation

All design packages which have been produced to support Construction are required to to be
released in accordance with the Consortium Issue of Design Documentation for Construction
Procedure [12].
This procedure defines the process to authorise the release of design documentation for the
issuance of design documentation (IFC) by the Designer via Engineering Manager, for the
permanent works design where the design has passed Gate 3 and has the status of IFC in
Aconex.
On occasion there will be a requirement to release design packages prior to IFC milestones to
support manufacturing of long lead time items etc. Although these packages are not at IFC
there is a requirement to manage the release of these packages in a controlled way. The
procedure for the issue of design packages to procurement which are not IFC shall be
managed in accordance with the Subcontracts and Service Requisition Procedure M-BCW-
000000-GE00-PRO-000001[16] and Material Requisitions and Purchase Memorandums
Procedure M-BCW-000000-GE00-PRO-000002 [17].
8.10 Design Activities during Installation and Test & Commissioning

Phases
During the Construction and T&C phases, the DPMs will support the construction phase. Once
finalized and approved at the 100% design stage the design documentation will be released
for construction with IFC status by the DPM to the Civil works JV Construction Manager.
For the Line-wide systems the TSIM will authorize the release of IFC documentation for
procurement and production.
During the construction phase the Designers will:

Review and respond to requests for information (RFIs), Non Conformance Reports
(NCRs) and Field Change Notices (FCNs)
Ensure the integrity of the design is maintained
Review test plans and test results.
9 COMPETENCY
The Engineering Director will ensure that only qualified and competent professional designers
undertake design work and the competency of personnel required to check and approve
designs will also be reviewed and approved by the Employer. Competency records will be
maintained on Aconex.
A staff competency matrix will be produced by the Engineering Director indicating the roles
and responsibilities for all Designers carrying out design and checking of design output and
records of individuals competencies.
Where the design is subcontracted, details of the Sub-Designer will be submitted for the
Consortium Engineering Directors acceptance.
To support the above process, the Designers are required to provide the role descriptions and
qualifications of the Designers competent persons fulfilling the key design roles.
All design documents will be signed by the Designers competent persons at each of the three
quality stages; Prepare, Check and Approve.
The person required to sign at each of these levels is stipulated in the Designers competency
records. The ability of a nominated individual to sign on behalf of the required party (at the
designated authorisation level) will be clearly stated.
It is expected that any designer who has checking capability will also have the ability to
prepare. However, it is recognised that at the approval level the skill requirement is more
multi-discipline so the designer may not have the ability to prepare. Authorisation levels are
defined as:
Prepared by a competent person who produces the design document, checking their
own work complies with codes and standards governing that work.
Checked by a competent person able to undertake a formal detailed check of design
methods, codes and standards used deliverables, calculations, drawings and
specifications produced by another member of the CSJV Design Team. This role is
undertaken by a competent person of the same discipline, not the Preparer, but can be a
member of the same team.
Approved by a competent person able to undertake a review of the design output after
detail checking has taken place to validate that the design is consistent with the project
requirements. Although integration is considered at every stage this level of sign-off is
specifically intended as the final confirmation that inter disciplinary checks have been
carried out.

10 RELATED DESIGN TASKS
10.1 Leadership in Energy and Environmental Design (LEED)

Leadership in Energy and Environmental Design (LEED) is a suite of rating systems for the
design, construction, operation, and maintenance of green buildings, homes and
neighborhoods. Developed by the US Green Building Council, LEED is intended to help
building owners and operators find and implement ways to be environmentally responsible and
resource-efficient.
It is an objective of the project that structures should be LEED Compliant to achieve a Silver
Rating as described below.
The systems is points based and there are 100 possible base points distributed across five
major credit categories: Sustainable Sites, Water Efficiency, Energy and Atmosphere,
Materials and Resources, Indoor Environmental Quality, plus an additional six points for
Innovation in Design and an additional 4 points for Regional Priority. Buildings can qualify for
four levels of certification:
Certified: 4049 points

Silver: 5059 points
Gold: 6079 points
Platinum: 80 points and above
Although BACs will not formally apply for a LEED rating for the project infrastructure, the
Designers will comply with the LEEDS requirements and processes in producing designs that
can achieve a LEED rating for the structure in question taking into account the cost benefit of
achieving the rating in question.
Further detail regarding LEED strategy and sustainability generally will be assessed during the
Detailed Design phase. For the Iconic stations the LEED process will be complied with through
the detailed design phase.
10.2 Asset Management and Traceability

The Consortium Asset Management strategy that describes the format and content of asset
information to be provided for Operations and Maintenance purposes is detailed within the
Consortium Automation Plan [11]. The designer is responsible for the provision of asset
information as required by the plan to include:
Asset inventory;
Classification of assets;
Attributes of these assets;
Location and spatial information of assets;
Relationships between assets;
Design models (including 2D, 3D CAD models and related data); and
Documents, drawings and records of assets and systems including test certificates; and
photographs.


M Bac 000000 Ge00 MPL 000002

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M Bac 000000 Ge00 MPL 000002

Uploaded by

Copyright:

Available Formats

Table of Contents

Document No. M-BAC-000000-GE00-MPL-000002 Page 2 of 37 Printed: 3 Dec. 14

Document No. M-BAC-000000-GE00-MPL-000002 Page 3 of 37 Printed: 3 Dec. 14

Document No. M-BAC-000000-GE00-MPL-000002 Page 4 of 37 Printed: 3 Dec. 14

Designer Entities carrying out the design

BACS The Consortium delivering the Riyadh Metro Project Package 1

Document No. M-BAC-000000-GE00-MPL-000002 Page 5 of 37 Printed: 3 Dec. 14

Item Title Document Reference

Document No. M-BAC-000000-GE00-MPL-000002 Page 6 of 37 Printed: 3 Dec. 14

5.1 General Project Information

The Project is divided into three Packages, as follows:

5.2 Contractual Basis

Document No. M-BAC-000000-GE00-MPL-000002 Page 7 of 37 Printed: 3 Dec. 14

5.4 Civil Works JV Infrastructure Design Packaging and Execution

5.4.1 CWJV Engineering Hub

Document No. M-BAC-000000-GE00-MPL-000002 Page 8 of 37 Printed: 3 Dec. 14

Design Description Designer

Document No. M-BAC-000000-GE00-MPL-000002 Page 9 of 37 Printed: 3 Dec. 14

5.6 Design Organization

5.6.1 Consortium Technical Management Team

Document No. M-BAC-000000-GE00-MPL-000002 Page 10 of 37 Printed: 3 Dec. 14

5.6.3 Civil Works Engineering Delivery

5.6.4 Civil Works Integration

Document No. M-BAC-000000-GE00-MPL-000002 Page 11 of 37 Printed: 3 Dec. 14

Document No. M-BAC-000000-GE00-MPL-000002 Page 12 of 37 Printed: 3 Dec. 14

6.1 Design Authority

6.2 Key Roles

6.2.1 CWJV Engineering Director

6.2.2 Consortium Systems Integration Manager

6.2.3 Consortium Systems Integration Manager Transit Systems

Document No. M-BAC-000000-GE00-MPL-000002 Page 13 of 37 Printed: 3 Dec. 14

6.2.5 Consortium Design Manager

6.2.6 Transit Systems Integration Manager

6.2.7 CWJV Integration Manager

Document No. M-BAC-000000-GE00-MPL-000002 Page 14 of 37 Printed: 3 Dec. 14

7 RMP DESIGN PROCESS

This process establishes a systematic methodology for fully identifying Employers

Document No. M-BAC-000000-GE00-MPL-000002 Page 15 of 37 Printed: 3 Dec. 14

Document No. M-BAC-000000-GE00-MPL-000002 Page 16 of 37 Printed: 3 Dec. 14

7.1.1 Engineering Safety Management

7.1.2 Standards Management

Document No. M-BAC-000000-GE00-MPL-000002 Page 17 of 37 Printed: 3 Dec. 14

Requirements will be allocated to the Designer as agreed between the Consortium

The Requirements Management process is described in the Consortium Requirements

7.1.4 Reliability, Availability and Maintainability (RAM)

Document No. M-BAC-000000-GE00-MPL-000002 Page 18 of 37 Printed: 3 Dec. 14

Validation is intended to ensure a product, service, or system results in a product, service, or

7.2 Design Development Stages

7.2.2 Red Diamond

The design has been developed to show:

Document No. M-BAC-000000-GE00-MPL-000002 Page 19 of 37 Printed: 3 Dec. 14

7.2.3 60% Design Gate Review

7.2.4 90% Draft Final Gate Review

7.2.5 100% Final Design Gate Review

7.2.6 Issue for Construction

8 DESIGN MANAGEMENT PROCESSES AND PROCEDURES

8.1 Design Management Plan

Document No. M-BAC-000000-GE00-MPL-000002 Page 21 of 37 Printed: 3 Dec. 14

8.2 Interface Management

The Consortium Interface Management strategy and processes is as described in the

Document No. M-BAC-000000-GE00-MPL-000002 Page 22 of 37 Printed: 3 Dec. 14

8.3 Design Progress Reporting

For details on progress reporting please refer to EPR Procedure [13].