GBCS 16.2 / 0x8F32
Supply Armed
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
6 clauses · 6 linked records- SMETS 4.5.2.2Exact evidence
1 direct clause reference
- Add Credit
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 42 · reference 4.5.2.2
- SMETS 4.5.3.3Exact evidence
1 direct clause reference
- Add Credit
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 42 · reference 4.5.3.3
- SMETS 4.5.3.6Exact evidence
1 direct clause reference
- Adjust Meter Balance
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 42 · reference 4.5.3.6
- SMETS 5.6.2.2Exact evidence
1 direct clause reference
- Add Credit
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 42 · reference 5.6.2.2
- SMETS 5.6.3.3Exact evidence
1 direct clause reference
- Add Credit
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 42 · reference 5.6.3.3
- SMETS 5.6.3.6Exact evidence
1 direct clause reference
- Adjust Meter Balance
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 42 · reference 5.6.3.6
Device Specific Details
- GSME
- Supplier
- ESME
- Supplier and Network Operator
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 →