knowledge management ofmanagement of a npp project …€¦ · knowledge management ofmanagement of...
TRANSCRIPT
KNOWLEDGE MANAGEMENT OFKNOWLEDGE MANAGEMENT OF A NPP PROJECTOLKILUOTO 3 CASE
7.11.2016
Silvennoinen Jouni
Teollisuuden Voima Oyj
© Teollisuuden Voima Oyj LUOTTAMUKSELLINEN© Teollisuuden Voima Oyj LUOTTAMUKSELLINEN
Teollisuuden Voima Oyj
Teollisuuden Voima Oyj and Posiva Oy- Unique Nuclear Site in Olkiluoto, Finland
OL1 and OL2 BWR’s started in early
q ,
OL1 and OL2 – BWR’s started in early 1980’s
Continuous improvement and i i k f f tuncompromising work for safety
2018 renewal of Operating License
OL3 – EPR technologygy
Testing phase ongoing, Operating License applied
Electricity production at the end of Electricity production at the end of 2018
Final disposal facility for spent nuclear fuel from R&D to constructionfuel – from R&D to construction
World first: Construction License granted
LUOTTAMUKSELLINEN© Teollisuuden Voima Oyj 2
LUOTTAMUKSELLINEN© Teollisuuden Voima Oyj
OL3 EPR October 2016
OL3 EPR October 2016 – Main Control Room
LUOTTAMUKSELLINEN© Teollisuuden Voima Oyj
6
OL3 EPR April 2016 –
Operation LicensepApplication
7
OL3 EPR Project Status
• Site workforce currently about 2 400 persons
• Finalization of the main electromechanical installations and plant finishing works are underway
• NCC – Nuclear Circuit Cleaning completed
Si l t Sit A t T t l t d• Simulator Site Acceptance Test completed
• The Turbine Plant commissioning has been completed as far as possible, partly in
tipreservation
• Cold Functional Tests, summer 2017
8
Knowledge Management During NPP Design and C t ti d T f i t O ti d M i tConstruction, and Transfer into Operation and Maintenance
1 2 3
Size
1
Duration
2
“Complexity”
3
X XKM
• Physical size• Nr of organisations• Amount of money
• Many years• People
change
• Integrated• FOAK• Proof of
complianceTransfer
Plant Operation and maintenance: long term reliable operation, cost-effective maintenance, safety case, etc
KM
9
OL3 EPR Project – Challenges in Plant Design Data M t d i th P j tManagement during the Project
• Data structure: databases, documents, hierarchy, distributed into several organisations
• Data quality: information content in the design data and documentation must be clear, consistent, and correct.
• Administration and management: planning and implementation of design data and document administration; metadata, data access etc
• Safety Regulations: need to prove that the design is compliant with the safety requirements, in a traceable and verifiable way
“ ” f f• “Dynamics” of plant design: design freezes, is the design mature enough to be release to downstream design steps, management of design changes (scope and impact)
• Configuration management and control
10
Plant Design Data Management during the Project
”Management”• People with skills and
relevant experiencep• Processes• Safety Case and Safety
Authority interaction
Tools
Etc.Important factors:- Maturity of plant design FOAK
- Capability of the Supplierp y pp- Capability of the Owner- Safety Authority and Regulatory Environment
LUOTTAMUKSELLINEN© Teollisuuden Voima Oyj
Knowledge Management During NPP Design and Construction- Licensing of Digital I&C
STUK
Conceptual Design PlanContents Correspond to PSAR +
System pre-inspection documentsContents Correspond to FSAR+
FAT Inspection SAT inspection Periodic inspection
STUK Approval of disassembly of test bay
STUK Approval of System Commissioning
Program
STUK Decision/Approval granted for Fuel Loading
For info For info For info For info For infoFor info
Safety Authority
TVO Licensing
TVO Plant Integration, Licensee review
SQAD Report 2+
SQAD Report 4-
SQAD Report
suppl. 5a
SQAD Report
suppl. 5b SQAD Report 0
SQAD Report 4/5'Owner
TVO I&C System
TVO I&C Architecture/Integration
PR-1PR-1PR-1P1 AssSys x
PR-1PR-1PR-1P2 AssSys x
PR-1PR-1PR-1P3 AssSys x
PR-1PR-1PR-1P4 AssSys x
PR-1PR-1PR-1
P5a AssSys x
P1 AssArch
P2 AssArch
P3 AssArch
P5a AssArch
P5b AssArch
P4 AssArch
PR-1PR-1PR-1
P5b AssSys xI&C Report (4):
‐I&C detailed design qualified as I&C Report (2): ‐ I&C Architecture and System basic
AREVA Plant Integration, Designers review
PR-1 Arch PR-2 Arch PR-3 ArchPR-5b ArchPR-5a Arch
PR-4 Arch
Plant Supplier
tested ‐ Readiness for I&C into Operating License Application
ydesign qualified as specified ‐ V&V and Test coverage adequate as planned
AREVA I&C Architecture/Integration
Pre-inspection docs P1Arch
PR-1PR-1PR-1
PR-2 Sys x
PR-1PR-1PR-1
PR-1 Sys x
PR-1PR-1PR-1
PR-3 Sys x
PR-1PR-1PR-1
PR-4 Sys x
PR-1PR-1PR-1
PR-5a Sys x
Pre-inspection docs P1Sys x
Pre-inspection docs P2Sys x
Pre-inspection docs P2Arch
PR-1PR-1PR-1
PR-5b Sys xDefined Design Phases based on defined Plant design configuration
‐ Documentation and organization adequately in place for start commissioning
AREVA I&C System
I&C Phase 1 I&C Phase 2 I&C Phase 3 I&C Phase 4
PSAR Phase
I&C Phase 5b
Plant LevelRequirements
Specification and
OLA Submittal FD OLG FL PTO
OLA system/plant level doc updates
for FLOLA doc updates
RC2 RC3RC4
30 days I&C Arch I&C Arch
Sys x Sys x
Construction Phase
OLA doc updates
I&C Phase 5a
FSAR Phase
OLA system/plant level doc updates for OLG
design configuration
LUOTTAMUKSELLINEN© Teollisuuden Voima Oyj 12
Requirements Specification and Planning
I&C Phase 2Design and Specification
I&C Phase 3Detail Design and implementation
I&C Phase 4Integration and analysis Nuc Comm, Phase
C+D
Specification and planning
P&S 2.0.00
yDemo Run(Phase E)
I&C ArchPhase 1
I&C Arch Phase 2 Non-nuclear commissioning, Phase A+BInstallation
I&C Phase 5a
OL3 EPR Project – Preparation for Operation Phase
• Build adequate competencies to be able to operate and maintain the plant
• Plant Operation• Maintenance• Engineering• Safety CaseSafety Case
• How to ensure that skills and competencies are
• built and collected during construction • transferred for operation and maintenance phase
• Case System Engineers readiness self-assessment
14
OL3 EPR Project – System Engineers
• Need to create “capability clusters” taking into account the different system groups / engineering disciplines, number of System Engineers, and the required knowledge
• System attributes: System group /engineering discipline, “required knowledge quantity” (i.e. how complex and/or difficult a system is can the work be outsourced etc)system is, can the work be outsourced, etc)
• Target is to have synergies in learning and create teams where System Engineers are bl t t b k f h thable to act as back-up for each other
17