Search NASA⌕ Search

SEARCH · Search NASA

Results for “Interoperable interfaces”

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
All sourcesNASA NTRSDOE OSTI
DOE OSTI2021

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↗
NASA NTRS1990

Interoperability among Space Station Freedom data systems - A field test of standards

A development status evaluation is presented for NASA efforts toward the achievement of interoperability among Space Station Freedom (SSF) data systems, despite the complexity created by the number and wide distribution of such systems, the intensive international participation, and the use of time-phased development cycles. Four areas have been identified as essential: communications interoperability, data interoperability, and crew and payload interface interoperability. Accelerated efforts are needed to define and refine detailed interface designs before developments by each of the SSF's international partners come to take fundamentally incompatible courses.

Whitelaw, Virginia A.↗
NASA NTRS2022

International Space Power System Interoperability Standards (ISPSIS)

This International Space Power System Interoperability Standards(ISPSIS) is the result of collaborations within the International Space Station (ISS) and Gateway memberships to establish interoperable interfaces, terminology, and techniques, to facilitate collaborative endeavors of space exploration in cislunar and deep space environments. These standards are available for international and commercial partnerships. Standards that are established and internationally recognized have been selected where possible to enable a variety of providers. Increasing hardware commonality among providers while decreasing unique configurations has the potential to reduce the traditional barriers in space exploration: overall mass and volume required to execute a mission. Standardizing interfaces reduces the scope of the development effort. The information within this document represents a set of parameters, which if accommodated in the system architecture support greater efficiencies, promote cost savings, and increase the probability of mission success. These standards are not intended to specify system details needed for implementation nor do they dictate design features behind the interface; specific requirements will be defined in unique documents.

David James Sadey↗
NASA NTRS2002

CAD Services: an Industry Standard Interface for Mechanical CAD Interoperability

Most organizations seek to design and develop new products in increasingly shorter time periods. At the same time, increased performance demands require a team-based multidisciplinary design process that may span several organizations. One approach to meet these demands is to use 'Geometry Centric' design. In this approach, design engineers team their efforts through one united representation of the design that is usually captured in a CAD system. Standards-based interfaces are critical to provide uniform, simple, distributed services that enable the 'Geometry Centric' design approach. This paper describes an industry-wide effort, under the Object Management Group's (OMG) Manufacturing Domain Task Force, to define interfaces that enable the interoperability of CAD, Computer Aided Manufacturing (CAM), and Computer Aided Engineering (CAE) tools. This critical link to enable 'Geometry Centric' design is called: Cad Services V1.0. This paper discusses the features of this standard and proposed application.

Claus, Russell↗
DOE OSTI2017

Connected Lighting System Interoperability Study Part 1: Application Programming Interfaces

First in a series of studies that focuses on interoperability as realized by the use of Application Programming Interfaces (APIs), explores the diversity of such interfaces in several connected lighting systems; characterizes the extent of interoperability that they provide; and illustrates challenges, limitations, and tradeoffs that were encountered during this exploration.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
NASA NTRS2007

Architecting the Communication and Navigation Networks for NASA's Space Exploration Systems

NASA is planning a series of short and long duration human and robotic missions to explore the Moon and then Mars. A key objective of the missions is to grow, through a series of launches, a system of systems communication, navigation, and timing infrastructure at minimum cost while providing a network-centric infrastructure that maximizes the exploration capabilities and science return. There is a strong need to use architecting processes in the mission pre-formulation stage to describe the systems, interfaces, and interoperability needed to implement multiple space communication systems that are deployed over time, yet support interoperability with each deployment phase and with 20 years of legacy systems. In this paper we present a process for defining the architecture of the communications, navigation, and networks needed to support future space explorers with the best adaptable and evolable network-centric space exploration infrastructure. The process steps presented are: 1) Architecture decomposition, 2) Defining mission systems and their interfaces, 3) Developing the communication, navigation, networking architecture, and 4) Integrating systems, operational and technical views and viewpoints. We demonstrate the process through the architecture development of the communication network for upcoming NASA space exploration missions.

Bhassin, Kul B.↗
DOE OSTI2020

Reference Interoperability Procurement Language

Achieving interoperability involves reaching agreement on common interfaces and promoting interoperability through performance specifications. Effective integration practices are a simple, effective, and direct way of addressing the challenge. By deciding on an integration approach with well-defined interfaces and selecting systems and devices that conform to that approach and choosing integrators that have experience implementing the chosen approach, many problems can be avoided. No integration effort is seamless but by specifying interoperability requirements during the procurement process typical problems from ad hoc approaches can be avoided or reduced. By continuing this approach to its conclusion at the end of the procurement process, these same interoperability requirements may lead themselves to specified performance criteria that can be used to measure interoperability during implementation. The contractual language may contain performance incentives and penalties tied to these requirements as appropriate.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
DOE OSTI2017

XPRESS: eXascale PRogramming Environment and System Software

The XPRESS project is the research and development of a complete software architecture for Exascale computing. The four major R&D thrusts include: 1) an Exascale lightweight kernel operating system (LXK), based on the Kitten operating system (OS), to manage billion way hardware parallelism, management of faults and power, management of global virtual name space, and other features of future system architectures; 2) a runtime system (HPX-5), co-designed with LXK, based on the ParalleX execution model that supports dynamic resource management and task scheduling; 3) system interfaces for interoperability between the runtime system and both the OS and the runtime system (RIOS); 4) compilation strategies and systems to translate MPI and OpenMP legacy codes to a form that can be run with performance at least as good as a native code implementation. The software architecture development has been driven by performance evaluation of mini-applications developed at Department of Energy Co-Design Centers as well as ancillary in-house developed applications and benchmarks. Research on the ParalleX execution model has been driven by the development of formal semantics and model checkers for the execution model. The major components of the software architecture are: ParalleX execution model – guiding principles for co-design of components of the system stack with advances in locality management and task prioritization through introspection; HPX runtime system – support of application dynamic adaptive resource management, task scheduling, and introspective control policies; LXK operating system – lightweight kernel operating system for order-constant scalability and low/no noise to manage resources; RIOS – a realm of Exascale system operation unique in the XPRESS project that includes the relationship between the new generation of lightweight kernel operating systems and runtime system software; XPI advanced programming model – intermediate form and low-level (readable) programming interface reflecting the ParalleX model, providing a target for source-to- source high level parallel language translation, and supporting early direct programming experimentation and measurement; Performance models & metrics – providing parameters and their mutual sensitivities to guide co-design and quantify operational behavior; Legacy migration – ensuring seamless transition of legacy codes and programming methods to the future generation of ParalleX-based Exascale systems; . Experiments and evaluation – critical to determining degree of effectiveness and likelihood of ultimate success as well as guiding corrective design changes to achieve DOE objectives; and Applications – collaborations with Co-Design Centers and other mission critical codes. The exemplar implementation of the ParalleX execution model, HPX-5, has been released along with five fully ported applications (LULESH, HPCG, SSSP, WAMR, and DASHMM) and multiple microbenchmarks. Using these applications, the system architecture demonstrated dynamic load balancing through active migration, legacy code migration, and data-driven approaches to for graph-like applications. Crucially for Exascale and billion way parallelism, the needs and patterns of irregular applications in HPX-5 were addressed using local flow control rather than relying on globally synchronized data structures.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2022

IRES Microgrid Energy Integration Report Version 1.0

This report presents technical information and guidance for the planned Integrated Renewable Energy System (IRES) microgrid project. This deployment of the microgrid and its associated assets was initiated in the beginning of 2022 at the Marine and Coastal Research Laboratory (MCRL) facility of Pacific Northwest National Laboratory (PNNL)-Sequim, Washington. The information in the report is organized under two main focus areas: electrical power interface, or interconnection, information of planned IRES assets; and communication and control interface, or interoperability, information of the planned IRES assets. The information will provide technical input for the development of the IRES microgrid controller technical specification, and also provide input for PNNL’s evaluation of adequacy of the electrical service infrastructure at MCRL to support the IRES project and help identify any gaps that will require facility-based upgrades. From an R&D aspect, this study and report will build on PNNL’s research and development work relating to energy storage (ES) codes and standards (C&Ss), including hybrid systems, performed on behalf of the Department of Energy (DOE) Office of Electricity (OE) ES. The current state of C&Ss for advanced technologies and their application, including microgrid-based technology is limited. For cases where formal standards issued by recognized Standards Developing Organizations do not yet exist, guidance is provided based on emerging best practices, including industry-group references that can be leveraged for microgrid technology which is in its early stages of development and use.

24 POWER TRANSMISSION AND DISTRIBUTION↗
DOE OSTI2024

Energy Services Interface: Architecture, Requirements, and Agreements

This report continues and extends the development of the Energy Services Interface (ESI) that recently has been led by the U.S. Department of Energy’s Grid Modernization Laboratory Consortium. The ESI is intended to facilitate the coordination of multiple, flexible energy resources that work in tandem to satisfy grid objectives by using performance attributes encoded within an ESI Service Template. The ESI relies on a pair of interfaces, representing the service requestor (the consumer of a service) and a service provider (who manages its resources per the agreed performance attributes) to achieve what is commonly known as a “grid service”. Due to its performance-driven approach, the ESI is hypothesized to be able to satisfy all common grid needs via only six common ESI service types. This report first reviews the status of ESI development, including its fundamental tenets. The report makes three important contributions to ESI development: First, it recognizes the similarity between service level agreements and the contract-like agreements that would be needed between energy service requestors and providers and recommends that ESI service agreements be modeled after the web services agreement specification. Second, whereas prior development efforts had focused on a flat, five-stage lifecycle, this report asserts that the ESI should have three behavioral layers in its architecture—the discovery, agreement, and service layers. Finally, this report offers concrete requirements that should be useful toward the development of the service requestors’ and service providers’ respective communications interfaces.

24 POWER TRANSMISSION AND DISTRIBUTION↗
NASA NTRS2009

Space Communications and Navigation (SCaN) Network Simulation Tool Development and Its Use Cases

In this work, we focus on the development of a simulation tool to assist in analysis of current and future (proposed) network architectures for NASA. Specifically, the Space Communications and Navigation (SCaN) Network is being architected as an integrated set of new assets and a federation of upgraded legacy systems. The SCaN architecture for the initial missions for returning humans to the moon and beyond will include the Space Network (SN) and the Near-Earth Network (NEN). In addition to SCaN, the initial mission scenario involves a Crew Exploration Vehicle (CEV), the International Space Station (ISS) and NASA Integrated Services Network (NISN). We call the tool being developed the SCaN Network Integration and Engineering (SCaN NI&E) Simulator. The intended uses of such a simulator are: (1) to characterize performance of particular protocols and configurations in mission planning phases; (2) to optimize system configurations by testing a larger parameter space than may be feasible in either production networks or an emulated environment; (3) to test solutions in order to find issues/risks before committing more significant resources needed to produce real hardware or flight software systems. We describe two use cases of the tool: (1) standalone simulation of CEV to ISS baseline scenario to determine network performance, (2) participation in Distributed Simulation Integration Laboratory (DSIL) tests to perform function testing and verify interface and interoperability of geographically dispersed simulations/emulations.

Jennings, Esther↗
DOE OSTI2025

Alquimia v1.0: a generic interface to biogeochemical codes – a tool for interoperable development, prototyping and benchmarking for multiphysics simulators

Alquimia v1.0 is a generic interface to geochemical solvers that facilitates development of multiphysics simulators by enabling code coupling, prototyping and benchmarking. The interface enforces the function arguments and their types for setting up, solving, serving up output data and carrying out other common auxiliary tasks while providing a set of structures for data transfer between the multiphysics code driving the simulation and the geochemical solver. Alquimia relies on a single-cell approach that permits operator splitting coupling and parallel computation. We describe the implementation in Alquimia of two widely used open-source codes that perform geochemical calculations: PFLOTRAN and CrunchFlow. We then exemplify its use for the implementation and simulation of reactive transport in porous media by two open-source flow and transport simulators: Amanzi and ParFlow. We also demonstrate its use for the simulation of coupled processes in novel multiphysics applications including the effect of multiphase flow on reaction rates at the pore scale with OpenFOAM, the role of complex biogeochemical processes in land surface models such as the E3SM Land Model (ELM) and the impact of surface–subsurface hydrological interactions on hydrogeochemical export from watersheds with the Advanced Terrestrial Simulator (ATS). These applications make it apparent that the availability of a well-defined yet flexible interface has the potential to improve the software development workflow, freeing up resources to focus on advances in process models and mechanistic understanding of coupled problems.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗
DOE OSTI2024

Guide to Developing Energy Services Interfaces

This document provides guidance to develop communications interfaces that are highly interoperable and adhere to a set of energy services interface (ESI) principles. It can be applied in the context of information and communications technology interface standards and implementation profiles that enable the integration of a facility with responsive distributed energy resources (DER) into an electric power system consistent with the fundamental ESI principles. In this context, a DER facility may consist of a single DER with a communicating controller or may be as complex as a microgrid campus with several buildings and many DERs. This document is not a technical interface standard, but the requirements described can be used to check that existing, augmented, or new interface standards meet the interoperability requirements of the ESI concept. In this way, this guide for the ESI specification can support future advancements in developing interoperability standards and implementation profiles. The intended audience for this document is DER integration practitioners and ecosystem groups that are in the business of developing and implementing communications interfaces for DER integration. It is intended that these groups apply the information and processes in this document to develop communications standards and implementation profiles that are consistent with fundamental ESI principles.

2030.5↗
DOE OSTI2025

A Grassroots Network and Community Roadmap for Interconnected Autonomous Science Laboratories for Accelerated Discovery

Scientific discovery is being revolutionized by AI and autonomous systems, yet current autonomous laboratories remain isolated islands unable to collaborate across institutions. We present the Autonomous Interconnected Science Lab Ecosystem (AISLE), a grassroots network transforming fragmented capabilities into a unified system that shorten the path from ideation to innovation to impact and accelerates discovery from decades to months. AISLE addresses five critical dimensions: (1) cross-institutional equipment orchestration, (2) intelligent data management with FAIR compliance, (3) AI-agent driven orchestration grounded in scientific principles, (4) interoperable agent communication interfaces, and (5) AI/ML-integrated scientific education. By connecting autonomous agents across institutional boundaries, autonomous science can unlock research spaces inaccessible to traditional approaches while democratizing cutting-edge technologies. This paradigm shift toward collaborative autonomous science promises breakthroughs in sustainable energy, materials development, and public health.

Ferreira da Silva, Rafael [Oak Ridge National Labo↗