Professional Documents
Culture Documents
Shanghai Nuclear Power Plant Control Room Modifications
Shanghai Nuclear Power Plant Control Room Modifications
We are “Sunflower, Better Energy, Better Life” team from a design institute
SNERDI.
Today we will present Qinshan Nuclear Power Plant Main Control Room
Modification Human Factors Engineering Project.
[NEXT]
1
P2
Section 01
Project Background and Purpose
Project Background and Purpose 1.00
Organizational Approach to Project Planning 1.01
Project Identification Process 1.02
Project Selection Process 1.03
Project Selection 1.04
Project Goals and Benefits 1.05
Success Measures/Criteria Identified 1.06
[NEXT]
2
Project Background and Purpose 3-1
1.00 Shanghai & Clean Energy – Nuclear Energy Industry - Company & Award
P3
In China
• National electric industry
quality award in 2009
• National advanced quality work
company in 2011
• China Performance Excellence
Award in 2012
• National quality award in 2014
• Shanghai quality management
gold award in 2016
3
The first nuclear power plant in mainland China was designed by SNERDI
30 years ago, in Qinshan. It has been operating with zero accident and
achieved great commercial success till now.
Striving towards Excellent Performance, we won lots of awards and
recognition at home and abroad.
[NEXT]
3
Project Background and Purpose 3-2
1.00 P4
Shanghai & Clean Energy – Nuclear Energy Industry - Company & Award (Video)
4
leading innovative nuclear energy designer and developer.
The first nuclear power plant in mainland China was designed by SNERDI
30 years ago, in Qinshan. It has been operating with zero accident and
achieved great commercial success till now.
Striving towards Excellent Performance, we won lots of awards and
recognition at home and abroad.
[NEXT]
4
Project Background and Purpose 3-3
1.00 Abbreviations & Terminology
P5
Human System
NPP Nuclear Power Plant MCR Main Control Room HSI Interface
Human Factors
HFE Engineering HED HFE Discrepancy VR Virtual Reality
[NEXT]
5
1.01 Organizational Approach to Project Planning 2-1 P6
Leadership Multi-year
Dr. Zheng Mingguang Project
President of SNERDI Culture of Excellent
IAQ Academician Performance & Nuclear Safety Planning
SWOT
Customer
• NPP owner
Supporting Work Process
Info KM HR AS TC FN CT
6
1.01 Organizational Approach to Project Planning 2-2 P7
Sources of Information/
Stage Tools Why
Data
•Strategy & Planning
•Digitalized Quality Management
•Voice of Process •On line Voice of Customer to understand
Platform
Problems & •Voice of Customer requirements/complains.
➢ Voice of Customer
Opportunities •Voice of National Regulatory •Understand the Voice of Process
➢ Satisfaction Surveys
Detection Agency •Analyze process quality and detect special
➢ Design Management System
•Operation Experience deviation
➢ Operation Experience Review (OER)
•KPIs Performance
Potential Projects •Project Pool •Collection of potential projects from design,
•Potential Projects List
Identification •Affinity Diagram modification, O&M
•Project Selection Criteria •Project Selection Matrix •Focus on important projects on selection criteria
Projects Selection
•Important Projects List •Score Principle •Select projects with higher score.
Source of information, data and tools are incorporated into the project
identification and selection process.
[NEXT]
7
1.02 Project Identification Process (General) P8
Identified
Potential
Projects
KPIs from DMS
[NEXT]
8
1.03 Project Selection Process (General) P9
Group
Committee Review
Operators (End
Benefit to other
Impact on NPP
Review
Link with other
Total Score
(time, budget)
shutdown or
customers)
Resources
objectives
Impact on
Impact on
Impact on
operation
Financial
Urgency
strategic
Criteria
project
Impact
(1~10)
(need
safety
Cost
NPP
not)
Review
Department Important Project
Review
We also provide the Scoring Principles of each criterion. So we can get the
total score.
Candidates and quality engineers provide data for group review and
department review first.
[CLICK 1]
If the project has high score on impact to safety or urgency or cost, i.e, at
least one of these three criteria is scored on a scale of nine to ten, it is
defined as important project, then this project will enter the Project
Selection Committee review. The project selection committee will review
9
and evaluate to select the final projects.
[NEXT]
9
1.04 Project Selection Process (Specific) 3-1 P10
[NEXT]
10
1.04 Project Selection Process (Specific) 3-2 P11
Group Review
Review
Total 27
Project Selection
Committee Review
Qinshan Nuclear Power Plant Control Room Modification
Human Factors Engineering Project
Approved
Total 5
Approved Projects
All the projects were prioritized in this Selection Matrix by group and
department.
[CLICK 3] Our team is responsible for the main control room modification
human factors engineering (HFE) project. The project selection committee
determined to start this project immediately.
[NEXT]
11
1.04 Project Selection Process (Specific) 3-3 P12
Technology Environment
Human
Organization Task
[CLICK 1]
Pictures show the difference between poor and good HFE application.
[NEXT]
12
1.05 Project Goals and Benefits P13
Benefit 1.2
Reduced CO2 Emissions
7.8 million t/y
Nuclear energy is a “Safety First” industry. The primary goal was “Safe
Operation of MCR for an additional 20 years”, which would bring large profit
and decrease of the carbon dioxide emission measured by the whole plant.
The second goal was “No Delay of the Modification Outage”. The
commercial operation of Qinshan nuclear power plant on schedule could
avoid 3million RMB per day as the delay cost.
The third goal is about the LEVERAGE, which means to establish the
benchmark for the entire nuclear energy industry in mainland China, since it
is the 1st HFE Project in the 1st MCR Modification Project
[NEXT]
13
1.06 Success Measures/Criteria Identified P14
Gap
HFE Analysis Coverage Rate No Delay Positive Feedback
Increase from 5% to 100% of Outage due to HFE Project by the Regulator & Industry
For the 1st Goal as safe operation, there were 3 gap criteria items as below:
- HFE Analysis Coverage Rate, increasing from 5% to 100%
- HFE Discrepancy (HED ) Resolution Rate, reaching a high resolution rate
especially for high priority HEDs
- Human Performance Index, increasing by 5%
An additional criteria for the safe operation during outage was added as well.
For the second goal, the gap criteria “no delay” had a Counter Metrics which
aimed to control the increase of labor cost due to the high priority of outage
duration limit.
For the third goal, the positive feedback from the regulator and industry
would be more convinced as the criteria.
14
[NEXT]
14
P15
Section 02
Project Framework
Concise Project Statement 2.01
Type of Project 2.02
Scope Statement 2.03
Assumptions/Expectation 2.04
Project Schedule/High-level 2.05
Budget(Financial or Resource) 2.06
Risk Management 2.07
[NEXT]
15
PROJECT STATEMENT
P16
• Current State: MCR without systematic HFE analysis
• Desired future state: A state-of-the-art HFE level design
• Gap: HFE discrepancies
PROJECT TYPE
Design Project
D/V
IV
RISK MANAGEMENT
[NEXT]
16
2.01 Concise Project Statement P17
[NEXT]
17
2.02 Type of Project P18
Type of project
Design Project
st
1 in China Project Approach 4.01, 5.01
No Methodology Guide
No available standard design criteria,
scheme, or template for reference,
only high level requirement
It is a Design Project
What an exciting challenge! This was the first HFE project for the first full-
scope MCR modification project in China. We had nothing about the design
for reference, only the high level requirement was available.
18
[NEXT]
18
2.03 Scope Statement P19
All the in-scope and out-of-scope items were clearly addressed in the HFE
Project Plan for better track, in compliance with the Mandatory
Requirement in the Organization.
19
The statement was reviewed and approved by the champion. Except the
control room environment was removed due to the risk on the delay in the
trade-off analysis later, there was no change.
[NEXT]
19
2.04 Assumptions/Expectations P20
We used the feedback from other project validated by all stakeholders who
were not with our team, and deduced a comprehensive list with 3 general
Assumptions and 4 Project Specific Assumptions.
For example, the new simulator was planned to be delivered after 6 months
of MCR modification implementation according to normal practice. However,
considering its importance in HFE validation test, the availability of the new
simulator before implementation must be ensured. Eventually, training
center agreed to change the contract with their suppliers to ensure the
availability and requirements on time.
After negotiation, all the providers accepted to fulfill the assumptions and
expectations.
[NEXT]
20
2.05 Project Schedule/High-level Plan P21
This is the High-level Project Schedule with milestones illustrated with four
project stages.
The schedule was monthly reviewed in the routine meeting of the project.
The HFE plan would be updated if the any factors of the project ( such as
scopes, schedule etc.) was changed. Changes to the plan needed to be
presented at the monthly meeting and approved by Champion. So that the
works could be pushed to complete with no delay.
[NEXT]
21
2.06 Budget(Financial or Resources) P22
Budget Timeline
16% 80%
12% 60%
8% 40%
4% 20%
0% 0%
10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8
2016 2017 2018 Labor Management System
Time All Projects * All Employee
Since all hardware and software were available in SNERDI HFE LAB, and
the depreciation was out of the project scope, Labor Cost was the only
factor affecting the budget/resources control in our project.
Our project had 1540 person*day budget according to the experience and
WBS analysis.
[NEXT]
22
2.07 Risk Management P23
Monitoring@Stage
Dimension Risk Prediction Grade Symptoms Contingency Plan
P A D/V IV
Regulator Reject the solution and results H Any disagrees Invite the regulator to inspect 〇 〇
Schedule Project delay H Milestone delay Add labor cost and Backup time 〇 〇 〇 〇
Unavailability of extra HFE designers M Workload increase or Dynamic monitoring plan 〇 〇 〇 〇
Resource Unavailability of simulator L reduce of free Application of digital tools 〇
Unavailability of operators L schedule champion’s coordination 〇
Hold routine meeting
Organization Unfamiliar with HFE principles M. Unknown what to do
Give appropriate training 〇 〇 〇 〇
Can not solve HED due to cost or schedule limits H 〇 〇
Communication and discussion,
Technology Conflict on HFE guideline and operators' habit L Failures, rejects, 〇 〇 〇
set backup time,
Unknow inconformity from new supplier L delays 〇 〇
Optimization plan
Failure of validation test L 〇 〇
According to the
New risk Unexpected risk arising during the project H/M/L
active conditions
Track and resolve in real time 〇 〇 〇 〇
The risk list was monthly reviewed in the routine meeting of the project
based on the occurrence of any symptom, and deviations of plan were
reviewed to identify potential new risks during the progress. Decisions and
supporting resources which addressed risks, should be clearly implemented
during the meeting avoiding any delay.
[NEXT]
23
P24
Section 03
Stakeholders and the Project Team
Stakeholders and How Identified 3.01
Project Champion 3.02
Project Team Selection 3.03
Team Preparation 3.04
Team Routines 3.05
[NEXT]
24
3.01 Stakeholders and How Identified 2-1 P25
Stakeholders
Identification S I P O C
Supplier Input Process Output Customers
Stakeholders
Analysis
▪ Directors ▪ Standards
▪ Operators ▪ Regulator Requirements ▪ Project Approval
Champion ▪ HFE Designers ▪ Director Requirements ▪ Plan
▪ Plan ▪ Operators
Selection Internal ▪ Risk ▪ Regulators
▪ HSI Designers ▪ Operator Feedback ▪ Analysis
▪ Deliveries ▪ HSI Designers
▪ Quality Expert ▪ Detail HSI Design ▪ Design
▪ Modified MCR ▪ Directors
▪ Training Center ▪ Construction ▪ Verification
Team Member ▪ Modified Procedure ▪ Suppliers
▪ Plant Physical Features ▪ Validation
Selection ▪ Modified Training ▪ HFE Designers
▪ Modification Differences ▪ Acceptance
▪ Monitoring Plan ▪ Quality Expert
▪ Regulators ▪ Procedures ▪ Monitoring
External ▪ Equipment Design
Team ▪ Suppliers
Preparation
Team
Routines
In order to identify all potential stakeholders, the tool SIPOC was used to
make it clear.
[NEXT]
25
3.01 Stakeholders and How Identified 2-2 P26
Analysis Operators 5 3
A more error tolerant and
user-friendly MCR
Influence
The major project needs and expectations of each stakeholder were pointed
out as well to support further communication and resistance analysis.
[NEXT]
26
3.02 Project Champion 2-1 P27
Stakeholders
Identification
Interest Influence
Stakeholders
Degree Degree
Stakeholders Directors 5 5
Analysis
Operators 5 3
Vice President
HFE Designers 4 3
Champion Yin Weiping
Selection HSI Designers 3 2
Quality Experts 2 3
Training Center 2 1
Team Member
Selection Regulators 3 5
Suppliers 2 1 Chief Engineer
Kong Deping
Team Internal External
Preparation Champion Selection Rule Project Champion(Sponsors)
The internal stakeholder with Highest Influence Degree
Team
Routines
They had power and technical capacity to remove barriers, obtain resources
and drive results within the organization.
[NEXT]
27
3.02 Project Champion 2-2 P28
Communication plan was created so that project champions and the team
could communicate with each other in a highly- efficient way. They kept
communicating with the team on their total concerns, in the manner of
kick-off meeting, workshop, and E-mails.
[NEXT]
28
3.03 Project Team Selection P29
At the start of the project, we made plans for team selection, defining
team roles and knowledge required.
We confirmed the team members’ skill gaps between their current level
of knowledge and the knowledge required. After finishing our plans for
team selection, we collected all the skill gaps which were showed on the
table, and arranged corresponding trainings for them.
[NEXT]
29
3.04 Team Preparation P30
Chen Mingjin 10
Team
Luo Jingping None
Preparation
Yuan Zhong 4
Ma Yuezhu 4
Team
Routines Shen Jialin 3
Though many of our team members had a history of working together for
nearly one decade, a specific visit to Qinshan Power Plant gave all the
team members, especially newcomers, a chance to know more about the
plant operation and our project as well. Adequate trainings and
brainstorming meetings brought all team members in-depth understanding
on our project and increased personal bonds.
[NEXT]
30
3.05 Team Routines P31
Stakeholders
Communication Plan
Identification
Stake-
Content Tools P A D/V IV
holders
Stakeholders Champion Project ▪ Meeting W R M M
Analysis progress and
▪ E-mail
reports
File, Fax ▪ Wechat
A A A A
▪ Face to face
More
Champion Formal Meeting Minutes ▪ Phone
Selection Team Internal ▪ Meeting W W W W
Shared folders Members technical
▪ Shared
communication
Emails Folders
Team Member ▪ E-mail
A A A A
Selection We-Chat ▪ Wechat
▪ Face to face
Face-to-face, Phone ▪ Phone
Team Other ▪ Meeting — — B B
Stake-
Preparation holders
▪ Fax
▪ E-mail
— — A A
▪ Wechat,
▪ Phone
Team
Routines A: As needed W: Weekly B: Biweekly M: Monthly R: Review meeting
From the very beginning, team routines and expectations had been
established, which included phone call, face-to-face talk, WeChat group
discussion, E-Mails, and collaborative work in shared folders. Meeting
minutes, files and faxes served as official formal way of communication.
[NEXT]
31
P32
Section 04
Project Overview
Project Approach 4.01
Tools Used Throughout Project 4.02
Tools Output at Different Stages of Projects 4.03
How Team Was Prepared to Use the Tools 4.04
Dealing with Project Risk 4.05
Encountering and Handling Resistance as a Risk 4.06
Stakeholder Involvement in Project 4.07
32
4.01 Project Approach 2-1
P33
[NEXT]
33
4.01 Project Approach 2-2
P34
In Plan stage, we defined all the critical factors, such as stakeholders, goals,
scope, risks , schedule and etc.
Analysis Stage generated project HFE guidelines, which were based on the
modification demands from stakeholders and state-of-the-art standards.
34
system design project.
[NEXT]
34
4.02 Tools Used Throughout Project P35
5.01
In the Plan Stage, we used 5 tools to define the key features of the project.
[CLICK 1]
Affinity Analysis Tool facilitated to summarize and categorize HSI
modification demands. Then the Trade-off Analysis Tool converted the
demands to design specifications. Finally, HFE guidelines were specified by
the tool Scoping.
[CLICK 2]
The first two tools applied parallelly in the third stage. Rapid Prototype
Iteration focused on the SUITABILITY check, while Task Cognitive
Walkthrough emphasized the AVAILABILITY check. And HED resolution
helped us to evaluate and identify correction action, and re-verify the design
change.
[CLICK 3]
35
In the final stage, all interactive features were integrated into an overview by
the tool Simulator-based Validation Test.
[NEXT]
35
4.03 Tool Output at Different Stages of Project P36
5.01
As you can see, each tool had clear outputs which would be used as part of
the project data flow in section 5.01.
For example, in the Analysis Stage the outputs were Modification Demands,
Design Specifications and HFE Guidelines separately.
And in the Stage D/V, same output “HEDs” were generated by first two tools.
After HED Resolution, Improved Design Solution would be outputted.
[NEXT]
36
4.04 How Team Was Prepared to Use the Tools 2-1
P37
Based on the analyzed knowledge gap of tools for all team members, a
comprehensive training program for all tools was developed.
[NEXT]
37
4.04 How Team Was Prepared to Use the Tools 2-2
P38
Customers Task
Rapid
Classroom Case Test Cognitive
How to Select Appropriate Walk-
Prototype
Training Iteration
HFE Guidelines? through
[CLICK 1]
Training effects were validated by exam, case test or field test to ensure the
thorough understanding of tools and their usages. Furthermore, the
organization also had the on-job mentoring policy.
[NEXT]
38
4.05 Dealing with Project Risk P39
Risks were captured from five different dimensions in the project plan.
[NEXT]
39
4.06 Encountering and Handling Resistance as a Risk P40
Receive confident HFE Some review conclusions can Consult implementation plan in Agree to discuss before
Regulators evidences for the safe not meet the regulator advance; formal conclusion
operation requirements Invite regulator to witness test published
Standard delivers meet the Changes on standard Communicate in advance reduce the
Suppliers project requirements platform features rework
Agree to make changes
[NEXT]
40
4.07 Stakeholder Involvement in Project P41
Operators N/A Provide and verify demands Provide feedback Join the validation test as subjects
*Not team operation N/A Specification change Promote HED resolution Provide feedback
expert Generate human performance index
HSI N/A Verify demands Provide correction method Discuss the validation results
Designers N/A Accept or reject the results Refine and improve design Refine and improve design
*Not team HSI
expert
Suppliers N/A N/A Provide correction method Discuss the validation results
N/A N/A Refine and improve Equipment Refine and improve equipment
Regulators Review the plan N/A N/A Witness the test and review the report
In the table, the cells in gray showed all stakeholders were involved in
appropriate stage, while green showed their feedback and impacts.
For example, champion’s feedback and impacts had very positive effects on
the project.
[NEXT]
41
P42
Section 05
Project Walkthrough
Data-Driven Project Flow 5.01
Solution Validation 5.02
Solution Justification 5.03
Results 5.04
Maintaining the Gain 5.05
Project Communication 5.06
[NEXT]
42
Data-Driven Project Flow
5.01 Overview
P43
Based on the features of old design, and general knowledge like standards,
knowledge & skill, experiences, and new technology, we developed the new
design and other 3 kinds of supporting data.
The progress of the whole project was driven by Data Flows from these
tools.
[NEXT]
43
Data-Driven Project Flow
5.01 Plan
P44
PLAN
INPUTS TOOL(Purpose) OUTPUTS
SIPOC
Identify all stakeholders ▪ All Stakeholders
Voice of Stakeholders
▪ Key Stakeholders Generate project goals & ▪ Goals & Criteria
criteria
In-Scope/Out-of-Scope
▪ Goals & Criteria Fully understand the project ▪ Scope
scope
Brainstorming
▪ Stakeholders Capture assumptions, ▪ Assumptions &
▪ Goals & Criteria expectations and risks Expectations
▪ Scope ▪ Risks
On the first page of each stage, we illustrated the purpose of stage and a
table containing inputs, tools(purpose), and outputs.
In the plan stage, all 5 tools were connected by the data flow closely.
[NEXT]
44
Data-Driven Project Flow
5.01 Plan *Tool1 SIPOC
P45
3.01
S I P O C
Supplier Input Process Output Customers
▪ Directors ▪ Standards
Internal
▪ Operators ▪ Regulator Requirements ▪ Project Approval
▪ Plan ▪ Operators
▪ HFE Designers ▪ Director Requirements ▪ Plan
▪ Risk ▪ Regulators
▪ HSI Designers ▪ Operator Feedback ▪ Analysis
▪ Deliveries ▪ HSI Designers
▪ Quality Expert ▪ Detail HSI Design ▪ Design
▪ Modified MCR ▪ Directors
▪ Training Center ▪ Construction ▪ Verification
▪ Modified Procedure ▪ Suppliers
▪ Plant Physical Features ▪ Validation
▪ Modified Training ▪ HFE Designers
▪ Modification Differences ▪ Acceptance
▪ Monitoring Plan ▪ Quality Expert
External ▪ Regulators ▪ Procedures ▪ Monitoring
▪ Suppliers ▪ Equipment Design
General knowledge, which was very helpful for all stages, would not be
addressed later to overshadow the data flow.
[NEXT]
45
Data-Driven Project Flow
5.01 Plan *Tool2 Influence & Interest Analysis
P46
3.02 3.03
Satisfaction Management
Director
Selection Criteria
Regulator
▪ Key Stakeholders
Interest >2 & Influence>2
Influence
▪ Champion/Sponsor
Operators Internal & MAX(Influence)
Quality ▪ Team Members
HSI
Designers
HFE Interest ≥ 2 & Influence ≥ 2
Designer
Training
Suppliers
Center
Supervision Notification
Interest
Stakeholder Weight Analysis
[NEXT]
46
Data-Driven Project Flow
5.01 Plan *Tool3 Voice of Stakeholders
P47
◼ No Delay of Outage
No Delay
◼ Safe Operation of MCR for an Additional 20 Years
Champion Pass Regulator Review
◼ Benchmark Establishment As the 1st HFE Project in the 1st
Enhance HFE
MCR Modification Project in China
Voice of Stakeholders
Generate project
▪ Key Stakeholders goals & criteria ▪ Goals & Criteria
Key stakeholders’ needs and expectations were the key source of project
goals.
[NEXT]
47
Data-Driven Project Flow
5.01 Plan *Tool4 In-Scope/Out-of-Scope
P48
In-Scope/Out-of-Scope
Fully understand the
▪ Goals & Criteria project scope ▪ Scope
With the constrains of goals and criteria generated by previous tool, the
project scope was fully understood.
[NEXT]
48
Data-Driven Project Flow
5.01 Plan *Tool5 Brainstorming
P49
Brainstorming
2.04 Assumptions/Expectations 2.07 Risks
Providers Assumptions/Expectations Communication Result Dimension Risk Prediction Grade
Accepted in principle, but the date and
Regulator Reject the solution and results H
3.01 Regulator
Arrange the review meeting and TIMELY frequency exist uncertain. One expert from Schedule Project delay H
feedback the review comments regulator is appointed as our Technical Unavailability of extra HFE
M
consultant. designers
Stakeholders Resource Unavailability of simulator L
Coordinate schedule and resources Unavailability of operators L
Champion cross projects
Accepted
Organization
1.05 1.06 Unfamiliar with HFE principles
Can not solve HED due to
M.
H
Participant in the discussion and cost or schedule limits
Goals & Criteria HSI Designers engaged in the design change
Get commitment from Manager
Conflict on HFE guideline and
L
Technology operators' habit
Interview, questionnaire and test Accepted by 30 operators of Qinshan NPP Unknow inconformity from
Operators L
2.03 subjects and added into annual re-training program new supplier
Failure of validation test L
Qinshan Old Simulator is available
Promise to provides the tools and build the Unexpected risk arising during
Scope Training Center
New simulator is constructed and
permits to use; Simulator instructors
new simulator in the planned stage New risk the project
H/M/L
(AGREED AND LISTED IN CONTRACT)
Training Mentors
Console/Panel Sample Parts before Oct. 2017 Promise to provide sample once available
Supplier Physical Mockups before Nov. 2017 Confirmed in the procurement contract
Brainstorming
▪ Stakeholders Capture assumptions, ▪ Assumptions &
▪ Goals & Criteria expectations and risks Expectations
▪ Scope ▪ Risks
[NEXT]
49
Data-Driven Project Flow
5.01 Analysis
P50
ANALYSIS
INPUTS TOOL(Purpose) OUTPUTS
P ▪ Key Stakeholders Affinity Analysis ▪ 60
Summarize & categorize Modification
A ▪ N/A HSI modification Demands
demands
The purpose of Analysis Stage was to generate project HFE guidelines with
3 tools (Affinity Analysis, Trade-off Analysis, Scoping).
[NEXT]
50
Data-Driven Project Flow
5.01 ANALYSIS *Tool1 Affinity Analysis 2-1
P51
A N/A
The last step was to combine all data above into a 256 Modification Raw
Demands list.
[NEXT]
51
Data-Driven Project Flow
5.01 ANALYSIS *Tool1 Affinity Analysis 2-2
P52
Some part of the mimic The background color and the font
60 Modification Demands was dropped, and it is of labels are different.
suggested to change Furthermore, the control room has
the material. different sizes of the label paper
Reduced by 77%
Other Groups under Console/Panel
Before After
[CLICK 1] In the 1st round analysis, firstly, we divided all these raw demands
into four top level groups based on the composition of control room.
[CLICK 3] Finally, all the Raw HSI Demands were reduced by 77%, and
52
outputted only 60 Modification Demands.
[NEXT]
52
Data-Driven Project Flow
5.01 ANALYSIS *Tool2 Trade-off Analysis 2-1
P53
PASS REJECT
[NEXT]
53
Data-Driven Project Flow
5.01 ANALYSIS *Tool2 Trade-off Analysis 2-2
P54
Higher Investment
Paperless VDU Pointer Enhanced Functional
Recorder Indicators CPC/Alarm Large Displays Unacceptable
Full-digital Control Room Technical Risks
Both half-digital and full-digital solution could solve the current problem of
old design.
[CLICK 2]
54
3) Large displays were not added due to the space limitation.
[NEXT]
54
Data-Driven Project Flow
5.01 ANALYSIS *Tool3 Scoping
P55
It was not appropriate and necessary to comply with all general state-of-the-
art guidelines from industry standards. Scoping was used to specify project
HFE guidelines based on the constrains of project types of equipment and
functions. Finally, 1191 guidelines were remained after scoping.
[NEXT]
55
Data-Driven Project Flow
5.01 Design & Verification Overview
P56
Then, all the HEDs were processed through HED Resolution to output the
Improved Design Solution.
[NEXT]
56
Data-Driven Project Flow
5.01 D/V *Tool1 Rapid Prototype Iteration 4-1
P57
Technology Environment
1154 HFE
Guidelines
(Part One of 1191)
Human
Organization Task
D/V N/A
[NEXT]
57
Data-Driven Project Flow
5.01 D/V *Tool1 Rapid Prototype Iteration 4-2
P58
1252
Verification
Items
Fail
113 HEDs
113
This was the flow chart of Rapid Prototype Iteration, which was done by
the HFE Designers independently
[NEXT]
58
Data-Driven Project Flow
5.01 D/V *Tool1 Rapid Prototype Iteration 4-3
P59
Hardware Prototypes
Software Prototypes
There were several hardware and software prototypes served along with the
progress of project.
[CLICK 1] Digital Manikin covered the contour size feature of panels and
consoles.
[CLICK 2] Virtual Panel supported the verification of detailed layout with a
flexible way in early iteration. And Wooden Prototype provided a better
overview to very the layout as well.
[NEXT]
59
Data-Driven Project Flow
5.01 D/V *Tool1 Rapid Prototype Iteration 4-4
P60
Documentation of HEDs
1154
HFE Guidelines
Match HSI
1252
Verification
Items
Examples of HEDs
Rapid
Prototype
Iteration
Verification
Fail
#1015 #1052 # 2078
Scale Readability Switch Torque Confused Lines
113 HEDs (Multiple types, unclear meaning)
Examples are like the scale readability, switch torque, confused lines.
[NEXT]
60
Data-Driven Project Flow
5.01 D/V *Tool2 Task Cognitive Walkthrough 4-1
P61
Technology Environment
37 HFE
Guidelines
(Part Two of 1191) Human
Organization Task
The second tool of D/V stage was Task Cognitive Walkthrough, which had
specific focus on the interaction between human, technology and TASK.
Its goal was to check the AVAILABILITY of HSI items needed to support
task sequence.
[NEXT]
61
Data-Driven Project Flow
5.01 D/V *Tool2 Task Cognitive Walkthrough 4-2
P62
Modification Differences List with Related Tasks and Scenarios Scenario List
Difference Potential Influences Impacted Related No. Scenario
37 HFE Guidelines No. Category
Description
P/C
Assessment Tasks Scenarios
1
2
正常运行期间降功率至60%
凝汽器抽气系统投入运行
旁排系统切除
Relocate CB-518 盘 专 设 相 关 红 色 光
CB-514A CB-514A本就用于显示保护系统信号,
专设相关的报警监 SGTR
3
汽机冲转至额定转速
2 字牌报警移至CB-514A。
CB-518 专设报警整体 迁移至CB-514A是较为
视任务。 SG液位高
4
Equipment 合适的,影响较小。 5 秦塘2P59对220kV I母充电
Task
Cognitive
Walkthrough
[CLICK 1] The virtual reality platform in HFE Lab and the plant new
simulator assisted the availability check of HSI items needed by the scenario
completion.
[NEXT]
62
Data-Driven Project Flow
5.01 D/V *Tool2 Task Cognitive Walkthrough 4-3
P63
54 Modification
Difference
Identification STEP 1 STEP 2 STEP 3 STEP 4
▪ List the Task ▪ Find supportive HSI elements ▪ Evaluate ▪ Compare before and
Sequence based on ▪ List their characteristics HSI problems after design in detail as a
Scenario Description with the supplement
18 Senario assistant Score Explanation
Selection checklist 1 The task can not be
derived from successfully completed
HFE guidelines after the modification
2 The task can be
successfully completed
after the modification but
with degraded user
Task experience
67 HEDs
[NEXT]
63
Data-Driven Project Flow
5.01 D/V *Tool2 Task Cognitive Walkthrough 4-4
P64
Documentation of HEDs
37 HFE Guidelines
54 Modification
Difference
Identification
18 Senario
Selection Examples of HEDs
Task
Cognitive
Walkthrough
[NEXT]
64
Data-Driven Project Flow
5.01 D/V *Tool3 HED Resolution 3-1
P65
113 HEDs
from
Rapid Prototype Iteration
67 HEDs
from
Task Cognitive Walkthrough
The goal of HED Resolution was to evaluate and identify correction action
for HED, and re-verify the design change.
All the HEDs from Rapid Prototype Iteration and Task Cognitive Walkthrough
were regarded as inputs.
[NEXT]
65
Data-Driven
Data-Driven ProjectProject
Flow Flow
5.01 D/V *Tool3 HED Resolution
Design & Verification——Tool2 Cognitive 3-2
Walkthrough (6-6)
P66
Exception Analysis
113+67 HEDs ◼ More technical basis exists to support current design
from Rapid Prototype Iteration
& Task Cognitive Walkthrough
HED Prioritization
Exception Analysis
HED Prioritization
Correction Action Development
◼ Developed by HED responsible group (non-
Correction Action HFE Evaluation
HFE group)
Development of Correction Action fail
HFE Evaluation of Resolution
pass
◼ If agreement can not be achieved between HFE
Design Change and HED responsible group, raise the HED to
Champion for final decision
◼ Multi-group Discussion Meeting were very
fail pass
Re-Verification useful
Closure
[NEXT]
66
Data-Driven
Data-Driven ProjectProject
Flow Flow
5.01 D/V *Tool3 HED Resolution
Design & Verification——Tool2 Cognitive 3-3
Walkthrough (6-6)
P67
1st
Round Sources All P1 P2 P3 Excp. HED Resolution Rate
HED Resolution Prototype-Hardware
Prototype-Software
49
64
0
0
12 29
17 43
8
4
Priority I & II HED, 100% ALL
Task Cognitive
Walkthrough
67 0 10 52 5
1.06
Criteria
Priority III HED , 85%
97.5%
∑ 180 0 39 124 17
Examples of HED Resolution
2nd Round Sources All P1 P2 P3 Excp.
HED Resolution Prototype-Hardware 15 0 0 8 7
Prototype-Software 7 0 0 6 1
Task Cognitive
40 0 0 15 5
Walkthrough
∑ 62 0 0 29 13
# Multiple controllers should be placed above a single monitor
3rd Round Sources All P1 P2 P3 Excp.
HED Resolution Prototype-Hardware 7 0 0 2 5
Prototype-Software 4 0 0 1 3
Task Cognitive
5 0 0 0 5
Walkthrough
∑ 16 0 0 3 13
◼ Unsolved: Due to the high cost to improve the standard # Add parameter to support the task completion
feature of plant computer system and scale of one indicator
And the HED Resolution Rate EXCEEDED the criteria set in section 1.06.
[NEXT]
67
Data-Driven Project Flow
5.01 Integrated Validation Overview
P68
INTEGRATED VALIDATION
INPUTS TOOL(Purpose) OUTPUTS
The goal of this stage is to provide confident evidences that the integrated
HSI system (HSI, Tasks, Operators) design solution adequately supports
plant personnel in safely operating the plant.
[NEXT]
68
5.01
Data-Driven Project Flow P69
IV *Tool Simulator-based Validation Test 5-1
Technology Environment
Human
All the design of real control room shall be validated by simulator before full
implementation.
The key input was the improved design solution from previous stage. And
besides human performance index , the validated design solution was
outputted.
[NEXT]
69
Data-Driven
Data-Driven Project
Project Flow
Flow
5.01 Integrated Validation *Simulator-based
IV *Tool Simulator-based Validation
Validation Test 5-2
P70
Conclusion
Unlike the new-built NPP, we conducted two-round tests to compare the old
design and modified design before implementation, so that we could acquire
clearer results.
Each round had similar test process showed on the flow chart .
[NEXT]
70
Data-Driven
Data-Driven Project
Project Flow
Flow
5.01 Integrated Validation *Simulator-based
IV *Tool Simulator-based Validation
Validation Test 5-3
P71
Pilot Test
Test
Training
Test Introduction
Test Video/Audio
Formal Test
Data
Collection
Questionnaires
Discussion ▪ Operators & Observers
▪ Subjective & Objective Data
▪ Qualitative & Quantitative Data
Data Analysis
Operator Performance Questionnaire
Plant Performance Data Observation Records
Conclusion Briefing Records
Raw data were collected during of the whole test, for example, video/audio
data, plant performance data from simulator, and qualitative and quantitative
data from operators and observers.
[NEXT]
71
Data-Driven Project Flow
5.01 IV *Tool Simulator-based Validation Test 5-4
P72
Pilot Test
Test
Training Workload of the same operator in
Different operator workload in
Test Introduction the same scenario different scenario
Formal Test
Data
Collection
Questionnaires
Discussion
Conclusion
After the test, we analyzed all these raw data in our HFE Lab by
professional software named “H-lab”.
[NEXT]
72
Data-Driven Project Flow
5.01 IV *Tool Simulator-based Validation Test 5-5
P73
[NEXT]
73
5.02 Solution Validation 2-1 P74
1.06 5.01
It was a challenge to validate the final HFE level of main control room, which
was determined by thousands integrated features and elements as a whole.
The results of HFE Analysis Coverage Rate, HED Resolution Rate and
Human Performance Index, which related to three gaps of the Goal “safe
operation”, validated the solution from different aspects.
[NEXT]
74
5.02 Solution Validation 2-2 P75
Operation Operator
Observation Satisfaction Survey
4.36
Not
Satisfied Satisfied
0 5
Observed fluent operator interaction and high satisfaction score revealed the
validation of our solution as well.
[NEXT]
75
5.03 Solution Justifications P76
1.04
SAME
HALF DIGITAL
1540 Person ∙ Day Under Control
2.06
Benefit
VS.
[NEXT]
76
5.04 Results 2-1 P77
All the project goals were achieved with the successful fulfillment of all gaps,
additional and counter criteria.
[NEXT]
77
5.04 Results 2-2 P78
Goal 3
Criteria
Benchmark Status
Type
Establishment
Gap
“Sufficient HFE guarantees have been
provided to the life extension
Positive Feedback application of Qinshan NPP. “
Achieved
by the Regulator & Industry
Regulator Could be applied
for similar projects in other 37 units in China
N/A
N/A
Additional N/A
Counter N/A
Metrics
[NEXT]
78
5.05 Maintaining the Gains P79
New KPI
Changes/Results One-Month Life Cycle Latest
Goals Where How
Against All Criteria Who Who Result
Human Performance Human Error
Index Reports
Training Center
HFE Designers Operation Tech. No Report
HFE Analysis Coverage New Modification
Support Department
Rate Proposal
Plant
HED Resolution Rate HED Tracking List
Safe Operation Power Generating Reliable
for an Additional Champion
*Additional Profit Champion Records 100% power
20 Years Project PM
operation
Results
No Delay Positive feedback
Feedback &
of the by the Regulator & Inside & Champion
HFE Designers Standardization Positive
Modification Industry Outside HFE Designers
in the Industry
Outage 118
◼ Safe Operation During
Benchmark Outage
Establishment ◼ No Delay of Modification
N/A, No Change upon Time N/A
Outage due to HFE
Project
◼ Labor Cost Growth Rate
HFE Designers
HFE Designers
Operation Tech. Change review
Changes Updated Guidelines Company Operation Tech. No Change
Support required
Support Department
Department
One-month and Life Cycle Plan with clear criteria and responsibility were
established to monitor project results and potential changes.
[CLICK 1]
Happily, there is no report and no change until now.
And the plant has been in reliable power operation status until we share this
presentation.
[CLICK 2]
After one month, the main responsibility of monitoring was transferred from
project members to plant operation staff.
79
a new KPI to track the performance of operators as a supplement.
[NEXT]
79
5.06 Project Communication P80
ALL
Communication Results
Stakeholders
International
Champion Project Extended Review Meeting
Summary Report IAEA
Operators Madrid, Spain
20th , Sep. 2018 14th, Sep. 2018
HSI Designers
Training Center
[NEXT]
80
P81
THANK YOU
Sunflower, Better Energy, Better Life
SNERDI@Shanghai, China
We are very happy to share with you our team´s efforts, and our dedication
to provide Better Energy, Better Life.
Thank you very much.
[NEXT]
81
P82
Quick Links
1.00 1.01 1.02 1.03 1.04 1.05 1.06
Section 01 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Section 02 15 16 17 18 19 20 21 22 23
Section 03 24 25 26 27 28 29 30 31
4.01 4.02 4.03 4.04 4.05 4.06 4.07
Section 04 32 33 34 35 36 37 38 39 40 41
5.01 P A
Section 05 42 43 44 45 46 47 48 49 50 51 52 53 54 55
D/V IV
56 57 58 59 60 61 62 63 64 65 66 67 68 69
5.02 5.03 5.04 5.05 5.06
70 71 72 73 74 75 76 77 78 79 80
82