Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
5.7.1.3 — Model Type
1 technical record hasbeen identified at this reference: 1 Section 20 item and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.
ESMESRV touchpoint
Documented touchpoints
Typed relationships supported by source mapping rows.
Linked SRVs
Unique retained services reached through exact control rows.
Linked alerts
Explicit requirement-to-alert references.
SMETS5.7.1.3 · item ModelType(SmartMeter).value
ModelType(SmartMeter) - value
The value shall be fixed at manufacture to be the 8 octet concatenation (value of Image Type) || (value of OTA Hardware Version), which equates to the corresponding DUIS Read Inventory DeviceModel data item.. The (value of Image Type) shall be a 4 octet utf-8 encoded, hexadecimal representation of the 16 bit unsigned integer used by Devices in the value of the Image Type parameter in relation to the OTA cluster. The (value of OTA Hardware Version) shall be a 4 octet utf-8 encoded, hexadecimal representation of the 16 bit unsigned integer used by Devices in the value of the Hardware Version parameter in relation to the OTA cluster.
- Object
ModelType(SmartMeter)- Attribute / method
value- Interface disposition
- E
- Category
- Constant data
- Section 20 meaning
- The value shall be fixed at manufacture to be the 8 octet concatenation (value of Image Type) || (value of OTA Hardware Version), which equates to the corresponding DUIS Read Inventory DeviceModel data item.. The (value of Image Type) shall be a 4 octet utf-8 encoded, hexadecimal representation of the 16 bit unsigned integer used by Devices in the value of the Image Type parameter in relation to the OTA cluster. The (value of OTA Hardware Version) shall be a 4 octet utf-8 encoded, hexadecimal representation of the 16 bit unsigned integer used by Devices in the value of the Hardware Version parameter in relation to the OTA cluster.
Documented touchpoints
- ReadsECS26m
0x00F9ESMESRV 6.2.4
How to read this page
Evidence is kept at record level
A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.