SOS Configuration Overview

To configure your Smart Operations Solution, follow the configuration instructions as outlined below. These steps assume you already have a working OASyS server that has an RCS service installed.

Step 1: Install ArcFM Desktop on the Responder Server and Responder Client machines. This application is a pre-requisite to installing both Responder applications. When installing ArcFM Solution, ensure you select the option to install Network Adapter for MultiSpeak 3.0 (DMS). This implementation of Network Adapter as well as MultiSpeak 3.0 is necessary to support real-time integration of Responder with DMS and/or OASyS. Network Adapter may be installed on the Responder Server, Responder Client, or both.

Step 2: Install Responder Server, Responder Client, and Responder Web. Install, but DO NOT configure these applications until after performing the next step. When installing, ensure you select the necessary SOS features in the installer (e.g., RealTime Integration DMS if you intend to integrate with DMS).

Step 3: Execute SQL script. All components of the integration rely on the mapping table to ensure data remains properly mapped between the systems. Before starting the Responder configurations, execute on your geodatabase the SQL script located here: Program Files (x86)\Miner and Miner\Responder\Developer Resources\Implementation Scripts\Addons\Oracle\SmartgridSOS_01_CreateSchema.sql. You must execute the script while logged in to the geodatabase as the SMARTGRID user. This script creates the mapping table and its associated components in the Responder Listener Service.

Step 4: Configure Responder. This includes the standard Responder configuration for the Responder Server, Client Machines, and Web Browser as well as any optional configurations you wish to implement.

Step 5: Configure Telvent PubSub Integration. This configuration is performed on the Responder Server. It includes updating configuration files as well as installing certificates to support Telvent PubSub on the Responder Server.

Step 6: Install and configure OASyS DAL Client on your Responder Server. OASyS provides Responder Data Services with telemetry data. For example, OASyS may report a device as Open (NormalStatus=Closed). The Responder Listener relays this information through Data Services and an incident is created in Responder Explorer. The reverse is true when the incident is resolved and the device is Closed. Responder relays the information to OASyS through the Real-Time Framework installed with Responder Server.

Step 7: Install and configure DMS. DMS provides Responder Data Services with non-telemetry data. For example, a DMS operator manually sets a device to Open (NormalStatus=Closed) and makes this change in DMS. The Responder Listener relays this information through Data Services and an incident is created in Responder Explorer. The reverse is true when the Responder user operates a device. Responder relays the information to DMS through the Real-Time Framework installed with Responder Server.

Step 8: Configure Network Adapter. Network Adapter provides DMS with NormalStatus information from the GIS database. Data is exported from a GIS database that uses a MultiSpeak or Electric Data Model or a Common Information Model (CIM). Network Adapter puts it into a MultiSpeak-compliant XML and imports it into DMS. This functionality requires Implementation 6 in the Network Adapter Configuration Guide. It also requires a valid Network Adapter license. (The link to the Network Adapter Configuration Guide requires that you have the Network Adapter/DMS extension installed.)

Step 9: Start Services. Once you have configured OASyS, Responder, and DMS, you must start the necessary services.

Step 10: Export Feeders. Once you've configured OASyS, Responder, DMS, and Network Adapter, you must use NetworkAdapter.exe to export all feeders in your network. This export initiates execution of the pipeline rules that populate mapping information in the Smart Grid tables and send normal status network information to DMS. This step is essential to the success of your implementation.