General, shared-data and service-specific DUIS tables describe 193 of these 194 codes, including SMETS1 variations. Expand table details and use the DUIS pills to choose the wording and source tables for a version set. Different service conditions have separate views. Select one or more DUIS versions to see their entries, or leave the filter clear to compare all releases. The version filter includes codes found in either the XSD or the parsed tables; their schema versions are shown separately.
Showing 194 of 194 response codes
No response codes match these filters. Try another code or DUIS version.
Device SMI Status incompatible with Service Reference
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Error Handling Strategy procedure
W6 Z1
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User Role is RSA and the CHF Device Status is not Pending
Sources
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.120.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits the Service Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
§ 3.8.121.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits this Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
.DUIS 5.3
Service-specific validation
Documented in DUIS 3.1
The User Role is RSA and the CHF Device Status is not Pending
Sources
DUIS 3.1
§ 3.8.115.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits the Service Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
§ 3.8.116.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits this Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
Failed Authorisation – Invalid Device Status
Documented in DUIS 1.1, 2.0
Device SMI Status incompatible with Service Reference
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Error Handling Strategy procedure
W6 Z1
Source
DUIS 1.1, 2.0
§ 3.5.10 · Table 30 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E11
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Source references.
Failed Validation – Invalid Service Request / device type combination
DCC Systems fails a sequenced Request, because its “Request ID” is the same as its “Preceding Request ID” or the “Preceding RequestID” of its preceding request or of one of its preceding requests, e.g. request id 1 has request 2 as its preceding request and request 2 has request 1 as its preceding request
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
Y1 Z1
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Sequenced Command – Circular Reference
Documented in DUIS 1.1, 2.0
DCC Systems fails a sequenced Request, because its “Request ID” is the same as its “Preceding Request ID” or the “Preceding RequestID” of its preceding request or of one of its preceding requests, e.g. request id 1 has request 2 as its preceding request and request 2 has request 1 as its preceding request
The GB Companion Specification Message Code in the Signed Pre-Command GBCS Payload doesn’t map to the Service Reference Variant in the Signed Pre-Command XML header
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
W5 Z1
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – Signed Pre-Command Message Code and Service Reference Variant mismatch
Documented in DUIS 1.1, 2.0
The GB Companion Specification Message Code in the Signed Pre-Command GBCS Payload doesn’t map to the Service Reference Variant in the Signed Pre-Command XML header
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
W5 Z1
Source
DUIS 1.1, 2.0
§ 3.5.10 · Table 30 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E52
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Source references.
Failed Validation – Unable to cancel Future Dated (DSP) Service Request
The requested Service Request is no longer supported by the DCC Systems. This error shall only occur if a Service Request which exists in an older version of the DUIS XML schema can no longer be accepted by the DCC Systems on that version of the DCC User Interface Please note this Response Code is not applicable to this version of DUIS
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Error Handling Strategy procedure
W9 Z1
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – Service Request no longer supported
Documented in DUIS 2.0
The requested Service Request is no longer supported by the DCC Systems. This error shall only occur if a Service Request which exists in an older version of the DUIS XML schema can no longer be accepted by the DCC Systems on that version of the DCC User Interface Please note this Response Code is not applicable to this version of DUIS
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Error Handling Strategy procedure
W9 Z1
Source
DUIS 2.0
§ 3.5.10 · Table 30 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E57
Included in DUIS XSD versions
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Description.
Failed Validation – Invalid Service Request / GBCS version combination
The Service Request is not compatible with the specified target Device’s Device Model according to the Device Model recorded in the Smart Metering Inventory for that Device and the version of GBCS that pertains to the entry for that Device Model in the Central Products List
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Error Handling Strategy procedure
W10 Z1
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – Invalid Service Request / GBCS version combination
Documented in DUIS 2.0
The Service Request is not compatible with the specified target Device’s Device Model according to the Device Model recorded in the Smart Metering Inventory for that Device and the version of GBCS that pertains to the entry for that Device Model in the Certified Products List
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Error Handling Strategy procedure
W10 Z1
Source
DUIS 2.0
§ 3.5.10 · Table 30 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E58
Included in DUIS XSD versions
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Source references.
Communications Failure – Command not delivered to ESME
The Communications Hub Function was unable to deliver the Command to the ESME The creation of this DCC Alert is in direct response to the receipt by the DCC Systems of an Alert 0x8F84 - Failure to Deliver Remote Party Message to ESME (as defined by GBCS) from the Communications Hub Function
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
X4 Z1
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Communications Failure – Command not delivered to ESME
Documented in DUIS 2.0
The Communications Hub Function was unable to deliver the Command to the ESME The creation of this DCC Alert is in direct response to the receipt by the DCC Systems of an Alert 0x8F84 - Failure to Deliver Remote Party Message to ESME (as defined by GBCS) from the Communications Hub Function
The CHF sends one of the following Alerts to the DCC Access Control Broker to indicate a communications event in the Sub GHz frequency range: Alerts without specific payload: 0x8F22 - Critical Duty Cycle Action Taken 0x8F24 - Regulated Duty Cycle Action Taken 0x8F29 - Three Lost GSME Searches Failed 0x8F2B - Sub GHz Channel not changed due to Frequency Agility Parameters Alerts with specific payload: 0x8F20 - Limited Duty Cycle Action Taken 0x8F2C - Message Discarded Due to Duty Cycle Management 0x8F2D - No More Sub GHz Device Capacity The DCC Alert includes the Alert Code and, for those that contain specific payload, it also includes the corresponding information
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
X5 Z1
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Dual Band CHF Sub GHz event
Documented in DUIS 2.0
The CHF sends one of the following Alerts to the DCC Access Control Broker to indicate a communications event in the Sub GHz frequency range: Alerts without specific payload: 0x8F22 - Critical Duty Cycle Action Taken 0x8F24 - Regulated Duty Cycle Action Taken 0x8F29 - Three Lost GSME Searches Failed 0x8F2B - Sub GHz Channel not changed due to Frequency Agility Parameters Alerts with specific payload: 0x8F20 - Limited Duty Cycle Action Taken 0x8F2C - Message Discarded Due to Duty Cycle Management 0x8F2D - No More Sub GHz Device Capacity The DCC Alert includes the Alert Code and, for those that contain specific payload, it also includes the corresponding information
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
X5 Z1
Source
DUIS 2.0
§ 3.5.10 · Table 30 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E60
Included in DUIS XSD versions
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
Failed Validation – Invalid Service Request for SMETS1 Devices
Documented in DUIS 5.3, 5.4, 5.5
The target device is a SMETS1 Device, but the Service Request is not a SMETS1 Service Request
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
W11
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – Invalid Service Request for SMETS1 Devices
Documented in DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
The target device is a SMETS1 Device, but the Service Request is not a SMETS1 Service Request
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
TBC
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E61
Included in DUIS XSD versions
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
Failed Validation – Invalid Command Variant for SMETS1 Service Request
Documented in DUIS 5.3, 5.4, 5.5
The Command Variant is not valid for the SMETS1 Service Request
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
W11
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – Invalid Command Variant for SMETS1 Service Request
Documented in DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
The Command Variant is not valid for the SMETS1 Service Request
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
TBC
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E62
Included in DUIS XSD versions
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
SMETS1 Service Provider error or information
Documented in DUIS 5.3, 5.4, 5.5
Error condition or notification from a SMETS1 Service Provider, for example a Service Request failed validation within a SMETS1 Service Provider. Additional information shall be provided in the S1SPAlertCode within the DCC Alert payload
Type
Error or information
Applicable response types
DCC Alerts
Error Handling Strategy procedure
W12
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
SMETS1 Service Provider error or information
Documented in DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
Error condition or notification from a SMETS1 Service Provider, for example a Service Request failed validation within a SMETS1 Service Provider. Additional information shall be provided in the S1SPAlertCode within the DCC Alert payload
Type
Error or information
Applicable response types
DCC Alerts
Error Handling Strategy procedure
TBC
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E63
Included in DUIS XSD versions
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
DCC Data Systems anti-Replay Intercept
Documented in DUIS 5.3, 5.4, 5.5
Protection against Replay mechanisms within the DCC have rejected a SMETS1 Service Request.
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
W13 Z1
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
DCC Data Systems anti-Replay Intercept
Documented in DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
Protection against Replay mechanisms within the DCC have rejected a SMETS1 Service Request.
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
TBC
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E64
Included in DUIS XSD versions
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Failed Validation – Originator ID is not the Notified Critical Supplier or Notified Critical Network Operator ID
Documented in DUIS 5.3, 5.4, 5.5
Where the Service Request is a SMETS1 Critical Service Request or a ‘Top Up Device’ SMETS1 Service Request, the Request was not originated by the Notified Critical Supplier or Notified Critical Network Operator.
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
W13 Z1
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E65
Included in DUIS XSD versions
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
Failed Validation – Certificate Role Mismatch
Documented in DUIS 5.3, 5.4, 5.5
The Service Request or Signed Pre-Command is not signed using an Organisation Certificate with Remote Party Role ‘xmlSign’
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
U1 Z1
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – Certificate Role Mismatch
Documented in DUIS 5.1, 5.2
The Service Request or Signed Pre-Command is not signed using an Organisation Certificate with Remote Party Role ‘xmlSign’
Type
Error
Applicable response types
Acknowledgement
Error Handling Strategy procedure
TBC
Source
DUIS 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E66
Included in DUIS XSD versions
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
Failed Delivery –Unable to deliver to CoS Party
Documented in DUIS 5.3, 5.4, 5.5
DCC Data Systems cannot establish communications with the CoS Party
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
X6 Z1
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Delivery –Unable to deliver to CoS Party
Documented in DUIS 5.1, 5.2
DCC Data Systems cannot establish communications with the CoS Party
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
TBC
Source
DUIS 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E67
Included in DUIS XSD versions
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
Timeout – No response received from CoS Party
Documented in DUIS 5.3, 5.4, 5.5
No response received from the CoS Party within the timeout period.
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
X6 Z1
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Timeout – No response received from CoS Party
Documented in DUIS 5.1, 5.2
No response received from the CoS Party within the timeout period.
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
TBC
Source
DUIS 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E68
Included in DUIS XSD versions
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
Failed Validation – Service Request failed CoS Party Validation
Documented in DUIS 5.3, 5.4, 5.5
The Service Request failed validation checks performed by the CoS Party
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
W14 Z1
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – Service Request failed CoS Party Validation
Documented in DUIS 5.1, 5.2
The Service Request failed validation checks performed by the CoS Party
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
TBC
Source
DUIS 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E69
Included in DUIS XSD versions
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
Failed Validation – CoS Service Request failed anti-replay checks
Documented in DUIS 5.3, 5.4, 5.5
Protection against Replay mechanisms within the DCC have rejected the Service Request.
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
W15 Z1
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – CoS Service Request failed anti-replay checks
Documented in DUIS 5.1, 5.2
Protection against Replay mechanisms within the DCC have rejected the Service Request.
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
TBC
Source
DUIS 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E70
Included in DUIS XSD versions
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
Failed Validation – CoS Anomaly Detection Threshold Breach
Documented in DUIS 5.3, 5.4, 5.5
A CoS-specific Anomaly Detection volume threshold has been exceeded
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
W16 Z1
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – CoS Anomaly Detection Threshold Breach
Documented in DUIS 5.1, 5.2
A CoS-specific Anomaly Detection volume threshold has been exceeded
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
TBC
Source
DUIS 5.1, 5.2
§ 3.5.10 · Table 36 : DCC Systems Response Codes
No entry in the parsed DUIS tables.
E71
Included in DUIS XSD versions
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Error Handling Strategy procedure.
Failed Validation – Invalid Response from CoS Party
Documented in DUIS 5.3, 5.4, 5.5
Authorisation payload or Signed Pre-Command from the CoS Party is not consistent with the original Service Request
Type
Error
Applicable response types
DCC Alerts
Error Handling Strategy procedure
W17 Z1
Source
DUIS 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Failed Validation – Invalid Response from CoS Party
Documented in DUIS 5.1, 5.2
Authorisation payload or Signed Pre-Command from the CoS Party is not consistent with the original Service Request
Future Dated Service Request Execution Date-Time is not valid
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Execution Date Time in a Future Dated Request valid?
Check that the Execution Date Time is a date-time in the Future and either no later than the current date plus 30 days or the date is ‘3000-12-31T00:00:00Z’ to specify cancellation of the Request
Sources
DUIS 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.10.3 · Table 325 : Response codes
§ 3.10.2 · Table 324 : Validation checks
Failed Validation – Invalid Date-Time for Future Dated Request
Documented in DUIS 3.0
Future Dated Service Request Execution Date-Time is not valid
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Execution Date Time in a Future Dated Request valid?
Check that the Execution Date Time is a date-time in the Future and either no later than the current date plus 30 days or the date is ‘3000-12-31T00:00:00Z’ to specify cancellation of the Request
Sources
DUIS 3.0
§ 3.10.3 · Table 326 : Response codes
§ 3.10.2 · Table 325 : Validation checks
Failed Validation – Invalid Date-Time for Future Dated Request
Documented in DUIS 2.0
Future Dated Service Request Execution Date-Time is not valid
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Execution Date Time in a Future Dated Request valid?
Check that the Execution Date Time is a date-time in the Future and either no later than the current date plus 30 days or the date is ‘3000-12-31T00:00:00Z’ to specify cancellation of the Request
Sources
DUIS 2.0
§ 3.10.3 · Table 317 : Response codes
§ 3.10.2 · Table 316 : Validation checks
Failed Validation – Invalid Date-Time for Future Dated Request
Documented in DUIS 1.1
Future Dated Service Request Execution Date-Time is not valid
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Execution Date Time in a Future Dated Request valid?
Check that the Execution Date Time is a date-time in the Future and either no later than the current date plus 30 days or the date is ‘3000-12-31T00:00:00Z’ to specify cancellation of the Request
Sources
DUIS 1.1
§ 3.10.3 · Table 297 : Response codes
§ 3.10.2 · Table 296 : Validation checks
No entry in the parsed DUIS tables.
E1001
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Source references.
Failed Validation – Log Period Start Date Time later than required execution date-time
The Log Period (sr:ReadLogPeriod) Start Date Time is later than the current date-time for “On Demand” or the Execution Date Time for “Future Dated” requests
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Read Log Period Start Date Time not later than the required execution date-time?
Check that the Read Log Period (sr:ReadLogPeriod) Start Date Time is not later than the current date-time for “On Demand” and the Execution Date Time for “Future Dated” requests
Sources
DUIS 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.10.3 · Table 325 : Response codes
§ 3.10.2 · Table 324 : Validation checks
Failed Validation – Log Period Start Date Time later than required execution date-time
Documented in DUIS 3.0
The Log Period (sr:ReadLogPeriod) Start Date Time is later than the current date-time for “On Demand” or the Execution Date Time for “Future Dated” requests
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Read Log Period Start Date Time not later than the required execution date-time?
Check that the Read Log Period (sr:ReadLogPeriod) Start Date Time is not later than the current date-time for “On Demand” and the Execution Date Time for “Future Dated” requests
Sources
DUIS 3.0
§ 3.10.3 · Table 326 : Response codes
§ 3.10.2 · Table 325 : Validation checks
Failed Validation – Log Period Start Date Time later than required execution date-time
Documented in DUIS 2.0
The Log Period (sr:ReadLogPeriod) Start Date Time is later than the current date-time for “On Demand” or the Execution Date Time for “Future Dated” requests
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Read Log Period Start Date Time not later than the required execution date-time?
Check that the Read Log Period (sr:ReadLogPeriod) Start Date Time is not later than the current date-time for “On Demand” and the Execution Date Time for “Future Dated” requests
Sources
DUIS 2.0
§ 3.10.3 · Table 317 : Response codes
§ 3.10.2 · Table 316 : Validation checks
Failed Validation – Log Period Start Date Time later than required execution date-time
Documented in DUIS 1.1
The Log Period (sr:ReadLogPeriod) Start Date Time is later than the current date-time for “On Demand” or the Execution Date Time for “Future Dated” requests
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Read Log Period Start Date Time not later than the required execution date-time?
Check that the Read Log Period (sr:ReadLogPeriod) Start Date Time is not later than the current date-time for “On Demand” and the Execution Date Time for “Future Dated” requests
Sources
DUIS 1.1
§ 3.10.3 · Table 297 : Response codes
§ 3.10.2 · Table 296 : Validation checks
No entry in the parsed DUIS tables.
E1003
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Source references.
Failed Validation – Log Period End Date Time earlier than Start Date Time
For those Service Requests that include sensitive data in the Response: Service Requests from Device URPs (e.g. ‘old’ Responsible Supplier and ‘Other User’) do not include the User’s Key Agreement Public Security Credentials or are included in other cases
Type
Error
Applicable response types
Acknowledgement
Validation checks
Are the Public Security Credentials included?
For those Service Requests that return Sensitive data and are available to Device Unknown Remote Parties (e.g. ‘Old’ Responsible Supplier and ‘Other User’) the Key Agreement Public Security Credentials are included in the Service Requests. For all Service Requests not subject to the Key Agreement Public Security Credentials are not included in the Service Requests.
Sources
DUIS 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.10.3 · Table 325 : Response codes
§ 3.10.2 · Table 324 : Validation checks
Failed Validation –Security Credentials Mismatch
Documented in DUIS 3.0
For those Service Requests that include sensitive data in the Response: Service Requests from Device URPs (e.g. ‘old’ Responsible Supplier and ‘Other User’) do not include the User’s Key Agreement Public Security Credentials or are included in other cases
Type
Error
Applicable response types
Acknowledgement
Validation checks
Are the Public Security Credentials included?
For those Service Requests that return Sensitive data and are available to Device Unknown Remote Parties (e.g. ‘Old’ Responsible Supplier and ‘Other User’) the Key Agreement Public Security Credentials are included in the Service Requests. For all Service Requests not subject to the Key Agreement Public Security Credentials are not included in the Service Requests.
Sources
DUIS 3.0
§ 3.10.3 · Table 326 : Response codes
§ 3.10.2 · Table 325 : Validation checks
Failed Validation –Security Credentials Mismatch
Documented in DUIS 2.0
For those Service Requests that include sensitive data in the Response: Service Requests from Device URPs (e.g. ‘old’ Responsible Supplier and ‘Other User’) do not include the User’s Key Agreement Public Security Credentials or are included in other cases
Type
Error
Applicable response types
Acknowledgement
Validation checks
Are the Public Security Credentials included?
For those Service Requests that return Sensitive data and are available to Device Unknown Remote Parties (e.g. ‘Old’ Responsible Supplier and ‘Other User’) the Key Agreement Public Security Credentials are included in the Service Requests. For all Service Requests not subject to the Key Agreement Public Security Credentials are not included in the Service Requests.
Sources
DUIS 2.0
§ 3.10.3 · Table 317 : Response codes
§ 3.10.2 · Table 316 : Validation checks
Failed Validation –Security Credentials Mismatch
Documented in DUIS 1.1
For those Service Requests that include sensitive data in the Response: Service Requests from Device URPs (e.g. ‘old’ Responsible Supplier and ‘Other User’) do not include the User’s Key Agreement Public Security Credentials or are included in other cases
Type
Error
Applicable response types
Acknowledgement
Validation checks
Are the Public Security Credentials included?
For those Service Requests that return Sensitive data and are available to Device Unknown Remote Parties (e.g. ‘Old’ Registered Supplier and ‘Other User’) the Key Agreement Public Security Credentials are included in the Service Requests. For all Service Requests not subject to the Key Agreement Public Security Credentials are not included in the Service Requests.
Sources
DUIS 1.1
§ 3.10.3 · Table 297 : Response codes
§ 3.10.2 · Table 296 : Validation checks
No entry in the parsed DUIS tables.
E1007
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (5 table views)
Differences between views: Validation process, Source references.
Failed Validation – Invalid Security Credentials
Documented in DUIS 5.1, 5.2, 5.3, 5.4, 5.5
For those Requests that include Public Security Credentials in the payload: At least one of the certificates used in the chain of trust has expired or been revoked or has an incorrect format
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Validation checks
Are the Public Security Credentials valid?
For those Requests that include Public Security Credentials in the Request body: Check that the certificates used in the chain of trust have NOT expired (i.e. their expiry date is post the date of check or, for Future Dated Requests, post the Execution Date) and that the certificates used in the chain of trust have NOT been revoked (i.e. they are not included in the Certificate Revocation List) Check that the Issuer certificate referenced in each Certificate in Replacement Certificates is included in the Certification Path Certificates set, and that each certificate in the Certification Path Certificates set is the Issuer for at least one certificate in the Replacement Certificates Check that the Certificate was validly issued under SMKI.
Sources
DUIS 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.10.3 · Table 325 : Response codes
§ 3.10.2 · Table 324 : Validation checks
Failed Validation – Invalid Security Credentials
Documented in DUIS 3.1, 4.0, 5.0
For those Requests that include Public Security Credentials in the payload: At least one of the certificates used in the chain of trust has expired or been revoked or has an incorrect format
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Validation checks
Are the Public Security Credentials valid?
For those Requests that include Public Security Credentials in the Request body: Check that the certificates used in the chain of trust have NOT expired (i.e. their expiry date is post the date of check or, for Future Dated Requests, post the Execution Date) and that the certificates used in the chain of trust have NOT been revoked (i.e. they are not included in the Certificate Revocation List) Check that the Certificate was validly issued under SMKI.
Sources
DUIS 3.1, 4.0, 5.0
§ 3.10.3 · Table 325 : Response codes
§ 3.10.2 · Table 324 : Validation checks
Failed Validation – Invalid Security Credentials
Documented in DUIS 3.0
For those Requests that include Public Security Credentials in the payload: At least one of the certificates used in the chain of trust has expired or been revoked or has an incorrect format
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Validation checks
Are the Public Security Credentials valid?
For those Requests that include Public Security Credentials in the Request body: Check that the certificates used in the chain of trust have NOT expired (i.e. their expiry date is post the date of check or, for Future Dated Requests, post the Execution Date) and that the certificates used in the chain of trust have NOT been revoked (i.e. they are not included in the Certificate Revocation List) Check that the Certificate was validly issued under SMKI.
Sources
DUIS 3.0
§ 3.10.3 · Table 326 : Response codes
§ 3.10.2 · Table 325 : Validation checks
Failed Validation – Invalid Security Credentials
Documented in DUIS 2.0
For those Requests that include Public Security Credentials in the payload: At least one of the certificates used in the chain of trust has expired or been revoked or has an incorrect format
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Validation checks
Are the Public Security Credentials valid?
For those Requests that include Public Security Credentials in the Request body: Check that the certificates used in the chain of trust have NOT expired (i.e. their expiry date is post the date of check or, for Future Dated Requests, post the Execution Date) and that the certificates used in the chain of trust have NOT been revoked (i.e. they are not included in the Certificate Revocation List) Check that the Certificate was validly issued under SMKI.
Sources
DUIS 2.0
§ 3.10.3 · Table 317 : Response codes
§ 3.10.2 · Table 316 : Validation checks
Failed Validation – Invalid Security Credentials
Documented in DUIS 1.1
For those Requests that include Public Security Credentials in the payload: At least one of the certificates used in the chain of trust has expired or been revoked or has an incorrect format
Type
Error
Applicable response types
Acknowledgement and DCC Alerts
Validation checks
Are the Public Security Credentials valid?
For those Requests that include Public Security Credentials in the Request body: Check that the certificates used in the chain of trust have NOT expired (i.e. their expiry date is post the date of check or, for Future Dated Requests, post the Execution Date) and that the certificates used in the chain of trust have NOT been revoked (i.e. they are not included in the Certificate Revocation List) Check that the Certificate was validly issued under SMKI.
The Device ID included in the Request body doesn’t exist in the Smart Metering Inventory
Type
Error
Applicable response types
Acknowledgement
Validation checks
Does the Device included in the Request exist?
For those Requests that include a Device ID in the body, check that the Device ID exists in the Smart Metering Inventory This is not applicable to Service Reference 12.2 (Device Pre-notification) which is used to add Devices to the Smart Metering Inventory
Sources
DUIS 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.10.3 · Table 325 : Response codes
§ 3.10.2 · Table 324 : Validation checks
Failed Validation – Invalid Device ID
Documented in DUIS 3.0
The Device ID included in the Request body doesn’t exist in the Smart Metering Inventory
Type
Error
Applicable response types
Acknowledgement
Validation checks
Does the Device included in the Request exist?
For those Requests that include a Device ID in the body, check that the Device ID exists in the Smart Metering Inventory This is not applicable to Service Reference 12.2 (Device Pre-notification) which is used to add Devices to the Smart Metering Inventory
Sources
DUIS 3.0
§ 3.10.3 · Table 326 : Response codes
§ 3.10.2 · Table 325 : Validation checks
Failed Validation – Invalid Device ID
Documented in DUIS 2.0
The Device ID included in the Request body doesn’t exist in the Smart Metering Inventory
Type
Error
Applicable response types
Acknowledgement
Validation checks
Does the Device included in the Request exist?
For those Requests that include a Device ID in the body, check that the Device ID exists in the Smart Metering Inventory This is not applicable to Service Reference 12.2 (Device Pre-notification) which is used to add Devices to the Smart Metering Inventory
Sources
DUIS 2.0
§ 3.10.3 · Table 317 : Response codes
§ 3.10.2 · Table 316 : Validation checks
Failed Validation – Invalid Device ID
Documented in DUIS 1.1
The Device ID included in the Request body doesn’t exist in the Smart Metering Inventory
Type
Error
Applicable response types
Acknowledgement
Validation checks
Does the Device included in the Request exist?
For those Requests that include a Device ID in the body, check that the Device ID exists in the Smart Metering Inventory This is not applicable to Service Reference 12.2 (Device Pre-notification) which is used to add Devices to the Smart Metering Inventory
Is the Service Request valid for the Target Device?
For On Demand or Future Dated Service Requests: Check that if the BusinessTargetID Device is a Gas Smart Meter that the User Role is GIS, and that User is the Responsible Supplier for that Device. For Create Schedule (for DCC Scheduled Service Requests): Check that if the DeviceID Device is a Gas Smart Meter that the User Role is GIS, and that User is the Responsible Supplier for that Device.
Sources
DUIS 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.10.3 · Table 325 : Response codes
§ 3.10.2 · Table 324 : Validation checks
Failed Validation – Invalid Device Type
Documented in DUIS 3.0
The Device Type is invalid
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Service Request valid for the Target Device?
For On Demand or Future Dated Service Requests: Check that if the BusinessTargetID Device is a Gas Smart Meter that the User Role is GIS, and that User is the Responsible Supplier for that Device. For Create Schedule (for DCC Scheduled Service Requests): Check that if the DeviceID Device is a Gas Smart Meter that the User Role is GIS, and that User is the Responsible Supplier for that Device.
Sources
DUIS 3.0
§ 3.10.3 · Table 326 : Response codes
§ 3.10.2 · Table 325 : Validation checks
Failed Validation – Invalid Device Type
Documented in DUIS 2.0
The Device Type is invalid
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Service Request valid for the Target Device?
For On Demand or Future Dated Service Requests: Check that if the BusinessTargetID Device is a Gas Smart Meter that the User Role is GIS, and that User is the Responsible Supplier for that Device. For Create Schedule (for DCC Scheduled Service Requests): Check that if the DeviceID Device is a Gas Smart Meter that the User Role is GIS, and that User is the Responsible Supplier for that Device.
Sources
DUIS 2.0
§ 3.10.3 · Table 317 : Response codes
§ 3.10.2 · Table 316 : Validation checks
Failed Validation – Invalid Device Type
Documented in DUIS 1.1
The Device Type is invalid
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Service Request valid for the Target Device?
For On Demand or Future Dated Service Requests: Check that if the BusinessTargetID Device is a Gas Smart Meter that the User Role is GIS, and that User is the Responsible Supplier for that Device. For Create Schedule (for DCC Scheduled Service Requests): Check that if the DeviceID Device is a Gas Smart Meter that the User Role is GIS, and that User is the Responsible Supplier for that Device.
Sources
DUIS 1.1
§ 3.10.3 · Table 297 : Response codes
§ 3.10.2 · Table 296 : Validation checks
No entry in the parsed DUIS tables.
E1011
Included in DUIS XSD versions
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Failed Validation – Device not a Dual Band Communications Hub
The DCC does not have this Device recorded as a Dual Band Communications Hub
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Service Request Target Device a Dual Band CHF?
Check that the Service Request’s Target Device is a Dual Band Communications Hub (Only applicable to Service Requests 6.28, 6.29, 6.30, 6.31 and 6.32. This check will only fail for CHFs not recorded by the DCC Systems as having a “Single Band (2.4GHz only)” HAN Variant. Please see HAN Variant for the corresponding CHF Device Id returned by Service Request 8.2 (Read Inventory) Response or by the SSI Read Inventory screen)
Sources
DUIS 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.10.3 · Table 325 : Response codes
§ 3.10.2 · Table 324 : Validation checks
Failed Validation – Device not a Dual Band Communications Hub
Documented in DUIS 3.0
The DCC does not have this Device recorded as a Dual Band Communications Hub
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Service Request Target Device a Dual Band CHF?
Check that the Service Request’s Target Device is a Dual Band Communications Hub (Only applicable to Service Requests 6.28, 6.29, 6.30, 6.31 and 6.32. This check will only fail for CHFs not recorded by the DCC Systems as having a “Single Band (2.4GHz only)” HAN Variant. Please see HAN Variant for the corresponding CHF Device Id returned by Service Request 8.2 (Read Inventory) Response or by the SSI Read Inventory screen)
Sources
DUIS 3.0
§ 3.10.3 · Table 326 : Response codes
§ 3.10.2 · Table 325 : Validation checks
Failed Validation – Device not a Dual Band Communications Hub
Documented in DUIS 2.0
The DCC does not have this Device recorded as a Dual Band Communications Hub
Type
Error
Applicable response types
Acknowledgement
Validation checks
Is the Service Request Target Device a Dual Band CHF?
Check that the Service Request’s Target Device is a Dual Band Communications Hub (Only applicable to Service Requests 6.28, 6.29, 6.30, 6.31 and 6.32. This check will only fail for CHFs not recorded by the DCC Systems as having a “Single Band (2.4GHz only)” HAN Variant. Please see HAN Variant for the corresponding CHF Device Id returned by Service Request 8.2 (Read Inventory) Response or by the SSI Read Inventory screen)
§ 3.8.1.3 · Specific Validation for this RequestSRV 1.1.1 · UpdateImportTariff(Primary Element)Section context
See clause 3.2.5 for general validation applied to all Requests and also ExecutionDateTime validation (clause 3.10.2)
§ 3.8.2.3 · Specific Validation for this RequestSRV 1.1.2 · UpdateImportTariff(SecondaryElement)Section context
See clause 3.2.5 for general validation applied to all Requests and also Execution Date Time validation (clause 3.10.2)DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
If the target Device is a SMETS1 ESME according to the Smart Metering Inventory, the XML element named HybridTariff must not be included in the ElecPriceElementsPrimary element within PriceElement (see 3.8.1.2). For clarity, SMETS1 ESME are not required to support such tariffs.
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 1.1.1 · UpdateImportTariff(Primary Element)Section context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
If the target Device is a SMETS1 ESME according to the Smart Metering Inventory, the XML element named HybridTariff must not be included in the ElecPriceElementsPrimary element within PriceElement (see 3.8.1.2). For clarity, SMETS1 ESME are not required to support such tariffs.
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 1.2.1 · UpdatePrice(Primary Element)Section context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
Check that if the ESMEEventLogType is ALCS then the target Device is not a SMETS1 Device according to the Smart Metering Inventory. For clarity, SMETS1 ESMEs are not required to support such logs.
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 3.3 · ClearEventLogSection context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
§ 3.8.18.3 · Specific Validation for this RequestSRV 4.1.2 · ReadInstantaneousImportTOUMatricesSection context
See clause 3.2.5 for general validation applied to all Requests and also Execution Date Time validation (clause 3.10.2)DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Service-specific validation
Documented in DUIS 5.3, 5.4, 5.5
The Gas Transporter can only read Instantaneous Import Registers from the GPF and not the Gas Smart Meter A Meter Data Retriever cannot read Instantaneous Import Registers from a SMETS2+ Device
Source
DUIS 5.3, 5.4, 5.5
§ 3.8.17.3 · Specific Validation for this RequestSRV 4.1.1 · ReadInstantaneousImportRegistersSection context
See clause 3.2.5 for general validation applied to all Requests and also Execution Date Time validation (clause 3.10.2)
The Gas Transporter can only read Instantaneous Import Registers from the GPF and not the Gas Smart Meter
Source
DUIS 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
§ 3.8.17.3 · Specific Validation for this RequestSRV 4.1.1 · ReadInstantaneousImportRegistersSection context
See clause 3.2.5 for general validation applied to all Requests and also Execution Date Time validation (clause 3.10.2)DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateScheduleSection context
See clause 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
See clauses 3.2.4 and 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 5.3, 5.4, 5.5
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateScheduleSection context
See clause 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
See clauses 3.2.4 and 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 5.3, 5.4, 5.5
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateScheduleSection context
See clause 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
See clauses 3.2.4 and 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 5.3, 5.4, 5.5
The Service Request format does not match the Service Reference Variant in the DCC Schedule. The combination of DSPScheduledServiceReference and DSPScheduledServiceReferenceVariant is not valid
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateScheduleSection context
See clause 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
See clauses 3.2.4 and 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 5.3, 5.4, 5.5
One of: • User’s Role is Unknown Remote Party to the Device and the DCC Scheduled Service Response contains Sensitive data and Request does not include the User’s Key Agreement Public Security Credentials Or • User’s Role is Known Remote Party to the Device and / or the DCC Scheduled Service Response doesn’t contain Sensitive data and Request includes the User’s Key Agreement Public Security Credentials
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateScheduleSection context
See clause 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
See clauses 3.2.4 and 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 5.3, 5.4, 5.5
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateScheduleSection context
See clause 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
See clauses 3.2.4 and 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 5.3, 5.4, 5.5
Service-specific validation
Documented in DUIS 1.1
Unable to create Schedule, because the DCC Service User already owns 99 active DSP Schedules for the Device
Source
DUIS 1.1
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateSchedule
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateScheduleSection context
See clause 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2
See clauses 3.2.4 and 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.DUIS 5.3, 5.4, 5.5
Where DeviceID in the Service Request is a SMETS1 Device according to the Smart Metering Inventory, check that the DSPScheduledServiceReferenceVariant is supported for a SMETS1 Device according to clause 3.1.
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 5.1 · CreateScheduleSection context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
No entry in the parsed DUIS tables.
E050111
Included in DUIS XSD versions
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.3, 5.4, 5.5
The DSPScheduledServiceReferenceVariant is not applicable for a MDR user
Source
DUIS 5.3, 5.4, 5.5
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateScheduleSection context
See clauses 3.2.4 and 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.
No entry in the parsed DUIS tables.
E050112
Included in DUIS XSD versions
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.3, 5.4, 5.5
The DSPScheduledServiceReferenceVariant is not applicable to SMETS2 Services
Source
DUIS 5.3, 5.4, 5.5
§ 3.8.43.3 · Specific Validation for this RequestSRV 5.1 · CreateScheduleSection context
See clauses 3.2.4 and 3.2.5 for general validation applied to all Requests (applicable to the Create Schedule and to the Scheduled Service Request) and clause 3.10.2 for Create Schedule Device ID existence validation.
The GBCS version that pertains to the Device Model recorded in the SMI for this Device doesn’t support the requested value format for Uncontrolled Gas Flow Rate .
Source
DUIS 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.59.3 · Specific Validation for this RequestSRV 6.7 · UpdateDeviceConfiguration(GasFlow)Section context
See clause 3.2.5 for general validation applied to all Requests.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Amended condition for SMETS1 Devices
If the target Device is a SMETS1 GSME according to the Smart Metering Inventory, the XML element named UncontrolledGasFlowRateDecimal must not be included in the Service Request.For clarity, only the XML element named UncontrolledGasFlowRate may be used with SMETS1 devices
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 6.7 · UpdateDeviceConfiguration(GasFlow)Section context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
Service-specific validation
Documented in DUIS 3.1
Amended condition for SMETS1 Devices
If the target Device is a SMETS1 GSME according to the Smart Metering Inventory, the XML element named UncontrolledGasFlowRateDecimal must not be included in the Service Request.For clarity, only the XML element named UncontrolledGasFlowRate may be used with SMETS1 devices.
Source
DUIS 3.1
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 6.7 · UpdateDeviceConfiguration(GasFlow)Section context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
The Service Request is not valid for the Device Type where the Billing Calendar is to be configured. • Electricity Smart Meter. The Service Request includes the ElectricityBillingCalendar data item • Gas Smart Meter. The Service Request includes the GasBillingCalendar data item
§ 3.8.60.3 · Specific Validation for this RequestSRV 6.8 · UpdateDeviceConfiguration(BillingCalendar)Section context
See clause 3.2.5 for general validation applied to all Requests.
Service-specific validation
Documented in DUIS 1.1
The Service Request is not valid for the Device Type where the Billing Calendar is to be configured. • Electricity Smart Meter. The Service Request includes the ElectricityBillingCalendar data item • Gas Smart Meter. The Service Request includes the GasBillingCalendar data item
Source
DUIS 1.1
§ 3.8.59.3 · Specific Validation for this RequestSRV 6.8 · UpdateDeviceConfiguration(BillingCalendar)
§ 3.8.63.3 · Specific Validation for this RequestSRV 6.13 · ReadEventOrSecurityLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Read Log Period validation.
Service-specific validation
Documented in DUIS 1.1
Log To Read / Device Type mismatch. The Log to Read is not applicable to the Device Type
Source
DUIS 1.1
§ 3.8.62.3 · Specific Validation for this RequestSRV 6.13 · ReadEventOrSecurityLog
No entry in the parsed DUIS tables.
E061304
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Invalid User Role. The ALCS Event Log is not available to the requesting User Role. The IS User Role is eligible to read this log regardless of the GBCS version that pertains to the Device Model recorded in the SMI for this Device. The ED User Role is eligible to read this log only where the GBCS version that pertains to the Device Model recorded in the SMI for this Device is GBCS v3.2 or later. All other User Roles are not eligible to read this log.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.63.3 · Specific Validation for this RequestSRV 6.13 · ReadEventOrSecurityLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Read Log Period validation.
Service-specific validation
Documented in DUIS 3.1
Invalid User Role. The ALCS Event Log is not available to the requesting User Role. The IS User Role is eligible to read this log regardless of the GBCS version that pertains to the Device Model recorded in the SMI for this Device. The ED User Role is eligible to read this log only where the GBCS version that pertains to the Device Model recorded in the SMI for this Device is GBCS v3.2. All other User Roles are not eligible to read this log.
Source
DUIS 3.1
§ 3.8.63.3 · Specific Validation for this RequestSRV 6.13 · ReadEventOrSecurityLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Read Log Period validation.
Service-specific validation
Documented in DUIS 2.0, 3.0
Invalid User Role. The ALCS Event Log is not available to the requesting User Role. Only the IS User Role is eligible to read this log
Source
DUIS 2.0, 3.0
§ 3.8.63.3 · Specific Validation for this RequestSRV 6.13 · ReadEventOrSecurityLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Read Log Period validation.
Service-specific validation
Documented in DUIS 1.1
Invalid Service User Role. The ALCS Event Log is not available to the requesting Service User Role. Only the Registered IS User Role is eligible to read this log
Source
DUIS 1.1
§ 3.8.62.3 · Specific Validation for this RequestSRV 6.13 · ReadEventOrSecurityLog
Check that if the LogToRead is ALCSEvent or PowerEvent then the target Device is not a SMETS1 Device according to the Smart Metering Inventory. For clarity, SMETS1 ESME are not required to support such logs.
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 6.13 · ReadEventOrSecurityLogSection context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
No entry in the parsed DUIS tables.
E061501
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The combination of User Role,Remote Party Role and Device Type is incorrect
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.67.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The combination of User Role,Remote Party Role and Device Type is incorrect
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.66.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation .DUIS 2.0
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.DUIS 3.0, 3.1
Service-specific validation
Documented in DUIS 1.1
The combination of User Role,Remote Party Role and Device Type is incorrect
Source
DUIS 1.1
§ 3.8.65.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)
No entry in the parsed DUIS tables.
E061504
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Remote Party New Prepayment Top Up Floor Seq Number data item is not applicable to the Request
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.67.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Remote Party New Prepayment Top Up Floor Seq Number data item is not applicable to the Request
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.66.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation .DUIS 2.0
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.DUIS 3.0, 3.1
Service-specific validation
Documented in DUIS 1.1
The Remote Party New Prepayment Top Up Floor Seq Number data item is not applicable to the Request
Source
DUIS 1.1
§ 3.8.65.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)
No entry in the parsed DUIS tables.
E061505
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Certificate Type is not applicable to the Device Type
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.67.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Certificate Type is not applicable to the Device Type
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.66.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation .DUIS 2.0
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.DUIS 3.0, 3.1
Service-specific validation
Documented in DUIS 1.1
The Certificate Type is not applicable to the Device Type
Source
DUIS 1.1
§ 3.8.65.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)
No entry in the parsed DUIS tables.
E061506
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Future Dating / Remote Party Role mismatch - The RemotePartyRole is not Supplier or LoadController
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.67.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
Future Dating / Remote Party Role mismatch - The Remote Party Role is not Supplier
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.66.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation .DUIS 2.0
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.DUIS 3.0, 3.1
Service-specific validation
Documented in DUIS 1.1
Future Dating / Remote Party Role mismatch - The Remote Party Role is not Supplier
Source
DUIS 1.1
§ 3.8.65.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)
No entry in the parsed DUIS tables.
E061507
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Certificate Type is not applicable to the Remote Party Role
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.67.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Certificate Type is not applicable to the Remote Party Role
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.66.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation .DUIS 2.0
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.DUIS 3.0, 3.1
Service-specific validation
Documented in DUIS 1.1
The Certificate Type is not applicable to the Remote Party Role
Source
DUIS 1.1
§ 3.8.65.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)
Check that the role of the User submitting the Service Request and RemotePartyRole align. Specifically if the User’s role is ES or GS, the RemotePartyRole must be Supplier. If the User’s role is GT or ED, the RemotePartyRole must be NetworkOperator.
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
No entry in the parsed DUIS tables.
E061509
Included in DUIS XSD versions
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type is ESME and ‘LoadController’ is specified as the RemotePartyRole in the Service Request, however the firmware version recorded in the SMI for the Device is not at GBCS version 4.0 or later
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.67.3 · Specific Validation for this RequestSRV 6.15.1 · UpdateSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
No entry in the parsed DUIS tables.
E061801
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Invalid Start Time - The Start Time is not valid. Start Time minutes must be either 00 or 30.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.70.3 · Specific Validation for this RequestSRV 6.18.1 · SetMaximumDemandConfigurableTimePeriodSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
Invalid Start Time - The Start Time is not valid. Start Time minutes must be either 00 or 30.
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.69.3 · Specific Validation for this RequestSRV 6.18.1 · SetMaximumDemandConfigurableTimePeriodSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
Service-specific validation
Documented in DUIS 1.1
Invalid Start Time - The Start Time is not valid. Start Time minutes must be either 00 or 30.
Source
DUIS 1.1
§ 3.8.68.3 · Specific Validation for this RequestSRV 6.18.1 · SetMaximumDemandConfigurableTimePeriod
No entry in the parsed DUIS tables.
E061802
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Invalid End Time - The End Time is not valid. End Time minutes must be either 00 or 30.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.70.3 · Specific Validation for this RequestSRV 6.18.1 · SetMaximumDemandConfigurableTimePeriodSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
Invalid End Time - The End Time is not valid. End Time minutes must be either 00 or 30.
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.69.3 · Specific Validation for this RequestSRV 6.18.1 · SetMaximumDemandConfigurableTimePeriodSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
Service-specific validation
Documented in DUIS 1.1
Invalid End Time - The End Time is not valid. End Time minutes must be either 00 or 30.
Source
DUIS 1.1
§ 3.8.68.3 · Specific Validation for this RequestSRV 6.18.1 · SetMaximumDemandConfigurableTimePeriod
No entry in the parsed DUIS tables.
E061803
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Invalid Request - The Request doesn’t include any Maximum Demand Register to reset
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.71.3 · Specific Validation for this RequestSRV 6.18.2 · ResetMaximumDemandRegistersSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
Invalid Request - The Request doesn’t include any Maximum Demand Register to reset
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.70.3 · Specific Validation for this RequestSRV 6.18.2 · ResetMaximumDemandRegistersSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
Service-specific validation
Documented in DUIS 1.1
Invalid Request - The Request doesn’t include any Maximum Demand Register to reset
Source
DUIS 1.1
§ 3.8.69.3 · Specific Validation for this RequestSRV 6.18.2 · ResetMaximumDemandRegisters
No entry in the parsed DUIS tables.
E062101
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Remote Party New Prepayment Top Up Floor Seq Number data item is not applicable to the Request
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Remote Party New Prepayment Top Up Floor Seq Number data item is not applicable to the Request
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.73.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 1.1
The Remote Party New Prepayment Top Up Floor Seq Number data item is not applicable to the Request
Source
DUIS 1.1
§ 3.8.72.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDevice
No entry in the parsed DUIS tables.
E062102
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Certificate type is not applicable to the Device Type
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Certificate type is not applicable to the Device Type
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.73.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 1.1
The Certificate type is not applicable to the Device Type
Source
DUIS 1.1
§ 3.8.72.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDevice
No entry in the parsed DUIS tables.
E062103
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The combination of User Role and Remote Party Role is invalid for the Device Type
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The combination of User Role and Remote Party Role is invalid for the Device Type
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.73.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 1.1
The combination of DCC Service User Role and Remote Party Role is invalid for the Device Type
Source
DUIS 1.1
§ 3.8.72.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDevice
No entry in the parsed DUIS tables.
E062105
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Certificate Type is not applicable to the Device Type & Remote Party Role combination or not all applicable Certificate Types are included in the Request.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Certificate Type is not applicable to the Device Type & Remote Party Role combination or not all applicable Certificate Types are included in the Request.
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.73.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 1.1
The Certificate Type is not applicable to the Device Type & Remote Party Role combination or not all applicable Certificate Types are included in the Request.
Source
DUIS 1.1
§ 3.8.72.3 · Specific Validation for this RequestSRV 6.21 · RequestHandoverOfDCCControlledDevice
No entry in the parsed DUIS tables.
E062201
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Service Request is invalid. The combination of User Role and Alert Code Configuration contents is incorrect OR at least one Alert configuration is not present.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.75.3 · Specific Validation for this RequestSRV 6.22 · ConfigureAlertBehaviourSection context
See clause 3.2.5 for general validation applied to all Requests.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Service Request is invalid. The combination of User Role and Alert Code Configuration contents is incorrect OR at least one Alert configuration is not present.
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.22 · ConfigureAlertBehaviourSection context
See clause 3.2.5 for general validation applied to all Requests.
Service-specific validation
Documented in DUIS 1.1
The Service Request is invalid. The combination of User Role and Alert Code Configuration contents is incorrect OR at least one Alert configuration is not present.
Source
DUIS 1.1
§ 3.8.73.3 · Specific Validation for this RequestSRV 6.22 · ConfigureAlertBehaviour
No entry in the parsed DUIS tables.
E062202
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The combination of Electricity Smart Meter Variant and Service Request contents is invalid
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.75.3 · Specific Validation for this RequestSRV 6.22 · ConfigureAlertBehaviourSection context
See clause 3.2.5 for general validation applied to all Requests.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The combination of Electricity Smart Meter Variant and Service Request contents is invalid
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.22 · ConfigureAlertBehaviourSection context
See clause 3.2.5 for general validation applied to all Requests.
Service-specific validation
Documented in DUIS 1.1
The combination of Electricity Smart Meter Variant and Service Request contents is invalid
Source
DUIS 1.1
§ 3.8.73.3 · Specific Validation for this RequestSRV 6.22 · ConfigureAlertBehaviour
No entry in the parsed DUIS tables.
E062203
Included in DUIS XSD versions
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The GBCS version that pertains to the Device Model recorded in the SMI for this Device, does not support the chosen features of this Service Request
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.75.3 · Specific Validation for this RequestSRV 6.22 · ConfigureAlertBehaviourSection context
See clause 3.2.5 for general validation applied to all Requests.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The GBCS version that pertains to the Device Model recorded in the SMI for this Device, does not support the chosen features of this Service Request
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.22 · ConfigureAlertBehaviourSection context
See clause 3.2.5 for general validation applied to all Requests.
No entry in the parsed DUIS tables.
E062301
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Invalid MPxN - The MPxN included in the Request does not match the Primary Import MPxN associated to the Device in the Smart Metering Inventory
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
Invalid MPxN - The MPxN included in the Request does not match the Primary Import MPxN associated to the Device in the Smart Metering Inventory
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.75.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 1.1
Invalid MPxN - The MPxN included in the Request does not match the Primary Import MPxN associated to the Device in the Smart Metering Inventory
Source
DUIS 1.1
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E062302
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 5.1, 5.2, 5.3, 5.4, 5.5
Invalid Supplier Prepayment Top Up Floor Seq Number - The Supplier Prepayment Top Up Floor Seq Number data item is not applicable to the Device Type or has not been included where it is applicable to the Device Type
Source
DUIS 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 4.0, 5.0
Invalid Supplier Prepayment Top Up Floor Seq Number - The Supplier Prepayment Top Up Floor Seq Number data item is not applicable to the Device Type
Source
DUIS 4.0, 5.0
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
Invalid Supplier Prepayment Top Up Floor Seq Number - The Supplier Prepayment Top Up Floor Seq Number data item is not applicable to the Device Type
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.75.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 1.1
Invalid Supplier Prepayment Top Up Floor Seq Number - The Supplier Prepayment Top Up Floor Seq Number data item is not applicable to the Device Type
Source
DUIS 1.1
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E062303
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 5.1, 5.2, 5.3, 5.4, 5.5
Device Type / Certificate Type mismatch - The Certificate Type is not applicable to the Device Type or not all Certificate Type applicable to the Device Type have been included in the Request or a certificate with an incorrect key usage has been provided for a Certificate Type
Source
DUIS 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 4.0, 5.0
Device Type / Certificate Type mismatch - The Certificate Type is not applicable to the Device Type or not all Certificate Type applicable to the Device Type have been included in the Request
Source
DUIS 4.0, 5.0
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
Device Type / Certificate Type mismatch - The Certificate Type is not applicable to the Device Type or not all Certificate Type applicable to the Device Type have been included in the Request
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.75.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 1.1
Device Type / Certificate Type mismatch - The Certificate Type is not applicable to the Device Type or not all Certificate Type applicable to the Device Type have been included in the Request
Source
DUIS 1.1
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E062304
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 5.1, 5.2, 5.3, 5.4, 5.5
User / Certificate mismatch - At least one of the Certificates included in the Request Body does not correspond to the User submitting the Request or a certificate with an incorrect Remote Party Role has been provided for a replacement Certificate
Source
DUIS 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 4.0, 5.0
User / Certificate mismatch - At least one of the Certificates included in the Request Body does not correspond to the User submitting the Request
Source
DUIS 4.0, 5.0
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
User / Certificate mismatch - At least one of the Certificates included in the Request Body does not correspond to the User submitting the Request
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.75.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
Service-specific validation
Documented in DUIS 1.1
User / Certificate mismatch - At least one of the Certificates included in the Request Body does not correspond to the User submitting the Request
Source
DUIS 1.1
§ 3.8.74.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E062305
Included in DUIS XSD versions
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.1, 5.2, 5.3, 5.4, 5.5
CoS Party / Certificate mismatch - The target Device holds a CoS Certificate in the CoS Party Trust Anchor Cell that is not an active CoS Party Certificate
Source
DUIS 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
No entry in the parsed DUIS tables.
E062306
Included in DUIS XSD versions
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.1, 5.2, 5.3, 5.4, 5.5
Incorrect MPID - The MPID (Market Participant ID) included within the Certificate that is used to sign the Request does not correspond to the Registered Supplier for the MPxN associated with the Device
Source
DUIS 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.23 · UpdateSecurityCredentials(CoS)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’.
No entry in the parsed DUIS tables.
E062401
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User Role is not a Known Remote Party (KRP) of the Device
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.77.3 · Specific Validation for this RequestSRV 6.24.1 · RetrieveDeviceSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User Role is not a Known Remote Party (KRP) of the Device
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.76.3 · Specific Validation for this RequestSRV 6.24.1 · RetrieveDeviceSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests.
Service-specific validation
Documented in DUIS 1.1
The User Role is not a Known Remote Party (KRP) of the Device
Source
DUIS 1.1
§ 3.8.75.3 · Specific Validation for this RequestSRV 6.24.1 · RetrieveDeviceSecurityCredentials(KRP)
No entry in the parsed DUIS tables.
E062402
Included in DUIS XSD versions
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type is ESME and ‘LoadController’ is specified for one of the RemotePartyRole XML data items in the Service Request, however the firmware version recorded in the SMI for the Device is not at GBCS version 4.0 or later
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.77.3 · Specific Validation for this RequestSRV 6.24.1 · RetrieveDeviceSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests.
No entry in the parsed DUIS tables.
E062403
Included in DUIS XSD versions
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type is not ESME, however ‘LoadController’ is specified for one of the RemotePartyRole XML data items in the Service Request
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.77.3 · Specific Validation for this RequestSRV 6.24.1 · RetrieveDeviceSecurityCredentials(KRP)Section context
See clause 3.2.5 for general validation applied to all Requests.
No entry in the parsed DUIS tables.
E062801
Included in DUIS XSD versions
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
At least one of the Sub GHz channels in the Service Request is not included in the Sub GHz Available Channels
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.82.3 · Specific Validation for this RequestSRV 6.28 · SetCHFSubGHzConfigurationSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Dual Band CHF validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
At least one of the Sub GHz channels in the Service Request is not included in the Sub GHz Available Channels
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.81.3 · Specific Validation for this RequestSRV 6.28 · SetCHFSubGHzConfigurationSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Dual Band CHF validation.
No entry in the parsed DUIS tables.
E062802
Included in DUIS XSD versions
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Service Request does not contain the required minimum number of Sub GHz channels in one or more of the Page Masks, as defined in GBCS section 10.6.2.3
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.82.3 · Specific Validation for this RequestSRV 6.28 · SetCHFSubGHzConfigurationSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Dual Band CHF validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Service Request does not contain the required minimum number of Sub GHz channels in one or more of the Page Masks, as defined in GBCS section 10.6.2.3
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.81.3 · Specific Validation for this RequestSRV 6.28 · SetCHFSubGHzConfigurationSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Dual Band CHF validation.
No entry in the parsed DUIS tables.
E062803
Included in DUIS XSD versions
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The LimitedCriticalDutyCycleThreshold is not > NormalLimitedDutyCycleThreshold
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.82.3 · Specific Validation for this RequestSRV 6.28 · SetCHFSubGHzConfigurationSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Dual Band CHF validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The LimitedCriticalDutyCycleThreshold is not > NormalLimitedDutyCycleThreshold
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.81.3 · Specific Validation for this RequestSRV 6.28 · SetCHFSubGHzConfigurationSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Dual Band CHF validation.
No entry in the parsed DUIS tables.
E080201
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Request does not uniquely identify a Premises
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.104.3 · Specific Validation for this RequestSRV 8.2 · ReadInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Request does not uniquely identify a Premises
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.99.3 · Specific Validation for this RequestSRV 8.2 · ReadInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
The Request does not uniquely identify a Premises
Source
DUIS 1.1
§ 3.8.91.3 · Specific Validation for this RequestSRV 8.2 · ReadInventorySection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E080202
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Premises do not contain any Devices
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.104.3 · Specific Validation for this RequestSRV 8.2 · ReadInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Premises do not contain any Devices
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.99.3 · Specific Validation for this RequestSRV 8.2 · ReadInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
The Premises do not contain any Devices
Source
DUIS 1.1
§ 3.8.91.3 · Specific Validation for this RequestSRV 8.2 · ReadInventorySection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E080301
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Status is invalid
Footnotes
Invalid Device Statuses are ‘Decommissioned’, ‘Pending’ or ‘Withdrawn’
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.105.3 · Specific Validation for this RequestSRV 8.3 · DecommissionDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Note that for this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device Status to be ‘Recovery’.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Status is invalid
Footnotes
Invalid Device Statuses are ‘Decommissioned’, ‘Pending’ or ‘Withdrawn’
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.100.3 · Specific Validation for this RequestSRV 8.3 · DecommissionDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Note that for this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device Status to be ‘Recovery’.
Service-specific validation
Documented in DUIS 1.1
The Device Status is invalid
Footnotes
Invalid Device Statuses are ‘Decommissioned’, ‘Pending’ or ‘Withdrawn’
Source
DUIS 1.1
§ 3.8.92.3 · Specific Validation for this RequestSRV 8.3 · DecommissionDeviceSection context
Note that for this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device Status to be ‘Recovery’.
No entry in the parsed DUIS tables.
E080302
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type is invalid
Footnotes
Check that the Device Type is not GPF or a Type 2 Device (IHD or CAD)
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.105.3 · Specific Validation for this RequestSRV 8.3 · DecommissionDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Note that for this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device Status to be ‘Recovery’.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Type is invalid
Footnotes
Check that the Device Type is not GPF or a Type 2 Device (IHD or CAD)
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.100.3 · Specific Validation for this RequestSRV 8.3 · DecommissionDeviceSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Note that for this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device Status to be ‘Recovery’.
Service-specific validation
Documented in DUIS 1.1
The Device Type is invalid
Footnotes
Check that the Device Type is not GPF or a Type 2 Device (IHD or CAD)
Source
DUIS 1.1
§ 3.8.92.3 · Specific Validation for this RequestSRV 8.3 · DecommissionDeviceSection context
Note that for this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device Status to be ‘Recovery’.
No entry in the parsed DUIS tables.
E080405
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Status is not applicable to the Device Type
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Status is not applicable to the Device Type
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Status is not applicable to the Device Type
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080406
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Status transition is not valid
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Status transition is not valid
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Status transition is not valid
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080407
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 5.2, 5.3, 5.4, 5.5
The Device ID does not exist in the Smart Metering Inventory or its status is not valid for the requested update
Source
DUIS 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1
The Device ID does not exist in the Smart Metering Inventory or its status is not ‘Pending’
Source
DUIS 4.0, 5.0, 5.1
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device ID does not exist in the Smart Metering Inventory or its status is not ‘Pending’
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device ID does not exist in the Smart Metering Inventory or its status is not ‘Pending’
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080408
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Request does not include any details to be updated
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Request does not include any details to be updated
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Request does not include any details to be updated
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080409
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type / Manufacturer / Model / Firmware Version data resulting from the changes specified by the User does not match the DCC list of equipment that has been approved for use
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Type / Manufacturer / Model / Firmware Version data resulting from the changes specified by the User does not match the DCC list of equipment that has been approved for use
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Type / Manufacturer / Model / Firmware Version data resulting from the changes specified by the User does not match the DCC list of equipment that has been approved for use
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080410
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User is not authorised to execute the Service Request to update the detail specified
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User is not authorised to execute the Service Request to update the detail specified
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The User is not authorised to execute the Service Request to update the detail specified
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080411
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Request to update Device Status not applicable to the Device Type
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
Request to update Device Status not applicable to the Device Type
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
Request to update Device Status not applicable to the Device Type
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080412
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Status transition is not valid
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Status transition is not valid
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Status transition is not valid
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080413
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The requested MPxN update isn’t suitable for the specified Device.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The requested MPxN update isn’t suitable for the specified Device.
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The requested MPxN update isn’t suitable for the specified Device.
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080414
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Status does not allow the MPxN to be updated. The Device Status must be one of ‘Whitelisted’, ‘Installed Not Commissioned’ or ‘Commissioned’ if the MPxN update is to succeed.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 3.0, 3.1
The Device Status does not allow the MPxN to be updated. The Device Status must be one of ‘Whitelisted’, ‘Installed Not Commissioned’ or ‘Commissioned’ if the MPxN update is to succeed.
Source
DUIS 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0
The Device Status does not allow the MPxN to be updated.
Source
DUIS 2.0
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Status does not allow the MPxN to be updated.
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080415
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User is not the Registered Supplier Party for the new MPxN specified within the UpdateMPxN part of the Service Request.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 3.0, 3.1
The User is not the Registered Supplier Party for the new MPxN specified within the UpdateMPxN part of the Service Request.
Source
DUIS 3.0, 3.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0
The User is not the Responsible Supplier for the new MPxN specified within the Service Request.
Source
DUIS 2.0
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventorySection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The User is not the Responsible Supplier for the new MPxN specified within the Service Request.
Source
DUIS 1.1
§ 3.8.93.3 · Specific Validation for this RequestSRV 8.4 · UpdateInventory
No entry in the parsed DUIS tables.
E080501
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device is associated to a Domestic MPxN
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.107.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOutSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device is associated to a Domestic MPxN
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.102.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOutSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 1.1
The Device is associated to a Domestic MPxN
Source
DUIS 1.1
§ 3.8.94.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOut
No entry in the parsed DUIS tables.
E080502
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Status is ‘Withdrawn’ (this particular check and Response Code is not expected to be reached in this DUIS version, as the generic Authorisation Check associated to Response Code E5 will fail prior to this check being carried out)
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.107.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOutSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 3.1
The Device Status is ‘Withdrawn (this particular check and Response Code is not expected to be reached in this DUIS version, as the generic Authorisation Check associated to Response Code E5 will fail prior to this check being carried out)
Source
DUIS 3.1
§ 3.8.102.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOutSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0
The Device Status is ‘Withdrawn’ (this particular check and Response Code is not expected to be reached in this DUIS version, as the generic Authorisation Check associated to Response Code E5 will fail prior to this check being carried out)
Source
DUIS 2.0, 3.0
§ 3.8.102.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOutSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 1.1
The Device Status is ‘Withdrawn’
Source
DUIS 1.1
§ 3.8.94.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOut
No entry in the parsed DUIS tables.
E080503
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Certificate Type is not applicable to the Device Type
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.107.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOutSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Certificate Type is not applicable to the Device Type
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.102.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOutSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time and Public Security Credentials validation.
Service-specific validation
Documented in DUIS 1.1
The Certificate Type is not applicable to the Device Type
Source
DUIS 1.1
§ 3.8.94.3 · Specific Validation for this RequestSRV 8.5 · ServiceOptOut
No entry in the parsed DUIS tables.
E080601
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Opt In Date is not a date in the future
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Opt In Date is not a date in the future
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.103.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Opt In Date is not a date in the future
Source
DUIS 1.1
§ 3.8.95.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptIn
No entry in the parsed DUIS tables.
E080602
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type is not correct
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Type is not correct
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.103.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Type is not correct
Source
DUIS 1.1
§ 3.8.95.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptIn
No entry in the parsed DUIS tables.
E080604
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Status is not ‘Pending’
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Status is not ‘Pending’
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.103.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Status is not ‘Pending’
Source
DUIS 1.1
§ 3.8.95.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptIn
No entry in the parsed DUIS tables.
E080606
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type is invalid
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Type is invalid
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.103.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Type is invalid
Source
DUIS 1.1
§ 3.8.95.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptIn
No entry in the parsed DUIS tables.
E080607
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User is not the registered organisation of any of the MPxNs in the Service Request
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User is not the registered organisation of any of the MPxNs in the Service Request
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.103.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptInSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Device Existence validation.
Service-specific validation
Documented in DUIS 1.1
The User is not the registered organisation of any of the MPxNs in the Service Request
Source
DUIS 1.1
§ 3.8.95.3 · Specific Validation for this RequestSRV 8.6 · ServiceOptIn
No entry in the parsed DUIS tables.
E080702
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The ‘Other Device’ Type is not valid for this Join Service
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.7.1 · JoinService(Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The ‘Other Device’ Type is not valid for this Join Service
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.104.3 · Specific Validation for this RequestSRV 8.7.1 · JoinService(Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The ‘Other Device’ Type is not valid for this Join Service
Source
DUIS 1.1
§ 3.8.96.3 · Specific Validation for this RequestSRV 8.7.1 · JoinService(Critical)
No entry in the parsed DUIS tables.
E080721
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The ‘Other Device’ Type is not valid for this Join Service
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.110.3 · Specific Validation for this RequestSRV 8.7.2 · JoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The ‘Other Device’ Type is not valid for this Join Service
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.105.3 · Specific Validation for this RequestSRV 8.7.2 · JoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The ‘Other Device’ Type is not valid for this Join Service
Source
DUIS 1.1
§ 3.8.97.3 · Specific Validation for this RequestSRV 8.7.2 · JoinService(Non-Critical)
No entry in the parsed DUIS tables.
E080722
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User Role is not authorised to Join this Device Type
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.110.3 · Specific Validation for this RequestSRV 8.7.2 · JoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User Role is not authorised to Join this Device Type
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.105.3 · Specific Validation for this RequestSRV 8.7.2 · JoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The User Role is not authorised to Join this Device Type
Source
DUIS 1.1
§ 3.8.97.3 · Specific Validation for this RequestSRV 8.7.2 · JoinService(Non-Critical)
No entry in the parsed DUIS tables.
E080723
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User is not authorised to Join these Gas Smart Meter / Gas Proxy Function
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.110.3 · Specific Validation for this RequestSRV 8.7.2 · JoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User is not authorised to Join these Gas Smart Meter / Gas Proxy Function
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.105.3 · Specific Validation for this RequestSRV 8.7.2 · JoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The User is not authorised to Join these Gas Smart Meter / Gas Proxy Function
Source
DUIS 1.1
§ 3.8.97.3 · Specific Validation for this RequestSRV 8.7.2 · JoinService(Non-Critical)
No entry in the parsed DUIS tables.
E080801
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (5 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 5.3, 5.4, 5.5
This Response Code is not used. The DCC Systems Smart Metering Inventory is no longer checked for the join status of the ‘Other Device’
Sources
DUIS 5.3, 5.4, 5.5
§ 3.8.111.3 · Specific Validation for this RequestSRV 8.8.1 · UnjoinService(Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
§ 3.8.112.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 5.2
According to the DCC Systems Smart Meter Inventory the ‘Other Device’ is not joined to the BusinessTargetID Device
Sources
DUIS 5.2
§ 3.8.111.3 · Specific Validation for this RequestSRV 8.8.1 · UnjoinService(Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
§ 3.8.112.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1
According to the DCC Systems Smart Metering Inventory the ‘Other Device’ is not joined to the BusinessTargetID Device
Sources
DUIS 4.0, 5.0, 5.1
§ 3.8.111.3 · Specific Validation for this RequestSRV 8.8.1 · UnjoinService(Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
§ 3.8.112.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
According to the DCC Systems Smart Metering Inventory the ‘Other Device’ is not joined to the BusinessTargetID Device
Sources
DUIS 2.0, 3.0, 3.1
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.8.1 · UnjoinService(Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
§ 3.8.107.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
According to the DCC Systems Smart Metering Inventory the ‘Other Device’ is not joined to the BusinessTargetID Device
Sources
DUIS 1.1
§ 3.8.98.3 · Specific Validation for this RequestSRV 8.8.1 · UnjoinService(Critical)
§ 3.8.99.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)
No entry in the parsed DUIS tables.
E080821
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 5.3, 5.4, 5.5
The User Role is not authorised to Unjoin this Device Type
Source
DUIS 5.3, 5.4, 5.5
§ 3.8.112.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2
The User Role is not authorised to Unjoin tis Device Type
Source
DUIS 4.0, 5.0, 5.1, 5.2
§ 3.8.112.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User Role is not authorised to Unjoin tis Device Type
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.107.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The User Role is not authorised to Unjoin tis Device Type
Source
DUIS 1.1
§ 3.8.99.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)
No entry in the parsed DUIS tables.
E080822
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User is not authorised to Unjoin these Gas Smart Meter / Gas Proxy Function
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.112.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User is not authorised to Unjoin these Gas Smart Meter / Gas Proxy Function
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.107.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)Section context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Other Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The User is not authorised to Unjoin these Gas Smart Meter / Gas Proxy Function
Source
DUIS 1.1
§ 3.8.99.3 · Specific Validation for this RequestSRV 8.8.2 · UnjoinService(Non-Critical)
Check that if the target Device is a SMETS1 Device according to the Smart Metering Inventory then the target Device’s Device Type is CHF according to the Smart Metering Inventory. For clarity, SMETS1 does not require any other Device Logs be supported.
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 8.9 · ReadDeviceLogSection context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
No entry in the parsed DUIS tables.
E080902
Included in DUIS XSD versions
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
ReadSecurityDetails is specified in the Service Request but the Firmware Version recorded in the SMI for the Device is not at GBCS version 3.2 or later.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.113.3 · Specific Validation for this RequestSRV 8.9 · ReadDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where the Request is sent by an Import Supplier or Gas Supplier to a CHF where there are no Smart Meters associated with that CHF.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0
Documented but absent from that release’s DUIS XSD: 2.0.
ReadSecurityDetails is specified in the Service Request but the Firmware Version recorded in the SMI for the Device is not at GBCS version 3.2 or later.
Source
DUIS 2.0
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.9 · ReadDeviceLogSection context
No specific validation is applied for this Request, see clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where the Request is sent by an Import Supplier or Gas Supplier to a CHF where there are no Smart Meters associated with that CHF.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device”
No entry in the parsed DUIS tables.
E080903
Included in DUIS XSD versions
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (2 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
ReadSecurityDetails is specified in the Service Request but the Device Type is not a CHF.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.113.3 · Specific Validation for this RequestSRV 8.9 · ReadDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where the Request is sent by an Import Supplier or Gas Supplier to a CHF where there are no Smart Meters associated with that CHF.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0
Documented but absent from that release’s DUIS XSD: 2.0.
ReadSecurityDetails is specified in the Service Request but the Device Type is not a CHF.
Source
DUIS 2.0
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.9 · ReadDeviceLogSection context
No specific validation is applied for this Request, see clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where the Request is sent by an Import Supplier or Gas Supplier to a CHF where there are no Smart Meters associated with that CHF.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device”
No entry in the parsed DUIS tables.
E081101
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device ID of a Device to be added to the CHF Whitelist is already associated with another CHF Whitelist
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device ID of a Device to be added to the CHF Whitelist is already associated with another CHF Whitelist
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 1.1
The Device ID of a Device to be added to the CHF Whitelist is already associated with another CHF Whitelist
Source
DUIS 1.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081102
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device ID of a Device to be removed is not included in the CHF Whitelist
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device ID of a Device to be removed is not included in the CHF Whitelist
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 1.1
The Device ID of a Device to be removed is not included in the CHF Whitelist
Source
DUIS 1.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081104
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type of the Device to be added to the Whitelist is invalid, e.g. if it is a Communications Hub Function or Gas Proxy Function
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Type of the Device to be added to the Whitelist is invalid, e.g. if it is a Communications Hub Function or Gas Proxy Function
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 1.1
The Device Type of the Device to be added to the Whitelist is invalid, e.g. if it is a Communications Hub Function or Gas Proxy Function
Source
DUIS 1.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081105
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The status of the Device being added to the Whitelist is not ‘Installed not Commissioned’, ‘Pending’ or ‘Whitelisted’
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The status of the Device being added to the Whitelist is not ‘Installed not Commissioned’, ‘Pending’ or ‘Whitelisted’
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 1.1
The status of the Device being added to the Whitelist is not ‘Installed not Commissioned’, ‘Pending’ or ‘Whitelisted’
Source
DUIS 1.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081106
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
If the Request Type is: ‘Add’. It doesn’t include the Add Device CHF Whitelist element ‘Remove’. It does include the Add Device CHF Whitelist element
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
If the Request Type is: ‘Add’. It doesn’t include the Add Device CHF Whitelist element ‘Remove’. It does include the Add Device CHF Whitelist element
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 1.1
If the Request Type is: ‘Add’. It doesn’t include the Add Device CHF Whitelist element ‘Remove’. It does include the Add Device CHF Whitelist element
Source
DUIS 1.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081107
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device ID of the Device to be added to or removed from the Whitelist does not exist
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device ID of the Device to be added to or removed from the Whitelist does not exist
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 1.1
The Device ID of the Device to be added to or removed from the Whitelist does not exist
Source
DUIS 1.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081108
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User Role is not authorised to add this Device Type to the HAN Device Log or remove it form it
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User Role is not authorised to add this Device Type to the HAN Device Log or remove it form it
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 1.1
The User Role is not authorised to add this Device Type to the HAN Device Log or remove it form it
Source
DUIS 1.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081109
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User is not the registered organisation for all of the MPxNs in the Service Request (This check supersedes the general Authorisation Check associated to Response Code E4 only for Request Type ‘Add' (please note the check associated to Response Code E4 is applicable to Request Type ‘Remove’))
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 3.0, 3.1
The User is not the registered organisation for all of the MPxNs in the Service Request (This check supersedes the general Authorisation Check associated to Response Code E4 only for Request Type ‘Add' (please note the check associated to Response Code E4 is applicable to Request Type ‘Remove’))
Source
DUIS 3.0, 3.1
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0
The User is not the registered organisation of any of the MPxNs in the Service Request (This check supersedes the general Authorisation Check associated to Response Code E4 only for Request Type ‘Add' (please note the check associated to Response Code E4 is applicable to Request Type ‘Remove’))
Source
DUIS 2.0
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 1.1
The User is not the registered organisation of any of the MPxNs in the Service Request
Source
DUIS 1.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081110
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Service Request contains an Invalid MPAN Type, e.g. the Import MPxN is populated with an Export MPAN
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Service Request contains an Invalid MPAN Type, e.g. the Import MPxN is populated with an Export MPAN
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.109.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
Service-specific validation
Documented in DUIS 1.1
The Service Request contains an Invalid MPAN Type, e.g. the Import MPxN is populated with an Export MPAN
Source
DUIS 1.1
§ 3.8.101.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081111
Included in DUIS XSD versions
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Service Request refers to a SMETS2+ Device and the InstallCode field is not 32 characters (representing 16 octets) in length.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.11 · UpdateHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for Execution Date Time validation.
For this Request, the general Authorisation Checks as defined below shall not be carried out where an IHD is being added to the Device Log by a User and the command is requested for Local Delivery only.
• a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
No entry in the parsed DUIS tables.
E081202
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Old CHF ID doesn’t correspond to a Device of Type Communications Hub Function
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.115.3 · Specific Validation for this RequestSRV 8.12.1 · RestoreHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old CHF Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Old CHF ID doesn’t correspond to a Device of Type Communications Hub Function
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.110.3 · Specific Validation for this RequestSRV 8.12.1 · RestoreHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old CHF Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Old CHF ID doesn’t correspond to a Device of Type Communications Hub Function
Source
DUIS 1.1
§ 3.8.102.3 · Specific Validation for this RequestSRV 8.12.1 · RestoreHANDeviceLog
No entry in the parsed DUIS tables.
E081204
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Status of the new Communications Hub Function is invalid
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.115.3 · Specific Validation for this RequestSRV 8.12.1 · RestoreHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old CHF Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Status of the new Communications Hub Function is invalid
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.110.3 · Specific Validation for this RequestSRV 8.12.1 · RestoreHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old CHF Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Status of the new Communications Hub Function is invalid
Source
DUIS 1.1
§ 3.8.102.3 · Specific Validation for this RequestSRV 8.12.1 · RestoreHANDeviceLog
No entry in the parsed DUIS tables.
E081205
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User is not a Responsible Supplier to any of the MPxNs associated with Device(s) in the Old CHF ID Whitelist
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.115.3 · Specific Validation for this RequestSRV 8.12.1 · RestoreHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old CHF Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User is not a Responsible Supplier to any of the MPxNs associated with Device(s) in the Old CHF ID Whitelist
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.110.3 · Specific Validation for this RequestSRV 8.12.1 · RestoreHANDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old CHF Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The User is not a Responsible Supplier to any of the MPxNs associated with Device(s) in the Old CHF ID Whitelist
Source
DUIS 1.1
§ 3.8.102.3 · Specific Validation for this RequestSRV 8.12.1 · RestoreHANDeviceLog
No entry in the parsed DUIS tables.
E081221
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Old GPF ID doesn’t correspond to a Device of Type Gas Proxy Function
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.116.3 · Specific Validation for this RequestSRV 8.12.2 · RestoreGPFDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old GPF Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Old GPF ID doesn’t correspond to a Device of Type Gas Proxy Function
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.111.3 · Specific Validation for this RequestSRV 8.12.2 · RestoreGPFDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old GPF Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Old GPF ID doesn’t correspond to a Device of Type Gas Proxy Function
Source
DUIS 1.1
§ 3.8.103.3 · Specific Validation for this RequestSRV 8.12.2 · RestoreGPFDeviceLog
No entry in the parsed DUIS tables.
E081222
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Status of the new Gas Proxy Function is invalid
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.116.3 · Specific Validation for this RequestSRV 8.12.2 · RestoreGPFDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old GPF Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Status of the new Gas Proxy Function is invalid
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.111.3 · Specific Validation for this RequestSRV 8.12.2 · RestoreGPFDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old GPF Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The Device Status of the new Gas Proxy Function is invalid
Source
DUIS 1.1
§ 3.8.103.3 · Specific Validation for this RequestSRV 8.12.2 · RestoreGPFDeviceLog
No entry in the parsed DUIS tables.
E081223
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User is not an Import Supplier to any of the MPxNs associated with Device(s) in the CHF ID Whitelist associated to the BusinessTargetID GPF
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.116.3 · Specific Validation for this RequestSRV 8.12.2 · RestoreGPFDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old GPF Device’ Existence validation.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User is not an Import Supplier to any of the MPxNs associated with Device(s) in the CHF ID Whitelist associated to the BusinessTargetID GPF
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.111.3 · Specific Validation for this RequestSRV 8.12.2 · RestoreGPFDeviceLogSection context
See clause 3.2.5 for general validation applied to all Requests and clause 3.10.2 for ‘Old GPF Device’ Existence validation.
Service-specific validation
Documented in DUIS 1.1
The DCC Service User is not a registered Import Supplier to any of the MPxNs associated with Device(s) in the CHF ID Whitelist associated to the BusinessTargetID GPF
Source
DUIS 1.1
§ 3.8.103.3 · Specific Validation for this RequestSRV 8.12.2 · RestoreGPFDeviceLog
No entry in the parsed DUIS tables.
E081301
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Original Request ID doesn’t correspond to a Command to be Delivered Locally for which no Response has been received
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.117.3 · Specific Validation for this RequestSRV 8.13 · ReturnLocalCommandResponseSection context
See clause 3.2.5 for general validation applied to all Requests.
Note that Response Codes E081301 and E081303 should be ignored by Users if they correspond to Commands that were not applied locally.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Original Request ID doesn’t correspond to a Command to be Delivered Locally for which no Response has been received
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.112.3 · Specific Validation for this RequestSRV 8.13 · ReturnLocalCommandResponseSection context
See clause 3.2.5 for general validation applied to all Requests.
Note that Response Codes E081301 and E081303 should be ignored by Users if they correspond to Commands that were not applied locally.
Service-specific validation
Documented in DUIS 1.1
The Original Request ID doesn’t correspond to a Command to be Delivered Locally for which no Response has been received
Source
DUIS 1.1
§ 3.8.104.3 · Specific Validation for this RequestSRV 8.13 · ReturnLocalCommandResponseSection context
Note that Response Codes E081301 and E081303 should be ignored by Users if they correspond to Commands that were not applied locally.
No entry in the parsed DUIS tables.
E081302
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Response doesn’t correspond to the Original Request ID or it isn’t a valid Alert Type (This check is not applicable to Service Request 6.23 Update Security Credentials (CoS))
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.117.3 · Specific Validation for this RequestSRV 8.13 · ReturnLocalCommandResponseSection context
See clause 3.2.5 for general validation applied to all Requests.
Note that Response Codes E081301 and E081303 should be ignored by Users if they correspond to Commands that were not applied locally.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Response doesn’t correspond to the Original Request ID or it isn’t a valid Alert Type (This check is not applicable to Service Request 6.23 Update Security Credentials (CoS))
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.112.3 · Specific Validation for this RequestSRV 8.13 · ReturnLocalCommandResponseSection context
See clause 3.2.5 for general validation applied to all Requests.
Note that Response Codes E081301 and E081303 should be ignored by Users if they correspond to Commands that were not applied locally.
Service-specific validation
Documented in DUIS 1.1
The Response doesn’t correspond to the Original Request ID or it isn’t a valid Device Alert Type
Source
DUIS 1.1
§ 3.8.104.3 · Specific Validation for this RequestSRV 8.13 · ReturnLocalCommandResponseSection context
Note that Response Codes E081301 and E081303 should be ignored by Users if they correspond to Commands that were not applied locally.
No entry in the parsed DUIS tables.
E081303
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
If the OriginalRequestID is included in the Request, the Device GBCS Response is not a successful Response If the OriginalRequestID is not included in the Request, the Device GBCS Response is not a Response for a Command to be Delivered Locally for which no Response has been received or valid Alert Type corresponding to a Command for which an Alert is expected and for which the DCC Systems have to perform the relevant actions
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.117.3 · Specific Validation for this RequestSRV 8.13 · ReturnLocalCommandResponseSection context
See clause 3.2.5 for general validation applied to all Requests.
Note that Response Codes E081301 and E081303 should be ignored by Users if they correspond to Commands that were not applied locally.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
If the OriginalRequestID is included in the Request, the Device GBCS Response is not a successful Response If the OriginalRequestID is not included in the Request, the Device GBCS Response is not a Response for a Command to be Delivered Locally for which no Response has been received or valid Alert Type corresponding to a Command for which an Alert is expected and for which the DCC Systems have to perform the relevant actions
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.112.3 · Specific Validation for this RequestSRV 8.13 · ReturnLocalCommandResponseSection context
See clause 3.2.5 for general validation applied to all Requests.
Note that Response Codes E081301 and E081303 should be ignored by Users if they correspond to Commands that were not applied locally.
Service-specific validation
Documented in DUIS 1.1
If the OriginalRequestID is included in the Request, the Device GBCS Response is not a successful Response If the OriginalRequestID is not included in the Request, the Device GBCS Response is not a Response for a Command to be Delivered Locally for which no Response has been received or valid Device Alert Type corresponding to a Command for which a Device Alert is expected and for which the DCC Systems have to perform the relevant actions
Source
DUIS 1.1
§ 3.8.104.3 · Specific Validation for this RequestSRV 8.13 · ReturnLocalCommandResponseSection context
Note that Response Codes E081301 and E081303 should be ignored by Users if they correspond to Commands that were not applied locally.
No entry in the parsed DUIS tables.
E081401
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type of the Device being notified is not CHF
Sources
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.118.3 · Specific Validation for this RequestSRV 8.14.1 · CommunicationsHubStatusUpdate-InstallSuccessSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.119.3 · Specific Validation for this RequestSRV 8.14.2 · CommunicationsHubStatusUpdate-InstallNoSMWANSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.120.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits the Service Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
§ 3.8.121.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits this Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
.DUIS 5.3
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device Type of the Device being notified is not CHF
Sources
DUIS 2.0, 3.0, 3.1
§ 3.8.113.3 · Specific Validation for this RequestSRV 8.14.1 · CommunicationsHubStatusUpdate-InstallSuccessSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verily that the User, in the User Role defined in the Service Request is a Eligible User for the Device”DUIS 2.0
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”DUIS 3.0, 3.1
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.14.2 · CommunicationsHubStatusUpdate-InstallNoSMWANSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.115.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits the Service Request then a specific validation check will be carried out for Response Code E5 as described in the table below.DUIS 3.1
§ 3.8.116.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits this Request then a specific validation check will be carried out for Response Code E5 as described in the table below.DUIS 3.1
Service-specific validation
Documented in DUIS 1.1
The Device Type of the Device being notified is not CHF
Sources
DUIS 1.1
§ 3.8.105.3 · Specific Validation for this RequestSRV 8.14.1 · CommunicationsHubStatusUpdate-InstallSuccessSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.14.2 · CommunicationsHubStatusUpdate-InstallNoSMWANSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.107.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E081402
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The install date & time supplied is a future date
Sources
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.118.3 · Specific Validation for this RequestSRV 8.14.1 · CommunicationsHubStatusUpdate-InstallSuccessSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.119.3 · Specific Validation for this RequestSRV 8.14.2 · CommunicationsHubStatusUpdate-InstallNoSMWANSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The install date & time supplied is a future date
Sources
DUIS 2.0, 3.0, 3.1
§ 3.8.113.3 · Specific Validation for this RequestSRV 8.14.1 · CommunicationsHubStatusUpdate-InstallSuccessSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verily that the User, in the User Role defined in the Service Request is a Eligible User for the Device”DUIS 2.0
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”DUIS 3.0, 3.1
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.14.2 · CommunicationsHubStatusUpdate-InstallNoSMWANSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
The install date & time supplied is a future date
Sources
DUIS 1.1
§ 3.8.105.3 · Specific Validation for this RequestSRV 8.14.1 · CommunicationsHubStatusUpdate-InstallSuccessSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.14.2 · CommunicationsHubStatusUpdate-InstallNoSMWANSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E081405
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (6 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The user reference date & time supplied is a future date
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.120.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits the Service Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The User reference date & time supplied is a future date
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.121.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits this Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
.DUIS 5.3
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The user reference date & time supplied is a future date
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.115.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits the Service Request then a specific validation check will be carried out for Response Code E5 as described in the table below.DUIS 3.1
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The User reference date & time supplied is a future date
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.116.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits this Request then a specific validation check will be carried out for Response Code E5 as described in the table below.DUIS 3.1
Service-specific validation
Documented in DUIS 1.1
The user reference date & time supplied is a future date
Source
DUIS 1.1
§ 3.8.107.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
The User reference date & time supplied is a future date
Source
DUIS 1.1
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E081406
Included in DUIS XSD versions
5.4
5.5
DUIS table details (2 table views)
Differences between views: Description.
Service-specific validation
Documented in DUIS 5.4, 5.5
The CHF Device status is not ‘Decommissioned’, and the CHF has associated Devices which are still communicating
Source
DUIS 5.4, 5.5
§ 3.8.120.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits the Service Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
Service-specific validation
Documented in DUIS 5.4, 5.5
The CHF status is not ‘Decommissioned’, and the CHF has associated Devices which are still communicating
Source
DUIS 5.4, 5.5
§ 3.8.121.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits this Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
No entry in the parsed DUIS tables.
E110101
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Firmware Version is not approved. The Firmware version ID does not align with an entry on the Central Products List.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.123.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 3.0, 3.1
The Firmware Version is not approved. The Firmware version ID does not align with an entry on the Central Products List.
Source
DUIS 3.0, 3.1
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 2.0
The Firmware Version is not approved. The Firmware version ID does not align with an entry on the Certified Products List.
Source
DUIS 2.0
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 1.1
The Firmware Version is not approved. The Firmware version ID does not align with an entry on the Certified Products List.
Source
DUIS 1.1
§ 3.8.110.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E110102
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (5 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The firmware is not marked as active in the Central Products List and Smart Metering Inventory.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.123.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 3.1
The firmware is not marked as active in the Central Products List and Smart Metering Inventory.
Source
DUIS 3.1
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 3.0
The firmware is not marked as active in the Central Products List and Smart MeteringInventory.
Source
DUIS 3.0
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 2.0
The firmware is not marked as active in the Certified Product List and Smart Metering Inventory.
Source
DUIS 2.0
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 1.1
The firmware is not marked as active in the Certified Product List and Smart Metering Inventory.
Source
DUIS 1.1
§ 3.8.110.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E110103
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (3 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The DCC Systems calculated Hash value over the Manufacturer Image part of the FirmwareImage provided by the User within the Service Request differs from that held in the CPL for the specified FirmwareVersion.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.123.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The DCC Systems calculated Hash value over the Manufacturer Image part of the FirmwareImage provided by the User within the Service Request differs from that held in the CPL for the specified FirmwareVersion.
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 1.1
The DCC Data Systems calculated Hash value over the Manufacturer Image part of the FirmwareImage provided by the User within the Service Request differs from that held in the CPL for the specified FirmwareVersion.
Source
DUIS 1.1
§ 3.8.110.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E110105
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (6 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.1, 5.3, 5.4, 5.5
The firmware image is not constructed as per the GBCS definition, i.e. the FirmwareImage does not contain both an OTA Header and a Firmware Image concatenated together , or where the Target Device is a SMETS2+ Device, the Length of the base64 encoded version of the GBCS defined Firmware “OTA Upgrade Image” exceeds 1024000.
Source
DUIS 4.0, 5.1, 5.3, 5.4, 5.5
§ 3.8.123.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 5.0, 5.2
The firmware image is not constructed as per the GBCS definition, i.e. the FirmwareImage does not contain both an OTA Header and a Firmware Image concatenated together, or where the Target Device is a SMETS2+ Device, the Length of the base64 encoded version of the GBCS defined Firmware “OTA Upgrade Image” exceeds 1024000.
Source
DUIS 5.0, 5.2
§ 3.8.123.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 3.1
The firmware image is not constructed as per the GBCS definition, i.e. the FirmwareImage does not contain both an OTA Header and a Firmware Image concatenated together, or where the Target Device is a SMETS2+ Device, the Length of the base64 encoded version of the GBCS defined Firmware “OTA Upgrade Image” exceeds 1024000.
Source
DUIS 3.1
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 3.0
The firmware image is not constructed as per the GBCS definition, i.e. the FirmwareImage does not contain both an OTA Header and a Firmware Image concatenated together , or where the Target Device is a SMETS2+ Device, the Length of the base64 encoded version of the GBCS defined Firmware “OTA Upgrade Image” exceeds 1024000.
Source
DUIS 3.0
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 2.0
The firmware image is not constructed as per the GBCS definition, i.e. the FirmwareImage does not contain both an OTA Header and a Firmware Image concatenated together
Source
DUIS 2.0
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 1.1
The firmware image is not constructed as per the GBCS definition, i.e. the FirmwareImage does not contain both an OTA Header and a Firmware Image concatenated together
Source
DUIS 1.1
§ 3.8.110.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E110106
Included in DUIS XSD versions
5.3
5.4
5.5
No entry in the parsed DUIS tables.
E110401
Included in DUIS XSD versions
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Firmware Version is not approved. The Firmware version ID does not align with an entry on the Central Products List.
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.126.3 · Specific Validation for this RequestSRV 11.4 · UpdatePPMIDFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E110402
Included in DUIS XSD versions
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The firmware is not marked as active in the Central Products List and Smart Metering Inventory.
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.126.3 · Specific Validation for this RequestSRV 11.4 · UpdatePPMIDFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E110403
Included in DUIS XSD versions
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The DCC Systems calculated Hash value over the Manufacturer Image part of the FirmwareImage provided by the User within the Service Request differs from that held in the CPL for the specified FirmwareVersion.
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.126.3 · Specific Validation for this RequestSRV 11.4 · UpdatePPMIDFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E110405
Included in DUIS XSD versions
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The firmware image is not constructed as per the GBCS definition, i.e. the FirmwareImage does not contain both an OTA Header and a Firmware Image concatenated together, or the Length of the base64 encoded version of the GBCS defined Firmware “OTA Upgrade Image” exceeds 1024000.
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.126.3 · Specific Validation for this RequestSRV 11.4 · UpdatePPMIDFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
E120101
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
No premises can be identified from the Request
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.127.3 · Specific Validation for this RequestSRV 12.1 · RequestWANMatrixSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” orDUIS 5.0, 5.1, 5.3, 5.4, 5.5
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” orDUIS 5.2
Service-specific validation
Documented in DUIS 4.0
No premises can be identified from the Request
Source
DUIS 4.0
§ 3.8.126.3 · Specific Validation for this RequestSRV 12.1 · RequestWANMatrixSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
No premises can be identified from the Request
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.121.3 · Specific Validation for this RequestSRV 12.1 · RequestWANMatrixSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” orDUIS 2.0, 3.0
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” orDUIS 3.1
Service-specific validation
Documented in DUIS 1.1
No premises can be identified from the Request
Source
DUIS 1.1
§ 3.8.112.3 · Specific Validation for this RequestSRV 12.1 · RequestWANMatrixSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E120102
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
No SM WAN data exists for the requested location (property)
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.127.3 · Specific Validation for this RequestSRV 12.1 · RequestWANMatrixSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” orDUIS 5.0, 5.1, 5.3, 5.4, 5.5
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” orDUIS 5.2
Service-specific validation
Documented in DUIS 4.0
No SM WAN data exists for the requested location (property)
Source
DUIS 4.0
§ 3.8.126.3 · Specific Validation for this RequestSRV 12.1 · RequestWANMatrixSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
No SM WAN data exists for the requested location (property)
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.121.3 · Specific Validation for this RequestSRV 12.1 · RequestWANMatrixSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” orDUIS 2.0, 3.0
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” orDUIS 3.1
Service-specific validation
Documented in DUIS 1.1
No SM WAN data exists for the for the requested location (property)
Source
DUIS 1.1
§ 3.8.112.3 · Specific Validation for this RequestSRV 12.1 · RequestWANMatrixSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E120103
Included in DUIS XSD versions
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.3, 5.4, 5.5
No SM WAN coverage data available for CSP Region
Source
DUIS 5.3, 5.4, 5.5
§ 3.8.127.3 · Specific Validation for this RequestSRV 12.1 · RequestWANMatrixSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E120201
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (5 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 5.5
One of: The Device ID already existed in Smart Metering Inventory and its Status was not ‘Decommissioned’ or ‘Withdrawn’ Or The AssociatedGPFDeviceID is the same as the DeviceID and DeviceType is CHF
Source
DUIS 5.5
§ 3.8.128.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4
The Device ID already existed in Smart Metering Inventory and its Status was not ‘Decommissioned’ or ‘Withdrawn’
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4
§ 3.8.128.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” orDUIS 5.0, 5.3, 5.4
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” orDUIS 5.1, 5.2
Service-specific validation
Documented in DUIS 4.0
The Device ID already existed in Smart Metering Inventory and its Status was not ‘Decommissioned’ or ‘Withdrawn’
Source
DUIS 4.0
§ 3.8.127.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Device ID already existed in Smart Metering Inventory and its Status was not ‘Decommissioned’ or ‘Withdrawn’
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.122.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
The Device ID already existed in Smart Metering Inventory and its Status was not ‘Decommissioned’ or ‘Withdrawn’
Source
DUIS 1.1
§ 3.8.113.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E120203
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (5 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Device Type / Manufacturer / Model / Firmware Version data specified by the User do not match the values contained on the Central Products List (CPL) that have been approved for use.
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.128.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” orDUIS 5.0, 5.3, 5.4, 5.5
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” orDUIS 5.1, 5.2
Service-specific validation
Documented in DUIS 4.0
The Device Type / Manufacturer / Model / Firmware Version data specified by the User do not match the values contained on the Central Products List (CPL) that have been approved for use.
Source
DUIS 4.0
§ 3.8.127.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 3.0, 3.1
The Device Type / Manufacturer / Model / Firmware Version data specified by the User do not match the values contained on the Central Products List (CPL) that have been approved for use.
Source
DUIS 3.0, 3.1
§ 3.8.122.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0
The Device Type / Manufacturer / Model / Firmware Version data specified by the User do not match the values contained on the Certified Products List (CPL) that have been approved for use.
Source
DUIS 2.0
§ 3.8.122.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
The Device Type / Manufacturer / Model / Firmware Version data specified by the User do not match the values contained on the Certified Products List (CPL) that have been approved for use.
Source
DUIS 1.1
§ 3.8.113.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E120204
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
Not all the applicable optional data items are included in the Request or not applicable data items are included in the Request
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.128.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” orDUIS 5.0, 5.3, 5.4, 5.5
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” orDUIS 5.1, 5.2
Service-specific validation
Documented in DUIS 4.0
Not all the applicable optional data items are included in the Request or not applicable data items are included in the Request
Source
DUIS 4.0
§ 3.8.127.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
Not all the applicable optional data items are included in the Request or not applicable data items are included in the Request
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.122.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
Not all the applicable optional data items are included in the Request or not applicable data items are included in the Request
Source
DUIS 1.1
§ 3.8.113.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
E120207
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (4 table views)
Differences between views: Source references.
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
This Device Type (GPF) can’t be Pre-notified
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.128.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” orDUIS 5.0, 5.3, 5.4, 5.5
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” orDUIS 5.1, 5.2
Service-specific validation
Documented in DUIS 4.0
This Device Type (GPF) can’t be Pre-notified
Source
DUIS 4.0
§ 3.8.127.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is an Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
This Device Type (GPF) can’t be Pre-notified
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.122.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
This Device Type (GPF) can’t be Pre-notified
Source
DUIS 1.1
§ 3.8.113.3 · Specific Validation for this RequestSRV 12.2 · DevicePrenotificationSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
a Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device” or
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Request received for sending to Device has been accepted and has passed access control Or In Response to a successful Non-Device Service Request where there is no specific XML data included in the Service Response
Type
Information
Applicable response types
Acknowledgement
Error Handling Strategy procedure
N/A
Source
DUIS 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.5.10 · Table 36 : DCC Systems Response Codes
Acknowledgement
Documented in DUIS 2.0
Request received for sending to Device has been accepted and has passed access control Or In Response to a successful Non-Device Service Request where there is no specific XML data included in the Service Response
Type
Information
Applicable response types
Acknowledgement
Error Handling Strategy procedure
N/A
Source
DUIS 2.0
§ 3.5.10 · Table 30 : DCC Systems Response Codes
Acknowledgement
Documented in DUIS 1.1
Request received for sending to Device has been accepted and has passed access control
§ 3.8.45.3 · Specific Validation for this RequestSRV 5.3 · DeleteScheduleSection context
See clause 3.2.5 for general validation applied to all Requests.DUIS 2.0, 3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
No entry in the parsed DUIS tables.
W081401
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (10 table views)
Differences between views: Description, Source references.
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The CHF SMI Status is not ‘Commissioned’. The change in logistical status of the CHF will be processed by the DCC, but no commissioned status is set according to information from the SM WAN rather than Service Requests. If the CHF SMI Status is not ‘Commissioned’ this suggests that the CHF Device has not been installed successfully.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.118.3 · Specific Validation for this RequestSRV 8.14.1 · CommunicationsHubStatusUpdate-InstallSuccessSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The CHF Device status is not ‘Decommissioned’.
Sources
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.120.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits the Service Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
§ 3.8.121.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits this Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
.DUIS 5.3
Service-specific validation
Documented in DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The CHF Device status is not ‘InstalledNotCommissioned’, which is the only valid status compatible with this Service Request. Note: Status of the Device for the CHF and the associated GPF will be updated to InstalledNotCommissioned if it is still in the Pending State.
Source
DUIS 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.119.3 · Specific Validation for this RequestSRV 8.14.2 · CommunicationsHubStatusUpdate-InstallNoSMWANSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The CHF SMI Status is not ‘Commissioned’. The change in logistical status of the CHF will be processed by the DCC, but no commissioned status is set according to information from the SM WAN rather than Service Requests. If the CHF SMI Status is not ‘Commissioned’ this suggests that the CHF Device has not been installed successfully.
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.113.3 · Specific Validation for this RequestSRV 8.14.1 · CommunicationsHubStatusUpdate-InstallSuccessSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verily that the User, in the User Role defined in the Service Request is a Eligible User for the Device”DUIS 2.0
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”DUIS 3.0, 3.1
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The CHF Device status is not ‘InstalledNotCommissioned’, which is the only valid status compatible with this Service Request.
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.114.3 · Specific Validation for this RequestSRV 8.14.2 · CommunicationsHubStatusUpdate-InstallNoSMWANSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 3.1
The CHF Device status is not ‘Decommissioned’.
Sources
DUIS 3.1
§ 3.8.115.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits the Service Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
§ 3.8.116.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Where a User with a User Role of RSA submits this Request then a specific validation check will be carried out for Response Code E5 as described in the table below.
Service-specific validation
Documented in DUIS 2.0, 3.0
The CHF Device status is not ‘Decommissioned’, which is the only valid status compatible with this Service Request.
Sources
DUIS 2.0, 3.0
§ 3.8.115.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.116.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
The CHF SMI Status is not ‘Commissioned’. The change in logistical status of the CHF will be processed by the DCC, but no commissioned status is set according to information from the SM WAN rather than Service Requests. If the CHF SMI Status is not ‘Commissioned’ this suggests that the CHF Device has not been installed successfully.
Source
DUIS 1.1
§ 3.8.105.3 · Specific Validation for this RequestSRV 8.14.1 · CommunicationsHubStatusUpdate-InstallSuccessSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
The CHF Device status is not ‘InstalledNotCommissioned’, which is the only valid status compatible with this Service Request.
Source
DUIS 1.1
§ 3.8.106.3 · Specific Validation for this RequestSRV 8.14.2 · CommunicationsHubStatusUpdate-InstallNoSMWANSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
Service-specific validation
Documented in DUIS 1.1
The CHF Device status is not ‘Decommissioned’, which is the only valid status compatible with this Service Request.
Sources
DUIS 1.1
§ 3.8.107.3 · Specific Validation for this RequestSRV 8.14.3 · CommsHubStatusUpdate-FaultReturnSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
§ 3.8.108.3 · Specific Validation for this RequestSRV 8.14.4 · CommsHubStatusUpdate-NoFaultReturnSection context
For this Request, the general Authorisation Checks as defined below shall not be carried out.
A Response Code of E4 as defined in clause 3.2.4 “Verify that the User, in the User Role defined in the Service Request is a Eligible User for the Device”
a Response Code of E5 as defined in clause 3.2.4 “Verify that the Service Request or Signed Pre-Command is applicable to the Device status”
No entry in the parsed DUIS tables.
W110101
Included in DUIS XSD versions
1.1
2.0
3.0
3.1
4.0
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details (10 table views)
Differences between views: Applicability, Description, Source references.
Service-specific validation
Documented in DUIS 5.1, 5.2, 5.3, 5.4, 5.5
Amended condition for SMETS1 Devices
Invalid conditions listed in this Update Firmware warning may relate to a SMETS1 CHF, a SMETS1 PPMID or a Smart Meter. An additional condition for listing a SMETS1 CHF or a SMETS1 PPMID in the InvalidDeviceIDList is where the DCC User submitting the Update Firmware Service Request is not the Responsible Supplier for the SMETS1 ESME which is connected to the same home area network as the SMETS1 CHF / PPMIDThe Response Code description within the InvalidDeviceIDList shall not contain the OtherRequestsInProgressList Update Firmware Warning as this is not applicable for SMETS1 Devices.
Source
DUIS 5.1, 5.2, 5.3, 5.4, 5.5
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 11.1 · UpdateFirmwareSection context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
Service-specific validation
Documented in DUIS 5.4, 5.5
The Update Firmware Warning contains between one and five lists of Device IDs for which the validation failed for each DeviceID: InvalidDeviceIDList . The DeviceID does not exist or the User is not the Meter or HCALCS Import Supplier NotCommissionedDeviceIDList. The Meter status is not ‘Commissioned’ or ‘Suspended’ or the Device is not a Meter or a HCALCS NotApplicableFirmwareDeviceIDList. The Firmware Version is not applicable to the Device OtherRequestsInProgressList. The Device already has another Firmware update request in progress.InvalidGBCSVersionList. The CHF associated with the HCALCS Device has a GBCS Version prior to v4.1,or the HCALCS Device currently has a GBCS Version that is prior to v4.1.
Source
DUIS 5.4, 5.5
§ 3.8.123.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 5.1, 5.2, 5.3
The Update Firmware Warning contains between one and five lists of Device IDs for which the validation failed for each DeviceID: InvalidDeviceIDList . The DeviceID does not exist or the User is not the Meter or HCALCS Import Supplier NotCommissionedDeviceIDList. The Meter status is not ‘Commissioned’ or ‘Suspended’ or the Device is not a Meter or a HCALCS NotApplicableFirmwareDeviceIDList. The Firmware Version is not applicable to the Device OtherRequestsInProgressList. The Device already has another Firmware update request in progress.InvalidGBCSVersionList. The CHF associated with the HCALCS Device has a GBCS Version prior to v4.1, or the HCALCS Device currently has a GBCS Version that is prior to v4.1.
Source
DUIS 5.1, 5.2, 5.3
§ 3.8.123.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 5.0
Amended condition for SMETS1 Devices
Invalid conditions listed in this Update Firmware warning may relate to a SMETS1 CHF, a SMETS1 PPMID or a Smart Meter. An additional condition for listing a SMETS1 CHF or a SMETS1 PPMID in the InvalidDeviceIDList is where the DCC User submitting the Update Firmware Service Request is not the Responsible Supplier for the SMETS1 ESME which is connected to the same home area network as the SMETS1 CHF / PPMID. The Response Code description within the InvalidDeviceIDList shall not contain the OtherRequestsInProgressList Update Firmware Warning as this is not applicable for SMETS1 Devices.
Source
DUIS 5.0
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 11.1 · UpdateFirmwareSection context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
Service-specific validation
Documented in DUIS 5.0
The Update Firmware Warning contains between one and five lists of Device IDs for which the validation failed for each DeviceID: InvalidDeviceIDList . The DeviceID does not exist or the User is not the Meter or HCALCS Import Supplier NotCommissionedDeviceIDList. The Meter status is not ‘Commissioned’ or ‘Suspended’ or the Device is not a Meter or a HCALCS NotApplicableFirmwareDeviceIDList. The Firmware Version is not applicable to the Device OtherRequestsInProgressList. The Device already has another Firmware update request in progress. InvalidGBCSVersionList. The CHF associated with the HCALCS Device has a GBCS Version prior to v4.1, or the HCALCS Device currently has a GBCS Version that is prior to v4.1.
Source
DUIS 5.0
§ 3.8.123.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 4.0
The Update Firmware Warning contains between one and three lists of Device IDs for which the validation failed for each DeviceID: InvalidDeviceIDList . The DeviceID does not exist or the User is not the Meter Import Supplier NotCommissionedDeviceIDList. The Meter status is not ‘Commissioned’ or ‘Suspended’ or the Device is not a Meter NotApplicableFirmwareDeviceIDList. The Firmware Version is not applicable to the Meter
Source
DUIS 4.0
§ 3.8.123.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 3.0, 4.0
Amended condition for SMETS1 Devices
Invalid conditions listed in this Update Firmware warning may relate to a SMETS1 CHF, a SMETS1 PPMID or a Smart Meter. An additional condition for listing a SMETS1 CHF or a SMETS1 PPMID in the InvalidDeviceIDList is where the DCC User submitting the Update Firmware Service Request is not the Responsible Supplier for the SMETS1 ESME which is connected to the same home area network as the SMETS1 CHF / PPMID.
Source
DUIS 3.0, 4.0
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 11.1 · UpdateFirmwareSection context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
Service-specific validation
Documented in DUIS 2.0, 3.0, 3.1
The Update Firmware Warning contains between one and three lists of Device IDs for which the validation failed for each DeviceID: InvalidDeviceIDList . The DeviceID does not exist or the User is not the Meter Import Supplier NotCommissionedDeviceIDList. The Meter status is not ‘Commissioned’ or ‘Suspended’ or the Device is not a Meter NotApplicableFirmwareDeviceIDList. The Firmware Version is not applicable to the Meter
Source
DUIS 2.0, 3.0, 3.1
§ 3.8.118.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
Service-specific validation
Documented in DUIS 3.1
Amended condition for SMETS1 Devices
Invalid conditions listed in this Update Firmware warning may relate to a SMETS1 CHF. a SMETS1 PPMID or a Smart Meter. An additional condition for listing a SMETS1 CHF or a SMETS1 PPMID in the InvalidDeviceIDList is where the DCC User submitting the Update Firmware Service Request is not the Responsible Supplier for the SMETS1 ESME which is connected to the same home area network as the SMETS1 CHF / PPMID.
Source
DUIS 3.1
§ 1.4.6 · Table 2 : Additional or Alternative Validation Conditions for SMETS1 DevicesSRV 11.1 · UpdateFirmwareSection context
In relation to SMETS1 Service Requests, the DCC shall apply the additional or alternative validation in this clause 1.4.6, additionally or as alternatives to the “Specific Validation for this Request” specified in clause 3.8.
Service-specific validation
Documented in DUIS 1.1
The Update Firmware Warning contains between one and three lists of Device IDs for which the validation failed for each DeviceID: InvalidDeviceIDList . The DeviceID does not exist or the User is not the Meter registered Import Supplier NotCommissionedDeviceIDList. The Meter status is not ‘Commissioned’ or ‘Suspended’ or the Device is not a Meter NotApplicableFirmwareDeviceIDList. The Firmware Version is not applicable to the Meter
Source
DUIS 1.1
§ 3.8.110.3 · Specific Validation for this RequestSRV 11.1 · UpdateFirmwareSection context
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’
No entry in the parsed DUIS tables.
W110401
Included in DUIS XSD versions
5.0
5.1
5.2
5.3
5.4
5.5
DUIS table details
Service-specific validation
Documented in DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
The Update Firmware Warning contains between one and five lists of Device IDs for which the validation failed for each DeviceID: InvalidDeviceIDList . The DeviceID does not exist or the User is not the Import Supplier or Gas Supplier for a Meter connected to the same HAN as the PPMID. NotCommissionedDeviceIDList. The PPMID status is not ‘Commissioned’ or ‘Suspended’ or the Device is not a PPMID NotApplicableFirmwareDeviceIDList. The Firmware Version is not applicable to the PPMID OtherRequestsInProgressList. The PPMID already has another Firmware update request in progress. InvalidGBCSVersionList. The CHF associated with the PPMID Device has a GBCS Version prior to v4.1.
Source
DUIS 5.0, 5.1, 5.2, 5.3, 5.4, 5.5
§ 3.8.126.3 · Specific Validation for this RequestSRV 11.4 · UpdatePPMIDFirmwareSection context
See clause 3.2.5 for general validation applied to all Requests.
For this Service Request and as an exception, the Authorisation Check associated to E5 allows the Device’s SMI Status to be ‘Suspended’