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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS1988

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.↗
NASA NTRS2002

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

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

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.↗
NASA NTRS2015

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

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

Draft LunaNet Interoperability Specification

This document, along with its companion documents, 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). LunaNet will include Earth ground stations and orbiting spacecraft and will provide services to 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, or node. The expectation is that the needs of 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 cooperative lunar network. This document was written and reviewed by NASA and the European Space Agency (ESA).

LunaNet↗
NASA NTRS2022

Draft LunaNet Interoperability Specification

This document, along with its companion documents, 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). LunaNet will include Earth ground stations and orbiting spacecraft and will provide services to 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, or node. The expectation is that the needs of 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 cooperative lunar network. This document was written and reviewed by NASA and the European Space Agency (ESA).

LunaNet↗
NASA NTRSDate not supplied

Interoperable Map Services with Performance Tuning for Earth Science Data through API-Tiles and Dynamic API-Styles

NASA’s Goddard Earth Sciences Data and Information Services Center (GES DISC) provides access to a wide range of global climate data from various satellite missions and models. However, the visualization and analysis of these data can be challenging due to their large volume, complex structure, and diverse formats. This study presents the implementation of interoperable map services (API-Maps) with performance tuning using API-Tiles and dynamic API-Styles. API-Maps is a standard for defining and exposing map services through RESTful (representational state transfer) APIs (application programming interfaces). API-Tiles is a technique for generating and delivering map tiles on demand from any data source. API-Styles is a method for dynamically applying styles to map tiles based on user preferences or data attributes. The use of API-Tiles and dynamic API-Styles enhances the performance and scalability of the map services, allowing for smooth and interactive visualization of large datasets. Two types of Earth Science data sources from the NASA GES DISC are used in the experiment: regularly gridded data, such as Global Precipitation Measurement (GPM) precipitation data, and low processing level data, such as low-level data of atmospheric composite measurements from the TROPOspheric Monitoring Instrument (TROPOMI) mission. Re-gridding of swath data (low level data - e.g. Level 2) of atmospheric composites (e.g. TROPOMI products, such as nitrogen dioxide, ozone and aerosol optical depth) is applied to enable the Web-based, interoperable, tiled, and styled mapping (rendering) services of such data. The results demonstrate the effectiveness of the proposed approach in providing fast and efficient access to Earth science data through interoperable map services.

Geographic Information System↗
NASA NTRSDate not supplied

Lunar Command and Control Interoperability (LuCCI) Project Overview

The Lunar Command and Control Interoperability (LuCCI) project was formed to address a gap in how Lunar Surface Systems (LSS) would interoperate across multiple programs, commercial partners, and international partners. The project objective is to define, prototype, integrate, and evaluate an interoperable lunar command, control, data, and software reference architecture to enable autonomy and informatics capability through common standards across LSS.

Communications↗
DOE OSTI2015

Interoperability format translation and transformation between IFC architectural design file and simulation file formats

Automatically translating a building architecture file format (Industry Foundation Class) to a simulation file, in one aspect, may extract data and metadata used by a target simulation tool from a building architecture file. Interoperability data objects may be created and the extracted data is stored in the interoperability data objects. A model translation procedure may be prepared to identify a mapping from a Model View Definition to a translation and transformation function. The extracted data may be transformed using the data stored in the interoperability data objects, an input Model View Definition template, and the translation and transformation function to convert the extracted data to correct geometric values needed for a target simulation file format used by the target simulation tool. The simulation file in the target simulation file format may be generated.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗
DOE OSTI2015

Interoperability format translation and transformation between IFC architectural design file and simulation file formats

Automatically translating a building architecture file format (Industry Foundation Class) to a simulation file, in one aspect, may extract data and metadata used by a target simulation tool from a building architecture file. Interoperability data objects may be created and the extracted data is stored in the interoperability data objects. A model translation procedure may be prepared to identify a mapping from a Model View Definition to a translation and transformation function. The extracted data may be transformed using the data stored in the interoperability data objects, an input Model View Definition template, and the translation and transformation function to convert the extracted data to correct geometric values needed for a target simulation file format used by the target simulation tool. The simulation file in the target simulation file format may be generated.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2017

System and methods of resource usage using an interoperable management framework

Generic rights expression language allowing interoperability across different computing environments including resource usage of different applications. A formal framework for usage management provides scaffolding upon which interoperable usage management systems can be built. Certain features of the framework are standardized, such as the operational semantics, including areas free of standards that necessitate choice and innovation to achieve a balance of flexibility and usability for interoperability in usage management systems.

97 MATHEMATICS AND COMPUTING↗
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↗
DOE OSTI2021

GMLC Survey of Distributed Energy Resource Interconnection and Interoperability Standards

This document reports on the Grid Modernization Laboratory Consortium effort to identify gaps in standards for the interconnection and interoperability of distributed energy resources (DERs). The project extended a 3-year period from 2017 to 2019. Under the work plan, the team identified standards and test procedures related to interconnection and interoperability, grouped under the broad headings of their primary applicable technology domain: automotive, responsive loads, photovoltaic inverters, inverter-based energy storage, machine-based DERs, and microgrids. The team then conducted a gap analysis by comparing the current standards to the expected future requirements needed for specific grid services. Overall, gaps could be any activity needed to harmonize requirements among standards development organizations, minimize conflicting requirements among technology domains, or streamline conformance test procedures.

24 POWER TRANSMISSION AND DISTRIBUTION↗
NASA NTRS2015

Exploring NASA GES DISC Data with Interoperable Services

Overview of NASA GES DISC (NASA Goddard Earth Science Data and Information Services Center) data with interoperable services: Open-standard and Interoperable Services Improve data discoverability, accessibility, and usability with metadata, catalogue and portal standards Achieve data, information and knowledge sharing across applications with standardized interfaces and protocols Open Geospatial Consortium (OGC) Data Services and Specifications Web Coverage Service (WCS) -- data Web Map Service (WMS) -- pictures of data Web Map Tile Service (WMTS) --- pictures of data tiles Styled Layer Descriptors (SLD) --- rendered styles.

Giovanni↗
NASA NTRS2014

IT Labs Proof-of-Concept Project: Technical Data Interoperability (TDI) Pathfinder Via Emerging Standards

No known system is in place to allow NASA technical data interoperability throughout the whole life cycle. Life Cycle Cost (LCC) will be higher on many developing programs if action isn't taken soon to join disparate systems efficiently. Disparate technical data also increases safety risks from poorly integrated elements. NASA requires interoperability and industry standards, but breaking legacy ways is a challenge.

Interoperability↗
NASA NTRS2017

Ensuring Interoperability between UAS Detect-and-Avoid and Manned Aircraft Collision Avoidance

The UAS community in the United States has identified the need for a collision avoidance region in which UAS Detect-and-Avoid (DAA) vertical guidance is restricted to preclude interoperability issues with manned aircraft collision avoidance system vertical resolution advisories (RAs). This paper documents the process by which the collision avoidance region was defined. Three candidate definitions were evaluated on 1.3 million simulated pairwise encounters between UAS and manned aircraft covering a wide range of horizontal and vertical closure rates, angles, and miss distances. They were evaluated with regard to UAS DAA interoperability with manned aircraft collision avoidance systems in terms of: 1) the primary objective of restricting DAA vertical guidance before RAs when the aircraft are close, and 2) the secondary objective of avoiding unnecessary restrictions of DAA vertical guidance at a DAA alert when the aircraft are further apart. The collision avoidance region definition that fully achieves the primary objective and best achieves the secondary objective was recommended to and accepted by the UAS community in the United States. By this definition, UAS and manned aircraft are in the collision avoidance region--during which DAA vertical guidance is restricted--when the time to closest point of approach is less than 50 seconds and either the time to co-altitude is less than 50 seconds or the current vertical separation is less than 800 feet.

collision avoidance↗