Search NASA⌕ Search

SEARCH · Search NASA

Results for “interoperability”

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 55 records · Page 3

A Generic Primary-Control Model for Grid-Forming Inverters: Towards Interoperable Operation & Control

This paper outlines an architectural vision centered around the notion of interoperability to integrate grid-forming inverter-based resources in large-scale grids. With the underlying principle of interoperability guiding developments, we focus on modeling the characteristics of droop, virtual synchronous machine, and virtual oscillator controls. Emphasis is placed on these three controllers since they are leading grid-forming control candidates and are likely to be commonplace as primary-control schemes in future systems. We show that these controllers can each be considered as instantiations of a more generic model and that all these controllers exhibit similar droop-like relations between pertinent terminal variables in steady state. This commonality between controllers gives interoperability among them such that automatic synchronization, power sharing, and voltage regulation can be achieved. Simulation results validate the models and demonstrate how the steady-state droop characteristics of these control methods can be aligned with the aid of the developed modeling paradigm.

control↗

A Comprehensive Review of Practical Issues for Interoperability Using the Common Information Model in Smart Grids

Smart grids with interoperability improve grid reliability by collecting system information and transferring it to an energy management system and associated applications through a seamless end-to-end connection. To achieve interoperability, it is required to exchange the semantic information within the different domains. The international electrotechnical commission has established the Common Information Model (CIM) tool, which is a standard application programming interface for the exchange of semantic information in power systems. CIM provides a robust framework for accurate data sharing, merging, and transformation into reusable information. However, as CIM provides a basic framework for information exchange, various practical issues arise in establishing an energy management system capable of exchanging information using CIM. This paper aims to offer a comprehensive understanding by summarizing and categorizing the research on the practical use of CIM for interoperability in smart grids. Many papers are analyzed and the issues are classified into CIM extension, harmonization, and validation to address the issues that arise when establishing an integrated information exchange system.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Challenges of Space Mission Interoperability

This viewgraph presentation reviews some of the international challenges to space mission interoperability. Interoperability is the technical capability of two or more systems or components to exchange information and to use the information that has been exchanged. One of the challenges that is addressed is the problem of spectrum bandwidth, and interference. The key to interoperability is the standardization of space communications services and protocols. Various levels of international cross support are reviewed: harmony, cooperation cross support and confederation cross support. The various international bodies charged with implementing cross support are reviewed. The goal of the Interagency Operations Advisory Group (IOAG) is to achieve plug-and-play operations where all that is required is for each of the systems to use an agreed communications medium, after which the systems configure each other for the purpose of exchanging information and subsequently effect such exchange automatically.

interoperability↗

Draft LunaNet Interoperability Specification

Under the guidance of NASA’s Space Communication and Navigation (SCaN) program, this document, along with its companion documents, LunaNet Services Requirements Document (TBD) and the LunaNet Concept of Operations and Architecture (TBD), provides the basis for a comprehensive set of requirements for operation of a lunar communications and navigation network capable of interoperating with other networks compliant with the Lunar Network (LunaNet) for services to the human exploration, lunar science, and space technology missions. LunaNet will start with a simple architecture of a few nodes to meet the needs of the early missions and evolve to meet the growing needs of a sustained lunar presence. All relay network services are not expected to be met by a single spacecraft platform, or node. The expectation is that the needs of NASA, its partners and other users will be met through a combination of interoperable systems provided by NASA, international partners, and commercial providers. Interoperability across this network-of-networks can be achieved through negotiation of mutually-agreed-upon standards that will be reflected in this document and in the specifications defined by other participants in the combined, cooperative lunar network.

LunaNet↗

Enabling Simulation Interoperability between International Standards in the Space Domain

Today, the design and development of space systems are conducted cooperatively by historical space agencies in this area such as NASA, ESA, Roscosmos, and JAXA together with their industrial partners. The space system lifecycle is characterized by high costs, uncertain conditions, and dangerous scenarios. To mitigate these issues, space agencies rely heavily on Modelling and Simulation as a key technology to support the analysis, design, and operation of space systems. To support large-scale distributed simulations, the scientific community has developed several standards to support the reuse and interoperability of simulation models such as IEEE 1516 High-Level Architecture (HLA), Real-time Platform Reference Federation Object Model (RPR FOM), Simulation Model Portability (SMP), and the novel Space Reference Federation Object Model (SpaceFOM). While the SpaceFOM standard has been specifically conceptualized for handling space systems, the other ones are more general-purpose and can be used to design and simulate generic complex systems. As a consequence, there is a lake of rules and guidelines to enable interoperability among these standards. The paper presents solutions and experiences for enabling interoperability and transferability of HLA, RPR FOM, and SMP simulation models with SpaceFOM.

Simulation↗

Interoperability Review of Wireless Hardware in Emergency Air-To-Ground Mesh Networks

The air-to-ground network has the goal of advancing the capabilities and versatility of communications in wildfire and emergency scenarios. To ensure compatibility and keep costs low for emergency services interoperability between hardware is an important step in development of the mesh network. For the purposes of this evaluation interoperability of hardware is described as the ability for hardware from different vendors to be interchangeable within the network with minimal initial setup and no functional change from an operator’s viewpoint. This report will also focus on the features and limitations in addition to the interoperability of the major wireless hardware systems core to the function of the proposed air-to-ground mesh network. The hardware systems involved are ADS-B receivers, 3GPP Sidelink devices, mesh radios, and commercial ISM band radios. For early testing the mesh radios will be in the 900 MHz frequency range using the DoodleLabs RM-1700-22W Mesh Rider Radio as the lab reference. This report will consider and categorize desirability of features, the amount of setup required before deployment, the effect on performance characteristics from nominal and maximum load, and the ability to interface with other vender devices.

Mesh Radio↗

Enabling Interoperability on PV Inverters Using IEC 61850

Inverter based distributed energy resources are integrated into distribution system at a fast pace. Distribution management systems, microgrid controllers, and other distributed assets need to communicate with each other for sensing and control of the different assets. Interoperability is critical to the ease of data exchange between different assets. This presentation will provide a background on interoperability and a laboratory implementation using IEC 61850. Specifically, this presentation will discuss the use of IEC 61850 7-420 to enable interoperability in PV inverter.

41 EE - Solar Energy Technologies Office (EE-4S)↗

Validation of Interconnection and Interoperability of Grid-Forming Inverters Sourced by Hydrogen Technologies in View of 100% Renewable Microgrids

Grid-forming assets are required in microgrids to act as voltage-frequency masters. These grid-forming assets can operate in two modes of operation: grid-following mode and grid-forming mode. In grid-following mode of operation, these assets will follow real power and reactive power setpoints and in grid-forming mode of operation these assets will follow voltage and frequency setpoints. Traditionally, diesel generators or natural gas-based generators are widely used to act as a voltage-frequency master. However, many utilities are aiming to replace generators with grid forming-inverters supplied by solar photovoltaics (PV), batteries or fuel cells. Since grid-forming assets need a long-term reliable energy source, fuel cells are a reasonable and viable choice to supply the grid-forming inverters, but some of the challenges facing the wide deployment of grid-forming fuel cell inverters need to be addressed. Specifically, in our proposed work, we aim to focus on the interconnection and interoperability requirements of grid-forming fuel cell inverters. Currently, state-of-the-art fuel cell inverters follow the general interconnection requirements of distributed energy resources (DERs) and general interoperability requirements of DERs, but these requirements were built with PV and battery systems in mind. Fuel cells have different operational requirements, and therefore these requirements need to be appropriately modified for the grid operators to use. These additional steps add to the investment and operational cost to the grid operators. Through the ARIES platform, this proposed project aims to bridge this gap and use power hardware-in-the-loop (PHIL) and controller hardware-in-the-loop (CHIL) experiments to inform the creation of open-source interconnection and interoperability information that can aid in faster and cheaper installation and operation of grid-forming fuel cell inverters.

grid-forming↗

Validation of Interconnection and Interoperability of Grid-Forming Inverters Sourced by Hydrogen Technologies in View of 100% Renewable Microgrids

Grid-forming assets are required in microgrids to act as voltage-frequency masters. These grid-forming assets can operate in two modes of operation: grid-following mode and grid-forming mode. In grid-following mode of operation, these assets will follow real power and reactive power setpoints and in grid-forming mode of operation these assets will follow voltage and frequency setpoints. Traditionally, diesel generators or natural gas-based generators are widely used to act as a voltage-frequency master. However, many utilities are aiming to replace generators with grid forming-inverters supplied by solar photovoltaics (PV), batteries or fuel cells. Since grid-forming assets need a long-term reliable energy source, fuel cells are a reasonable and viable choice to supply the grid-forming inverters, but some of the challenges facing the wide deployment of grid-forming fuel cell inverters need to be addressed. Specifically, in our proposed work, we aim to focus on the interconnection and interoperability requirements of grid-forming fuel cell inverters. Currently, state-of-the-art fuel cell inverters follow the general interconnection requirements of distributed energy resources (DERs) and general interoperability requirements of DERs, but these requirements were built with PV and battery systems in mind. Fuel cells have different operational requirements, and therefore these requirements need to be appropriately modified for the grid operators to use. These additional steps add to the investment and operational cost to the grid operators. Through the ARIES platform, this proposed project aims to bridge this gap and use power hardware-in-the-loop (PHIL) and controller hardware-in-the-loop (CHIL) experiments to inform the creation of open-source interconnection and interoperability information that can aid in faster and cheaper installation and operation of grid-forming fuel cell inverters.

controller hardware-in-the-loop↗

mzPeak: Designing a Scalable, Interoperable, and Future-Ready Mass Spectrometry Data Format

Advances in mass spectrometry (MS) instrumentation, such as higher resolution, faster scan speeds, and improved sensitivity, have significantly increased the volume and complexity of data. The growing adoption of imaging and ion mobility further amplifies these challenges across MS-based omics fields, including proteomics, metabolomics, and lipidomics. While these technologies unlock new possibilities, they also present significant challenges in data management, storage, and accessibility. Existing open formats, such as the XML-based community standards mzML and imzML, struggle to meet the demands of modern MS workflows due to their large file sizes, slow data access, and limited metadata support. Vendor-specific formats, while optimized for proprietary instruments, lack interoperability, comprehensive metadata support and long-term archival reliability. This white paper lays the groundwork for mzPeak, a next-generation community data format designed to address these challenges and support high-throughput, multi-dimensional MS workflows. By adopting a hybrid model that combines efficient binary storage for numerical data and both human and machine-readable metadata storage, mzPeak will reduce file sizes, accelerate data access, and offer a scalable, adaptable solution for evolving MS technologies. For researchers, mzPeak will enable enhanced interoperability across platforms, seamless support for complex workflows including ion mobility and MS imaging, and faster data access compared to existing community formats such as mzML. Its design will ensure data is managed in compliance with regulatory standards, essential for applications such as precision medicine and chemical safety, where long-term data integrity and accessibility are critical. For vendors, mzPeak provides a streamlined, open alternative to proprietary formats, reducing the burden of regulatory compliance while aligning with the industry's push for transparency and standardization. By offering a high-performance, interoperable solution, mzPeak positions vendors to meet customer demands for sustainable data management tools which will be able to handle emerging and future data types and workflows. mzPeak aspires to become the cornerstone of MS data management, empowering researchers, vendors, and developers to innovate and collaborate more effectively.

data formats↗

Quantum Chemistry Common Driver and Databases (QCDB) and Quantum Chemistry Engine (QCEngine): Automation and interoperability among computational chemistry programs

We report that community efforts in the computational molecular sciences (CMS) are evolving toward modular, open, and interoperable interfaces that work with existing community codes to provide more functionality and composability than could be achieved with a single program. The Quantum Chemistry Common Driver and Databases (QCDB) project provides such capability through an application programming interface (API) that facilitates interoperability across multiple quantum chemistry software packages. In tandem with the Molecular Sciences Software Institute and their Quantum Chemistry Archive ecosystem, the unique functionalities of several CMS programs are integrated, including CFOUR, GAMESS, NWChem, OpenMM, Psi4, Qcore, TeraChem, and Turbomole, to provide common computational functions, i.e., energy, gradient, and Hessian computations as well as molecular properties such as atomic charges and vibrational frequency analysis. Both standard users and power users benefit from adopting these APIs as they lower the language barrier of input styles and enable a standard layout of variables and data. These designs allow end-to-end interoperable programming of complex computations and provide best practices options by default.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

DLR Calculation Engine Interoperability Profile: A Project for the TOGETs Task Force

This document contains a detailed interoperability profile outlining how the components of the CIM can be used to implement DLR in support of the two use cases identified in the Use Case Document. An interoperability profile is defined by the Smart Electric Power Alliance (SEPA) as a document that “specifies standards-based requirements for interfaces or applications that are accepted by the user-community, testing authorities, and other stakeholders. It specifies configuration options within a standard’s requirements sufficient to deliver the desired level of interoperability and functionality.” To that end, this document is not in itself a standard, nor has it been approved by any formal body. Rather, it is an example of how to implement the CIM standard and has been reviewed by industry, including transmission operators and DLR vendors.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Report on the Second Catalog Interoperability Workshop

The events, resolutions, and recommendations of the Second Catalog Interoperability Workshop, held at JPL in January, 1988, are discussed. This workshop dealt with the issues of standardization and communication among directories, catalogs, and inventories in the earth and space science data management environment. The Directory Interchange Format, being constructed as a standard for the exchange of directory information among participating data systems, is discussed. Involvement in the Interoperability effort by NASA, NOAA, ISGS, and NSF is described, and plans for future interoperability considered. The NASA Master Directory prototype is presented and critiqued and options for additional capabilities debated.

Thieman, James R.↗

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↗

Enabling Interoperable Space Robots With the Joint Technical Architecture for Robotic Systems (JTARS)

Robots that operate independently of one another will not be adequate to accomplish the future exploration tasks of long-distance autonomous navigation, habitat construction, resource discovery, and material handling. Such activities will require that systems widely share information, plan and divide complex tasks, share common resources, and physically cooperate to manipulate objects. Recognizing the need for interoperable robots to accomplish the new exploration initiative, NASA s Office of Exploration Systems Research & Technology recently funded the development of the Joint Technical Architecture for Robotic Systems (JTARS). JTARS charter is to identify the interface standards necessary to achieve interoperability among space robots. A JTARS working group (JTARS-WG) has been established comprising recognized leaders in the field of space robotics including representatives from seven NASA centers along with academia and private industry. The working group s early accomplishments include addressing key issues required for interoperability, defining which systems are within the project s scope, and framing the JTARS manuals around classes of robotic systems.

Bradley, Arthur↗

The Challenges of Interoperable Data Discovery

The Global Change Master Directory (GCMD) assists the oceanographic community in data discovery and access through its online metadata directory. The directory also offers data holders a means to post and search their oceanographic data through the GCMD portals, i.e. online customized subset metadata directories. The Gulf of Maine Ocean Data Partnership (GoMODP) has expressed interest in using the GCMD portals to increase the visibility of their data holding throughout the Gulf of Maine region and beyond. The purpose of the Gulf of Maine Ocean Data Partnership (GoMODP) is to "promote and coordinate the sharing, linking, electronic dissemination, and use of data on the Gulf of Maine region". The participants have decided that a "coordinated effort is needed to enable users throughout the Gulf of Maine region and beyond to discover and put to use the vast and growing quantities of data in their respective databases". GoMODP members have invited the GCMD to discuss further collaborations in view of this effort. This presentation. will focus on the GCMD GoMODP Portal - demonstrating its content and use for data discovery, and will discuss the challenges of interoperable data discovery. interoperability among metadata standards and vocabularies will be discussed. A short overview of the lessons learned at the Marine Metadata Interoperability (MMI) metadata workshop held in Boulder, Colorado on August 9-11, 2005 will be given.

Meaux, Melanie F.↗

Finalizing the CCSDS Space-Data Link Layer Security Protocol: Setup and Execution of the Interoperability Testing

The protection of data transmitted over the space-link is an issue of growing importance also for civilian space missions. Through the Consultative Committee for Space Data Systems (CCSDS), space agencies have reacted to this need by specifying the Space Data-Link Layer Security (SDLS) protocol which provides confidentiality and integrity services for the CCSDS Telemetry (TM), Telecommand (TC) and Advanced Orbiting Services (AOS) space data-link protocols. This paper describes the approach of the CCSDS SDLS working group to specify and execute the necessary interoperability tests. It first details the individual SDLS implementations that have been produced by ESA, NASA, and CNES and then the overall architecture that allows the interoperability tests between them. The paper reports on the results of the interoperability tests and identifies relevant aspects for the evolution of the test environment.

Fischer, Daniel↗

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project: Advanced Collision Avoidance System for UAS (ACAS Xu) Interoperability White Paper Presentation

The Phase 1 DAA Minimum Operational Performance Standards (MOPS) provided requirements for two classes of DAA equipment: equipment Class 1 contains the basic DAA equipment required to assist a pilot in remaining well clear, while equipment Class 2 integrates the Traffic Alert and Collision Avoidance (TCAS) II system. Thus, the Class 1 system provides RWC functionality only, while the Class 2 system is intended to provide both RWC and Collision Avoidance (CA) functionality, in compliance with the Minimum Aviation System Performance (MASPS) for the Interoperability of Airborne Collision Avoidance Systems. The FAAs TCAS Program Office is currently developing Airborne Collision Avoidance System X (ACAS X) to support the objectives of the Federal Aviation Administrations (FAA) Next Generation Air Transportation System Program (NextGen). ACAS X has a suite of variants with a common underlying design that are intended to be optimized for their intended airframes and operations. ACAS Xu being is designed for UAS and allows for new surveillance technologies and tailored logic for platforms with different performance characteristics. In addition to Collision Avoidance (CA) alerting and guidance, ACAS Xu is being tuned to provide RWC alerting and guidance in compliance with the SC 228 DAA MOPS. With a single logic performing both RWC and CA functions, ACAS Xu will provide industry with an integrated DAA solution that addresses many of the interoperability shortcomings of Phase I systems. While the MOPS for ACAS Xu will specify an integrated DAA system, it will need to show compliance with the RWC alerting thresholds and alerting requirements defined in the DAA Phase 2 MOPS. Further, some functional components of the ACAS Xu system such as the remote pilots displayed guidance might be mostly references to the corresponding requirements in the DAA MOPS. To provide a seamless, integrated, RWC-CA system to assist the pilot in remaining well clear and avoiding collisions, several issues need to be addressed within the Phase 2 SC-228 DAA efforts. Interoperability of the RWC and CA alerting and guidance, and ensuring pilot comprehension, compliance and performance, will be a primary research area.

detect and avoid↗