Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “conflicts”

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 1,585 records · Page 88

Crew collaboration in space: a naturalistic decision-making perspective

Successful long-duration space missions will depend on the ability of crewmembers to respond promptly and effectively to unanticipated problems that arise under highly stressful conditions. Naturalistic decision making (NDM) exploits the knowledge and experience of decision makers in meaningful work domains, especially complex sociotechnical systems, including aviation and space. Decision making in these ambiguous, dynamic, high-risk environments is a complex task that involves defining the nature of the problem and crafting a response to achieve one's goals. Goal conflicts, time pressures, and uncertain outcomes may further complicate the process. This paper reviews theory and research pertaining to the NDM model and traces some of the implications for space crews and other groups that perform meaningful work in extreme environments. It concludes with specific recommendations for preparing exploration crews to use NDM effectively.

Review, Tutorial↗

Method and System For an Automated Tool for En Route Traffic Controllers

A method and system for a new automation tool for en route air traffic controllers first finds all aircraft flying on inefficient routes, then determines whether it is possible to save time by bypassing some route segments, and finally whether the improved route is free of conflicts with other aircraft. The method displays all direct-to eligible aircraft to an air traffic controller in a list sorted by highest time savings. By allowing the air traffic controller to easily identify and work with the highest pay-off aircraft, the method of the present invention contributes to a significant increase in both air traffic controller and aircraft productivity. A graphical computer interface (GUI) is used to enable the air traffic controller to send the aircraft direct to a waypoint or fix closer to the destination airport by a simple point and click action.

Heinz Erzberger↗

System Study: Technology Assessment and Prioritizing

The objective of this NASA funded project is to assess and prioritize advanced technologies required to achieve the goals for an "Intelligent Propulsion System" through collaboration among GEAE, NASA, and Georgia Tech. Key GEAE deliverables are parametric response surface equations (RSE's) relating technology features to system benefits (sfc, weight, fuel burn, design range, acoustics, emission, etc...) and listings of Technology Impact Matrix (TIM) with benefits, debits, and approximate readiness status. TIM has been completed for GEAE and NASA proposed technologies. The combined GEAE and NASA TIM input requirement is shown in Table.1. In the course of building the RSE's and TIM, significant parametric technology modeling and RSE accuracy improvements were accomplished. GEAE has also done preliminary ranking of the technologies using Georgia Tech/GEAE USA developed technology evaluation tools. System level impact was performed by combining beneficial technologies with minimum conflict among various system figures of merits to assess their overall benefits to the system. The shortfalls and issues with modeling the proposed technologies are identified, and recommendations for future work are also proposed.

Source record↗

Space Shuttle Hot Cabin Emergency Responses

Methods: Human thermal tolerance, countermeasures, and thermal model data were reviewed and compared to existing shuttle ECS failure temperature and humidity profiles for each failure mode. Increases in core temperature associated with cognitive impairment was identified, as was metabolic heat generation of crewmembers, temperature monitoring, and communication capabilities after partial power-down and other limiting factors. Orbiter landing strategies and a hydration and salt replacement protocol were developed to put wheels on deck in each failure mode prior to development of significant cognitive impairment or collapse of crewmembers. Thermal tradeoffs for use of the Advanced Crew Escape Suit (ACES), Liquid Cooling Garment, integrated G-suit and Quick Don Mask were examined. candidate solutions involved trade-offs or conflicts with cabin oxygen partial pressure limits, system power-downs to limit heat generation, risks of alternate and emergency landing sites or compromise of Mode V-VIII scenarios. Results: Rehydration and minimized cabin workloads are required in all failure modes. Temperature/humidity profiles increase rapidly in two failure modes, and deorbit is recommended without the ACES, ICU and g-suit. This latter configuration limits several shuttle approach and landing escape modes and requires communication modifications. Additional data requirements were identified and engineering simulations were recommended to develop more current shuttle temperature and humidity profiles. Discussion: After failure of the shuttle ECS, there is insufficient cooling capacity of the ACES to protect crewmembers from rising cabin temperature and humidity. The LCG is inadequate for cabin temperatures above 76 F. Current shuttle future life policy makes it unlikely that major engineering upgrades necessary to address this problem will occur.

Stepaniak, P.↗

Human Factors in Space Flight

After forty years of experience with human space flight (Table 1), the current emphasis is on the design of space vehicles, habitats, and missions to ensure mission success. What lessons have we learned that will affect the design of spacecraft for future space exploration, leading up to exploring Mars? This chapter addresses this issue in four sections: Anthropometry and Biomechanics; Environmental Factors; Habitability and Architecture; and Crew Personal Sustenance. This introductory section introduces factors unique to space flight. A unique consideration for design of a habitable volume in a space vehicle is the lack of gravity during a space flight, referred to as microgravity. This affects all aspects of life, and drives special features in the habitat, equipment, tools, and procedures. The difference in gravity during a space mission requires designing for posture and motion differences. In Earth s gravity, or even with partial gravity, orientation is not a variable because the direction in which gravity acts defines up and down. In a microgravity environment the working position is arbitrary; there is no gravity cue. Orientation is defined primarily through visual cues. The orientation within a particular crew station or work area is referred to as local vertical, and should be consistent within a module to increase crew productivity. Equipment was intentionally arranged in various orientations in one module on Skylab to assess the efficiency in use of space versus the effects of inconsistent layout. The effects of that arrangement were confusion on entering the module, time spent in re-orientation, and conflicts in crew space requirements when multiple crew members were in the module. Design of a space vehicle is constrained by the three major mission drivers: mass, volume and power. Each of these factors drives the cost of a mission. Mass and volume determine the size of the launch vehicle directly; they can limit consumables such as air, water, and propellant; and they impact crew size and the types of activities the crew performs. Power is a limiting factor for a space vehicle. All environmental features (e.g., atmosphere, temperature, lighting) require power to maintain them. Power can be generated from batteries, from fuel cells, or from solar panels. Each of these sources requires lifting mass and volume from Earth, driving mission cost. All engineering decisions directly impact the design for habitation design and usage. For instance, if fuel cells are used they produce water, which is used for drinking and food preparation. If a different power source is used water has to be carried and stored on the vehicle which then directly impacts the food system choice as well as the launch weight of the vehicle.

Woolford, Barbara J.↗

Towards Robust Designs Via Multiple-Objective Optimization Methods

Fabricating and operating complex systems involves dealing with uncertainty in the relevant variables. In the case of aircraft, flow conditions are subject to change during operation. Efficiency and engine noise may be different from the expected values because of manufacturing tolerances and normal wear and tear. Engine components may have a shorter life than expected because of manufacturing tolerances. In spite of the important effect of operating- and manufacturing-uncertainty on the performance and expected life of the component or system, traditional aerodynamic shape optimization has focused on obtaining the best design given a set of deterministic flow conditions. Clearly it is important to both maintain near-optimal performance levels at off-design operating conditions, and, ensure that performance does not degrade appreciably when the component shape differs from the optimal shape due to manufacturing tolerances and normal wear and tear. These requirements naturally lead to the idea of robust optimal design wherein the concept of robustness to various perturbations is built into the design optimization procedure. The basic ideas involved in robust optimal design will be included in this lecture. The imposition of the additional requirement of robustness results in a multiple-objective optimization problem requiring appropriate solution procedures. Typically the costs associated with multiple-objective optimization are substantial. Therefore efficient multiple-objective optimization procedures are crucial to the rapid deployment of the principles of robust design in industry. Hence the companion set of lecture notes (Single- and Multiple-Objective Optimization with Differential Evolution and Neural Networks ) deals with methodology for solving multiple-objective Optimization problems efficiently, reliably and with little user intervention. Applications of the methodologies presented in the companion lecture to robust design will be included here. The evolutionary method (DE) is first used to solve a relatively difficult problem in extended surface heat transfer wherein optimal fin geometries are obtained for different safe operating base temperatures. The objective of maximizing the safe operating base temperature range is in direct conflict with the objective of maximizing fin heat transfer. This problem is a good example of achieving robustness in the context of changing operating conditions. The evolutionary method is then used to design a turbine airfoil; the two objectives being reduced sensitivity of the pressure distribution to small changes in the airfoil shape and the maximization of the trailing edge wedge angle with the consequent increase in airfoil thickness and strength. This is a relevant example of achieving robustness to manufacturing tolerances and wear and tear in the presence of other objectives.

Man Mohan, Rai↗

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and Their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative a requirement to standardize and control the naming conventions of very disparate systems and technologies are emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation Initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation Initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and birds of a feather activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another

Bradford, Robert N.↗

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative, a requirement to standardize and control the naming conventions of very disparate systems and technologies is emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and Birds of a Feather (BoF) activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another standards body or technologies that are currently not standardized. For activities one through three, we will provide the analysis by either discipline or technology with rationale, identification and brief description of requirements and precedence. For activity four, we will provide a list of current standards bodies e.g. IETF and a list of potential candidates.

Bradford, Robert N.↗

Analysis and training - why different?

It is tempting to seek universal combat simulations, optimized for both analysis and training. Such a quest would be quixotic, however, because the two environments place conflicting requirements.

simulation modeling training analysis↗

A simple protocol for coordinating planning agents

This paper introduces a simple decentralized protocol that enables seperate planners to coordinate shared tasks and resolve conflicts over shared and private resources.

multiple agents coordination planning scheduling M↗

Coordination of Distributed Fuzzy Behaviors in Mobile Robot Control

This presentation describes an approach to behavior coordination and conflict resolution within the context of a hierarchical architecture of fuzzy behaviors. Coordination is achieved using weighted decision-making based on behavioral degrees of applicability. This strategy is appropriate for fuzzy control of systems that can be represented by hierarchical or decentralized structures.

Robotics Robot Navigation Fuzzy Logic Control Syst↗

(abstract) Science-Project Interaction in the Low-Cost Mission

Large, complex, and highly optimized missions have performed most of the preliminary reconnaisance of the solar system. As a result we have now mapped significant fractions of its total surface (or surface-equivalent) area. Now, however, scientific exploration of the solar system is undergoing a major change in scale, and existing missions find it necessary to limit costs while fulfilling existing goals. In the future, NASA's Discovery program will continue the reconnaisance, exploration, and diagnostic phases of planetary research using lower cost missions, which will include lower cost mission operations systems (MOS). Historically, one of the more expensive functions of MOS has been its interaction with the science community. Traditional MOS elements that this interaction have embraced include mission planning, science (and engineering) event conflict resolution, sequence optimization and integration, data production (e.g., assembly, enhancement, quality assurance, documentation, archive), and other science support services. In the past, the payoff from these efforts has been that use of mission resources has been highly optimized, constraining resources have been generally completely consumed, and data products have been accurate and well documented. But because these functions are expensive we are now challenged to reduce their cost while preserving the benefits. In this paper, we will consider ways of revising the traditional MOS approach that might save project resources while retaining a high degree of service to the Projects' customers. Pre-launch, science interaction can be made simplier by limiting numbers of instruments and by providing greater redundancy in mission plans. Post launch, possibilities include prioritizing data collection into a few categories, easing requirements on real-time of quick-look data delivery, and closer integration of scientists into the mission operation.

mission operation science community interaction co↗

Key ingredients needed when building large data processing systems for scientists

Why is building a large science software system so painful? Weren't teams of software engineers supposed to make life easier for scientists? Does it sometimes feel as if it would be easier to write the million lines of code in Fortran 77 yourself? The cause of this dissatisfaction is that many of the needs of the science customer remain hidden in discussions with software engineers until after a system has already been built. In fact, many of the hidden needs of the science customer conflict with stated needs and are therefore very difficult to meet unless they are addressed from the outset in a system's architectural requirements. What's missing is the consideration of a small set of key software properties in initial agreements about the requirements, the design and the cost of the system.

Earth Observing System EOS↗

Cassini science planning process

The mission design for Cassini-Huygens calls for a four-year orbital survey of the Saturnian system and the descent into the Titan atmosphere and eventual soft-landing of the Huygens probe. The Cassini orbiter tour consists of 76 orbits around Saturn with 44 close Titan flybys and 8 targeted icy satellite flybys. The Cassini orbiter spacecraft carries twelve scientific instruments that will perform a wide range of observations on a multitude of designated targets. The science opportunities, frequency of encounters, the length of the Tour, and the use of distributed operations pose significant challenges for developing the science plan for the orbiter mission. The Cassini Science Planning Process is the process used to develop and integrate the science and engineering plan that incorporates an acceptable level of science required to meet the primary mission objectives far the orbiter. The bulk of the integrated science and engineering plan will be developed prior to Saturn Orbit Insertion (Sol). The Science Planning Process consists of three elements: 1) the creation of the Tour Atlas, which identifies the science opportunities in the tour, 2) the development of the Science Operations Plan (SOP), which is the conflict-free timeline of all science observations and engineering activities, a constraint-checked spacecraft pointing profile, and data volume allocations to the science instruments, and 3) an Aftermarket and SOP Update process, which is used to update the SOP while in tour with the latest information on spacecraft performance, science opportunities, and ephemerides. This paper will discuss the various elements of the Science Planning Process used on the Cassini Mission to integrate, implement, and adapt the science and engineering activity plans for Tour.

Cassini↗

E-Scheduling the Deep Space Network

This paper describes an operations concept for electronic scheduling and software interface for organizations to extract required views of the schedule. Advantages include widespread accessibility to a common schedule document, virtually instantaneous distribution of new schedule releases, and the ability of missions to perfom conflict resolution off-line without time-consuming meetings.

telecommunications↗

New high performance algorithmic solution for diagnosis problem

In this paper we address the problem of generating the minimal diagnosis from the conflicts. This problem can be formulated as the well-known Hitting Set Problem. Our approach starts by mapping the Hitting Set problem into the Integer Programming Problem that enables us, for the first time, a priori determination of the lower and upper bounds on the size for the solution. Based on these bounds, we introduce a new concept of solution window for the problem. We also propose a new branch-and-bound technique that not only is faster than the current techniques in terms of number of operations (by exploiting the structure of the problem) but also, using the concept of window, allows a massive reduction (pruning) in the number of branches. Furthermore, as the branch-and-bound proceeds, the solution window is dynamically updated and narrowed to enable further pruning.

diagnosis problems↗

Biomedical Aspects of Lunar and Mars Exploration Missions

Recent long-range planning for exploration-class missions has emphasized the need for anticipating the medical and human factors aspects of such expeditions. Missions returning Americans to the moon for stays of up to 6 months at a time will provide the opportunity to demonstrate the means to function safely and efficiently on another planet. Details of mission architectures are still under study, but a typical Mars design reference mission comprises a six-month transit from Earth to Mars, eighteen months in residence on Mars, and a six-month transit back to Earth. Physiological stresses will come from environmental factors such as prolonged exposure to radiation, weightlessness en route to Mars and then back to Earth, and low gravity and a toxic atmosphere while on Mars. Psychological stressors will include remoteness from Earth, confinement, and potential interpersonal conflicts, all complicated by circadian alterations. Medical risks including trauma must be considered. The role of such risk-modifying influences as artificial gravity and improved propulsion technologies to shorten round-trip time will also be discussed. Results of planning for assuring human health and performance will be presented.

Charles, John B.↗

A Low Cost Spacecraft Architecture for Robotic Lunar Exploration Projects

A program of frequent, capable, but affordable lunar robotic missions prior to return of humans to the moon can contribute to the Vision for Space Exploration (VSE) NASA is tasked to execute. The Lunar Reconnaissance Orbiter (LRO) and its secondary payload are scheduled to orbit the moon, and impact it, respectively, in 2008. It is expected that the sequence of missions occurring for approximately the decade after 2008 will place an increasing emphasis on soft landed payloads. These missions are requited to explore intrinsic characteristics of the moon, such as hydrogen distribution in the regolith, and levitated dust, to demonstrate the ability to access and process in-situ resources, and to demonstrate functions critical to supporting human presence, such as automated precision navigation and landing. Additional factors governing the design of spacecraft to accomplish this diverse set of objectives are: operating within a relatively modest funding profile, the need tb visit multiple sites (both polar and equatorial) repeatedly, and to use the current generation of launch vehicles. In the US, this implies use of the Evolved Expendable Launch Vehicles, or EELVs, although this design philosophy may be extended to launch vehicles of other nations, as well. Many of these factors are seemingly inconsistent with each other. For example, the cost of a spacecraft usually increases with mass; therefore the desire to fly frequent, modestly priced spacecraft seems to imply small spacecraft (< 1 Mt, injected mass). On the other hand, the smallest of the EELVs will inject approx. 3 Mt. on a Trans Lunar Injection (TLI) trajectory md would therefore be wasteful or launching a single, small spacecraft. Increasing the technical capability of a spacecraft (such as autonomous navigation and soft landing) also usually increases cost. A strategy for spacecraft design that meets these conflicting requirements is presented. Taken together, spacecraft structure and propulsion subsystems constitute the majority of spacecraft mass; saving development and integration cost on these elements is critical to controlling cost. Therefore, a low cost, modular design for spacecraft structure and propulsion subsystems is presented which may be easily scaled up or down for either insertion into lunar orbit or braking for landing on the lunar surface. In order to effectively use the approx.3 Mt mass-to-TLI of the EELV, two low cost spacecraft will be manifested on the same launch. One spacecraft will be located on top of the other for launch and the two will have to be released in sequence in order to achieve all mission objectives. The two spacecraft could both be landers, both orbiters, or one lander and one orbiter. In order to achieve mass efficiency, the body of the spacecraft will serve the dual purposes of carrying launch loads and providing attachment points for all the spacecraft subsystems. In order to avoid unaffordable technology development costs, small liquid propulsion components and autonomous, scene-matching navigation cameras may be adapted from military missile programs in order to execute precision soft landings.

Lemke, Lawrence G.↗