UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

GBCS 16.2 / 0x8F1C

Firmware Verification Failed

Alert Details

WAN: YUse Case Specific Alert StructureMandatedCriticalPre-config: No

Cross-specification evidence

Technical requirement relationships

The source clauses below explicitly relate this alert to equipment behaviour. Confidence and evidence labels show how each relationship was established.

Alert touchpoint

4 clauses · 4 linked records
  • SMETS 4.4.10.1Exact evidence

    1 direct clause reference

    • General
    GSME

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 20 · reference 4.4.10.1

  • SMETS 5.5.10.1Exact evidence

    1 direct clause reference

    • General
    ESME

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 20 · reference 5.5.10.1

  • SMETS 8.4.4.1Reviewed evidence

    1 direct clause reference

    • General
    HCALCS

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 20 · reference 8.4.1.1

  • SMETS 9.4.4.1Exact evidence

    1 direct clause reference

    • General
    SAPC

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 20 · reference 9.4.4.1

Device Specific Details

GSME
Supplier
ESME
Supplier
HCALCS
Supplier

DUIS Annex 15 / 15.4.1

Device Alert payload structure

This alert carries additional structured payload defined by DUIS Annex 15 section 15.4.1, delivered inside ra:DeviceAlertContent asFirmwareVerificationDeviceAlert.

Payload root
FirmwareVerificationDeviceAlert
Payload type
FirmwareVerificationDeviceAlertType
Annex section
15.4.1 — Device Alert 0x8F1C and 0x8F72 Firmware Verification Status

Message codes and device contexts

Message codeDevice contextMessage name
00CEElectricity Alert (ESME)Firmware Distribution Receipt Alert (ESME)
00CFGas Alert (GSME)Firmware Distribution Receipt Alert (GSME)
012CElectricity Alert (HCALCS)Firmware Distribution Receipt Alert (HCALCS)

Payload fields

FieldTypeMandatoryUnitsDescriptionSensitivity
ManufacturerImageHashxs:hexBinary (maxLength = 32)YesN/AFirmware hash associated with the firmware update. Presented as 64 hex characters excluding colon separators.Non-Sensitive

Message Patterns and Examples

View the step-by-step alert delivery pattern — from device event through WAN transmission to Known Remote Party notification — with available XML examples.

View Message Patterns →