1 FCAP Review Comments and Responses – 05/13/08 Fermilab Contractor Assurance Program Ed Vokoun EG&G Sr. Logistics Manager at Fermilab.

Slides:



Advertisements
Similar presentations
Course Material Overview of Process Safety Compliance with Standards
Advertisements

EMPLOYEE GRIEVANCE POLICY SUMMARY FACTS Goals of the Employee Grievance Policy: Provide procedural consistency across the agencies and universities of.
Centralization vs Decentralization County General Services Association April 3, 4 and 5, 2013.
Chapter 2 Analyzing the Business Case.
Contractor Assurance System AC Overview October 13, 2009.
How to Document A Business Management System
Documenting Disciplinary Issues
Assurance Council Brief Status of QA Implementation at Fermilab Tuesday Nov 11, 2008 Jed Heyes.
Page 1 National Defense Industrial Association (NDIA) Program Management Systems Committee (PMSC). NDIA Earned Value Management Systems Intent Guide Overview.
Membership and Personnel Requirements for VCA Programs (Resolution 27) Vascularized Composite Allograft (VCA)Transplantation Committee Sue V. McDiarmid,
Overview Lesson 10,11 - Software Quality Assurance
Experimental Psychology PSY 433
Chapter 3 The Structure of the CMM
Office of Inspector General (OIG) Internal Audit
RC14001 ® Update GPCA Responsible Care Committee September 23, 2013.
 A written document that specifies how, where, and to whom a business plans to market its product(s) and/or brand(s).  A small business typically creates.
1 © 2003 Cisco Systems, Inc. All rights reserved. Session Number Presentation_ID Cisco Technical Assistance Center (TAC) TAC Service Request Tool Overview.
Key changes and transition process
Typical Software Documents with an emphasis on writing proposals.
Developing an accessibility strategy. In this talk we will discuss an accessibility strategy an accessibility policy getting started - steps to consultation.
Gerson & Gerson: Technical Writing, 5th Edition© 2006 Pearson Education, Upper Saddle River, NJ All Rights Reserved. 1 Chapter 17: Proposals This.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
Implementing the New Reliability Standards Status of Draft Cyber Security Standards CIP through CIP Larry Bugh ECAR Standard Drafting Team.
Information Assurance The Coordinated Approach To Improving Enterprise Data Quality.
Standards for Internal Control in the Government Going Green Standards for Internal Control in the Federal Government 1.
Doc.: IEEE /0003r0 Submission January 2013 S. Filin H. Harada, NICTSlide 1 Introduction to Contributions Notice: This document has been prepared.
Writing the Introduction to the Study Dissertation Editors Writing Center.
National Commission for Academic Accreditation & Assessment Developmental Reviews at King Saud University and King Faisal University.
11 FSO Assessment of Fermilab QA Program Status September 14 – 18, 2009.
4.3 Document control 4.4 Review of requests, tenders and contracts
Public Health Reporting Initiative Stage 3 Sprint: Implementation Guide Development Phone: x
Take Charge of Change MASBO Strategic Roadmap Update November 15th, 2013.
QUALITY MANAGEMENT STATEMENT
Chapter 9: Introduction to Internal Control Systems
University Senate Faculty Handbook Review Committee April 2, 2013.
ECOS Information Session Draft EPA Quality Documents February 13, 2013 Presented by EPA Quality Staff, Office of Environmental Information For meeting.
WG or TG # SC17 Liaison Report Mohsen Shavandi / Virgilio Garcia Soulé SC17 Liaisons Update from SC18 Summer 2013 Meeting January 2014.
Page 1 | Proprietary and Copyrighted Information Structure of the Code Don Thomson, Task Force Chair IESBA Meeting New York, USA November 30 – December.
TTI Performance Evaluation Training. Agenda F Brief Introduction of Performance Management Model F TTI Annual Performance Review Online Module.
Page 1 | Proprietary and Copyrighted Information Part C Jim Gaa, Chair Part C Task Force IESBA Meeting December 2, 2015 New York.
Update: AUL Guidance Revisions Summary of Comments June 23, 2011 Peggy Shaw Workgroup Chair.
Doc.: IEEE /0281r1 Submission James D. Allen (Appairent Technologies, Inc.) Project: IEEE P Working Group for Wireless Personal Area Networks.
Project Discovery – Monday Holyoke 561 Most updates will only have 30 minutes maximum for their presentations. At least 10 minutes should be left for Q&A.
Page  ASME 2013 Standards and Certification Training Module B – Process B7. The Appeals Process.
DOCUMENTATION ISO/IEC 17025:2005 Documentation.
Planning and Organizing Chapter 4. The Planning Function Business Plan – a written description of the nature of the business, its goals, and objectives,
JOB DESCRIPTIONS 1. Overview Regardless of the size or complexity of an organization, good job descriptions are vital management tools and important documents.
A LOOK AT AMENDMENTS TO ISO/IEC (1999) Presented at NCSLI Conference Washington DC August 11, 2005 by Roxanne Robinson.
ANNUAL PRODUCT REVIEW Patchara Kootiratrakarn Independent consultant.
Software Quality Control and Quality Assurance: Introduction
Security Management: Successes and Failures
ECE361 Engineering Practice
Enterprise Content Management Owners Representative Contract Approval
Structure of the Code – Phases 1 and 2
Description of Revision
Working Title Guidelines
Structure of the Code – Phase 2 TF Comments and Proposals
Structure of the Code Phase 1
Quality Management at the Engagement Level Proposed ISA 220 (Revised)
EMPLOYEE GRIEVANCE POLICY SUMMARY FACTS
Structure–Feedback on Structure ED-2 and Task Force Proposals
CBP Biennial Strategy Review System
Competency and Competency Analysis
TGn Editor – Adrian Stephens
Larry Bugh ECAR Standard Drafting Team Chair June 1, 2005
Inclusive Excellence Grants for Faculty and Graduate Students
QA Reviews Lecture # 6.
Requirements Document
TECHNOLOGY ASSESSMENT
1915(c) WAIVER REDESIGN 2019 Brain Injury Summit
Presentation transcript:

1 FCAP Review Comments and Responses – 05/13/08 Fermilab Contractor Assurance Program Ed Vokoun EG&G Sr. Logistics Manager at Fermilab

2 FCAP Review Comments and Responses – 05/13/08 Agenda Past and Next Steps Comment Resolution Process Comments and Responses

3 FCAP Review – History and Path Forward  Rough draft document written and reviewed 04/01/08  Edits made and draft distributed to AC04/08/08  Comments due 04/15/08  Comments review and presentation to AC04/21/08  Additional comments due by05/27/08  Comments review and resolution response06/03/08  Meet if necessary to resolve comments06/10/08  Distribute final review document06/17/08  Final review comments or sign-off due07/08/08

4 FCAP Review – Comments Review and Resolution Process  Review comments  Determine response/action  Edit, no change or different change  Response with reason  Review proposed responses with Bob Grant And Bruce Chrisman  Respond to person providing comments  If resolution not accepted, meet with Bruce, Bob and commenter  If fundamental issue needing larger group buy-in, meet with AC  If impasse, Bob and Bruce decide

5 FCAP Review Comments – 04/21/08  General comment:  Assurance Representative (AR) role Vs system(s) requirements and QAR  Staffing for the role…  Determining major processes  Response:  AR role is a lot of what you do today.  QAR role description applies to a specific management system, Quality.  AR role applies across all systems in this order.  The FCAP only shows the common AR responsibilities necessary for all management systems.  Resource requirements will be defined in the implementation plans.  Decision on which processes get graded is determined by Graded Approach Procedure and a definition of “major processes”.

6 FCAP Review Comments – 04/21/08  General comment:  Include Finance and other business operations systems now?  Response:  Finance/Business Operations is not required by order 226.1A.  Recommend the approach should be compliance first and then enhanced control.

7 FCAP Review Comments – 04/21/08  General comment:  Should we list our external reporting requirements in an appendix?  Response:  Recommend this is not done.  Creating a separate list outside of the FCAP document would be a useful tool and should be done.

8 FCAP Changes – 04/21/08  Comment: Overview – Introduction, paragraph 5, sentence 1:  Delete word “assurance” in order to place emphasis on all contractor systems not just assurance system.  Comment: Overview – Introduction, paragraph 6, sentence 1:  Add word “system” in order change emphasis from management to management system.  Comment: Overview – Purpose:  Add word “systems” in order change emphasis from management to management system.  Response to above:  Done

9 FCAP Changes – 04/21/08  Comment: Overview – Attributes of an Effective Assurance Program:  Add an introductory sentence to clarify or emphasize why section is included and/or intent.  Response:  Done

10 FCAP Changes – 04/21/08  Comment: Overview – Attributes of an Effective Assurance Program:  Continual Improvement, last sentence: Need to define “significant”.  Response:  Done; changed wording to include definition as part of sentence and replaced the word significant.

11 FCAP Changes – 04/21/08  Comment: Program – Introduction, paragraph 1, sentence 1:  Need to define “highest quality”.  Response:  Done; replaced the word highest and added the perspective in which to view quality, the customer’s.

12 FCAP Changes – 04/21/08  Program – Organizational Structure, Section 1.1, paragraph 5:  Change Internal Audit reporting to show administrative and functional reporting structure.  Response:  Done

13 FCAP Changes – 04/21/08  Comment: Program – Organizational Structure, Section 1.3:  Add “Centers” to title, Division/Section,  Response:  Done  Check remainder of document for consistency. Done – Also, document will be reviewed by the Technical Editor.

14 FCAP Changes – 04/21/08  Comment: Program – Personnel Responsible for Management and Assurance Systems, Section 1.5.3:  Add “Property Management”.  Response:  Done

15 FCAP Changes – 04/21/08  Comment: Planning, Section 5.3, paragraph 1:  Change DOE High Energy Physics Advisory Panel to Directors Physics Advisory Committee.  Response:  Done

16 FCAP Changes – 04/21/08  Comment: Planning, Section 5.3, paragraph 2:  Place emphasis on DOE Business Plan being strategic and PEMP being tactical and note they are done at different points in time  Business Plans are typically done a year in advance.  Response:  Done

17 FCAP Changes – 04/21/08  Issue: Reporting - Responsibilities, Section 6.2  Capitalize “C” in title, …Chair of the AC.  Response:  Done  Check for others in document. Done – Also, document will be reviewed by the Technical Editor.

18 FCAP Changes – 04/21/08  Comment: Reporting - Responsibilities, Section 6.2  Potential issue: Verify Facility Manager role versus reserved definition from DOE orders and Randy’s job title.  What is intended use in the FCAP? Clarify or determine if there is a need to change.  Response:  Decision by Fermilab management was to leave document as is, because Randy reports to COO.

19 FCAP Review Changes – 04/21/08  Comment: Employee Concerns Process, Section 8.3.2:  Should we include internal “Action Line”, x4000?  Response:  Decision by Fermilab management was to include X4000 and have phone message updated to indicate relationship to program.

20 FCAP Review Changes – 04/21/08  Comment: Issue Management - Responsibilities, Section 9.5  Opportunity to elaborate on DOE O 226.1A, Attachment 1, Appendix A, page A-5, points  Response:  No change done at this time.  “To BE” document for corrective action and preventative action procedure will be created per FIQMP.