Workshop 1: Processing Facility Configuration Information Facilitator: Sam Melton Progress Energy June 11-14, 2006 Richmond, VA

Topics for Discussion Defining FCI Scope: Deciding what of existing info needs to be maintained with limited resources How to communicate the results of the decision CM Equilibrium This module describes a well established, widely accepted model of the equilibrium state of Configuration Management in nuclear power plants. CM Process Model This module describes the processes that are used to return a plant to the equilibrium state. Design and Operating Margins This module describes how CM is used to protect design and Operating Margins Functional Areas This module demonstrates how Configuration Management applies to the normal everyday functions performed by most organizations across the site.

Example horror stories. Topics for Discussion Example horror stories. Large volume of drawings produced at construction, little used Historical status Do you post changes to historical documents? Upgrade if used? Process to restore with as-built. (use of ECN package) Ownership? What is controlled? What is NOT Controlled? Power block vs. non-power block

Defining FCI Scope Solutions: Topics for Discussion Defining FCI Scope Solutions: Classification by priority, (type, use or safety class) Use of hierarchy Move information to databases or other sources Validate use Allocate resources Communications: Status Notes on drawings Notes in database

Topics for Discussion How to manage identification, scheduling and resource allocation and impact for FCI update. Change process ensures FCI is tagged Identifying FCI Engineers CM review MEL cross reference (as good as the data) Check list, by programs or by document Design guides

Topics for Discussion Problem areas: CM Review In Line? Most do not. A/E Missing or without tribal knowledge. Skill of the craft.

Topics for Discussion Prioritization: Reviewed schemes on prioritization and update schedules. EPRI document contains recommendations No consensus Issue - communication of prioritization scheme

Process for doc type change verses Process for change type: Topics for Discussion Process for doc type change verses Process for change type: By change package only Identify all changes in change packages Policing/pending changes monitoring: Identified unimplemented (design complete) changes exist too long

Topics for Discussion Principles: 1 - Accurate EC status 2 - Scheduling EC implementation (Exelon 20/40 rule) 3 - Periodic review of pending changes 4 - Communicate document management status to workers

Topics for Discussion Change Notice Verses Direct Revision: Very few facilities produce final document revisions as part of the design EC Most use the change notice of different sorts