Steve, I believe your issue was based on how you'all have your machines defined in Terminal Nodes, and your 'Node Up' method for Logging In to IDispatcher on a daily/shift-ly basis.  The initial Refresh CAD after login was a workaround to see the OMS-related fields populated in the Monitors, and there was a CR filed during your 9.2 Upgrade (1-EPN339) for this behavior, and Siebel shows it as fixed in MR4 and MR5, as well as 9.3 MR1.  What version of OMS_DISP are you running when you observe this behavior?

Scott, which 'outage icons' are you referring to in your description?  The map event flags?  or the Call symbols? (or something else perhaps?).  The map event flags should be visible based on Define Node (Terminal Node) agency/dgroup settings, and teh Call Symbols can be toggled on/off via the View/Display > Symbol Display command in IDispatcher, and can update the default/automatic display levels on/off in cad > OMS_SymbolVisibility.

Scott, I'm still not clear on if this is a customized event flag symbol (that might show a custom T, F, L bitmap right next to the event number on the map)?  or the call bitmap icon (by default a yellow X, that perhaps is now a T, F, L, etc.)?

If Refresh CAD-SignOff/On gets desired results, that's typically an indicator of a Listener/packet issue (as a Refresh/SignOff/On re-synchs everything with the database itself).  You may want to recycle Listener on your IDisp client and the BC/TA server).

Thanks for clarifying it's the Event symbol itself and not the Call bitmap.  After some internal discussions, looks like Intergraph Canada has seen this as well, and after reproducing it locally, Rick has filed a CR Patch Request for you (1-UPN59B) on this.  Latest Note in Siebel shows it being referred to the core CAD Dev folks for review.