1. INPO Update CMBG Meeting June 2013
Theme is applying technical conscience principles in engineering activities and products
The mods we do and technical decisions we make put us on the front line of protecting our design basis
If you don’t do it – ask yourself who in your organization will do it?

2. 2013 Department Focus Areas
Engineering Fundamentals and Technical Authority
Vendor Product Quality
Digital Projects / Cyber Security
Seismic / External Events
AC Power Reliability
Last year Technical Conscience Principles were a key focus area for us – using these as statements in AFIs to punctuate their importance. New PO&C have these principles woven into cross-functional areas where engineering interface occurs. Additional focus on beyond design basis event influence on current design bases.
Engineering Fundamentals
• LEARN - Engineers have expert knowledge of plant design, operating requirements, and industry codes and standards
• EVALUATE - Engineers closely monitor and evaluate plant conditions and equipment performance
• ADVOCATE - Engineers proactively promote plant health improvements
• DESIGN – Engineers ensure the plant is operated, maintained and modified in a controlled manner, consistent with design requirements and licensing bases
• EFFECTIVE COMMUNICATION - Engineers communicate technical information effectively, advise management, and advocate resolution of conditions that affect design or equipment performance
• RIGOR - Engineers model critical thinking, exercise disciplined technical decision making, challenge facts, methods, and decisions

3. 2013 Ongoing Work Efforts
Principles, Objectives, and Criteria Revision
EN.1, Engineering Fundamentals
EN.2, Technical Authority
Updated CM.1, Margin Management
Recognizing when your current design basis may need to be changed
Fukushima
Open Phase conditions
Seismic Events
Flooding
CM.1 changed from 5 criteria to previous criteria covered as 6 in new PO &Cs.
New criteria focus on recent events and industry operating experience

4. 2013 Ongoing Work Efforts Transitional CM for New Construction Plants
Need CM controls / programs that use technology
Revised Evaluation Guidelines and Procedures
Evaluation Guidelines Support Focus Areas
AP-932, AP-929 are not updated to reflect need to integrate projects
Example recommendations:
Develop a transition plan for construction, testing, and turnover phase of the project – through initial fuel load. (focus on integrated department hand-offs)
Establish project commitments to ensure design information needed for Operational programs is provided (drawings, calculations, vendor manuals, etc.)
Provide engineering oversight of equipment procurement and use OE
Ensure design requirements are included and verified in field testing
Ensure information management system established during construction phase to support retrieval

5. Engineering Fundamentals and Technical Authority

6. Engineering Fundamentals
Engineering personnel apply essential knowledge, skills, behaviors, and practices needed to ensure:
Equipment performs as required
The plant is maintained within design requirements
Margins are controlled
The plant is operated safely and reliably
57 percent of EN/ER/CM AFI’s can be tied back to engineering fundamentals
Reference Documents:
INPO Principles for Maintaining an Effective Technical Conscience
INPO SOER 10-02, Engaged Thinking Organizations

7. Engineering Fundamentals
Five principle level categories of engineering fundamentals
Monitor and Evaluate
Operate, Maintain, and Modify in a Controlled Manner
Communicate, Advise and Advocate
Acquire and Maintain Expert Knowledge
Critical Thinking, Decision-Making, and Challenging
Engineering personnel recognize and accept their responsibility to:
Address plant technical issues
Act as the site technical conscience
Uphold the plant design and licensing bases
Ensure a margin of safety is maintained

8. Must Know OE - MKOE Part of Performance Objectives & Criteria
A collection of the most important OE documents issued since Engineering MKOE is found in INPO
As discussed in Recommendation 2 of SOER 10-2, Engaged, Thinking Organizations
MKOE should be included in initial and continuing training for supervisors

9. Vendor Product Quality

10. Vendor Product Quality
Working Meeting in April 2012
Selected A/E firms and Various Utilities
Collected best practices for the different blocks in the flowchart
Issued Evaluation Guideline for Vendor Oversight / Engagement
Project Initiation & Project Performance
Workgroup felt that revising INPO and using INPO (Project Management) should provide enough good practice guidance for the industry
How-To:
The scope of work correctly solves the problem
The appropriate controls, processes, and resource mechanisms have been initiated to assure that all critical attributes are satisfied.
Ralph Schwartzbeck
Terry Schuster

11. Vendor Product Quality
INPO , Conduct of Design Engineering Revised for Cyber, Digital, and Vendor Quality Good Practices (Nov. 2012)
Examples of Appendix C (new):
Identify, document, and communicate expectations between engineering vendors and the requesting organization
Perform a feasibility study to identify the best solution

12. Vendor Product Quality
Perform licensing review prior to starting design work
Develop a road map of applicable standards, procedures, and best practices. Communicate this to the engineering service providers
Determine hardware lead time impacts on project schedules
Document and communicate expectations for project and deliverable quality

13. Digital Projects / Cyber Security

14. Digital Projects Digital Project Guidance Modification Testing
FMEA Analysis
Integration of Digital Equipment
Ralph Schwartzbeck
4 scrams in 2012 caused by digital mods – set point changes, 2013? Aligns with SCRAM IER findings
Bill Nowicki
Gary Garrett
Doug Kinsman

15. Digital Projects Recent Industry Workshop – May 2013
IER L Scram Analysis and IERL Causes of Digital Upgrade-Related Events
Community of Practice Webpage
Pilot Review Visits
List Pilot Review Sites -

16. Digital Projects Communication / Technical Leadership (from IER 12-87)
Vendor Interface and Oversight
Technical risk assignment and monitoring
Project personnel knowledge and experience
Supervisor assignment and monitoring of project engineering activities

17. Digital Projects Community of Practice Pilot Review Visits
Used to Share Issues Unique to Digital Modifications
Design Project Issues May Occur Prior to Installation
Pilot Review Visits
Two sites approved in 2013

18. Cyber Security Created Cyber Security Training NANTeL
Awareness (general)
CSAT (assessment team)
Technical (OPS, MA, Design Engr., Engr. Support)
Added Digital/Cyber event codes in EPIX
2013 Plant Evaluations will include cyber security
Waterford and Beaver Valley Plant Evaluations
Driven by NRC regulation. INPO’s Role -Evaluate integration of cyber security behaviors plant programs and processes. Cyber security behaviors need to be part of the plant culture

19. Cyber Security Scope of Cyber Security Program
Safety-related, Important to Safety
Security
Emergency Preparedness
Support systems (BOP) and equipment, which if compromised, would adversely impact configuration control and plant operations

20. Seismic / External Events

21. Seismic Update How-To has been developed and is being used.
No real issues with sites compliance; use with IER L response
IER L issues for NAPS Lessons Learned
EPRI NP-6695 has been supplemented with TR
NRC Issued Draft GL 2011-XX; no movement on it because of Fukushima activities

22. External Events PO & C include - External Events (CM.1)
11 Evaluation Activities
Beyond Design Basis Event
Cliff edge effects
IER on Fukushima Lessons Learned:
Out for Review
IAEA promotes doing Periodic Safety Reviews every 10 years
IAEA Recommended because:
Likelihood of changes in technology and underlying scientific knowledge and analytical techniques
The need to evaluate the cumulative effects of plant modifications and ageing
Evaluate changes in plant (and site) design, climate, flood potential, and transport and industrial activities near the plant site should be considered

23. External Events
Post-Fukushima NRC Near Term Task Force Recommendations (2.1, 2.2, and 2.3)
Items 2.1 and 2.3 are being performed now; NRC Request for Information, issued March 12, 2012
Summary of Industry Results (NRC Follow-ups)
Capability to Mitigate Fires in Large Areas of Plant
Licensee Capability to Mitigate Design Basis Internal and External Events
2.1 Order licensees to reevaluate the seismic and flooding hazards at their sites against current NRC requirements and guidance, and if necessary, update the design basis and SSCs important to safety to protect against the updated hazards.
2.2 Initiate rulemaking to require licensees to confirm seismic hazards and flooding hazards every 10 years and address any new and significant information. If necessary, update the design basis for SSCs important to safety to protect against the updated hazards.
2.3 Order licensees to perform seismic and flood protection walkdowns to identify and address plant-specific vulnerabilities and verify the adequacy of monitoring and maintenance for protection features such as watertight barriers and seals in the interim period until longer term actions are completed to update the design basis for external events.

24. AC Power Source Reliability

25. AC Power Source Reliability
Joint Focus Area with Equipment Reliability
Event LOOP Matrix Reviews
Joint TSG / EDG Reviews
Evaluator Guideline (How To) Issued
Identify vulnerability to design related risk
Checklist Attachment 3, Evaluator Checklist
IER Focused on Causes / Contributors
Target June 2013
Shawn
Simon
Ralph
Kothe
Steve
Swanson

26. EN/CM Department Staff
Org change by adding a section manager
Always looking for new loaned employees