GBCS 16.2 / 0x8155
Immediate HAN Interface Command Received but not Successfully Actioned
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
5 clauses · 5 linked records- CHTS 4.5.1Exact evidence
1 direct clause reference
- CHF Interface Commands
Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 71 · reference 4.5.1
- SMETS 4.5.3Exact evidence
1 direct clause reference
- HAN Interface Commands
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 71 · reference 4.5.3
- CHTS 4.5.4Exact evidence
1 direct clause reference
- GPF Interface Commands
Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 71 · reference 4.5.4
- SMETS 5.6.3Exact evidence
1 direct clause reference
- HAN Interface Commands
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 71 · reference 5.6.3
- SMETS 9.5.2Exact evidence
1 direct clause reference
- HAN Interface Commands
SAPCEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 71 · reference 9.5.2
Device Specific Details
- GSME
- Supplier
- ESME
- Supplier
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.