GUARDIAN UIWG Meeting Notes Presenter: Tom Filliagi 2 March 2004 Attendees: Jim Fluke, Woody Roberts, Joe Wakefield, Dale Perry, Joe Golden, Carl Bullock, Chad Gimmestad, Rich Jesuroga, Jim Ramer, Susan Williams Teleconference Attendees: Steve Smith, Liz Quoetone, Gautam Sood GUARDIAN - General User Alert Display Panel; a vechicle for relaying information from software to user that will hopefully be used for all aspects of AWIPS. GUARDIAN Interface ------------------ Tom started the meeting by describing the appearance of the GUARDIAN. - persistently running software on each text and graphics workstation - interface is always on top - suggested that GUARDIAN be position on the D2D top bar - described each symbol on the interface: FF - FFMP Monitor, which would move off of D2D FZ - Sever Weather Monitor, which would move off of D2D X - error or message log from GUARDIAN software i - tips document and how to user GUARDIAN GUARDIAN logo - launches the GUARDIAN Configuration GUI Log Message Bars - messages clustered by category 1) MON 2) INGEST, SEND, RADAR 3) SYSTAT, SYSCOM 4) MISC - for demo purposes, messages were send from the command - the priority given to the message determines how GUARDINA responds. Priorities range from the highest priority of 0 to the lowest priority of 5. - categories will be delivered, but users can define their own as well - popup message box: takes up too much real estate. Tom mentioned that he is working on reducing the size of the box. - color of the message text relate to message priority - pop-ups: could most of the info displayed in the pop-up be put in the - logos are configurable and could be used a visual ques Suggestions ----------- - Do we need both an Acknowledge and Close, this could be combined into on mouse click Configuration GUI ----------------- Next, Tom demoed the GUARDIAN Configuration GUI. - can be configured on a user or scenario basis - perhaps after a predetermined amount of time, the configuration resets to basic configuration - configure GUARDIAN on a task basis, i.e. short-term forecaster, long- term forecaster - priorities are 0 to 5, with 0 being the highest priority - can set actions based on priority, that is, text, blink, pop-up, audio. - can configure foreground and background - can configure layout of the log messages window at the top (Q2, H2, etc.) Suggestions ----------- 1) instead of have the color name on the foreground and background, have the color instead 2) allow user to select color from a color palette 3) determine limits for the blinking and audio. Perhaps after a preset amount of time, the blinking and audio stop Discussion ---------- 1) Would GUARDIAN replace all D2D red-banner boxes? 2) Need input from the user asking what they have a hard time monitoring, what is critical 3) Need for training the user on how to configure GUARDIAN 4) Does GUARDIAN need to remain persistently on top? 5) Does GUARDIAN need to run on every screen in a 3-4 head configuration? 6) Can the size of the interface be reduced? 7) Is there an option to choose or not to choose to run GUARDIAN? Action Items ------------ 1) Make the "Acknowledge" button in the popup actually be 'acknowledge and close' in both name and functionality. 2) Change the color configuration from the separate word entries to back/ foreground color examples only. Don't need the text -- just use a color chooser, so no typing is needed. 3) Provide an 'expanded popup' toggle in the config GUI that will allow the popups to either show the separate labels for source, priority and category or not. 4) Move the layout, category list, and over-arching toggles (i.e.: include priority, source, category in text, and expanded popup mode) to above the tabular configuration section - to the top of the config GUI. 5) Move the action buttons from the top of the config GUI to the bottom (?) 6) When the main GUI is visible, do not allow the width of it to cover the entire window title bar of the D2D. Make it a couple of inches more narrow. 7) Provide a format of the main GUI that removes the text and only provides the monitor section (and perhaps the 'logo' section, which contains the launcher for the config GUI and the error log and tips text?). 8) Provide a method to minimize the main GUI completely, so that it is no longer visible. This will not turn off the GUARDIAN process, which means pop-ups will still be active. 9) Decided not to try to have screen-specific sources, at this time. It may becomde more evident how to do this in the future, but for now, leave it alone. This means that some messages coming from D2D will stay in the D2D - we will not yet try to have all D2D messages be sent to GUARDIAN. Respectfully Submitted, Susan M. Williams