Search NASA⌕ Search

SEARCH · Search NASA

Results for “Ground Systems Development and Operations”

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 109 records · Page 6

Using SFOC to fly the Magellan Venus mapping mission

Traditionally, spacecraft flight operations at the Jet Propulsion Laboratory (JPL) have been performed by teams of spacecraft experts utilizing ground software designed specifically for the current mission. The Jet Propulsion Laboratory set out to reduce the cost of spacecraft mission operations by designing ground data processing software that could be used by multiple spacecraft missions, either sequentially or concurrently. The Space Flight Operations Center (SFOC) System was developed to provide the ground data system capabilities needed to monitor several spacecraft simultaneously and provide enough flexibility to meet the specific needs of individual projects. The Magellan Spacecraft Team utilizes the SFOC hardware and software designed for engineering telemetry analysis, both real-time and non-real-time. The flexibility of the SFOC System has allowed the spacecraft team to integrate their own tools with SFOC tools to perform the tasks required to operate a spacecraft mission. This paper describes how the Magellan Spacecraft Team is utilizing the SFOC System in conjunction with their own software tools to perform the required tasks of spacecraft event monitoring as well as engineering data analysis and trending.

Bucher, Allen W.↗

Safety management of a complex R&D ground operating system

A perspective on safety program management has been developed for a complex R&D operating system, such as the NASA-Lewis Research Center. Using a systems approach, hazardous operations are subjected to third-party reviews by designated area safety committees and are maintained under safety permit controls. To insure personnel alertness, emergency containment forces and employees are trained in dry-run emergency simulation exercises. The keys to real safety effectiveness are top management support and visibility of residual risks.

Connors, J. F.↗

Security aspects of space operations data

This paper deals with data security. It identifies security threats to European Space Agency's (ESA) In Orbit Infrastructure Ground Segment (IOI GS) and proposes a method of dealing with its complex data structures from the security point of view. It is part of the 'Analysis of Failure Modes, Effects Hazards and Risks of the IOI GS for Operations, including Backup Facilities and Functions' carried out on behalf of the European Space Operations Center (ESOC). The security part of this analysis has been prepared with the following aspects in mind: ESA's large decentralized ground facilities for operations, the multiple organizations/users involved in the operations and the developments of ground data systems, and the large heterogeneous network structure enabling access to (sensitive) data which does involve crossing organizational boundaries. An IOI GS data objects classification is introduced to determine the extent of the necessary protection mechanisms. The proposal of security countermeasures is oriented towards the European 'Information Technology Security Evaluation Criteria (ITSEC)' whose hierarchically organized requirements can be directly mapped to the security sensitivity classification.

Schmitz, Stefan↗

Software Design Methodology Migration for a Distributed Ground System

The Marshall Space Flight Center's (MSFC) Payload Operations Center (POC) ground system has been developed and has evolved over a period of about 10 years. During this time the software processes have migrated from more traditional to more contemporary development processes. The new Software processes still emphasize requirements capture, software configuration management, design documenting, and making sure the products that have been developed are accountable to initial requirements. This paper will give an overview of how the Software Process have evolved highlighting the positives as well as the negatives. In addition, we will mention the COTS tools that have been integrated into the processes and how the COTS have provided value to the project .

Ritter, George↗

Configurable technology development for reusable control and monitor ground systems

The control monitor unit (CMU) uses configurable software technology for real-time mission command and control, telemetry processing, simulation, data acquisition, data archiving, and ground operations automation. The base technology is currently planned for the following control and monitor systems: portable Space Station checkout systems; ecological life support systems; Space Station logistics carrier system; and the ground system of the Delta Clipper (SX-2) in the Single-Stage Rocket Technology program. The CMU makes extensive use of commercial technology to increase capability and reduce development and life-cycle costs. The concepts and technology are being developed by McDonnell Douglas Space and Defense Systems for the Real-Time Systems Laboratory at NASA's Kennedy Space Center under the Payload Ground Operations Contract. A second function of the Real-Time Systems Laboratory is development and utilization of advanced software development practices.

Uhrlaub, David R.↗

X-33 Reusable Launch Vehicle Demonstrator, Spaceport and Range

The X-33 was a suborbital reusable spaceplane demonstrator, in development from 1996 to early 2001. The intent of the demonstrator was to lower the risk of building and operating a full-scale reusable vehicle fleet. Reusable spaceplanes offered the potential to lower the cost of access to space by an order of magnitude, compared with conventional expendable launch vehicles. Although a cryogenic tank failure during testing ultimately led to the end of the effort, the X-33 team celebrated many successes during the development. This paper summarizes some of the accomplishments and milestones of this X-vehicle program, from the perspective of an engineer who was a member of the team throughout the development. X-33 Program accomplishments include rapid, flight hardware design, subsystem testing and fabrication, aerospike engine development and testing, Flight Operations Center and Operations Control Center ground systems design and construction, rapid Environmental Impact Statement NEPA process approval, Range development and flight plan approval for test flights, and full-scale system concept design and refinement. Lessons from the X-33 Program may have potential application to new RLV and other aerospace systems being developed a decade later.

Letchworth, Gary F.↗

1-G Human Factors for Optimal Processing and Operability of Ground Systems Up to CxP GOP PDR

This slide presentation reviews the development and use of a process and tool for developing these requirements and improve the design for ground operations. A Human Factors Engineering Analysis (HFEA) Tool was developed to create a dedicated subset of requirements from the FAA requirements for each subsystem. As an example the use of the human interface with an actuator motor is considered.

Stambolian, Damon B.↗

Study of application of space telescope science operations software for SIRTF use

The design and development of the Space Telescope Science Operations Ground System (ST SOGS) was evaluated to compile a history of lessons learned that would benefit NASA's Space Infrared Telescope Facility (SIRTF). Forty-nine specific recommendations resulted and were categorized as follows: (1) requirements: a discussion of the content, timeliness and proper allocation of the system and segment requirements and the resulting impact on SOGS development; (2) science instruments: a consideration of the impact of the Science Instrument design and data streams on SOGS software; and (3) contract phasing: an analysis of the impact of beginning the various ST program segments at different times. Approximately half of the software design and source code might be useable for SIRTF. Transportability of this software requires, at minimum, a compatible DEC VAX-based architecture and VMS operating system, system support software similar to that developed for SOGS, and continued evolution of the SIRTF operations concept and requirements such that they remain compatible with ST SOGS operation.

Dignam, F.↗

1-G Human Factors for Optimal Processing and Operability of Ground Systems up to CxP GOP PDR

During the mid stages of design development, up to Constellation Program (CxP) Preliminary Design Review (PDR), the requirements for leveraging I-G human factors for optimizing ground processing of Flight Hardware were mature for levels - 2, 3, 4, and 5. This paper gives an overview of the accomplishments achieved during that time. The main focus of this paper will be on the CxP Ground Operations Project human factors engineering analysis process using a Human Factors Engineering Analysis Tool (HFEAT) for developing the level- 5 requirements effecting the design development of the subsystems for Ground Support System (GSS), and Ground Support Equipment (GSE).

Stambolian, Damon B.↗

Distributed operating system for NASA ground stations

NASA ground stations are characterized by ever changing support requirements, so application software is developed and modified on a continuing basis. A distributed operating system was designed to optimize the generation and maintenance of those applications. Unusual features include automatic program generation from detailed design graphs, on-line software modification in the testing phase, and the incorporation of a relational database within a real-time, distributed system.

Doyle, John F.↗

Evolution paths for advanced automation

As Space Station Freedom (SSF) evolves, increased automation and autonomy will be required to meet Space Station Freedom Program (SSFP) objectives. As a precursor to the use of advanced automation within the SSFP, especially if it is to be used on SSF (e.g., to automate the operation of the flight systems), the underlying technologies will need to be elevated to a high level of readiness to ensure safe and effective operations. Ground facilities supporting the development of these flight systems -- from research and development laboratories through formal hardware and software development environments -- will be responsible for achieving these levels of technology readiness. These facilities will need to evolve support the general evolution of the SSFP. This evolution will include support for increasing the use of advanced automation. The SSF Advanced Development Program has funded a study to define evolution paths for advanced automaton within the SSFP's ground-based facilities which will enable, promote, and accelerate the appropriate use of advanced automation on-board SSF. The current capability of the test beds and facilities, such as the Software Support Environment, with regard to advanced automation, has been assessed and their desired evolutionary capabilities have been defined. Plans and guidelines for achieving this necessary capability have been constructed. The approach taken has combined indepth interviews of test beds personnel at all SSF Work Package centers with awareness of relevant state-of-the-art technology and technology insertion methodologies. Key recommendations from the study include advocating a NASA-wide task force for advanced automation, and the creation of software prototype transition environments to facilitate the incorporation of advanced automation in the SSFP.

Healey, Kathleen J.↗

Automated Ground Umbilical Systems (AGUS) Project

All space vehicles require ground umbilical systems for servicing. Servicing requirements can include, but are not limited to, electrical power and control, propellant loading and venting, pneumatic system supply, hazard gas detection and purging as well as systems checkout capabilities. Of the various types of umbilicals, all require several common subsystems. These typically include an alignment system, mating and locking system, fluid connectors, electrical connectors and control !checkout systems. These systems have been designed to various levels of detail based on the needs for manual and/or automation requirements. The Automated Ground Umbilical Systems (AGUS) project is a multi-phase initiative to develop design performance requirements and concepts for launch system umbilicals. The automation aspect minimizes operational time and labor in ground umbilical processing while maintaining reliability. This current phase of the project reviews the design, development, testing and operations of ground umbilicals built for the Saturn, Shuttle, X-33 and Atlas V programs. Based on the design and operations lessons learned from these systems, umbilicals can be optimized for specific applications. The product of this study is a document containing details of existing systems and requirements for future automated umbilical systems with emphasis on design-for-operations (DFO).

Gosselin, Armand M.↗

An intelligent position-specific training system for mission operations

Marshall Space Flight Center's (MSFC's) payload ground controller training program provides very good generic training; however, ground controller position-specific training can be improved by including position-specific training systems in the training program. This report explains why MSFC needs to improve payload ground controller position-specific training. The report describes a generic syllabus for position-specific training systems, a range of system designs for position-specific training systems, and a generic development process for developing position-specific training systems. The report also describes a position-specific training system prototype that was developed for the crew interface coordinator payload operations control center ground controller position. The report concludes that MSFC can improve the payload ground controller training program by incorporating position-specific training systems for each ground controller position; however, MSFC should not develop position-specific training systems unless payload ground controller position experts will be available to participate in the development process.

Schneider, M. P.↗

Human-Automation Allocations for Current Robotic Space Operations

Within the Human Research Program, one risk delineates the uncertainty surrounding crew working with automation and robotics in spaceflight. The Risk of Inadequate Design of Human and Automation/Robotic Integration (HARI) is concerned with the detrimental effects on crew performance due to ineffective user interfaces, system designs and/or functional task allocation, potentially compromising mission success and safety. Risk arises because we have limited experience with complex automation and robotics. One key gap within HARI, is the gap related to functional allocation. The gap states: We need to evaluate, develop, and validate methods and guidelines for identifying human-automation/robot task information needs, function allocation, and team composition for future long duration, long distance space missions. Allocations determine the human-system performance as it identifies the functions and performance levels required by the automation/robotic system, and in turn, what work the crew is expected to perform and the necessary human performance requirements. Allocations must take into account each of the human, automation, and robotic systems capabilities and limitations. Some functions may be intuitively assigned to the human versus the robot, but to optimize efficiency and effectiveness, purposeful role assignments will be required. The role of automation and robotics will significantly change in future exploration missions, particularly as crew becomes more autonomous from ground controllers. Thus, we must understand the suitability of existing function allocation methods within NASA as well as the existing allocations established by the few robotic systems that are operational in spaceflight. In order to evaluate future methods of robotic allocations, we must first benchmark the allocations and allocation methods that have been used. We will present 1) documentation of human-automation-robotic allocations in existing, operational spaceflight systems; and 2) To gather existing lessons learned and best practices in these role assignments, from spaceflight operational experience of crew and ground teams that may be used to guide development for future systems. NASA and other space agencies have operational spaceflight experience with two key Human-Automation-Robotic (HAR) systems: heavy lift robotic arms and planetary robotic explorers. Additionally, NASA has invested in high-fidelity rover systems that can carry crew, building beyond Apollo's lunar rover. The heavy lift robotic arms reviewed are: Space Station Remote Manipulator System (SSRMS), Japanese Remote Manipulator System (JEMRMS), and the European Robotic Arm (ERA, designed but not deployed in space). The robotic rover systems reviewed are: Mars Exploration Rovers, Mars Science Laboratory rover, and the high-fidelity K10 rovers. Much of the design and operational feedback for these systems have been communicated to flight controllers and robotic design teams. As part of the mitigating the HARI risk for future human spaceflight operations, we must document function allocations between robots and humans that have worked well in practice.

robotic allocation↗

Development of a Space Station Operations Management System

To enhance the productivity of operations aboard the Space Station, a means must be provided to augment, and frequently to supplant, human effort in support of mission operations and management, both on the ground and onboard. The Operations Management System (OMS), under development at the Johnson Space Center, is one such means. OMS comprises the tools and procedures to facilitate automation of station monitoring, control, and mission planning tasks. OMS mechanizes, and hence rationalizes, execution of tasks traditionally performed by mission planners, the mission control center team, onboard System Management software, and the flight crew.

Brandli, A. E.↗

Progress Towards a 2012 Landsat Launch

The Landsat Data Continuity Mission (LDCM) is on schedule for a December 2012 launch date. The mission is being managed by an interagency partnership between NASA and the U.S. Geological Survey (USGS). NASA leads the development and launch of the satellite observatory while leads ground system development. USGS will assume responsibility for operating the satellite and for collecting, archiving, and distributing the LDCM data following launch. When launched the satellite will carry two sensors into orbit. The Operational Land Imager (OLI) will collect data for nine shortwave spectral bands with a spatial resolution of 30 m (with a 15 m panchromatic band). The Thermal Infrared Sensor (TIRS) will coincidently collect data for two thermal infrared bands with a spatial resolution of 100 m. The OLI is fully assembled and tested and has been shipped by it?s manufacturer, Ball Aerospace and Technology Corporation, to the Orbital Sciences Corporation (Orbital) facility where it is being integrated onto the LDCM spacecraft. Pre-launch testing indicates that OLI will meet all performance specification with margin. TIRS is in development at the NASA Goddard Space Flight Center (GSFC) and is in final testing before shipping to the Orbital facility in January, 2012. The ground data processing system is in development at the USGS Earth Resources Observation and Science (EROS) Center. The presentation will describe the LDCM satellite system, provide the status of system development, and present prelaunch performance data for OLI and TIRS. The USGS has committed to renaming the satellite as Landsat 8 following launch.

Irons, Jim↗

Mission Design & Operations Approach for the HelioSwarm Mission

HelioSwarm: The Nature of Turbulence in Space Plasmas is a transformational mission to explore the dynamic three-dimensional mechanisms controlling the physics of plasma turbulence, a ubiquitous process occurring in the heliosphere and plasmas throughout the universe. Turbulence is the process by which energy contained in fluctuating magnetic fields and plasma motion cascades from large to smaller spatial scales. HelioSwarm achieves its science goals by making simultaneous measurements across a wide range of measurement baselines, spanning magnetohydrodynamic scales (1000’s of km) to sub-ion heating scales (10’s of km), using a novel nine-spacecraft swarm. The swarm operates in a high-altitude lunar resonant Earth orbit (two-week period, ~63 RE apogee, ~13 RE perigee), giving it access to both the pristine solar wind and regions of strongly driven turbulence (specifically the magnetosphere and foreshock), and utilizes customized relative orbital motion of the swarm members to produce the range of measurement baselines and configurations. The swarm comprises eight “node” spacecraft, manufactured by Blue Canyon Technologies, and a “hub” spacecraft produced by Northrop Grumman Corp. The hub serves as a communications relay, with all communications between the ground and the nodes flowing through it. Mission operations are conducted within the Multi-Mission Operations Center at the NASA Ames Research Center and science operations at the University of New Hampshire, Durham. HelioSwarm was selected in 2022 as one of NASA’s newest Heliophysics Explorer missions to proceed from mission concept into mission implementation, with a target launch in 2029. This paper provides an overview of the mission’s science goals and objectives, the mission design, and the concept of operations, with an emphasis on how the swarm aspects of the mission both enable the science measurements and present unique operational challenges. The paper then describes the proposed development approach for the mission operations system and ground data system which relies on a selective combination of scaling strategies to meet the challenges.

HelioSwarm↗

Lessons Learned on Implementing Fault Detection, Isolation, and Recovery (FDIR) in a Ground Launch Environment

This paper's main purpose is to detail issues and lessons learned regarding designing, integrating, and implementing Fault Detection Isolation and Recovery (FDIR) for Constellation Exploration Program (CxP) Ground Operations at Kennedy Space Center (KSC). Part of the0 overall implementation of National Aeronautics and Space Administration's (NASA's) CxP, FDIR is being implemented in three main components of the program (Ares, Orion, and Ground Operations/Processing). While not initially part of the design baseline for the CxP Ground Operations, NASA felt that FDIR is important enough to develop, that NASA's Exploration Systems Mission Directorate's (ESMD's) Exploration Technology Development Program (ETDP) initiated a task for it under their Integrated System Health Management (ISHM) research area. This task, referred to as the FDIIR project, is a multi-year multi-center effort. The primary purpose of the FDIR project is to develop a prototype and pathway upon which Fault Detection and Isolation (FDI) may be transitioned into the Ground Operations baseline. Currently, Qualtech Systems Inc (QSI) Commercial Off The Shelf (COTS) software products Testability Engineering and Maintenance System (TEAMS) Designer and TEAMS RDS/RT are being utilized in the implementation of FDI within the FDIR project. The TEAMS Designer COTS software product is being utilized to model the system with Functional Fault Models (FFMs). A limited set of systems in Ground Operations are being modeled by the FDIR project, and the entire Ares Launch Vehicle is being modeled under the Functional Fault Analysis (FFA) project at Marshall Space Flight Center (MSFC). Integration of the Ares FFMs and the Ground Processing FFMs is being done under the FDIR project also utilizing the TEAMS Designer COTS software product. One of the most significant challenges related to integration is to ensure that FFMs developed by different organizations can be integrated easily and without errors. Software Interface Control Documents (ICDs) for the FFMs and their usage will be addressed as the solution to this issue. In particular, the advantages and disadvantages of these ICDs across physically separate development groups will be delineated.

Ferrell, Bob A.↗