Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “corrective action 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.

214 records · Page 12

General purpose architecture for intelligent computer-aided training

An intelligent computer-aided training system having a general modular architecture is provided for use in a wide variety of training tasks and environments. It is comprised of a user interface which permits the trainee to access the same information available in the task environment and serves as a means for the trainee to assert actions to the system; a domain expert which is sufficiently intelligent to use the same information available to the trainee and carry out the task assigned to the trainee; a training session manager for examining the assertions made by the domain expert and by the trainee for evaluating such trainee assertions and providing guidance to the trainee which are appropriate to his acquired skill level; a trainee model which contains a history of the trainee interactions with the system together with summary evaluative data; an intelligent training scenario generator for designing increasingly complex training exercises based on the current skill level contained in the trainee model and on any weaknesses or deficiencies that the trainee has exhibited in previous interactions; and a blackboard that provides a common fact base for communication between the other components of the system. Preferably, the domain expert contains a list of 'mal-rules' which typifies errors that are usually made by novice trainees. Also preferably, the training session manager comprises an intelligent error detection means and an intelligent error handling means. The present invention utilizes a rule-based language having a control structure whereby a specific message passing protocol is utilized with respect to tasks which are procedural or step-by-step in structure. The rules can be activated by the trainee in any order to reach the solution by any valid or correct path.

Loftin, R. Bowen↗

Paint and Oil Locker, SWMU 067 Southern Treatment Area Air Sparge System Construction Completion and Performance Monitoring and Paint and Oil Locker, Northern Area (SWMU 067) and Supply Warehouse #3, SWMU 088 Long-Term Monitoring Report Kennedy Space Center, Florida

This Air Sparge (AS) System Construction Completion, Performance Monitoring, and Long-Term Monitoring (LTM) Report presents activities conducted at the Paint and Oil Locker (POL) (Solid Waste Management Unit [SWMU] 067) and Supply Warehouse #3 (SW3) (SWMU 088) sites located at the Kennedy Space Center (KSC), Florida. Activities include implementation and Year 1 (Quarters [Q] 1 through 4) and Q5 operation, maintenance, and monitoring (OM&M) activities and performance monitoring results for the AS Interim Measure (IM) in the POL Southern Treatment Area, LTM results for the POL Northern Area and SW3, and supplemental direct push technology (DPT) sampling at both sites to support the LTM and performance monitoring programs. The timeframe for activities included in this report extends from August 2019 to August 2022. The scope for these sites currently includes two main components, which are documented within this report: (1) LTM at SW3 and POL Northern Area where an AS system began operation at these sites in May 2009 and June 2013, respectively, and subsequently turned off for both sites in March 2018 (during the previous reporting period); and (2) Active AS operations and performance monitoring in the POL Southern Treatment Area where an AS system was installed and began operation in 2021. The AS IM in the POL Southern Treatment Area was implemented between 2019 and 2021 to treat a chlorinated solvent groundwater plume that resulted from historic operations supporting the National Aeronautics and Space Administration’s (NASA) Space Program. The objective of the AS IM is to remediate groundwater within the treatment zone to support transition to monitored natural attenuation (MNA). The overall Corrective Action objective is to reduce concentrations of trichloroethene (TCE), cis-1,2-dichloroethene (cDCE), trans-1,2- dichloroethene (tDCE), and vinyl chloride (VC) present in groundwater to levels below their respective State of Florida Groundwater Cleanup Target Levels (GCTLs). The AS IM was installed in the POL Southern Treatment Area to target the high concentration plume (HCP), which includes a source zone (SZ) area where TCE was found to exceed 11,000 micrograms per liter (µg/L), and extend to a depth of 30 feet below land surface (bls).

TCE↗

The Cost of (In-) Accurate Waste Characterization in the U.S. Nuclear Power Industry - 20066

Proper disposal of waste has never been a human priority. Our history is full of examples of throwing away things with minimal effort or thought to consequence. That is until disease or toxicity become apparent and we realize we need to change. Unfortunately, we almost never have all the information we need at the time we make decisions. In addition to the technical and scientific issues, profits and politics are also factors. Newton's third law also applies to politics and so for every policy (action) put in place, there will be (opposite reaction) forces in play to push back against it. These forces are seldom balanced and so the reaction to the discovery of harm is to over-correct and destroy the benefit to be had. This of course causes those who want the benefit, or profit from it, to work to undermine or repeal those measures put in place to eliminate the harm. The issue is exacerbated when the problem to be solved is highly technical and at the edge of our science so that the harm and benefit cannot be easily or accurately quantified. At these times, reason often goes out the window and our decision makers are influenced by either greed or fear as these emotions are much easier to stoke. Those of us in the middle, with the charge to 'do the right thing for the least cost', are therefore frequently constrained and forced into actions that are neither technically the right thing to do and not cost effective. The cost of radioactive waste disposal is based on the concentrations of various radioisotopes in the waste. Some of these isotopes are relatively easy to quantify and some are not. Most laboratory methods for quantification are limited in the amount of activity that can be present during the measurement process. Current nuclear plants were not designed with the idea that taking truly representative waste samples would be important. The limits used to define waste class and therefore cost are precisely defined but the methods for determining those concentrations are far less precise. Improving the accuracy of radioactivity concentrations in waste and having consistent and reasonable oversight can reduce waste costs through active management of the process. So what can we do about it? Science may provide an answer. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Fault Management Techniques in Human Spaceflight Operations

This paper discusses human spaceflight fault management operations. Fault detection and response capabilities available in current US human spaceflight programs Space Shuttle and International Space Station are described while emphasizing system design impacts on operational techniques and constraints. Preflight and inflight processes along with products used to anticipate, mitigate and respond to failures are introduced. Examples of operational products used to support failure responses are presented. Possible improvements in the state of the art, as well as prioritization and success criteria for their implementation are proposed. This paper describes how the architecture of a command and control system impacts operations in areas such as the required fault response times, automated vs. manual fault responses, use of workarounds, etc. The architecture includes the use of redundancy at the system and software function level, software capabilities, use of intelligent or autonomous systems, number and severity of software defects, etc. This in turn drives which Caution and Warning (C&W) events should be annunciated, C&W event classification, operator display designs, crew training, flight control team training, and procedure development. Other factors impacting operations are the complexity of a system, skills needed to understand and operate a system, and the use of commonality vs. optimized solutions for software and responses. Fault detection, annunciation, safing responses, and recovery capabilities are explored using real examples to uncover underlying philosophies and constraints. These factors directly impact operations in that the crew and flight control team need to understand what happened, why it happened, what the system is doing, and what, if any, corrective actions they need to perform. If a fault results in multiple C&W events, or if several faults occur simultaneously, the root cause(s) of the fault(s), as well as their vehicle-wide impacts, must be determined in order to maintain situational awareness. This allows both automated and manual recovery operations to focus on the real cause of the fault(s). An appropriate balance must be struck between correcting the root cause failure and addressing the impacts of that fault on other vehicle components. Lastly, this paper presents a strategy for using lessons learned to improve the software, displays, and procedures in addition to determining what is a candidate for automation. Enabling technologies and techniques are identified to promote system evolution from one that requires manual fault responses to one that uses automation and autonomy where they are most effective. These considerations include the value in correcting software defects in a timely manner, automation of repetitive tasks, making time critical responses autonomous, etc. The paper recommends the appropriate use of intelligent systems to determine the root causes of faults and correctly identify separate unrelated faults.

O'Hagan, Brian↗

Post-Closure Report for Closed Resource Conservation and Recovery Act Corrective Action Units, Nevada National Security Site, Nevada: For Calendar Year 2020 (Rev. 2)

This report serves as the combined annual report for post-closure activities in compliance with the requirements listed in Resource Conservation and Recovery Act (RCRA) Permit Number NEV HW0101 associated with the following closed corrective action units (CAUs): 1) CAU 90, Area 2 Bitcutter Containment; 2) CAU 91, Area 3 U-3fi Injection Well; 3) CAU 92, Area 6 Decon Pond Facility; 4) CAU 110, Area 3 WMD U-3ax/bl Crater; 5) CAU 111, Area 5 WMD Retired Mixed Waste Pits; 6) CAU 112, Area 23 Hazardous Waste Trenches The locations of the sites are shown in Figure ES-1. This report covers calendar year 2020. The post-closure requirements for these sites are described in RCRA Permit NEV HW0101 and are summarized in each CAU-specific section of this report. The results of the inspections, a summary of maintenance activities, and an evaluation of monitoring data are presented in this report. Site inspections are conducted annually at CAUs 90, 91, and 112; semiannually at CAUs 92 and 110; and quarterly at CAU 111. Additional inspections are conducted at CAUs 92 and 111 if precipitation occurs in excess of 1.0 inch in a 24-hour period. Inspections include an evaluation of the condition of the units, including covers, fences, signs, gates, and locks. At CAUs 110 and 111, soil moisture monitoring and subsidence surveys are conducted in addition to the visual inspections. At CAU 110, the site fence, gate, lock, and use restriction signs are evaluated. At CAU 111, an ecological survey, direct radiation monitoring, air monitoring, radon flux monitoring, and groundwater monitoring are also conducted. This report will address all monitoring item notes above except groundwater monitoring. Groundwater monitoring is documented in the Nevada National Security Site Data Report: Groundwater Monitoring Program Area 5 Radioactive Waste Management Site. All required inspections, maintenance, and monitoring were conducted in accordance with the post-closure requirements of the permit. Revision 6 of RCRA Permit NEV HW0101 was issued effective December 10, 2015, and remained in effect until December 10, 2020. At the time of this report submittal, the new RCRA permit application was in review.

54 ENVIRONMENTAL SCIENCES↗

Post-Closure Inspection and Monitoring Report for Surface Corrective Action Unit 417 at the Central Nevada Test Area, Nevada, Site

This report documents the biennial postclosure site inspections conducted in June 2018 at the surface Corrective Action Unit (CA U) 417 at the Central Nevada Test Area, Nevada, Site. The UC-I, UC-3, and UC-4 sites are inspected every 2 years, in accordance with the Post-Closure Monitoring Plan provided in the CAU 417 Closure Report published in 2001. The requirements for postclosure monitoring have been modified over the years through negotiations with the Nevada Division of Environmental Protection (NDEP). Modifications were documented through three separate Records of Technical Change to the Closure Report, which were approved by NDEP in 2003, 2011, and 2015. The UC-1, UC-3, and UC-4 sites were all observed as being in good condition during the 2018 inspections. A few minor cracks on the UC-1 Central Mud Pit cover were repaired during the UC- I inspection. A concrete monument at the northeast corner of Mud Pit U3E at the UC-3 site had some damage near the top of the monument, but the damage has not impacted the functionality of the monument or survey pin on top of the monument. No issues were identified at the UC-4 site. No maintenance or additional repair activities are recommended at the UC-1, UC-3, and UC-4 sites.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Problem Reporting System

The Problem Reporting System (PRS) is a Web application, running on two Web servers (load-balanced) and two database servers (RAID-5), which establishes a system for submission, editing, and sharing of reports to manage risk assessment of anomalies identified in NASA's flight projects. PRS consolidates diverse anomaly-reporting systems, maintains a rich database set, and incorporates a robust engine, which allows tracking of any hardware, software, or paper process by configuring an appropriate life cycle. Global and specific project administration and setup tools allow lifecycle tailoring, along with customizable controls for user, e-mail, notifications, and more. PRS is accessible via the World Wide Web for authorized user at most any location. Upon successful log-in, the user receives a customizable window, which displays time-critical 'To Do' items (anomalies requiring the user s input before the system moves the anomaly to the next phase of the lifecycle), anomalies originated by the user, anomalies the user has addressed, and custom queries that can be saved for future use. Access controls exist depending on a user's role as system administrator, project administrator, user, or developer, and then, further by association with user, project, subsystem, company, or item with provisions for business-to-business exclusions, limitations on access according to the covert or overt nature of a given project, all with multiple layers of filtration, as needed. Reporting of metrics is built in. There is a provision for proxy access (in which the user may choose to grant one or more other users to view screens and perform actions as though they were the user, during any part of a tracking life cycle - especially useful during tight build schedules and vacations to keep things moving). The system also provides users the ability to have an anomaly link to or notify other systems, including QA Inspection Reports, Safety, GIDEP (Government-Industry Data Exchange Program) Alert, Corrective Actions, and Lessons Learned. The PRS tracking engine was designed as a very extensible and scalable system, able to support additional applications, with future development possibilities already discussed, including Incident Surprise Anomalies (for anomalies occurring during Operations phases of NASA Flight projects), GIDEP and NASA Alerts, and others.

Potter, Don↗

Model for Simulating a Spiral Software-Development Process

A discrete-event simulation model, and a computer program that implements the model, have been developed as means of analyzing a spiral software-development process. This model can be tailored to specific development environments for use by software project managers in making quantitative cases for deciding among different software-development processes, courses of action, and cost estimates. A spiral process can be contrasted with a waterfall process, which is a traditional process that consists of a sequence of activities that include analysis of requirements, design, coding, testing, and support. A spiral process is an iterative process that can be regarded as a repeating modified waterfall process. Each iteration includes assessment of risk, analysis of requirements, design, coding, testing, delivery, and evaluation. A key difference between a spiral and a waterfall process is that a spiral process can accommodate changes in requirements at each iteration, whereas in a waterfall process, requirements are considered to be fixed from the beginning and, therefore, a waterfall process is not flexible enough for some projects, especially those in which requirements are not known at the beginning or may change during development. For a given project, a spiral process may cost more and take more time than does a waterfall process, but may better satisfy a customer's expectations and needs. Models for simulating various waterfall processes have been developed previously, but until now, there have been no models for simulating spiral processes. The present spiral-process-simulating model and the software that implements it were developed by extending a discrete-event simulation process model of the IEEE 12207 Software Development Process, which was built using commercially available software known as the Process Analysis Tradeoff Tool (PATT). Typical inputs to PATT models include industry-average values of product size (expressed as number of lines of code), productivity (number of lines of code per hour), and number of defects per source line of code. The user provides the number of resources, the overall percent of effort that should be allocated to each process step, and the number of desired staff members for each step. The output of PATT includes the size of the product, a measure of effort, a measure of rework effort, the duration of the entire process, and the numbers of injected, detected, and corrected defects as well as a number of other interesting features. In the development of the present model, steps were added to the IEEE 12207 waterfall process, and this model and its implementing software were made to run repeatedly through the sequence of steps, each repetition representing an iteration in a spiral process. Because the IEEE 12207 model is founded on a waterfall paradigm, it enables direct comparison of spiral and waterfall processes. The model can be used throughout a software-development project to analyze the project as more information becomes available. For instance, data from early iterations can be used as inputs to the model, and the model can be used to estimate the time and cost of carrying the project to completion.

Mizell, Carolyn↗

Decision Making In A High-Tech World: Automation Bias and Countermeasures

Automated decision aids and decision support systems have become essential tools in many high-tech environments. In aviation, for example, flight management systems computers not only fly the aircraft, but also calculate fuel efficient paths, detect and diagnose system malfunctions and abnormalities, and recommend or carry out decisions. Air Traffic Controllers will soon be utilizing decision support tools to help them predict and detect potential conflicts and to generate clearances. Other fields as disparate as nuclear power plants and medical diagnostics are similarly becoming more and more automated. Ideally, the combination of human decision maker and automated decision aid should result in a high-performing team, maximizing the advantages of additional cognitive and observational power in the decision-making process. In reality, however, the presence of these aids often short-circuits the way that even very experienced decision makers have traditionally handled tasks and made decisions, and introduces opportunities for new decision heuristics and biases. Results of recent research investigating the use of automated aids have indicated the presence of automation bias, that is, errors made when decision makers rely on automated cues as a heuristic replacement for vigilant information seeking and processing. Automation commission errors, i.e., errors made when decision makers inappropriately follow an automated directive, or automation omission errors, i.e., errors made when humans fail to take action or notice a problem because an automated aid fails to inform them, can result from this tendency. Evidence of the tendency to make automation-related omission and commission errors has been found in pilot self reports, in studies using pilots in flight simulations, and in non-flight decision making contexts with student samples. Considerable research has found that increasing social accountability can successfully ameliorate a broad array of cognitive biases and resultant errors. To what extent these effects generalize to performance situations is not yet empirically established. The two studies to be presented represent concurrent efforts, with student and professional pilot samples, to determine the effects of accountability pressures on automation bias and on the verification of the accurate functioning of automated aids. Students (Experiment 1) and commercial pilots (Experiment 2) performed simulated flight tasks using automated aids. In both studies, participants who perceived themselves as accountable for their strategies of interaction with the automation were significantly more likely to verify its correctness, and committed significantly fewer automation-related errors than those who did not report this perception.

Mosier, Kathleen L.↗

Uranium Mill Tailings Radiation Control Act Title II DOE Due Diligence and Lessons Learned from a Previous Site Transfer - 20352

Title II of the Uranium Mill Tailings Radiation Control Act (UMTRCA) established that a government agency will provide perpetual care for closed uranium and thorium ore-processing sites that were operating under an NRC source material license in 1978 or were licensed thereafter. Commercial owners (licensees) operating under an NRC or agreement state specific license when UMTRCA was passed are responsible for conducting reclamation of any byproduct material remaining from uranium-ore processing operations in accordance with an NRC or agreement state approved reclamation plan. Reclamation includes both surface and groundwater remedies. Upon completion of reclamation and approval by NRC, the site is required to be transferred to either the host state or the DOE for long-term surveillance and maintenance. Since UMTRCA's enactment, six Title II sites have been transferred to DOE; an additional 24 Title II sites are anticipated to be transferred before 2050. DoE's role mandated under UMTRCA Title II as the long-term care custodian is to perform 'monitoring, maintenance, and emergency measures necessary to protect the public health and safety.' UMTRCA requires that the licensee pay a long-term surveillance charge 'sufficient to cover the annual costs of site surveillance.' However, at some sites such as the Bluewater, New Mexico, Disposal Site, this mandate has required additional effort and expense by DOE, beyond the originally anticipated and intended scope within UMTRCA, but within the authority of DOE under UMTRCA. In 1997, the Bluewater site became the second UMTRCA Title II site to be transferred to DOE. The site was the location of a uranium mill operated from 1953 until 1982. The specific licensee began site reclamation in 1991, and by 1995 all tailings and contaminated materials were encapsulated in two tailings disposal cells and other disposal areas. In addition to surface contamination, milling activities impacted groundwater in the two upper aquifers. In 1989, the specific licensee attempted active groundwater remediation; however, no significant reduction in contaminant concentrations was observed. As a result, the specific licensee applied to NRC for alternate concentration limits (ACLs) in 1990, which were approved in 1996 as being protective, after additional corrective actions were performed. Since transfer of the Bluewater site to DOE, unforeseen challenges have occurred, requiring additional actions. The first challenge is the occurrence of surface depressions located on the northern section of the main tailings disposal cell. The depressions were first observed during DoE's initial inspection in 1998; however, evidence of these can be observed on satellite images taken prior to transfer. Since being first observed, the depressions have continued to grow both in depth and areal extent. Due to the design of the main tailings disposal cell, the depressions impede storm water from being effectively shed off the 101- hectare (250-acre) top slope of the main tailings disposal cell. Instead, storm water accumulates in the depressions, forming a large ephemeral pond that has stored up to 16.3 x 10{sup 6} liters (4.3 million gallons) of stormwater. The ponding poses a potential risk to the integrity of the main tailings disposal cell in the case of a large storm event, with the potential to cause the pond to overtop and erode the cover material and underlying waste. DOE has taken a number of short-term actions to monitor, measure, and reduce the ponding and is currently working with the US Army Corps of Engineers to design and construct a repair. Additional challenges are associated with groundwater at the Bluewater site. Nine wells were present on the 1335-hectare (3300-acre) site upon transfer. Groundwater compliance was called into question after the State of New Mexico reduced its uranium groundwater standard from 5.0 to 0.03 milligrams per liter in 2004, and when an ACL for uranium was exceeded in a site monitoring well in 2010. Acquiring historical groundwater data and subsequent evaluations as well as additional DOE groundwater monitoring led to installing 10 new monitoring wells and performing additional site hydrogeology recharacterization. DOE continues to evaluate groundwater conditions at the site and works with the NRC to determine regulatory requirements and a path forward. As a result of lessons learned at the Bluewater site and other Title II sites, improved processes have been implemented at a programmatic level to increase due diligence before site transfer and prevent similar issues from occurring at other UMTRCA Title II sites under long-term management. DoE's due diligence process is documented in the Process for Transition of UMTRCA Title II Disposal Sites to DOE for Long-Term Surveillance and Maintenance and is designed to ensure that DOE has no technical or compliance concerns with regulatory decisions that might compromise protectiveness following site transfer to DOE. Implementation of the due diligence process has increased DoE's role prior to site transfer and has been effective in identifying potential issues. Actions by NRC and specific licensees, in response to enhanced due diligence efforts by DOE, are expected to minimize, if not totally prevent, the need for unanticipated actions by DOE pertaining to the surface and groundwater remedies after site transfer. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Modeling in the State Flow Environment to Support Launch Vehicle Verification Testing for Mission and Fault Management Algorithms in the NASA Space Launch System

Analysis methods and testing processes are essential activities in the engineering development and verification of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS). Central to mission success is reliable verification of the Mission and Fault Management (M&FM) algorithms for the SLS launch vehicle (LV) flight software. This is particularly difficult because M&FM algorithms integrate and operate LV subsystems, which consist of diverse forms of hardware and software themselves, with equally diverse integration from the engineering disciplines of LV subsystems. M&FM operation of SLS requires a changing mix of LV automation. During pre-launch the LV is primarily operated by the Kennedy Space Center (KSC) Ground Systems Development and Operations (GSDO) organization with some LV automation of time-critical functions, and much more autonomous LV operations during ascent that have crucial interactions with the Orion crew capsule, its astronauts, and with mission controllers at the Johnson Space Center. M&FM algorithms must perform all nominal mission commanding via the flight computer to control LV states from pre-launch through disposal and also address failure conditions by initiating autonomous or commanded aborts (crew capsule escape from the failing LV), redundancy management of failing subsystems and components, and safing actions to reduce or prevent threats to ground systems and crew. To address the criticality of the verification testing of these algorithms, the NASA M&FM team has utilized the State Flow environment6 (SFE) with its existing Vehicle Management End-to-End Testbed (VMET) platform which also hosts vendor-supplied physics-based LV subsystem models. The human-derived M&FM algorithms are designed and vetted in Integrated Development Teams composed of design and development disciplines such as Systems Engineering, Flight Software (FSW), Safety and Mission Assurance (S&MA) and major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GN&C), Thrust Vector Control (TVC), liquid engines, and the astronaut crew office. Since the algorithms are realized using model-based engineering (MBE) methods from a hybrid of the Unified Modeling Language (UML) and Systems Modeling Language (SysML), SFE methods are a natural fit to provide an in depth analysis of the interactive behavior of these algorithms with the SLS LV subsystem models. For this, the M&FM algorithms and the SLS LV subsystem models are modeled using constructs provided by Matlab which also enables modeling of the accompanying interfaces providing greater flexibility for integrated testing and analysis, which helps forecast expected behavior in forward VMET integrated testing activities. In VMET, the M&FM algorithms are prototyped and implemented using the same C++ programming language and similar state machine architectural concepts used by the FSW group. Due to the interactive complexity of the algorithms, VMET testing thus far has verified all the individual M&FM subsystem algorithms with select subsystem vendor models but is steadily progressing to assessing the interactive behavior of these algorithms with LV subsystems, as represented by subsystem models. The novel SFE applications has proven to be useful for quick look analysis into early integrated system behavior and assessment of the M&FM algorithms with the modeled LV subsystems. This early MBE analysis generates vital insight into the integrated system behaviors, algorithm sensitivities, design issues, and has aided in the debugging of the M&FM algorithms well before full testing can begin in more expensive, higher fidelity but more arduous environments such as VMET, FSW testing, and the Systems Integration Lab7 (SIL). SFE has exhibited both expected and unexpected behaviors in nominal and off nominal test cases prior to full VMET testing. In many findings, these behavioral characteristics were used to correct the M&FM algorithms, enable better test coverage, and develop more effective test cases for each of the LV subsystems. This has improved the fidelity of testing and planning for the next generation of M&FM algorithms as the SLS program evolves from non-crewed to crewed flight, impacting subsystem configurations and the M&FM algorithms that control them. SFE analysis has improved robustness and reliability of the M&FM algorithms by revealing implementation errors and documentation inconsistencies. It is also improving planning efficiency for future VMET testing of the M&FM algorithms hosted in the LV flight computers, further reducing risk for the SLS launch infrastructure, the SLS LV, and most importantly the crew.

Trevino, Luis↗

Understanding Structures of Cyber Competition in an Era of Major Power Rivalry

Over the past two decades, the cyber domain has emerged and evolved into a key strategic domain for nations across the globe. Security strategies are espoused by heads of state that focus on how to manage the increasingly enormous, crosscutting impact that the cyber domain has on national security across economic, military, intelligence, intellectual property, and countless other facets. These strategies frequently evolve, and even change entirely, as leaders adapt to new technologies and administrations change. Even if these strategies did not change at all, they would take inordinate amounts of time to effectively implement within the organizational structures of government. The time required to go from setting department and agency-level goals, to the time small teams have well-oiled processes and expertise to accomplish tactical objectives that meet the strategic vision is lengthy. With near certainty, by the time objectives and vision are implemented, the landscape, strategy, or both has changed entirely. While this churn will likely never cease due to the rapidly changing nature of the cyber domain, this problem raises an important question: can governmental structures be organized to rapidly adapt to changing cyber strategies? As offices responsible for particular missions in cyberspace shuffle about within the bureaucracy, are technical capabilities enabled or enhanced? No matter how advanced a particular technical capability is or how adept the staff is at solving problems, they will be ineffective if placed haphazardly within the organization: the right authorities may not exist for their office, the correct lines of interpersonal communication may not be established properly, or insufficient resources have not been allocated to effectively deploy a brilliant technical solution. This concept of organizational agility in the context of national cyber capabilities is important when taking into account the National Defense Strategy’s emphasis on cyber capability and the ability of the United States to compete and rapidly adapt to new challenges posed by rivals. As a nation, we are at a point where technology evolves rapidly enough to warrant thoughtful and nimble changes to the bureaucratic structures that support how cyber operations are carried out. Taking these questions and cross-comparing them to the organizational structures across China, Russia, and the United States provides for an interesting thought experiment. As non-democratic regimes, China and Russia have differing priorities and internal power dynamics than the United States and thus organize their governments differently. By combining known and broadcasted strategies of these nations with the observed technical capabilities demonstrated in the public domain, we can begin to see how organizational structures map to strategic goals and directly enable technical capabilities. Insight can be gained by introducing organizational structures into traditional analysis focusing solely around strategies and capabilities; additionally, otherwise unknown capabilities or intents might be discovered or inferred by analyzing organizational structures alone. Analyzing cyber operations from this oft-overlooked perspective could potentially provide useful insight and more concrete actions that can be undertaken to realize the National Defense Strategy’s goals.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

Low Count and Background Radionuclides Analysis - 20488

The US Department of Energy (DOE) is often faced with the need to evaluate radionuclides at low concentrations. When site sample data are likely to be close to threshold activity concentrations of interest, then the means by which the radiochemical analysis is performed and reported is critical. This situation can occur when differentiating from zero (presence/absence) for radionuclides that do not occur naturally, close comparison with environmental background for naturally occurring radionuclides, close comparison with a risk- or dose-based threshold concentrations of interest, or even comparisons across studies. There are several analytical issues that are of concern, but the two that appear to cause incorrect decisions to be made most often involve establishing detection limits and subtracting ambient background conditions in the laboratory. These issues are not critical when radionuclide activity concentrations are large relative to thresholds of concern, but they seem to be poorly understood when it matters. When the comparisons are important and are likely to be close to a threshold of interest, then the general contract with the analytical laboratories needs to be changed so that the right or appropriate data are obtained. The concern is that important decisions are made incorrectly more often as greater scrutiny is placed on DoE's radionuclide cleanup or monitoring decisions by the public and other stakeholders. Examples are presented of problems that have been observed for different projects, both within and outside the realm of DOE and NRC remediation and radioactive waste disposal problems, and solutions are offered that should lead to better data from which important decisions need to be made. The first example is from Los Alamos National Laboratory (LANL) and involves radionuclide concentrations in soil and rock beneath LANL's Material Disposal Area (MDA) G. An initial review of the data led to a conclusion that americium and plutonium are a long way present beneath MDA G. A more thorough review of the data that accounted properly for ambient background and the detection limits that had been established led to the opposite conclusion. Another example is from the Nevada National Security Site where tritium results from one of the wells were unexpectedly high. Proper understanding and analysis of ambient background led to the conclusion that the increased concentrations were not so obvious, and that a different contract with the analytical laboratory was needed to provide more appropriate data to support a better determination. Other examples are used from regulatory review of projects in Nevada, where background levels and secular equilibrium for naturally occurring radionuclides are not established correctly because of analytical issues. The same basic issues have also been found to create difficulties analyzing historical data from the West Valley Demonstration Project. There is evidence in the data that the apparent lack of secular equilibrium where it is expected to exist is related to ambient background subtraction or other analytical issues. A final example is presented for analysis of Tc-99 in samples of depleted uranium. In this case, two different studies that were performed only three months apart provide quite different results. The US Environmental Protection Agency (EPA) established the data quality objectives (DQO) process in the mid-1980's to establish decision performance criteria for data collection. EPA guidance (EPA G-4, for example) clearly distinguishes between DQOs and measurement performance objectives (MQOs) that should be addressed for laboratory analysis of samples. The language of DQOs and MQOs has become confused over time it seems, and the subsequent effects seem to include a lack of attention to decision performance and a routine approach to measurement quality. In order to better address radionuclide sample analysis when the concentrations are close to thresholds of concern, which might be zero for some radionuclides, background for others, and risk-based thresholds for yet others, it is important that routine laboratory analysis methods are adjusted, and that the project team and the laboratory work closely together to ensure that the data meets the MQO requirements of laboratory analysis and reporting of results, and that the MQOs effectively support project-specific DQOs. This basic approach will be applied in Los Alamos in the coming year to the collection of moisture data from underneath MDA T that will be analyzed for americium and neptunium isotopes. Proper understanding of the radiochemistry methods and reporting, and of appropriate statistical methods is critical to the success of such projects, ensuring that the right decisions are made. (authors)

07 ISOTOPE AND RADIATION SOURCES↗

Evaluation of H-Canyon Ventilation Exhaust Tunnel Inspection at the Savannah River Site - 20052

The Department of Energy (DOE) H-Canyon Facility at the Savannah River Site (SRS) is operated by Savannah River Nuclear Solutions (SRNS). The Facility Structural Integrity Program [1] provides a process to inspect, evaluate, and document the conditions of passive safety related structural systems and components, their degradation mechanisms and their impact on the safety envelope. The Structural Integrity Program performs periodic visual inspections to confirm the systems and components can perform their safety function and recommend corrective actions before the function is compromised. The H-Canyon Exhaust Tunnel is part of the H-Canyon Ventilation System and is periodically inspected under the Structural Integrity Program. The Tunnel performs a Safety Class passive design feature function that is available 100% of the time. The underground reinforced concrete Tunnel directs Canyon process air from the Canyon to the Sand Filter System. The radiological and chemical airborne activity coupled with the physical configuration of the tunnel precludes a manned entry into the tunnel to perform the inspection. Unlike active systems that can be subjected to physical testing to confirm capability, qualification calculations, including modeling, is performed to assess passive design feature capabilities relative to operational, accident and natural phenomena hazards events. Input for these calculations come from knowledge of field conditions, design drawings and conservative assumptions. The knowledge of field conditions comes from concrete and soil testing activities as well as inspection data. The use of cameras on crawlers to obtain inspection data and how that data is used in qualification calculations is the focus of this discussion. Remote Tunnel inspections have been performed using cameras on a stick, referred to as pole cameras, prior to Calendar Year 2003 (CY2003). Since CY2003, six camera equipped crawlers have been used. Crawlers have evolved and improved by incorporating lessons learned from the previous inspections. The latest 2019 crawler successfully traveled the entire length of the tunnel between the Canyon and Sand Filter System and captured images that were previously unseen, thus providing key visual data for the Structural Integrity Program report [2]. The inspection data serves as 1) input to qualification calculations, 2) validates current conditions remain bounded by qualification calculations, and 3) documents a record of change over time. This data is vital for the effective evaluation of the tunnel structure and aids with predicting the life cycle service life safety envelope to protect the public, environment, and facility worker. The goal of the 2019 deployment was to use a more robust vehicle to ensure travel over obstacles, perform the inspection with higher resolution cameras, and have the ability to elevate the cameras to view surfaces previously obscured by abandon-in-place ducts in the tunnel. The inspection information will serve to strengthen the input basis for qualification calculations, versus using excessive conservative calculation assumptions. This 2019 inspection was compared with previous crawler visual evidence to identify change over time to project remaining service life and confirm field conditions remain bounded by qualification calculations. The results of the 2019 Exhaust Tunnel inspection continue to improve and provide a firm basis to make sound engineering judgements regarding tunnel capability and approaches in projecting remaining service life with an aging system and component. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Monitoring Airspace Complexity and Determining Contributing Factors

The national airspace has evolved over many years to accommodate increased traffic demand [1] while simultaneously maintaining one of the safest forms of transportation [2], [3]. One of the reasons for this success is the ability of the system and the operators to adapt and accommodate to situations that routinely disrupt optimal operations. These situations may include: adverse weather, delays, early arrivals, equipment outages, and other factors that are outside the operators ability to control. These factors can lead to states where automation is unable to properly handle these issues and therefore air traffic controllers and pilots have to intervene, ultimately increasing communication between operators resulting in higher workload. As controller workload increases to handle sub-optimal operating conditions this can be viewed as an increase in complexity. The reasoning for this is because humans are now required to make tactical decisions in response to external factors, resulting in a departure from the strategic plan where operations would be more efficiently managed. Human operators control airspace complexity under rigid regulations that are constantly changing. The airspace is divided into sectors and the number of aircraft assigned to each controller is limited for safe handling. There has been past work that devised airspace complexity metrics in commercial aviation and related these metrics to controller workload (e.g., [4],[5]). The upper bounds on the system load are pre-determined. Such bounds on complexity make for a safe system, but the system cannot scale and adapt to autonomous, dense, and heterogeneous traffic, including the many types of Unmanned Aerial Vehicles (UAVs) envisioned to be added to the operations. We hypothesize that, as traffic density and heterogeneity grow, and other key metrics change, there will be phase transitions at which the way traffic should be managed changes significantly [6]. We offer a method for in-time detection of contributing factors that lead to phase transitions, characterized by increased complexity. To the best of our knowledge, there is no tool similar to our proposed effort that identifies such contributing factors or precursor patterns. To define the scope we are proposing to measure complexity from the viewpoint of the Terminal Radar Approach Control Facilities (TRACON) controller’s perspective. In particular we are analyzing arrivals into KSFO. With safety as the top concern for airspace operators, it is important to recognize that as density and heterogeneity grow, the focus of the system will change. Times of the day when the airspace has low density and heterogeneity, the flights will follow more efficient paths where the aircraft move on established routes that are more or less directly to the destination. However, when density and heterogeneity increases, the system will begin changing focus to avoiding conflicts and collisions and route the flights in a more flexible way. Higher flexibility requires more communication and coordination between controllers and pilots which the current automation is unable to handle. This paper proposes a novel approach that monitors airspace complexity at multiple scales, uses a Machine Learning-based tool that predicts when operations will transition to a regime of greater complexity, and identifies actions that can reduce the complexity while still maintaining efficient and safe operations. We demonstrate our proposed approach using data from multiple complementary sources. This includes, but is not limited to: historical aircraft surveillance data from NASA’s Sherlock Data Warehouse [7], METAR weather data, and airport configuration data from Aviation System Performance Metrics (ASPM). The surveillance data flight paths are sampled at a variable sample rate — increasing as the aircraft approaches the airport. This is due to how Sherlock manages flight track stitching between different radar facilities which have different sampling rates. The weather and performance data are logged at defined intervals throughout the day at a courser refresh rate. In addition to the logged data and metrics, we leverage pre-defined Standard Terminal Arrival Routes (STARs) procedures to characterize the path of each flight. Each flight files for one of these routes in the flight plan well before entering the terminal airspace, and approximately follows the route until it leaves the STAR, typically on the final fix of a runway transition. However, most flights do not always fly the full STAR procedure to completion [8], but the majority do adhere to the fixes within the common route of the procedure. Our approach leverages fixes in the common route of each of the STARs to build a reference path to the airport. This allows us to characterize the flight paths in what we are defining as the “maneuvering area” (the airspace between the STAR and before the flight is lined up on the runway’s final approach) to determine how off nominal the flights are to calculate its complexity score. Determining airspace complexity is a concept that does not have a concrete answer. In designing this metric, we consider what increases the workload for the air traffic controllers. Consequently more specialized vectoring maneuvers results in higher workload. Accordingly, we start with a theory: each flight has a direct path it takes from the STAR’s common route to the final approach’s outer marker fix for the flight’s landing runway. It is important to note that the direct path is only used as a reference. If the majority of the flights have a large consistent offset as compared to other routes it does not necessarily mean that those flights have higher complexity. We are merely building a distribution based on this direct path for that particular STAR and runway pair to determine the normal mode of operations for that route. Flights that are in the upper tail of these distributions will result in higher complexity scores and flights that fly in the median will represent the normal mode of operations and therefore will have lower complexity scores. Since flights following each STAR route take different paths to the airport, we have a different distribution for each STAR route and therefore can model these distributions to compute a complexity score from their respective normalized distributions. To evaluate the effectiveness of our proposed airspace complexity metric we will compare against an established approach based on trajectory clustering [9]. This unsupervised learning technique consists of the following steps: (1) identify the general maneuvering areas (waypoints) by performing $\kappa$-means or DBSCAN clustering on locations where aircraft frequently turn based on the surveillance radar track data, (2) map flight trajectories onto sequences of waypoints, and (3) cluster the sequences based on their common subsequences. From a high-level perspective, this baseline model learns nominal operations in the airspace through the sequence of waypoints that are representative of where aircraft change direction and defines deviations from the nominal operations as “complex.” Therefore, more deviations from the nominal operations correspond to higher complexity values. For our validation, we re-implemented this technique and tune model hyper-parameters to correctly detect waypoints for the arrival traffic into the San Francisco bay area. We will compute the complexity measure over a one-year period using our proposed technique as well as the baseline. Our validation will be based on each technique’s ability to detect a set of undesirable outcomes (e.g., go-arounds, holding patterns, average time in the airspace, etc.). Since our current complexity metric is derived from the offset from the direct reference path, it’s important to understand what causes these offsets. In many of the flights with high offset distance, flights performing holding patterns and S turns can be observed. These maneuvering tactics are utilized to add distance between the aircraft and the destination runway to prevent multiple flights from having conflicting arrival times. In order to predict a rise in complexity (or the precursor to complexity), it’s necessary to be able to identify these potential conflicts (which in turn, result in higher offsets). To do this, we define a “representative flight” for each STAR route and runway pair. This flight is approximately the path the flight would take if there was a clear path with no other flights in the airspace — including the time remaining to the airport. We first identify the flights for a given STAR runway pair using the offset to the reference path distributions that fall between the 44-55 percentiles. This yields the flights that conform to the most normal mode of operation. Each of these flights is partitioned based on the percent complete from the entry point into the maneuvering areas from 0\% – 100\% complete. Then for each percent “bin”, we take the median value of the flight’s latitude/longitude coordinates, airspeed, and (non causal) time remaining to the airport to construct a lookup table for each percent complete bin on a given route. As a flight enters the maneuvering area, we can find the estimated arrival time of a flight to the airport by finding the closest point to the representative path’s percent complete bin (relative to the flight’s current position at any snapshot in the airspace) and therefore retrieve the corresponding remaining time left on the “representative path”. We assume that the flight will follow the representative path to completion when deriving these estimates. We can then compare these estimated arrival times against other flights for the same snapshot in time to identify potential conflicts. If more flights are estimated to arrive within a tolerance window than there are runways available, then we have a potential conflict. We can use this derived measure along with other factors expected to add disruption to the operation such as weather and runway configuration changes as an input to machine learning tools to detect precursors that increases in our complexity measure. This novel method will assist in uncovering insights into the contributing factors that lead to increased complexity that may allow for in-time responses to avoid reaching a high complexity state in the airspace.

complexity↗

Pantex Plant Ogallala Aquifer and Perched Groundwater Contingency Plan

The Pantex Plant Ogallala Aquifer and Perched Groundwater Contingency Plan has been developed in accordance with the requirements identified in the: • Interagency Agreement for the Pantex Superfund Site, Article 8.5 Work to be Performed, • Compliance Plan Provision of Hazardous Waste Permit No. 50284, and • Record of Decision for Groundwater, Soil, and Associated Media, Pantex Plant. A Long‐Term Monitoring System Design has been designed to monitor conditions in the perched groundwater including changes in the perched aquifer as a result of implementing the response actions. Monitoring is required for verifying the effectiveness of perched groundwater response actions (i.e., conditions in the perched aquifer are being affected as intended) and for confirming that the perched aquifer and Ogallala Aquifer characterization as defined in the Resource Conservation and Recovery Act Facility Investigation Report and the Corrective Measure Studies/Feasibility Study remains accurate. If monitoring results obtained through the monitoring network identify an unexpected condition or deviation, contingent actions will be considered and implemented as necessary to ensure continued protection of the Ogallala Aquifer and human health and the environment. Potential deviations to expected technology performance may be encountered for each of the four primary response actions that compose the selected remedy for perched groundwater; Playa 1 Pump and Treat System, Southeast Area Pump and Treat System, Southeast Area In‐Situ Bioremediation System (comprised of the Southeast In‐Situ Bioremediation System Original System, Southeast Area In‐Situ Bioremediation System Extension System, Offsite In‐Situ Bioremediation System, Perchlorate/Chromium ISB, Northeast ISB and County Road 8 ISB), and Zone 11 In‐Situ Bioremediation System. Monitoring will also be conducted to determine if there are deviations to the expected characterization, e.g., contaminants not expected as a result of the RCRA Facility Investigation characterization. Deviations to expected conditions in the Ogallala Aquifer could also be encountered if the response actions in the perched groundwater are not performing as expected, i.e., preventing contaminants from migrating to the Ogallala Aquifer. Currently, Pantex has begun investigation of detections of high explosives above groundwater protection standards in wells on the Texas Tech University property and a plume that is moving to the northeast from that area. Due to those detections, this Plan recognizes the fact that future detections in the Ogallala will be focused on first‐ time detections of analytes. After a remedy is determined, this Plan will require modification to address-deviations and contingent actions. This Plan was developed to identify the contingent actions necessary to mitigate impacts resulting from deviations to site conditions or response action performance. The Plan defines the environmental problem being addressed by the response actions, clarifies the expected conditions and objectives of the response actions, and identifies the potential deviations to the response actions (due to site conditions or technology performance) that could be encountered. The deviations were evaluated to determine the likelihood of occurrence, potential impact, and time to respond to avoid impact. The Plan also identifies the monitoring outlined in the Long‐Term Monitoring System Design Report (Consolidated Nuclear Security, 2024) and Sampling Analysis Plan (PanTeXas Deterrence, 2024) that will be used to detect the deviations. Lastly, the Plan specifies the contingent actions that could be implemented in response to the deviations. Because each response focuses on a discrete portion of the perched aquifer and contaminant plume, each response action has a different set of expected conditions, and therefore differing impacts from deviations to the site and technology expectations. As a result, the contingent actions are identified for each response action and potential deviation including specific constituents, location, and conditions. If deviations are encountered that impact the ability of the response action to meet performance objectives, the contingent actions will be focused on ensuring the response action can meet the performance objective. Contingent actions may be implemented as interim actions (ISMs/removal actions) in accordance with the Record of Decision, Interagency Agreement, and Hazardous Waste Permit‐50284, if warranted by the specific circumstances. For deviations to site characterization expected conditions, the contingent action will focus on determination of the source of the deviation, determination of the appropriate response, and evaluation of additional work to be completed. However, if the deviation to characterization impacts the performance of the response action, the contingent action will again focus on ensuring performance objectives can be met. Early source term removals and cleanup actions have been implemented to protect the Ogallala Aquifer. Because of these actions and based on modeling results, the expected conditions in the Ogallala Aquifer are that constituents of concern will not be detected above the Groundwater Protection Standards (GWPSs) nor will they reach potential points of exposure above the GWPS. The primary deviation of concern for the Ogallala is if constituents are detected in the Ogallala Aquifer near or above GWPSs. If it occurs, this change in expected conditions would require further evaluation of site and contaminant characteristics to determine an appropriate course of action. The evaluation would include additional monitoring, source identification, implementation of interim protective measures (if necessary), and delineation of extent. These evaluations are necessary to determine an appropriate response action for the Ogallala. The primary goal of the Plan is to provide for the continued protection of the Ogallala Aquifer and the health of its consumers. In recognition, this Plan presents a flexible and rational approach for making future decisions associated with confirming the change in perched and Ogallala aquifer conditions and identifying a response (technical activities, changes to response actions, regulatory oversight, and public involvement).

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗