GBCS 16.2 / 0x8F3F
Unauthorised Physical Access - Tamper Detect
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- SMETS 4.3Exact evidence
1 direct clause reference
- Physical requirements
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 55 · reference 4.3
- CHTS 4.3Exact evidence
1 direct clause reference
- Physical Requirements
CHFEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 55 · reference 4.3
- SMETS 5.4Exact evidence
1 direct clause reference
- Physical Requirements
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 55 · reference 5.4
- SMETS 5.10Exact evidence
1 direct clause reference
- Physical Requirements
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 55 · reference 5.10
- SMETS 5.16Exact evidence
1 direct clause reference
- Physical Requirements
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 55 · reference 5.16
- SMETS 7.3Exact evidence
1 direct clause reference
- Physical Requirements
PPMIDEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 55 · reference 7.3
- SMETS 9.3Exact evidence
1 direct clause reference
- Physical Requirements
SAPCEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 55 · reference 9.3
Device Specific Details
- GSME
- Supplier
- ESME
- Supplier and Network Operator
- CHF
- WAN Provider
- PPMID
- Access Control Broker
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 →