The following operations are supported. For a formal definition, please review the Service Description.

• AccumulatedValueChangedNotification
  Publisher notifies subscriber of changes in accumulator values by sending an array of changed accumulatedValue objects. Publisher returns failed transactions using an array of errorObjects.
• AnalogChangedNotificationByPointID
  Publisher notifies subscriber of changes in analog values by sending an array of changed scadaAnalog objects. subscriber returns failed transactions using an array of errorObjects. The transactionID calling parameter links this published data response with the previously received InitiateAnalogReadByPointID method call. If no points are identified, the server shall return analogs for all analog points.
• ControlActionCompleted
  THIS METHOD IS INCLUDED FOR DISCUSSION ONLY; IT SHOULD NOT BE IMPLEMENTED UNTIL THE TECHNICAL COMMITTEE ACCEPTS THE FORM OF THE METHOD. DA notifies SCADA that a previously requested scada control action request has been completed. SCADA returns the status of the control action in a modified scadaControl object, containing an updated controlStatus element. The transactionID parameter is used to link the InitiateControl and ControlActionCompleted method calls.
• DRProgramEnrollmentNotification
  The DR program enrollment agent (publisher) notifies subscribers of customers who have subscribed to an existing DR Program. Subscriber returns information about failed transactions in an array of errorObjects. The message header attribute 'registrationID' should be added to all publish messages to indicate to the subscriber under which registrationID they received this notification data.
• DRProgramUnenrollmentNotification
  The DR program enrollment agent (publisher) notifies subscribers of customers who have ended their enrollment in an existing DR Program. Subscriber returns information about failed transactions in an array of errorObjects. The message header attribute 'registrationID' should be added to all publish messages to indicate to the subscriber under which registrationID they received this notification data.
• GetAllDRPrograms
  Requests a list of DR programs. The calling parameter lastReceived is included so that large sets of data can be returned in manageable blocks. lastReceived should carry an empty string the first time in a session that this method is invoked. When multiple calls to this method are required to obtain all of the data, the lastReceived should carry the objectID of the last data instance received in subsequent calls. If the sessionID parameter is set in the message header, then the server shall respond as if it were being asked for a GetModifiedXXX since that sessionID; if the sessionID is not included in the method call, then all instances of the object shall be returned in response to the call.
• GetAllDRProgramsByStatus
  Requests a list of DR programs for a particular value of DRProgramStatus. The permissible values of DRProgramStatus are: 'Active', 'Suspended', 'Rescinded', 'Other' and 'Unknown'. Active status means that the DRProgram has an ending date in the future and customer enrollment is possible, even if control is not currently active. A status of Suspended implies that a customer can still be enrolled in the program but no load control or pricing signals will be sent. A status of Rescinded means that a customer cannot be enrolled in the DRProgram. The Other and Unknown statuses are included for extensibility, but their use is discouraged. If the DRProgramStatus is set to be Other, the DR Program Owner should populate the OtherDRProgramStatus element with the non-standard status value. THIS METHOD HAS BEEN DEPRECATED AND WILL BE REMOVED IN V5.0. IMPLEMENTERS SHOULD USE THE GetDRProgramsByStatus METHOD RATHER THAN THIS ONE.
• GetDRProgramsByStatus
  Requests a list of DR programs for a particular value of DRProgramStatus. The permissible values of DRProgramStatus are: 'Active', 'Suspended', 'Rescinded', 'Other' and 'Unknown'. Active status means that the DRProgram has an ending date in the future and customer enrollment is possible, even if control is not currently active. A status of Suspended implies that a customer can still be enrolled in the program but no load control or pricing signals will be sent. A status of Rescinded means that a customer cannot be enrolled in the DRProgram. The Other and Unknown statuses are included for extensibility, but their use is discouraged. If the DRProgramStatus is set to be Other, the DR Program Owner should populate the OtherDRProgramStatus element with the non-standard status value.
• GetMethods
  Requester requests list of methods supported by SCADA.
• OutageEventChangedNotification
  Publisher notifies subscriber of a change in OutageEvent by sending an array of changed OutageEvent objects. Subscriber returns information about failed transactions using an array of errorObjects. The message header attribute 'registrationID' should be added to all publish messages to indicate to the subscriber under which registrationID they received this notification data.
• PingURL
  Requester pings URL of SCADA to see if it is alive. Returns errorObject(s) as necessary to communicate application status.
• PointSubscriptionListNotification
  Client notifies SCADA of a new list of points to which it would like to subscribe. This list replaces any prior lists. The client SHALL provide the RegistrationID under which this subscription is being requested, unless the SCADA server does not support automated registration for services. If automated subscription is supported, the subscriber SHALL include the RegistrationID in the message header for this method. SCADA returns failed transactions by returning an array of errorObjects. Subscriber specifies the URL to which information is to be published by sending the responseURL.
• PowerFactorManagementEventNotification
  This method will be published to notify subscribers that the status of a capacitor switch has changed, either in response to an InitiatePowerFactorEvent, or as a result of a capacitor switch failure. Subscriber returns information about failed transactions in an array of errorObjects.The transactionID calling parameter links this Notification with the corresponding InitiatePowerFactorManagementEvent, if any. The message header attribute 'registrationID' should be added to all publish messages to indicate to the subscriber under which registrationID they received this notification data.
• SCADAAnalogChangedNotification
  Client notifies DA of changes in analog values by sending an array of changed scadaAnalog objects. DA returns failed transactions using an array of errorObjects.
• SCADAAnalogChangedNotificationByPointID
  SCADA Notifies DA of changes in a specific analog value, chosen by scadaPointID, by sending a changed scadaAnalog object. If this transaction fails, DA returns information about the failure in a SOAPFault.
• SCADAAnalogChangedNotificationForPower
  SCADA Notifies DA of changes in a specific analog value, limited to power analogs, by sending an arrray of changed scadaAnalog objects. DA returns failed transactions using an array of errorObjects.
• SCADAAnalogChangedNotificationForVoltage
  SCADA Notifies DA of changed analog values, limited to voltage analogs, by sending an array of changed scadaAnalog objects. DA returns failed transactions using an array of errorObjects.
• SCADAPointChangedNotification
  SCADA Notifies DA of changes in SCADA point definitions by sending an array of changed scadaPoint objects. DA returns failed transactions using an array of errorObjects.
• SCADAPointChangedNotificationForAnalog
  SCADA Notifies DA of changes in SCADA point definitions, limited to Analog points, by sending an array of changed scadaPoint objects. DA returns failed transactions using an array of errorObjects.
• SCADAPointChangedNotificationForStatus
  SCADA Notifies DA of changes in SCADA point definitions, limited to Status points, by sending an array of changed scadaPoint objects. DA returns failed transactions using an array of errorObjects.
• SCADAStatusChangedNotification
  SCADA Notifies DA of changes in point status by sending an array of changed scadaStatus objects. DA returns failed transactions using an array of errorObjects.
• SCADAStatusChangedNotificationByPointID
  SCADA Notifies DA of changes in the status of a specific point, chosen by PointID, by sending a changed scadaStatus object. If this transaction fails, DA returns information about the failure in a SOAPFault.
• StatusChangedNotificationByPointID
  Publisher notifies subscriber of changes in point status by sending an array of changed scadaStatus objects. Subscriber returns failed transactions using an array of errorObjects. The transactionID calling parameter links this published data response with the previously received InitiateStatusReadByPointID method call. If no points are identified, the server shall return statuses for all status points.
• SwitchingOrderChangedNotification
  Publisher notifies subscriber of new or changed switching order(s) by sending switchingOrder object(s). Subscriber returns information about failed transactions in an array of errorObjects. The message header attribute 'registrationID' should be added to all publish messages to indicate to the subscriber under which registrationID they received this notification data.