NASA TECHNICAL STANDARDS PROGRAM

1
NASA TECHNICAL STANDARDS WORKING GROUP MEETING
March 9-10, 2004 NASA Headquarters Washington,
D.C.
2
AGENDA TUESDAY MARCH 9, 2004
TUESDAY MARCH 9, 2004 830 845 Welcome
Gill/Weinstein 845
900 Introductions / Announcements 900 1000
Program Status Gill - Engineering
Standards in Development / Revalidation /
Adoption - Engineering Standards Development
Process / Revised Template For NASA Technical
Standards - Program Metrics (Effectiveness,
etc.)/ NASA Technical Standards System -
FY03 A-119 Report - NTSP Office Review of
Programs Applicable Document Lists 1000
1015 Break 1015 1100 Technical Discipline
Working Gill Groups / Topic Working
Groups 1100 1200 Code D Reorganization Bradle
y/Weinstein / Standards Policy 1200
100 Lunch
100 145 Lesson Learned Activities Robinson 1
45 215 NASA Awards and Contributions
Hussey 215 245 Recognition for
Contributions Gill to the NASA
Technical Standards Program 245
300 Break 300 330 Consultative Committee
for Kelley Space Data Systems
(CCSDS) Standards Activities 330 400
Chief Information Officer (CIO)
Benedict Standards Activities 400
430 Safety and Mission Assurance
Harkins Standards Activities 430 Adjourn
3
AGENDA WEDNESDAY - MARCH 10, 2004
Special Topics (Continued) 1245 130 Air
Force/Space Missile Ingram-Cotton
Command Standards
Activities 130 200 Nondestructive Evaluation
Mih (NDE) for Aerospace
Composites Standard Activities 200
230 NASA Configuration Management
Torres Standard Activities 230 300 ISO
TC20/SC14, Space Weinstein/Schultz Sys
tems and Operations Activities / ISO Review
and Adoption Process 300 315 Break 315
400 FY04 Budget / POP Call FY05 Gill -
FY05 POP Schedule, Criteria Submission
Guidelines - Full Cost Accounting Impact on
Standards Program 400 430 Enhancements to
NASA Technical Gill Standards System
Architecture 430 445 New Action Items Review
Bailey Future NTSWG Meetings Schedule
Gill 445 Adjourn
WEDNESDAY MARCH 10, 2003 830 1000
Center/JPL Reports All Centers/JPL - Status
of Actions - Standards Development Status -
FY05 and FY06 Requirements, Including RD,
Manpower, and Travel - Each Centers ITEA
Approach to Technical Standards 1000
1015 Break Special Topics 1015 1100 AIAA
Standards Program Day - AIAA Structure and
Business Plan - ISO TC20/SC14 Activities 1100
1145 NAVSEA Standards and
Rogers Waiver
Process 1145 1245 Lunch
4
PROGRAM STATUS Paul S. Gill
5
NASA TECHNICAL STANDARDS WORKING GROUP (NTSWG)
NTSWG CHAIR Paul Gill NTSWG EXECUTIVE
SECRETARY Brenda Bailey CENTER
REPRESENTATIVES ARC Phil Luna/Laura
Doty DFRC Ray Kacmar GRC Frank Greco/Dan
Gauntner GSFC George Alcorn/Steven
Scott JPL Cheng Hsieh (Interim) JSC Nick
Lance KSC Larry Schultz/Eric Ernst LaRC Richard
Foss MSFC Barry Musick/Wendell Colberg SSC Bill
St. Cyr/Clifton Arnold WSTF Harold Beeson/David
L. Baker -----------------------------------------
--------------------------------------------------
--------------------------------------------------
------HEADQUARTERS REPRESENTATIVES Richard (Dick)
Weinstein, Code D Robert (Bob) Benedict, Code
V John (Jack) Kelley, Code MT Wil Harkins and
Wayne Frazier, Code QS
6
NASA PREFERRED TECHNICAL STANDARDS STATUS
NASA ENGINEERING STANDARDS IN DEVELOPMENT/REVISIO
N (SPONSORED BY CODE D)
7
NASA TECHNICAL STANDARDS IN DEVELOPMENT (SEPTEMBER
2003- MARCH 2004)
8
NASA TECHNICAL STANDARDS IN DEVELOPMENT
(CONT) (SEPTEMBER 2003- MARCH 2004)
9
NASA TECHNICAL STANDARDS IN DEVELOPMENT
(CONT) (SEPTEMBER 2003- MARCH 2004)
10
NASA TECHNICAL STANDARDS IN REVISION (SEPTEMBER
2003- MARCH 2004)
11
Technical Standards In Development (Updated March
3, 2004)
Document Number NASA-STD-0001 Document
TitleNASA Configuration Management (CM)
Standard Task Description Develop a NASA CM
Standard to strengthen the requirements and
implementation of configuration
management. Center MSFC
Approved Resources
Notes
Planned Schedule
Status/Issues (Technical, Schedule, Resources,
Other)
Determined by NTSP Office
12
Technical Standards In Development (Updated March
3, 2004)
Document Number NASA-STD-5015 Document Title
Nondestructive Evaluation (NDE) for Aerospace
Composites Task Description Develop an NDE
Standard for various aerospace composite
structural components. Center JPL
Approved Resources
Notes (1) This is a joint effort between JPL
and LaRC. Ed Generazio/LaRC has agreed to share
in the funding. (2) Consolidates two other
Composites related proposals submitted by JPL.
Planned Schedule
Status/Issues (Technical, Schedule, Resources,
Other)
Determined by NTSP Office
13
NASA-DEVELOPED TECHNICAL STANDARDS DUE FOR
REVALIDATION
14
NASA ENGINEERING STANDARDS REVALIDATION STATUS

• Revalidation confirms that the standard is
  current and that no changes to the standard are
  required, to be completed within 5 years of the
  current baseline, revision, or revalidation date.
• Revalidation Process
• NTSP Office notifies the Office of Primary
  Responsibility (OPR)/OPR Designee and Center
  NTSWG member that revalidation is due.
• The OPR Designee reviews the standard within the
  5-year timeframe to confirm that the standard is
  current and no changes are required.
• The OPR Designee prepares, signs, and submits the
  original Notice of Revalidation to the NTSP
  Office.
• If action is not taken within the timeframe, the
  NTSP Office initiates action.

() Code Q and Code V status unknown regarding
revisions in progress
15
VCS NATIONAL AND INTERNATIONAL STANDARDS IN
DEVELOPMENT (SPONSORED BY CODE D)
16
VCS - NATIONAL STANDARDS IN DEVELOPMENT
(SPONSORED BY CODE AE)
17
VCS - INTERNATIONAL STANDARDS IN DEVELOPMENT
(TC20/SC14 - SPONSORED BY CODE D (CONTD)
(OCTOBER 2003-February 2004)
Summary
18
STANDARDS ADOPTION SUMMARY STATUS TO DATE

• ADOPTED/PENDING ADOPTION SUMMARY
• Total 3,228 - (1660 Performance, 1568
  Acquisition)
• 2,247 Adopted (Non-NASA) - (955 Performance, 1292
  Acquisition)
• 981 Pending Adoption (Non-NASA) - (705
  Performance, 276 Acquisition)
• 32 Performance Standards Forwarded to NASA Chief
  Engineer for Approval
• 276 Acquisition, 673 Performance Standards Not
  Yet Sent Out to NTSWG
• Participation In VCS Development For FY03 Per
  A-119
• 33 Standards Developing Organizations
• 144 NASA Participants
• 197 Non-Govt Standards

19
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-STDs, Mil-Specs
• 28 Federal CID Standards
• 29 NASA Preferred Technical Standards in
  Development/Revision (Code D Sponsored)
• 20 In Development
• 16 Being Revised/Revalidated
• 7 Revisions in Progress
• 9 Due/Overdue for Revalidation
• Two Proposals Received from GRC
• Determination of the Fracture Toughness of
  Advanced Ceramics at Elevated Temperatures
  (Salem)
• Standards for Photovoltaic Array (Bailey)

20
REVISED NASA ENGINEERING STANDARDS DEVELOPMENT
PROCESS
21
REVISED NASA ENGINEERING STANDARDS DEVELOPMENT
PROCESS

• Revision of the 5-Step Process (Redlined)
  Resulted from Decisions Made at the October 2004
  NTSWG Meeting
• Detailed Procedure for the Process was Developed
  to Provide
• Better Structured Agencywide Review
• Documented Reviews/Comments by Individual
  Programs/Projects/Directorates at Each
  Center/Facility to Ensure Adequate Agencywide
  Review
• Separate Action Assignment for Obtaining EMB
  Concurrence
• An Example Resolution Matrix
• ISSUE Enterprise Reviews

22
PROCESS FOR DEVELOPMENT OF NASA ENGINEERING
STANDARDS SPONSORED BY THE NASA CHIEF ENGINEER
 
NASA Technical Standards Working Group (Formerly
Engineering Standards Steering Council) Engineer
ing Management Board (Formerly Engineering
Management Council)
(1) If Comments Cannot be Resolved, Proceed to
the Optional Stage
23
NASA FY2003 OMB CIRCULAR A-119 ANNUAL REPORT

• On-line Report Submitted January 2004 to NIST
• NASA had 144 Employee Participants in 33
  Voluntary Consensus Standards (VCS) Bodies
• 10 Increase in Number of Participants
• There were 266 Categorical New VCSs Adopted for
  use in FY 2003
• NASA Substituted 1 Voluntary Consensus Standard
  for a Government Unique Standard
• ASTM-MANL-36 for NSS 1740.15
• Participant Information was Updated

24

• Agencywide Full-Text Technical Standards System
• Standards Update Notification System (SUNS)
• Lessons Learned/Application Notes/Technical
  Standards System

25
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.
26
Agencywide Full-Text Technical Standards System
27
Agencywide Full-Text Technical Standards System
(Continued)
Accesses/No. of Center Employees
Downloads/No. of Center Employees
28
Agencywide Full-Text Technical Standards System
(continued) Top 20 SDO Accesses
NASA.gov Domain Period Jul 2001 Feb 2004
29
TOP 20 CENTER-DEVELOPED STANDARDS
DOWNLOADED (6/1/2001- 3/1/2004)
30
STANDARDS UPDATE NOTIFICATION SYSTEM (SUNS)

• STANDARDS UPDATE NOTIFICATION SYSTEM (SUNS)
  STATUS
• Period 4/1/2001 3/4/2004
• 6,446 Update Notifications Requested
• 1,866 Update Notifications Sent by Update
  Providers
• Over 56 of Unique Requests are for NASA
  Preferred Technical Standards
• Ratio of Access to SUNS from Full-Text is 21
• Programs/Projects With Highest Utilization of
  SUNS
• JPL Standards Program
• KSC Library
• KSC Acquisition Pollution Prevention (AP2)
• Most Requested Notifications from SDOs
• ASTM (1229)
• MIL (1400)
• SAE (726)
• SUNS-Related Activities
• Planned Procurement Information Circular (PIC) is
  expected to be released requiring
  programs/projects to utilize SUNS for every
  RFQ/RFP to ensure latest versions are
  usedapplicable to Flight and Ground Support.

31
NTSP OFFICE REVIEW OF PROGRAM APPLICABLE
DOCUMENT LISTS VIA SUNS

• The NTSP Office was tasked by the NASA Space
  Shuttle Program Office to review Applicable
  Document Lists for currency, NASA Preferred
  Status, etc.
• Space Shuttle
• NSTS 08102, Program Document Description and
  Status Report
• Most documents are 30-40 years old
• 82 of MIL documents have been superseded/canceled
  
• 88 of NASA NMIs/Handbooks have been
  canceled/superseded/replaced
• 54 of documents listed are JSC/KSC/MSFC
  Center-developed with no information relative to
  current OPR or document status
• 9 currently eligible for update notifications
  via SUNS

32
NTSP OFFICE REVIEW OF PROGRAM APPLICABLE
DOCUMENT LISTS VIA SUNS (Continued)

• Orbital Space Plane (OSP) - Program recently
  cancelled
• 186 Applicable Documents (Review Requested by
  JSC/OSP)
• 29 documents not found via the Technical
  Standards Website
• 17 document No. / revision discrepancies
• 1 draft document
• 180 Applicable Documents (Review Requested by
  Chief Engineers Office)
• 8 documents not found via the Technical Standards
  Website
• 56 document revision discrepancies
• 9 superseded/canceled documents
• 77 unique documents accepted for update
  notification in SUNS
• 175 Statement of Work / Data Procurement Document
  Applicable Documents (Review Requested by
  MSFC/OSP)
• 2 superseded / cancelled documents however, the
  superseding documents were listed
• 42 unique documents accepted for update
  notification in SUNS

33
Access to Lessons Learned Via Lessons
Learned/Application Notes/Technical Standards
System
To Date  543 LL out of 1700 are linked to 354
NASA and Non-Government Standards.  168
Application Notes have been submitted and linked.
34
Engineering Experience Lesson System(EELS)
Input
Storage
Usage
Engineering Experience Lessons Database
Search Presentation Engine
Web-Based Lesson Uploader
Media Attachments
EELSDB
MSFC Lessons Learned Sources
Lessons Input Interface
Various Engineering Lessons Sources
35
Program Awareness

• Program Presentations From October 2003-February
  2004
• Space Shuttle Program Office Presentation
  November 18, 2003
• Defense Specification Management Course PQM 103
  - February 11, 2004
• Standards And Architectures For Space Modular
  Systems Workshop (Sponsored by Code T )
  February 18, 2004
• Aerospace Standards Users Group February 25,
  2004

36

• FY04 Program Budget Status
• Obligation and Cost
• Full Cost Accounting Issues

37
FY04 NASA TECHNICAL STANDARDS WBS
XX-297-10-00/XX-103-06-10 Obligations/Cost Plan
vs. Actuals
93 Obs Plan
84 Cost Plan
38
MSFC FULL COST ACCOUNTING RESOURCE ISSUES FY04
WBS 62-103-06
-- FTEs and Contractors include Standards,
Software
39
FULL COST ISSUES/CONCERNS
- General confusion regarding how to
implement full cost - Inconsistency
of full cost rates - CFOs deducting
for cost pools, labor, travel, etc., Without
consulting with Program Managers
- Not clear if the full cost the
CFOs submitted for FY04 will be enough to
actually cover full cost - Centers
must be certain they include all full cost
elements in the pop submit

40
REVISED TECHNICAL STANDARDS TEMPLATE
41
REVISED TECHNICAL STANDARDS TEMPLATE

• Purpose of developing the template
• To provide the author a well-defined standard
  consistent format for use when developing the
  standard
• To provide a model of clear, accurate
  communication that is simple enough to use in a
  time-efficient manner
• Adaptable to the criteria of various standards

42
REVISED TECHNICAL STANDARDS TEMPLATE(CONT)

• Comments Boxes
• Indicate Where, When, and What Type Of Data
  Should Be Inserted
• Provide Improved Boilerplate Text
• Provide Additional Formatting Instruction
• Give Detailed Information On Figure And Table
  Numbering

Note Instructions for Viewing Comment Boxes
Are Provided In A Separate Read Me File
43
REVISED TECHNICAL STANDARDS TEMPLATE(CONT)

• Future Plans
• Send out to several experienced authors of NASA
  standards and the NTSWG for review and comments
• Incorporate any changes resulting from review
• Make accessible from the NASA technical standards
  system for use by Topic Working Group in the
  development/revision of the technical standard

44
Engineering Discipline Working Groups(Communities
of Interest)
45
Engineering Discipline Working Groups(Communities
of Interest)

• Problem
• Extensive pockets of knowledge exist, but lack
  structure
• Engineering communities of interest exist within
  the Agency
• Expertise de-centralized
• Need inter-group collaboration
• Potential for duplication of effort exists

46
Existing Technical Working Groups
47
STANDARDS TOPIC WORKING GROUPS
48
STANDARDS TOPIC WORKING GROUPS (CONTINUED)
49
TECHNICAL DISCIPLINE CATEGORIES
50
PROPOSED WORKING GROUP ORGANIZATION
NASA CHIEF ENGINEER
NESC
EMB
DCE
EDCO
NTSP
ITA/ ITEA
EDWG 1
STWG 1
EDWG 2
STWG 2
EDWG n
STWG n

• NASA Engineering Safety Center (NESC)
• Discipline Chief Engineers (DCE)
• Independent Technical Authority (ITA)
• Independent Technical Engineering Authority
  (ITEA)
• Engineering Management Board (EMB)
• Office of the NASA Chief Engineer (Code D)

51
ANTICIPATED APPROACH

• Identify All Active Technical Working Groups
• Validate Current Standards Topic Working Group
  Information
• Validate Technical Discipline Categories
• Define Initial Structure Of EDWGs
• Create and Charter EDWGs
• Assign Chair For Each EDWG
• Train Chair (Whys And Hows, Charter)
• Establish Inter And Intra Communication Network
• Identify Gaps In Work Needed or Duplicated
• Propose Additional EDWGs or STWGs To Fill Gaps

52
WHERE DO WE GO FROM HERE?

• ?

53
NASA TECHNICAL STANDARDIZATION AWARDPROPOSAL
54
NASA TECHNICAL STANDARDIZATION AWARDPROPOSAL

• Purpose
• Recognize outstanding contributions to the
  development and use of technical standards as
  applied to the advancement of NASA
• Programs and projects.
• Rationale
• Given the extensive efforts devoted to technical
  standards activities and importance to agency, A
  distinct award for outstanding contributions is
  warranted to recognize substantive
  accomplishments.
• Background
• Other government agencies and non-government
  standards developing organizations have awards
  for high-level recognition of technical
  standards activities

55
NASA TECHNICAL STANDARDIZATION AWARDPROPOSAL

• Award type Annual (multiple awards may be made
  if justified) with appropriate certificate,
  rosette pin, medal, and monetary award as
  deemed appropriate by NASA chief engineer.
  Letter of recognition to awardees organization
  director/manager.
• Nominations (a) Individual and team awards
  considered.
• (B) Activities may cover nominees career
• (C) Nominations shall be held over for
  1-yr.
• (D) Nominees will be NASA employees
• Presentation annually by NASA chief engineer
  during an
• appropriate NASA Engineering Management
  Board meeting

56
NASA TECHNICAL STANDARDIZATION AWARDPROPOSAL

• Timeline
• Nominations Due August 1
• Awardee Selected By NTSWG September 15
• NEMB Approval October 15
• NASA Chief Engineer Approval November 1
• Awardee Notified November 15
• Award Presented An Appropriate EMB
  Meeting

57
NASA TECHNICAL STANDARDIZATION AWARDPROPOSAL

• Selection criteria
• Importance significance of nominees
  accomplishment to NASA and advancement of the
  aerospace community relative to meeting needs of
  programs/projects. (30 points)
• Longevity duration of recognized, substantive
  contributions as sustained effort. (20 points)
• Breadth overall scope and originality of
  contribution in terms of impact on the
  development of agencys programs and projects.
  (20 points)
• Leadership role of nominee in being responsible
  for what is being recognized including
  development of concepts, goals, consensus
  building and promoting knowledge. (30 points)
• Minimum score for consideration should be greater
  than 50 points

58
NASA TECHNICAL STANDARDIZATION AWARDPROPOSAL

• Other considerations
• Nominees should not be current members of NTSWG,
  EMB, or Code D.
• Nominee and nominator shall not be part of the
  award review or selection process.
• Any NASA employee can make nomination. Only
  complete nomination packages considered.
• Selection and grading criteria should be made
  available to all nominators.

59
NASA TECHNICAL STANDARDIZATION AWARDPROPOSAL

• Other Considerations (cont)
• Awards for specific accomplishments should not be
  given out in multiple years.
• Awardee may not be selected for same award each
  year.
• Code D and NTSWG responsible for ensuring an
  award for a similar accomplishment is not
  repeated.
• Summary of NTSWG selection and grading with
  nomination package for awardee will be forwarded
  to chair, NEMB and NASA chief engineer for
  approval.
• NASA Chief Engineer must receive each nomination
  packages from nominators by stated deadline.
  Otherwise they will be considered for the
  following year.

60
Enhancements to NASA Technical Standards System
Architecture
61
Enhancements to NASA Technical Standards System
Architecture
Current Process (Manual)

• Collect data from various sources (Manual
  Process)
• Ex SAE provides NTSP office with monthly updates
  of their documents index in an XML format
• Manually enter data into NTSP system database
• Provide indices of data to contractor
• Contractor updates their indices with data
• Links to data that are not searchable from the
  Agencywide Full-text Technical Standards System
• JSC libraries (PILS, PALS, etc.)
• JPL standards
• PROBLEM The Current NTSP System Needs to
  maintain Pace With Current Technology Trends
  and provide robustness for Increase in System
  Usage

62
Enhancements to NASA Technical Standards System
Architecture
Issues With Current Process

• Labor Intensive
• Delay In Getting Latest Data To Users
• Inconsistency Of Data
• Subject To Human Errors
• Index/Document Links Change Without Notification
  To NTSP Office
• Inconsistency Of Index Updates (Weekly, Monthly,
  Etc.)
• Time Consuming
• Inadequate NTSP Office Resources To Gather And
  Maintain Data In A Timely Manner

63
Enhancements to NASA Technical Standards System
Architecture
Where We Want To Go From Here
MIL/VCS Data
Via Advanced Search System
NASA Dev. Standards
Search For Document
User
No Data Found Message
Center Data
Real-time Index
Data Found
No
Program/ Project Data
Yes
SUNS Notification Issued
Changes Identified
Yes
Lessons Learned Data Linked To Standards
No
End
64
Enhancements to NASA Technical Standards System
Architecture
How Do We Get There

• Data in common format
• Coordinate with each center/facility and SDO to
  have the data in A common format
• Retrieve the data
• Automated electronic retrieval of data via access
  to center/facility and SDO data sources directly
• OR
• Center/facility and SDO submit data (manually or
  automated) daily to NTSPO data server

65
System/Data Information Needed From Each
Center/Facility

• Type Of Systems (Operating System, COTS Package,
  Web-based, Server Hardware, Etc.)?
• How Is Data Displayed (HTML, XML, Manually
  Updated, Excel, Cold Fusion Page, Perl, Word,
  Etc.)?
• How Is Data Stored (Database--what Type Oracle,
  SQL, Excel, Etc.)?
• How Is It Updated (Manually or Automatically)?
• Frequency Of Update?
• Do You Maintain Historical Documents?
• Restrictions On Incoming Requests (Is Scraping Of
  The Web Page Allowed)?
• Firewall Restrictions?
• Data Distribution Restrictions (Export
  Controlled, NASA Only, Etc.) Are They
  Identified? How?
• Who Are The Points Of Contact For The System And
  Data (System Administrator, Data Owner)?
• Anticipated Changes To System (Planned Upgrades,
  Major Changes To System)?
• Does Your Data Contain The Following?
• Document Number
• Document Title
• Revision Level
• Release Date
• Change Date
• Revalidation Date
• URL To Link To Document

66
FY05 POP CALL
PROGRAM BUDGET 103-06-10
67
PROGRAM BUDGET (UPN 103-06-10)

•  
• Objective
•  
• The objective of the Technical Standards Program
  is to provide for the identification,
  development, selection, dissemination,
  management, and user support of technical
  standards required by NASA Programs/Projects.
•  
• Program Areas (Within Guidelines)
•  
• Agencywide Full-Text Technical Standards System
• Standards Update Notification System (SUNS)
• Lessons Learned-Standards Integration System
• Develop Technical Standards and Supporting
  Information
• Standards Support/Assessment Review
• Engineering Standards Program Management
• Development of NASA Technical Standards
• Establish and Maintain Engineering Disciplinary
  Working Groups
• Establishment of Mandatory Standards??
•  

68
PROGRAM BUDGET (CONTD)
Program Areas (Within Guidelines)
69
PROGRAM BUDGET (CONTD)

• Status
• Finalized decisions on proposals for FY04 NASA
  Engineering Standards development, however, need
  to make some funding adjustments for the Centers
• Finalizing FY05 Requirements with the Centers
• Budget Strategy
• Identification of requirements for new NASA
  Engineering Standards
• Establish Agencywide Engineering Discipline
  Working Groups
• Define Mandatory standards and implementation
  actions
• Centers must be certain they include all
  necessary full cost elements in the POP submit

70
BACKUP CHARTS
71
NASA-DEVELOPED TECHNICAL STANDARDS DUE FOR
REVALIDATION
72
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
29 Standards Overdue for Revalidation (9 Code D,
9 Code V, 11 Code Q)
73
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
74
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
75
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
76
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
77
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
78
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
12 Standards Due for Revalidation in 2003 (3 Code
D, 3 Code V, 6 Code Q)
79
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
80
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
81
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
6 Standards Due for Revalidation in 2004 (4 Code
D, 2 Code Q)
82
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
83
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
6 Standards Due for Revalidation in 2005 (1 Code
D, 1 Code Q, 4 Code V)
84
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION
6 Standards Due for Revalidation in 2005 (1 Code
D, 1 Code Q, 4 Code V)
85
NASA-DEVELOPED TECHNICAL STANDARDS OVERDUE FOR
REVALIDATION