One of your ideas has been delivered from your suggestion.Update Head-End Registration Status Based on Device Status Check Outcome

In previous releases the application was unable to correctly update a controllable device's registration status. This limitation stemmed from the acknowledgement message received from external systems (like Edge DERMS) for the customer asset synchronization request message. As the external system's response lacks a device-specific registration status, the application was unable to correctly update the status for multiple devices included in a single customer asset synchronization  request.

Adding a device to a customer's program enrollment requires registering that device with the head-end system. This is true whether it's a new customer enrolling for the first time or an existing customer adding another device to their current subscription. Whenever a customer unenrolls from a program, or a device is replaced, that device must also be deregistered from the head-end system.

This feature introduces an acknowledgment operation on the existing inbound web service. This allows external systems to provide a more comprehensive response to a customer asset synchronization request, including a message-level acknowledgment and the head registration status for each individual device included in the original request. The application processes this information and automatically updates each device's Head End Registration status flag to either 'Registered' or 'De-registered' accordingly. 

This automated process is crucial for maintaining data integrity and enabling seamless, end-to-end device management. By capturing updates to a device's head-end registration status directly from an external source, this feature ensures the accuracy of the device's communication status. This capability also provides a significant operational benefit: it gives users the ability to report on any failures that may occur during the registration or deregistration process. If an external system reports a failure for a specific device, this information is automatically logged, allowing users to quickly identify and troubleshoot issues.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

To configure feature, refer to About Controllable Assets and Devices in the Oracle Utilities Digital Asset Cloud Service/Digital Asset Management Business User Guide and Digital Asset Cloud Service / Digital Asset Management Inbound Web Services in the Oracle Utilities Digital Asset Cloud Service/Digital Asset Management Administrative User Guide for more information.