Technical Standards And Technical Authority - Technical Warrant Holders Background And Responsibilities

1. Technical StandardsAndTechnical 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 • EnsureDesign 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 Technical Authority Mission Directorate NASA Chief Engineer Warrants Program Project Manager STWH for System DTWH for Technical Area • Cost • Schedule • Technical 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. Agenda Opening Remarks - Rex Geveden Technical Authority Plan Development TWH Website Overview TWH Planning Meeting Dinner Speaker - Sean O’Keefe / Fred Gregory Technical Authority - Outside Experts TWH Working Session TWH Plan Development Developing TWH Interfaces TWH Plan Presentations Chief Engineer’s Plan Closing Remarks - Walter Hussey (Next TWH Workshop Scheduled For March 2005) NASA Technical Warrant Holders (TWH)Workshop January 11-14, 2005

7. NASA Technical Warrant Holder Workshop January 11 – 13, 2005 Speakers and Resources In 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:

8. NASA Technical Warrant Holder Workshop January 11 – 13, 2005 (Speakers and Resources) (Con’t)

9. ITA Technical Warrant Holders

10. 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. Integration of Discipline Technical Warrant Holder Into NASA Engineering Standards Process Warrant Holder Interaction Technical Standards Process

13. Summary of NASA Preferred Technical StandardsMapped to Discipline Technical Warrants

14. Provide Discipline Technical Warrant Holders (DTWH) With Applicable Technical Standards — Collaborate On Identification Of “Gaps” Support System Technical Warrant Holders (STWH) With Inputs Via NASA Technical Standards Website Interact With DTWH On Priorities For Development And Adoption Of Technical Standards As NASA Preferred Technical Standards Provide STWH With Technical Standards Update Notifications For Topics Related To System Responsibilities Sponsor Development Of Technical Standards To Meet Needs Identified By DTWH And STWH — Process Responsibility Support Technical Authority (TA) With Continued Development Of NASA Technical Standards Program Products Technical Standards — Technical Warrant HoldersConcept Of Operation