projet hinkley point c a new engineering model

1

Projet Hinkley Point C

A new Engineering model

26/06/2017 Robert Pays

UK PROTECT

UK PROTECT

HUC © 18 May 2017 EDF Energy plc. All rights Reserved Template Number: NNB-301-TEM-000002 Version: 4.0

2

HPC Project Values developed

with lessons learned in mind

UK PROTECT

UK PROTECT

NNB-301-PRE-000219


3

HPC schedule

UK PROTECT

UK PROTECT

NNB-301-PRE-000219


COD Unit 2J0 Unit 2

ESTABLISH SITEMOBILISE

RECRUIT ; RESTART SITE

DISCHARGE CONSENTS

CONSTRUCTION(TO JO)

CONSTRUCTION(TO JO)

CONSTRUCTION(TO COD)

CONSTRUCTION(TO COD)

72 MONTHS

72 MONTHS12 MONTHS

ENGINEERING SCHEDULE

J0 Unit 1 COD Unit 1

COD Unit 2

First CSJ PCSR 3 I&C software release

IDR

DCO

FID

J0 Unit 2

31 MONTHS

Construction : 72 months(+6 months contingency) - 12 months between the 2 units

HPC Project Organisation

HUC Update © 4 January 2017 EDF Energy plc. All rights Reserved Template Number: NNB-301-TEM-000002 Version: 4.04

HPC Project Director

(Directeur de projetHPC)

Engineering

Director

(Directeur de

l’ingénierie)

Delivery

Director

(directeur des

programme)

Director

(directeur

commercial)

DIPNN HPC

Engineering

NNB

Engineering

WHO is going to build HPC – An integrated team


Bylor - JV

BBB - JV

JV - JV

- JV

A strong design configuration management


Main actions taken

- Lessons learnt from TSN, FA3 and OL3

- UK regulatory issues addressed up front through

Generic Design Assessment

- Required design changes reflected in UK EPR

design base (RC1)

- Design process set out to ensure sequence links

to construction and procurement (Integrated

Working Schedule)

- Constructability addressed through 4D models

- Constructive relationships with regulators,

significant regulatory oversight inside the UK

project

- Early Contractors Involvement at early stage in

developing the detailed design to ensure full

benefit of supply chain’s FA3 and UK experience

Schedule Risk managed through ECI, 4D model

and contracting strategy


● Early contractor involvement (ECI) with FID 7 contractors (main site contractors)

● 4D model testing: The Integrated Working Schedule is continuously tested against the 4D model (3D + time) to ensure optimal activity sequencing

● Contracting strategy provides strong schedule related incentives and a requirement for early warnings (Will be covered in detail later)

● Early/temporary systems: Identification of alternative construction sequences through early/temporary commissioning systems.

● Contingency: the current investment case includes a provision of 6 months of contingency over the baseline IWS on Unit 1.

● Experience from Flamanville as well as other major infrastructure projects, including: London Olympics, Crossrail, Heathrow Terminals 2 & 5, Sizewell B, Taishan and AP1000 nuclear power plant

Digital Engineering with Common Tools Shared

by all the Designers


3D Modelling of all the buildings

For each HPC building, a digital 3D modelling showing all the components

and layout (piping, ventilation, cabling, instrumentation , ...)

• 3D modelling shared between all the electro mechanical

designers

• This 3D modelling connected to the data kernel for the

management of data and to guarantee the consistency between

1D, 2D and 3D design data

• As built 3D modelling transferred to the Operation team

3D Modelling of Site Plot Plan

-To manage all the design interfaces between the designers

-To provide a design site configuration to be used for construction

3D clash free civil reinforcement drawings

-To manage all the interfaces between rebars and anchors plates

-To provide a clash free design for construction to minimise field changes and improve productivity


Command Centres key to our success

HPC Engineering Command Centre (ECC):

drivers


• ECC coordinates all the main HPC stakeholders involved in engineering activities:

- EDF/RD entities (CNEN, SOFINEL, SEPTEN, CEIDRE)

- FID 7 (engineering activities) and civil designers- NNB for design process & surveillance and the interfaces with

Delivery Command Center

• Technical teams (“plateaux métiers”) with dedicated resources (from RD and suppliers) directly connected and controlled by the ECC

• The presence of FID 7 in ECC should enable to significantly simplify the interface management

• ECC under HPC Engineering Director strategic oversight

HPC Engineering Command Center (ECC):

Main ECC Responsibilities


1. Management of delivery of HPC Engineering scope including:a) RD documentation

b) HPC Project surveillance of supplier documentation

2. Management of design integration includinga) Modification and design configuration management

b) Design interfaces

c) Tools/methods

3. Engineering Project Control Activities including:a) Schedule and cost

b) Risks/opportunities

c) NNB/RD Contract

4. Efficient interface with NNB Design Process – especially surveillance

Objectives for HPC new engineering delivery

model


5 OBJECTIVES TO IMPROVE ENGINEERING PERFORMANCE

Clarify and improve project management and NI technical

integration

Design & set-up multi-discipline NI project production plateaus

1

2

On-board locally suppliers and NNB resources having delegation on

the design within the RD plateaus3

Implement “System Engineering” method and data-centric approach

taking to deliver project design4

Define a unique integration model common to NNB & RD5

Key evolutions


� The ECC creation in 2015 lead to a reinforced collaboration between contributors to

project steering activities

� The new model aims at significantly increase :

� HPC dedicated resources

� and the co-localisation of disciplines collaborating to HPC engineering studies.

� On the NI scope, launch of 2 new Integrated Teams responsible for the design of NI

Buildings & and the process activities, and under direct operational steering of the RD

project team

� In addition, a new plateau dedicated to HPC for manufacturing activites Equipment

Supply Function covering quality surveillance and expediting

� Creation of Unit Integration

HPC Delivery model overview


Integrated Team

Auxiliary

buildings Bristol

NNB/CNEN/Sofinel/

Areva/fournisseurs

Integrated Team

Main Buildings

Malakoff/VivaNNB/CNEN/SOFINEL

/Areva, Civil

designer/ suppliers

Delivery in Integrated

Teams

NN

B E

ng

ine

eri

ng

AR

EV

A

Fo

urn

isse

urs

CN

EP

E,

Se

pte

n,

Ce

idre

, G

E

Delivery and

expertise outside

integrated teams

Plant Integration Team(configuration &data management, interfaces, methods and tools, …)

NI

NI Management (EDVANCE)

Equipment supply Function

NNB/CEIDRE/AREVA/GE

CE

IDR

E

SE

PT

EN

CI/BOP Management

Integrated

Team

CI/BOPTours/ Parc

Grammont

NNB, CNEPE,

GE, suppliers

Delivery/ex

pertise

outside

integrated

teams

Integrated Team

Process and I&C

Montrouge/Parc

AzurNNB/CNEN/Sofinel/A

reva/fournisseurs

Key principles for Plant Integration


Principle #1 Plant integration covers the overall scope of engineering activities of HPC project. The perimeter includes EDF SA and NNB engineering

activities

Principle #2 Plant integration is the only responsible for the overall integration and cross interfaces management among lots

Plant Integration does not perform design production on its own and relies for this on delivery entities

Principle #3Plant integration is the unique governance focal point between engineering delivery entities and other project stakeholders within NNB (eg.

DCC, SCC)

Working level interactions can be done directly to ease delivery

Principle #4 Plant integration covers the “end-to-end” project life cycle : as-designed, as-procured, as-constructed, as commissioned in the frame of the

CDE (Common Data Environment)

Purpose of Plant Integration :

Support the Engineering Director, to ensure that HPC Engineering delivers to quality, cost and schedule a

coherent, safe and compliant design, fit for construction, commissioning and operation


THANKS

projet hinkley point c a new engineering model

Documents