DCC Alerts
DCC Alert catalogue — 13 / 16.2.1
DCC Alerts are generated by DCC Data Systems in response to device or infrastructure events. They are delivered via DCCAlertMessage using 66 codes: AD1, N1–N65 excluding N32, which DS.0226 Table 49 does not define, and N999. Select a row to view trigger detail, payload structure, and XML examples.
DUIS applicability is exact DCCAlertMessage/DCCAlertCode membership across the checked-in DUIS XSDs, covering DUIS 1.1–5.5. Search the catalogue or combine filters to find matching alerts.
Compare DUIS XSD → for DCC Alert code additions and withdrawals.
Showing 66 of 66 DCC Alerts
No DCC Alerts match your search and filters. Try another search or clear the filters.
| Code | Name | Trigger | Recipient(s) | SMETS | DUIS | Payload element | |
|---|---|---|---|---|---|---|---|
AD1 | Power Outage Event | Power Outage Event received from CSP | Registered EIS Registered ENO Registered GIS Registered GNO | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | PowerOutageEvent | Detail → |
N1 | Electricity Smart Meter Decommission or withdrawal | Decommissioning or withdrawal of an Electricity Smart Meter Device | Registered ENO and, if applicable, registered EES | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceStatusChangeEvent | Detail → |
N2 | Gas Smart Meter Decommission or withdrawal | Decommissioning or withdrawal of Gas Smart Meter Device | Registered GNO | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceStatusChangeEvent | Detail → |
N3 | Cancellation of “Future Dated (DSP)” requests because of CoT | Cancellation of “Other User” “Future Dated (DSP)” Services not yet submitted to the Devices in the Electricity or Gas Smart Metering System | All applicable Future Dated (DSP) Request senders | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N4 | Schedule removal because of CoT | Removal of “Other User” “DSP Scheduled” schedules for Devices in the Electricity or Gas Smart Metering System | All applicable Schedule “owners” | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DSPScheduleRemoval | Detail → |
N5 | Schedule removal because of Device withdrawal | “DSP Scheduled” schedule removal6 | All applicable Schedule “owners” | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DSPScheduleRemoval | Detail → |
N6 | Schedule removal because of Device decommission | “DSP Scheduled” schedule removal | All applicable Schedule “owners” | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DSPScheduleRemoval | Detail → |
N7 | “DSP Scheduled” / “Future Dated (DSP)” access control failure | “DSP Scheduled” / “Future Dated (DSP)” access control failure (Authorisation, Device status, GBCS compatibility check) | Schedule “owner” / “Future Dated (DSP) request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N8 | Device removed from Inventory- Pending Status expired | Removal of Device from Inventory | Original DCC Service User that requested addition of the Device to the DCC Inventory | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceStatusChangeEvent | Detail → |
N9 | Communications Hub Decommission | Decommission of Communications Hub | All Responsible Import Suppliers for that CH function, other than the Responsible EIS / GIS that instigated the Decommissioning Registered ENO Registered GNO | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceStatusChangeEvent | Detail → |
N10 | “Future Dated (Device)” command time-out | “Future Dated(Device)” command time-out | “Future Dated (Device)” request sender | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N11 | “DSP Scheduled” / “Future Dated (DSP)” command time-out | “DSP Scheduled” / “Future Dated (DSP)” command time-out | Schedule “owner” / “Future Dated (DSP) request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N12 | Failure to deliver command to Device | Failure to deliver command to Device | Request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N13 | Failure to receive response from Device | Failure to receive response from Device | Request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N14 | Sequenced Request Failure | Sequenced Request Failure | Request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N15 | Sequenced Request received Out of Order | Sequenced Request received Out of Order | Request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N16 | Device Identity Confirmation | Device Identity Confirmation by Registered Energy Supplier – either first setting or update to previous setting | Registered ENO Registered GNO | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceStatusChangeEvent | Detail → |
N17 | Schedule removal because of CoS | Previously registered Supplier “DSP Scheduled” schedule removal | Previously registered EIS Previously registered GIS | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DSPScheduleRemoval | Detail → |
N18 | Firmware Version / Hash mismatch | Firmware Version / Hash mismatch | Update Firmware request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareDistributionFailure | Detail → |
N19 | Firmware Distribution Device ID identification failure | Firmware Distribution Device ID identification failure | Update Firmware request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareDistributionFailure | Detail → |
N20 | Firmware image provided is too large | Firmware image provided is too large | Update Firmware request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareDistributionFailure | Detail → |
N21 | Unknown Firmware | Unknown Firmware | Update Firmware request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareDistributionFailure | Detail → |
N22 | Failure to deliver Update Firmware Command to CSP / S1SP | Failure to deliver Update Firmware command to CSP / S1SP | Update Firmware request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareDistributionFailure | Detail → |
N23 | Failure to receive Update Firmware Command Validation response from CSP / S1SP | Failure to receive Update Firmware Command Validation response from CSP / S1SP | Update Firmware request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareDistributionFailure | Detail → |
N24 | Successful Communications Hub Function Whitelist Update | Communications Hub Function Whitelist Update | Update HAN Device Log request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | UpdateHANDeviceLogResult | Detail → |
N25 | Potentially Unsuccessful Communications Hub Function Whitelist Update | Communications Hub Function Whitelist Update | Update HAN Device Log request sender | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | UpdateHANDeviceLogResult | Detail → |
N26 | Update Security Credentials (CoS) – access control failure | Update Security Credentials (CoS) – access control failure | Update Security Credentials (CoS) request sender | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | ChangeOfSupplier | Detail → |
N27 | Device CoS | New Import Supplier for Device | Previously registered EIS Previously registered GIS | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | ChangeOfSupplier | Detail → |
N28 | Device Suspended | Device Suspended | Registered EIS Registered GIS Registered ENO Registered GNO | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceStatusChangeEvent | Detail → |
N29 | Device Restored from Suspension | Device Restored from Suspension | Registered EIS Registered GIS Registered ENO Registered GNO | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceStatusChangeEvent | Detail → |
N30 | CHF Device Log Restored | CHF Device Log Restored | All Responsible Import Suppliers for that CHF, other than the Responsible EIS / GIS that submitted the Request | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceLogRestored | Detail → |
N31 | GPF Device Log Restored | GPF Device Log Restored | All Responsible Import Suppliers for that CHF, other than the Responsible EIS / GIS that submitted the Request | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceLogRestored | Detail → |
N33 | Cancellation of “Future Dated (DSP)” requests because of Device Decommission | Cancellation of all “Future Dated (DSP)” Services not yet submitted to the Device | All applicable Future Dated (DSP) Request senders | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N34 | Cancellation of “Future Dated (DSP)” requests because of CHF Decommission | Cancellation of all “Future Dated (DSP)” Services not yet submitted to the CHF and its associated GPF | All applicable Future Dated (DSP) Request senders | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N35 | Cancellation of “Future Dated (DSP)” requests because of Device Withdrawal | Cancellation of all “Future Dated (DSP)” Services not yet submitted to the Device6 | All applicable Future Dated (DSP) Request senders | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N36 | Cancellation of “Future Dated (DSP)” requests because of CHF Withdrawal | Cancellation of all “Future Dated (DSP)” Services not yet submitted to the CHF and Devices in its Whitelist | All applicable Future Dated (DSP) Request senders | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N37 | Schedule removal because of CHF withdrawal | “DSP Scheduled” schedule removal for ESME, GSME and GPF in the Whitelist | All applicable Schedule “owners” | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DSPScheduleRemoval | Detail → |
N38 | Cancellation of “Future Dated (DSP)” requests because of CoS | Cancellation of all “Future Dated (DSP)” Services not yet submitted to the Device from the previously registered Supplier | Previously registered EIS Previously registered GIS | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N39 | PPMID Alert | A PPMID Device generates a Device Alert as defined by GBCS | Registered EIS Registered GIS | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | PPMIDAlert | Detail → |
N40 | Schedule removal because of Device suspension | “DSP Scheduled” schedule removal | All applicable Schedule “owners” | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DSPScheduleRemoval | Detail → |
N41 | Cancellation of “Future Dated (DSP)” requests because of Device suspension | Cancellation of all “Future Dated (DSP)” Services not yet submitted to the Device | All applicable Future Dated (DSP) Request senders | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N42 | Security Credentials updated on device | Security Credentials updated on Device by Service Request 6.15.1 or 6.21 | The Remote Party whose certificate has been placed on the Device | All | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | SecurityCredentialsUpdated | Detail → |
N43 | PPMID Removal | A PPMID Device has been removed from the HAN via Service Request 8.11 | All Responsible Import Suppliers for that CHF, other than the Responsible EIS / GIS that submitted the Request | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | PPMIDRemoval | Detail → |
N44 | SMKI Recovery Procedure Complete (Placing ACB Credentials on the Device)9 | SMKI Recovery Procedure is complete - at least one of the KRP Certificates on the Device has been replaced with an ACB Certificate | Registered EIS Registered GIS | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceStatusChangeEvent | Detail → |
N45 | SMKI Recovery Procedure Complete | SMKI Recovery Procedure is complete - all required Certificates on the Device have been recovered | Registered EIS Registered GIS Registered ENO Registered GNO | SMETS2 or later | 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DeviceStatusChangeEvent | Detail → |
N46 | Quarantined Request – Anomaly Detection User Threshold Breach | An Anomaly Detection User-specific volume threshold has been breached | Request sender | All | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | QuarantinedRequest | Detail → |
N47 | Quarantined Request – Anomaly Detection DCC Threshold Breach | An Anomaly Detection DCC system-wide volume threshold has been breached | Request sender | All | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | QuarantinedRequest | Detail → |
N48 | Quarantined Request – Anomaly Detection Attribute Limits Breach | An Anomaly Detection Attribute Limit has been breached | Request sender | SMETS2 or later | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | QuarantinedRequest | Detail → |
N49 | Firmware Version Updated in the Smart Metering Inventory | Device’s Firmware Version updated in the Smart Metering Inventory | Responsible EIS Responsible GIS | All | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareVersionMismatch | Detail → |
N50 | Firmware Version no longer valid on the CPL | Device’s Firmware Version updated in the Smart Metering Inventory, and Device Status set to ‘Suspended’ | Responsible EIS Responsible GIS | All | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareVersionMismatch | Detail → |
N51 | Invalid Firmware Version | Device’s Firmware Version is unknown (not in the CPL) D evice’s Firmware Version updated in the Smart Metering Inventory and Device Status set to ‘Suspended’ | Responsible EIS Responsible GIS | All | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareVersionMismatch | Detail → |
N52 | GSME Firmware Version Mismatch | GSME’s Firmware Version returned by the GPF is different from that in the Smart Metering Inventory GSME’s Firmware Version not updated in the Smart Metering Inventory | Responsible GIS | All | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareVersionMismatch | Detail → |
N53 | Command not delivered to ESME | CHF unable to deliver Command to ESME. The creation of this DCC Alert is in direct response to the receipt by the DCC of a Device Alert 0x8F84 - Failure to Deliver Remote Party Message to ESME (as defined by GBCS) from the CHF. | Request sender | SMETS2 or later | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommandFailure | Detail → |
N54 | Dual Band CH Alert | A Dual Band CH Device generates a Device Alert as defined by GBCS | Responsible EIS Responsible GIS | SMETS2 or later | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DualBandCHAlert | Detail → |
N55 | S1SP Service Request validation failure | DCC Alert indicating an error with a Service Request, initiated by an S1SP, or a notification by an S1SP | Service Request sender | SMETS1 | 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | S1SPAlertDSP | Detail → |
N56 | S1SP provision of a prepayment top-up UTRN | DCC Alert containing a prepayment top-up UTRN provided by an S1SP | Service Request sender | SMETS1 | 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | S1SPAlertDSP | Detail → |
N57 | SMETS1 CHF or SMETS1 PPMID Firmware notification | Notification of intended or successful Firmware version update of a SMETS1 CHF or SMETS1 PPMID | Gas Supplier associated with the SMETS1 CHF / SMETS1 PPMID | SMETS1 | 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | SMETS1CHFirmwareNotification | Detail → |
N58 | Auxiliary Controller configuration change | APC / ALCS / HCALCS configuration changed on ESME | Registered ENO | SMETS2 or later | 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | ALCSHCALCSConfigurationChange | Detail → |
N59 | Firmware update in progress | Notification of a valid request from a Supplier to update the Firmware of a SMETS2 PPMID. | All Responsible Import Suppliers for that Device, other than the Service Request sender | SMETS2 or later | 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | FirmwareUpgradeRequested | Detail → |
N60 | Failed to deliver Firmware image to Comms Hub | Failed to deliver Firmware image to Comms Hub | Update Firmware request sender | SMETS2 or later | 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CSPFirmwareDeliveryStatus | Detail → |
N61 | Firmware image successfully delivered to Comms Hub | Firmware image successfully delivered to Comms Hub | Update Firmware request sender | SMETS2 or later | 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CSPFirmwareDeliveryStatus | Detail → |
N62 | Comms Hub Alert | A Comms Hub generates a Device Alert as defined by GBCS | Responsible EIS Responsible GIS (For firmware delivery status the Alerts will be delivered to the sender of the Request) | SMETS2 or later | 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | CommsHubAlert | Detail → |
N63 | ECoS Alert | The ECoS Party sends a message to DSP for delivery to the relevant Service User | Responsible EIS Responsible GIS | All | 5.1, 5.2, 5.3, 5.4, 5.5 | ECoSAlert | Detail → |
N64 | Comms Hub Firmware Activation | Successful Comms Hub Firmware Activation | All Responsible Suppliers | SMETS2 or later | 5.1, 5.2, 5.3, 5.4, 5.5 | CommsHubFirmwareActivation | Detail → |
N65 | CoS Certificate Alert | A Device is installed with an unsupported CoS Certificate in its CoS Party Trust Anchor Cell. | Responsible EIS Responsible GIS | SMETS2 or later | 5.1, 5.2, 5.3, 5.4, 5.5 | CoSCertificateAlert | Detail → |
N999 | DUIS Version Mismatch | DCC Service User DUIS version incompatible with DCC Alert or Service Response to be sent | Recipient of the incompatible DCC Alert or Service Response | All | 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5 | DUISVersionMismatch | Detail → |