Search NASASearch

SEARCH · Search NASA

Results for “ICD”

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 55 records · Page 3

Media independent interface

The work done on the Media Independent Interface (MII) Interface Control Document (ICD) program is described and recommendations based on it were made. Explanations and rationale for the content of the ICD itself are presented.

Source record

Medical impact analysis for the Space Station

In this study, Space Station medical care priorities were determined by a medical impact analysis of two analog populations, U.S. Army and U.S. Navy personnel. Diseases and injuries in the International Classification of Disease, 9th Revision, Clinical Modification (ICD-9-CM) were ranked, using a Medical Impact Score (MIS) combining modified incidence rate and a function of disease outcome. The validity of the analysis method was tested by measuring rank order correlation between the two analog populations. Despite virtually identical age and sex distributions, Army and Navy incidence rates differed significantly for half of the ICD-9-CM categories, p less than 0.05. Disability rates differed for 76 percent, p less than 0.05. Nevertheless, Army and Navy MIS rank orders for categories and sections were not significantly different, p less than 0.001. In critical ways, the Space Station will be a safer environment than earth. Cardiac events, musculoskeletal injuries, affective psychoses, and renal calculi were among the highest scoring categories.

Nelson, Brent D.

Space station automation of common module power management and distribution, volume 2

The new Space Station Module Power Management and Distribution System (SSM/PMAD) testbed automation system is described. The subjects discussed include testbed 120 volt dc star bus configuration and operation, SSM/PMAD automation system architecture, fault recovery and management expert system (FRAMES) rules english representation, the SSM/PMAD user interface, and the SSM/PMAD future direction. Several appendices are presented and include the following: SSM/PMAD interface user manual version 1.0, SSM/PMAD lowest level processor (LLP) reference, SSM/PMAD technical reference version 1.0, SSM/PMAD LLP visual control logic representation's (VCLR's), SSM/PMAD LLP/FRAMES interface control document (ICD) , and SSM/PMAD LLP switchgear interface controller (SIC) ICD.

Ashworth, B.

Aquarius's Instrument Science Data System (ISDS) Automated to Acquire, Process, Trend Data and Produce Radiometric System Assessment Reports

The Aquarius Radiometer, a subsystem of the Aquarius Instrument required a data acquisition ground system to support calibration and radiometer performance assessment. To support calibration and compose performance assessments, we developed an automated system which uploaded raw data to a ftp server and saved raw and processed data to a database. This paper details the overall functionalities of the Aquarius Instrument Science Data System (ISDS) and the individual electrical ground support equipment (EGSE) which produced data files that were infused into the ISDS. Real time EGSEs include an ICDS Simulator, Calibration GSE, Labview controlled power supply, and a chamber data acquisition system. ICDS Simulator serves as a test conductor primary workstation, collecting radiometer housekeeping (HK) and science data and passing commands and HK telemetry collection request to the radiometer. Calibration GSE (Radiometer Active Test Source) provides source choice from multiple targets for the radiometer external calibration. Power Supply GSE, controlled by labview, provides real time voltage and current monitoring of the radiometer. And finally the chamber data acquisition system produces data reflecting chamber vacuum pressure, thermistor temperatures, AVG and watts. Each GSE system produce text based data files every two to six minutes and automatically copies the data files to the Central Archiver PC. The Archiver PC stores the data files, schedules automated uploads of these files to an external FTP server, and accepts request to copy all data files to the ISDS for offline data processing and analysis. Aquarius Radiometer ISDS contains PHP and MATLab programs to parse, process and save all data to a MySQL database. Analysis tools (MATLab programs) in the ISDS system are capable of displaying radiometer science, telemetry and auxiliary data in near real time as well as performing data analysis and producing automated performance assessment reports of the Aquarius Radiometer.

Source record

Phased Array Noise Source Localization Measurements Made on a Williams International FJ44 Engine

A 48-microphone planar phased array system was used to acquire noise source localization data on a full-scale Williams International FJ44 turbofan engine. Data were acquired with the array at three different locations relative to the engine, two on the side and one in front of the engine. At the two side locations the planar microphone array was parallel to the engine centerline; at the front location the array was perpendicular to the engine centerline. At each of the three locations, data were acquired at eleven different engine operating conditions ranging from engine idle to maximum (take off) speed. Data obtained with the array off to the side of the engine were spatially filtered to separate the inlet and nozzle noise. Tones occurring in the inlet and nozzle spectra were traced to the low and high speed spools within the engine. The phased array data indicate that the Inflow Control Device (ICD) used during this test was not acoustically transparent; instead, some of the noise emanating from the inlet reflected off of the inlet lip of the ICD. This reflection is a source of error for far field noise measurements made during the test. The data also indicate that a total temperature rake in the inlet of the engine is a source of fan noise.

Podboy, Gary G.

J-2X Turbopump Cavitation Diagnostics

The J-2X is the upper stage engine currently being designed by Pratt & Whitney Rocketdyne (PWR) for the Ares I Crew Launch Vehicle (CLV). Propellant supply requirements for the J-2X are defined by the Ares Upper Stage to J-2X Interface Control Document (ICD). Supply conditions outside ICD defined start or run boxes can induce turbopump cavitation leading to interruption of J-2X propellant flow during hot fire operation. In severe cases, cavitation can lead to uncontained engine failure with the potential to cause a vehicle catastrophic event. Turbopump and engine system performance models supported by system design information and test data are required to predict existence, severity, and consequences of a cavitation event. A cavitation model for each of the J-2X fuel and oxidizer turbopumps was developed using data from pump water flow test facilities at Pratt & Whitney Rocketdyne (PWR) and Marshall Space Flight Center (MSFC) together with data from Powerpack 1A testing at Stennis Space Center (SSC) and from heritage systems. These component models were implemented within the PWR J-2X Real Time Model (RTM) to provide a foundation for predicting system level effects following turbopump cavitation. The RTM serves as a general failure simulation platform supporting estimation of J-2X redline system effectiveness. A study to compare cavitation induced conditions with component level structural limit thresholds throughout the engine was performed using the RTM. Results provided insight into system level turbopump cavitation effects and redline system effectiveness in preventing structural limit violations. A need to better understand structural limits and redline system failure mitigation potential in the event of fuel side cavitation was indicated. This paper examines study results, efforts to mature J-2X turbopump cavitation models and structural limits, and issues with engine redline detection of cavitation and the use of vehicle-side abort triggers to augment the engine redline system.

Santi, I. Michael

Lessons Learned on Implementing Fault Detection, Isolation, and Recovery (FDIR) in a Ground Launch Environment

This paper's main purpose is to detail issues and lessons learned regarding designing, integrating, and implementing Fault Detection Isolation and Recovery (FDIR) for Constellation Exploration Program (CxP) Ground Operations at Kennedy Space Center (KSC). Part of the0 overall implementation of National Aeronautics and Space Administration's (NASA's) CxP, FDIR is being implemented in three main components of the program (Ares, Orion, and Ground Operations/Processing). While not initially part of the design baseline for the CxP Ground Operations, NASA felt that FDIR is important enough to develop, that NASA's Exploration Systems Mission Directorate's (ESMD's) Exploration Technology Development Program (ETDP) initiated a task for it under their Integrated System Health Management (ISHM) research area. This task, referred to as the FDIIR project, is a multi-year multi-center effort. The primary purpose of the FDIR project is to develop a prototype and pathway upon which Fault Detection and Isolation (FDI) may be transitioned into the Ground Operations baseline. Currently, Qualtech Systems Inc (QSI) Commercial Off The Shelf (COTS) software products Testability Engineering and Maintenance System (TEAMS) Designer and TEAMS RDS/RT are being utilized in the implementation of FDI within the FDIR project. The TEAMS Designer COTS software product is being utilized to model the system with Functional Fault Models (FFMs). A limited set of systems in Ground Operations are being modeled by the FDIR project, and the entire Ares Launch Vehicle is being modeled under the Functional Fault Analysis (FFA) project at Marshall Space Flight Center (MSFC). Integration of the Ares FFMs and the Ground Processing FFMs is being done under the FDIR project also utilizing the TEAMS Designer COTS software product. One of the most significant challenges related to integration is to ensure that FFMs developed by different organizations can be integrated easily and without errors. Software Interface Control Documents (ICDs) for the FFMs and their usage will be addressed as the solution to this issue. In particular, the advantages and disadvantages of these ICDs across physically separate development groups will be delineated.

Ferrell, Bob A.

The Rapid Response Radiation Survey (R3S) Mission Using the HiSat Conformal Satellite Architecture

The Rapid Response Radiation Survey (R3S) experiment, designed as a quick turnaround mission to make radiation measurements in Low Earth Orbit (LEO), will fly as a hosted payload in partnership with NovaWurks using their Hyper-integrated Satlet (HISat) architecture. The need for the mission arises as the Nowcast of Atmospheric Ionization Radiation for Aviation Safety (NAIRAS) model moves from a research effort into an operational radiation assessment tool. Currently, airline professionals are the second largest demographic of radiation workers and to date their radiation exposure is undocumented in the USA. The NAIRAS model seeks to fill this information gap. The data collected by R3S, in addition to the complementary data from a NASA Langley Research Center (LaRC) atmospheric balloon mission entitled Radiation Dosimetry Experiment (RaD-X), will validate exposure prediction capabilities of NAIRAS. The R3S mission collects total dose and radiation spectrum measurements using a Teledyne μDosimeter and a Liulin-6SA2 LED spectrometer. These two radiation sensors provide a cross correlated radiometric measurement in combination with the Honeywell HMR2300 Smart Digital Magnetometer. The magnetometer assesses the Earth's magnetic field in the LEO environment and allows radiation dose to be mapped as a function of the Earth's magnetic shielding. R3S is also unique in that the radiation sensors will be exposed on the outer surface of the spacecraft, possibly making this the first measurements of the LEO radiation environment with bare sensors. Viability of R3S as an extremely fast turnaround mission is due, in part, to the nature of the robust, well-defined interfaces of the conformal satellite HiSat Architecture. The HiSat architecture, which was developed with the support of the Defense Advanced Research Projects Agency's (DARPA's) Phoenix Program, enabled the R3S system to advance from the first concept to delivery of preliminary design review (PDR) level documents in 29 calendar days. The architecture allows for interface complexities between the specific devices and the satellite bus to be resolved in a standardized interface control document (ICD). The ICD provided a readymade framework to interface to the modular satellite bus. This modularity allowed for approximately 90% of the R3S system to be designed and fabricated in two months without constraint of the hosting satellite's development cycle. This paper discusses the development of the R3S experiment as made possible by use of the HiSat architecture. The system design and operational modes of the experiment are described, as well as the experiment interfaces to the HiSat satellite via the user defined adapter (UDA) provided by NovaWurks. This paper outlines the steps taken by the project to execute the R3S mission in the 4 months of design, build, and test. Additionally portrayed is the ground work done at LaRC to posture the organization for a fast response and the process by which the opportunity was identified as aligning with key strategic goals. Finally, a description of the engineering process is provided, including the use of facilitated rapid/concurrent engineering sessions, the associated documentation, and the review process employed.

Miller, Nathanael A.

Predictive Modeling for Differential Diagnosis and Mortality Risk Assessment

The prevalence of electronic health record (EHR) systems has brought prodigious biomedical informatics opportunity. Automated machine learning methods can effectively utilize such data and have become common tools for healthcare predictive modeling. Researches in medical informatics have explored the potential of deep learning and classical models in emergent care scenarios. In particular, predicting differential diagnoses for admissions have proven useful in decreasing unnecessary lab tests and improving inpatient triage decision-making. Moreover, identification of high-risk patients for in-hospital mortality is vitally important to maximize allocation of medical resources.The Medical Information Mart for Intensive Care (MIMIC-III) database, containing de-identified critical care inpatient was used in our study. This data set captures hospital patient laboratory measurements, pharmacologic prescriptions, diagnostic data and procedure event recordings. When considering adult patients and discounting admissions with ICU length of stay less than 24 hours, there were 37,787 unique admissions and 30,414 total patients. We examined the top 25 most prevalent ICD-9 group-level disease specificities in MIMIC-III using a multi-label classification model. In-hospital mortality was modeled as binary classification with 4,155 (13%) adult patients that expired, of which 3,138 (75.5%) were in the ICU setting. The metrics AUC, F1 score, sensitivity and specificity values calculated for each disease label measured prediction performance.The usage of ICD-9 group codes reduced feature dimension from 14,567 to 942 and greatly improved distribution of patient diagnostic categories. Disease temporal patterns were captured by considering the most frequently sampled 6 vital signs and 13 laboratory values. Missing data were imputed at each time-stamp. Time-series raw hourly average values were converted into 5 summary features (mean, standard deviation, number of observations, min & max values). Patient demographic variables such as age, gender, marital status and ethnicity were also factored into the modeling. Choi et al showed that contextual embedding of medical data, diagnostic and procedural codes alone can predict future diagnoses with sensitivity as high as 0.79. We utilized an embedding technique called word2vec which allowed sparse representations of medical history to be transformed into dense word vectors. The mappings captured contextual information by treating each admission as a sentence and learning the most likely neighboring words in a sliding window fashion. Binary and multi-label classification was achieved via collapse models, which do not consider temporal information, as well as recurrent neural networks with regularization, Softmax output layer activation together with categorical cross-entropy as the loss function.

US Army collaboration

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy that is ubiquitous throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and Concepts of Operations (ConOps) for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, ConOps, and interface control documents (ICDs), in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module (i.e. ECLSS). A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM) to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design – GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1) to implement autonomy at the VSM, MSM, and SM levels; (2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with the VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1) Orion as visiting vehicle registers with VSM; (2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Fernando Figueroa

Future ATM Concepts Evaluation Tool (FACET) Interface Control Document

This Interface Control Document (ICD) documents the airspace adaptation and air traffic inputs of NASA's Future ATM Concepts and Evaluation Tool (FACET). Its intended audience is the project manager, project team, development team, and stakeholders interested in interfacing with the system. FACET equips Air Traffic Management (ATM) researchers and service providers with a way to explore, develop and evaluate advanced air transportation concepts before they are field-tested and eventually deployed. FACET is a flexible software tool that is capable of quickly generating and analyzing thousands of aircraft trajectories. It provides researchers with a simulation environment for preliminary testing of advanced ATM concepts. Using aircraft performance profiles, airspace models, weather data, and flight schedules, the tool models trajectories for the climb, cruise, and descent phases of flight for each type of aircraft. An advanced graphical interface displays traffic patterns in two and three dimensions, under various current and projected conditions for specific airspace regions or over the entire continental United States. The system is able to simulate a full day's dynamic national airspace system (NAS) operations, model system uncertainty, measure the impact of different decision-makers in the NAS, and provide analysis of the results in graphical form, including sector, airport, fix, and airway usage statistics. NASA researchers test and analyze the system-wide impact of new traffic flow management algorithms under anticipated air traffic growth projections on the nation's air traffic system. In addition to modeling the airspace system for NASA research, FACET has also successfully transitioned into a valuable tool for operational use. Federal Aviation Administration (FAA) traffic flow managers and commercial airline dispatchers have used FACET technology for real-time operations planning. FACET integrates live air traffic data from FAA radar systems and weather data from the National Weather Service to summarize NAS performance. This information allows system operators to reroute flights around congested airspace and severe weather to maintain safety and minimize delay. FACET also supports the planning and post-operational evaluation of reroute strategies at the national level to maximize system efficiency. For the commercial airline passenger, strategic planning with FACET can result in fewer flight delays and cancellations. The performance capabilities of FACET are largely due to its architecture, which strikes a balance between flexibility and fidelity. FACET is capable of modeling the airspace operations for the continental United States, processing thousands of aircraft on a single computer. FACET was written in Java and C, enabling the portability of its software to a variety of operating systems. In addition, FACET was designed with a modular software architecture to facilitate rapid prototyping of diverse ATM concepts. Several advanced ATM concepts have already been implemented in FACET, including aircraft self-separation, prediction of aircraft demand and sector congestion, system-wide impact assessment of traffic flow management constraints, and wind-optimal routing.

FACET

Decoding substance use disorder severity from clinical notes using a large language model

Substance use disorder (SUD) poses a major concern due to its detrimental effects on health and society. SUD identification and treatment depend on a variety of factors such as severity, co-determinants (e.g., withdrawal symptoms), and social determinants of health. Existing diagnostic coding systems used by insurance providers, like the International Classification of Diseases (ICD-10), lack granularity for certain diagnoses, but American clinicians will add this granularity (as that found within the Diagnostic and Statistical Manual of Mental Disorders classification or DSM-5) as supplemental unstructured text in clinical notes. Traditional natural language processing (NLP) methods face limitations in accurately parsing such diverse clinical language. Large language models (LLMs) offer promise in overcoming these challenges by adapting to diverse language patterns. This study investigates the application of LLMs for extracting severity-related information for various SUD diagnoses from clinical notes. We propose a workflow employing zero-shot learning of LLMs with carefully crafted prompts and post-processing techniques. Through experimentation with Flan-T5, an open-source LLM, we demonstrate its superior recall compared to the rule-based approach. Focusing on 11 categories of SUD diagnoses, we show the effectiveness of LLMs in extracting severity information, contributing to improved risk assessment and treatment planning for SUD patients.

60 APPLIED LIFE SCIENCES

Design study of RL10 derivatives. Volume 3, part 1: Preliminary interface control document

The Interface Control Document contains engine information necessary for installation of the baseline RL10 Derivative engines in the Space Tug vehicle. The ICD presents a description of the baseline engines and their operating characteristics, mass and load characteristics, and environmental criteria. The document defines the engine/vehicle mechanical, electrical, fluid and pneumatic interface requirements.

Adams, A.

Test procedures

The test procedures required to evaluate the performance of the Space Lab Bus Interface Unit (SL/BIU) are described. This level of testing involves the design evaluation of signal levels, timing, and signal-to-noise (S/N) performance. The tests are to be comprehensive in order to provide data on the operational characteristics of the SL/BIU. The evluation tests are designed to accomplish the following determinations as a minimum for component level testing of the SL/BIU: (1) the baseline operation parameters for comparison to ICD 2-05301 requirements; (2) the influence of serial data line parameter variation on the operation of SL/BIU; (3) the effects of noise on discrete and serial data lines (S/N ratio); and (4) the effects of cable length variation.

Source record

Space Shuttle SRM performance improvement

A number of options for Solid Rocket Motor (SRM) performance improvement were studied and evaluated by NASA with respect to payload improvement potential, technical risk, schedule, cost, and impact on Shuttle system performance. It was found that the SRM delivered specific impulse could be improved by increasing the nozzle expansion ratio from 7.16 to 7.72. This was achieved by decreasing the throat diameter of the nozzle exit cone, while staying within tooling, facility, and ICD limitations. A simple modification of the grain inhibiting pattern was made to reshape the thrust-time history and thereby obtain more delivered impulse during the early portion of motor operation. These performance options, initiated in October 1980, provide a 3,000 lb payload increase. Longer range options are the use of a filament wound composite case, a HTPB propellant, and further increases in the nozzle expansion ratio. These improvements have a potential of 10,000 to 11,000 lb payload increase.

Speak, C. A.

Effects of wind on turbofan engines in outdoor static test stands

Wind can affect measured thrust and can cause turbofan engine speed to fluctuate during outdoor testing. Techniques used at an outdoor test stand at NASA Lewis Research Center to make testing easier and faster and to improve data repeatability include using an inflow control device (ICD) to make fan speed steadier, taking many raw data samples for better averaging, and correcting thrust for wind direction and speed. Data from engine tests are presented to show that the techniques improve repeatability of thrust and airflow measurements under various wind conditions.

Mcardle, J. G.

Effects of wind on turbofan engines in outdoor static test stands

Wind can affect measured thrust and can cause turbofan engine speed to fluctuate during outdoor testing. Techniques used at an outdoor test stand at NASA Lewis Research Center to make testing easier and faster and to improve data repeatability include using an inflow control device (ICD) to make fan speed steadier, taking many raw data samples for better averaging, and correcting thrust for wind direction and speed. Data from engine tests are presented to show that the techniques improve repeatability of thrust and airflow measurements under various wind conditions. Previously announced in STAR as N83-34945

Mcardle, J. G.

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.