Search NASA⌕ Search

SEARCH · Search NASA

Results for “Systems Integration”

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 379 records · Page 21
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Assessment of Spacecraft Systems Integration Using the Electric Propulsion Interactions Code (EPIC)

SAIC is currently developing the Electric Propulsion Interactions Code 'EPIC', an interactive computer tool that allows the construction of a 3-D spacecraft model, and the assessment of interactions between its subsystems and the plume from an electric thruster. EPIC unites different computer tools to address the complexity associated with the interaction processes. This paper describes the overall architecture and capability of EPIC including the physics and algorithms that comprise its various components. Results from selected modeling efforts of different spacecraft-thruster systems are also presented.

Mikellides, Ioannis G.↗
NASA NTRS2005

Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Contingency Management

This document involves definition of technology interface requirements for Contingency Management. This was performed through a review of Contingency Management-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Contingency Management Work Package were considered. Beginning with HSI high-level functional requirements for Contingency Management, and Contingency Management technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of system failures and associated contingency procedures, and (2) the control capability needed by the pilot to obtain system status and procedure information. Fundamentally, these requirements provide the candidate Contingency Management technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Contingency Management operations and functions should interface with the pilot to provide the necessary Contingency Management functionality to the UA-pilot system. Requirements and guidelines for Contingency Management are partitioned into four categories: (1) Health and Status and (2) Contingency Management. Each requirement is stated and is supported with a rationale and associated reference(s).

Source record↗
NASA NTRS2007

Step 1:Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Collision Avoidance

This document provides definition of technology human interface requirements for Collision Avoidance (CA). This was performed through a review of CA-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Access 5 CA work package were considered... Beginning with the HSI high-level functional requirement for CA, and CA technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge CA system status, and (2) the control capability needed by the pilot to obtain CA information and affect an avoidance maneuver. Fundamentally, these requirements provide the candidate CA technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how CA operations and functions should interface with the pilot to provide the necessary CA functionality to the UA-pilot system .Requirements and guidelines for CA are partitioned into four categories: (1) General, (2) Alerting, (3) Guidance, and (4) Cockpit Display of Traffic Information. Each requirement is stated and is supported with a rationale and associated reference(s).

Source record↗
NASA NTRS1984

Report of the Panel on Systems Integration

Projections of technological advances to the year 2000 have suggested a number of possible conceptual types of air vehicles. For convenience, these have been grouped according to speed, increasing from below Mach 1 (including hovering flight) through various Mach ranges to orbital flight. The potential performance capabilities that could be realized for each of these types of aircraft provide exciting prospects for the years beyond 2000. It is clear that the greater design flexibilities provided by the projected technology advances will permit significant improvements in performance, economy, and safety and allow the design and development of aircraft systems that current technology will not support. In the following sections, each vehicle type is discussed, noting design features and significant advances. Where related aircraft exist, the significant economic and performance factors are compared. In addition, for each concept, the technology developments considered essential for the advanced concept are identified. The types of aircraft described are examples of what advances in the technology projected for the year 2000 could provide. They are by no means all that would be possible. The panel's views on the current state of knowledge of systems intergration as a discipline and the need for advancement in this area presented in the concluding section of this report.

Sigalla, Armand↗
NASA NTRS1976

Design, fabrication and systems integration of a satellite tracked, free-drifting ocean data buoy

Engineering details are presented of a small free-drifting buoy configuration designed for use in the study of continental shelf water circulation patterns in the Chesapeake Bight of the Western North Atlantic Ocean. The buoy incoporated French instrumentation and was interrogated by the French EOLE satellite to provide position and four channels of temperature data. The buoy design included a variable depth drogue and a power supply sufficient for six weeks of continuous operations. Proof tests of the configuration indicated an adequate design and subsequent field experiments verified the proper functioning of the system.

Wallace, J. W.↗
NASA NTRS1992

GRO/EGRET data analysis software: An integrated system of custom and commercial software using standard interfaces

The Energetic Gamma Ray Telescope Experiment (EGRET) on the Compton Gamma Ray Observatory has been in orbit for more than a year and is being used to map the full sky for gamma rays in a wide energy range from 30 to 20,000 MeV. Already these measurements have resulted in a wide range of exciting new information on quasars, pulsars, galactic sources, and diffuse gamma ray emission. The central part of the analysis is done with sky maps that typically cover an 80 x 80 degree section of the sky for an exposure time of several days. Specific software developed for this program generates the counts, exposure, and intensity maps. The analysis is done on a network of UNIX based workstations and takes full advantage of a custom-built user interface called X-dialog. The maps that are generated are stored in the FITS format for a collection of energies. These, along with similar diffuse emission background maps generated from a model calculation, serve as input to a maximum likelihood program that produces maps of likelihood with optional contours that are used to evaluate regions for sources. Likelihood also evaluates the background corrected intensity at each location for each energy interval from which spectra can be generated. Being in a standard FITS format permits all of the maps to be easily accessed by the full complement of tools available in several commercial astronomical analysis systems. In the EGRET case, IDL is used to produce graphics plots in two and three dimensions and to quickly implement any special evaluation that might be desired. Other custom-built software, such as the spectral and pulsar analyses, take advantage of the XView toolkit for display and Postscript output for the color hard copy. This poster paper outlines the data flow and provides examples of the user interfaces and output products. It stresses the advantages that are derived from the integration of the specific instrument-unique software and powerful commercial tools for graphics and statistical evaluation. This approach has several proven advantages including flexibility, a minimum of development effort, ease of use, and portability.

Laubenthal, N. A.↗
NASA NTRS1983

LFC leading edge glove flight: Aircraft modification design, test article development and systems integration

Reduction of skin friction drag by suction of boundary layer air to maintain laminar flow has been known since Prandtl's published work in 1904. The dramatic increases in fuel costs and the potential for periods of limited fuel availability provided the impetus to explore technologies to reduce transport aircraft fuel consumption. NASA sponsored the Aircraft Energy Efficiency (ACEE) program in 1976 to develop technologies to improve fuel efficiency. This report documents the Lockheed-Georgia Company accomplishments in designing and fabricating a leading-edge flight test article incorporating boundary layer suction slots to be flown by NASA on their modified JetStar aircraft. Lockheed-Georgia Company performed as the integration contractor to design the JetStar aircraft modification to accept both a Lockheed and a McDonnell Douglas flight test article. McDonnell Douglas uses a porous skin concept. The report describes aerodynamic analyses, fabrication techniques, JetStar modifications, instrumentation requirements, and structural analyses and testing for the Lockheed test article. NASA will flight test the two LFC leading-edge test articles in a simulated commercial environment over a 6 to 8 month period in 1984. The objective of the flight test program is to evaluate the effectiveness of LFC leading-edge systems in reducing skin friction drag and consequently improving fuel efficiency.

Etchberger, F. R.↗
NASA NTRSDate not supplied

Communication Delays in Cislunar Space: A Lab Study Examining Human System Integration Architecture (HSIA) and Team Risk Concerns

BACKGROUND: Communication delays are an inherent challenge of space missions to the Moon and beyond. Past research studies showed that 50+ second delays adversely affected individual well-being, team cohesion, and overall task performance (Kintz et al., 2016; Larson et al., 2019). However, there is a dearth of research on the effects of shorter delays (on the order of 4-12 seconds one-way) that may present a more immediate challenge during the upcoming Artemis missions. Even these shorter delays could make it difficult or infeasible for ground control to provide real-time support to Artemis astronauts, especially in complex and time-critical tasks such as extra-vehicular activities (EVAs). Results from studies on longer or Mars-like delays cannot be directly applied to Artemis-like delays, due to the large differences in delay magnitude and task types between these mission categories. For example, real-time oversight and guidance from ground control is impossible under Mars-like delays but may be performed under Artemis-like delays, albeit with potentially high workload and communication difficulty. Thus, a better understanding of the effects of Artemis-like communication delays on collaborative task performance is needed. Additionally, there is a need to develop reliable task paradigms that can be used in future studies on communication delays. METHODS: This project will study the effects of Artemis-like communication delays on collaborative task performance in a simulated space-to-ground team task via a lunar Gateway-like interface prototype. Teams of two astronaut-like participants - one serving as “crewmember” and one as “flight controller” - will perform a spaceflight-relevant task under six delay conditions (i.e., 0, 4, 6, 8, 10, and 12 seconds). Audio, video, texting, and file transfer will be delayed between the participants to mimic lunar-like communication delays. Measures related to workload, situation awareness, system usability, task performance, team cohesion, well-being, and communication strategies will be collected. These measures will be compared across delay levels, participant roles, and off-nominal and nominal tasks. Participants will be given the choice to use any combination of video and text communication in order to study preferences in interaction modality. RESEARCH AIMS: One aim is to identify a delay level or range of levels at which there may be significant decrements in individual and team-based measures. Identifying such ranges may help design novel workload management or communication countermeasures for future space missions. Also, the spaceflight-relevant research tasks and corresponding communication delay technology developed as part of this effort may be used for future studies on communication delays. Results from this work are also expected to inform study scenarios in the Human Exploration Research Analog (HERA) Campaign.

S Upasani↗
DOE OSTI2025

Integrated System for Methane Emissions Monitoring, Mapping, and Quantification

This report presents the work completed under the DOE iM4 project for the development of a methane emission monitoring system for detection, location, and quantification of methane in oil and gas industries. The task was divided into four main areas including: 1) Sensors and Input, 2) Centralized Cloud Information Center, 3) Algorithms, and 4) Testing and Validation. Task 1 focused on researching and developing an understanding of the current, or soon to be, available methane sensing technologies. Task 2 consisted of developing the architecture, selecting hardware, software and elements for the methane monitoring system. Task 3 focused on the algorithms used for the complex inverse model of going from measured methane signatures to the detection, localization, and quantification of sources that are desired. Finally, Task 4 focused on the methods of testing and validating the operation of the system. Attention was also given to the development method and cost breakdown of the system.

03 NATURAL GAS↗
NASA NTRS1971

Integrating system safety into the basic systems engineering process

The basic elements of a systems engineering process are given along with a detailed description of what the safety system requires from the systems engineering process. Also discussed is the safety that the system provides to other subfunctions of systems engineering.

John W. Griswold↗