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.
Mission Managers' Workstation (MMW) is personal-computer-based system providing data management and reporting functions to assist Space Shuttle mission managers. Allows to relate events and stored data in timely and organized fashion. Using MMW, standard reports formatted, generated, edited, and electronically communicated with minimum clerical help. Written in PASCAL, BASIC, and assembler.
The concept and the responsibilities of a mission manager approach are reviewed, and some of the associated problems in implementing Spacelab mission are discussed. Consideration is given to program control, science management, integrated payload mission planning, and integration requirements. Payload specialist training, payload and launch site integration, payload flight/mission operations, and postmission activities are outlined.
This manual prescribes the NASA mission management aircraft program and provides policies and criteria for the safe and economical operation, maintenance, and inspection of NASA mission management aircraft. The operation of NASA mission management aircraft is based on the concept that safety has the highest priority. Operations involving unwarranted risks will not be tolerated. NASA mission management aircraft will be designated by the Associate Administrator for Management Systems and Facilities. NASA mission management aircraft are public aircraft as defined by the Federal Aviation Act of 1958. Maintenance standards, as a minimum, will meet those required for retention of Federal Aviation Administration (FAA) airworthiness certification. Federal Aviation Regulation Part 91, Subparts A and B, will apply except when requirements of this manual are more restrictive.
The nucleus of the approach to Spacelab Payload mission management is the establishment of a single point of authority for the entire payload on a given mission. This single point mission manager will serve as a 'broker' between the individual experiments and the STS, negotiating agreements by two-part interaction. The payload mission manager, along with a small support team, will represent the users in negotiating use of STS accommodations. He will provide the support needed by each individual experimenter to meet the scientific, technological, and applications objectives of the mission with minimum cost and maximum efficiency. The investigator will assume complete responsibility for his experiment hardware definition and development and will take an active role in the integration and operation of his experiment.
This paper describes a project's design and implementation for streamlining mission management with knowledge capture processes across multiple organizations of a NASA directorate. Thc project's focus is on standardizing processes and reports; enabling secure information access and case of maintenance; automating and tracking appropriate workflow rules through process mapping; and infusing new technologies. This paper will describe a small team's experiences using XML technologies through an enhanced vendor suite of applications integrated on Windows-based platforms called the Wallops Integrated Scheduling and Document Management System (WISDMS). This paper describes our results using this system in a variety of endeavors, including providing range project scheduling and resource management for a Range and Mission Management Office; implementing an automated Customer Feedback system for a directorate; streamlining mission status reporting across a directorate; and initiating a document management, configuration management and portal access system for a Range Safety Office's programs. The end result is a reduction of the knowledge gap through better integration and distribution of information, improved process performance, automated metric gathering, and quicker identification of problem areas and issues. However, the real proof of the pudding comes through overcoming the user's reluctance to replace familiar, seasoned processes with new technology ingredients blended with automated procedures in an untested recipe. This paper shares some of the team's observations that led to better implementation techniques, as well as an IS0 9001 Best Practices citation. This project has provided a unique opportunity to advance NASA's competency in new technologies, as well as to strategically implement them within an organizational structure, while wetting the appetite for continued improvements in mission management.
The Spacelab development program is a joint undertaking of the NASA and ESA. The paper addresses the initial concept of Spacelab payload mission management, the lessons learned, and modifications made as a result of the actual implementation of Spacelab Mission 1. The discussion covers mission management responsibilities, program control, science management, payload definition and interfaces, integrated payload mission planning, integration requirements, payload specialist training, payload and launch site integration, payload flight/mission operations, and postmission activities. After 3.5 years the outlined overall mission manager approach has proven to be most successful. The approach does allow the mission manager to maintain the lowest overall mission cost.
The availability of highly capable, yet relatively cheap, unmanned aerial vehicles (UAVs) is opening up new areas of use for hobbyists and for commercial activities. This research is developing methods beyond classical control-stick pilot inputs, to allow operators to manage complex missions without in-depth vehicle expertise. These missions may entail several heterogeneous UAVs flying coordinated patterns or flying multiple trajectories deconflicted in time or space to predefined locations. This paper describes the functionality and preliminary usability measures of an interface that allows an operator to define a mission using speech inputs. With a defined and simple vocabulary, operators can input the vast majority of mission parameters using simple, intuitive voice commands. Although the operator interface is simple, it is based upon autonomous algorithms that allow the mission to proceed with minimal input from the operator. This paper also describes these underlying algorithms that allow an operator to manage several UAVs.
To meet cost and safety objectives, space missions that involve proximity operations between two vehicles require a high level of autonomy to successfully complete their missions. The need for autonomy is primarily driven by the need to conduct complex operations outside of communication windows, and the communication time delays inherent in space missions. Autonomy also supports the goals of both NASA and the DOD to make space operations more routine, and lower operational costs by reducing the requirement for ground personnel. NASA and the DoD have several programs underway that require a much higher level of autonomy for space vehicles. NASA's Space Launch Initiative (SLI) program has ambitious goals of reducing costs by a factor or 10 and improving safety by a factor of 100. DARPA has recently begun its Orbital Express to demonstrate key technologies to make satellite servicing routine. The Air Force's XSS-ll program is developing a protoflight demonstration of an autonomous satellite inspector. A common element in space operations for many NASA and DOD missions is the ability to rendezvous, inspect anclJor dock with another spacecraft. For DARPA, this is required to service or refuel military satellites. For the Air Force, this is required to inspect un-cooperative resident space objects. For NASA, this is needed to meet the primary SLI design reference mission of International Space Station re-supply. A common aspect for each of these programs is an Autonomous Mission Manager that provides highly autonomous planning, execution and monitoring of the rendezvous, inspection and docking operations. This paper provides an overview of the Autonomous Mission Manager (AMM) design being incorporated into many of these technology programs. This AMM provides a highly scalable level of autonomous operations, ranging from automatic execution of ground-derived plans to highly autonomous onboard planning to meet ground developed mission goals. The AMM provides the capability to automatically execute the plans and monitor the system performance. In the event of system dispersions or failures the AMM can modify plans or abort to assure overall system safety. This paper describes the design and functionality of Draper's AMM framework, presents concept of operations associated with the use of the AMM, and outlines the relevant features of the flight demonstrations.
The Marshall Space Flight Center (MSFC) Spacelab Payload Project Office was responsible for the mission management and development of several successful payloads. Two recent space construction experiments, the Experimental Assembly of Structures in Extravehicular Activity (EASE) and the Assembly Concept for Construction of Erectable Space Structures (ACCESS), were combined into a payload managed by the center. The Ease/ACCESS was flown aboard the Space Shuttle Mission 61-B. The EASE/ACCESS experiments were the first structures assembled in space, and the method used to manage this successful effort will be useful for future space construction missions. The MSFC mission management responsibilities for the EASE/ACCESS mission are addressed and how the lessons learned from the mission can be applied to future space construction projects are discussed.
Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade its science site database management tool, which at the time was integrated with the Automated Mission Planning System (AMPS) originally developed for Earth Observations mission planning in the 1980s. Although AMPS had been adapted and was reliably used by CEO for International Space Station (ISS) payload operations support, the database structure was dated, and the compiler required for modifications would not be supported in the Windows 7 64-bit operating system scheduled for implementation the following year. The Sites Mission Management System (SMMS) is now the tool used by CEO to manage a heritage Structured Query Language (SQL) database of more than 2,000 records for Earth science sites. SMMS is a carefully designed and crafted in-house software package with complete and detailed help files available for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in April 2012. The database spans the period from the earliest systematic requests for astronaut photography during the shuttle era to current ISS mission support of the CEO science payload. Besides logging basic image information (site names, locations, broad application categories, and mission requests), the upgraded database management tool now tracks dates of creation, modification, and activation; imagery acquired in response to requests; the status and location of ancillary site information; and affiliations with studies, their sponsors, and collaborators. SMMS was designed to facilitate overall mission planning in terms of site selection and activation and provide the necessary site parameters for the Satellite Tool Kit (STK) Integrated Message Production List Editor (SIMPLE), which is used by CEO operations to perform daily ISS mission planning. The CEO team uses the SMMS for three general functions - database queries of content and status, individual site creation and updates, and mission planning. The CEO administrator of the science site database is able to create or modify the content of sites and activate or deactivate them based on the requirements of the sponsors. The administrator supports and implements ISS mission planning by assembling, reporting, and activating mission-specific site selections for management; deactivating sites as requirements are met; and creating new sites, such as International Charter sites for disasters, as circumstances warrant. In addition to the above CEO internal uses, when site planning for a specific ISS mission is complete and approved, the SMMS can produce and export those essential site database elements for the mission into XML format for use by onboard Earth-location systems, such as Worldmap. The design, development, and implementation of the SMMS resulted in a superior database management system for CEO science sites by focusing on the functions and applications of the database alone instead of integrating the database with the multipurpose configuration of the AMPS. Unlike the AMPS, it can function and be modified within the existing Windows 7 environment. The functions and applications of the SMMS were expanded to accommodate more database elements, report products, and a streamlined interface for data entry and review. A particularly elegant enhancement in data entry was the integration of the Google Earth application for the visual display and definition of site coordinates for site areas defined by multiple coordinates. Transfer between the SMMS and Google Earth is accomplished with a Keyhole Markup Language (KML) expression of geographic data (see figures 3 and 4). Site coordinates may be entered into the SMMS panel directly for display in Google Earth, or the coordinates may be defined on the Google Earth display as a mouse-controlled polygonal definition and transferred back into the SMMS as KML input. This significantly reduces the possibility of errors in coordinate entries and provides visualization of the scale of the site being defined. CEO now has a powerful tool for managing and defining sites on the Earth's surface for both targets of astronaut photography or other onboard remote sensing systems. It can also record and track results by sponsor, collaborator, or type of study.
We present a prototype human assistant system for space crew assessment and mission management. Our system is based on case episodes from American and Russian space missions and analog environments such as polar stations and undersea habitats. The general domain of small groups in isolated and confined environments represents a near ideal application area for case-based reasoning (CBR) - there are few reliable rules to follow, and most domain knowledge is in the form of cases. We define the problem domain and outline a unique knowledge representation system driven by conflict and communication triggers. The prototype system is able to represent, index, and retrieve case studies of human performance. We index by social, behavioral, and environmental factors. We present the problem domain, our current implementation, our research approach for an operational system, and prototype performance and results.
The briefing opened with Bruce Buckingham (NASA Public Affairs) introducing John Shannon (Chairman, Mission Management Team, JSC), John Chapman (External Tank Project Manager), Mike Leinbach (Shuttle Launch Director), and 1st Lt. Kaleb Nordgren (USAF 45th Weather Squadron). John Shannon reported that the team for hydrogen loading was proceeding well and the external tank detanking was completed. During detanking the inspection team cracked foam caused by condensation and ice formation as the tank expanded and contracted. Aerothermal analysis and analysis fro ice formation will be completed before launch. John Chapman explained the mechanics of the external tank design, the foam cracking, bracket design, etc. Mike Leinbach discussed the inspection teams and their inspection final inspection for ice formation before and after external tank filling. The inspection team of eight very experienced personnel also use telescopes with cameras to find any problems before launch. Kaleb Nordgren discussed weather and said there was a 40% chance of weather prohibiting launch. The floor was the opened for questions from the press.
The briefing began with Allard Buetel (NASA Public Affairs) introducing Bill Gerstenmaier (Associate Administrator for Space Operations) who provided an update of the Mission Management team meeting. The 3 criteria reviewed by the team were: a) ascent heating; b) ice formation and c) remaining foam still intact. The ascent heating had a safety factor of 5 and posed no concern. Ice formation was not a concern. In order to insure there was no damage to the remaining foam, an 8ft. pipe with a camera attached was used to provide pictures. The boroscope pictures showed there was no damage to the brackets or foam. The inspection went very well and the foam was acceptable and ready to fly. Then the floor was open to questions from the press.
The Pluto unmanned long-range scientific explorer (PULSE) is a probe that will do a flyby of Pluto. It is a low weight, relatively low costing vehicle which utilizes mostly off-the-shelf hardware, but not materials or techniques that will be available after 1999. A design, fabrication, and cost analysis is presented. PULSE will be launched within the first decade of the twenty-first century. The topics include: (1) scientific instrumentation; (2) mission management, planning, and costing; (3) power and propulsion systems; (4) structural subsystem; (5) command, control, and communication; and (6) attitude and articulation control.
NASA is proposing increasingly complex missions that will require a high degree of autonomy and autonomicity. These missions pose hereto unforeseen problems and raise issues that have not been well-addressed by the community. Assuring success of such missions will require new software development techniques and tools. This paper discusses some of the challenges that NASA and the rest of the software development community are facing in developing these ever-increasingly complex systems. We give an overview of a proposed NASA mission as well as techniques and tools that are being developed to address autonomic management and the complexity issues inherent in these missions.
Operations required to launch a modular space station and to provides sustaining ground operations for support of that orbiting station throughout its 10 year mission are studied. A baseline, incrementally manned program and attendent experiment program options are derived. In addition, features of the program that significantly effect initial development and early operating costs are identified, and their impact on the program is assessed. A preliminary design of the approved modular space station configuration is formulated.
People who must work at night experience a number of physiological and psychological difficulties. These include sleepiness and fatigue at work, poor daytime sleep, gastrointestinal distress, impaired concentration and performance, disturbed mood, and increased health complaints and risk of disease. These difficulties arise because nocturnal work and daytime sleep take place at inappropriate phases of the body's circadian rhythms. Intense artificial light can shift the phase of human circadian rhythms, and can thus be used to promote adaptation to shifted work schedules. The first attempts to investigate the efficacy of light treatment for MSFC POCC shiftworkers took place during USML-1 and ATLAS-2. The findings from these studies led to the development of a Circadian Countermeasures Program that was implemented during USMP-2. Light treatment and other circadian countermeasures were employed to promote adjustment to mission shiftwork in POCC cadre volunteers. Treatment protocols were designed and customized for each volunteer's work hours and personal preferences. Treatment protocols included some or all of the following: scheduled self-administration of intense light, scheduled avoidance or attenuation of sunlight at other times, and sleep schedules. Data from post-mission questionnaires indicated that volunteers found the program to be effective, convenient, and beneficial.
Historically, NASA's cost for developing mission requirements has been a significant part of a mission's budget. Large amounts of time have been allocated in mission schedules for the development and review of requirements by the many groups who are associated with a mission. Additionally, tracing requirements from a current document to a parent document has been time-consuming and costly. The Requirements Generation System (RGS) is a computer-supported cooperative-work tool that assists mission developers in the online creation, review, editing, tracing, and approval of mission requirements as well as in the production of requirements documents. This paper describes the RGS and discusses some lessons learned during its development.