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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2004

Evaluating the Emergency Notification Systems of the NASA White Sands Test

The problem was that the NASA Fire and Emergency Services did not know if the current emergency notification systems on the NASA White Sands Test Facility were appropriate for alerting the employees of an emergency. The purpose of this Applied Research Project was to determine if the current emergency notification systems of the White Sands Test Facility are appropriate for alerting the employees of an emergency. This was a descriptive research project. The research questions were: 1) What are similar facilities using to alert the employees of an emergency?; 2) Are the current emergency notification systems suitable for the community hazards on the NASA White Sands Test Facility?; 3) What is the NASA Fire and Emergency Services currently using to measure the effectiveness of the emergency notification systems?; and 4) What are the current training methods used to train personnel to the emergency notification systems at the NASA White Sands Test Facility? The procedures involved were to research other established facilities, research published material from credible sources, survey the facility to determine the facility perception of the emergency notification systems, and evaluate the operating elements of the established emergency notification systems for the facility. The results were that the current systems are suitable for the type of hazards the facility may endure. The emergency notification systems are tested frequently to ensure effectiveness in the event of an emergency. Personnel are trained and participate in a yearly drill to make certain personnel are educated on the established systems. The recommendations based on the results were to operationally improve the existing systems by developing and implementing one system that can overall notify the facility of a hazard. Existing procedures and training should also be improved to ensure that all personnel are educated on what to do when the emergency notification systems are activated.

Chavez, Alfred Paul↗
NASA NTRS2013

Real-Time Multimission Event Notification System for Mars Relay

As the Mars Relay Network is in constant flux (missions and teams going through their daily workflow), it is imperative that users are aware of such state changes. For example, a change by an orbiter team can affect operations on a lander team. This software provides an ambient view of the real-time status of the Mars network. The Mars Relay Operations Service (MaROS) comprises a number of tools to coordinate, plan, and visualize various aspects of the Mars Relay Network. As part of MaROS, a feature set was developed that operates on several levels of the software architecture. These levels include a Web-based user interface, a back-end "ReSTlet" built in Java, and databases that store the data as it is received from the network. The result is a real-time event notification and management system, so mission teams can track and act upon events on a moment-by-moment basis. This software retrieves events from MaROS and displays them to the end user. Updates happen in real time, i.e., messages are pushed to the user while logged into the system, and queued when the user is not online for later viewing. The software does not do away with the email notifications, but augments them with in-line notifications. Further, this software expands the events that can generate a notification, and allows user-generated notifications. Existing software sends a smaller subset of mission-generated notifications via email. A common complaint of users was that the system-generated e-mails often "get lost" with other e-mail that comes in. This software allows for an expanded set (including user-generated) of notifications displayed in-line of the program. By separating notifications, this can improve a user's workflow.

Wallick, Michael N.↗
NASA NTRS2018

Design and Development of Responder: a Notification-Acknowledgment Android OS Phone Application

This paper discusses the design and development of the Android phone application Responder and how it assists Flight Operation Team (FOT) members in handling alerts from a Short Message Service (SMS) text message and email based notification system. The FOT needed a simplified and more powerful tool for receiving, storing, and acknowledging notifications sent from the ground systems automated notification software called Attention! (Registered Trademark). The previous system was to rely on a text message application that comes on a phone. This way was slow, inefficient, and did a poor job of keeping FOT members informed on the state of a situation when multiple notifications are being sent out by Attention! (Registered Trademark). Responder is designed to provide easier viewing and acknowledging of multiple messages. It gives the user a quick look at all recently received messages in an organized and clean manner that prevents notifications from being lost during a large burst of messages. It makes it easier to find and review old messages received and Responder was designed to give the user more flexibility in setting up how and what alerts will notify them when they are received by the phone. Since the implementation of Responder the FOT members are more informed and are able to focus more on problem solving the reason a notification was received then trying to keep up with sending cumbersome acknowledgements over text message or email. Responder is only able to receive and send SMS text messages but by using email to text services provided by the cellular carrier it is able to send and receive emails.

notification↗
NASA NTRS1980

Heat Capacity Mapping Mission (HCMM) Notification Efforts

To encourage wide use of the Heat Capacity Mapping Mission (HCMM) data, especially among the scientific community, special notifications were prepared to inform them about the data's availability, its form, and the procedures for obtaining them. To achieve the widest distribution to the primary audiences of interest, mailings were made to scientists associated with the OSTA Resource Observation Division programs and to scientific and professional societies and journals. Accompanying the notifications to the societies and journals were samples of the HCMM imagery and a description of the image's predominant characteristics. A follow-up survey was completed to determine the effectiveness of the HCMM notifications.

Source record↗
NASA NTRS2009

Alert Notification System Router

The Alert Notification System Router (ANSR) software provides satellite operators with notifications of key events through pagers, cell phones, and e-mail. Written in Java, this application is specifically designed to meet the mission-critical standards for mission operations while operating on a variety of hardware environments. ANSR is a software component that runs inside the Mission Operations Center (MOC). It connects to the mission's message bus using the GMSEC [Goddard Space Flight Center (GSFC) Mission Services Evolution Center (GMSEC)] standard. Other components, such as automation and monitoring components, can use ANSR to send directives to notify users or groups. The ANSR system, in addition to notifying users, can check for message acknowledgements from a user and escalate the notification to another user if there is no acknowledgement. When a firewall prevents ANSR from accessing the Internet directly, proxies can be run on the other side of the wall. These proxies can be configured to access the Internet, notify users, and poll for their responses. Multiple ANSRs can be run in parallel, providing a seamless failover capability in the event that one ANSR system becomes incapacitated.

Gurganus, Joseph↗
NASA NTRS2015

Avionics Configuration Assessment for Flightdeck Interval Management: A Comparison of Avionics and Notification Methods

Flightdeck Interval Management is one of the NextGen operational concepts that FAA is sponsoring to realize requisite National Airspace System (NAS) efficiencies. Interval Management will reduce variability in temporal deviations at a position, and thereby reduce buffers typically applied by controllers - resulting in higher arrival rates, and more efficient operations. Ground software generates a strategic schedule of aircraft pairs. Air Traffic Control (ATC) provides an IM clearance with the IM spacing objective (i.e., the TTF, and at which point to achieve the appropriate spacing from this aircraft) to the IM aircraft. Pilots must dial FIM speeds into the speed window on the Mode Control Panel in a timely manner, and attend to deviations between actual speed and the instantaneous FIM profile speed. Here, the crew is assumed to be operating the aircraft with autothrottles on, with autopilot engaged, and the autoflight system in Vertical Navigation (VNAV) and Lateral Navigation (LNAV); and is responsible for safely flying the aircraft while maintaining situation awareness of their ability to follow FIM speed commands and to achieve the FIM spacing goal. The objective of this study is to examine whether three Notification Methods and four Avionics Conditions affect pilots' performance, ratings on constructs associated with performance (workload, situation awareness), or opinions on acceptability. Three Notification Methods (alternate visual and aural alerts that notified pilots to the onset of a speed target, conformance deviation from the required speed profile, and reminded them if they failed to enter the speed within 10 seconds) were examined. These Notification Methods were: VVV (visuals for all three events), VAV (visuals for all three events, plus an aural for speed conformance deviations), and AAA (visual indications and the same aural to indicate all three of these events). Avionics Conditions were defined by the instrumentation (and location) used to present IM information to crews: (1) Integrated (IM information is embedded in extant PFD (Primary Flight Display), ND (Navigation Display), EICAS (Engine Indicating and Crew Alerting System) displays); (2) EFB_Aft (IM information is only supplied in an EFB and mounted in location similar to that for MITRE's UPS work); (3) EFB_Fore (IM information is only supplied in an EFB which is mounted more forward, under the side window), and (4) EFB_Aft plus use of an AGD (the same IM information is supplied in an EFB and on an AGD, both mounted in locations similar to that in MITRE's UPS work ). Twelve commercial pilot crews flew descent scenarios (VNAV Speed with the mode control panel (MCP) speed window open until flaps extended, then VNAV Path) in a commercial transport flight simulator with realistic visual scene and communications. The results of this study serve three practical aims: (1) contribute to the down-select of avionics configuration for future assessment of the ASTAR spacing algorithm at NASA; (2) provide information useful to the FAA Human Factors Division (ANG-C1)'s mission to identify issues pertinent to flight certification of, and flight standards; (3) identify methodological considerations in support of future FIM human-in-the-loop (HITL) investigations.

Latorella, Kara A.↗
NASA NTRS2018

Responder: Notification Acknowledgement Android Phone Application

Responder is designed to provide easier viewing and acknowledging of multiple messages. It gives the user a quick look at all recently received messages in an organized and clean manner that prevents notifications from being lost during a large burst of messages. It makes it easier to find and review old messages received and Responder was designed to give the user more flexibility in setting up how and what alerts will notify them when they are received by the phone. Since the implementation of Responder the FOT (Flight Operations Team) members are more informed and are able to focus more on problem solving the reason a notification was received then trying to keep up with sending cumbersome acknowledgements over text message or email. Responder is only able to receive and send SMS (Short Message Service) text messages but by using email-to-text services provided by the cellular carrier it is able to send and receive emails.

application↗
NASA NTRS2010

Development of a Human Motor Model for the Evaluation of an Integrated Alerting and Notification Flight Deck System

A human motor model was developed on the basis of performance data that was collected in a flight simulator. The motor model is under consideration as one component of a virtual pilot model for the evaluation of NextGen crew alerting and notification systems in flight decks. This model may be used in a digital Monte Carlo simulation to compare flight deck layout design alternatives. The virtual pilot model is being developed as part of a NASA project to evaluate multiple crews alerting and notification flight deck configurations. Model parameters were derived from empirical distributions of pilot data collected in a flight simulator experiment. The goal of this model is to simulate pilot motor performance in the approach-to-landing task. The unique challenges associated with modeling the complex dynamics of humans interacting with the cockpit environment are discussed, along with the current state and future direction of the model.

Daiker, Ron↗
NASA NTRS2001

Improving Explicit Congestion Notification with the Mark-Front Strategy

Delivering congestion signals is essential to the performance of networks. Current TCP/IP networks use packet losses to signal congestion. Packet losses not only reduces TCP performance, but also adds large delay. Explicit Congestion Notification (ECN) delivers a faster indication of congestion and has better performance. However, current ECN implementations mark the packet from the tail of the queue. In this paper, we propose the mark-front strategy to send an even faster congestion signal. We show that mark-front strategy reduces buffer size requirement, improves link efficiency and provides better fairness among users. Simulation results that verify our analysis are also presented.

Liu, Chunlei↗
NASA NTRS2005

Automated Status Notification System

NASA Lewis Research Center's Automated Status Notification System (ASNS) was born out of need. To prevent "hacker attacks," Lewis' telephone system needed to monitor communications activities 24 hr a day, 7 days a week. With decreasing staff resources, this continuous monitoring had to be automated. By utilizing existing communications hardware, a UNIX workstation, and NAWK (a pattern scanning and processing language), we implemented a continuous monitoring system.

Source record↗
NASA NTRS2005

Enhanced, Partially Redundant Emergency Notification System

The Johnson Space Center Emergency Notification System (JENS) software utilizes pre-existing computation and communication infrastructure to augment a prior variable-tone, siren-based, outdoor alarm system, in order to enhance the ability to give notice of emergencies to employees working in multiple buildings. The JENS software includes a component that implements an administrative Web site. Administrators can grant and deny access to the administrative site and to an originator Web site that enables authorized individuals to quickly compose and issue alarms. The originator site also facilitates maintenance and review of alarms already issued. A custom client/server application program enables an originator to notify every user who is logged in on a Microsoft Windows-based desktop computer by means of a pop-up message that interrupts, but does not disrupt, the user s work. Alternatively or in addition, the originator can send an alarm message to recipients on an e-mail distribution list and/or can post the notice on an internal Web site. An alarm message can consist of (1) text describing the emergency and suggesting a course of action and (2) a replica of the corresponding audible outdoor alarm.

Pounds, Clark D.↗
NASA NTRS2010

Modeling Pilot Behavior for Assessing Integrated Alert and Notification Systems on Flight Decks

Numerous new flight deck configurations for caution, warning, and alerts can be conceived; yet testing them with human-in-the-Ioop experiments to evaluate each one would not be practical. New sensors, instruments, and displays are being put into cockpits every day and this is particularly true as we enter the dawn of the Next Generation Air Transportation System (NextGen). By modeling pilot behavior in a computer simulation, an unlimited number of unique caution, warning, and alert configurations can be evaluated 24/7 by a computer. These computer simulations can then identify the most promising candidate formats to further evaluate in higher fidelity, but more costly, Human-in-the-Ioop (HITL) simulations. Evaluations using batch simulations with human performance models saves time, money, and enables a broader consideration of possible caution, warning, and alerting configurations for future flight decks.

Cover, Mathew↗
NASA NTRS2009

Software Tools Streamline Project Management

Three innovative software inventions from Ames Research Center (NETMARK, Program Management Tool, and Query-Based Document Management) are finding their way into NASA missions as well as industry applications. The first, NETMARK, is a program that enables integrated searching of data stored in a variety of databases and documents, meaning that users no longer have to look in several places for related information. NETMARK allows users to search and query information across all of these sources in one step. This cross-cutting capability in information analysis has exponentially reduced the amount of time needed to mine data from days or weeks to mere seconds. NETMARK has been used widely throughout NASA, enabling this automatic integration of information across many documents and databases. NASA projects that use NETMARK include the internal reporting system and project performance dashboard, Erasmus, NASA s enterprise management tool, which enhances organizational collaboration and information sharing through document routing and review; the Integrated Financial Management Program; International Space Station Knowledge Management; Mishap and Anomaly Information Reporting System; and management of the Mars Exploration Rovers. Approximately $1 billion worth of NASA s projects are currently managed using Program Management Tool (PMT), which is based on NETMARK. PMT is a comprehensive, Web-enabled application tool used to assist program and project managers within NASA enterprises in monitoring, disseminating, and tracking the progress of program and project milestones and other relevant resources. The PMT consists of an integrated knowledge repository built upon advanced enterprise-wide database integration techniques and the latest Web-enabled technologies. The current system is in a pilot operational mode allowing users to automatically manage, track, define, update, and view customizable milestone objectives and goals. The third software invention, Query-Based Document Management (QBDM) is a tool that enables content or context searches, either simple or hierarchical, across a variety of databases. The system enables users to specify notification subscriptions where they associate "contexts of interest" and "events of interest" to one or more documents or collection(s) of documents. Based on these subscriptions, users receive notification when the events of interest occur within the contexts of interest for associated document or collection(s) of documents. Users can also associate at least one notification time as part of the notification subscription, with at least one option for the time period of notifications.

Source record↗
NASA NTRS2003

Image processing for hazard recognition in on-board weather radar

A method of providing weather radar images to a user includes obtaining radar image data corresponding to a weather radar image to be displayed. The radar image data is image processed to identify a feature of the weather radar image which is potentially indicative of a hazardous weather condition. The weather radar image is displayed to the user along with a notification of the existence of the feature which is potentially indicative of the hazardous weather condition. Notification can take the form of textual information regarding the feature, including feature type and proximity information. Notification can also take the form of visually highlighting the feature, for example by forming a visual border around the feature. Other forms of notification can also be used.

Kelly, Wallace E.↗
NASA NTRS2019

Space Weather Forecasting Capabilities at the Community Coordinated Modeling Center (CCMC)

The Community Coordinated Modeling Center (CCMC) provides a variety of services to the space science community. The mission for the CCMC's Space Weather Forecasting team is to address the space weather needs of NASA's robotic mission by conducting customized space weather services to NASA end-users. The team leverages CCMC tools/resources, carries out prototyping activities for the next generation space weather tools and follows communications/interactions with the users. We provide space weather forecasts, notifications, analysis and also education. This presentation will describe the team's concepts of operations, notification processes, anomaly analysis, and the tools used for space weather forecasting. The tools include a system that are completely open and available to the public's use like the Integrated Space Weather Analysis (iSWA) tool and the Database of Notifications, Knowledge and Information (DONKI). We will also discuss the education and training activities and how events like solar eclipses are important for the improvement and validation of different space weather models.

Collado-Vega, Yaireska↗
NASA NTRS2001

Enabling Advanced Automation in Spacecraft Operations with the Spacecraft Emergency Response System

True autonomy is the Holy Grail of spacecraft mission operations. The goal of launching a satellite and letting it manage itself throughout its useful life is a worthy one. With true autonomy, the cost of mission operations would be reduced to a negligible amount. Under full autonomy, any problems (no matter the severity or type) that may arise with the spacecraft would be handled without any human intervention via some combination of smart sensors, on-board intelligence, and/or smart automated ground system. Until the day that complete autonomy is practical and affordable to deploy, incremental steps of deploying ever-increasing levels of automation (computerization of once manual tasks) on the ground and on the spacecraft are gradually decreasing the cost of mission operations. For example, NASA's Goddard Space Flight Center (NASA-GSFC) has been flying spacecraft with low cost operations for several years. NASA-GSFC's SMEX (Small Explorer) and MIDEX (Middle Explorer) missions have effectively deployed significant amounts of automation to enable the missions to fly predominately in 'light-out' mode. Under light-out operations the ground system is run without human intervention. Various tools perform many of the tasks previously performed by the human operators. One of the major issues in reducing human staff in favor of automation is the perceived increased in risk of losing data, or even losing a spacecraft, because of anomalous conditions that may occur when there is no one in the control center. When things go wrong, missions deploying advanced automation need to be sure that anomalous conditions are detected and that key personal are notified in a timely manner so that on-call team members can react to those conditions. To ensure the health and safety of its lights-out missions, NASA-GSFC's Advanced Automation and Autonomy branch (Code 588) developed the Spacecraft Emergency Response System (SERS). The SERS is a Web-based collaborative environment that enables secure distributed fault and resource management. The SERS incorporates the use of intelligent agents, threaded discussions, workflow, database connectivity, and links to a variety of communications devices (e.g., two-way paging, PDA's, and Internet phones) via commercial gateways. When the SERS detects a problem, it notifies on-call team members, who then can remotely take any necessary actions to resolve the anomalies.The SERS goes well beyond a simple '911' system that sends out an error code to everyone with a pager. Instead, SERS' software agents send detailed data (i.e., notifications) to the most appropriate team members based on the type and severity of the anomaly and the skills of the on-call team members. The SERS also allows the team members to respond to the notifications from their wireless devices. This unique capability ensures rapid response since the team members no longer have to go to a PC or the control center for every anomalous event. Most importantly, the SERS enables safe experimentation with various techniques for increasing levels of automation, leading to robust autonomy. For the MIDEX missions at NASA GSFC, the SERS is used to provide 'human-in-the-loop' automation. During lights-out operations, as greater control is given to the MIDEX automated systems, the SERS can be configured to page remote personnel and keep them informed regarding actions taking place in the control center. Remote off-duty operators can even be given the option of enabling or inhibiting a specific automated response in near real time via their two-way pagers. The SERS facilitates insertion of new technology to increase automation, while maintaining the safety and security of mission resources. This paper will focus on SERS' overall functionality and how SERS has been designed to handle the monitoring and emergency response for missions with varying levels of automation. The paper will also convey some of the key lessons learned from SERS' deployment across of variety of missions, highlighting this incremental approach to achieving 'robust autonomy'.

Breed, Julie↗