Long Term Device

Devices that are intended to be switched to an abnormal state for an extended time, but for which you do NOT wish to update the GIS, can be marked as Long Term devices in Responder. This allows new faults to occur on the device and be managed on different incidents. It also allows for filtering these devices or incidents in and out of the Responder grid as desired.

Long Term designation can only be applied to normally open, switchable devices that are currently abnormal.

To designate a device as Long Term, follow the steps below:

Create a switching operation on a normally open device.
Right-click the device row for the switched device and select Long Term.

TIP: You are then prompted to update ArcMap.
Click the Long Term Refresh button in ArcMap. This requires editing privileges in ArcMap and it updates the GIS trace weight of the long term feature, to change its normal state from a tracing perspective. This can be done in any version, however general practice in Responder is to hit a GIS replica rather than a version receiving direct GIS edits.
The incident and device row highlights in purple when set to Long Term.

The switched device is now long term, the status is closed, and you can create faults on the device. You can change the fault, move upstream, and predict to the device just like it’s a normally closed device.

Devices set to Long Term can’t be operated by the long term incident, for example, you can’t cancel, restore, or edit the device.

To remove the Long Term designation:

Right-click the device row and select Remove Long Term Designation.
Click the Long Term Refresh button.

The device returns to normally open and the purple highlight is removed.

A View filter in Explorer displays Incidents with Long Term Devices and the Incident Report shows a device that is or was set to long term. Additionally, the Incident by ID report in Archive shows if a device was Long Term.

TIP: Miner.Responder.LongTermGISUpdater.exe is a standalone Server tool which can be used in place of the Long Term Refresh button. This should be scheduled after any replication, as replication from another GIS instance or version overwrites the GIS changes made by the tool in Step 3 in the first set of steps above.

For additional configuration information see Long Term GIS Updater.