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.
This report presents a concept for a User Operations Facility (UOF) for payloads sponsored by the NASA Office of Aeronautics and Space Technology (OAST). The UOF can be located at any OAST sponsored center; however, for planning purposes, it is assumed that the center will be located at Langley Research Center (LaRC).
This paper will present the Space Station Biological Research Project (SSBRP) User Operations Facility (UOF) architecture and development strategy. A major element of the UOF at NASA Ames Research Center, the Communication and Data System (CDS) will be the primary focus of the discussions. CDS operational, telescience, security, and development objectives will be discussed along with CDS implementation strategy. The implementation strategy discussions will include: Object Oriented Analysis & Design, System & Software Prototyping, and Technology Utilization. A CDS design overview that includes: CDS Context Diagram, CDS Architecture, Object Models, Use Cases, and User Interfaces will also be presented. CDS development brings together "cutting edge" technologies and techniques such as: object oriented development, network security, multimedia networking, web-based data distribution, JAVA, and graphical user interfaces. Use of these "cutting edge" technologies and techniques translates directly to lower development and operations costs.
The Space Station Biological Research Project (SSBRP) Is developing hardware referred to as the "facility" for providing life sciences research capability on the International Space Station. This hardware includes several biological specimen habitats, habitat holding racks, a centrifuge and a glovebox. An SSBRP end to end data system architecture has been developed to allow command and control of the facility from the ground, either with crew assistance or autonomously. The data system will be capable of handling commands, sensor data, and video from multiple cameras. The data will traverse through several onboard and ground networks and processing entities including the SSBRP and Space Station onboard and ground data systems. A large number of onboard and ground (,entities of the data system are being developed by the Space Station Program, other NASA centers and the International Partners. The SSBRP part of the system which includes the habitats, holding racks, and the ground operations center, User Operations Facility (UOF) will be developed by a multitude of geographically distributed development organizations. The SSBRP has the responsibility to define the end to end data and communications systems to make the interfaces manageable and verifiable with multiple contractors with widely varying development constraints and schedules. This paper provides an overview of the SSBRP end-to-end data system. Specifically, it describes the hardware, software and functional interactions of individual systems, and interface requirements among various entities of the end-to-end system.
This report describes the Microgravity Science and Applications Division's (MSAD) operations concept for using the Space Station Freedom (SSF) program ground data systems and services, and the plans for and capabilities of the MSAD remote User Operations Facilities (UOF) from which the MSAD SSF payloads will be operated. Attention is given to the MSAD operational phases, the MSAD UOF concept, and UOF operations teams. MSAD is planning remote payload operations for a number of Spacelab missions which will supply MSAD valuable information for application to the development of UOFs in the SSF era.
The Unified Modeling Language (UML) is the standard method for specifying, visualizing, and documenting the artifacts of an object-oriented system under development. UML is the unification of the object-oriented methods developed by Grady Booch and James Rumbaugh, and of the Use Case Model developed by Ivar Jacobson. This paper discusses the application of UML by the Communications and Data Systems (CDS) team to model the ground control and command of the Space Station Biological Research Project (SSBRP) User Operations Facility (UOF). UML is used to define the context of the system, the logical static structure, the life history of objects, and the interactions among objects.
Automated User's Training Operations Facility Utilization Request (AutoFUR) is prototype software that administers a Web-based system for requesting and allocating facilities and equipment for astronaut-training classes in conjunction with scheduling the classes. AutoFUR also has potential for similar use in such applications as scheduling flight-simulation equipment and instructors in commercial airplane-pilot training, managing preventive- maintenance facilities, and scheduling operating rooms, doctors, nurses, and medical equipment for surgery. Whereas requesting and allocation of facilities was previously a manual process that entailed examination of documents (including paper drawings) from different sources, AutoFUR partly automates the process and makes all of the relevant information available via the requester s computer. By use of AutoFUR, an instructor can fill out a facility-utilization request (FUR) form on line, consult the applicable flight manifest(s) to determine what equipment is needed and where it should be placed in the training facility, reserve the corresponding hardware listed in a training-hardware inventory database, search for alternative hardware if necessary, submit the FUR for processing, and cause paper forms to be printed. Auto-FUR also maintains a searchable archive of prior FURs.
International Space Station Alpha (ISSA) will accommodate a variety of user payloads investigating diverse scientific and technology disciplines on behalf of five international partners: Canada, Europe, Japan, Russia, and the United States. A combination of crew, automated systems, and ground operations teams will control payload operations that require complementary on-board and ground systems. This paper presents the current planning for the ISSA U.S. user payload operations concept and the functional architecture supporting the concept. It describes various NASA payload operations facilities, their interfaces, user facility flight support, the payload planning system, the onboard and ground data management system, and payload operations crew and ground personnel training. This paper summarizes the payload operations infrastructure and architecture developed at the Marshall Space Flight Center (MSFC) to prepare and conduct ISSA on-orbit payload operations from the Payload Operations Integration Center (POIC), and from various user operations locations. The authors pay particular attention to user data management, which includes interfaces with both the onboard data management system and the ground data system. Discussion covers the functional disciplines that define and support POIC payload operations: Planning, Operations Control, Data Management, and Training. The paper describes potential interfaces between users and the POIC disciplines, from the U.S. user perspective.
The NASA Goddard Space Flight Center's Flight Dynamics Facility (FDF) is a multimission support facility that performs ground navigation and spacecraft trajectory design services for a wide range of scientific satellites. The FDF also supports the NASA Space Network by providing orbit determination and tracking data evaluation services for the Tracking Data Relay Satellite System (TDRSS). The FDF traces its history to early NASA missions in the 1960's, including navigation support to the Apollo lunar missions. Over its 40 year history, the FDF has undergone many changes in its architecture, services offered, missions supported, management approach, and business operation. As a fully reimbursable facility (users now pay 100% of all costs for FDF operations and sustaining engineering activities), the FDF has faced significant challenges in recent years in providing mission critical products and services at minimal cost while defining and implementing upgrades necessary to meet future mission demands. This paper traces the history of the FDF and discusses significant events in the past that impacted the FDF infrastructure and/or business model, and the events today that are shaping the plans for the FDF in the next decade. Today's drivers for change include new mission requirements, the availability of new technology for spacecraft navigation, and continued pressures for cost reduction from FDF users. Recently, the FDF completed an architecture study based on these drivers that defines significant changes planned for the facility. This paper discusses the results of this study and a proposed implementation plan. As a case study in how flight dynamics operations have evolved and will continue to evolve, this paper focuses on two periods of time (1992 and the present) in order to contrast the dramatic changes that have taken place in the FDF. This paper offers observations and plans for the evolution of the FDF over the next ten years. Finally, this paper defines the mission model of the future for the FDF based on NASA's current mission list and planning for the Constellation Program. As part of this discussion the following are addressed: the relevance and benefits of a multi-mission facility for NASA's navigation operations in the future; anticipated technologies affecting ground orbit determination; continued incorporation of Commercial Off-the-shelf (COTS) software into the FDF; challenges of a business model that relies entirely on user fees to fund facility upgrades; anticipated changes in flight dynamics services required; and considerations for defining architecture upgrades given a set of cost drivers.
Explicit integration of aviation weather forecasts with the National Airspace System (NAS) structure is needed to improve the development and execution of operationally effective weather impact mitigation plans and has become increasingly important due to NAS congestion and associated increases in delay. This article considers several contemporary weather-air traffic management (ATM) integration applications: the use of probabilistic forecasts of visibility at San Francisco, the Route Availability Planning Tool to facilitate departures from the New York airports during thunderstorms, the estimation of en route capacity in convective weather, and the application of mixed-integer optimization techniques to air traffic management when the en route and terminal capacities are varying with time because of convective weather impacts. Our operational experience at San Francisco and New York coupled with very promising initial results of traffic flow optimizations suggests that weather-ATM integrated systems warrant significant research and development investment. However, they will need to be refined through rapid prototyping at facilities with supportive operational users We have discussed key elements of an emerging aviation weather research area: the explicit integration of aviation weather forecasts with NAS structure to improve the effectiveness and timeliness of weather impact mitigation plans. Our insights are based on operational experiences with Lincoln Laboratory-developed integrated weather sensing and processing systems, and derivative early prototypes of explicit ATM decision support tools such as the RAPT in New York City. The technical components of this effort involve improving meteorological forecast skill, tailoring the forecast outputs to the problem of estimating airspace impacts, developing models to quantify airspace impacts, and prototyping automated tools that assist in the development of objective broad-area ATM strategies, given probabilistic weather forecasts. Lincoln Laboratory studies and prototype demonstrations in this area are helping to define the weather-assimilated decision-making system that is envisioned as a key capability for the multi-agency Next Generation Air Transportation System [1]. The Laboratory's work in this area has involved continuing, operations-based evolution of both weather forecasts and models for weather impacts on the NAS. Our experience has been that the development of usable ATM technologies that address weather impacts must proceed via rapid prototyping at facilities whose users are highly motivated to participate in system evolution.
The main phase of solar physics (including flare-buildup) research on Shuttle/Spacelab during the 1980s centers around the use of facility instruments for multiple-user, multiple flight operations. Three main facilities are being considered: a meter-class optical telescope for visible and near-UV wavelengths, an EUV/XUV/soft X-ray facility, and a hard X-ray imaging facility (including a full-sun 5-600 keV spectrometer, a nuclear gamma ray spectrometer, and an X-ray polarimeter for the 5-100 keV range). Smaller instruments designed for specific observations and other classes of instruments such as solar monitors that are not on the facility level are also being considered.
User-service operations at supercomputer facilities are examined. The question is whether a single, possibly distributed, user-services organization could be shared by NASA's supercomputer sites in support of a diverse, geographically dispersed, user community. A possible structure for such an organization is identified as well as some of the technologies needed in operating such an organization.
A relay transponder, located either on a satellite in geostationary orbit or on a local tower to relay acquisition-aiding data, ephemerides, etc, from a ground-based remote control station to a GPS civil user terminal located on a ship or land-transportation vehicle is described. Termed REFSAT (Reference Satellite), this concept reduces the circuit complexity and cost of user terminals. The various systems needed to implement the REFSAT concept for low-cost, GPS civil terminals are defined. The GPS/REFSAT system compatible with the NAVSTAR GPS system consists of a geostationary relay satellite, civil user terminals, and the central facility which performs operations common to all users for relay via the space segment. A GPS/REFSAT system utilizing a local tower for the relay transponder is described, results of a study of civil user requirements are presented, and specifications for the GPS/REFSAT system and its individual segments are included.
The Midwestern astronomical data reduction and analysis facility (MADRAF) PDS microdensitometer which was the first astronomical PDS which was provided with a Motorola 6800 microprocessor control/interface and will be interfaced to a 32-bit instruction computer operating in a multiuser environment is outlined. Command and response handshaking are handled on an RS 232 serial line while data transfer occurs on a dedicated Direct Memory Access line. This set of conditions necessitated the creation of a specialized device for the system. The general outline of this software is discussed. The availability of an extraordinarily powerful computer opened the possibility of a user operating program of great versatility with diverse data destinations and formats, automatic documentation, and an extensive set of utilities which facilitate operations.
The Space Infrared Telescope Facility (SIRTF) is a long life cryogenically cooled space based telescope for infrared astronomy from 2 to 700 microns currently under study and planned for launch in the mid 90's. SIRTF will operate as a multi-user facility, initially carrying 3 instruments at the focal plane. It will be cooled to below 2 K by superfluid liquid helium to achieve radiometric sensitivity limited only by the statistical fluctuations in the natural infrared background radiation over most of its spectral range. The lifetime of the mission will be limited by the lifetime of the liquid helium supply, and is currently baselined to be 2 years. Candidates are reviewed for a liquid management device to be used in the resupply of liquid helium, and for the selection of an appropriate candidate.
The Management Information and Decision Support Environment (MIDSE) is a research activity to build and test a prototype of a generic human interface on the Johnson Space Center (JSC) Information Network (CIN). The existing interfaces were developed specifically to support operations rather than the type of data which management could use. The diversity of the many interfaces and their relative difficulty discouraged occasional users from attempting to use them for their purposes. The MIDSE activity approached this problem by designing and building an interface to one JSC data base - the personnel statistics tables of the NASA Personnel and Payroll System (NPPS). The interface was designed against the following requirements: generic (use with any relational NOMAD data base); easy to learn (intuitive operations for new users); easy to use (efficient operations for experienced users); self-documenting (help facility which informs users about the data base structure as well as the operation of the interface); and low maintenance (easy configuration to new applications). A prototype interface entitled the JSC Management Information Systems (JSCMIS) was produced. It resides on CIN/PROFS and is available to JSC management who request it. The interface has passed management review and is ready for early use. Three kinds of data are now available: personnel statistics, personnel register, and plan/actual cost.
The Space Infrared Telescope Facility (SIRTF) is a long-life cryogenically cooled space-based telescope for infrared astronomy from 2 micrometer to 700 miocrometers currently under study by NASA-ARC, and planned for launch in approximately the mid 90's. SIRTF will operate as a multi-user facility, initially carrying 3 instruments at the focal plane. It will be cooled to below 2 K by superfluid liquid helium to achieve radiometric sensitivity limited only by the statistical fluctuations in the natural infrared background radiation over most of its spectral range. The lifetime of the mission will be limited by the lifetime of the liquid helium supply, and is currently baselined to be 2 years. The telescope changes required to allow in-space replenishment of the 2,000 liter superfluid helium tank are investigated. A preliminary design for the space services equipment is also developed. The impacts of basing the equipment and servicing on the space station are investigated. Space replenishment and changeout of instruments requires changes to the telescope design and preliminary concepts are presented.
A focus of NASA’s Moon-to-Mars objectives is the development of the infrastructure on the lunar surface that will be needed to support broader lunar surface operations. This infrastructure is intended to support both United States and international partners to expand human presence on the lunar surface. As this lunar infrastructure is designed and established, it will be critical to ensure that the various hardware elements work together to both enable the capabilities and to avoid unintended actions. NASA’s Glenn Research Center (GRC) is establishing ground-based testing and emulation facilities to mimic the lunar environment that the surface power and communications infrastructure will operate in. These facilities are intended to represent power and communications providers, users, and interfaces to ensure that systems operate as intended to support the lunar economy. They will empower industry to rapidly evaluate new technologies under realistic conditions. In 2023 GRC is opening a new, state-of-the-art, Aerospace Communications Facility featuring hardware-in-the-loop and ground-to-orbit testbeds. The Multiple Asset Testbed for Research in Innovative Communications Systems (MATRICS) capability will emulate the lunar communications environment, enabling validation of mission concepts and technologies to reduce risk through performance and operations testing, training, and uncover potential issues in compatibility among communication systems providers and users. In addition to the communications testbed, GRC is also developing a full-scale power grid to reduce lunar mission risk. The Adaptable Surface Power Integration and Research (ASPIRE) project aims to reduce mission and hardware risk via high-fidelity integrated testing and pave the way for commercially supplied utility power on the lunar surface. The facility will be scalable and highly adaptable and will be available to NASA, Industry, Academia, and International Partners. ASPIRE will allow developers to integrate and demonstrate their power solutions in a relevant environment, and it will be able to characterize the lunar power performance in representative mission contexts.
The Mission Operations and Data Systems Directorate (MO&DSD) has embarked on a new approach for developing and operating Ground Data Systems (GDS) for flight mission support. This approach is driven by the goals of minimizing cost and maximizing customer satisfaction. Achievement of these goals is realized through the use of a standard set of capabilities which can be modified to meet specific user needs. This approach, which is called the Renaissance architecture, stresses the engineering of integrated systems, based upon workstation/local area network (LAN)/fileserver technology and reusable hardware and software components called 'building blocks.' These building blocks are integrated with mission specific capabilities to build the GDS for each individual mission. The building block approach is key to the reduction of development costs and schedules. Also, the Renaissance approach allows the integration of GDS functions that were previously provided via separate multi-mission facilities. With the Renaissance architecture, the GDS can be developed by the MO&DSD or all, or part, of the GDS can be operated by the user at their facility. Flexibility in operation configuration allows both selection of a cost-effective operations approach and the capability for customizing operations to user needs. Thus the focus of the MO&DSD is shifted from operating systems that we have built to building systems and, optionally, operations as separate services. Renaissance is actually a continuous process. Both the building blocks and the system architecture will evolve as user needs and technology change. Providing GDS on a per user basis enables this continuous refinement of the development process and product and allows the MO&DSD to remain a customer-focused organization. This paper will present the activities and results of the MO&DSD initial efforts toward the establishment of the Renaissance approach for the development of GDS, with a particular focus on both the technical and process implications posed by Renaissance to the MO&DSD.