Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Information Sharing”

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 73 records · Page 4

IT Research Services: Powerful Tools to Track a Fast Moving Industry

Research services change and evolve over time, sometimes suddenly, in their focus, topics, formats, service model, etc. You have to check in often. Some offer products that you can customize to your environment, others not so much. You will find a variation in customer management practices (e.g., when and how they share information) ...can sometimes be annoying. Assess your needs carefully. Each research service has a very different service model. Explore ways to share or lower the cost. Someone out there may share the expense when that is an option. Make sure you read the small print. It can work for you as well as against you. When in doubt, ask your Vendor's POC. Set up Research Service "gurus or SME's." Not to violate the copyright agreement of course, just have someone who knows what's there. After you subscribe, reassess.Get the most out of your investment. Some early enthusiasts will fade, and there will be others who don't know it's there and can use it.

Hunter, Paul↗

JPL Project Information Management: A Continuum Back to the Future

This slide presentation reviews the practices and architecture that support information management at JPL. This practice has allowed concurrent use and reuse of information by primary and secondary users. The use of this practice is illustrated in the evolution of the Mars Rovers from the Mars Pathfinder to the development of the Mars Science Laboratory. The recognition of the importance of information management during all phases of a project life cycle has resulted in the design of an information system that includes metadata, has reduced the risk of information loss through the use of an in-process appraisal, shaping of project's appreciation for capturing and managing the information on one project for re-use by future projects as a natural outgrowth of the process. This process has also assisted in connection of geographically disbursed partners into a team through sharing information, common tools and collaboration.

Information Management↗

TCL3 UTM (UAS Traffic Management) Flight Tests, Airspace Operations Laboratory (AOL) Report

The Technology Capability Level-3 (TCL3) flight tests were conducted at six different test sites located across the USA from March to May of 2018. The campaign resulted in over 830 data collection flights using 28 different aircraft and involving 20 flight crews. Flights not only varied in duration, but also in the environments and terrains over which they flew. The TCL3 tests highlighted four different types of tests: three tests focused on Communication, Navigation and Surveillance (CNS); six tests focused on Sense and Avoid (SAA) technologies; six tests focused on USS Data and Information Exchange (DAT); and five tests focused on exploring fundamental Concepts of the project (CON). This document presents data collected during the TCL3 tests that informed the operator’s experiences—the quality of the unmanned aerial system (UAS) Service Supplier (USS) information that the operator was provided with, the usefulness of this information, and the usability of the automation, both while airborne and on the ground. It is intended to complement the reports written by the test sites and the quantitative reports and presentations of the UAS Traffic Management (UTM) project. With the goal of instructing what the minimum information requirements and/or best practices might be in TCL3 operations, the driving enquiry was: How do you get the information you need, when you need it, to successfully fly a UAS in UTM airspace? This enquiry touches on two requirements for displays, which are to provide adequate situation awareness (SA) and to share information through a USS. The six test sites participating in the TCL3 tests flew a subset of the 20 tests (outlined above), with most sites working on a subset of each of the four types: Communications, Navigation and Surveillance (CNS); DAT; CON; and Sense and Avoid (SAA). The, mainly qualitative, data addressed in this report was collected by the AOL (Airspace Operations Laboratory) both on-site and remotely for each test. The data consists of the contents of end-of-day debriefs, end-of-day surveys, observer notes, and flight test information, all submitted as part of the Data Management Plan (DMP).

Martin, Lynne↗

Departure Approval Request Compliance Effects on Overhead Stream Insertion

Integrated Arrival-Departure-Surface (IADS) air traffic management relies on information sharing and integration between automation systems for efficiency, predictability, and throughput improvements throughout the National Airspace System (NAS). The NASA Airspace Technology Demonstration 2 (ATD-2) project supports this effort by integrating SWIM (System Wide Information Management) information and evaluating and refining potential TFDM (Terminal Flight Data Manager) functionality in a surface traffic management system fielded at Charlotte-Douglas International Airport (CLT). Among the IADS areas under study during ATD-2 is the use of electronically negotiated departure times for efficiently inserting flights into overhead traffic streams. Stream-insertion accuracy is important for reducing excessive vectoring that negatively impacts the NAS by increasing controller workload along with aircraft fuel burn and emissions. Departure-time approval requests (APREQs) provide center-approved departure times to allow for smooth stream insertion. In this presentation, TBFM (Time-Based Flow Management) and ATD-2 flight summary data are used to empirically show that APREQ compliance leads to improved stream insertion.

Overhead-Stream Insertion↗

SPHERES Synchronized, Position, Hold, Engage, Reorient, Experimental Satellites: SPHERES Working Group (SWG) Quarterly Meeting

SPHERES Working Group (SWG) Quarterly meeting. Membership includes MIT, FIT, AFS, DARPA, CASIS, SJSU, and NASA (HQ, KSC, JSC, MSFC, and ARC). Face-to-Face, twice a year. Next Face-to-Face will be scheduled in Feb. 2017 at NASA Ames. Purpose: Information sharing across the SPHERES community. Program office shares National Lab Facility availability. Status of resources (batteries, CO2 tanks, etc.), Overall Calendar (scheduled Test Sessions, upmassreturn), and Updates on new PD, Investigations, and ISS infrastructure.Provide the SPHERES community (PD, investigators, etc.) with up-to-date information to determine opportunities to use the NL Facility. Discuss proposed changes updates to SPHERES Nat Lab which may be required to support a specific activity or research. Discuss specific support requests made to the ISS Office.

Jose V Benavides↗

SPHERES/Astrobee Working Group (SAWG) Quarterly Meeting

SPHERES Astrobee Working Group (SAWG) Quarterly meeting. Membership includes MIT, FIT, AFS, DARPA, CASIS, SJSU, and NASA (HQ, KSC, JSC, MSFC, and ARC). Face-to-Face, twice a year Purpose: Information sharing across the SPHERES community. Program office shares National Lab Facility availability. Status of resources (batteries, CO2 tanks, etc.), Overall Calendar (scheduled Test Sessions, upmassreturn), and Updates on new PD, Investigations, and ISS infrastructure. Provide the SPHERES community (PD, investigators, etc.) with up-to-date information to determine opportunities to use the NL Facility. Discuss proposed changes updates to SPHERES Nat Lab which may be required to support a specific activity or research. Discuss specific support requests made to the ISS Office

Benavides, Jose V.↗

SPHERES: Synchronized, Position, Hold, Engage, Reorient, Experimental Satellites

SPHERES/Astrobee Working Group (SAWG) Quarterly meeting. Membership includes MIT, FIT, AFS, DARPA, CASIS, SJSU, and NASA (HQ, KSC, JSC, MSFC, and ARC) Face-to-Face, twice a year. The purpose is information sharing across the SPHERES community. Program office shares National Lab facility availability. Status of resources (batteries, CO2 tanks, etc.), overall calendar (scheduled Test Sessions, upmass return), and updates on new PD, investigations, and ISS infrastructure. Provide the SPHERES community (PD, investigators, etc.) with up-to-date information to determine opportunities to use the National Lab facility. Discuss proposed changes and updates to SPHERES National Lab which may be required to support a specific activity or research. Discuss specific support requests made to the ISS Office.

SPHERES satellites↗

Evaluating and Evolving Metadata in Multiple Dialects

Despite many long-term homogenization efforts, communities continue to develop focused metadata standards along with related recommendations and (typically) XML representations (aka dialects) for sharing metadata content. Different representations easily become obstacles to sharing information because each representation generally requires a set of tools and skills that are designed, built, and maintained specifically for that representation. In contrast, community recommendations are generally described, at least initially, at a more conceptual level and are more easily shared. For example, most communities agree that dataset titles should be included in metadata records although they write the titles in different ways.

metadata quality↗

SPHERES: Synchronized, Position, Hold, Engage, Reorient, Experimental Satellites: SPHERES/Astrobee Working Group (SAWG)

SPHERES/Astrobee Working Group (SAWG) Quarterly meeting. Membership includes MIT, FIT, AFS, DARPA, CASIS, SJSU, and NASA (HQ, KSC, JSC, MSFC, and ARC)Face-to-Face, twice a year Purpose: Information sharing across the SPHERES community Program office shares National Lab Facility availability Status of resources (batteries, CO2 tanks, etc.), Overall Calendar (scheduled Test Sessions, up mass return), and Updates on new PD, Investigations, and ISS infrastructure. Provide the SPHERES community (PD, investigators, etc.) with up-to-date information to determine opportunities to use the NL Facility Discuss proposed changes updates to SPHERES Nat Lab which may be required to support a specific activity or research. Discuss specific support requests made to the ISS Office.

Benavides, Jose↗

Behavioral Health and Performance (BHP) Standing Review Panel (SRP) Final Report

The first meeting of the Behavioral Health and Performance (BHP) Standing Review Panel (SRP) was held in Houston, TX on November 1-3, 2009. Our task was to assess the Integrated Research Plan (IRP) related to the fields covered in the SRP charge (see section VIII). Having considered and discussed the extensive materials distributed prior to the meeting, and the highly informative briefings by the NASA BHP Human Research Program (HRP) personnel during the site visit, the SRP agreed that the IRP is comprehensive and was developed carefully. Question and answer periods with the presenters were particularly productive and helpful to the SRP. The presenters' willingness to share information and positive responses to the SRP's suggestions were greatly appreciated. Although the IRP and related documents are impressive, the SRP does have a number of recommendations regarding both the overall plan and its component parts.

Suedfeld, Peter↗

A Web-based Collaborative Tool for Mars Analog Data Exploration

Solving today's complex research and modeling challenges are dependent on our ability to discover, access, integrate, and share information from multiple sources. The planetary sciences community is no exception'; over the last few years, the need for data mining and exploration tools that can expedite comparative studies between Martian and terrestrial analogs sites and aid the interpretation of Mars data sets has become evident. Data sharing maximizes scientific return from studies and data sets.

Necsoiu, M.↗

AstroBetter: A Blog and Wiki for Professional Astronomers

AstroBetter.com is a multi-contributor blog and wiki website designed for information sharing among professional astronomers. The goal of the site is to increase the productivity of astronomers by creating a centralized location for tips and tools of our multifaceted trade. Our content includes topics related to data reduction and analysis, general computing, writing papers and proposals, giving talks, teaching, career planning, productivity, organization, and diversity and equity in science and education. While we have several contributors, the site is intended to be community driven and we encourage everyone to publish to the wiki, submit guest posts, suggest post ideas, and to comment on blog entries. One of our primary goals is to consolidate and reduce the transient nature of the astronomy community's collective knowledge base by having an active wiki. Currently, the most common way to share astro-centric tools and tips that are not appropriate for a published paper, is to put them on an individual's website. However, the average astronomer's website will have at least four different addresses over the course of their career and only the site owner can edit the content. As a result, information on personal websites goes stale very quickly and deal links to such sites abound. It is our hope that community maintained wikis, such as the one hosted on AstroBetter, will gradually replace the personal website. In this poster we introduce the contributors to AstroBetter, show statistics about our current readership, give excerpts of some of our most popular posts and wiki entries, and show how anyone can add or edit content on the wiki. The goal of this poster is to spread the work about AstroBetter and increase our community of readers and wiki editors, because together, we can AstroBetter.

Rigby, Jane↗

Modular Software Interfaces for Revolutionary Flexibility in Space Operations

To make revolutionary improvements in exploration, space systems need to be flexible, realtime reconfigurable, and able to trade data transparently among themselves and mission operations. Onboard operations systems, space assembly coordination and EVA systems in exploration and construction all require real-time modular reconfigurability and data sharing. But NASA's current exploration systems are still largely legacies from hastily-developed, one-off Apollo-era practices. Today's rovers, vehicles, spacesuits, space stations, and instruments are not able to plug-and-play, Lego-like: into different combinations. Point-to-point dominates - individual suit to individual vehicle, individual instrument to rover. All are locally optimized, all unique, each of the data interfaces has been recoded for each possible combination. This will be an operations and maintenance nightmare in the much larger Project Constellation system of systems. This legacy approach does not scale to the hundreds of networked space components needed for space construction and for new, space-based approaches to Earth-Moon operations. By comparison, battlefield information management systems, which are considered critical to military force projection, have long since abandoned a point-to-point approach to systems integration. From a system-of-systems viewpoint, a clean-sheet redesign of the interfaces of all exploration systems is a necessary prerequisite before designing the interfaces of the individual exploration systems. Existing communications and Global Information Grid and middleware technologies are probably sufficient for command and control and information interfaces, with some hardware and time-delay modifications for space environments. NASA's future advanced space operations must also be information and data compatible with aerospace operations and surveillance systems being developed by other US Government agencies such as the Department of Homeland Security, Federal Aviation Administration and Department of Defense. This paper discusses fundamental system-of-systems infrastructure: approaches and architectures for modular plug-and-play software interfaces for revolutionary improvements in flexibility, modularity, robustness, ease of maintenance, reconfigurability, safety and productivity. Starting with middleware, databases, and mobile communications technologies, our technical challenges will be to apply these ideas to the requirements of constellations of space systems and to implement them initially on prototype space hardware. This is necessary to demonstrate an integrated information sharing architecture and services. It is a bottom-up approach, one that solves the problem of space operations data integration. Exploration demands uniform software mechanisms for application information interchange, and the corresponding uniformly available software services to enhance these mechanisms. We will examine the issues in plug-and-play, real-time-configurable systems, including common definition and management and tracking of data and information among many different space systems. Different field test approaches are discussed, including the use of the International Space Station and terrestrial analog mission operations at field sites.

Glass, Brian↗

S&MA Internship to Support Orion and the European Service Module

As a University Space Research Association (USRA) intern for NASA Johnson Space Center (JSC) during the summer 2016 work term, I worked on three main projects for the Space Exploration Division (NC) of the Safety and Mission Assurance (S&MA) Directorate. I worked on all three projects concurrently. One of the projects involved facilitating the status and closure of technical actions that were created during European Service Module (ESM) safety reviews by the MPCV Safety & Engineering Review Panel (MSERP). The two main duties included accurately collecting and summarizing qualitative data, and communicating that information to the European Space Agency (ESA) and Airbus (ESA's prime contractor) in a clear, succinct and precise manner. This project also required that I create a report on the challenges and opportunities of international S&MA. With its heavy emphasis on soft skills, this project taught me how to communicate better, by showing me how to present and share information in an easy-to-read and understandable format, and by showing me how to cooperate with and culturally respect international partners on a technical project. The second project involved working with the Orion Thermal Protection System (TPS) Process Failure Modes and Effects Analysis (PFMEA) Working Group to create the first full version of the Orion TPS PFMEA. The Orion TPS PFMEA Working Group met twice a week to analyze the Avcoat block installation process for failure modes, the failure modes effects, and how such failure modes could be controlled. I was in charge of implementing changes that were discussed in meeting, but were not implemented real time. Another major task included creating a significant portion of the content alongside another team member outside the two weekly meetings. This project caused me to become knowledgeable about TPS, heatshields, space-rated manufacturing, and non-destructive evaluation (NDE). The project also helped me to become better at working with a small team and helped improved my technical communication skills. My main duty for the third project was creating a Safety Verification Tracking Log (SVTL) for the Orbital Maneuvering System Engine (OMS-E), and contacting subject matter experts to close Hazard Report (HR) control verifications. This project also required me to support other OMS-E safety process tasks, like monitoring OMS-E vibration testing for Quality Assurance (QA) purposes. This project helped me become even more proficient in Excel. Throughout the project, I gained knowledge about the OMS-E system and improved my understanding of pressure systems and propellant systems. In terms of education goals, this work term has affirmed my desire to take a few more space-related courses, like orbital mechanics, so that I can have a better understanding of human spaceflight and the industry surrounding it. However, the work term did not persuade me to pursue a master's degree. In terms of career goals, this work term has helped me clarify the direction I would like to head in the future. The perspective of three summer terms working for NASA in S&MA has allowed me to observe that most S&MA employees joined S&MA after working in other NASA directorates, such as Engineering or Flight Operations. It is my belief that it would be advantageous for both NASA and I for me to broaden my knowledge base and technical skill set by completing hands-on technical work on human spaceflight projects, and for me to integrate my safety experience directly into technical work in other directorates. The other significant advantage to this proposed situation is that if I were to eventually return to S&MA, I would be returning with a substantial set of hands-on technical experience and knowledge, which would be a significant resource for S&MA tasks and projects.

Hutcheson, Connor↗

A Deeper Dive Into the Meaning and Implications of Interoperability for LunaNet Communications and Navigation Services

As part of planning efforts for cislunar exploration and science missions, space agencies have been collaborating with each other to enable communications, networking, Position, Navigation, and Timing (PNT) systems to exchange information and provide services to spacecraft and space systems in transit, in orbit, and on the surface, thus helping each other to achieve their common goals. To achieve commonality and lower cost for mutual benefit, the strategy of interoperability is being adopted to help all the pieces fit together and function smoothly. Interoperability gives cislunar users the ability to operate in a collaborative environment similar to the terrestrial Internet, allowing them to share information, navigate safely despite increasing radio frequency congestion, and follow common processes and procedures for effective joint operations. Unlike prior government-dominated efforts, this ecosystem is expected to include commercial for-profit businesses, non-profit organizations, and academic institutions. Ultimately, the goal is to enable a cislunar ecosystem of service providers and users to contribute and/or utilize infrastructure and capabilities to accomplish mission objectives spanning the full range of human endeavours while supporting a variety of business models. This paper reports on the results of an effort to assist in efforts to frame the development of the international LunaNet architecture by providing a canonical definition of interoperability broad enough to meet these needs, examine architectural and operational implications of the definition, and explore interoperability strategies and tactics for deploying and evolving these services. It describes key systems-of-systems (SoS) (Network-of-Networks) interoperability concepts in the context of sustainment of the ecosystem over time as systems evolve in technologies, standards and Standards Development Organizations, component and subsystem upgrades, and user applications

LunaNet↗

The Evolution of Lidar Networks: A US Perspective

Atmospheric aerosols and clouds play an important role in climate by directly scattering and absorbing sunlight. Aerosol-cloud interactions modify the particle properties causing indirect effects, alter aerosol deposition and rainfall, and contribute substantially to the uncertainties in predicting climate effects. Aerosols also affect air quality and both constituents modulate boundary layer dynamics to a certain extent, in turn impacting aerosol transport and aerosol-cloud interactions. The spatiotemporal distribution of aerosol and cloud layers is thus important, and lidar remains the primary instrument for determining the vertical distribution of aerosols and thin clouds. Lidar still provides important information for opaque cloud layers by determining base heights. Combined lidar and radar data provide a comprehensive coverage of aerosol and cloud vertical distributions, and thus locations where and when they interact. Lidar data provide a means of constraining column aerosol loading observations (e.g. AOD) to vertical extents. In addition, lidar has proven effective at determining a proxy for boundary layer height by examining aerosol gradients and/or cloud base heights in lidar profiles. Polarized lidars provide additional information on particle shape, allowing estimates of cloud phase and separation of dust or smoke from sulfate and sea salt aerosols. Given the importance of lidar observations and a critical maturation in technology and retrieval techniques, several organizations began to build operational lidar networks around 2000. The European Aerosol Research Lidar Network (EARLINET) was started as a research focused network of advanced lidars across Europe. The Asian Dust Lidar Network (ADNET) was also developed as a regional network providing lidar profiles of dust and pollution across Eastern Asia. In the US, the NASA Micro Pulse Lidar Network (MPLNET) was created to provide global lidar profiling at key sites in the NASA Aerosol Robotic Network (AERONET). The Network for the Detection of Atmospheric Composition Change (NDACC) pre-dates these networks and many sites have lidar, but it is not strictly a lidar network and at the time focused less on the lower troposphere. Finally, there were already existing ceilometer networks operated by various meteorological agencies, but in particular here in the US the profile data has not been available. The ceilometer networks were used to provide only clouds base heights and estimates of PBL height. Thus, the distinguishing feature between lidar and ceilometer networks was historically the ability to actually provide profile information (in addition to differences in wavelength, and advanced retrievals such as the raman technique). As time progressed, each lidar network matured and developed more operational capabilities and data sets, coupled with viable data centers providing DAAC services and access to near-real-time (NRT) data. In 2008 under WMO guidance, the Global Atmospheric Watch (GAW) Aerosol Lidar Observation Network (GALION) was formed as a global network made up of the existing lidar networks. The goal was to share information, best practices, and develop frameworks and techniques for quality data. GALION grew to include several other regional lidar networks and this has led to a vast increase in quality lidar sites worldwide.

Welton, Ellsworth J.↗

STEReO: Combining NASA Technologies and Partnerships to Transform Current-Day Emergency Response Operations

STEReO brings together several technologies in Unmanned Aircraft Systems (UAS) Traffic Management (UTM), Autonomy, Communications, Human Factors, and Domain Expertise & Tools, aimed at providing scalability and flexibility, as well as operational resiliency to dynamic changes during a disaster event. Some of the concepts STEReO explores are: collaborative tools to ingest remote sensing information and distribute a common mission operating picture, apply ad-hoc communication networks to facilitate timely information sharing and communication of changes, vehicle-to-vehicle and onboard autonomy technologies ensure the safety and resiliency of operations, and apply NASA?s UAS traffic management system (UTM) as a public safety UAS Service Supplier (USS) to access and coordinate use of the airspace by both manned and unmanned operations. The potential benefits of STEReO include: standardized, cross-platform communication means increased interoperability and ease of cooperation/collaboration, increased situation awareness and common operating picture allow for earlier detection and decision making, and scalable to size and complexity of environment, operations, and mission objectives. This presentation gives an informational overview of the STEReO project to attendees of the annual North American Aerial Fire Fighting conference (AFFNA 2020).

Mercer, Joey S.↗

Stereo: Combining NASA Technologies and Partnerships to Transform Current-Day Emergency Response Operations

STEReO brings together several technologies in Unmanned Aircraft Systems (UAS) Traffic Management (UTM), Autonomy, Communications, Human Factors, and Domain Expertise & Tools, aimed at providing scalability and flexibility, as well as operational resiliency to dynamic changes during a disaster event. Some of the concepts STEReO explores are: collaborative tools to ingest remote sensing information and distribute a common mission operating picture, apply ad-hoc communication networks to facilitate timely information sharing and communication of changes, vehicle-to-vehicle and onboard autonomy technologies ensure the safety and resiliency of operations, and apply NASA's UAS traffic management system (UTM) as a public safety UAS Service Supplier (USS) to access and coordinate use of the airspace by both manned and unmanned operations. The potential benefits of STEReO include: standardized, cross-platform communication means increased interoperability and ease of cooperation/collaboration, increased situation awareness and common operating picture allow for earlier detection and decision making, and scalable to size and complexity of environment, operations, and mission objectives. This presentation gives an informational overview of the STEReO project to the members of the US Forest Service (USFS) region 5 aerial supervisor steering committee (ASSC).

Mercer, Joey↗