Search NASA⌕ Search

SEARCH · Search NASA

Results for “Computer Backup Systems”

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.

117 records · Page 7
All sourcesNASA NTRSDOE OSTI
DOE OSTI2026

Framework for Modeling 3D-Printed Concrete Construction to Assess Energy Efficiency and Backup Power Trade-Offs in a Mixed-Use, New Construction Neighborhood Development

This paper presents a framework that expands the URBANopt(TM) modeling platform to include 3D-printed concrete wall assemblies and assess energy efficiency and backup power trade-offs in new housing developments. Applied to a planned mixed-use neighborhood in Oil City, Pennsylvania, the workflow integrates building energy and distributed energy resource (DER) modeling to evaluate envelope and equipment upgrades alongside DER operations. Results show that advanced 3D-printed envelopes combined with efficient systems and onsite photovoltaics (PV) and storage reduce energy use intensity and sustain critical loads during outages. The framework supports planning for emerging construction technologies by quantifying key trade-offs between energy efficiency and backup power performance.

24 POWER TRANSMISSION AND DISTRIBUTION↗
NASA NTRS2023

Software Error Incident Categorizations in Aerospace

Since the first use of computers in space and aircraft, software errors have occurred. These errors can manifest as loss-of-life or less catastrophically. As the demand for automation increases, software in safety-critical systems should be designed to be tolerant to the most likely software faults. This paper categorizes historic aerospace software errors to determine trends of how and where automation is most likely to fail. A distinction between software producing wrong (erroneous) output versus no output (fail-silent) is introduced. Of the historical incidents analyzed, 87% were from software acting unexpectedly rather than simply stopping. Rebooting was found to be ineffective to clear erroneous behavior, and only partially effective for silent software. Errors were traced back to the software logic itself in 62% of cases, 13% within configurable data, and 25% introduced through input. Thirty percent (30%) of unexpected software behavior was caused by the absence of software and 20% was due to “unknown-unknowns”. These findings indicate that to achieve fault tolerance in safety-critical systems, backup strategies must be employed to detect and respond to erroneous software behavior beyond only fail-silent cases, and robust off-nominal testing should be performed to uncover unanticipated situations.

Software↗
NASA NTRS2011

Situational Lightning Climatologies for Central Florida: Phase V

The AMU added three years of data to the POR from the previous work resulting in a 22-year POR for the warm season months from 1989-2010. In addition to the flow regime stratification, moisture and stability stratifications were added to separate more active from less active lighting days within the same flow regime. The parameters used for moisture and stability stratifications were PWAT and TI which were derived from sounding data at four Florida radiosonde sites. Lightning data consisted of NLDN CG lightning flashes within 30 NM of each airfield. The AMU increased the number of airfields from nine to thirty-six which included the SLF, CCAFS, PAFB and thirty-three airfields across Florida. The NWS MLB requested the AMU calculate lightning climatologies for additional airfields that they support as a backup to NWS TBW which was then expanded to include airfields supported by NWS JAX and NWS MFL. The updated climatologies of lightning probabilities are based on revised synoptic-scale flow regimes over the Florida peninsula (Lambert 2007) for 5-, 10-, 20- and 30-NM radius range rings around the thirty-six airfields in 1-, 3- and 6-hour increments. The lightning, flow regime, moisture and stability data were processed in S-PLUS software using scripts written by the AMU to automate much of the data processing. The S-PLUS data files were exported to Excel to allow the files to be combined in Excel Workbooks for easier data handling and to create the tables and charts for the Gill. The AMU revised the Gill developed in the previous phase (Bauman 2009) with the new data and provided users with an updated HTML tool to display and manipulate the data and corresponding charts. The tool can be used with most web browsers and is computer operating system independent. The AMU delivered two Gills - one with just the PWAT stratification and one with both the PWAT and TI stratifications due to insufficient data in some of the PWATITI stratification combinations. This will allow the forecasters to choose a moisture-only or moisture/stability stratification depending on the flow regime and available data.

Bauman, William H., III↗
NASA NTRS1994

Hot gas ingestion effects on fuel control surge recovery and AH-1 rotor drive train torque spikes

This report summarizes the work accomplished through computer simulation to understand the impact of the hydromechanical turbine assembly (TA) fuel control on rocket gas ingestion induced engine surges on the AH-1 (Cobra) helicopter. These surges excite the lightly damped torsional modes of the Cobra rotor drive train and can cause overtorqueing of the tail rotor shaft. The simulation studies show that the hydromechanical TA control has a negligible effect on drive train resonances because its response is sufficiently attenuated at the resonant frequencies. However, a digital electronic control working through the TA control's separate, emergency fuel metering system has been identified as a solution to the overtorqueing problem. State-of-the-art software within the electronic control can provide active damping of the rotor drive train to eliminate excessive torque spikes due to any disturbances including engine surges and aggressive helicopter maneuvers. Modifications to the existing TA hydromechanical control are relatively minor, and existing engine sensors can be utilized by the electronic control. Therefore, it is concluded that the combination of full authority digital electronic control (FADEC) with hydromechanical backup using the existing TA control enhances flight safety, improves helicopter performance, reduces pilot workload, and provides a substantial payback for very little investment.

Tokarski, Frank↗
NASA NTRS2012

Tools Ensure Reliability of Critical Software

In November 2006, after attempting to make a routine maneuver, NASA's Mars Global Surveyor (MGS) reported unexpected errors. The onboard software switched to backup resources, and a 2-day lapse in communication took place between the spacecraft and Earth. When a signal was finally received, it indicated that MGS had entered safe mode, a state of restricted activity in which the computer awaits instructions from Earth. After more than 9 years of successful operation gathering data and snapping pictures of Mars to characterize the planet's land and weather communication between MGS and Earth suddenly stopped. Months later, a report from NASA's internal review board found the spacecraft's battery failed due to an unfortunate sequence of events. Updates to the spacecraft's software, which had taken place months earlier, were written to the wrong memory address in the spacecraft's computer. In short, the mission ended because of a software defect. Over the last decade, spacecraft have become increasingly reliant on software to carry out mission operations. In fact, the next mission to Mars, the Mars Science Laboratory, will rely on more software than all earlier missions to Mars combined. According to Gerard Holzmann, manager at the Laboratory for Reliable Software (LaRS) at NASA's Jet Propulsion Laboratory (JPL), even the fault protection systems on a spacecraft are mostly software-based. For reasons like these, well-functioning software is critical for NASA. In the same year as the failure of MGS, Holzmann presented a new approach to critical software development to help reduce risk and provide consistency. He proposed The Power of 10: Rules for Developing Safety-Critical Code, which is a small set of rules that can easily be remembered, clearly relate to risk, and allow compliance to be verified. The reaction at JPL was positive, and developers in the private sector embraced Holzmann's ideas.

Source record↗
NASA NTRS2014

Virtualization - A Key Cost Saver in NASA Multi-Mission Ground System Architecture

With science team budgets being slashed, and a lack of adequate facilities for science payload teams to operate their instruments, there is a strong need for innovative new ground systems that are able to provide necessary levels of capability processing power, system availability and redundancy while maintaining a small footprint in terms of physical space, power utilization and cooling.The ground system architecture being presented is based off of heritage from several other projects currently in development or operations at Goddard, but was designed and built specifically to meet the needs of the Science and Planetary Operations Control Center (SPOCC) as a low-cost payload command, control, planning and analysis operations center. However, this SPOCC architecture was designed to be generic enough to be re-used partially or in whole by other labs and missions (since its inception that has already happened in several cases!)The SPOCC architecture leverages a highly available VMware-based virtualization cluster with shared SAS Direct-Attached Storage (DAS) to provide an extremely high-performing, low-power-utilization and small-footprint compute environment that provides Virtual Machine resources shared among the various tenant missions in the SPOCC. The storage is also expandable, allowing future missions to chain up to 7 additional 2U chassis of storage at an extremely competitive cost if they require additional archive or virtual machine storage space.The software architecture provides a fully-redundant GMSEC-based message bus architecture based on the ActiveMQ middleware to track all health and safety status within the SPOCC ground system. All virtual machines utilize the GMSEC system agents to report system host health over the GMSEC bus, and spacecraft payload health is monitored using the Hammers Integrated Test and Operations System (ITOS) Galaxy Telemetry and Command (TC) system, which performs near-real-time limit checking and data processing on the downlinked data stream and injects messages into the GMSEC bus that are monitored to automatically page the on-call operator or Systems Administrator (SA) when an off-nominal condition is detected. This architecture, like the LTSP thin clients, are shared across all tenant missions.Other required IT security controls are implemented at the ground system level, including physical access controls, logical system-level authentication authorization management, auditing and reporting, network management and a NIST 800-53 FISMA-Moderate IT Security plan Risk Assessment Contingency Plan, helping multiple missions share the cost of compliance with agency-mandated directives.The SPOCC architecture provides science payload control centers and backup mission operations centers with a cost-effective, standardized approach to virtualizing and monitoring resources that were traditionally multiple racks full of physical machines. The increased agility in deploying new virtual systems and thin client workstations can provide significant savings in personnel costs for maintaining the ground system. The cost savings in procurement, power, rack footprint and cooling as well as the shared multi-mission design greatly reduces upfront cost for missions moving into the facility. Overall, the authors hope that this architecture will become a model for how future NASA operations centers are constructed!

Ground System Architecture↗
NASA NTRS1993

High-performance mass storage system for workstations

Reduced Instruction Set Computer (RISC) workstations and Personnel Computers (PC) are very popular tools for office automation, command and control, scientific analysis, database management, and many other applications. However, when using Input/Output (I/O) intensive applications, the RISC workstations and PC's are often overburdened with the tasks of collecting, staging, storing, and distributing data. Also, by using standard high-performance peripherals and storage devices, the I/O function can still be a common bottleneck process. Therefore, the high-performance mass storage system, developed by Loral AeroSys' Independent Research and Development (IR&D) engineers, can offload a RISC workstation of I/O related functions and provide high-performance I/O functions and external interfaces. The high-performance mass storage system has the capabilities to ingest high-speed real-time data, perform signal or image processing, and stage, archive, and distribute the data. This mass storage system uses a hierarchical storage structure, thus reducing the total data storage cost, while maintaining high-I/O performance. The high-performance mass storage system is a network of low-cost parallel processors and storage devices. The nodes in the network have special I/O functions such as: SCSI controller, Ethernet controller, gateway controller, RS232 controller, IEEE488 controller, and digital/analog converter. The nodes are interconnected through high-speed direct memory access links to form a network. The topology of the network is easily reconfigurable to maximize system throughput for various applications. This high-performance mass storage system takes advantage of a 'busless' architecture for maximum expandability. The mass storage system consists of magnetic disks, a WORM optical disk jukebox, and an 8mm helical scan tape to form a hierarchical storage structure. Commonly used files are kept in the magnetic disk for fast retrieval. The optical disks are used as archive media, and the tapes are used as backup media. The storage system is managed by the IEEE mass storage reference model-based UniTree software package. UniTree software will keep track of all files in the system, will automatically migrate the lesser used files to archive media, and will stage the files when needed by the system. The user can access the files without knowledge of their physical location. The high-performance mass storage system developed by Loral AeroSys will significantly boost the system I/O performance and reduce the overall data storage cost. This storage system provides a highly flexible and cost-effective architecture for a variety of applications (e.g., realtime data acquisition with a signal and image processing requirement, long-term data archiving and distribution, and image analysis and enhancement).

Chiang, T.↗
DOE OSTI2019

Challenges in Long-Term Records Preservation and Access - 19549

The US Department of Energy Office of Legacy Management (LM) mission includes preserving records and information about the nation's Cold War-era weapons projects and making that information available for years to come. As LM assumes responsibility for each project, records documenting operations and cleanup activities are absorbed into a central recordkeeping system. Each record category is governed by a federal retention requirement. Routine administrative records are kept just a few years, while the most important records have 'permanent' retention requirements and are transferred to the National Archives typically within 25 years of creation. It is relatively easy for LM to meet retention requirements for these routine and permanent records. LM's big preservation challenge is with records with tremendously long retention requirements. Records with 75-year retention requirements are common, and a small subset of LM records pertaining to waste disposal requires 150-year retention periods. LM must consider the best format for maintaining each of its records collections. Should physical records be boxed up for long-term storage, or should they be digitized? Each option has associated benefits, costs, and risks. Keeping records in paper format avoids digitizing expense and preserves the original media, but the paper must be maintained in a certified storage facility. A vermin infestation or sprinkler malfunction at a certified facility may be rare but could easily destroy records. Keeping the paper and making reference or backup electronic copies reduces the risk of loss but requires diligence and resources to keep the physical records and electronic versions synchronized. This becomes an overwhelming task in a database with millions of records. Entirely replacing paper records with digitized versions as electronic records introduces the risk that records could be lost due to a cybersecurity incident or made inaccessible by evolving technology. LM's early electronic records management efforts were limited to documents saved to PDF format. More recently, LM has embraced the benefits of maintaining records in native formats. (A spreadsheet includes formulas and other details lost when converted to a PDF file.) But whether the file is saved as a Microsoft Excel spreadsheet or PDF document, how do we ensure the file is readable in 75 or 150 years when these records meet their retention requirement? We have no way of knowing for sure from our 2019 vantage point-no more than we would expect to get good technology advice from someone 150 years ago. We cannot predict the technological future, but we can make sure our current electronic records environment is healthy and future ready. This includes making sure the electronic recordkeeping system is built on a modern platform and ensuring that each record in the system is saved in a current format. Quality standards are critical for electronic records to be future ready. Implementing quality involves an organization-wide approach to having consistently formatted file names and complete and descriptive metadata. Quality PDF documents are scanned to settings that ensure characters are machine-readable (with optical character recognition, or OCR). LM is currently replacing its electronic recordkeeping system and simultaneously modernizing its organizational approach to data management; it is replacing a traditional electronic records repository with a system that also manages records stored anywhere across the computer network. This new records management approach will require new thinking in how LM manages a dramatically increased volume of information across the network while not losing focus on its responsibility for long-term records preservation and access. (author)

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

Precursor Analysis Report: Ryuk Ransomware Attack on Universal Health Services 2020

The Ryuk Ransomware Attack on Universal Health Services (UHS) 2020 Precursor Analysis Report leverages publicly available information about the 2020 UHS cyber attack and catalogs anomalous observables for each technique employed in the attack. This analysis is based upon the methodology of the Cybersecurity for the Operational Technology Environment (CyOTE) program. UHS manages over 400 hospitals and is one of the largest healthcare providers in the United States with 3.5 million patients each year. On 27 September 2020, UHS suffered a widespread ransomware attack that resulted in a denial of service to critical internet-dependent healthcare systems including workstations, phones, and data centers. Employees resorted to filing patient details with pen and paper, while other facilities had to redirect ambulances and urgent patients to other facilities for adequate care. Adversaries carried out the attack with Ryuk, a ransomware that encrypts data and generates a RyukReadMe.txt ransom note with the ransom fee to decrypt the data, varying from 15 Bitcoin (BTC) to 50 BTC, equivalent to roughly $\$$353,892 to $\$$964,617. UHS did not pay the ransom and was able to recover data through backups, but still reported an impact of $\$$67 million dollars in recovery costs. On 29 October, one month after the attack, UHS made an official statement that their systems had been restored and they were resuming normal operations. Researchers and analysts identified 18 unique techniques (used in a sequence of 19 steps) utilized during the attack with a total of 185 observables using MITRE ATT&CK® for Industrial Control Systems. The CyOTE program assesses observables accompanying techniques used prior to the triggering event to identify opportunities to detect malicious activity. If observables accompanying the attack techniques are perceived and investigated prior to the triggering event, earlier comprehension of malicious activity can take place. Fourteen of the identified techniques used during the UHS cyber attack were precursors to the triggering event. Analysis identified 106 observables associated with these precursor techniques, 82 of which were assessed to have an increased likelihood of being perceived in the 30 days to two hours preceding the triggering event. The response and comprehension time could have been reduced if the observables had been identified earlier. The information gathered in this report contributes to a library of observables tied to a repository of artifacts, data sources, and technique detection references for practitioners and developers to support the comprehension of indicators of attack. Asset owners and operators can use these products if they experience similar observables or to prepare for comparable scenarios.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗