Search NASA⌕ Search

SEARCH · Search NASA

Results for “collaborative 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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2012

Using Collaborative Engineering to Inform Collaboration Engineering

Collaboration is a critical competency for modern organizations as they struggle to compete in an increasingly complex, global environment. A large body of research on collaboration in the workplace focuses both on teams, investigating how groups use teamwork to perform their task work, and on the use of information systems to support team processes ("collaboration engineering"). This research essay presents collaboration from an engineering perspective ("collaborative engineering"). It uses examples from professional and student engineering teams to illustrate key differences in collaborative versus collaboration engineering and investigates how challenges in the former can inform opportunities for the latter.

Collaboration Engineering↗
NASA NTRS2003

Concurrent and Collaborative Engineering Implementation in an R and D Organization

Concurrent Engineering (CE), and Collaborative Engineering (or Collaborative Product Development - CPD) have emerged as new paradigms with significant impact in the development of new products and processes. With documented and substantiated success in the automotive and technology industries CE and, most recently, CPD are being touted as innovative management philosophies for many other business sectors including Research and De- velopment. This paper introduces two independent research initiatives conducted at the NASA Glenn Research Center (GRC) in Cleveland, Ohio investigating the application of CE and CPD in an RdiD environment. Since little research has been conducted in the use of CE and CPD in sectors other than the high mass production manufacturing, the objective of these independent studies is to provide a systematic evaluation of the applicability of these paradigms (concur- rent and collaborative) in a low/no production, service environment, in particular R&D.

DelRosario, Ruben↗
NASA NTRS1999

Aerospace Systems Design in NASA's Collaborative Engineering Environment

Past designs of complex aerospace systems involved an environment consisting of collocated design teams with project managers, technical discipline experts, and other experts (e.g. manufacturing and systems operations). These experts were generally qualified only on the basis of past design experience and typically had access to a limited set of integrated analysis tools. These environments provided less than desirable design fidelity, often lead to the inability of assessing critical programmatic and technical issues (e.g., cost risk, technical impacts), and generally derived a design that was not necessarily optimized across the entire system. The continually changing, modern aerospace industry demands systems design processes that involve the best talent available (no matter where it resides) and access to the best design and analysis tools. A solution to these demands involves a design environment referred to as collaborative engineering. The collaborative engineering environment evolving within the National Aeronautics and Space Administration (NASA) is a capability that enables the Agency's engineering infrastructure to interact and use the best state-of-the-art tools and data across organizational boundaries. Using collaborative engineering, the collocated team is replaced with an interactive team structure where the team members are geographically distributed and the best engineering talent can be applied to the design effort regardless of physical location. In addition, a more efficient, higher quality design product is delivered by bringing together the best engineering talent with more up-to-date design and analysis tools. These tools are focused on interactive, multidisciplinary design and analysis with emphasis on the complete life cycle of the system, and they include nontraditional, integrated tools for life cycle cost estimation and risk assessment. NASA has made substantial progress during the last two years in developing a collaborative engineering environment. NASA is planning to use this collaborative engineering infrastructure to provide better aerospace systems life cycle design and analysis, which includes analytical assessment of the technical and programmatic aspects of a system from "cradle to grave." This paper describes the recent NASA developments in the area of collaborative engineering, the benefits (realized and anticipated) of using the developed capability, and the long-term plans for implementing this capability across the Agency.

Monell, Donald W.↗
NASA NTRS2000

Aerospace Systems Design in NASA's Collaborative Engineering Environment

Past designs of complex aerospace systems involved an environment consisting of collocated design teams with project managers, technical discipline experts, and other experts (e.g., manufacturing and systems operation). These experts were generally qualified only on the basis of past design experience and typically had access to a limited set of integrated analysis tools. These environments provided less than desirable design fidelity, often lead to the inability of assessing critical programmatic and technical issues (e.g., cost, risk, technical impacts), and generally derived a design that was not necessarily optimized across the entire system. The continually changing, modern aerospace industry demands systems design processes that involve the best talent available (no matter where it resides) and access to the the best design and analysis tools. A solution to these demands involves a design environment referred to as collaborative engineering. The collaborative engineering environment evolving within the National Aeronautics and Space Administration (NASA) is a capability that enables the Agency's engineering infrastructure to interact and use the best state-of-the-art tools and data across organizational boundaries. Using collaborative engineering, the collocated team is replaced with an interactive team structure where the team members are geographical distributed and the best engineering talent can be applied to the design effort regardless of physical location. In addition, a more efficient, higher quality design product is delivered by bringing together the best engineering talent with more up-to-date design and analysis tools. These tools are focused on interactive, multidisciplinary design and analysis with emphasis on the complete life cycle of the system, and they include nontraditional, integrated tools for life cycle cost estimation and risk assessment. NASA has made substantial progress during the last two years in developing a collaborative engineering environment. NASA is planning to use this collaborative engineering engineering infrastructure to provide better aerospace systems life cycle design and analysis, which includes analytical assessment of the technical and programmatic aspects of a system from "cradle to grave." This paper describes the recent NASA developments in the area of collaborative engineering, the benefits (realized and anticipated) of using the developed capability, and the long-term plans for implementing this capability across Agency.

Monell, Donald W.↗
NASA NTRS2005

Overview of NASA MSFC IEC Federated Engineering Collaboration Capability

The MSFC IEC federated engineering framework is currently developing a single collaborative engineering framework across independent NASA centers. The federated approach allows NASA centers the ability to maintain diversity and uniqueness, while providing interoperability. These systems are integrated together in a federated framework without compromising individual center capabilities. MSFC IEC's Federation Framework will have a direct affect on how engineering data is managed across the Agency. The approach is directly attributed in response to the Columbia Accident Investigation Board (CAB) finding F7.4-11 which states the Space Shuttle Program has a wealth of data sucked away in multiple databases without a convenient way to integrate and use the data for management, engineering, or safety decisions. IEC s federated capability is further supported by OneNASA recommendation 6 that identifies the need to enhance cross-Agency collaboration by putting in place common engineering and collaborative tools and databases, processes, and knowledge-sharing structures. MSFC's IEC Federated Framework is loosely connected to other engineering applications that can provide users with the integration needed to achieve an Agency view of the entire product definition and development process, while allowing work to be distributed across NASA Centers and contractors. The IEC DDMS federation framework eliminates the need to develop a single, enterprise-wide data model, where the goal of having a common data model shared between NASA centers and contractors is very difficult to achieve.

Moushon, Brian↗
NASA NTRS2011

The MSFC Collaborative Engineering Process for Preliminary Design and Concept Definition Studies

This paper describes a collaborative engineering process developed by the Marshall Space Flight Center's Advanced Concepts Office for performing rapid preliminary design and mission concept definition studies for potential future NASA missions. The process has been developed and demonstrated for a broad range of mission studies including human space exploration missions, space transportation system studies and in-space science missions. The paper will describe the design team structure and specialized analytical tools that have been developed to enable a unique rapid design process. The collaborative engineering process consists of integrated analysis approach for mission definition, vehicle definition and system engineering. The relevance of the collaborative process elements to the standard NASA NPR 7120.1 system engineering process will be demonstrated. The study definition process flow for each study discipline will be will be outlined beginning with the study planning process, followed by definition of ground rules and assumptions, definition of study trades, mission analysis and subsystem analyses leading to a standardized set of mission concept study products. The flexibility of the collaborative engineering design process to accommodate a wide range of study objectives from technology definition and requirements definition to preliminary design studies will be addressed. The paper will also describe the applicability of the collaborative engineering process to include an integrated systems analysis approach for evaluating the functional requirements of evolving system technologies and capabilities needed to meet the needs of future NASA programs.

Mulqueen, Jack↗
NASA NTRS2003

Software for Collaborative Engineering of Launch Rockets

The Rocket Evaluation and Cost Integration for Propulsion and Engineering software enables collaborative computing with automated exchange of information in the design and analysis of launch rockets and other complex systems. RECIPE can interact with and incorporate a variety of programs, including legacy codes, that model aspects of a system from the perspectives of different technological disciplines (e.g., aerodynamics, structures, propulsion, trajectory, aeroheating, controls, and operations) and that are used by different engineers on different computers running different operating systems. RECIPE consists mainly of (1) ISCRM a file-transfer subprogram that makes it possible for legacy codes executed in their original operating systems on their original computers to exchange data and (2) CONES an easy-to-use filewrapper subprogram that enables the integration of legacy codes. RECIPE provides a tightly integrated conceptual framework that emphasizes connectivity among the programs used by the collaborators, linking these programs in a manner that provides some configuration control while facilitating collaborative engineering tradeoff studies, including design to cost studies. In comparison with prior collaborative-engineering schemes, one based on the use of RECIPE enables fewer engineers to do more in less time.

Stanley, Thomas Troy↗
NASA NTRS2004

Collaborative Engineering for Research and Development

Research and development (R&D) organizations are being required to be relevant, to be more application-oriented, and to be partners in the strategic management of the business while meeting the same challenges as the rest of the organization, namely: (1) reduced time to market; (2) reduced cost; (3) improved quality; (4) increased reliability; and (5) increased focus on customer needs. Recent advances in computer technology and the Internet have created a new paradigm of collaborative engineering or collaborative product development (CPD), from which new types of relationships among researchers and their partners have emerged. Research into the applicability and benefits of CPD in a low/no production, R&D, and/or government environment is limited. In addition, the supply chain management (SCM) aspects of these relationships have not been studied. This paper presents research conducted at the NASA Glenn Research Center (GRC) investigating the applicability of CPD and SCM in an R&D organization. The study concentrates on the management and implementation of space research activities at GRC. Results indicate that although the organization is engaged in collaborative relationships that incorporate aspects of SCM, a number of areas, such as development of trust and information sharing merit special attention.

Davis, Jose M.↗
NASA NTRS2004

Human Motion Tracking at Marshall Space Flight Center's Collaborative Engineering Center ANVIL

The installation and use of electromagnetic human motion trackers requires a specially designed and metal-free environment for optimal performance. Such an area is not readily available at the Marshall Space Flight Center Collaborative Engineering Center ANVIL. Our paper details a systems engineering approach to installing and operating Ascension Technologies Ethernet MotionStar tracking system in a sub-optimal environment, used with the JACK human computer model's motion capture capabilities. We also discuss how this system is integrated into the Marshall Space Flight Center's Human Engineering process.

Henderson, Steven J.↗
NASA NTRS1999

Enabling Collaborative Engineering and Science at JPL

We examine the issue of distributed collaboration at the Jet Propulsion Laboratory. With the goals of faster, better, cheaper missions, an efficient, seamless collaboration capabilitity is critical to future JPL space exploration missions.

collaboration↗
NASA NTRS1998

An Example of Concurrent Engineering

The Collaborative Engineering Design and Analysis Room (CEDAR) facility allows on-the- spot design review capability for any project during all phases of development. The required disciplines assemble in this facility to work on any problems (analysis, manufacturing, inspection, etc.) associated with a particular design. A small highly focused team of specialists can meet in this room to better expedite the process of developing a solution to an engineering task within the framework of the constraints that are unique to each discipline. This facility provides the engineering tools and translators to develop a concept within the confines of the room or with remote team members that could access the team's data from other locations. The CEDAR area is envisioned as excellent for failure investigation meetings to be conducted where the computer capabilities can be utilized in conjunction with the Smart Board display to develop failure trees, brainstorm failure modes, and evaluate possible solutions.

Rowe, Sidney↗
NASA NTRS2005

Software Engineering Research/Developer Collaborations in 2004 (C104)

In 2004, six collaborations between software engineering technology providers and NASA software development personnel deployed a total of five software engineering technologies (for references, see Section 7.2) on the NASA projects. The main purposes were to benefit the projects, infuse the technologies if beneficial into NASA, and give feedback to the technology providers to improve the technologies. Each collaboration project produced a final report (for references, see Section 7.1). Section 2 of this report summarizes each project, drawing from the final reports and communications with the software developers and technology providers. Section 3 indicates paths to further infusion of the technologies into NASA practice. Section 4 summarizes some technology transfer lessons learned. Section 6 lists the acronyms used in this report.

Pressburger, Tom↗
NASA NTRS2006

Software Engineering Research/Developer Collaborations in 2005

In CY 2005, three collaborations between software engineering technology providers and NASA software development personnel deployed three software engineering technologies on NASA development projects (a different technology on each project). The main purposes were to benefit the projects, infuse the technologies if beneficial into NASA, and give feedback to the technology providers to improve the technologies. Each collaboration project produced a final report. Section 2 of this report summarizes each project, drawing from the final reports and communications with the software developers and technology providers. Section 3 indicates paths to further infusion of the technologies into NASA practice. Section 4 summarizes some technology transfer lessons learned. Also included is an acronym list.

Pressburger, Tom↗
NASA NTRS2004

Collaborative Product Development in an R&D Environment

Research and development (R&D) organizations are being required to be relevant, to be more application-oriented, and to be partners in the strategic management of the business while meeting the same challenges as the rest of the organization, namely: (1) reduced time to market; (2) reduced cost; (3) improved quality; (4) increased reliability; and (5) increased focus on customer needs. Recent advances in computer technology and the Internet have created a new paradigm of collaborative engineering or collaborative product development (CPD), from which new types of relationships among researchers and their partners have emerged. Research into the applicability and benefits of CPD in a low/no production, R&D, and/or government environment is limited. In addition, the supply chain management (SCM) aspects of these relationships have not been studied. This paper presents research conducted at the NASA Glenn Research Center (GRC) investigating the applicability of CPD and SCM in an R&D organization. The study concentrates on the management and implementation of space research activities at GRC. Results indicate that although the organization is engaged in collaborative relationships that incorporate aspects of SCM, a number of areas, such as development of trust and information sharing merit special attention.

Davis, Jose M.↗
NASA NTRS2001

Team Expo: A State-of-the-Art JSC Advanced Design Team

In concert with the NASA-wide Intelligent Synthesis Environment Program, the Exploration Office at the Johnson Space Center has assembled an Advanced Design Team. The purpose of this team is two-fold. The first is to identify, use, and develop software applications, tools, and design processes that streamline and enhance a collaborative engineering environment. The second is to use this collaborative engineering environment to produce conceptual, system-level-of-detail designs in a relatively short turnaround time, using a standing team of systems and integration experts. This includes running rapid trade studies on varying mission architectures, as well as producing vehicle and/or subsystem designs. The standing core team is made up of experts from all of the relevant engineering divisions (e.g. Power, Thermal, Structures, etc.) as well as representatives from Risk and Safety, Mission Operations, and Crew Life Sciences among others. The Team works together during 2- hour sessions in the same specially enhanced room to ensure real-time integration/identification of cross-disciplinary issues and solutions. All subsystem designs are collectively reviewed and approved during these same sessions. In addition there is an Information sub-team that captures and formats all data and makes it accessible for use by the following day. The result is Team Expo: an Advanced Design Team that is leading the change from a philosophy of "over the fence" design to one of collaborative engineering that pushes the envelope to achieve the next-generation analysis and design environment.

Tripathi, Abhishek↗