Search NASA⌕ Search

SEARCH · Search NASA

Results for “CONCURRENT”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS2004

Concurrent Engineering for the Management of Research and Development

The Management of Research and Development (R&D) is facing the challenges of reducing time from R&D to customer, reducing the cost of R&D, having higher accountability for results (improved quality), and increasing focus on customers. Concurrent engineering (CE) has shown great success in the automotive and technology industries resulting in significant decreases in cycle time, reduction of total cost, and increases in quality and reliability. This philosophy of concurrency can have similar implications or benefits for the management of R&D organizations. Since most studies on the application of CE have been performed in manufacturing environments, research into the benefits of CE into other environments is needed. This paper presents research conducted at the NASA Glenn Research Center (GRC) investigating the application of CE in the management of an R&D organization. In particular the paper emphasizes possible barriers and enhancers that this environment presents to the successful implementation of CE. Preliminary results and recommendations are based on a series of interviews and subsequent surveys, from which data has been gathered and analyzed as part of the GRC's Continuous Improvement Process.

DelRosario, Ruben↗
NASA NTRS2010

GLobal Integrated Design Environment (GLIDE): A Concurrent Engineering Application

The GLobal Integrated Design Environment (GLIDE) is a client-server software application purpose-built to mitigate issues associated with real time data sharing in concurrent engineering environments and to facilitate discipline-to-discipline interaction between multiple engineers and researchers. GLIDE is implemented in multiple programming languages utilizing standardized web protocols to enable secure parameter data sharing between engineers and researchers across the Internet in closed and/or widely distributed working environments. A well defined, HyperText Transfer Protocol (HTTP) based Application Programming Interface (API) to the GLIDE client/server environment enables users to interact with GLIDE, and each other, within common and familiar tools. One such common tool, Microsoft Excel (Microsoft Corporation), paired with its add-in API for GLIDE, is discussed in this paper. The top-level examples given demonstrate how this interface improves the efficiency of the design process of a concurrent engineering study while reducing potential errors associated with manually sharing information between study participants.

McGuire, Melissa L.↗
NASA NTRS2012

Concurrent Mission and Systems Design at NASA Glenn Research Center: The Origins of the COMPASS Team

Established at the NASA Glenn Research Center (GRC) in 2006 to meet the need for rapid mission analysis and multi-disciplinary systems design for in-space and human missions, the Collaborative Modeling for Parametric Assessment of Space Systems (COMPASS) team is a multidisciplinary, concurrent engineering group whose primary purpose is to perform integrated systems analysis, but it is also capable of designing any system that involves one or more of the disciplines present in the team. The authors were involved in the development of the COMPASS team and its design process, and are continuously making refinements and enhancements. The team was unofficially started in the early 2000s as part of the distributed team known as Team JIMO (Jupiter Icy Moons Orbiter) in support of the multi-center collaborative JIMO spacecraft design during Project Prometheus. This paper documents the origins of a concurrent mission and systems design team at GRC and how it evolved into the COMPASS team, including defining the process, gathering the team and tools, building the facility, and performing studies.

McGuire, Melissa L.↗
NASA NTRS2012

Resource Management and Contingencies in Aerospace Concurrent Engineering

significant concern in designing complex systems implementing new technologies is that while knowledge about the system is acquired incrementally, substantial financial commitments, even make-or-break decisions, must be made upfront, essentially in the unknown. One practice that helps in dealing with this dichotomy is the smart embedding of contingencies and margins in the design to serve as buffers against surprises. This issue presents itself in full force in the aerospace industry, where unprecedented systems are formulated and committed to as a matter of routine. As more and more aerospace mission concepts are generated by concurrent design laboratories, it is imperative that such laboratories apply well thought-out contingency and margin structures to their designs. The first part of this publication provides an overview of resource management techniques and standards used in the aerospace industry. That is followed by a thought provoking treatise on margin policies. The expose presents the actual flight telemetry data recorded by the thermal discipline during several recent NASA Goddard Space Flight Center missions. The margins actually achieved in flight are compared against pre-flight predictions, and the appropriateness and the ramifications of having designed with rigid margins to bounding stacked worst case conditions are assessed. The second half of the paper examines the particular issues associated with the application of contingencies and margins in the concurrent engineering environment. In closure, a discipline-by-discipline disclosure of the contingency and margin policies in use at the Integrated Design Center at NASA s Goddard Space Flight Center is made.

Karpati, Gabe↗
NASA NTRS2012

Flammability Aspects of a Cotton-Fiberglass Fabric in Opposed and Concurrent Airflow in Microgravity

Microgravity combustion tests burning fabric samples were performed aboard the International Space Station. The cotton-fiberglass blend samples were mounted inside a small wind tunnel which could impose air flow speeds up to 40 cm/s. The wind tunnel was installed in the Microgravity Science Glovebox which supplied power, imaging, and a level of containment. The effects of air flow speed on flame appearance, flame growth, and spread rates were determined in both the opposed and concurrent flow configuration. For the opposed flow configuration, the flame quickly reached steady spread for each flow speed, and the spread rate was fastest at an intermediate value of flow speed. These tests show the enhanced flammability in microgravity for this geometry, since, in normal gravity air, a flame self-extinguishes in the opposed flow geometry (downward flame spread). In the concurrent flow configuration, flame size grew with time during the tests. A limiting length and steady spread rate were obtained only in low flow speeds ( 10 cm/s) for the short-length samples that fit in the small wind tunnel. For these conditions, flame spread rate increased linearly with increasing flow. This is the first time that detailed transient flame growth data was obtained in purely forced flows in microgravity. In addition, by decreasing flow speed to a very low value (around 1 cm/s), quenching extinction was observed. The valuable results from these long-duration experiments validate a number of theoretical predictions and also provide the data for a transient flame growth model under development.

Ferkul, Paul V.↗
NASA NTRS2010

Risk Identification and Visualization in a Concurrent Engineering Team Environment

Incorporating risk assessment into the dynamic environment of a concurrent engineering team requires rapid response and adaptation. Generating consistent risk lists with inputs from all the relevant subsystems and presenting the results clearly to the stakeholders in a concurrent engineering environment is difficult because of the speed with which decisions are made. In this paper we describe the various approaches and techniques that have been explored for the point designs of JPL's Team X and the Trade Space Studies of the Rapid Mission Architecture Team. The paper will also focus on the issues of the misuse of categorical and ordinal data that keep arising within current engineering risk approaches and also in the applied risk literature.

Risk Scoring↗
NASA NTRS2013

Domain-Specific Languages and Diagram Customization for a Concurrent Engineering Environment

A major open question for advocates of Model-Based Systems Engineering (MBSE) is the question of how system and subsystem engineers will work together. The Systems Modeling Language (SysML), like any language intended for a large audience, is in tension between the desires for simplicity and for expressiveness. In order to be more expressive, many specialized language elements may be introduced, which will unfortunately make a complete understanding of the language a more daunting task. While this may be acceptable for systems modelers, it will increase the challenge of including subsystem engineers in the modeling effort. One possible answer to this situation is the use of Domain-Specific Languages (DSL), which are fully supported by the Unified Modeling Language (UML). SysML is in fact a DSL for systems engineering. The expressive power of a DSL can be enhanced through the use of diagram customization. Various domains have already developed their own schematic vocabularies. Within the space engineering community, two excellent examples are the propulsion and telecommunication subsystems. A return to simple box-and-line diagrams (e.g., the SysML Internal Block Diagram) are in many ways a step backward. In order allow subsystem engineers to contribute directly to the model, it is necessary to make a system modeling tool at least approximate in accessibility to drawing tools like Microsoft PowerPoint and Visio. The challenge is made more extreme in a concurrent engineering environment, where designs must often be drafted in an hour or two. In the case of the Jet Propulsion Laboratory's Team X concurrent design team, a subsystem is specified using a combination of PowerPoint for drawing and Excel for calculation. A pilot has been undertaken in order to meld the drawing portion and the production of master equipment lists (MELs) via a SysML authoring tool, MagicDraw. Team X currently interacts with its customers in a process of sharing presentations. There are several inefficiencies that arise from this situation. The first is that a customer team must wait two weeks to a month (which is 2-4 times the duration of most Team X studies themselves) for a finalized, detailed design description. Another is that this information must be re-entered by hand into the set of engineering artifacts and design tools that the mission concept team uses after a study is complete. Further, there is no persistent connection to Team X or institutionally shared formulation design tools and data after a given study, again reducing the direct reuse of designs created in a Team X study. This paper presents the underpinnings of subsystem DSLs as they were developed for this pilot. This includes specialized semantics for different domains as well as the process by which major categories of objects were derived in support of defining the DSLs. The feedback given to us by the domain experts on usability, along with a pilot study with the partial inclusion of these tools is also discussed.

Cole, Bjorn↗
NASA NTRS2015

Model-Based Systems Engineering in Concurrent Engineering Centers

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a narrow design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

Iwata, Curtis↗
NASA NTRS2016

JPL's Foundry Furnace: Web-Based Concurrent Engineering for Formulation

The Jet Propulsion Laboratory’s Innovation Foundry is an enterprise tasked with shepherding space mission concepts through the formulation lifecycle. It oversees a number of “virtual teams” for the various stages of formulation. Among these is Team X, which has had considerable success over its more than 20-year history. In a Team X study, domain experts (including engineers devoted to the various spacecraft subsystems) work concurrently and collaboratively over several days to arrive at a feasible point design with a reasonable cost estimate. They use a set of linked Excel workbooks, each developed and approved by a responsible “line organization” within JPL. This toolset has served Team X well over the years, and has evolved since its inception. At the same time, the Innovation Foundry’s portfolio of formulation teams has expanded, and so has the scope of the design challenges they face. The A-Team runs workshop-like architecture studies to focus science investigations, generate mission concepts, assess feasibility, and explore trade spaces. Team Xc performs rapid point design in the style of Team X, but for CubeSats and small spacecraft, using a different toolset. Proposal teams further mature concepts to the point where they can be proposed. Recognizing the importance of trade space modeling combined with new IT services for providing and integrating data, JPL is developing the Foundry Furnace web-based software infrastructure. It will support A-Team, Team Xc, and Team X, providing study management, a catalog of hardware components, a library of re-usable analyses, and a design environment. It is a modernization of JPL’s concurrent engineering infrastructure, embracing the core concepts of Model-Based Systems Engineering, and built with modern software design philosophies.

Murphy, Jonathan↗
NASA NTRS2019

Land–Atmosphere Feedbacks Exacerbate Concurrent Soil Drought and Atmospheric Aridity

Compound extremes such as cooccurring soil drought (low soil moisture) and atmospheric aridity (high vapor pressure deficit) can be disastrous for natural and societal systems. Soil drought and atmospheric aridity are 2 main physiological stressors driving widespread vegetation mortality and reduced terrestrial carbon uptake. Here, we empirically demonstrate that strong negative coupling between soil moisture and vapor pressure deficit occurs globally, indicating high probability of cooccurring soil drought and atmospheric aridity. Using the Global Land Atmosphere Coupling Experiment (GLACE)-CMIP5 experiment, we further show that concurrent soil drought and atmospheric aridity are greatly exacerbated by land– atmosphere feedbacks. The feedback of soil drought on the atmosphere is largely responsible for enabling atmospheric aridity extremes. In addition, the soil moisture–precipitation feedback acts to amplify precipitation and soil moisture deficits in most regions. CMIP5 models further show that the frequency of concurrent soil drought and atmospheric aridity enhanced by land–atmosphere feedbacks is projected to increase in the 21st century. Importantly, land– atmosphere feedbacks will greatly increase the intensity of both soil drought and atmospheric aridity beyond that expected from changes in mean climate alone.

Compound extreme events↗
NASA NTRS2018

How Do You Go From a Concept Idea to a NASA Selected Mission? Formulating the Psyche Discovery Mission with JPL's Concurrent Engineering Teams

JPL’s Office of Formulation provides continuity of support and access to domain subject matter experts, as Principal Investigators mature their mission concepts from “cocktail napkin” ideas to Preliminary Design Reviews [1]. Using NASA’s Psyche mission as a case study, we describe JPL’s concurrent engineering A-Team and Team X support to the Psyche competed concept study team in the areas of 1) Initial Feasibility, 2) Trade Space Exploration, 3) Spacecraft Point Design and Cost Estimate, 4) Science, Technical, Management, and Cost Review, and 5) Strategy and Communication Development. NASA’s Psyche Discovery-class mission started as a grassroots idea from Principal Investigator L.T. ElkinsTanton. Is there a compelling Discovery mission to visit the interior of a body for the first time, by sending a mission to an iron metal asteroid? In less than five years the Psyche concept was selected as a mission under NASA’s Discovery Program. While Psyche had a dedicated concept development team [2], they utilized JPL’s concurrent engineering teams, methods, analysis tools, and subject matter experts throughout their mission concept formulation lifecycle

Ziemer, John↗
NASA NTRS2018

How Do You Go From a Concept Idea to a NASA Selected Mission? Formulating the Psyche Discovery Mission with JPL's Concurrent Engineering Teams

JPL’s Office of Formulation provides continuity of support and access to domain subject matter experts, as Principal Investigators mature their mission concepts from “cocktail napkin” ideas to Preliminary Design Reviews [1]. Using NASA’s Psyche mission as a case study, we will describe JPL’s concurrent engineering ATeam and Team X support to the Psyche competed concept study team in the areas of 1) Science Feasibility, 2) Trade Space Exploration, 3) Spacecraft Point Design and Cost Estimate, 4) Science, Technical, Management, and Cost Review, and 5) Strategy and Communication Development. NASA’s Psyche Discovery class mission started as a grassroots idea in our A-Team facility, and in less than five years was selected as a mission under NASA’s Discovery Program. While Psyche had a dedicated concept development team [2], they utilized JPL’s concurrent engineering teams, methods, analysis tools, and experts throughout their mission concept lifecycle.

Ziemer, John↗
NASA NTRS2021

Lessons Learned in Remote Participant Concurrent Engineering Concept Development Studies

Team-X was born from a need to perform rapid space mission design for principal investigator-led competed proposals in the mid-1990s. Throughout the last 25 years, Team-X at the Jet Propulsion Laboratory has expanded its application of the collaborative, concurrent study approach into every facet necessary to win competed proposals. The COVID-19 pandemic of 2020 created an immediate and new constraint on these studies – the need to conduct them with remote participants, both on the client side requesting the study, but also on the provider side producing the study. This paper provides lessons learned from dozens of design studies run by Team-X at the Jet Propulsion Laboratory during the COVID-19 pandemic. These lessons span all aspects of the information infrastructure: the people, processes, procedures, methods, tools, and “facilities”. These lessons learned will have applicability post-pandemic, as they have shown how best to incorporate participants, both on the provider side, and on the client side, who cannot travel or otherwise be co-located during collaborative, concurrent study sessions.

Nash, Alfred↗
NASA NTRS1996

An Element-Based Concurrent Partitioner for Unstructured Finite Element Meshes

A concurrent partitioner for partitioning unstructured finite element meshes on distributed memory architectures is developed. The partitioner uses an element-based partitioning strategy. Its main advantage over the more conventional node-based partitioning strategy is its modular programming approach to the development of parallel applications. The partitioner first partitions element centroids using a recursive inertial bisection algorithm. Elements and nodes then migrate according to the partitioned centroids, using a data request communication template for unpredictable incoming messages. Our scalable implementation is contrasted to a non-scalable implementation which is a straightforward parallelization of a sequential partitioner.

concurrent partitioner finite element meshes distr↗
NASA NTRS2006

Next-generation concurrent engineering: developing models to complement point designs

Concurrent Engineering Design teams have made routine the rapid development of point designs for space missions. The Jet Propulsion Laboratory's Team X is now evolving into a next generation CED; nin addition to a point design, the team develops a model of the local trade space. The process is a balance between the power of model-developing tools and the creativity of human experts, enabling the development of a variety of trade models for any space mission.

trade space exploration↗
NASA NTRS2006

Next-generation concurrent engineering: developing models to complement point designs

Concurrent Engineering Design (CED) teams have made routine the rapid development of point designs for space missions. The Jet Propulsion Laboratory's Team X is now evolving into a 'next-generation CED; in addition to a point design, the Team develops a model of the local trade space. The process is a balance between the power of a model developing tools and the creativity of humal experts, enabling the development of a variety of trade models for any space mission. This paper reviews the modeling method and its practical implementation in the ED environment. Example results illustrate the benefit of this approach.

concurrent engineering↗
NASA NTRS2007

Visualization of Concurrent Program Executions

Various program analysis techniques are efficient at discovering failures and properties. However, it is often difficult to evaluate results, such as program traces. This calls for abstraction and visualization tools. We propose an approach based on UML sequence diagrams, addressing shortcomings of such diagrams for concurrency. The resulting visualization is expressive and provides all the necessary information at a glance.

concurrent programs↗