PRISM Outage Management System provides a Ticket Management system that summarizes all of the ticket information and is primarily used by the Operator / Dispatcher.
Ticket Management is designed to assist the Operator Dispatcher to analyze the location of any ticket (prediction or confirmed outage) and to monitor the repair progress. The Ticket Summary display provides an itemized summary of all Tickets on the system in whole or by area.
Following calls or outage reports that are not telemetry-driven, a prediction of a device failure or outage location is made. The system automatically generates an Incident Ticket. Trouble Ticket Management manages outages as either Incident (predicted) Tickets or as Outage (confirmed) Tickets. A Ticket is automatically assigned to an area.
A roll-up numeric of the total number of Tickets for each level (# total) is displayed with each group. When a Ticket is generated the system updates the Trouble Ticket Summary display identifying the predicted outage devices and other relevant data for comparison and monitoring purposes. The Trouble Ticket Summary display shows a summary utilizing a single line per ticket.
Since PRISM Outage Management System incorporates SCADA telemetry, the system will behave differently on automated circuits than on non-automated circuits. The system will not generate a predicted incident against a device which the telemetry shows to be closed. The prediction algorithm will look further upstream to the next non-telemetered device. Any device which operates under SCADA control as a commanded change of state, the system will generate an outage ticket which does not have to be confirmed by a crew. If the automated switch operated automatically based on a fault condition (un-commanded), then the system will predict an incident downstream of the open switch.
Conversely if an open switch closes automatically, or under SCADA control, the system will close the outage ticket and commence with the call back process to inform the affected customers. The SCADA generated tickets are logged as SCADA generated so as to differentiate them from tickets generated manually or by the prediction algorithm.