Break Out 1: CM of Digital Equipment Facilitator: Bill Kline - FENOC June 1, 2019 Cleveland 2005

Existence of Formal Programs Program Administration Few specific programs for digital CM identified Fermi has procedure to handle digital CM Most adapt current processes for digital CM Tending toward Eng. for program control, away from IT Level of Detail Control Need standard level of detail, responsibilities clearly defined Supplier QA - standards for rigor, web access to software revision Record and Track Default Values Drawings, software control programs, June 1, 2019 Cleveland 2005

Process Attributes As-Found, As-Left Conditions Is complexity of digital CM updates error-likely? How tested or verified? Not well defined Need to document as-left conditions CM Security needs or methods Password protection for various tasks Initial Modification and Testing Start very early for large projects Simulator testing, out-of-bounds testing, “try to break it” Emergent Plant Issues No particular concerns noted June 1, 2019 Cleveland 2005

Special Requirements Formal Training Programs Knowledge and need for training of all affected on digital CM Industry maturity on digital CM issues Overlap testing (like relay testing) Lack of INPO inspection modules Generate historical record of what was done before Need to “simulate” as well as “stimulate” June 1, 2019 Cleveland 2005

Take Away Points Group Insights Need to Identify/Define Boundaries Who is allowed to do what Engineering needs to understand full capability Testing Requirements Standards for integration testing Listing of as-left function configuration Need for Control Executable File - Retain Source File - Retain Revisions June 1, 2019 Cleveland 2005