SEARCH · Engineering Papers

Results for “Guideline documentation”

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 343 records · Page 19

All sources NASA NTRS DOE OSTI

NASA NTRS1979

Safety, reliability, maintainability and quality provisions for the Space Shuttle program

This publication establishes common safety, reliability, maintainability and quality provisions for the Space Shuttle Program. NASA Centers shall use this publication both as the basis for negotiating safety, reliability, maintainability and quality requirements with Shuttle Program contractors and as the guideline for conduct of program safety, reliability, maintainability and quality activities at the Centers. Centers shall assure that applicable provisions of the publication are imposed in lower tier contracts. Centers shall give due regard to other Space Shuttle Program planning in order to provide an integrated total Space Shuttle Program activity. In the implementation of safety, reliability, maintainability and quality activities, consideration shall be given to hardware complexity, supplier experience, state of hardware development, unit cost, and hardware use. The approach and methods for contractor implementation shall be described in the contractors safety, reliability, maintainability and quality plans. This publication incorporates provisions of NASA documents: NHB 1700.1 'NASA Safety Manual, Vol. 1'; NHB 5300.4(IA), 'Reliability Program Provisions for Aeronautical and Space System Contractors'; and NHB 5300.4(1B), 'Quality Program Provisions for Aeronautical and Space System Contractors'. It has been tailored from the above documents based on experience in other programs. It is intended that this publication be reviewed and revised, as appropriate, to reflect new experience and to assure continuing viability.

M S Malkin↗

NASA NTRS1982

Space station automation and autonomy - Advantages and problems

Design guidelines and functional systems being considered in the process of defining the configuration of the automated systems for a manned space station are outlined. The requirements are dependent on life-cycle costing and will set the necessary level of automation, as well as autonomy from outside commands. Fault protection routines have been largely devised according to successful programming on the Voyager spacecraft. An analysis is still needed of the housekeeping functions, including human necessities, machine functions, and mission objectives. A data base will result, defining the functions that have historically been delegated to either man or machine. Care must be taken to coordinate and document stationkeeping functions that might interface with mission functions. A data management system that is flexible with regards to changing mission objectives and to the MTBF factors, which will determine the level of technology to be used is required. Expert systems will be integrated into the automation to guide the machines in problem solving, including ensuring adequate management of the battery subsystem.

Carlisle, R. F.↗

NASA NTRS1987

Definition and testing of the hydrologic component of the pilot land data system

The specific aim was to develop within the Pilot Land Data System (PLDS) software design environment, an easily implementable and user friendly geometric correction procedure to readily enable the georeferencing of imagery data from the Advanced Very High Resolution Radiometer (AVHRR) onboard the NOAA series spacecraft. A software subsystem was developed within the guidelines set by the PLDS development environment utilizing NASA Goddard Space Flight Center (GSFC) Image Analysis Facility's (IAF's) Land Analysis Software (LAS) coding standards. The IAS current program development environment, the Transportable Applications Executive (TAE), operates under a VAX VMS operating system and was used as the user interface. A brief overview of the ICARUS algorithm that was implemented in the set of functions developed, is provided. The functional specifications decription is provided, and a list of the individual programs and directory names containing the source and executables installed in the IAF system are listed. A user guide is provided for the LAS system documentation format for the three functions developed.

Ragan, Robert M.↗

NASA NTRS2014

Integrated Medical Model Verification, Validation, and Credibility

The Integrated Medical Model (IMM) was designed to forecast relative changes for a specified set of crew health and mission success risk metrics by using a probabilistic (stochastic process) model based on historical data, cohort data, and subject matter expert opinion. A probabilistic approach is taken since exact (deterministic) results would not appropriately reflect the uncertainty in the IMM inputs. Once the IMM was conceptualized, a plan was needed to rigorously assess input information, framework and code, and output results of the IMM, and ensure that end user requests and requirements were considered during all stages of model development and implementation. METHODS: In 2008, the IMM team developed a comprehensive verification and validation (VV) plan, which specified internal and external review criteria encompassing 1) verification of data and IMM structure to ensure proper implementation of the IMM, 2) several validation techniques to confirm that the simulation capability of the IMM appropriately represents occurrences and consequences of medical conditions during space missions, and 3) credibility processes to develop user confidence in the information derived from the IMM. When the NASA-STD-7009 (7009) was published, the IMM team updated their verification, validation, and credibility (VVC) project plan to meet 7009 requirements and include 7009 tools in reporting VVC status of the IMM. RESULTS: IMM VVC updates are compiled recurrently and include 7009 Compliance and Credibility matrices, IMM VV Plan status, and a synopsis of any changes or updates to the IMM during the reporting period. Reporting tools have evolved over the lifetime of the IMM project to better communicate VVC status. This has included refining original 7009 methodology with augmentation from the NASA-STD-7009 Guidance Document. End user requests and requirements are being satisfied as evidenced by ISS Program acceptance of IMM risk forecasts, transition to an operational model and simulation tool, and completion of service requests from a broad end user consortium including Operations, Science and Technology Planning, and Exploration Planning. CONCLUSIONS: The VVC approach established by the IMM project of combining the IMM VV Plan with 7009 requirements is comprehensive and includes the involvement of end users at every stage in IMM evolution. Methods and techniques used to quantify the VVC status of the IMM have not only received approval from the local NASA community but have also garnered recognition by other federal agencies seeking to develop similar guidelines in the medical modeling community.

Validation↗

NASA NTRS2013

A Concept of Operations for an Integrated Vehicle Health Assurance System

This document describes a Concept of Operations (ConOps) for an Integrated Vehicle Health Assurance System (IVHAS). This ConOps is associated with the Maintain Vehicle Safety (MVS) between Major Inspections Technical Challenge in the Vehicle Systems Safety Technologies (VSST) Project within NASA s Aviation Safety Program. In particular, this document seeks to describe an integrated system concept for vehicle health assurance that integrates ground-based inspection and repair information with in-flight measurement data for airframe, propulsion, and avionics subsystems. The MVS Technical Challenge intends to maintain vehicle safety between major inspections by developing and demonstrating new integrated health management and failure prevention technologies to assure the integrity of vehicle systems between major inspection intervals and maintain vehicle state awareness during flight. The approach provided by this ConOps is intended to help optimize technology selection and development, as well as allow the initial integration and demonstration of these subsystem technologies over the 5 year span of the VSST program, and serve as a guideline for developing IVHAS technologies under the Aviation Safety Program within the next 5 to 15 years. A long-term vision of IVHAS is provided to describe a basic roadmap for more intelligent and autonomous vehicle systems.

Hunter, Gary W.↗

NASA NTRS2015

Data Recipes: Toward Creating How-To Knowledge Base for Earth Science Data

Both the diversity and volume of Earth science data from satellites and numerical models are growing dramatically, due to an increasing population of measured physical parameters, and also an increasing variety of spatial and temporal resolutions for many data products. To further complicate matters, Earth science data delivered to data archive centers are commonly found in different formats and structures. NASA data centers, managed by the Earth Observing System Data and Information System (EOSDIS), have developed a rich and diverse set of data services and tools with features intended to simplify finding, downloading, and working with these data. Although most data services and tools have user guides, many users still experience difficulties with accessing or reading data due to varying levels of familiarity with data services, tools, and or formats. The data recipe project at Goddard Earth Science Data and Information Services Center (GES DISC) was initiated in late 2012 for enhancing user support. A data recipe is a How-To online explanatory document, with step-by-step instructions and examples of accessing and working with real data (http:disc.sci.gsfc.nasa.govrecipes). The current suite of recipes has been found to be very helpful, especially to first-time-users of particular data services, tools, or data products. Online traffic to the data recipe pages is significant, even though the data recipe topics are still limited. An Earth Science Data System Working Group (ESDSWG) for data recipes was established in the spring of 2014, aimed to initiate an EOSDIS-wide campaign for leveraging the distributed knowledge within EOSDIS and its user communities regarding their respective services and tools. The ESDSWG data recipe group is working on an inventory and analysis of existing data recipes and tutorials, and will provide guidelines and recommendation for writing and grouping data recipes, and for cross linking recipes to data products. This presentation gives an overview of the data recipe activites at GES DISC and ESDSWG. We are seeking requirements and input from a broader data user community to establish a strong knowledge base for Earth science data research and application implementations.

data recipe↗

NASA NTRS2010

Notes on SAW Tag Interrogation Techniques

We consider the problem of interrogating a single SAW RFID tag with a known ID and known range in the presence of multiple interfering tags under the following assumptions: (1) The RF propagation environment is well approximated as a simple delay channel with geometric power-decay constant alpha >/= 2. (2) The interfering tag IDs are unknown but well approximated as independent, identically distributed random samples from a probability distribution of tag ID waveforms with known second-order properties, and the tag of interest is drawn independently from the same distribution. (3) The ranges of the interfering tags are unknown but well approximated as independent, identically distributed realizations of a random variable rho with a known probability distribution f(sub rho) , and the tag ranges are independent of the tag ID waveforms. In particular, we model the tag waveforms as random impulse responses from a wide-sense-stationary, uncorrelated-scattering (WSSUS) fading channel with known bandwidth and scattering function. A brief discussion of the properties of such channels and the notation used to describe them in this document is given in the Appendix. Under these assumptions, we derive the expression for the output signal-to-noise ratio (SNR) for an arbitrary combination of transmitted interrogation signal and linear receiver filter. Based on this expression, we derive the optimal interrogator configuration (i.e., transmitted signal/receiver filter combination) in the two extreme noise/interference regimes, i.e., noise-limited and interference-limited, under the additional assumption that the coherence bandwidth of the tags is much smaller than the total tag bandwidth. Finally, we evaluate the performance of both optimal interrogators over a broad range of operating scenarios using both numerical simulation based on the assumed model and Monte Carlo simulation based on a small sample of measured tag waveforms. The performance evaluation results not only provide guidelines for proper interrogator design, but also provide some insight on the validity of the assumed signal model. It should be noted that the assumption that the impulse response of the tag of interest is known precisely implies that the temperature and range of the tag are also known precisely, which is generally not the case in practice. However, analyzing interrogator performance under this simplifying assumption is much more straightforward and still provides a great deal of insight into the nature of the problem.

Barton, Richard J.↗

NASA NTRS1994

Endangered and potentially endangered wildlife on John F. Kennedy Space Center and faunal integrity as a goal for maintaining biological diversity

Buffer zones for space operations provide for a wildlife diversity unsurpassed among most federal facilities in the continental U.S. demonstrating the coexistence possible with one of man's greatest technological achievements. This document ranks 119 resident or migratory wildlife species that are endangered or declining. The ranking system herein was based on species' vulnerability to extinction and the relevance of Kennedy Space Center (KSC) for maintaining populations in the U.S. and Florida. One amphibian, 19 reptiles, 80 birds, and 19 mammals were considered endangered or declining. KSC is an integral area for regional species diversity being the focus of the Merritt Island/Cape Canaveral/Turnbull Ecosystem which is part of the Indian River Lagoon watershed, an estuary of national significance. Many species that use this system also use the nearby St. Johns River Basin ecosystem. These two ecosystems are biological corridors between temperate Carolinian and tropical/subtropical Caribbean biotic provinces. Threats to biological diversity on KSC were also reviewed. Traditional environmental assessments, resulting from environmental regulation guidelines, focus on environmental contaminants and habitat lost due to construction. However, this review suggested that small population sizes, isolation of populations, ecosystem and habitat fragmentation, road mortality, and other edge effects may represent more critical threats to biological diversity than the traditional topics.

Breininger, David R.↗

NASA NTRS2000

Hypergolic Propellant Safety Course

Under the sponsorship of the NASA Safety Training Center at the Johnson Space Center, a hypergolic propellant safety course has been developed. This is a 2-day course on guidelines for hypergolic propellant system design, materials selection, operations, storage, and transportation. Recognizing that numerous fuels and oxidizers can be hypergolic, this course is specific to the hydrazine family of fuels and nitrogen tetroxide and its variants. The objectives of the course are to enable the student to identify and evaluate the hazards of hypergolic propellants, and to understand the methods for controlling those hazards and responding to emergencies. The course covers properties and hazards of the hydrazines and oxidizers; design and operations in hypergolic facilities; materials selection for use in hypergol systems; storage vessels, piping, and component considerations; hypergol detection; fire fighting practices; operating and transportation principles and procedures; and emergency practices and considerations. A hazards analysis methodology is presented. Numerous references are provided and the applicability of certain regulatory documents is discussed. A brief overview of other propellants, including hydrogen peroxide, is given at the end of the course.

Rathgeber, Kurt A.↗

NASA NTRS2007

Step 1:Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Collision Avoidance

This document provides definition of technology human interface requirements for Collision Avoidance (CA). This was performed through a review of CA-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Access 5 CA work package were considered... Beginning with the HSI high-level functional requirement for CA, and CA technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge CA system status, and (2) the control capability needed by the pilot to obtain CA information and affect an avoidance maneuver. Fundamentally, these requirements provide the candidate CA technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how CA operations and functions should interface with the pilot to provide the necessary CA functionality to the UA-pilot system .Requirements and guidelines for CA are partitioned into four categories: (1) General, (2) Alerting, (3) Guidance, and (4) Cockpit Display of Traffic Information. Each requirement is stated and is supported with a rationale and associated reference(s).

Source record↗

NASA NTRS2005

Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Contingency Management

This document involves definition of technology interface requirements for Contingency Management. This was performed through a review of Contingency Management-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Contingency Management Work Package were considered. Beginning with HSI high-level functional requirements for Contingency Management, and Contingency Management technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of system failures and associated contingency procedures, and (2) the control capability needed by the pilot to obtain system status and procedure information. Fundamentally, these requirements provide the candidate Contingency Management technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Contingency Management operations and functions should interface with the pilot to provide the necessary Contingency Management functionality to the UA-pilot system. Requirements and guidelines for Contingency Management are partitioned into four categories: (1) Health and Status and (2) Contingency Management. Each requirement is stated and is supported with a rationale and associated reference(s).

Source record↗

NASA NTRS2005

Step 1: Human System Integration Pilot-Technology Interface Requirements for Weather Management

This document involves definition of technology interface requirements for Hazardous Weather Avoidance. Technology concepts in use by the Access 5 Weather Management Work Package were considered. Beginning with the Human System Integration (HIS) high-level functional requirement for Hazardous Weather Avoidance, and Hazardous Weather Avoidance technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of hazardous weather, and (2) the control capability needed by the pilot to obtain hazardous weather information. Fundamentally, these requirements provide the candidate Hazardous Weather Avoidance technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Hazardous Weather Avoidance operations and functions should interface with the pilot to provide the necessary Weather Management functionality to the UA-pilot system. Requirements and guidelines for Hazardous Weather Avoidance are partitioned into four categories: (1) Planning En Route (2) Encountering Hazardous Weather En Route, (3) Planning to Destination, and (4) Diversion Planning Alternate Airport. Each requirement is stated and is supported with a rationale and associated reference(s).

Source record↗

NASA NTRS2023

Commercial Smallsat Data Acquisition Program: Airbus U.S. Synthetic Aperture Radar Quality Assessment Summary

Quality assessment of the Airbus X-band Synthetic Aperture Radar (SAR) satellite products was conducted by the Commercial Smallsat Data Acquisition (CSDA) program’s radar subject matter experts, following the Joint NASA/ESA (European Space Agency) assessment draft guidelines. All three Airbus SAR spacecraft (TerraSAR-X, TanDEM-X, and PAZ) are based on the TerraSAR-X platform, and each have an active phased array antenna that is 4.8 x 0.7 m in the along-track and cross-track dimensions, respectively. TerraSAR-X and TanDEM-X are in a helical orbit, creating a bistatic imaging geometry, in addition to being capable of independent monostatic observations. The PAZ mission follows TerraSAR-X and TanDEM-X in the same 11-day orbit with a 5.5-day lag. TerraSAR-X and TanDEM-X are designed, developed, and operated through a Public-Private Partnership, while PAZ is a dual-use mission (civil and defense agencies), funded and owned by the Spanish Ministry of Defense and managed by Hisdesat (Hisdesat Servicios Estratégicos, S.A.), a Spanish private communications company. The assessment presented in this document is divided into two main parts: documentation review and the assessment of test datasets. The documentation review in sections 2.1 through 2.4 includes the assessment of the Airbus documentation provided to the CSDA evaluation team. The grading of these documents is given in columns 1-4 of the maturity matrix shown in section 1.1. Section 2.5 summarizes the evaluation performed by NASA using the data purchased through the CSDA program. The grading for this is given in the last column of the maturity matrix. Section 3 provides more detailed explanations on the methods and the results of the data analysis performed by NASA. Only the documents provided by Airbus for the evaluation were considered for the review. Additional documentation with more detailed description of the calibration and validation procedures may be available online but were not considered for this evaluation. The product information provided in the available documentation (RD-1, RD-2) and the product metadata together provided adequate information to work with the data. The product details in the metadata included the required information to work with the data in the common XML file format. Metrological traceability documentation was not provided to CSDA. All relevant characterization of the SAR system and data were provided, and the metadata include all relevant ancillary information. Documentation provided to CSDA included limited pre-flight and post-launch calibration information.

Batuhan Osmanoglu↗

NASA NTRSDate not supplied

Logistics Rates and Assumptions for Future Human Spaceflight Missions Beyond LEO

As NASA prepares for future human spaceflight missions with extended crew duration in destinations beyond low Earth orbit (LEO), the Agency has focused itself on understanding the drivers to sustainably support human life beyond Earth’s atmosphere. Future missions to deep space, the lunar surface, and eventually the Martian surface pose new challenges in ensuring the crew is sufficiently supplied with all necessary materials. To mitigate the risk of not delivering sufficient consumables and logistics for human spaceflight missions, NASA has examined past human space mission data and developed metabolic modeling to determine estimates for the crew consumption rates of fluids, solid consumables, and additional equipment needed. This paper is a compilation of guidelines, rates, and assumptions necessary to evaluate the logistics needs for future human exploration conceptual missions beyond LEO, providing a starting point and resource of information regarding usage rates and overall logistics supply planning for crewed exploration missions. Logistics represent all equipment and supplies not installed as part of the vehicle that are needed to support mission activities. Logistics can be further divided into specific categories, including consumables, maintenance items, spares, utilization, outfitting, as well as any packaging required. This paper will also provide use case examples of logistics needs to support human missions in deep space, including a conceptual lunar surface mission. The paper provides information necessary to calculate the mass and volume of known logistics for conceptual future human exploration missions beyond LEO. The assumptions in the paper are updated versions of previous assumptions made by the Agency and were derived from a number of sources, including International Space Station (ISS) historical usage and resupply rates, the Life Support Baseline Values and Assumptions Document (BVAD) 2022, Human Integration Design Handbook (HIDH) 2014, and data gathered from NASA human spaceflight programs and projects. The primary goal of the paper is to establish a set of consistent reference rates that multiple teams and groups can utilize to conduct logistics analysis and compare cases. This methodology is for initial estimates of conceptual human missions and does not take the place of detailed analysis for programs, nor does it provide requirements for programs.

Human Spaceflight↗

NASA NTRSDate not supplied

Logistics Rates and Assumptions for Future Human Spaceflight Missions Beyond LEO

Human Spaceflight↗

NASA NTRS2024

Survey of Methods for Assessing Safety Compliance of sUAS BVLOS Operations

To ensure the safety of small Unmanned Aircraft System (sUAS) Beyond Line of Sight (BVLOS) operations in the National Airspace System (NAS), the FAA offers a guideline on how sUAS operators can demonstrate compliance with FAA rules, including regulations, advisory circulars, policy statements, and acceptable means of compliance (AMOC), using a formal and top-down approach. According to FAA Advisory Circular 23.2010-1, the AMOC refers to “one method, but not the only method, to show compliance with a regulatory requirement.” It is common for regulations to include a performance and safety standard rather than a detailed design or operation requirement, which allows for flexibility in fulfilling the regulatory requirements while still achieving a predetermined level of safety. This technical report explores existing frameworks for sUAS BVLOS safety analysis. It begins by discussing how sUAS BVLOS operations can be strategically deconflicted and then discusses their hazards. The next step is to establish safety assessment methods commonly used by the aviation industry and the FAA, illustrate how these methods can be applied to several safety-critical air traffic systems, and list collision models that the FAA and industry use. This investigation documents the processes for assessing safety risks in sUAS BVLOS operations and will allow sUAS BVLOS operations to be assessed for safety compliance more efficiently.

sUAS BVLOS Operations↗

NASA NTRS2013

Shuttle Repair Tools Automate Vehicle Maintenance

Successfully building, flying, and maintaining the space shuttles was an immensely complex job that required a high level of detailed, precise engineering. After each shuttle landed, it entered a maintenance, repair, and overhaul (MRO) phase. Each system was thoroughly checked and tested, and worn or damaged parts replaced, before the shuttle was rolled out for its next mission. During the MRO period, workers needed to record exactly what needed replacing and why, as well as follow precise guidelines and procedures in making their repairs. That meant traceability, and with it lots of paperwork. In 2007, the number of reports generated during electrical system repairs was getting out of hand-placing among the top three systems in terms of paperwork volume. Repair specialists at Kennedy Space Center were unhappy spending so much time at a desk and so little time actually working on the shuttle. "Engineers weren't spending their time doing technical work," says Joseph Schuh, an electrical engineer at Kennedy. "Instead, they were busy with repetitive, time-consuming processes that, while important in their own right, provided a low return on time invested." The strain of such inefficiency was bad enough that slow electrical repairs jeopardized rollout on several occasions. Knowing there had to be a way to streamline operations, Kennedy asked Martin Belson, a project manager with 30 years experience as an aerospace contractor, to co-lead a team in developing software that would reduce the effort required to document shuttle repairs. The result was System Maintenance Automated Repair Tasks (SMART) software. SMART is a tool for aggregating and applying information on every aspect of repairs, from procedures and instructions to a vehicle s troubleshooting history. Drawing on that data, SMART largely automates the processes of generating repair instructions and post-repair paperwork. In the case of the space shuttle, this meant that SMART had 30 years worth of operations that it could apply to ongoing maintenance work. According to Schuh, "SMART standardized and streamlined many shuttle repair processes, saving time and money while increasing safety and the quality of repairs." Maintenance technicians and engineers now had a tool that kept them in the field, and because SMART is capable of continually evolving, each time an engineer put it to use, it would enrich the Agency-wide knowledge base. "If an engineer sees something in the work environment that they could improve, a repair process or a procedure, SMART can incorporate that data for use in future operations," says Belson.

Source record↗

NASA NTRS2016

Development and Use of Engineering Standards for Computational Fluid Dynamics for Complex Aerospace Systems

Computational fluid dynamics (CFD) and other advanced modeling and simulation (M&S) methods are increasingly relied on for predictive performance, reliability and safety of engineering systems. Analysts, designers, decision makers, and project managers, who must depend on simulation, need practical techniques and methods for assessing simulation credibility. The AIAA Guide for Verification and Validation of Computational Fluid Dynamics Simulations (AIAA G-077-1998 (2002)), originally published in 1998, was the first engineering standards document available to the engineering community for verification and validation (V&V) of simulations. Much progress has been made in these areas since 1998. The AIAA Committee on Standards for CFD is currently updating this Guide to incorporate in it the important developments that have taken place in V&V concepts, methods, and practices, particularly with regard to the broader context of predictive capability and uncertainty quantification (UQ) methods and approaches. This paper will provide an overview of the changes and extensions currently underway to update the AIAA Guide. Specifically, a framework for predictive capability will be described for incorporating a wide range of error and uncertainty sources identified during the modeling, verification, and validation processes, with the goal of estimating the total prediction uncertainty of the simulation. The Guide's goal is to provide a foundation for understanding and addressing major issues and concepts in predictive CFD. However, this Guide will not recommend specific approaches in these areas as the field is rapidly evolving. It is hoped that the guidelines provided in this paper, and explained in more detail in the Guide, will aid in the research, development, and use of CFD in engineering decision-making.

Lee, Hyung B.↗