Dan Conlon 951.273.5210 2008 Auditor Workshop “Output Matters” 14 July 2008.

Slides:



Advertisements
Similar presentations
AWARENESS OF ISO 9000 (2000) By C. Das Additional Director
Advertisements

EMS Checklist (ISO model)
Configuration Management
Checking & Corrective Action
1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
ISO 9001:2000 Documentation Requirements
Transition from Q1- 8th to Q1- 9th edition
Understanding the Requirements Qimpro Standards Organization
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
First Article Inspection Report
ISO 9001 : 2000.
SAE AS9100 Quality Systems - Aerospace Model for Quality Assurance
The ISO 9002 Quality Assurance Management System
Quality Management System
GLAST LAT ProjectLAT Engineering Meeting, April 1, 2003 GLAST Large Area Telescope: Performance & Safety Assurance Darren S. Marsh Stanford Linear Accelerator.
ISO 9001 Interpretation : Exclusions
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
GLAST LAT ProjectTEM &TEM-PS Manufacturing Readiness Review – September 16, 2004 GLAST Large Area Telescope: Performance & Safety Assurance Pat Lujan TEM.
Prepared by Long Island Quality Associates, Inc. ISO 9001:2000 Documentation Requirements Based on ISO/TC 176/SC 2 March 2001.
External Defibrillators: Recalls, Inspections, and the Quality System Regulation Melissa Torres Office of Compliance December 15, 2010.
ISO 9000 Certification ISO 9001 and ISO
QMS ISO 9001:2008 Introduction to QMS 9001:2008 and system auditing.
4. Quality Management System (QMS)
4. Quality Management System (QMS)
© 2009 Michigan State University licensed under CC-BY-SA, original at Corrective Action.
Effective Methods for Software and Systems Integration
University of Sunderland CIFM03Lecture 3 1 QMS / Standards CIFM03 Lecture 3.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Chapter 16 Software Quality Assurance
Quality Management Systems P.Suriya Prakash Final Mech Vcet
MethodGXP The Solution for the Confusion.
Introduction to ISO New and modified requirements.
Software Engineering Term Paper
Standard WBS Version 1.0 WBS2-3.pptPage 1 Standard Work Breakdown Structure Legend = Decomposes to lower level WBS elements 4.0 Implementation 4.0 Implementation.
ISO 9001:2000 QUALITY MANAGEMENT SYSTEM REQUIREMENTS
Software Quality Assurance Lecture 4. Lecture Outline ISO ISO 9000 Series of Standards ISO 9001: 2000 Overview ISO 9001: 2008 ISO 9003: 2004 Overview.
From Research Prototype to Production
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Introduction to ISO 9001:2000.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
ISO / IEC : 2012 Conformity assessment – Requirements for the operation of various types of bodies performing inspection.
July LEReC Review July 2014 Low Energy RHIC electron Cooling Edward T. Lessard ESHQ.
Paul Hardiman and Rob Brown SMMT IF Planning and organising an audit.
QUALITY MANAGEMENT STATEMENT
It was found in 1946 in Geneva, Switzerland. its main purpose is to promote the development of international standards to facilitate the exchange of goods.
The Second Annual Medical Device Regulatory, Reimbursement and Compliance Congress Presented by J. Glenn George Thursday, March 29, 2007 Day II – Track.
Internal Auditing ISO 9001:2015
1 Lecture 12: Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
Checking and Corrective Action EPA Regions 9 & 10 and The Federal Network for Sustainability 2005.
Most Common Deficiencies Cheryl O. Morton Managing Director, AIHA Laboratory Accreditation Programs, LLC.
MDA Supply Chain Initiatives Presentation to GSFC Supply Chain Conference Ed Jopson MDA/QSI Division Chief 28 October 2008 DISTRIBUTION STATEMENT A. Approved.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Collaborating for Quality Quality Assurance (QA) & Quality Control (QC) in the Accelerator Project (ACCSYS) Matthew Conlon ACCSYS QA/QC
WORKSHOP ON ACCREDITATION OF BODIES CERTIFYING MEDICAL DEVICES INT MARKET TOPIC 9 CH 8 ISO MEASUREMENT, ANALYSIS AND IMPROVEMENT INTERNAL AUDITS.
Technology Services – National Institute of Standards and Technology Conformity Assessment ANSI-HSSP Workshop Emergency Communications December 2, 2004.
Collaborating for Quality through the Project Quality Plan Matthew Conlon ESS ACCSYS QA/QC Quality Learning & Planning.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Software and Systems Integration
External Validation of Quality Programs
ارائه كننده : محمودرضا طاهري
UNIT-6 SOFTWARE QUALITY ASSURANCE
Quality Management Systems – Requirements
ISO 9001 Awareness Training.
ISO 9000 Dr. S. Thomas Foster, Jr..
First Article Inspection
How to conduct Effective Stage-1 Audit
External Validation of Quality Programs
Presentation transcript:

Dan Conlon Auditor Workshop “Output Matters” 14 July 2008

2 Agenda AS9100 Importance to MDA MDA Assurance Provisions (MAP) MDA Audit Process AS9100 Findings Analysis Examples of AS9100 Audit Findings Common AS9100 Issues How You Can Help Conclusion

3 AS9100 Important to MDA AS9100 is a key QMS document – MDA Core standard The MAP builds on AS9100 requirements/disciplines to create a very rigorous set of QMS implementation requirements MAP includes additional Quality, Safety, and Mission Assurance (QSMA) disciplines for developing mission and safety critical items such as: –Systems Engineering –Reliability, Maintainability, and Availability –Parts and Materials Management –Software –Risk Management –Configuration Management –Safety and Environmental Management –Interface Management

4 MDA Assurance Provisions (MAP) A standardized set of 14 QSMA provisions, requirements, and processes for mission and safety critical items: –Authored by joint Gov/Industry Team –Goal is to implement on all MDA contracts –160 pages, shall statements Provide methods to measure, verify, and validate mission success through: –Collection and analysis of metrics –Risk Assessment, technical evaluations, independent assessment, reviews –Conduct of qualification, ground, and flight tests Promote continual process improvement to ensure QSMA, reduce cost, and improve productivity Proven Mission Assurance Requirements on Contracts MDA Assurance Provisions (MAP) 3.1 Management 3.2 Design and Development 3.3 Software and Firmware 3.4 Technical and Mission Assurance Reviews 3.5 Reliability, Maintainability, and Availability 3.6 Parts and Materials Control Program 3.7 Integrated Test and Evaluation Program 3.8 Test, Meas., and Diagnostic Equip. & Stds. 3.9 Interface Management 3.10 Configuration Management 3.11 Control of Nonconforming Items & Materials 3.12 Fabrication and Quality 3.13 Supplier Management 3.14 Safety

5 MDA MAP Program Usage As part of the MDA Acquisition Strategy the MAP was developed for MDA Program Office implementation and flow down to prime contractors and suppliers –Use existing processes, when adequate, to achieve and sustain mission success –Tailored by the MDA Program Offices for each program –Further tailored for subsystem components through supplier management Implementation of MAP (including AS9100) assessed via: –Mission Assurance audits –Supplier audits –On-Site Mission Assurance Representatives (MARs) –Focus Teams – (VAFB Flight Test Team, PMRF, NGST)

6 Why Audit? QS Organization founded in Late 2002 Majority of Failures Were Lack of Process Discipline Aegis NMD/GMD THAAD FM-5 6/03FTR-1 7/00 IFT-01 1/97 IFT-04 1/00 IFT-05 7/00 IFT-10 12/02 IFT-13c 12/04 IFT-14 2/05 FT-07 3/97 FT-08 5/98 FT-09 3/99 No Interceptor Failures BV-2 8/01 BV-3 12/01BV-5 1/04 22 Flight Test / 10 Failures (45% failure rate) 32 Flight Test / 4 Failures (13% failure rate) 17 Flight Test / 0 Failures (0% failure rate) First MDA/QS Mission Assurance Audit performed

7 GMD Flight Test-03a 28 Sept 07 Engages -Target launch from Kodiak -Interceptor launched VAFB -In midcourse phase of flight -EKV discrimination

8 MDA QS Audit Program Purpose –Conduct Mission Assurance audits of MDA prime contractors and suppliers MDA Audit Objectives –Validate that the end item at a selected level conforms to engineering design requirements –Validate that the end item at a selected level is qualified –Compare fabrication methods and acceptance test levels against MDA and industry standards as appropriate for MDA use –Validate production readiness –Assess contractor/government Mission Assurance practices, procedures, and implementation MDA Audit Findings –Deficiency - a non-compliance to a contractual requirement or internal procedure/process Includes AS9100 deficiencies (if AS9100 is on contract or if audit site is certified or compliant) –Observation - when an MDA or Industry “best-practice” should be used

9 All MDA Audits CY05-CY08

10 AS9100 Findings

11 Analysis Majority of MDA deficiencies can be tied to an AS9100 element AS9100 related deficiencies are primarily in the following areas: –Production and Service Provision: Quality Records, Procedural Discipline, Foreign Object Debris/Damage (FOD), and Electrostatic Discharge (ESD) –Documentation Requirements: Control of Documents (Change and Approval), Quality Management System Records –Purchasing: Supplier Requirements Flow Down, Supplier Rating System –Design and Development: Inputs/Outputs, Traceability, Design Reviews, Design Verification/Validation –Control of Monitoring and Measuring Devices: Design and Selection, Calibration, and Tool Control –Planning of Product Realization: Establishment and Documentation of Processes –Control of Nonconforming Product: Nonconformance Disposition and Nonconforming Material Identification and Segregation

12 Finding Examples Production and Service Provision, AS9100, paragraph 7.5 –Drawing parameters and/or pass/fail criteria were not accurately represented in the build paper. –Foreign Object Debris/Damage (FOD) was found in the Building Powder Blend Area. –Limited life materials were expired and available for use in the production of deliverable hardware. –Electrostatic discharge equipment continuity and environmental limits are not adequately controlled in the Bonded Stores and Electrical Inspection Areas. –Desiccant used to minimize moisture in motor manufacturing is not used per Manufacturing and Inspection Records (M&IR) or drawing requirements. –Preventive Maintenance Work Orders are not verified and Repair Work Orders are not generated to correct deficiencies.

13 Finding Examples Documentation Requirements, AS9100, paragraph 4.2 –The audited program did not implement enterprise company practices for requirement traceability, and did not have an approved process for the unique implementation of their particular practices. –X-Ray inspection procedures are not controlled. –Changes to a Mix and Cast Building checklist were not approved before use. –Receiving Inspection Records were missing required documentation (Inspection report, Government Source Inspection Stamp, Material Certification). –The contractor could not provide supporting information that correlated or related to waivers and deviations. –Uncontrolled and improperly marked documentation were posted in the Process Control Lab.

14 Finding Examples Purchasing, AS9100, paragraph 7.4 –Parts that did not comply with all supplier quality assurance requirements were accepted at Receiving Inspection. –The contractor’s Approved Vendor List does not include some vendors and does not reflect the vendor’s quality rating. –The prime contractor Statement of Work imposes an incorrect quality requirement. –The contractor did not impose core quality requirements (corrective action system, inspection procedures, and quality records) on suppliers. –The contractor accepted a supplier certificate of analysis that certified material for a storage temperature in conflict with the material specification.

15 Finding Examples Design and Development, AS9100, paragraph 7.3 –Contractor Automated Test Station configuration identification does not reflect the current approved configuration. –The contractor does not have a formal process for documenting and tracking design review action items and responses. Control of Monitoring and Measuring Devices, AS9100, paragraph 7.6 –Calibrated equipment at a work station in the Destructive Lot Acceptance Test Area had broken integrity seals. –Test and Measuring Equipment with expired calibration was in the receiving inspection area.

16 Finding Examples Planning of Product Realization, AS9100, paragraph 7.1 –The contractor’s software development practices were not documented and were dependent on the cognizant engineer. –The mass test limit for the Inertial Measurement Unit was incorrectly noted on the test sheet in the Engineering Note Book. Control of Nonconforming Product, AS9100, paragraph 8.3 –The contractor processed “Use as Is” dispositions for hardware without proper review and approval, including the customer. –Undocumented items (various mechanical, electrical and optical parts) were noted in the bonded Material Review Board lockers and cages which appear to be scrap.

17 Common AS9100 Issues Interpretation varies between contractors and government organizations –AS9100 Paragraph , Production Documentation: Production operations shall be carried out in accordance with approved data MDA Interpretation: Mission and Safety Critical processes shall be carried out in accordance with approved detailed plans and procedures –AS9100 Paragraph 8.3, Control of Nonconforming Product: The organization shall ensure that product that does not conform to product requirements is identified and controlled to prevent its unintended use or delivery MDA Interpretation: Nonconforming product is conspicuously identified (tagged), segregated, and retained in a hold status until dispositioned by formal review process –AS9100 Paragraph 4.3 Configuration Management: The organization shall establish, document and maintain a configuration management process appropriate to the product. NOTE: Guidance on configuration management is given in ISO MDA Interpretation: A formal Configuration Management Program includes: a CM Plan which addresses Configuration Planning, Configuration Identification, Configuration Change Management (Waivers/Deviations), Configuration Status Accounting, Configuration Verification / Audit, and CM of Digital Data

18 Common AS9100 Issues Continued Compliance and interpretation varies from contractor to contractor –Some contractors manufacture mission and safety critical hardware per an approved drawing, while others use an approved drawing, traveler, and detailed procedures –Contractors advertise AS9100 Certification, however, implementation varies based on programs and funding Certification achieved at division level, but not implemented across all programs –MDA experience: Many contractors have stated that AS9100 requires them to have a documented system, but the documented system does not have to be effective or implemented for compliance.

19 AS9100 How You Can Help Strengthen Implementation Requirements –MDA experience: There is a gap between system assessment and implementation. AS9100 certification should include assessment of critical processes and the associated detailed planning and procedures. Audit/Assess MDA Programs as part of Certification –Identify MDA Programs with MAP on Contract –Assess effectiveness of Corrective Actions from MDA Audit Findings –Provide feedback for high risk MDA Suppliers

20 Conclusion Majority of MDA deficiencies can be tied to an AS9100 Element Most audit findings are violations of internal processes –Not following their own procedures or processes Our audits have indicated gaps in PDCA implementation –Most sites do the “Plan” portion –They do less well with the “Do” portion –Even do less well with the “Check” portion –Most “Act” actions are short term, focusing on immediate fixes rather than well thought out long term actions that address systemic issues and improve performance across the enterprise Output of Requirements Must be Defined

Backup

22 MDA Audit Findings MAP to AS9100 Correlation Nonconformances