Search NASA⌕ Search

SEARCH · Search NASA

Results for “Integrated”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

Organizational Considerations for Implementing Systems Engineering and Integration in the Ares Projects Office

Systems Engineering and Integration (SE&I) is a critical discipline in developing new space systems. In 2005, NASA performed an internal study of 24 agency and Department of Defense (DoD) programs to evaluate methods of integrating SE&I practices and determine their effectiveness. The goal of the study was to determine the best SE&I implementation strategy for the Ares Projects Office. The study identified six SE&I organizational structures: 1. Lead systems integrator (LSI) with SE&I responsibility and government technical insight. 2a. Integration contractor with government SE&I responsibility (government insight). 2b. Integration contractor with government SE&I responsibility (government oversight). 3a. Prime contractor with SE&I responsibility (government insight). 3b. Prime contractor with SE&I responsibility (government oversight). 3c. Prime contractor with SE&I responsibility (government/industry partnership). 4a.Prime contractor with government SE&I responsibility (government insight). 4b. Prime contractor with government SE&I responsibility (government oversight). 4d.Prime contractors with total system performance responsibility (TSPR). 5. Prime contractor with government SE&I responsibility and integration products through a Federally Funded Research and Development Center (FFRDC). 6. Government/FFRDC in-house development with SE&I responsibility and function. The organizational structure used most often was number 4, using a prime contractor with government SE&I responsibility and government technical insight. However, data analyses did not establish a positive relationship between program development costs and specific SE&I organizational types, nor did it positively determine the relationship between successful programs or projects and their SE&I structure. The SE&I study reached the following conclusions: (1) Large, long-duration, technically complex programs or projects reach their technical goals, but rarely meet schedule or cost goals. NASA's recent successes have been smaller, short-duration development projects using heritage hardware/software, focused technology development, technical oversight and stable external factors. (2) Programs and projects have failed or been terminated due to lack of technical insight, relaxing of SE&I processes, and unstable external factors. (3) The study did not find a single, clear optimum SE&I organization type to fit all projects. However, while any organizational structure can be made to work, the fewer complexities in the program, the better the likelihood of success. (4) The most common successful SE&I organization structure type in the study was type 4b, where the government maintained integration responsibility, with the prime contractor providing SE&I products and the government providing technical oversight. This study was instrumental in helping the APO select organization structure 4, following the same SE&I and oversight process used during humanlund7s last voyages to the Moon.

Thomas, LeAnn↗
NASA NTRS2007

System for Secure Integration of Aviation Data

The Aviation Data Integration System (ADIS) of Ames Research Center has been established to promote analysis of aviation data by airlines and other interested users for purposes of enhancing the quality (especially safety) of flight operations. The ADIS is a system of computer hardware and software for collecting, integrating, and disseminating aviation data pertaining to flights and specified flight events that involve one or more airline(s). The ADIS is secure in the sense that care is taken to ensure the integrity of sources of collected data and to verify the authorizations of requesters to receive data. Most importantly, the ADIS removes a disincentive to collection and exchange of useful data by providing for automatic removal of information that could be used to identify specific flights and crewmembers. Such information, denoted sensitive information, includes flight data (here signifying data collected by sensors aboard an aircraft during flight), weather data for a specified route on a specified date, date and time, and any other information traceable to a specific flight. The removal of information that could be used to perform such tracing is called "deidentification." Airlines are often reluctant to keep flight data in identifiable form because of concerns about loss of anonymity. Hence, one of the things needed to promote retention and analysis of aviation data is an automated means of de-identification of archived flight data to enable integration of flight data with non-flight aviation data while preserving anonymity. Preferably, such an automated means would enable end users of the data to continue to use pre-existing data-analysis software to identify anomalies in flight data without identifying a specific anomalous flight. It would then also be possible to perform statistical analyses of integrated data. These needs are satisfied by the ADIS, which enables an end user to request aviation data associated with de-identified flight data. The ADIS includes client software integrated with other software running on flight-operations quality-assurance (FOQA) computers for purposes of analyzing data to study specified types of events or exceedences (departures of flight parameters from normal ranges). In addition to ADIS client software, ADIS includes server hardware and software that provide services to the ADIS clients via the Internet (see figure). The ADIS server receives and integrates flight and non-flight data pertaining to flights from multiple sources. The server accepts data updates from authorized sources only and responds to requests from authorized users only. In order to satisfy security requirements established by the airlines, (1) an ADIS client must not be accessible from the Internet by an unauthorized user and (2) non-flight data as airport terminal information system (ATIS) and weather data must be displayed without any identifying flight information. ADIS hardware and software architecture as well as encryption and data display scheme are designed to meet these requirements. When a user requests one or more selected aviation data characteristics associated with an event (e.g., a collision, near miss, equipment malfunction, or exceedence), the ADIS client augments the request with date and time information from encrypted files and submits the augmented request to the server. Once the user s authorization has been verified, the server returns the requested information in de-identified form.

Kulkarni, Deepak↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗
NASA NTRS2012

Human Systems Integration in Practice: Constellation Lessons Learned

NASA's Constellation program provided a unique testbed for Human Systems Integration (HSI) as a fundamental element of the Systems Engineering process. Constellation was the first major program to have HSI mandated by NASA's Human Rating document. Proper HSI is critical to the success of any project that relies on humans to function as operators, maintainers, or controllers of a system. HSI improves mission, system and human performance, significantly reduces lifecycle costs, lowers risk and minimizes re-design. Successful HSI begins with sufficient project schedule dedicated to the generation of human systems requirements, but is by no means solely a requirements management process. A top-down systems engineering process that recognizes throughout the organization, human factors as a technical discipline equal to traditional engineering disciplines with authority for the overall system. This partners with a bottoms-up mechanism for human-centered design and technical issue resolution. The Constellation Human Systems Integration Group (HSIG) was a part of the Systems Engineering and Integration (SE&I) organization within the program office, and existed alongside similar groups such as Flight Performance, Environments & Constraints, and Integrated Loads, Structures and Mechanisms. While the HSIG successfully managed, via influence leadership, a down-and-in Community of Practice to facilitate technical integration and issue resolution, it lacked parallel top-down authority to drive integrated design. This presentation will discuss how HSI was applied to Constellation, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers. This presentation will discuss how Human Systems Integration (HSI) was applied to NASA's Constellation program, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers on how to accomplish this critical function.

Zumbado, Jennifer Rochlis↗
NASA NTRS2011

Systems Integration Challenges for a National Space Launch System

System Integration was refined through the complexity and early failures experienced in rocket flight. System Integration encompasses many different viewpoints of the system development. System Integration must ensure consistency in development and operations activities. Human Space Flight tends toward large, complex systems. Understanding the system fs operational and use context is the guiding principle for System Integration: (1) Sizeable costs can be driven into systems by not fully understanding context (2). Adhering to the system context throughout the system fs life cycle is essential to maintaining efficient System Integration. System Integration exists within the System Architecture. Beautiful systems are simple in use and operation -- Block upgrades facilitate manageable steps in functionality evolution. Effective System Integration requires a stable system concept. Communication is essential to system simplicity

May, Todd A.↗
NASA NTRS2015

Reflections on Centaur Upper Stage Integration by the NASA Lewis (Glenn) Research Center

The NASA Glenn (then Lewis) Research Center (GRC) led several expendable launch vehicle (ELV) projects from 1963 to 1998, most notably the Centaur upper stage. These major, comprehensive projects included system management, system development, integration (both payload and stage), and launch operations. The integration role that GRC pioneered was truly unique and highly successful. Its philosophy, scope, and content were not just invaluable to the missions and vehicles it supported, but also had significant Agency-wide benefits. An overview of the NASA Lewis Research Center (now the NASA Glenn Research Center) philosophy on ELV integration is provided, focusing on Atlas/Centaur, Titan/Centaur, and Shuttle/Centaur vehicles and programs. The necessity of having a stable, highly technically competent in-house staff is discussed. Significant depth of technical penetration of contractor work is another critical component. Functioning as a cohesive team was more than a concept: GRC senior management, NASA Headquarters, contractors, payload users, and all staff worked together. The scope, content, and history of launch vehicle integration at GRC are broadly discussed. Payload integration is compared to stage development integration in terms of engineering and organization. Finally, the transition from buying launch vehicles to buying launch services is discussed, and thoughts on future possibilities of employing the successful GRC experience in integrating ELV systems like Centaur are explored.

Centaur↗
NASA NTRS2011

Integrated Arrays on Silicon at Terahertz Frequencies

In this paper we explore various receiver font-end and antenna architecture for use in integrated arrays at terahertz frequencies. Development of wafer-level integrated terahertz receiver front-end by using advanced semiconductor fabrication technologies and use of novel integrated antennas with silicon micromachining are reported. We report novel stacking of micromachined silicon wafers which allows for the 3-dimensional integration of various terahertz receiver components in extremely small packages which easily leads to the development of 2- dimensioanl multi-pixel receiver front-ends in the terahertz frequency range. We also report an integrated micro-lens antenna that goes with the silicon micro-machined front-end. The micro-lens antenna is fed by a waveguide that excites a silicon lens antenna through a leaky-wave or electromagnetic band gap (EBG) resonant cavity. We utilized advanced semiconductor nanofabrication techniques to design, fabricate, and demonstrate a super-compact, low-mass submillimeter-wave heterodyne frontend. When the micro-lens antenna is integrated with the receiver front-end we will be able to assemble integrated heterodyne array receivers for various applications such as multi-pixel high resolution spectrometer and imaging radar at terahertz frequencies.

silicon micromaching↗
NASA NTRSDate not supplied

Distribution of SLS Integrated Load Uncertainty to Surface Pressures and Sectional Loads

Aerodynamic loads that are important to launch vehicle programs such as NASA’s Space Launch System (SLS) include both integrated loads such as the force & moment on the entire vehicle and distributed loads. In this work two examples of distributed loads are considered: the pressure field on the surface of the vehicle and sectional loads, which are one-dimensional distributions along the axis of the launch vehicle. In some modern flight programs, the integrated loads, such as lift and drag, used to design the guidance and control laws for the vehicle come from wind tunnel testing, while distributed loads are produced using Computational Fluid Dynamics(CFD). The first task that is addressed in this paper, then, is to provide a formal method to adjust the distributed loads so that integrating them matches the prescribed integrated load. In addition, the integrated loads in a launch vehicle typically include an uncertainty estimate. The second task is to distribute this prescribed integrated uncertainty to each point in a distributed load. Both tasks are addressed using the same technique, which is to create distributed load profiles that isolate adjustments to one integrated load while leaving the others unaffected. These adjustments are informed by Proper Orthogonal Decomposition (POD) of the entire CFD-based distributed load database. Once applied, the adjusted distributed loads can be used to evaluate any scalar quantity of interest that might be needed by downstream users such as structural analysis or trajectory modelers.

SLS↗
NASA NTRS2023

The Assembly, Test, and Integration of LOFTID (Low-Earth Orbit Flight Test of an Inflatable Decelera-tor)

R.J. Bodkin Biography Mr. Bodkin worked in industry for a rapid prototype company focusing on UAVs and manned experimental aircraft. Later he served as the Inflation System Lead on IRVE-II and 3 and the Re-Entry Vehicle Lead for LOFTID at NASA Langley Research Center. Introduction: The Low-Earth Orbit Flight Test of an Inflatable Decelerator (LOFTID), developed in partnership with United Launch Alliance (ULA) and flown in conjunction with the National Oceanic and Atmospheric Administration (NOAA) Joint Polar Satellite System-2 (JPSS-2) satellite, demonstrated Hypersonic Inflatable Aerodynamic Decelerator (HIAD) technology has progressed and is ready for mission infusion. LOFTID’s success demonstrates that aeroshells are not limited to the internal diame-ter of the launch vehicle payload fairing, allowing larger payloads to be deployed to the surfaces of planetary bodies with atmospheres. The challenges of assembling, integrating, and testing this revolutionary spacecraft will be dis-cussed as well as issues associated with doing this with a fixed launch date the project did not control. Assembly: Because LOFTID flew as a rideshare partner with JPSS-2, it was constrained with addi-tional schedule, milestone, and technical require-ments that were beyond the project’s control. As-sembly of the LOFTID hardware was challenged with the normal mechanical fit issues while also having to navigate the SARS-COVID-II pandemic. Challenges ranged from availability of team per-sonnel required on-site for vehicle assembly to dif-ficulties associated with team collaboration while working remotely and increased costs and lead times of components due to supply chain con-straints. Numerous additional challenges cascaded from the additional time required. Integration: LOFTID flew as a secondary pay-load to JPSS-2 in a mission-unique configuration, directly under JPSS-2 primary payload, inside the Payload Adapter that integrated JPSS-2 to the Atlas V launch vehicle. A mission unique Payload Adapt-er Separation System (PASS) was required to sepa-rate the Payload Adapter from the Launch Vehicle prior to the start of the LOFTID flight demonstra-tion. Development of this system was challenging due to a shortened development schedule resulting from the iterative nature of Payload Adapter devel-opment with the partners at ULA. Preparations to integrate the main segments of the LOFTID vehicle posed unique challenges of having to accommodate issues with a fixed launch date that led to some cre-ative solutions to the integration. The partnership agreement with ULA and JPSS-2 resulted in a mass simulator designed to be installed late in the inte-gration in the event the LOFTID vehicle was not ready in time.. Test: LOFTID testing was carried out in several phases. Some components were tested at the com-ponent level, others at the sub-system levels and then finally the integrated vehicle level. This culmi-nated with the Complete Systems Test (CST) per-formed in a vacuum chamber as one of the final checkouts prior to disassembly for re-packing of the aeroshell. CST challenges will be discussed as well as obstacles encountered post-CST. After CST, the vehicle was disassembled so the HIAD could be repacked, and the vehicle was reassembled for ac-ceptance vibration testing. Testing concluded with the fully assembled vehicle being shipped to the launch site for final testing and integrations with the Payload Adapter to JPSS-2 for launch and opera-tions. Conclusion: The challenges posed by the AI&T for LOFTID could inform the planetary community of some of the opportunities and challenges of de-veloping technologies on a rideshare with a rela-tively small budget.

R.J. Bodkin↗
NASA NTRS2024

Crew Health and Performance Integrated Data Architecture (CHP-IDA) Project

BACKGROUND: Future Human Exploration missions introduce a new paradigm as crews move further from the resupply and near real-time ground support typical of Low Earth Orbit missions today. Without immediate support from ground-based personnel, exploration crews will be more reliant on inflight data and technology to respond to emergencies and anomalies. A data architecture to support a new generation of technologies, employing advanced analytical and predictive modeling techniques, is needed to enable crew autonomy. OVERVIEW: The Crew Health and Performance Integrated Data Architecture (CHP-IDA) project funded by NASA’s Exploration Medical Integrated Product Team (XMIPT) is laying a foundation for future in-flight informatics by providing a back-end architecture for collecting, storing, and integrating multiple sources of data generated by and around the crew. CHP-IDA provides a platform for common data models and Application Programming Interfaces to access, integrate, process, and display CHP data (e.g., environmental, exercise, medical, sleep, performance, etc.). This will facilitate the increased situation awareness and decision support required by the crew and remote support of exploration missions. This presentation will describe the currently ongoing effort to develop and evaluate a path-to-flight concept of the CHP-IDA software and its core capabilities. Current integrations will be discussed, including analytics for Extravehicular Activity metabolic rate and data ingestion from a multi-functional integrated medical device. The presentation will also provide examples of scenarios used to demonstrate the CHP-IDA through human-in-the-loop test bed activities as well as examples of appropriate system performance metrics. DISCUSSION: Today, in-flight data is often siloed, unsynchronized, and largely inaccessible in real time. Many data sets require manual entry and/or data transfer between vehicles and the ground. These issues contribute to risks in supporting exploration medical capabilities. The CHP-IDA is a back-end data system providing core capabilities needed for timely and meaningful data insights across CHP domains to crew and remote personnel to enable increased crew autonomy. Future work includes collaboration with additional CHP domains, new technology integrations, and further demonstrations of the IDA within different vehicle and communication latency contexts. LEARNING OBJECTIVES 1. The audience will understand that the CHP-IDA is a back-end system, providing a platform to facilitate access, promote decision tools, and provide meaningful insights to crew and to remote stakeholders during exploration missions. 2. The audience will gain insight into human-centered research and activities used to discover CHP domain data needs and pain points and how this information is used to guide development of the IDA.

Exploration↗
NASA NTRS2024

Integrated Simulations of the Sabatier and Carbon Vapor Deposition Reactor to Understand Its Impacts to Operations and Performance

The carbon vapor deposition (CVD) reactor is a technology developed by Honeywell Aerospace to convert methane, at high temperatures, into hydrogen and solid carbon. This element is coupled with a Sabatier reactor to support a closed-loop environmental control and life support system with the aim of achieving nearly complete oxygen recovery (> 95%). Initial open-loop, brassboard CVD reactor tests and simulations have shown the CVD’s ability to achieve moderately high methane conversion and high hydrogen selectivity. However, in an integrated system, additional deficiencies are expected due to recycling of unreacted or extraneous species from the Sabatier reactor (e.g., carbon dioxide, hydrogen, water) and CVD reactor (e.g., hydrocarbons, methane, etc.). Sabatier and CVD reactor models were integrated and simulated to predict potential impacts to individual reactors’ and the overall system’s performance. The simulations showed that increasing the recycle of the CVD effluent hydrogen combined with decreasing the system inlet hydrogen flow rate (i.e., drawing a stoichiometric flow rate from an electrolyzer) can lead to an oxygen recovery of > 95%. However, system integration comes at a detriment to the individual reactors. The simulations show the initial conversion from the integrated system (Sabatier = 87% and CVD = 59%) to be lower than the standalone systems (Sabatier = 91% and CVD = 69%). Furthermore, transient simulations show substrate densification, leading to worsening methane conversion coupled with increasing acetylene production, which is commensurate with soot formation. Simulations predict a shortening of the maintenance interval (i.e., time until CVD methane conversion drops below 50%) in the integrated system, which would increase the consumable substrate mass. These analyses highlight the importance of long-duration, integrated tests to corroborate these findings as well as suggest potential modifications (e.g., intermediate gas separations) to improve performance.

Air Revitalization↗
NASA NTRS1973

Numerical integration routines for near-earth operations

Two general purpose numerical integration schemes were built into the NASA-JSC computer system. The state-of-the-art of numerical integration, the particular integrators built into the JSC computer system, and the use of the new integration packages are described. Background information about numerical integration and the variable-order, variable-stepsize Adams numerical integration technique is discussed. Results concerning the PEACE parameter optimization program are given along with recommendations and conclusions.

Powers, W. F.↗
NASA NTRS1981

A unique integrated flight testing facility for advanced control/display research

NASA is engaged in programs aimed at developing avionic concepts and systems technology for air transportation systems of the 1980's and beyond. A part of these programs is related to the development of advanced concepts and avionics technology for integrated displays and controls. In support of these efforts an interactive Flight Display Research System (FDRS) has been developed as an integral part of integrated flight test facilities which have been used in evaluation studies of integrated display and control concepts in support of a VTOL Approach and Landing Technology (VALT) program and current Terminal Configured Vehicle (TCV) program. A description is provided of several of the advanced integrated display and control concepts that have evolved within the VALT, TCV, and general aviation programs, as well as the integrated flight test facilities.

Batson, V. M.↗
NASA NTRS1984

Highly integrated digital engine control system on an F-15 airplane

The Highly Integrated Digital Electronic Control (HIDEC) program will demonstrate and evaluate the improvements in performance and mission effectiveness that result from integrated engine/airframe control systems. This system is being used on the F-15 airplane. An integrated flightpath management mode and an integrated adaptive engine stall margin mode are implemented into the system. The adaptive stall margin mode is a highly integrated mode in which the airplane flight conditions, the resulting inlet distortion, and the engine stall margin are continuously computed; the excess stall margin is used to uptrim the engine for more thrust. The integrated flightpath management mode optimizes the flightpath and throttle setting to reach a desired flight condition. The increase in thrust and the improvement in airplane performance is discussed.

Burcham, F. W., Jr.↗
NASA NTRS1984

Highly integrated digital engine control system on an F-15 airplane

The highly integrated digital electronic control (HIDEC) program will demonstrate and evaluate the improvements in performance and mission effectiveness that result from integrated engine-airframe control systems. This system is being used on the F-15 airplane at the Dryden Flight Research Facility of NASA Ames Research Center. An integrated flightpath management mode and an integrated adaptive engine stall margin mode are being implemented into the system. The adaptive stall margin mode is a highly integrated mode in which the airplane flight conditions, the resulting inlet distortion, and the engine stall margin are continuously computed; the excess stall margin is used to uptrim the engine for more thrust. The integrated flightpath management mode optimizes the flightpath and throttle setting to reach a desired flight condition. The increase in thrust and the improvement in airplane performance is discussed in this paper.

Burcham, F. W., Jr.↗
NASA NTRS1986

Analytic evaluation of two-center molecular integrals

By using the Fourier-transform technique, the explicit expressions for the one-electron - two-center overlap integrals of Slater-type atomic orbitals up to 3d are derived. The final expressions are analytic, simple, and independent of local coordinates. Furthermore, they do not contain the nonclosed-form of exponential integrals which were presented in expressions given in earlier work. It is shown that the two-electron - two-center Coulomb integrals, as well as the hybrid integrals, can simply be expressed in terms of these integrals. The numerical instability arising from the situation in which the exponents of the two orbitals are almost equal is discussed, and a solution for this problem based on a Taylor-series expansion of the integral is suggested.

Tai, H.↗
NASA NTRS1988

Computational technique for compressible vortex flows using the integral equation solution

The steady full-potential equation is written in the form of Poisson's equation, and the solution for the velocity field is expressed in terms of an integral equation. The integral solution consists of two surface integrals and one volume integral. The solution is obtained through successive iteration cycles. Each cycle of iteration consists of two sub-cycles, an inner cycle for wake relaxation and an out cycle for the strength of the source distribution integrals representing the flow compressibility. The density gradients in the source distribution is computed by using a type-differencing scheme of the Murman-Cole type. The method is applied to delta wings and the numerical examples show that a curved shock is captured on the wing suction side beneath the leading edge vortex sheet. Recently, a modified version of the scheme was applied to rectangular wings. In this modified scheme, the surface integral terms were computed by using a bilinear distribution of vorticity on triangular vortex panels which represent the wing and its wake. The results were compared with the available experimental data and they are in good agreement.

Kandil, Osama A.↗
NASA NTRS1988

Space station integrated propulsion and fluid systems study. Space station program fluid management systems databook

Commonality and integration of propulsion and fluid systems associated with the Space Station elements are being evaluated. The Space Station elements consist of the core station, which includes habitation and laboratory modules, nodes, airlocks, and trusswork; and associated vehicles, platforms, experiments, and payloads. The program is being performed as two discrete tasks. Task 1 investigated the components of the Space Station architecture to determine the feasibility and practicality of commonality and integration among the various propulsion elements. This task was completed. Task 2 is examining integration and commonality among fluid systems which were identified by the Phase B Space Station contractors as being part of the initial operating capability (IOC) and growth Space Station architectures. Requirements and descriptions for reference fluid systems were compiled from Space Station documentation and other sources. The fluid systems being examined are: an experiment gas supply system, an oxygen/hydrogen supply system, an integrated water system, the integrated nitrogen system, and the integrated waste fluids system. Definitions and descriptions of alternate systems were developed, along with analyses and discussions of their benefits and detriments. This databook includes fluid systems descriptions, requirements, schematic diagrams, component lists, and discussions of the fluid systems. In addition, cost comparison are used in some cases to determine the optimum system for a specific task.

Bicknell, B.↗