Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Ground 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 703 records · Page 39
All sourcesNASA NTRSDOE OSTI
NASA NTRS1988

Flight and ground packet telemetry systems activities at NASA's Goddard Space Flight Center

NASA's Goddard Space Flight Center (GSFC) has the responsibility for the telemetry ground data processing for two current spacecraft which use packet telemetry. These spacecraft are the Hubble Space Telescope (HST) and the Gamma Ray Observatory (GRO). GSFC has designed and built two ground systems to meet this responsibility. The first is the HST DATA Capture Facility (DCF), which has now completed its integration and test phase and is supporting spacecraft and data flow tests. The second is the Packet Processor System (Pacor). This system became operational in July 1987. These systems are known generally as Level Zero Processors. Level Zero Processors ingest telemetry composite bit streams, output selected user specific data in real time, and in a batch mode perform all necessary processing to produce individual user data files which are, within the limits of the quality of the received data, contiguous, complete, ordered and nonredundant.

Carper, Richard D.↗
NASA NTRS1977

Parametric design of ground data processing/support systems for advanced sensor systems

A parametric system design technique has been applied to ground data processing/support systems for advanced sensor applications. The system establishes a direct link between budget analysts and system planners. Three primary phases are identified: the definition of requirements, system design, and system costing. The system is evaluated for three cases: (1) a study of ground data handling systems for earth resource satellites, (2) a ground data mass storage and processing system for agricultural remote-sensing studies, and (3) a parametric study of shuttle era data processing support required for atmospheric and space physics.

Denny, C.↗
NASA NTRS1993

Lessons learned - MO&DA at JPL

The issues of how to avoid future surprise growth in Mission Operations and Data Analysis (MO&DA) costs and how to minimize total MO&DA costs for planetary missions are discussed within the context of JPL mission operations support. It is argued that there is no simple, single solution: the entire Project life-cycle must be addressed. It is concluded that cost models that can predict both MO&DA cost as well as Ground System development costs are needed. The first year MO&DA budget plotted against the total of ground and flight systems developments is shown. In order to better recognize changes and control costs in general, a modified funding line item breakdown is recommended to distinguish between development costs (prelaunch and postlaunch) and MO&DA costs.

Handley, Thomas H., Jr.↗
NASA NTRS1997

AMOS: Generic Planetary Mission Ops

The spacecraft control community is focusing increasing attention on various forms of architectures. Studies on software architectures and related technologies have been commissioned by DOD programs. The purpose of planning a series of annual workshops is to bring together participants working in the Spacecraft Ground System (SGS) domain. The overall intent of these workshops is to expedite the transition to common consensus-based open software architectures for SGSs.

workshops SGS technologies↗
NASA NTRS1994

Experience with the EURECA Packet Telemetry and Packet Telecommand system

The European Retrieval Carrier (EURECA) was launched on its first flight on the 31st of July 1992 and retrieved on the 29th of June 1993. EURECA is characterized by several new on-board features, most notably Packet telemetry, and a partial implementation of packet telecommanding, the first ESA packetised spacecraft. Today more than one year after the retrieval the data from the EURECA mission has to a large extent been analysed and we can present some of the interesting results. This paper concentrates on the implementation and operational experience with the EURECA Packet Telemetry and Packet Telecommanding. We already discovered during the design of the ground system that the use of packet telemetry has major impact on the overall design and that processing of packet telemetry may have significant effect on the computer loading and sizing. During the mission a number of problems were identified with the on-board implementation resulting in very strange anomalous behaviors. Many of these problems directly violated basic assumptions for the design of the ground segment adding to the strange behavior. The paper shows that the design of a telemetry packet system should be flexible enough to allow a rapid configuration of the telemetry processing in order to adapt it to the new situation in case of an on-board failure. The experience gained with the EURECA mission control should be used to improve ground systems for future missions.

Sorensen, Erik Mose↗
NASA NTRS1981

On-board computer progress in development of A 310 flight testing program

Onboard computer progress in development of an Airbus A 310 flight testing program is described. Minicomputers were installed onboard three A 310 airplanes in 1979 in order to: (1) assure the flight safety by exercising a limit check of a given set of parameters; (2) improve the efficiency of flight tests and allow cost reduction; and (3) perform test analysis on an external basis by utilizing onboard flight types. The following program considerations are discussed: (1) conclusions based on simulation of an onboard computer system; (2) brief descriptions of A 310 airborne computer equipment, specifically the onboard universal calculator (CUB) consisting of a ROLM 1666 system and visualization system using an AFIGRAF CRT; (3) the ground system and flight information inputs; and (4) specifications and execution priorities for temporary and permanent programs.

Reau, P.↗
NASA NTRS1987

Expert systems tools for Hubble Space Telescope observation scheduling

This paper discusses the utility of expert systems techniques for Hubble Space Telescope (HST) planning and scheduling and describes a plan for development of expert system tools which will augment the existing ground system. Additional capabilities provided by these tools will include graphics-oriented plan evaluation, long-range analysis of the observation pool, analysis of optimal scheduling time intervals, constructing sequences of spacecraft activities which minimize operational overhead, and optimization of linkages between observations. Initial prototyping of a scheduler used the Automated Reasoning Tool running on a LISP workstation.

Miller, Glenn↗
NASA NTRS1987

Expert systems tools for Hubble Space Telescope observation scheduling

The utility of expert systems techniques for the Hubble Space Telescope (HST) planning and scheduling is discussed and a plan for development of expert system tools which will augment the existing ground system is described. Additional capabilities provided by these tools will include graphics-oriented plan evaluation, long-range analysis of the observation pool, analysis of optimal scheduling time intervals, constructing sequences of spacecraft activities which minimize operational overhead, and optimization of linkages between observations. Initial prototyping of a scheduler used the Automated Reasoning Tool running on a LISP workstation.

Miller, Glenn↗
NASA NTRS1993

Cost effective data system design approach for EOS AM-1

The question of how to design a cost-effective data system for a space-based application with a high aggregate data rate is addressed. The steps used by the EOS AM-1 design team are defined. A summary of the design as of January 1993 is outlined. The AM-1 Science Data system is comprised of one subsystem that ingests, formats, and routes data - the Science Formatting Equipment (SFE), and another that records the data. Key interfaces are the interfaces to the high rate science instruments, the real-time transmitters, and the internal interface between the SFR and the Solid State Recorder. A cost-effective design approach for the AM-1 data system must take into account impacts on ground systems, data processing facilities, availability of data for real-time users, and future spacecraft designs.

Westmeyer, Paul A.↗
NASA NTRS1993

Automatic tools for system testing

As spacecraft control and other space-related ground systems become increasingly complex, the effort required in testing and validation also increases. Implementation of a spacecraft control system normally involves a number of incremental deliveries. In addition kernel or general purpose software may also be involved, which must itself be considered in the integration and testing program. Tools can be used to assist this testing. These can reduce the effort required or alternatively they can ensure that for a given level of effort, a better job is done. Great benefit could be derived by automating certain types of testing (interactive software) which up to now has been performed manually at a terminal. This paper reports on an on-going study. The study examines means of automating spacecraft control system testing, evaluates relevant commercial tools and aims to prototype basic automatic testing functions.

Peccia, N. M.↗
NASA NTRS2008

Linking and Combining Distributed Operations Facilities using NASA's "GMSEC" Systems Architectures

NASA's Goddard Mission Services Evolution Center (GMSEC) ground system architecture has been in development since late 2001, has successfully supported eight orbiting satellites and is being applied to many of NASA's future missions. GMSEC can be considered an event-driven service-oriented architecture built around a publish/subscribe message bus middleware. This paper briefly discusses the GMSEC technical approaches which have led to significant cost savings and risk reduction for NASA missions operated at the Goddard Space Flight Center (GSFC). The paper then focuses on the development and operational impacts of extending the architecture across multiple mission operations facilities.

Smith, Danford↗
NASA NTRS2013

Towards a Decision Support System for Space Flight Operations

The Mission Operations Directorate (MOD) at the Johnson Space Center (JSC) has put in place a Model Based Systems Engineering (MBSE) technological framework for the development and execution of the Flight Production Process (FPP). This framework has provided much added value and return on investment to date. This paper describes a vision for a model based Decision Support System (DSS) for the development and execution of the FPP and its design and development process. The envisioned system extends the existing MBSE methodology and technological framework which is currently in use. The MBSE technological framework currently in place enables the systematic collection and integration of data required for building an FPP model for a diverse set of missions. This framework includes the technology, people and processes required for rapid development of architectural artifacts. It is used to build a feasible FPP model for the first flight of spacecraft and for recurrent flights throughout the life of the program. This model greatly enhances our ability to effectively engage with a new customer. It provides a preliminary work breakdown structure, data flow information and a master schedule based on its existing knowledge base. These artifacts are then refined and iterated upon with the customer for the development of a robust end-to-end, high-level integrated master schedule and its associated dependencies. The vision is to enhance this framework to enable its application for uncertainty management, decision support and optimization of the design and execution of the FPP by the program. Furthermore, this enhanced framework will enable the agile response and redesign of the FPP based on observed system behavior. The discrepancy of the anticipated system behavior and the observed behavior may be due to the processing of tasks internally, or due to external factors such as changes in program requirements or conditions associated with other organizations that are outside of MOD. The paper provides a roadmap for the three increments of this vision. These increments include (1) hardware and software system components and interfaces with the NASA ground system, (2) uncertainty management and (3) re-planning and automated execution. Each of these increments provide value independently; but some may also enable building of a subsequent increment.

Meshkat, Leila↗
NASA NTRS2017

Exploration Medical System Technical Development

The Exploration Medical Capability (ExMC) Element systems engineering goals include defining the technical system needed to implement exploration medical capabilities for Mars. This past year, scenarios captured in the medical system concept of operations laid the foundation for systems engineering technical development work. The systems engineering team analyzed scenario content to identify interactions between the medical system, crewmembers, the exploration vehicle, and the ground system. This enabled the definition of functions the medical system must provide and interfaces to crewmembers and other systems. These analyses additionally lead to the development of a conceptual medical system architecture. The work supports the ExMC community-wide understanding of the functional exploration needs to be met by the medical system, the subsequent development of medical system requirements, and the system verification and validation approach utilizing terrestrial analogs and precursor exploration missions.

McGuire, K.↗
NASA NTRS2018

Nasa's Space Launch System: Exceptional Opportunities for Secondary Payloads to Deep Space

When NASA’s Space Launch System (SLS) launches for the first time from Kennedy Space Center, it will send the Orion crew vehicle farther into space than a human-rated spacecraft has ever traveled. The primary objectives of this first uncrewed mission, Exploration Mission-1 (EM-1), focus on verifying and validating the new technologies and integrated systems developed for SLS, Orion and Exploration Ground Systems (EGS), which together comprise NASA’s new deep space exploration system. EM-1 also provides the opportunity for 13 6U CubeSat secondary payloads to be deployed in deep space. As progress is being made toward that first launch, planning is also taking place for secondary payload opportunities on future missions. This paper will provide an overview of the status of the SLS Block 1 launch vehicle and an overview of the 6U payloads selected for EM-1. In addition, an overview of the EM-1 mission trajectories and the “bus stops” along the trajectory where the payloads will be deployed will be noted. Challenges and new workflows required in identifying and certifying potential payloads will be discussed. The paper will also discuss opportunities that will be presented by future evolutions of SLS.

Robinson, Kimberly F.↗
NASA NTRS2013

Towards a decision support system for space flight operations

The Mission Operations Directorate (MOD) at the Johnson Space Center (JSC) has put in place a Model Based Systems Engineering (MBSE) technological framework for the development and execution of the Flight Production Process (FPP). This framework has provided much added value and return on investment to date. This paper describes a vision for a model based Decision Support System (DSS) for the development and execution of the FPP and its design and development process. The envisioned system extends the existing MBSE methodology and technological framework which is currently in use. The MBSE technological framework currently in place enables the systematic collection and integration of data required for building an FPP model for a diverse set of missions. This framework includes the technology, people and processes required for rapid development of architectural artifacts. It is used to build a feasible FPP model for the first flight of spacecraft and for recurrent flights throughout the life of the program. This model greatly enhances our ability to effectively engage with a new customer. It provides a preliminary work breakdown structure, data flow information and a master schedule based on its existing knowledge base. These artifacts are then refined and iterated upon with the customer for the development of a robust end-to-end, high-level integrated master schedule and its associated dependencies. The vision is to enhance this framework to enable its application for uncertainty management, decision support and optimization of the design and execution of the FPP by the program. Furthermore, this enhanced framework will enable the agile response and redesign of the FPP based on observed system behavior. The differences between the anticipated system behavior and the observed behavior may be due to the processing of tasks internally, or due to external factors such as changes in program requirements or conditions associated with other organizations that are outside of MOD. The paper provides a roadmap for the four increments of this vision. These increments include (1) the existing capabilities (2) hardware and software system components and interfaces with the NASA ground system, (3) uncertainty management and (4) re-planning and automated execution. Each of these increments provides value independently; but some may also enable building of a subsequent increment.

Ruszkowski, James↗
NASA NTRSDate not supplied

Multidisciplinary Dynamic Testing Challenges in Validating the NASA Artemis Architecture

NASA is in the midst of bold and exciting next steps in human exploration and spaceflight. The designs of the new Space Launch System (SLS), the Orion spacecraft and the Exploration Ground Systems (EGS) for vehicle processing and launch are essentially complete and there has been significant progress in manufacturing and assembly of specific hardware for the Artemis I and Artemis II missions. Equally as important, the program level and integrated system level testing and analyses are also well underway to support integrated verification, validation, and certificate of flight readiness (CoFR) for the first Artemis mission. Testing and analysis are key to addressing technical challenges that the Artemis missions offer. Building block approaches are required that provide the right balance between component, system, and/or element level testing that satisfies verification and validation objectives and where, uncertainties are quantified and minimized. Artemis I is a system of systems that requires a fusion of test and analysis that adeptly characterizes critical interfaces between major program elements. NASA is implementing new in-situ testing that fuse traditional aerospace structures with civil structures, such as the Integrated Modal Test for the Artemis I vehicle where the Mobile Launcher and Crawler Transporter serve as a support structure whose dynamics couple with that of the Artemis I vehicle. This new paradigm requires a closer inspection of structural behavior of the Crawler Transporter and the Mobile Launcher as they now serve multiple purposes. This requires a paradigm shift to look beyond experimental modal techniques and incorporates operational modal analysis techniques to validate dynamic models from data collected during rollout to the launch pad. A further complicating factor is the Crawler Transporter generated ground forces have numerous harmonics making extracting dynamic responses of the Artemis I, Mobile Launcher, and Crawler Transporter coupled system challenging. This discussion explores all these challenges with and attempts to understand how we best build confidence in systems and system-of-systems performance capabilities and margins and understand uncertainties.

Joel W Sills↗
NASA NTRS2019

NASA SEXTANT Mission Operations Architecture

The Station Explorer for X-Ray Timing and Navigation (SEXTANT) mission is a technology demonstration enhancement to the Neutron Star Interior Composition Explorer (NICER) mission, a NASA Astrophysics Explorer Mission of Opportunity to the International Space Station (ISS) that was launched in June of 2017. The NICER instrument is a precision pointing X-ray telescope that times pulsar sourced photon arrivals which the SEXTANT mission uses to perform autonomous onboard X-ray Pulsar Navigation (XNAV). By comparing the detected time of arrival of X-ray photons to a reference of expected pulsar timing models, one can infer a range and range rate measurement based on light time delay. Since both timing and orientation information comes from a celestial source, this technology could provide a GPS-like navigation capability available throughout our Solar System and beyond. Applications that XNAV can support include outer planet and interstellar missions, manned missions, libration orbit missions, and current infrastructure such as the Deep Space Network (DSN). The SEXTANT team successfully completed a first demonstration of in-space and autonomous XNAV in November 2017. NICER and SEXTANT have separate teams, with NICER being the primary team with its own science objectives. Operational modes for both missions must have concurrent and independent components as well as an integrated ground system. This paper describes on the operational infrastructure and successful operations for performing X-ray Pulsar Navigation with the Station Explorer for X-ray Timing and Navigation Technology (SEXTANT) demonstration. This paper first details the infrastructure implemented, then the concept of operations, and finally the operations for the SEXTANT demonstration and lessons learned.

Ground Systems↗