1 / 93

NASA/GSFC Safety & Mission Assurance Directorate - A Value-Added Organization

NASA/GSFC Safety & Mission Assurance Directorate - A Value-Added Organization . February 5, 2009. Presented by Mike Kelly, Institutional Support Office, Chief. 8. AGENDA. Safety and Mission Assurance Directorate Organization Charts How Code 300 Organization Interacts with a GSFC Projects

Audrey
Télécharger la présentation

NASA/GSFC Safety & Mission Assurance Directorate - A Value-Added Organization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. NASA/GSFC Safety & Mission Assurance Directorate -A Value-Added Organization February 5, 2009 Presented by Mike Kelly, Institutional Support Office, Chief 8

  2. AGENDA • Safety and Mission Assurance Directorate Organization Charts • How Code 300 Organization Interacts with a GSFC Projects • Code 323, Mission Assurance Branch • Code 324, Institutional Assurance Branch • NASA/GSFC Mission Assurance Approach • Standard MAR • Support at Suppliers • Software Assurance

  3. Agenda (Con’t) • Code 301, System Review Office • Code 302, Institutional Support Office • Supply Chain Management • Introduction to AS9100 Class at GSFC • Lead Auditor Class at GSFC • Code 300 Orientation Program • Code 300 Education Series • GOLD Rules • Supplier Conference at GSFC • Internal Audit Training Program • Mission Operations Assurance

  4. Agenda (Con’t) • Code 300 EEE Parts/Workmanship Group • GIDEP Program • Workmanship Standards/Training • ESD Certification Program • Code 321, System Safety Branch – Safety Program • Typical Safety Deliverables • Code 322, Reliability and Risk Analysis Branch - Reliability and Risk Management Program • Typical Reliability Deliverables • Code 305, Resource Analysis Office • Presenter’s Lessons Learned

  5. GSFC Organization Chart *November 2008 Safety & Mission Assurance Directorate M. So * Safety & Mission Assurance Directorate, Deputy was added.

  6. Safety and Mission Assurance Directorate (Code 300) *(Draft, 02/02/09) (Vacant) (Vacant) * Principal Engineer changed to “Vacant”

  7. Actual Manpower Numbers GSFC Greenbelt: 2957 civil servants GSFC: Greenbelt 5706 contractors supporting the civil servants (FY05) GSFC Safety & Mission Assurance Directorate: 207 total distributed as follows: • 100 contractors • 107 civil servants • 87 permanent • 18 term • 2 co-op • Approximately 100 contractors total from Mantech/SRS and Honeywell

  8. Codes 323/324: Mission Assurance/Institutional Assurance Branches Name: Bob Savage/Rob Sticka Title: Branch Head Office W120/W126D Tel: 68840/69900 Email: Robert.M.Savage@nasa.gov / Rob.Sticka@nasa.gov

  9. SOFTWARE ASSURANCE How Code 300 Organization Interacts With GSFC Projects PROGRAM MANAGER PROJECT QUALITY RESIDENT OFFICE MANAGER ENGINEERING SUPPORT AT TEAM (HW/SW) SUPPLIERS’ FACILITIES Code 320 SYSTEM SAFETY CONTAMINATION ENGINEERING Chief Safety & Mission Assurance Officer Code 321 Code 546 (CSO) RELIABILITY EEE PARTS/ RADIATION ENGINEERING ENGINEERING Code 562 Code 322 Code 561 MATERIALS ENGINEERING Code 541 Code 320

  10. Chief Safety and Mission Assurance Officers (CSO, Code 323, Mission Assurance Branch) Robert Savage, (Branch Chief) • Projects: • POES, Sam Archer-Davies • GOES NOP, Dave Bogart • SAM, Roger Counts • GLORY, Jack Ellis • LDCM, RSDO, Patty Huber • GLAST, James Lohr • NPP, Tim Bowser • TDRSS K, David Smalts

  11. Chief Safety and Mission Assurance Officers (CSO, Code 324, Institutional Assurance Branch) Rob Sticka, (Branch Chief) • Projects: • JWST ISIM, Sue Aleman • MMS, John Blackwood • IBEX/RBSP, Robert Calvo • SDO, Oscar Cheatom • ELC, Joseph Hall • LRO, Ronald Kolecki • LRO/SMAP, Lydia Lee • HST, Lynette Marbley • GPM, John Rauscher • HST, Renee Robinson • JWST, Joe Radich • S/GN/SNE/NIMO/SCiP, Thomas Toutsi

  12. Organization Functions Chief Safety and Mission Assurance OfficerCSO • CSOs assigned to Projects (formerly known as SAMs and FAMs before that) • Co-located with Projects • Reports to Project Manager (dotted line) • Assurance program includes Quality Assurance, Safety, Reliability, Workmanship, Risk Management, Parts, Materials • Reports independently back to Code 300 • Works Project full life-cycle from Concept through Launch • Manages assurance program for both in-house and out-of-house Projects • Generates and implements Mission Assurance Requirements (MAR)

  13. Organization Functions CSOs cont’d • Lead for Problem Report/Problem Failure Report (PR/PFR) System • Lead for Work Order Authorization (WOA) implementation (IAB) • Typically the Project’s ISO 9001 Implementation Manager • Responsible for manufacturing and QA oversight of Project contractors by utilizing: • Defense Contracts Management Agency (DCMA) • NASA Contractor Assurance Services (NCAS) • Code 300 Support Contractors • Works with Systems Safety Engineers to implement project safety program • Works with Reliability engineering to implement project reliability program

  14. Organization Functions CSOs cont’d • Member of Parts Control Board. Works closely with Code 562 Parts Engineers. • Implements Government-Industry Data Exchange Program (GIDEP) compliance and dispositions • Works with Code 541 Materials to determine acceptability of printed wiring boards by coupon evaluation • Ensures parts and materials lists are thoroughly reviewed and acceptable for use. • Coordinates radiation requirements and implementation with Code 561 (Radiation Effects) • Implements Workmanship Standards such as soldering, cabling, harnessing, conformal coating

  15. NASA/GSFC Mission Assurance Approach • NASA Chief Safety and Mission Assurance Officer (CSO) is the program/project focal point and is responsible for supporting the Goddard missions from an End-to-End Perspective which includes Procurement Activities through On-Orbit Operations. • CSO has an independent reporting chain to the GSFC Center Director. • The Mission Assurance Team supports the Program and Project Offices in their daily operations. However, if there are conflicting opinions it is the CSO’s responsibility to report those disagreements to NASA management. (CONTINUED)

  16. NASA/GSFC Mission Assurance Approach • Generally the CSO is co-located with the project office, to provide the most efficient access to the project manager and his staff. It is desirable to have safety and reliability personnel co-located there as well. • CSO must be a good communicator and understand where support is needed and keep the Project in the loop. • CSO walks a fine line between supporting the Project and remaining an independent entity. (CONTINUED)

  17. Chief Safety and Mission Assurance Officers (CSO, Code 323, 324) • CSO duties in support of the Project are as follows: • Voting member of CCB and risk management board • Conduct audits/assessments at hardware developers (and provide follow-up). Responsible for determining mandatory inspection points • Support in resolution of hardware/software problems • Member of Source Evaluation Boards • Member of Senior Staff • Interface for all Printed Wiring Board (PWB) coupons • Point of contact for all manpower in Code 300 • Ensure LOD and LOA (task order) are written and followed to support the project. All task orders are in the Task Order Management System (TOMS). • Attendance and participation at all major reviews • Provide monthly presentations to Code 300 Management • Provide presentations to Project/Program Management as required • Development of Mission Assurance Requirements • Present Safety and Mission Success Review to Headquarters

  18. Standard MAR • In the recent past, the CSO used as a guide the Mission Assurance Guidelines (MAG) Procedure (300-PG-7120.2.2) and consultation with functional disciplines in Codes 301, 302, 320 and other GSFC organizations to develop the MAR for the Instrument, Spacecraft, and Ground System • More recently, a “Standard MAR” began development. This is to be used as a tailoring tool to generate project MARs. • The Standard MAR, including the requirements narrative and DIDs, are available on the Agency's PBMA web site in a community work area called "Goddard Mission Assurance Guide.“ • The current versions of the individual components are available on the web site and are not expected to undergo further revisions. • A controlled version of the Standard MAR has been prepared and is under review in anticipation of being placed under CM in the near future. A new Code 320 PG is being developed to establish relevant procedures and processes for its use.

  19. Support at Suppliers • The work activities performed by the developer and/or his suppliers are subject to evaluation and audit by government-designated representatives. • CSO supports project by selecting on-site supplier representative’s by one of several methods: • (1) a Defense Contract Management Agency (DCMA) person via a Letter Of Delegation (LOD), • (2) an independent assurance contractor (IAC) via a contract • NASA Contract Assurance Services (NCAS) • Code 300 Mission Assurance Support Contract (MASC) • DCMA and NCAS contract employees: • Advantage: Funded by NASA HQ, not by the GSFC Program/Project budget • Disadvantage – Usually working several projects at one time • MASC contract employees: • Advantage - Usually works exclusively on your project • Disadvantage - Costs are directly to the GSFC Program/Project budget

  20. Software Assurance • Our primary objective is to assess program / project products and processes to • assure that programmatic capabilities are achieved. • Software Assurance shall apply to flight and ground system software developed by or for GSFC. • Government off-the-shelf (GOTS) software • Modified off-the-shelf (MOTS) software • Commercial off-the-shelf (COTS) software • Overview • Software assurance comprises a set of disciplines that strive to improve the overall quality of the product/software while employing risk mitigation techniques. • Software Quality Software Safety Software Reliability • Verification and Validation (V&V) • Independent Verification and Validation (IV&V). • SW Quality Assurance Functions: • assures that the standards, processes, and procedures are appropriate for the project and correctly implemented, • assures adherence to those software requirements, plans, procedures and standards, • shall plan and conduct process and product assurance activities throughout the project development life cycle. • Assures compliance to Center Software Process Improvement (SPI) initiatives and performs Product Process Quality Assurance (PPQA) assessments.

  21. Goddard Review ProcessSystem Review Office, Code 301 Name: Mark Goans Title: Office Chief Tel: 301-286-9763 Email: Mark.D.Goans@nasa.gov

  22. Independent Review Process • The Systems Review Office (SRO) is the implementation arm of the GSFC independent review process. • Types of Independent Reviews • Mission Life-Cycle Reviews conducted by Standing Review Board (SRB) / HQ Driven • Reference: NPR 7120.5D NASA Space Flight Program and Project Management Requirements • GSFC Level Independent Reviews conducted by a SRO chartered Review Team • Reference: GPR 8700.4F Integrated Independent Reviews • Engineering Peer Reviews conducted by an independent peer review team • Reference: GPR 8700.6A Engineering Peer Reviews

  23. Project Life-Cycle and Reviews SMSR

  24. Center Level Independent Reviews (1 of 2) • Center Level Independent Reviews comprise life cycle reviews for the Spacecraft(s), Instrument(s), Ground System(s) and Operations. • For larger projects dozens of reviews may be conducted • The SRO convenes review teams to conduct Center Level Independent Reviews • For each project, the SRO assigns a Systems Review Manager (SRM) to serve as the review team chair. • The SRM develops a Systems Review Plan in conjunction with the Project that appropriately tailors the GSFC process to the mission needs. • For each element the SRM establishes an appropriate independent review team with members chosen for their management and technical expertise • The SRM presides at each review and ensures compliance with center-level processes.

  25. Center Level Independent Reviews (2 of 2) • The review team evaluates the project based on compliance with the review objectives and adherence to Key Project Management Practices • Formal Requests for Action or additional information are generated as needed • The review team caucuses and out briefs the project at the conclusion of the review • The SRM provides a report to the Project documenting the review results and makes appropriate recommendations to the GSFC Center Management Council • The SRM provides feedback the to mission SRB (HQ team) regarding key results from Center Level Reviews

  26. Engineering Peer Reviews • Each GSFC flight project is required to develop an Engineering Peer Review Plan • Engineering Peer Reviews (EPRs) are conducted for spacecraft subsystem, instrument component, software and crosscutting functional elements. • The project manager (PM) appoints an independent EPR chairperson for the various elements. • For each element, the EPR chairperson recruits independent review team members based on their technical knowledge and practical experience. • For each review the EPR chairperson provides a report with findings to the PM and the assigned SRM • Engineering Peer Review Results are summarized at the next schedule Center Level Independent Review and/or Mission Life-cycle Review

  27. Institutional Support Office,Code 302 Name: Mike Kelly Title: Office Chief Tel: 301-286-0662 Email: Michael.P.Kelly@nasa.gov

  28. Code 302 Institutional Support Office 1 (02/02/09 tc) Michael P. Kelly Office Chief Regina MartinAdministrative Assistant Lead Systems Engineer *Tom Clifford/SRS NASA/HQ OCE Support G.S. Krishnan (detail to HQ) SMA Configuration Mgmt *Rhonda Weaver/CSC Supply Chain Management Louis Thomas Charles Kim Jonathan Root *V. DiMarco/SRS Mission Ops Support/ Anomaly Management James La *Jim Suraci/SRS *Nicole Smith/SRS GSFC Management System / Internal Audit Lead (VACANT) Darryl Younger (Detail from 500) *Mark Bollard/Honeywell *Linda Emerson/Honeywell Sue Aleman GOLD Rules Management Jerry Kosko Environmental Test Verif & Problem Reporting Analysis Scotty Milne *Contractor Draft 01/16/09 1 Added an internal auditor

  29. Organization Functions • Conducts Supplier assessments • Maintains Records of assessments in GSFC audit database • Sponsors Quality training (e.g. AS9100 quality system, ISO Lead Auditor) • Sponsors suppliers conferences • Is Technical Liaison for NASA Contract Assurance Services (NCAS) • Is Focal Point for Defense Contract Management Agency (DCMA) • Working with NASA Assurance Management Team (NAMT) – all NASA Centers Participation • Working with Joint Audit Planning Committee (JAPC) – Primes and other Government Agencies (NASA, MDA, NRO, and DCMA)

  30. The Assessment Approach/Process NASA Goddard Supply Chain Manager has a large role in the planning of the assessment in order to work issues/concerns upfront He is calling supplier’s to set up the assessments (not NCAS) He is conducting the in-brief when possible to set the proper tone for both the assessment team and the supplier He is attending each out-brief (sometimes remotely) Draft copy of the Supplier’s Assessment Plan is forwarded to the Supplier for their comments and feedback to ensure agreements are reached prior to the assessment No scoring is used during the assessment process Only non-compliances, observations, & commendations and A final out-brief package is left with the supplier at the end of the assessment (CONTINUED)

  31. The Assessment Approach/Process (con’t) • A final report is written and forwarded to the supplier Point of Contact for comment • This report will be a few pages long and will contain the assessment cards and the final out-brief package • NASA/GSFC provides a “Supplier Assessment Team Evaluation Survey Form” to solicit both positive and negative comments about the assessment process and the participation of each assessor • NASA/GSFC does care about the Corrective Actions and wants to work with each supplier to support Closure of each one. • Plan to conduct follow-up assessments if necessary and/or if requested by the supplier (CONTINUED)

  32. Assessment Objectives • Assess the supplier’s processes for compliance to: • the requirements of ISO9001:2000 or AS9100, (if supplier is third party certified, we will assess the supplier to it.) • to the applicable NASA Contractual Requirements, and • to the requirements of the internal Quality Management System. • Follow up on previous NASA assessments • The goal of each assessment is to identify strengths and areas for improvement.

  33. Assessment Reporting • Assessment Team Members will document closed and outstanding non-compliances & observations during the course of the assessment as well as note any observed commendations Critical Noncompliance: Failure to follow requirements that could lead to loss of life, serious injury to personnel, or damage to high-value equipment. Noncompliance: Failure to comply with Federal, State, local, Agency, or Center requirements that would not have the impact of a Critical Noncompliance Observation: A condition that is not contrary to documented requirements, but, in the judgment of the assessor warrants improvement or clarification. Commendation: A process that is considered an industry benchmark by the assessor. • Daily debrief will entail informal discussions of the day’s activities. • Draft copies of Corrective Action Reviews will be provided at the Out-briefing. • A formal report will be provided within 20 working days after the assessment.

  34. Sample Assessment Plan “items to be reviewed” • The following list provides an outline of some of the topics the assessment team will review: • Flowdown of contractual requirements • Receiving inspection • Configuration Management / Change Control • Packaging • Handling • Parts sampling, selection, and traceability • Training and Certification of operators/inspectors/disposition authorities/testers • Process documentation adequacy (work orders, shop aids, drawings, etc.) • Document control • Workmanship and inspection • Travelers, routers and configuration recording • Nonconforming product control • Scrap control • Rework and repair processes • Acceptance Data Packages • Problem Reporting System • Internal Audit • Calibration • GFE • Industrial Safety • System Safety • GIDEP

  35. Management One-Pager The following chart is a sample assessment “One-Pager” that is presented to Code 300 management after each assessment.

  36. NCAS Supplier Assessment SummarySupplier XYZCity, State September 18-20, 2007 • Products • Developer of processors, command and data handling systems, and related electronics for space flight. Expertise in planetary and space science instrument design and fabrication and data systems development. • Centers/projects which may be impacted (if known) • GSFC Project A, JSC Project B, JPL Project C Summary of Issues Identified • No evidence that SAM and/or SSM had reviewed & approved PAIPs and Safety Plan. • GSFC approval for PWB coupon evaluations not required by Mission PAIP. • Missing and/or lost test & measuring devices. • Software Reliability plan not developed, and S/W risk prediction not calculated. • QMS not fully compliant with ISO Q9001,i.e., Continual Improvement, Customer Satisfaction, Analysis of Data, Management Responsibility. • No continual process (semi-annual only) for addressing vendors falling below 80% rating. • Training not performed in accordance with developed training procedure.

  37. Supplier Assessments - Non-Code 302

  38. How to Obtain all NASA/GSFC Assessments Reports

  39. GSFC Audit Database Link http://auditsystem.gsfc.nasa.gov Civil Servants Click here. Non-civil-servants do not have access to Supplier records.

  40. Introduction to AS9100 Class at GSFC (01/22/09) • Civil servants and contractors are invited to attend a class presenting the requirements of Aerospace Standard AS9100 and ISO 9001/2000.  • The class is sponsored by Mike Kelly, Supply Chain Manager for the Safety and Mission Assurance Directorate.  • Presented by DCMA Headquarters Representatives, Gil Kimbrough and James Rodden • The course is an in-depth overview of requirements, organization, structure, and use of the Quality Management Standard (agenda is available per request). Contact (301) 286-4333, ckim@mscmail.gsfc.nasa.gov • The objective is to give the student a working knowledge and auditing skills of the International Organization for Standardization (ISO) Quality Management Standard (QMS) for the year 2008 and AS9100 Aerospace requirements. • The room can accommodate 25 to 30 persons and spaces will be reserved on a first-come, first-served basis. • Where:  Goddard Spaceflight Center or vicinity. • When:   Eighth class is scheduled for February 17-19 2009, Tuesday through Thursday.  Class starts at 8am.

  41. Lead Auditor Class at GSFC • Civil servants and contractors are invited to attend a class ….  • The class is sponsored by Mike Kelly, Supply Chain Manager for the Safety and Mission Assurance Directorate.  • Presented by Plexus Corporation • The course is an in-depth overview of requirements, organization, structure, and use of the Quality Management Standard (agenda is available per request). Contact (301) 286-4333, ckim@mscmail.gsfc.nasa.gov • The course provides either new or current aerospace auditors with an understanding of the AS9100 standard, the process approach of ISO 9001:200, and how the process approach impacts auditing practices. The course includes a simulated audit to develop and refine newly acquired knowledge and skills including the application and evaluation of a process based quality management system. A successful completion of Plexus Corporation’s program meets the training requirements for certification of individual QMS Auditors and Aerospace Auditors. • The class can accommodate 10 persons. • Where:  Goddard Spaceflight Center or vicinity. • First class occurred:   May 19 - 23, 2008 • Another class is planned for all Directorates personnel. Date is TBD.

  42. Code 300 Orientation Program Code 300 Orientation FINAL Agenda B6 - S019: October 22, 2008

  43. Code 300 Education Series (01/22/09) A series of presentations being sponsored by SMA-D in support of communication and outreach initiatives identified in NASA's Strategic Plan.  The intent of the series is to foster a greater understanding of key NASA activities, functions, and processes. • 1st session: Bryan O’Connor presented "Quality & NASA" on July 28, 2008. • 2nd session: Safety and Mission Assurance Directorate (SMA-D, Code 300) welcomed Mr. Gregory Robinson on September 30, 2008. Mr. Robinson is a NASA Ambassador supporting the Office of Chief Engineer, NASA HQ. • He presented “Systems Engineering, with Quality”. • NPR 7123.1A: Impacts of the Implementation Architecture, SE Engine, & Application.  • Forty attended in Building 8 auditorium. • This was the second in   • 3rd session: The third session addressed NPR 7120.5 D, “Program and Project Management” and the impact on mission success. • Presented by Michael Blythe, NASA HQ, January 9th (CONTINUED)

  44. Code 300 Education Series (con’t) (01/22/09) • Topic #4: “SMARTS” • An internet-based information system designed to: • Collect all SMA policy and procedural requirements at the Agency and Center levels and from appropriate sources external to NASA • Support research into SMA requirements by providing a means to filter, collect, search, and sort requirements into “virtual” documents to meet specific needs • Support the data associated with the verification of compliance to SMA requirements • Support maintenance and development of new SMA policy and implementation documents/requirements • Trace links of SMA requirements to improve effectiveness and help limit duplication of requirements • Presentation by John Lyver, NASA HQ, Date: 18 February 09, 1-2:30 p.m., in Bldg 26, Room 205 • Also tied into NASA’s Supplier Assessment System (SAARIS) • Proposed Topic #5 • Procurement & Quality • Specific topic under review with James Becker • Presenter/Date TBD • Future Topics • Plan to pursue topics to be presented by QED-related Vendors and Aerospace Corp.

  45. GOLD Rules • Goddard Open Learning Design http://gsfcrules.gsfc.nasa.gov • Rules for the Design, Development, Verification, and Operation of Flight Systems, (GSFC - STD - 1000) • The Rules are a high-level subset of all the design rules required for safety and mission success for all space flight products regardless of implementation approach. All products shall be designed, developed, verified and operated in accordance with the GSFC Rules. • The rationale is based on sound engineering practice, systems management principles, or lessons learned; and • A systems engineering product or other objective verification method is identified at one or more milestones in the project life cycle. • Each "Gold Rule" includes a Principle, Rationale, and Activities and Verification by phase. • Code 500 ‘owns’ the Rules. • Code 300 hosts the server, involved in all waiver approvals, and currently updating the GPG. (CONTINUED)

  46. GOLD Rules screenshot

  47. Supply Chain 20082nd Annual NASA Supply Chain Quality Assurance ConferenceOctober 28-30, 2008 @ NASA’s Goddard Space Flight Center (10/02/08 jr) • Go to http://supplychain.gsfc.nasa.gov for agenda, online registration and other conference information • Outstanding interest with 165 attended. • Unique gathering of leaders and practitioners from aerospace industry, suppliers and across NASA, including: GSFC, JPL, JSC, KSC, NASA Headquarters,Hamilton Sundstrand, Space land & Sea, Mantech/SRS, Johns Hopkins University Applied Physics Laboratory, Lane Industries, Inc., Goodrich ISR Systems, SGT, Inc., ITT Space Systems Division, REI Systems, Inc., Honeywell Technology Solutions, Inc., ATK - Tactical Propulsion and Controls Elkton Division, ITT Space Systems Div., DCMA, Ball Aerospace & Technologies Corp., University of Bradford/UK, Lockheed Martin Space Systems Company, Space Dynamics Laboratory/USURF, Boeing Space and Intelligence Systems, Moog Inc. Space and Defense Group, Ball Aerospace & Technologies Corporation, Northrop Grumman Technical Services, General Dynamics C4 Systems, Raytheon Vision Systems, Raytheon Missile Systems, Harris Corporation, SSG-Tinsley, MIT Lincoln Laboratory, ITT Industries Space Systems, LLC, PolarOnyx, Inc., aPeak Inc, Qualtech Systems, Inc., Orbital Sciences Corporation, Diamond Materials, Inc., Pratt Whitney Rocketdyne, Advanced Power Solutions, Inc., The Aerospace Corporation, Advanced Cooling Technologies, Comet Technology Corporation, Raytheon Information Systems, MDL Manufacturing Industries, Inc., L-3 Communications SSG-Tinsley Inc., TRAX International, Booz Allen Hamilton, Inc., Applied Biomathematics, Southwest Research Institute, Co-eXprise, Aerojet, NOAA, MDL Manufacturing Industries, Missile Defense Agency, Syneren Technologies Corporation • Hosted by the Institutional Support Office, Safety and Mission Assurance Directorate, GSFC (CONTINUED)

  48. GSFC Management System • Moving from ISO 9000 to AS9100 • “Compliance” only, Not “certification” • Goddard Directives Management System (GDMS) • Lab Management GPR and Training Program

  49. Number of Internal Audits (02/02/09) * Excludes DNV/NQA and external audits

  50. Internal Audit Training April 08, May 08 and September 08 • Training opportunity for current Goddard internal auditors and auditor candidates • Experienced lead auditors from the Supply Chain Assessment Team provided training and mentoring (Charlie Robinson and Larry Oien) • Auditors were from Honeywell • Part of the NASA Contract Assurance Services (NCAS) contract • Free service for GSFC (Headquarters Funded) • Visited labs in eleven buildings • Verbal results were provided prior to leaving the lab and at the daily outbriefs. • Written results were provided to each lab point of contact. • Follow-up assessments will be coordinated as-needed February 3, 2009 50

More Related