Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “collaborative”

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 775 records · Page 43

The TechEdSat-N Series: A Collaborative Technology Development Platform in the Nano-Satellite Form Factor

The TechEdSat-1 (TES-1) was the first U.S. CubeSat to be deployed from the ISS (International Space Station). This permitted the initiation of a flight series that has recently de-orbited the 6th nano-satellite with subsequent numbers 7-10 under development. The nano-satellites range from 1U (1 unit) to 6U (TechEdSat-8) but have the critical ISS Safety design features standardized in order to focus on the particular experiment objectives. Incremental experimental development has included unique communication subsystems such as command/control of the nanosatellite through email commands -as well as a recent record for Wifi transmission. Also, the thermophysics of controlled drag devices (Exo-Brake) has been developed which will prelude sample return and planetary exploration applications. The successful "rapid incremental experiment" approach has also been incorporated into collaborations with academia, permitting professors/student interns to be exposed to the rigors of space mission hardware design and execution. The TechEdSat-8, a linear 6U configuration, allows for 5 different groups to contribute an "experiment, sensor, or sub-system" through a well-defined common interface. Lastly, the flying laboratory concept is helpful in developing future interplanetary nano-satellite subsystems which will advance exploration goals by allowing rapid demonstration/validation first in LEO (Low Earth Orbit).

Small Payload Quick Return↗

ISEP: A Joint SRAG/CCMC Collaboration to Improve Mitigation of Space Weather Effects on Crew Health in the Exo-LEO Era

The Space Radiation Analysis Group (SRAG) at Johnson Space Center (JSC) is tasked with monitoring changes to space weather and mitigating any resultant impacts to crew health and safety. As human spaceflight goals extend from Low-Earth Orbit (LEO) missions like the International Space Station (ISS) to the moon, Mars and beyond, SRAG will need to update their current approach for crew monitoring of and protection from radiation exposure due to energetic Solar Particle Events (ESPEs). Challenges faced in planning exo-LEO missions include the lack of protection from the Earth’s geomagnetic field employed by the ISS in addition to limited communication capability between the crew and the ground. In the event of an ESPE, the current ISS trajectory ensures that the vehicle is only traveling through fields of higher radiation exposure for a brief period of time; the Earth’s geomagnetic field prevents the penetration of the high-energy particles of concern throughout the majority of the orbit. Exo-LEO missions, on the other hand, require that the vehicle travel through free space, exposing vehicle and crew to the full impact of the ESPE. NASA has combined multiple approaches to resolve this radiation exposure issue. New vehicles are designed to take advantage of advances in particle transport modeling capabilities and shielding technology, allowing redistribution of mass throughout the vehicle to areas of thinner shielding when the energetic particle flux has increased to levels of concern. Although vehicle shielding is an important aspect of radiation exposure protection, there is a continued requirement to monitor and predict the space weather environment. To this end, SRAG maintains a console position in Mission Control with 24/7 mission support capability. In the event of increased solar activity, SRAG collaborates with the Flight Control Team (FCT) to determine if crew action (i.e., shelter) is required. During any increase in solar activity, the FCT needs three pieces of information to effectively decide the crew response in light of other required mission tasks: if an event (ESPE) will occur, how ‘intense’ an observed event will be, and how long will an observed event will last. An ideal alert system limits false alarms, therefore causing the crew to take action unnecessarily, without ignoring events that pose a hazard to the crew. SRAG’s current operational concept for ISS missions focuses on short-term forecasts, best described as ‘now-casting’. Console operators are in daily communication with the Space Weather Prediction Center (SWPC) for situational awareness purposes. When conditions exist that may lead to increased solar activity, operators receive notifications from SWPC. In the case of a well-connected ESPE, the console operator may only have on the order of minutes to several hours to notify the FCT of the event and provide a recommendation for crew action. As NASA shifts to exo-LEO missions, the increased time in free space as well as the reduced ability to communicate with the crew will force a transition in crew protection strategy that emphasizes improvments to both the accuracy and the lead time in forecasting capabilities.

Barzilla, Janet E.↗

Flight Awareness Collaboration Tool Quick Start Guide

The Flight Awareness Collaboration Tool (FACT) is a web-based software tool that provides important information about winter weather operations to airline dispatchers and airport personnel. This document provides instructions on how to operate FACT. It reviews FACT goals, features, functions, controls, and data displays. The manual uses text and screen shots of the screens to guide new users on how to access FACT features. This manual is required for FACT distribution to airlines and airports and is needed as part of the NASA patent process.

winter weather↗

UAS Integration in the NAS Detect and Avoid Subproject: Kitty Hawk - NASA Collaboration Discussion

NASA is conducting research under the UAS Integration in the NAS Project to develop standards that will enable mid-size and large unmanned aircraft to fly unrestricted in the National Airspace System. As these efforts move into its second phase, NASA is planning a series of flight tests and demonstrations, integrating industry partners' technologies. These events will not only provide valuable data to inform the RTCA Special Committee 228 DAA and C2 MOPS, but also provide an opportunity for the UAS community to test their technologies in a realistic environment. An overview of NASA UAS-NAS research will be presented touching on human systems integration, modeling and simulation and guidance and control. Plans for Flight Test 6 and Systems Integration Operationalization (SIO) will also be presented. The purpose of this meeting is to share with Kitty Hawk, at a high level, UAS-NAS research and discuss potential future collaboration between NASA and Kitty Hawk.

Shively, Jay↗

Orion Ascent Abort 2 Test - Benefits of a Digital Collaboration Environment

The Ascent Abort-2 Crew Module and Separation Ring (CSR) were developed internally to NASA, led by the JSC EA Integrated Product Team. The CSR IPT leveraged Sharepoint as an Integrated Data environment to link systems engineering and project management data element, enabling collaborative development and engagement from across the project (NASA-wide). This presentation describes the mission, the development approach, and the benefits of this approach. flight operations

Devolites, Jenny↗

The Cumulus Ecosystem: Open Source and Beyond to Foster Collaboration

NASA’s Earth Observing System Data and Information System (EOSDIS) open source Cumulus software is designed as a common set of code and services that can be used to create a pipeline to deliver and manage earth science data in the cloud. Cumulus strives to create an ecosystem on the foundation of open source that unites those with shared problems and goals by encouraging users to contribute solutions back to the platform. Large parts of ingesting and managing data are common and much of what is created can be used by others. Our goal is to maximize collaboration and code reuse while allowing users to design a custom solution that meets their needs without having to take on extraneous functionality. In this talk we will describe how the Cumulus ecosystem works beyond just open source software. We will review the technology, the successes and challenges, and the evolution and future of Cumulus as an ecosystem.

Cumulus↗

An “EPIIC” Vision to Evolve Project Integration, Innovation, and Collaboration with Broad Impact for How NASA Executes Complex Projects

Evolving Project Integration, Innovation, and Collaboration (EPIIC) is a vision defined to transform the way projects manage information to support real-time decisions, capture best practices and lessons learned, perform assessments, and manage risk across a portfolio of projects. The foundational project management needs for data and information will be revolutionized through innovations on how we manage and access that data, implement configuration control, and certify compliance. The embedded intelligence of new interactive data interfaces integrate technical and programmatic data such that near real time analytics can be accomplished to more efficiently and accurately complete systems engineering and project management tasks. The system-wide data analytics that are integrated into customized data interfaces allows the growing team of engineers and managers required to develop and implement major NASA missions the ability to access authoritative source(s) of system information while greatly reducing the labor required to complete system assessments. This would allow, for example, much of what is accomplished in a scheduled design review to take place as needed, between any team members, at any time. An intelligent data interface that rigorously integrates systems engineering and project management information in near real time can provide substantially greater insight for systems engineers, project managers, and the large diverse teams required to complete a complex project. System engineers, programmatic personnel (those who focus on cost, schedule, and risk), the technical engineering disciplines, and project management can realize immediate benefit from the shared vision described herein. Implementation of the vision also enables significant improvements in the performance of the engineered system being developed.

Moreland, Robert J.↗

DAAC Collaboration Overview for AGU

The Atmospheric Science Data Center (ASDC), Goddard Earth Sciences Data and Information Systems Center (GES DISC), Socioeconomic Data and Applications Center (SEDAC), Oak Ridge National Laboratory (ORNL), Land Processes DAAC, Alaska Satellite Facility (ASF), as well as NASA Global Imagery Browse Service (GIBS), Earth Science Data Systems (ESDS) Geographic Information Systems Team (EGIST), Earthdata Content Delivery Team, ArcGIS Online Governance Team, and the Systematic Data Transformation ACCESS team have come together to establish the ArcGIS DAAC Collaboration. This coalition of participants will demonstrate their use of the ArcGIS Enterprise to support Earth science research, applied science, and outreach using Earth Observing System Data and Information System (EOSDIS) data. This includes the use of web services to fuse data products across space and time through services (e.g. ArcGIS Image Services, Open Geospatial Consortium (OGC) Web Coverage Service (WCS), and OGC Web Mapping Services (WMS)) for analysis in Jupyter notebooks, desktop tools, and web based applications.

Matthew Steven Tisdale↗

Cloud Software Enables Collaborative, Real-Time Procedures for NASA and Others

TRACLabs’ PRIDE software was the first collaborative and highly-customizable tool designed to allow astronauts to document and mark progress on procedures in real-time, display system data, and issue commands—all from a single application. The versatility of the software caught the eye of a major oil field service company, who bought licenses and support from TRACLabs for $3.3M

William Douglas Goodman↗

M:N Operations NASA/Uber Collaboration

In this presentation, current approaches to enable multiple-operator, multiple vehicle (M:N) operations are reviewed together with recent collaborative efforts between NASA and Uber. Topics include a review of human-automation teaming (HAT) concepts, including plays and working agreements, and a particular task-allocation method called Automation Level-based Task Allocation (ALTA). Following introductory material on HAT, an overview of a recent (July 2020) cognitive walkthrough study of M:N operations in the context of a food delivery via small-Unmanned Aircraft Systems application is provided. Initial results from this cognitive walkthrough detailing operator feedback on displays, operator and supervisor roles and responsibilities, and the overall concept of operation are reviewed. The presentation concludes with a description of a future, human-in-the-loop simulation experiment of M:N operations in a high-fidelity environment, which will examine the effects of high workload and assistive automation/tools on operator performance.

human-automation teaming↗

NASA and Blue Origin Collaborative Assessment of Precision Landing Algorithms and Computing

NASA’s Safe and Precise Landing Integrated Capabilities Evolution (SPLICE) project is developing sensor, algorithm, and compute technologies for precision landing and hazard avoidance. These technologies are being tested as an integrated Precision Landing and Hazard Avoidance (PL&HA) system on Blue Origin’s New Shephard suborbital vehicle. A key goal for the computing element of this technology development is to characterize the performance of the SPLICE software workloads on the project’s Descent and Landing Computer (DLC). The DLC is a multi-core processor designed as a surrogate for NASA’s High-Performance Space Computer (HPSC). Measurements of the SPLICE workload performance on the DLC provides NASA insight on how PL&HA capabilities will perform on the HPSC, and guidance on how the SPLICE algorithms can be implemented to best utilize the DLC platform. This insight can also be used to derive requirements to guide trade studies on candidate computing architectures, for use on platforms like Blue Moon. NASA and Blue Origin are collaborating under an agreement to pursue this mutual benefit. Performance metrics collected are based on measurement of common compute resources such as percentage used of memory bandwidth, I/O utilization, interrupt latency, and kernel vs. user space code residency. Where possible existing performance counters and metrics that are part of the operating system kernel are used. As the design has a significant FPGA component, performance counters are identified and instantiated in the fabric to measure DMA performance and interface metrics. Collection of metrics is performed on the DLC with a representative workload that simulates a full landing cycle of the Blue Origin New Shepard vehicle. Consideration is given to the other compute implementations and whether they can run SPLICE algorithms at the same rate and with the same latency as the DLC. One option being considered is the use of a RISC-V soft core instantiated in a radiation resilient FPGA fabric such as the Xilinx KU60. Select algorithms from the SPLICE code will be run for comparison with the DLC. This paper describes how the DLC is instrumented to collect performance measurements of the SPLICE workloads, preliminary results from these measurements, and their implications on SPLICE algorithm implementation. The results of experimentation to derive candidate requirements for architecture trades on a PL&HA computing system are also presented.

computer performance↗

The Genesis Mission: A Unique Opportunity for Scientific Collaboration

The Genesis Solar Wind Sample Return was flown with the goal of creating a baseline of elemental and isotopic solar photospheric composition from solar matter (not rocks!) for use in cosmochemical modeling. No uses for the samples outside of Cosmochemistry were advertised, and for good reason. In these days of limited funding, there is an overwhelming tendency to look inward instead of recognizing that the best outcomes of science tend to be interdisciplinary. So, below, we suggest two radical acts of collaboration that we believe will accelerate the advancement of science.

A. J. G. Jurewicz↗

Trust in Collaborative Automation in High Stakes Software Engineering Work

The amount of autonomy in software engineering tools is increasing as developers build increasingly complex systems. Research in other domains shows that too much or too little trust in autonomous tools can have negative consequences, but we are not aware of any study that has investigated trust in autonomous tools in the highly interactive context of a software engineering workplace. We present the results of a ten week ethnographic case study of engineers collaborating with autonomous tools to write flight software at a large national space exploration organization to support high stakes missions. We find that trust in an autonomous software engineering tool in this setting was influenced by four main factors: the tool’s transparency, social context, an organization’s associated processes, and its usability. We outline theoretical implications for future research into trust in autonomous software engineering tools, and practical implications for tool designers and organizations conducting high stakes work with autonomous tools.

Davidoff, Scott↗

Collaborating with NASA

Resources for academia collaborating with NASA subject matter experts

Stephanie Vivod↗

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

activity planning↗