Paul Gill - NASA Technical Standards Program Office

1. NASA Technical Standards ProgramStatusPresented at theEngineering Management Board MeetingApril 29,2004 Paul Gill - NASA Technical Standards Program Office

2. Program Goals And Authority Goals: Support NASA’s engineering function through: • Providing the technical standards needed for NASA programs • Improving the practice of engineering by integrating experience into the engineering process Authority: • NPD 8070.6B, “Technical Standards”, May 7, 2003 • NASA Preferred Technical Standards Program Plan, April 15, 1999 • NPG 7120.5B, “NASA Program and Project Management Processes and Requirements”, November 21, 2002 • Public Law 104-113, “National Technology Transfer and Advancement Act of 1995” • OMB Circular A-119, “Federal Participation in the Development and Use of Voluntary Consensus Standards and Conformity Assessment Activities” (1998) • NPG 8070.x , Technical Standards Processes (In Development)

3. Program Elements • Development of NASA Technical Standards • Support and Adoption of Voluntary Consensus/ Non-Government Standards (PL104-113) • Transition of Center-Developed Standards with multi-program application to NASA Preferred Technical Standards (NASA or Non-Government) • NASA Integrated Technical Standards System • Agencywide Full-text Technical Standards System • Standards Update Notification System (SUNS) • “Hot link” integration of Lessons Learned/Best Practices/Application Notes with NASA Technical Standards • Standards Awareness

4. NASA TECHNICAL STANDARDS IN DEVELOPMENT (SEPTEMBER 2003- MARCH 2004)

5. NASA TECHNICAL STANDARDS IN DEVELOPMENT (CON’T) (SEPTEMBER 2003- MARCH 2004)

6. NASA TECHNICAL STANDARDS IN DEVELOPMENT (CON’T) (SEPTEMBER 2003- MARCH 2004)

7. NASA TECHNICAL STANDARDS IN DEVELOPMENT (CON’T) (SEPTEMBER 2003- MARCH 2004)

8. NASA TECHNICAL STANDARDS IN REVISION (SEPTEMBER 2003- MARCH 2004)

9. FY04 PROPOSALS FOR DEVELOPMENT OF NASA TECHNICAL STANDARDS

10. Purpose: To Identify Priorities, provide for necessary reviews of standards to establish Core/Mandatory Technical Standards Plans: Leverage off existing or Establish planned disciplinary working groups (NASA M&P working Group, PBMA, etc.) to: - Pursue development activities on new NASA engineering standards and identification of gaps relative to establishing agency core/ mandatory Technical standards (extensive effort) , plus designation of associated “warrant holders” - Increase efforts to identify lessons learned and application notes for integration with NASA technical standards. - Support the development of a process for tailoring and waivers of technical standards not considered directly applicable for use on A program. Status: Pop-04 solicitations for new NASA engineering standards made/associated topic working groups being chartered. Initial plan prepared for standards disciplinary working groups formal designation and chartering. Evaluating USAF list of compliance standards with NASA Preferred list for potential identification of NASA’s Core/Mandatory standards. (Need chartered working groups along with NESC for review and buy-in) Key Effort in FY04-FY06:Establish Core/Mandatory Standards

11. Identify requirements for additional NASA Technical Standards Possible fallout from CAIB recommendations, +… Complete review of 900+ Non-Gov’t Performance-based standards (ISO, ASTM, SAE, etc.) that are pending adoption Maintain/Enhance Agencywide Full-text Technical Standards System Comply with Agency Architecture, Enhance Search Capabilities, etc. Identify/register non-program technical standards for update tracking through SUNS Capture standards experience in “Application Notes/Lessons Learned” for linking to NASA Preferred Technical Standards Helps the whole agency; “priceless” Additional Efforts in FY04-FY06

12. NASA PREFERRED TECHNICAL STANDARDS STATUS TO DATE • NASA Preferred Technical Standards • 59 NASA Developed Technical Standards • 21 Engineering Standards, 20 IT Standards, & 18 Safety And Mission Assurance Standards • Technical Standards Adopted by NASA • 2247 Adopted Standards • 1547 Voluntary Consensus Standards • 672 Mil-STD’s, Mil-Spec’s • 28 Federal & CID Standards • 981 Pending Adoption (Non-NASA) - (705 Performance, 276 Acquisition) • 30 NASA Preferred Technical Standards in Development/Revision 20 In Development • 16 Being Revised/Revalidated • 7 Revisions in Progress • 9 Due/Overdue for Revalidation

13. ON-GOING SURVEY ON “USE” OF TECHNICAL STANDARDS Over 3782 Unique Users Have Responded to the Questionnaire from July 8, 2003 to February 20, 2004.

14. Agencywide Full-text Technical Standards System • Composed of Standards from over 111 Standards Developing Organizations Including: • Technical standards developed by NASA (Preferred) • Center developed standards (JSC, KSC, MSFC, etc.) • Program documents: Shuttle, Space Station, Payloads • Other government standards (FAA, Navy, DoD, DoE, etc) • Single Interface (online “One Stop”) – Transparent to users • Sophisticated, but user friendly search capability • Extensive metrics: accesses, downloads, documents, requestors... • Over 170,000 documents downloads to date (June 2001 – March 2004)

15. Agencywide Full-Text Technical Standards System

16. Agencywide Full-Text Technical Standards System (continued) “Top 20” SDO Accesses Period: Jul 2001 – Mar 2004

17. Standards Update Notification System (SUNS) • SUNS allows users to register standards they use, and receive automatic notification when standards are revised, re-issued • Changes to technical standards can have major impacts on the safety, performance, reliability, and cost of programs/projects • Using out-of-date standards—unless required to meet specific need • Ignores improvements and misses the benefits of experience • Exposes programs/projects to the risk of repeating those failures that led to update of the standard • Pilot Test on Space Shuttle Solid Rocket Booster/TVC System • 552 standards cited; all but 124 cancelled, replaced, or not accessible for verification • For all programs to date: • Over 6500 document update notifications requested (Over 50% for Preferred Technical Standards) • Approx. 1950 document update notifications sent

18. PIC 04-04 APPROVED 2/25/2004 – ENGINEERING STANDARDS AND SPECIFICATIONS CITED IN NASA SOLICITATIONS AND CONTRACTS • PURPOSE: To establish a uniform Agencywide approach for ensuring that all engineering standards and specs cited in solicitations and contracts are complete and of the latest version. • A NASA Engineer assigned to a procurement is responsible for assuring that NASA Preferred Technical Standards/other engineering standards/specs cited in solicitations/contracts have been: • Thoroughly reviewed and applied appropriately. • Are the latest version. • Have been registered with the NASA Standards Update Notification System (SUNS) to ensure that all future revisions will be automatically sent to the NASA Engineer for evaluation/assessment relative to applicability. • Final solicitations/contracts with an estimated value >$5M, and acquisitions of any value for equipment or analysis for spaceflight systems, shall NOT BE ISSUEDunless WRITTEN DOCUMENTATION [from the NASA Engineer responsible for the acquisition or ITEA] relative to the above bullet is included in the acquisition package. The initiating program/project office ensures the required documentation is signed by the responsible NASA Engineer or ITEA. • If written documentation is not contained in the package, the Contracting Officer informs the initiating program/project office that it must be provided prior to release of a final solicitation. • When the NASA Engineer responsible for a procurement notifies the Contracting Officer of the applicability/impact of an update to an engineering standard/spec, the Contracting Officer, with the NASA Engineer and COTR, assess whether any procurement action is required; the Contracting Officer accomplishes any necessary procurement action.

19. Integration Of Lessons Learned/ Application Notes With Standards • NASA Lessons Learned System documents problems and improved guidance from program and project experience • Linking Lessons Learned with standards provides basis for interpretation/use and update of standards • Users alerted to Lessons Learned at the time they come looking for the standards • Current status • Over 600 out of 1700 Lessons Learned now hot-linked to 420 NASA preferred and non-government technical standards • “Reverse” search capability permits users to view specific lessons learned by technical discipline and view the standards linked to them • Now adding “Application notes” from standards users that clarify or limit the scope, use, or context of standards; 170 linked to date • Use of Lessons Learned system climbing

20. FY04 NASA TECHNICAL STANDARDS WBS XX-297-10-00/XX-103-06-10 Obligations/Cost Plan vs. Actuals

21. Full Cost For the Program ** - OGL by several Centers is for additional Procurement funds, primarily to develop new technical standards. Most of the OGL requested will be covered within the original guidelines (3.3M) by making appropriate adjustments from the MSFC procurement guidelines, which was put as a place holder for new proposals in F4 – FY10.

22. Backup Charts