Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “distributed teams”

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

Investigation Organizer

Contents include the folloving:Overview of the Application; Input Data; Analytical Process; Tool's Output; and Application of the Results of the Analysis.The tool enables the first element through a Web-based application that can be accessed by distributed teams to store and retrieve any type of digital investigation material in a secure environment. The second is accomplished by making the relationships between information explicit through the use of a semantic network-a structure that literally allows an investigator or team to "connect -the-dots." The third element, the significance of the correlated information, is established through causality and consistency tests using a number of different methods embedded within the tool, including fault trees, event sequences, and other accident models. And finally, the evidence gathered and structured within the tool can be directly, electronically archived to preserve the evidence and investigative reasoning.

Panontin, Tina↗
NASA NTRS2006

Science Planning for the NASA Mars Reconnaissance Orbiter Mission

The Mars Reconnaissance Orbiter (MRO), launched on August 12, 2005, carries six science instruments, each with unique requirements for repetitive global monitoring, regional or global survey mapping, and/or targeted observations of Mars. Some prefer nadir-only observations, while other instruments require many off-nadir observations (especially for stereo viewing). Because the operations requirements are often incompatible, an interactive science planning process has been developed. This process is more complex than in some recent NASA Mars missions, but less complex (and more repetitive) than processes used by many large planetary missions. It takes full advantage of MRO's novel onboard processing capabilities, and uses simple electronic interactions between geographically distributed teams. This paper describes the process used during MRO's Primary Science Phase (PSP) to plan both interactive and non-interactive observations of Mars, and what has already been learned in the tests and rehearsals preparing for PSP.

planning↗
NASA NTRS2023

The James Webb Space Telescope Mission: Optical Telescope Element Design, Development, and Performance

The James Webb Space Telescope (JWST) is a large, infrared space telescope that has recently started its science program which will enable breakthroughs in astrophysics and planetary science. Notably, JWST will provide the very first observations of the earliest luminous objects in the universe and start a new era of exoplanet atmospheric characterization. This transformative science is enabled by a 6.6 m telescope that is passively cooled with a 5 layer sunshield. The primary mirror is comprised of 18 controllable, low areal density hexagonal segments, that were aligned and phased relative to each other in orbit using innovative image-based wave front sensing and control algorithms. This revolutionary telescope took more than two decades to develop with a widely distributed team across engineering disciplines. We present an overview of the telescope requirements, architecture, development, superb on-orbit performance, and lessons learned. JWST successfully demonstrates a segmented aperture space telescope and establishes a path to building even larger space telescopes.

Infrared observatories↗
NASA NTRS2011

Characterizing Distributed Concurrent Engineering Teams: A Descriptive Framework for Aerospace Concurrent Engineering Design Teams

As aerospace missions grow larger and more technically complex in the face of ever tighter budgets, it will become increasingly important to use concurrent engineering methods in the development of early conceptual designs because of their ability to facilitate rapid assessments and trades in a cost-efficient manner. To successfully accomplish these complex missions with limited funding, it is also essential to effectively leverage the strengths of individuals and teams across government, industry, academia, and international agencies by increased cooperation between organizations. As a result, the existing concurrent engineering teams will need to increasingly engage in distributed collaborative concurrent design. This paper is an extension of a recent white paper written by the Concurrent Engineering Working Group, which details the unique challenges of distributed collaborative concurrent engineering. This paper includes a short history of aerospace concurrent engineering, and defines the terms 'concurrent', 'collaborative' and 'distributed' in the context of aerospace concurrent engineering. In addition, a model for the levels of complexity of concurrent engineering teams is presented to provide a way to conceptualize information and data flow within these types of teams.

Concept Design↗
NASA NTRS2008

It's a Go

The Electrical Power Distribution Control Team takes on the task of determining power failures throughout the Orbiter. The Displays and Controls Team takes on the task of determining distribution, circuit breakers, and switch failures that might occur on the Orbiter or displays that stop working. This paper will identify the circuit packages I have put together for the D&C group, the redesigning of a Hybrid Driver Controller box, and the web designing the Displays and Controls website for easier access to information which can range from indicators to switches.

Welker, Joshua T.↗
NASA NTRS2006

Implementing Distributed Operations: A Comparison of Two Deep Space Missions

Two very different deep space exploration missions--Mars Exploration Rover and Cassini--have made use of distributed operations for their science teams. In the case of MER, the distributed operations capability was implemented only after the prime mission was completed, as the rovers continued to operate well in excess of their expected mission lifetimes; Cassini, designed for a mission of more than ten years, had planned for distributed operations from its inception. The rapid command turnaround timeline of MER, as well as many of the operations features implemented to support it, have proven to be conducive to distributed operations. These features include: a single science team leader during the tactical operations timeline, highly integrated science and engineering teams, processes and file structures designed to permit multiple team members to work in parallel to deliver sequencing products, web-based spacecraft status and planning reports for team-wide access, and near-elimination of paper products from the operations process. Additionally, MER has benefited from the initial co-location of its entire operations team, and from having a single Principal Investigator, while Cassini operations have had to reconcile multiple science teams distributed from before launch. Cassini has faced greater challenges in implementing effective distributed operations. Because extensive early planning is required to capture science opportunities on its tour and because sequence development takes significantly longer than sequence execution, multiple teams are contributing to multiple sequences concurrently. The complexity of integrating inputs from multiple teams is exacerbated by spacecraft operability issues and resource contention among the teams, each of which has their own Principal Investigator. Finally, much of the technology that MER has exploited to facilitate distributed operations was not available when the Cassini ground system was designed, although later adoption of web-based and telecommunication tools has been critical to the success of Cassini operations.

Cassini Mission↗
NASA NTRS2006

Cassini Distributed Instrument Operations: What We've Learned Since Saturn Orbit Insertion

The Cassini mission to Saturn is complex with 12 science teams conducting distributed operations across the United States and Europe. Each Team includes scientists from around the world who actively participate in operations, including observation design, instrument commanding, downlink processing, and archiving. This represents a change in how JPL complex deep-space missions have been operated. Since Saturn Orbit Insertion (SOI), the Cassini Project has spent 17 months conducting science operations and has gained real-world experience that has tested the assumptions and rationale for this approach. We have learned that many of the expected benefits have been realized, but there were numerous unexpected challenges as well. This paper will discuss the lessons learned from the Cassini Tour experience to date. It will revisit the assumptions and rationale behind the distributed instrument operations design and will describe the results, good and bad, of implementing this method of operations. We will describe how Instrument Teams are structured, their roles and responsibilities, what challenges they faced going into orbital operations (the 'tour') and what creative solutions were proposed when funding limitations and schedule milestones prevented optimum solutions. We will also discuss the problems that have been encountered both on the ground and with the instruments, how these problems and anomalies were overcome, and what was learned along the way about the characteristics of distributed instrument operations.

Cassini↗
NASA NTRS2006

Cassini distributed instrument operations – what we’ve learned since Saturn orbit insertion

The Cassini mission to Saturn is complex with 12 science teams conducting distributed operations across the United States and Europe. Each Team includes scientists from around the world who actively participate in operations, including observation design, instrument commanding, downlink processing, and archiving. This represents a change in how JPL complex deep-space missions have been operated. Since Saturn Orbit Insertion (SOI), the Cassini Project has spent 17 months conducting science operations and has gained realworld experience that has tested the assumptions and rationale for this approach. We have learned that many of the expected benefits have been realized, but there were numerous unexpected challenges as well. This paper will discuss the lessons learned from the Cassini Tour experience to date. It will revisit the assumptions and rationale behind the distributed instrument operations design and will describe the results, good and bad, of implementing this method of operations. We will describe how Instrument Teams are structured, their roles and responsibilities, what challenges they faced going into orbital operations (the “tour”) and what creative solutions were proposed when funding limitations and schedule milestones prevented optimum solutions. We will also discuss the problems that have been encountered both on the ground and with the instruments, how these problems and anomalies were overcome, and what was learned along the way about the characteristics of distributed instrument operations.

Woncik, Pam↗
NASA NTRS2002

Research on Intelligent Synthesis Environment

The ultimate goal of this research project is to develop a methodology for the assessment and continuous improvement of engineering team effectiveness in distributed collaborative environments. This review provides the theoretical foundation upon which subsequent empirical work will be based. Our review of the team performance literature has identified the following 12 conceptually distinct team interaction processes as characteristic of effective teams. 1) Mission Analysis; 2) Resource Distribution; 3) Leadership; 4) Timing; 5) Intra-team Feedback; 6) Motivational Functions; 7) Team Orientation; 8) Communication; 9) Coordination; 10) Mutual Performance Monitoring; 11) Back-up Behaviors; and 12) Cooperation. In addition, this review summarizes how team task characteristics (i.e., task type, task complexity, motivation, and temporal changes), team characteristics (i.e., team structure and team knowledge), and individual team member characteristics (i.e., dispositions and teamwork knowledge, skills, and abilities) affect team interaction processes, determine the relevance of these processes, and influence team performance. The costs and benefits of distributed team collaboration are also considered. The review concludes with a brief discussion of the nature of collaborative team engineering tasks.

Loftin, R. Bowen↗
NASA NTRS2017

Beyond Control Centers

For NASA's Resource Prospector (RP) Lunar Rover Mission, we are moving away from a control center concept, to a fully distributed operation utilizing control nodes, with decision support from anywhere via mobile devices. This operations concept will utilize distributed information systems, notifications, mobile data access, and optimized mobile data display for off-console decision support. We see this concept of operations as a step in the evolution of mission operations from a central control center concept to a mission operations anywhere concept. The RP example is part of a trend, in which mission expertise for design, development and operations is distributed across countries and across the globe. Future spacecraft operations will be most cost efficient and flexible by following this distributed expertise, enabling operations from anywhere. For the RP mission we arrived at the decision to utilize a fully distributed operations team, where everyone operates from their home institution, based on evaluating the following factors: the requirement for physical proximity for near-real time command and control decisions; the cost of distributed control nodes vs. a centralized control center; the impact on training and mission preparation of flying the team to a central location. Physical proximity for operational decisions is seldom required, though certain categories of decisions, such as launch abort, or close coordination for mission or safety-critical near-real-time command and control decisions may benefit from co-location. The cost of facilities and operational infrastructure has not been found to be a driving factor for location in our studies. Mission training and preparation benefit from having all operators train and operate from home institutions.

Operations↗
NASA NTRS2011

Teaching the Next Generation of Scientists and Engineers the NASA Design Process

The Integrated Product Team (IPT) program, led by The University of Alabama in Huntsville (UAH), is a multidisciplinary, multi-university, multi-level program whose goal is to provide opportunities for high school and undergraduate scientists and engineers to translate stakeholder needs and requirements into viable engineering design solutions via a distributed multidisciplinary team environment. The current program supports three projects. The core of the program is the two-semester senior design experience where science, engineering, and liberal arts undergraduate students from UAH, the College of Charleston, Southern University at Baton Rouge, and Ecole Suprieure des Techniques Aronautiques et de Construction Automobile (ESTACA) in Paris, France form multidisciplinary competitive teams to develop system concepts of interest to the local aerospace community. External review boards form to provide guidance and feedback throughout the semester and to ultimately choose a winner from the competing teams. The other two projects, the Innovative Student Project for the Increased Recruitment of Engineering and Science Students (InSPIRESS) Level I and Level II focus exclusively on high school students. InSPIRESS Level I allows high schools to develop a payload to be accommodated on the system being developed by senior design experience teams. InSPIRESS Level II provides local high school students first-hand experience in the senior design experience by allowing them to develop a subsystem or component of the UAH-led system over the two semesters. This program provides a model for NASA centers to engage the local community to become more involved in design projects.

Caruso, Pamela W.↗
NASA NTRS1994

The Virtual Mission Operations Center

Spacecraft management is becoming more human intensive as spacecraft become more complex and as operations costs are growing accordingly. Several automation approaches have been proposed to lower these costs. However, most of these approaches are not flexible enough in the operations processes and levels of automation that they support. This paper presents a concept called the Virtual Mission Operations Center (VMOC) that provides highly flexible support for dynamic spacecraft management processes and automation. In a VMOC, operations personnel can be shared among missions, the operations team can change personnel and their locations, and automation can be added and removed as appropriate. The VMOC employs a form of on-demand supervisory control called management by exception to free operators from having to actively monitor their system. The VMOC extends management by exception, however, so that distributed, dynamic teams can work together. The VMOC uses work-group computing concepts and groupware tools to provide a team infrastructure, and it employs user agents to allow operators to define and control system automation.

Moore, Mike↗
NASA NTRS2008

Framework for the Parametric System Modeling of Space Exploration Architectures

This paper presents a methodology for performing architecture definition and assessment prior to, or during, program formulation that utilizes a centralized, integrated architecture modeling framework operated by a small, core team of general space architects. This framework, known as the Exploration Architecture Model for IN-space and Earth-to-orbit (EXAMINE), enables: 1) a significantly larger fraction of an architecture trade space to be assessed in a given study timeframe; and 2) the complex element-to-element and element-to-system relationships to be quantitatively explored earlier in the design process. Discussion of the methodology advantages and disadvantages with respect to the distributed study team approach typically used within NASA to perform architecture studies is presented along with an overview of EXAMINE s functional components and tools. An example Mars transportation system architecture model is used to demonstrate EXAMINE s capabilities in this paper. However, the framework is generally applicable for exploration architecture modeling with destinations to any celestial body in the solar system.

Komar, David R.↗
NASA NTRS1991

Computer conferencing: Choices and strategies

Computer conferencing permits meeting through the computer while sharing a common file. The primary advantages of computer conferencing are that participants may (1) meet simultaneously or nonsimultaneously, and (2) contribute across geographic distance and time zones. Due to these features, computer conferencing offers a viable meeting option for distributed business teams. Past research and practice is summarized denoting practical uses of computer conferencing as well as types of meeting activities ill suited to the medium. Additionally, effective team strategies are outlined which maximize the benefits of computer conferencing.

Smith, Jill Y.↗
NASA NTRS1995

Link Winds: A visual data analysis system and its application to the atmospheric ozone depletion problem

The Linked Windows Interactive Data System (LinkWinds) is a prototype visual data exploration system resulting from a NASA Jet Propulsion Laboratory (JPL) program of research into the application of graphical methods for rapidly accessing, displaying, and analyzing large multi variate multidisciplinary data sets. Running under UNIX it is an integrated multi-application executing environment using a data-linking paradigm to dynamically interconnect and control multiple windows containing a variety of displays and manipulators. This paradigm, resulting in a system similar to a graphical spreadsheet, is not only a powerful method for organizing large amounts of data for analysis, but leads to a highly intuitive, easy-to-learn user interface. It provides great flexibility in rapidly interacting with large masses of complex data to detect trends, correlations, and anomalies. The system, containing an expanding suite of non-domain-specific applications, provides for the ingestion of a variety of data base formats and hard -copy output of all displays. Remote networked workstations running LinkWinds may be interconnected, providing a multiuser science environment (MUSE) for collaborative data exploration by a distributed science team. The system is being developed in close collaboration with investigators in a variety of science disciplines using both archived and real-time data. It is currently being used to support the Microwave Limb Sounder (MLS) in orbit aboard the Upper Atmosphere Research Satellite (UARS). This paper describes the application of LinkWinds to this data to rapidly detect features, such as the ozone hole configuration, and to analyze correlations between chemical constituents of the atmosphere.

Jacobson, Allan S.↗
NASA NTRS1998

Experimental Internet Environment Software Development

Geographically distributed project teams need an Internet based collaborative work environment or "Intranet." The Virtual Research Center (VRC) is an experimental Intranet server that combines several services such as desktop conferencing, file archives, on-line publishing, and security. Using the World Wide Web (WWW) as a shared space paradigm, the Graphical User Interface (GUI) presents users with images of a lunar colony. Each project has a wing of the colony and each wing has a conference room, library, laboratory, and mail station. In FY95, the VRC development team proved the feasibility of this shared space concept by building a prototype using a Netscape commerce server and several public domain programs. Successful demonstrations of the prototype resulted in approval for a second phase. Phase 2, documented by this report, will produce a seamlessly integrated environment by introducing new technologies such as Java and Adobe Web Links to replace less efficient interface software.

Maddux, Gary A.↗
NASA NTRS2000

Advanced Engineering Environments for Space Transportation System Development

There are significant challenges facing today's launch vehicle industry. Global competition, more complex products, geographically-distributed design teams, demands for lower cost, higher reliability and safer vehicles, and the need to incorporate the latest technologies quicker, all face the developer of a space transportation system. Within NASA, multiple technology development and demonstration projects are underway toward the objectives of safe, reliable, and affordable access to space. New information technologies offer promising opportunities to develop advanced engineering environments to meet these challenges. Significant advances in the state-of-the-art of aerospace engineering practice are envisioned in the areas of engineering design and analytical tools, cost and risk tools, collaborative engineering, and high-fidelity simulations early in the development cycle. At the Marshall Space Flight Center, work has begun on development of an advanced engineering environment specifically to support the design, modeling, and analysis of space transportation systems. This paper will give an overview of the challenges of developing space transportation systems in today's environment and subsequently discuss the advanced engineering environment and its anticipated benefits.

Thomas, L. Dale↗
NASA NTRS2000

BOREAS TF-4 CO2 and CH4 Soil Profile Data from the SSA

The BOReal Ecosystem-Atmosphere Study Tower Flux (BOREAS TF-4) team measured distributions of carbon dioxide (CO2) and methane (CH4) concentrations for the upper 5 m of soil and unsaturated zone at the mature stand, upper 6 m at the 20-year-old stand, and the upper 1 m at the 8-year-old stand and clear cut area at the BOREAS Southern Study Area (SSA) during August 1993 to March 1995. Particle size and carbon content of the unsaturated deposits, precipitation, soil temperature and moisture, carbon and oxygen isotopes of soil CO2, and soil water chemistry are also presented. The data are stored in tabular ASCII files.

Striegl, Robert↗