Skip to main content

Device Control Transactions

Overview​

The Device Control Transactions package enables the system to send commands directly to meters and/or related relays. This module provides a standardized interface for requesting meter readings and controlling device functions such as connect/disconnect operations.

Supported Message Types​

The system supports the following Common Interface Model (CIM) IEC 61968-9 message types:

  • GetMeterReading
  • EndDeviceControl

Process Flow​

Command Type Selection

  • User selects the appropriate command type
  • Supported command types include:
    • Get Meter Reading: Request readings from HES or directly from meter
    • End Device Control: Connect or disconnect meter's breaker or connected relay

Command Parameter Definition

  • For Get Meter Reading commands:
    • Define which channel readings are requested
    • Specify the period for which readings are requested
  • For End Device Control commands:
    • Define operation (connect or disconnect)
    • Specify control type (meter's breaker or relay)
    • Identify relay name (the relay ID to switch)

Business Rules & Customization Points​

Command Request Rules​

On-Demand Read Request

  • Rule : Standard_On_Demand_Read_Request_Publishing
  • Purpose : Formats and publishes read requests to the device or head-end system
  • Customization : Configure request priorities, timeouts, and retry logic

End Device Control

  • Rule : Standard_End_Device_Control_Publishing
  • Purpose : Formats and publishes control commands to devices
  • Customization : Configure safety checks, authorization levels, and confirmation requirements

Configuration Components​

Flow Designs​

  • Standard_On_Demand_Reads_Flow
  • Standard_End_Device_Control_Flow

Rules​

  • Standard_On_Demand_Read_Request_Forwarding
  • Standard_End_Device_Control_Forwarding

Integration Patterns​

The Device Control Transactions module typically integrates with:

  • Head-end Systems (HES)

Customization Opportunities​

Partners can customize this module by:

  1. Adding pre-command validation logic
  2. Implementing customer notification workflows
  3. Creating specialized command types for specific device models
  4. Adding command batching capabilities for bulk operations
  5. Integrating with workflow systems for command approval