Search NASA⌕ Search

SEARCH · Search NASA

Results for “Environmental Management System (EMS)”

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.

39 records · Page 3
All sourcesNASA NTRSDOE OSTI
DOE OSTI2020

D and D Research on KM-IT Platform - 20494

The Knowledge Management Information Tool (KM-IT) is a web-based system developed to maintain and preserve the Department of Energy's (DoE's) knowledge base. The system was developed by Florida International University's Applied Research Center (FIU-ARC) with the support of the D and D community including the DOE Office of Environmental Management, and with the collaboration and support of the DoE's Energy Facility Contractors Group (EFCOG) and the former ALARA Centers at Hanford and Savannah. The KM-IT system is a community driven system tailored to serve the technical issues faced by the workforce across the DOE Complex. This KM-IT web-based interactive system is operational and available for use at www.dndkm.org and is currently comprised of the following modules: Web Crawler, Hotline, Technology, Hanford's ALARA Center Reports, Specialist Directory, Lessons Learned, Best Practices, Video/Picture Library, Vendors and Industry News. The Web Crawler dynamically searches through the KM-IT repository as well as the web and displays search results based on the search criteria. The Hotline allows registered users to post questions/problems related to D and D and to receive solutions from a subject-matter specialist. The Technology module serves as repository of D and D technologies and contains technology/ demonstration fact sheets and vendor information. D and D community members can add Lessons Learned, Best Practices, and Pictures/Videos to the D and D repository, after a formal approval process. The Vendor module provides a directory of commercial vendors who provide D and D related technologies, supplies, and services. KM-IT makes an excellent use of the knowledge that exists within the D and D community by allowing D and D project managers around the DOE complex to collaborate by sharing innovative ideas, past experiences, and practices and by maintaining a directory of subject matter specialists. FIU has developed the dedicated module on KM-IT platform to publish D and D research being performed at FIU. This module highlights current EM research efforts and activities in support of D and D being performed at FIU/SRNL associated with fixatives and intumescent products. FIU will expand this module to include the recent and current D and D research being performed across multiple DOE EM sites, national labs and universities. FIU will collaborate with SRNL, INL, ANL and other universities to explore and publish D and D research activities on KM-IT. As a result, the user community will have a centralized location to review new D and D related research across the DOE EM complex. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2020

Status Update on TRAC: A DOE-EM Tool for Tracking Groundwater Cleanup and Progress Toward Site Closure - 20245

The U.S. Department of Energy (DOE) Office of Environmental Management (EM) uses a customized, web-based mapping tool called TRAC (Tracking Restoration and Closure) to communicate information on plume sizes, remedial approaches, regulatory drivers, exit strategies, and long-term stewardship requirements at all sites within the DOE-EM complex. The web-based GIS story maps provide robust geospatial visualization of plumes at DOE sites using an intuitive interface that allows users to explore the plume maps, explanatory text, photographs, and video. This collection of story maps not only communicates information for each individual site, but also summarizes pertinent metrics on cleanup and remaining contaminants across all EM sites. This paper describes a new design within TRAC for communicating metrics on plume status, regulatory cleanup progress, and technology implementation. A principal benefit of TRAC is the ability to view individual pieces of data at a time, permitting targeted questions to be addressed, such as the status of regulatory decisions, site cleanup priorities, and site closure needs for each site within the DOE-EM complex. TRAC manages communication and supports decision-making through knowledge access, data and information transparency and traceability, and inclusive participation. It serves as a common resource that provides consistent information for DOE managers, site personnel, regulators and stakeholders. Because long-term stewardship of legacy waste sites requires ongoing coordination and communication among DOE, regulators, and stakeholders, TRAC can also be used to help transition EM sites to the Office of Legacy Management at site closure. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2024

Models, data, and scripts associated with “Prediction of Distributed River Sediment Respiration Rates using Community-Generated Data and Machine Learning”

This data package is associated with the publication “Prediction of Distributed River Sediment Respiration Rates using Community-Generated Data and Machine Learning’’ submitted to the Journal of Geophysical Research: Machine Learning and Computation (Scheibe et al. 2024). River sediment respiration observations are expensive and labor intensive to obtain and there is no physical model for predicting this quantity. The Worldwide Hydrobiogeochemisty Observation Network for Dynamic River Systems (WHONDRS) observational data set (Goldman et al.; 2020) is used to train machine learning (ML) models to predict respiration rates at unsampled sites. This repository archives training data, ML models, predictions, and model evaluation results for the purposes of reproducibility of the results in the associated manuscript and community reuse of the ML models trained in this project. One of the key challenges in this work was to find an optimum configuration for machine learning models to work with this feature-rich (i.e. 100+ possible input variables) data set. Here, we used a two-tiered approach to managing the analysis of this complex data set: 1) a stacked ensemble of ML models that can automatically optimize hyperparameters to accelerate the process of model selection and tuning and 2) feature permutation importance to iteratively select the most important features (i.e. inputs) to the ML models. The major elements of this ML workflow are modular, portable, open, and cloud-based, thus making this implementation a potential template for other applications. This data package is associated with the GitHub repository found at Please see the file level metadata (flmd; “sl-archive-whondrs_flmd.csv”) for a list of all files contained in this data package and descriptions for each. Please see the data dictionary (dd; “sl-archive-whondrs_dd.csv”) for a list of all column headers contained within comma separated value (csv) files in this data package and descriptions for each. The GitHub repository is organized into five top-level directories: (1) “input_data” holds the training data for the ML models; (2) “ml_models” holds machine learning models trained on the data in “input_data”; (3) “scripts” contains data preprocessing and postprocessing scripts and intermediate results specific to this data set that bookend the ML workflow; (4) “examples” contains the visualization of the results in this repository including plotting scripts for the manuscript (e.g., model evaluation, FPI results) and scripts for running predictions with the ML models (i.e., reusing the trained ML models); (5) “output_data” holds the overall results of the ML model on that branch. Each trained ML model resides on its own branch in the repository; this means that inputs and outputs can be different branch-to-branch. Furthermore, depending on the number of features used to train the ML models, the preprocessing and postprocessing scripts, and their intermediate results, can also be different branch-to-branch. The “main-*” branches are meant to be starting points (i.e. trunks) for each model branch (i.e. sprouts). Please see the Branch Navigation section in the top-level README.md in the GitHub repository for more details. There is also one hidden directory “.github/workflows”. This hidden directory contains information for how to run the ML workflow as an end-to-end automated GitHub Action but it is not needed for reusing the ML models archived here. Please the top-level README.md in the GitHub repository for more details on the automation.

13C↗