SEARCH · Search NASA

Results for “Ground Operational Support System”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 325 records · Page 18

All sources NASA NTRS DOE OSTI

NASA NTRS2008

A Simulation Testbed for Airborne Merging and Spacing

The key innovation in this effort is the development of a simulation testbed for airborne merging and spacing (AM&S). We focus on concepts related to airports with Super Dense Operations where new airport runway configurations (e.g. parallel runways), sequencing, merging, and spacing are some of the concepts considered. We focus on modeling and simulating a complementary airborne and ground system for AM&S to increase efficiency and capacity of these high density terminal areas. From a ground systems perspective, a scheduling decision support tool generates arrival sequences and spacing requirements that are fed to the AM&S system operating on the flight deck. We enhanced NASA's Airspace Concept Evaluation Systems (ACES) software to model and simulate AM&S concepts and algorithms.

Santos, Michel↗

NASA NTRS2010

Modeling and Performance Considerations for Automated Fault Isolation in Complex Systems

The purpose of this paper is to document the modeling considerations and performance metrics that were examined in the development of a large-scale Fault Detection, Isolation and Recovery (FDIR) system. The FDIR system is envisioned to perform health management functions for both a launch vehicle and the ground systems that support the vehicle during checkout and launch countdown by using suite of complimentary software tools that alert operators to anomalies and failures in real-time. The FDIR team members developed a set of operational requirements for the models that would be used for fault isolation and worked closely with the vendor of the software tools selected for fault isolation to ensure that the software was able to meet the requirements. Once the requirements were established, example models of sufficient complexity were used to test the performance of the software. The results of the performance testing demonstrated the need for enhancements to the software in order to meet the demands of the full-scale ground and vehicle FDIR system. The paper highlights the importance of the development of operational requirements and preliminary performance testing as a strategy for identifying deficiencies in highly scalable systems and rectifying those deficiencies before they imperil the success of the project

Ferrell, Bob↗

NASA NTRS1994

Intelligent command and control systems for satellite ground operations

The Georgia Tech portion of the Intelligent Control Center project includes several complementary activities. Two major activities entail thesis level research; the other activities are either support activities or preliminary explorations (e.g., task analyses) to support the research. The first research activity is the development of principles for the design of active interfaces to support monitoring during real-time supports. It is well known that as the operator's task becomes less active, i.e., more monitoring and less active control, there is concern that the operator will be less involved and less able to rapidly identify anomalous or failure situations. The research project to design active monitoring interfaces is an attempt to remediate this undesirable side-effect of increasingly automated control systems that still depend ultimately on operator supervision. The second research activity is the exploration of the use of case-based reasoning as a way to accumulate operator experience and make it available in computational form.

Mitchell, Christine M.↗

NASA NTRS2002

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↗

NASA NTRS2014

Simscape Modeling Verification in the Simulink Development Environment

The purpose of the Simulation Product Group of the Control and Data Systems division of the NASA Engineering branch at Kennedy Space Center is to provide a realtime model and simulation of the Ground Subsystems participating in vehicle launching activities. The simulation software is part of the Spaceport Command and Control System (SCCS) and is designed to support integrated launch operation software verification, and console operator training. Using Mathworks Simulink tools, modeling engineers currently build models from the custom-built blocks to accurately represent ground hardware. This is time consuming and costly due to required rigorous testing and peer reviews to be conducted for each custom-built block. Using Mathworks Simscape tools, modeling time can be reduced since there would be no custom-code developed. After careful research, the group came to the conclusion it is feasible to use Simscape's blocks in MatLab's Simulink. My project this fall was to verify the accuracy of the Crew Access Arm model developed using Simscape tools running in the Simulink development environment.

SIMSCAPE↗

NASA NTRS2003

Managing a Product Development Team

Orbiting 380 miles above the earth, NASA s Hubble Space Telescope (HST) has returned a wealth of scientific data about our universe and galaxies beyond highlighted by spectacular images of the birth and death of stars, colliding galaxies, and other extra-worldly events. Despite its tremendous success for almost two decades, the HST ground support system experienced down-to-earth problems prior to the turn of the century, namely budgetary ones. To keep HST operating efficiently to 201 2 and beyond, the Vision 2000 project was conceived with the primary goal of substantially reducing the costs of operating and maintaining the spacecraft ground systems. Taking advantage of this atypical management opportunity, a set of Product Development Teams (PDTs) were established, whose charter was to re-engineer the ground system, and in doing so, reduce the remaining life-of-mission operating and maintenance costs, while providing improved reliability and increased capabilities.

Lehtonen, Kenneth E.↗

NASA NTRS2005

New Directions in Space Operations Services in Support of Interplanetary Exploration

To gain access to the necessary operational processes and data in support of NASA's Lunar/Mars Exploration Initiative, new services, adequate levels of computing cycles and access to myriad forms of data must be provided to onboard spacecraft and ground based personnel/systems (earth, lunar and Martian) to enable interplanetary exploration by humans. These systems, cycles and access to vast amounts of development, test and operational data will be required to provide a new level of services not currently available to existing spacecraft, on board crews and other operational personnel. Although current voice, video and data systems in support of current space based operations has been adequate, new highly reliable and autonomous processes and services will be necessary for future space exploration activities. These services will range from the more mundane voice in LEO to voice in interplanetary travel which because of the high latencies will require new voice processes and standards. New services, like component failure predictions based on data mining of significant quantities of data, located at disparate locations, will be required. 3D or holographic representation of onboard components, systems or family members will greatly improve maintenance, operations and service restoration not to mention crew morale. Current operational systems and standards, like the Internet Protocol, will not able to provide the level of service required end to end from an end point on the Martian surface like a scientific instrument to a researcher at a university. Ground operations whether earth, lunar or Martian and in flight operations to the moon and especially to Mars will require significant autonomy that will require access to highly reliable processing capabilities, data storage based on network storage technologies. Significant processing cycles will be needed onboard but could be borrowed from other locations either ground based or onboard other spacecraft. Reliability will be a key factor with onboard and distributed backup processing an absolutely necessary requirement. Current cluster processing/Grid technologies may provide the basis for providing these services. An overview of existing services, future services that will be required and the technologies and standards required to be developed will be presented. The purpose of this paper will be to initiate a technological roadmap, albeit at a high level, of current voice, video, data and network technologies and standards (which show promise for adaptation or evolution) to what technologies and standards need to be redefined, adjusted or areas where new ones require development. The roadmap should begin the differentiation between non manned and manned processes/services where applicable. The paper will be based in part on the activities of the CCSDS Monitor and Control working group which is beginning the process of standardization of the these processes. Another element of the paper will be based on an analysis of current technologies supporting space flight processes and services at JSC, MSFC, GSFC and to a lesser extent at KSC. Work being accomplished in areas such as Grid computing, data mining and network storage at ARC, IBM and the University of Alabama at Huntsville will be researched and analyzed.

Bradford, Robert N.↗

NASA NTRS1964

Launch vehicle support.

Criteria for power, weight, personnel, cost and development requirements of launch vehicle support operations

PRELAUNCH PROBLEM↗

NASA NTRS1991

NASA's In-Space Technology Experiments Program - Status and plans

The Space Station Freedom constitutes a space facility uniquely suited to space technology-related R&D. Such test data as those involving fluids (power, thermal management, life support systems, and payload operations), space structures, and space materials, cannot be realistically obtained on the ground. The Space Station will also allow the validation of technologies that promise either higher performance or lower costs but which, if not validated in the necessary environment, could pose unacceptable program risks.

Harris, Leonard A.↗

NASA NTRS2002

Monitor and control software for ground systems in the Deep Space Network

Currently, the NMC is being utilized for 24/7 operations at the three main DSN complexes supporting all of the major spacecraft supported and managed by JPL. A portable version of NMC is being exercised in a Compatibility Test Trailer for off-site monitor and control. Remote monitoring of the three complexes at JPL is accomplished as part of the NMC infrastructure.

monitor and control infrastructure spacecraft oper↗

NASA NTRS2006

Built But Not Used, Needed But Not Built: Ground System Guidance Based On Cassini-Huygens Experience

These reflections share insight gleaned from Cassini-Huygens experience in supporting uplink operations tasks with software. Of particular interest are developed applications that were not widely adopted and tasks for which the appropriate application was not planned. After several years of operations, tasks are better understood providing a clearer picture of the mapping of requirements to applications. The impact on system design of the changing user profile due to distributed operations and greater participation of scientists in operations is also explored. Suggestions are made for improving the architecture, requirements, and design of future systems for uplink operations.

telecommunications↗

NASA NTRS2006

Built But Not Used, Needed But Not Built: Ground System Guidance Based On Cassini-Huygens Experience

telecommunications↗

NASA NTRS2007

Integrating Automation into a Multi-Mission Operations Center

NASA Goddard Space Flight Center's Space Science Mission Operations (SSMO) Project is currently tackling the challenge of minimizing ground operations costs for multiple satellites that have surpassed their prime mission phase and are well into extended mission. These missions are being reengineered into a multi-mission operations center built around modern information technologies and a common ground system infrastructure. The effort began with the integration of four SMEX missions into a similar architecture that provides command and control capabilities and demonstrates fleet automation and control concepts as a pathfinder for additional mission integrations. The reengineered ground system, called the Multi-Mission Operations Center (MMOC), is now undergoing a transformation to support other SSMO missions, which include SOHO, Wind, and ACE. This paper presents the automation principles and lessons learned to date for integrating automation into an existing operations environment for multiple satellites.

Surka, Derek M.↗

NASA NTRS2001

Human Centered Autonomous and Assistant Systems Testbed for Exploration Operations

The Engineering and Mission Operations Directorates at NASA Johnson Space Center are combining laboratories and expertise to establish the Human Centered Autonomous and Assistant Systems Testbed for Exploration Operations. This is a testbed for human centered design, development and evaluation of intelligent autonomous and assistant systems that will be needed for human exploration and development of space. This project will improve human-centered analysis, design and evaluation methods for developing intelligent software. This software will support human-machine cognitive and collaborative activities in future interplanetary work environments where distributed computer and human agents cooperate. We are developing and evaluating prototype intelligent systems for distributed multi-agent mixed-initiative operations. The primary target domain is control of life support systems in a planetary base. Technical approaches will be evaluated for use during extended manned tests in the target domain, the Bioregenerative Advanced Life Support Systems Test Complex (BIO-Plex). A spinoff target domain is the International Space Station (ISS) Mission Control Center (MCC). Prodl}cts of this project include human-centered intelligent software technology, innovative human interface designs, and human-centered software development processes, methods and products. The testbed uses adjustable autonomy software and life support systems simulation models from the Adjustable Autonomy Testbed, to represent operations on the remote planet. Ground operations prototypes and concepts will be evaluated in the Exploration Planning and Operations Center (ExPOC) and Jupiter Facility.

Malin, Jane T.↗

NASA NTRS2017

Exploration Medical Capability System Engineering Introduction and Vision

Human exploration missions to beyond low Earth orbit destinations such as Mars will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element's approach to enabling the necessary autonomy. The Element's work must integrate with the overall exploration mission and vehicle design efforts to successfully provide exploration medical capabilities. ExMC is applying systems engineering principles and practices to accomplish its integrative goals. This talk will briefly introduce the discipline of systems engineering and key points in its application to exploration medical capability development. It will elucidate technical medical system needs to be met by the systems engineering work, and the structured and integrative science and engineering approach to satisfying those needs, including the development of shared mental and qualitative models within and external to the human health and performance community. These efforts are underway to ensure relevancy to exploration system maturation and to establish medical system development that is collaborative with vehicle and mission design and engineering efforts.

Mindock, J.↗

NASA NTRS2002

NASA 2nd Generation RLV Program Introduction, Status and Future Plans

The Space Launch Initiative (SLI), managed by the Second Generation Reusable Launch Vehicle (2ndGen RLV) Program, was established to examine the possibility of revolutionizing space launch capabilities, define conceptual architectures, and concurrently identify the advanced technologies required to support a next-generation system. Initial Program funds have been allocated to design, evaluate, and formulate realistic plans leading to a 2nd Gen RLV full-scale development (FSD) decision by 2006. Program goals are to reduce both risk and cost for accessing the limitless opportunities afforded outside Earth's atmosphere fo civil, defense, and commercial enterprises. A 2nd Gen RLV architecture includes a reusable Earth-to-orbit launch vehicle, an on-orbit transport and return vehicle, ground and flight operations, mission planning, and both on-orbit and on-the-ground support infrastructures All segments of the architecture must advance in step with development of the RLV if a next-generation system is to be fully operational early next decade. However, experience shows that propulsion is the single largest contributor to unreliability during ascent, requires the largest expenditure of time for maintenance, and takes a long time to develop; therefore, propulsion is the key to meeting safety, reliability, and cost goals. For these reasons, propulsion is SLI's top technology investment area.

Dumbacher, Dan L.↗

NASA NTRS2004

Telescience Resource Kit Software Capabilities and Future Enhancements

The Telescience Resource Kit (TReK) is a suite of PC-based software applications that can be used to monitor and control a payload on board the International Space Station (ISS). This software provides a way for payload users to operate their payloads from their home sites. It can be used by an individual or a team of people. TReK provides both local ground support system services and an interface to utilize remote services provided by the Payload Operations Integration Center (POIC). by the POIC and to perform local data functions such as processing the data, storing it in local files, and forwarding it to other computer systems. TReK can also be used to build, send, and track payload commands. In addition to these features, work is in progress to add a new command management capability. This capability will provide a way to manage a multi- platform command environment that can include geographically distributed computers. This is intended to help those teams that need to manage a shared on-board resource such as a facility class payload. The environment can be configured such that one individual can manage all the command activities associated with that payload. This paper will provide a summary of existing TReK capabilities and a description of the new command management capability. For example, 7'ReK can be used to receive payload data distributed

Schneider, Michelle↗

NASA NTRSDate not supplied

Custom Integration of Multiple Medical Functionalities

INTRODUCTION: Previous spaceflight experience and results from probabilistic risk assessment of spaceflight medical risk have highlighted the need for vital sign measurements, medical scopes, and clinical imaging tools for managing medical conditions during spaceflight. The Human Research Program’s Exploration Medical Capability (ExMC) Element and the Mars Campaign Office’s Exploration Medical Integrated Product Team (XMIPT) have performed ground-based evaluations of two Commercial-off-the-Shelf (COTS) Multi-functional Integrated Medical (MIM) devices, which integrate various medical capabilities together in one device. The key findings from these evaluations are presented in a complementary presentation, leaving this presentation to focus on forward recommendations for customized integration of multiple medical functionalities. KEY COMPONENTS: The key features of a custom integration of multiple medical functionalities includes devices and capabilities that optimally reduce medical risk. The COTS MIM devices incorporated functionality for best supporting Earth-based, emergency, pre-hospital care. Our custom integration will use probabilistic risk assessment tools, such as the Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT), to determine the optimal functionality to include based on medical risk minimization. An additional feature of custom integration includes the ability to adapt to different requirements within different vehicles and/or missions. The COTS MIM devices store data in patient specific records, however, the format of the records is not modifiable, and data are not easily transferred from the MIM device to a central data architecture outside of the manufacturer’s established system. Our concept for custom integration will use devices that have an open application programming interface, which can easily connect to independent data architectures and third-party visualization software. The ultrasound capabilities included within the COTS MIM devices did not satisfy many of the Artemis Research and Operations Working Group’s ultrasound functional needs, and therefore, incorporation of higher quality ultrasound capabilities within a customized integration will be beneficial. The COTS MIM devices included minimal procedural guidance and clinical decision support tools. Supplemental tools of this type would need to be supplied along with the COTS MIM devices if they were to be used operationally, so another advantage of customization is the ability to integrate these support tools along with the medical functionality, for a more streamlined user experience. CONCLUSION: Investigation of a customized integration of medical functionality provides a method for further understanding the needs of a long-term exploration spaceflight medical system. The crew members of these exploration missions will need to operate more and more independently from Earth-based ground support. Therefore, having an optimized, streamlined medical system, which contains the functionality and supporting information needed, while remaining within mission and vehicle constraints, will help to maintain crew health and performance, which is necessary for achieving high levels of mission success.

B E Lewandowski↗