root cause investigation (rci) best practices guide product … · 08/05/2014 · corrective...
Post on 17-Oct-2020
4 Views
Preview:
TRANSCRIPT
AEROSPACE REPORT NO. TOR-2014-02163
Root Cause Investigation (RCI) Best Practices Guide Product Overview
May 8, 2014
Roland Duphily Acquisition Risk and Reliability Engineering Department Systems Engineering Division
Prepared for: National Reconnaissance Office 14675 Lee Road Chantilly, VA 20151-1715
Contract No. FA8802-14-C-0001
Authorized by: National Systems Group
Developed in conjunction with Government and Industry contributions as part of the U.S. Space Program Mission Assurance Improvement Workshop. Distribution Statement A: Approved for public release; distribution unlimited.
Report Documentation Page Form ApprovedOMB No. 0704-0188
Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if itdoes not display a currently valid OMB control number.
1. REPORT DATE 08 MAY 2014
2. REPORT TYPE Final
3. DATES COVERED -
4. TITLE AND SUBTITLE Root Cause Investigation (RCI) Best Practices Guide Product Overview
5a. CONTRACT NUMBER FA8802-14-C-0001
5b. GRANT NUMBER
5c. PROGRAM ELEMENT NUMBER
6. AUTHOR(S) Roland Duphily
5d. PROJECT NUMBER
5e. TASK NUMBER
5f. WORK UNIT NUMBER
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) The Aerospace Corporation 2310 E. El Segundo Blvd. El Segundo, CA 90245-4609
8. PERFORMING ORGANIZATION REPORT NUMBER TOR-2014-02163
9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) National Reconnaissance Office 14675 Lee Road Chantilly, VA20151-1715
10. SPONSOR/MONITOR’S ACRONYM(S) NRO
11. SPONSOR/MONITOR’S REPORT NUMBER(S)
12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release, distribution unlimited
13. SUPPLEMENTARY NOTES The original document contains color images.
14. ABSTRACT
15. SUBJECT TERMS
16. SECURITY CLASSIFICATION OF: 17. LIMITATIONOF ABSTRACT
UU
18. NUMBEROF PAGES
42
19a. NAME OFRESPONSIBLE PERSON
a. REPORT unclassified
b. ABSTRACT unclassified
c. THIS PAGE unclassified
Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18
i
Acknowledgments
This presentation provides a summary overview of TOR-2014-02202, “Root Cause Investigation Best Practices Guide”, which was produced as part of the 2014 Mission Assurance Improvement Workshop. This document was created by multiple authors throughout the government and the aerospace industry. For their content contributions, we thank the following contributing authors for making this collaborative effort possible: Harold Harder (Co-Lead) The Boeing Company Roland Duphily (Co-Lead) The Aerospace Corporation Rodney Morehead The Aerospace Corporation Joe Haman Ball Aerospace & Technologies Corp Helen Gjerde Lockheed Martin Corporation Susanne Dubois Northrop Grumman Thomas Stout Northrop Grumman David Ward Orbital Sciences Corp Thomas Reinsel Raytheon Jim Loman SSL Eric Lau SSL A special thank you to Harold Harder, The Boeing Company, for co-leading this team, and to Andrew King, The Boeing Company, for sponsoring this team; your efforts to ensure the completeness and quality of this document are appreciated.
ii
Acknowledgments (Cont)
The Topic Team would like to acknowledge the contributions and feedback from the following subject matter experts (SMEs) who reviewed the document: Lane Saechao Aerojet Rocketdyne Tom Hecht Aerospace Matthew Eby Aerospace Richard Pfisterer APL David Eckhardt BAE Systems Mary D’Odine Ball Aerospace & Technologies Corp Gerald Schumann NASA Mark Wroth Northrop Grumman Larry DeFillipo Orbital Sciences Corp Mauricio Tapia Orbital Sciences Corp Deanna Musil SSL Matteo Genna SSL
1
U.S. SPACE PROGRAM MISSION ASSURANCE IMPROVEMENT WORKSHOP ORBITAL SCIENCES CORPORATION | DULLES, VA | MAY 7 - 8, 2014
Root Cause Investigation (RCI) Best Practices Guide
Overview Harold Harder, The Boeing Company
Roland Duphily, The Aerospace Corporation
May 21, 2014 This presentation provides a summary overview of TOR-2014-02202, “Root Cause Investigation Best Practices Guide”, which was produced as part of the 2014 Mission Assurance Improvement Workshop.
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 2
RCI Overview Agenda
• Motivation for RCI Guide • Example • Product Overview • Topic Details • Product Implementation Recommendations • Topic Follow-on Recommendations • Team Membership and Recognition
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 3
Motivation for RCI Guide
• Some root cause failure investigations failed to identify true root cause – Unfortunately, failure recurred after corrective actions were implemented for
what was believed to be the root cause • Projects and teams may lack leadership and guidance documents on
performance of root cause analysis (RCA) • Variability in RCA techniques used can result in ineffective or inefficient
root cause investigations • For the National Security Space community, no recognized RCI best
practice exists
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 4
Summary • This guide has been prepared to help determine what methods and
software tools are available when significant detailed root cause investigations are needed and what level of rigor is appropriate to reduce the likelihood of missing true root causes identification. For this report a root cause is the ultimate cause or causes that if eliminated would have prevented the occurrence of the failure. In reality, many failures require only one or two investigators to identify root causes and do not demand an investigation plan that includes many of the practices defined in this document.
• During ground testing and on-orbit operations of space systems, programs have experienced anomalies and failures where investigations did not truly establish definitive root causes. This has resulted in unidentified residual risk for future missions
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 5
Notional Failure Recurrence Example
Feb 2009 Mar 2011
Payload Fairing Failed to Separate
Payload Fairing Failed to Separate
4 possible root causes identified and corrective action implemented
2 likely intermediate causes identified Unable to identify root cause Several technical recommendations made
Failure to Identify True Root Cause Increases Mission Risk Goal of RCI Best Practices Guide is to Improve Identification of True Root Causes and Minimize Mission Risk
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 6
RCI Topic Team Charter
• Establish a cross industry and government team to formulate foundational information and recommended best practices for Root Cause Investigations (RCI) focused on the space industry
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 7
Root Cause Investigation Purpose and Scope
• During ground testing and on-orbit operations of space systems, programs have experienced anomalies and failures where investigations did not truly establish definitive root causes. This has resulted in unidentified residual risk for future missions
• Guide focuses on RCA elements of the broader Root Cause Corrective Action (RCCA) process per request of the Steering Committee. Corrective action process is not discussed in this guide.
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 8
Root Cause Investigation Guide Traceability to Steering Committee
Deliverable Requested
Location in RCI Guide
Overview of basis for RCAs, definitions and terminology, commonly used techniques, needed skills/experience
Sec 2, Sec 3, Sec 8, Sec 5.3
Key early actions to take following anomaly/failure Sec 5.0
Data/information collection approaches Sec 6.0
Structured RCA approaches – pros/cons Sec 8, Table 11
Survey/review of available RCA tools Sec 9.0
Guidance on criteria for determining when a RCA is sufficient (when do you stop)
Sec 10.0
RCA of on orbit vs. on ground anomalies Sec 11.0
Handling of root cause unknown and unverified failures
Sec 12.0
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 9
Root Cause Investigation Best Practices Guide
• Focus is on Root Cause Analysis Methods and Tools utilized by the RCI Space Systems Team and companies – No magic methods or tools; identified common issues and facilitation techniques – Many ground failure RCI’s validate true root cause quickly (hardware available) – A few complex anomalies benefit from a combination of items in the RCI guide
7. Problem
Definition
8. Root Cause
Analysis
9. Corrective
Action Plan
10. Implement
& Verify
11. Validate Actions
Effective
Return to Step #6 if Problem Recurs
6. Collect &
Classify Data
2. Preserve Scene
3. Communication
& Documentation
4. Team Composition
5. FRB & Other Process Initiation 1. Containment
Key Early Actions following the failure/anomaly are included in the top chevron bar, and the balance of the RCCA process is included in the bottom chevron bar. Note that this document only addresses those actions that significantly affect the Root Cause Analysis step (noted in bold blue):
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 10
RCI Guide Details
• This Guidance Document summarizes root cause investigation best practice recommendations and key takeaways for use with simple or complex on-ground or in-orbit failures and anomalies.
• The industry Core Team focused on combining most effective root cause investigation approaches from each company in a usable format.
• Provide Pro and Cons for RCA Methods and RCA Pitfalls.
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 11
RCI Guide Details- Cont
• Preservation of the “scene” of the failure: Don’t contaminate evidence (by immediately reworking affected unit to restore operation if it would affect failure investigation)
• Immediate Data Collection: Interviews, observations, measurements, audio/video, chart recordings, all relevant data, etc.
• Determine Team Composition (as appropriate): Ideally include 6-8 people including Process Performers (operators, technicians, etc.), Subject Matter Experts (engineers, scientists, etc.), Customer or Rep (Quality, Mission Assurance, etc.), RCCA Facilitator, Team Leader/Chair; define roles (RACI – Responsible, Accountable, Consulted, Informed and/or RAA – Responsibility, Accountability, Authority)
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 12
RCI Guide Details - Cont
• Problem Definition (“Problem Definition Worksheet”): Define, understand and agree upon the facts surrounding the anomaly: Title, Customer, What happened (be specific)?, When did it happen (start date/time – stop date/time)?, Where did it happen (be specific)?, How often did it happen?, Was it repeatable under specific conditions?, Importance/Significance?, Avoid “Who” (may inhibit cooperation if people think they are being blamed), Avoid “Why” and “How” (RCCA process will determine this)
• Brainstorm potential causes/contributing factors including use of Data Collection above: Classify data utilizing KNOT Chart, may also use Affinity Diagram, Pareto or Scatter Chart, Histogram, or other tools; assign actions, ECD’s, etc
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 13
RCI Guide Details - Cont • Root Cause Analysis (RCA): Almost always more than one root
cause, and the level of rigor is determined by complexity of problem. Consider “Severity/Recurrence Risk Cube” analysis for RCA approach – RCA Techniques (may use one or more): Timeline, 5-Whys, Apollo,
Fishbone (Ishikawa) Cause and Effect Diagram, Process Analysis or Process Classification Method including Process Mapping or Logic Flow Pert Chart , Advanced Cause and Effect Analysis (complex Cause/Effect relationships in Fault/Failure Tree format ), RCA “Stacking” (apply multiple techniques) or Interaction of methods (i.e., Fishbone diagram followed by 5-Why’s on the identified RC from the Fishbone)
– Special Considerations for Space RCA: Low volume, high value assets vs. serial production situations, Pre-launch vs. on-orbit investigations, Managing schedule pressures and team technical independence
– Unverified Failures (UVF ): What to do when root causes cannot be determined (in this context the UVF discussion is often about “how far do you go in looking for root cause?”)
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 14
RCI Outline – 1 of 3 1. Overview .. ..... ...... ..... ..... ... ... .. ..... ...... ..................... ..... ...... ............. ..... ..... ...... ..... ..... .... .... 1
1.1 MAIW RCI Team Formation ... ..... ..... .................................................................... 1
2. Purpose and Scope ................. ..... ...... ..... ............. ..... ...... .................. ..... ...... ..... ..... ..... ... 2
3. Definitions ..... ..... ...... ...... ..... .. ..... ... .............. ................................................................... .4
4. References .... ..... ...... ..... ... ........ ..... ...... ..... ............. ..... ...... .................. ..... ...... ..... ..... .... .... 7
5. RCA Key Early Actions .. ... .... ............ ..... ..... .................................................................... 8
5.1 Preliminary Investigation ... .. ..... ...... ..... ....... ......... ..... ...... ............. ..... ...... ..... ..... .... 8
5.2 Scene Preservation and Data Collection ............................................................. 9
5.2.1 Site Safety and Initial Data Collection ..... ..... ...... ............. ..... ...... ..... ..... ..... .... 9
5.2.2 Witness Statements ... ..... ..... ..... ......................................... ......... .. ... .. ..... ... . 1 0
5.2.3 Physical Control of Evidence .. ... .................. ..... ...... ............. ....... .... ..... ..... .. 1 0
5.2.4 NASA Mishap Reference ..... ..... .................................................................. 11
5.3 Investigation Team Composition and Facilitation Techniques .......... ..... ..... ..... .. 11
5.3.1 Team Composition ..... ..... ..... ..... .................................................................. 11
5.3.2 Team Facilitation Techniques ................. ..... ..... ...... ............. ....... .... ..... ..... .. 13
6. Collect and Classify Data .. .... ..... ... ......... ..... .................................................................. 14
6. 1 KNOT Chart .. ... .. ...... ..... ..... ...... ............. ..... ...... .................. ..... ...... ..... ..... ..... ...... 16
6.2 Event Timeline ....... ..... ...... ..... ..... ..... .................................................................. 17
6.3 Process Mapping .. ... ..... ...... ............. ..... ..... ...... ............. ..... ...... ..... ..... ..... ..... ...... 18
7. Problem Definition .. .. ... ... ... .... ............ ..... ..... .................................................................. 20
, U.S. Space Program
l ' Mission Assuranc~ . ... :1' Improvement ~
.., -~• Workshop
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 15
RCI Outline – 2 of 3 8. Root Cause Analysis (RCA) Methods ........................................................................... 24
8. 1 RCA Rigor Based on Significance of Anomaly ............ ... ........ .... ............ ......... .. 24
8.2 Brainstorm ing Potential Causes/Contributing Factors ... ...... ... ... .......... .. .... ........ 28
8.3 Fish bone Style ......................... ........................ ....... .................................... ... .... 29
8.4 Tree Techn iques ......... ..................................... ....... .................................... ... .... 31
8.4.1 5-Why's ... ................................................ .................................................... 31
8.4.2 Cause Mapping ......................................... ........... ..................... .............. .... 32
8.4.3 Advanced Cause and Effect Analysis (ACEA) ............................................ 33
8.4.4 Fault Tree Analysis (FTA) ......................... ........... ............ ......................... .. 35
8.5 Process Flow Style ..... ................................. ...................................................... 38
8.5.1 Process Classification ...... ................ ......... .................................................. 38
8.5.2 Process Analysis ................................... .. ......... .................................... ... .... 39
8.6 RCA Stacking ..................................................................................................... 39
9. Root Cause Analysis Tools (Software Package Survey) ........ ... ......... ... ............ ......... .. 40
, U.S. Space Program
l ' Mission Assuranc~ . .. :1' Improvement ~
.., -~• Workshop
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 16
RCI Outline – 3 of 3 9.1 Surveyed Candidates .. _ ... . _ .. .. _._ .... _ .... _._ .... _ .... _ .. .. _._ .... _ .... _._ ... . _ .. .. _._ .. _._ .... _ .... _._ ... .41
9.2 Rea lity Charting (Apollo ) ..... ..... .. .......... ............ ... ........ ........ .......... .. ........ .. ... ...... 41
9.3 TapRooT ..... ...... ......... ..... .... ..... .......... ........ ...... ... ............ ..... ... .... ..... ....... ........ ... 43
9.4 GoldFire ..................... ...... ...... ..... ...... ..... .... ... ..... ............. ..... .. .......... ...... ..... .... ... 46
9.5 RCAT (NASA Tool) ......... .... ..... ... ....... .......... .... ........ ............ .... ... ............ .......... .48
9.6 Think Reliabili ty ....... ... ............. .... ........ ....... .... .... ... ....... .... ....... ..... .... ........ ...... .... 50
10. When is RCA Depth Sufficient ... ....... .. ............... ...... ... ......... ...... ..... ...................... ....... . 52
10.1 Prioritization Techniques ..... ..... ... ....... ..... ............ ............... ...... .... ..... ............ ...... 54
10.1.1 Risk Cube (Harder-need Clarification) .. .... ........ ............ .... ....... ............. ...... 54
10.1.2 Solution Evaluation Template (Harder-need Clarification ) .. ..... .. ...... ........... 55
11. RCA On-Orbit versus On-Ground ... ...... ...... ............. .. .... ...... .... ...... ..... ....... ....... ............ 55
12. RCA Unverified and Unknown Cause Failures .. ...... ... ........... .... ..... ......... ................. ... . 58
12.1 Unverified Failure (UVF) ... .. ....... ......................... ... ....... ...... ............ ......... .......... 58
12.2 Unknown Direct/Root Cause Fa ilu re ..... .... .... ...... .... ...... ..... .............. ... ....... .... .... 61
13. RCA Pitfalls ... .. ....... ......... ...... ........ .... ..... ....... ....... ...... .... ............ ..... ... .... ..... ....... ....... .... 62
A.1 Type B Reaction Wheel Root Cause Case Study ........ ........ ......... ............... ...... 63
, U.S. Space Program
l ' Mission Assuranc~ . .. :1' Improvement ~
.., -~• Workshop
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 17
Reasons For Missing True Root Cause
• Incorrect team composition
• Incorrect data classification
• Lack of objectivity/incorrect problem definition
• Cost and schedule constraints
• Rush to judgment
• Lack of management commitment
Details on RCA Pitfalls Covered in Exec Overview and Section 13
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 18
Team Facilitation Techniques • Knowledge of group dynamics
– Ability to “read” the team (confusion, progress, intimidation)
– Ability to create a safe environment
– Ability to deal with disruptions and intimidation
• Ability to determine if team is diverse enough
• Approach the problem from both right brain creative and left brain
logical perspectives
• Classify data accurately (KNOT)
• Use RCA tool with which the team is most comfortable
• FOLLOW THE PROCESS (deviation introduces risk)
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 19
RCA Level Based on Risk Matrix
Failure Risk Matrix used to Determine RCA Rigor Needed
Hig h
Highest Risk Level3 RCA Level4 RCA Items
LevelS RCA 1\
+-' u rc 0.
Medi um
> E .~ .....
lo... 0 QJ Q)
u > c QJ rc
Level2 RCA Level3 RCA Level4 RCA
(,/') u ~ c Q.O
~ Low v Lowest Risk
Items Level 2 RCA Level3 RCA Level 1 RCA
Low Med ium High
Recurrence
< Likelihood of the Event Recurring >
, U.S. Space Program
l ' Mission Assuranc~ . .. :1' Improvement ~
.., .~• Workshop
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 20
RCA Level by Impact Matrix
Impact Matrix Provides Guidance on Applicable RCA Methods
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 21
Intended RCI Guide Use • Primary use
– Guide for RCI teams and sponsors on space related investigations – Help develop effective RCI plan and depth of rigor
• Publicize RCI guide at conferences – International Society of Testing and Failure Analysis (ASM) – International Reliability Physics Symposium (IEEE) – Reliability Availability and Maintainability Symposium (RAMS) – And others
• Specific recommendations for industry: – Incorporate best practices in corporate command media – Use as a reference to subcontractors to set expectations and improve
communications
• Specific recommendations for government: – Use as a reference to contractors to set expectations and improve
communications – Consider using as reference in program offices and RFP’s
U.S. SPACE PROGRAM MAIW | DULLES, VA | MAY 7 - 8, 2014 22
Core Team Additional SME
Company Participant Company Participant The Aerospace Corporation
Ron Duphily
Rodney Morehead
The Aerospace Corporation
Tom Hecht
Matthew Eby Ball Aerospace & Technologies Corp
Joseph Haman Orbital
David Adcock
Mauricio Tapia
Larry Defillipo The Boeing Company Harold Harder Northrop Grumman
Mark Wroth
Lockheed Martin Corporation
Helen Gjerde Aerojet Rocketdyne Iane Saechao
Northrop Grumman Susanne Dubois
Thomas Stout
NASA
Gerald Schumann
Orbital David Ward BAE Systems David Eckhardt
Raytheon Space and Airborne Systems
Tom Reinsel Ball Aerospace & Technologies Corp
Mary D’Odine
SSL Jim Loman
Eric Lau
RCI Team Introductions
Approved Electronically by:
AEROSPACE REPORT NO.TOR-2014-02163
Root Cause Investigation (RCI) Best Practices Guide Product Overview
Jacqueline M. Wyrwitzke, PRINCDIRECTORMISSION ASSURANCE SUBDIVISIONSYSTEMS ENGINEERING DIVISIONENGINEERING & TECHNOLOGYGROUP
Russell E. Averill, GENERAL MANAGERSPACE BASED SURVEILLANCEDIVISIONSPACE PROGRAM OPERATIONS
Manuel De Ponte, SR VP NATL SYSNATIONAL SYSTEMS GROUP
Jackie M. Webb-Larkin, SECURITYSPECIALIST IIIGOVERNMENT SECURITYSECURITY OPERATIONSOPERATIONS & SUPPORT GROUP
© The Aerospace Corporation, 2014.
All trademarks, service marks, and trade names are the property of their respective owners.
SK0669
Technical Peer Review Performed by:
AEROSPACE REPORT NO.TOR-2014-02163
Root Cause Investigation (RCI) Best Practices Guide Product Overview
Jacqueline M. Wyrwitzke, PRINC DIRECTORMISSION ASSURANCE SUBDIVISIONSYSTEMS ENGINEERING DIVISIONENGINEERING & TECHNOLOGY GROUP
Norman Y. Lao, DIRECTOR DEPTACQ RISK & RELIABILITY ENGINEERING DEPTMISSION ASSURANCE SUBDIVISIONENGINEERING & TECHNOLOGY GROUP
© The Aerospace Corporation, 2014.
All trademarks, service marks, and trade names are the property of their respective owners.
SK0669
External Distribution
REPORT TITLE
Root Cause Investigation (RCI) Best Practices Guide Product Overview
REPORT NO. PUBLICATION DATE SECURITY CLASSIFICATION
TOR-2014-02163 June 23, 2014 UNCLASSIFIED
Charles AbernethyAerojetcharles.abernethy@aerojet.com
Carlo AbesamisNASAabesamis@jpl.nasa.gov
Andrew AdamsBoeingandrew.c.adams@boeing.com
David AdcockOrbitaladcock.david@orbital.com
Robert AdkissonBoeingrobert.w.adkisson@boeing.com
Scott AndersonSeakerscott.anderson@seaker.com
Aaron ApruzzeseATKaaron.apruzzese@atk.com
Chic AreyNROareyc@nro.mil
Brent ArmandOrbitalArmand.Brent@orbital.com
Larry ArnettLoralarnett.larry@ssd.loral.com
Ken BaierLockheed Martinken.b.baier@lmco.com
Dean BakerNRObakerdea@nro.mil
Mark BaldwinRaytheonMark.L.Baldwin@raytheon.com
Lisa BarbozaGeneral DynamicsLisa.Barboza@gd-ais.com
Glenn BarneyComdev-USAglenn.barney@comdex-use.com
David BeckwithNRObeckwith@nro.mil
Theresa BeechMetispacetbeech@metispace.com
Barry BirdsongMDAbarry.birdsong@mda.mil
Ruth BishopNorthrop Grummanruth.bishop@ngc.com
Robert BodemullerBallrbodemuller@ball.com
Silvia BouchardNorthrop Grummansilver.bouchard@ngc.com
Wayne BrownULA Launchwayne.brown@ulalaunch.com
Christopher BrustDCMAChristopher.Brust@dcma.mil
Alexis BurkevicsRocketAlexis.Burkevics@rocket.com
Thomas BurnsNOAAthomas.burns@noaa.gov
Edward BushNorthrop GrummanEdward.Bush@ngs.com
Tim CahillLockheed Martintim.cahil@lmco.com
Kevin CampbellExelis Inckevin.campbell@exelisinc.com
Larry CapotsLockheed Martinlarry.capots@lmco.com
Will CavenLoralcaven.will@ssd.loral.com
Shawn CheadleLockheed Martinshawn.cheadle@lmco.com
Janica CheneyATKjanica.cheney@atk.com
Brian ClassOrbitalclass.brian@orbital.com
Brad ClevengerEMCOREbrad_clevenger@emcore.com
Jerald CogenFREQELECJerald.Cogen@FreqElec.com
Bernie CollinsDNIbernie.f.collins@dni.gov
Jeff ConyersBalljconyers@ball.com
Kevin CrackelAerojetkevin.crackel@aerojet.com
James CreimanNorthrup GrummanJames.Creiman@ngc.com
Stephen CrossULA Launchstephen.d.cross@ulalaunch.com
Shawn CullenJDSUshawn.cullen@jdsu.com
Louis D'AngeloLockheed Martinlouis.a.d'angelo@lmco.com
David DavisSMCDavid.Davis.3@us.af.mil
Douglas DawsonNASAdouglas.e.dawson@jpl.nasa.gov
Jaclyn DeckerOrbitaldecker.jaclun@orbital.com
Larry DeFillipoOrbitaldefillipo.aryy@orbital.com
Ken DodsonSSL MDAken.dodson@sslmda.com
Tom DonehueATKtom.donehue@atk.com
Mary D'OrdineBallmdordine@ball.com
Susanne DuboisNorthrop Grummansusanne.dubois@ngc.com
David EckhardtBAE Systemsdavid.g.eckhardt@baesystems.com
Robert EllsworthBoeingrobert.h.ellsworth@boeing.com
Matt FahlHarris Corporationmfahl@harris.com
James FarrellBoeingjames.t.farrell@boeing.com
Tracy FiedlerRaytheontracy.m.fiedler@raytheon.com
Brad FieldsOrbitalfields.brad@orbital.com
Sherri FikeBallsfike@ball.com
Richard FinkNROrichard.fink@nro.mil
Bruce FlanickNorthrop Grummanbruce.flanick@ngc.com
Mike FloydGeneral DynamicsMike.Floyd@gdc4s.com
David FordFlextronicsdavid.ford@flextronics.com
Robert FrankievichLockheed Martinrobert.h.frankievich@lmco.com
Bill FrazierBallwfrazier@ball.com
Jace GardnerBalljgardner@ball.com
Matteo GennaSSLmatteo.genna@sslmda.com
Helen GjerdeLockheed Martinhelen.gjerde@lmco.con
Ricardo GonzalezBAE Systemsricardo.gonzalez@baesystems.com
Dale GordonRocketdale.gordon@rocket.com
Chuck GrayFescorpChuckg@fescorp.com
Luigi GrecoExelis Incluigi.greco@exelisinc.com
Gregory HafnerOrbitalHafner.Gregory@orbital.com
Joe HamanBalljhaman@ball.com
Lilian HannaBoeinglilian.hanna@boeing.com
Harold HarderBoeingharold.m.harder@boeing.com
Bob HarrSeakerbob.harr@seaker.com
Frederick HawthorneLockheed Martinfrederick.d.hawthorne@lmco.com
Ben HoangOrbitalHoang.Ben@orbital.com
Rosemary HobartHobart Machinedrosemary@hobartmachined.com
Richard HodgesNASArichard.e.hodges@jpl.nasa.gov
Paul HopkinsLockheed Martinpaul.c.hopkins@lmco.com
Kevin HorganNASAkevin.horgan@nasa.gov
Eugene JaramilloRaytheoneugenejaramillo@raytheon.com
Dan JarmelNorthrop Grummandan.jarmel@ngc.com
Robert JenningsRaytheonrjennings@raytheon.com
Mike JensenULA Launchmike.jensen@ulalaunch.com
Amanda JohnsonOrbitaljohnson.amanda@orbital.com
Edward JopsonNorthrop Grummanedward.jopson@ngc.com
Jim Juddorbitaljudd.jim@orbital.com
Geoffrey KaczynskiNEA Electronicsgkazynik@neaelectonics.com
Mike KahlerBallmkahler@ball.com
Yehwan KimMoogykim@moog.com
Jeff KincaidPowerJeffrey.Kincaid@pwr.utc.com
Mark KingMicopacmarkking@micropac.com
Andrew KingBoeingandrew.m.king@boeing.com
Byron KnightNROknightby@nro.mil
Hans KoenigsmannSpaceXhans.koenigsmann@spacex.com
James KooryRocketjames.koory@rocket.com
Brian KosinskiSSLKosinski.Brian@ssd.loral.com
John KowalchikLockheed Martinjohn.j.kowalchik@lmco.com
Rick KrauseBallrkrause@ball.com
Steve KreinATKsteve.krein@atk.com
Steve KuritzNorthrop Grummansteve.kuritz@ngc.com
Louise LadowSeakerlouise.ladow@seaker.com
C J LandHarriscland@harris.com
Chris LaroccaEMCOREclarocca@emcore.com
Robert LaskyOrbitallasky.robert@orbital.com
Eric LauSSLlau.eric@ssd.loral.com
Marvin LeBlancNOAAMarvin.LeBlanc@noaa.gov
Scott LeeNorthrop GrummanScott.lee@ngc.com
Don LeRoyBarden Bearingsdleroy@bardenbearings.com
Scot LichtyLockheed Martinscot.r.lichty@lmco.com
Sultan Ali LilaniIntegra - Techsultan.lilani@integra-tech.com
Josh LindleyMDAjoshua.lindley@mda.mil
Henry LivingstonBAE Systemshenry.c.livingson@baesystems.com
Art LoftonNorthrop GrummanArt.Lofton@ngc.com
James LomanSSLjames.loman@sslmda.com
Jim LomanSSLloman.james@ssd.loral.com
Lester LopezHarrisllopez04@harris.com
Frank Lucca1-3 Comfrank.l.lucca@1-3com.com
Joan LumBoeingjoan.l.lum@boeing.com
Brian MackOrbitalmack.brian@orbital.com
Julio MalagaOrbitalmalaga.julio@orbital.com
Kevin Mallon1-3 ComKevin.P.Mallon@1-3com.com
Miroslav MaramicaArea 51miroslav@area51esq.com
John Mc BrideOrbitalMcbride.John@orbital.com
Ian McDonaldBAE Systemsian.a.mcdonald@baesystems.com
Kurt MeisterHoneywellkurt.meister@honeywell.com
Jeff MendenhallMITmendenhall@ll.mit.edu
Jo MerrittAVTECjmerritt@avtec.com
Charles MillsLockheed Martincharles.a.mills@lmco.com
Edmond MitchellAPLedmond.mitchell@jhuapl.edu
Dennis MlynarskiLockheed Martindennis.mlynarski@lmco.com
George MockNYE Lubricantsgbm3@nyelubricants.com
Nancy MurraySafety BatteriesNancy.murray@saftbatteries.com
Deanna MusilSSLdeanna.musil@sslmda.com
Thomas MusselmanBoeingthomas.e.musselman@boeing.com
John NelsonLockheed Martinjohn.d.nelson@lmco.com
Dave NovotneyEBAdbnovotney@eba-d.com
Ron NowlinEaglePicherron.nowlin@eaglepicher.com
Mike NumbergerNavynurnberger@nrl.navy.mil
Michael O'BrienExelis Incmichael.obrien@exelisinc.com
Michael OgneovskiExelis Incmichael.ognenovski@exelisinc.com
Debra OlejniczakNorthrop GrummanDebra.Olejniczak@ngc.com
Larry OstendorfpsemcLostendorf@psemc.com
Anthony OwensRaytheonanthony_owens@raytheon.com
Joseph PackardExelis IncJoseph.packard@exelisinc.com
Peter PallinSSLpeter.pallin@sslmda.com
Richard PatricanRaytheonRichard.A.Patrican@raytheon.com
Paulette MeganOrbitalpaulette.megan@orbital.com
Mark PazderMoogmpazder@moog.com
Steven PereiraAPLSteven.Pereira@jhuapl.edu
Richard PfistererAPLRichard.Pfisterer@jhuapl.edu
Angela PhillipsRaytheonamphillips@raytheon.com
Dave PinkleyBalldpinkley@ball.com
Kay RandNorthrop Grummankay.rand@ngc.com
David ReaBAE Systemsdavid.a.rea@baesystems.com
Forrest ReedEaglePicherforrest.reed@eaglepicher.com
Thomas ReinselRaytheonthomas_j_reinsel@raytheon.com
Bob RiccoNorthrop Grummanbob.ricco@ngc.com
Mike RiceRT Logicmrice@rtlogic.com
Sally RichardsonOrbitalrichardson.sally@orbital.com
Troy RodriquezSierra Microwavetroy_rodriquez@sierramicrowave.com
Ralph RoeNASAralph.r.roe@nasa.gov
Mike RollerUTASmike.roller@utas.utc.com
John RotondoBoeingjohn.l.rotondo@boeing.com
William RozeaRocketwilliam.rozea@rocket.com
Dennis RubienNorthrop Grummandennis.rubien@ngc.com
Larry RubinSSLRubin.larry@ssd.loral.com
Lane SaechaoRocketlane.saechao@rocket.com
Michael SampsonNASAmichael.j.sampson@nasa.gov
Victor SankNASAvictor.j.sank@nasa.gov
Don SawyerAVNETdon.sawyer@avnet.com
Fred SchippMDA - Navyfrederick.schipp@navy.mil
Jim SchultzBoeingjames.w.schultz@boeing.com
Gerald SchumannNASAgerald.d.schumann@nasa.gov
Annie SennetSafety BatteriesAnnie.Sennet@saftbarries.com
Michael SettemberNASAmichael.a.settember@jpl.nasa.gov
Tom SharpeSMT Corptsharpe@smtcorp.com
Jonathan SheffieldSSLjonathan.sheffield@sslmda.com
Andrew ShroyerBallashroyer@ball.com
Fredic SilvermanHSTCfsilverman@hstc.com
Rob SinghSSLrob.singh@sslmda.com
Kevin SinkTTINCkevin.sink@ttinc.com
Melanie SloaneLockheed Martinmelanie.sloane@lmco.com
Jerry SobetskiLockheed Martinjerome.f.sobetski@lmco.com
LaKeisha SouterNorthrop Grummanlakeisha.souter@ngc.com
Jerry SpindlerExeclis IncJerry.Spindler@exelisinc.com
Peter StoltzTX Corppstoltz@txcorp.com
Thomas StoutNorthrop Grummanthomas.stout@ngc.com
George StykExelis Incgeorge.styk@exelisinc.com
David SwansonOrbitalswanson.david@orbital.com
Mauricio TapiaOribitaltapia.mauricio@orbital.com
Jeffrey TateRaytheonjeffery_tate@raytheon.com
Bill TothNorthrop Grummanwilliam.toth@ngc.com
Ghislain TurgeonSSLghislain.turgeon@sslmda.com
Deborah ValleyMITdeborah.valley@ll.mit.edu
Fred Van MilligenJDSUfvanmilligen@jdsu.com
Marvin VanderWegSpaceXmarvin.vanderwag@spacex.com
Gerrit VanOmmeringSSLgerrit.vanommering@sslmda.com
Michael VerzuhBallmverzuh@ball.com
John ViljaPower UTCjussi.vilja@pwr.utc.com
Vinvent StefanOrbitalvincent.stefan@orbital.com
James WadeRaytheonjames.w.wade@raytheon.com
John WalkerSSLJohnF.Walker@sslmda.com
Brian WeirBooz Allen Hamiltonweir_brian@bah.com
Arthur WeissPower UTCarthur.weiss@pwr.utc.com
Craig WesserNorhtrop Grummancraig.wesser@ngc.com
Dan WhiteComdex-USAdan.white@comdev-usa.com
Thomas WhitmeyerNASAtom.whitmeyer@nasa.gov
Charlie WhitmeyerOrbitalwhitmeyer.charlie@orbtial.com
Michael WooRaytheonmichael.woo@raytheon.com
Larry WraySSLwray.larry@ssd.loral.com
Mark WrothNorthrop Grummanmark.wroth@ngc.com
Jian XuAeroflexjian.xu@aeroflex.com
George YoungRaytheongyoung@raytheon.com
APPROVED BY_____________________________________________________________________________________ DATE___________________________________(AF OFFICE)
top related