Search NASA⌕ Search

SEARCH · Search NASA

Results for “process systems engineering”

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 145 records · Page 8

Evaluation of NASA's end-to-end data systems using DSDS+

The Data Systems Dynamic Simulator (DSDS+) is a software tool being developed by the authors to evaluate candidate architectures for NASA's end-to-end data systems. Via modeling and simulation, we are able to quickly predict the performance characteristics of each architecture, to evaluate 'what-if' scenarios, and to perform sensitivity analyses. As such, we are using modeling and simulation to help NASA select the optimal system configuration, and to quantify the performance characteristics of this system prior to its delivery. This paper is divided into the following six sections: (1) The role of modeling and simulation in the systems engineering process. In this section, we briefly describe the different types of results obtained by modeling each phase of the systems engineering life cycle, from concept definition through operations and maintenance; (2) Recent applications of DSDS+. In this section, we describe ongoing applications of DSDS+ in support of the Earth Observing System (EOS), and we present some of the simulation results generated of candidate system designs. So far, we have modeled individual EOS subsystems (e.g. the Solid State Recorders used onboard the spacecraft), and we have also developed an integrated model of the EOS end-to-end data processing and data communications systems (from the payloads onboard to the principle investigator facilities on the ground); (3) Overview of DSDS+. In this section we define what a discrete-event model is, and how it works. The discussion is presented relative to the DSDS+ simulation tool that we have developed, including it's run-time optimization algorithms that enables DSDS+ to execute substantially faster than comparable discrete-event simulation tools; (4) Summary. In this section, we summarize our findings and 'lessons learned' during the development and application of DSDS+ to model NASA's data systems; (5) Further Information; and (6) Acknowledgements.

Rouff, Christopher↗

CanSat Competition: Contributing to the Development of NASA's Vision for Robotic Space Exploration

CanSat is an international student design-build-launch competition organized by the American Astronautical Society (AAS) and American Institute of Aeronautics and Astronautics (AIAA). The competition is also sponsored by the Naval Research Laboratory (NRL) and the National Aeronautics and Space Administration (NASA). The CanSat competition is designed for college, university and high school students wanting to participate in an applicable space-related competition. The objective of the CanSat competition is to complete space exploration missions by designing a specific system for a small sounding rocket payload which will follow and perform to a specific set of rules and guidelines for each year's competition. The competition encompasses a complete life-cycle of one year which includes all phases of design, integration, testing, judging and competition. The mission guidelines are based from space exploration missions and include bonus requirement options which teams may choose to participate in. The fundamental goal of the competition is to educate future engineers and scientists. This is accomplished by students applying systems engineering practices to a development project that incorporates an end-to-end life cycle, from requirements analysis, through preliminary design, integration and testing, an actual flight of the CanSat, and concluding with a post-mission debrief. This is done specifically with space related missions to bring a unique aspect of engineering and design to the competition. The competition has been progressing since its creation in 2005. The competition was originally meant to purely convey the engineering and design process to its participants, but through many experiences the competition has also undergone a learning experience with respect to systems engineering process and design. According

Berman, Joshua↗

The Role of Margin in Link Design and Optimization

Link analysis is a system engineering process in the design, development, and operation of communication systems and networks. Link models that are mathematical abstractions representing the useful signal power and the undesirable noise and attenuation effects (including weather effects if the signal path transverses through the atmosphere) that are integrated into the link budget calculation that provides the estimates of signal power and noise power at the receiver. Then the link margin is applied which attempts to counteract the fluctuations of the signal and noise power to ensure reliable data delivery from transmitter to receiver. (Link margin is dictated by the link margin policy or requirements.) A simple link budgeting approach assumes link parameters to be deterministic values typically adopted a rule-of-thumb policy of 3 dB link margin. This policy works for most S- and X-band links due to their insensitivity to weather effects. But for higher frequency links like Ka-band, Ku-band, and optical communication links, it is unclear if a 3 dB link margin would guarantee link closure. Statistical link analysis that adopted the 2-sigma or 3-sigma link margin incorporates link uncertainties in the sigma calculation. (The Deep Space Network (DSN) link margin policies are 2-sigma for downlink and 3-sigma for uplink.) The link reliability can therefore be quantified statistically even for higher frequency links. However in the current statistical link analysis approach, link reliability is only expressed as the likelihood of exceeding the signal-to-noise ratio (SNR) threshold that corresponds to a given bit-error-rate (BER) or frame-error-rate (FER) requirement. The method does not provide the true BER or FER estimate of the link with margin, or the required signalto-noise ratio (SNR) that would meet the BER or FER requirement in the statistical sense. In this paper, we perform in-depth analysis on the relationship between BER/FER requirement, operating SNR, and coding performance curve, in the case when the channel coherence time of link fluctuation is comparable or larger than the time duration of a codeword. We compute the "true" SNR design point that would meet the BER/FER requirement by taking into account the fluctuation of signal power and noise power at the receiver, and the shape of the coding performance curve. This analysis yields a number of valuable insights on the design choices of coding scheme and link margin for the reliable data delivery of a communication system - space and ground. We illustrate the aforementioned analysis using a number of standard NASA error-correcting codes.

Cheung, K.↗

CLINICAL DECISION SUPPORT: PATH TO FUNCTIONAL REQUIREMENTS

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

clinical decision support↗

Clinical Decision Support: Path to Functional Requirements

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

Clinical decision support↗

Human Systems Integration Relationships Between Deep Space and Deepwater Exploration Challenges

NASA pursuit of human missions Beyond Earth Orbit (BEO) to the moon and eventually Mars will pose many new challenges. These missions are characterized by increased risks to human performance due to stress, fatigue, radiation exposure, and isolation. Fundamental changes in spaceflight operations will be required as well. A very critical part of future missions will be assisting the crew with problem-solving and contingency resolution using next-generation smart spacecraft systems. Human Systems Integration (HSI) must be included as part of the systems engineering process. Gateway1 will serve as part of the proving ground for maturing technology such as autonomous systems and space operations procedures to help meet moon mission goals and prepare humans for missions to Mars. For deep space missions, risk factors affecting humans such as mission duration, distance, and physiological/psychological effects, must be considered. A human is not a simple component but rather a system in a systems-of-systems application-a system influenced by cognitive and biological factors that are difficult to model/analyze. System complexity will demand an integrated approach that requires multiple viewpoints, including the understanding of the astronauts' capabilities and limitations to enhance safety, performance, and satisfaction on the interaction between all system users in a variety of environments to achieve acceptable mission goals and performance. HSI will play a vital role in the development of these future missions. This paper provides a discussion of HSI used at NASA and the critical role human factors engineering will play in the HSI process for future missions along with the challenges. Industries such as oil and gas (O&G) could benefit from the content of this paper to help improve the safety and operations of deepwater/oil and gas exploration activities. NASA engineering and human systems subject-matter expert personnel reviewed challenges reported in space-related environments for long space duration missions and identified similarities with the challenges encountered in deepwater exploration. The researchers noted the space industry's current solutions and proposed a system development view to solve future deepwater exploration challenges using HSI principles. This paper discusses the results of the review.

George Salazar↗

Expanded Guidance for NASA Systems Engineering. Volume 1: Systems Engineering Practices

This document is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the expanded guidance is to increase awareness and consistency across the Agency and advance the practice of SE. This guidance provides perspectives relevant to NASA and data particular to NASA. This expanded guidance should be used as a companion for implementing NPR 7123.1, Systems Engineering Processes and Requirements, the Rev 2 version of SP-6105, and the Center-specific handbooks and directives developed for implementing systems engineering at NASA. It provides a companion reference book for the various systems engineering-related training being offered under NASA's auspices.

Steven R Hirshorn↗

An Agile-Like Approach to Hardware Development: The Ejectable Data Recorder (EDR) for Orion's Ascent Abort 2 (AA-2) Test Flight

On July 2, 2019, the Ascent Abort 2 (AA-2) Flight Test Vehicle was launched from Cape Canaveral, with the goal of demonstrating the performance of Orion’s Launch Abort System (LAS) and collecting data from hundreds of sensors throughout the vehicle. The data collected during this test flight is of paramount importance, as it will be used to certify the Orion vehicle for human spaceflight. Originally, the data was to be downlinked via a single string network of antennas on the LAS, with the associated risk of potential data dropouts, as well as loss of data once the LAS was jettisoned. Thus, additional antennas were added onto the crew module (CM) to support data downlink post-LAS jettison, a buffer rebroadcast capability was added to fill in any gaps in data downlink transmissions, and an ejectable data recorder (EDR) subsystem was added to the CM as a redundant measure to collect all the instrumentation data. The EDR subsystem was added to the project about one year after the project commenced, which significantly reduced the available development time when compared with the other subsystems of the AA-2 Test Flight. The project was further accelerated by six months, around the critical design review gate. Due to the schedule compression challenge and the fact that the EDR subsystem was a backup system and not flight critical, the EDR subsystem was further challenged to find a new and more efficient way to develop hardware. Thus, the EDR subsystem experimented with different management and systems engineering processes, team sizes, communication methods, and tools. Some examples are novel uses of SharePoint as a Data-centric Project Management & Systems Engineering environment, a continuous testing approach through the lifecycle, and a Skunkworks approach to managing the team. The EDR subsystem blended Commercial Off The Shelf (COTS) hardware with in-house developed hardware and software to create a novel data retrieval capability. The capability evolved rapidly through a hardware in the loop simulation environment that enabled incremental component updates for not only the EDR subsystem but across the entire Crew Module. This paper will present an overview of how the EDR subsystem was managed and compare it to an Agile approach to managing projects. The paper will further provide a recommended approach to future Agile-like hardware development that incorporates lessons learned from the EDR experience.

Agile↗

Systems Engineering and Integration for Advanced Life Support System and HST

Systems engineering (SE) discipline has revolutionized the way engineers and managers think about solving issues related to design of complex systems: With continued development of state-of-the-art technologies, systems are becoming more complex and therefore, a systematic approach is essential to control and manage their integrated design and development. This complexity is driven from integration issues. In this case, subsystems must interact with one another in order to achieve integration objectives, and also achieve the overall system's required performance. Systems engineering process addresses these issues at multiple levels. It is a technology and management process dedicated to controlling all aspects of system life cycle to assure integration at all levels. The Advanced Integration Matrix (AIM) project serves as the systems engineering and integration function for the Human Support Technology (HST) program. AIM provides means for integrated test facilities and personnel for performance trade studies, analyses, integrated models, test results, and validated requirements of the integration of HST. The goal of AIM is to address systems-level integration issues for exploration missions. It will use an incremental systems integration approach to yield technologies, baselines for further development, and possible breakthrough concepts in the areas of technological and organizational interfaces, total information flow, system wide controls, technical synergism, mission operations protocols and procedures, and human-machine interfaces.

Kamarani, Ali K.↗

An Altair Overview: Designing a Lunar Lander for 21st Century Human Space Exploration

Altair, the lunar lander element of NASA's Constellation program, was conducted in a different design environment than many other NASA projects of similar scope. Because of this relatively unique approach, there are a number of significant success stories that should be considered during the development of any future lunar landers or human spacecraft. This paper is divided into two separate themes; the first is the approach used during the conceptual design studies, including the systematic analysis cycles and the decision making process associated with each: and the second is a summary of the resulting lessons learned that were compiled after looking back at the lifetime of the Project. Altair was terminated before entering Phase B of its design, and was often criticized for being a very heavy and very large vehicle. While there was specific rationale for all of the decisions that led up to that configuration, future design cycles were specifically planned to re-address the mass challenge. Had the project continued, the deliberate, stepwise design process would have converged on an optimized lander design that balanced mass, risk, cost and capabilities. Some of the specific items that will be addressed in this paper include project development strategy, organizational approach and team dynamics, risk-informed design process, mission architecture constraints, mission key driving requirements, model-based systems engineering process, configuration studies, contingency considerations, subsystem overviews and key trade studies. The paper will conclude with a summary of the lessons identified during the Altair project and make suggestions for application to future studies.

Brown, Kendall K.↗

Methods for Developing Successful Systems Engineers

Systems Engineering (SE) is a complex and challenging field that incorporates the knowledge of systems engineering processes, the ability to synthesize a wide-range of engineering disciplines, and the ability to lead a team of people to successfully accomplish the goals of a project. It requires hard technical skills and soft-skill leadership savvy. As a result, three main development needs are identified: 1) Knowledge of SE processes, the benefits of these processes to a project and their tailored application 2) Knowledge of a wide-range of engineering disciplines, how they interrelate in a system, and the development of sound technical judgement 3) Team leadership to direct and motivate a team of subsystem and discipline experts This paper describes the establishment of a comprehensive training and development program for Systems Engineers at NASA Ames Research Center that addresses in part each of these three areas from the perspective of the implementing manager. A variety of methods have been utilized including the establishment of a SE Community of Practice, a unique and innovative web tool, on-line videos, classroom training in NASA’s 17 Common Technical Processes, guidance on the tailored application of these processes, monthly technical talks, mentoring in both technical judgment and team leadership, and NASA’s Leadership Development Programs. While much of professional SE development must come through project experience, the approaches listed above can accelerate development. The diversity of skills required of Systems Engineering demands a multi-faceted approach to successfully train and develop this critical skill.

development↗

Methods for Developing Successful Systems Engineers

Systems Engineering (SE) is a complex and challenging field that incorporates the knowledge of systems engineering processes, the ability to synthesize a wide-range of engineering disciplines, and the ability to lead a team of people to successfully accomplish the goals of a project. It requires hard technical skills and soft-skill leadership savvy. As a result, three main development needs are identified: 1. Knowledge of SE processes, the benefits of these processes to a project and their tailored application 2. Knowledge of a wide-range of engineering disciplines, how they interrelate in a system, and the development of sound technical judgement 3. Team leadership to direct and motivate a team of subsystem and discipline experts This paper describes the establishment of a comprehensive training and development program for Systems Engineers at NASA Ames Research Center that addresses in part each of these three areas from the perspective of the implementing manager. A variety of methods have been utilized including the establishment of a SE Community of Practice, a unique and innovative web tool, on-line videos, classroom training in NASA’s 17 Common Technical Processes, guidance on the tailored application of these processes, monthly technical talks, mentoring in both technical judgment and team leadership, and NASA’s Leadership Development Programs. While much of professional SE development must come through project experience, the approaches listed above can accelerate development. The diversity of skills required of Systems Engineering demands a multi-faceted approach to successfully train and develop this critical skill.

development↗

Cooperative Research and Development Agreement between National Energy Technology Laboratory and Korea Institute of Energy Research [Abstract]

The Korea Institute of Energy Research (KIER) and the National Energy Technology Laboratory (NETL) intend to collaborate under a CRADA to advance the development of oxy-combustion technology, with an emphasis on process modeling, optimization, and techno-economic analysis. This collaboration will result in the development of a full-scale process model of a commercial oxy-fueled circulating fluid bed combustion (oxy-CFBC) plant, informed from pilot-scale data and built using the Institute for the Design of Advanced Energy Systems (IDAES) process systems engineering framework. It will also generate cost comparisons of the optimized oxyCFBC process with an air-CFBC process with and without carbon capture and sequestration.

20 FOSSIL-FUELED POWER PLANTS↗

Renaissance: A revolutionary approach for providing low-cost ground data systems

The NASA is changing its attention from large missions to a greater number of smaller missions with reduced development schedules and budgets. In relation to this, the Renaissance Mission Operations and Data Systems Directorate systems engineering process is presented. The aim of the Renaissance approach is to improve system performance, reduce cost and schedules and meet specific customer needs. The approach includes: the early involvement of the users to define the mission requirements and system architectures; the streamlining of management processes; the development of a flexible cost estimation capability, and the ability to insert technology. Renaissance-based systems demonstrate significant reuse of commercial off-the-shelf building blocks in an integrated system architecture.

Butler, Madeline J.↗

Opportunities for Process Intensification with Membranes to Promote Circular Economy Development for Critical Minerals

Critical minerals are essential to the future of clean energy, especially energy storage, electric vehicles, and advanced electronics. In this paper, we argue that process systems engineering (PSE) paradigms provide essential frameworks for enhancing the sustainability and efficiency of critical mineral processing pathways. As a concrete example, we review challenges and opportu-nities across material-to-infrastructure scales for process intensification (PI) with membranes. Within critical mineral processing, there is a need to reduce environmental impact, especially con-cerning chemical reagent usage. Feed concentrations and product demand variability require flex-ible, intensified processes. Further, unique feedstocks require unique processes (i.e., no one-size-fits-all recycling or refining system exists). Membrane materials span a vast design space that allows significant optimization. Therefore, there is a need to rapidly identify the best opportunities for membrane implementation, thus informing materials optimization with process and infrastructure scale performance targets. Finally, scale-up must be accelerated and de-risked across the materials-to-process levels to fully realize the opportunity presented by membranes, thereby fostering the development of a circular economy for critical minerals. Tackling these challenges requires integrating efforts across diverse disciplines. We advocate for a holistic molecular-to-systems perspective for fully realizing PI with membranes to address sustainability challenges in critical mineral processing. The opportunities for PI with membranes are excellent applications for emerging research in machine learning, data science, automation, and optimization.

Dougher, Molly↗

Space station functional relationships analysis

A systems engineering process is developed to assist Space Station designers to understand the underlying operational system of the facility so that it can be physically arranged and configured to support crew productivity. The study analyzes the operational system proposed for the Space Station in terms of mission functions, crew activities, and functional relationships in order to develop a quantitative model for evaluation of interior layouts, configuration, and traffic analysis for any Station configuration. Development of the model involved identification of crew functions, required support equipment, criteria of assessing functional relationships, and tools for analyzing functional relationship matrices, as well as analyses of crew transition frequency, sequential dependencies, support equipment requirements, potential for noise interference, need for privacy, and overall compatability of functions. The model can be used for analyzing crew functions for the Initial Operating Capability of the Station and for detecting relationships among these functions. Note: This process (FRA) was used during Phase B design studies to test optional layouts of the Space Station habitat module. The process is now being automated as a computer model for use in layout testing of the Space Station laboratory modules during Phase C.

Tullis, Thomas S.↗

Development of an Accepted Medical Condition List for Exploration Medical Capability Scoping

Future NASA human spaceflight programs are on the verge of moving beyond Low Earth Orbit (LEO) to implement missions in lunar space and ultimately Mars. The mission constraints for these types of missions are expected to be progressively challenging for integration of Human Systems requirements into the vehicle and mission architectures. Mass and volume allocations are expected to become increasingly restrictive at the same time that mission realities will drive an increasing need for crew self-sufficiency in the maintenance and repair of both vehicle systems and human systems. To meet these challenges, a systematic, traceable, and repeatable approach to identifying, defining, and prioritizing medical capabilities is required. To provide a systematic and repeatable approach to defining and prioritizing clinical capabilities for spaceflight medicine, a clear process is required for delivering a list of prioritized medical capabilities to the Systems Engineering process that will delineate the mass, power, volume, and similar needs and the trade space analysis for a given space vehicle and mission architecture.

Rebecca Blue↗