Instructor: Lloyd Hancock

Slides:



Advertisements
Similar presentations
PRINCIPLES OF A CALIBRATION MANAGEMENT SYSTEM
Advertisements

Software Quality Assurance Plan
EPSON STAMPING ISO REV 1 2/10/2000.
1. 2 ANSI/NIRMA Standard CM 1.0 The Rear View Mirror and What’s Ahead.
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
SAE AS9100 Quality Systems - Aerospace Model for Quality Assurance
Quality Management System
School of Computing, Dublin Institute of Technology.
Software Configuration Management (SCM)
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne. – Times: –See noticeboard outside.
Configuration Management
Achieving our mission Presented to Line Staff. INTERNAL CONTROLS What are they?
Introduction to Software Testing
ISO 9000 Certification ISO 9001 and ISO
Laboratory Information Management Systems (LIMS) Lindy A. Brigham Div of Plant Pathology and Microbiology Department of Plant Sciences PLS 595D Regulatory.
Software Configuration Management (SCM)
CSSE 375 Software Construction and Evolution: Configuration Management
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
Configuration Management for Transportation Management Systems Establishing and Maintaining System Integrity.
1 Configuration Management 101 ITS Professional Capacity Building Program T3 Webinar February 21, 2008.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Configuration Management, Logistics, and Universal CM Issues Larry Bauer Boeing Commercial Airplanes NDIA Conference Miami March 4-5, 2005
Introduction to Software Quality Assurance (SQA)
Configuration Management T3 Webinar Feb 21, 2008 Chuck Larsen ITS Program Coordinator Oregon Department of Transportation.
Commissioning of Fire Protection and Life Safety Systems Presented by: Charles Kilfoil Bechtel National Waste Treatment Plant Richland WA.
Quality Assurance Program National Enrichment Facility Warren Dorman September 19, National Energy and Environmental Conference.
Configuration Management Benchmarking Group Conference June 6 – 9, 2004 Kansas City, MO © 2004 CMBG Configuration Management Fundamentals including Margin.
Software Configuration Management (SCM)
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
IRSN STRATEGY TO ASSESS A NEW MAINTENANCE POLICY / Nesebar, Bulgaria Presented by Naoëlle MATAHRI, IRSN.
1 Configuration Management “The Cookbook Approach”
NHUG - Boston - 08/04/20101 Considerations for Operability of Chillers and Chilled Water Systems NHUG Summer Meeting August 4, 2010 Tim Mitchell Component.
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
2006 CMBG Conference Sam Melton Supervisor, Configuration Management Brunswick Nuclear Plant Progress Energy June 11-14, 2006 Richmond, VA CM04 Facility.
Configuration Management Non Government Std: EIA Standard-649 “A management process for establishing and maintaining consistency of a product’s performance,
ANSI/NIRMA Standard CM 1.0 Status Update
© Mahindra Satyam 2009 Configuration Management QMS Training.
Software Configuration Management (SCM). Product Developer Disciplines One view of the world is that there are three types of activities are required.
1 Review of Specifications for Digital Upgrades NHUG Summer Meeting July 17, 2008 Tim Mitchell Component Engineering Palo Verde Nuclear Generating Station.
2006 CMBG Conference Keith A. Reinsmith PPL Susquehanna 2006 CMBG Conference June 11-14, 2006 Richmond, VA Configuration Management Awareness Training.
Project management Topic 8 Configuration Management.
CMBG Conference 2013 Atlanta GA June 3, 2013 ANSI/NIRMA Standard CM Year History.
ANSI/NIRMA Standard CM 1.0 Status Update CMBG Conference 2016 West Palm Beach Gardens FL June 6, 2016.
TEMPUS ME-TEMPUS-JPHES “IMPROVEMENT OF PARTNERSHIP WITH ENTERPISES BY ENHENCEMENT OF A REGIONAL QUALITY MANAGEMENT POTENTIALS IN WBC” TEMPUS
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
CM-101 Configuration Management Fundamentals
Accelerator Readiness Review October 31, 2006
Software Configuration Management (SCM)
Software Configuration Management
Software Project Configuration Management
Software Quality Control and Quality Assurance: Introduction
Chapter 11: Software Configuration Management
Software Configuration Management
Software and Systems Integration
UNIT V QUALITY SYSTEMS.
EOB Methodology Overview
Presented By: Mike Stout – PPL Glenn Neises - INPO
NRC Cyber Security Regulatory Overview
Engineering Processes
Introduction to Software Testing
How to Manage Guidance from Multiple Organizations into CM
Chapter 11: Software Configuration Management
Configuration Management AP-929, Revision 1 Mike Stout Chairman CMBG Steering Committee April 9, 2019 Cleveland 2005.
Configuration Management
Configuration Management
I&C requirements and configuration management
DOE Review of the LCLS Project October 2006
Software Reviews.
DRAFT ISO 10007:2017 Revision Overview Quality management – Guidelines for configuration management ISO/TC176 TG 01.
Presentation transcript:

Instructor: Lloyd Hancock Configuration Management Benchmarking Conference Tarrytown, NY September 24-27, 2000 CM - 101 Instructor: Lloyd Hancock

Presentation Topics CM Definition Differences in CM Programs Basic CM Model CM Fundamentals Benefits of CM

CM Definition An integrated management process to ensure that: Design requirements for plant systems, structures, components, software and hardware are defined and documented, Changes to Design requirements are identified, documented, controlled, evaluated and approved or disapproved,

CM Definition (cont.) Approved design changes and status of implementation are recorded and reported throughout the life of the Plant, which results in the accurate implementation of design output information into the physical configuration of the Plant (i.e., the as-built status matches the design documents),

CM Definition (cont.) Plant configuration documents specifying operations, maintenance, testing, installation, procurement, inspection and training requirements are updated and maintained consistent with the Plant design, and The implementation of the program is evaluated for effectiveness.

Differences in CM Programs Primary Purpose Secondary Issues Governing Requirements Peripheral Organizations NASA, DoD, DoE Making sure the right parts are installed to support schedules Change control, status accounting, rigid compliance NASA, Mil Specs, CM Standard EIA Commercial Industry Support , assembly, manufacturing, and production activities Change control, status accounting ISO 9000, ISO 10007, OSHA 9410 ACDM, NIRMA Software CM Manage data elements (code) throughout software life cycle Change/version control, V&V activities IEEE Standards, NIRMA Guidelines ACDM, NUSMG Hardware CM Managing automation functions and devices Managing URLs, PC configurations ANSI and IEEE Standards ACDM Nuclear Facilities Supporting long-term facility operation and maintenance activities. Maintain synchronization between requirements – physical plant – configuration documents Change control, knowing & maintaining design basis, rigid compliance, parts obsolescence 10CFR, NUREGs, Reg. Guides, etc. ANSI/NIRMA CM 1.0-2000 IAEA CM Guidelines CMBG, INPO, NEI, NIRMA, IAEA

Basic CM Model Source: ANSI/NIRMA CM 1.0-2000

CM Fundamentals Work Processes must assure that: • Elements conform all the time • All changes are authorized • Conformance is auditable Source: ANSI/NIRMA CM 1.0-2000

CM Fundamentals Program Management • Program Planning • Physical Configuration Scope Criteria • Facility Configuration Information Scope Criteria • Concepts and Terminology • Interfaces • Configuration Control Info System (CCIS) • Implementation Source: ANSI/NIRMA CM 1.0-2000

CM Fundamentals Design Requirements • Establishment of Design Requirements • System and Process Boundaries • Specific Equipment List • Assignment of SSC Classes • Basis • Communication of Design Requirements Source: ANSI/NIRMA CM 1.0-2000

CM Fundamentals Information Control • Identification • Categorization • Storage • Control and Tracking • Retrieval • Minimization • Operational Configuration Information Status Control Source: ANSI/NIRMA CM 1.0-2000

CM Fundamentals Change Control • Identification • Review of Changes • Implementation of Changes • Documentation of Changes Source: ANSI/NIRMA CM 1.0-2000

CM Fundamentals Assessments • Programmatic Assessments • Physical Configuration Assessment Follow-up • Periodic Equipment Performance Monitoring Source: ANSI/NIRMA CM 1.0-2000

CM Fundamentals Training • Training Content • Specialized Training Source: ANSI/NIRMA CM 1.0-2000

Benefits of CM  More Reliable and Credible Design Information  Reduced O&M Costs  Better Input to Make Informed Decisions  Less Time Spent Researching, Verifying and Cross-Checking Data  Better Job Planning  Reduced Maintenance Time & Rework  Improved ALARA  Elimination of Duplicate Data Bases

Benefits of CM (cont.)  Reduction of Parts Inventory  Fewer Condition Reports, LER's, Audit & Inspection Findings  Reduced Number of Plant Trips  Enhanced Training  More Credible, Less Costly Life Extension Evaluations  Less Time Spent Responding to NRC Requests  Improved NRC Performance Indicator Ratings