Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “architecture design”

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 469 records · Page 26
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

Pyrotechnically Actuated Gas Generator Utilizing Aqueous Methanol

A gas-generating device was developed to supplement the ram-air inflation of a supersonic ballute. The device is designed to initially pressurize the ballute following deployment, exposing and orienting its ram-air inlets to free-stream air for complete inflation. The supplemental pressurization decreases the total inflation time, and increases the likelihood of a successful inflation. The device contains a reservoir filled with an aqueous mixture of methanol that, when released in to the interior of the ballute, rapidly vaporizes due to the low ambient pressure. Upon activation of the device, a pair of redundant ring mechanisms initiate pyrotechnic charges that pressurize and rupture the reservoir, resulting in ejection of the methanol in to the ballute. In addition to its role in inflation, the device serves as the structural connection to the ballute. Analytical models were developed for the inflation capability of the device, which were verified using vacuum chamber testing of developmental hardware. Static, deployment, and environmental testing demonstrated the functionality of the ring mechanism and reservoir under several temperature and pressure conditions. Finally, the device was successfully operated during the first Supersonic Flight Dynamics Test (SFDT) of NASA's Low Density Supersonic Decelerator (LDSD) project. The design architecture is scalable to accommodate different quantities of gas generation, can be adjusted to operate in a variety of temperature and atmospheric pressure regimes, and provides a robust device that may be installed with minimal risk to personnel or hardware.

IA↗
NASA NTRS2016

Predictive Modeling for NASA Entry, Descent and Landing Missions

Entry, Descent and Landing (EDL) Modeling and Simulation (MS) is an enabling capability for complex NASA entry missions such as MSL and Orion. MS is used in every mission phase to define mission concepts, select appropriate architectures, design EDL systems, quantify margin and risk, ensure correct system operation, and analyze data returned from the entry. In an environment where it is impossible to fully test EDL concepts on the ground prior to use, accurate MS capability is required to extrapolate ground test results to expected flight performance.

Modeling & Simulation↗
NASA NTRS2018

The Importance of User Feedback in Sustaining Trusted Repositories

The NASA Earth Observation System Data and Information System (EOSDIS) has been operating since 1994 and is serving a global user community with well-managed Earth science data in a variety of scientific disciplines. EOSDIS processes, archives and distributes data and information products resulting from spaceborne and airborne instruments as well as in situ measurements from field campaigns. The Earth Science Data and Information System (ESDIS) Project at the NASA Goddard Space Flight Center manages EOSDIS with its 12 Distributed Active Archive Centers (DAACs) located across the United States. During the entire life of EOSDIS, the ESDIS Project and the DAACs have deployed many different mechanisms for user feedback, which have proven extremely valuable to their evolution and performance in their service to user communities. Some of the inputs from our user groups have resulted in fundamental changes in the architecture, design and operations of EOSDIS, while others have provided novel ideas for incremental changes. The EOSDIS DAACs have User Working Groups (UWGs) that represent broad user communities in the Earth science disciplines served by the DAACs. The UWGs meet periodically to assess and provide feedback on dataset and service priorities. As regular users of the data and services of the DAAC and experts in the scientific disciplines, the UWG members provide valuable inputs for planning and prioritizing the services, as well as addition of new datasets, for the benefit of the community. The EOSDIS is evaluated annually through an independently administered survey of its users resulting in the American Customer Satisfaction Index (ACSI). The survey provides an ACSI score as well as free-text suggestions from users, which are also helpful in making specific system improvements. In addition, each of the DAACs has a user services group that address on-going requests for help and other comments from users. The ESDIS Project has established a mechanism through the "earthdata" website (http://earthdata.nasa.gov) for users to provide feedback of any kind and these questions/comments are routed to the appropriate individuals in the Project or the DAACs. These various forms of receiving user feedback and responding to them continue to be extremely valuable in evolving and sustaining our Earth Science repository.

Behnke, Jeanne↗
NASA NTRS2016

Conceive, Believe and Achieve; A Path to Miniaturization, COTS Infusion, and Size Weight and Power Realization for Flight

JPL along with other aerospace agencies such as the US Air Force Space Pro-grams and a packaging technology innovator, i3 Electronics, Inc., are evaluating the use of state-of-the-art (SOA) commercial off-the-shelf (COTS) and alternative packaging technologies for future high performance and high reliability space applications. Utilization of SOA COTS technologies have resulted in large scale reduction in electronics volume, weight, power, cost and schedule with outstanding electrical performance and high reliability. We will share JPL’s joint design, architectural approach, alternative substrate materials selection, associated processes, and mission assurance role in identifying reliability and qualification risks, as part of the three year Heterogeneous Packaging/Device Integration effort under the guidance and leadership of JPL’s Mission Assurance Directorate.

Hunter, Don J.↗
NASA NTRS2016

Design and Execution of Dawn HAMO to LAMO Transfer at Ceres

On October 23, 2015, the Dawn spacecraft left the High Altitude Mapping Orbit (HAMO) around Ceres and began its final decent to the Low Altitude Mapping Orbit (LAMO), arriving on December 15. The transfer between the two science orbits, a tight spiraling trajectory with over 100 revolutions, required the operations team to perform weekly maneuver designs for a period of 50 days. While the first six weeks of the transfer executed as planned, unexpectedly the spacecraft incurred a multi-sigma delivery error to the final science orbit that was subsequently clean-up at the first orbit maintenance maneuver. In this paper we discuss the design architecture for the transfer in detail, including challenges the team faced in flying the transfer and lessons learned.

Grebow, Daniel J.↗
NASA NTRS2016

Design and Execution of Dawn HAMO to LAMO Transfer at Ceres

On October 23, 2015, the Dawn spacecraft left the High Altitude Mapping Orbit (HAMO) around Ceres and began its final decent to the Low Altitude Mapping Orbit (LAMO), arriving on December 15. The transfer between the two science orbits, a tight spiraling trajectory with over 100 revolutions, required the operations team to perform weekly maneuver designs for a period of 50 days. While the first six weeks of the transfer executed as planned, unexpectedly the spacecraft incurred a multi-sigma delivery error to the final science orbit that was subsequently clean-up at the first orbit maintenance maneuver. In this paper we discuss the design architecture for the transfer in detail, including challenges the team faced in flying the transfer and lessons learned.

Grebow, Dan↗
NASA NTRS2020

Medical Data Architecture Platform and Recommended Requirements for a Medical Data System for Exploration Missions

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically- relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions. In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗
NASA NTRS2020

Medical Data Architecture Platform and Recommended Requirements for A Medical Data System for Exploration Missions

Minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions.In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗
NASA NTRS2019

Development of Human-Spacesuit Interaction Models

Today’s astronaut corps represents a wide range of various anthropometric dimensions. Accommodating this wide range of anthropometry and protecting for size variations in future crews, makes spacesuit sizing and fit a challenging and necessary aspect of suit development. Spacesuit fit can play an important role in performance, but a suit fit assessment, especially in dynamic postures, is difficult without extensive human-in-the-loop testing. One approach to address this issue is to model and simulate the human-spacesuit interactions for a target population early in the design process. The Anthropometry and Biomechanics Facility (ABF) at the NASA Johnson Space Center has been working to incorporate parametric human models based on 3D full-body scan data with spacesuit CAD models that can be driven by the user or imported motion capture data. An articulated spacesuit model combined with a poseable high-fidelity human model allows comparisons to be made between spacesuit capabilities and normal human ranges of motion. Furthermore, predictions can be made as to how a specific individual or population may perform in the suit from the perspective of reach and mobility. In this paper, we will present case study examples of reach, mobility, and fit analyses that can be done with these models and the methodology developed thus far. These models have the potential to become powerful tools for evaluating future spacesuit design architectures from the perspective of optimizing fit and performance.

Jarvis, Sarah↗
NASA NTRS2019

Challenges Using Linux as a Real-Time Operating System

Human-in-the-loop (HITL) simulation groups at NASA and the Air Force Research Lab have been using Linux as a real-time operating system (RTOS) for over a decade. More recently, SpaceX has revealed that it is using Linux as an RTOS for its Falcon launch vehicles and Dragon capsules. As Linux makes its way from ground facilities to flight critical systems, it is necessary to recognize that the real-time capabilities in Linux are cobbled onto a kernel architecture designed for general purpose computing. The Linux kernel contain numerous design decisions that favor throughput over determinism and latency. These decisions often require workarounds in the application or customization of the kernel to restore a high probability that Linux will achieve deadlines.

Madden, Michael M.↗
NASA NTRS2002

Interferometer real time control development for SIM

This paper provides an overview of the architecture, design, integration, and test of the SIM flight interferometer real time control to meet challenging flight system requirements for the high processor throughput, low-latency interconnect, and precise synchronization to support microarcsecond-level astrometric measurements for greater than five years at 1 AU in Earth-trailing orbit.

real↗
NASA NTRSDate not supplied

Architecture Options for Navigation in Cislunar Space for Human Landing System Vehicles

As part of architecture studies and insight analysis focused on requirements development into Human Landing System lunar architecture designs, multiple studies are underway to understand the sensitivities and options for achieving high precision landing on the lunar surface. The baseline approach utilizes a combination of multiple sensors to capture autonomous state observations of the lander with respect to the lunar surface. These systems are typically constrained in terms of operational altitudes by parameters such as onboard map size, camera focus, or sensor transmitted power (for altimeter observations). While these sensor suites do enable high precision landing, they are typically very complex and expensive. For a human-rated vehicle, fault detection algorithms are needed in addition to redundant sensors drive additional design complexity. Conversely, for these early missions, mass performance is key, so extended analysis is required to identify numbers of sensors, their ideal placement, and integration algorithms. A key part of this analysis is to help identify key sensor suites and options to help alleviate this design tension. An alternate approach is to take advantage and build out in-situ assets to allow for GPS-like navigation within the lunar regime through the use of navigation references or beacons. This can be achieved through the integration of navigation services into potential relays and pre-placed lunar surface assets. This research focuses on the capability of this infrastructure to support navigation in all areas of cislunar space such as: approach to the moon, in orbit around the moon, and ascent/descent operations to the surface. An augmented state linear covariance analysis (LinCov) and navigation state covariance analysis (NavCov) tools were used to assess a variety of navigation reference locations and how they can support vehicle operations through both understanding of state uncertainties and trajectory dispersions. This research helps to supplement existing studies focused on communication link analysis by providing additional insight into specific vehicle operational scenarios that are tied closely to potential Human Landing System scenarios. Key aspect of this analysis focus on the sensitivity to state knowledge of the references, the accuracy of inter-asset measurements, and placement in support of the various scenarios.

Evan J Anzalone↗
NASA NTRS2021

Hybrid Electric Aircraft Thermal Management: Now, New Visions and Future Concepts and Formulation

The global fuel consumption by commercial airlines has increased each year since 2009 and is predicted to reach an all-time high of 97 billion gallons in 2019. There is also an environmental impact from this: CO2 emissions from commercial passenger and freight operations totaled 918 Mt in 2018 (ICCT, 2019), or around 2.5% of global energy-related CO2 emissions. Passenger transport accounted for 81% of the total. Emissions from aviation have grown 32% over the past five years. Coupled with this aspect, there is a continuous and growing need to satisfy ever-growing electrical power needs on commercial and military aircraft. All the armed services (Army, Navy, and Air Force) are continuously trying to enhance UAV (unmanned aerial vehicle) endurance and range across a broad fleet of different aircraft. The commercial Boeing 787 requires about 1.2MWe and that is expected to grow. Current technologies used to supply increased on-board electrical power are generally: 1) “burn more fuel and convert through on-board generators” and 2) use additional heavy (i.e., weight-inefficient) and sometimes unsafe battery systems on-board the aircraft. The aircraft industry is seeking new, innovative ways to satisfy this increasing power demand. One as-yet-untapped power source is the enormous amount of “waste” thermal energy flowing out the jet engine exhaust; some estimates in smaller “by-pass” flow jet engines is several hundreds of kilowatts (e.g., Pratt & Whitney Canada PW545B turbofan). This quantity is much higher in large jet engines associated with commercial aircraft. This large waste thermal energy manifests itself in large temperature differences within the by-pass-flow engine exhaust system relative to outside ambient conditions, because of the actual by-pass engine design configuration. There is strong need to develop thermal technologies and systems that could harness and convert at least a portion of this thermal energy into useful electrical energy to satisfy growing on-board electrical needs. In addition, there is a strong desire within the aircraft and engine manufacturing community to reduce the “carbon footprint” of the industry though reduced fuel usage worldwide. NASA has a robust aircraft electrification program to meet these desires and support industry in its aircraft electrification objectives. This program is integrating thermoacoustic systems, advanced lightweight heat exchanger technology, and advanced heat pipe technology to capture and transport large amounts of engine waste thermal energy for on-board power conversion, advanced heat-pump cooling, and exergy enhancement (i.e., temperature lift). Advanced lightweight heat exchangers are envisioned to capture engine exhaust thermal energy at approximately 673 K and deliver it to efficient thermoacoustic power conversion systems operating at temperature ratios (Thot/Tcold) > 1.6. Advanced heat pipe systems are envisioned to transport thermal energy from low temperature sources, through thermoacoustic heat pumps, to high temperature needs such as wing anti-icing, fuel pre-heating, and combustion air pre-heating. The paper will discuss the current state-of-the-art, objectives, system design architecture, and remaining technical challenges in system formulation within the NASA aircraft electrification program.

Dyson, Rodger↗
NASA NTRSDate not supplied

Integrating Upper Class E Traffic Management (ETM) Operations into the National Airspace System: Use Cases and Research Questions

As new categories of vehicles are introduced in the National Airspace System, so too are novel concepts for a cooperative approach to traffic management environments. One of these new environments, Upper Class E Traffic Management (ETM), is expected to include a variety of high altitude, long endurance vehicles with a range of performance capabilities and mission profiles that operate in cooperative areas above 60,000 feet. In addition to developing the rules, architecture, and systems for operations within the ETM environment itself, it is also important to consider how ETM vehicles will integrate with traditional Air Traffic Management and interact with Air Traffic Control (ATC) as they traverse ATC-controlled airspace and transition in and out of cooperative ETM operating areas. As a first step toward future ETM demonstrations at the National Aeronautics and Space Administration (NASA) Ames Research Center’s Airspace Operations Laboratory, use cases with step-by-step procedures were developed to identify both nominal and off-nominal scenarios in which ETM operations will interact with ATC. As NASA prepares to develop a simulation platform to demonstrate ETM cooperative practices and ETM-ATC interactions, the procedures, ATC roles and responsibilities, data exchange requirements, and research questions that were identified as part of use case development will inform scenario and system architecture design. The upcoming simulation work will include initial prototype ETM-ATC coordination tools to support ATC controllers’ interactions with ETM operations. This paper will briefly discuss NASA’s upcoming ETM development work and then provide background on ETM-ATC interactions, describe each ETM-ATC interaction use case, and discuss open questions on concept, procedures, and assumptions.

ATC↗
NASA NTRSDate not supplied

CoCoSim Tutorial: Contract-based Compositional Verification of Simulink Models

This tutorial presents CoCoSim, a verification framework for MATLAB Simulink and Stateflow models. We demonstrate CoCoSim’s architecture, designed to be compatible with Lustre-based verification tools, as well as easily extensible to other candidate backends. We focus on CoCoSim’s powerful compositional verification scheme, which allows for scalable verification through the usage of abstractions of subsystems, express ed in the form of Assume-Guarantee Contracts. We show CoCoSim’s interconnection with NASA’s Formal Requirements Tool (FRET), that enables a seamless transition between authoring and formally verifying requirements for Simulink/Stateflow models. Finally, we discuss work in progress with regards to test case generation options in CoCoSim, demonstrating the generation of MC/DC tests for Simulink artifacts.

Formal Verification↗
NASA NTRSDate not supplied

Integrating Upper Class E Traffic Management (ETM) Operations into the National Airspace System: Use Cases and Research Questions

As new categories of vehicles are introduced in the National Airspace System, so too are novel concepts for a cooperative approach to traffic management environments. One of these new environments, Upper Class E Traffic Management (ETM), is expected to include a variety of high altitude, long endurance vehicles with a range of performance capabilities and mission profiles that operate in cooperative areas above 60,000 feet. In addition to developing the rules, architecture, and systems for operations within the ETM environment itself, it is also important to consider how ETM vehicles will integrate with traditional Air Traffic Management and interact with Air Traffic Control (ATC) as they traverse ATC-controlled airspace and transition in and out of cooperative ETM operating areas. As a first step toward future ETM demonstrations at the National Aeronautics and Space Administration (NASA) Ames Research Center’s Airspace Operations Laboratory, use cases with step-by-step procedures were developed to identify both nominal and off-nominal scenarios in which ETM operations will interact with ATC. As NASA prepares to develop a simulation platform to demonstrate ETM cooperative practices and ETM-ATC interactions, the procedures, ATC roles and responsibilities, data exchange requirements, and research questions that were identified as part of use case development will inform scenario and system architecture design. The upcoming simulation work will include initial prototype ETM-ATC coordination tools to support ATC controllers’ interactions with ETM operations. This paper will briefly discuss NASA’s upcoming ETM development work and then provide background on ETM-ATC interactions, describe each ETM-ATC interaction use case, and discuss open questions on concept, procedures, and assumptions.

ATC↗
NASA NTRSDate not supplied

Overview of the SLS Core Stage Thrust Vector Control System Design

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) consists of four independent hydraulic systems. The SLS CS TVC system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Each hydraulic system nominally provides hydraulic power to one RS-25 engine and two actuators. Additionally, each system provides redundant control capability to one actuator on each of its neighboring systems. The RS-25 uses hydraulic power to control propellant valves, and the TVC actuators are used to move the engine in the pitch and yaw gimbal planes. The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Solid Rocket Booster APU turbines are powered by hot gas produced by a catalyzed hydrazine decomposition. The SLS Core Auxiliary Power Unit (CAPU) is derived from the Space Shuttle Orbiter Auxiliary Power Unit (APU); on the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. The remaining hardware in the TVC system (hydraulic Filter Manifold (FM), hydraulic Supply Accumulator (SA), hydraulic Return Accumulator (RA), Hydraulic Reservoir, Exhaust Gas Heat Exchanger (EGHE)) as well as the avionics providing control and telemetry (TVC Actuator Controller (TAC) and CAPU Controller (CAPUC) are new components developed for SLS. This paper is the first installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. In this paper, the overall design architecture of the CS TVC is presented, with a focus on the interfaces between the TVC actuators, the engines, their hydraulic power systems, and the avionics that provide commands from the SLS Vehicle Management (VM) software to effect stable and robust flight control for the integrated SLS launch vehicle.

Thrust Vector Control↗
NASA NTRSDate not supplied

Overview of the SLS Core Stage Thrust Vector Control System Design

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) consists of four independent hydraulic systems. The SLS CS TVC system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Each hydraulic system nominally provides hydraulic power to one RS-25 engine and two actuators. Additionally, each system provides redundant control capability to one actuator on each of its neighboring systems. The RS-25 uses hydraulic power to control propellant valves, and the TVC actuators are used to move the engine in the pitch and yaw gimbal planes. The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Solid Rocket Booster APU turbines are powered by hot gas produced by a catalyzed hydrazine decomposition. The SLS Core Auxiliary Power Unit (CAPU) is derived from the Space Shuttle Orbiter Auxiliary Power Unit (APU); on the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. The remaining hardware in the TVC system (hydraulic Filter Manifold (FM), hydraulic Supply Accumulator (SA), hydraulic Return Accumulator (RA), Hydraulic Reservoir, Exhaust Gas Heat Exchanger (EGHE)) as well as the avionics providing control and telemetry (TVC Actuator Controller (TAC) and CAPU Controller (CAPUC) are new components developed for SLS. This paper is the first installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. In this paper, the overall design architecture of the CS TVC is presented, with a focus on the interfaces between the TVC actuators, the engines, their hydraulic power systems, and the avionics that provide commands from the SLS Vehicle Management (VM) software to effect stable and robust flight control for the integrated SLS launch vehicle.

Thrust Vector Control↗