Configuring Admin Data in Oracle Utilities Digital Asset Cloud Service

This section describes the admin data setup in Oracle Utilities Digital Asset Cloud Service related to the integration. The Admin menus can be configured to be grouped alphabetically or by functional groups. The descriptions that follow will include both groupings.

• Message Senders

• External System

• Inbound Web Service (IWS)

• Master Configuration

• Head End System

• Activity Type

• Communication Type

• Service Task Type

• Sync Request Process

• Scheduling Batch Jobs

Message Senders

Create a new or update an existing real-time message sender for each Oracle Utilities Digital Asset Cloud Service Outbound Message.

To create a message sender:

1. In the Admin menu navigate to [M or Integration] > Message Sender > Add.

2. Enter a unique message sender and its description.

3. Populate the following values:

• Message Sender: Sender name in Oracle Utilities Digital Asset Cloud Service

• Description: Sender’s description

• Invocation Type: Real-time

• Message Class: RTJSONSNDR (Sender for real-time HTTP / JSON messages)

• Active: Select the check box.

• MSG Encoding: UTF-8 message encoding

4. Select the Context tab and set values for the following context types:

• HTTP Header: application/json

• HTTP Login User: User ID to access OIC

• HTTP Login Password: Password to access OIC

• HTTP Method (POST/GET): POST

• HTTP Timeout: 300

External System

Create a new or update an existing external system to support the Distributed Energy Resources Management System.

To create an external system:

1. In the Admin menu navigate to [M or Integration] > External System > Add.

2. Enter a unique External System and its Description.

3. Associate the outbound message types created to the external system. For each outbound message type, set the following:

• Outbound Message Type

• Controllable Device Status Check: Use the X1-CTRLDVCS (Controllable Device Status Check) outbound message type

• Synchronize Digital Asset: Use the X1-NMSDASMSG (Synchronize Digital Asset (NMS)) outbound message type

• Processing Method: Real-time

• Message Sender: Set the corresponding message sender for the outbound message

• Date/Time Format: XSD

• JSON Conversion Method: Base JSON conversion

Inbound Web Service (IWS)

The following REST inbound web services are delivered for this integration:

• X1-ProgramEnrollment

• X1-ControllableDeviceStatus

• X1-ProgramEventParticipation

The full URI component for the REST inbound web service is configurable.

The Oracle Utilities Digital Asset Cloud Service documentation provides instructions about the one-time setup. Refer to the Documentation and Resources section in Configuring Oracle Utilities Digital Asset Cloud Service for information about documentation resources.

Master Configuration

This section describes the master configuration details for the integration. The following Master Configurations can be found from the Admin menu > [M or General] > Master Configuration.

• Digital Asset Integration Master Configuration

Head End System

Create a new or update an existing head end system for each external energy aggregator interfaced to Oracle Utilities Live Energy Connect.

To create a head end system:

1. In the Admin menu navigate to [H or Digital Asset Management] > Head End System > Add.

2. Enter a unique head end system and its description.

3. Specify the external system created for Oracle Utilities Grid Edge Distributed Energy Resources Management System.

4. Add a processing method for processing role Device Status Check. On the processing method, set the following:

• Default Business Object: X1-CtrlDvcStatusCheckComm (Controllable Device - Device Status Check)

• Default Outbound Message Type: Controllable Device Status Check

Activity Type

Create a new or update an existing activity type for the Controllable Device Status Check activity.

To create an activity type:

1. In the Admin menu, navigate to [A or Communication].

2. Add or edit the Controllable Device Status Check activity and its description. Refer to the embedded help for more information.

Communication Type

Create a new or update an existing communication type for the following Communication Types:

• Controllable Device: Device Status Check

• Controllable Device: Device Status Check Response

To create a communication type:

1. In the Admin menu navigate to [C or Communication Type].

2. Enter a unique communication type and its description. Refer to the embedded help for more information.

Service Task Type

Create a new or update an existing service task type for the following Service Task Type Business Objects:

• Digital Asset Enrollment Request Task Type

• Digital Asset Unenrollment Request Task Type

To create a service task type:

1. In the Admin menu navigate to [S or General].

2. Enter a unique service task type and its description. Refer to the embedded help for more information.

Sync Request Process

The Sync Request Process is used to synchronize customer enrollment and unenrollment data from Oracle Utilities Digital Asset Cloud Service to Oracle Utilities Grid Edge Distributed Energy Resources Management System. Maintenance Object - Audit algorithms are responsible for instantiating subscription based sync request records.

To configure a Maintenance Object:

1. In the Admin menu, navigate to [M or Database] > Maintenance Object > Search.

2. Navigate to the following Maintenance Objects and configure the following:

• Usage Subscription (D1-US): Under the Maintenance Object - Options tab, add the “Sync Request BO” MO Option with an option value “X1-NMSDigitalAssetCustSync (NMS Digital Asset Customer Sync Request)”. Plug in the F1-GCHG-CDCP (Generic Change Data Capture) MO audit algorithm. When a change is detected on a program subscription, this algorithm is responsible for instantiating the sync request.

• Contact (D1-CONTACT): Plug in the X1-CNTCDCDA (Contact Change Data Capture (Digital Asset Subscription Based)) MO audit algorithm. When a change is detected on a contact associated to an eligible program subscription, this algorithm is responsible for instantiating the sync request.

• Device (D1-DEVICE): Plug in the X1-DVCCDCDA (Device Change Data Capture (Digital Asset Subscription Based)) MO audit algorithm. When a change is detected on a controllable device associated to an eligible program subscription, this algorithm is responsible for instantiating the sync request.

• Service Point (D1-SP): Plug in the X1-LOCCDCDA (Location Change Data Capture (Digital Asset Subscription Based)) MO audit algorithm.When a change is detected on a device location associated to an eligible program subscription, this algorithm is responsible for instantiating the sync request.

Scheduling Batch Jobs

Make sure to schedule the following batch jobs in the order they are listed:

1. X1-CALAS: Updates control scores of enrolled devices with the latest information.

2. X1-SDCSE: Extracts the latest control scores of enrolled devices.