Dryden Flight Research Center Presentation to NASA Technical Standards Working Group

1. Dryden Flight Research CenterPresentation to NASA Technical Standards Working Group Oct 5-6, 2004Raymond Kacmar http://standards.nasa.gov

2. DFRC Standards Activities: • DFRC CLOSED ACTION ITEMS: • Action No. 255-2, NASA-STD-5017 (Draft 1), "Design And Development Criteria For Critical Mechanical Systems" • Action No. 245-1, Review of DIS 23038 - Space Solar Cells - Electron and Proton Irradiation Test Methods • Action No. 229-1, Review of Draft ISO 14625 - Space systems — Ground support equipment for use at launch, landing, or retrieval sites - General requirements • Action No. 219-1, Review of Draft ISO/CD 22010 - Space systems — Mass properties control • Action No. 218-1, EMB Approval of NASA-HDBK-5010, "Fracture Control Implementation Handbook for Payloads, Experiments, and Similar Hardware • Action No. 216-1, AIAA Hydrogen Safety Guide Available for Public Review http://standards.nasa.gov

3. DFRC Standards Activities: • DFRC CLOSED ACTION ITEMS: • Action No. 215-1, Review of Draft ISO/WD 16193 "Probabilistic Risk Assessment" • Action No. 214-1, Review of Draft ISO FDIS 15859-1 Through -13 "Space systems - Fluid characteristics, sampling and test methods" • Action No. 209-1: Review of Revised Template for NASA Technical Standards • Action No. 182-1, Review of DRAFT ISO 21350, Off-the-shelf item utilization • Action No. 181-1: Agencywide Review of NASA-STD-5001A, Structural Design and Test Factors of Safety for Spaceflight Hardware http://standards.nasa.gov

4. DFRC Standards Activities (Cont’d): • DFRC Proposal Review: • GRC-2004-1, Determination of the Fracture Toughness of Advanced Ceramics at Elevated Temperature   • JPL-2004-16, Standards on Getters for High Vacuum Hermetic Microelectromechanical Systems (MEMS) Packaging   • JSC-2004-3, Structural Design and Verification Requirements for Glass, Ceramics and Windows in Human Space Flight Applications    • MSFC-2004-16, Standard Manned Spacecraft Requirements for Materials and Processes  • MSFC-2004-17, Design Guide for Composite Oxygen Tanks   • MSFC-2004-18, NASA Tailoring Standard for IPC-2221, Generic Standard on Printed Board Design   • MSFC-2004-19, Compilation and Evaluation of Existing Data on the Compatibility of Materials with High-Test Hydrogen Peroxide http://standards.nasa.gov

5. DFRC Standards Activities (Cont’d): • DFRC Proposal Review (Cont’d): • MSFC-2004-20, The Effects of High-Test Hydrogen Peroxide (HTP) on Structural Materials as Determined by Isothermal Microcalorimetry • MSFC-2004-21, Standard for Evaluating the Contamination Transfer Potential from Process Support Materials • MSFC-2004-22, NASA Sustaining Engineering Standard • MSFC-2004-24, NASA Foreign Object Debris Elimination Standard or Handbook • WSTF-2004-1, Update of Safe Use of Oxygen and Oxygen Systems ASTM MNL 36   • WSTF-2004-2, Hydrogen Hazard Analysis Protocol   • WSTF-2004-3, Detailed Revision of ISO/FDIS 15859 - Parts 1 through 13 http://standards.nasa.gov

6. DFRC Standards Activities (Cont’d): • OTHER ITEMS: • Open Items: • Action No. 256-1, EMB Approval of NASA-STD-5012, " Strength and Life Assessment Requirements for Space Propulsion System Engines“ • Review of KSC-2004-1, Technical Standards for Trend Analysis • No comments submitted from DFRC • Action No. 235-1, Review of Draft ISO/CD 16455-2 - Space Systems-Stress Corrosion Cracking -Part 2-Selection of metallic materials • Action No. 234-1, Review of Draft ISO/CD 16455-1 - Space Systems-Stress Corrosion Cracking -Part 1-Test methods for determining susceptibility of metals http://standards.nasa.gov

7. Other Program Status FY 04 FULL COST FUNDING 103 - 06 - 10 FOR FY2004 Civil Service Full Time Equivalents (FTE) FY 04 allocation 0 FTE FY 04 requirement – not recorded Civil Service Travel FY 04 allocation $0 K. FY 04 requirement $3 K. FY 04 Funding (Procurement Funds Only) FY 04 Funding - $40 K FY 04 Funding Commit - $40 K FY 04 Funding Obs - $40 K FY 04 Cost $28 K http://standards.nasa.gov

8. Other Program Status FY 05 FULL COST FUNDING 103 - 06 - 10 FOR FY 05 ($371K) Task 1.2.2 Develop Technical Standards and Supporting Information Integrating lessons learned into the NASA preferred standards Support for disciplinary working groups Task 1.2.3 Standards support/assessment Civil Service Full Time Equivalents (FTE) - 1.8 (full cost) Civil Service Travel - $3 K Procurement Funding (Labor and Material) - $40 K Center G&A and Service Pool - $328K Mandatory Standards Support (?) http://standards.nasa.gov

9. DFRC ITA Technical Standards Discussion Raymond Kacmar DFRC ITA http://standards.nasa.gov

10. The DFRC implementation of the ITA is a high-level Center staff function that provides senior technical and management oversight of select engineering activities, Mission and Ground Operations, and S&MA efforts in support of the programs. Key Characteristics of the ITA We will not “reinvent the wheel”. We recognize that much of what is called for within CAIB R7.51 is already done at DFRC, and we will incorporate that within the context of our operations (by independent funding and providing dedicated resources as necessary). For example: Flight Readiness Reviews/Airworthiness and Flight Safety Review Board activities Flight Assurance activities Many of the ongoing independent assessment activities http://standards.nasa.gov

11. Key Characteristics (Continued) We will improve those areas where DFRC is currently performing but have resource issues, for example: Lessons Learned support Systems Management Office - use ITA staffing to expand their presence There are also some areas that are not done at DFRC and we will build the capability to accomplish them. Centerwide Tracking and Trending Facilities independent assessment Implementation of Waiver Issues http://standards.nasa.gov

12. Managed collaboratively by the ITA Board, consisting of the DFRC Chief Engineer and S&MA Director, and the DFRC NESC Chief Engineer (non-voting) The ITA Board reports to the Center Director The ITA Board has signature authority (waivers, etc.) An ITA Director will run day-to-day ITA operations The ITA will consist of a core team, rotational assignees (1 - 2 year), matrixed experts and contractor support – 13 FTE , 2 WYE (FY05) Some realignment of responsibility may be required, but no functionality will be duplicated We recognize that success will be measured by becoming an asset, not a burden to the center. Again, a lot of the effort will not be new work but work already being done at the center. The ITA will encourage projects and line engineering to provide feedback on ITA activities. ITA Structure and Function http://standards.nasa.gov

13. Manage technical standards (including the waiver-granting authority of these standards). Approve safety and reliability assessment plans and products for all mission programs. Conduct periodic independent assessments using safety, reliability, quality, trend and risk analysis techniques as a check against similar program and project analyses. Supplement program and project problem reporting systems with independent inputs. Provide formal verification to appropriate decision authorities of mission and acquisition milestone readiness. Major ITA Functions http://standards.nasa.gov

14. There are two principal elements in executing engineering work: The first, is execution of line engineering work (work that produces a mission-related product) that is done for programs by a matrixed organization. The second, is that to ensure that the line engineering process is able to perform its work relatively dispassionately, there is an additional group that acts as an arbiter for technical issues. This group maintains the authority for applying and modifying technical standards, identifying issues and resolving technical disputes between line engineering and program line management. Note that people within the line engineering organization may conduct some aspects of ITA work (and vice versa) through appropriately controlled processes. Independent Authority http://standards.nasa.gov

15. For the NASA engineering community, Headquarters (through the Office of the Chief Engineer), provides overall policy, coordination, standardization, oversight, and when necessary direction of field activity engineering work. In the context of the ITA, this principally consists of: approving Agency-wide standardized engineering practices, including collaborative processes; providing policy and direction for the establishment, implementation, and modification of technical standards, including delegation of authority to Centers as appropriate; Headquarters ITA Functions http://standards.nasa.gov

16. Field activities (through the Center Director) provide independent controls and oversight of the line engineering work through ITA functions. In the context of the ITA, this principally consists of approving and overseeing standardized and project-specific engineering practices at each Center; approving and overseeing the implementation and modification of program-specific standards for each Center as delegated by Headquarters; providing oversight of line engineering work conducted in support of projects; establishing and executing ITA processes at Centers; acting as the primary technical authority for engineering-related disputes and issues within projects and programs, as delegated by Headquarters. Field ITA Functions http://standards.nasa.gov

17. Technical standards include Agency, Center, program, project, industry, and international standard processes and requirements for generically performing technical work or producing manufactured equipment, and are covered within NPD 8070.6, “Technical Standards. Project functional requirements include performance requirements specific to that project, and are covered within NPD 7120.4, “Program/Project Management.” For example, technical standards might provide analytic techniques and part requirements for a vehicle, project functional requirements might provide the velocity, volume, and mass requirements for that vehicle. Technical standards vs. Project requirements http://standards.nasa.gov

18. Technical standards: are developed or adopted by the engineering community, approved by the ITA and are applied and executed by line engineering personnel, and this application and execution is in turn overseen by both line engineering management and the ITA. By contrast, project functional requirements are established by project management, executed by line engineering using technical standards as the means for execution, and this execution is overseen by cognizant enterprise and Center programmatic management; Independent Agency oversight of this process is provided by associated Program Management Councils, the Independent Program Assessment Office, and Center Systems Management Offices. Technical standards vs. Project requirements Cont’d http://standards.nasa.gov

19. During authorization and formulation of each project, the list of applicable technical standards (including Center and program/project standards) will: be proposed by line engineering, concurred with by the program/project manager, and approved by the ITA manager for that Center as delegated by the NASA Chief Engineer. In addition, this list of standards will identify any exceptional cases in which standards are not intended to be incorporated in relevant project contracts. http://standards.nasa.gov

20. Most technical issues will be resolved among project management and the line engineering directorate based on a reasoned resolution of competing technical, schedule, and cost considerations. In such cases, appropriate technical, cost, and schedule strategies can often be developed that satisfy all requirements, or which lead to an appropriately developed and reviewed revision to those requirements. This process is overseen continually by the Center element of the ITA, and ITA actions are required for those cases in which technical standard requirements are proposed to be modified. In the event there are issues that are not satisfactorily resolved within the Center, or which require a solution for which the Center does not have authority or resources, the issue will be identified to the cognizant Mission Office Associate Administrator and the NASA Chief Engineer for concurrent resolution, including appropriately justified recommendations from program management, line engineering, and the Center element of the ITA on alternate courses of action. In the very unlikely event this process does not reach concurrent resolution, the issue will be identified to the NASA Administrator for final resolution. Resolution of Technical Issues http://standards.nasa.gov