Search NASA⌕ Search

SEARCH · Search NASA

Results for “DOCUMENTATION”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,567 records · Page 87
All sourcesNASA NTRSDOE OSTI
DOE OSTI2018

Modeling of Lead-210 Data Documents Benefits in Proactively Understanding TENORM Deposition - 18515

Radioactive decay of naturally occurring Radon-222 present in just-produced natural gas can lead to deposition of its radiogenic daughter, Lead-210, and subsequent radiogenic progeny within natural gas handling, treatment, and distribution facilities. Worker safety issues and disposal challenges arise when these accumulate to radiologically problematic activity levels. This is due to the 22.3-year half-life of Lead-210, allowing for multi-decade period of accumulation to occur and to persist, even after facility operations have ceased. Due to the far shorter half-lives of Lead-210 radiogenic progeny, especially that of Polonium-210, secular equilibrium within the Lead-210-Bismuth-210-Polonium-210 decay chain is quickly approached during facility operations and achieved after facility operations end. Lead-210 that accumulates in pipe scale can complicate any subsequent intrusive facility modifications, such as disassembly and dismantlement, potentially exposing workers to adverse radioactivity and impeding recycling and/or disposal of radiologically impacted equipment or other material. Experience has shown it is not strictly the presence of Lead-210 that is problematic but rather its 'unexpected' presence when this Technologically Enhanced Naturally Occurring Radioactive Material (TENORM) is discovered during intrusive work not incorporating radiological health and safety and material handling plans. Conversely, when implementing a program that proactively considers the potential for Lead-210, this form of TENORM simply becomes another 'special waste' that can be safely, efficiently, and effectively addressed during a decommissioning effort, without associated adverse worker exposures, project cost over-runs, and schedule delays. This paper will discuss how proactive radioactive scanning quickly and safely identified Lead-210 and its radiogenic progeny within a natural gas sweetening and compressor station located in northern Montana, a portion of which was undergoing decommissioning, aiding in safe and compliant material handling and recycling. The location of this operation necessitated that the decommissioning program be completed on schedule to prevent weather-related impacts due to the onset of adverse winter conditions. Further, the radioactive data acquired during this project will be shown to provide important insight into historic behavior of Lead-210 in terms of its disposition and its more recent decay. From these data, it became possible to back-model the average activity of Radon-222 within the natural gas being processed during the life of the operation, how the estimated Radon-222 activity within the processed natural gas conformed to measured Radon-222 at various other natural gas fields, and how this information can be leveraged in developing safe and successful plans for future intrusive work at this and companion site operations. This presentation will also note the apparent preferential accumulation of Lead-210 within both rubber-based materials, such as gaskets and seals, and grease-based products found within natural gas flow lines. Thoughts regarding processes that may lead to this finding will be explored. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2024

Guidance on EPAct section 707 Emergency Repair and Restoration Vehicle Exclusions: EPAct State and Alternative Fuel Provider Fleet Program Guidance Document

Section 707 of the Energy Policy Act of 2005 (EPAct 2005) amended section 301(9)(E) of EPAct 1992 by adding to the list of vehicles excluded from the definition of "fleet" a new subcategory of emergency motor vehicles, i.e., "vehicles directly used in the emergency repair of transmission lines and in the restoration of electricity service following power outages, as determined by the Secretary." Like other excluded vehicles, these light-duty vehicles (LDVs) do not count (1) when determining whether a fleet is covered under the U.S. Department of Energy's (DOE) State and Alternative Fuel Provider Fleet Program (Program), and (2) for fleets that are covered under the Program, when calculating annual alternative fuel vehicle (AFV)-acquisition requirements. If AFV models of excluded vehicles are acquired, however, a fleet may count them toward their acquisition requirement by including them in the calculation of the number of AFVs acquired. Exclusion Process.

ADVANCED PROPULSION SYSTEMS,ENERGY PLANNING, POLIC↗
NASA NTRSDate not supplied

Genesis Solar Wind – Capture, Return, Curate and Analyze: Looking Backward and Creating a Timeline

Introduction: In 1997 NASA’S Discovery Program selected the Genesis mission proposal to return solar wind samples to Earth for laboratory analyses. Principal Investigator Donald S. Burnett and the science team defined the purity of collector materials and ability to analyze solar wind composition to the precision required for planetary science. As a small mission, focused on a well-defined science goal, yet needing careful attention to engineering details, the communication among scientists and engineers, nurtured by Don Burnett, was exceptional. Genesis Mission and Curation Legacy: Genesis, as the first U. S. spacecraft to return astromaterial samples since Apollo, not only integrated the mission planning and flight teams, but also the science and sample curation teams during the mission development period. Since Genesis is a sample return mission, the Science Team was essential in certifying the collectors (sample containers for solar atoms). From inception, Genesis established mission funding for returned sample curation. JSC was lead in contamination control during mission preparation, including establishment of an ISO 4 cleanroom facility and use of ultrapure water (UPW) for cleaning flight hardware (and, as it turned out, for cleaning collectors after the mishap). Reliable, fast communication among scientists, engineers and curators at the hands-on level established deep respect among team members and efficient decision-making. JSC’s 50-years of astromaterial sample curation provided experienced sample processors onsite during recovery in Utah (a deep bench for emergency response). Post-recovery curation included iterative collaboration with science sample users to clean or verify cleanliness of samples. The science legacy from Genesis is addressed by Burnett and Jurewicz, this volume. In The Beginning: After Apollo sample return, Burnett and Marcia Neugebauer at JPL began discussing a solar wind sample return, with Neugebauer arguing that separate collection of solar wind regimes was essential science. By 1992 a solar wind sample return mission was presented at a workshop, and by 1994 a mission was proposed named Suess-Urey. The mission was re-proposed under a new name GENESIS and selected in 1997. Susan Niebur captured the Genesis mission history and stories, from high level management documents and from many interviews with participants [2]. Her account lets readers glimpse personality of participants in quotations from interviews. Need and Scope for Detailed Technical Timeline: A timeline constructed from lower level task documents has been initiated to document the resources and skills actually used, as well as task sequence or concurrency. Timelines for high level mission events are captured in two documents [1] [2] and for detailed re-entry events in [3]. A detailed technical timeline for Genesis mission and curation activities will provide data points for lower level tasks, such as ISO 4 curation facility construction time, preparation for nominal sample field recovery, mishap recovery, and UPW expansion. Changes in technology context 1990-2024: Semiconductor technologies were easily accessible in the U.S.A. (1990-1999), and the Genesis team used those resources for cleanroom design and UPW system expansion. Image documentation was changing from film to digital during cleanroom construction and payload cleaning (1997-2001). Engineering design was done using computer aided design proprietary software, making more difficult the archiving of payload configuration and materials. Email of documents, tracked delivery service and virtual meeting capability greatly improved communication efficiency. Information sources – Pre-launch mission preparation: Examples of mission science, engineering and contamination control are collector purity testing, payload design/fabrication and ISO 4 cleanroom construction. Information on timing of these activities comes from facility readiness reviews, management reviews, shipping documents, procurement documents, test reports, travel documents, laboratory logs, Quality Assurance documents, dates on images, participant notebooks and emails. Information sources – Sample return re-entry and field recovery activities: Information comes from event timelines produced by Mid-Air Recovery team, Lockheed team lead notes and from chase video, JPL Quality Assurance. Information also comes from images and logbooks from UTTR cleanroom operations and from curatorial documents. Information sources – Resulting science and sample cleaning processes: Agendas from the annual gatherings of the science team initially trace testing for collector purity/cleanliness, and after sample recovery, include collector cleaning and cleanliness assessment. Post-recovery documents include curatorial orders and procedures, sample allocation documents and LPSC abstracts. Timeline Objectives: A simple spreadsheet timeline with headers DATE, EVENT, PEOPLE, COMMENT, INFORMATION SOURCE has been initiated and currently has over 90 entries. While this is not definitive historical research, it is a quick look at the evolution of Genesis curation with pointers to documents or people with information. Engineers for future missions may find useful points of comparison for development of facilities. References:[1] Genesis Mission Reference Document, (2011) JPL D-62382.[2] Niebur S. M., edited by Brown D. W. (2023) NASA’s Discovery Program: The First 20 Years of Competitive Planetary Exploration, NASA-SP-2023-4238.[3] Genesis Mishap Investigation Board Report, Vol. 1 (July 2005).

solar wind↗
DOE OSTI2019

Methods, media, and systems for detecting attack on a digital processing device

Methods, media, and systems for detecting attack are provided. In some embodiments, the methods include: comparing at least part of a document to a static detection model; determining whether attacking code is included in the document based on the comparison of the document to the static detection model; executing at least part of the document; determining whether attacking code is included in the document based on the execution of the at least part of the document; and if attacking code is determined to be included in the document based on at least one of the comparison of the document to the static detection model and the execution of the at least part of the document, reporting the presence of an attack. In some embodiments, the methods include: selecting a data segment in at least one portion of an electronic document; determining whether the arbitrarily selected data segment can be altered without causing the electronic document to result in an error when processed by a corresponding program; in response to determining that the arbitrarily selected data segment can be altered, arbitrarily altering the data segment in the at least one portion of the electronic document to produce an altered electronic document; and determining whether the corresponding program produces an error state when the altered electronic document is processed by the corresponding program.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Methods, media, and systems for detecting attack on a digital processing device

Methods, media, and systems for detecting attack are provided. In some embodiments, the methods include: comparing at least part of a document to a static detection model; determining whether attacking code is included in the document based on the comparison of the document to the static detection model; executing at least part of the document; determining whether attacking code is included in the document based on the execution of the at least part of the document; and if attacking code is determined to be included in the document based on at least one of the comparison of the document to the static detection model and the execution of the at least part of the document, reporting the presence of an attack. In some embodiments, the methods include: selecting a data segment in at least one portion of an electronic document; determining whether the arbitrarily selected data segment can be altered without causing the electronic document to result in an error when processed by a corresponding program; in response to determining that the arbitrarily selected data segment can be altered, arbitrarily altering the data segment in the at least one portion of the electronic document to produce an altered electronic document; and determining whether the corresponding program produces an error state when the altered electronic document is processed by the corresponding program.

Stolfo, Salvatore J.↗
NASA NTRS2015

SLS-SPEC-159 Cross-Program Design Specification for Natural Environments (DSNE) Revision D

This document is derived from the former National Aeronautics and Space Administration (NASA) Constellation Program (CxP) document CxP 70023, titled "The Design Specification for Natural Environments (DSNE), Revision C." The original document has been modified to represent updated Design Reference Missions (DRMs) for the NASA Exploration Systems Development (ESD) Programs. The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems. These natural environments include the following types of environments: Terrestrial environments at launch, abort, and normal landing sites (winds, temperatures, pressures, surface roughness, sea conditions, etc.); Space environments (ionizing radiation, orbital debris, meteoroids, thermosphere density, plasma, solar, Earth, and lunar-emitted thermal radiation, etc.); Destination environments (Lunar surface and orbital, Mars atmosphere and surface, near Earth asteroids, etc.). Many of the environmental specifications in this document are based on models, data, and environment descriptions contained in the CxP 70044, Constellation Program Natural Environment Definition for Design (NEDD). The NEDD provides additional detailed environment data and model descriptions to support analytical studies for ESD Programs. For background information on specific environments and their effects on spacecraft design and operations, the environment models, and the data used to generate the specifications contained in the DSNE, the reader is referred to the NEDD paragraphs listed in each section of the DSNE. Also, most of the environmental specifications in this document are tied specifically to the ESD DRMs in ESD-10012, Revision B, Exploration Systems Development Concept of Operations (ConOps). Coordination between these environment specifications and the DRMs must be maintained. This document should be compatible with the current ESD DRMs, but updates to the mission definitions and variations in interpretation may require adjustments to the environment specifications.

Roberts, Barry C.↗
DOE OSTI2017

Launching a Research Archive for FUSRAP Site Records - 17057

The US Department of Energy Office of Legacy Management (LM) maintains a broad set of Formerly Utilized Sites Remedial Action Program (FUSRAP) document collections. The LM FUSRAP technical staff regularly needs access to documents contained in these record collections. The majority of the FUSRAP records are maintained in a large paper-based collection in the LM records storage facility. These records cover the period prior to 1997 in which DOE was responsible for the remediation efforts of FUSRAP sites. Other FUSRAP records are maintained as PDF files in LM's record keeping system. LM also maintains FUSRAP information in reference repositories in SharePoint directories and on network drives. The reference collection allows LM to keep abreast of active site remediation by the U.S. Army Corps of Engineers (USACE) since 1997. Searching these FUSRAP collections in its current arrangement can be time-consuming and can result in incomplete searches. In response, LM proactively developed the FUSRAP Document Information System (FDIS) to provide a rapid, single-point search and retrieval system to provide real-time access to reference copies of FUSRAP documents. Each entry in FDIS includes metadata listing the FUSRAP site, document title, date, source collection, and pertinent keywords. More significant entries (e.g., certification documents, site characterization reports, waste manifests) include a PDF scan of the entire document. Each PDF file is processed using an advanced optical character recognition (OCR) tool. The first significant content added to FDIS is 45,000 entries documenting remediation work performed primarily in the early 1990's by Bechtel National, Inc. With the entries in FDIS, technical staff will be able to search the collection by site, category and keyword to quickly locate precise required content. LM records staff are also adding records that document remediation and monitoring work at FUSRAP sites where cleanup activities are considered complete. Documents for completed FUSRAP sites will be processed before documents for sites currently being remediated. In the future, FDIS will be populated with information about FUSRAP sites with ongoing remediation work as they are released to LM stewardship. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2018

Parametric Studies for Plutonium Metal-Water Mixtures in Arrays of 6-Inch Columns

A parametric study for arrays of 6-inch diameter tank columns was performed in order to assist in the practical development of limits for plutonium solution operations. This technical document utilizes approaches taken in NCS-TECH-10-009 [Reference 1]. While this technical document expands on areas where the authors feel appropriate, it does not attempt to recreate all parts of the existing technical document. This technical document is intended to be used in conjunction with the previous technical document. The results reported in this technical document may be used to support facility-specific program documents or individual Criticality Safety Evaluation Documents (CSEDs). This technical document does not derive any specific requirements. Caution should be taken when applying these results; it is the criticality safety analyst's responsibility, if he/she chooses to utilize this technical document, to properly assess the applicability of the results presented herein for his/her application.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗
NASA NTRS1987

United States Space Station technical and programmatic interfaces

This paper describes the design of the U.S. Space Station and explains the control factors used for internal and external interfaces among the various government and contractor participants. It discusses the documentation of the U.S. Space Station Program including the Program Approval Document (PAD), the Program Plans (PPs), the Program Requirements Document (PRD), the Program Definition and Requirements Document (PDRD), the Level III project plans, and the Level III project design requirements documents. It discusses the relationship of Space Station documentation to the international Memoranda of Understanding (MOUs) and the Joint PP, PRD, and PDRD, the interrelationship of the Architectural Control Documents (ACDs), the Baseline Control Document (BCD), and the Interface Requirement Documents (IRDs) and Interface Control Documents (ICDs). Also included are the controlling functions of the various NASA and contractor participants and the international partners.

Carlisle, Richard F.↗
NASA NTRS2023

Commercial Smallsat Data Acquisition Program: Airbus U.S. Synthetic Aperture Radar Quality Assessment Summary

Quality assessment of the Airbus X-band Synthetic Aperture Radar (SAR) satellite products was conducted by the Commercial Smallsat Data Acquisition (CSDA) program’s radar subject matter experts, following the Joint NASA/ESA (European Space Agency) assessment draft guidelines. All three Airbus SAR spacecraft (TerraSAR-X, TanDEM-X, and PAZ) are based on the TerraSAR-X platform, and each have an active phased array antenna that is 4.8 x 0.7 m in the along-track and cross-track dimensions, respectively. TerraSAR-X and TanDEM-X are in a helical orbit, creating a bistatic imaging geometry, in addition to being capable of independent monostatic observations. The PAZ mission follows TerraSAR-X and TanDEM-X in the same 11-day orbit with a 5.5-day lag. TerraSAR-X and TanDEM-X are designed, developed, and operated through a Public-Private Partnership, while PAZ is a dual-use mission (civil and defense agencies), funded and owned by the Spanish Ministry of Defense and managed by Hisdesat (Hisdesat Servicios Estratégicos, S.A.), a Spanish private communications company. The assessment presented in this document is divided into two main parts: documentation review and the assessment of test datasets. The documentation review in sections 2.1 through 2.4 includes the assessment of the Airbus documentation provided to the CSDA evaluation team. The grading of these documents is given in columns 1-4 of the maturity matrix shown in section 1.1. Section 2.5 summarizes the evaluation performed by NASA using the data purchased through the CSDA program. The grading for this is given in the last column of the maturity matrix. Section 3 provides more detailed explanations on the methods and the results of the data analysis performed by NASA. Only the documents provided by Airbus for the evaluation were considered for the review. Additional documentation with more detailed description of the calibration and validation procedures may be available online but were not considered for this evaluation. The product information provided in the available documentation (RD-1, RD-2) and the product metadata together provided adequate information to work with the data. The product details in the metadata included the required information to work with the data in the common XML file format. Metrological traceability documentation was not provided to CSDA. All relevant characterization of the SAR system and data were provided, and the metadata include all relevant ancillary information. Documentation provided to CSDA included limited pre-flight and post-launch calibration information.

Batuhan Osmanoglu↗
DOE OSTI2018

Central and Eastern North America Ground-Motion Characterization (NGA-East)

This document is the final project report of the Next Generation Attenuation for Central and Eastern North America (CENA) project (NGA-East). The NGA-East objective was to develop a new ground-motion characterization (GMC) model for the CENA region. The GMC model consists of a set of new ground-motion models (GMMs) for median and standard deviation of ground motions and their associated weights to be used with logic-trees in probabilistic seismic hazard analyses (PSHA). NGA-East is a large multidisciplinary project coordinated by the Pacific Earthquake Engineering Research Center (PEER), at the University of California. The project has two components: (1) a set of scientific research tasks, and (2) a model-building component following the framework of the “Seismic Senior Hazard Analysis Committee (SSHAC) Level 3” (Budnitz et al. 1997; NRC 2012). Component (2) is built on the scientific results of component (1) of the NGA-East project. This report documents the tasks under component (2) of the project. Under component (1) of NGA-East, several scientific issues were addressed, including: (a) development of a new database of ground motion data recorded in CENA; (b) development of a regionalized ground-motion map for CENA, (c) definition of the reference site condition; (d) simulations of ground motions based on different methodologies; and (e) development of numerous GMMs for CENA. The scientific tasks of NGA-East were all documented as a series of PEER reports. The scope of component (2) of NGA-East was to develop the complete GMC. This component was designed as a SSHAC Level 3 study with the goal of capturing the ground motions’ center, body, and range of the technically defensible interpretations in light of the available data and models. The SSHAC process involves four key tasks: evaluation, integration, formal review by the Participatory Peer Review Panel (PPRP), and documentation (this report). Key tasks documented in this report include review and evaluation of the empirical groundmotion database, the regionalization of ground motions, and screening sets of candidate GMMs. These are followed by the development of new median and standard deviation GMMs, the development of new analyses tools for quantifying the epistemic uncertainty in ground motions, and the documentation of implementation guidelines of the complete GMC for PSHA computations. Appendices include further documentation of the relevant SSHAC process and additional supporting technical documentation of numerous sensitivity analyses results. The PEER reports documenting component (1) of NGA-East are also considered “attachments” to the current report and are all available online on the PEER website (https://peer.berkeley.edu/). The final NGA-East GMC model includes a set of 17 GMMs defined for 24 ground-motion intensity measures, applicable to CENA in the moment magnitude range of 4.0 to 8.2 and covering distances up to 1500 km. Standard deviation models are also provided for site-specific analysis (single-station standard deviation) and for general PSHA applications (ergodic standard deviation). Adjustment factors are provided for consideration of source-depth effects and hanging-wall effects, as well as for hazard computations at sites in the Gulf Coast region.

58 GEOSCIENCES↗
NASA NTRS2009

Software Tools Streamline Project Management

Three innovative software inventions from Ames Research Center (NETMARK, Program Management Tool, and Query-Based Document Management) are finding their way into NASA missions as well as industry applications. The first, NETMARK, is a program that enables integrated searching of data stored in a variety of databases and documents, meaning that users no longer have to look in several places for related information. NETMARK allows users to search and query information across all of these sources in one step. This cross-cutting capability in information analysis has exponentially reduced the amount of time needed to mine data from days or weeks to mere seconds. NETMARK has been used widely throughout NASA, enabling this automatic integration of information across many documents and databases. NASA projects that use NETMARK include the internal reporting system and project performance dashboard, Erasmus, NASA s enterprise management tool, which enhances organizational collaboration and information sharing through document routing and review; the Integrated Financial Management Program; International Space Station Knowledge Management; Mishap and Anomaly Information Reporting System; and management of the Mars Exploration Rovers. Approximately $1 billion worth of NASA s projects are currently managed using Program Management Tool (PMT), which is based on NETMARK. PMT is a comprehensive, Web-enabled application tool used to assist program and project managers within NASA enterprises in monitoring, disseminating, and tracking the progress of program and project milestones and other relevant resources. The PMT consists of an integrated knowledge repository built upon advanced enterprise-wide database integration techniques and the latest Web-enabled technologies. The current system is in a pilot operational mode allowing users to automatically manage, track, define, update, and view customizable milestone objectives and goals. The third software invention, Query-Based Document Management (QBDM) is a tool that enables content or context searches, either simple or hierarchical, across a variety of databases. The system enables users to specify notification subscriptions where they associate "contexts of interest" and "events of interest" to one or more documents or collection(s) of documents. Based on these subscriptions, users receive notification when the events of interest occur within the contexts of interest for associated document or collection(s) of documents. Users can also associate at least one notification time as part of the notification subscription, with at least one option for the time period of notifications.

Source record↗
NASA NTRS2018

Validation & Verification of Electrical Components B2 Test Facility

The research focus of this project is to assist in the closure of Measurement, Monitoring and Control System (MMCS) and other electrical requirements in support of the B2 Space Launch System (SLS) Core Stage Green Run Test Project. Alongside this goal I am to understand project management tools to analyze and control activities/tasks associated with those items. The project I am working on will assist electrical engineers in developing and or identifying closure rationale for the MMCS and electrical requirements. Also as serving the role of a training project manager, I am to develop and maintain a method for tracking progress with estimate completion dates specifically identifying those items during this performance window. The methods I used in order to perform the research consisted of worddocuments, excel sheets, and pdf documents needed for review. For example, documents consisted of: a SLS Core Stage Green Run Facility Requirement Document (FRD) identifying the SSC MMCS and electrical requirements, a Stage Controller to SSC Interface Control Document (ICD) identifying the SSC requirements, and the B2 SLS Core Stage Green Run Test project System Requirements Document (SRD) which identifies the MMCS and electrical requirements. The files were sent to me by both mentors, Mr. Barry Robinson and Ms. Dawn Davis. Overall, the review process for the word documents and excel spreadsheets proved to be successful. The data for the electrical components were accurate and were consistent with the original recorded data. However, the consistency with the pdf documents did not follow up all the way. Attention to this mistake was made and further revisions were done in order for the data to agree with each other. Furthermore, an itinerary was designed using Microsoft Outlook in order to track progress with estimated completion dates. This project contributes to NASA/Center Missions and Goals through the Waterfall Model. The Waterfall Model is a linear system used for engineering design. In the Waterfall Model, the fourth step is Verification and Validation. This involves installation, testing, and debugging of the B2 SLS Core Stage electrical components. For the SLS Core Stage Green Run Test Project, each requirement contained in this approved requirements set will have at least one Verification Item (VI) assigned to it. During the design phase, VIs will mostly consist of Analysis or Inspection types. Design phase VIs and closure information will be documented in Dynamics Data Management System (DDMS) in the form of analysis reports and design documentation.

Bastian, Tyler↗
NASA NTRSDate not supplied

Knowledge Discovery for Early Failure Assessment of Complex Engineered Systems Using Natural Language Processing

Emerging complex engineered systems may have unexpected safety issues due to novel operational environments, increasing autonomy, human-machine interaction, and other factors. To prevent failures in operation or testing that necessitate costly redesign, it is desirable to predict likely failure modes early in the design process. Information about past engineering failures in natural language format presents one possible solution by enabling the retrieval of information that can inform new designs. However, identifying documents containing usable information and extracting the required information can be prohibitively time-consuming when implemented at scale. In this research, an automated natural language processing (NLP) framework is proposed to discover relevant knowledge from documents containing failure-related design information. The framework is applied to NASA’s Lessons Learned Information System (LLIS),which is publicly available. Documents containing usable information are filtered using two different NLP-based models. Next, from the identified usable documents, a failure taxonomy is extracted using a partitioned hierarchical topic modeling approach. Partitions of the document describe different sections of the failure taxonomy – i.e., failure, cause of failure, and recommendations – as indicated by the structure of the original document. The extracted failure taxonomy can be leveraged in early design failure assessment methods. Moreover, the framework can be used to identify documents containing usable failure-related design information from other databases and extract relevant information from these documents.

Documentation and Information Science↗
NASA NTRSDate not supplied

Knowledge Discovery for Early Failure Assessment of Complex Engineered Systems Using Natural Language Processing

Emerging complex engineered systems may have unexpected safety issues due to novel operational environments, increasing autonomy, human-machine interaction, and other factors. To prevent failures in operation or testing that necessitate costly redesign, it is desirable to predict likely failure modes early in the design process. Information about past engineering failures in natural language format presents one possible solution by enabling the retrieval of information that can inform new designs. However, identifying documents containing usable information and extracting the required information can be prohibitively time-consuming when implemented at scale. In this research, an automated natural language processing (NLP) framework is proposed to discover relevant knowledge from documents containing failure-related design information. The framework is applied to NASA’s Lessons Learned Information System (LLIS),which is publicly available. Documents containing usable information are filtered using two different NLP-based models. Next, from the identified usable documents, a failure taxonomy is extracted using a partitioned hierarchical topic modeling approach. Partitions of the document describe different sections of the failure taxonomy – i.e., failure, cause of failure, and recommendations – as indicated by the structure of the original document. The extracted failure taxonomy can be leveraged in early design failure assessment methods. Moreover, the framework can be used to identify documents containing usable failure-related design information from other databases and extract relevant information from these documents.

Documentation and Information Science↗