SEARCH · Engineering Papers

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.

SourceResearch connectionFrom yearThrough year

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

At least 127 records · Page 7

All sources NASA NTRS DOE OSTI

DOE OSTI2022

Obstructive Sleep Apnea Among Army Aircrew

INTRODUCTION: Obstructive sleep apnea (OSA) is a condition characterized by disrupted sleep and excessive daytime fatigue. Associated cognitive and psychomotor decrements pose a threat to aviators’ performance and flight safety. Additionally, the longer term health effects associated with the disease can jeopardize an aviator’s career and negatively impact operational outputs. This study reviews OSA prevalence, related comorbid conditions in Army aviators, and analyzes the aeromedical dispositions of affected individuals. METHODS: The U.S. Army Aeromedical Electronic Resource Office (AERO) database was interrogated for all cases of OSA from June 2005 through June 2015 using ICD-9 code 327.23. Prevalence rates for OSA and other comorbid conditions were then calculated using the total number of aviators in the AERO database. RESULTS: A total of 663 unique instances of OSA were found among the aviator population ( N = 24,568), giving a point prevalence of 2.69%. Four cases affected women. Mean age of initial presentation was 42.62 yr and mean Body Mass Index was 28.69. The top five most prevalent comorbid conditions were hypertension, lumbago, degeneration of a lumbar or lumbosacral intervertebral disc, PTSD, and testicular hypofunction. DISCUSSION: Prevalence of OSA among aviators is lower than the general population but is not uncommon. A positive diagnosis requires a waiver or can result in suspension if not managed effectively, potentially leading to a reduction in aviator numbers. Aggressive health promotion and robust medical surveillance and aeromedical disposition management by the aeromedical community is essential to reduce OSA numbers, maintain aviator health, and maximize flight safety. Goldie C, Stork B, Bernhardt K, Gaydos SJ, Kelley AM. Obstructive sleep apnea among army aircrew . Aerosp Med Hum Perform. 2022; 93(5):415–420.

Biophysics↗

NASA NTRS1973

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.↗

NASA NTRS1978

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↗

NASA NTRS1981

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.↗

NASA NTRS1983

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.↗

NASA NTRS1983

Effects of wind on turbofan engines in outdoor static test stands

Mcardle, J. G.↗

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 NTRS1987

SOLON: An autonomous vehicle mission planner

The State-Operator Logic Machine (SOLON) Planner provides an architecture for effective real-time planning and replanning for an autonomous vehicle. The highlights of the system, which distinguish it from other AI-based planners that have been designed previously, are its hybrid application of state-driven control architecture and the use of both schematic representations and logic programming for the management of its knowledge base. SOLON is designed to provide multiple levels of planning for a single autonomous vehicle which is supplied with a skeletal, partially-specified mission plan at the outset of the vehicle's operations. This mission plan consists of a set of objectives, each of which will be decomposable by the planner into tasks. These tasks are themselves comparatively complex sets of actions which are executable by a conventional real-time control system which does not perform planning but which is capable of making adjustments or modifications to the provided tasks according to constraints and tolerances provided by the Planner. The current implementation of the SOLON is in the form of a real-time simulation of the Planner module of an Intelligent Vehicle Controller (IVC) on-board an autonomous underwater vehicle (AUV). The simulation is embedded within a larger simulator environment known as ICDS (Intelligent Controller Development System) operating on a Symbolics 3645/75 computer.

Dudziak, M. J.↗

NASA NTRS1992

Design Feasibility Study of a Space Station Freedom Truss

Here, the focus is on the design and configuration feasibility of the short spacer for the Space Station Program in its launch configuration. The product of this study is being used by Rockwell International (Rocketdyne Division) as they continue their design concept of the current short spacer configuration. It is anticipated that the launch loads will dominate the on-orbit loads and dictate the design configuration of the short spacer. At the present time, the on-orbit loads have not been generated. The structural analysis discussed herein is based on the transient events derived from the Space Transportation System (STS) Interface Control Document (ICD). The transient loading events consist of liftoff loads, landing loads, and emergency landing loads. The quasi-static loading events have been neglected, since the magnitude of the acceleration factors are lower than the transient acceleration factors. The normal mode analyses presented herein are based on the most feasible configurations with acceptable stress ranges.

Armand, Sasan C.↗

NASA NTRS1993

Longitudinal study of astronaut health: Mortality in the years 1959-1991

We conducted a historical cohort study of mortality among 195 astronauts who were exposed to space and medical sources of radiation between 1959 and 1991. Cumulative occupational and medical radiation exposures were obtained from the astronaut radiation exposure history data base. Causes of death were obtained from obligatory death certificates and autopsy reports that were on file in the medical records. A total of 18 deaths occurred during the 32-year follow-up period for which the all-cause standardized mortality ratio (SMR) was 142 (95 percent confidence interval 84 225). There was one cancer death in the buccal cavity and pharynegeal ICD-9 rubric whose occurrence was significantly beyond expectation. Mortality for coronary disease was 59 percent lower than expected (2 deaths; SMR = 41; 95 percent confidence limit 5 147). The crude death rate for 10 occupationally related accidents was 400 deaths per 100,000 person-years, which is an order of magnitude greater than accidental death rates in mining industries. The SMR of 1027 for fatal accidents was significantly beyond expectation (14 deaths; 95 percent confidence limit 561 1723) and was similar to SMRs for accidents among aerial pesticide applications. The 10-year cumulative risk of occupational fatalities based on the exponential, Weibull, Gompertz, and linear-exponential distributions was 10 percent. Mortality from motor vehicle accidents was slightly higher than expected but was not significant (1 death; SMR = 145; 95 percent confidence limit 2 808). Radiation exposures from medical procedures accounted for a majority of cumulative dose when compared with space radiation exposures. The results of the study do not confirm the impression that astronauts are at increased risk of cancer, but this does not obviate the need for further study. Overall, it was found that astronauts are at a health disadvantage as a result of catastrophic accidents.

Peterson, Leif E.↗

NASA NTRS1994

Structural design feasibility study of Space Station long spacer truss

The structural design and configuration feasibility of the long spacer truss assembly that will be used as part of the Space Station Freedom is the focus of this study. The structural analysis discussed herein is derived from the transient loading events presented in the Space Transportation System Interface Control Document (STS ICD). The transient loading events are liftoff, landing, and emergency landing loads. Quasi-static loading events were neglected in this study since the magnitude of the quasi-static acceleration factors is lower than that of the transient acceleration factors. Structural analysis of the proposed configuration of the long spacer truss with four longerons indicated that negative safety margins are possible. As a result, configuration changes were proposed. The primary configuration change suggested was to increase the number of truss longerons to six. The six-longeron truss appears to be a more promising structure than the four-longeron truss because it offers a positive margin of safety and more volume in its second bay (BAY2). This additional volume can be used for resupply of some of the orbital replacement units (such as a battery box). Note that the design effort on the long spacer truss has not fully begun and that calculations and reports of the negative safety margins are, to date, based on concept only.

Armand, Sasan C.↗

NASA NTRS1994

Earth Observing System (EOS) Advanced Microwave Sounding Unit-A (AMSU-A): Instrumentation interface control document

This Interface Control Document (ICD) defines the specific details of the complete accomodation information between the Earth Observing System (EOS) PM Spacecraft and the Advanced Microwave Sounding Unit (AMSU-A)Instrument. This is the first submittal of the ICN: it will be updated periodically throughout the life of the program. The next update is planned prior to Critical Design Review (CDR).

Source record↗

NASA NTRS2000

Microgravity Acceleration Measurement System (MAMS) Flight Configuration Verification and Status

The Microgravity Acceleration Measurement System (MAMS) is a precision spaceflight instrument designed to measure and characterize the microgravity environment existing in the US Lab Module of the International Space Station. Both vibratory and quasi-steady triaxial acceleration data are acquired and provided to an Ethernet data link. The MAMS Double Mid-Deck Locker (DMDL) EXPRESS Rack payload meets all the ISS IDD and ICD interface requirements as discussed in the paper which also presents flight configuration illustrations. The overall MAMS sensor and data acquisition performance and verification data are presented in addition to a discussion of the Command and Data Handling features implemented via the ISS, downlink and the GRC Telescience Center displays.

Wagar, William↗

NASA NTRS2003

Standards-and Component-Based Mission Operations Architecture at NASA's Goddard Space Flight Center

NASA Goddard Space Flight Center (GSFC) manages many of NASA s earth and space science satellite missions. A wide variety of commercial products and GSFC-developed software components are typically integrated into a unique system configuration for each mission. Independent development of the many mission operations center systems has led to systems that are expensive to integrate, difficult to infuse with new capabilities developed for other programs, and cumbersome to maintain. This traditional approach becomes even more problematic as NASA moves towards satellite constellations, new operations concepts, and even further budgets reductions. The GSFC Mission Services Evolution Center (GMSEC) is creating a new architecture for future missions at GSFC. Instead of selecting the best-in-class components and creating a standard control center system, GMSEC is developing component interface standards so that multiple products can plug-and-play into the configuration. Missions can then select the best components based on the merits of the product and not simply based on recent integration history at NASA. The GMSEC system utilizes a publish/subscribe information bus and standard XML-based key message interfaces. Functional components can either match directly to the interface standard, or adapters can be developed to match the product's interface to the GMSEC standard with out impacting the source product. Applications Program Interfaces (API's) are being developed to isolate the underlying middleware from the applications software and to allow the middleware product to be switched if necessary. Interface Control Documents (ICDs) between each pair of communicating components is replaced by a single message/API specification document. New applications must simply match to the information bus standards and need not worry about all of the other applications in the system. For legacy software, adapters can be developed to facilitate communications between the application and the information bus. As the approach has matured, it has become apparent that it can provide innovative solutions to some of the multi-satellite challenges facing GSFC.

Smith, Danford↗

NASA NTRS2006

SpaceWire Protocol ID: What Does It Mean To You?

Spacewire is becoming a popular solution for satellite high-speed data buses because it is a simple standard that provides great flexibility for a wide range of system requirements. It is simple in packet format and protocol, allowing users to easily tailor their implementation for their specific application. Some of the attractive aspects of Spacewire that make it easy to implement also make it hard for future reuse. Protocol reuse is difficult because Spacewire does not have a defined mechanism to communicate with the higher layers of the protocol stack. This has forced users of Spacewire to define unique packet formats and define how these packets are to be processed. Each mission writes their own Interface Control Document (ICD) and tailors Spacewire for their specific requirements making reuse difficult. Part of the reason for this habit may be because engineers typically optimize designs for their own requirements in the absence of a standard. This is an inefficient use of project resources and costs more to develop missions. A new packet format for Spacewire has been defined as a solution for this problem. This new packet format is a compliment to the Spacewire standard that will support protocol development upon Spacewire. The new packet definition does not replace the current packet structure, i.e., does not make the standard obsolete, but merely extends the standard for those who want to develop protocols over Spacewire. The Spacewire packet is defined with the first part being the Destination Address, which may be one or more bytes. This is followed by the packet cargo, which is user defined. The cargo is truncated with an End-Of-Packet (EOP) marker. This packet structure offers low packet overhead and allows the user to define how the contents are to be formatted. It also provides for many different addressing schemes, which provide flexibility in the system. This packet flexibility is typically an attractive part of the Spacewire. The new extended packet format adds one new field to the packet that greatly enhances the capability of Spacewire. This new field called the Protocol Identifier (ID) is used to identify the packet contents and the associated processing for the packet. This feature along with the restriction in the packet format that uses the Protocol ID, allows a deterministic method of decoding packets that was not before possible. The first part of the packet is still the Destination Address, which still conforms to the original standard but with one restriction. The restriction is that the first byte seen at the destination by the user needs to be a logical address, independent of the addressing scheme used. The second field is defined as the Protocol ID, which is usually one byte in length. The packet cargo (user defined) follows the Protocol ID. After the packet cargo is the EOP, which defines the end of packet. The value of the Protocol ID is assigned by the Spacewire working group and the protocol description published for others to use. The development of Protocols for Spacewire is currently the area of greatest activity by the Spacewire working group. The first protocol definition by the working group has been completed and is now in the process of formal standardization. There are many other protocols in development for missions that have not yet received formal Protocol ID assignment, but even if the protocols are not formally assigned a value, this effort will provide synergism for future developments.

Rakow, Glenn↗

NASA NTRS2006

Control of Technology Transfer at JPL

Controlled Technology: 1) Design: preliminary or critical design data, schematics, technical flow charts, SNV code/diagnostics, logic flow diagrams, wirelist, ICDs, detailed specifications or requirements. 2) Development: constraints, computations, configurations, technical analyses, acceptance criteria, anomaly resolution, detailed test plans, detailed technical proposals. 3) Production: process or how-to: assemble, operated, repair, maintain, modify. 4) Manufacturing: technical instructions, specific parts, specific materials, specific qualities, specific processes, specific flow. 5) Operations: how-to operate, contingency or standard operating plans, Ops handbooks. 6) Repair: repair instructions, troubleshooting schemes, detailed schematics. 7) Test: specific procedures, data, analysis, detailed test plan and retest plans, detailed anomaly resolutions, detailed failure causes and corrective actions, troubleshooting, trended test data, flight readiness data. 8) Maintenance: maintenance schedules and plans, methods for regular upkeep, overhaul instructions. 9) Modification: modification instructions, upgrades kit parts, including software

Jet Propulsion Laboratory (JPL)↗

NASA NTRS2014

Injury Surveillance Among NASA Astronauts Using the Barell Injury Diagnosis Matrix

Astronauts perform physically demanding tasks and risk incurring musculoskeletal injuries during both groundbased training and missions. Increased injury rates throughout the history of the U.S. space program have been attributed to numerous factors, including an aging astronaut corps, increased Weightless Environment Training Facility (WETF) and Neutral Buoyancy Laboratory (NBL) training to construct the International Space Station, and improved clinical operations that promote injury prevention and reporting. With NASA program changes through the years (including retirement of the Shuttle program) and an improved training environment (including a new astronaut gym), there is no surveillance program to systematically track injury rates. A limited number of research projects have been conducted over the past 20 years to evaluate musculoskeletal injuries: (1) to evaluate orthopedic injuries from 1987 to 1995, (2) to describe upper extremity injuries, (3) to evaluate EVA spacesuit training related injuries, and (4) to evaluate in-flight musculoskeletal injuries. Nevertheless, there has been no consistently performed comprehensive assessment of musculoskeletal injuries among astronauts. The Barell Injury Diagnosis Matrix was introduced at the 2001 meeting of the International Collaborative Effort (ICE) on Injury Statistics. The Matrix proposes a standardized method of classifying body region by nature of injury. Diagnoses are coded using the International Classification of Diseases, Ninth Revision, Clinical Modification (ICD-9-CM) coding system. The purpose of this study is to assess the usefulness and complexity of the Barell Injury Diagnosis Matrix to classify and track musculoskeletal injuries among NASA astronauts.

Murray, J. D.↗

NASA NTRS2015

Interfacing and Verifying ALHAT Safe Precision Landing Systems with the Morpheus Vehicle

The NASA Autonomous precision Landing and Hazard Avoidance Technology (ALHAT) project developed a suite of prototype sensors to enable autonomous and safe precision landing of robotic or crewed vehicles under any terrain lighting conditions. Development of the ALHAT sensor suite was a cross-NASA effort, culminating in integration and testing on-board a variety of terrestrial vehicles toward infusion into future spaceflight applications. Terrestrial tests were conducted on specialized test gantries, moving trucks, helicopter flights, and a flight test onboard the NASA Morpheus free-flying, rocket-propulsive flight-test vehicle. To accomplish these tests, a tedious integration process was developed and followed, which included both command and telemetry interfacing, as well as sensor alignment and calibration verification to ensure valid test data to analyze ALHAT and Guidance, Navigation and Control (GNC) performance. This was especially true for the flight test campaign of ALHAT onboard Morpheus. For interfacing of ALHAT sensors to the Morpheus flight system, an adaptable command and telemetry architecture was developed to allow for the evolution of per-sensor Interface Control Design/Documents (ICDs). Additionally, individual-sensor and on-vehicle verification testing was developed to ensure functional operation of the ALHAT sensors onboard the vehicle, as well as precision-measurement validity for each ALHAT sensor when integrated within the Morpheus GNC system. This paper provides some insight into the interface development and the integrated-systems verification that were a part of the build-up toward success of the ALHAT and Morpheus flight test campaigns in 2014. These campaigns provided valuable performance data that is refining the path toward spaceflight infusion of the ALHAT sensor suite.

Carson, John M., III↗