Search NASA⌕ Search

SEARCH · Search NASA

Results for “Systems Engineering and Program Integration”

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 1,333 records · Page 74

The Inspectability Metric: A Formalized System Of Measurement Enabling The Design For Inspection Framework

Nondestructive evaluation (NDE) engineers are often confronted with structural design choices that present challenges to meeting inspection requirements. These challenges, at best, increase the resources needed to design an inspection solution and, at worst, require resource intensive redesign of the structure. If the inspectability of the structure can be determined early in the design cycle, these challenging inspection scenarios can be avoided. The emergence of additive manufacturing has further compounded this problem by enabling the creation of highly optimized structures with no regard to inspection constraints. Design for inspection (DFI) offers a framework to integrate nondestructive evaluation (NDE) into the design process to alleviate the mechanisms that produce uninspectable designs. DFI is the concept of including inspectability in a multi-objective optimization framework so that it can be considered in parallel to other metrics such as mass and manufacturability. This allows rapid evaluation of the trade-off between design metrics to find solutions that meet the inspection needs of a particular material system, structural concept, or vehicle program. To enable DFI, there must be a system by which the inspectability of a structure can be measured. This system must be agile to produce results quickly, it must be versatile to work with the type of incomplete information one would encounter early in the design process (such as lack of inspection requirements), and it must be delivered in a form that is easily understood by designers. To meet this need, this presentation introduces the novel inspectability metric as a system to measure inspectability. The inspectability metric is a standardized, automation friendly procedure that uses simulations to determine inspectability. Along with guidelines to properly process designs and integrate with existing workflows, the inspectability metric provides a suite of simulation tests to interrogate the ability to find defects and the sensitivity to variability. The testing rubric is designed to maximize the coverage of the parameter space while minimizing the number of simulations needed. The inspectability metric has been in development in collaboration with industry partners to ensure compatibility with modern simulation tools and aerospace design workflows. In this study, we will demonstrate how the inspectability metric is able to determine the inspectability of multiple types of structures, including aerospace composites and additively manufactured parts. We will then show how the inspectability score can be plugged into existing design optimization tasks, such as structural sizing algorithms or design for manufacturing (DFM) frameworks.

Design for inspection↗

Titan/Centaur T/C-1 post flight evaluation report

The first Titan/Centaur launch vehicle, TC-1, was launched from the Eastern Test Range Complex 41 at 09:48:01.46 hours Eastern Daylight Time on February 11, 1974. The vehicle carried a dynamic mass model of the Viking spacecraft and a SPHINX spacecraft, intended to study high voltage interactions in space. This launch was a Proof Flight of a vehicle con- figuration integrating the Air Force Titan booster and the NASA Centaur upper stage. It also was the first flight of the Centaur Standard Shroud developed for the Titan/Centaur. The countdown for the launch proceeded normally except for an additional 45 minute hold which was required to resolve a question concerning interpretation of booster hydraulic system data. The launch window opened at 09:03:00 hours Eastern Daylight Time. The vehicle was launched o on a flight azimuth of 105°. The Titan boost phase of flight was satisfactory. Solid Motor operation, Stage I and Stage II operation were normal. Venting of the Centaur Standard Shroud during ascent was successful and shroud separation and jettison was accomplished without incident. At the completion of the Titan Stage II burn, the Centaur successfully separated from the Titan. At this time, the Centaur main engines were sequenced through the first planned starting cycle but failed to achieve steady state operation. The vehicle flight control system, not sensing vehicle acceleration, commanded engine shutdown, and recycled, as programmed, through a back-up engine start attempt. The second engine start attempt was also unsuccessful. The flight control system then placed the vehicle in a coast-phase mode and the vehicle continued downrange in free fall. The vehicle was destroyed by Range Safety when the impact point was approximately 2200 nautical miles downrange, 12 minutes, 28.5 seconds after liftoff.

S. V. Szabo, Jr.↗

NASA Space Flight Vehicle Fault Isolation Challenges

The Space Launch System (SLS) is the new NASA heavy lift launch vehicle and is scheduled for its first mission in 2017. The goal of the first mission, which will be uncrewed, is to demonstrate the integrated system performance of the SLS rocket and spacecraft before a crewed flight in 2021. SLS has many of the same logistics challenges as any other large scale program. Common logistics concerns for SLS include integration of discrete programs geographically separated, multiple prime contractors with distinct and different goals, schedule pressures and funding constraints. However, SLS also faces unique challenges. The new program is a confluence of new hardware and heritage, with heritage hardware constituting seventy-five percent of the program. This unique approach to design makes logistics concerns such as testability of the integrated flight vehicle especially problematic. The cost of fully automated diagnostics can be completely justified for a large fleet, but not so for a single flight vehicle. Fault detection is mandatory to assure the vehicle is capable of a safe launch, but fault isolation is another issue. SLS has considered various methods for fault isolation which can provide a reasonable balance between adequacy, timeliness and cost. This paper will address the analyses and decisions the NASA Logistics engineers are making to mitigate risk while providing a reasonable testability solution for fault isolation.

Bramon, Christopher↗

Rocketdyne - Lunar Ascent Engine

The ascent engine was the last one from the moon, and I want to focus on the idea of redundancy and teams in regard to the engine. By teams, I mean teamwork - not just within Rocketdyne. It was teamwork within Rocketdyne; it was teamwork within Grumman; it was teamwork within NASA. These were all important elements leading to the successful development of the lunar excursion module (LEM) engine. Communication, rapid response, and cooperation were all important. Another aspect that went into the development of the ascent engine was the integration of technology and of lessons learned. We pushed all the above, plus technology and lessons learned, into a program, and that led to a successful result. One of the things that I like to think about - again in retrospect - is how it is very "in" now to have integrated product and process teams. These are buzzwords for teamwork in all program phases. That s where you combine a lot of groups into a single organization to get a job done. The ascent engine program epitomized that kind of integration and focus, and because this was the mid- to late-1960s; this was new ground for Rocketdyne, Grumman, and NASA. Redundancy was really a major hallmark of the Apollo Program. Everything was redundant. Once you got the rocket going, you could even lose one of the big F-1 engines, and it would still make it to orbit. And once the first stage separated from the rest of the vehicle, the second stage could do without an engine and still make a mission. This redundancy was demonstrated when an early Apollo launch shut down a J-2 second-stage engine. Actually, they shut down two J-2 engines on that flight. Even the third stage, with its single J-2 engine, was backed up because the first two stages could toss it into a recoverable orbit. If the third stage didn't work, you were circling the earth, and you had time to recover the command module and crew. Remember how on the Apollo 13 flight, there was sufficient system redundancy even when we lost the service module. That was a magnificent effort. TRW Inc. really ought to be proud of their engine for that. (See Slide 2, Appendix I) We had planned for redundancy; we had landed on the moon. However, weight restrictions in the architecture said, "You can t have redundancy for ascent from the moon. You've got one engine. It s got to work. There is no second chance. If that ascent engine doesn't work, you re stuck there." It would not have looked good for NASA. It wouldn't have looked good for the country. There was a letter written that President Richard Nixon would read if the astronauts got stuck on the moon, expressing how sorry we were and so forth. It was a scary letter, really. The ascent engine was an engine that had to work. (See Slide 3, Appendix I).

Harmon, Tim↗

Constraints and Opportunities in GCM Model Development

Over the past 30 years climate models have evolved from relatively simple representations of a few atmospheric processes to complex multi-disciplinary system models which incorporate physics from bottom of the ocean to the mesopause and are used for seasonal to multi-million year timescales. Computer infrastructure over that period has gone from punchcard mainframes to modern parallel clusters. Constraints of working within an ever evolving research code mean that most software changes must be incremental so as not to disrupt scientific throughput. Unfortunately, programming methodologies have generally not kept pace with these challenges, and existing implementations now present a heavy and growing burden on further model development as well as limiting flexibility and reliability. Opportunely, advances in software engineering from other disciplines (e.g. the commercial software industry) as well as new generations of powerful development tools can be incorporated by the model developers to incrementally and systematically improve underlying implementations and reverse the long term trend of increasing development overhead. However, these methodologies cannot be applied blindly, but rather must be carefully tailored to the unique characteristics of scientific software development. We will discuss the need for close integration of software engineers and climate scientists to find the optimal processes for climate modeling.

Schmidt, Gavin↗

NASA’s Space Launch System: Progress Toward Launch

The Space Launch System (SLS), NASA’s cornerstone launch capability for a new generation of deep space exploration, has begun assembly at Kennedy Space Center (KSC) in preparation for launch in 2021. SLS will provide an unparalleled launch capability for human and robotic deep space exploration missions. Its proven propulsion system, upgrade path to more powerful vehicles, and high-volume payload fairings make it the foundation for ambitious and demanding as part of the Artemis program. Artemis is NASA’s 21st-century plan to put boots on the Moon and to perform sustainable, long-term science in deep space, with eyes toward sending explorers to Mars. The initial SLS vehicle to fly, Block 1 in the crew configuration – with the new Orion spacecraft – is scheduled to lift off from revitalized launch facilities at KSC in 2021 for an uncrewed test flight known as Artemis I. Manufacturing is complete on the vehicle and all elements have been delivered to the Exploration Ground Systems (EGS) Program, except the core stage. The program’s all-new development, the core stage is currently in the midst of a “Green Run” test campaign at Stennis Space Center (SSC). Eight progressively more challenging tests in the Green Run series will culminate in a hot-fire of four flight-proven liquid hydrogen/liquid oxygen (LH2/LOX) RS25 engines. Following the Green Run hotfiring, the core stage will ship to KSC. Already at KSC, aft sections of the fivesegment solid rocket boosters are being assembled. Previously delivered elements, including the upper stage, are undergoing final checkouts in preparation for stacking. An exciting 2021 will include such milestones as stacking SLS and Orion in KSC’s Vehicle Assembly Building (VAB), modal testing, roll out to Launch Pad 39B, Wet Dress Rehearsal (WDR), and launch. Teams across the country are preparing for launch by finalizing procedures, defining launch constraints and flight rules, training console operators, performing simulations, and more. With the SLS Block 1 vehicle for Artemis I nearing integration and launch, the second Block 1 vehicle in the crew configuration, which will carry astronauts on an Artemis II hybrid lunar flyby mission, has several elements manufactured. In fact, the solid rocket motor segments and RS-25 engines are complete. Those program elements are processing hardware for the third flight and working toward manufacturing the second SLS variant to fly, Block 1B, which will onramp a powerful new upper stage, the Exploration Upper Stage (EUS).

John Honeycutt↗

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

M Kaetzer↗

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

Mary Susan Kaetzer↗

Launch Pad Coatings for Smart Corrosion Control

Corrosion is the degradation of a material as a result of its interaction with the environment. The environment at the KSC launch pads has been documented by ASM International (formerly American Society for Metals) as the most corrosive in the US. The 70 tons of highly corrosive hydrochloric acid that are generated by the solid rocket boosters during a launch exacerbate the corrosiveness of the environment at the pads. Numerous failures at the pads are caused by the pitting of stainless steels, rebar corrosion, and the degradation of concrete. Corrosion control of launch pad structures relies on the use of coatings selected from the qualified products list (QPL) of the NASA Standard 5008A for Protective Coating of Carbon Steel, Stainless Steel, and Aluminum on Launch Structures, Facilities, and Ground Support Equipment. This standard was developed to establish uniform engineering practices and methods and to ensure the inclusion of essential criteria in the coating of ground support equipment (GSE) and facilities used by or for NASA. This standard is applicable to GSE and facilities that support space vehicle or payload programs or projects and to critical facilities at all NASA locations worldwide. Environmental regulation changes have dramatically reduced the production, handling, use, and availability of conventional protective coatings for application to KSC launch structures and ground support equipment. Current attrition rate of qualified KSC coatings will drastically limit the number of commercial off the shelf (COTS) products available for the Constellation Program (CxP) ground operations (GO). CxP GO identified corrosion detection and control technologies as a critical, initial capability technology need for ground processing of Ares I and Ares V to meet Constellation Architecture Requirements Document (CARD) CxP 70000 operability requirements for reduced ground processing complexity, streamlined integrated testing, and operations phase affordability. Researchers at NASA's Corrosion Technology Laboratory at KSC are developing a smart, environmentally friendly coating system for early corrosion detection, inhibition, and self healing of mechanical damage without external intervention. This smart coating will detect and respond actively to corrosion and mechanical damage such as abrasion and scratches, in a functional and predictable manner, and will be capable of adapting its properties dynamically. This coating is being developed using corrosion sensitive microcapsules that deliver the contents of their core (corrosion inhibiting compounds, corrosion indicators, and self healing agents) on demand when corrosion or mechanical damage to the coating occurs.

Calle, Luz M.↗

NASA Space Rocket Logistics Challenges

The Space Launch System (SLS) is the new NASA heavy lift launch vehicle and is scheduled for its first mission in 2017. The goal of the first mission, which will be uncrewed, is to demonstrate the integrated system performance of the SLS rocket and spacecraft before a crewed flight in 2021. SLS has many of the same logistics challenges as any other large scale program. Common logistics concerns for SLS include integration of discreet programs geographically separated, multiple prime contractors with distinct and different goals, schedule pressures and funding constraints. However, SLS also faces unique challenges. The new program is a confluence of new hardware and heritage, with heritage hardware constituting seventy-five percent of the program. This unique approach to design makes logistics concerns such as commonality especially problematic. Additionally, a very low manifest rate of one flight every four years makes logistics comparatively expensive. That, along with the SLS architecture being developed using a block upgrade evolutionary approach, exacerbates long-range planning for supportability considerations. These common and unique logistics challenges must be clearly identified and tackled to allow SLS to have a successful program. This paper will address the common and unique challenges facing the SLS programs, along with the analysis and decisions the NASA Logistics engineers are making to mitigate the threats posed by each.

Neeley, James R.↗

Computer aided system engineering for space construction

This viewgraph presentation covers the following topics. Construction activities envisioned for the assembly of large platforms in space (as well as interplanetary spacecraft and bases on extraterrestrial surfaces) require computational tools that exceed the capability of conventional construction management programs. The Center for Space Construction is investigating the requirements for new computational tools and, at the same time, suggesting the expansion of graduate and undergraduate curricula to include proficiency in Computer Aided Engineering (CAE) though design courses and individual or team projects in advanced space systems design. In the center's research, special emphasis is placed on problems of constructability and of the interruptability of planned activity sequences to be carried out by crews operating under hostile environmental conditions. The departure point for the planned work is the acquisition of the MCAE I-DEAS software, developed by the Structural Dynamics Research Corporation (SDRC), and its expansion to the level of capability denoted by the acronym IDEAS**2 currently used for configuration maintenance on Space Station Freedom. In addition to improving proficiency in the use of I-DEAS and IDEAS**2, it is contemplated that new software modules will be developed to expand the architecture of IDEAS**2. Such modules will deal with those analyses that require the integration of a space platform's configuration with a breakdown of planned construction activities and with a failure modes analysis to support computer aided system engineering (CASE) applied to space construction.

Racheli, Ugo↗

Managed Development Environment Successes for MSFC's VIPA Team

This paper outlines the best practices of the Vehicle Design Team for VIPA. The functions of the VIPA Vehicle Design (VVD) discipline team are to maintain the controlled reference geometry and provide linked, simplified geometry for each of the other discipline analyses. The core of the VVD work, and the approach for VVD s first task of controlling the reference geometry, involves systems engineering, top-down, layout-based CAD modeling within a Product Data Manager (PDM) development environment. The top- down approach allows for simple control of very large, integrated assemblies and greatly enhances the ability to generate trade configurations and reuse data. The second VVD task, model simplification for analysis, is handled within the managed environment through application of the master model concept. In this approach, there is a single controlling, or master, product definition dataset. Connected to this master model are reference datasets with live geometric and expression links. The referenced models can be for drawings, manufacturing, visualization, embedded analysis, or analysis simplification. A discussion of web based interaction, including visualization, between the design and other disciplines is included. Demonstrated examples are cited, including the Space Launch Initiative development cycle, the Saturn V systems integration and verification cycle, an Orbital Space Plane study, and NASA Exploration Office studies of Shuttle derived and clean sheet launch vehicles. The VIPA Team has brought an immense amount of detailed data to bear on program issues. A central piece of that success has been the Managed Development Environment and the VVD Team approach to modeling.

Finckenor, Jeff↗

Human Rating Requirements for NASA's Constellation Program

NASA s Constellation Program (CxP) will conduct a series of human space expeditions of increasing scope, starting with missions supporting the International Space Station and expanding to encompass the Moon and Mars. Although human-rating is an integral part of all CxP activities throughout their life cycle, NASA Procedural Requirements document NPR 8705.2B, Human-Rating Requirements (HRR) for Space Flight Systems, defines the additional processes, procedures, and requirements necessary to produce human-rated space systems that protect the safety of crew members and passengers on these NASA missions. In order to be in compliance with 8705.2B the CxP must show appropriate implementation or progression toward the HRR, or justification for an exception. Compliance includes an explanation of how the CxP intends to meet the HRR, analyses to be performed to determine implementation; and a matrix to trace the HRR to CxP requirements. The HRR requires the CxP to establish a human system integration team (HSIT), consisting of astronauts, mission operations personnel, training personnel, ground processing personnel, human factors personnel, and human engineering experts, with clearly defined authority, responsibility, and accountability to lead the human-system integration. For example, per the HRR the HSIT is involved in the evaluation of crew workload, human-in-the-loop usability evaluations, determining associated criteria, and in assessment of how these activities influenced system design. In essence, the HSIT is invaluable in CxP s ability to meet the three fundamental tenets of human rating: the process of designing, evaluating, and assuring that the total system can safely conduct the required human missions; the incorporation of design features and capabilities that accommodate human interaction with the system to enhance overall safety and mission success; and the incorporation of design features and capabilities to enable safe recovery of the crew from hazardous situations.

Berdich, Debbie↗

Spinoff 2013

Topics covered include: Innovative Software Tools Measure Behavioral Alertness; Miniaturized, Portable Sensors Monitor Metabolic Health; Patient Simulators Train Emergency Caregivers; Solar Refrigerators Store Life-Saving Vaccines; Monitors Enable Medication Management in Patients' Homes; Handheld Diagnostic Device Delivers Quick Medical Readings; Experiments Result in Safer, Spin-Resistant Aircraft; Interfaces Visualize Data for Airline Safety, Efficiency; Data Mining Tools Make Flights Safer, More Efficient; NASA Standards Inform Comfortable Car Seats; Heat Shield Paves the Way for Commercial Space; Air Systems Provide Life Support to Miners; Coatings Preserve Metal, Stone, Tile, and Concrete; Robots Spur Software That Lends a Hand; Cloud-Based Data Sharing Connects Emergency Managers; Catalytic Converters Maintain Air Quality in Mines; NASA-Enhanced Water Bottles Filter Water on the Go; Brainwave Monitoring Software Improves Distracted Minds; Thermal Materials Protect Priceless, Personal Keepsakes; Home Air Purifiers Eradicate Harmful Pathogens; Thermal Materials Drive Professional Apparel Line; Radiant Barriers Save Energy in Buildings; Open Source Initiative Powers Real-Time Data Streams; Shuttle Engine Designs Revolutionize Solar Power; Procedure-Authoring Tool Improves Safety on Oil Rigs; Satellite Data Aid Monitoring of Nation's Forests; Mars Technologies Spawn Durable Wind Turbines; Programs Visualize Earth and Space for Interactive Education; Processor Units Reduce Satellite Construction Costs; Software Accelerates Computing Time for Complex Math; Simulation Tools Prevent Signal Interference on Spacecraft; Software Simplifies the Sharing of Numerical Models; Virtual Machine Language Controls Remote Devices; Micro-Accelerometers Monitor Equipment Health; Reactors Save Energy, Costs for Hydrogen Production; Cameras Monitor Spacecraft Integrity to Prevent Failures; Testing Devices Garner Data on Insulation Performance; Smart Sensors Gather Information for Machine Diagnostics; Oxygen Sensors Monitor Bioreactors and Ensure Health and Safety; Vision Algorithms Catch Defects in Screen Displays; and Deformable Mirrors Capture Exoplanet Data, Reflect Lasers.

Source record↗

An Overview of Starfish: A Table-Centric Tool for Interactive Synthesis

Engineering is an interactive process that requires intelligent interaction at many levels. My thesis [1] advances an engineering discipline for high-level synthesis and architectural decomposition that integrates perspicuous representation, designer interaction, and mathematical rigor. Starfish, the software prototype for the design method, implements a table-centric transformation system for reorganizing control-dominated system expressions into high-level architectures. Based on the digital design derivation (DDD) system a designer-guided synthesis technique that applies correctness preserving transformations to synchronous data flow specifications expressed as co- recursive stream equations Starfish enhances user interaction and extends the reachable design space by incorporating four innovations: behavior tables, serialization tables, data refinement, and operator retiming. Behavior tables express systems of co-recursive stream equations as a table of guarded signal updates. Developers and users of the DDD system used manually constructed behavior tables to help them decide which transformations to apply and how to specify them. These design exercises produced several formally constructed hardware implementations: the FM9001 microprocessor, an SECD machine for evaluating LISP, and the SchemEngine, garbage collected machine for interpreting a byte-code representation of compiled Scheme programs. Bose and Tuna, two of DDD s developers, have subsequently commercialized the design derivation methodology at Derivation Systems, Inc. (DSI). DSI has formally derived and validated PCI bus interfaces and a Java byte-code processor; they further executed a contract to prototype SPIDER-NASA's ultra-reliable communications bus. To date, most derivations from DDD and DRS have targeted hardware due to its synchronous design paradigm. However, Starfish expressions are independent of the synchronization mechanism; there is no commitment to hardware or globally broadcast clocks. Though software back-ends for design derivation are limited to the DDD stream-interpreter, targeting synchronous or real-time software is not substantively different from targeting hardware.

Tsow, Alex↗

Modeling Spacecraft Power Systems Using the SPACE Code

The NASA Glenn Research Center’s Power Architecture and Analysis Branch performs spacecraft electrical power system (EPS) performance analysis using the System Power Analysis for Capability Evaluation (SPACE) model. Accurately predicting EPS performance requires a wide range of inputs, including the spacecraft’s position, attitude, solar array temperature, load demand, and data on the EPS itself. By operating as a combined analysis tool with integrated orbit mechanics, attitude, shadowing, thermal, solar array, battery, and electrical component models, SPACE provides flexibility for the analyst to examine various scenarios without a time-consuming iterative process involving separate analysis tools and groups. SPACE also achieves short run times by tailoring the complexity of the included models, providing enough fidelity to ensure accurate EPS performance predictions without being bogged down by unnecessary detail. These advantages that SPACE has over similar power system models has contributed to its successful use on a variety of human spaceflight programs for over three decades, and makes it applicable across the development cycle from early conceptual design up through on-orbit operations.

Electrical Power System↗

Moving base simulation of an ASTOVL lift-fan aircraft

Using a generalized simulation model, a moving-base simulation of a lift-fan short takeoff/vertical landing fighter aircraft was conducted on the Vertical Motion Simulator at Ames Research Center. Objectives of the experiment were to (1) assess the effects of lift-fan propulsion system design features on aircraft control during transition and vertical flight including integration of lift fan/lift/cruise engine/aerodynamic controls and lift fan/lift/cruise engine dynamic response, (2) evaluate pilot-vehicle interface with the control system and head-up display including control modes for low-speed operational tasks and control mode/display integration, and (3) conduct operational evaluations of this configuration during takeoff, transition, and landing similar to those carried out previously by the Ames team for the mixed-flow, vectored thrust, and augmentor-ejector concepts. Based on results of the simulation, preliminary assessments of acceptable and borderline lift-fan and lift/cruise engine thrust response characteristics were obtained. Maximum pitch, roll, and yaw control power used during transition, hover, and vertical landing were documented. Control and display mode options were assessed for their compatibility with a range of land-based and shipboard operations from takeoff to cruise through transition back to hover and vertical landing. Flying qualities were established for candidate control modes and displays for instrument approaches and vertical landings aboard an LPH assault ship and DD-963 destroyer. Test pilot and engineer teams from the Naval Air Warfare Center, Boeing, Lockheed, McDonnell Douglas, and the British Defence Research Agency participated in the program.

Chung, William W. Y.↗

Human Factors and Habitability Challenges for Mars Missions

As NASA is planning to send humans deeper into space than ever before, adequate crew health and performance will be critical for mission success. Within the NASA Human Research Program (HRP), the Space Human Factors and Habitability (SHFH) team is responsible for characterizing the risks associated with human capabilities and limitations with respect to long-duration spaceflight, and for providing mitigations (e.g., guidelines, technologies, and tools) to promote safe, reliable and productive missions. SHFH research includes three domains: Advanced Environmental Health (AEH), Advanced Food Technology (AFT), and Space Human Factors Engineering (SHFE). The AEH portfolio focuses on understanding the risk of microbial contamination of the spacecraft and on the development of standards for exposure to potential toxins such as chemicals, bacteria, fungus, and lunar/Martian dust. The two risks that the environmental health project focuses on are adverse health effects due to changes in host-microbe interactions, and risks associated with exposure to dust in planetary surface habitats. This portfolio also proposes countermeasures to these risks by making recommendations that relate to requirements for environmental quality, foods, and crew health on spacecraft and space missions. The AFT portfolio focuses on reducing the mass, volume, and waste of the entire integrated food system to be used in exploration missions, and investigating processing methods to extend the shelf life of food items up to five years, while assuring that exploration crews will have nutritious and palatable foods. The portfolio also delivers improvements in both the food itself and the technologies for storing and preparing it. SHFE sponsors research to establish human factors and habitability standards and guidelines in five risk areas, and provides improved design concepts for advanced crew interfaces and habitability systems. These risk areas include: Incompatible vehicle/habitat design, inadequate human-computer interaction, inadequate critical task design, inadequate human-automation/robotic interaction, and performance errors due to training deficiencies. To address the identified research gaps within each risk, SHFH's research plan includes studies in the laboratory, in analogs, and on International Space Station (ISS). In addition to establishing and maintaining the risk-based research portfolio, SHFH is also implementing a qualitative approach to determine how we at NASA evaluate human performance. Via interviews with experts, such as trainers, flight controllers, and flight surgeons, we are collecting the metrics by which they assess human performance, evidence of performance issues, and potential or actual consequences. The Human Performance Data Project will determine what human performance data have been collected in the past at NASA, and what data should be collected in the future in order to complete our knowledgebase and reduce risks related to human factors and habitability.

Whitmore, Mihriban↗