Search NASA⌕ Search

SEARCH · Search NASA

Results for “Federated identity management”

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.

11 records
All sourcesNASA NTRSDOE OSTI
DOE OSTI2025

Analysis Facilities for the HL-LHC White Paper

This white paper presents the current status of the R&D for Analysis Facilities (AFs) and attempts to summarize the views on the future direction of these facilities. These views have been collected through the High Energy Physics (HEP) Software Foundation’s (HSF) Analysis Facilities forum (HSF Analysis Facilities Forum), established in March 2022, the Analysis Ecosystems II workshop (Analysis Ecosystems Workshop II), that took place in May 2022, and the WLCG/HSF pre-CHEP workshop (WLCG–HSF pre-CHEP Workshop), that took place in May 2023. The paper attempts to cover all the aspects of an analysis facility.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS2013

Identity Federation and Its Importance for NASA's Future: The SharePoint Extranet Pilot

My project at Kennedy Space Center (KSC) during the spring 2013 Project Management and Systems Engineering Internship was to functionalJy test and deploy the SharePoint Extranet system and ensure successful completion of the project's various lifecycle milestones as described by NASA Procedural Requirement (NPR) 7 120.7. I worked alongside NASA Project Managers, Systems Integration Engineers, and Information Technology (IT) Professionals to pilot this collaboration capability between NASA and its External Partners. The use of identity federation allows NASA to leverage externally-issued credentials of other federal agencies and private aerospace and defense companies, versus the traditional process of granting and maintaining full NASA identities for these individuals. This is the first system of its kind at NASA and it will serve as a pilot for the Federal Government. Recognizing the novelty of this service, NASA's initial approach for deployment included a pilot period where nearby employees of Patrick Air Force Base would assist in testing and deployment. By utilizing a credential registration process, Air Force users mapped their Air Force-issued Common Access Cards (CAC) to a NASA identity for access to the External SharePoint. Once the Air Force stands up an Active Directory Federation Services (ADFS) instance within their Data Center and establishes a direct trust with NASA, true identity federation can be established. The next partner NASA is targeting for collaboration is Lockheed Martin (LMCO), since they collaborate frequently for the ORION Program. Through the use of Exostar as an identity hub, LMCO employees will be able to access NASA data on a need to know basis, with NASA ultimately managing access. In a time when every dollar and resource is being scrutinized, this capability is an exciting new way for NASA to continue its collaboration efforts in a cost and resource effective manner.

Baturin, Rebecca R.↗
DOE OSTI2023

A step towards the final frontier: Lessons learned from acceptance testing of the first HPE/Cray EX 3000 system at ORNL

Summary In this article, we summarize the deployment of the Air Force Weather (AFW) HPC11 system at Oak Ridge National Laboratory (ORNL) including the process followed to successfully complete acceptance testing of the system. HPC11 is the first HPE/Cray EX 3000 system that has been successfully released to its user community in a federal facility. HPC11 consists of two identical 800‐node supercomputers, Fawbush and Miller, with access to two independent and identical lustre parallel file systems. HPC11 is equipped with Slingshot 10 interconnect technology and relies on the HPE Performance Cluster Manager software for system configuration. ORNL has a clearly defined acceptance testing process used to ensure that every new system deployed can provide the necessary capabilities to support user workloads. We worked closely with HPE and AFW to develop a set of tests that used the United Kingdom's Meteorological Office's Unified Model and 4‐dimensional variational data assimilation. We also included benchmarks and applications from the Oak Ridge Leadership Computing Facility portfolio to fully exercise the HPE/Cray programming environment and evaluate the functionality and performance of the system. Acceptance testing of HPC11 required parallel execution of each element on Fawbush and Miller. In addition, careful coordination was needed to ensure successful acceptance of the newly deployed lustre file systems alongside the compute resources. In this work, we present test results from specific system components and provide an overview of the issues identified, challenges encountered, and the lessons learned along the way.

Melesse Vergara, Verónica G.↗
DOE OSTI2021

A Step Towards the Final Frontier: Lessons Learned from Acceptance Testing of the First HPE/Cray EX 3000 System at ORNL

In this paper, we summarize the deployment of the Air Force Weather (AFW) HPC11 system at Oak Ridge National Laboratory (ORNL) including the process followed to successfully complete acceptance testing of the system. HPC11 is the first HPE/Cray EX 3000 system that has been successfully released to its user community in a federal facility. HPC11 consists of two identical 800-node supercomputers, Fawbush and Miller, with access to two independent and identical Lustre parallel file systems. HPC11 is equipped with Slingshot 10 interconnect technology and relies on the HPE Performance Cluster Manager (HPCM) software for system configuration. ORNL has a clearly defined acceptance testing process used to ensure that every new system deployed can provide the necessary capabilities to support user workloads. We worked closely with HPE and AFW to develop a set of tests that used the United Kingdom’s Meteorological Office’s Unified Model (UM) and 4DVAR. We also included benchmarks and applications from the Oak Ridge Leadership Computing Facility (OLCF) portfolio to fully exercise the HPE/Cray programming environment and evaluate the functionality and performance of the system. Acceptance testing of HPC11 required parallel execution of each element on Fawbush and Miller. In addition, careful coordination was needed to ensure successful acceptance of the newly deployed Lustre file systems alongside the compute resources. In this work, we present test results from specific system components and provide an overview of the issues identified, challenges encountered, and the lessons learned along the way.

Melesse Vergara, Veronica↗
DOE OSTI2025

Enabling end-to-end secure federated learning in biomedical research on heterogeneous computing environments with APPFLx

Facilitating large-scale, cross-institutional collaboration in biomedical machine learning (ML) projects requires a trustworthy and resilient federated learning (FL) environment to ensure that sensitive information such as protected health information is kept confidential. Specifically designed for this purpose, this work introduces APPFLx - a low-code, easy-to-use FL framework that enables easy setup, configuration, and running of FL experiments. APPFLx removes administrative boundaries of research organizations and healthcare systems while providing secure end-to-end communication, privacy-preserving functionality, and identity management. Furthermore, it is completely agnostic to the underlying computational infrastructure of participating clients, allowing an instantaneous deployment of this framework into existing computing infrastructures. Experimentally, the utility of APPFLx is demonstrated in two case studies: (1) predicting participant age from electrocardiogram (ECG) waveforms, and (2) detecting COVID-19 disease from chest radiographs. Here, ML models were securely trained across heterogeneous computing resources, including a combination of on-premise high-performance computing and cloud computing facilities. By securely unlocking data from multiple sources for training without directly sharing it, these FL models enhance generalizability and performance compared to centralized training models while ensuring data remains protected. In conclusion, APPFLx demonstrated itself as an easy-to-use framework for accelerating biomedical studies across organizations and healthcare systems on large datasets while maintaining the protection of private medical data.

Biomedical Research↗
NASA NTRSDate not supplied

Simulating Secure Data Exchange and Storage for Urban Air Mobility Environments

Urban Air Mobility (UAM) defines an environment for managing operations of vertical takeoff and landing (VTOL) and short takeoff and landing (STOL) vehicles in an urban environment. Within a UAM environment, UAM operators manage fleets of vehicles, relying on Providers of Services for UAM (PSUs) for managing flights in a region of airspace. Flight plan deconfliction is primarily performed by the Discovery and Synchronization Service (DSS), and the Federal Aviation Administration (FAA) maintains control over the UAM space via the FAA-Industry Exchange Protocol (FIDXP). UAM is a federated environment with many different entities owning and operating vehicles, PSUs, and other services. These entities often need to interoperate or access data generated by other organizations. This paper demonstrates the feasibility of using blockchain to facilitate a secure data exchange and storage for this flight information in a UAM environment. In particular, this paper is focused on flight plans and telemetry data. A blockchain network was developed with a set of smart contracts for managing relevant flight data. Hyperledger Fabric was chosen as it is performent, scalable, and allows organizations to reuse existing public key infrastructure (PKI) for identity management. A set of simulated UAM services were also developed. These services propose flight plans and negotiate with other UAM services for airspace access. All interactions between UAM services, as well as vehicle telemetry data, is recorded onto the blockchain. Vehicle telemetry data is generated by a vehicle flight simulation service. This paper successfully demonstrates the feasibility of using blockchain as a secure data exchange and storage mechanism in a UAM environment.

UAM↗
DOE OSTI2020

Accelerating Nuclear Facility Mission Completion Through an Improved Chemical Hazard Control Strategy - 20460

Code of Federal Regulation (CFR) 10 CFR 830, Nuclear Safety Management [1], explicitly identifies hazardous materials in addition to radioactive materials when establishing the scope of materials that must be evaluated in Hazard Category (HC) 1, 2, and 3 nuclear facilities. This inclusion has led to a near decade-long progression of more and more rigorous application of chemical hazard controls in these facilities. The progressive addition of more rigorous chemical hazard controls has occurred across the Department of Energy (DOE) Complex, having been driven by contractors and regulators alike. However, chemical hazards in other DOE facilities have been, and continue to be, controlled using traditional industrial safety centered strategies. Thus, identical chemical hazards are controlled using dramatically different approaches based solely on the facility type. Not only are the controls different, the analysis and derivation rigor and requirements are also significantly different. In particular, chemical control derivation and application in non-nuclear facilities are much less onerous than the comprehensive hazard analysis process used in nuclear facilities, even in circumstances in which chemicals are not initiators to, or do not exacerbate a nuclear event. While the derivation and control approaches used in these two types of facilities are disparate, the safety results are similarly effective based on a review of reported chemical events from 2014 through 2018. While both approaches achieve comparable safety outcomes, the approach used in nuclear facilities results in significantly greater preparation costs and implementation costs. Furthermore, the problem with the differing approach is not relegated to the control preparation and implementation burden. The operational impact of potentially unnecessary controls slows mission completion without a corresponding increase in safety, not to mention the dilution of the importance of Technical Safety Requirements. The proposed solution must first include a critical and thorough examination of DOE Complex and top-tier chemical industry chemical hazard control practices, coupled with a similar examination of the driving facility regulatory requirements. Results from the examination can then be used to fuel a bold departure from current chemical control practices in Hazard Category 1, 2, and 3 nuclear facilities. Development of an improved and consistent chemical hazard control process would follow, one that continues to ensure safety while accelerating mission completion and significantly reducing the burden associated with chemical hazard control development and implementation. The improved process must establish a hierarchy where radiological hazards are addressed using safety class and safety significant controls and chemical hazards are addressed using overarching safety management programs (with limited unique exceptions). The improved Hazard Category 1,2, and 3 nuclear facility chemical hazard control strategy, while compliant with 10 CFR 830 [1], would be founded on the requirements in 10 CFR 851, Worker Safety and Health Program [2], and the complementary DOE O 151.1D, Comprehensive Emergency Management System [3]. In this way, the Hazard Category 1, 2, and 3 nuclear facility chemical hazard control strategy would, wherever appropriate, be the same process used at other DOE Complex facilities. Ultimately, the improved process will maintain safety and significantly reduce costs and life cycle risk through faster mission completion. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
NASA NTRS1978

A New Look For Greenbelt

Greenbelt, Maryland, 12 miles from the nation's capital, is an efficiently planned model town and most of its 1600 homes are almost identical in appearance. Four of them, however, stand out from their neighbors; they have distinctive blue glass rooftop superstructures made up of a series of solar collectors. They are part of a NASA community aid program, a joint energy research project involving the Greenbelt housing cooperative and NASA's Goddard Space Flight Center, located near the community. Built in 1935, Greenbelt is one of three government-planned communities of President Franklin D. Roosevelt's first administration; the others are Greendale, Wisconsin and Greenhills, Ohio. The government built the towns to make available low-cost housing, provide employment for workers on relief in the Great Depression era, and to establish models designed to encourage construction of similar developments by private industry. In 1952, the residents of Greenbelt formed a nonprofit cooperative called Greenbelt Homes, Inc., which bought the dwellings, facilities and a large part of the land from the government. The homes are individually owned but collectively maintained by the co-op, with each owner paying a prorated share of utility and maintenance costs. Greenbelt residents are mostly in the low and medium income brackets, and one of every three families lives on a fixed retirement income. For that reason, the sharp escalation of fuel oil prices that began in 1973 imposed particular hardship on the co-op community. So Greenbelt Homes' management asked its NASA neighbor, Goddard Space Flight Center, for assistance in setting up a solar energy research project. The idea was to conduct a small scale demonstration to show what savings could be realized by solar heating Greenbelt homes, with an eye toward possible future expansion of solar energy systems as a means of combating rising fuel costs. Goddard undertook the project as part of the federal government's effort to research and demonstrate ways of conserving energy. The Center was well qualified for the assignment, having acquired extensive expertise in designing thermal control systems for satellites, which must maintain stable temperatures for successful operation.

Source record↗
NASA NTRS2014

Control and Non-Payload Communications Generation 1 Prototype Radio Flight Test Report

Unmanned aircraft (UA) represent a new capability that will provide a variety of services in the Government (public) and commercial (civil) aviation sectors. The growth of this potential industry has not yet been realized because of the lack of a common understanding of what is required to safely operate Unmanned Aircraft Systems in the National Airspace System (UAS in the NAS). The desire and ability to fly UA is of increasing urgency. The application of UA to perform national security, defense, scientific, and emergency management are driving the critical need for less restrictive access by UA to the NAS. Existing Federal Aviation Regulations, procedures, and technologies do not allow routine UA access to the NAS. Access to the NAS is hampered by challenges such as the lack of an onboard pilot to see and avoid other aircraft; the ability of a single pilot or operator to control multiple UA; the reliance on command and control (C2) links; the altitudes, speeds, and duration at which the aircraft fly; and the wide variation in UA size and performance. NASA is working with other Government agencies to provide solutions that reduce technical barriers and make access to the NAS routine. This goal will be accomplished through system-level integration of key concepts, technologies, or procedures and through demonstrations of these integrated capabilities in an operationally relevant environment. This project provides an opportunity to transition the acquired empirical data and knowledge to the Federal Aviation Administration and other stakeholders to help them define the requirements for routine UA access to the NAS.Radio communications channels for UA are currently managed through exceptions and use either Department of Defense frequencies for line-of-sight (LOS) and satellite-based communications links, low-power LOS links in amateur bands, or unlicensed Industrial/Scientific/Medical (ISM) frequencies. None of these frequency bands are designated for safety and regularity of flight. Only recently has radiofrequency (RF) spectrum been allocated by the International Telecommunications Union specifically for commercial UA C2, LOS communication (L-Band: 960 to 1164 MHz, and C-Band: 5030 to 5091 MHz). The safe and efficient integration of UA into the NAS requires the use of protected RF spectrum allocations and a new data communications system that is both secure and scalable to accommodate the potential growth of these new aircraft. Data communications for UA-referred to as control and non-payload communications (CNPC)-will be used to exchange information between a UA and a ground station (GS) to ensure safe, reliable, and effective UA flight operation. The focus of this effort is on validating and allocating new RF spectrum and data link communications to enable civil UA integration into the NAS. Through a cost-sharing cooperative agreement with Rockwell Collins, Inc., the NASA Glenn Research Center is exploring and performing the necessary development steps to realize a prototype UA CNPC system. These activities include investigating signal waveforms and access techniques, developing representative CNPC radio hardware, and executing relevant testing and validation activities. There is no intent to manufacture the CNPC end product, rather the goals are to study, demonstrate, and validate a typical CNPC system that will allow safe and efficient communications within the L-Band and C-Band spectrum allocations. The system is addressing initial "seed" requirements from RTCA, Inc., Special Committee 203 (SC-203) and is on a path to Federal Aviation Administration certification. This report provides results from the flight testing campaign of the Rockwell Collins Generation 1 prototype radio, referred hereafter as the "radio." The radio sets operate within the 960- to 977-MHz frequency band with both air and ground radios using identical hardware. Flight tests involved one aircraft and one GS. Results include discussion of aircraft flight paths and associated radio performance.

Shalkhauser, Kurt A.↗
DOE OSTI2025

DOE Repository Metadata Profile (DRMP): A Metadata Framework for Advancing Interoperability and AI Readiness Across Scientific Repositories

The Department of Energy (DOE) funds a diverse and distributed ecosystem of repositories that steward scientific data, publications, and software across its research programs, user facilities, and national laboratories. While significant progress has been made in standardizing dataset-level metadata, the metadata describing repositories themselves (their identity, governance, access interfaces, policies, and technical capabilities) remains inconsistent and fragmented across DOE-funded systems. This variability limits discoverability, interoperability, automated validation, and AI-driven analysis, all of which are increasingly essential for modern scientific workflows. To address this gap, the DOE Data Curation Working Group (DCWG) developed the DOE Repository Metadata Profile (DRMP). The DRMP is a practical, community-driven framework that defines how repositories can describe themselves in a consistent, machine-actionable, and scalable manner. The DRMP is not a new metadata schema. Instead, it is a mapping profile and structured element set capturing the essential characteristics of DOE repositories. It harmonizes repository-level metadata across six widely adopted community schemas: RE3Data; DCAT-US v3; Schema.org; Dublin Core; DataCite 4.6; and PREMIS 3.0. This harmonization eliminates reinvention and enables interoperability within DOE and across the broader scientific ecosystem. A core objective of the DRMP is to reduce burden on repositories by allowing them to reuse their existing metadata through a Rosetta-style crosswalk rather than redesigning local implementations. The profile introduces a three-level conformance model that supports incremental adoption: • Level 1 – Minimum Viable Record (MVR): foundational identification elements required for workflows, project registration, and basic repository presence. • Level 2 – Interoperable: structured metadata enabling alignment with national and international discovery systems. • Level 3 – AI-Ready: enhanced provenance, policy transparency, fixity, semantic context, and capabilities that support automated reasoning, model training governance, and machine-assisted curation. To support implementation, the DRMP includes JSON Schema definitions, OpenAPI patterns, and MCP templates that allow repositories to publish machine-readable metadata directly within existing platforms. These resources are modular and lightweight, enabling adoption without major architectural change. Adopting the DRMP enables repositories to: • Enhance discoverability and interoperability by aligning identifiers, classifications, and descriptive elements across widely used schema standards. • Support federated discovery and cross-registration across DOE systems, Data.gov, and international catalogs. • Enable AI agents and workflow orchestration systems to interpret repository-level metadata within the American Science Cloud (AmSC) through Model Context Protocol (MCP)-based context publication. • Demonstrate alignment with DOE’s open science, stewardship, and FAIR data priorities. This guidance represents a community-driven step forward. Through voluntary adoption and continued feedback, the DRMP advances a cohesive, machine-actionable description of DOE repositories that supports FAIR data practices, preparing the infrastructure for AI-enabled research, and strengthening the discoverability and reuse of DOE’s scientific outputs.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗
DOE OSTI2024

Innovating the next generation of commercial smart building software

Nearly 30% of commercial building energy use is wasted due to equipment faults and HVAC controls problems. The result is increased emissions, compromised comfort and productivity, and less reliable coordination of building power needs with a clean grid. The energy impact alone represents $17 billion in potential savings. Today’s smart building software provides a robust solution to address these operational deficiencies. Energy management and information systems (EMIS) are saving up to 9% on average, with two-year paybacks. They are being incorporated into energy management processes, commissioning services, and utility programs. As effective as they are, two barriers prevent even deeper benefits; limited personnel to fix problems once they are identified, and the expense and time to manually implement changes in control systems. In partnership with the research community, the EMIS industry is developing new capabilities to overcome these barriers. Moving beyond siloed products for either fault detection and diagnostics, or optimal control, these new capabilities empower users to not only automatically identify faults, but also to push corrective action, and control improvements to their buildings. In this paper, several areas for enhancements are documented: ‘one-time’ correction of faults such as setpoints, schedules, and economizer lockouts; short-term active testing for automated proportional integral derivative (PID) loop tuning and functional testing; and continuous supervisory control for demand flexibility and year-round efficiency. Results are presented from a pair of partner implementations out of a dozen providers integrating these enhancements into their products, including field tests from across the country, and insights into operator acceptance and integration into operations and maintenance practices.

Casillas, Armando↗