On Friday 18th May, we circulated an update on a DCC DSP issue that is blocking Certified Product List (CPL) updates where GBCS v1.1 is referenced in the submission. We highlighted that a DCC fix would not be in place until mid-June 2018 (the completion date of the fix development expected to be 12th June 2018, with deployment date on or before 22nd June 2018). The update also noted that in light of the timings of the fix, that the Panel would be considering any interim steps in advance of the fix being deployed.
On 25th May 2018, the SEC Panel considered the attached paper and in particular the way forward for:
- the blocked GBCSv1.1 CPL submissions that cannot be loaded; and
- an approach for existing active CPL entries that reference GBCS v1.0 (that stopped being in effect on 7th May 2018).
Details of the Panel considerations and agreed way forward are set out below:
Blocked GBCS v1.1 CPL submissions
The Panel were asked to consider two options:
- Option A: Complaint with SEC Requirements
Follow the existing SEC requirements, valid CPL submissions that reference GBCS v1.1 would continue to be processed. The existing entries and subsequent entries that reference GBCS v1.1 would be buffered until the DCC DSP fix is deployed. Parties would be advised that those new entries while on the published CPL list, have not been uploaded into the DCC DSP Systems. This approach does not involve subsequent actions by Suppliers/manufacturers to correct amended entries, as the submission will remain in line with the SEC requirements and active version of GBCS v1.1.
- Option B: Deploy a workaround interim approach (until the DCC DSP fix is in place).
Between now and the deployment of the fix, on or before 22nd June 2018, SECAS will amend references to GBCS v1.1, in existing and subsequent CPL submissions, to reference GBCS v1.0. This will enable the new CPL entries to pass the DCC DSP validation that is applied to the GBCS version field within the DCC DSP systems. This approach would involve subsequent actions by Suppliers/manufactures to correct the entries, where the reference to GBSC 1.1 is changed to GBCS v1.0, back to GBCS v1.1 as part of a future (firmware) update to the device.
The full details of the two options, with associated pros, cons and risks can be found within the Panel paper. Having consider the two options, the Panel agreed to proceed with Option A.
SECAS will continue to process valid CPL submissions (that reference the active GBCS v1.1) and keep affected parties informed that whilst the submissions are on the published CPL that they have not be uploaded into the DCC DSP Systems and Smart Metering Inventory.
Following the deployment of the DCC DSP fix, the CPL with all the buffered entries that reference GBCS v1.1 will be provided to the DCC for upload. Subject to a successful upload a confirmation notification will be provided to all interested parties that the devices have been successfully loaded. All subsequent submissions would be processed and upload per the SEC defined timescales including the DCC action to upload the amended CPL into its systems within 24hrs of being notified of an update by SECAS.
Existing CPL entries that reference GBCS v1.0
The existing active entries in the CPL reference GBCS v1.0. As noted within the attached paper GBSC v1.0 stopped being a valid version of GBCS on 7th May and was fully replaced by GBSC v1.1 following a six month transition period, where both were active.
The Panel were asked to consider what to do with these CPL entries, while recognising any Supplier/device manufacturer activities would not have been able to update the entries (alongside a firmware) update to reference GBCS v1.1 due to the DCC DSP validation blocking issue.
The Panel agreed to defer agreeing the recommendation, requesting SECAS and the DCC to provide clarity on the requirements associated with Technical Specification Applicability and its implications. This will help inform a Panel decision on the matter at its June 2018 Panel meeting.
The details of this approach will also be included on the CPL page shortly.
If you have any question on the matters above, please email firstname.lastname@example.org.