June 2010 

NASA/TM-2010-216704 

NESC-RP-07-031 

 

Problem Reporting Taxonomy and Data 

Preparation Tool Evaluation 

Robert J. Beil/NESC 

Kennedy Space Center, Florida 
NASA STI Program . . . in Profile

 Since its founding, NASA has been dedicated to 

the advancement of aeronautics and space science. 

The NASA scientific and technical information (STI) 

program plays a key part in helping NASA maintain 

this important role. 

 The NASA STI program operates under the 

auspices of the Agency Chief Information Officer. It 

collects, organizes, provides for archiving, and 

disseminates NASA’s STI. The NASA STI program 

provides access to the NASA Aeronautics and Space 

Database and its public interface, the NASA Technical 

Report Server, thus providing one of the largest 

collections of aeronautical and space science STI in 

the world. Results are published in both non-NASA 

channels and by NASA in the NASA STI Report 

Series, which includes the following report types: 

 TECHNICAL PUBLICATION. Reports of 

completed research or a major significant phase 

of research that present the results of NASA 

programs and include extensive data or 

theoretical analysis. Includes compilations of 

significant scientific and technical data and 

information deemed to be of continuing 

reference value. NASA counterpart of peerreviewed formal professional papers, but having 

less stringent limitations on manuscript length 

and extent of graphic presentations. 

 TECHNICAL MEMORANDUM. Scientific 

and technical findings that are preliminary or of 

specialized interest, e.g., quick release reports, 

working papers, and bibliographies that contain 

minimal annotation. Does not contain extensive 

analysis. 

 CONTRACTOR REPORT. Scientific and 

technical findings by NASA-sponsored 

contractors and grantees. 

 CONFERENCE PUBLICATION. Collected 

papers from scientific and technical 

conferences, symposia, seminars, or other 

meetings sponsored or co-sponsored by NASA. 

 SPECIAL PUBLICATION. Scientific, 

technical, or historical information from NASA 

programs, projects, and missions, often 

concerned with subjects having substantial 

public interest. 

 TECHNICAL TRANSLATION. Englishlanguage translations of foreign scientific and 

technical material pertinent to NASA’s mission. 

 Specialized services also include creating custom 

thesauri, building customized databases, and 

organizing and publishing research results. 

 For more information about the NASA STI 

program, see the following: 

 Access the NASA STI program home page at 

http://www.sti.nasa.gov

 E-mail your question via the Internet to 

help@sti.nasa.gov

 Fax your question to the NASA STI Help Desk 

at 443-757-5803 

 Phone the NASA STI Help Desk at 

443-757-5802 

 Write to: 

 NASA STI Help Desk 

 NASA Center for AeroSpace Information 

 7115 Standard Drive 

 Hanover, MD 21076-1320
National Aeronautics and 

Space Administration 

Langley Research Center 

Hampton, Virginia 23681-2199 

 

June 2010 

NASA/TM-2010-216704 

NESC-RP-07-031 

 

Problem Reporting Taxonomy and Data 

Preparation Tool Evaluation 

Robert J. Beil/NESC 

Kennedy Space Center, Florida 
Available from: 

NASA Center for AeroSpace Information 

7115 Standard Drive 

Hanover, MD 21076-1320 

443-757-5802 

The use of trademarks or names of manufacturers in the report is for accurate reporting and does not 

constitute an official endorsement, either expressed or implied, of such products or manufacturers by the 

National Aeronautics and Space Administration. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

1 of 112 

NESC Request No.: 07-031-I

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

January 28, 2010 

 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

2 of 112 

NESC Request No.: 07-031-I

Report Approval and Revision History 

NOTE: This document was approved at the January 28, 2010, NRB. This document was 

submitted to the NESC Director on February 2, 2010, for configuration control. 

Approved 

Version: 

Original Signature on File 2/2/10 

1.0 NESC Director Date 

Version Description of Revision Office of Primary 

Responsibility Effective Date 

1.0 Initial Release Mr. Robert J. Beil, 

Lead, NESC SEO 01/28/10 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

3 of 112 

NESC Request No.: 07-031-I

Table of Contents 

Volume I: Technical Assessment Report 

1.0 Notification and Authorization ..................................................................................................... 4

2.0 Signature Page ................................................................................................................................ 5

3.0 Team List ........................................................................................................................................ 6

4.0 Executive Summary ....................................................................................................................... 7

5.0 Problem Description ...................................................................................................................... 8

5.1 Objective 1: Taxonomy Standard Data Field Analysis .................................................................... 8

5.2 Objective 2: TechOasis Filter .......................................................................................................... 9

6.0 Data Analysis for Objective 1: Taxonomy Standard Data Field Analysis .............................. 11

6.1 Recommended Mandatory Additional Data Elements ................................................................... 11

6.2 Recommended Non-Mandatory Additional Data Elements .......................................................... 15

7.0 Finding and NESC Recommendations ....................................................................................... 19

7.1 Finding .......................................................................................................................................... 19

7.2 NESC Recommendations ............................................................................................................... 19

8.0 Definition of Terms ...................................................................................................................... 19

9.0 Acronyms List .............................................................................................................................. 20

List of Figures

Figure 5.2-1. Process Flow Diagram .......................................................................................................... 10

List of Tables

Table 6.1-1. Recommended Additional Mandatory Fields ......................................................................... 11

Table 6.2-1. Recommended Additional Fields ........................................................................................... 15

Volume II: Appendices 

A. Gap Analysis 

B. How-To Procedures 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

4 of 112 

NESC Request No.: 07-031-I

Volume I: Technical Assessment Report 

1.0 Notification and Authorization 

Mr. Robert J. Beil, a member of the NASA Engineering and Safety Center (NESC) Systems 

Engineering Office (SEO) Technical Discipline Team (TDT) requested this SEO-managed 

activity to perform a gap analysis for the proposed NASA Standard 0006 “Common NASA 

Taxonomy for Problem Reporting, Analysis, and Resolution” and to “develop a data filter to aid 

in performing data mining on the Space Shuttle Program PRACA data.” 

An NESC out-of-board activity was approved on June 7, 2007, by Ms. Dawn Schaible, NESC 

SEO Manager. Mr. Beil was selected to lead this assessment. The assessment plan was 

presented and approved by the SEO Manager on February 13, 2008. The final report was 

presented to the NESC Review Board (NRB) for approval on January 28, 2010. 

The key stakeholders for this assessment are the NESC Data Mining and Trending Working 

Group and the Kennedy Space Center (KSC) Office of the Chief Engineer (OCE). 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

5 of 112 

NESC Request No.: 07-031-I

2.0 Signature Page 

Submitted by: 

Original Signature on File – 2/2/10 

Mr. Robert J. Beil Date 

Signatories declare the findings and observations complied in the report are factually based from 

data extracted from Program/Project documents, contractor reports, and open literature, and/or 

generated from independently conducted tests, analysis, and inspections. 

 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

6 of 112 

NESC Request No.: 07-031-I

3.0 Team List 

Name Discipline Organization 

Core Team 

Robert Beil NESC Lead KSC 

Tim Adams NESC Deputy Lead KSC 

Tim Barth Systems Engineering LaRC 

Anthony Burris Systems Engineering KSC/SAIC 

David Armstrong Systems Engineering KSC 

Wayne Fowler Systems Engineering KSC/SAIC 

Charles Wilson Systems Engineering KSC/SAIC 

Pam Throckmorton MTSO Program Analyst LaRC 

Administrative Support 

Erin Moran Technical Writer LaRC/ATK 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

7 of 112 

NESC Request No.: 07-031-I

4.0 Executive Summary 

The two objectives of this assessment were: to perform a gap analysis on the proposed NASA 

Standard 0006, “Common NASA Taxonomy for Problem Reporting, Analysis, and Resolution”, 

and to create an input filter and set of instructions for using the data-mining/data-cleansing tool 

TechOasis1

 with Space Shuttle Program (SSP) problem reporting data. 

The gap analysis (classification of how well a product or solution meets a targeted need) used a 

bottoms-up approach (assessing against various problem reporting systems) to demonstrate the 

efficacy of the proposed standard and to identify variances between the actual and the desired 

state. The first section of this report reviews the work completed, discusses the results, and 

provides suggestions for further use of this data. 

The second objective was achieved through the development and deployment of import filters 

for Web-based Program Compliance Assurance and Status System (WebPCASS) data (i.e., SSP 

Web-based PRACA data) to facilitate its use in the data/text mining tool, TechOasis. 

The assessment team consisted of members from the NASA Engineering and Safety Center 

(NESC) Systems Engineering Office (SEO) Data Mining and Trending Working Group, the 

NESC SEO Statistics Technical Discipline Team (TDT) sub team, and contractor support 

(Science Applications International Corporation (SAIC)-Kennedy Space Center (KSC)) to assist 

with the filter development and data integration. The team also had support from Search 

Technologies Inc., developers of TechOasis, in developing the data filter. 

The work that achieved these objectives and deployment of TechOasis are discussed in this 

report. 

 

 

1

TechOasis is a text and data mining/data-preparation software tool that was developed under contract to Defense Advanced Research Projects 

Agency (DARPA) and the United States (US) Army by Search Technologies Inc., and is freely accessible to the federal government.
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

8 of 112 

NESC Request No.: 07-031-I

5.0 Problem Description 

The two objectives of this assessment were to perform a gap analysis on the proposed NASA 

Standard 0006 “Common NASA Taxonomy for Problem Reporting, Analysis, and Resolution”, 

and to create an input filter and set of instructions for using the data mining/data-cleansing tool 

(TechOasis) with SSP problem-reporting data (described in the next paragraphs). 

A gap analysis (classification of how well a product or solution meets a targeted need) was 

performed on the proposed “Common NASA Taxonomy for Problem Reporting, Analysis and 

Resolution Standard.” The proposed standard was developed at the request of the OCE and 

developed by an Agency cross-cutting team led by the NESC. This standard has been informally 

utilized by the Constellation Program (CxP) in the development of their Level II PRACA system 

and has been released for final review and acceptance as a formal standard. The utility of this 

standard has not been fully demonstrated. Section 5.1 reviews the gap-analysis in greater detail 

and discusses the results. Suggestions for further use of this data are also presented. 

The development and deployment of an import filter and set of instructions for utilization with 

WebPCASS data to facilitate its use in TechOasis was accomplished. TechOasis is a text and 

data-mining/data-preparation software tool that was developed under contract to Defense 

Advanced Research Projects Agency (DARPA) and the United States Army by Search 

Technologies Inc. and is freely accessible to federal government employees and contractors. The 

work that achieved this objective and the deployment of TechOasis is described in detail in 

Section 5.2. 

5.1 Objective 1: Taxonomy Standard Data Field Analysis 

At the request of the Agency OCE, in 2005, the NESC formed a multi Center group to develop a 

proposed NASA standard, “Common NASA Taxonomy for Problem Reporting, Analysis, and 

Resolution Standard”. The proposed standard was approved at the NESC review board and went 

out for review and comment to the NASA Centers. Although it has been used as a reference and 

starting point for developing the CxP Level II PRACA system structured data fields, the utility of 

this standard had not been fully demonstrated.

This study performed a gap analysis, using the proposed standard as the baseline, assessing how 

well it performed against similar problem reporting systems. The approach taken was to gather 

structured data fields from a number of representative problem-reporting databases. These 

databases included: KSC Ground Operations Problem Reporting System, Aviation Safety 

Reporting System, Marshall Space Flight Center (MSFC) UNIX PRACA System, International 

Space Station (ISS) Program PRACA System, CxP PRACA, Space Shuttle Program PRACA 

Requirements (STS-08126K), Johnson Space Center (JSC) Government round-Furnished 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

9 of 112 

NESC Request No.: 07-031-I

Equipment Problem Reporting System, The Aerospace Corporation Anomaly Tracking System, 

Incident Reporting and Information System (IRIS)-partial, and General Atomics Failure 

Reporting Analysis and Corrective Action System (FRACAS). These structured fields were then 

consolidated and sorted to compare like fields and identify unique fields. The consolidated 

summary is provided in Appendix A. Based on this work, fields that should be considered for 

inclusion in the proposed standard were identified. These were binned into two categories: 

recommended additional mandatory fields and recommended additional fields (matching the 

format used in the proposed standard). Section 6.0 contains the descriptions of these fields, 

where they originated, and rationale for recommending their inclusion in the proposed standard. 

5.2 Objective 2: TechOasis Filter 

TechOasis is the US Government version of the commercially-available VantagePoint software 

from Search Technology, Inc, originally developed under contract to DARPA and the US Army. 

TechOasis is a text-mining tool used for discovery and extraction of knowledge from text-based 

sources. In order to utilize the tool, data has to be in a form that will allow it to be imported for 

analysis. 

This task focused on establishing a set of ‘how-to’ procedures or user resource guides. The 

workflow of procedures is depicted in Figure 5.2-1. Each of these items represents an output 

from this task. The first procedure describes how to obtain access to the SSP PRACA data 

system. The second and third procedures are the key outputs from this task. The second 

procedure describes the intermediary process of outputting a tilde delimited search file followed 

by the truncation of certain characters from the beginning and end of the file to allow it to be 

configured as an Microsoft® Excel® file for subsequent building of an import filter and raw data 

import. The third procedure describes how to build the import filter using the previous search 

file and then import this raw data file. The fourth procedure is a summary of referenced key 

features found in the TechOasis User’s Guide. The fifth procedure provides users who have 

processed data through the TechOasis application a means to validate their data analysis 

techniques and arrive at conclusions. Since this section is in its early stage of development, these 

methods and processes have not yet been fully determined. However, this effort provides a 

starting point for the community to build a knowledge base where methods, techniques, and 

other supporting information can be exchanged in an open forum. The procedures are contained 

in Appendix B, and can be found at: http://kscsma.ksc.nasa.gov/Reliability/IDAS.html. This site 

is the Integrated Design and Assurance System (IDAS) website, which is a KSC resource that 

shares and supports tools that perform technical analyses. This site also serves as a location for 

collecting and sharing information that helps analysts to learn and apply the tools and techniques. 

This site is open to all NASA employees and contractors. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

10 of 112 

NESC Request No.: 07-031-I

Figure 5.2-1. Process Flow Diagram 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

11 of 112 

NESC Request No.: 07-031-I

6.0 Data Analysis for Objective 1: Taxonomy Standard Data Field 

Analysis 

6.1 Recommended Mandatory Additional Data Elements 

The data elements in Table 6.1-1 are recommended mandatory additional data elements for the 

standard. These are the elements categorized in the standard as “all projects shall use in their 

reporting systems.” The first column describes where the field reference originated (from the 

bottoms up review), while the next 3 fields mimic the proposed standard format. The last 

column “Rationale for Addition,” describes the rationale for including the given field. 

Table 6.1-1. Recommended Additional Mandatory Fields 

PRACA 

System(s) 

Data 

Field Description Data Type or Source Rationale for Addition 

CxP 70068-

03 // ISS 

PRACA Db 

DD250 Has the H/W or S/W 

been accepted by the 

government? 

Yes/No Important distinction during new 

system development and 

acquisition (may affect decisions 

about program/mission impacts, 

severity, priorities, etc.). 

KSCPR Deferred 

Date 

 Date The specific definition and 

inclusion of this series of fields 

is dependent on the type of 

program/project. The message 

here is that if a problem 

resolution is being deferred, 

whether the hardware/software is 

in flight or on the ground, the 

deferral event needs to be 

documented, including the date, 

the signatories and a 

justification. The ISS Program 

uses a model where they include 

a review of the deferral rationale 

from flight to flight in the 

Certification of Flight Readiness 

(CoFR). This model seems to 

work well for them, ensuring 

problems are addressed prior to 

missions, as well as documenting 

the rationale for that deferral. 

KSCPR/ISS 

PRACA Db 

Deferred to 

Event/Flt# 

 Pick List 

ISS PRACA 

Db 

Flight 

Effectivity 

Status 

Open/Closed buttons 

indicating the status. 

Open/Closed 

 

ISS PRACA 

Db 

Justification Justification for 

changes to the PR’s 

Flight Effectivity. 

Text string 

ISS PRACA 

Db 

Name Name of person 

responsible to open 

and close Flight 

Effectivity. 

People 

Taxonomy 

PRACA 

System(s) 

Data 

Field Description Data Type or Source Rationale for Addition 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

12 of 112 

NESC Request No.: 07-031-I

 

CxP 70068-

03 

Likelihood 

Score 

Determine 

likelihood of 

problem occurring 

again (1, 2, 3, 4 or 5) 

based on qualitative 

and quantitative 

values per CxP 

70056. 

Pick List This series of fields offers 

various possibilities of 

addressing risk. It was based 

largely on the existing CxP 

PRACA requirements document, 

which has since evolved. 

However, these fields offer a 

possible approach. The proposed 

Standard includes a “Criticality 

Field” and an “Adverse Program 

Impact” field, which could be 

improved upon. The CxP has 

taken an interesting approach of 

identifying a significance 

category and a likelihood score, 

which is then multiplied, 

resulting in a risk score. No 

standardized risk approach exists 

for the Agency, but this approach 

provides a possible model that is 

based on a widely used risk 

matrix format. Additionally, the 

CxP suggests two fields, 

“Program Approval Required” 

and “Project Approval 

Required/Desired” that could be 

invoked if certain criteria are 

met. Inclusion of this series of 

fields is meant to spur thought, 

and to recommend inclusion of 

risk identification, but not 

suggest the solution. 

CxP 70068-

03 

Program 

Approval 

Required? 

Is program approval 

required? 

Yes/No 

CxP 70068-

03 

Project 

Approval 

Required? 

Is project approval 

required/desired? 

This approval 

field(s) depends on 

significance 

category, risk score, 

FMEA/CIL 

criticality code and 

resolution actions. 

Yes/No 

CxP 70068-

03/ 

Northrop 

Grumman - 

F18 

FRACAS 

Risk Score/ 

Safety 

Analysis RHI 

Automatically 

calculates the 

product of 

Consequence Score 

times Likelihood 

Score. The RHI 

forms the basis for 

judging the 

acceptability of a 

risk and prioritizing 

resources. 

Automatically 

Calculated 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

13 of 112 

NESC Request No.: 07-031-I

 

PRACA 

System(s) 

Data 

Field Description 

Data 

Type or 

Source 

Rationale for Addition 

CxP 70068-

03 

Significance 

Category 

Significance of problem 

based on criteria in 

volume 1 of the 

PRACA requirements 

document. For 

Software: Assessment 

of the 

software/firmware/ 

complex electronics 

safety functions as 

defined in NASA-STD8719.13B, Section 

4.1.1, NASA Software 

Safety Standard. If the 

system is determined to 

be safety critical then 

the software must be 

evaluated for its 

contribution and 

addressed. 

Pick List 

CxP 70068-

03 

Safety 

Critical 

Software? 

Assessment of the 

software/firmware/com

plex electronics safety 

functions as defined in 

NASA-STD-8719.13B, 

Section 4.1.1, NASA 

Software Safety 

Standard. If the system 

is determined to be 

safety critical then the 

software must be 

evaluated for its 

contribution. 

Yes/No This field identifies if software is 

safety critical, per NASA-STD8719.13B. (i.e., software is 

considered safety critical for those 

software operations that, if not 

performed, performed out-of 

sequence or performed incorrectly 

could result in improper control 

functions (or lack of control 

functions required for proper 

system operation) that could 

directly or indirectly cause or 

allow a hazardous condition to 

exist.) 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

14 of 112 

NESC Request No.: 07-031-I

PRACA 

System(s) 

Data 

Field Description 

Data 

Type or 

Source 

Rationale for Addition 

CxP 70068-

03 // 

Northrop 

Grumman - 

F18 

FRACAS 

Run Time/ 

Elapsed 

Time/Cycles 

For items with elapsed 

time indicator (ETI) - 

time elapsed or number 

of cycles from NASA 

acceptance of 

equipment item to 

fault/failure/ anomaly 

detection; at the level at 

which maintenance 

action is initiated. 

Text Field This field would provide 

important trending data, which 

could support predictive analysis. 

CxP 70068-

03 // 

Aerospace 

ATR 

Software 

Version 

(CSCI/CSC/ 

CSU) 

Computer Software 

Configuration Item 

(CSCI): an aggregation 

of software that is 

designated for 

configuration 

management and 

treated as a single entity 

in the configuration 

management process. 

[IEEE-STD 610.12-

1990] Computer 

Software Component 

(CSC) 

Single line 

text field 

Add a software version field, as 

required by NPR 7150.2. 

CxP 70068-

03 

Software 

Classification 

Identify classification 

of the defective 

software/ 

firmware/complex 

electronics as defined 

by NPR 7150.2. Refer 

to the system 

classification 

assessment or contact 

your software assurance 

representative for 

assistance in selection. 

Pick List This field is identified as 

mandatory for Problem Reporting 

by NPR 7150.2. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

15 of 112 

NESC Request No.: 07-031-I

6.2 Recommended Additional Data Elements 

The data elements in Table 6.2-1 represent recommended additional data elements categorized in 

the standard as non-mandatory. The first column describes where the field reference originated 

(from the bottoms up review), while the next 3 fields mimic the proposed standard format. The 

last column, “Rationale for addition,” describes the rationale for including each field. 

 

Table 6.2-1. Recommended Additional Fields 

PRACA 

System(s) 

Data Field Description Data Type or Source Rationale for Addition 

CxP 70068-

03 

Alias Identifying 

numbers/names of 

the vendor’s nonconformance/ 

problem report. 

Auto-populate with edit 

capability. 

Provides cross-reference 

to vendor-unique 

identification of 

problem. 

Northrop 

Grumman - 

F18 

FRACAS 

Attachment Attachment This field can be 

automated with addition 

of attachment. It 

provides a quick 

indication of 

attachments included, or 

not. 

CxP 70068-

03 

Common 

Hardware - 

Automatic 

Automatically 

filled in by 

software for any 

common part 

numbers (need to 

define work flow). 

Yes/No Automatic (when 

parts database created) 

Suggest linking to parts 

database, if feasible. 

CxP 70068-

03 

Cost 

Exceeded 

$100K 

Yes, if Total Cost 

(Labor and 

Material) to work 

the problem 

exceeds $100K 

(high level estimate 

of cost). 

Yes/No Provides a discriminator 

to management. 

Suggest as nonmandatory field for 

NASA Standard 0006. 

CxP 70068-

03 

Detectable Fault is detectable 

during preoperation 

screening, 

preventive 

maintenance 

Pick List This field provides 

additional management 

insight into the problem.
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

16 of 112 

NESC Request No.: 07-031-I

PRACA 

System(s) 

Data Field Description Data Type or Source Rationale for Addition 

checks, etc. Pick 

list includes: 

Screenable, 

Nonscreenable. 

USAF DRIS Governmen

t-Furnished 

Material 

(GFM) 

 List Government-furnished 

equipment (GFE) 

distinction. 

Northrop 

Grumman - 

F18 

FRACAS 

How Detect 

Bit 

 Text Combine with 

recommendation for 

BIT of failure...this is a 

sub-pick list. 

Northrop 

Grumman - 

F18 

FRACAS 

How 

Indicate Bit 

 Text Combine with 

recommendation for 

BIT of failure...this is a 

sub-pick list. 

Northrop 

Grumman - 

F18 

FRACAS 

How Isolate 

Bit 

 Text Combine with 

recommendation for 

BIT of failure...this is a 

sub-pick list. 

IRIS Incident 

Category 

Example: 

occurrence or 

condition of 

employee concern 

where there is no 

injury or only 

minor injury 

requiring first aid 

and no significant 

equipment/property 

damage/mission 

failure (less than 

$1,000), but which 

possesses a 

potential to cause a 

mishap. 

Pick List 

 Indicator-Close Call 

 Indicator-Construction 

 Indicator-False Alarm 

 Indicator-High Visibility 

 Indicator-Injury Involved 

 Indicator-Mission 

Affected 

 Indicator-Serious 

Damage to Aircraft or 

Space Hardware 

 Indicator-Serious 

Damage to Flight or 

Ground Support 

Hardware 

 Indicator-Test Failure 

 Indicator-Unexpected 

Damage Due to Test 

Failure

This provides linkage to 

IRIS in the event of an 

incident or mishap type 

event. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

17 of 112 

NESC Request No.: 07-031-I

PRACA 

System(s) 

Data Field Description Data Type or Source Rationale for Addition 

CxP 70068-

03 // KSCPR 

Location on 

Hardware 

Zone location on 

hardware itself, if 

applicable. Based 

on engineering 

drawings. 

Text Field This field provides 

additional management 

insight into the problem.

Northrop 

Grumman - 

F18 

FRACAS 

Other How 

Isol bit 

 Text Combine with 

recommendation for 

BIT of failure...this is a 

sub-pick list. 

ISS PRACA 

Db 

Reject PR Used to reject 

public release of a 

PR that does not 

meet reportability 

criteria. 

Selection button Categorizes that a PR 

was initiated, but later 

rejected (provides quick 

reference/insight). 

CxP 70068-

03 // 

Northrop 

Grumman - 

F18 

FRACAS 

Repair/Fix Elapsed 

maintenance time 

from fault/failure 

detection to return 

to service. 

Text This field provides 

additional management 

insight into the problem.

CxP 70068-

03 

Software 

Type 

Identify the type of 

software/firmware/ 

complex 

electronics that is 

defective. 

Pick List This field provides 

additional management 

insight into the problem.

Aerospace 

ATR 

Symptom 

Duration 

Indicate duration of 

the anomalous 

behavior as 

“persistent” 

(permanent, 

continual), 

“transient” 

(momentary, 

temporary), 

“intermittent” 

(recurring at 

irregular intervals), 

“periodic” 

(recurring at 

regular intervals), 

String (20) Recommend adding to 

defect characteristic 

pick list. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

18 of 112 

NESC Request No.: 07-031-I

PRACA 

System(s) 

Data Field Description Data Type or Source Rationale for Addition 

or “unrepeatable” 

(cannot recreate). 

Northrop 

Grumman - 

F18 

FRACAS 

Use as is 

Qty 

 Value Good indicator of how 

many items affected by 

use-as-is condition. 

Aerospace 

ATR 

Verification 

Level 

The verification 

level/method 

description that 

should have 

detected the most 

likely cause of the 

anomaly, given the 

verification process 

used. 

String (60) This field provides 

additional management 

insight into the problem.
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

19 of 112 

NESC Request No.: 07-031-I

7.0 Finding and NESC Recommendations 

7.1 Finding 

The following finding was identified: 

F-1. The proposed NASA Standard 0006, “Common NASA Taxonomy for Problem 

Reporting, Analysis, and Resolution”, is missing data fields (mandatory and suggested) 

when compared with referenced aerospace problem reporting databases. 

7.2 NESC Recommendations 

The following NESC recommendations were identified and are directed to the Agency OCE 

concerning the proposed NASA Standard 0006: 

R-1. Fields described in Table 6.1-1 should be added as ‘mandatory’ fields in NASA Standard 

0006. (F-1) 

R-2. Fields described in Table 6.1-2 should be considered for inclusion in NASA Standard 

0006. (F-1) 

8.0 Definition of Terms 

Corrective Actions Changes to design processes, work instructions, workmanship practices, 

training, inspections, tests, procedures, specifications, drawings, tools, 

equipment, facilities, resources, or material that result in preventing, 

minimizing, or limiting the potential for recurrence of a problem. 

Finding A conclusion based on facts established by the investigating authority. 

Lessons Learned Knowledge or understanding gained by experience. The experience may 

be positive, as in a successful test or mission, or negative, as in a mishap 

or failure. A lesson must be significant in that it has real or assumed 

impact on operations; valid in that it is factually and technically correct; 

and applicable in that it identifies a specific design, process, or decision 

that reduces or limits the potential for failures and mishaps, or reinforces a 

positive result. 

Observation A factor, event, or circumstance identified during the assessment that did 

not contribute to the problem, but if left uncorrected has the potential to 

cause a mishap, injury, or increase the severity should a mishap occur. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

20 of 112 

NESC Request No.: 07-031-I

Alternatively, an observation could be a positive acknowledgement of a 

Center/Program/Project/Organization’s operational structure, tools, and/or 

support provided. 

Problem The subject of the independent technical assessment. 

Proximate Cause The event(s) that occurred, including any condition(s) that existed 

immediately before the undesired outcome, directly resulted in its 

occurrence and, if eliminated or modified, would have prevented the 

undesired outcome. 

Recommendation An action identified by the NESC to correct a root cause or deficiency 

identified during the investigation. The recommendations may be used by 

the responsible Center/Program/Project/Organization in the preparation of 

a corrective action plan. 

Root Cause One of multiple factors (events, conditions, or organizational factors) that 

contributed to or created the proximate cause and subsequent undesired 

outcome and, if eliminated or modified, would have prevented the 

undesired outcome. Typically, multiple root causes contribute to an 

undesired outcome. 

9.0 Acronyms List 

AA/OSMA Associate Administrator/Office of Safety and Mission Assurance 

CFR Certification of Flight Readiness 

CSC Computer Software Component 

CSCI Computer Software Configuration Item 

CxP Constellation Program 

DARPA Defense Advanced Research Projects Agency 

Db Database 

DD Deferred Date 

ETI Elapsed Time Indicator 

FMEA/CIL Failure Modes and Effects Analysis/Critical Item List 

FRACAS Failure Reporting Analysis and Corrective Action System 

GFE Government-Furnished Equipment 

GFM Government-Furnished Material 

HQ Ops Headquarters Operations 

IEEE Institute of Electrical and Electronics Engineers 

IRIS Incident Reporting and Information System 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

21 of 112 

NESC Request No.: 07-031-I

IDAS Integrated Design and Assurance System 

JSC Johnson Space Center 

KSC Kennedy Space Center 

LaRC Langley Research Center 

MTSO Management and Technical Support Office 

NESC NASA Engineering and Safety Center 

NRB NESC Review Board 

PRACA Problem Reporting and Corrective Action 

RHI Risk Hazard Index 

SAIC Science Applications International Corporation 

SEO Systems Engineering Office 

WebPCASS Web-based Program Compliance Assurance and Status System 

Volume II: Appendices 

A. Gap Analysis 

B. How-To Procedures 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

22 of 112 

NESC Request No.: 07-031-I

Appendix A. Gap Analysis 

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

Yes 074 Residual 

Risk? 

Is there remaining risk in using this item/system after implementation of final resolution (after corrective action)? 

Yes/No Analysis, 

Closeout 

 No Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi

Yes 087 Lesson 

Learned? 

Is there a lesson learned resulting from this problem? 

Yes/No Analysis, 

Closeout 

 No Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi

Yes 062 Expected 

Date Root Cause(s) 

Expected date for determination of root cause(s). 

mm/dd/yyyy 

Analysis No 

Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi

Yes 068 Expected 

Date Solution Development 

Expected date for development of solution to resolve problem (remedial and/or corrective). 

mm/dd/yyyy 

Analysis No 

Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi

Yes 017 Mission 

Type 

Type of mission. Pick 

List 

 Initiation No 

Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi

Yes 089 Notification? Does the flight crew, ground 

crew, or others need to be notified of the problem? 

Yes/No Initiation, 

Analysis, Closeout 

 No Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi

Yes 011 Detection 

Time 

Time when problem was detected. 

hh:mm:ss 

 Initiation No 

Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi

 069 Expected 

Date Solution Implementation 

Expected date for implementation of solution to resolve problem (remedial and/or corrective). 

mm/dd/yyyy 

Analysis Expected 

Date(s) Corrective Action/Recurrence Control Implemented 

Expected date(s) for implementation of problem solution and corrective action. 

ECD No 

Matching Field 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

23 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 023 Failure 

Mode/Symptoms 

The manner in which an item can fail or actually failed to perform its required function within specified limits, under specified limits, under specified conditions, for a specified duration / an actual component failure/error misperformance that was an i 

Pick List 

 Y Initiation, 

Analysis 

Failure Mode/Symptoms 

The symptoms of the failure and the manner in which an item can or actually failed to perform its required function within specified limits, under specified conditions, for a specified duration; an actual component failure/error misperformance that was an 

Failure Mode // Failure Mode Code 

Incident Type // Incident Sub Type 

FaM

 086 Follow-on 

Action Description 

Description of the follow-on actions assigned as a result of this problem, including who is actionable. 

Text String 

Analysis, 

Closeout 

Corrective Action(s)/Recurrence Control Description(s) // Remedial Action/Disposition Description 

Action 

(beyond remedial action) to correct a problem and prevent/control nonconformance/ problem recurrence in existing and/or future hardware or software. Corrective action should include one or more of the following: a. Design change; b. Manufacturing 

Actionee 

Name // Corrective Action // Investigation/Analysis Summary // Maintenance Action Request // PR MRB Disposition // PR Recurrence Control 

Follow Up N

MFi

 085 Follow-on 

Action? 

Is follow-on action required as a result of this problem (other than configuration change, i.e., procedural)? 

Yes/No Analysis, 

Closeout 

Corrective Action/Preventive Action 

Based on

significance category, risk score, 

No 

matching field 

Further Action Req'd? 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

24 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

Required? criticality 

code, etc., the PRT will determine if corrective action is required. This may be based on the potential that this problem has to occur on other missions or systems; or the potential to recur again. I 

 037 Hardware 

Criticality Code 

Criticality code assigned to particular hardware based on FMEA and CIL. 

Pick List (auto fill) 

 Initiation, 

Analysis 

Functional Criticality 

Assessment 

of the criticality of the observed failure mode based on FMEA and CIL for the assembly level. This is the functional criticality level. 

FMEA Criticality Code 

No 

Matching Field 

HC

 022 Immediate 

Response 

Description of initial actions taken to respond to the problem as soon as it was discovered / e.g., removereplace, securing. 

Text String 

 Initiation Immediate 

Response 

Description of initial actions that were taken to respond to the problem and safe the situation as soon as it was discovered; (e.g., securing the system, spill containment, system shutdown). Provide clear status/conditio

Investigation/Analysis Summary 

Immediate Corrective Action 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

25 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

n for PRT.

 077 Impacted 

Document Description 

Description of documents that require revision as a result of this problem, including title, reference number, schedule for revision, etc. 

Text String 

Analysis, 

Closeout 

Process Escape Description 

Description of the process escape, list of processes names/numbers that are applicable. Specify the area of the process where the escape occurred. 

Corrective Action // Disposition // Investigation/Analysis Summary 

Document Description 

N

MFi

 018 Lifecycle 

Phase 

Phase of mission when problem occurred. 

Pick List 

 Y Initiation Lifecycle 

Phase 

Phase of mission when problem occurred. 

On-Orbit Notes 

No 

Matching Field 

N

MFi

 067 Implementat

ion POC 

Name, organization, email, and telephone of person responsible for implementing the problem resolution (remedial and/or corrective). 

NASA People Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

Analysis Corrective 

Action/Recurrence Control POC 

Name, organization, email, & telephone for person/team responsible for implementation of the problem resolution. 

Last Name (Assigned To) // Phone 

Organization - AR 

Eg 

 005 Initiator 

POC 

Name, organization, email, telephone, and role of person who initiated the problem report. 

NASA People Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

 Initiation Initiator/Re

porter POC 

Name, organization, email, telephone, & role of person/team who initiated the problem 

E-mail (Initiator) // First Name // Initiator Name // Initiating Org // Last Name 

Submitter's Name // Submitter's Phone // Submitter's Mail Stop // Created by 

Rby N
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

26 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

report (problem 

initiator) // Org // Phone Number // PR Initiator Name 

 071 Interim 

Approval Responsibility 

Name, organization, email, and telephone of person responsible for approval of interim resolution. 

NASA People Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

Analysis No 

Matching Field 

Focal Name Responsible 

Manager/Supervisor 

Re 

 070 Interim 

Resolution 

Description of the problem resolution, including plan of action and rationale. 

Text String 

Analysis Remedial 

Action/Disposition Description // OpenInterim Disposition Rationale 

Description of the activities taken to disposition a nonconforming process, software item, or hardware item. // Rationale allowing continued use or processing of specific components/milestones/ events. 

Investigation/Analysis Summary 

Action To 

Take 

DS

 039 Item 

Disposition 

Description of what was done with the anomalous item, e.g., repair, return to vendor. 

Text String 

 Initiation, 

Analysis 

Remedial Action/Disposition // Reliability Disposition 

Description of what was done with the anomalous/nonconforming/problem item. // Description of fault/failure disposition. To include: No Fault Found - Could Not 

Disposition Action 

Taken 

D
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

27 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

duplicate; Relevant Failure; Independent Failure. 

 036 Item History Item history includes use 

time and cycles, design use time and cycles, longest 

observed use time and cycles. 

 Initiation, 

Analysis 

 No Matching Field 

Flight History // ISS Flights (Deferrals) // ISSP Average Day Standard Values // Operating Times/Cycles Units 

No 

Matching Field 

RD

 093 Last Update 

Field 

Automatically filled by 

software when record saved. 

mm/dd/yyyy / hh:mm:ss 

 Y Initiation, 

Analysis, Closeout (auto) 

Last Updated 

Automatically 

filled by software when record saved. 

NCR Last Updated Date // Update Date 

Last Updated 

N

MFi

 088 Lesson 

Learned Description 

Brief description of lesson learned from this process of identifying/working/resolving the problem, including link to lessons learned database item with more details. 

Text String 

Analysis, 

Closeout 

 No Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi

 076 Impacted 

Documents? 

Are any documents 

invalidated or revisions required as a result of this problem? 

Yes/No Analysis, 

Closeout 

Process Escape? 

Was there a process escape? 

No 

matching field 

No 

Matching Field 

CAf
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

28 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 033 Assembly/C

omponent/Part Serial Number 

Serial number(s) of the hardware, firmware or software item(s) involved in the anomaly, incident, or problem. 

Text String 

 Initiation, 

Analysis 

Nonconforming Part/Assembly Serial Number or lot/date code 

Smart serial number or lot/date code pick list based on part number. 

LRU Serial Number // NCA Serial/Lot Number // Part Serial Numbers // Serial Number; 

No 

Matching Field 

S# 

 082 Actual Date 

Solution Development 

Actual date(s) for 

development of problem solution. 

mm/dd/yyyy 

Analysis Date(s) 

Corrective Action/Recurrence Control Implemented 

Actual date(s) 

for implementation of problem solution and corrective action. 

PR Release Date 

Actual 

Comp. Date - AR response 

CD

 083 Actual Date 

Solution Implementation 

Actual date(s) for 

implementation of problem solution. 

mm/dd/yyyy 

Analysis Date(s) 

Corrective Action/Recurrence Control Implemented 

Actual date(s) 

for implementation of problem solution and corrective action. 

Close Date // Release/Closed Date 

Date Closed // Actual Comp. Date - Issue 

N

MFi

 041 Adverse 

Program Impact 

Identification of adverse effects resulting from the problem, e.g., schedule delay, missed test date. 

Pick List 

 Y Initiation, 

Analysis, Closeout 

Defect Impact 

The impact to System as a result of the defect. (From CxP 70065 <TBD D-1>) 

Investigation/Analysis Summary // Flight Effectivity // ISS Flights (Deferrals) // SSP Flights (Deferrals) 

Program Impact 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

29 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 042 Analysis 

POC 

Name, organization, email, telephone, and role of person who has been assigned to analyze the problem. 

NASA People Taxonomy 

Picklist or Auto-fill fields via direct link to the NASA Taxonomy 

Y Initiation, 

Analysis 

Analysis 

POC/Assigned Analyst 

Name, organization, email, telephone, & role of person/team who has been assigned to analyze the problem. 

Last Name (Assigned Engineer) // Phone # // Responsible Org 

Investigator // First name (CI Coordinator) // Last Name (CI Coordinator) // Organization - CI 

Eg 

 025 Anomalous 

Item State 

Identification of the state or configuration of the anomalous item when the problem occurred. 

Example List 

 Y Initiation, 

Analysis 

Defect Trigger 

The defect trigger is the environment or condition that had to exist for the defect to surface. (From CxP 70065 <TBD D-1>) 

Defect Code // Material Code // OnOrbit Notes // Prevailing Conditions 

Incident Notes Details 

N

MFi

 053 Applicable 

Documents 

Identification of references/documents that are applicable to this problem, e.g., CIL, HAZ, GIDEP, FMEA. 

Example List 

Analysis Material 

Review Board Supporting Data // Related Documents 

Attach 

supporting MRB documents used to disposition hardware. // Attach documents, pictures, and other supporting data. For process problems, attach the process that is broke and any other supporting 

Attach 

Documents // Document Title // Related Documents 

NASA Mishap Report // NCR 

RDRDTyRDNRDN
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

30 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

documentation. Attach applicable variance/waivers/devia 

 030 Assembly 

Level 

Depends on the specific characteristics of the mission components (i.e., LRU, SRU, CRU, Component, Assembly, Part, etc.) 

Example List 

 Initiation, 

Analysis 

Assembly 

Level 

Not defined. Hardware 

Level Code // NCA Name 

No 

Matching Field 

N

 035 Assembly/C

omponent/Part Integrator 

Name and CAGE code of the company or other entity that assembled the hardware, firmware or software item(s) involved in the anomaly, incident, or problem. 

Text String 

 Initiation, 

Analysis 

Nonconforming Part/Assembly Integrator 

Cage Code of the manufacturer of anomalous/nonconforming/problem assembly/component 

Manufacturer Name 

No 

Matching Field 

N

MFi

 034 Assembly/C

omponent/Part Manufacturer 

Name and CAGE code of the company or other entity that manufactured the hardware, firmware or software item(s) involved in the anomaly, incident, or problem. 

Text String 

 Initiation, 

Analysis 

Nonconforming Part/Assembly Number Manufacturer 

Manufacturer or software developer of anomalous/nonconforming/problem assembly/component 

Manufacturer Name // Manufacturer CAGE Code 

Manufacturer’s authorized Commercial and Government Entity (CAGE) Code (automatically populated) 

No 

Matching Field 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

31 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 080 Dissenting Description of reasons for 

non-concurrence with the problem resolution, including name, date, role of person dissenting 

Text String 

 Y Analysis, 

Closeout 

 No Matching Field 

Closure Comments // Closure Rationale Text // Deferral Rationale Text // MRB Rationale // Rejection Rationale 

No 

Matching Field 

N

MFi

 032 Assembly/C

omponent/Part Number 

Part Number(s) or other unique identifier of the hardware, firmware or software item(s) involved in the anomaly, incident, or problem. 

Text String 

 Initiation, 

Analysis 

Nonconforming Article/Component Number // Nonconforming Part/Assembly Number 

Part number of the lowest level that the anomaly/nonconformance/problem was isolated to. // Part/Assembly Number that the anomaly/nonconformance/problem was isolated to. 

Part Number;NCA Part Number // LRU Part Number // SRU Part Number 

No 

Matching Field 

Pm 

 012 Detection 

Location 

Geographical or orbital location of the anomalous item when problem was detected. 

Text String 

 Initiation No 

Matching Field 

Countries // Site Location 

No 

Matching Field 

Lo

 079 Concurrenc

e(s) 

Name, role, date for people that need to concur with the resolutiConcurrence(s)on for this problem, e.g., ITA, review boards, project manager. 

NASA People Taxonomy 

Picklist or Auto-fill fields via direct link to the NASA Taxonomy 

Analysis, 

Closeout 

Problem Closure Concurrences // Closure Signature(s) 

Name, role, date for people that need to concur with the closure of this problem, 

Available 

Concurrences // Concur Sign // Concur Sig Cmpl/Reqd // Focal 

No 

Matching Field 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

32 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

e.g., ITA, review boards, project manager // Quality signature at minimum; depends on significance category, risk score, approval level, etc, for who and how many closure si 

Name // several others 

 084 Configuratio

n Change? 

Was there a configuration change as a result of this problem? This would generate an automatic notification to key persons. 

Yes/No Y Analysis, 

Closeout 

 No Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi

 055 Contributing 

Factor Category(s) 

Classification of the contributing factor(s) for the problem. 

Pick List 

 Y Analysis Cause 

Code 

The cause code that most closely matches the root cause (or probable cause if root cause is not known). 

No 

matching field 

No 

Matching Field 

N

MFi

 056 Contributing 

Factors 

Description of the contributing factors to this problem (a) contributing factor is an event or condition that may have contributed to the occurrence of an undesired outcome, but if eliminated or modified, would not by itself have prevented the occurrence) 

Text String 

 Y Analysis Cause(s) Description of 

the root, probable, or proximate cause(s) for this problem (a root cause is one of multiple factors (events, 

Flight History 

Contributing Factors 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

33 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

conditions, organizational factors, etc.) that contributed to or created the proximate cause and subsequent undesired outcome, and 

 073 Corrective 

Action 

Description of final resolution to prevent reoccurrence of this problem or to minimize its impact – a systemic fix – “prescription” is provided for information to be included (see Appendix C.2). 

Text String 

 Y Analysis Corrective 

Action(s)/Recurrence Control Description(s) 

Action 

(beyond remedial action) to correct a problem and prevent/control nonconformance/ problem recurrence in existing and/or future hardware or software. Corrective action should include one or more of the following: a. Design change; b. Manufacturing 

Corrective Action 

Corrective Action 

N

MFi

 038 Criticality 

Code 

Assessment of the severity 

of the problem based on FMEA and CIL for the assembly level / this is the functional criticality level. 

Pick List 

 Y Initiation, 

Analysis 

Criticality Code / Consequence Score (Severity) 

Not defined in 0006 (see comments) // Determine Severity of Problem (1, 2, 3, 4, or 5) based on CxP 70056 

FMEA Criticality Code 

Severity Fu

C
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

34 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 024 Defect 

Characteristics 

A

fault/flaw/discrepancy/nonconformance in a component or process that causes discrepant performance of the component or assembly involved. 

Example List 

 Y Analysis Failure 

Mechanism // Malfunction // Defect Type 

The physical process which causes the failure; the manner in which an item can or actually failed to perform required function; an actual component failure/error misperformance that was an initiating event in occurrence. // Identification of the nature o 

Defect Code 

No 

Matching Field 

HMed 

 010 Detection 

Date 

Date when problem was detected. 

mm/dd/yyyy 

 Initiation Detection 

Date 

Date when problem was detected. 

Detect Date // PR Detect Date 

No 

Matching Field 

DDWD

 013 Detected 

During 

Description of the activity that led to detection of the problem, e.g., analysis, text, maintenance. 

Text String 

 Initiation Detecting 

During / Defect Activity 

Description of the activity that was occurring when the problem was identified, (e.g., analysis, functional test, environmental testing, shipping & receiving, maintenance, work authorization document number, etc.) // The defect activity is the specific ac 

Detected During 

Project/Activity 

DD
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

35 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 040 Mishap 

Report? 

Did this problem result in a formal mishap report due to damage of equipment or personal injury? 

Yes/No Initiation, 

Analysis, Closeout 

Mishap Report? 

Did this problem result in a formal mishap report due to damage of equipment or personal injury? Is a mishap per NPD 8621.1G - NASA Mishap Reporting and Investigating Policy. 

No 

matching field 

NASA Mishap Report 

N

MFi

 031 Assembly/C

omponent/Part Name 

Name(s) of the hardware, firmware or software item(s) involved in the anomaly, incident, or problem. 

Text String 

 Initiation, 

Analysis 

Nonconforming Assembly/Part Name // Nonconforming Article/Component Name 

Part Name that the anomaly/nonconformance/problem was isolated to. // Name of the lowest level Part/Component that the anomaly/nonconformance/problem was isolated to. 

Part Name // NCA Part Name // LRU Part Name // SRU Part Name 

No 

Matching Field 

Pm 

 078 Resolution 

Approver(s) 

Name, role, date for approver(s) of final resolution that corrects the problem. 

NASA People Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

Analysis, 

Closeout 

 No Matching Field 

Focal Name // Required Concurrences 

Organization - CI // Organization - AR 

(mfie

 014 Program Program name (program 

attributes defined in NPR 7120.5C). 

NASA Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

 Initiation Program The name of 

the program or programs supported 

Program No 

Matching Field 

Pm 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

36 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 015 Project Project name (project 

attributes defined in NPR 7120.5C). 

NASA Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

Y Initiation Project Project Name 

(see CxP 70070-ANX02) 

Project Project/Acti

vity 

N

MFi

 060 Proximate 

Cause Category(s) 

Classification of the proximate cause(s) for the problem. 

Pick List 

 Y Analysis Cause

Code 

The cause code that most closely matches the root cause (or probable cause if root cause is not known). 

Cause Code 

No 

Matching Field 

N

MFi

 061 Proximate 

Cause(s) 

Description of the most immediate proximate cause(s) for this problem. A proximate cause is one of multiple factors (events or conditions) that occurred, including any condition(s) that existed immediately before the undesired outcome, directly resulted 

Text String 

 Y Analysis Cause(s) Description of 

the root, probable, or proximate cause(s) for this problem (a root cause is one of multiple factors (events, conditions, organizational factors, etc.) that contributed to or created the proximate cause and subsequent undesired outcome, and 

Cause Code 

No 

Matching Field 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

37 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 027 Recurrence 

Control Required? 

“Yes” indicates that this problem has the potential to occur on other missions or systems. It's a generic issue. 

Yes/No Initiation, 

Analysis 

Corrective Action/Preventive Action Required? 

Based on significance category, risk score, criticality code, etc., the PRT will determine if corrective action is required. This may be based on the potential that this problem has to occur on other missions or systems; or the potential to recur again. I 

Recurrence Control Code 

No 

Matching Field 

RCR

 044 Related 

Problems 

Description of related problems, including the problem identifiers and how this problem is different or similar to those / this could also include descriptions of noticed irregularities that did not generate formal problem records. 

Text String 

 Initiation, 

Analysis 

Related Problem Link/Problem Linking 

List and links of PRACA problems that are related to this problem. See CxP 70068-02, Section 2.7. 

Investigation/Analysis Summary 

Contributing Factors Available 

RD

 072 Remedial 

Action 

Action taken to bring a 

specific failed unit to operational status or to eliminate an unsatisfactory condition on the specific unit / e.g., remove and replace, rework to print, Material Review Board (MRB) disposition, etc. Description of resolution to cor 

Text String 

Problem resolution summary, Problem Clarification, Analysis/Investigation Summary, Problem History, Effect on Fielded Units, Mission Effect, Last test, Recurrence 

Analysis Remedial 

Action/Disposition Description 

Description of the activities taken to disposition a nonconforming process, software item, or hardware item; 

PR MRB Disposition 

Corrective Action 

DS
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

38 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

Control actions, etc. 

 051 Requiremen

t Violation Description 

Description of the requirement that was violated and the mitigating circumstances. 

Text String 

 Initiation, 

Analysis 

 No Matching Field 

Investigation/Analysis Summary 

No 

Matching Field 

N

MFi

 026 Material 

Involved 

Identification of materials related to the anomalous item, e.g., gases, liquids. 

Example List 

Create Project specific Pick List (see examples in -0006). 

 Initiation, 

Analysis 

 No Matching Field 

Material Code 

No 

Matching Field 

N

MFi

 075 Residual 

Risk Description 

Description of the remaining risk factors (after corrective action) in using this item/system after implementation of final resolution. 

Text String 

Analysis, 

Closeout 

 No Matching Field 

No 

matching field 

No 

Matching Field 

D

 004 Problem 

Type 

Categorization of the type of problem. 

Pick List 

 Initiation Problem 

Type 

Identification if a hardware problem, software problem, GSE/facility hardware or software, or process problem (Multiple types permitted). 

No 

matching field 

Incident Type // Accident Type // Issue Type 

N

MFi

 066 Resolution 

POC 

Name, organization, email, and telephone of person responsible for resolution development. 

NASA People Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

Analysis Remedial 

Action POC 

Name, organization, email, & telephone for person/team responsible for resolution development. 

Actionee 

Name // Assigned To Last Name // Assigned To Name // Assignee Name // EMail (PR OPR) // 

Organization - CI // Organization - AR 

Eg 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

39 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

First/Last Name 

 054 Root Cause 

Analysis Techniques 

Identification of the root cause analysis techniques and/or tools that were used in the analysis, e.g., fault tree, Relex, Reason. 

Example List 

Analysis Investigatio

n and Analysis Description 

Description of the steps taken during the investigation and analysis to determine the corrective action. 

Investigation/Analysis Summary 

No 

Matching Field 

N

MFi

 058 Root Cause 

Category(s) 

Classification of the root cause(s) for the problem. 

Pick List 

 Y Analysis Cause 

Code 

The cause code that most closely matches the root cause (or probable cause if root cause is not known). 

Cause Code 

No 

Matching Field 

N

MFi

 059 Root 

Cause(s) 

Description of the root cause(s) for this problem. A root cause is one of multiple factors (events, conditions, organizational factors, etc.) that contributed to or created the proximate cause and subsequent undesired outcome, and if eliminated or modifi 

Text String 

 Y Analysis Cause(s) Description of 

the root, probable, or proximate cause(s) for this problem (a root cause is one of multiple factors (events, conditions, organizational factors, etc.) that contributed to or created the proximate cause and subsequent undesired outcome, and 

Root Cause Statement // Root Cause Summary 

Root Cause C
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

40 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 029 SubSystem The applicable subsystem 

associated with the specified system. Generally the subsystems are the first level breakdown in the hierarchy of elements that make up a system. 

Generic Subsystem 

Picklist from Table 5 in NASA Std0006. Type of element to which the anomalous item applies. Provides context for the subsystems in the Subsystems Field. 

 Initiation, 

Analysis 

Subsystem Not defined in 

0006. 

Distributed Subsystem Name // Subsystem Name 

No 

Matching Field 

Sy

 028 System Type of element to which 

the anomalous item applies. Provides context for the subsystems in the Subsystems Field. 

Generic Subsystem 

Picklist from Table 5 in NASA Std0006. Type of element to which the anomalous item applies. Provides context for the subsystems in the Subsystems Field. 

Y Initiation, 

Analysis 

System Not defined in 

0006. 

System Name 

No 

Matching Field 

E

 052 Usage 

Constraints 

Description of the constraints that were immediately applied as a result of this problem until the problem is resolved. 

Text String 

 Initiation, 

Analysis 

Usage Constraints 

Describe constraints such that processing of a part/system can’t go past point until this problem is resolved. 

Flight Effectivity 

No 

Matching Field 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

41 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 019 Vehicle/Spa

cecraft Type 

This is either the spacecraft type or a particular vehicle name. 

Pick List 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

Y Initiation No 

Matching Field 

No 

matching field 

Vehicle Class 

N

MFi

 045 Waiver/ 

Deviation? 

Has a waiver or deviation been issued for this type problem before? 

Yes/No Initiation, 

Analysis 

Waiver/Deviation/variance? 

Has a waiver, variance or deviation been issued that addresses this problem before or does a variance, waiver, or deviation need to be issued? 

No 

matching field 

No 

Matching Field 

Wia

 050 Requiremen

t Violation? 

Was this problem in violation of the functionality of the system/subsystem/assembly/component/part? 

Yes/No Initiation, 

Analysis 

 No Matching Field 

No 

matching field 

No 

Matching Field 

Rnt 

 043 Previous 

occurrence? 

Has this or a similar problem happened before in this mission or others? 

Yes/No Initiation, 

Analysis 

Previous occurrence? 

Has this or a similar problem happened before in this mission or others? 

No 

matching field 

Contributing Factors Available 

N

MFi

 047 Material 

Review Board? 

Does this problem need to be referred to the Material Review Board? 

Yes/No Initiation, 

Analysis 

Material Review Board (MRB) Required? 

Does this problem need to be referred to the Materials Review 

MRB Req'd // MRB Required 

No 

Matching Field 

MRR
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

42 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

Board?

 046 Waiver/Devi

ation Info 

Description of applicable waivers/deviation documentation. 

Text String 

 Initiation, 

Analysis 

Waiver/Deviation/variance Information 

Attach 

applicable variances/waivers/deviation documentation 

Waiver/Deviation Number 

No 

Matching Field 

D

 016 Mission 

Name 

Mission name within project, e.g., STS 114, GOES-N. 

NASA Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

 Initiation Mission 

Name 

Mission name within project that the hardware/software was assigned to when the nonconformance occurred. 

Flight Name No 

Matching Field 

MEf

 090 Notification 

Identification 

Identification of who needs to be notified as a result of this problem occurrence. 

Text String 

 Initiation, 

Analysis, Closeout 

 No Matching Field 

No 

matching field 

Report Type N

MFi

 008 Occurrence 

Location 

Geographical or orbital location of the anomalous item when problem occurred. 

Text String 

 Y Initiation Occurrence 

Location 

NASA Center, government facility, Contractor Facility, or orbital location of the anomalous item when problem occurred. 

On-Orbit Notes // Site Location 

General Location // Specific Location // Site // Country // Campus // Country - AR Origin 

Lo

 091 Owner of 

anomalous item 

Identification of who owns the hardware/software that experienced the problem. 

Text String 

Analysis, 

Closeout 

 No Matching Field 

Countries First name 

(Incident Owner) // Last Name (Incident 

Re 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

43 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

Owner) // Submitter's Employer 

 020 Payload/Inst

rument Name 

Name given to the element within the mission that is gathering the science data. 

NASA Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

 Initiation Element Not defined in 

CxP 70068. 

Flight Element Code 

No 

Matching Field 

N

MFi

 021 Payload/Inst

rument Type 

Type of instrument or payload. 

NASA Taxonomy 

Picklist or Auto-fill via direct link to the NASA Taxonomy 

 Initiation Element Not defined in 

CxP 70068. 

Flight Element Code 

No 

Matching Field 

N

MFi

 065 Potential 

Future Impact Description 

Description of the potential ripple effects of this problem within this mission or other missions, including dependencies among components, existence of common components, effectivity. 

Text String 

 Initiation, 

Analysis 

Failure Consequence 

Effect of failure on failed unit function and impact on next higher assembly, end item, or system. Pick list includes: Loss of all functions; Loss of function (partial failure); Erroneous indication of fault. 

Flight Effectivity // Investigation/Analysis Summary // ISS Flights (Deferrals) // SSP Flights (Deferrals) 

No 

Matching Field 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

44 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 048 Process 

Escape? 

Should this problem have been prevented by some established process? 

Yes/No Y Initiation, 

Analysis 

Process Escape? 

Was there a process escape? 

No 

matching field 

No 

Matching Field 

PEs

 009 Prevailing 

Conditions 

Environment in which the anomalous item existed when the problem occurred. 

Text String 

 Y Initiation No 

Matching Field 

Prevailing Conditions // Prevailing Condition Code 

Incident Notes Details 

N

MFi

 049 Process 

Description 

Description of the process that should have prevented this problem, including identification of the process and the circumstances associated with missing the problem. 

Text String 

 Y Initiation, 

Analysis 

Process Description 

Give a description of the process associated with this problem and the aspects of the process that caused the problem or could have caused a problem. 

Investigation/Analysis Summary 

Project/Activity 

N

MFi

 057 Probable 

Cause(s) 

Description of the probable cause(s) for this problem (a) probable cause is a factor that is believed to have contributed to or created the undesired outcome)—“prescription” is provided for information to be included (see Appendix C.4) —either there is a 

Text String 

 Y Analysis Cause(s) Description of 

the root, probable, or proximate cause(s) for this problem (a root cause is one of multiple factors 

Cause Code 

Contributing Factors 

C
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

45 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

(events, conditions, organizational factors, etc.) that contributed to or created the proximate cause and subsequent undesired outcome, and 

 081 Problem 

Closeout Summary 

Description of the problem resolution implementation including results. 

Text String 

 Y Analysis, 

Closeout 

Problem Closeout Summary 

Description of the problem resolution implementation including results. 

Closure Comments // Closure Rationale Text // Recurrence Control 

No 

Matching Field 

DS

 003 Problem 

Description 

Detailed description of the problem – “prescription” is provided for information to be included (see Appendix C.3). 

Large Text String 

 Y Initiation Problem 

Description 

The Problem Description is a complete and succinct explanation of the problem. It should include information that will assist in identifying the cause of the problem. 

Problem Description // Reportable Problem Description 

Description - Issue // Description - General 

PD

 001 Problem 

Identifier 

Computer-generated unique identification number, based on some predetermined scheme. 

Computer Generated 

 Y Initiation Problem 

Identifier 

Computergenerated unique identification number, based on some predetermined scheme. 

PR Number // NCR Number // Nonconformance Number 

Incident Number // Parent Case # 

P
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

46 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 006 Problem 

Occurrence Date 

Date that problem occurred. mm/dd/

yyyy 

 Y Initiation Problem 

Occurrence Date 

Date that problem occurred (if design center or problem initiator knows?) 

Reject Date Incident 

Date 

N

MFi

 007 Problem 

Occurrence Time 

Time that problem occurred. hh:mm:

ss 

 Initiation No 

Matching Field 

No 

matching field 

Time // Incident Time 

N

MFi

 092 Problem 

Status 

Identification of the current status of this problem, e.g., open, assigned, closed. 

Pick List 

 Y Initiation, 

Analysis, Closeout 

Problem Status 

Identification of the current status of this problem, e.g., open, assigned, closed. 

PR Status Case Status 

// Status // Incident Status // Corrective Action Status // Investigation Status // Issue Status 

PS

 002 Problem 

Title 

Short description of the problem (100 -120 characters), indicating the what, when, where. 

Limited Length Text String 

 Y Initiation Problem 

Title/Summary 

Short description of the problem (150 characters), indicating the what, when, where State what experienced the nonconformance and what the nonconformance is. (e.g., APU has scratch near connector J1). 

Problem Title 

Incident Title // Title // Title - CI // Issue Title 

Ti

 063 Actual Date 

Root Cause(s) 

Actual date for 

determination of root cause(s). 

mm/dd/yyyy 

Analysis No 

Matching Field 

PR Release Date 

No 

Matching Field 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

47 of 112 

NESC Request No.: 07-031-I

0006 Only 

0006 

Sort 

Order 

Field in 

0006 Definition in 0006 

Type 

or 

Source 

0006 

Notes from 

0006 Required PHASE CxP Field(s) CxP Field Descriptions ISS Field(s) 

ISS 

Field 

Descript

ions 

IRIS 

Field(s) 

IRIS Field 

Descriptions 

 064 Potential 

Future Impact? 

Are there potential ripple 

effects of this problem within this mission or other missions? 

Yes/No Initiation, 

Analysis 

 No Matching Field 

No 

matching field 

No 

Matching Field 

N

MFi
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

48 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

ARN Source 

Identifier 

Identify the agency, group, or organization which issued the report number, and which assures the uniqueness of the report number within its system, i.e., GPS I / Intelsat III; IUS; or possibly the name of a contractor that issues anomaly reports. 

Aerospace 

ATR 

ARN 

Source Identifier 

Idethe aggroorgion issthe nuanwhasthe unss repnuwitsysi.eI / IntIII; or pothe of cor thissanrep

Comments any relevant 

information that is not contained in the other fields regarding this anomaly 

Aerospace 

ATR 

Comments an

relinfon nocod iothfieregthis an
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

49 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Confidence Level 

The level of confidence that the source of the anomaly can be identified to have been a particular anomalous item. See table 7 of the TOR 

Aerospace 

ATR 

Confidence Level 

Thof coe tsothe ancaideto bepaanus Se7 oTO

Database field name(s) 

Identify all database fields, elements, or columns involved with the anomaly. See Table 13 in the TOR 

Aerospace 

ATR 

Database field name(s) 

Ideall dafieele, ocoinvwitanSeTain TO

Database name(s) 

Identify all databases involved with the anomaly. See Table 13 in the TOR 

Aerospace 

ATR 

Database name(s) 

Ideall das invwitanSeTain TO

Database record(s) 

Identify all database records, by record ID, involved with the anomaly. See Table 13 in the TOR 

Aerospace 

ATR 

Database record(s) 

Ideall darecby ID, inv
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

50 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

witanSeTain TO

Database table name(s) 

Identify all database tables involved with the anomaly. See Table 13 in the TOR 

Aerospace 

ATR 

Database table name(s) 

Ideall databinvwitanSeTain TO

Downtime (in seconds) 

The amount of time (in seconds) "normal" operation was disrupted. 

Aerospace 

ATR 

Downtime (in seconds) 

Thamof (in se"noopwadis. 

Fourth level development identification 

The conventionally developed module name or the object oriented affected method(s). See table 13. 

Aerospace 

ATR 

Fourth level development identification 

the conaded mnathe objoriaffme). tab

In-production Item Closure Date 

Date the corrective action for similar items currently in the factory is resolved. See table 7. 

Aerospace 

ATR 

Inproduction Item Closure Date 

dacoe afor simitecuin fac
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

51 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

resSe7. 

In-production Item Disposition Category 

The category of the actions taken as a result of the anomalous event (e.g., Use As Is, Change Specification, Redesign). See table 7. 

Aerospace 

ATR 

Inproduction Item Disposition Category 

Thcaof actaka rof anus (e.UsIs, ChSptioRe). Stab

Recovery Method Category 

redundancy, software upload, operational workaround, automatic recovery, and reduced capability 

Aerospace 

ATR 

RecoveryMethod Category 

redcy, soupopal wondauc recanredca

Reference ARN Source Identifier 

the organization issuing the ARN. See table 6 

Aerospace 

ATR 

Reference ARN Source Identifier 

the orgion issthe Se6 

Reference Type 

Indicates what aspect of a referenced anomaly makes it relevant to the current anomaly. Allowed values are: 

Aerospace 

ATR 

Reference Type 

Indwhasa refd 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

52 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

repeat within satellite / repeat within fleet; repeat on-ground. See table 6 

anmarelto cuanAllvaarerepwitsarepwitflerepongroSe6 

Second level development identification 

the conventionally developed CSC or the object-oriented base class(es) name(s). See table 13. 

Aerospace 

ATR 

Second level development identification 

the conaded Cthe objoribaclanaSe13

Software build version number 

Enter the entire name of the software application, including the build version number. See table 13 

Aerospace 

ATR 

Software build version number 

Enennathe soapn, incthe venuSe13 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

53 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Symptom Duration 

indicate duration of the anomalous behavior as “persistent” (permanent, continual), “transient” (momentary, temporary), “intermittent” (recurring at irregular intervals), “periodic” (recurring at regular intervals), or “unrepeatable” (cannot recreate). 

Aerospace 

ATR 

Symptom Duration 

indduof anus beas “pent” (pent, co), “tra” (marytemy), “inen(reat irreint, “pe(reat int, o“unab(carec

Task(s) or process(es) affected by defect 

Software runtime task or process affected by the defect. See table 13 

Aerospace 

ATR 

Task(s) or process(es) affected by defect 

Soruntasproaffby deSe13 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

54 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Test Like You Fly Exception 

Enter "Yes" if the most likely contributor to the system was processed as an exception to Test Like you Fly Criteria, as defined in 2.3.8.1-T1-Test-1.1-G Test Engineering Guidebook (The Test Like You Fly principle necessitates that a product should experi 

Aerospace 

ATR 

Test Like You Fly Exception 

En"Yethe likecoor syswaprod aexto LikFly Cras dein 2.3T11.1TeEnng Guok TeYoprinetes proshex

Third level development identification 

the conventionally developed CSU or the object oriented derived class(es) names(s). See table 13. 

Aerospace 

ATR 

Third level development identification 

the conaded Cthe objorideclana. tab
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

55 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Unique Item Identifier (UII) 

A concatenation of 

the Enterprise Identifier, Original Part Number, and Serial Number, not to exceed 78 characters. See table 12. 

Aerospace 

ATR 

Unique Item Identifier (UII) 

A

coatithe Ene IdeOrPaNuanSeNunoex78 chs. tab

Unbuild Item Closure Date 

date corrective action is resolved for similar items in the program production stream (but not yet in the factory). See table 7. 

Aerospace 

ATR 

Unbuild Item Closure Date 

dacoe ais resfor simitethe propron s(buyefacSe7. 

Unbuild Item Disposition Category 

The category of the actions taken as a result of the anomalous event (e.g., Use As Is, Change Specification, Redesign). See table 7. 

Aerospace 

ATR 

Unbuild Item Disposition Category 

Thcaof actaka rof anus (e.UsIs, Ch
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

56 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

SptioRe). Stab

Verification Assessment Narrative 

a detailed description of how the verification program was executed that may have impacted the detected anomaly. 

Aerospace 

ATR 

Verification Assessment Narrative 

a deden othe ven prowaexthahaimthe dean

Verification Level 

the verification level that should have detected the most likely cause of the anomaly, given the verification process used 

Aerospace 

ATR 

Verification Level 

the ven lthashhadethe likecathe angivven prous

Verification Category 

Test, Analysis, Simulation or other method used to detect the anomaly. 

Aerospace 

ATR 

Verification Category 

TeAnSimn omeusdethe an
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

57 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Verification Method Name 

name of the verification method included in the verification program that should have identified the detected anomaly. 

Aerospace 

ATR 

Verification Method Name 

nathe ven mincin ven prothashhaidethe dean

Impact Severity on Mission 

Numeric code identifying the severity of the impact on the mission (ranges from Catastrophic to Negligible). 

Aerospace 

ATR 

Impact Severity on Mission 

nucoideg tsevof imon mis(rafroCaphNee). 

Impact Severity on Anomalous Item 

Numeric code identifying the severity of the impact on the anomalous item (ranges from Catastrophic to Negligible) 

Aerospace 

ATR 

Impact Severity on Anomalous Item 

nucoideg tsevof imon anus (rafroCaphNee) 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

58 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Plus/Minus Anomaly DateTime Offset 

The range in date and time during which the anomaly may have occurred. See 4.2.17. in the TOR. 

Aerospace 

ATR 

Plus/Minus Anomaly DateTime Offset 

ThrandatimduwhanmahaocSe4.2the 

Data Collection Report Date 

Enter the date that this report was prepared for submittal to the appropriate agency for analysis and trending. 

Aerospace 

ATR 

Data Collection Report Date 

Endathis repwaprefor suto apte agfor anantre

IFA Number If checked yes to 

IFA, need IFI number here. Generate automatically based on what IFI process ends up being. 

CxP 70068-03 // KSCPR 

IFA Number 

If checked yes to IFA, need IFI number here. Generate automatically based on what IFI process ends up being. 

IFA# Official IFA 

number assigned by SSP or by design element/project office (SASCB). 

In-Flight Anomaly (IFA) 

In-flight anomalies (IFA’s) are problems that occur from L-5 hours during the mission until recovery. (Including its on-orbit/in-space duty cycle). This includes any IFA’s detected during post-mission or postuse analysis. (See 

CxP 70068-03 

In-Flight Anomaly (IFA) 

In-flight anomalies (IFA’s) are problems that occur from L-5 hours during the mission until recovery. (Including its onorbit/in-space duty cycle). This includes any IFA’s detected during 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

59 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Table 4.1.3 for unique In-F 

post-mission or post-use analysis. (See Table 4.1.3 for unique In-F 

Likelihood Score 

Determine Likelihood of Problem occurring again (1, 2, 3, 4, or 5) based on Qualitative and Quantitative values per CxP 70056 

CxP 70068-03 

Likelihood Score 

Determine Likelihood of Problem occurring again (1, 2, 3, 4, or 5) based on Qualitative and Quantitative values per CxP 70056 

Location on Hardware 

Zone location on hardware itself, if applicable Based on engineering drawings. 

CxP 70068-03 // KSCPR 

Location on Hardware 

Zone location on hardware itself, if applicable Based on engineering drawings. 

Zone 

MRB Rationale Rationale for 

accepting the disposition of the non-conforming part(s). 

CxP 70068-03 

MRB Rationale 

Rationale for accepting the disposition of the non-conforming part(s). 

Next Higher Assembly 

 CxP 

70068-03 & ISS PRACA Db & Northrop Grumman - F1 

Next Higher Assembly 

 Next 

Higher Assembly 

Next Higher Assembly Part Number 

 CxP 

70068-03 & ISS PRACA Db & Northrop Grumman - F1 

Next Higher Assembly Part Number 

 Next 

Higher Assembly Part Number 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

60 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Next Higher Assembly Serial Number/ Lot/Date Code 

 CxP 

70068-03 & ISS PRACA Db & Northrop Grumman - F1 

Next Higher Assembly Serial Number/ Lot/Date Code 

 Next 

Higher Assembly Serial Number/ Lot/Date Code 

Alias Identifying 

numbers/names of the vendor’s nonconformance/ problem report. 

CxP 70068-03 

Alias Identifying 

numbers/names of the vendor’s nonconformance/ problem report. 

Applicable 

FMEA/CIL and/or Hazard Report and/or Program Risk 

Link to the version of the applicable FMEA/CIL, Hazard Report, and/or Program Risk Assessment at time of PR closure. Mandatory for government Facilities and NASA Centers; otherwise Optional. 

CxP 70068-03 

Applicable 

FMEA/CIL and/or Hazard Report and/or Program Risk 

Link to the version of the applicable FMEA/CIL, Hazard Report, and/or Program Risk Assessment at time of PR closure. Mandatory for government Facilities and NASA Centers; otherwise Optional. 

Cause Type List of whether 

cause listed is a “Root Cause,” “Probable Cause,” or a “Proximate Cause” either there is a root cause or a probable cause (not both). Optional/ May be selected by the Project. Required for directly entered problems. 

CxP 70068-03 

Cause Type 

List of whether cause listed is a “Root Cause,” “Probable Cause,” or a “Proximate Cause” either there is a root cause or a probable cause (not both). Optional/ May be selected by the Project. Required 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

61 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

for directly entered problems. 

Common Hardware - Automatic 

Automatically filled in 

by software for any common part numbers (need to define work flow) 

CxP 70068-03 

Common Hardware - Automatic 

Automatically filled 

in by software for any common part numbers (need to define work flow) 

Cost Exceeded $100K 

Yes, if Total Cost (Labor and Material) to work the problem exceeds $100K (High level estimate of cost.) 

CxP 70068-03 

Cost Exceeded $100K 

Yes, if Total Cost (Labor and Material) to work the problem exceeds $100K (High level estimate of cost.) 

DD250? Has the H/W or S/W 

been accepted by the government? 

CxP 70068-03 & ISS PRACA Db 

DD250? Has the H/W or 

S/W been accepted by the government? 

 DD250? Has the H/W or 

S/W been accepted by the government? 

Detectable Fault is detectable 

during pre-operation screening, preventive maintenance checks, etc. Pick list includes: Screenable, Nonscreenable 

CxP 70068-03 

Detectable 

Fault is detectable during preoperation screening, preventive maintenance checks, etc. Pick list includes: Screenable, Nonscreenable 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

62 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Failure Detection 

Identification of failure detection to include Built-In-Test (BIT), Built-In-TestEquipment (BITE), Preventive Maintenance Screen, Corrective Maintenance 

CxP 70068-03 

Failure Detection 

Identification of failure detection to include Built-InTest (BIT), Built-InTest-Equipment (BITE), Preventive Maintenance Screen, Corrective Maintenance 

Program Approval Required? 

Is program approval required? 

CxP 70068-03 

Program Approval Required? 

Is program approval required? 

Project Approval Required? 

Is project approval required/desired? These approval field(s) depend on significance category, risk score, FMEA/CIL criticality code, and Resolution Actions. 

CxP 70068-03 

Project Approval Required? 

Is project approval required/desired? These approval field(s) depend on significance category, risk score, FMEA/CIL criticality code, and Resolution Actions. 

Refurbishment Item 

Is the item identified as a reuse item? Is the item refurbished at center? Is the item refurbished at Depot Level Maintenance? 

CxP 70068-03 

Refurbishment Item 

Is the item identified as a reuse item? Is the item refurbished at center? Is the item refurbished at Depot Level Maintenance? 

Repair Grading Identification of 

preventive and corrective maintenance repair results. Indication of effect of repair on system functionality. Includes: Good - Condition return to service Above Average - Condition minor degradation Average - Condition adequate to function. 

CxP 70068-03 

Repair Grading 

Identification of preventive and corrective maintenance repair results. Indication of effect of repair on system functionality. Includes: Good - Condition return to service Above Average - Condition minor degradation Average - Condition adequate to 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

63 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

function. 

Repair/Fix Elapsed 

Maintenance Time from fault/failure detection to return to service. 

CxP 70068-03 // Northrop Grumman - F18 FRACAS 

Repair/Fix Elapsed 

Maintenance Time from fault/failure detection to return to service. 

Risk Score Automatically 

calculates the product of Consequence Score times Likelihood Score 

CxP 70068-03 

Risk Score 

Automatically 

calculates the product of Consequence Score times Likelihood Score 

Run time/ Elapsed Time/Cycles 

For items with Elapsed Time Indicator (ETI) - Time elapsed or number of cycles from NASA Acceptance of equipment item to fault/failure/anomaly detection; At the level at which maintenance action is initiated. 

CxP 70068-03 // Northrop Grumman - F18 FRACAS 

Run time/ Elapsed Time/Cycles 

For items with Elapsed Time Indicator (ETI) - Time elapsed or number of cycles from NASA Acceptance of equipment item to fault/failure/anomaly detection; At the level at which maintenance action is initiated. 

Safety critical software? 

Assessment of the 

software/firmware/complex electronics safety functions as defined in NASASTD-8719.13B, Section 4.1.1, NASA Software Safety Standard. If the system is determined to be safety critical then the software must be evaluated for its contribut 

CxP 70068-03 

Safety critical software? 

Assessment of the 

software/firmware/complex electronics safety functions as defined in NASASTD-8719.13B, Section 4.1.1, NASA Software Safety Standard. If the system is determined to be safety critical then the software must be evaluated for its 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

64 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

contribution 

Significance Category 

Significance of problem based on criteria in volume 1 of the PRACA Requirements document 

CxP 70068-03 

Significance Category 

Significance of problem based on criteria in volume 1 of the PRACA Requirements document 

Software Classification 

Identify classification of the defective software/firmware/complex electronics as defined by NPR 7150.2. Refer to the system classification assessment or contact your software assurance representative for assistance in selection. 

CxP 70068-03 

Software Classification 

Identify classification of the defective software/firmware/complex electronics as defined by NPR 7150.2. Refer to the system classification assessment or contact your software assurance representative for assistance in selection. 

Software Type Identify the type of 

software/firmware/ complex electronics that is defective. 

CxP 70068-03 

Software Type 

Identify the type of software/firmware/ complex electronics that is defective. 

Software Version (CSCI/CSC/ CSU) 

Computer Software Configuration Item (CSCI) An aggregation of software that is designated for configuration management and treated as a single entity in the configuration 

CxP 70068-03 // Aerospace ATR 

Software Version (CSCI/CSC/ CSU) 

Computer Software Configuration Item (CSCI) An aggregation of software that is designated for configuration management and treated as a single entity in the 

Software build version number 

Enennathe soapn, incthe venu
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

65 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

management process. [IEEE-STD 610.12-1990] Computer Software Component (CSC)- A dist 

configuration management process. [IEEESTD 610.12-1990] Computer Software Component (CSC)- A dist 

Se13 

Work Authorization Document Number 

If WAD is initiated based on remedial or corrective action, list WAD number. Active Link with Work Authorization System until WAD closed then version in Government approved format version of final (closed) WAD is attached 

CxP 70068-03 // IRIS 

Work Authorization Document Number 

If WAD is initiated based on remedial or corrective action, list WAD number. Active Link with Work Authorization System until WAD closed then version in Government approved format version of final (closed) WAD is attached 

WOA State the Work 

Order Authorization, if applicable. 

Name Name of person 

responsible to open and close Flight Effectivity 

ISS PRACA Db 

 Name Name of person 

responsible to open and close Flight Effectivity 

NASA Engineer Review 

Accept/Reject/Clear 

selection boxes for PR Closure 

ISS PRACA Db 

 NASA 

Engineer Review 

Accept/Reject/Cl

ear selection boxes for PR Closure 

NASA QA Review 

NASA QA Accept/Reject/Clear selection boxes for PR Closure 

ISS PRACA Db 

 NASA 

QA Review 

NASA QA Accept/Reject/Clear selection boxes for PR Closure 

Accept? This field is disabled 

until the PR is released 

ISS PRACA Db 

Accept? This field is 

disabled until the PR is released 

Board Chair Accept/Reject/Clear 

selection boxes for PR Closure 

ISS PRACA Db 

 Board 

Chair 

Accept/Reject/Cl

ear selection boxes for PR Closure 

Identification Data 

Activates Problem 

Identification form (used to enter original PR data) 

ISS PRACA Db 

 Identificat

ion Data 

Activates 

Problem Identification form (used to enter original PR 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

66 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

data)

Export Control ISS 

PRACA Db 

 Export 

Control 

F.E. Signoff Allows users to 

add/delete flights and enter signature(s) for individual flights. 

ISS PRACA Db 

 F.E. 

Signoff 

Allows users to 

add/delete flights and enter signature(s) for individual flights. 

Local MRB ISS 

PRACA Db 

 Local 

MRB 

MAR Number ISS 

PRACA Db 

 MAR 

Number 

MAR Required ISS 

PRACA Db 

 MAR 

Required 

Justification Justification for 

changes to the PR’s Flight Effectivity 

ISS PRACA Db 

 Justificati

on 

Justification for changes to the PR’s Flight Effectivity 

Like H/W OnOrbit Indicates if like hardware is already 

on-orbit. 

ISS PRACA Db 

 Like H/W 

On-Orbit 

Indicates if like hardware is already on-orbit. 

CEO Engineer Review 

 ISS 

PRACA Db 

 CEO 

Engineer Review 

CEO QA Review 

CEO QA Accept/Reject/Clear 

ISS PRACA Db 

 CEO QA 

Review 

CEO QA Accept/Reject/Clear 

CEO Safety Review 

 ISS 

PRACA Db 

 CEO 

Safety Review 

Closed NotReportable Criteria Code 

 ISS 

PRACA Db 

 Closed 

NotReportable Criteria Code 

Contractor QA Review 

 ISS 

PRACA Db 

 Contracto

r QA Review 

Date Signed Date signed box for 

each required concurrence signature. 

ISS PRACA Db 

 Date 

Signed 

Date signed box for each required concurrence signature. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

67 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Date Submitted ISS 

PRACA Db 

 Date 

Submitted // PR Submit Date 

Flight Effectivity Status 

Open/Closed buttons indicating the status. 

ISS PRACA Db 

 Flight 

Effectivity Status 

Open/Closed buttons indicating the status. 

Flt Sig date ISS 

PRACA Db 

 Flt Sig 

date 

Flt Status ISS 

PRACA Db 

 Flt Status

Flt# ISS 

PRACA Db 

 Flt#

FMEA Number Unique FMEA 

worksheet number that identifies the hardware item and specific failure mode being analyzed. If multiple worksheets apply, identify the worst-case effect FMEA worksheet. 

ISS PRACA Db // KSCPR 

 FMEA 

Number 

Unique FMEA worksheet number that identifies the hardware item and specific failure mode being analyzed. If multiple worksheets apply, identify the worst-case effect FMEA worksheet. 

FMEA # The FMEA 

number which addresses the failure mode of failed elements/LRU/SRU (to lowest level possible). 

FMEA Rationale 

Explanation/additional information/rationale for FMEA criticality and implementation. 

ISS PRACA Db 

 FMEA 

Rationale 

Explanation/additional information/rationale for FMEA criticality and implementation. 

FMEA Verified Selected by R/M 

engineer after all FMEA data has been entered and verified 

ISS PRACA Db 

 FMEA 

Verified 

Selected by R/M engineer after all FMEA data has been entered and verified 

Fracture Critical Indicator 

 ISS 

PRACA Db 

 Fracture 

Critical Indicator 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

68 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

PR Level ISS 

PRACA Db 

 PR Level

Pre/Post DD250 

 ISS 

PRACA Db 

 Pre/Post 

DD250 

Private PR # Non-editable field; 

private number is assigned when a problem has been submitted/saved. This is not the public PR number. 

ISS PRACA Db 

 Private 

PR # 

Non-editable field; private number is assigned when a problem has been submitted/saved. This is not the public PR number. 

Problem Priority Designation (PPD) 

 ISS 

PRACA Db 

 Problem 

Priority Designation (PPD) 

Reject PR Used to reject public 

release of a PR that does not meet reportability criteria. 

ISS PRACA Db 

 Reject 

PR 

Used to reject public release of a PR that does not meet reportability criteria. 

Rejected By ISS 

PRACA Db 

 Rejected 

By 

Serial Number Status 

 ISS 

PRACA Db 

 Serial 

Number Status 

SPRT Lead Review 

Accept/Reject/Clear 

selection boxes for PR Closure 

ISS PRACA Db 

 SPRT 

Lead Review 

Accept/Reject/Cl

ear selection boxes for PR Closure 

System Problem Resolution Team 

System Problem Resolution Team (SPRT) that will be responsible for the PR 

ISS PRACA Db 

 System 

Problem Resolution Team 

System Problem Resolution Team (SPRT) that will be responsible for the PR 

Test Op Code Code identifying the 

type of test/operation at the time the problem was detected. 

ISS PRACA Db // Northrop Grumman - F18 

 Test Op 

Code 

Code identifying the type of test/operation at the time the problem was detected. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

69 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

FRACAS 

Trend Codes Verified 

Selected by CEO QA after all trend codes have been entered and verified 

ISS PRACA Db 

 Trend 

Codes Verified 

Selected by CEO QA after all trend codes have been entered and verified 

Updated By ISS 

PRACA Db 

 Updated 

By 

Applicable 

Paragraph 

 Northrop 

Grumman - F18 FRACAS 

Bench Test Reqd 

 Northrop 

Grumman - F18 FRACAS 

Buyer Northrop 

Grumman - F18 FRACAS 

Customer Date Northrop 

Grumman - F18 FRACAS 

Engineering Liaison Date 

 Northrop 

Grumman - F18 FRACAS 

Fact Closed Date 

 Northrop 

Grumman - F18 FRACAS 

Fact Review Completed? 

 Northrop 

Grumman - F18 FRACAS 

Fail Verified Northrop 

Grumman - F18 FRACAS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

70 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

How detect bit Northrop 

Grumman - F18 FRACAS 

How Indicate bit 

 Northrop 

Grumman - F18 FRACAS 

How Isolate bit Northrop 

Grumman - F18 FRACAS 

Final How Mal Northrop 

Grumman - F18 FRACAS 

JCN Job Control number Northrop 

Grumman - F18 FRACAS 

Maintenance Level 

 Northrop 

Grumman - F18 FRACAS 

Manufacturing Status 

 Northrop 

Grumman - F18 FRACAS 

Material Eng Status 

 Northrop 

Grumman - F18 FRACAS 

Modified Part Number 

 Northrop 

Grumman - F18 FRACAS 

Other How Isol bit 

 Northrop 

Grumman - F18 FRACAS 

Part Category Code 

 Northrop 

Grumman - F18 FRACAS 

Preliminary Review Date 

 Northrop 

Grumman - F18 FRACAS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

71 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Qty Inspected Northrop 

Grumman - F18 FRACAS // USAF DRIS 

Qty Rejected Northrop 

Grumman - F18 FRACAS // USAF DRIS 

Quality Status Northrop 

Grumman - F18 FRACAS 

Receiving Report No 

 Northrop 

Grumman - F18 FRACAS 

Reliability Eng Status 

 Northrop 

Grumman - F18 FRACAS 

Repair Qty Northrop 

Grumman - F18 FRACAS 

Repair Time Date 

 Northrop 

Grumman - F18 FRACAS 

Rtn to Supplier Qty 

 Northrop 

Grumman - F18 FRACAS 

Rwk to Spec Qty 

 Northrop 

Grumman - F18 FRACAS 

Safety Analysis RHI 

Risk Hazard Index (RHI) derived by combining the probability of occurrence with hazard severity. The RHI forms the basis for judging the 

Northrop Grumman - F18 FRACAS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

72 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

acceptability of a risk and to prioritize resources. 

Safety Eng Status 

 Northrop 

Grumman - F18 FRACAS 

Safety Final RHI 

Risk Hazard Index (RHI) derived by combining the probability of occurrence with hazard severity. The RHI forms the basis for judging the acceptability of a risk and to prioritize resources. 

Northrop Grumman - F18 FRACAS 

Safety Initial RHI 

Risk Hazard Index (RHI) derived by combining the probability of occurrence with hazard severity. The RHI forms the basis 

Northrop Grumman - F18 FRACAS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

73 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

for judging the acceptability of a risk and to prioritize resources. 

Scrap Qty Northrop 

Grumman - F18 FRACAS 

Ship Date Northrop 

Grumman - F18 FRACAS 

Std Repair Qty Northrop 

Grumman - F18 FRACAS 

Team Code Northrop 

Grumman - F18 FRACAS 

Test Failure Northrop 

Grumman - F18 FRACAS 

Time/Unit Northrop 

Grumman - F18 FRACAS 

Use as is Qty Northrop 

Grumman - F18 FRACAS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

74 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Warranty Expiration Date 

 Northrop 

Grumman - F18 FRACAS // USAF DRIS 

Type FENR Northrop 

Grumman - F18 FRACAS 

Relevant? Northrop 

Grumman - F18 FRACAS 

Relevant Date Northrop 

Grumman - F18 FRACAS 

Failure Analysis Required? 

 Northrop 

Grumman - F18 FRACAS 

Failure Analysis Required Date 

 Northrop 

Grumman - F18 FRACAS 

Failure Analysis Required By 

 Northrop 

Grumman - F18 FRACAS 

Failure Analysis Approved? 

 Northrop 

Grumman - F18 FRACAS 

Failure Analysis Approved Date 

 Northrop 

Grumman - F18 FRACAS 

Failure Analysis Approved By 

 Northrop 

Grumman - F18 FRACAS 

Failure Trend Northrop 

Grumman - F18 FRACAS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

75 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

No Fault Found Northrop 

Grumman - F18 FRACAS 

Failure Analysis Finding 

 Northrop 

Grumman - F18 FRACAS 

Safety Initial RHI By 

 Northrop 

Grumman - F18 FRACAS 

Safety Final RHI By 

 Northrop 

Grumman - F18 FRACAS 

Safety Final RHI Date 

 Northrop 

Grumman - F18 FRACAS 

Pertinent Stress Levels 

 Northrop 

Grumman - F18 FRACAS 

Verification Method/Period 

 Northrop 

Grumman - F18 FRACAS 

Reliability Northrop 

Grumman - F18 FRACAS 

Quality Comments 

 Northrop 

Grumman - F18 FRACAS 

Design Comments 

 Northrop 

Grumman - F18 FRACAS 

Built-In-Test Indication of Failure 

 Northrop 

Grumman - F18 FRACAS 

Failure Analysis Results 

 Northrop 

Grumman - F18 FRACAS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

76 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Attachment Northrop 

Grumman - F18 FRACAS 

Failure Analysis Attachment 

 Northrop 

Grumman - F18 FRACAS 

Workflow Northrop 

Grumman - F18 FRACAS 

Complaint Narrative 

Additional 

Information not included in the other fields that will assist in identifying the exhibits. 

USAF DRIS 

Condition Code USAF 

DRIS 

Credit/Replacement Statement 

 USAF 

DRIS 

Action Taken Maintenance action 

taken to include Removal, Replace, Repair, Service or Calibrate 

CxP 70068-03 // Northrop Grumman - F18 FRACAS // USAF DRIS 

Action 

Taken 

Maintenance action taken to include Removal, Replace, Repair, Service or Calibrate 

Date Exhibit Released 

Date that the exhibit was released to the Screening Point, Action Point, or support point. 

USAF DRIS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

77 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Deficiency Responsibility Code 

Used primarily to determine who (contractor or Government) was responsible for the reported or any other deficiency found during the investigation. They are measurements used to evaluate contractor’s/Government’s quality performance. The responsibility he reported or any other deficiency found during the investigation. 

USAF DRIS 

Estimated Repair Cost 

 USAF 

DRIS 

Exhibit Holding Activity 

Name, address and phone numbers of contact person for the DR exhibit holding activity. 

USAF DRIS 

Exhibit Released To 

Name, address, and telephone number of the Screening Point, Action Point, or support point to whom the exhibit was released. 

USAF DRIS 

GBL Number If unknown, leave 

blank. 

USAF DRIS 

Government Furnished Material (GFM) 

 USAF 

DRIS 

National Stock Number 

The NSN and the applicable materiel management aggregation code. If no stock number is assigned enter “SL.” Use the NSN of the TCTO or when reporting deficiencies on nonUSAF DRIS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

78 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

stocklisted parts in a TCTO or repair kit. For software deficiencies enter the Compu 

Next inspection due 

 USAF 

DRIS 

Purchase Order Number 

Enter these numbers or any other available transportation document number in lieu of the GBI. Such numbers appear on the container, purchase document and/or the item. If unknown, enter “UNK.” 

Northrop Grumman - F18 FRACAS & USAF DRIS 

Quantity In Stock 

The quantity of materiel from the same manufacturer remaining in stock. 

USAF DRIS 

Quantity Received 

Total number of items received in the lot or batch in which the condition was found, if known. Disregard the unit of issue. 

USAF DRIS 

Reason or authority 

 USAF 

DRIS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

79 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Requisition Number 

Required for credit, but if unknown, leave blank. 

USAF DRIS 

Result of Investigation (ROI) Code 

Specifies the result of the investigation relative to the reported deficiency; the ROI Code should support, substantiate, or refute the root cause of the reported deficiency. Used with one of the associated status codes. 

USAF DRIS 

Results of stock screening 

Results of, or necessity for stock screening. 

USAF DRIS 

Shipper, City And State 

When the shipper of an item is different from the manufacturer, also include the shipper’s or supplier’s name. 

USAF DRIS 

Support Data Mailed 

Describe support data provided (photographs, tags, labels, etc.) and ensure the DR control number is identified on any support data mailed under separate cover. 

USAF DRIS 

Unit cost Dollar value of the 

deficient item (per unit of issue). 

USAF DRIS 

Unit of Issue Self Explanatory USAF 

DRIS 

Warranty Item? USAF 

DRIS 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

80 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Work Unit Code 

The WUC of the item for which the DR is submitted. Refer to the applicable -06 technical order (aircraft, support equipment, munitions, etc). For software DRs, if a WUC is not available for specific item but there is one for the NHA, use the WUC of the NH 

Northrop Grumman - F18 FRACAS // USAF DRIS 

Site Type Onsite (NASA 

property)/Offsite (NASA contractor property)/Other (neither) 

IRIS Site Type Onsite (NASA 

property)/Offsite (NASA contractor property)/Other (neither) 

AR Assigned 

By 

Name of AR sender IRIS AR Assigned 

By 

Name of AR sender

AR Assigned 

To 

Name of AR recipient 

IRIS AR Assigned 

To 

Name of AR recipient 

AR Number Displays unique 

Action Request ID assigned sequentially by IRIS 

IRIS AR Number Displays unique 

Action Request ID assigned sequentially by IRIS 

AR Title Short descriptor of 

AR 

IRIS AR Title Short descriptor of 

AR 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

81 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Is this AR private (Between Sender and Recipient Only)? 

Yes/No IRIS Is this AR 

private (Between Sender and Recipient Only)? 

Yes/No 

Sch. Comp. Date 

Displays date in future of AR assignment date for suspense tracking. Default is 14 days, can be changed by AR assigner. 

IRIS Sch. Comp. 

Date 

Displays date in future of AR assignment date for suspense tracking. Default is 14 days, can be changed by AR assigner. 

Apply Privacy 

Act? 

Yes/No IRIS Apply Privacy 

Act? 

Yes/No 

Description - Attachment 

Description of attached file contents 

IRIS Description - 

Attachment 

Description of attached file contents 

Last Modified By 

Name of IRIS User most recently modifying issue record 

IRIS Last Modified 

By 

Name of IRIS User most recently modifying issue record 

Notification Sent Date 

User enters date IRIS Notification 

Sent Date 

User enters date

Audit Date 

From 

Date range start IRIS Audit Date 

From 

Date range start

Audit Date To Date range end IRIS Audit Date To Date range endTitle Search Searches Incident 

Titles 

IRIS Title Search Searches Incident 

Titles 

Organization Type 

All/Contractor/Organi

zation 

IRIS Organization 

Type 

All/Contractor/Organi

zation 

Sched Comp. Date From 

Date range start IRIS Sched Comp. 

Date From 

Date range start

Sched Comp. Date To 

Date range end IRIS Sched Comp. 

Date To 

Date range end

Employee Type 

Example - NASA government employee 

IRIS Employee 

Type 

Example - NASA government employee 

Level of Experience 

Time employed with NASA or NASA contractor 

IRIS Level of 

Experience 

Time employed with NASA or NASA contractor 

Organization NASA real estate 

holding associated with IRIS case 

IRIS Organization NASA real estate 

holding associated with IRIS case 

Safety Devices Provided? 

PPE, guards, other controls provided 

IRIS Safety 

Devices Provided? 

PPE, guards, other controls provided 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

82 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Safety Devices Used? 

PPE, guards, other controls used 

IRIS Safety 

Devices Used? 

PPE, guards, other controls used 

Classification, Investigation Type 

Example: Condition of employee concern where there is no injury or only minor injury requiring first aid and no significant equipment/property damage/mission failure (less than $1,000), but which possesses a potential to cause a mishap. 

IRIS Classification, 

Investigation Type 

Example: Condition of employee concern where there is no injury or only minor injury requiring first aid and no significant equipment/property damage/mission failure (less than $1,000), but which possesses a potential to cause a mishap. 

Classification Example: COTS IRIS Classification Example: COTSContractor Investigation Type 

Example: Responsible contractor convenes board 

IRIS Contractor 

Investigation Type 

Example: Responsible contractor convenes board 

Government Investigation Type 

Example: NASA appoints team 

IRIS Government 

Investigation Type 

Example: NASA appoints team 

Headquarters Notified? 

Telephonic notification at minimum of HQ OSMA 

IRIS Headquarters 

Notified? 

Telephonic notification at minimum of HQ OSMA 

Incident Estimate 

Estimated sum of the costs (the greater value of actual or fair market value) of damaged property, destroyed property, or mission failure, actual cost of repair or replacement, labor (actual value of replacement or repair hours for internal and external/c 

IRIS Incident 

Estimate 

Estimated sum of the costs (the greater value of actual or fair market value) of damaged property, destroyed property, or mission failure, actual cost of repair or replacement, labor (actual value of replacement or repair hours for internal and external/c 

Indicator Example: Affected 

Primary Objective(s) of Mission 

IRIS Indicator Example: Affected 

Primary Objective(s) of Mission 

Probability Example: Likelihood IRIS Probability Example: Likelihood 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

83 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

of recurrence 1-1/10 of recurrence 1-1/10

Class Example: Real 

estate holding or structure 

IRIS Class Example: Real 

estate holding or structure 

Report Source Example: IRIS Quick 

Incident Report (Health) 

IRIS Report 

Source 

Example: IRIS Quick Incident Report (Health) 

AR's Open Number of 

associated AR's with Status=Open 

IRIS AR's Open Number of 

associated AR's with Status=Open 

Issues Open Number of 

associated issues with Status=Open 

IRIS Issues Open Number of 

associated issues with Status=Open 

Are there any 

issues? 

Yes/No IRIS Are there any 

issues? 

Yes/No 

Audit Date Date audit initiated IRIS Audit Date Date audit initiatedContractor NASA Contractor 

which one or more NASA Centers monitor for incident data 

IRIS Contractor NASA Contractor 

which one or more NASA Centers monitor for incident data 

Contract NASA contract 

number 

IRIS Contract NASA contract 

number 

Location All/Indoor/Outdoor IRIS Location All/Indoor/Outdoor Incident Category 

Example: Occurrence or condition of employee concern where there is no injury or only minor injury requiring first aid and no significant equipment/property damage/mission failure (less than $1,000), but which possesses a potential to cause a mishap. 

IRIS Incident 

Category 

Example: Occurrence or condition of employee concern where there is no injury or only minor injury requiring first aid and no significant equipment/property damage/mission failure (less than $1,000), but which possesses a potential to cause a mishap. 

Affiliation State the project, 

company, or Code 

IRIS Affiliation State the project, 

company, or Code 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

84 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

the personnel involved work for. 

the personnel involved work for. 

Beginning Period 

from Indicators screen 

IRIS Beginning 

Period 

from Indicators screen 

Date Type from Indicators 

screen 

IRIS Date Type from Indicators 

screen 

Ending Period from Indicators 

screen 

IRIS Ending Period from Indicators 

screen 

Eye Witness List all personnel 

that were not involved in the incident, but witnesses what happened. 

IRIS Eye Witness List all personnel 

that were not involved in the incident, but witnesses what happened. 

Injury Describe any injuries 

involved in the incident. 

IRIS Injury Describe any injuries 

involved in the incident. 

IRIS File IRIS IRIS File NASA/Contractor? 

 IRIS NASA/Contra

ctor? 

Personnel Involved 

State names of all personnel involved in the incident. 

IRIS Personnel 

Involved 

State names of all personnel involved in the incident. 

Property Damage Indicator 

 IRIS Property 

Damage Indicator 

Vehicle Damage Indicator 

 IRIS Vehicle 

Damage Indicator 

Direct Damage Cost 

 IRIS Direct 

Damage Cost 

Total Direct Damage 

 IRIS Total Direct 

Damage 

Injury Cases IRIS Injury Cases Damage Cases IRIS Damage 

Cases 

Audit From IRIS Audit From Audit To IRIS Audit To Report Output (HTML, Excel, etc.) IRIS Report Output (HTML, Excel, etc.)Report Sections 

 IRIS Report 

Sections 

Accident 

Source 

NASA or other aircraft 

IRIS Accident 

Source 

NASA or other aircraft 

CrtInc Type ISO Audit Metric IRIS CrtInc Type ISO Audit Metric
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

85 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

IndicatorAffected Primary Objective(s) of Mission 

Per mission operations report or equivalent document 

IRIS IndicatorAffected 

Primary Objective(s) of Mission 

Per mission operations report or equivalent document 

Indicator-Close Call 

Occurrence or condition of employee concern where there is no injury or only minor injury requiring first aid and no significant equipment/property damage/mission failure (less than $1,000), but which possesses a potential to cause a mishap. 

IRIS IndicatorClose Call Occurrence or condition of 

employee concern where there is no injury or only minor injury requiring first aid and no significant equipment/property damage/mission failure (less than $1,000), but which possesses a potential to cause a mishap. 

IndicatorConstruction NASA Facilities- related IRIS Indicator- Construction NASA Facilities- related Indicator-False Alarm 

Report later found inaccurate or baseless 

IRIS IndicatorFalse Alarm Report later found inaccurate or 

baseless 

Indicator-High Visibility 

Those particular mishaps or close calls, regardless of the amount of property damage or personnel injury, that the Administrator, AA/OSMA, CD, Director, HQ Ops., or the Center SMA director judges to possess a high degree of programmatic impact or public, 

IRIS Indicator-High 

Visibility 

Those particular mishaps or close calls, regardless of the amount of property damage or personnel injury, that the Administrator, AA/OSMA, CD, Director, HQ Ops., or the Center SMA director judges to possess a high degree of programmatic impact or public, 

Indicator-Injury Involved 

Incident where victim is instantaneously exposed to condition or object causing physical harm. 

IRIS IndicatorInjury 

Involved 

Incident where victim is instantaneously exposed to condition or object causing physical harm. 

IndicatorMission Affected 

Per mission operations report or equivalent document 

IRIS IndicatorMission 

Affected 

Per mission operations report or equivalent document 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

86 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

IndicatorSerious Damage to Aircraft or Space Hardware 

Any hardware that is 

flown on or is a part of an aircraft, experimental flight vehicle, satellite, lighter than air vehicles, unoccupied aerial vehicle, or space transportation system. 

IRIS IndicatorSerious 

Damage to Aircraft or Space Hardware 

Any hardware that is 

flown on or is a part of an aircraft, experimental flight vehicle, satellite, lighter than air vehicles, unoccupied aerial vehicle, or space transportation system. 

IndicatorSerious Damage to Flight or Ground Support Hardware 

Equipment dedicated to flight support or groundto-flight support 

IRIS IndicatorSerious 

Damage to Flight or Ground Support Hardware 

Equipment dedicated to flight support or groundto-flight support 

Indicator-Test Failure 

Damage expected as part of test procedures 

IRIS Indicator-Test 

Failure 

Damage expected as part of test procedures 

IndicatorUnexpected Damage Due to Test Failure 

Damage not expected as part of test procedures 

IRIS IndicatorUnexpected 

Damage Due to Test Failure 

Damage not expected as part of test procedures 

Property Class Real estate holding 

or structure 

IRIS Property 

Class 

Real estate holding or structure 

Substandard Action 

Human action that may have contributed to accident 

IRIS Substandard 

Action 

Human action that may have contributed to accident 

Substandard Condition 

Human condition that may have contributed to accident 

IRIS Substandard 

Condition 

Human condition that may have contributed to accident 

Shift Day shift IRIS Shift Day shift Hospital Local medical 

treatment facility associated with IRIS case 

IRIS Hospital Local medical 

treatment facility associated with IRIS case 

Office of Visit NASA real estate 

holding associated with IRIS case 

IRIS Office of Visit NASA real estate 

holding associated with IRIS case 

Case Type Employee takes 

medical leave due to a non-occupational injury, illness, or scheduled procedure 

IRIS Case Type Employee takes 

medical leave due to a non-occupational injury, illness, or scheduled procedure 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

87 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

Restriction Supervisor-medical 

professional consensus on employee work limitation 

IRIS Restriction Supervisor-medical 

professional consensus on employee work limitation 

Attributable 

Source 

 KSCPR Attributa

ble Source 

Deferred Date KSCPR Deferred 

Date 

Deferred to Event 

 KSCPR Deferred 

to Event 

EICN An end-item control 

number is a sequential identifier contained in implementing organization instructions. 

KSCPR EICN An end-item 

control number is a sequential identifier contained in implementing organization instructions. 

OMRS Affected 

 KSCPR OMRS 

Affected 

Out of Family KSCPR Out of 

Family 

Report Date KSCPR Report 

Date 

Report Group KSCPR Report 

Group 

Report Sequence 

Report number assigned by the design center, contractor, or KSC. 

KSCPR Report 

Sequence 

Report number assigned by the design center, contractor, or KSC. 

Report Type KSCPR Report 

Type 

Work Area Code 

 KSCPR Work 

Area Code 

Hazard Report # 

This number is the alpha/numeric designator associated with the SSP approved HR found in the SSP WebPCASS. 

KSCPR Hazard 

Report # 

This number is the alpha/numeric designator associated with the SSP approved HR found in the SSP 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

88 of 112 

NESC Request No.: 07-031-I

Data Fields 

 (from All 

Systems 

Compared) 

Definition PRACA System CxP Field(s) CxP Field Descriptions IRIS Field(s) IRIS Field Descriptions ISS Field(s) ISS Field Descriptions KSC PR Field(s) KSC PR Field Descriptions Aerospace Field(s) 

Ae

ce 

De

WebPCASS. 

Include Related Parts 

 KSCPR Include 

Related Parts 

Date Isolated Date that the 

problem was isolated. 

KSCPR Date 

Isolated 

Date that the problem was isolated. 

Date/Time Updated 

Date/Time of latest status or update. 

KSCPR Date/Ti

me Updated 

Date/Time of latest status or update. 

Expected Date or Mission of Interim Disposition 

Date or mission that problem was interim dispositioned to. 

KSCPR Expecte

d Date or Mission of Interim Disposition 

Date or mission that problem was interim dispositioned to. 

Latest Interim Disposition Date 

Date that last interim disposition occurred. 

KSCPR Latest 

Interim Disposition Date 

Date that last interim disposition occurred. 

Report Number Report number 

assigned by the design center, contractor, or KSC. 

KSCPR Report 

Number 

Report number assigned by the design center, contractor, or KSC. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

89 of 112 

NESC Request No.: 07-031-I

In 

0006 Only 

0006 

Sort 

Order 

PRACA System(s) Data Field Description Data Type or Source Field in 0006 

 CxP 70068-03 // ISS PRACA 

Db 

DD250? Has the H/W or S/W been accepted by the government? Yes/No * Mandatory 

 KSCPR Deferred Date DATE * Mandatory KSCPR Deferred to Event VARCHAR2(30) * Mandatory CxP 70068-03 Detectable Fault is detectable during pre-operation screening, preventive 

maintenance checks, etc. Pick list includes: Screenable, Nonscreenable 

Pick List *

 ISS PRACA Db Flight Effectivity Status Open/Closed buttons indicating the status. Open/Closed * Mandatory  ISS PRACA Db Flt# * Mandatory  CxP 70068-03 // KSCPR IFA Number If checked yes to IFA, need IFI number here. Generate automatically 

based on what IFI process ends up being. 

String \ 

 CxP 70068-03 In-Flight Anomaly (IFA) In-flight anomalies (IFA’s) are problems that occur from L-5 hours 

during the mission until recovery. (Including its on-orbit/in-space duty cycle). This includes any IFA’s detected during post-mission or postuse analysis. (See Table 4.1.3 for unique In-F 

Yes/No \ 

 ISS PRACA Db Justification Justification for changes to the PR’s Flight Effectivity * Mandatory  ISS PRACA Db Like H/W On-Orbit Indicates if like hardware is already on-orbit. Y/N \  CxP 70068-03 Likelihood Score Determine Likelihood of Problem occurring again (1, 2, 3, 4, or 5) 

based on Qualitative and Quantitative values per CxP 70056 

Pick List * Mandatory 

 ISS PRACA Db Name Name of person responsible to open and close Flight Effectivity Display * Mandatory  CxP 70068-03 Program Approval Required? Is program approval required? Yes/No * Mandatory 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

90 of 112 

NESC Request No.: 07-031-I

In 

0006 Only 

0006 

Sort 

Order 

PRACA System(s) Data Field Description Data Type or Source Field in 0006 

 CxP 70068-03 Project Approval Required? Is project approval required/desired? These approval field(s) depend 

on significance category, risk score, FMEA/CIL criticality code, and Resolution Actions. 

Yes/No * Mandatory 

 CxP 70068-03 Risk Score Automatically calculates the product of Consequence Score times 

Likelihood Score 

Automatically 

Calculated 

* Mandatory 

 CxP 70068-03 // Northrop 

Grumman - F18 FRACAS 

Run time/ Elapsed Time/Cycles For items with Elapsed Time Indicator (ETI) - Time elapsed or number 

of cycles from NASA Acceptance of equipment item to fault/failure/anomaly detection; At the level at which maintenance action is initiated. 

Text Field * Mandatory 

 Northrop Grumman - F18 

FRACAS 

Safety Analysis RHI Risk Hazard Index (RHI) derived by combining the probability of 

occurrence with hazard severity. The RHI forms the basis for judging the acceptability of a risk and to prioritize resources. 

List - Text * Mandatory 

 CxP 70068-03 Safety critical software? Assessment of the software/firmware/complex electronics safety 

functions as defined in NASA-STD-8719.13B, Section 4.1.1, NASA Software Safety Standard. If the system is determined to be safety critical then the software must be evaluated for its contribut 

Yes/No * Mandatory 

 CxP 70068-03 Significance Category Significance of problem based on criteria in volume 1 of the PRACA 

Requirements document 

Pick List * Mandatory 

Aerospace ATR Software build version number Enter the entire name of the software application, including the build 

version number. See table 13 

string (1024) * Mandatory 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

91 of 112 

NESC Request No.: 07-031-I

In 

0006 Only 

0006 

Sort 

Order 

PRACA System(s) Data Field Description Data Type or Source Field in 0006 

 CxP 70068-03 Software Classification Identify classification of the defective software/firmware/complex 

electronics as defined by NPR 7150.2. Refer to the system classification assessment or contact your software assurance representative for assistance in selection. 

Pick List * Mandatory
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

92 of 112 

NESC Request No.: 07-031-I

Appendix B. How-To Procedures 

WEBPCASS/iPRACA Access

Objective 

This document provides users basic instruction for gaining access to WEBPCASS/iPRACA 

resources. 

Procedure

Note: As a prerequisite to using the WEBPCASS/iPRACA Query and Data Export procedure 2, 

users must first have access to WEBPCASS. Users who already have access to WEBPCASS 

may skip this procedure and proceed directly to procedure 2. 

For those requiring access: 

1. Click http://usa1.unitedspacealliance.com/hq/warehouse/ to go to USA’s ADAM Data 

Warehouse, a portal for Space Shuttle Program (SSP) anomaly data. 

2. If you do not currently have access, you must use the ‘REQUEST ACCESS’ option 

under the main menu. When you reach the ‘Request Access to ADAM Data’ screen, look 

down to the section labeled ‘WEBPCASS’ and then click in the far-right column where it 

says “External CURF’. At this point, follow the on-screen instructions. 

Continue to Procedure 2 

 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

93 of 112 

NESC Request No.: 07-031-I

Procedure 2:

Space Shuttle Anomaly Data—Exporting USA’s WEBPCASS/iPRACA Data 

Objective

The purpose of this procedure is to provide users a basic instruction on the performance of 

data query and export from WEBPCASS/iPRACA. This serves as a prerequisite to 

subsequent TechOASIS import filter creation and data analysis work (See TechOASIS 

procedures 3-5). 

Procedure

1. Click http://usa1.unitedspacealliance.com/hq/warehouse/ to go to USA’s ADAM 

Data Warehouse, a portal for Space Shuttle Program (SSP) anomaly data. 

2. Click on the WebPCASS button on the right side. 

o Note 1: WebPCASS = Web based Program Compliance Assurance and Status 

System. 

o Note 2:“WebPCASS is required by, and supports the objectives of, the System 

Integrity Assurance Program (SIAP), NSTS 07700, Volume XI. It was created in 

1987 in response to the Rogers Commission recommendation to provide decision 

makers with readily available, timely, and accurate data. WebPCASS is a 

centralized database system that provides access to data from numerous sources, 

required to accurately analyze and assess the status of Shuttle pre-flight, flight and 

post-flight activities.” 

3. At the next screen, select ‘iPRACA’ from the ‘Nonconformance’ pull-down 

menu. 

o The iPRACA database for contractor-furnished equipment, CFE, at each Center is: 

 KSC = iPRACA 

 JSC = Orbiter CAR (PDSS) 

 MSFC = MSFC PRACA 

o For government furnished-equipment, GFE, use “JSC GFE.” 

4. You should now be at the iPRACA basic search screen. Enter values as shown 

in the following sub-tasks:

Note 4: The following sequence for conducting a basic iPRACA data query and export is 

based on criteria considered to be suitable for many general purpose applications. 

However, at the discretion of the individual user, deviations to the query and export 

criteria may be implemented to suit specific applications as required. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

94 of 112 

NESC Request No.: 07-031-I

a) Under the ‘Document/Issue Information’ area, enter, at a minimum, the issue 

initiated or issue closure date criteria along with applicable on, before, after, or 

between qualifier. 

b) Click the ‘Parts/Related Part Information’ link found near the bottom left of the 

screen and enter part name and/or part number information as applicable. 

c) Near the top-center of screen, click the ‘Execute Search’ button. 

d) Near the top-left area of the display, click the ‘Save All’ button. 

e) Towards the left of the screen, select the ‘User Defined Layout’ tab. 

f) In the ‘Fields to Select’ box, select the following fields and move them to the 

‘Listing Order’ box by clicking the right-hand red arrow: 

o Issue Tab Document Issue Number 

o Issue Tab Issue Detected Date 

o Task Tab Task Description 

o Task Tab Task Summary 

g) Towards the bottom left of this screen, under ‘Report Format’, select ‘Tilde 

Delimited’ from the options. 

h) Click the ‘Generate Report’ button. 

i) Copy and Paste the resulting data (see following note) from the browser screen 

to a new Notepad document saving as a .txt file with a name and location of your 

choosing. 

Note 5: Prior to the copy operation, select data starting immediately after the 

report date/time shown in the format ‘AS OF XX-XXX-XXXX YY:YY:AM/PM’ and 

ending immediately following the last Tilde in the data stream. 

j) After the Notepad file has been created, edit the file to delete the duplicate Tilde 

character, if one occurs, immediately following the words ‘Task Tab Task 

Summary’ located within the first few lines of the report data. 

k) The data is now ready for import to TechOasis given the proper Import 

Filter. 

Continue to Procedure 3 

 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

95 of 112 

NESC Request No.: 07-031-I

Procedure 3: 

TechOasis Import Filter Development and Data Import Procedure

Objective

The purpose of this document is to provide users with a process for creating custom 

import filters in support of work with the TechOASIS Text Mining software tool. 

Note: 

Before proceeding, the user must have generated a proper data file using a 

tilde delimited format due to anomalies that may occur within MS Excel (.xls) 

formatted files. Additionally, use of this procedure is contingent upon the user 

obtaining and installing the Vantage Point TechOASIS software application. 

For details on obtaining the package, please contact Tim Adams, NASA SA-G 

at tim.adams@nasa.gov or by phone at (321) 867-2267). 

Although the following steps first guide the user through conversion and 

subsequent use of an MS Excel format file, this is done for data modeling and 

import filter creation purposes only and any actual data import must take 

place utilizing the original, tilde delimited data. 

AFTER COMPLETION OF THIS PROCESS, PROCEED TO PROCEDURE 4 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

96 of 112 

NESC Request No.: 07-031-I

Procedure:

1. Build the Excel data model as follows: 

a. Launch the MS Excel application and chose ‘Open’ from the ‘File’ menu. 

b. When the Open dialog box appears (see figure 1), click the down arrow at 

the bottom of the dialog box to change the ‘Files of Type’ entry to ‘Text 

Files’ as shown in the figure. 

Figure 1 

c. Once you have configured the dialog box as instructed, use the dialog box 

to locate the tilde delimited file you exported from WEBPCASS. 

d. Once you have located your file, select it and click the ‘Open’ button. 

e. Text Import Wizard step 1 of 3 (see Figure 2) appears next. Click the 

‘Delimited’ button as shown in Figure 2. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

97 of 112 

NESC Request No.: 07-031-I

Figure 2 

f. Now click the ‘Next’ button. 

g. Configure the Text Import Wizard window (step 2 of 3) as shown (see 

Figure 3 as shown on next page). To do this, manually set the delimiters 

options to show a check next to the ‘Other’ option and a ‘Tilde’ is to be 

typed in the adjacent box. Additionally, check the box labeled ‘Treat 

consecutive delimiters as one’. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

98 of 112 

NESC Request No.: 07-031-I

Figure 3 

h. Now click the ‘Next’ button. 

i. Accept the defaults by clicking ‘Finish’ at step 3 of 3 of the Text Import 

Wizard (see Figure 4 on next page). 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

99 of 112 

NESC Request No.: 07-031-I

Figure 4 

j. The resulting Excel worksheet should now appear. 

k. Save the sheet to a location of your choice by using the ‘Save As’ 

command under the ‘File’ menu making sure to select ‘.xls’ as the file type 

in the Save As dialog box. 

2. Create the Import Filter from the Excel Data Model: 

a. Launch TechOasis, select the ‘Import Excel Table’ radio button and then 

click ‘OK’. 

Note: The first time you launch the TechOASIS application, you will be 

prompted for the registration code as provided. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

100 of 112 

NESC Request No.: 07-031-I

b. Locate the Excel you file you wish to import in the ‘Import Data’ dialog 

box and click ‘Open’. 

c. If your Excel workbook contains multiple worksheets, a dialog box may 

appear asking you to select which worksheet contains the desired data. If 

this occurs, select the worksheet from the list and click ‘OK’. 

d. The import process should now begin and during this process, an icon will 

appear showing that data is being processed. 

e. Once data processing has completed, a summary is displayed showing all 

of the column headings and associated information. 

f. Accesses the Import Engine Editor by selecting the ‘Tools’ menu, then the 

‘Import Engine Editor’. 

i. From the ‘File’ menu, select ‘New’ 

ii. Go to the ‘File’ and select ‘Open from Dataset’. 

iii. Double-click on ‘Excel Quick Import’. 

iv. Highlight ‘Excel Quick Import’ in the database window. The fields 

will automatically populate below. 

1. Typical field and database settings can be found in the 

additional figures 4-6 on the following pages. 

2. Use these settings unless a custom export file has been 

generated that is different from that as defined in the 

WEBPCASS/iPRACA query and data export procedure 

located in the TechOASIS server folder. 

v. Right-click on ‘Excel Quick Import’, in the database section, and 

rename the field. This will be the name of your new import filter. 

Then go to the ‘File’ menu and select ‘Save As’ to put the new 

configuration file in the desired directory. 

3. Basic Data Import: 

a. The first time you Import Data, you are presented with a dialog box, where 

you choose which import method to use: the Import Wizard or the Classic 

Interface. Either selection will perform the desired import so choosing 

between the two options is based purely on user preference and 

TechOasis familiarity level. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

101 of 112 

NESC Request No.: 07-031-I

i. From the ‘File’ menu, select ‘Import Raw Data’. 

ii. Click on ‘Select Files’ and when the ‘Open’ dialog box appears, 

select the desired tilde delimited data file that you obtained from 

your data query/export and click ‘Open’. Follow the directions until 

you are asked to select the filter. 

iii. Choose ‘Select New Filter Directory’ and select the import filter 

that you created earlier. 

iv. Continue to open your data file. The data will appear in the correct 

formant and you are now ready to use the program to create lists, 

matrices, etc... 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

102 of 112 

NESC Request No.: 07-031-I

Additional Figures

Figure 5: Typical Database Settings Configuration Window 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

103 of 112 

NESC Request No.: 07-031-I

Figure 6: Typical Field Definition Configuration Window 

 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

104 of 112 

NESC Request No.: 07-031-I

Figure 7: Typical Field Settings Configuration Window 

 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

105 of 112 

NESC Request No.: 07-031-I

TechOASIS Software Basic Hands-On Introductory Resource Guide

Objective

The ultimate purpose of the document is to provide a hands-on guide to the tools and 

utilities found within the TechOASIS suite. 

At this time, the IDAS team is working to further explore and validate the capabilities 

and application of Vantage Point Software’s TechOASIS text mining solution. This 

document’s objective is to provide a high-level guide to resources to assist users in 

applying key tools and utilities within the TechOASIS application. The current version of 

this document serves as a straw-man for development of a detailed hands-on guide and 

quick access reference to support tools. 

Users are encouraged to use t he identified resources as they work through their 

own specific text mining trials and share lessons learned and developed 

methods. With that, text mining becom es in some senses, an open-source 

community based skill. 

For further information or to participate in this informational exchange effort, 

please contact Charles Wilson, SAIC at KSC, (321) 867-4430 or 

charles.a.wilson@nasa.gov. 

AS FOLLOW-ON TO THIS GUIDE, USERS SHOULD REFER TO PROCEDURE 5 

 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

106 of 112 

NESC Request No.: 07-031-I

TechOASIS Identified Resources

Lists & Data Cleaning:

An important stepping stone for data analysis within TechOASIS is what is called list 

view. Please use the section titled ‘List’ and the section titled ‘Tools for Working With 

Lists’ starting on pages 55 and 72 respectively. 

TechOASIS Tools & Utilities:

Preliminary exploration with TechOASIS has revealed that there are multiple tools likely 

to be applicable for use in text mining applications as follows: 

1. Extract Nearby Phrases: The identification of phrases that occur based upon 

their proximity to items in a predefined group. 

For details on using this capability, see the Files section, page 54 of the 

VantagePoint User’s Guide. 

2. Co-Occurrence Matrix: Generates a table that outlines the number of records in 

the dataset where the row and column list items coexist. 

For details on using this capability, see the Co-Occurrence section, page 107 of 

the VantagePoint User’s Guide. 

3. Correlation Matrix: Generates a table that outlines the degree of correlation 

between items that tend to occur in the same record (correlation). 

There are multiple varieties of the Correlation Matrix including Auto-Correlation 

and Cross-Correlation styles. 

For details on using this capability, see the Correlation Matrix section, page 116 

of the VantagePoint User’s Guide. 

4. Factor Matrix: This is a statistical analysis tool that attempts to identify related 

list items in the dataset. 

For details on using this capability, see the Factor Matrix section, page 122 of the 

VantagePoint User’s Guide. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

107 of 112 

NESC Request No.: 07-031-I

TechOASIS Built-In Tutorials and How-To Videos:

TechOASIS has many built in demonstrated tutorials and how-to style videos that can 

be access through the Analyst Guide section under the Help menu. 

See Figure 1 for a screen shot of the Analyst Guide’s contents and point-click access 

instructions.

Analyst Guide: Introductory Demonstrations Section: 

By clicking the ‘Introductory Demonstrations’ link in the Analyst Guide, the user is taken 

to a series of video based tutorials encompassing a variety of subjects including: 

 Basic Maintenance Functions 

 Data Cleanup 

 Data Field Operations 

 Mapping Functions 

 Advanced Topics 

See Figure 2 for a screen shot of the Introductory Demonstrations list of contents. 

Analyst’s Handbook Section:

By clicking the ‘Analyst’s Handbook link, the user is taken to an option screen 

containing links to a series of reference write-ups and mini articles on subjects to 

include: 

 Introductory Comments 

 Data Cleanup 

 Data Analysis 

 General Feature Reference 

See Figure 3 for a screen shot of the Analyst’s Handbook contents screen. 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

108 of 112 

NESC Request No.: 07-031-I

Analyst’s Guide Additional Features:

In addition to the aforementioned contents found within the Analyst’s Guide, there are 

links to the following: 

 Walkthroughs of Common Analysis Techniques 

 A Frequently Asked Question (FAQ) section 

 A Link to a general help section 

 A link to the Vantage Point software website (developer of TechOASIS) 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

109 of 112

NESC Request No.: 07-031-I

Figure 1: Accessing the Analysts Guide 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

110 of 112

NESC Request No.: 07-031-I 

Figure 2: Various Functional Demonstrations (via clicking Introductory Demonstrations) 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

111 of 112

NESC Request No.: 07-031-I 

Figure 3: Contents of the Analyst’s Handbook 

 
NASA Engineering and Safety Center 

Technical Assessment Report

Document #: 

NESC-RP07-031 

Version: 

1.0 

Title:

Problem Reporting Taxonomy and Data Preparation 

Tool Evaluation 

Page #: 

112 of 112

NESC Request No.: 07-031-I 

Data Analysis and Formulation of Conclusions Utilizing TechOASIS

Objective

The purpose of this document is to provide users, who have completed processed data 

through the TechOASIS application, a means to validate their data analysis techniques 

and arrive at valid conclusions. 

As the IDAS team is in its early stage of exploration, these methods and processes 

have not yet been determined. However, we welcome input from the KSC/NASA 

community as we build a knowledge base where methods, techniques, and other 

supporting information can be exchanged in an open forum type environment. 

For further information or to participate in this informational exchange effort, 

please contact Charles Wilson, SAIC at KSC.
REPORT DOCUMENTATION PAGE Form Approved

OMB No. 0704-0188

2. REPORT TYPE 

Technical Memorandum

 4. TITLE AND SUBTITLE

Problem Reporting Taxonomy and Data Preparation Tool Evaluation

5a. CONTRACT NUMBER

 6. AUTHOR(S)

Beil, Robert J.

 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES)

NASA Langley Research Center

Hampton, VA 23681-2199

 9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES)

National Aeronautics and Space Administration

Washington, DC 20546-0001

 8. PERFORMING ORGANIZATION

 REPORT NUMBER

L-19887 NESC-RP-07-031

10. SPONSOR/MONITOR'S ACRONYM(S)

NASA

13. SUPPLEMENTARY NOTES

12. DISTRIBUTION/AVAILABILITY STATEMENT

Unclassified - Unlimited

Subject Category 82 - Documentation and Information Science

Availability: NASA CASI (443) 757-5802

19a. NAME OF RESPONSIBLE PERSON

STI Help Desk (email: help@sti.nasa.gov)

14. ABSTRACT

A member of the NASA Engineering and Safety Center (NESC) Systems Engineering Office (SEO) Technical Discipline 

Team (TDT) requested a SEO-managed activity to perform a gap analysis on the proposed NASA Standard 0006, "Common 

NASA Taxonomy for Problem Reporting, Analysis, and Resolution", and to create an input filter and set of instructions for 

using the data-mining/data-cleansing tool TechOasis1 with Space Shuttle Program (SSP) problem reporting data. The work 

that achieved these objectives and deployment of TechOasis are discussed in this report.

15. SUBJECT TERMS

Data-mining/data-cleansing; NASA Engineering and Safety Center; NASA Standard 0006; Space Shuttle Program; TechOasis

18. NUMBER

 OF 

 PAGES

117

19b. TELEPHONE NUMBER (Include area code)

(443) 757-5802

a. REPORT

U

c. THIS PAGE

U

b. ABSTRACT

U

17. LIMITATION OF 

 ABSTRACT

UU

Prescribed by ANSI Std. Z39.18

Standard Form 298 (Rev. 8-98)

3. DATES COVERED (From - To)

June 2007 - January 2010

5b. GRANT NUMBER

5c. PROGRAM ELEMENT NUMBER

5d. PROJECT NUMBER

5e. TASK NUMBER

5f. WORK UNIT NUMBER

869021.03.07.01.15

11. SPONSOR/MONITOR'S REPORT

 NUMBER(S)

NASA/TM-2010-216704

16. SECURITY CLASSIFICATION OF:

The public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, 

gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this 

collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and 

Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person 

shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS.

1. REPORT DATE (DD-MM-YYYY)

01- 06 - 2010