Search NASA⌕ Search

SEARCH · Search NASA

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

Total Quality Management: Analysis, Evaluation and Implementation Within ACRV Project Teams

Total quality management (TQM) is a cooperative form of doing business that relies on the talents of everyone in an organization to continually improve quality and productivity, using teams and an assortment of statistical and measurement tools. The Assured Crew Return Vehicle (ACRV) Project Office was identified as an excellent project in which to demonstrate the applications and benefits of TQM processes. As the ACRV Program moves through its various stages of development, it is vital that effectiveness and efficiency be maintained in order to provide the Space Station Freedom (SSF) crew an affordable, on-time assured return to Earth. A critical factor for the success of the ACRV is attaining the maximum benefit from the resources applied to the program. Through a series of four tutorials on various quality improvement techniques, and numerous one-on-one sessions during the SSF's 10-week term in the project office, results were obtained which are aiding the ACRV Office in implementing a disciplined, ongoing process for generating fundamental decisions and actions that shape and guide the organization. Significant advances were made in improving the processes for two particular groups - the correspondence distribution team and the WATER Test team. Numerous people from across JSC were a part of the various team activities including engineering, man systems, and safety. The work also included significant interaction with the support contractor to the ACRV Project. The results of the improvement activities can be used as models for other organizations desiring to operate under a system of continuous improvement. In particular, they have advanced the ACRV Project Teams further down the path of continuous improvement, in support of a working philosophy of TQM.

Raiman, Laura B.↗

The Role of National Research and Education Networks Providing Connectivity and Advanced Network Services to Virtual Communities in Collaborative R&E Projects. CUDI: The Mexican Case Part 1, , In: ISUM 2015: High Performance Computer Applications

This paper describes the role of National Research and Education Networks (NRENs) and their aim to provide a seamless, large scale, high-speed, low-latency network to accelerate scientific and education discovery for national, regional or global collaborative projects that are dependent on the use of modern high performance distributed computing systems (HPDCS) to process mathematical models, produce new knowledge and drive innovation when resolving complex problems. NRENs have become the mainstream of communication and collaboration to integrate the efforts of large geographically distributed teams of Virtual Communities (VC) that - train, teach and learn-, -create, use and share- knowledge, data, information and communications technology resources (e.g. computer and information systems, middleware, tools, instruments, data sets, repositories, applications and services) building e-infrastructures necessary to meet the collaborative projects’ goals. The paper focuses on the current status of the Mexican NREN: CUDI, its future organization and political support, necessary to provide seamless, large scale, high-speed, low latency and secure national backbone and international links providing connectivity, advanced network services and technical support to VCs and their e-infrastructures in collaborative R&E projects within the country, the LAC region and worldwide.

Computer Science↗

Crowdsourcing, citizen sensing and Sensor Web technologies for public and environmental health surveillance and crisis management: trends, OGC standards and application examples

The PIE Activity Awareness Environment is designed to be an adaptive data triage and decision support tool that allows role and activity based situation awareness through a dynamic, trainable filtering system. This paper discusses the process and methodology involved in the application as well as some of its capabilities. 'Wikification of GIS by the masses' is a phrase-term first coined by Kamel Boulos in 2005, two years earlier than Goodchild's term 'Volunteered Geographic Information'. Six years later (2005-2011), OpenStreetMap and Google Earth (GE) are now full-fledged, crowdsourced 'Wikipedias of the Earth' par excellence, with millions of users contributing their own layers to GE, attaching photos, videos, notes and even 3-D (three dimensional) models to locations in GE. From using Twitter in participatory sensing and bicycle-mounted sensors in pervasive environmental sensing, to creating a 100,000-sensor geo-mashup using Semantic Web technology, to the 3-D visualisation of indoor and outdoor surveillance data in real-time and the development of next-generation, collaborative natural user interfaces that will power the spatially-enabled public health and emergency situation rooms of the future, where sensor data and citizen reports can be triaged and acted upon in real-time by distributed teams of professionals, this paper offers a comprehensive state-of-the-art review of the overlapping domains of the Sensor Web, citizen sensing and 'human-in-the-loop sensing' in the era of the Mobile and Social Web, and the roles these domains can play in environmental and public health surveillance and crisis/disaster informatics. We provide an in-depth review of the key issues and trends in these areas, the challenges faced when reasoning and making decisions with real-time crowdsourced data (such as issues of information overload, 'noise', misinformation, bias and trust), the core technologies and Open Geospatial Consortium (OGC) standards involved (Sensor Web Enablement and Open GeoSMS), as well as a few outstanding project implementation examples from around the world.

59 BASIC BIOLOGICAL SCIENCES↗

2012 Pollution Prevention Summary

Every year, the Pollution Prevention (P2) Program either facilitates or performs activities to reduce pollution, minimize waste, and conserve resources. This document summarizes the P2 efforts performed by the Program and other Laboratory organizations. The P2 Team conducts overarching programmatic support activities to facilitate the implementation and completion of waste minimization and reduction projects. These tasks are summarized in the Pollution Prevention Team Performance section. During Earth Week, the P2 Team publicly recognizes employees and P2 projects performed during the previous fiscal year that have improved the Laboratory’s environmental performance. This year, the P2 Team distributed $10K in monetary awards to more than individuals involved in 55 projects. Further information on the awards is provided in the Pollution Prevention Awards section, detailed project descriptions and cost savings documentation are provided in Appendices A and B, respectively.

Environmental Protection↗

FTP 100: An Ultra-High Speed Data Transfer Service Over Next Generation 100 Gigabit Per Second Network

Data-intensive applications, including high energy and nuclear physics, astrophysics, climate modeling, nano-scale materials science, genomics, and financing, are expected to generate exabytes of data over the coming years, which must be transferred, visualized, and analyzed by geographically distributed teams of users. High-performance network capabilities must be available to these users at the application level in a transparent, virtualized manner. Moreover, the application users must have the capability to move large datasets from local and remote locations across network environments to their home institutions. To solve these challenges, the main goal of our project is to design and evaluate high-performance data transfer software to support various data-intensive applications. First, we have designed a middleware software that provides access to Remote Direct Memory Access (RDMA) functionalities. This middleware integrates network access, memory management and multitasking in its core design. We address a number of issues related to its efficient implementation, for instance, explicit buffer management and memory registration, and parallelization of RDMA operations, which are vital to delivering the benefit of RDMA to the applications. Built on top of this middleware, an implementation and experimental evaluation of the RDMA-based FTP software, RFTP, is described and evaluated. This application has been implemented by our team to exploit the full capabilities of advanced RDMA mechanisms for ultra-high speed bulk data transfer applications on Energy Sciences Network (ESnet). Second, we designed our data transfer software to optimize TCP/IP based data transfer performance such that RFTP can be fully compatible with today’s Internet. Our kernel optimization techniques with Linux system calls sendfile and splice, can reduce data copy cost. In this report, we summarize the technical challenges of our project, the primary software design methods, the major project milestones achieved, as well as the testbed evaluation work and demonstrations during our project life time.

97 MATHEMATICS AND COMPUTING↗

Center for Center for Technology for Advanced Scientific Component Software (TASCS)

A resounding success of the Scientific Discovery through Advanced Computing (SciDAC) program is that high-performance computational science is now universally recognized as a critical aspect of scientific discovery [71], complementing both theoretical and experimental research. As scientific communities prepare to exploit unprecedented computing capabilities of emerging leadership-class machines for multi-model simulations at the extreme scale [72], it is more important than ever to address the technical and social challenges of geographically distributed teams that combine expertise in domain science, applied mathematics, and computer science to build robust and flexible codes that can incorporate changes over time. The Center for Technology for Advanced Scientific Component Software (TASCS)1 tackles these these issues by exploiting component-based software development to facilitate collaborative high-performance scientific computing.

97 MATHEMATICS AND COMPUTING↗

Center for Technology for Advanced Scientific Component Software (TASCS)

A resounding success of the Scientific Discover through Advanced Computing (SciDAC) program is that high-performance computational science is now universally recognized as a critical aspect of scientific discovery, complementing both theoretical and experimental research. As scientific communities prepare to exploit unprecedened computing capabilities of emerging leadership-class machines for multi-model simulations at the extreme scale, it is more important than ever to address the technical and social challenges of geographically distributed teams that combine expertise in domain science, applied mathematics, and computer science to build robust and flexible codes that can incorporate changes over time. The Center for Technology for Advanced Scientific Component Software (TASCS) tackles these issues by exploiting component-based software development to facilitate collaborative high-performance scientific computing.

97 MATHEMATICS AND COMPUTING↗

Center for Technology for Advanced Scientific Component Software (TASCS) Consolidated Progress Report July 2006 - March 2009

A resounding success of the Scientific Discovery through Advanced Computing (SciDAC) program is that high-performance computational science is now universally recognized as a critical aspect of scientific discovery [71], complementing both theoretical and experimental research. As scientific communities prepare to exploit unprecedented computing capabilities of emerging leadership-class machines for multi-model simulations at the extreme scale [72], it is more important than ever to address the technical and social challenges of geographically distributed teams that combine expertise in domain science, applied mathematics, and computer science to build robust and flexible codes that can incorporate changes over time. The Center for Technology for Advanced Scientific Component Software (TASCS) tackles these issues by exploiting component-based software development to facilitate collaborative high-performance scientific computing.

99 GENERAL AND MISCELLANEOUS↗

Aeroassist Technology Planning for Exploration

Now that the International Space Station is undergoing assembly, NASA is strategizing about the next logical exploration strategy for robotic missions and the next destination for humans. NASA's current efforts are in developing technologies that will both aid the robotic exploration strategy and make human flight to other celestial bodies both safe and affordable. One of these enabling technologies for future robotic and human exploration missions is aeroassist. This paper will (1) define aeroassist, (2) explain the benefits and uses of aeroassist, and (3) describe a method, currently used by the NASA Aeroassist Working Group, by which widely geographically distributed teams can assemble, present, use, and archive technology information.

Munk, Michelle M.↗

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↗

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↗

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↗

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↗

SECARB Collect Data via Logging, Testing, and Sampling and Distribute to Project Team

Data collection was conducted from Phase III Project start date with completion of the NEPA review in Spring for 2009, through an intense characterization period during well drilling in the summer of 2009, to the start of injection December 1, 2009. During the early stages of injection, data collection was very intense. With staff onsite on 24 hour shifts until January, 2010. Detailed data collection was completed episodically during 2010, with an high injection rate in a tracer study completed during the spring of 2010, and then a repeat seismic survey with borehole gravity, VSP, cross-well and sonic logging conducted during the fall of 2010. By the report date at the end of 2011, data had been compiled and distributed to the team for analysis.

54 ENVIRONMENTAL SCIENCES↗

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.↗

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↗

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↗

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↗