Search NASA⌕ Search

SEARCH · Search NASA

Results for “Data exchange”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records

Enabling Data Exchange and Data Integration with the Common Information Model: An Introduction for Power Systems Engineers and Application Developers

The Common Information Model (CIM) is an open-source information model that is used to model an electrical network and the various equipment used on the network. CIM is widely used for data exchange of bulk transmission power systems and is finding increasing use for distribution systems. Use of a non-proprietary information model (such as CIM) that has been agreed upon and adopted by numerous utilities, vendors, and researchers allows significant reduction in the effort and cost of data integration. Likewise, adoption of open data platforms built around the CIM increases available functionalities for managing and optimizing the smart grid of the future. This report is intended as an introduction to CIM for utility engineers, power systems researchers, and application developers, providing a broad view of the CIM and how particular profiles can be adapted for various use cases. Unlike most other CIM introduction documents and the International Electrotechnical Commission (IEC) standards (which are mostly targeted to an audience of data scientists, enterprise database managers, and platform developers), this report is intended for users of traditional power systems analysis software and other readers without any prior experience with canonical information models, data profiles, or UML modeling.

24 POWER TRANSMISSION AND DISTRIBUTION↗

WIS and WIGOS Metadata as the Foundation for a Sustainable Framework for Global Greenhouse Gas Watch Data Exchange

Metadata (data about data) is a critical component of data discovery, description, evaluation, documentation, and preservation. Developing and propagating metadata standards has been a longstanding area of activity in WMO and beyond. The WIS2 and WIGOS metadata models are being actively developed and maintained by dedicated task teams, established under the WMO Expert Team on Metadata. The metadata representations and vocabularies are governed by well-established processes within WMO. These standards are being used in a number of metadata/data exchange activities (e.g., WMO Information System 2.0 (WIS2), WIGOS (WMDR), Climate Data Management Systems (CMDS), etc.). It should also be noted that the application of the WIS2 and WIGOS standards fully support the WMO Unified Data Policy and open data policy as well as greatly enhance the value of observations by fostering data F.A.I.R.ness. Furthermore, the WMO metadata standards can serve as the foundation for a framework that will facilitate metadata mapping between the existing schemas used in well-established data centres, e.g., WMO WDCGG (World Data Centre for Greenhouse Gases) and NOAA ObsPack (Observation Package Data Products) and to automate metadata exchange between data centres as well as with WMO. These activities will play a central role in integrating measurements sponsored by various member countries and organizations to provide a more comprehensive characterization of the temporal and spatial distribution of the greenhouse gases. At the same time, this metadata exchange can lead to member countries and partner organizations improving their current metadata collection process for data discoverability, interoperability, and (re)usability. This presentation will describe metadata activities in the context of WIS2 and WIGOS and how they apply to GGGW data integration via metadata mapping and exchange.

Gao Chen↗

NASA data exchange standards for computational fluid dynamics

This presentation covers the following topics in viewgraph format: purpose of data exchange standards; data exchange in engineering analysis/CFD; geometry data exchange through existing product data exchange standards, NASA Data Exchange Committee, and NASA-IGES (Initial Graphics Exchange Specification); CFD grid and solution data exchange; and data exchange for multi-disciplinary engineering.

Matthew Blake↗

The NASA-IGES geometry data exchange standard

Described here are the data exchange efforts and plans supported by the NASA Steering Committee for Surface Modeling and Grid Generation. Current methods for geometry data exchange between computer aided design (CAD) systems and NASA computational fluid dynamics (CFD) analysis systems are tedious and induce errors. A Geometry Data Exchange Standard is proposed, utilizing a subset of an existing national standard titled Initial Graphic Exchange Standard (IGES). Future plans for data exchange standardization include all aspects of CFD data. Software systems to utilize this NASA-IGES Geometry Data Exchange Specification are under development.

Blake, Matthew W.↗

BIM Interoperability Tool for Improving IFC-based Model Data Exchange Between Architectural Design and Structural Analysis for Linear Piping Components

There is a growing need in the AEC industry for the digitalization of model-based data exchange in BIM workflows. However, users continue to face difficulties exchanging data between BIM-based computer-aided design (CAD) and computer-aided engineering (CAE) software, even with the open, non-proprietary data exchange format called Industry Foundation Classes (IFC). Proposed solutions in academic research focus primarily on building systems, with comparatively little attention to piping models. Therefore, this paper introduces an interoperability tool for enabling piping model data exchange between architectural and structural analysis domains. The tool is tested using a piping model created in Autodesk Revit and shows marked improvement for IFC-based CAD-to-CAE interoperability over existing practice.

97 MATHEMATICS AND COMPUTING↗

The NASA Scientific and Technical Information (STI) Program's Implementation of Open Archives Initiation (OAI) for Data Interoperability and Data Exchange

Interoperability and data-exchange are critical for the survival of government information management programs. E-government initiatives are transforming the way the government interacts with the public. More information is to be made available through web-enabled technologies. Programs such as the NASA's Scientific and Technical Information (STI) Program Office are tasked to find more effective ways to disseminate information to the public. The NASA STI Program is an agency-wide program charged with gathering, organizing, storing, and disseminating NASA-produced information for research and public use. The program is investigating the use of a new protocol called the Open Archives Initiative (OAI) as a means to improve data interoperability and data collection. OAI promotes the use of the OAI harvesting protocol as a simple way for data sharing among repositories. In two separate initiatives, the STI Program is implementing OAI In collaboration with the Air Force, Department of Energy, and Old Dominion University, the NASA STI Program has funded research on implementing the OAI to exchange data between the three organizations. The second initiative is the deployment of OAI for the NASA technical report server (TRS) environment. The NASA TRS environment is comprised of distributed technical report servers with a centralized search interface. This paper focuses on the implementation of OAI to promote interoperability among diverse data repositories.

Rocker, JoAnne↗

Universal Utility Data Exchange (UUDEX) Functional Design Requirements - Rev 1

This document provides a set of high-level functional design requirements for Universal Utility Data Exchange (UUDEX). These requirements include a set of use cases, data exchanges supported by UUDEX, both for grid operations and for cyber security data, functional requirements for data exchange, data models used by UUDEX, data exchange architectures, and security considerations. These functional design requirements are intended to be used in more detailed design documents.

97 MATHEMATICS AND COMPUTING↗

Government-Industry Data Exchange Program (GIDEP)

The Government-Industry Data Exchange Program (GIDEP) was originated in 1959 by the Army, Navy, and Air Force Ballistic Missile Agencies. Known at that time as IDEP--Interservice Data Exchange Program--its intent was to eliminate duplicate testing of parts and components by disseminating pertinent test data among Department of Defense contractors and various government agencies. In 1966 both the National Aeronautics and Space Administration and the Canadian Military Electronics Standards Agency (CAMESA) recognized the value of the data provided by the program and became participants. Today, GIDEP provides the interchange of specialized technical data to all the military services, participating government contractors and numerous government agencies such as the Atomic Energy Commission, Federal Aviation Administration, Defense Supply Agency, and the Small Business Administration.

Richards, E. T.↗

Universal Utility Data Exchange (UUDEX) - Workflow Design - Rev 1

This workflow design document describes the process of establishing a Universal Utility Data Exchange (UUDEX) Connection between two or more UUDEX Endpoints. The existing processes required to establish a data link using Inter Control Center Communications Protocol (ICCP) are very time consuming, from both the perspectives of effort and calendar time. The intent of UUDEX is to provide a more streamlined alternative. The UUDEX Workflow is also used to establish UUDEX Connections to exchange data other than that found in traditional ICCP data exchanges such as exchanges of power system model files, security events and mitigations, disturbance reports, and market data.

97 MATHEMATICS AND COMPUTING↗

Data for Autonomous Transportation Awareness: Data Exchange Use Cases, Standards, and Barriers

This report examines the critical data exchanges between automated vehicle (AV) service providers and the cities and municipalities they serve. It assists municipal authorities in navigating the often complex and real-time digital data exchanges needed to support AV mobility services, with emphasis in three areas: (1) critical safety data for broad-area situational awareness of hazards typically associated emergency dispatch or roadway work zones; (2) performance metrics of AV services that inform the quantity, quality, spatial extents, and impact on the roadway network; and (3) regulatory and policy information, particularly dynamic information that governs how AV services interact with the roadway network, with emphasis on curb space. The report reviews existing practices and emerging protocols and standards and identifies key gaps to address moving forward.

33 ADVANCED PROPULSION SYSTEMS↗

Impact of Data Exchange Provided by ATD2 Tools at Charlotte-Douglas International Airport

Data Exchange and Integration is necessary for progress towards an Integrated Arrival, Departure, and Surface (IADS) traffic management capability. In collaboration with the FAA, NASA has introduced new data exchange elements to Charlotte-Douglas International Airport air traffic facilities, including the American Airlines ramp, as part of the Airspace Technology Demonstration 2 (ATD2). This paper describes the new tools that deliver these elements, and the human factors impact of the tools as measured by post-bank surveys. Workload was unaffected by ATD2 tool use, and situational awareness was improved in the Tower and with Ramp controllers in the second round of surveys. Respondents described their tools as more helpful if they included ATD2 tools 1) in the Tower for insuring compliance for aircraft under a Traffic Management Initiative, 2) in the TRACON when actively used for many TRACON tasks, and 3) in the Ramp in the second round of surveys.

and surface traffic management; human factors asse↗

Leaf gas exchange data, Nov 2018 and May 2019, Daintree Rainforest, Australia

This data package contains leaf gas exchange data for 11 canopy tree species in the control and drought treatments at the Daintree Rainforest Observatory in Queensland, Australia (AU-DRO) with the purpose of testing for differences in gas exchange between treatments. Data were collected at the end of the dry season (November 2018) and end of the wet season (May 2019). Using a canopy crane, large branches (>1 m) were collected from the top of the canopy and immediately placed in a bucket of water, upon which the LI-6800 leaf chamber was clamped onto a recently mature leaf with minimal herbivory. Measurements were recorded every 3 seconds for 3 minutes total. The species included in the dataset are: Castanospermum australe, Cleistanthus myrianthus, Cryptocarya mackinnoniana, Dysoxylum papuanum, Elaeocarpus angustifolius (Elaeocarpus grandis), Endiandra microneura, Mallotus paniculatus, Myristica globosa, Rockinghamia angustifolia, Synima cordierorum, Syzygium spp. The two data files included are: 1. LICOR_Data_AU_DRO_2019_GasEx.csv (a compilation of individual LICOR output files, with correction of user input errors such as incorrect species spelling) 2. ESS_DIVE_Data_AU_DRO_2019_GasEx.csv (selected variables and converted units from LICOR_Data_AU_DRO_2019_GasEx.csv to follow the standard gas exchange reporting format from Ely et al. 2021 Ecological Informatics). The metadata files included are: (3) ESS_DIVE_Metadata_AU_DRO_2019_GasEx.xlsx (4) File_Submission_Metadata_AU_DRP_2019_GasEx.xlsx (5) E-Field_Log_AU_DRO_2019_GasEx.xlsx (6) Data_Column_Description_AU_DRO_2019_GasEx.xlsx.

54 ENVIRONMENTAL SCIENCES↗

Flight Test of Weather Data Exchange Using the 1090 Extended Squitter (1090ES) and VDL Mode 3 Data Links

This report describes preliminary results of work done by JHU/APL under contract to the NASA Glenn Research Center to support flight testing of the Universal Access Transceiver (UAT) data link as a medium for weather data exchange. It presents a high level architectural description of the use of UAT to meet the program objectives with an identification of issues associated with the use of this data link, including a high level definition of the changes required to UAT avionics and ground-based receivers and supporting ground infrastructure to support implementation of the recommended architecture with focus on the issues associated with these changes.

Griner, James H., Jr.↗

Improving and Automating Building Model Data Exchange

There are many instances throughout a project’s lifecycle where there arises a need for quick and accurate risk assessment of building designs. For example, an unexpected design change during construction may necessitate structural engineers to perform a seismic risk assessment on analytical models of the updated building design using high fidelity structural analysis software, such as ANSYS or Abaqus. However, the efficiency of such workflows often depends upon the interoperability of architectural design software and structural analysis software. When the quality of this interoperability is lacking or even non-existent, the efficiency of virtual engineering workflows is hampered, which increases project costs. A McGraw Hill industry survey of professional users of Building Information Modeling (BIM) technologies found that there is high demand for BIM interoperability for structural analysis, but that the value/difficulty ratio is currently too low for practical use. There have been efforts by the academic community to facilitate model data exchange between the architectural design and structural analysis domains, but such solutions have not been widely adopted by industry, face technical challenges, and oftentimes are limited in applicability for users of various BIM software. Therefore, INL is developing capabilities to improve, automate, and generalize model data exchange between architectural BIM software (e.g., Revit) and structural analysis software (e.g., SAP2000, ANSYS). The goal is to help expedite and automate as much of the pre-processing step for creating analytical models in finite element analysis software as reasonably as possible. Such a "BIM-to-FEA" conversion tool should provide direct benefit to end-users through accuracy, automation, quick turn-around, and wide applicability. To generalize the application of this BIM-to-FEA conversion tool and increase its useability among the many different commercial BIM software currently used by industry, the program is being developed with the concept of openBIM. OpenBIM is the application of non-proprietary, open data standards that allow for BIM model data exchange in a format that is accessible, retainable, and useable for all users. The most widely used open, non-proprietary data exchange format for BIM is the Industry Foundation Classes (IFC) schema. IFC is developed by buildingSMART international and is ISO certified (ISO 16739-1:2018). The BIM-to-FEA conversion tool is being developed for compatibility with typical commercial building designs of steel framed structures. The tool is currently capable of importing architectural BIM data of framed building structures, recognizing and extracting the aspects of the model that are required for structural analysis, adjusting the connectivity of frame members, and finally exporting to an analytical model stored in the IFC format. The exported IFC analytical model can then be imported into various openBIM compliant software, such as SAP2000. Such capabilities have already been tested on commercial software, as shown above, and continue to be improved. Work is underway to test the conversion on various commercial BIM software, develop a user-friendly interface, incorporate the program into the broader DeepLynx data warehouse project being developed by INL, and to eventually open-source the tool for the benefit of the community. Future development of the tool envisions the ability for efficient iterative risk assessment of generative building designs, all within a workflow utilizing open-source tools. One such open-source tool will be MOOSE, an advanced finite element analysis tool developed at INL. The conversion tool will also branch out from typical commercial building designs and will aim to incorporate nuclear construction. The aim will be to convert both structural and non-structural components of nuclear facilities, such as curved concrete containment structures and piping systems, respectively.

97 MATHEMATICS AND COMPUTING↗

Technology Candidates for Air-to-Air and Air-to-Ground Data Exchange

Technology Candidates for Air-to-Air and Air-to-Ground Data Exchange is a two-year research effort to visualize the U. S. aviation industry at a point 50 years in the future, and to define potential communication solutions to meet those future data exchange needs. The research team, led by XCELAR, was tasked with identifying future National Airspace System (NAS) scenarios, determining requirements and functions (including gaps), investigating technical and business issues for air, ground, & air-to-ground interactions, and reporting on the results. The project was conducted under technical direction from NASA and in collaboration with XCELAR's partner, National Institute of Aerospace, and NASA technical representatives. Parallel efforts were initiated to define the information exchange functional needs of the future NAS, and specific communication link technologies to potentially serve those needs. Those efforts converged with the mapping of each identified future NAS function to potential enabling communication solutions; those solutions were then compared with, and ranked relative to, each other on a technical basis in a structured analysis process. The technical solutions emerging from that process were then assessed from a business case perspective to determine their viability from a real-world adoption and deployment standpoint. The results of that analysis produced a proposed set of future solutions and most promising candidate technologies. Gap analyses were conducted at two points in the process, the first examining technical factors, and the second as part of the business case analysis. In each case, no gaps or unmet needs were identified in applying the solutions evaluated to the requirements identified. The future communication solutions identified in the research comprise both specific link technologies and two enabling technologies that apply to most or all specific links. As a result, the research resulted in a new analysis approach, viewing the underlying architecture of ground-air and air-air communications as a whole, rather than as simple "link to function" paired solutions. For the business case analysis, a number of "reference architectures" were developed for both the future technologies and the current systems, based on three typical configurations of current aircraft. Current and future costs were assigned, and various comparisons made between the current and future architectures. In general, it was assumed that if a future architecture offers lower cost than the current typical architecture, while delivering equivalent or better performance, it is likely that the future solution will gain industry acceptance. Conversely, future architectures presenting higher costs than their current counterparts must present a compelling benefit case in other areas or risk a lack of industry acceptance. The business case analysis consistently indicated lower costs for the proposed future architectures, and in most cases, significantly so. The proposed future solutions were found to offer significantly greater functionality, flexibility, and growth potential over time, at lower cost, than current systems. This was true for overall, fleet-wide equipage for domestic and oceanic air carriers, as well as for single, General Aviation (GA) aircraft. The overall research results indicate that all identified requirements can be met by the proposed solutions with significant capacity for future growth. Results also illustrate that the majority of the future communication needs can be met using currently allocated aviation RF spectrum, if used in more effective ways than it is today. A combination of such optimized aviation-specific links and commercial communication systems meets all identified needs for the 50-year future and beyond, with the caveat that a new, overall function will be needed to manage all information exchange, individual links, security, cost, and other factors. This function was labeled "Delivery Manager" (DM) within this research. DM employs a distributed client/server architecture, for both airborne and ground communications architectures. Final research results included identifying the most promising candidate technologies for the future system, conclusions and recommendations, and identifying areas where further research should be considered.

Communications↗

Universal Utility Data Exchange (UUDEX) – Security and Administration: Cybersecurity of Energy Delivery Systems (CEDS) Research and Development

A critical component of the Universal Utility Data Exchange (UUDEX) approach is the integrated security contained within its processing. This document describes how that security is designed and expected to be implemented by UUDEX Implementations (U-Implementations), including the UUDEX Server (U-Server) and UUDEX Clients (U-Clients). The UUDEX security hierarchy consists of three levels: 1. The UUDEX Instance (U-Instance) itself, which sits at the top of the hierarchy and contains the U-Server, the UUDEX Identity Authority (U-Identity Authority), and the UUDEX Administrator (U-Administrator) functions; 2. A group of one or more UUDEX Participants (U-Participants) that present “organizations” that participate in the U-Instance and contains the UUDEX Administrator Participant (U-U-Administrator Participant) function; 3. A group of one or more UUDEX Endpoints (U-Endpoints) that represent the individual UUDEX Publish Clients (U-Publish Client) responsible for supplying data to the U-Instance that is consumed by UUDEX Subscriber Clients (U-Subscriber Clients). U-Endpoints can be either autonomous devices that publish and subscribe data such as data exchange servers found in supervisory control and data acquisition and energy management systems, or they can be tied to users of applications that, for example, submit DOE OE-417 disturbance reports. U-Participants and U-Endpoints can be organized into UUDEX Groups (U-Groups). Any number of U-Participants or U-Endpoints can be members of a U-Group. A given U-Participant or U-Endpoint can be a member of multiple U-Groups, but a U-Group cannot contain other U-Groups. For example, a U-Group could be created to contain all U-Participant Transmission Operators within the purview of a Reliability Coordinator, and another U-Group could be created to contain all U-Participant Generator Operators within the purview of a Reliability Coordinator. U-Participants that are both Transmission Operators and Generator Operators would be members of both U-Groups. U-Participants, U-Endpoints, and U-Groups are used in the access control structures to provide access to individual UUDEX Subjects (U-Subjects). U-Groups are created by the U-Administrator and are managed by the U-Administrator or the designated U-Group Managers. U-Endpoints can be assigned UUDEX Roles (U-Roles) that can be used to further restrict access. U-Roles are assigned to individual U-Endpoints. For example, a U-Role of “Security Analyst” could be used to restrict which U-Endpoints can publish or subscribe security incident reports and vulnerability notifications, while a U-Role of “Transmission Planner” can be used to restrict which U-Endpoints can publish power system model updates. U-Role definitions are created by the U-Administrator, but the U-Roles are assigned to U-Endpoints by their respective UUDEX Participant Administrators (U-Participant Administrator). Because all information required to make security decisions is either included within the U-Endpoint’s X.509 digital certificate or stored in a datastore on the U-Server, all security decisions are performed and enforced within the U-Server. This reduces the complexity of the U-Client code and minimizes the chance for compromise of the integrity of the UUDEX security features.

97 MATHEMATICS AND COMPUTING↗

Government-Industry Data Exchange Program (GIDEP) and NASA Advisories

This viewgraph presentation reviews the Government-Industry Data Exchange Program (GIDEP) and NASA Advisories policy to practice. The contents include: 1) Purpose of the Government-Industry Data Exchange Program (GIDEP); 2) NASA and GSFC Documentation; 3) NASA Advisories, differences from GIDEP; 4) GIDEP Distribution by Originator; 5) New Interim GIDEP Policy for Suspect Counterfeits; 6) NASA and Suspect Counterfeits; 7) Threats to GIDEP; and 8) Conclusions and Contact Information.

Sampson, Michael J.↗