1. Operations and Release Working Group
11 June 2019
Stephen J Winnie

2. Agenda 1. Tea and coffee All 09:30-10:00 2. Welcome and introduction
Item
Description
Who
Time 1.
Tea and coffee
All
09:30-10:00 2.
Welcome and introduction
Objectives for the day
Stephen Winnie
10:00-10:15 3.
MOSL updates
Release Schedule
8.5 Release schedule
Maintenance Schedule 2019
10:15-11:30
Break
11:30 – 11:45 4.
Workshop
Data issues
Syntax errors
ID violations
Duplicate message requests
11:45 – 12:30
Lunch
12:30-13:15 5.
NCC Status
TP issues
Test Data purge development
Test Data Reload specs
13:15–14:30 6.
AOB and Wrap up.
Meeting Close.
14:30 – 15:00

3. Release Management

4. Release Management – R6.0 CPW025 TCORRs to be applied to DEREG SPIDs
CPW038 Tariff Report Updates – standing data
CPW040 NAPS report extension – columns for submitted transactions
CPW042/DCP005 Reads MDS - add reread flag
CPW053 – MO Transaction processing and reporting – non CMOS affecting
Functionality scope declared and confirmed
Panel recommendation on WRC content confirmed 31 July 2018
Ofwat approval of CPW content 30 September 2018
MPS_2 deployment 19 April 2019 for TP testing
TP testing to complete 10 May 2019 (plus one week Contingency)
Deploy to PRD 17 May 2019

5. Release Management – R6.5
CPW047/DCP006: Meter Networks for SWR/TE WHL.
Sub-Meter Owner to set up Networks.
CPW050 / DCP011 / PIP011 - Long Unread meter report updates
add columns to report to show last no-G read (UU).
T125/TCORR125
Improvements to Validation rules for T125/TCORR125 to allow update/amend of existing Calc Discharges. ALM refs: 637; 640; 642; 655; 734
CPW057 
Improving the Transparency of Guarantee Credit Arrangements 
CPM014
DCP016 
Early deployment of CPW047 requested by Panel, then CPW050 requested
MPS_2 deployment 28 June 2019 for TP testing
TP testing to complete 19 July 2019 (plus one week Contingency)
Deploy to PRD 26 July 2019

6. Release Management – R7.0 NCC003 - EFD of the Deregistration on LVI
NCC004 - EFD of the Vacancy on LVI
NCC005 - ETD of the SC on LVI
CPW056 / DCP018 / PIP004 - SPD Cascade Erasure
Non CMOS changes
Panel recommendation on WRC content confirmed 28 February 2019
Ofwat approval of CPW content 30 April 2019
MPS_2 deployment 04 October 2019 for TP testing
TP testing to complete 25 October 2019 (plus one week Contingency)
Deploy to PRD 08 November 2019 (moved to avoid Settlement runs)
DCP019 - Amendments to the provision of credit assessment score evaluation for the purposes of unsecured credit allowance
DCP020 - Unsecured Credit Allowance based on Payment history
CPM015
CPM016

7. Release Management – R8.0
CPW065 / DCP024 / PIP008 - Notifications for Retailers prior to T103.R submission
DCP024 / PIP008 data initialisation
Panel recommendation on WRC content confirmed 31 July 2019
Ofwat approval of CPW content 30 September 2019
MPS_2 deployment 17 April 2020 for TP testing
TP testing to complete 08 May 2020 (plus one week Contingency)
Deploy to PRD 15 May 2020

8. Industry Consultation – Release Schedule
Panel – Requested Consultation on appropriate number of releases PA as Panel would like to see changes implemented faster.
Currently two major release PA – Spring and Autumn
Does Industry have desire for more releases PA?
Does Industry have capability for more releases PA?
What times in year are suitable for releases?
What lead times are appropriate for each release?
Consultation from Monday 18 February to 1 March 2019
Results overall were to retain Status Quo but we saw a desire for additional releases so the recommendation was to add a Minor Release in Summer.
Propose July or August.

9. Release Management – R8.5
Panel recommendation on WRC content confirmed 10 December 2019
Ofwat approval of CPW content 28 February 2020
MPS_2 deployment 31 July 2020 for TP testing
TP testing to complete 21 August 2020 (with one week Contingency)
Deploy to PRD 28 August 2020

10. Release Management – R9.0
Panel recommendation on WRC content confirmed 28 February 2020
Ofwat approval of CPW content 01 May 2020
MPS_2 deployment 02 October 2020 for TP testing
TP testing to complete 23 October 2020 (with one week Contingency)
Deploy to PRD 6 November 2020 (avoid Settlement runs)

11. Systems Code versions System Version as from date PRD 6.0.3(42071)
17/05/2019
MPS
21/05/2019
MPS_2
15/05/2019

12. RF – Plan

13. RF Settlement run Required to run backlog of RF in sequence
March 2017, April 2017, May 2917 etc
Panel recommended to delay the double running – March has one RF, then 2 per month starting in April.
First run of March 2017 period processed. Delay in publication
Follow up of second run of March 2017 period due 27 February to allow correction of any inaccuracies etc
April 2017 period and beyond is being run as per the plan.

14. RF Settlement run
Invoice period
Month RF run originally due to be run in
Month RF run to be run in
Proposed G read execution date
Proposed RF execution date
Proposed RF publication date
Apr-17
September
March
May-17
October
April 2019
Jun-17
November
Jul-17
December
May 2019
Aug-17
January
Sep-17
February
June 2019
Oct-17
March has one RF, then 2 per month starting in April.

15. RF Settlement run Nov-17 April 2019 July 2019 02-07-19 03-07-19
Dec-17
May 2019
Jan-18
June 2019
August 2019
Feb-18
Mar-18
September
Apr-18
May-18
October

16. RF Settlement runs – G Reads
RF Period
Dec-16
Jan-17
Feb-17
Mar-17
Apr-17
May-17
Jun-17
Jul-17
Aug-17
Sep-17
Read-Date
01/04/2017 rerun
Oct-17
Estimated
175,000
188,000
123,000
131,000
120,000
Created
141,837
149,936
157,769
107,972
90,429
110,977
109,710
117,540
121,081
126,898
131,052
G Reads removed by TPs as at end of each month
Jan-19
Feb-19
Mar-19
Apr-19
May-19
Removed 1
24219
802
654
1246

17. Maintenance Schedule 2019 Published on MOSL website
Quarterly
January
April
** 19th & 22nd Bank Holiday **
Tuesday 22/01/2019
Tuesday 16/04/2019
PRE PROD
Saturday 09/02/2019
Saturday 27/04/2019
PROD
July
October
Tuesday 16/07/2019
Tuesday 12/10/2019
Saturday 27/07/2018
Saturday 23/11/2019
Tuesday 21/01/2020
Saturday 08/02/2020
Published on MOSL website
CMOS/Training/MOSL Guidance
Additional PRD outage 15th June

18. Break

19. Workshop – Data issues

20. TP Data Issues Transaction syntax errors
T132.R – SIC code not included in the transaction
ID violations - multiple use of Data Transaction Reference Numbers

21. Non Code Change (NCC)

22. NCC Process Non-Code Change Process
Allows changes to CMOS or MOSL systems to be requested and considered
Sharepoint location for submitting change requests
MOSL EXTRANET / Non Code change Requests tracker
ed confirmations of receipt
Tracker Form of status
Run consultations as per Code change CPs
Submit to Panel if/when funding is required

23. NCC Tracker ID Request title Date submitted NCC Ref Category
Trading party submitted
Describe the issue
Priority
Assigned to
Status
Target Release 10
OPS Statistics upload and reporting
26/04/2019
NCC010
MVI
MOSL
A new set of OPS standards were defined by Panel and the MO portal has been modified to permit the upload of the new metrics. The MO Portal will also report on the results
High
Digital Initiatives
Open
1.2 9
Registration history
11/04/2019
NCC009
LVI
Business Stream
Identifying previous retailer of a SPID in the CMOS LVI is difficult and requires accessing earlier ‘warehoused’ cuts from the Meter Data set or contacting the relevant wholesaler This causes daily frustration and additional working time for colleagues looking to review the ‘stewardship’ of a SPID and/or plan a data correction At the moment the T108 transaction is noted in the Supply Point History, this view does provide the relevant RSD however it doesn’t show the previous LP. In certain circumstances we might seek to progress a data correction which extends beyond our period of stewardship and in order to discuss such a proposal we must be able to identify the relevant trading parties Having to request this information from our Corporate Reporting team or the relevant Wholesaler is unnecessarily delaying resolution of customer issues. The proposal is to add Trading Party column to the table within Supply Point History on CMOS LVI, this would allow clear and quick visibility of the relevan. TP history of the SPID
Low
Review 8
MVI Peek and Dequeue extract improvements
28/12/2018
008
Portsmouth Water
The recently introduced Peek and De-Queue, Expanded Notifications are not presented in a readable or searchable form, nor are they grouped by Transaction, which obliges us to export the data into an external program. This area does not provide an improvement on the LVI Notifications Portal.
Medium 7
BTD to show only specific transaction
19/12/2018
007
When open the BTD in Business Transactions, show only the specific transaction that is subject to the drill down and not the whole Document.
cgi 6
Market Operator Portal: Segregation of Notifications by environment
10/12/2018
006
Portsmouth Water use the new MOSL Market Operator Portal, Peek and De-queue facility to receive Notifications. Both Production and MPS2 Notifications follow the same route, which is inconvenient for both business users and testers. A means of choosing between Production and other environment transactions is required.
Complete
March 2019 5
SC ETD Date column added to SC page
12/11/2018
005
BUSSTREAM-R
Tariff Code related data can easily be misinterpreted when looking at low volume interface where tariffs have been removed or at least an end date set to a date in the past, and will affect all such instances. This includes cases where Service Components were erroneously setup at market opening and have been subsequently removed. The likely consequence of this is that customers will be charged for services they are not liable for
CMOS 7.0 3
Deregistration Effective From Date
30/10/2018
003
When a SPID is Deregistered the SPID, the date from which it became Deregistered is not shown on the Core SPID screen. 4
Occupancy Status Effective from Date
004
The Effective From date of the Occupancy Status (VACANT/OCCUPIED) is not shown on the Premise Core Data screen. 1
DPID History - Terminated DPIDs
16/07/2018
001
Some Trading Parties are having issues checking details at terminated DPIDs as they disappear from the LVI screen once terminated. · The proposal from some TEIC members is that DPIDs should have an „Effective From Date‟ and „Effective To Date‟ on the portal, so it‟s easily distinguishable from a glance whether a DPID has been terminated or is active. · The EFD and ETD being displayed on the screen would be similar to how meters are currently displayed. · Additionally, as DPIDs can also be discontinued, it‟d be useful to have a „DPID Status‟ field somewhere on the LVI screen, with a possible set of „Active‟, „Discontinued‟ and „Terminated‟.
CMOS 5.0 2
DPID History - Terminated Calculated Discharges
002
Some Trading Parties are having difficulties with Calculated Discharges as the LVI screen doesn‟t distinguish between active and discontinued Calculated Discharges. They state that they can only see the discontinuation if they go into the BTD. · The proposal from TEIC members is that the LVI DPID screen has some way of managing the status of Calculated Discharges; perhaps, again, by having an „Effective To Date‟ in the Calculated Discharges section. There‟s currently an „Effective From Date‟ already there, so would make sense to have the other effective date.

24. NCC Process Non-Code Change Process - status
Two completed and deployed in CMOS 5.0
LVI screen changes for DPID and Calculated Discharges
Three approved for development
LVI screen changes for SC, Vacancy, Deregistration dates
Due in CMOS 7.0
One approved for MVI
Splitting out MPS_2 and PRD transaction reporting
Deployed 7 April 2019
One under review by CGI
BTD review of XML display
One under review by MOSL
MVI translation of XML into excel report

25. TP Question / Issues Service Component data and Transactions
Service Component data and Transactions
T143 updates do not show the EFD on the LVI screen.
Appear to retain the original SC EFD. Review the ALM Ticket
Appear to only update within the original SC EFD an ETD and cannot extend forward beyond the ETD of the original SC value
Tariff File
Where are changes shown? – CSD0302
Historic Tariffs are not shown on the report
Review the ALM ticket
Cascade Erasure
Will the SPID Erase also erase the meter network associations?
No the network association must still be torn down manually – as with Meter Erasure process – before the Erasure will be accepted.

26. Lunch

27. Test System Management
In total 20 Responses were received.;
14 wholesalers
6 Retailers
5 Trading Parties preferred option 1  (Trading Parties to create new test data by transaction flow using HVI/LVI/MVI)
8 Trading Parties preferred option 2  (Trading Parties to supply new test data to MOSL in a format to be confirmed and for MOSL to load the test data into the test systems)
7 Trading parties preferred option 3  (An extract taken from Production CMOS by MOSL, based upon a set of nominated SPIDs (by Trading Party) that would be applied to the test systems by MOSL.  Data to be anonymised by Trading Party transactional flows)
As such Option 2 was selected. However due to the small margin MOSL will develop a simple extract (based on SPID) process that will feed into the Upload solution. The purge process will be deferred to prior to Release 7
Expect Specifications for data load to be issued by end of June 2019

28. Test System data load Budget for data load – 20,000 SPIDs
Develop in line for CMOS 7.0
File based update – Spreadsheet format
Premise
SPID
Service Component
Meter (including network associations)
DPID
Meter/DPID
Meter Reads
Two principles
Can provide data set to MOSL
Can provide a SPID list and EFD and MOSL will extract from PRD and load. TP must then anonymise it.

29. Test System Management - Costs
Description
Dev/test cost
Op cost
Data Loader development and test
£ ,338
Ongoing Maintenance of the Data Loader
£ ,000
Purge process development
£ ,000
Purge process running (est 2 PA)
£ ,000
total PA
£ ,338
£ ,000
£ ,338
SPID extract c £10K additional

30. ORWG
ORWG Meetings
Move to every two months, alternating with User Forum
13 August 2019
CMOS Operations Calls
Weekly during 6.5 and 7.0 testing phases – Wednesday at 16:00hrs

31. Close