Responder also provides optional configurations to expand your outage management functionality. The following functionality is optional. However, you must configure the optional functionality that you would like to implement. The following configurations also require that you perform the basic Responder configuration.
- Smart Operations Solution: Responder may be integrated with Schneider Electric'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 supports clustering for Responder Services and Message Queues to maintain high availability and provide failover support. There are many factors to consider when choosing a clustering option like Windows Clustering, virtualization, or drive mirroring. Discussions between your IT professionals and Schneider Electric will provide the best options to support your specific implementation needs. The following examples demonstrate Windows Clustering configuration:
- 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 to disable it.
- Show Callers on Customer Tab: Allows you to disable including customers on the Customers Tab in Responder Explorer that do not include loadpoints.
- Move Fault Upstream Respecting Downstream Phasing: Allows you to set the default action so that only the phases that are already open on a downstream device are open on the upstream device, when moving the fault upstream.
- Disable Jumper Warning for No Upstream Feature: Allows you to remove a jumper that was supplying power to a de-energized area without receiving a warning message first.
- Notify Call Reprocess on Restore: You can configure Responder Explorer to display a notification when you restore an incident at a time earlier than that of the outage time on calls associated with that incident.
- Require Cancel Reason: You can configure Responder Explorer to require users to select the reason for cancelling an incident.
- 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 OASyS 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.
- Setting the Multicast Network Card IP Address: You can set the IP address that matches the network card for Responder services.
- Restart Services via Notify Network Change Button: You can configure the Notify Network Change button to stagger restarting services to eliminate client application down time.
- 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.
- View All When Selecting From ArcMap: When selecting a single feature or multiple features from ArcMap, you can configure Responder Explorer to display the selected incidents or calls within the grid with the other incidents and calls appearing as well.
- Use Feeder ID Instead of Feeder Name: Responder labels feeders with Feeder Name on both display and reports. Apply this configuration to use Feeder ID instead..
