Voyager capsule phase B. Volume III - Surface laboratory system. Part D - Operational support equipment Final report
Voyager capsule surface laboratory system - operational support equipment
SEARCH · Search NASA
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.
Voyager capsule surface laboratory system - operational support equipment
Space shuttle operations, maintenance, and integration of ground support system, logistics, checkout, and recovery
As the first interplanetary mission managed by the NASA Goddard Space Flight Center, the Mars Atmosphere and Volatile EvolutioN (MAVEN) had three IT security goals for its ground system: COMPLIANCE, (IT) RISK REDUCTION, and COST REDUCTION. In a multiorganizational environment in which government, industry and academia work together in support of the ground system and mission operations, information security governance, risk management, and compliance (GRC) becomes a challenge as each component of the ground system has and follows its own set of IT security requirements. These requirements are not necessarily the same or even similar to each other's, making the auditing of the ground system security a challenging feat. A combination of standards-based information security management based on the National Institute of Standards and Technology (NIST) Risk Management Framework (RMF), due diligence by the Mission's leadership, and effective collaboration among all elements of the ground system enabled MAVEN to successfully meet NASA's requirements for IT security, and therefore meet Federal Information Security Management Act (FISMA) mandate on the Agency. Throughout the implementation of GRC on MAVEN during the early stages of the mission development, the Project faced many challenges some of which have been identified in this paper. The purpose of this paper is to document these challenges, and provide a brief analysis of the lessons MAVEN learned. The historical information documented herein, derived from an internal pre-launch lessons learned analysis, can be used by current and future missions and organizations implementing and auditing GRC.
Final Paper, not the Abstract, is attached: This report discusses how history can be used by management, engineering, and operations personnel within space flight programs. Works by professional historians and sociologists inform key decision makers and policy specialists on lessons learned from space flight program management successes and failures, as well as from legislative affairs, policy making, and commercial space efforts. Vehicle engineering history written by engineers for an engineering or operations audience informs project management and technical personnel on lessons learned, best practices, and the rationale behind the design and operation of flight vehicles and supporting ground systems. Archives play a critical role in supporting the efforts of both professional historians and flight program personnel. Suggestions are made concerning how professional historians could leverage the interests and knowledge of flight program personnel to obtain more insight that is needed to support historical research efforts.
AirSTAR is the collection of Ground Support Systems, Subscale Flight Vehicles and Operations Expertise required for conducting remotely piloted flight-dynamics and controls research.
The physical configuration, task versatility, and typical mission profile of the Space Shuttle are illustrated and described, and a comparison of shuttle and expendable rocket costs is discussed, with special emphasis upon savings to be achieved in ground operations. A review of economies achieved by engineering design improvements covers the automated checkout by onboard shuttle systems, the automated launch processing system, the new maintenance concept, and the analogy of Space Shuttle and airline repetitive operations. The Space Shuttle is shown to represent a new level in space flight technology, particularly, the sophistication of the systems and procedures devised for its support and ground operations.
The Mission Design and Navigation (MDNAV) Section at the Jet Propulsion Laboratory (JPL) supports many deep space and earth orbiting missions from formulation to end of mission operations. The requirements of these missions are met with a multimission approach to MDNAV ground data system (GDS) infrastructure capable of being shared and allocated in a seamless and consistent manner across missions. The MDNAV computing infrastructure consists of compute clusters, network attached storage, mission support area facilities, and desktop hardware. The multimission architecture allows these assets, and even personnel, to be leveraged effectively across the project lifecycle and across multiple missions simultaneously. It provides a more robust and capable infrastructure to each mission than might be possible if each constructed its own. It also enables a consistent interface and environment within which teams can conduct all mission analysis and navigation functions including: trajectory design; ephemeris generation; orbit determination; maneuver design; and entry, descent, and landing analysis. The savings of these efficiencies more than offset the costs of increased complexity and other challenges that had to be addressed: configuration management, scheduling conflicts, and competition for resources. This paper examines the benefits of the multimission MDNAV ground data system infrastructure, focusing on the hardware and software architecture. The result is an efficient, robust, scalable MDNAV ground data system capable of supporting more than a dozen active missions at once.
The MultiMission Control Team (MMCT) consists of mission controllers which provides Real-Time operations support for the Mars Observer project. The Real-Time Operations task is to insure the integrity of the ground data system, to insure that the configuration is correct to support the mission, and to monitor the spacecraft for the Spacecraft Team. Operations systems are typically developed by adapting operations systems from previous projects. Problems tend to be solved empirically when they are either anticipated or observed in testing. This development method has worked in the past when time was available for extensive Ops testing. In the present NASA budget environment, a more cost conscious design approach has become necessary. Cost is a concern because operations is an ongoing, continuous activity. Reducing costs entails reducing staff. Reducing staffing levels potentially increases the risk of mission failure. Therefore, keeping track of the risk level is necessary.
Project management and payload integration requirements definition activities are reported. Mission peculiar equipment; systems integration; ground operations analysis and requirement definition; safety and quality assurance; and support systems development are examined for payloads planned for the following missions: EOM-1; SL-2; Sl-3 Astro-1; MSL-2; EASE/ACCESS; MPESS; and the middeck ADSF flight.
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.
Significant and substantial progress continues to be accomplished in the design, development, and testing of the Space Launch System (SLS), the most powerful human-rated launch vehicle the United States has ever undertaken. Designed to support human missions into deep space, SLS is one of three programs being managed by the National Aeronautics and Space Administration's (NASA's) Exploration Systems Development directorate. The Orion spacecraft program is developing a new crew vehicle that will support human missions beyond low Earth orbit, and the Ground Systems Development and Operations program is transforming Kennedy Space Center into next-generation spaceport capable of supporting not only SLS but also multiple commercial users. Together, these systems will support human exploration missions into the proving ground of cislunar space and ultimately to Mars. SLS will deliver a near-term heavy-lift capability for the nation with its 70 metric ton (t) Block 1 configuration, and will then evolve to an ultimate capability of 130 t. The SLS program marked a major milestone with the successful completion of the Critical Design Review in which detailed designs were reviewed and subsequently approved for proceeding with full-scale production. This marks the first time an exploration class vehicle has passed that major milestone since the Saturn V vehicle launched astronauts in the 1960s during the Apollo program. Each element of the vehicle now has flight hardware in production in support of the initial flight of the SLS -- Exploration Mission-1 (EM-1), an un-crewed mission to orbit the moon and return. Encompassing hardware qualification, structural testing to validate hardware compliance and analytical modeling, progress in on track to meet the initial targeted launch date in 2018. In Utah and Mississippi, booster and engine testing are verifying upgrades made to proven shuttle hardware. At Michoud Assembly Facility in Louisiana, the world's largest spacecraft welding tool is producing tanks for the SLS core stage. This paper will particularly focus on work taking place at Marshall Space Flight Center (MSFC) and United Launch Alliance in Alabama, where upper stage and adapter elements of the vehicle are being constructed and tested. Providing the Orion crew capsule/launch vehicle interface and in-space propulsion via a cryogenic upper stage, the Spacecraft/Payload Integration and Evolution (SPIE) Element serves a key role in achieving SLS goals and objectives. The SPIE element marked a major milestone in 2014 with the first flight of original SLS hardware, the Orion Stage Adapter (OSA) which was used on Exploration Flight Test-1 with a design that will be used again on EM-1. Construction is already underway on the EM-1 Interim Cryogenic Propulsion Stage (ICPS), an in-space stage derived from the Delta Cryogenic Second Stage. Manufacture of the Orion Stage Adapter and the Launch Vehicle Stage Adapter is set to begin at the Friction Stir Facility located at MSFC while structural test articles are either completed (OSA) or nearing completion (Launch Vehicle Stage Adapter). An overview is provided of the launch vehicle capabilities, with a specific focus on SPIE Element qualification/testing progress, as well as efforts to provide access to deep space regions currently not available to the science community through a secondary payload capability utilizing CubeSat-class satellites.
In order to enable arrival management concepts and solutions in a NextGen environment, ground- based sequencing and scheduling functions have been developed to support metering operations in the National Airspace System. These sequencing and scheduling algorithms as well as tools are designed to aid air traffic controllers in developing an overall arrival strategy. The ground systems being developed will support the management of aircraft to their Scheduled Times of Arrival (STAs) at flow-constrained meter points. This paper presents a methodology for determining the undelayed delivery accuracy for current day air traffic control operations. This new method analyzes the undelayed delivery accuracy at meter points in order to understand changes of desired flow rates as well as enabling definition of metrics that will allow near-future ground automation tools to successfully achieve desired separation at the meter points. This enables aircraft to meet their STAs while performing high precision arrivals. The research presents a possible implementation that would allow delivery performance of current tools to be estimated and delivery accuracy requirements for future tools to be defined, which allows analysis of Estimated Time of Arrival (ETA) accuracy for Time-Based Flow Management (TBFM) and the FAA's Traffic Management Advisor (TMA). TMA is a deployed system that generates scheduled time-of-arrival constraints for en- route air traffic controllers in the US. This new method of automated analysis provides a repeatable evaluation of the delay metrics for current day traffic, new releases of TMA, implementation of different tools, and across different airspace environments. This method utilizes a wide set of data from the Operational TMA-TBFM Repository (OTTR) system, which processes raw data collected by the FAA from operational TMA systems at all ARTCCs in the nation. The OTTR system generates daily reports concerning ATC status, intent and actions. Due to its availability, ease of use, and vast collection of data across several airspaces it was determined that the OTTR data set would be the best method to utilize moving forward with this analysis. The particular variables needed for further analysis were determined along with the necessary OTTR reports, by working closely with the repository team additional analysis reports were developed that provided key ETA and STA information at the freeze horizon. One major benefit of the OTTR data is that using the correct reports the data across several airports could be analyzed over large periods of time. The OTTR data processes the TBFM data daily and is stored in various formats across several airspaces. This allowed us to develop our own parsing methods and raw data processing that would not rely on other computationally expensive tools that perform more in depth analysis of similar sets of data. The majority of this work consisted of the development of the ability to filter flights to create a subset of flights that could be considered undelayed, which is defined as a flight at the freeze horizon with an ETA and STA difference that was minimal or close to zero. This was a broad method that allowed the consideration of a large data set which consisted of all the traffic across a two month period in 2013, the hottest and coldest months, arriving into four airports: George Bush Intercontinental, Denver International, Los Angeles International, and Phoenix Sky Harbor.
Test Objectives Summary: a) Verify operation of the core simulator, the instrumentation & control system, and the ground support gas and vacuum test equipment. b) Examine cooling & heat regeneration performance of the cold trap purification. c) Test the ALIP pump at voltages beyond 120V to see if the targeted mass flow rate of 1.75 kg/s can be obtained in the RxSim. Testing Highlights: a) Gas and vacuum ground support test equipment performed effectively for operations (NaK fill, loop pressurization, and NaK drain). b) Instrumentation & Control system effectively controlled loop temperature and flow rates or pump voltage to targeted settings and ramped within prescribed constraints. It effectively interacted with reactor simulator control model and defaulted back to temperature control mode if the transient fluctuations didn't dampen. c) Cold trap design was able to obtain the targeted cold temperature of 480 K. An outlet temperature of 636 K was obtained which was lower than the predicted 750 K but 156 K higher than the minimum temperature indicating the design provided some heat regeneration. d) ALIP produce a maximum flow rate of 1.53 kg/s at 800 K when operated at 150 V and 53 Hz.
Modern space propulsion and exploration system designs are becoming increasingly sophisticated and complex. Determining the health state of these systems using traditional methods is becoming more difficult as the number of sensors and component interactions grows. Data-driven monitoring techniques have been developed to address these issues by analyzing system operations data to automatically characterize normal system behavior. The Inductive Monitoring System (IMS) is a data-driven system health monitoring software tool that has been successfully applied to several aerospace applications. IMS uses a data mining technique called clustering to analyze archived system data and characterize normal interactions between parameters. This characterization, or model, of nominal operation is stored in a knowledge base that can be used for real-time system monitoring or for analysis of archived events. Ongoing and developing IMS space operations applications include International Space Station flight control, satellite vehicle system health management, launch vehicle ground operations, and fleet supportability. As a common thread of discussion this paper will employ the evolution of the IMS data-driven technique as related to several Integrated Systems Health Management (ISHM) elements. Thematically, the projects listed will be used as case studies. The maturation of IMS via projects where it has been deployed, or is currently being integrated to aid in fault detection will be described. The paper will also explain how IMS can be used to complement a suite of other ISHM tools, providing initial fault detection support for diagnosis and recovery.
Modern space propulsion and exploration system designs are becoming increasingly sophisticated and complex. Determining the health state of these systems using traditional methods is becoming more difficult as the number of sensors and component interactions grows. Data-driven monitoring techniques have been developed to address these issues by analyzing system operations data to automatically characterize normal system behavior. The Inductive Monitoring System (IMS) is a data-driven system health monitoring software tool that has been successfully applied to several aerospace applications. IMS uses a data mining technique called clustering to analyze archived system data and characterize normal interactions between parameters. This characterization, or model, of nominal operation is stored in a knowledge base that can be used for real-time system monitoring or for analysis of archived events. Ongoing and developing IMS space operations applications include International Space Station flight control, spacecraft vehicle system health management, launch vehicle ground operations, and fleet supportability. As a common thread of discussion this paper will employ the evolution of the IMS data-driven technique as related to several Integrated Systems Health Management (ISHM) elements. Thematically, the projects listed will be used as case studies. The maturation of IMS via projects where it has been deployed or is currently being integrated to aid in fault detection will be described. The paper will also explain how IMS can be used to complement a suite of other ISHM tools, providing initial fault detection support for diagnosis and recovery
Hydraulic ground support for saturn v, supplying fluid power to actuate engine gimbal system and operate engine valves
In this work we describe in detail the architecture, design, testing and operation of the Electrical Ground Support Equipment (EGSE) “Blue Box” used to test and validate the Sampling Caching System (SCS) of the Mars 2020 Perseverance rover. The Blue Box architecture is centered around COTS motor controllers and COTS input-output modules communicating over an EtherCAT bus. A custom, low-level safety subsystem ensures no harm can be done to the flight articles. The modular architecture of the EGSE reduces cost and complexity while expediting assembly time. The Blue Box drives the 19 actuators of the SCS which span the main robotic arm, the corer system, the internal sample handling arm, the sample tube sealing system and the gas dust removal tool; mimicking the Rover Motor Control Assembly (RMCA). Due to the limited availability of RMCA’s, the EGSE enabled and performed the bulk of testing activities for SCS. The majority of the SCS actuators are composed of a 3-phase DC brushless motors, hall sensors for commutation, dual resolvers for output angular measurement, brakes, heaters and platinum thermistors. Additionally, the EGSE read 12 strain gauges forming part of a force torque sensor, and switches used for external positioning references. Over the 3-year span of the V&V campaign for the SCS, over 32 EGSE systems were built, tested and deployed to test venues at JPL and externally. The EGSE tested several families of the SCS subsystem, ranging from engineering units, life test units and two flight units. Test venues that this EGSE supported included lab benches, ultra-clean cleanrooms, ATLO facilities, and thermal vacuum chambers. Together with the test software systems, SSDEV and SSDEV-ECAT, the Blue Box EGSE enabled the team to efficiently test flight hardware and flight software together. We go over the safety features and fault management techniques employed to protect flight hardware. The effects of the long, 50-feet, EGSE harnesses on motor performance, EMI, electrical noise, and motor control performance are explained. Mitigations to these unwanted effects, including shielding strategy and inductance compensation, are summarized. We go over an excerpt of notable anomalies that this EGSE suffered through its operation, along with investigations and resolutions. Lessons learned, areas of improvement as part of future work, and recommendations for future implementations for similar EGSE’s, are shared.
This study was the first in a series of planned tests to use physics-based subsystem simulations to investigate the interactions between a spacecraft's crew and a ground-based mission control center for vehicle subsystem operations across long communication delays. The simulation models the life support system of a deep space habitat. It contains models of an environmental control and life support system, an electrical power system, an active thermal control systems, and crew metabolic functions. The simulation has three interfaces: 1) a real-time crew interface that can be use to monitor and control the subsystems; 2) a mission control center interface with data transport delays up to 15 minute each way; and 3) a real-time simulation test conductor interface used to insert subsystem malfunctions and observe the interactions between the crew, ground, and simulated vehicle. The study was conducted at the 21st NASA Extreme Environment Mission Operations (NEEMO) mission. The NEEMO crew and ground support team performed a number of relevant deep space mission scenarios that included both nominal activities and activities with system malfunctions. While this initial test sequence was focused on test infrastructure and procedures development, the data collected in the study already indicate that long communication delays have notable impacts on the operation of deep space systems. For future human missions beyond cis-lunar, NASA will need to design systems and support tools to meet these challenges. These will be used to train the crew to handle critical malfunctions on their own, to predict malfunctions and assist with vehicle operations. Subsequent more detailed and involved studies will be conducted to continue advancing NASA's understanding of space systems operations across long communications delays.