Configuration Management Operating Experience Breakout Meeting 6/26/18

Discussion Topics Temporary Modifications (WOTM/PCTM vs Temporary Design Change) Governance Roles Responsibilities Cost Codes for FCRs (Trending) Document Control and Procedure Requirements Cyber Security – Configuration Control

Temporary Modifications Several Learnings Recent findings throughout industry due to No clear ownership Lack of or inconsistent documentation Ownership of PCTM and WOTM is usually Operations with limited to no Engineering Oversight Documentation is required Engineering owns temporary modifications Wolf Creek - Documentation changes by OPS/MTN require Face-to-Face communication Recommend cross-functional training on 3-pillars of configuration management OPS, WM, MTN, etc.

FCR Cause Codes for Trending How are others documenting cause codes for PICs/FCRs Only documenting engineering consequential errors Not consistently documenting walk-down errors

Procedural Requirements for Document Control Design Changes Most have 90 days past ECP RTO for all documents to be complete and support closure Some in industry have had a significant backlog Limited attention to ECP closure activities How was it corrected One day per week in Engineering Alignment Meeting One plant has a CR generated every week for not meeting procedural requirements Some documents can have a backlog of changes posted before revision Drawings – already discussed in presentation from Southern Company Benchmarking

Cyber Security Configuration Control Discussion held, however limited knowledge in breakout. Question for all – how do others maintain configuration for “Cyber Security” Not Safeguard Not Safety Related Somewhere in between Password protected server?