SEARCH · Engineering Papers

Results for “best practice”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 361 records · Page 20

All sources NASA NTRS DOE OSTI

DOE OSTI2025

Southwest Regional Partnership on Carbon Sequestration: Phase III (Final Scientific/Technical Report)

The Southwest Regional Partnership on Carbon Sequestration (SWP) is one of 7 regional partnerships formed in 2003 under the U.S. Department of Energy’s (DOE) Regional Carbon Sequestration Partnerships (RCSPs) initiative. The overall purpose of the initiative was to help determine and implement the technology, infrastructure, and regulations most appropriate to promote carbon storage in different regions of the country. Covering Arizona, Colorado, New Mexico, Oklahoma, Utah, and parts of Texas, Wyoming, and Kansas, the SWP evaluated regional carbon storage and utilization potential and focused on technologies and sites that could complement the region’s strong position in energy production. The project progressed through three phases: • Phase I (2003–2005): Characterized regional geologic formations and CO 2 sources, assessed sequestration potential, and identified pilot test sites. • Phase II (2005–2013): Conducted small-scale field tests to validate sequestration methods, including geologic and terrestrial projects. • Phase III (2008–2022): Demonstrated large-scale CO 2 injection at a commercial oil field to test monitoring, verification, and long-term storage strategies. This report covers Phase III. The final project site, the Farnsworth Unit (FWU) in Texas, provided real-world testing of reservoir characterization, monitoring, and risk evaluation tools and processes that could be used in any commercial scale carbon capture, utilization, and storage (CCUS) project. Extensive data collection and analysis helped refine best practices for reservoir characterization, injection monitoring, and storage verification. The SWP contributed to national databases, DOE best practice manuals, and regional geological assessments to support future sequestration efforts. Key lessons learned include the importance of robust data management, strategic site selection, regulatory navigation, and effective industry collaboration. The project’s findings will inform ongoing and future carbon storage initiatives. Task 1 (Regional Characterization) • The SWP continued to participate in national outreach efforts and NATCARB. • The SWP evaluated multiple potential sites before selecting the FWU as the primary field test location. Task 2 (Public Outreach and Education) • The SWP contributed to national databases, DOE best practice manuals, and regional geological assessments to support future sequestration efforts. Task 3 (Permitting and Regulatory Compliance) • The SWP ensured compliance with federal and state regulations, including National Environmental Policy Act (NEPA) requirements. • The SWP obtained all necessary permits for drilling, injection, and monitoring activities. Task 4 (Site Characterization and Planning) • The SWP developed work plans for four key activities: characterization, simulation, monitoring and verification, and risk evaluation. • The SWP collected and synthesized legacy data from multiple sources to build initial static geological models and dynamic reservoir models demonstrating project feasibility. • The SWP conducted an initial risk evaluation and developed mitigation plans. Task 5 (Field Operations and Data Collection) • The SWP drilled, logged, and cored three characterization wells to gather critical subsurface data. • The SWP conducted multiple geophysical surveys, including 3D seismic, crosswell seismic, and vertical seismic profiling, to improve reservoir characterization. Task 6 (Monitoring and Verification) • The SWP performed extensive geological characterization using data from characterization wells and seismic surveys. • The SWP established a surface monitoring network to track CO 2 flux in soil gas, groundwater chemistry, and near-surface atmospheric CO 2 levels. • The SWP built and refined reservoir models to study the effects of relative permeability on simulation behavior and improve calibration with experimental data. Task 7 (Risk Assessment and Model Refinement) • The SWP conducted multiple studies to evaluate reservoir integrity, predict CO 2 plume behavior and improve predictive modeling capabilities. • The SWP refined geological models and used them to enhance the accuracy of simulation models. • The SWP continued quantitative risk assessment of top-ranked risks and strengthened the link between qualitative and quantitative risk methodologies.

02 PETROLEUM↗

NASA NTRS2017

How Should Life Support Be Modeled and Simulated?

Why do most space life support research groups build and investigate large models for systems simulation? The need for them seems accepted, but are we asking the right questions and solving the real problems? The modeling results leave many questions unanswered. How then should space life support be modeled and simulated? Life support system research and development uses modeling and simulation to study dynamic behavior as part of systems engineering and analysis. It is used to size material flows and buffers and plan contingent operations. A DoD sponsored study used the systems engineering approach to define a set of best practices for modeling and simulation. These best practices describe a systems engineering process of developing and validating requirements, defining and analyzing the model concept, and designing and testing the model. Other general principles for modeling and simulation are presented. Some specific additional advice includes performing a static analysis before developing a dynamic simulation, applying the mass and energy conservation laws, modeling on the appropriate system level, using simplified subsystem representations, designing the model to solve a specific problem, and testing the model on several different problems. Modeling and simulation is necessary in life support design but many problems are outside its scope.

Jones, Harry W.↗

DOE OSTI2026

U.S. Department of Energy Energy to Communities Program: Moore Street Seniors, Inc., Building Survey

Per U.S. Department of Energy (DOE) Energy to Communities (E2C) Expert Match Program, National Laboratory of the Rockies (NLR) staff provided Technical Assistance (TA) to Moore Street Seniors, Inc., in Fairbanks, Alaska. NLR provided, within the TA scope of work, a list of Recommendations and Best Practices, as well as Data Analysis and Final Deliverable Development. NLR staff have provided the results within this report and several Energy Efficiency Considerations for Moore Street Seniors Inc. Window replacement considerations and best practices are listed in section 3.8. Building ventilation considerations and best practices are listed in section 3.9. A full list of Energy Efficiency Considerations is listed in section 3.10 of this report.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

DOE OSTI2022

International Radiological/Nuclear Training for Emergency Response - Major Public Events Virtual Workshop: Nuclear Security Planning and Operations (Day 3) [Slides]

This module will provide an overview of best practices for nuclear security planning requirements to include building a nuclear security plan and a concept of operations. It will introduce best practices for nuclear security planning to include the following: (1) Develop a Nuclear Security Plan, (2) Review 10 key elements of a Concept of Operations, (3) Estimate resources for an MPE, and (4) Capture lessons learned and best practices.

61 RADIATION PROTECTION AND DOSIMETRY↗

NASA NTRS2015

Risk Informed Philosophy: Using What We Fear to Lose to Guide Us to Success

When an organization sets out on a new effort, program, or project, one of the first steps undertaken is to understand the related requirements. Most often, these requirements come in the form of standards, directives, or other organizational processes, and are derived to meet a broad range of efforts, programs, and projects. The net result is that organizations or teams are forced to start with a maximum set of requirements and expend time and energy tailoring the set of requirements down to what is more appropriate for the effort, program, or project at hand. This presentation will present an alternate method for the application of requirements or best practices that is based upon the actual risks to the safety, performance, or success of the effort. This additive route for applying best practices and requirements also encourages an early exploration of the risks, thus yielding a better understanding of where resources should be applied. This presentation also extends this concept of risk-based application of best practices and requirements to the selection of organization-wide improvement or standardization efforts, such as Lean, Six Sigma, and Quality Management Systems.

Darpel, Scott↗

DOE OSTI2021

Federal Water Management Planning Manual

This Federal Water Management Resource Guide provides direction to Federal agencies on how optimize water use at Federal facilities, use water balance analysis methods, identify design elements and procurement best practices, and expand use of alternative water. It provides best practices for managing water to be considered when developing or improving an effective facility water management program. PNNL developed this guide for the Federal Energy Management Program (FEMP). FEMP was directed by the Council on Environmental Quality (CEQ) to develop a Federal Water Management Resource Guide per the Implementing Instructions for Executive Order (E.O.) 13834, Efficient Federal Operations. This document serves to satisfy this requirement in order to provide best water management practices within the Federal Government.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

DOE OSTI2021

Federal Water Management Planning Manual

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

DOE OSTI2024

Aligning Ukrainian Building Energy Codes with the EPBD

The aim of this report is to support Ukraine in revising its building energy codes in line with regulations laid out by the Energy Performance in Buildings Directive (EPBD). The main objectives are to i) provide valuable information to help Ukraine align its building energy codes with EPBD requirements, ii) advance the capacity of key stakeholders in Ukraine to develop new regulations based on robust technical methodologies and analysis, iii) summarize building energy codes best practices using examples from the EU and elsewhere, and iv) recommend steps Ukraine can take to improve its building energy code regulations and implementation. This report summarizes EPBD requirements for new buildings, and buildings undergoing major renovations, related to cost-optimal and Nearly Zero Energy Building (NZEB) requirements. This report highlights Ukraine’s progress in aligning it’s building energy codes with the aforementioned requirements and best practices regarding those requirements from the EU and internationally. Based on best practices and Ukraine’s current progress on requirements, recommendations are presented. A brief overview of the EPBD and building energy codes in Ukraine is also provided. Implementation related to building energy codes is touched upon as well. Potential next steps for Ukraine are outlined based on provided recommendations.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

DOE OSTI2022

Small Hydropower Interconnections: Small Hydropower in the United States

Small hydropower projects, which we define as generators below 20 MW in capacity have been the predominant source of hydropower growth over the past decade and create the most cost-effective and environmentally permissible avenues for new hydropower installation in the United States (DOE 2016; Johnson et al. 2018). Small hydropower developers across the United States have found that interconnecting these projects with the grid can be challenging due to unexpected costs and schedule overruns. Understanding the interconnection challenges and improving the process may allow more small hydropower projects to be successful. Noting these challenges, the U.S. Department of Energy Water Power Technologies Office enlisted Pacific Northwest National Laboratory (PNNL) and Oak Ridge National Laboratory (ORNL) to investigate the small hydropower interconnection landscape across the United States. To begin to analyze the existing interconnection processes and challenges facing small hydropower, the state of small hydropower development in the U.S. must first be described to understand the characteristics of the industry. The first in a series, this paper presents the state of small hydropower projects in the U.S. to describe their type, location, and size based on data extracted from the HydroSource database (ORNL 2020). The following papers in the series will detail the variety of state interconnection processes to connect power generators with the grid (“Small Hydropower Interconnections: State Interconnection Processes”), analyze these interconnection processes (“Small Hydropower Interconnections: Analysis of Interconnection Processes”), and present best practices in interconnection processes (“Small Hydropower Interconnections: Best Practices”) that will help overcome barriers to future small hydropower development.

13 HYDRO ENERGY↗

DOE OSTI2023

polishCLR: A Nextflow Workflow for Polishing PacBio CLR Genome Assemblies

Long-read sequencing has revolutionized genome assembly, yielding highly contiguous, chromosome-level contigs. However, assemblies from some third generation long read technologies, such as Pacific Biosciences (PacBio) continuous long reads (CLR), have a high error rate. Such errors can be corrected with short reads through a process called polishing. Although best practices for polishing non-model de novo genome assemblies were recently described by the Vertebrate Genome Project (VGP) Assembly community, there is a need for a publicly available, reproducible workflow that can be easily implemented and run on a conventional high performance computing environment. Here, we describe polishCLR (https://github.com/isugifNF/polishCLR), a reproducible Nextflow workflow that implements best practices for polishing assemblies made from CLR data. PolishCLR can be initiated from several input options that extend best practices to suboptimal cases. It also provides re-entry points throughout several key processes, including identifying duplicate haplotypes in purge_dups, allowing a break for scaffolding if data are available, and throughout multiple rounds of polishing and evaluation with Arrow and FreeBayes. PolishCLR is containerized and publicly available for the greater assembly community as a tool to complete assemblies from existing, error-prone long-read data.

59 BASIC BIOLOGICAL SCIENCES↗

DOE OSTI2025

Switchgrass Best Management Practices for Biofuel Production

Switchgrass is a perennial C 4 grass native to North America and broadly adaptable across the U.S. Its high productivity, low input requirements, and ability to deliver significant ecosystem services benefits, including carbon sequestration, soil conservation, and wildlife habitat, make it well-suited for cultivation on marginal lands. Achieving the U.S. Department of Energy’s projected potential of 1 billion dry tons of biomass annually by 2050 – with switchgrass contributing up to 230 million tons – will require a transition to large-scale, commercial production. This technical guide was developed to provide decision-makers with current best management practices (BMPs) for establishing, managing, and harvesting bioenergy switchgrass at scale on marginal lands across the U.S. Midwest and Great Plains. Drawing extensively on previous field research and insights from the five-year 'Next-Generation Feedstocks for the Emerging Bioeconomy' project – funded by the U.S. Department of Energy’s Bioenergy Technologies Office – this guide provides practical strategies for scaling up switchgrass production to meet the demands of the growing bioeconomy.

Lee, D.K.↗

NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

DOE OSTI2024

Preferred Practices Through a Project Template

In the realm of scientific software development, adherence to best practices is often advocated. However, implementing these can be challenging due to differing opinions. Certain aspects, such as software licenses and naming conventions, are typically left to the discretion of the development team. Our team has established a set of preferred practices, informed by, but not limited to, widely accepted best practices. These preferred practices are derived from our understanding of the specific contexts and user needs we cater to. To facilitate the dissemination of these practices among our team and foster standardization with collaborating domain scientists, we have created a project template for Python projects. This template serves as a platform for discussing the implementation of various decisions. This paper will succinctly delineate the components that constitute an effective project template and elucidate the advantages of consolidating preferred practices in such a manner.

Zhang, Chen↗

NASA NTRS2009

Integrated Risk and Knowledge Management Program -- IRKM-P

The NASA Exploration Systems Mission Directorate (ESMD) IRKM-P tightly couples risk management and knowledge management processes and tools to produce an effective "modern" work environment. IRKM-P objectives include: (1) to learn lessons from past and current programs (Apollo, Space Shuttle, and the International Space Station); (2) to generate and share new engineering design, operations, and management best practices through preexisting Continuous Risk Management (CRM) procedures and knowledge-management practices; and (3) to infuse those lessons and best practices into current activities. The conceptual framework of the IRKM-P is based on the assumption that risks highlight potential knowledge gaps that might be mitigated through one or more knowledge management practices or artifacts. These same risks also serve as cues for collection of knowledge particularly, knowledge of technical or programmatic challenges that might recur.

Lengyel, David M.↗

DOE OSTI2021

Cybersecurity Guide for Distributed Wind

Distributed wind sits at the intersection of grid-connected, off-grid and behind-the-meter cyber-physical electrical energy systems. The unique physical properties and communications requirements for distributed wind systems mean that there are unique cybersecurity considerations, but there is little to no existing guidance on best practices for cybersecurity. This document is intended to be a starting point for distributed wind stakeholders including manufacturers, installers and integrators, and operators (facility, aggregator, or utility). We discuss common distributed wind architectures and describe their role in the larger power system, pointing out some of the key connections to be aware of. Cybersecurity cannot exist in a vacuum, but rather must consider all the system and all its connections holistically. The role of distributed wind and the functions it can serve are described to gain understanding of the full range of capabilities. The purpose and application of relevant standards that may apply to certain distributed wind systems is presented. These standards may not apply to all installations, but even for systems that are not required to meet these standards they can be a good reference for best practices. A holistic threat perspective is used to describe the adversaries, threats, and potential impacts of cyberattacks, with special emphasis on what sets distributed wind systems apart from other distributed energy resources (DER). Finally, we present the recommendations for cybersecurity, both in terms of needs of the system and roles that specific stakeholders should fulfill. Distributed wind systems can come in a variety of architectures and applications, so there is no one-size-fits-all approach to cybersecurity. However, this document contains the relevant information for stakeholders to identify the cybersecurity needs of their system, refer to relevant standards, and apply best practices in a manner most consistent with their security and operational goals.

17 WIND ENERGY↗

DOE OSTI2022

Small Hydropower Interconnections: Analysis of Interconnection Processes

Small hydropower projects have faced the challenge of navigating the process to interconnect their generation source to electricity distribution and transmission grids. Small hydropower developers have found interconnection procedures to be opaque and ultimately result in unexpected cost surprises and long timelines. Noting these challenges, the U.S. Department of Energy Water Power Technologies Office enlisted Pacific Northwest National Laboratory (PNNL) and Oak Ridge National Laboratory (ORNL) to investigate the small hydropower interconnection landscape across the United States. After reviewing the status of small hydropower (“Small Hydropower Interconnections: Small Hydropower in the United States”) and the interconnection procedures across the United States (“Small Hydropower Interconnections: State Interconnection Processes”) in the first two white papers of this series, this paper uses recent data from small hydropower interconnection applications to benchmark the efficacy of the process. Using data from interconnection queues hosted by utilities, balancing authorities, independent system operators (ISOs), and regional transmission organizations (RTOs), this paper provides context for the costs, timelines, and types of upgrades required for small hydropower projects. Interconnection applications and study reports for small hydropower projects were analyzed to collect key pieces of information about the interconnection process, timeline, costs, and type of upgrades required for interconnection. Information sourced from the reports was entered into an Interconnection Benchmarking database (IBdb), which may be found in Appendix A.1. Information from this database was used to evaluate the performance and challenges associated with interconnecting small hydropower projects. This white paper presents a description of the sources contained in the interconnection database (Section 2.0), an analysis of the interconnection timeline (Section 3.0), an evaluation the cost of interconnection upgrades (Section 4.0), and a description of the types of infrastructure upgrades (Section 5.0). The final paper in this series (“Small Hydropower Interconnections: Best Practices”) will use the analysis described here to outline best practices for interconnection processes that will help overcome barriers to future small hydropower development.

13 HYDRO ENERGY↗

DOE OSTI2021

Recommendations for Distributed Energy Resource Patching

While computer systems, software applications, and operational technology (OT)/Industrial Control System (ICS) devices are regularly updated through automated and manual processes, there are several unique challenges associated with distributed energy resource (DER) patching. Millions of DER devices from dozens of vendors have been deployed in home, corporate, and utility network environments that may or may not be internet-connected. These devices make up a growing portion of the electric power critical infrastructure system and are expected to operate for decades. During that operational period, it is anticipated that critical and noncritical firmware patches will be regularly created to improve DER functional capabilities or repair security deficiencies in the equipment. The SunSpec/Sandia DER Cybersecurity Workgroup created a Patching Subgroup to investigate appropriate recommendations for the DER patching, holding fortnightly meetings for more than nine months. The group focused on DER equipment, but the observations and recommendations contained in this report also apply to DERMS tools and other OT equipment used in the end-to-end DER communication environment. The group found there were many standards and guides that discuss firmware lifecycles, patch and asset management, and code-signing implementations, but did not singularly cover the needs of the DER industry. This report collates best practices from these standards organizations and establishes a set of best practices that may be used as a basis for future national or international patching guides or standards.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

Data Validation for Hosting Capacity Analyses

The usefulness of Hosting Capacity Analysis (HCA) is dependent on users' confidence that the results accurately reflect grid conditions. This report provides the findings and recommendations from research, conducted by The National Renewable Energy Lab (NREL) and The Interstate Renewable Energy Council (IREC), into HCA data validation best practices. The goal is to provide utilities, regulators, and stakeholders best practices for HCA data validation procedures so that future HCA deployments avoid uncertainties and potential mistakes from earlier rollouts and provide useful and accurate data from the day they are published. Utilities can use this report to develop or refine their HCA data validation procedures. Regulators can use the report to inform their oversight of utilities' HCA data validation practices, while stakeholders can use it to evaluate the effectiveness of utility efforts.

14 SOLAR ENERGY↗