Responder also provides optional configurations to expand your outage management functionality. The following functionality is optional. However, if you'd like to implement it, it MUST be configured. The following configurations also require that you perform the basic Responder configuration.
- Regions: Regions allow you to break a larger area into districts (areas of responsibility, zones). Dispatchers can be assigned responsibility for specific regions.
- Smart Operations Solution: Responder may be integrated with Telvent's OASyS SCADA application and the DMS analysis engine. You have the option of integrating with either or both applications. The Real-Time Framework (installed with Responder Server) facilitates communication between Responder and OASyS and/or DMS, allowing you to maintain synchronized outage information. This optional functionality requires additional Responder configuration as well as configuration for OASyS, DMS and Network Adapter.
- Support for Esri Replication and GUIDs: Responder provides support for Esri Replication and GUIDs in the Responder database.
- Clustering: Responder maintains high availability and provides failover support by supporting clustering for Responder Services and Message Queues. This section discusses how to set up your clustering environment in Server 2003. For Server 2008 R2 Clustering, click here.
- Auto Reconnect requires no configuration and is enabled by default. The Responder services (e.g., Data Services, Archive Services) examine exceptions related to communication with the geodatabase or SDE server. Should communication fail, the Auto Reconnect functionality monitors whether it can communicate with the geodatabase. Once communication is possible, Auto Reconnect connects to the geodatabase without requiring interaction with the user. This tool requires configuration ONLY if you wish to disable it.
- Archive Explorer: Modify how historical Responder data is displayed in Archive Explorer.
- Support Extended Feeder Manager: Extended Feeder Manager allows the utility manager to define a set of intermediate feeder sources within electric circuits at points downstream of the ultimate power sources recognized by Feeder Manager. Responder can be configured to support an electric network that has multiple voltage levels and has been configured to use Extended Feeder Manager (EFM).
- Affected Transformers: With this configuration transformers that are included in an incident are stored in a new table. This allows you to track all transformers currently affected by an outage.
- Tag Validation: You may configure Responder to verify that the user who placed the tag is the user who removes the tag. Regardless of how tag validation is set up, the user must always enter the correct tag ID when removing a tag.
- Switch Orders: This section discusses various ways you can customize the configuration for managing switch orders.
- Dispatcher Auto-Populate: This section describes how to control whether the Dispatcher field on new incidents is populated with the current user or not.
- PubSub Viewer: This stand-alone executable allows you to view PubSub activity - either the internal Responder publish/subscribe activity or Telvent PubSub. This is a debugging tool that can be used to identify a broken Data Services instance and requires no configuration.
- Web Server: This section contains a number of optional configurations for the Responder web application.
- Client Machines: This section contains several optional configurations for Responder client machines.
- Enhanced Responder Server Performance: You may turn on additional caching to improve the performance of Responder Services.
- Modify Time Threshold: The current time on the server and client machines may likely vary. Incident processing may be impacted when this time varies by more than a minute. The Time Threshold setting allows you to determine just how big this difference may be to prevent incident processing from being affected.
