GBCS 16.2 / 0x8F52

Event Log Cleared

Alert Details

WAN: NMandatedN/APre-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

7 clauses · 7 linked records
  • CHTS 4.5.1.3Exact evidence

    1 direct clause reference

    • Clear CHF Event Log

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 68 · reference 4.5.1.3

  • SMETS 4.5.3.8Exact evidence

    1 direct clause reference

    • Clear Event Log
    GSME

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 68 · reference 4.5.3.8

  • CHTS 4.5.4.2Exact evidence

    1 direct clause reference

    • Clear GPF Event Log

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 68 · reference 4.5.4.2

  • SMETS 5.6.3.8Exact evidence

    1 direct clause reference

    • Clear Auxiliary Controller Event Log
    ESME

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 68 · reference 5.6.3.8

  • SMETS 5.6.3.9Exact evidence

    1 direct clause reference

    • Clear Event Log
    ESME

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 68 · reference 5.6.3.9

  • SMETS 9.5.2.3Exact evidence

    1 direct clause reference

    • Clear Auxiliary Controller Event Log
    SAPC

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 68 · reference 9.5.2.3

  • SMETS 9.5.2.4Exact evidence

    1 direct clause reference

    • Clear Event Log
    SAPC

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 68 · reference 9.5.2.4

Device Specific Details

GSME
N/A
ESME
N/A
CHF
N/A
GPF
N/A

Message Patterns and Examples

This row is not a WAN Alert, so it is never transmitted to the DSP or to a Known Remote Party and has no delivery pattern. It is recorded in a Device log and read through the corresponding log-read Service Request.