Search NASASearch

NASA NTRS · 20140007524

Launch Control System Master Console Event Message Reduction

Abstract

System monitoring and control (SMC) message browsers receive so many messages daily that operators do not need to see. Important messages are often mixed up among the less important ones. My job is to reduce the messages displayed in the message browser so that warning and emergency messages can be seen easily and therefore, responded promptly. There are multiple methods to achieve this. Firstly, duplicate messages should not appear many times in the message browser. Instead, the message should appear only once but with a number that counts the times that it appears. This method is called duplicate message suppression. Secondly, messages that update the most recent state (e.g. up/down) of a component should replace the old-state messages. This method is called state based message correlation. Thirdly, messages that display "normal" alarm level should be suppressed unless it's a response to an operator action. In addition to message reduction, I also work on correcting the severity level and text formats on messages.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Nguyen, Uyen. 2014-04-09. Launch Control System Master Console Event Message Reduction. https://ntrs.nasa.gov/citations/20140007524

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related reports

LCS Master Console Event Message Reduction

System monitoring and control (SMC) message browsers receive so many messages daily that operators are unable to keep track all of them. Important messages are often mixed up among the less important ones. My job is to reduce the messages so that warning and emergency messages can be seen easily and therefore, responded promptly. There are multiple methods to achieve this. Firstly, messages that look the same should not appear many times in the message browser. Instead, the message should appear only once but with a number that counts the times that it appears. This method is called duplicate message suppression. Messages that display "normal" or "advisory" alarm level should be suppressed. Secondly, messages that update the most recent status of a system should replace the old-status messages. This method is called state based message correlation. Thirdly, some unnecessary messages should be sent straight to history after being displayed or not displayed at all. For an example, normal messages that are not a response to an operator's action should not be displayed. I also work on fixing messages that are not color-coded and formatted properly.

messages