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.

SourceResearch connectionFrom yearThrough year

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

At least 721 records · Page 40

All sources NASA NTRS DOE OSTI

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

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↗

NASA NTRS2008

Aquarius's Instrument Science Data System (ISDS) Automated to Acquire, Process, Trend Data and Produce Radiometric System Assessment Reports

The Aquarius Radiometer, a subsystem of the Aquarius Instrument required a data acquisition ground system to support calibration and radiometer performance assessment. To support calibration and compose performance assessments, we developed an automated system which uploaded raw data to a ftp server and saved raw and processed data to a database. This paper details the overall functionalities of the Aquarius Instrument Science Data System (ISDS) and the individual electrical ground support equipment (EGSE) which produced data files that were infused into the ISDS. Real time EGSEs include an ICDS Simulator, Calibration GSE, Labview controlled power supply, and a chamber data acquisition system. ICDS Simulator serves as a test conductor primary workstation, collecting radiometer housekeeping (HK) and science data and passing commands and HK telemetry collection request to the radiometer. Calibration GSE (Radiometer Active Test Source) provides source choice from multiple targets for the radiometer external calibration. Power Supply GSE, controlled by labview, provides real time voltage and current monitoring of the radiometer. And finally the chamber data acquisition system produces data reflecting chamber vacuum pressure, thermistor temperatures, AVG and watts. Each GSE system produce text based data files every two to six minutes and automatically copies the data files to the Central Archiver PC. The Archiver PC stores the data files, schedules automated uploads of these files to an external FTP server, and accepts request to copy all data files to the ISDS for offline data processing and analysis. Aquarius Radiometer ISDS contains PHP and MATLab programs to parse, process and save all data to a MySQL database. Analysis tools (MATLab programs) in the ISDS system are capable of displaying radiometer science, telemetry and auxiliary data in near real time as well as performing data analysis and producing automated performance assessment reports of the Aquarius Radiometer.

Source record↗

NASA NTRS1975

Viking mission operations

The Viking Flight Team and ground system must operate in an integrated manner with the two orbiters and two landers to acquire the scientific data that will significantly increase our knowledge of Mars. Viking mission requires an adaptive mode of flight operations which permits reflection of the knowledge gained as the mission progresses into subsequent data acquisition operations. This includes reflection of both the knowledge gained about Mars and knowledge as to how well each of the four vehicles and the ground data system are performing. The requirement for adaptive mission operations has imposed special considerations in the Viking mission design, landing site selection, organization of the Flight Team and in the design and development of the operational tools required by this team. A mission operations strategy has been developed which governs the multivehicle adaptive mission operations.

Young, A. T.↗

NASA NTRS2012

Automation and Process Improvement Enables a Small Team to Operate a Low Thrust Mission in Orbit Around the Asteroid Vesta

NASA's Dawn mission to the asteroid Vesta and dwarf planet Ceres launched September 27, 2007 and arrived at Vesta in July of 2011. This mission uses ion propulsion to achieve the necessary delta-V to reach and maneuver at Vesta and Ceres. This paper will show how the evolution of ground system automation and process improvement allowed a relatively small engineering team to transition from cruise operations to asteroid operations while maintaining robust processes. The cruise to Vesta phase lasted almost 4 years and consisted of activities that were built with software tools, but each tool was open loop and required engineers to review the output to ensure consistency. Additionally, this same time period was characterized by the evolution from manually retrieved and reviewed data products to automatically generated data products and data value checking. Furthermore, the team originally took about three to four weeks to design and build about four weeks of spacecraft activities, with spacecraft contacts only once a week. Operations around the asteroid Vesta increased the tempo dramatically by transitioning from one contact a week to three or four contacts a week, to fourteen contacts a week (every 12 hours). This was accompanied by a similar increase in activity complexity as well as very fast turn around activity design and build cycles. The design process became more automated and the tools became closed loop, allowing the team to build more activities without sacrificing rigor. Additionally, these activities were dependent on the results of flight system performance, so more automation was added to analyze the flight data and provide results in a timely fashion to feed the design cycle. All of this automation and process improvement enabled up the engineers to focus on other aspects of spacecraft operations, including spacecraft health monitoring and anomaly resolution.

ground system automation↗

NASA NTRS1988

Considerations in development of expert systems for real-time space applications

Over the years demand on space systems have been increased tremendously and this trend will continue for the near future. The enhanced capabilities of space systems, however, can only be met with increased complexity and sophistication of onboard and ground systems, and artificial intelligence and expert system concepts have a significant role in space applications. Expert systems could facilitate decision making, improved fault diagnosis and repair, enhanced performance and less reliance on ground support. However, some requirements have to be fulfilled before practical use of flight-worthy expert systems for onboard (and ground) operations. This paper discusses some of the characteristics and important considerations in design, development, implementation and use of expert systems for real-life space applications. Further, it describes a typical life cycle of expert system development and its usage.

Murugesan, S.↗

NASA NTRS1996

High Speed Simulator - A Simulator for All Seasons

This paper will discuss the evolution of the Multimission Ground Systems Office's (MGSO) High Speed Spacecraft Simulator (HSS) development at the Jet Propulsion Laboratory. This paper will examine the evolution from both a development and operations perspective. The HSS in reality is a series of simulators capable of modeling the spacecraft and its subsystems at either the bit or functional level, depending on specific mission needs.

command↗

NASA NTRS1967

Ground test facilities for aircraft airbreathing propulsion system development.

Ground test facilities for aircraft air breathing propulsion system development

TEST FACILITY↗

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 NTRSDate not supplied

Fusion of Test and Analysis: Artemis I Booster to Mobile Launcher Interface Validation

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 Artemis I. Testing and analysis are key to addressing technical challenges faced by the Artemis missions. Building block approaches are required that provide the right balance between component, element, and/or system level testing that satisfies verification and validation objectives 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. An example of this fusion involves characterizing the interface between the SLS booster and the Mobile Launcher (ML) Vertical Support Post (VSP) interfaces. Proper characterization of this interface represents a number of challenges beginning with the fact that it is a mating of ground support structure in the form of a civil structure to flight hardware. Both sides of the interface are built to different construction standards, but are governed by interface requirements to ensure compatibility when mated. From past program experience, the flexibility at the booster to ML interface is critical in developing accurate prelaunch stacking and cryogenic preloads, squat loads, and pad separation release of preloads and squat loads. This same premise holds for Artemis I. To characterize the asymmetric characteristics at this interface, careful consideration of static forces due to gravity loading with the commensurate effects due to leveling during booster stacking (i.e., spacing and shimming) and nonlinear geometric forces are necessary for inclusion in pre-test assessments. This paper will look at these issues for the upcoming Booster Pull Test in which two boosters will be installed on the ML and one of these boosters will undergo static lateral loading followed afterwards with dynamic excitation into resonance and free-decay. This paper evaluates the booster to ML interface characteristics by characterizing the interface flexibility between the booster aft skirt and the ML VSP interfaces. Furthermore, this paper methodically evaluates the effect of the following on the test outcome: gravitational effects on the booster and ML, the effects of VSP leveling, spacing, and shimming under gravitational loading during booster stacking, the effect of geometric nonlinear follower force due to cg offset as booster is laterally displaced, and the system coupling between the booster under test, ML, and the second booster. Simulated results for a static load pull and dynamic excitation provide insight into the differences in measurement responses when boundary conditions and geometric conditions are included and not included.

Joel W Sills Jr.↗

NASA NTRS2013

Citric Acid Alternative to Nitric Acid Passivation

The Ground Systems Development and Operations GSDO) Program at NASA John F. Kennedy Space Center (KSC) has the primary objective of modernizing and transforming the launch and range complex at KSC to benefit current and future NASA programs along with other emerging users. Described as the launch support and infrastructure modernization program in the NASA Authorization Act of 2010, the GSDO Program will develop and implement shared infrastructure and process improvements to provide more flexible, affordable, and responsive capabilities to a multi-user community. In support of the GSDO Program, the purpose of this project is to demonstratevalidate citric acid as a passivation agent for stainless steel. Successful completion of this project will result in citric acid being qualified for use as an environmentally preferable alternative to nitric acid for passivation of stainless steel alloys in NASA and DoD applications.

Technology↗

NASA NTRS2007

Mars Reconnaissance Orbiter Mission: Systems Engineering Challenges on the Mars Reconnaissance Orbiter Mission

MRO project is a system of systems requiring system engineering team to architect, design, integrate, test, and operate these systems at each level of the project. The challenge of system engineering mission objectives into a single mission architecture that can be integrated tested, launched, and operated. Systems engineering must translate high-level requirements into integrated mission design. Systems engineering challenges were overcome utilizing a combination by creative designs built into MRO's flight and ground systems: a) Design of sophisticated spacecraft targeting and data management capabilities b) Establishment of a strong operations team organization; c) Implementation of robust operational processes; and d) Development of strategic ground tools. The MRO system has met the challenge of its driving requirements: a) MRO began its two-year primary science phase on November 7, 2006, and by July 2007, met it minimum requirement to collect 15 Tbits of data after only eight months of operations. Currently we have collected 22 Tbits. b) Based on current performance, mission data return could return 70 Tbits of data by the end of the primary science phase in 2008.

systems engineering↗

NASA NTRS1972

Advanced ground support checkout systems.

The experience gained with the acceptance checkout equipment for spacecraft, which was used for checkout on the Apollo and Skylab Programs, is discussed in this paper and related to advanced ground systems for the Space Shuttle Program. The basic capabilities of the checkout system are outlined, goals for future checkout systems are discussed, and the unified test equipment system is described.

Osgood, D. R.↗