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.
The Weather-Related Service Management (WSRM) operations concept is presented. The topics include: 1) X & Ka-band Link Comparison; 2) Justification for WRSM; 3) Operations Concept; and 4) External Interactions.
Mission operation concepts are described which are being used to evaluate and influence space and ground system designs and architectures with the goal of achieving successful, efficient, and cost-effective Earth Observing System (EOS) operations. Emphasis is given to the general characteristics and concepts developed for the EOS Space Measurement System, which uses a new series of polar-orbiting observatories. Data rates are given for various instruments. Some of the operations concepts which require a total system view are also examined, including command operations, data processing, data accountability, data archival, prelaunch testing and readiness, launch, performance monitoring and assessment, contingency operations, flight software maintenance, and security.
OBJECTIVES: NASA Extreme Environment Mission Operations (NEEMO) is an underwater spaceflight analog that allows a true mission‐like operational environment and uses buoyancy effects and added weight to simulate different gravity levels. Three missions were undertaken from 2014‐2015, NEEMO's 18‐20. All missions were performed at the Aquarius undersea research habitat. During each mission, the effects of varying operations concepts and tasks type and complexity on representative communication latencies associated with Mars missions were studied. METHODS: 12 subjects (4 per mission) were weighed out to simulate near‐zero or partial gravity extravehicular activity (EVA) and evaluated different operations concepts for integration and management of a simulated Earth‐based science backroom team (SBT) to provide input and direction during exploration activities. Exploration traverses were planned in advance based on precursor data collected. Subjects completed science‐related tasks including presampling surveys, geologic‐based sampling, and marine‐based sampling as a portion of their tasks on saturation dives up to 4 hours in duration that were to simulate extravehicular activity (EVA) on Mars or the moons of Mars. One‐way communication latencies, 5 and 10 minutes between space and mission control, were simulated throughout the missions. Objective data included task completion times, total EVA times, crew idle time, translation time, SBT assimilation time (defined as time available for SBT to discuss data/imagery after it has been collected, in addition to the time taken to watch imagery streaming over latency). Subjective data included acceptability, simulation quality, capability assessment ratings, and comments. RESULTS: Precursor data can be used effectively to plan and execute exploration traverse EVAs (plans included detailed location of science sites, high‐fidelity imagery of the sites, and directions to landmarks of interest within a site). Operations concepts that allow for presampling surveys enable efficient traverse execution and meaningful Mission Control Center (MCC) interaction across long communication latencies and can be done with minimal crew idle time. Imagery and information from the EVA crew that is transmitted real‐time to the intravehicular (IV) crewmember(s) can be used to verify that exploration traverse plans are being executed correctly. That same data can be effectively used by MCC (across comm latency) to provide further instructions to the crew from a SBT on sampling priorities, additional tasks, and changes to the plan. Text / data capabilities are preferred over voice capabilities between MCC and IV when executing exploration traverse plans over communication latency. Autonomous crew planning tools can be effective at modifying existing plans if the objectives and constraints are clearly defined.
This document defines the Small Aircraft Transportation System (SATS) Higher Volume Operations concept. The general philosophy underlying this concept is the establishment of a newly defined area of flight operations called a Self-Controlled Area (SCA). Within the SCA, pilots would take responsibility for separation assurance between their aircraft and other similarly equipped aircraft. This document also provides details for a number of off-nominal and emergency procedures which address situations that could be expected to occur in a future SCA. The details for this operational concept along with a description of candidate aircraft systems to support this concept are provided.
The initiation of the (German-) nationally funded control center for manned spaceflight operations triggered by the invitation of President Reagan to ESA, Japan, and Canada in 1984 to join the International Space Station Freedom Program is recalled. The requirements for a Manned Space-Laboratories Control Center (MSCC) as defined at the beginning of the planning and construction process in 1987 and the resulting modifications during the various programmatic scenario changes on NASA and ESA side between 1987 and now are presented. The validity of the original requirements with respect to the current scenario, which asks for a logical evolution from the execution of the D-2 mission in January 1993 via the European Columbus Precursor flights (in particular the E-1 mission) towards Columbus Attached Laboratory (APM)-operations by the end of this century are discussed. The resulting tasks of the MSCC for the various missions, the current configuration, and the ensuing operations concept leading from a more centralized concept for D-2 towards a decentralized payload operations concept for the APM and the implications with respect to European and International interfaces are presented. The planned Columbus MSCC facility architecture and its expected modifications introduced by the ESA Ministerial Conference in Munich (Nov. 1991) and follow-on discussions are briefly addressed. The last chapter outlines the planned services to be provided by the MSCC to the decentralized User (experimenter) community. Issues like decentralized mission planning on executional level, command validation, data flow coordination, archiving services, and telescience capabilities are highlighted from a MSCC point of view.
This paper briefly outlines EOS Aura's Tropospheric Emmision Spectrometer (TES) experiment and TES instrument activities on operations.
A preliminary survey of existing separation assurance and collision avoidance advancements, technologies, and efforts has been conducted in order to develop a concept of operations for flight testing autonomous separation assurance at Dryden Flight Research Center. This effort was part of the Unmanned Aerial Systems in the National Airspace System project. The survey focused primarily on separation assurance projects validated through flight testing (including lessons learned), however current forays into the field were also examined. Comparisons between current Dryden flight and range assets were conducted using House of Quality matrices in order to allow project management to make determinations regarding asset utilization for future flight tests. This was conducted in order to establish a body of knowledge of the current collision avoidance landscape, and thus focus Dryden s efforts more effectively towards the providing of assets and test ranges for future flight testing within this research field.
As JPL's missions grow more complex, the need for improved systems engineering processes is becoming clear. Of significant promise in this regard is the move toward a more integrated and model-centric approach to mission conception, design, implementation and operations. The Integrated Model-Centric Engineering (IMCE) Initiative, now underway at JPL, seeks to lay the groundwork for these improvements. This paper will report progress on three fronts: articulating JPL's need for IMCE; characterizing the enterprise into which IMCE capabilities will be deployed; and constructing an operations concept for a flight project development in an integrated model-centric environment.
The Biologic Analog Science Associated with Lava Terrains (BASALT) project is a multi-year program dedicated to iteratively develop, implement, and evaluate concepts of operations (ConOps) and supporting capabilities intended to enable and enhance human scientific exploration of Mars. This pa-per describes the planning, execution, and initial results from the first field deployment, referred to as BASALT-1, which consisted of a series of 10 simulated extravehicular activities (EVAs) on volcanic flows in Idaho's Craters of the Moon (COTM) National Monument. The ConOps and capabilities deployed and tested during BASALT-1 were based on previous NASA trade studies and analog testing. Our primary research question was whether those ConOps and capabilities work acceptably when performing real (non-simulated) biological and geological scientific exploration under 4 different Mars-to-Earth communication conditions: 5 and 15 min one-way light time (OWLT) communication latencies and low (0.512 Mb/s uplink, 1.54 Mb/s downlink) and high (5.0 Mb/s uplink, 10.0 Mb/s downlink) bandwidth conditions representing the lower and higher limits of technical communication capabilities currently proposed for future human exploration missions. The synthesized results of BASALT-1 with respect to the ConOps and capabilities assessment were derived from a variety of sources, including EVA task timing data, network analytic data, and subjective ratings and comments regarding the scientific and operational acceptability of the ConOp and the extent to which specific capabilities were enabling and enhancing, and are presented here. BASALT-1 established preliminary findings that baseline ConOp, software systems, and communication protocols were scientifically and operationally acceptable with minor improvements desired by the "Mars" extravehicular (EV) and intravehicular (IV) crewmembers, but unacceptable with improvements required by the "Earth" Mission Support Center. These data will provide a basis for guiding and prioritizing capability development for future BASALT deployments and, ultimately, future human exploration missions.
Space communications to date has been largely managed at the link layer, with simple point-to-point links between a spacecraft at Earth. However, future space exploration scenarios involve much richer communications scenarios, with complex network scenarios involving space assets communicating back to Earth via multiple intermediate relay service providers. To support these more complex network scenarios, the Space Internetworking Strategy Group has developed an operations concept for a Solar System Internetwork (SSI). The operations concept draws on the successes of the terrestrial Internet while addressing unique aspects of space communications. Key elements of the operations concept include a standardized network layer across the end-to-end SSI and the underlying processes for development of a contact plan that captures the link layer connectivity among SSI network nodes.
The planning and scheduling of human space activities is an expensive and time-consuming task that seldom provides the crew with the control, flexibility, or insight that they need. During the past thirty years, scheduling software has seen only incremental improvements; however, software limitations continue to prevent even evolutionary improvements in the operations concept that is used for human space missions. Space missions are planned on the ground long before they are executed in space, and the crew has little input or influence on the schedule. In recent years the crew has been presented with a job jar of activities that they can do whenever they have time, but the contents of the jar is limited to tasks that do not use scarce shared resources and do not have external timing constraints. Consequently, the crew has no control over the schedule of the majority of their own tasks. As humans venture farther from earth for longer durations, it will become imperative that they have the ability to plan and schedule not only their own activities, but also the unattended activities of the systems, equipment, and robots on the journey with them. Significant software breakthroughs are required to enable the change in the operations concept. The crew does not have the time to build or modify the schedule by hand. They only need to issue a request to schedule a task and the system should automatically do the rest. Of course, the crew should not be required to build the complete schedule. Controllers on the ground should contribute the models and schedules where they have the better knowledge. The system must allow multiple simultaneous users, some on earth and some in space. The Mission Operations Laboratory at NASA's Marshall Space flight Center has been researching and prototyping a modeling schema, scheduling engine, and system architecture that can enable the needed paradigm shift - it can make the crew autonomous. This schema and engine can be the core of a planning and scheduling system that would enable multiple planners, some on the earth and some in space, to build one integrated timeline. Its modeling schema can capture all the task requirements; its scheduling engine can build the schedule automatically, and its architecture can allow those (on earth and in space) with the best knowledge of the tasks to schedule them. This paper describes the enabling technology and proposes an operations concept for astronauts autonomously scheduling their activities and the activities around them.
Historically, the Mission Operations System (MOS) for a space mission has been designed last because it is needed last. This has usually meant that the ground system must adjust to the flight vehicle design, sometimes at a significant cost. As newer missions have increasingly longer flight operations lifetimes, the MOS becomes proportionally more difficult and more resource-consuming. We can no longer afford to design the MOS last. The MOS concept may well drive the spacecraft, instrument, and mission designs, as well as the ground system. A method to help avoid these difficulties, responding to the changing nature of mission operations is presented. Proper development and use of an Operations Concept document results in a combined flight and ground system design yielding enhanced operability and producing increased flexibility for less cost.
NASA has considerable experience in two areas of Extravehicular Activities (EVA). The first can be defined as microgravity, orbital EVAs. This consists of everything done in low Earth orbit (LEO), from the early, proof of concept EVAs conducted during the Gemini program of the 1960s, to the complex International Space Station (ISS) assembly tasks of the first decade of the 21st century. The second area of expertise is comprised of those EVAs conducted on the lunar surface, under a gravitational force one-sixth that of Earth. This EVA expertise encapsulates two extremes - microgravity and Earthlike gravitation - but is insufficient as humans expand their exploration purview, most notably with respect to spacewalks conducted on very low-gravity bodies, such as near- Earth objects (NEO) and the moons of Mars. The operational and technical challenges of this category of EVA have yet to be significantly examined, and as such, only a small number of operational concepts have been proposed thus far. To ensure mission success, however, EVA techniques must be developed and vetted to allow the selection of operational concepts that can be utilized across an assortment of destinations whose physical characteristics vary. This paper examines the utilization of ISS-based EVAs to test operational concepts and hardware in preparation for a low-gravity terrestrial EVA. While the ISS cannot mimic some of the fundamental challenges of a low-gravity terrestrial EVA - such as rotation rate and surface composition - it may be the most effective test bed available.
This document is one of three. It describes the Operational Concept (OpsCon) for a generic space exploration communication architecture. The purpose of this particular document is to identify communication flows and data types. Two other documents accompany this document, a security policy profile and a communication architecture document. The operational concepts should be read first followed by the security policy profile and then the architecture document. The overall goal is to design a generic space exploration communication network architecture that is affordable, deployable, maintainable, securable, evolvable, reliable, and adaptable. The architecture should also require limited reconfiguration throughout system development and deployment. System deployment includes: subsystem development in a factory setting, system integration in a laboratory setting, launch preparation, launch, and deployment and operation in space.
With the retirement of the Space Shuttle fleet imminent in 2011, a new operations concept will become reality to meet the transportation challenges of the International Space Station (ISS). The planning associated with the retirement of the Space Shuttle has been underway since the announcement in 2004. Since then, several companies and government entities have had to look for innovative low-cost commercial orbital transportation systems to continue to achieve the objectives of ISS delivery requirements. Several options have been assessed and appear ready to meet the large and demanding delivery requirements of the ISS. Options that have been identified that can facilitate the challenge include the Russian Federal Space Agency's Soyuz and Progress spacecraft, European Space Agency's Automated Transfer Vehicle (ATV), and the Japan Aerospace Exploration Agency's (JAXA s) H-II Transfer Vehicle (HTV). The newest of these options is the JAXA's HTV. This paper focuses on the HTV, mission architecture and operations concept for Extra-Vehicular Activities (EVA) hardware, the associated launch system, and details of the launch operations approach.
A trajectory design and analysis that describes aerocapture, entry, descent, and inflation of manned and unmanned High Altitude Venus Operation Concept (HAVOC) lighter-than-air missions is presented. Mission motivation, concept of operations, and notional entry vehicle designs are presented. The initial trajectory design space is analyzed and discussed before investigating specific trajectories that are deemed representative of a feasible Venus mission. Under the project assumptions, while the high-mass crewed mission will require further research into aerodynamic decelerator technology, it was determined that the unmanned robotic mission is feasible using current technology.
The Deep Space Mission System (DSMS) Science Operations Concept describes the vision for enabling the use of the DSMS, particularly the Deep Space Network (DSN) for direct science observations in the areas of radio astronomy, planetary radar, radio science and VLBI.
This paper will discuss the concept of developing a space mission operations concept; the benefits of starting this system engineering task early; the neccessary inputs to the process; and the products that are generated.