Search NASA⌕ Search

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.

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

At least 289 records · Page 16

Supporting Crew Autonomy in Deep Space Exploration: Preliminary Onboard Capability Requirements and Proposed Research Questions. Technical Report of the Autonomous Crew Operations Technical Interchange Meeting

Communication delays are a critical challenge posed by long duration deep space exploration. Space missions historically have relied on an ever-present Mission Control Center (MCC) to direct operations in near real-time. As unanticipated anomalies that defeat fault detection and resolution systems do arise, the lack of real-time communication will significantly weaken what the MCC support represents: a reliable safety net for the flight crew through its deep and diverse areas of expertise and investigative resources. As a consequence, future space vehicles and habitats need to be equipped with capabilities to support the flight crew to operate with little or no ground support. Considerations must be given to vehicle and mission designs that will fortify the traditionally ground-centered safety net and forge new support systems, when communication delays exist. In August 2018, NASA’s Human Research Program, through its Human Factors and Behavioral Performance Element, convened a Technical Interchange Meeting (TIM) on Autonomous Crew Operations at NASA Ames Research Center. The goal of the meeting was to gather input from NASA centers, industry, academia, and branches of the Department of Defense (DoD) to address how intelligent technologies can be applied to augment onboard capabilities to support crew anomaly response. The TIM featured 24 presentations by 29 speakers and hosted a total of 59 attendees, including 43 from 5 NASA centers (Ames, Johnson, Langley, Marshall, and Jet Propulsion Lab) and 4 from the DoD (3 from Army Research Lab and 1 from Naval Postgraduate School), with remaining attendees from academia (e.g., UC Davis, CMU) and industry (e.g., IBM, Siemens). Discussions were centered around three themes: standards and guidelines, lessons learned in analog environments, and technologies. To help provide a framework for discussion, a concept matrix describing anomaly response processes was created prior to the TIM (Figure 1, page 6). The matrix captures the steps involved (monitoring and detection, diagnosis, solution development and evaluation, solution implementation and verification, resolution documentation) as well as the resources and capabilities required to support these steps (data, knowledge, analysis, synthesis, resource management). A wallpaper size printout of the matrix was utilized at the TIM to solicit attendee inputs along the three themes; the activity garnered 108 submissions of ideas. Overall, what emerged from TIM discussions was a picture of mismatch between crew anomaly response needs and support that can be provided by existing intelligent technologies. The needs are broad, spanning multiple steps and processes/resources, with many of which lacking support from existing technologies, such as knowledge management throughout the steps of problem solving (especially in resolution documentation) and manpower management. The solutions provided by existing intelligent technologies are specific to the steps/processes that they are designed to support and constrained to solving only problems similar to those that have occurred before. What is lacking from technologies is typically made up by humans, specifically their complex critical thinking, creative problem solving, and domain expertise. In the end, the TIM highlighted the pressing need to support responses to onboard anomalies during autonomous crew operations, particularly those that have eluded the system tests, inspection, and other assurance processes. Such anomalies can potentially threaten crew and vehicle safety, as well as significantly impact overall operations with additional workload. These fairly rare events are difficult to anticipate and prepare for, given the state-of-the-art in intelligent technologies. This is true even for anomalies that stem from “unknown knowns”—cases in which there is sufficient external information to characterize the problem but the overall pattern fails to be recognized by the problem solver, or in which the internal knowledge needed to solve a problem is held tacitly and potentially accessible by the problem solver but not articulated. It follows that the ability to tackle anomalies lies not only with the availability of relevant information and knowledge but also their accessibility in times of need. To that end, we propose research questions along the following three broad themes: • How intelligent technologies can help make relevant knowledge and information available? • How intelligent technologies can help make relevant knowledge and information accessible? • How intelligent technologies can help support the crew operating as a team in anomaly response processes?

autonomous crew operations↗

Hazard Analysis for the Mark III Space Suit Assembly (SSA) Used in One-g Operations

This Hazard Analysis document encompasses the Mark III Space Suit Assembly (SSA) and associated ancillary equipment. It has been prepared using JSC17773, "Preparing Hazard Analyses for JSC Ground Operation", as a guide. The purpose of this document is to present the potential hazards involved in ground (23 % maximum O2, One-g) operations of the Mark III and associated ancillary support equipment system. The hazards listed in this document are specific to suit operations only; each supporting facility (Bldg. 9, etc.) is responsible for test specific Hazard Analyses. A "hazard" is defined as any condition that has the potential for harming personnel or equipment. This analysis was performed to document the safety aspects associated with manned use of the Mark III for pressurized and unpressurized ambient, ground-based, One-g human testing. The hazards identified herein represent generic hazards inherent to all standard JSC test venues for nominal ground test configurations. Non-standard test venues or test specific configurations may warrant consideration of additional hazards analysis prior to test. The cognizant suit engineer is responsible for the safety of the astronaut/test subject, space suit, and suit support personnel. The test requester, for the test supported by the suit test engineer and suited subject, is responsible for overall safety and any necessary Test Readiness Reviews (TRR).

Mitchell, Kate↗

Network command processing system overview

The Network Command Processing System (NCPS) developed for the National Aeronautics and Space Administration (NASA) Ground Network (GN) stations is a spacecraft command system utilizing a MULTIBUS I/68030 microprocessor. This system was developed and implemented at ground stations worldwide to provide a Project Operations Control Center (POCC) with command capability for support of spacecraft operations such as the LANDSAT, Shuttle, Tracking and Data Relay Satellite, and Nimbus-7. The NCPS consolidates multiple modulation schemes for supporting various manned/unmanned orbital platforms. The NCPS interacts with the POCC and a local operator to process configuration requests, generate modulated uplink sequences, and inform users of the ground command link status. This paper presents the system functional description, hardware description, and the software design.

Nam, Yon-Woo↗

Artificial intelligent decision support for low-cost launch vehicle integrated mission operations

The feasibility, benefits, and risks associated with Artificial Intelligence (AI) Expert Systems applied to low cost space expendable launch vehicle systems are reviewed. This study is in support of the joint USAF/NASA effort to define the next generation of a heavy-lift Advanced Launch System (ALS) which will provide economical and routine access to space. The significant technical goals of the ALS program include: a 10 fold reduction in cost per pound to orbit, launch processing in under 3 weeks, and higher reliability and safety standards than current expendables. Knowledge-based system techniques are being explored for the purpose of automating decision support processes in onboard and ground systems for pre-launch checkout and in-flight operations. Issues such as: satisfying real-time requirements, providing safety validation, hardware and Data Base Management System (DBMS) interfacing, system synergistic effects, human interfaces, and ease of maintainability, have an effect on the viability of expert systems as a useful tool.

Szatkowski, Gerard P.↗

Integration of a satellite ground support system based on analysis of the satellite ground support domain

This analysis defines a complete set of ground support functions based on those practiced in real space flight operations during the on-orbit phase of a mission. These functions are mapped against ground support functions currently in use by NASA and DOD. Software components to provide these functions can be hosted on RISC-based work stations and integrated to provide a modular, integrated ground support system. Such modular systems can be configured to provide as much ground support functionality as desired. This approach to ground systems has been widely proposed and prototyped both by government institutions and commercial vendors. The combined set of ground support functions we describe can be used as a standard to evaluate candidate ground systems. This approach has also been used to develop a prototype of a modular, loosely-integrated ground support system, which is discussed briefly. A crucial benefit to a potential user is that all the components are flight-qualified, thus giving high confidence in their accuracy and reliability.

Pendley, R. D.↗

Concept of Operations for Commercial and Business Aircraft Synthetic Vision Systems

A concept of operations (CONOPS) for the Commercial and Business (CaB) aircraft synthetic vision systems (SVS) is described. The CaB SVS is expected to provide increased safety and operational benefits in normal and low visibility conditions. Providing operational benefits will promote SVS implementation in the Net, improve aviation safety, and assist in meeting the national aviation safety goal. SVS will enhance safety and enable consistent gate-to-gate aircraft operations in normal and low visibility conditions. The goal for developing SVS is to support operational minima as low as Category 3b in a variety of environments. For departure and ground operations, the SVS goal is to enable operations with a runway visual range of 300 feet. The system is an integrated display concept that provides a virtual visual environment. The SVS virtual visual environment is composed of three components: an enhanced intuitive view of the flight environment, hazard and obstacle defection and display, and precision navigation guidance. The virtual visual environment will support enhanced operations procedures during all phases of flight - ground operations, departure, en route, and arrival. The applications selected for emphasis in this document include low visibility departures and arrivals including parallel runway operations, and low visibility airport surface operations. These particular applications were selected because of significant potential benefits afforded by SVS.

Williams Daniel M.↗

Web-Altairis: An Internet-Enabled Ground System

This paper describes Web-Altairis, an Internet-enabled ground system software package funded by the Advanced Automation and Architectures Branch (Code 588) of NASA's Goddard Space Flight Center. Web-Altairis supports the trend towards "lights out" ground systems, where the control center is unattended and problems are resolved by remote operators. This client/server software runs on most popular platforms and provides for remote data visualization using the rich functionality of the VisAGE toolkit. Web-Altairis also supports satellite commanding over the Internet. This paper describes the structure of Web-Altairis and VisAGE, the underlying technologies, the provisions for security, and our experiences in developing and testing the software.

Miller, Phil↗

Cross support overview and operations concept for future space missions

Ground networks must respond to the requirements of future missions, which include smaller sizes, tighter budgets, increased numbers, and shorter development schedules. The Consultative Committee for Space Data Systems (CCSDS) is meeting these challenges by developing a general cross support concept, reference model, and service specifications for Space Link Extension services for space missions involving cross support among Space Agencies. This paper identifies and bounds the problem, describes the need to extend Space Link services, gives an overview of the operations concept, and introduces complimentary CCSDS work on standardizing Space Link Extension services.

Stallings, William↗

Satellite Power Systems (SPS) concept definition study. Volume 2, part 2: System engineering

The latest technical and programmatic developments are considered as well as expansions of the Rockwell SPS cost model covering each phase of the program through the year 2030. Comparative cost/economic analyses cover elements of the satellite, construction system, space transportation vehicles and operations, and the ground receiving station. System plans to define time phased costs and planning requirements that support major milestones through the year 2000. A special analysis is included on natural resources required to build the SPS reference configuration. An appendix contains the SPS Work Breakdown Structure and dictionary along with detail cost data sheet on each system and main element of the program. Over 200 line items address DDT&E, theoretical first unit, investment cost per satellite, and operations charges for replacement capital and normal operations and maintenance costs.

Hanley, G. M.↗

Mission Operations, Cubed: NASA Marshall Operations Support for SmallSats

SmallSats have come a long way since the Huntsville Operations Support Center (HOSC) at NASA’s Marshall Space Flight Center supported its first “minisatellite” mission in 2010. And just as SmallSats themselves have evolved in those 12 years, so too has the HOSC’s mission support for SmallSats. Marshall Space Flight Center has a long history with payload and mission operations, including support for the Apollo missions to the moon, the Space Shuttle program, and 21 years of continuous around-the-clock science operations support for research aboard the International Space Station. Today, the HOSC is a multi-tenant facility, supporting not only ISS, but also NASA’s Commercial Crew program, the Space Launch System, the Hubble and Chandra observatories and others – including multiple SmallSat missions. Two SmallSat solar sail missions will be among those taking advantage of the HOSC’s resources for planning, training for and executing mission operations – the Near Earth Asteroid (NEA) Scout and Solar Cruiser missions. One of 10 6U CubeSats manifest on the Artemis I launch of NASA’s Space Launch System rocket this year, NEA Scout’s three-year mission will be supported through a more traditional operations concept, with a dedicated Flight Controller staff operating within the HOSC. Scheduled to launch as part of the Interstellar Mapping and Acceleration Probe (IMAP) in February 2025, Solar Cruiser’s 11-month mission will take a next-generation approach to operations by utilizing a multi-mission flight controller concept, as well as Marshall’s Telescience Resource Kit (TreK). TreK provides a suite of software applications and libraries that allow the Mission Operations Center to serve as an in-house ground system which incorporates remote and automation capability options for engineers and scientists. This presentation will compare the approaches the HOSC will use to support these two missions as a way of demonstrating the array of options NASA MSFC offers for operations support for CubeSat and SmallSat missions.

Darren S Wallace↗

DSN telemetry system, Mark 3-77

A description is given of the DSN Telemetry System, Mark3-77, which is used to support multiple deep space missions. Telemetry functions performed by the Deep Space Stations, Ground Communications Facility, and the Network Operations Control Center are defined. Recent improvements to the system and planned upgrades are described.

Gatz, E. C.↗

Test, Control and Monitor System (TCMS) operations plan

The purpose is to provide a clear understanding of the Test, Control and Monitor System (TCMS) operating environment and to describe the method of operations for TCMS. TCMS is a complex and sophisticated checkout system focused on support of the Space Station Freedom Program (SSFP) and related activities. An understanding of the TCMS operating environment is provided and operational responsibilities are defined. NASA and the Payload Ground Operations Contractor (PGOC) will use it as a guide to manage the operation of the TCMS computer systems and associated networks and workstations. All TCMS operational functions are examined. Other plans and detailed operating procedures relating to an individual operational function are referenced within this plan. This plan augments existing Technical Support Management Directives (TSMD's), Standard Practices, and other management documentation which will be followed where applicable.

Macfarlane, C. K.↗

What Has ExMC Systems Engineering Been Up To Since Last IWS?

Long duration Lunar and Martian missions will change the way NASA currently practices medicine. The missions 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. This element promotes human health and performance in space by advancing medical systems design and risk-informed decision-making for long-duration deep-space exploration missions (LDEMs). ExMC is using system engineering processes and Model-Based System Engineering (MBSE) tools to identify the user needs and requirements of LDEM medical systems. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and the medical system, and directly supports the transition of Earth-reliant International Space Station operations to the Earth-independent operations envisioned for LDEMs. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last IWS, an introduction to upcoming SE talks, and the ongoing systems engineering work.

K. McGuire↗

Taking advantage of ground data systems attributes to achieve quality results in testing software

During the software development life cycle process, basic testing starts with the development team. At the end of the development process, an acceptance test is performed for the user to ensure that the deliverable is acceptable. Ideally, the delivery is an operational product with zero defects. However, the goal of zero defects is normally not achieved but is successful to various degrees. With the emphasis on building low cost ground support systems while maintaining a quality product, a key element in the test process is simulator capability. This paper reviews the Transportable Payload Operations Control Center (TPOCC) Advanced Spacecraft Simulator (TASS) test tool that is used in the acceptance test process for unmanned satellite operations control centers. The TASS is designed to support the development, test and operational environments of the Goddard Space Flight Center (GSFC) operations control centers. The TASS uses the same basic architecture as the operations control center. This architecture is characterized by its use of distributed processing, industry standards, commercial off-the-shelf (COTS) hardware and software components, and reusable software. The TASS uses much of the same TPOCC architecture and reusable software that the operations control center developer uses. The TASS also makes use of reusable simulator software in the mission specific versions of the TASS. Very little new software needs to be developed, mainly mission specific telemetry communication and command processing software. By taking advantage of the ground data system attributes, successful software reuse for operational systems provides the opportunity to extend the reuse concept into the test area. Consistency in test approach is a major step in achieving quality results.

Sigman, Clayton B.↗

Lunar and Mars Exploration: The Autonomy Factor

Long duration space flight crews have relied heavily on almost constant communication with ground control mission support. Ground control teams provide vehicle status and system monitoring, while offering near real time support for specific tasks, emergencies, and ensuring crew health and well being. With extended exploration goals to lunar and Mars outposts, real time communication with ground control teams and the ground s ability to conduct mission monitoring will be very limited compared to the resources provided to current International Space Station (ISS) crews. An operational shift toward more autonomy and a heavier reliance on the crew to monitor their vehicle and operations will be required for these future missions. NASA s future exploration endeavors and the subsequent increased autonomy will require a shift in crew skill composition, i.e. engineer, doctor, mission specialist etc. and lead to new training challenges and mission scenarios. Specifically, operational and design changes will be necessary in many areas including: Habitat Infrastructure and Support Systems, Crew Composition, Training, Procedures and Mission Planning. This paper will specifically address how to apply ISS lessons learned to further use ISS as a test bed to address decreased amounts of ground support to achieve full autonomous operations for lunar and Mars missions. Understanding these lessons learned and applying them to current operations will help to address the future impacts of increased crew autonomy for the lunar and Mars outposts and pave the way for success in increasingly longer mission durations.

Rando, Cynthia M.↗

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.↗

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↗