GBCS 16.2 / 0x8162
User Interface Command Input 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- SMETS 4.5.2Exact evidence
1 direct clause reference
- User Interface Commands
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 79 · reference 4.5.2
- SMETS 5.6.2Exact evidence
1 direct clause reference
- User Interface Commands
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 79 · reference 5.6.2
- SMETS 5.22.1Exact evidence
1 direct clause reference
- User Interface Commands
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 79 · reference 5.22.1
- SMETS 5.25.1Exact evidence
1 direct clause reference
- User Interface Commands
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 79 · reference 5.25.1
- SMETS 9.13.1Exact evidence
1 direct clause reference
- User Interface Commands
SAPCEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 79 · reference 9.13.1
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.