Search NASASearch

Engineering topics

Nguyen, Uyen

Publications and source records attributed to Nguyen, Uyen.

Launch Control System Message Reduction

System Monitoring and Control (SMC) message browsers receive many messages daily that operators do not need to see. My job is to reduce the number of messages so that warning and emergency messages can be seen easily and therefore, responded to promptly. There are two methods to reduce messages: duplicate and state-based message correlations. With duplicate message correlation, SMC display the message the first time it shows up. The next times it occurs, a duplicate number will count the number of times the message appears. State-based message correlation is a process in which more informative messages acknowledge less useful ones and send them to history. I also work on correcting the severity level and text formats of messages. I follow two SMC message filtering tenets as I'm working on this project. Firstly, before filtering an offending message, a non-conformance (NC) must be created in order to attempt fixing that message through hardware or software. Only after the NC assessment states that it cannot fix an offending message, it can be filtered by SMC. Secondly, per Launch Control System (LCS) Coding Standards, SMC does not send information messages to the active message browser unless it's a response to an operator action.

correlation

Launch Control System Master Console Event Message Reduction

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.

messages

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