330 likes | 515 Views
NASA Technical Standards Program Overview. Presented at the DEFENSE SPECIFICATION MANAGEMENT COURSE: PQM 103 February 11, 2004. Paul S. Gill NASA Technical Standards Program Office. Program Goals And Authority. Goals : Support NASA’s engineering function through:
E N D
NASA Technical Standards ProgramOverview Presented at the DEFENSE SPECIFICATION MANAGEMENT COURSE: PQM 103 February 11, 2004 Paul S. Gill NASA Technical Standards Program Office
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)
Traditionally, NASA “standards” were built around specific programs and organizations Shuttle, Space Station, Explorers… NASA field centers - MSFC, JSC,… “Standards” frequently included technical and programmatic requirements Substantial use was made of Mil-Std’s. NASA-wide technical standards were generally limited to specific areas: Safety, Mission Assurance, electronic components Construction of Facilities Data Communications Standards Technical standards were generally presumed “good forever” – until the next program decided to change them or specific problems were found Background And Context
Today Create and maintain common, multi-program NASA Technical Standards for NASA unique needs Make maximum use of applicable national and international standards through “adoption” as NASA Preferred Technical Standards (PL 100-113) Reference existing standards “as is” with program/ project tailoring (not re-write) to maintain traceability Use of “Preferred Standards” is voluntary Future?: Mandatory technical standards with waiver through Independent Engineering Technical Authority (Columbia Accident Investigation Board Recommendations) NASA Core Standards? Program Lists? Current Approach
Administrator Deputy Administrator Associate Deputy Administrator Chief of Staff Senior Advisor Chief Engineer Chief Health and Medical Officer Chief Information Officer Chief Scientist
NASA Technical Standards Program Other NASA Headquarters Offices NASA Chief Engineer (Code AE) (Theron Bradley, Chief Engineer) (Richard Weinstein, Standards Program Exec.) - Functional Standards - Program Level Coordination - Policy/Oversight/Approval - Program Sponsorship NASA Technical Standards Working Group (TSWG) (Paul Gill, Chair) NASA Engineering Management Board (Theron Bradley, Chair) - Center Representation - Program Guidance NASA Technical Standards Program Office (Paul Gill, Manager) - Center Approving Authority - Program Issues - Program Management - Standards Management System Topic and Discipline Working Groups http://standards.nasa.gov - Prioritization of Needs - Standards Development
Program Elements • Development of NASA Technical Standards • Support and Adoption of Voluntary Consensus/ Non-Government Standards (PL100-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
Engineering standards needs are identified through Centers and/or Discipline Working Groups Formal process (separate from Directives Management System) controls proposals submittal, screening, development, Center review, and approval Center Engineering Management Board member provides Center approval Chief Engineer approves for NASA Standards from other functional areas (Codes Q, AO, M) approved by HQ Associate Administrator Future: Common management process for all NASA Standards Enterprise concurrence for policy, overall impact Standards Program Processes
NASA Preferred Technical Standards Taxonomy
NASA Preferred Technical Standards • 59 NASA-Developed Technical Standards • 20 Engineering Standards • 20 Information Technology Standards • 19 Safety and Mission Assurance Standards • 2241 Adopted Standards • 1550 Non-Government Voluntary Consensus Standards • 663 DOD/MIL-STD’s • 28 Federal & CID Standards • In Development or Pending Adoption • 33 NASA Technical Standards in Development • 17 Non–NASA Technical Standards In Development • 719 Additional Standards Are Identified as Potential for Adoption • NASA Participation in the Standards Development Organizations in FY04 • 144 employees participating in 33 different Standards Developing Organizations • Leading or participating in the development of 197 Non-gov’t standards
Agencywide Full-text Technical Standards System • Initiated in FY2000: competitive, 5 year, fixed price contract • Non-Gov’t Standards Listings available to public; full text documents to nasa.gov only • Provides “one stop”, transparent access to standards from more than 111 Standards Developing Organizations (SDO’s) • NASA “preferred” technical standards: • Technical standards developed by NASA • Adopted standards from other sources • Center developed standards (JSC, KSC, MSFC, etc.) • Program documents: Shuttle, Space Station, Payloads • Other government standards (FAA, Navy, DoD, DoE, etc) • Links to related technical information (I.e. Material and Metal Database, SPECSINTACT, Logistic Parts Database, etc.) • Sophisticated, but user friendly search capability • Extensive metrics: accesses, downloads, documents, requestors...
Agencywide Full-text Technical Standards System (Cont’d)
Top 20 SDO Standards Downloaded Within Nasa.gov June 2001 - Number of SDO Documents Downloaded MIL 45043 AIA 17051 ASTM 13972 NASA Developed (Preferred) 13952 SAE 12984 NASA Center Developed 12688 Other Gov Stds 6971 ASME 6207 ISO 4178 IEEE 3293 IPC 2217 ASME(BPVC) 1263 IEC 1002 AIAA 685 NFPA(Fire) 635 AWS 514 CGA 505 CSA 425 Guide/Spec/Pub 423 EIA/TIA 422
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 uncontrolled • For all programs to date: • Over 6000 document update requests received • Over 1600 document update notifications sent
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 • 543 out of 1700 Lessons Learned now hot-linked to 355 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; 168 linked to date • Use of Lessons Learned system climbing
“Top 20” Lessons Learned/Best Practices Accesses via NTSP Website (NASA Employees/On-site Contractors) Jul 2001 – Oct 2003 A History of Aerospace Problems, Their Solutions, Their Lessons NASA Lessons Learned Information System (LLIS) NASA Preferred Reliability Practices for Design and Test System Engineering “Toolbox” for Design-Oriented Engineers Systems Engineering Office Lessons Learned Flight Project Lessons Learned Database Space Engineering Lessons Learned Software Engineering, Doing Requirements Right the First Time! Technical Design Review Practices Fastener Torque and Clamp Force Lessons Learned Launch Vehicle Design Process: Characterization, Technical Integration, Lessons Learned Interplanetary Mission Design Handbook Working on the Boundaries: Philosophies and Practices of the Design Process COTS-Based Software Development: Processes and Open Issues Best Manufacturing Practices Satellite Mission Operations Best Practices Lessons Learned in Developing Commercial Off-The-Shelf (COTS)Intensive Software Systems Spacecraft Electrical Harness Design Practice Design Guidelines for Assessing and Controlling Spacecraft Charging Effects Lessons from the Shuttle Independent Assessment
PREFERRED / CORE / MANDATORY TECHNICAL STANDARDS PROCESS FOR CITING ON CONTRACTS (PRELIMINARY) Start Voluntary Consensus Standards Adopted by NASA NASA-Developed Standards Codes AE, AO, Q NASA PREFERRED TECHNICAL STANDARDS (Maintained by NASA Technical Standards Program [NTSP]) No NESC, in Conjunction with the *NTSP Office, Recommend Core Standards OTHER TECHNICAL STANDARDS (Center-, Program/Project Developed) (Maintained by NTSP and Various Document Owners) EMB Concurs; NASA Chief Engineer Approves No Yes Yes CORE STANDARDS (Maintained by NTSP) ** Technical Team Review Mandatory for Consideration on Programs/Projects Engineering Directorate, with Program/Project Concurrence, Determines to Cite on Contracts/ As Program/Project Requirements No LEGEND: ITA: Centralized Agency-Level Independent Technical Authority—NESC ITEA: Center-Level Independent Technical Engineering Authority Cite with Proposed Tailoring? Tailoring Approved by ITEA/ITA Yes Use As-Is *The NTSP Office will identify standards in development and approved standards, and assist in the establishment of Technical Discipline Working Groups and Topic Working Groups. Use As-Is PROGRAM/PROJECT MANDATORY STANDARDS ** Rationale for negative position by ITEA/ITA provided to NTSPO for information relative to standard development and update. NASA Technical Standards Program 01/14/2004 Notify NTSP Office for Trending
NASA Preferred Technical Standards Published (Continued)
NASA Preferred Technical Standards Published (Continued)
NASA Preferred Technical Standards Published (Continued)
NASA Technical Standards In Development (Continued)
NASA Technical Standards In Development (Continued)
NASA Technical Standards In Development (Continued)
NASA Technical Standards In Development (Continued)