Update MRL Matrix to address STE/SIE Validation Steve Watts AMRDEC 256-876-3244 22 Sep 15.

Slides:



Advertisements
Similar presentations
Transition from Q1- 8th to Q1- 9th edition
Advertisements

PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 110/17/2014 V1.
Ensure Vendor/Engineer of Choice Product Quality
COST CONTROLS OF CAPITAL COSTS THROUGHOUT THE DESIGN PHASE Presented by Planning & Management Services, Inc Federal Way, WA (near Seattle) Western Winter.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
EPSON STAMPING ISO REV 1 2/10/2000.
DoD Information Technology Security Certification and Accreditation Process (DITSCAP) Phase III – Validation Thomas Howard Chris Pierce.
Documentation Testing
FAA Workshop on Key Characteristics for Advanced Material Control
System Safety & Mission Assurance (SS&MA) for Sub-Class D Missions Steve Jara NASA Ames System Safety & Mission Assurance Division.
Introduction to ARA’s Proposal Resources Don Cole
Systems Engineering Management
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
IV&V Facility Model-based Design Verification IVV Annual Workshop September, 2009 Tom Hempler.
ISO 9000 Certification ISO 9001 and ISO
Software Engineering Institute Capability Maturity Model (CMM)
Introductions Jim Enzinna, Chief, Licensing Division Mark DiNapoli, Assistant Chief, Licensing Division Tracie Coleman, Head, Information Section Vince.
This material was produced under grant number SH SH-1 from the Occupational Safety and Health Administration, U.S. Department of Labor. It does not.
Hartley, Project Management: Integrating Strategy, Operations and Change, 3e Tilde Publishing Chapter 11 Procurement Management Embedding value into the.
Effective Methods for Software and Systems Integration
I) Bob Ettinger Flight Test Manager Northrop Grumman Aerospace Systems El Segundo, CA An Approach to Flight Readiness and Executive Readiness Reviews The.
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Introduction to ISO New and modified requirements.
Introduction to Software Quality Assurance (SQA)
1 Software Testing and Quality Assurance Theory and Practice Chapter 16 Test Team Organization.
Cybersecurity: Engineering a Secure Information Technology Organization, 1st Edition Chapter 7 Software Supporting Processes and Software Reuse.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Proposed Updates to Deskbook Gary Stanley 22 July 14.
Software System Engineering: A tutorial
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
© Grant Thornton | | | | | Guidance on Monitoring Internal Control Systems COSO Monitoring Project Update FEI - CFIT Meeting September 25, 2008.
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.
Requirements Verification & Validation Requirements Engineering & Project Management.
PERT Overview Federal Perspective Annual PERT Workshop February 7-9, 2012 Nevada Site Office Evelyn Landini, Contracting Officer Brookhaven Site Office.
UKSMA 2005 Lessons Learnt from introducing IT Measurement Peter Thomas –
Test Team Organization. 2  Test Groups  Integration Test Group  System Test Group  Software Quality Assurance Group  Quality.
Tier I: Module 5 CERCLA 128(a): Tribal Response Program Element 4: Verification & Certification.
Presented to: By: Date: Federal Aviation Administration Quality and Standards Team (QST) In-Service Management Gold Standard ATO Acquisition Practices.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
IV&V Facility 26SEP071 Validation Workshop Dr. Butch Caffall Director, NASA IV&V Facility 26SEP07.
Verification and Validation — An OSD Perspective — Fred Myers Deputy Director, Test Infrastructure Test Resource Management Center November 4, 2009.
The Research Process.  There are 8 stages to the research process.  Each stage is important, but some hold more significance than others.
A Guide for Management. Overview Benefits of entity-level controls Nature of entity-level controls Types of entity-level controls, control objectives,
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
Jim Hill Nuclear Management Company Nuclear Plant Operation under NRC Reactor Oversight Program.
Date: 25 Sep 12 Presented by: Steve Watts Team Leader Aviation and Missile Research, Development and Engineering Center Presented to: MRL Government /
McDonough Bolyard Peck Educational Series Building Commissioning Presented by: Doug Wrenn Steve Baxter July
McDonough Bolyard Peck Educational Series HVAC Commissioning Presented by: Doug Wren Steve Baxter September 30, 2003.
The Contract Management Process Post Award Activities.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Security Development Lifecycle (SDL) Overview
[Team Name] (e.g. ESH) Team Lead.
Software Engineering (CSI 321)
Software and Systems Integration
Milestone A to Milestone B Requirements Management Activities
Uniform Guidance Discussion
(Additional materials)
Software Requirements
Fundamentals of a Business Impact Analysis
HSE Case: Risk Based Approach.
MRL 6 Artifacts (at End of TMRR) Page 1 of 6
Verification and Validation Unit Testing
When Tests Fail Engineering Design and Development
Project Management Process Groups
HHS Child Welfare National IT Managers' Meeting
An Assessment of Space Shuttle Flight Software Development Processes
[Team Name] (e.g. ESH) Team Lead.
Fiber Reinforced Polymer Systems
Presentation transcript:

Update MRL Matrix to address STE/SIE Validation Steve Watts AMRDEC Sep 15

Inspection equipment planning, design, validation, and control have always been considered a critical element of a contractor’s quality program. The AMRDEC’s Quality Engineering (QE) Division is working hard to improve the way STE/SIE and acceptance test procedures associated with the hardware testing and buyoff is validated. It is critical that "validation" efforts for STE/SIE be conducted during EMD and prior to LRIP to ensure the capability of test sets to produce data that shows repeatability and accuracy of measurements and the capability to pass "good" hardware and fail "bad" hardware. For example: –In the production world, contractor requirement interpretations, objectives, and influences affect the adequacy and quality of ATE produced. So, it is entirely possible that a product passes when verified (contractor needs) but fails when validated (government needs). This can happen when for example, a product is built per the specifications but the specifications themselves fail to address the user’s needs. Case in point will be that the requirements might need clarification and/or it is determined that there is a need for more testing. An independent government validation of the contractor’s verification will ensure that the final acceptance test equipment and procedures do not end up containing trivial problems such as operating procedures not being clear or incomplete (i.e. based on tribal knowledge) to more serious problems such as a set of acceptance test requirements not being tested due to an oversight or arbitrarily omitting a test requirement because it was deemed too expensive to accomplish. This alleviates the risk of accepting bad hardware or rejecting good hardware in LRIP. The bottom line is that the last line of defense that the Government has for assessing the condition of the hardware prior to acceptance and one of the primary functions of government quality engineering is the ATE validation process. At the very least, testing across government validated and controlled ATE will assure that the hardware design meets the most basic performance requirements (under ambient conditions) and forms a basis for DD250 acceptance. Need for Validation A Government validated and controlled ATE provides a proven method to evaluate and accept hardware; Particularly when the test equipment used for hardware acceptance is the primary basis for DD250.

Recommended approach through the Life-Cycle: Contractor develop an STE/SIE Validation Plan Government review/approve Validation Plan Contractor performs verification prior to government validation as part of Pilot Line Contractor maintains Validation in Production Re-Validate as necessary throughout Production (i.e. any changes) Update the MRL Matrix to reflect the execution of this recommended approach, and to specifically state the terminology “Validation”. Approach

Recommended Verbiage Recommended changes are highlighted in RED

Comments from MRL WG

AMRDEC’s Quality Engineering Division identified need and provided approach & recommended changes to MRL Matrix MRL Working Group reviewed at 28 Jul 15 meeting and provided comments Currently presenting approach & recommended changes to Government/Industry Workshop for comments Will incorporate Workshop comments and present to MRL WG for final determination Summary