1 / 13

Sam Melton Supervisor, Configuration Management Brunswick Nuclear Plant Progress Energy

CM04 Facility Configuration Information Change Process. Sam Melton Supervisor, Configuration Management Brunswick Nuclear Plant Progress Energy June 11-14, 2006 Richmond, VA. CM Process Model. Change Facility Configuration Information? Design Output documents (drawings & specs)

petra
Download Presentation

Sam Melton Supervisor, Configuration Management Brunswick Nuclear Plant Progress Energy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CM04 Facility Configuration Information Change Process Sam Melton Supervisor, Configuration Management Brunswick Nuclear Plant Progress Energy June 11-14, 2006Richmond, VA

  2. CM Process Model Change Facility Configuration Information? • Design Output documents (drawings & specs) • Operational Configuration Documents • Other operating, maintenance, training, etc. ChangeDesignRequirements? ChangePhysicalConfiguration? ChangeFacilityConfigurationInformation? EvaluateIdentifiedProblem orDesiredChange DoNothing More No No No CM Equilibrium Yes Yes Yes DesignRequirementsChange Process Physical ConfigurationChangeAuthorizationProcess Facility ConfigurationInformationChange Process CM004

  3. FCI Change Process It ain’t over till the paperwork’s done!

  4. FCI Change Process • Initiators • CM02: mismatch between design requirements and other CM elements prompts change to design requirements. • CM03: mismatch between physical plant and other CM elements prompts change to physical plant. • CM04: mismatch between elements of facility configuration information prompts change to facility configuration information ALL MISMATCH RESOLUTIONS EXCEPT RESTORE WILL RESULT IN FCI CHANGE

  5. FCI Change Process • Initiators • Engineering Change process – desired/planned update to design requirements • Work Management process – resolution of discrepancies discovered during work, implementation of authorized changes not directed by EC process • Corrective Action Process (CAP) – resolution of CM mismatches documented via CAP • Procedure development process • Informal processes – minor improvements, trivial problem resolutions, sub-tier processes

  6. FCI Change Process • Characteristics of FCI • Defined: content, format, quality is specified, usually in a procedure • Controlled: revision level, status, storage and distribution • Tracked: meta-data (index information) exists in a record system • Owned: mechanism for update exists with defined responsibilities, including approval authority • Verifiable

  7. FCI Change Process • Initiating Change • Process driver defines need for change • Usually embedded in other process • Process requirement includes record identification and definition of what in the existing record must be changed or what is the content of a new record. • Process may initiate a stand-alone FCI process (for example, CAP investigation creates action for Procedure Revision Request)

  8. FCI Change Process • Tracking Change • FCI process or initiating process flags FCI record to identify that a change has been initiated • Status of FCI record or change record indicates status of development and implementation of revision • Users of FCI record consider the impact of pending change on the use of FCI (for example, Verify Working Documents)

  9. FCI Change Process • Developing Change • FCI change process is defined • Method • Format • Content • Review • Impact of change on other FCI is considered • Impact of change on organizations (Change Management) may be in FCI process or in initiating process

  10. FCI Change Process • Scheduling Change • Usually driven by initiating process • Sometimes driven by FCI process • Always driven by resource • Can be established as a restraint • For Engineering Changes, can be tied to Operations Turnover • Can be tied to Change Closeout • Another example – Procedure on hold (prevents use until revision is issued)

  11. FCI Change Process Other Issues • Document Priority • Mechanism to classify documents based on importance • Used to aid in scheduling changes • Used to aid in determining distribution • Document Hierarchy • Mechanism to aid in resolving CM mismatches between documents

  12. FCI Change Process Other Issues • Unincorporated Changes • Long term (or forever) tracking of changes in lieu of incorporation to ensure impact is evaluated • Used for low priority documents with few likely changes • Risks: error-likely situation, user frustration • Benefits: resource application efficiency • Training • CM training typically focuses on problem identification and physical change • Important to include FCI, particularly status control

  13. Facility Configuration Information Change Process QUESTIONS?

More Related