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.
An analysis of space tug operating techniques is presented. The subjects discussed are: (1) sustaining engineering requirements, (2) off-site facility requirements, (3) evaluation of tug checkout alternatives, and (4) spares provisioning. Tables of data are included to clarify the written presentation.
In order to reduce costs and accelerate vehicle turnaround, a single automated system will be developed to support shuttle launch site operations, replacing a multiplicity of systems used in previous programs. The Launch Processing System will provide real-time control, data analysis, and information display for the checkout, servicing, launch, landing, and refurbishment of the launch vehicles, payloads, and all ground support systems. It will also provide real-time and historical data retrieval for management and sustaining engineering (test records and procedures, logistics, configuration control, scheduling, etc.).
A procedure is described which partitions the recurring costs of the Deep Space Network (DSN) over the individual DSN subsystems. The procedure results in a table showing the maintenance, operations, sustaining engineering and supportive costs for each subsystems.
Four hypersonic research airplane configurations found to be the most cost effective were selected for further refinement. The selection was based on a systematic analysis and evaluation of realistic designs, involving nine different configurations, evolving from three different structural/thermal concepts, coupled with existing rocket and sustainer engines. All configurations were constrained by the mission profiles, research requirements, aerodynamic envelope and maximum launch weight established by NASA.
General conceptual requirements and specific application rules and procedures are provided for the production of software specification documents in conformance with deep space network software standards and class B standards. Class B documentation is identified as the appropriate level applicable to implementation, sustaining engineering, and operational uses by qualified personnel. Special characteristics of class B documents are defined.
This article describes the syntax editing concepts used by the Operations Sustaining Engineering Section in implementing System Performance Test software for the Mark 4-A era. The processing functions are discussed, as well as the necessary data structures and table generation macros used in implementing those functions. In addition, the procedural and software interfaces which have been developed for users of the syntax editor are described, including the forms required for establishing directive and parameter characteristics.
The Environmental Control and Life Support System (ECLSS) is a Freedom Station distributed system with inherent applicability to advanced automation primarily due to the comparatively large reaction times of its subsystem processes. This allows longer contemplation times in which to form a more intelligent control strategy and to detect or prevent faults. The objective of the ECLSS Advanced Automation Project is to reduce the flight and ground manpower needed to support the initial and evolutionary ECLS system. The approach is to search out and make apparent those processes in the baseline system which are in need of more automatic control and fault detection strategies, to influence the ECLSS design by suggesting software hooks and hardware scars which will allow easy adaptation to advanced algorithms, and to develop complex software prototypes which fit into the ECLSS software architecture and will be shown in an ECLSS hardware testbed to increase the autonomy of the system. Covered here are the preliminary investigation and evaluation process, aimed at searching the ECLSS for candidate functions for automation and providing a software hooks and hardware scars analysis. This analysis shows changes needed in the baselined system for easy accommodation of knowledge-based or other complex implementations which, when integrated in flight or ground sustaining engineering architectures, will produce a more autonomous and fault tolerant Environmental Control and Life Support System.
The ground processing and launch of Shuttle vehicles and their payloads is the primary task of Kennedy Space Center. It is a process which is largely manual and contains little inherent automation. Business is conducted today much as it was during previous NASA programs such as Apollo. In light of new programs and decreasing budgets, NASA must find more cost effective ways in which to do business while retaining the quality and safety of activities. Advanced technologies including artificial intelligence could cut manpower and processing time. This paper is an overview of the research and development in Al technology at KSC with descriptions of the systems which have been implemented, as well as a few under development which are promising additions to ground processing software. Projects discussed cover many facets of ground processing activities, including computer sustaining engineering, subsystem monitor and diagnosis tools and launch team assistants. The deployed Al applications have proven an effectiveness which has helped to demonstrate the benefits of utilizing intelligent software in the ground processing task.
The maintenance requirements for Test, Control, and Monitor System (TCMS) and the method for satisfying these requirements prior to First Need Date (FND) of the last TCMS set are described. The method for satisfying maintenance requirements following FND of the last TCMS set will be addressed by a revision to this plan. This maintenance plan serves as the basic planning document for maintenance of this equipment by the NASA Payloads Directorate (CM) and the Payload Ground Operations Contractor (PGOC) at KSC. The terms TCMS Operations and Maintenance (O&M), Payloads Logistics, TCMS Sustaining Engineering, Payload Communications, and Integrated Network Services refer to the appropriate NASA and PGOC organization. For the duration of their contract, the Core Electronic Contractor (CEC) will provide a Set Support Team (SST). One of the primary purposes of this team is to help NASA and PGOC operate and maintain TCMS. It is assumed that SST is an integral part of TCMS O&M. The purpose of this plan is to describe the maintenance concept for TCMS hardware and system software in order to facilitate activation, transition planning, and continuing operation. When software maintenance is mentioned in this plan, it refers to maintenance of TCMS system software.
Viewgraphs on the Space Station Freedom Software Support Environment are presented. After a brief overview of the SSE, the implementation approach and the current and planned functionality are described. The implications and future potential of this common environment for software development and sustaining engineering are also discussed.
This paper focuses on the logistics support to be provided by the APM Center (APMC). Among the Columbus ground infrastructures, this center is tasked to provide logistics, sustaining engineering and P/L integration support to the ongoing missions of the APM, i.e. the Columbus Laboratory attached to the Freedom Space Station. The following is illustrated: an analysis of the requirements that are levied on the logistics support of the APM; how such requirements are reflected in the corresponding support to be available on-ground and at APMC; the functional components of the APMC logistics support and how such components interact each other; how the logistics support function interfaces with the other functions of the ground support; and how the logistics support is being designed in terms of resources (such as hardware, data bases, etc.). Emphasis is given to the data handling aspects and to the related data bases that will constitute for the logistics activities the fundamental source of information during the APM planned lifetime. Functional and physical architectures, together with trades for possible implementation, are addressed. Commonalities with other centers are taken into account and recommendations are made for possible reuse of tools already developed in the C/D phase. Finally, programmatic considerations are discussed for the actual implementation of the center.
The Simulation Virtual Machine (SBM) is an Ada architecture which eases the effort involved in the real-time software maintenance and sustaining engineering. The Software Architecture Standard defines the infrastructure which all the simulation models are built from. SVM was developed for and used in the Space Station Verification and Training Facility.
The National Aeronautics and Space Administration (NASA) supports unmanned space missions through a Deep Space Network (DSN) that is developed and operated by the Jet Propulsion Laboratory (JPL and its subcontractors. The DSN capabilities have been incrementally upgraded since its establishment in the late '50s and are delivered from three Deep Space Communications Complexes (DSCC's) near Goldstone, California, Madrid, Spain, and Canberra, Australia. At present each DSCC includes large antennas with diameters from 11 meters to 70 meters, that operate largely in S-band and X-band frequencies. In addition each DSCC includes all the associated electronics to receive and process the low-level telemetry signals, and radiate the necessary command with high-power transmitters. To accommodate support of the rapidly increasing number of missions by NASA and other space agencies, and to facilitate maintaining and increasing the level of service in a shrinking budget environment, JPL has initiated a bold road map with three key components: 1. A Network Simplification Project (NSP) to upgrade aging electronics, replacing them with modem commercially based components. NSP and related replacement tasks are projected to reduce the cost of operating the DSN by 50% relative to the 1997 levels. 2. Upgrade of all 34-m and 70-m antennas to provision of Ka-Band telemetry downlink capability, complemented by an existing X-band uplink capability. This will increase the effective telemetry downlink capacity by a factor of 4, without building any new antennas. 3. Establishment of an optical communications network to support for high data rate unmanned missions that cannot be accommodated with radiofrequency (RF) communications, as well as establish a path toward support of manned missions at Mars. In this paper we present the mission loading projected for 1998-2008 and the elements of the JPL road map that will enable supporting it with a reduced budget. Particular emphasis will be on streamlining the architecture and to reduce the DSN cost for operations, maintenance and sustaining engineering while at the same time also simplifying and reducing the operations cost for the flight missions.
The EXpedite the processing of Experiments to Space Station or EXPRESS Rack System was developed to provide Space Station accommodations for subrack payloads. The EXPRESS Rack accepts Space Shuttle middeck locker type payloads and International Subrack Interface Standard (ISIS) Drawer payloads, allowing previously flown payloads an opportunity to transition to the International Space Station. The EXPRESS Rack provides power, data command and control, video, water cooling, air cooling, vacuum exhaust, and Nitrogen supply to payloads. The EXPRESS Rack system also includes transportation racks to transport payloads to and from the Space Station, Suitcase Simulators to allow a payload developer to verify data interfaces at the development site, Functional Checkout Units to allow payload checkout at KSC prior to launch, and trainer racks for the astronauts to learn how to operate the EXPRESS Racks prior to flight. Standard hardware and software interfaces provided by the EXPRESS Rack simplify the integration processes, and facilitate simpler ISS payload development. Whereas most ISS Payload facilities are designed to accommodate one specific type of science, the EXPRESS Rack is designed to accommodate multi-discipline research within the same rack allowing for the independent operation of each subrack payload. On-orbit operations began with the EXPRESS Rack Project on April 24, 2001, with one rack operating continuously to support long-running payloads. The other on-orbit EXPRESS Racks operate based on payload need and resource availability. Sustaining Engineering and Logistics and Maintenance functions are in place to maintain operations and to provide software upgrades.
The EXpedite the PRocessing of Experiments to Space Station or EXPRESS Rack System was developed to provide Space Station accommodations for subrack payloads. The EXPRESS Rack accepts Space Shuttle middeck locker type payloads and International Subrack Interface Standard (ISIS) Drawer payloads, allowing previously flown payloads an opportunity to transition to the International Space Station. The EXPRESS Rack provides power, data command and control, video, water cooling, air cooling, vacuum exhaust, and Nitrogen supply to payloads. The EXPRESS Rack system also includes transportation racks to transport payloads to and from the Space Station, Suitcase Simulators to allow a payload developer to verify data interfaces at the development site, Functional Checkout Units to allow payload checkout at KSC prior to launch, and trainer racks for the astronauts to learn how to operate the EXPRESS Racks prior to flight. Standard hardware and software interfaces provided by the EXPRESS Rack simplify the integration processes, and facilitate simpler ISS payload development. Whereas most ISS Payload facilities are designed to accommodate one specific type of science, the EXPRESS Rack is designed to accommodate multi-discipline research within the same rack allowing for the independent operation of each subrack payload. On-orbit operations began with the EXPRESS Rack Project on April 24, 2001, with one rack operating continuously to support long-running payloads. The other on-orbit EXPRESS Racks operate based on payload need and resource availability. Sustaining Engineering and Logistics and Maintenance functions are in place to maintain operations and to provide software upgrades.
As part of the Sustaining Engineering program for the International Space Station (ISS), a ground simulator of the Internal Thermal Control System (ITCS) in the Lab Module was designed and built at the Marshall Space Flight Center (MSFC). To support prediction and troubleshooting, this facility is operationally and functionally similar to the flight system and flight-like components were used when available. Flight software algorithms, implemented using the LabVIEW(Registered Trademark) programming language, were used for monitoring performance and controlling operation. Validation testing of the low temperature loop was completed prior to activation of the Lab module in 2001. Assembly of the moderate temperature loop was completed in 2002 and validated in 2003. The facility has been used to address flight issues with the ITCS, successfully demonstrating the ability to add silver biocide and to adjust the pH of the coolant. Upon validation of the entire facility, it will be capable not only of checking procedures, but also of evaluating payload timelining, operational modifications, physical modifications, and other aspects affecting the thermal control system.
The contents include the following: High availability. Hardware is in harsh environment. Flight processor (constraints) very widely due to power and weight constraints. Software must be remotely modifiable and still operate while changes are being made. Many custom one of kind interfaces for one of a kind missions. Sustaining engineering. Price of failure is high, tens to hundreds of millions of dollars.
A mission-systems architecture based on a highly modular "systems of systems" infrastructure utilizing open-standards hardware and software interfaces as the enabling technology is absolutely essential for an affordable and sustainable space exploration program. This architecture requires (a) robust communication between heterogeneous systems, (b) high reliability, (c) minimal mission-to-mission reconfiguration, (d) affordable development, system integration, and verification of systems, and (e) minimum sustaining engineering. This paper proposes such an architecture. Lessons learned from the space shuttle program are applied to help define and refine the model.