SCADA Service Configuration

Update the Connection String in the application configuration file Miner.Responder.RxIF.ScadaService.exe.config located in C:\Program Files (x86)\Miner and Miner\Responder\Integration\Scada Service or in the installed path if changed during installation.

Change the log file location, if required. By default the log file will be placed in C:\Responder\Logs.
```
<file value="C:\Responder\Logs\SE.Responder.Integration.ScadaService.log"/>
```

Change the MSMQ ComputerName to the FQDN of the Responder Message Router Server.

Verify that the “ComputerName” is not populated, it should say “ComputerName”:

<wellknown type="Miner.Responder.Shared.IDataServices, Miner.Responder.Shared" url="msmq://FormatName:DIRECT=OS:{ComputerName}\private$\RxServer/DataServices.rem" />

Set the “ComputerName” here:

<channel type="Miner.Responder.Shared.Channels.MSMQ.MSMQChannel, Miner.Responder.Shared" ComputerName="ComputerName " responseTimeout="00:00:03" />

The following configurations are made in the Miner.Responder.RxIF.ScadaService.exe XML configuration file, which by default is found in directory C:\Program Files (x86)\Miner and Miner\Responder\Integration\Scada Service:

IMPORTANT:

Depending on the version of RxIF first implemented, some config key settings might not be present in the Miner.Responder.RxIF.ScadaService.exe configuration file. In that case, you can add them to the config file. For example, if you need to add the ReceiveInterval key, the format is the following:

<add key="ReceiveInterval" value="00:01:00"/>

Config Key	Config Description	Default Config Value
ScadaIncidentRemarks	Remarks on Incidents created as a result of SCADA device operation	Created by SCADA
Scada.MomentaryRemarks	Remarks on Incidents created as a result of device operation of SCADA devices for momentary outages	Auto Reclose occurred between {0} and {1}
ProcessWaitInterval	Time between two subsequent processing cycles for analyzing the SCADA events.	0:00:15
ReceiveInterval	This is the amount an event’s start time can differ from the current time and still be processed. In other words, an event’s start time might be earlier than the current time when it arrives. The ReceiveInterval is how much earlier it is allowed to be and not be considered “stale.” The time value is in the format of hr:mn:sc.	00:01:00
Scada.ProcessMomentaryWaitInterval	Time between two subsequent processing cycles for operating the devices in Responder.	0:00:15
Scada.OptimizeScadaIncidentCreation	Flag to use optimized mechanism of Incident creation/device operation. IMPORTANT: Switching this configuration to TRUE significantly enhances the performance of SCADA incident creation. However, this bypasses Responder code that considers incidents submitted before the SCADA incident, but within a configured time threshold, from being rolled up into SCADA incidents. The threshold defaults to 20 seconds. See Modify Time Threshold for details how adjust the default. This threshold is primarily needed if communication between integrations causes AMI events triggered by a SCADA device going out to reach Responder before the SCADA event that caused that outage in the first place. Otherwise, it is generally safe for SCADA events to not consider pre-existing incidents, calls, and events for roll up.	FALSE
Scada.NumberOfRetryAttempts	Number of tries to operate the device before moving to the new Scada Device operation	0
ScadaClassModelName	Class model name to be assigned to identify the SCADA device in the geodatabase.	SCADAFEATURECLASS
ScadaFieldModelName	Field model name to identify the Scada Device using the Field assigned this model name.	SCADADEVICEID
LogMomentaryOutages	Flag to control the incident creation for the momentary outages.	TRUE
CallRemarks	Remarks on Incidents created by IVR.	Call by IVR.
StaleEventThreshold	EVENTTIME timestamp in HTTP endpoint data received over this threshold compared to system time are not processed and are errored out back to the source system.	02:00
MomentaryEventThreshold	Time between PowerDown and PowerUp events that are within this threshold are considered momentary. IMPORTANT: If the RECEIVETIME of the event at the HTTP endpoint is greater than the PowerUp EVENTTIME, the event is not treated as momentary.	00:01:00
FilterDuplicates	Multiple incidents will not be created when SCADA events are created for the same device.	TRUE
Scada.AllowDelayProcessing	Flag that controls the behavior of device operations and introduces a delay defined by `Scada.AllowedTimeToProcessDevice`.	FALSE
Scada.NumberOfRetryAttempts	Number of times to retry before ignoring the device operation.	0
EventPersistDuration	The amount of time to keep the SCADA events in the RXINT_SCADA_EVENT and RXINT_SCADA_EVENT_PROCESS tables before they are archived to the RXINT_SCADA_EVENT_HISTORY and RXINT_SCADA_EVENT_PROCESS_HIST tables.	02:00:00
ArchivePersistDays	The maximum number of days an event record is kept in the RXINT_SCADA_EVENT_HISTORY and RXINT_SCADA_EVENT_PROCESS_HIST tables.	15
ArchiveInterval	The frequency of running the job responsible for Archive and Delete from Archive.	00:01:00