Fermilab’s New Quality Assurance Program Irwin Gaines 23-Jan-2008.

Slides:



Advertisements
Similar presentations
External Quality Assessments Frequently Occurring Findings Observed by The IIA QA Teams.
Advertisements

Contract Review Process Round Table Corporate Counsel Section April 11, 2007.
1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
Ensure Vendor/Engineer of Choice Product Quality
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
ORGANIZATION. 2 Problem scenario  Develop an organizational chart for your laboratory showing lines of authority from the head of the organization to.
ORGANIZATION. 2 Purchasing & Inventory Assessment Occurrence Management Information Management Process Improvement Customer Service Facilities & Safety.
Contractor Assurance System AC Overview October 13, 2009.
Marcy Mealy Procurement Specialist CDBG Program
OHS Worksite Inspections February Health & Safety Systems > The goal of any health & safety system is to eliminate or reduce as far as is practicable.
1 Approach to Implementing the QA Program Local Effort - Global Expectations Approach to Implementing the QA Program Local Effort - Global Expectations.
Assurance Council Brief Status of QA Implementation at Fermilab Tuesday Nov 11, 2008 Jed Heyes.
Corrective & Preventive Action Programme l Corrective and preventive action managed by one programme l Closely linked to the internal audit programme l.
Project Change Management
Stepan Potiyenko ISS Sr.SW Developer.
Laboratory Personnel Dr/Ehsan Moahmen Rizk.
QUALITY MANAGEMENT DEFINITIONS AND CONCEPTS QUALITY MANAGEMENT TOOLS QA / QC PROCESS COMPUTERS AND PROJECT QUALITY.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Configuration Management
5.2 Personnel Use competent staff Supervise as necessary
SQA Work Procedures.
Bodil Mose Pedersen, DHI Status for implementering af ”Quality Manual”
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
Integrated Capability Maturity Model (CMMI)
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
Introduction to Software Quality Assurance (SQA)
FY2010 PEMP Notable Outcomes October 15, FRA, LLC Board of Directors 10/15-16/2009 Office of Quality and Best Practices Performance Evaluation Management.
Software Quality Assurance Activities
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Session 5 Integrating CLAS Into Policy and Practice CLAS Training [ADD DATE] [ADD PRESENTER NAME] [ADD ORGANIZATION NAME]
NCSX Management Overview Hutch Neilson, NCSX Project Manager NCSX Conceptual Design Review Princeton, NJ May 23, 2002.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Lab-Wide Earned Value Management System Project Core Team Meeting October 01, 2008 Dean A. Hoffer/Elaine McCluskey.
QUALITY OF EVIDENCE FRCC Compliance Workshop September/October 2008.
Georgia Institute of Technology CS 4320 Fall 2003.
11 FSO Assessment of Fermilab QA Program Status September 14 – 18, 2009.
Launching the Ship Without a Captain Presented by Betsy Bratton, CPPB, VCO Lead Contract Specialist Department of Motor Vehicles.
How to audit the role of the vendor in the conduct of outsourced studies Kristel Van de Voorde Director Global Quality Regulatory Compliance Bristol-Myers.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
Fermilab Presentation Greg Bock, Pepin Carolan, Mike Lindgren, Elaine McCluskey 2014 SC PM Workshop July 2014.
NCSX Systems Engineering Management Plan Peer Review Bob Simmons May 15, 2003.
Action Tracker · Status Report | Bill Moss, Assistant SecretaryOct 09, 2015 Aging & Long-Term Support Administration Background Strategic Plan Goal / Commitment.
RECOMMENDATIONS OF THE GOVERNOR ’ S TASK FORCE ON CONTRACTING AND PROCUREMENT REVIEW Report Overview PD Customer Forum September 2002.
Doane Pet Care Company Pet Food Safety System (PFSS) M.W. Merkel September 23, 2003 Animal Feed Safety System Public Meeting.
Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
National Center for Coastal Ocean Science Environmental Management System Implementation August 2005.
DOCUMENTATION ISO/IEC 17025:2005 Documentation.
A risk assessment is the process of identifying potential hazards an organization may face and analyzing methods of response if exposure occurs.
Good Laboratory Practice
Responsibilities of Test Facility Management, Study Director, Principal Investigator and Study Personnel G. Jacobs Belgian GLP Monitorate Zagreb, 17 December.
QUALITY ASSURANCE MODULE 3. Definitions Quality Assurance - A process/effort that ensures that processes are followed, that the processes of doing right.
Principal Investigator ESTCP Selection Meeting
Personnel.
Software Project Configuration Management
Software Quality Control and Quality Assurance: Introduction
Software and Systems Integration
Principal Investigator ESTCP Selection Meeting
Software Subcontractor
Quality Management Systems – Requirements
ROADMAP TO ISO/TS REGISTRATION
Quality Measurable characteristic Cyclomatic complexity Cohesion
QA Reviews Lecture # 6.
Chapter # 1 Overview of Software Quality Assurance
Managing Project Work, Scope, Schedules, and Cost
DOE Review of the LCLS Project October 2006
System Safety Regulation
Presentation transcript:

Fermilab’s New Quality Assurance Program Irwin Gaines 23-Jan-2008

Fermilab needs a QA Program FRA promised one in their bid for the management contract DOE order 414.1C requires one We have been cited in recent audits for lack of a lab wide QA program The Director wants one Note that a Quality Assurance program is at least as much about A (assurance) as it is about Q (quality)

Creating the new QA Program EG&G wrote an initial draft of the QA plan It was presented to a newly constituted QDT (QA Plan development team) for approval before being sent to DOE at end of December Plan was for team to have 3 4-hour meetings to review and modify plan

But in real life…. Team was violently opposed to many of provisions in draft plan (overly prescriptive, insufficiently flexible, unaware of costs associated with proposed QA controls) Team met 3 full days/wk for 5 weeks and made substantial revisions in plan New draft (still considered a draft) is much improved and is now being shared with division/sections for comment

Basic structure of plan Take credit for all that we already do to assure quality, but strive for more uniformity across lab (especially in documentation and procedures) Graded approach: activity owners will determine what additional QA controls (chosen from standard menu) are appropriate Many “to-be” documents describing lab standard procedures will be developed at appropriate future dates

Sample text from plan This QAP describes the overarching institutional Quality Assurance Program for Fermilab. It is implemented using a graded approach to the application of controls, based on the analysis of risks identified in areas where work is to be performed. This QAP refers to laboratory-wide manuals, policies, and procedures that detail the activities which execute the Fermilab QA requirements. In many cases, these activities are decentralized among the divisions/sections. Centralized implementations will leverage current activities and capture best practices. In cases where the documents do not yet exist, full laboratory-wide implementations will be developed according to a schedule based on availability of resources and perceived benefits. While the ultimate responsibility for ensuring an effective Quality Assurance Program lies with the laboratory director, the responsibility for full and effective implementation of the QA Program is delegated to every employee, user, and subcontractor while conducting work for Fermilab or its customers. (Integrated Quality Management)

To Be Documents contractor assurance plan graded approach procedures managing qualification and training Project mgmt procedure issues tracking procedure process improvement procedure mgmt review procedure document control procedures material control property inventory control policy and procedures FEMP (Fermilab Engineering Manual) corrective action preventive action assessments manual suspect/counterfeit items procedure control of measuring and test equip (?)

Examples of additional QA controls Task specific training Corrective and preventive action plans when defect are discovered Document control with versioning, approval tracking, history Written procedures Monitoring and assessing performance Design authorities for engineering projects Design baselines and design reviews Documented inspection and test plans Formal assessment plans to identify deficiencies and opportunities for improvement

Next Steps Plan will be put into DocDB at conclusion of this meeting Irwin, Bill and Bakul are doing careful read If you have time look it over and send comments to Bakul by close of business Friday She will coordinate division response which is due to Bob Grant by Tuesday next week