2006 CMBG Conference Sam Melton Supervisor, Configuration Management Brunswick Nuclear Plant Progress Energy June 11-14, 2006 Richmond, VA CM04 Facility.

Slides:



Advertisements
Similar presentations
RETURN TO MAIN Implementing a Change Control Procedure Within Your Firm Presented by: TOBI M. HALL SYSTEMS OPERATIONS MANAGER SHOOK, HARDY & BACON L.L.P.
Advertisements

Process and Product Quality Assurance (PPQA)
2007 CMBG Conference Keith Reinsmith PPL Susquehanna, LLC June 17-20, 2007 Charleston, SC Engineering Change Impact Evaluation Process.
Checking & Corrective Action
Configuration Management
[Organisation’s Title] Environmental Management System
Transition from Q1- 8th to Q1- 9th edition
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Chapter 4 Quality Assurance in Context
Environmental Management Systems An Overview With Practical Applications.
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
CSC 395 – Software Engineering Lecture 25: SCM –or– Expecting Change From Everything But Vending Machines.
CMPUT Software Process & QualityProcess Categories - slide# 1©P. Sorenson Engineering Process Category  Processes that specify, implement, or maintain.
Computer Security: Principles and Practice
10.5 Report Performance The process of collecting and distributing performance information, including status reports, progress measurements and forecasts.
Configuration Management
ITIL: Why Your IT Organization Should Care Service Support
Configuration Management
ISO Standard is based on the management model of plan – do - check – act. Today we all be discussing the elements of the standard that deal with.
Release & Deployment ITIL Version 3
What is Business Analysis Planning & Monitoring?
Project Management: Madness or Mayhem
© 2012 IBM Corporation Rational Insight | Back to Basis Series Documents and Record Control Liu Xue Ning.
Software Configuration Management
Configuration Management Benchmarking Group Conference June 6 – 9, 2004 Kansas City, MO © 2004 CMBG Configuration Management Fundamentals including Margin.
Software Configuration Management (SCM)
© Mahindra Satyam 2009 Defect Management and Prevention QMS Training.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Configuration Management Benchmarking Group Conference June 6 – 9, 2004 Kansas City, MO © 2004 CMBG Characteristics of a Good Calculation Program Presented.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
ISO NON-CONFORMANCE, CORRECTIVE AND PREVENTIVE ACTION.
Release Management Configuration management. Release Management Goal Coordinate the processes through the project development life cycle Ensure the.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 1 Diploma of Project Management.
Software Configuration Management (SCM). Product Developer Disciplines One view of the world is that there are three types of activities are required.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
Lesson 1: Examining Professional Project Management Topic 1A: Identify Project Management Processes.
Configuration Management Fundamentals including Margin Management Bill Kline FirstEnergy Nuclear Operating Company (FENOC) June 2, 2008 Shell Beach, CA.
Project management Topic 1 Project management principles.
2006 CMBG Conference Keith A. Reinsmith PPL Susquehanna 2006 CMBG Conference June 11-14, 2006 Richmond, VA Configuration Management Awareness Training.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
2006 CMBG Conference Workshop 2: Facilitator: Keith Reinsmith PPL Susquehanna June 11-14, 2006 Richmond, VA.
Maintaining and Sustaining System Integrity Configuration Management for Transportation Management Systems Configuration management (CM) describes a series.
CM Tools Data Management Trends Wednesday, June 4, 2008 Laurent Perkins Enterprise Informatics.
2010 CMBG Conference Temporary Design Changes Tony Hathcock Duke Energy - Oconee June , 2010 Charlotte, NC.
1 City of Shelby Wastewater Treatment Division Becomes State’s Second Public Agency to Implement a Certified Environmental Management System CERTIFICATION.
2007 CMBG Conference Sam Melton Progress Energy June 19, 2007 Charleston, SC Configuration Management Principles And Practices for New Nuclear Plants.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
Introduction to ITSM processes. CONFIDENTIAL Agenda Problem Management  Overview  High Level process Change Management  Overview  High Level process.
2006 CMBG Conference Mike Stout Spescom Software, Inc. Configuration Management For The Next Generation.
1 CMBG 2009 Planning for Obsolescence June 27, 2009 John Parler South Carolina Electric & Gas.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Instructor: Lloyd Hancock
CM-101 Configuration Management Fundamentals
ITIL: Service Transition
Software Project Configuration Management
NIEP Evaluation PO&A “How-to” Guide and Issue Classification
Software Configuration Management
NEI Configuration Control Benchmark – Palo Verde
Presented By: Mike Stout – PPL Glenn Neises - INPO
Facilitator: Rick Harris and Mike Stout
Reducing Managed Facility Configuration Information
FSAR Configuration Control at PPL Susquehanna, LLC.
Guidance on the New 10CFR50.59 Rule
Configuration Management AP-929, Revision 1 Mike Stout Chairman CMBG Steering Committee April 9, 2019 Cleveland 2005.
BREAKOUT 8: CM and The Next Generation of Plants
Workshop 1: Processing Facility Configuration Information
Final Design Authorization
Managing Project Work, Scope, Schedules, and Cost
Risk Management NDS Forum June 23rd 2010.
Presentation transcript:

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

2006 CMBG Conference CM Process Model Change Facility Configuration Information? Design Output documents (drawings & specs) Operational Configuration Documents Other operating, maintenance, training, etc. Evaluate Identified Problem or Desired Change Change Facility Configuration Information ? Change Design Requirements ? Change Physical Configuration ? Do Nothing More CM Equilibrium Physical Configuration Change Authorization Process Design Requirements Change Process Facility Configuration Information Change Process No Yes No CM004

2006 CMBG Conference FCI Change Process It ain’t over till the paperwork’s done!

2006 CMBG Conference 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

2006 CMBG Conference 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

2006 CMBG Conference 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

2006 CMBG Conference 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)

2006 CMBG Conference 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)

2006 CMBG Conference 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

2006 CMBG Conference 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)

2006 CMBG Conference 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

2006 CMBG Conference 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

2006 CMBG Conference Facility Configuration Information Change Process QUESTIONS?