SEARCH · Engineering Papers
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.
A project manager recounts his decisions before and during the aftermath of the crash of a full-size flying model of Quetzalcoatlus northropi. The unstable pterodactyl crashed without harming anyone, although it caused a local power outage. The manager summarizes lessons learned about flight testing prototypes, including the effects of impatience.
The DRMS is the Discrepancy Reporting Management System used by the Deep Space Network (DSN). It uses a web interface and is a management tool designed to track and manage: data outage incidents during spacecraft tracks against equipment and software known as DRs (discrepancy Reports), to record "out of pass" incident logs against equipment and software in a Station Log, to record instances where equipment has be restarted or reset as Reset records, and to electronically record equipment readiness status across the DSN. Tracking and managing these items increases DSN operational efficiency by providing: the ability to establish the operational history of equipment items, data on the quality of service provided to the DSN customers, the ability to measure service performance, early insight into processes, procedures and interfaces that may need updating or changing, and the capability to trace a data outage to a software or hardware change. The items listed above help the DSN to focus resources on areas of most need.
All International Space Station (ISS) Ku-band telemetry transmits through the High-Rate Communications Outage Recorder (HCOR). The HCOR provides the recording and playback capability for all payload, science, and International Partner data streams transmitting through NASA's Ku-band antenna system. The HCOR is a solid-state memory recorder that provides recording capability to record all eight ISS high-rate data during ISS Loss-of-Signal periods. NASA payloads in the Destiny module are prime users of the HCOR; however, NASDA and ESA will also utilize the HCOR for data capture and playback of their high data rate links from the Kibo and Columbus modules. Marshall Space Flight Center's Payload Operations Integration Center manages the HCOR for nominal functions, including system configurations and playback operations. The purpose of this paper is to present the nominal operations plan for the HCOR and the plans for handling contingency operations affecting payload operations. In addition, the paper will address HCOR operation limitations and the expected effects on payload operations. The HCOR is manifested for ISS delivery on flight 9A with the HCOR backup manifested on flight 11A. The HCOR replaces the Medium-Rate Communications Outage Recorder (MCOR), which has supported payloads since flight 5A.1.
The three interplanetary ESA missions Mars-Express, Rosetta and Venus-Express (launched 2003, 2004 and 2005 resp.) are three-axes stabilized spacecraft (s/c) that estimate their inertial attitude (i.e. the attitude of the s/c w.r.t. the inertial frame) using measurements from a redundant set of star trackers (STR). Each s/c is equipped with four reaction wheels, a reaction control system based on thrusters and a redundant set of ring laser gyroscopes (gyros). The STR h/w layout of the three s/c is identical whereas there is a difference in the star pattern recognition algorithm of Rosetta which uses five neighbouring stars around a central star instead of star triads. The Rosetta algorithm has been implemented to cope with the presence of false stars which are expected to be seen during operations around the comet. The attitude acquisition capability from lost in space is different also in terms of AOCMS: The survival mode of Rosetta which is entered upon STR failure is presented. The AOCMS of Mars- and Venus-Express manages temporary STR outages during sky occultation by the planet not even by using redundancy. Though, a blinding of both STR during cruise lasting for the order of days confronts the ground operators with the limits of the AOCMS design. The operations and analyses that have been planned and partially been performed to compensate for the outage of the STR are demonstrated for Mars-Express. The caution measures taken before Venus orbit insertion of Venus-Express are detailed.
Adverse space weather affects operational activities in aviation and satellite systems. For example, large solar flares create highly variable enhanced neutral atmosphere and ionosphere electron density regions. These regions impact aviation communication frequencies as well as precision orbit determination. The natural space environment, with its dynamic space weather variability, is additionally changed by human activity. The increase in orbital debris in low Earth orbit (LEO), combined with lower atmosphere CO2 that rises into the lower thermosphere and causes increased cooling that results in increased debris lifetime, adds to the environmental hazards of navigating in near-Earth space. This is at a time when commercial space endeavors are posed to begin more missions to LEO during the rise of the solar activity cycle toward the next maximum (2012). For satellite and aviation operators, adverse space weather results in greater expenses for orbit management, more communication outages or aviation and ground-based high frequency radio used, and an inability to effectively plan missions or service customers with space-based communication, imagery, and data transferal during time-critical activities. Examples of some revenue-impacting conditions and solutions for mitigating adverse space weather are offered.
Lightning causes an estimated $50 million annually in damages to power lines, transformers and other electric utility equipment. Lightning strikes are not yet predictable, but U.S. East Coast Lightning Detection Network (LDN) is providing utilities and other clients data on lightning characteristics, flash frequency and location, and the general direction in which lightning associated storms are heading. Monitoring stations are equipped with direction finding antennas that detect lightning strikes reaching the ground by measuring fluctuations in the magnetic field. Stations relay strike information to SUNY-Albany-LDN operations center which is manned around the clock. Computers process data, count strikes, spot their locations, and note other characteristics of lightning, LDN's data is beamed to a satellite for broadcast to client's receiving stations. By utilizing real-time lightning strike information, managers are now more able to effectively manage their resources. This reduces outage time for utility customers.
The commuter and freight railroad industry is required to implement Positive Train Control (PTC) by 2015 (2012 for Metrolink), a challenging network communications problem. This paper will discuss present technologies developed by the National Aeronautics and Space Administration (NASA) to overcome comparable communication challenges encountered in deep space mission operations. PTC will be based on a new cellular wireless packet Internet Protocol (IP) network. However, ensuring reliability in such a network is difficult due to the "dead zones" and transient disruptions we commonly experience when we lose calls in commercial cellular networks. These disruptions make it difficult to meet PTC s stringent reliability (99.999%) and safety requirements, deployment deadlines, and budget. This paper proposes innovative solutions based on space-proven technologies that would help meet these challenges: (1) Delay Tolerant Networking (DTN) technology, designed for use in resource-constrained, embedded systems and currently in use on the International Space Station, enables reliable communication over networks in which timely data acknowledgments might not be possible due to transient link outages. (2) Policy-Based Management (PBM) provides dynamic management capabilities, allowing vital data to be exchanged selectively (with priority) by utilizing alternative communication resources. The resulting network may help railroads implement PTC faster, cheaper, and more reliably.
This paper evaluates the on-orbit performance of the first civilian operational use of a Global Positioning System Receiver (GPSR) at a geostationary orbit (GEO). The GPSR is on-board the newly launched Geostationary Operational Environmental Satellite (GOES-R). GOES-R is the first of four next generation GEO weather satellites for NOAA, now in orbit GOES-R is formally identified as GOES-16. Among the pioneering technologies required to support its improved spatial, spectral and temporal resolution is a GPSR. The GOES-16 GPSR system is a new design that was mission critical and therefore received appropriate scrutiny. As ground testing of a GPSR for GEO can only be done by simulations with numerous assumptions and approximations regarding the current GPS constellation, this paper reveals what performance can be achieved in using on orbit data. Extremely accurate orbital position is achieved using GPS navigation at GEO. Performance results are shown demonstrating compliance with the1007575 meter and 6 cms radial/in-track/cross-track orbital position and velocity accuracy requirements of GOES-16. The aforementioned compliance includes station-keeping and momentum management maneuvers, contributing to no observational outages. This performance is achieved by a completely new system design consisting of a unique L1 GEOantenna, low-noise amplifier (LNA) assembly and a 12 channel GPSR capable of tracking the edge of the main beam and the side lobes of the GPS L1 signals. This paper presents the definitive answer that the GOES-16 GPSR solution exceeds all performance requirements tracking up to 12 satellites and achieving excellent carrier-to-noise density (C/N0). Additionally, these performance results show the practicality of this approach. This paper makes it clear that all future GEO Satellites should consider the addition of a GPSR in their spacecraft design, otherwise they may be sacrificing spacecraft capabilities and accuracy along with incurring increased and continual demand on ground support.
Assessment of National Airspace System performance, which is usually measured in terms of delays resulting from the application of traffic flow management initiatives in response to weather conditions, volume, equipment outages and runway conditions, is needed both for guiding flow control decisions during the day of operations and for post operations analysis. Comparison of the actual delay, resulting from the traffic flow management initiatives, with the expected delay, based on traffic demand and other conditions, provides the assessment of the National Airspace System performance. This paper provides a method for estimating delay using the expected traffic demand and weather. In order to identify the cause of delays, 517 days of National Airspace System delay data reported by the Federal Aviation Administration s Operations Network were analyzed. This analysis shows that weather is the most important causal factor for delays followed by equipment and runway delays. Guided by these results, the concept of weather weighted traffic counts as a measure of system delay is described. Examples are given to show the variation of these counts as a function of time of the day. The various datasets, consisting of aircraft position data, enroute severe weather data, surface wind speed and visibility data, reported delay data and number of aircraft handled by the Centers data, and their sources are described. The procedure for selecting reference days on which traffic was minimally impacted by weather is described. Different traffic demand on each reference day of the week, determined by analysis of 42 days of traffic and delay data, was used as the expected traffic demand for each day of the week. Next, the method for computing the weather weighted traffic counts using the expected traffic demand, derived from reference days, and the expanded regions around severe weather cells is discussed. It is shown via a numerical example that this approach improves the dynamic range of the weather weighted traffic counts considerably. Time histories of these new weather weighted traffic counts are used for synthesizing two statistical features, six histogram features and six time domain features. In addition to these enroute weather features, two surface weather features of number of major airports in the United States with high mean winds and low mean visibility are also described. A least squares procedure for establishing a functional relation between the features, using combinations of these features, and system delays is explored using 36 days of data. Best correlations between the estimated delays using the functional relation and the actual delays provided by the Operations Network are obtained with two different combinations of features: 1) six time domain features of weather weighted traffic counts plus two surface weather features, and 2) six histogram features and mean of weather weighted traffic counts along with the two surface weather features. Correlation coefficient values of 0.73 and 0.83 were found in these two instances.
The runway configuration used by an airport has significant implications with respect to its capacity and ability to effectively manage surface and airborne traffic. Aircraft operators rely on runway configuration information because it can significantly affect an airline's operations and planning of their resources. Current practices in runway management are limited by a relatively short time horizon for reliable weather information and little assistance from automation. Wind velocity is the primary consideration when selecting a runway configuration; however when winds are below a defined threshold, discretion may be used to determine the configuration. Other considerations relevant to runway configuration selection include airport operator constraints, weather conditions (other than winds) traffic demand, user preferences, surface congestion, and navigational system outages. The future offers an increasingly complex landscape for the runway management process. Concepts and technologies that hold the potential for capacity and efficiency increases for both operations on the airport surface and in terminal and enroute airspace are currently under investigation. Complementary advances in runway management are required if capacity and efficiency increases in those areas are to be realized. The System Oriented Runway Management (SORM) concept has been developed to address this critical part of the traffic flow process. The SORM concept was developed to address all aspects of runway management for airports of varying sizes and to accommodate a myriad of traffic mixes. SORM, to date, addresses the single airport environment; however, the longer term vision is to incorporate capabilities for multiple airport (Metroplex) operations as well as to accommodate advances in capabilities resulting from ongoing research. This paper provides an update of research supporting the SORM concept including the following: a concept of overview, results of a TRCM simulation, single airport and Metroplex modeling effort and a benefits assessment.
Due to the criticality of continuous mission operations, some control centers must plan for alternate locations in the event an emergency shuts down the primary control center. Johnson Space Center (JSC) in Houston, Texas is the Mission Control Center (MCC) for the International Space Station (ISS). Due to Houston s proximity to the Gulf of Mexico, JSC is prone to threats from hurricanes which could cause flooding, wind damage, and electrical outages to the buildings supporting the MCC. Marshall Space Flight Center (MSFC) has the capability to be the Backup Control Center for the ISS if the situation is needed. While the MSFC Huntsville Operations Support Center (HOSC) does house the BCC, the prime customer and operator of the ISS is still the JSC flight operations team. To satisfy the customer and maintain continuous mission operations, the BCC has critical infrastructure that hosts ISS ground systems and flight operations equipment that mirrors the prime mission control facility. However, a complete duplicate of Mission Control Center in another remote location is very expensive to recreate. The HOSC has infrastructure and services that MCC utilized for its backup control center to reduce the costs of a somewhat redundant service. While labor talents are equivalent, experiences are not. Certain operations are maintained in a redundant mode, while others are simply maintained as single string with adequate sparing levels of equipment. Personnel at the BCC facility must be trained and certified to an adequate level on primary MCC systems. Negotiations with the customer were done to match requirements with existing capabilities, and to prioritize resources for appropriate level of service. Because some of these systems are shared, an activation of the backup control center will cause a suspension of scheduled HOSC activities that may share resources needed by the BCC. For example, the MCC is monitoring a hurricane in the Gulf of Mexico. As the threat to MCC increases, HOSC must begin a phased activation of the BCC, while working resource conflicts with normal HOSC activities. In a long duration outage to the MCC, this could cause serious impacts to the BCC host facility s primary mission support activities. This management of a BCC is worked based on customer expectations and negotiations done before emergencies occur. I.
NASA fs Short-term Prediction Research and Transition (SPoRT) project operates from NASA's Marshall Space Flight Center in Huntsville, Alabama. The team provides unique satellite data to the National Weather Service (NWS) and other agencies and organizations for weather analysis. While much of its work is focused on improving short-term weather forecasting, the SPoRT team supported damage assessment and response to Hurricane Superstorm Sandy by providing imagery that highlighted regions without power. The team used data from the Visible Infrared Imaging Radiometer Suite (VIIRS) on the Suomi National Polar-orbiting Partnership (Suomi NPP) satellite. The VIIRS low-light sensor, known as the day-night-band (DNB), can detect nighttime light from wildfires, urban and rural communities, and other human activity which emits light. It can also detect moonlight reflected from clouds and surface features. Using real time VIIRS data collected by our collaborative partner at the Space Science and Engineering Center of the University of Wisconsin, the SPoRT team created composite imagery to help detect power outages and restoration. This blackout imagery allowed emergency response teams from a variety of agencies to better plan and marshal resources for recovery efforts. The blackout product identified large-scale outages, offering a comprehensive perspective beyond a patchwork GIS mapping of outages that utility companies provide based on customer complaints. To support the relief efforts, the team provided its imagery to the USGS data portal, which the Federal Emergency Management Agency (FEMA) and other agencies used in their relief efforts. The team fs product helped FEMA, the U.S. Army Corps of Engineers, and U.S. Army monitor regions without power as part of their disaster response activities. Disaster responders used the images to identify possible outages and effectively distribute relief resources. An enhanced product is being developed and integrated into a web mapping service (WMS) for dissemination and use by a broader end user community.
There is a strategic interest in understanding how the propellant manufacturing process contributes to military capabilities outside the United States. The paper will discuss how system dynamics (SD) has been applied to rapidly assess the capabilities and vulnerabilities of a specific composite propellant production complex. These facilities produce a commonly used solid propellant with military applications. The authors will explain how an SD model can be configured to match a specific production facility followed by a series of scenarios designed to analyze operational vulnerabilities. By using the simulation model to rapidly analyze operational risks, the analyst gains a better understanding of production complexities. There are several benefits of developing SD models to simulate chemical production. SD is an effective tool for characterizing complex problems, especially the production process where the cascading effect of outages quickly taxes common understanding. By programming expert knowledge into an SD application, these tools are transformed into a knowledge management resource that facilitates rapid learning without requiring years of experience in production operations. It also permits the analyst to rapidly respond to crisis situations and other time-sensitive missions. Most importantly, the quantitative understanding gained from applying the SD model lends itself to strategic analysis and planning.
Days of operations in the National Airspace System can be described in term of traffic demand, runway conditions, equipment outages, and surface and enroute weather conditions. These causes manifest themselves in terms of departure delays, arrival delays, enroute delays and traffic flow management delays, Traffic flow management initiatives such as, ground stops, ground delay programs, miles-in-trail restrictions, rerouting and airborne holding are imposed to balance the air traffic demand with respect to the available capacity, In order to maintain operational efficiency of the National Airspace System, the Federal Aviation Administration (FAA) maintains delay sad other statistics in the Air Traffic Operations Network (OPSNET) and the Aviation System Performance Metrics (ASPM) databases. OPSNET data includes reportable delays of fifteen minutes ox more experienced by Instrument Flight Rule (IFR) flights. Numbers of aircraft affected by departure delays, enroute delays, arrival delays and traffic flow delays are recorded in the OPSNET data. ASPM data consist of number of actual departures, number of canceled departures, percentage of on time departures, percentage of on time gate arrivals, taxi-out delays. taxi-in delays, gate delays, arrival delays and block delays. Surface conditions at the major U.S. airports are classified in terms of Instrument Meteorological Condition (IMC) and Visual Meteorological Condition (VMC) as a function of the time of the day in the ASPM data. The main objective of this paper is to use OPSNET and ASPM data to classify the days in the datasets into few distinct groups, where each group is separated from the other groups in terms of a distance metric. The motivations for classifying the days are two-fold, 1) to enable selection of days of traffic with particular operational characteristics for concept evaluation using system-wide simulation systems such as the National Aeronautics and Space Administration's Airspace Concepts Evaluation Tool (ACES) and 2) to enable evaluation of a given day with respect to the characteristics of the classified groups. The first part of the paper is devoted to the analysis of major trends seen in the OPSNET and ASPM data. The second part of the paper is devoted to describing features or measures derived from the OPSNET and ASPM data that are suitable for characterizing days, and the classification algorithm used for grouping the days. Finally, the method for evaluating the characteristics of a given day with respect to the properties of the groups is described.
Discrepancy Reporting Management System (DRMS) is a computer program designed for use in the stations of NASA's Deep Space Network (DSN) to help establish the operational history of equipment items; acquire data on the quality of service provided to DSN customers; enable measurement of service performance; provide early insight into the need to improve processes, procedures, and interfaces; and enable the tracing of a data outage to a change in software or hardware. DRMS is a Web-based software system designed to include a distributed database and replication feature to achieve location-specific autonomy while maintaining a consistent high quality of data. DRMS incorporates commercial Web and database software. DRMS collects, processes, replicates, communicates, and manages information on spacecraft data discrepancies, equipment resets, and physical equipment status, and maintains an internal station log. All discrepancy reports (DRs), Master discrepancy reports (MDRs), and Reset data are replicated to a master server at NASA's Jet Propulsion Laboratory; Master DR data are replicated to all the DSN sites; and Station Logs are internal to each of the DSN sites and are not replicated. Data are validated according to several logical mathematical criteria. Queries can be performed on any combination of data.
The HCOR will be used onboard the ISS to record digital data during Ku-band Loss of Signal (LOS) periods. This recorded data will be played back to the ground during Ku-band Acquisition of Signal (AOS) periods. The Data Management (DM) Team at the Payload Operations and Integration Center is the primary operator of this complex recorder. The record and playback capabilities - along with the memory management functions - are presented in this paper. To illustrate how the DM Team plans to manage the record, playback and memory management tasks of operating the HCOR, an operational scenario for a ninety-minute orbit is presented.
The Psyche Mission presents the first opportunity toexplore the largest metal asteroid in the solar system, (16)Psyche, which is believed to be the exposed core of a largerplanetesimal that was stripped of its rocky mantle throughmultiple collisions during early solar system formation. Themission was selected in January 2017 for a 2022 launch as partof NASA’s Discovery Program and is uniquely enabled by theintegration of a Solar Electric Propulsion (SEP) Chassisdelivered by Maxar Space Solutions with JPL’s core deepspace avionics, flight software, and fault managementarchitectures. One of the key design tasks is the development ofa fault management system capable of being responsive to theunique elements of the combined JPL and Maxar spacecraftarchitecture. This new design leverages the strengths of eachorganization, with Maxar delivering its well-proven highvoltage power bus and low-thrust electric propulsionsubsystem from its GEO communications satellite product line,and JPL delivering its deep space mission expertise and thehardware and software most critical to deep space missiondesign. The development of a robust low-thrust mission andthe integration of design philosophies and hardware from twoorganizations is not without its challenges though.A key challenge in the development of the Psyche faultmanagement architecture and design is in the integration ofdesign philosophies and hardware from JPL and Maxar. Atthe architecture level, Maxar GEO communications satellitesare developed under the premise of highly responsive groundin the loop for the resolution of anomalies, and theimplementation takes a fail-operational approach to minimizedown time for its customers. In contrast, a deep space missionmust be able to maintain safety with long periods of groundcommunication outage. Additionally, with no time-criticalevents after launch, the Psyche spacecraft will generally failsafe in the presence of anomalous conditions; specialconsideration is being given to this approach, however, tominimize the loss of electric propulsion thrust time, which iscritical to low-thrust missions. At the hardware level, thedetailed definition of interfaces between JPL and Maxarhardware presents a unique challenge in the development andflowdown of fault management requirements, the developmentand implementation of fault monitors and responses, and thedevelopment and verification of fault containment boundaries.This paper describes the evolution of the Psyche faultmanagement architecture and design from the concept studyinto the preliminary design phase, with a focus on the uniquechallenges associated with flying GEO communicationssatellite hardware in deep space, implementing a robust lowthrust mission, and the integration of design philosophies andhardware from JPL and Maxar. Details regarding how thesechallenges are addressed in the fault management design inorder to maximize heritage, leverage the strengths of eachorganization, and minimize risk across the design are alsodiscussed.
The Huntsville Operations Support Center (HOSC) is a multi-project facility that is responsible for 24x7 real-time International Space Station (ISS) payload operations management, integration, and control and has the capability to support small satellite projects and will provide real-time support for SLS launches. The HOSC is a serviceoriented/ highly available operations center for ISS payloads-directly supporting science teams across the world responsible for the payloads. The HOSC is required to endure an annual 2-day power outage event for facility preventive maintenance and safety inspection of the core electro-mechanical systems. While complete system shut-downs are against the grain of a highly available sub-system, the entire facility must be powered down for a weekend for environmental and safety purposes. The consequence of this ground system outage is far reaching: any science performed on ISS during this outage weekend is lost. Engineering efforts were focused to maximize the ISS investment by engineering a suitable solution capable of continuing HOSC services while supporting safety requirements. The HOSC Power Outage Contingency (HPOC) System is a physically diversified compliment of systems capable of providing identified real-time services for the duration of a planned power outage condition from an alternate control room. HPOC was designed to maintain ISS payload operations for approximately three continuous days during planned HOSC power outages and support a local Payload Operations Team, International Partners, as well as remote users from the alternate control room located in another building. This paper presents the HPOC architecture and lessons learned during testing and the planned maiden operational commissioning. Additionally, this paper documents the necessity of an HPOC capability given the unplanned HOSC Facility power outage on April 27th, 2011, as a result of the tornado outbreak that damaged the electrical grid to such a degree that significantly inhibited the Tennessee Valley Authority's ability to transmit electricity throughout the North Alabama region.