DCC Alert

N9 — Communications Hub Decommission

SMETS applicability: All

Trigger & context

When and why this alert fires

Event
Decommission of Communications Hub
Trigger
Upon successful completion of Service Request 8.3 Decommission Device for a Communications Hub
Recipient(s)
All Responsible Import Suppliers for that CH function, other than the Responsible EIS / GIS that instigated the Decommissioning Registered ENO Registered GNO
SMETS applicability
All
Payload DUIS applicability
>= 1.0

DUIS delivery

Wrapper and field names

Wrapper element
DCCAlertMessage
Alert code field
DCCAlertCode
Payload field
DCCAlert
Throttling supported
Yes

Payload structure (16.2.1)

DeviceStatusChangeEventsr:DeviceStatusChangeEvent

This payload element is shared across multiple DCC alert codes:N1N2N8N9N16N28N29N44N45

Device withdrawn from Inventory or Device status changed.

FieldTypeMandatoryDescriptionSensitivity
DeviceIDsr:EUIYesDevice ID whose status is changing.Non-Sensitive
DeviceStatusChangesr:DeviceStatusChangeYesChoice of status-change payload.Non-Sensitive

Response codes (16.2.1.3)

DUIS response codes applicable to this alert

I0

DUIS XSD version: >= 1.0

XML examples

Sample DUIS delivery messages

Figure 33 Sample CHF Decommissioning DCC Alert Response Format 16.2.1.4.6 Device Suspended

                <DCCAlertMessage>
<DCCAlertCode>N9</DCCAlertCode>
<DCCAlert>
<DeviceStatusChangeEvent>
<DeviceID>99-00-AA-BB-CC-DD-EE-FF</DeviceID>
<DeviceStatusChange>
<CHFDecommissioning/>
</DeviceStatusChange>
</DeviceStatusChangeEvent>
</DCCAlert>
</DCCAlertMessage>