Search NASA⌕ Search

SEARCH · Search NASA

Results for “notification”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

Contingency Support Simulation for the Tracking and Data Relay Satellite System (TDRSS)

In March 2006, the Tracking and Data Relay Satellite (TDRS)-3 experienced an unexpected thrusting event, which caused significant changes to its orbit. Recovery from this anomaly was protracted, raising concerns during the Independent Review Team (IRT) investigation of the anomaly regarding the contingency response readiness. The simulations and readiness exercises discussed in this paper were part of the response to the IRT concerns. This paper explains the various levels of simulation needed to enhance the proficiency of the Flight Dynamics Facility (FDF) and supporting elements in recovery from a TDRS contingency situation. The main emergency to address is when a TDRS has experienced uncommanded, unreported, or misreported thrusting, causing a ground station to lose the ability to acquire the spacecraft, as happened in 2006. The following levels of simulation are proposed: 1) Tests that would be performed by the individual support sites to verify that internal procedures and tools are in place and up to date; 2) Tabletop simulations that would involve all of the key support sites talking through their respective operating procedures to ensure that proper notifications are made and communications links are established; and 3) Comprehensive simulations that would be infrequent, but realistic, involving data exchanges between ground sites and voice and electronic communications among the supporting elements.

Dykes, Andy↗
NASA NTRS2008

The New NASA Orbital Debris Mitigation Procedural Requirements and Standards

NASA has issued major updates to its principal orbital debris mitigation policy directive and standards. The new NASA Procedural Requirements for Limiting Orbital Debris (NPR 8715.6), with its supporting NASA Standard 8719.14, both refine earlier orbital debris mitigation documents and in some areas expand their applicability. Organizational and individual responsibilities along with general directives are set forth in NPR 8715.6. New requirements include routine conjunction assessments for all maneuverable NASA spacecraft in LEO and GEO, prompt notifications of intended or unintended debris generation, preparation and maintenance of formal end-of-mission plans, and disposal of vehicles in operation around the Moon and Mars and at the Earth-Sun Lagrangian points. NASA Standard 8719.14 replaces the 1995 NASA Safety Standard 1740.14 with no major new requirements but with several refinements and additions, some of which had already been adopted. Compliance with human casualty risk limitations from reentering debris will be calculated explicitly and not be expressed in terms of average debris casualty area. Moreover, the minimum kinetic energy threshold for potentially injurious reentering debris is set at 15 Joules. The overarching requirement for the disposal of GEO spacecraft and launch vehicle orbital stages is to ensure that the vehicles do not come within GEO + 200 km for at least 100 km after end of mission, rather than setting specific requirements for the disposal orbit. Spacecraft operating in or routinely transiting LEO must remain in the region for no more than 25 years after end of mission or 30 years after launch, whichever occurs sooner. A comprehensive new NASA handbook on orbital debris has also been prepared to provide background on the orbital debris environment and the related NASA mitigation requirements and standards.

Johnson, Nicholas L.↗
NASA NTRS2006

Cooperative Collision Avoidance Step 1 - Technology Demonstration Flight Test Report. Revision 1

The National Aeronautics and Space Administration (NASA) Access 5 Project Office sponsored a cooperative collision avoidance flight demonstration program for unmanned aircraft systems (UAS). This flight test was accomplished between September 21st and September 27th 2005 from the Mojave Airport, Mojave, California. The objective of these flights was to collect data for the Access 5 Cooperative Collision Avoidance (CCA) Work Package simulation effort, i.e., to gather data under select conditions to allow validation of the CCA simulation. Subsequent simulation to be verified were: Demonstrate the ability to detect cooperative traffic and provide situational awareness to the ROA pilot; Demonstrate the ability to track the detected cooperative traffic and provide position information to the ROA pilot; Demonstrate the ability to determine collision potential with detected cooperative traffic and provide notification to the ROA pilot; Demonstrate that the CCA subsystem provides information in sufficient time for the ROA pilot to initiate an evasive maneuver to avoid collision; Demonstrate an evasive maneuver that avoids collision with the threat aircraft; and lastly, Demonstrate the ability to assess the adequacy of the maneuver and determine that the collision potential has been avoided. The Scaled Composites, LLC Proteus Optionally Piloted Vehicle (OPV) was chosen as the test platform. Proteus was manned by two on-board pilots but was also capable of being controlled from an Air Vehicle Control Station (AVCS) located on the ground. For this demonstration, Proteus was equipped with cooperative collision sensors and the required hardware and software to place the data on the downlink. Prior to the flight phase, a detailed set of flight test scenarios were developed to address the flight test objectives. Two cooperative collision avoidance sensors were utilized for detecting aircraft in the evaluation: Traffic Alert and Collision Avoidance System-II (TCAS-II) and Automatic Dependent Surveillance Broadcast (ADS-B). A single intruder aircraft was used during all the flight testing, a NASA Gulfstream III (G-III). During the course of the testing, six geometrically different near-collision scenarios were evaluated. These six scenarios were each tested using various combinations of sensors and collision avoidance software. Of the 54 planned test points 49 were accomplished successfully. Proteus flew a total of 21.5 hours during the testing and the G-III flew 19.8 hours. The testing fully achieved all flight test objectives. The Flight IPT performed an analysis to determine the accuracy of the simulation model used to predict the location of the host aircraft downstream during an avoidance maneuver. The data collected by this flight program was delivered to the Access 5 Cooperative Collision Avoidance (CCA) Work Package Team who was responsible for reporting on their analysis of this flight data.

Trongale, Nicholas A.↗
NASA NTRS2005

Kennedy Space Center (KSC) Mishap Response Plan

KSC Medical Operations, in exercising the KSC Psychological Triage Plan, provided crewmember family support following notification of the Columbia accident. KSC Medical Operations also provided field support in working with FEMA and EPA to assure adequate occupational medicine and environmental health care of KSC workers. In addition, the development of policy and procedures for handling and clearing biohazardous debris material in the KSC reconstruction hangar was prepared and implemented.

Scarpa, Philip↗
NASA NTRS2008

Observing Gamma-ray Bursts with GLAST

The Gamma-ray Large Area Telescope (GLAST) is a satellite-based observatory to study the high-energy gamma-ray sky. The Large Area Telescope, the main instrument, is a pair-conversion telescope which will survey the sky in the energy range 20 MeV to greater than 300 GeV. The LAT's wide field of view (greater than 2 sr), large effective area and low deadtime combine to provide excellent high-energy gamma-ray observations of GRB. To tie these frontier high-energy observations to the better-known properties at lower energies, a second instrument, the GLAST Burst Monitor (GBM) will provide important spectra and timing in the 8 keV to 30 MeV range. Upon detection of a GRB by the LAT or the GBM, the spacecraft can autonomously repoint to keep the GRB location within the LAT field of view, allowing high-energy afterglow observations. We describe how the instruments, spacecraft, and ground system work together to provide observations of gamma-ray bursts from 8 keV to over 300 GeV and provide rapid notification of these observations to the wider gamma-ray burst community. Analysis and simulation tools dedicated to the GRB science have been developed. In this contribution we show the expected LAT sensitivity obtained with such simulations, and illustrate the results we expect from GLAST observations with spectral and temporal analysis of simulated GRB.

McEnery, Julie↗
NASA NTRS2008

Emergency Response Virtual Environment for Safe Schools

An intelligent emergency response virtual environment (ERVE) that provides emergency first responders, response planners, and managers with situational awareness as well as training and support for safe schools is presented. ERVE incorporates an intelligent agent facility for guiding and assisting the user in the context of the emergency response operations. Response information folders capture key information about the school. The system enables interactive 3D visualization of schools and academic campuses, including the terrain and the buildings' exteriors and interiors in an easy to use Web..based interface. ERVE incorporates live camera and sensors feeds and can be integrated with other simulations such as chemical plume simulation. The system is integrated with a Geographical Information System (GIS) to enable situational awareness of emergency events and assessment of their effect on schools in a geographic area. ERVE can also be integrated with emergency text messaging notification systems. Using ERVE, it is now possible to address safe schools' emergency management needs with a scaleable, seamlessly integrated and fully interactive intelligent and visually compelling solution.

Wasfy, Ayman↗
NASA NTRS2008

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

Event Driven Messaging with Role-Based Subscriptions

Event Driven Messaging with Role-Based Subscriptions (EDM-RBS) is a framework integrated into the Service Management Database (SMDB) to allow for role-based and subscription-based delivery of synchronous and asynchronous messages over JMS (Java Messaging Service), SMTP (Simple Mail Transfer Protocol), or SMS (Short Messaging Service). This allows for 24/7 operation with users in all parts of the world. The software classifies messages by triggering data type, application source, owner of data triggering event (mission), classification, sub-classification and various other secondary classifying tags. Messages are routed to applications or users based on subscription rules using a combination of the above message attributes. This program provides a framework for identifying connected users and their applications for targeted delivery of messages over JMS to the client applications the user is logged into. EDMRBS provides the ability to send notifications over e-mail or pager rather than having to rely on a live human to do it. It is implemented as an Oracle application that uses Oracle relational database management system intrinsic functions. It is configurable to use Oracle AQ JMS API or an external JMS provider for messaging. It fully integrates into the event-logging framework of SMDB (Subnet Management Database).

Bui, Tung↗
NASA NTRS2007

Grid Task Execution

IPG Execution Service is a framework that reliably executes complex jobs on a computational grid, and is part of the IPG service architecture designed to support location-independent computing. The new grid service enables users to describe the platform on which they need a job to run, which allows the service to locate the desired platform, configure it for the required application, and execute the job. After a job is submitted, users can monitor it through periodic notifications, or through queries. Each job consists of a set of tasks that performs actions such as executing applications and managing data. Each task is executed based on a starting condition that is an expression of the states of other tasks. This formulation allows tasks to be executed in parallel, and also allows a user to specify tasks to execute when other tasks succeed, fail, or are canceled. The two core components of the Execution Service are the Task Database, which stores tasks that have been submitted for execution, and the Task Manager, which executes tasks in the proper order, based on the user-specified starting conditions, and avoids overloading local and remote resources while executing tasks.

Hu, Chaumin↗
NASA NTRS2007

Collaborative Resource Allocation

Collaborative Resource Allocation Networking Environment (CRANE) Version 0.5 is a prototype created to prove the newest concept of using a distributed environment to schedule Deep Space Network (DSN) antenna times in a collaborative fashion. This program is for all space-flight and terrestrial science project users and DSN schedulers to perform scheduling activities and conflict resolution, both synchronously and asynchronously. Project schedulers can, for the first time, participate directly in scheduling their tracking times into the official DSN schedule, and negotiate directly with other projects in an integrated scheduling system. A master schedule covers long-range, mid-range, near-real-time, and real-time scheduling time frames all in one, rather than the current method of separate functions that are supported by different processes and tools. CRANE also provides private workspaces (both dynamic and static), data sharing, scenario management, user control, rapid messaging (based on Java Message Service), data/time synchronization, workflow management, notification (including emails), conflict checking, and a linkage to a schedule generation engine. The data structure with corresponding database design combines object trees with multiple associated mortal instances and relational database to provide unprecedented traceability and simplify the existing DSN XML schedule representation. These technologies are used to provide traceability, schedule negotiation, conflict resolution, and load forecasting from real-time operations to long-range loading analysis up to 20 years in the future. CRANE includes a database, a stored procedure layer, an agent-based middle tier, a Web service wrapper, a Windows Integrated Analysis Environment (IAE), a Java application, and a Web page interface.

Wang, Yeou-Fang↗
NASA NTRS2006

Internet Distribution of Spacecraft Telemetry Data

Remote Access Multi-mission Processing and Analysis Ground Environment (RAMPAGE) is a Java-language server computer program that enables near-real-time display of spacecraft telemetry data on any authorized client computer that has access to the Internet and is equipped with Web-browser software. In addition to providing a variety of displays of the latest available telemetry data, RAMPAGE can deliver notification of an alarm by electronic mail. Subscribers can then use RAMPAGE displays to determine the state of the spacecraft and formulate a response to the alarm, if necessary. A user can query spacecraft mission data in either binary or comma-separated-value format by use of a Web form or a Practical Extraction and Reporting Language (PERL) script to automate the query process. RAMPAGE runs on Linux and Solaris server computers in the Ground Data System (GDS) of NASA's Jet Propulsion Laboratory and includes components designed specifically to make it compatible with legacy GDS software. The client/server architecture of RAMPAGE and the use of the Java programming language make it possible to utilize a variety of competitive server and client computers, thereby also helping to minimize costs.

Specht, Ted↗
NASA NTRS2010

Shuttle Environmental Assurance: Brominated Flame Retardants - Concerns, Drivers, Potential Impacts and Mitigation Strategies

Brominated Flame Retardants (BFRs) are widely used in the manufacture of electrical and electronic components and as additives in formulations for foams, plastics and rubbers. The United States (US) and the European Union (EU)have increased regulation and monitoring of of targeted BFRs, such as Polybrominated Diphenyl Ethers (PBDEs) due to the bioaccumulative effects in humans and animals. In response, manufacturers and vendors of BFR-containing materials are changing flame-retardant additives, sometimes without notifying BFR users. In some instances, Deca-bromodiphenylether (Deca-BDE) and other families of flame retardants are being used as replacement flame retardants for penta-BDE and octa-BDE. The reformulation of the BFR-containing material typically results in the removal of the targeted PBDE and replacement with a non-PBDE chemical or non-targeted PBDE. Many users of PBDE -based materials are concerned that vendors will perform reformulation and not inform the end user. Materials performance such as flammability, adhesion , and tensile strength may be altered due to reformulation. The requalification of newly formulated materials may be required, or replacement materials may have to be identified and qualified. The Shuttle Enviornmental Assurance (SEA) team indentified a risk to the Space Shuttle Program associated with the possibility that targeted PBDEs may be replaced without notification. Resultant decreases in flame retardancy, Liquid Oxygen (LOX) compatibility, or material performance could have serious consequences.

Clark-Ingram, Marceia↗
NASA NTRS2005

NASA Tech Briefs, December 2005

Topics covered include: Video Mosaicking for Inspection of Gas Pipelines; Shuttle-Data-Tape XML Translator; Highly Reliable, High-Speed, Unidirectional Serial Data Links; Data-Analysis System for Entry, Descent, and Landing; Hybrid UV Imager Containing Face-Up AlGaN/GaN Photodiodes; Multiple Embedded Processors for Fault-Tolerant Computing; Hybrid Power Management; Magnetometer Based on Optoelectronic Microwave Oscillator; Program Predicts Time Courses of Human/ Computer Interactions; Chimera Grid Tools; Astronomer's Proposal Tool; Conservative Patch Algorithm and Mesh Sequencing for PAB3D; Fitting Nonlinear Curves by Use of Optimization Techniques; Tool for Viewing Faults Under Terrain; Automated Synthesis of Long Communication Delays for Testing; Solving Nonlinear Euler Equations With Arbitrary Accuracy; Self-Organizing-Map Program for Analyzing Multivariate Data; Tool for Sizing Analysis of the Advanced Life Support System; Control Software for a High-Performance Telerobot; Java Radar Analysis Tool; Architecture for Verifiable Software; Tool for Ranking Research Options; Enhanced, Partially Redundant Emergency Notification System; Close-Call Action Log Form; Task Description Language; Improved Small-Particle Powders for Plasma Spraying; Bonding-Compatible Corrosion Inhibitor for Rinsing Metals; Wipes, Coatings, and Patches for Detecting Hydrazines; Rotating Vessels for Growing Protein Crystals; Oscillating-Linear-Drive Vacuum Compressor for CO2; Mechanically Biased, Hinged Pairs of Piezoelectric Benders; Apparatus for Precise Indium-Bump Bonding of Microchips; Radiation Dosimetry via Automated Fluorescence Microscopy; Multistage Magnetic Separator of Cells and Proteins; Elastic-Tether Suits for Artificial Gravity and Exercise; Multichannel Brain-Signal-Amplifying and Digitizing System; Ester-Based Electrolytes for Low-Temperature Li-Ion Cells; Hygrometer for Detecting Water in Partially Enclosed Volumes; Radio-Frequency Plasma Cleaning of a Penning Malmberg Trap; Reduction of Flap Side Edge Noise - the Blowing Flap; and Preventing Accidental Ignition of Upper-Stage Rocket Motors.

Source record↗
NASA NTRS2011

Enterprise Reference Library

Introduction: Johnson Space Center (JSC) offers two extensive libraries that contain journals, research literature and electronic resources. Searching capabilities are available to those individuals residing onsite or through a librarian s search. Many individuals have rich collections of references, but no mechanisms to share reference libraries across researchers, projects, or directorates exist. Likewise, information regarding which references are provided to which individuals is not available, resulting in duplicate requests, redundant labor costs and associated copying fees. In addition, this tends to limit collaboration between colleagues and promotes the establishment of individual, unshared silos of information The Integrated Medical Model (IMM) team has utilized a centralized reference management tool during the development, test, and operational phases of this project. The Enterprise Reference Library project expands the capabilities developed for IMM to address the above issues and enhance collaboration across JSC. Method: After significant market analysis for a multi-user reference management tool, no available commercial tool was found to meet this need, so a software program was built around a commercial tool, Reference Manager 12 by The Thomson Corporation. A use case approach guided the requirements development phase. The premise of the design is that individuals use their own reference management software and export to SharePoint when their library is incorporated into the Enterprise Reference Library. This results in a searchable user-specific library application. An accompanying share folder will warehouse the electronic full-text articles, which allows the global user community to access full -text articles. Discussion: An enterprise reference library solution can provide a multidisciplinary collection of full text articles. This approach improves efficiency in obtaining and storing reference material while greatly reducing labor, purchasing and duplication costs. Most importantly, increasing collaboration across research groups provides unprecedented access to information relevant to NASA s mission. Conclusion: This project is an expansion and cost-effective leveraging of the existing JSC centralized library. Adding key word and author search capabilities and an alert function for notifications about new articles, based on users profiles, represent examples of future enhancements.

Bickham, Grandin↗
NASA NTRS2003

The Technical Work Plan Tracking Tool

The Technical Work Plan Tracking Tool is a web-based application that enables interactive communication and approval of contract requirements that pertain to the administration of the Science, Engineering, Analysis, and Test (SEAT) contract at Johnson Space Center. The implementation of the application has (1) shortened the Technical Work Plan approval process, (2) facilitated writing and documenting requirements in a performance-based environment with associated surveillance plans, (3) simplified the contractor s estimate of the cost for the required work, and (4) allowed for the contractor to document how they plan to accomplish the work. The application is accessible to over 300 designated NASA and contractor employees via two Web sites. For each employee, the application regulates access according to the employee s authority to enter, view, and/or print out diverse information, including reports, work plans, purchase orders, and financial data. Advanced features of this application include on-line approval capability, automatic e-mail notifications requesting review by subsequent approvers, and security inside and outside the firewall.

Chullen, Cinda↗
NASA NTRS2004

Observations of Gamma-Ray Bursts by HETE-2

The High Energy Transient Explorer 2 (HETE-2), launched in October 2000, is currently localizing gamma-ray bursts (GRBs) at a rate of approximately 20/yr, many in real time. As of August 2003, HETE-2 had localized 43 GRBs; 16 localizations had led to the detection of an X-ray, optical, or radio afterglows. The prompt position notification of HETE-2 enabled probing the nature of so-called "dark bursts" for which no optical afterglows were found despite of accurate localizations. In some cases, the optical afterglow was found to be intrinsically faint , and its flux declined rapidly. In another case, the optical emission was likely to be extinguished by the dust in the vicinity of the GRB source. The bright afterglows of GRB021004 and GRB030329 were observed in unprecedented details by telescopes around the world. Strong evidence for the association of long GRBs with the core-collapse supernovae was found. HETE-2 has localized almost as many X-ray rich GRBs as classical GRBs. The nature of the X-ray rich GRBs and X-ray flashes have been studied systematically with HETE-2, and they are found to have many properties in common with the classical GRBs, suggesting that they are a single phenomenon.

Kawai, N.↗
NASA NTRS2005

NESTA: NASA Engineering Shuttle Telemetry Agent

The Spaceport Processing Systems Branch at NASA Kennedy Space Center has developed and deployed an agent based tool to monitor the Space Shuttle's ground processing telemetry stream. The application, the NASA Engineering Shuttle Telemetry Agent, increases situational awareness for system and hardware engineers during ground processing of the Shuttle's subsystems. The agent provides autonomous monitoring of the telemetry stream and automatically alerts system engineers when predefined criteria have been met. Efficiency and safety are improved through increased automation. Sandia National Labs' Java Expert System Shell is employed as the rule engine. The shell's predicate logic lends itself well to capturing the heuristics and specifying the engineering rules of this spaceport domain. The declarative paradigm of the rule-based agent yields a highly modular and scalable design spanning multiple subsystems of the Shuttle. Several hundred monitoring rules have been written thus far with corresponding notifications sent to Shuttle engineers. This paper discusses the rule-based telemetry agent used for Space Shuttle ground processing and explains the problem domain, development of the agent software, benefits of AT technology, and deployment and sustaining engineering of the product.

Semmel, Glenn S.↗
NASA NTRS2005

Monitoring Agents for Assisting NASA Engineers with Shuttle Ground Processing

The Spaceport Processing Systems Branch at NASA Kennedy Space Center has designed, developed, and deployed a rule-based agent to monitor the Space Shuttle's ground processing telemetry stream. The NASA Engineering Shuttle Telemetry Agent increases situational awareness for system and hardware engineers during ground processing of the Shuttle's subsystems. The agent provides autonomous monitoring of the telemetry stream and automatically alerts system engineers when user defined conditions are satisfied. Efficiency and safety are improved through increased automation. Sandia National Labs' Java Expert System Shell is employed as the agent's rule engine. The shell's predicate logic lends itself well to capturing the heuristics and specifying the engineering rules within this domain. The declarative paradigm of the rule-based agent yields a highly modular and scalable design spanning multiple subsystems of the Shuttle. Several hundred monitoring rules have been written thus far with corresponding notifications sent to Shuttle engineers. This chapter discusses the rule-based telemetry agent used for Space Shuttle ground processing. We present the problem domain along with design and development considerations such as information modeling, knowledge capture, and the deployment of the product. We also present ongoing work with other condition monitoring agents.

Semmel, Glenn S.↗