Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Spacecraft Crew Interfaces”

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 73 records · Page 4

Reaction control system/remote manipulator system automation

The objectives of this project is to evaluate the capability of the Procedural Reasoning System (PRS) in a typical real-time space shuttle application and to assess its potential for use in the Space Station Freedom. PRS, developed by SRI International, is a result of research in automating the monitoring and control of spacecraft systems. The particular application selected for the present work is the automation of malfunction handling procedures for the Shuttle Remote Manipulator System (SRMS). The SRMS malfunction procedures will be encoded within the PRS framework, a crew interface appropriate to the RMS application will be developed, and the real-time data interface software developed. The resulting PRS will then be integrated with the high-fidelity On-orbit Simulation of the NASA Johnson Space Center's System Engineering Simulator, and tests under various SRMS fault scenarios will be conducted.

Hiers, Harry K.↗

Crew interface specification development study for in-flight maintenance and stowage functions

The need and potential solutions for an orderly systems engineering approach to the definition, management and documentation requirements for in-flight maintenance, assembly, servicing, and stowage process activities of the flight crews of future spacecraft were investigated. These processes were analyzed and described using a new technique (mass/function flow diagramming), developed during the study, to give visibility to crew functions and supporting requirements, including data products. This technique is usable by NASA for specification baselines and can assist the designer in identifying both upper and lower level requirements associated with these processes. These diagrams provide increased visibility into the relationships between functions and related equipments being utilized and managed and can serve as a common communicating vehicle between the designer, program management, and the operational planner. The information and data product requirements to support the above processes were identified along with optimum formats and contents of these products. The resulting data product concepts are presented to support these in-flight maintenance and stowage processes.

Carl, J. G.↗

RadLab and the Environmental Data Application Dashboard: Graphical and Programming Interfaces for Interrogation of Space Telemetry Data

Sensors on the International Space Station (ISS) and multiple spacecraft elsewhere in Earth orbit and in deep space continuously monitor and collect environmental data, transmitting this information back to Earth. These data include ionizing radiation and, on the ISS, CO2, relative humidity levels, and temperature, and are of great importance to space biology research. Ionizing radiation in particular has been established in ground-based experiments as being correlated with increased risk of carcinogenesis and cardiovascular and neurological effects. Looking ahead to future long duration crewed missions beyond low Earth orbit, the ability to study how factors including CO2 levels, light cycle, temperature modulate the response to ionizing radiation and microgravity is essential. To date, access to these data has been fragmented across space agencies, spacecraft, and databases. To address this issue, NASA’s Open Science Data Repository (osdr.nasa.gov) has developed two Web applications: the Environmental Data Application (EDA) and a radiation-specific RadLab. Each consists of an API (application programming interface) and an associated GUI (graphical user interface) that provide single points of access to the data. To date, OSDR has focused on the sensors from payloads and radiation detectors located on the ISS. The Web applications process telemetry information and associated data, such as spacecraft location and orientation, from multiple international databases. The applications’ request syntax enables users to interrogate these data by craft, sensor type, time range, radiation type (galactic cosmic rays, solar particle events, the contribution of the South Atlantic Anomaly), facilitating arbitrary comparisons of original source data at varying time resolutions. The applications provide programmatic access for use in computational pipelines and GUIs for data visualization and exploration, making these data FAIR (Findable, Accessible, Interoperable, and Reusable), complementing the biological data contained in OSDR, and providing the space science community with a valuable resource for scientific analyses.

radiation↗

The Repair Maintenance and Fabrication Facility in the Common Habitat Architecture

The Common Habitat Architecture seeks to increase the habitability of long-duration human spaceflight systems. A key aspect of this is vehicle survivability. Missions beyond low Earth orbit need onboard capabilities for Repair, Maintenance, And Fabrication (RMAF) to overcome potential contingency scenarios. Strategies employed in historic human spaceflight such as redundancy management, reliability, sparing, orbital replacement units, and aborts may be insufficient by themselves. Based on subject matter input, a list of 53 critical failures defining a set of incidents that can render a key spacecraft subsystem inoperable were generated. A subsequent analysis found that a robust in-space RMAF system capable of performing 14 key functions can potentially repair a subsystem plagued by any of these failures. An ancillary benefit is this capability may provide psychological benefits to the crew, by enabling greater self-sufficiency in earth-independent problem solving. A basic RMAF facility has been defined for the Common Habitat, consisting of five workstations. A work bench and computer workstation provide a multipurpose horizontal work surface, computing interface, and tools storage. A CNC machining center provides a subtractive manufacturing capability for metals and plastics. A multi-material 3D printing facility provides additive manufacturing capabilities for plastic, metals, and printed electronics. A welding facility is used for joining metal components where a higher strength is needed than can be achieved with fasteners or adhesives. A glovebox facility is used to perform work that is too hazardous for any of the other workstations. This may include hardware brought in from outside the spacecraft that could potentially contaminate the cabin environment. Forward work includes considering the accommodation of additional manufacturing processes not modeled in the current system, assessing the ability of systems to operate in partial gravity and microgravity environments, incorporation of the system into the Common Habitat Computer Aided Design (CAD) model, bottoms-up mass estimating, and a crew time analysis.

Habitat↗

KU-Band rendezvous radar performance computer simulation model

The preparation of a real time computer simulation model of the KU band rendezvous radar to be integrated into the shuttle mission simulator (SMS), the shuttle engineering simulator (SES), and the shuttle avionics integration laboratory (SAIL) simulator is described. To meet crew training requirements a radar tracking performance model, and a target modeling method were developed. The parent simulation/radar simulation interface requirements, and the method selected to model target scattering properties, including an application of this method to the SPAS spacecraft are described. The radar search and acquisition mode performance model and the radar track mode signal processor model are examined and analyzed. The angle, angle rate, range, and range rate tracking loops are also discussed.

Griffin, J. W.↗

Automated Operations Development for Advanced Exploration Systems

Automated space operations command and control software development and its implementation must be an integral part of the vehicle design effort. The software design must encompass autonomous fault detection, isolation, recovery capabilities and also provide "single button" intelligent functions for the crew. Development, operations and safety approval experience with the Timeliner system onboard the International Space Station (ISS), which provided autonomous monitoring with response and single command functionality of payload systems, can be built upon for future automated operations as the ISS Payload effort was the first and only autonomous command and control system to be in continuous execution (6 years), 24 hours a day, 7 days a week within a crewed spacecraft environment. Utilizing proven capabilities from the ISS Higher Active Logic (HAL) System, along with the execution component design from within the HAL 9000 Space Operating System, this design paper will detail the initial HAL System software architecture and interfaces as applied to NASA's Habitat Demonstration Unit (HDU) in support of the Advanced Exploration Systems, Autonomous Mission Operations project. The development and implementation of integrated simulators within this development effort will also be detailed and is the first step in verifying the HAL 9000 Integrated Test-Bed Component [2] designs effectiveness. This design paper will conclude with a summary of the current development status and future development goals as it pertains to automated command and control for the HDU.

Haddock, Angie T.↗

EVA Swab Kit: Tools and Techniques for Collecting Aseptic Samples from Crewed Space Missions

Introduction: When we send humans to search for life on other planets, we'll need to know what we brought with us versus what may already be there. To ensure our crewed spacecraft meet planetary protection requirements—and to protect our science from human contamination—we'll need to assess and verify whether micro-organisms may be leaking/venting from our spacesuits. This requires collecting samples under Extravehicular Activity (EVA) conditions. Detailed, systematic research on forward contamination from robotic spacecraft has been steadily progressing since the Viking missions, but systematic studies of contamination from space suits has not been conducted in many years. The modern EMU (Extravehicular Mobility Unit) suit used by NASA is designed to leak at rates as high as 100 cc/min. Before humans land on Mars there is a critical need to understand the types and quantities of microbes that could be introduced via space suits. The Human Forward Contamination Assessment team at NASA’s Johnson Space Center (JSC) has developed a prototype EVA swab tool [1,2,3,4] designed for use in space to sample cleaned and uncleaned space suits to determine the present day microbial load and eventually the rate of leakage. The ability to assess microbial leakage early in advanced space suit and life support system design cycles will help avoid costly hardware redesign later. Test Objectives: The primary objective of EMU testing was to characterize the type of micro-organisms typically found on or near selected suit pressure joints under suit differential pressure conditions. Most human-borne microbes can fit through a 0.5 to 1.0 µm gap. Knowing which joints are more likely to leak will inform hardware design decisions. Knowing which types of micro-organisms may leak from EVA suits provides a basis for subsequent studies to characterize the viability of those organisms under destination conditions, as well as how far they might spread through natural or human-influenced processes. That data, in turn, will inform exploration mission operations and hardware design. The secondary objective of testing was to evaluate the interface between a fully suited test subject and the EVA swab tool at vacuum. Bulky EVA suits can restrict movement and limit visibility through the helmet visor. Fully suited testing is important for identifying tool design issues prior to flight. At exploration destinations, such as Mars, suited crew may be required to periodically sample their suits as part of an environmental monitoring protocol. Suit Microbial Sampling Results: This report details results of microbial swabs collected from current flight suit configurations worn by crew members assigned to upcoming ISS expedition missions as well as swabs collected from prototype suits intended for use on the Orion spacecraft. These tests were intended to characterize the types of contaminants found on flight suits under current, typical handling conditions. No attempt was made to change suit handling procedures, provide additional sterilization, or to limit typical potential contaminant sources. Using culture based techniques, we cultivated 235 CFU (colony forming units) comprised of 26 bacterial species and one fungal species on the outside of the suits. The fungal species and 14 of the bacterial species were unique to the suit surfaces and were not detected in any of the background samples collected within the chambers. We sequenced 755,434 ribosomal fragments on all of the suit surfaces from swab samples. 557,016 of these sequences represent DNA that survived at least 4 hours at vacuum. These sequences formed 2,464 OTU's (Operational Taxonomic Units, 97% similarity) showing low diversity in the samples. The most abundant sequences that survived vacuum belong to the genera Staphyloccocus, Ralstona, Bacillus and Rhodobacter all of which are common to the human microbiome. [5] See Danko et al., (2021) for more complete details of these first analyses. Further analysis of EVA suit materials with respect to the efficacy of various cleaning protocols and engineered containment solutions is planned to inform suit design for NASA’s Artemis Moon to Mars program crew testing. Swab Tool Function Results: The kit was demonstrated for fit and function in suited subject vacuum tests to determine how well the tool worked as an aseptic microbial sampling device as well as to identify any design elements that could be upgraded for EVA task specific improvement. It was found that sample acquisition efficacy could be enhanced by redesign of the sample canister to end-effector interface. Several modifications of the sample caddy assemblies to optimize EVA safety and functionality were also identified. Consequently, fabrication of the redesigned sample canister to end-effector assembly interfaces and and the sample caddy assemblies are required. Fabrication of sixteen flight sample canister assemblies (8 per each of two EVA Swab Kits) and two sample caddy assemblies are in process to be followed by hardware testing and certification to produce two flight-certified EVA Swab Kits for transport to ISS no earlier than summer of 2022. Sampling Strategy: The International Space Station is an ideal testbed for systematic studies of contamination from crewed vehicles since it has been continuously occupied for 20 years and exposed to non-terrestrial conditions. We will sample the exterior of the ISS during EVA using a purpose-built swab tool capable of maintaining sterility while undergoing temperature changes from -151 to +121°C under hard vacuum. Prior to each EVA, the project team will work with ISS mission managers to identify precise sampling locations, which will vary by EVA based on the translation paths and worksites scheduled for that particular EVA. Ideally, translation path handrails and areas near ECLSS (Environmental Control and Life Support System) external vent openings on a spacecraft would be assessed. There are currently more than a dozen ECLSS external vents on the ISS. Some are connected to systems that vent waste products, while others are intended to equalize cabin pressure. As EVA opportunity allows, microbial samples from any of these external vents would provide a valuable data point, though some will be more useful than others. Four criteria have been identified to help prioritize sampling sites near vents: • EVA Accessibility: To minimize cost, it is desired to piggy-back onto a planned EVA. Therefore, the sampling location must be readily accessible by an EVA crew • Type of Vented Products: Vent products that have been in direct contact with crew, such as cabin air, are more likely to contain microorganisms than vent products associated with isolated systems, such as experiment module combustion products. • Mass of Vented Products: Higher-flow vents are more likely to contain detectible levels of microbial contaminants than lower-flow vents. • Local Environment: Sample locations with relatively benign local conditions, such as warm surfaces shielded from direct ultraviolet (UV) radiation exposure, may be more likely to support microbial growth than locations with harsher local environmental conditions. Because EVA accessibility is the most important criteria, the proposal team worked with an astronaut and flight controllers using the Dynamic Onboard Ubiquitous Graphics (DOUG) tool. The DOUG virtual environment allows an operator to “fly” around the current ISS vehicle configuration to assess EVA translation paths, attach points, and keep-out zones. While analysis on station or rapid return to Earth would be preferable, samples collected from the exterior of the ISS have already been exposed to temperature variations between -157 and +121 °C as well as hard vacuum. Therefore, they should be fairly stable and robust. We hypothesize that samples collected from the ISS exterior could be stored for up to 6 months at -80°C without degradation. Sample canisters will be returned to Earth while frozen at -80°C for analysis, and sterilized canisters can be re-flown back to ISS to support additional sampling opportunities Relevance to NASA Exploration Objectives: These data will allow us to identify new or improved methods, technologies, and procedures for spacecraft sterilization and leakage mitigation to minimize the amount of contamination introduced to the environment by human explorers. This work is funded by NASA research grant: NNH18ZDA001N-PPR References: [1] Bell, M.S. et al. (2015) LPS XLVI, Abst. #1832 [2] Rucker et al. (2018) 42nd COSPAR (PPP.3) [3] Bell, M.S. et al. (2019) Mars Extant Life Conference, Abst. #5096.[4] Bell, M.S. et al., (2020) 43rd COSPAR (BO.2).[5] Danko D, et.al.,(2021)Front.Microbiol.12:608478.

Mary Suzanne Bell↗

AMO EXPRESS: A Command and Control Experiment for Crew Autonomy Onboard the International Space Station

NASA is investigating a range of future human spaceflight missions, including both Mars-distance and Near Earth Object (NEO) targets. Of significant importance for these missions is the balance between crew autonomy and vehicle automation. As distance from Earth results in increasing communication delays, future crews need both the capability and authority to independently make decisions. However, small crews cannot take on all functions performed by ground today, and so vehicles must be more automated to reduce the crew workload for such missions. NASA's Advanced Exploration Systems Program funded Autonomous Mission Operations (AMO) project conducted an autonomous command and control experiment on-board the International Space Station that demonstrated single action intelligent procedures for crew command and control. The target problem was to enable crew initialization of a facility class rack with power and thermal interfaces, and involving core and payload command and telemetry processing, without support from ground controllers. This autonomous operations capability is enabling in scenarios such as initialization of a medical facility to respond to a crew medical emergency, and representative of other spacecraft autonomy challenges. The experiment was conducted using the Expedite the Processing of Experiments for Space Station (EXPRESS) rack 7, which was located in the Port 2 location within the U.S Laboratory onboard the International Space Station (ISS). Activation and deactivation of this facility is time consuming and operationally intensive, requiring coordination of three flight control positions, 47 nominal steps, 57 commands, 276 telemetry checks, and coordination of multiple ISS systems (both core and payload). Utilization of Draper Laboratory's Timeliner software, deployed on-board the ISS within the Command and Control (C&C) computers and the Payload computers, allowed development of the automated procedures specific to ISS without having to certify and employ novel software for procedure development and execution. The procedures contained the ground procedure logic and actions as possible to include fault detection and recovery capabilities.

Stetson, Howard K.↗

AMO EXPRESS: A Command and Control Experiment for Crew Autonomy Onboard the International Space Station

NASA is investigating a range of future human spaceflight missions, including both Mars-distance and Near Earth Object (NEO) targets. Of significant importance for these missions is the balance between crew autonomy and vehicle automation. As distance from Earth results in increasing communication delays, future crews need both the capability and authority to independently make decisions. However, small crews cannot take on all functions performed by ground today, and so vehicles must be more automated to reduce the crew workload for such missions.NASAs Advanced Exploration Systems Program funded Autonomous Mission Operations (AMO) project conducted an autonomous command and control experiment on-board the International Space Station that demonstrated single action intelligent procedures for crew command and control. The target problem was to enable crew initialization of a facility class rack with power and thermal interfaces, and involving core and payload command and telemetry processing, without support from ground controllers. This autonomous operations capability is enabling in scenarios such as initialization of a medical facility to respond to a crew medical emergency, and representative of other spacecraft autonomy challenges. The experiment was conducted using the Expedite the Processing of Experiments for Space Station (EXPRESS) rack 7, which was located in the Port 2 location within the U.S Laboratory onboard the International Space Station (ISS).

Autonomous Mission Operations↗

Development of an Inflatable Airlock for Deep Space Exploration

An airlock is a required component of a crewed spacecraft to allow for maintenance, repair and exploration outside of a habitable vehicle. Airlock designs in use today are rigid pressure vessels with complex hatches and seals. Inflatable structures technology utilizes high strength fabric materials and internal pressure to create a stiffened pressure vessel that can replace traditional rigid primary structure in a habitable spacecraft. The flexibility of fabric structures allows them to be compactly stowed for launch and expanded in space. Recent developments towards the design of an inflatable airlock structure show feasibility and a significant launch volume savings over a traditional metallic design. This paper provides a detailed summary of historical and current work in inflatable airlock development and provides guidance for the design of a soft goods airlock system. Accommodations for withstanding crew-induced loads, provisions for human interfaces, the design and development of an internal substructure to provide translation aids and restraints, the thermal considerations of a fabric shell, micrometeoroid protection in deep space, and packaging and deployment of an inflatable airlock are all discussed.

Deep Space Exploration↗

Automated Operations Development for Advanced Exploration Systems

Automated space operations command and control software development and its implementation must be an integral part of the vehicle design effort. The software design must encompass autonomous fault detection, isolation, recovery capabilities and also provide single button intelligent functions for the crew. Development, operations and safety approval experience with the Timeliner system on-board the International Space Station (ISS), which provided autonomous monitoring with response and single command functionality of payload systems, can be built upon for future automated operations as the ISS Payload effort was the first and only autonomous command and control system to be in continuous execution (6 years), 24 hours a day, 7 days a week within a crewed spacecraft environment. Utilizing proven capabilities from the ISS Higher Active Logic (HAL) System [1] , along with the execution component design from within the HAL 9000 Space Operating System [2] , this design paper will detail the initial HAL System software architecture and interfaces as applied to NASA s Habitat Demonstration Unit (HDU) in support of the Advanced Exploration Systems, Autonomous Mission Operations project. The development and implementation of integrated simulators within this development effort will also be detailed and is the first step in verifying the HAL 9000 Integrated Test-Bed Component [2] designs effectiveness. This design paper will conclude with a summary of the current development status and future development goals as it pertains to automated command and control for the HDU.

Haddock, Angie↗

Next Generation Flight Displays Using HTML5

The Human Integrated Vehicles and Environments (HIVE) lab at Johnson Space Center (JSC) is focused on bringing together inter-disciplinary talent to design and integrate innovative human interface technologies for next generation manned spacecraft. As part of this objective, my summer internship project centered on an ongoing investigation in to building flight displays using the HTML5 standard. Specifically, the goals of my project were to build and demo "flight-like" crew and wearable displays as well as create a webserver for live systems being developed by the Advanced Exploration Systems (AES) program. In parallel to my project, a LabVIEW application, called a display server, was created by the HIVE that uses an XTCE (XML (Extensible Markup Language) Telemetry and Command Exchange) parser and CCSDS (Consultative Committee for Space Data System) space packet decoder to translate telemetry items sent by the CFS (Core Flight Software) over User Datagram Protocol (UDP). It was the webserver's job to receive these UDP messages and send them to the displays. To accomplish this functionality, I utilized Node.js and the accompanying Express framework. On the display side, I was responsible for creating the power system (AMPS) displays. I did this by using HTML5, CSS and JavaScript to create web pages that could update and change dynamically based on the data they received from the webserver. At this point, I have not started on the commanding, being able to send back to the CFS, portion of the displays but hope to have this functionality working by the completion of my internship. I also created a way to test the webserver's functionality without the display server by making a JavaScript application that read in a comma-separate values (CSV) file and converted it to XML which was then sent over UDP. One of the major requirements of my project was to build everything using as little preexisting code as possible, which I accomplished by only using a handful of JavaScript libraries. As a side project, I created a model of the HIVE lab and Building 29 using SketchUp. I obtained the floorplans of the building from the JSC Geographic Information Systems (GIS), which were computer-aided design (CAD) files, and imported them into SketchUp. I then took those floorplans and created a 3D model of the building from them. Working in conjunction with the Hybrid Reality lab in Building 32, the SketchUp model was imported into Unreal Engine for use with the HTC Vive. Using the Vive, I was able to interact with the model I created in virtual reality (VR). The purpose of this side project was to be able to visualize potential lab layouts and mockup designs as they are in development in order to finalize design decisions. Pending approval, the model that I created will be used in the Build-As-You-Test: Can Hybrid Reality Improve the SE/HSI Design Process project in the fall. Getting the opportunity to work at NASA has been one of the most memorable experiences of my life. Over the course of my internship, I improved my programming and web development abilities substantially. I will take all the skills and experiences I have had while at NASA back to school with me in the fall and hope to pursue a career in the aerospace industry after graduating in the spring.

Greenwood, Brian↗

Aerospace crew station design

Consideration is given to spacecraft cockpits and work stations, commercial aircraft cockpits and crew stations, high performance aircraft cockpits and crew stations, and space stations and habitat crew stations. Particular attention is given to an historical review of NASA manned spacecraft crew stations, ESA spacelab crew stations, the evolution of commercial aircraft flight station design, Boeing 757/767 flight deck, a historical review of Concorde flight deck design, trends in the cockpit design of new European fighters, and state-of-the-art applications for Space Station crew interface design.

Carr, Gerald P.↗

Standard Materials and Processes Requirements for Spacecraft

This NASA Technical Standard is directed toward materials and processes (M&P) used in the design, fabrication, and testing of space program flight hardware for NASA, including but not limited to crewed, uncrewed, robotic, launch vehicle, lander, in-space and surface systems, and spacecraft program/project hardware elements. All spaceflight hardware is covered by the M&P requirements of this document, including vendor-designed, off-the-shelf, and vendor-furnished items. M&P used in interfacing ground support equipment (GSE), test equipment, hardware processing equipment, hardware packaging, and hardware shipment is covered by the M&P requirements of this NASA Technical Standard only to the extent required to prevent damage to or contamination of spaceflight hardware (see section 4). M&P used in NASA aircraft and aircraft operations are not covered by the M&P requirements of this document.

Materials↗

New Human-Computer Interface Concepts for Mission Operations

The current climate of budget cuts has forced the space mission operations community to reconsider how it does business. Gone are the days of building one-of-kind control centers with teams of controllers working in shifts 24 hours per day, 7 days per week. Increasingly, automation is used to significantly reduce staffing needs. In some cases, missions are moving towards lights-out operations where the ground system is run semi-autonomously. On-call operators are brought in only to resolve anomalies. Some operations concepts also call for smaller operations teams to manage an entire family of spacecraft. In the not too distant future, a skeleton crew of full-time general knowledge operators will oversee the operations of large constellations of small spacecraft, while geographically distributed specialists will be assigned to emergency response teams based on their expertise. As the operations paradigms change, so too must the tools to support the mission operations team's tasks. Tools need to be built not only to automate routine tasks, but also to communicate varying types of information to the part-time, generalist, or on-call operators and specialists more effectively. Thus, the proper design of a system's user-system interface (USI) becomes even more importance than before. Also, because the users will be accessing these systems from various locations (e.g., control center, home, on the road) via different devices with varying display capabilities (e.g., workstations, home PCs, PDAS, pagers) over connections with various bandwidths (e.g., dial-up 56k, wireless 9.6k), the same software must have different USIs to support the different types of users, their equipment, and their environments. In other words, the software must now adapt to the needs of the users! This paper will focus on the needs and the challenges of designing USIs for mission operations. After providing a general discussion of these challenges, the paper will focus on the current efforts of creatin(y an effective USI for one specific suite of tools, SERS (The Spacecraft Emergency Response System), which has been built to enable lights-out operations. SERS is a Web-based collaborative environment that enables secure distributed fault management.

Fox, Jeffrey A.↗

The design and fabrication of the Centaur neutral buoyancy trainer and related hardware

Two full scale mockups of the Centaur upper stage were designed, fabricated and delivered to NASA. One was the Centaur Weightless Environment Training Facility (WETF) trainer and the other was the Centaur 1-G mockup. The Centaur upper stage booster is designed to carry the spacecraft Galileo to Jupiter, and the spacecraft Ulysses to an orbit around the Sun after launch from the Space Shuttle. The flight vehicle has several Extravehicular Activity (EVA) contingency tasks that require crew training. This need for crew training generated the requirement for the Centaur WETF crew trainer, which is high fidelity in areas of expected crew interface. During the production of the Centaur WETF crew trainer, the need for a jumper cable from Centaur to the Orbiter was identified. This EVA contingency task would be the installation of a cable from the Orbiter cargo bay sill to various command data boxes on Centaur to allow crew control deployment should a failure occur. This task required the upgrading of volumetric boxes on the trainer to a high fidelity configuration including electrical connector installation and cable routing.

Ware, Alan S.↗

Spacecraft Requirements Development and Tailoring

Spacecraft design is managed through the use of design requirements. Requirements are flowed from the highest level, the overall spacecraft, to systems, subsystems and ultimately individual components. Through the use of requirements, each part of the spacecraft will perform the functions that are required of it and will interface to the rest of the spacecraft. Functional requirements are used to make sure every component performs as expected and interface requirements ensure that each component works within the larger design environment where it operates. Writing good requirements is difficult and the verification of requirements can be expensive and time consuming. Because of this difficulty and expense, it is important that each requirement truly be “required” and critical to the overall performance of the vehicle. It is also important that requirements can be changed or eliminated as the system matures to minimize verification cost and schedule. The Capsule Parachute Assembly System (CPAS) Project is developing the parachute system for the NASA Multi-Purpose Crew Vehicle (MPCV) Orion Spacecraft. Throughout the development and qualification cycle for CPAS, requirements have been evaluated, added, eliminated, or more generically, “tailored”, to ensure that the system performs as required while minimizing the verification cost to the Program. One facet of this tailoring has been to delete requirements that do not add value to the overall spacecraft or are not needed. A second approach to minimize the cost of requirement verification has been to evaluate requirements based on the actual design as it has matured. As the design of the parachute system has become better understood, requirements that are not applicable have been eliminated. This paper will outline the evolution of CPAS requirements over time and will show how careful and considered changes to requirements can benefit the technical solution for the overall system design while allowing a Project to control costs.

Mcmichael, James H.↗

Space Launch System Spacecraft and Payload Elements: Making Progress Toward First Launch

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.

Schorr, Andrew A.↗