Technical StandardsAnd

Technical Authority-

Technical Warrant HoldersBackground And Responsibilities

Paul S. Gill

NASA Technical Standards Program

January 24, 2005

2

Technical AuthorityGeneral Concept

• Applicability – NASA Missions That Are Governed By NPR 7120.5B

– Flight Programs/Projects – Space And Aeronautics

– Generally, Does Not Include Ground Based Technology Development Projects

– Generally, Does Not Include Institutionally Provided Facilities

• Scope– Ensure Safe And Reliable Operations

• Reliable Operations Address Those Activities That May Affect Human Safety

• Includes Development/Ground Processing, Launch, Flight Operations, And Deorbit/Landing

– Own All Technical Requirements (In Participation With The Program/Project), And Is The Technical Authority For Safety Related Requirements

– Ensure Design Is Compliant With Requirements, And Be The Technical Authority For Variances That May Compromise Safety

– Approve The Verification Plan, And Be The Technical Authority For Any Variances To Verification Plans Or Activities That May Compromise Safety

– Independently Approve Flight Readiness By Signing The COFR

– Participate, As Required, In Flight Operations To Ensure Safe And Reliable Operations

• Implementation– Technical Authority Is The Agency Chief Engineer

– Technical Authority Is Delegated Through Warrant System

3

Technical AuthorityHierarchy of Authority

Administrator

NASA Chief Engineer

Mission Directorate

ProgramProject Manager

DTWH for Technical Area

Technical Authority

Warrants

•Cost•Schedule•Technical

STWH for System

Technical Authority

4

Technical AuthorityKey Attributes

• General– Fully Utilize Project Funded Engineering Activities And Products– Resources Are Available To Expand Upon The Efforts Performed By The Project, When Necessary– Responsive, Without Unnecessary Latency– Selection Of The Right People Is Key To The Success Of The Independent Technical Authority (ITA) Process– Exercise Wisdom, Maturity, And The Ability To Differentiate Between Acceptable And Unacceptable Risk (Not

Risk Averse)– Success Is Contingent On An Effective Safety Culture, The Technical Conscience

• The System Technical Warrant Holder (STWH) For A Specified System(s) Has Extensive Knowledge Of That System, And:

– Is The Technical Authority For All Matters Involving Safe And Reliable Operations– Engaged In Day To Day Activities (Like The Traditional Project Chief Engineer)– Is The Program’s Primary Interface Into The ITA Process– Owns All Technical Requirements With Appropriate DTWH– Approves All Variances That Affect Safe And Reliable Operations– Draws On Matrix Experts, Discipline Technical Warrant Holders, And Their Network Of Experts– May Require A Dedicated Staff (Agents) Depending On Scope Of System– Signs The COFR Based On Input From Agents And DTWH’s (CE May Retain This Responsibility)

• The Discipline Technical Warrant Holder (DTWH) For A Technical Area Brings The Highest Level Of Discipline Expertise And A Fresh Set Of Eyes And Perspective To Assist The STWH

– Agency Wide Responsibility– Approves All Variances To Technical Standards/Requirements Within The Scope Of Warrant (Initially, NASA

Preferred Technical Standards)– Provides Evaluation And Recommendation For Other Technical Issues, As Required– Develops Network Of Discipline Experts Across The Agency To Assist In Technical Evaluations And Standards

Development– Participates With The NASA Technical Standards Program In The Development/Adoption Of NASA Preferred

Standards

• TWH’s Will Seek To Gain Internal Consensus

5

Technical AuthorityConcept of Operations

• Establishment Of Technical Requirements (New Programs)– The Systems Technical Warrant Holder (STWH), Is Responsible To

Ensure The Program Establishes The Correct Set Of Technical Requirements At Formulation

• SEB – Statement Of Work• Contract End Item Specification• Other Technical Requirements Levied By The Government

– Discipline TWH’s Or Their Agents Will Establish Technical Requirements

– The STWH Will Approve The Technical Content Of The RFP Including Contractual Documentation Requirements

– Neither The SEB Chair Nor The Program/Project Manager Has The Authority To Overrule The Technical Authority If Safety May Be Compromised

6

NASA Technical Warrant Holders (TWH)Workshop January 11-14, 2005

Agenda

1. Opening Remarks - Rex Geveden2. Technical Authority Plan Development3. TWH Website Overview4. TWH Planning Meeting5. Dinner Speaker - Sean O’Keefe / Fred Gregory6. Technical Authority - Outside Experts7. TWH Working Session8. TWH Plan Development9. Developing TWH Interfaces10. TWH Plan Presentations11. Chief Engineer’s Plan12. Closing Remarks - Walter Hussey

(Next TWH Workshop Scheduled For March 2005)

7

NASA Technical Warrant Holder WorkshopJanuary 11 – 13, 2005

Speakers and ResourcesIn keeping with the purpose of the workshop, i.e. TWHs build their implementation plan with which to execute Technical Authority for their system or discipline, attendees are divided into two categories: TWHs and their resources. The following are the proposed speakers, resources, and TWHs:

Speakers

Name Position Perspective

Honorable Sean O’Keefe NASA Administrator NASA

RADM (Ret’d) Walt Cantrell SFLC Co-Chair RTF, External Stakeholders

Rex Geveden NASA Chief Engineer Technical Authority

RADM P. Sullivan Engineer Dir, NAVSEA Navy Technical Authority

Dr. A. Summeroff Chief Engr., NAVAIR Tech Auth/Conscience

ADM (Ret’d) Gehman CAIB

VADM (Ret’d) Dyer ASAP

Bryan O’Connor Chief, Safety & Mission Assurance Off of Safe and Miss Assurance

Nancy Leveson Professor , MIT Systems Safety Engineering

8

Resources

Name Position Perspective

D. Weinstein NASA Standards Program Executive Standards Policy

P. Gill Manager, NASA Technical Standards Program Standards Management

(SMA person) JSC SMA SMA Interface

Gene Oliver NASA (Ret’d) PM Interface

Gilbrech or Roe NASA Engineering Safety Center NESC Interface

B. Kilpatrick Office of the Chief Engineer How to Manual

J. Terek Off Chief Eng/ ITA Mgr Budget/ CMS

C. Paquette NAVSEA Tech War Sys NAVYTech Warrant (Days)

Tinsley or Frazier Off Safety & Miss Assurance OSMA Interface

W. Hussey OCE Tech Auth Implementation

Maturo or Hoffman Academy of Applied Learning (APPL) NASA PM Training

P. Patterson NASA Engr Train (NET) NASA Engr Training

C. Mussen NAVY (Ret'd) NAVY PM

G. Robinson OCE Engineer NASA Engineering/ EMB

D. Lengyel OCE Lessons Learned Website, IT

M. Adoko OCE Engineer Training Workforce Education

T. Coleman Bus, Fin Mgr, OCE Budget (Day 1 only)

M. Shepanek Off of Chief, Health & Med Medical/ Health

NASA Technical Warrant Holder WorkshopJanuary 11 – 13, 2005(Speakers and Resources) (Con’t)

9

ITA Technical Warrant Holders

Technical WarrantTechnical Warrant Holder

Location Email Phone Authorization

Aerothermal Flight Mechanics Steve Labbe JSC Flight Sciences

steven.g.labbe@nasa.gov 281-483-4656 Letter

Atmospheric Flight Research and Test Systems Marta Bohn-Meyer DFRC Chief Engineer

Marta.Bohn-Meyer@nasa.gov 661-276-3199 Letter

Electrical Power Distribution and Control Robert Kichak

GSFC Power and Avionics

Robert.A.Kichak@nasa.gov 301-286-1199 Letter

Environmental Control and Life Support Henry Rotter

JSC Fluids, Life Support and Thermal Systems

henry.a.rotter@nasa.gov 281-483-9249 Letter

Global Precipitation Measurement System Steve S. Scott GSFC Engineering

Steven.S.Scott@nasa.gov 301-286-2529 Letter

Hubble Robotic Servicing and De-orbit Module System Steve S. Scott GSFC Engineering

Steven.S.Scott@nasa.gov 301-286-2529 Letter

Human Factors Engineering Dr. Cynthia Null ARC Human Factors

Cynthia.H.Null@nasa.gov 650-604-1260 Letter

International Space Station Payload Processing Systems Oscar Toledo KSC ITA & SM

Oscar.Toledo-1@nasa.gov 321-867-1460 Letter

International Space Station Systems Michael Conley JSC Engineering

michael.g.conley@nasa.gov 281-483-6511 Letter

Mars Reconnaissance Orbiter System Brian K. Muirhead JPL Engineering

Brian.K.Muirhead-106099@jpl.nasa.gov 818-393-1013 Letter

10

Materials and Processes (Metals) Robert Piascik LRC Materials

Robert.S.Piascik@nasa.gov 757-864-3483 Letter

Mechanisms Design and Test John McManamen

JSC Mechanical Systems

john.p.mcmanamen@nasa.gov 281-483-8958 Letter

Non-Destructive Evaluation Edward Generazio LRC NDE

Edward.R.Generazio@nasa.gov 757-864-4968 Letter

Phoenix System Brian K. Muirhead JPL EngineeringBrian.K.Muirhead-106099@jpl.nasa.gov 818-393-1013 Letter

Power Robert KichakGSFC Power and Avionics

Robert.A.Kichak@nasa.gov 301-286-1199 Letter

Propulsion George HopsonMSFC Space Shuttle Main Engine Project

George.D.Hopson@nasa.gov 256-544-1735 Letter

Rocket Propulsion Testing

Dr. Shamim A. Rahman

SSC Propulsion Test Directorate

Shamim.A.Rahman@nasa.gov 228-688-2610 Letter

Software Engineering Tim Crumbley MSFC AvionicsRobert.T.Crumbley@nasa.gov 256-544-5978 Letter

Space Shuttle Ground and Processing Systems Oscar Toledo KSC ITA & SM

Oscar.Toledo-1@nasa.gov 321-867-1460 Letter

Space Shuttle Propulsion Systems Dr. Paul Munafo MSFC Engineering

Paul.M.Munafo@nasa.gov 256-544-2566 Letter

Space Shuttle Systems Paul Shack JSC Engineering paul.e.shack@nasa.gov 281-483-1458 Letter

Stardust System Brian K. Muirhead JPL EngineeringBrian.K.Muirhead-106099@jpl.nasa.gov 818-393-1013 Letter

Thermal Protection and Control Henry Rotter

JSC Fluids, Life Support and Thermal Systems

henry.a.rotter@nasa.gov 281-483-9249 Letter

Wide-Field Infrared Survey Explorer Steve S. Scott GSFC Engineering

Steven.S.Scott@nasa.gov 301-286-2529 Letter

ITA Technical Warrant Holders

11

Technical AuthorityConcept of Operations

• Development Of NASA Preferred Technical Standards– DTWH’s Will Participate With The NASA Technical Standards Program, Which

Retains Process Responsibility, For Standards Development And Maintenance

– DTWH’s Will Recommend Priorities For Development And Updating Of Technical Standards In Their Areas

– Technical Standards Program Will Coordinate With The DTWH’s For Membership Of The Various Technical Standards Working Groups, And Their Activities

• Creation Of New NASA Standards• Review Of Standards Produced By External Groups For Adoption And “Interpretation”• Update/Annotation Of Standards To Incorporate Experience And Lessons Learned• Ensure Adequate Review Of Standards By Centers, Programs &Mission Directorates

– As The Standards “Owner” , The DTWH Must Signify Concurrence On New Or Modified Standards

– Agency Approval Is Retained By The Chief Engineer

12

Technical Standards Process

Warrant Holder Interaction

Integration of Discipline Technical Warrant Holder Into NASA Engineering Standards Process

13

Warrant Holder DISCIPLINE TECHNICAL WARRANTS Document Count

C. Null Human Factors Engineering 7

E. Generazio NDE 8

G. HopsonPropulsion: Liquid, Cryogenic, Earth Storage, & Gas Propulsion: Gas

172

H. Rotter Environmental Control & Life Support 3

H. RotterActive Thermal Protection and Control (Heat Exchangers, etc.)

0

I. Raju Structures (Design, Fracture) 24

J. Kramer-White

Mechanical Analysis (stress & loads analysis) Static & Dynamic Structural Analysis Structural Analysis and Test

918

J. McManamen

Mechanisms Design and Test Kinematic / Dynamic Analysis & Simulation Mechanisms, Actuators, Hydraulics Docking / Berthing Mechanisms & Analysis System Modeling and Simulation

0421

M. Bohn-Meyer Atmospheric Flight Res & Test, Prac and Process TBD

R. KichakElectrical Power & Signal Distribution & Control Grounding and bonding

9517

R. KichakPower Energy Conversion and Storage Solar Power

60

R. Piascik ??

Materials & Processes, and Test Materials & Processes, and Test (Metals) Materials & Processes, and Test (Non-Metallic) Mechanical and Material Properties Test

1059506268

S. LabbeAerothermal Flight Mechanics Analysis Aerothermal Analysis, Aerothermal Flight Mechanics 1

T. Crumbley Software Engineering Standards 38

Summary of NASA Preferred Technical StandardsMapped to Discipline Technical Warrants

14

Technical Standards — Technical Warrant HoldersConcept Of Operation

1. Provide Discipline Technical Warrant Holders (DTWH) With Applicable Technical Standards — Collaborate On Identification Of “Gaps”

2. Support System Technical Warrant Holders (STWH) With Inputs Via NASA Technical Standards Website

3. Interact With DTWH On Priorities For Development And Adoption Of Technical Standards As NASA Preferred Technical Standards

4. Provide STWH With Technical Standards Update Notifications For Topics Related To System Responsibilities

5. Sponsor Development Of Technical Standards To Meet Needs Identified By DTWH And STWH — Process Responsibility

6. Support Technical Authority (TA) With Continued Development Of NASA Technical Standards Program Products