Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operations coordination plan”

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 217 records · Page 12

LUMIS: Land Use Management and Information Systems; coordinate oriented program documentation

An integrated geographic information system to assist program managers and planning groups in metropolitan regions is presented. The series of computer software programs and procedures involved in data base construction uses the census DIME file and point-in-polygon architectures. The system is described in two parts: (1) instructions to operators with regard to digitizing and editing procedures, and (2) application of data base construction algorithms to achieve map registration, assure the topological integrity of polygon files, and tabulate land use acreages within administrative districts.

Source record↗

Magnetospheric Multiscale (MMS) Mission Attitude Ground System Design

This paper describes the attitude ground system (AGS) design to be used for support of the Magnetospheric MultiScale (MMS) mission. The AGS exists as one component of the mission operations control center. It has responsibility for validating the onboard attitude and accelerometer bias estimates, calibrating the attitude sensors and the spacecraft inertia tensor, and generating a definitive attitude history for use by the science teams. NASA's Goddard Space Flight Center (GSFC) in Greenbelt, Maryland is responsible for developing the MMS spacecraft, for the overall management of the MMS mission, and for mission operations. MMS is scheduled for launch in 2014 for a planned two-year mission. The MMS mission consists of four identical spacecraft flying in a tetrahedral formation in an eccentric Earth orbit. The relatively tight formation, ranging from 10 to 400 km, will provide coordinated observations giving insight into small-scale magnetic field reconnection processes. By varying the size of the tetrahedron and the orbital semi-major axis and eccentricity, and making use of the changing solar phase, this geometry allows for the study of both bow shock and magnetotail plasma physics, including acceleration, reconnection, and turbulence. The mission divides into two phases for science; these phases will have orbit dimensions of 1.2 x 12 Earth radii in the first phase and 1.2x25 Earth radii in the second in order to study the dayside magnetopause and the nightside magnetotail, respectively. The orbital periods are roughly one day and three days for the two mission phases. Each of the four MMS spacecraft will be spin stabilized at 3 revolutions per minute (rpm), with the spin axis oriented near the ecliptic north pole but tipped approximately 2.5 deg towards the Sun line. The main body of each spacecraft will be an eight-sided platform with diameter of 3.4 m and height of 1.2 m. Several booms are attached to this central core: two axial booms of 14.9 m length, two radial magnetometer booms of 5 m length, and four radial wire booms of 60 m length. Attitude and orbit control will use a set of axial and radial thrusters. A four-head star tracker and a slit-type digital Sun sensor (DSS) provide input for attitude determination. In addition, an accelerometer will be used for closed-loop orbit maneuver control. The primary AGS product will be a daily definitive attitude history. Due to power limitations, the star tracker and accelerometer data will not be available at all times. However, tracker data from at least 10 percent of each orbit and continuous DSS data will be provided. An extended Kalman filter (EKF) will be used to estimate the three-axis attitude (i.e., spin axis orientation and spin phase) and rotation rate for all times when the tracker data is valid. For other times, the attitude is generated by assuming a constant angular momentum vector in the inertial frame. The DSS sun pulse will provide a timing signal to maintain an accurate spin phase. There will be times when the Sun is occulted and DSS data is not available. If this occurs at the start or end of a definitive attitude product, then the spin phase will be extrapolated using the mean rate determined by the EKF.

Sedlak, Joseph E.↗

Magnetospheric Multiscale (MMS) Mission Attitude Ground System Design

This paper describes the attitude ground system (AGS) design to be used for support of the Magnetospheric MultiScale (MMS) mission. The AGS exists as one component of the mission operations control center. It has responsibility for validating the onboard attitude and accelerometer bias estimates, calibrating the attitude sensors and the spacecraft inertia tensor, and generating a definitive attitude history for use by the science teams. NASA's Goddard Space Flight Center (GSFC) in Greenbelt, Maryland is responsible for developing the MMS spacecraft, for the overall management of the MMS mission, and for mission operations. MMS is scheduled for launch in 2014 for a planned two-year mission. The MMS mission consists of four identical spacecraft flying in a tetrahedral formation in an eccentric Earth orbit. The relatively tight formation, ranging from 10 to 400 km, will provide coordinated observations giving insight into small-scale magnetic field reconnection processes. By varying the size of the tetrahedron and the orbital semi-major axis and eccentricity, and making use of the changing solar phase, this geometry allows for the study of both bow shock and magnetotail plasma physics, including acceleration, reconnection, and turbulence. The mission divides into two phases for science; these phases will have orbit dimensions of l.2xl2 Earth radii in the first phase and l.2x25 Earth radii in the second in order to study the dayside magnetopause and the nightside magnetotail, respectively. The orbital periods are roughly one day and three days for the two mission phases. Each of the four MMS spacecraft will be spin stabilized at 3 revolutions per minute (rpm), with the spin axis oriented near the ecliptic north pole but tipped approximately 2.5 deg towards the Sun line. The main body of each spacecraft will be an eight-sided platform with diameter of 3.4 m and height of 1.2 m. Several booms are attached to this central core: two axial booms of 14.9 m length, two radial magnetometer booms of 5 m length, and four radial -wire booms of 60 m length. Attitude and orbit control will use a set of axial and radial thrusters. A four-head star tracker and a slit-type digital Sun sensor (DSS) provide input for attitude determination. In addition, an accelerometer will be· used for closed-loop orbit maneuver control. The primary AGS product will be a daily definitive attitude history. Due to power limitations; the star tracker and accelerometer data will not be available at all times. However, tracker data from at least 10 percent of each orbit and continuous DSS data will be provided. An extended Kalman filter (EKF) will be used to estimate the three-axis attitude (i.e., spin axis orientation and spin phase) and rotation rate for all times when the tracker data is valid. For other times, the attitude is generated by assuming a constant angular momentum vector in the inertial frame. The DSS sun pulse will provide a timing signal to maintain an accurate spin phase. There will be times when the Sun is occulted and DSS data is not available. If this occurs at the start or end of a definitive attitude product, then the spin phase will be extrapolated using the mean rate determined by the EKF.

Sedlak, Joseph E.↗

Analogs and the BHP Risk Reduction Strategy for Future Spaceflight Missions

In preparation for future exploration missions to distant destinations (e.g., Moon, Near Earth Objects (NEO), and Mars), the NASA Human Research Program s (HRP) Behavioral Health and Performance Element (BHP) conducts and supports research to address four human health risks: Risk of Behavioral Conditions; Risk of Psychiatric Conditions; Risk of Performance Decrements Due to Inadequate Cooperation, Coordination, Communication, and Psychosocial Adaptation within a Team; and Risk of Performance Errors due to Sleep Loss, Fatigue, Circadian Desynchronization, and Work Overload (HRP Science Management Plan, 2008). BHP Research, in collaboration with internal and external research investigators, as well as subject matter experts within NASA operations including flight surgeons, astronauts, and mission planners and others within the Mission Operations Directorate (MOD), identifies knowledge and technology gaps within each Risk. BHP Research subsequently manages and conducts research tasks to address and close the gaps, either through risk assessment and quantification, or the development of countermeasures and monitoring technologies. The resulting deliverables, in many instances, also support current Medical Operations and/or Mission Operations for the International Space Station (ISS).

Whitmire, Sandra↗

Simplifying operations with an uplink/downlink integration toolkit

The Operations Engineering Lab (OEL) at JPL has developed a simple, generic toolkit to integrate the uplink/downlink processes, (often called closing the loop), in JPL's Multimission Ground Data System. This toolkit provides capabilities for integrating telemetry verification points with predicted spacecraft commands and ground events in the Mission Sequence Of Events (SOE) document. In the JPL ground data system, the uplink processing functions and the downlink processing functions are separate subsystems that are not well integrated because of the nature of planetary missions with large one-way light times for spacecraft-to-ground communication. Our new closed-loop monitoring tool allows an analyst or mission controller to view and save uplink commands and ground events with their corresponding downlinked telemetry values regardless of the delay in downlink telemetry and without requiring real-time intervention by the user. An SOE document is a time-ordered list of all the planned ground and spacecraft events, including all commands, sequence loads, ground events, significant mission activities, spacecraft status, and resource allocations. The SOE document is generated by expansion and integration of spacecraft sequence files, ground station allocations, navigation files, and other ground event files. This SOE generation process has been automated within the OEL and includes a graphical, object-oriented SOE editor and real-time viewing tool running under X/Motif. The SOE toolkit was used as the framework for the integrated implementation. The SOE is used by flight engineers to coordinate their operations tasks, serving as a predict data set in ground operations and mission control. The closed-loop SOE toolkit allows simple, automated integration of predicted uplink events with correlated telemetry points in a single SOE document for on-screen viewing and archiving. It automatically interfaces with existing real-time or non real-time sources of information, to display actual values from the telemetry data stream. This toolkit was designed to greatly simplify the user's ability to access and view telemetry data, and also provide a means to view this data in the context of the commands and ground events that are used to interpret it. A closed-loop system can prove especially useful in small missions with limited resources requiring automated monitoring tools. This paper will discuss the toolkit implementation, including design trade-offs and future plans for enhancing the automated capabilities.

Murphy, Susan C.↗

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment↗

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment↗

General aviation IFR operational problems

Operational problems of general aviation IFR operators (particularly single pilot operators) were studied. Several statistical bases were assembled and utilized to identify the more serious problems and to demonstrate their magnitude. These bases include official activity projections, historical accident data and delay data, among others. The GA operating environment and cockpit environment were analyzed in detail. Solutions proposed for each of the problem areas identified are based on direct consideration of currently planned enhancements to the ATC system, and on a realistic assessment of the present and future limitations of general aviation avionics. A coordinated set of research program is suggested which would provide the developments necessary to implement the proposed solutions.

Bolz, E. H.↗

Communication Research in Aviation and Space Operations: Symptoms and Strategies of Crew Coordination

The day-to-day operators of today's aerospace systems work under increasing pressures to accomplish more with less. They work in operational systems which are complex, technology-based, and high-risk; in which incidents and accidents have far-reaching and costly consequences. For these and other reasons, there is concern that the safety net formerly built upon redundant systems and abundant resources may become overburdened. Although we know that human ingenuity can overcome incredible odds, human nature can also fail in unpredictable ways. Over the last 20 years, a large percentage of aviation accidents and incidents have been attributed to human errors rather than hardware or environmental factors alone. A class of errors have been identified which are not due to a lack of individual, technical competencies. Rather, they are due to the failure of teams to utilize readily available resources or information in a timely fashion. These insights began a training revolution in the aviation industry called Cockpit Resource Management, which later became known as Crew Resource Management (CRM) as its concepts and applications extended to teams beyond the flightdeck. Then, as now, communication has been a cornerstone in CRM training since crew coordination and resource management largely resides within information transfer processes--both within flightcrews, and between flightcrews and the ground operations teams that support them. The research I will describe takes its roots in CRM history as we began to study communication processes in order to discover symptoms of crew coordination problems, as well as strategies of effective crew management. On the one hand, communication is often the means or the tool by which team members manage their resources, solve problems, maintain situational awareness and procedural discipline. Conversely, it is the lack of planning and resource management, loss of vigilance and situational awareness, and non-standard communications that are implicated in accidents and incidents. NASA/Ames Crew Factors researchers have been developing a model of effective crew coordination in order to understand the sources of performance breakdowns, and to develop effective solutions and interventions. Because communication is a primary mechanism by which information is received and transmitted, and because it is observable behavior, we focus on these group processes in order to identify patterns of communication that distinguish effective from less effective crew performance. Since a prime objective is to develop training recommendations for enhancing communication skills, we interpret our findings in the context of relevant task and environmental conditions, role and procedural constraints, and the normal real-time parameters of flight operations. Another research objective is to consider how communication and coordination can be enhanced through design. For example, flight deck and hardware design as well as procedural and software design may greatly influence the efficiency with which crews communicate and coordinate their work. In addition, teams and tasks may be designed, organized, and trained so that team interactions with each other are based upon appropriately shared knowledge, procedures and situation awareness. In short, we are interested in enhancing communication practices through (1) the training of specific communication skills, and (2) the design of equipment, tasks, procedures, and teams that optimize smooth, unambiguous communication processes. Two examples of communication research will be described; one in aviation and one in space operations. The first example is a high-fidelity full mission simulation study which investigates the affect of flightdeck automation on crew coordination and communication (contrasting crew performance in the DC-9 vs. MD88). Additional information is contained in the original extended abstract.

Kanki, Barbara G.↗

Integrated Demand Management: Concepts and Procedures

This report provides a comprehensive description of the Integrated Demand Management concept. Motivation: NASA’s Integrated Demand Management (IDM) research explores the idea that, under certain conditions, time-based flow management (TBFM) arrival operations can benefit from the coordinated use of a strategic traffic management initiative (TMI) to “precondition” the inbound demand. The research was motivated by the observation that TBFM was usually turned off during convective weather, even in facilities where it was routinely used. Our hypothesis was that strategic adjustments to the inbound traffic so that it provided a better match to the off-nominal changes in capacity observed during these conditions could enable TBFM scheduling to continue to provide effective support for arrival traffic management. Concept: IDM proposes that a TMI (e.g., a Collaborative Trajectory Options Program, or CTOP) be used to adjust the rate and/or geographic distribution across flows of the traffic inbound to a high-demand, TBFM-managed airport before that traffic reaches the TBFM planning horizon. After this strategic preconditioning, TBFM can then tactically fine-tune the demand to deliver a well-managed, orderly feed to the destination airport. Coordinated use of these two flow management capabilities is intended to improve system performance in terms of: • Equity of ground delay assignment, avoiding excessive ground delay for TBFM-scheduled departures, without penalizing longer flights; • Throughput, by distributing traffic to maximize use of available capacity; • Predictability for operators, providing advance notice about the impact on individual flights; • Increased flexibility, supporting operator mitigation strategies such as slot swapping or trajectory options; • Efficiency of flight operations, using ground delay more effectively and reducing airborne delay. The operational description in this document highlights how the IDM concept builds upon already existing tools and procedures, and also indicates where tool enhancements could facilitate conduct of IDM operations. However, enhanced tools are not a requirement for concept introduction. In fact, initial deployment that focused on training procedures and rationale for coordinated use of TFMS and TBFM, without changes to existing tools, might be a simpler way to introduce and to familiarize traffic managers with the idea of preconditioning. The concept and procedures described in this document can hopefully provide useful guidance for introduction of IDM into field operations..

IDM↗

Systems Architecture for Fully Autonomous Space Missions

The NASA Goddard Space Flight Center is working to develop a revolutionary new system architecture concept in support of fully autonomous missions. As part of GSFC's contribution to the New Millenium Program (NMP) Space Technology 7 Autonomy and on-Board Processing (ST7-A) Concept Definition Study, the system incorporates the latest commercial Internet and software development ideas and extends them into NASA ground and space segment architectures. The unique challenges facing the exploration of remote and inaccessible locales and the need to incorporate corresponding autonomy technologies within reasonable cost necessitate the re-thinking of traditional mission architectures. A measure of the resiliency of this architecture in its application to a broad range of future autonomy missions will depend on its effectiveness in leveraging from commercial tools developed for the personal computer and Internet markets. Specialized test stations and supporting software come to past as spacecraft take advantage of the extensive tools and research investments of billion-dollar commercial ventures. The projected improvements of the Internet and supporting infrastructure go hand-in-hand with market pressures that provide continuity in research. By taking advantage of consumer-oriented methods and processes, space-flight missions will continue to leverage on investments tailored to provide better services at reduced cost. The application of ground and space segment architectures each based on Local Area Networks (LAN), the use of personal computer-based operating systems, and the execution of activities and operations through a Wide Area Network (Internet) enable a revolution in spacecraft mission formulation, implementation, and flight operations. Hardware and software design, development, integration, test, and flight operations are all tied-in closely to a common thread that enables the smooth transitioning between program phases. The application of commercial software development techniques lays the foundation for delivery of product-oriented flight software modules and models. Software can then be readily applied to support the on-board autonomy required for mission self-management. An on-board intelligent system, based on advanced scripting languages, facilitates the mission autonomy required to offload ground system resources, and enables the spacecraft to manage itself safely through an efficient and effective process of reactive planning, science data acquisition, synthesis, and transmission to the ground. Autonomous ground systems in turn coordinate and support schedule contact times with the spacecraft. Specific autonomy software modules on-board include mission and science planners, instrument and subsystem control, and fault tolerance response software, all residing within a distributed computing environment supported through the flight LAN. Autonomy also requires the minimization of human intervention between users on the ground and the spacecraft, and hence calls for the elimination of the traditional operations control center as a funnel for data manipulation. Basic goal-oriented commands are sent directly from the user to the spacecraft through a distributed internet-based payload operations "center". The ensuing architecture calls for the use of spacecraft as point extensions on the Internet. This paper will detail the system architecture implementation chosen to enable cost-effective autonomous missions with applicability to a broad range of conditions. It will define the structure needed for implementation of such missions, including software and hardware infrastructures. The overall architecture is then laid out as a common thread in the mission life cycle from formulation through implementation and flight operations.

Esper, Jamie↗

Flight Dynamics Operations: Methods and Lessons Learned from Space Shuttle Orbit Operations

The Flight Dynamics Officer is responsible for trajectory maintenance of the Space Shuttle. This paper will cover high level operational considerations, methodology, procedures, and lessons learned involved in performing the functions of orbit and rendezvous Flight Dynamics Officer and leading the team of flight dynamics specialists during different phases of flight. The primary functions that will be address are: onboard state vector maintenance, ground ephemeris maintenance, calculation of ground and spacecraft acquisitions, collision avoidance, burn targeting for the primary mission, rendezvous, deorbit and contingencies, separation sequences, emergency deorbit preparation, mass properties coordination, payload deployment planning, coordination with the International Space Station, and coordination with worldwide trajectory customers. Each of these tasks require the Flight Dynamics Officer to have cognizance of the current trajectory state as well as the impact of future events on the trajectory plan in order to properly analyze and react to real-time changes. Additionally, considerations are made to prepare flexible alternative trajectory plans in the case timeline changes or a systems failure impact the primary plan. The evolution of the methodology, procedures, and techniques used by the Flight Dynamics Officer to perform these tasks will be discussed. Particular attention will be given to how specific Space Shuttle mission and training simulation experiences, particularly off-nominal or unexpected events such as shortened mission durations, tank failures, contingency deorbit, navigation errors, conjunctions, and unexpected payload deployments, have influenced the operational procedures and training for performing Space Shuttle flight dynamics operations over the history of the program. These lessons learned can then be extended to future vehicle trajectory operations.

Cutri-Kohart, Rebecca M.↗

The International Satellite Cloud Climatology Project (ISCCP) - The first project of the World Climate Research Programme

The first project of the World Climate Research Program is the International Satellite Cloud Climatology Project, (ISCCP) whose objective is the collection and analysis of satellite radiance data in order to infer the global distribution of cloud radiative properties and improve the modeling of cloud effects on climate. The operational component of ISCCP takes advantage of the global coverage provided by the current and planned international array of geostationary and polar-orbiting meteorological satellites in the 1980s. It will produce a five-year global radiance and cloud data set. The research component of ISCCP will coordinate studies to validate climatology, improve cloud analysis algorithms, improve cloud effects modelling, and investigate the role of clouds in the atmospheric radiation budget and hydrologic cycle.

Schiffer, R. A.↗

NASA metric transition plan

NASA science publications have used the metric system of measurement since 1970. Although NASA has maintained a metric use policy since 1979, practical constraints have restricted actual use of metric units. In 1988, an amendment to the Metric Conversion Act of 1975 required the Federal Government to adopt the metric system except where impractical. In response to Public Law 100-418 and Executive Order 12770, NASA revised its metric use policy and developed this Metric Transition Plan. NASA's goal is to use the metric system for program development and functional support activities to the greatest practical extent by the end of 1995. The introduction of the metric system into new flight programs will determine the pace of the metric transition. Transition of institutional capabilities and support functions will be phased to enable use of the metric system in flight program development and operations. Externally oriented elements of this plan will introduce and actively support use of the metric system in education, public information, and small business programs. The plan also establishes a procedure for evaluating and approving waivers and exceptions to the required use of the metric system for new programs. Coordination with other Federal agencies and departments (through the Interagency Council on Metric Policy) and industry (directly and through professional societies and interest groups) will identify sources of external support and minimize duplication of effort.

Source record↗

Global disaster satellite communications system for disaster assessment and relief coordination

The global communication requirements for disaster assistance and examines operationally feasible satellite system concepts and the associated system parameters are analyzed. Some potential problems associated with the current method of providing disaster assistance and a scenario for disaster assistance relying on satellite communications are described. Historical statistics are used with the scenario to assess service requirements. Both present and planned commercially available systems are considered. The associated global disaster communication yearly service costs are estimated.

Leroy, B. E.↗

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗

System-Oriented Runway Management Concept of Operations

This document describes a concept for runway management that maximizes the overall efficiency of arrival and departure operations at an airport or group of airports. Specifically, by planning airport runway configurations/usage, it focuses on the efficiency with which arrival flights reach their parking gates from their arrival fixes and departure flights exit the terminal airspace from their parking gates. In the future, the concept could be expanded to include the management of other limited airport resources. While most easily described in the context of a single airport, the concept applies equally well to a group of airports that comprise a metroplex (i.e., airports in close proximity that share resources such that operations at the airports are at least partially dependent) by including the coordination of runway usage decisions between the airports. In fact, the potential benefit of the concept is expected to be larger in future metroplex environments due to the increasing need to coordinate the operations at proximate airports to more efficiently share limited airspace resources. This concept, called System-Oriented Runway Management (SORM), is further broken down into a set of airport traffic management functions that share the principle that operational performance must be measured over the complete surface and airborne trajectories of the airport's arrivals and departures. The "system-oriented" term derives from the belief that the traffic management objective must consider the efficiency of operations over a wide range of aircraft movements and National Airspace System (NAS) dynamics. The SORM concept is comprised of three primary elements: strategic airport capacity planning, airport configuration management, and combined arrival/departure runway planning. Some aspects of the SORM concept, such as using airport configuration management1 as a mechanism for improving aircraft efficiency, are novel. Other elements (e.g., runway scheduling, which is a part of combined arrival/departure runway scheduling) have been well studied, but are included in the concept for completeness and to allow the concept to define the necessary relationship among the elements. The goal of this document is to describe the overall SORM concept and how it would apply both within the NAS and potential future Next Generation Air Traffic System (NextGen) environments, including research conducted to date. Note that the concept is based on the belief that runways are the primary constraint and the decision point for controlling efficiency, but the efficiency of runway management must be measured over a wide range of space and time. Implementation of the SORM concept is envisioned through a collection of complementary, necessary capabilities collectively focused on ensuring efficient arrival and departure traffic management, where that efficiency is measured not only in terms of runway efficiency but in terms of the overall trajectories between parking gates and transition fixes. For the more original elements of the concept-airport configuration management-this document proposes specific air traffic management (ATM) decision-support automation for realizing the concept.

Lohr, Gary W.↗

A task control architecture for autonomous robots

An architecture is presented for controlling robots that have multiple tasks, operate in dynamic domains, and require a fair degree of autonomy. The architecture is built on several layers of functionality, including a distributed communication layer, a behavior layer for querying sensors, expanding goals, and executing commands, and a task level for managing the temporal aspects of planning and achieving goals, coordinating tasks, allocating resources, monitoring, and recovering from errors. Application to a legged planetary rover and an indoor mobile manipulator is described.

Simmons, Reid↗