Search NASA⌕ Search

SEARCH · Search NASA

Results for “contingency”

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.

At least 19 records
All sourcesNASA NTRSDOE OSTI
DOE OSTI2016

Contingency Contractor Optimization Phase 3 Sustainment Software Design Document - Contingency Contractor Optimization Tool - Prototype

This document describes the final software design of the Contingency Contractor Optimization Tool - Prototype. Its purpose is to provide the overall architecture of the software and the logic behind this architecture. Documentation for the individual classes is provided in the application Javadoc. The Contingency Contractor Optimization project is intended to address Department of Defense mandates by delivering a centralized strategic planning tool that allows senior decision makers to quickly and accurately assess the impacts, risks, and mitigation strategies associated with utilizing contract support. The Contingency Contractor Optimization Tool - Prototype was developed in Phase 3 of the OSD ATL Contingency Contractor Optimization project to support strategic planning for contingency contractors. The planning tool uses a model to optimize the Total Force mix by minimizing the combined total costs for selected mission scenarios. The model optimizes the match of personnel types (military, DoD civilian, and contractors) and capabilities to meet mission requirements as effectively as possible, based on risk, cost, and other requirements.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2016

Contingency Contractor Optimization Phase 3 Sustainment Platform Requirements - Contingency Contractor Optimization Tool - Prototype

Sandia National Laboratories (Sandia) is in Phase 3 Sustainment of development of a prototype tool, currently referred to as the Contingency Contractor Optimization Tool - Prototype (CCOTP), under the direction of OSD Program Support. CCOT-P is intended to help provide senior Department of Defense (DoD) leaders with comprehensive insight into the global availability, readiness and capabilities of the Total Force Mix. The CCOT-P will allow senior decision makers to quickly and accurately assess the impacts, risks and mitigating strategies for proposed changes to force/capabilities assignments, apportionments and allocations options, focusing specifically on contingency contractor planning. During Phase 2 of the program, conducted during fiscal year 2012, Sandia developed an electronic storyboard prototype of the Contingency Contractor Optimization Tool that can be used for communication with senior decision makers and other Operational Contract Support (OCS) stakeholders. Phase 3 used feedback from demonstrations of the electronic storyboard prototype to develop an engineering prototype for planners to evaluate. Sandia worked with the DoD and Joint Chiefs of Staff strategic planning community to get feedback and input to ensure that the engineering prototype was developed to closely align with future planning needs. The intended deployment environment was also a key consideration as this prototype was developed. Initial release of the engineering prototype was done on servers at Sandia in the middle of Phase 3. In 2013, the tool was installed on a production pilot server managed by the OUSD(AT&L) eBusiness Center. The purpose of this document is to specify the CCOT-P engineering prototype platform requirements as of May 2016. Sandia developed the CCOT-P engineering prototype using common technologies to minimize the likelihood of deployment issues. CCOT-P engineering prototype was architected and designed to be as independent as possible of the major deployment components such as the server hardware, the server operating system, the database, and the web server. This document describes the platform requirements, the architecture, and the implementation details of the CCOT-P engineering prototype.

42 ENGINEERING↗
NASA NTRS2007

An Evidence-based Approach to Developing a Management Strategy for Medical Contingencies on the Lunar Surface: The NASA/Haughton-Mars Project (HMP) 2006 Lunar Medical Contingency Simulation at Devon Island

The lunar architecture for future sortie and outpost missions will require humans to serve on the lunar surface considerably longer than the Apollo moon missions. Although the Apollo crewmembers sustained few injuries during their brief lunar surface activity, injuries did occur and are a concern for the longer lunar stays. Interestingly, lunar medical contingency plans were not developed during Apollo. In order to develop an evidence-base for handling a medical contingency on the lunar surface, a simulation using the moon-Mars analog environment at Devon Island, Nunavut, high Canadian Arctic was conducted. Objectives of this study included developing an effective management strategy for dealing with an incapacitated crewmember on the lunar surface, establishing audio/visual and biomedical data connectivity to multiple centers, testing rescue/extraction hardware and procedures, and evaluating in suit increased oxygen consumption. Methods: A review of the Apollo lunar surface activities and personal communications with Apollo lunar crewmembers provided the knowledge base of plausible scenarios that could potentially injure an astronaut during a lunar extravehicular activity (EVA). Objectives were established to demonstrate stabilization and transfer of an injured crewmember and communication with ground controllers at multiple mission control centers. Results: The project objectives were successfully achieved during the simulation. Among these objectives were extraction from a sloped terrain by a two-member crew in a 1 g analog environment, establishing real-time communication to multiple centers, providing biomedical data to flight controllers and crewmembers, and establishing a medical diagnosis and treatment plan from a remote site. Discussion: The simulation provided evidence for the types of equipment and methods for performing extraction of an injured crewmember from a sloped terrain. Additionally, the necessary communications infrastructure to connect multiple centers worldwide was established from a remote site. The surface crewmembers were confronted with a number of unexpected scenarios including environmental, communications, EVA suit, and navigation challenges during the course of the simulation which provided insight into the challenges of carrying out a medical contingency in an austere environment. The knowledge gained from completing the objectives will be incorporated into the exploration medical requirements involving an incapacitated astronaut on the lunar surface.

Scheuring, R. A.↗
DOE OSTI2018

Practical Implementation of Synchrophasor Based Real-Time Contingency Analysis

Synchrophasor technology is increasingly accepted and adopted by the power industry. Linear State Estimator (LSE) is a recent development in the synchrophasor industry, and has been integrated and deployed at control centers, providing improved coverage and greater reliability from synchrophasor systems. This paper describes a first-of-a-kind synchrophasor based real-time contingency analysis (RTCA), which takes the LSE solved case as input, and then solves the what-if cases to provide timely information about impending grid problems to system operators. Test results on IEEE 39 bus and 300 bus system demonstrate the accuracy of the method for solving the RTCA problem using synchrophasor data. With this the synchrophasor measurement system provides an independent real-time monitoring and operation system which utilizes PMU data alone.

Nayak, Neeraj↗
DOE OSTI2016

Contingency Contractor Optimization Phase 3 Sustainment Requirements Document Contingency Contractor Optimization Tool - Prototype

This requirements document serves as an addendum to the Contingency Contractor Optimization Phase 2, Requirements Document [1] and Phase 3 Requirements Document [2]. The Phase 2 Requirements document focused on the high-level requirements for the tool. The Phase 3 Requirements document provided more detailed requirements to which the engineering prototype was built in Phase 3. This document will provide detailed requirements for features and enhancements being added to the production pilot in the Phase 3 Sustainment.

42 ENGINEERING↗
DOE OSTI2016

Contingency Contractor Optimization Phase 3 Sustainment Verification and Validation V&V) Report - Contingency Contractor Optimization Engineering - Prototype

The reports and test plans contained within this document serve as supporting materials to the activities listed within the “Contingency Contractor Optimization Tool – Prototype (CCOT-P) Verification & Validation Plan” [1]. The activities included test development, testing, peer reviews, and expert reviews. The engineering prototype reviews were done for both the software and the mathematical model used in CCOT-P. Section 2 includes the peer and expert review reports, which summarize the findings from each of the reviews and document the resolution of any issues. Section 3 details the test plans that were followed for functional testing of the application through the interface. Section 4 describes the unit tests that were run on the code.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2016

Photovoltaic frequency–watt curve design for frequency regulation and fast contingency reserves

When renewable energy resources are installed in electricity grids, they typically increase generation variability and displace thermal generator control action and inertia. Grid operators combat these emerging challenges with advanced distributed energy resource (DER) functions to support frequency and provide voltage regulation and protection mechanisms. This paper focuses on providing frequency reserves using autonomous IEC TR 61850-90-7 pointwise frequency-watt (FW) functions that adjust DER active power as a function of measured grid frequency. The importance of incorporating FW functions into a fleet of photovoltaic (PV) systems is demonstrated in simulation. Effects of FW curve design, including curtailment, deadband, and droop, were analyzed against performance metrics using Latin hypercube sampling for 20%, 70%, and 120% PV penetration scenarios on the Hawaiian island of Lanai. Finally, to understand the financial implications of FW functions to utilities, a performance function was defined based on monetary costs attributable to curtailed PV production, load shedding, and generator wear. An optimization wrapper was then created to find the best FW function curve for each penetration level. Lastly, it was found that in all cases, the utility would save money by implementing appropriate FW functions.

14 SOLAR ENERGY↗
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↗
DOE OSTI2025

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↗
NASA NTRS2010

Contingency Operations of Americas Next Moon Rocket, Ares V

America has begun the development of a new space vehicle system which will enable humans to return to the moon and reach even farther destinations. The system is called Constellation: it has 2 earth-launch vehicles, Ares I and Ares V; a crew module, Orion; and a lander, Altair with descent and ascent stages. Ares V will launch an Earth Departure Stage (EDS) and Altair into low earth orbit. Ares I will launch the Orion crew module into low earth orbit where it will rendezvous and dock with the Altair and EDS "stack". After rendezvous, the stack will contain four complete rocket systems, each capable of independent operations. Of course this multiplicity of vehicles provides a multiplicity of opportunities for off-nominal behavior and multiple mitigation options for each. Contingency operations are complicated by the issues of crew safety and the possibility of debris from the very large components impacting the ground. This paper examines contingency operations of the EDS in low earth orbit, during the boost to translunar orbit, and after the translunar boost. Contingency operations under these conditions have not been a consideration since the Apollo era and analysis of the possible contingencies and mitigations will take some time to evolve. Since the vehicle has not been designed, much less built, it is not possible to evaluate contingencies from a root-cause basis or from a probability basis; rather they are discussed at an effects level (such as the reaction control system is consuming propellant at a high rate). Mitigations for the contingencies are based on the severity of the off-nominal condition, the time of occurrence, recovery options, options for alternate missions, crew safety, evaluation of the condition (forensics) and future prevention. Some proposed mitigations reflect innovation in thinking and make use of the multiplicity of on-orbit resources including the crew; example: Orion could do a "fly around" to allow the crew to determine the condition and cause of a partially separated payload shroud. Other mitigations are really alternate missions; example, an engine out on during ascent resulted in insufficient propellant for the lunar mission, but the on-orbit vehicle stack is otherwise perfect and can pursue an alternate mission, such as a high ballistic trajectory to test the high-speed atmospheric reentry of Orion. Evaluation and presentation of contingency operations at this early stage of the development of the Ares V rocket will improve the design of the vehicle and lay the groundwork for the exhaustive contingency planning which must be done after the vehicle is built as preparations for operations.

Jaap, John↗
NASA NTRS2014

Mini-Membrane Evaporator for Contingency Spacesuit Cooling

The next-generation Advanced Extravehicular Mobility Unit (AEMU) Portable Life Support System (PLSS) is integrating a number of new technologies to improve reliability and functionality. One of these improvements is the development of the Auxiliary Cooling Loop (ACL) for contingency crewmember cooling. The ACL is a completely redundant, independent cooling system that consists of a small evaporative cooler--the Mini Membrane Evaporator (Mini-ME), independent pump, independent feedwater assembly and independent Liquid Cooling Garment (LCG). The Mini-ME utilizes the same hollow fiber technology featured in the full-sized AEMU PLSS cooling device, the Spacesuit Water Membrane Evaporator (SWME), but Mini-ME occupies only 25% of the volume of SWME, thereby providing only the necessary crewmember cooling in a contingency situation. The ACL provides a number of benefits when compared with the current EMU PLSS contingency cooling technology, which relies upon a Secondary Oxygen Vessel; contingency crewmember cooling can be provided for a longer period of time, more contingency situations can be accounted for, no reliance on a Secondary Oxygen Vessel (SOV) for contingency cooling--thereby allowing a reduction in SOV size and pressure, and the ACL can be recharged-allowing the AEMU PLSS to be reused, even after a contingency event. The first iteration of Mini-ME was developed and tested in-house. Mini-ME is currently packaged in AEMU PLSS 2.0, where it is being tested in environments and situations that are representative of potential future Extravehicular Activities (EVA's). The second iteration of Mini-ME, known as Mini- ME2, is currently being developed to offer more heat rejection capability. The development of this contingency evaporative cooling system will contribute to a more robust and comprehensive AEMU PLSS.

Makinen, Janice V.↗
NASA NTRS2015

Mini-Membrane Evaporator for Contingency Spacesuit Cooling

The next-generation Advanced Extravehicular Mobility Unit (AEMU) Portable Life Support System (PLSS) is integrating a number of new technologies to improve reliability and functionality. One of these improvements is the development of the Auxiliary Cooling Loop (ACL) for contingency crewmember cooling. The ACL is a completely redundant, independent cooling system that consists of a small evaporative cooler--the Mini Membrane Evaporator (Mini-ME), independent pump, independent feedwater assembly and independent Liquid Cooling Garment (LCG). The Mini-ME utilizes the same hollow fiber technology featured in the full-sized AEMU PLSS cooling device, the Spacesuit Water Membrane Evaporator (SWME), but Mini-ME occupies only approximately 25% of the volume of SWME, thereby providing only the necessary crewmember cooling in a contingency situation. The ACL provides a number of benefits when compared with the current EMU PLSS contingency cooling technology, which relies upon a Secondary Oxygen Vessel; contingency crewmember cooling can be provided for a longer period of time, more contingency situations can be accounted for, no reliance on a Secondary Oxygen Vessel (SOV) for contingency cooling--thereby allowing a reduction in SOV size and pressure, and the ACL can be recharged-allowing the AEMU PLSS to be reused, even after a contingency event. The first iteration of Mini-ME was developed and tested in-house. Mini-ME is currently packaged in AEMU PLSS 2.0, where it is being tested in environments and situations that are representative of potential future Extravehicular Activities (EVA's). The second iteration of Mini-ME, known as Mini-ME2, is currently being developed to offer more heat rejection capability. The development of this contingency evaporative cooling system will contribute to a more robust and comprehensive AEMU PLSS.

Makinen, Janice V.↗
NASA NTRS2013

NextGen Flight Deck Surface Trajectory-Based Operations (STBO): Contingency Holds

The purpose of this pilot-in-the-loop taxi simulation was to investigate a NextGen Surface Trajectory-Based Operations (STBO) concept called "contingency holds." The contingency-hold concept parses a taxi route into segments, allowing an air traffic control (ATC) surface traffic management (STM) system to hold an aircraft when necessary for safety. Under nominal conditions, if the intersection or active runway crossing is clear, the hold is removed, allowing the aircraft to continue taxiing without slowing, thus improving taxi efficiency, while minimizing the excessive brake use, fuel burn, and emissions associated with stop-and-go taxi. However, when a potential traffic conflict exists, the hold remains in place as a fail-safe mechanism. In this departure operations simulation, the taxi clearance included a required time of arrival (RTA) to a specified intersection. The flight deck was equipped with speed-guidance avionics to aid the pilot in safely meeting the RTA. On two trials, the contingency hold was not released, and pilots were required to stop. On two trials the contingency hold was released 15 sec prior to the RTA, and on two trials the contingency hold was released 30 sec prior to the RTA. When the hold remained in place, all pilots complied with the hold. Results also showed that when the hold was released at 15-sec or 30-sec prior to the RTA, the 30-sec release allowed pilots to maintain nominal taxi speed, thus supporting continuous traffic flow; whereas, the 15-sec release did not. The contingency-hold concept, with at least a 30-sec release, allows pilots to improve taxiing efficiency by reducing braking, slowing, and stopping, but still maintains safety in that no pilots "busted" the clearance holds. Overall, the evidence suggests that the contingency-hold concept is a viable concept for optimizing efficiency while maintaining safety.

NextGen↗
NASA NTRS1988

Contingency rescheduling of spacecraft operations

Spacecraft activity scheduling was a focus of attention in artificial intelligence recently. Several scheduling systems were devised which more-or-less successfully address various aspects of the activity scheduling problem, though most of these are not yet mature, with the notable expection of NASA's ESP. Few current scheduling systems, however, make any attempt to deal fully with the problem of modifying a schedule in near-real-time in the event of contingencies which may arise during schedule execution. These contingencies can include resources becoming unavailable unpredictably, a change in spacecraft conditions or environment, or the need to perform an activity not scheduled. In these cases it becomes necessary to repair an existing schedule, disrupting ongoing operations as little as possible. Normal scheduling is just a part of that which must be accomplished during contingency rescheduling. A prototype system named MAESTRO was developed for spacecraft activity scheduling. MAESTRO is briefly described with a focus on recent work in the area of real-time contingency handling. Included is a discussion of some of the complexities of the scheduling problem and how they affect contingency rescheduling, such as temporal constraints between activities, activities which may be interrupted and continued in any of several ways, and different ways to choose a resource complement which will allow continuation of an activity. Various heuristics used in MAESTRO for contingency rescheduling is discussed, as are operational concerns such as interaction of the scheduler with spacecraft subsystems controllers.

Britt, Daniel L.↗