SEARCH · Search NASA
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.
Descriptive model of system development activities and man machine systems for determining optimal human performance in aerospace systems
The Phase 1 DAA Minimum Operational Performance Standards (MOPS) provided requirements for two classes of DAA equipment: equipment Class 1 contains the basic DAA equipment required to assist a pilot in remaining well clear, while equipment Class 2 integrates the Traffic Alert and Collision Avoidance (TCAS) II system. Thus, the Class 1 system provides RWC functionality only, while the Class 2 system is intended to provide both RWC and Collision Avoidance (CA) functionality, in compliance with the Minimum Aviation System Performance (MASPS) for the Interoperability of Airborne Collision Avoidance Systems. The FAAs TCAS Program Office is currently developing Airborne Collision Avoidance System X (ACAS X) to support the objectives of the Federal Aviation Administrations (FAA) Next Generation Air Transportation System Program (NextGen). ACAS X has a suite of variants with a common underlying design that are intended to be optimized for their intended airframes and operations. ACAS Xu being is designed for UAS and allows for new surveillance technologies and tailored logic for platforms with different performance characteristics. In addition to Collision Avoidance (CA) alerting and guidance, ACAS Xu is being tuned to provide RWC alerting and guidance in compliance with the SC 228 DAA MOPS. With a single logic performing both RWC and CA functions, ACAS Xu will provide industry with an integrated DAA solution that addresses many of the interoperability shortcomings of Phase I systems. While the MOPS for ACAS Xu will specify an integrated DAA system, it will need to show compliance with the RWC alerting thresholds and alerting requirements defined in the DAA Phase 2 MOPS. Further, some functional components of the ACAS Xu system such as the remote pilots displayed guidance might be mostly references to the corresponding requirements in the DAA MOPS. To provide a seamless, integrated, RWC-CA system to assist the pilot in remaining well clear and avoiding collisions, several issues need to be addressed within the Phase 2 SC-228 DAA efforts. Interoperability of the RWC and CA alerting and guidance, and ensuring pilot comprehension, compliance and performance, will be a primary research area.
Project Constellation implements NASA's vision for space exploration to expand human presence in our solar system. The engineering focus of this project is developing a system of systems architecture. This architecture allows for the incremental development of the overall program. Systems can be built and connected in a "Lego style" manner to generate configurations supporting various mission objectives. The development of the avionics or control systems of such a massive project will result in concurrent engineering. Also, each system will have software and the need to communicate with other (possibly heterogeneous) systems. Fortunately, this design problem has already been solved during the creation and evolution of systems such as the Internet and the Department of Defense's successful effort to standardize distributed simulation (now IEEE 1516). The solution relies on the use of a standard layered software framework and a communication protocol. A standard framework and communication protocol is suggested for the development and maintenance of Project Constellation systems. The ARINC 653 standard is a great start for such a common software framework. This paper proposes a common system software framework that uses the Real Time Publish/Subscribe protocol for framework-to-framework communication to extend ARINC 653. It is highly recommended that such a framework be established before development. This is important for the success of concurrent engineering. The framework provides an infrastructure for general system services and is designed for flexibility to support a spiral development effort.
Explore the source record for details and available documents.
The Earth Observer System (EOS) was officially established in 1990 and went operational in December 1999 with the launch of its flagship spacecraft Terra. Aqua followed in 2002 and Aura in 2004. All three spacecraft are still operational and producing valuable scientific data. While all are beyond their original design lifetime, they are expected to remain viable well into the 2020s. The EOS Ground System is a multi-mission system based at NASA Goddard Space Flight Center that supports science and spacecraft operations for these three missions. Over its operational lifetime to date, the EOS Ground System has evolved as needed to accommodate mission requirements. With an eye towards the future, several updates are currently being deployed. Subsystem interconnects are being upgraded to reduce data latency and improve system performance. End-of-life hardware and operating systems are being replaced to mitigate security concerns and eliminate vendor support gaps. Subsystem hardware is being consolidated through the migration to Virtual Machine based platforms. While mission operations autonomy was not a design goal of the original system concept, there is an active effort to apply state-of-the-art products from the Goddard Mission Services Evolution Center (GMSEC) to facilitate automation where possible within the existing heritage architecture. This presentation will provide background information on the EOS ground system architecture and evolution, discuss latest improvements, and conclude with the results of a recent effort that investigated how the current system could accommodate a proposed new earth science mission.
A Bioregenerative Life Support Test Complex, BIO-Plex, is currently being constructed at the Johnson Space Center (JSC) in Houston, TX. This facility will attempt to answer the questions involved in developing a lunar or planetary base. The Food Processing System (FPS) of the BIO-Plex is responsible for supplying food to the crew in coordination with the chosen mission scenario. Long duration space missions require development of both a Transit Food System and of a Lunar or Planetary Food System. These two systems are intrinsically different since the first one will be utilized in the transit vehicle in microgravity conditions with mostly resupplied foods, while the second will be used in conditions of partial gravity (hypogravity) to process foods from crops grown in the facility. The Transit Food System will consist of prepackaged food of extended shelf life. It will be supplemented with salad crops that will be consumed fresh. Microgravity imposes significant limitation on the ability to handle food and allows only for minimal processing. The challenge is to develop food systems similar to the International Space Station or Shuttle Food Systems but with a shelf life of 3 - 5 years. The Lunar or Planetary Food System will allow for food processing of crops due to the presence of some gravitational force (1/6 to 1/3 that of Earth). Crops such as wheat, soybean, rice, potato, peanut, and salad crops, will be processed to final products to provide a nutritious and acceptable diet for the crew. Not only are constraints imposed on the FPS from the crops (e.g., crop variation, availability, storage and shelf-life) but also significant requirements are present for the crew meals (e.g., RDA, high quality, safety, variety). The FPS becomes a fulcrum creating the right connection from crops to crew meals while dealing with issues of integration within a closed self-regenerative system (e.g., safe processing, waste production, volumes, air contaminations, water usage, etc.). Options for the first test, for duration of 120 days, currently scheduled for late 2003 are outlined.
The key objectives of the NASA ASP are to: Improve mobility, capacity efficiency and access of the airspace system. Improve collaboration, predictability, and flexibility for the airspace users. Enable accurate modeling and simulation of air transportation systems. Accommodate operations of all classes of aircraft. Maintain system safety and environmental protection. In support of these program objectives, the major goal of the NextGen-SAIE Project is to enable the transition of key capacity and efficiency improvements to the NAS. Since many aspects of the NAS are unique to specific airport or airspace environments, demand on various parts of the NAS is not expected to increase equally as system demand grows. SAIE will provide systems level analysis of the NAS characteristics, constraints, and demands such that a suite of capacity-increasing concepts and technologies for system solutions are enabled and facilitated. The technical objectives in support of this goal are the following: Integration, evaluation, and transition of more mature concepts and technologies in an environment that faithfully emulates real-world complexities. Interoperability research and analysis of ASP technologies across ATM functions is performed to facilitate integration and take ASP concepts and technologies to higher Technology Readiness Level (TRL). Analyses are conducted on the program s concepts to identify the system benefits or impacts. System level analysis is conducted to increase understanding of the characteristics and constraints of airspace system and its domains.
Current engineering practice in the analysis and design of large-scale multi-disciplinary control systems is typified by some form of decomposition- whether functional or physical or discipline-based-that enables multiple teams to work in parallel and in relative isolation. Too often, the resulting system after integration is an awkward marriage of different control and data mechanisms with poor end-to-end accountability. System of systems engineering, which faces this problem on a large scale, cries out for a unifying framework to guide analysis, design, and operation. This paper describes such a framework based on a state-, model-, and goal-based architecture for semi-autonomous control systems that guides analysis and modeling, shapes control system software design, and directly specifies operational intent. This paper illustrates the key concepts in the context of a large-scale, concurrent, globally distributed system of systems: NASA's proposed Array-based Deep Space Network.
Data Systems Dynamic Simulation is a simulation system designed to reduce cost and time and increase the confidence and comprehensiveness of Data Systems Simulation. It is designed to simulate large data processing and communications systems from end-to-end or by subsystem. Those features relevant to system timing, control, sizing, personnel support activities, cost and external influences are modeled. Emphasis is placed on ease of use, comprehensive system performance measures, and extensive post simulation analysis capability. The system has been used to support trade studies of the NASA data system needs in the 1985 to 1990 time frame.
The International Space Station (ISS) Internal Active Thermal Control System (IATCS) experienced a number of chemical changes driven by system absorption of CO2 which altered the coolant’s pH. The natural effects of the decrease in pH from approximately 9.2 to less than 8.4 had immediate consequences on system corrosion rates and corrosion product interactions with specified coolant constituents. The alkalinity of the system was increased through the development and implementation of a carbonate/bicarbonate buffer that would increase coolant pH to 9.0 – 10.0 and maintain pH above 9.0 in the presence of ISS cabin concentrations of CO2 up to twenty times higher than ground concentrations. This paper defines how a carbonate/bicarbonate buffer works in an open carbon dioxide system and summarizes the analyses performed on the buffer for safe and effective application in the on-orbit system. The importance of the relationship between the cabin environment and the IATCS is demonstrated as the dominant factor in understanding the system chemistry and pH trends before and after addition of the carbonate/bicarbonate buffer. The paper also documents the corollary electrochemical and chemical reactions the system has experienced and the rationale for remediation of these effects with the addition of the carbonate/bicarbonate buffer.
The performance of the thermal protection system, field joint protection system, and systems tunnel components of flight set 360L007 is presented as evaluated by postflight hardware inspection. The condition of both motors was similar to previous flights. Four aft edge strikes were noted on the ground environment instrumentation thermal protection system. The hits all left a clean substrate, indicating that the damage was caused by nozzle severance debris and/or water impact. No National Space Transportation System debris criteria for missing thermal protection system were violated. Two problem reports were written against the field joint protection system. The first concerned two cracks in the K5NA closeout over the trunnion/vent valve location on the left-hand aft field joint. A similar condition was observed on Flight 5 (360H005). The second problem report referred to a number of small surface cracks between two impact marks on the left-hand forward field joint. Neither area exhibited loose material or any abnormal heat effects, and they have no impact on flight safety.
The performance of the thermal protection system, field joint protection system, and systems tunnel components of Flight Set 360L006, are documented, as evaluated by postflight hardware inspection. The condition of both motors was similar to previous flights. Sixteen aft edge hits were noted on the ground environment instrumentation thermal protection system. Each hit left a clean substrate, indicating that the damage was caused by nozzle severance debris and/or water impact. No National Space and Transporation System debris criteria for missing thermal protection system were violated. One 5.0 by 1.0 in. unbond was observed on the left hand center field joint K5NA closeout and was elevated to an in-flight anomaly (STS-34-M-4) by the NASA Ice/Debris team. Aft edge damage to the K5NA and an associated black streak indicate that burning debris from the nozzle severance system was the likely cause of the damage. Minor divots caused by debris were seen on previous flights, but this is the first occurrence of a K5NA unbond. Since the unbond occurred after booster separation there is no impact on flight safety and no corrective actions was taken. The right hand center field joint primary heater failed the dielectric withstanding voltage test after joint closeout. The heater was then disabled by opening the circuit breaker, and the redundant heater was used. The redundant heater performed nominally during the launch countdown. A similar condition occurred on Flight 4 when a secondary joint heater failed the dielectric withstanding voltage test.
The present invention relates to an Inductive Monitoring System (IMS), its software implementations, hardware embodiments and applications. Training data is received, typically nominal system data acquired from sensors in normally operating systems or from detailed system simulations. The training data is formed into vectors that are used to generate a knowledge database having clusters of nominal operating regions therein. IMS monitors a system's performance or health by comparing cluster parameters in the knowledge database with incoming sensor data from a monitored-system formed into vectors. Nominal performance is concluded when a monitored-system vector is determined to lie within a nominal operating region cluster or lies sufficiently close to a such a cluster as determined by a threshold value and a distance metric. Some embodiments of IMS include cluster indexing and retrieval methods that increase the execution speed of IMS.
A system baseline design oriented to the requirements of the next generation of Earth Observatory Satellite missions is presented. The first mission (EOS-A) is envisioned as a two-fold mission which (1) provides a continuum of data of the type being supplied by ERTS for the emerging operational applications and also (2) expands the research and development activities for future instrumentation and analysis techniques. The baseline system specifically satisfies the requirements of this first mission. However, EOS-A is expected to be the first of a series of earth observation missions. Thus the baseline design has been developed so as to accommodate these latter missions effectively as the transition is made from conventional, expendable launch vehicles and spacecraft to the Shuttle Space Transportation System era. Further, a subset of alternative missions requirements including Seasat, SEOS, SMM and MSS-5 have been analyzed to verify that the spacecraft design to serve a multi-mission role is economically sound. A key feature of the baseline system design is the concept of a modular observatory system whose elements are compatible with varying levels of launch vehicle capability. The design configuration can be used with either the Delta or Titan launch vehicles and will adapt readily to the space shuttle when that system becomes available in the early 1980's.
The technical and economic feasibility of a solar electric power plant for a small community is evaluated and specific system designs for development and demonstration are selected. All systems investigated are defined as point focusing, distributed receiver concepts, with energy conversion at the collector. The preferred system is comprised of multiple parabolic dish concentrators employing Stirling cycle engines for power conversion. The engine, AC generator, cavity receiver, and integral sodium pool boiler/heat transport system are combined in a single package and mounted at the focus of each concentrator. The output of each concentrator is collected by a conventional electrical distribution system which permits grid-connected or stand-alone operation, depending on the storage system selected.
A mission-systems architecture based on a highly modular "systems of systems" infrastructure utilizing open-standards hardware and software interfaces as the enabling technology is absolutely essential for an affordable and sustainable space exploration program. This architecture requires (a) robust communication between heterogeneous systems, (b) high reliability, (c) minimal mission-to-mission reconfiguration, (d) affordable development, system integration, and verification of systems, and (e) minimum sustaining engineering. This paper proposes such an architecture. Lessons learned from the space shuttle program are applied to help define and refine the model.
A preliminary study has been made of the navigation performance which might be achieved for the high cross-range space shuttle orbiter during final approach and landing by using an optimally augmented inertial navigation system. Computed navigation accuracies are presented for an on-board inertial navigation system augmented (by means of an optimal filter algorithm) with data from two different ground navigation aids; a precision ranging system and a microwave scanning beam landing guidance system. These results show that augmentation with either type of ground navigation aid is capable of providing a navigation performance at touchdown which should be adequate for the space shuttle. In addition, adequate navigation performance for space shuttle landing is obtainable from the precision ranging system even with a complete dropout of precision range measurements as much as 100 seconds before touchdown.
The objectives of the Earth Observatory Satellite (EOS) program are defined. The system specifications for the satellite payload are examined. The broad objectives of the EOS-A program are as follows: (1) to develop space-borne sensors for the measurement of land resources, (2) to evolve spacecraft systems and subsystems which will permit earth observation with greater accuracy, coverage, spatial resolution, and continuity than existing systems, (3) to develop improved information processing, extraction, display, and distribution systems, and (4) to use space transportation systems for resupply and retrieval of the EOS.