4-10-2002 http://standards.nasa.gov 1

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

NASA TECHNICAL STANDARDS PROGRAM BACKGROUND,

DEVELOPMENT AND PLANS

IHS MEETINGCOLORADO SPRINGS, COLORADO

APRIL 10, 2002

Paul S. Gill, Manager

NASA Technical Standards Program Office

4-10-2002 http://standards.nasa.gov 2

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

OVERVIEW

Technical Standards have been an integral part of NASA Programs and Projects developments and operations since the Agency was established in 1959. However, for years each Center was responsible for its own development and selection of non-NASA Technical Standards that met the needs of Programs and Projects for which they were responsible. There were few “Agencywide” applicable Technical Standards, mainly those in area of safety. Department of Defense Standards and Specifications were the foundation and main source for Technical Standards used by the Agency. This process existed until about 1997 when NASA embarked on a Program to convert NASA’s Center-developed Technical Standards into Agencywide endorsed NASA Preferred Technical Standards and the formal adoption of non-NASA Technical Standards (DOD, SAE, ASTM, ASME, IEEE, etc.) as NASA Preferred Technical Standards.

Technical Standards are important to the Agency for many reasons. For example, they are used in contract proposal reviews to verify inputs, in-house design and development actions, supporting contractor use, to capture lessons learned and new technology, and to maintain engineering excellence in research and development and operations. They provide a common base for interoperability. As noted by Greg Saunders, Director of the Department of Defense Standardization Program Office, interoperability and standardization are connected just as thunder and lightning. Lightning causes thunder, and the “right” type of standardization and standards results in the interoperability the Agency needs to win on the development and operation of spacecraft and associated instrumentation.

4-10-2002 http://standards.nasa.gov 3

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

OVERVIEW (Cont’d)

The NASA Technical Standards Program now has several key elements. They include the development of NASA-unique Technical standards; formal adoption of non-NASA Technical Standards, especially those developed by Voluntary Consensus Standards Developing Organizations; conversion of NASA’s Center-developed Technical Standards and, of considerable importance to the Agency’s Programs and Projects, the development of NASA’s Integrated Technical Standards Initiative. This unique Initiative resulted from interactions with many Managers and staff members of NASA Programs and Projects, plus individual engineering staff members of the Centers. The three focal points of the Initiative consist of the Agencywide Full-text Technical Standards System, Standards Update Notification System, and the Lessons Learned/Best Practices/Application Notes – Integrated Standards System. All of these Systems have been implemented and their further development and enhancement to meet the Agency’s engineering needs continues as experience and feedback are obtained from the users.

4-10-2002 http://standards.nasa.gov 4

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

4-10-2002 http://standards.nasa.gov 5

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

BACKGROUND AND CONTEXT

Traditionally, NASA “Technical Standards” were built around specific programs and organizations, e.g.,– Apollo, Shuttle, Space Station, Explorers…– NASA Field Centers - MSFC, JSC,…

Liberal use was made by NASA of MIL-STD’s. Agencywide Technical Standards were generally limited to specific areas:– Safety, Mission Assurance, Electronic Components– Construction of Facilities– Data Communications Standards

Technical Standards were mainly prescriptive and essentially “good forever”

Establishment and use of an Agencywide NASA Technical Standards Program has been established and accepted.

4-10-2002 http://standards.nasa.gov 6

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

GOALS AND AUTHORITY

Goals:Improve NASA’s Engineering CapabilityCapture and Preserve Engineering Lessons Learned and Best PracticesFacilitate the Insertion of Technology into all NASA Programs/Projects Ref: NASA Strategic Plan, Provide Aerospace Products and Capabilities (PAPAC)

Authority:NASA Policy Directive (NPD 8070.6), “Technical Standards”, October 10, 1997 NASA Preferred Technical Standards Program Plan, April 15, 1999

NASA Procedures and Guidelines (NPG 7120.5), “NASA Programs and Project Management Processes and Requirements”, April 3, 1998

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” (Revised February 10, 1998)

Delegation of Authority:Marshall Space Flight Center Designated by the Administrator as the Responsible Center for Management of the NASA Technical Standards Program

4-10-2002 http://standards.nasa.gov 7

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

OMB CIRCULAR A-119 POLICY

“Federal Participation in the Development and Use of Voluntary Consensus Standards and in Conformity Assessment Activities”

Establishes policy to be followed by Agencies in working with Voluntary Consensus Standards Development Bodies (non-Government) and in using Voluntary Consensus Standards (VCS), in accordance with Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (Public Law 104-113).

Requires Agencies to use Voluntary Consensus Standards (VCS), both domestic and international, in preference to Government standards products except where inconsistent with law or otherwise impractical.

Requires Agencies to provide support to VCS Development Bodies and encourage employees to participate in domestic and international VCS Development Bodies as Agency representatives in areas of the Agency’s mission and responsibility.

Annual Key Reporting Requirements

Justification for use of Government standards products in lieu of VCSs in procurement actions. Number of VCSs used in procurement actions. Number of government-unique standards products replaced with VCS products. Number of employees participating in VCS Developing Bodies.

4-10-2002 http://standards.nasa.gov 8

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

THE AMERICAN NATIONAL STANDARDS INSTITUTE’S NATIONAL STANDARDS STRATEGY FOR THE UNITED STATES

<http://web.ansi.org/public/NSS.html>

Participate in standards development efforts to define technical specifications that met public objectives, and encourage the same approach internationally

Encourage more use of the principles embodied in accreditation by recognizing the ANSI process as providing sufficient evidence that American National Standards (ANS) meet

federal criteria for voluntary consensus standards

Identify needed new standards and pursue global solutions

Encourage standards developers to emphasize use of information technology, compatible tools, distribution systems that met user needs, and need to take advantage of “best in class” technologies and processes

Establish processes to ensure timely communication of standards related needs and activities – both internal ones and those in inter-governmental activities – so that voluntary consensus processes can provide the best standards development support

Develop and implement appropriate training programs for government personnel at all levels

SELECTED RECOMMENDED GOVERNMENT TACTICAL ISSUES (ACTIONS) BEING ADDRESSED

4-10-2002 http://standards.nasa.gov 9

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

WHY NASA NEEDS TO DEVELOP AND ADOPT AGENCY-WIDE TECHNICAL STANDARDS PRODUCTS

• Even performance-based contracts will require some standards• Technical Standards are needed for “in-house” projects• Technical Standards are needed in NASA-unique project

Interface Control Documents (ICD’s)• Standards can be provided for “guidance” even on performance

contracts and used for reference in the evaluation of proposals.• Technical Standards are an important mechanism for collecting

and communicating experiences (Lessons Learned/Best Practices) within/among Centers

• Adopting non-Government Technical Standards meets the requirements of OMB Circular A-119, Public Law 104-113, and NASA Policy Directive NPD 8070.6A

4-10-2002 http://standards.nasa.gov 10

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAMAdministrator

Deputy Administrator

Associate Deputy Administrator

Chief of Staff

Senior Advisor

Chief Engineer

Chief Health and Medical Officer

Chief Information Officer

Chief Scientist

4-10-2002 http://standards.nasa.gov 11

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

NASA Chief Engineer’s Office (Code AE)

NASA Technical Standards Program Office

(Paul Gill, Manager)

NASA Engineering Standards Steering Council

(Paul Gill, Chair)

Topic and Discipline Working Groups

(Chairs: As Assigned)

Development of Standards Unique to Needs

NASA Preferred Technical Standards

Products Website

FUNCTIONAL DIAGRAM FOR THE NASA TECHNICAL STANDARDS PROGRAM

Policy/Oversight/Approval

Program Management

Center Representatives Program Guidance

Prioritization of NeedsStandards Development

http://standards.nasa.gov

NASA Engineering Management Council

Center Approving AuthorityProgram Issues

NASA Headquarters Offices

Standards Management System

Program Sponsorship

4-10-2002 http://standards.nasa.gov 12

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

MAJOR PROGRAM ELEMENTS

NASA-Unique Standards Development Initiative

Conversion of Center-Unique Standards to NASA Preferred

Technical Standards (NASA or Non-Government) Initiative

Voluntary Consensus Standards (Non-Government) Adoption and

Development Initiative

Standardization Awareness Initiative

NASA Integrated Technical Standards Initiative

–Agencywide Full-text Technical Standards System

–Standards Update Notification System

–Lessons Learned/Best Practices/Application Notes - Standards Integration System

4-10-2002 http://standards.nasa.gov 13

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

AGENCYWIDE PREFERRED TECHNICAL STANDARDS

(Development and Adoption Initiatives) • Engineering

– 20 NASA-Unique Standards Published, 15 in Development– 943 Standards Adopted From 40 Non-Government Voluntary Consensus Standards

(VCS) Organizations– 584 MIL-STD’s, MIL-SPECS– 9 Federal/CID Standards– 91 Center-Unique Standards Identified as Candidates for Conversion to a NASA Standard or

VCS• Safety and Mission Assurance

– 22 NASA Standards Published

• Information Technology– 19 NASA Standards Published

• Data Communications

– 22 Consultative Committee for Space Data Systems (CCSDS) Standards Published/Adopted

• Facility Construction

– Linked to SPECSINTACT system with >4000 standards

• NASA Personnel Involved in Over 145 National and International Standards Developing Organizations, Committees and Working Groups

4-10-2002 http://standards.nasa.gov 14

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

NASA INTEGRATED TECHNICAL STANDARDS INITIATIVE

Consists of Three Agencywide (Full-Text, Update Notification, Lessons Learned - Standards Integration) Systems

Uniqueness is the Integration of Three Systems Into One Focused Web Site (“One Stop Shop”) for Agency’s Engineering Applications

Provides an Agencywide Asset Accessible by All Field Centers/ Facilities, JPL, Headquarters Employees, and On-Site Support Contractors

Minimizes Agency Costs and Maximizes Technical Standards and Related Information for Use by Programs/Projects

Metrics Will Enable Considerable Management Visibility on Agency’s Actual Technical Standards Usage and Needs

4-10-2002 http://standards.nasa.gov 15

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

Increase use of non-Government Voluntary Consensus Standards (VCS) Products.– Recommend to Program Office VCS products for adoption as NASA

Preferred Technical Standards.– Identify Government-Unique Standards Products, Including Center-Unique

Standards for replacement with VCSs.– Participate in Standards Development Efforts of VCS Development Bodies.

Develop New NASA Technical Standards Products– Where VCSs do not exist or are not practical for use (such as Safety, NASA-

unique,etc.), Propose New Standards Products or the Standards Program to Develop or Adopt

– To capture “Lessons Learned” and “Best Practices”– For use on “in-house” activities (such as ICD’s)

COMMUNICATE THE EXISTENCE OF THE NASA TECHNICAL STANDARDS

PROGRAM AND WEBSITE (http://standards.nasa.gov)

AREAS FOR PARTICIPATION OF NASA EMPLOYEES IN THE NASA TECHNICAL STANDARDS PROGRAM

4-10-2002 http://standards.nasa.gov 16

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

GUIDELINES FOR EMPLOYEE PARTICIPATION IN NON-GOVERNMENT VOLUNTARY CONSENSUS STANDARDS DEVELOPING BODIES

Agency Participation In and Endorsement of Decisions– Participation Does Not Necessarily Imply Agency Agreement With, or Endorsement of,

Decisions Reached– May Serve as Chairpersons or Other Capacity– May Vote at Each Stage of Development Process Unless Prohibited by Law or NASA

Limitations of Participation– Refrain from Involvement in the Internal Management of Voluntary Consensus Standards

Developing Bodies– Must Not Dominate Such Bodies– Must Avoid the Practice or the Appearance of Undue Influence

Responsibilities– Express Views That are Consistent With Established NASA Views– Ensure Participation Is Consistent With Agency’s Mission, Authorities, Priorities, and

Budget Resources– Provide Input to Agency-wide Directory Regarding Employee’s Participation and Standards

Body Federal Contractors

– Do Not Fall Within the Definition of an Agency– If Participating in Behalf of Agency (As Representative or Liaison), Contractor Must comply

With Federal “Participation” Policies of OMB Circular A-119

4-10-2002 http://standards.nasa.gov 17

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

4-10-2002 http://standards.nasa.gov 18

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

PROGRAM DIRECTION

Increase NASA Use of Voluntary Consensus (Non-Government) Standards Products– Adopt What We Use– Replace NASA/Other Government-Unique Standards with Voluntary Consensus

Standards (VCS)– Realign Participation in VCS Development With NASA Needs

Selective Development of NASA-Unique Technical Standards– Where NASA Needs Unique or Critical (e.g.safety)– To Capture “Lessons Learned”; Transition to VCS– For Use on “In-House” Activities

Better Harmonization With National/International Standards– To Maintain US Competitiveness– To Enhance International Cooperation and Trade

Fully Explore the Potential of Web based Standardization Information– Incorporate Standards Development Into Management Process– Integrate Program Activities With National/International Networks– Improve Availability of VCS Products Agencywide

4-10-2002 http://standards.nasa.gov 19

NASA TECHNICAL STANDARDS PROGRAMNASA TECHNICAL STANDARDS PROGRAM

SUMMARY

Program Enjoys Strong “Grass Roots” Engineering Support Throughout the Agency and Endorsement of Senior NASA Management

Program’s Website Continues to Experience Increased User Visits From All NASA Facilities

The NASA Integrated Technical Standards Initiative is a Unique Endeavor – Not Duplicated Within Government or Industry