dsc delivery sub-group · (tbc) 08/08/18 secondary scope scoping initiation delivery realisation...
TRANSCRIPT
Agenda Defect Dashboard
UPD Address Dataset
UNC Validation Roles
Information on defects Change of Class defect
Defect 933
Release 2 update R2 Dashboard
Release 2 – Project Status Update
XRN249 – Data Migration Plan – Approve plan for ChMC to approve Implementation Plan in May 18
meeting.
XRN4361 – Final DSG approval for the R2 Implementation Plan (Option 1) – Clarification on the file
processing date/times
XRN4449 – Customer Testing
Release 3 update R3 Dashboard
CSEPs variance XRN update.
R3 Design Engagement (cont’d)
Market Breaker CP update
Release 3 CP representation overview
Release 3 Plan update including MT timelines and recommendation
Agenda (Continued)
Documentation Changes – February 2019 release
New Changes for Prioritisation Ratification.
Actions
AOB XRN4667A – Provision of Formula Year AQ/SOQ to Proposing User
Negative Consumption within the AQ Calculation
ADDRS Dataset Change
• Need for change driven by ‘Irrelevant Dataset’ functionality
• At RGMA Implementation – July 2004 – Transco GT were instructed to accept a
generic ONUPD flow
• including datasets that were not relevant at all
• Including datasets provided in a context not relevant to the GT
• As a consequence the UPD GT Hierarchy was different from the ONUPD
hierarchy
• Issue identified in Market Trials – presence of ADDRS dataset was causing
rejection of UPD as Irrelevant Dataset principle was not observed initially
ONUPD RGMA Hierarchy (including Irrelevant Datasets)
Key:
Notify Update
Metering Details
Header TrailerH T
Mandatory data
set
Optional
data set
o
Name
Asset
o1.2.2.5
1.2.2
Register
Details
o1.2.2.3
Address
O
O
Transaction
1
= Site Address
Market
Participant
o1.2.2.4
= Asset Provider
Name
Contact
Mechanism
o1.1.1
1.1.1.1 o
1.1
Meter1.2.2.1 o
Converter1.2.2.2 o
Address Contact
Mechanism
o1.2.3.1 1.2.3.2 o Care
Details
1.2.3.3
= Customer
= Contact
Meter Point1.2
Appointmento1.2.2.6
Readingo1.2.2.431
Nameo1.2.3
o
= MAM
= Unattached Asset Location
= Asset Provider
= MAM
Address
o1.2.2.5.1
Contact
Mechanism
o1.2.2.5.2
Address1.2.1
= Meter Point Address
O
Key:
Notify Update
Metering Details
Header TrailerH T
Mandatory
data set
Optional
data set
o
Name
Asset
o1.2.2.5
1.2.2
Register
Details
o1.2.2.3
Address
O
O
Transaction
1
= Site Address
Market
Participant
o1.2.2.4
= Asset Provider
Name
Contact
Mechanism
o1.1.1
1.1.1.1 o
1.1
Meter1.2.2.1 o
Converter1.2.2.2 o
Address Contact
Mechanism
o1.2.3.1 1.2.3.2 o Care
Details
1.2.3.3
= Customer
= Contact
Meter Point1.2
Appointmento1.2.2.6
Readingo1.2.2.431
Nameo1.2.3
o
= MAM
= Unattached Asset Location
= Asset Provider
= MAM
Address
o1.2.2.5.1
Contact
Mechanism
o1.2.2.5.2
Address1.2.1
= Meter Point Address
O
ONUPD RGMA Hierarchy – showing annotation
Proposed UPD Hierarchy
REGISTER
DETAILS
METER POINT
ASSET
SYSTEM USER TO CDSP
Notify Metering Details ONUPD for Asset Updates or Found, Removed or Missing Assets
Mandatory
Optional
TRANSACTION
METER POINT
ASSET
=Reported
=Installed
=Removed
REGISTER
DETAILS
=Asset Provider
File Type: UPD Version 5FA
Issued 16.04.18
Implementation Release 3
HEADER
NOTIFY UPDATE
METERING
DETAILS
TRAILER
READING
APPOINTMENT
METER
MARKET
PARTICIPANT
CONVERTER
ADDRS
DSG Views Sought….
• Change needs to REMOVE ADDRS dataset from UPD File Format (there is no
context in which it is relevant)
• Proposal to amend annotation to explicitly show irrelevant datasets in hierarchy,
so that these are explicitly shown – this will include:
• NAME
• CONTACT MECHANISM
• CARE DETAILS
• This is not a functional change for Xoserve
• Shipper User views?
• Assessment that no other Users are impacted – is this correct?
• Same principle will be applied to JOB
ONJOB RGMA Hierarchy – showing annotation
Key:
Notify Metering Job
Header Trailer
Meter Point
Asset
Register
Details
Reading
o
1.1
H T
1.1.1
1.1.1.3
1.1.1.3.1 Mandatory data set
Optional data set
= installed
= removed
o
Transaction 1
Address
1.3.1 o
= Meter Worker = Requestor
Market
Participant
1.4 o
Name 1.3 o
Meter 1.1.1.1
Converter 1.1.1.2
= reported
o o Market
Participant
o 1.1.1.4
= Asset Provider
Name o 1.1.1.5
= Meter Worker
Contact
Mechanism
1.3.2 o
o
= Asset Provider
Address
o 1.1.1.5.1
Contact
Mechanism
o 1.1.1.5.2
Appointment
1.2 o
= Job Completed Date
14
Gas Meter Reads
Update on proposed changes to Outer Tolerance Levels
Summary: The original inner and outer tolerance ranges were based on a best
estimate of what the market believed to be appropriate. Post Nexus Go Live we are
seeing a number of “valid” reads failing to pass the outer tolerance check. This has a
consequential impact on a number of other processes
Latest Updates:
Xoserve don’t have full picture as reads are filtered
by Shippers i.e. reads we know would be rejected
are not sent in to Xoserve
Outer tolerance range was a best guess at Go Live
Analysis of filtered “valid” reads undertaken &
suggested changes to tolerances set out
The revised “Proposed” tolerances will allow
large numbers valid reads to be submitted
Should be a quick and easy change
Band Current Suggested Proposed
1 No Change No change
2 25,001 55,001 55,001
3 10,001 20,001 55,001
4 5,001 20,001 25,001
5 2,001 6,001 7,001
6 501 1,001 1,801
7 401 701 701
8 601 1,001 1,101
9 551 901 901
10 501 1,001 1,001
11 451 701 701
XRN4361 – UK Link Release 2 - Delivery
19th April 2018 Overall Project RAG Status G
Plan/Time Risks and Issues Cost Resources
RAG Status G G G G
Status Explanation
Objective Full project delivery of UK Link Future Release 2 Scope
Plan/Time
• User acceptance testing currently tracking to plan (9 CRs have been signed off), XRN4449 and XRN4249 are tracking 5 days
behind plan however analysis indicates no impact to the overall UAT Completion milestone of 18th May
• Performance testing is scheduled to begin on 30th April
• Clarification on the R2 Implementation approach/plan to be provided at the DSG on 23rd April and approved by ChMC at the
May meeting
• R2 Customer Training plan has been updated with the delivery dates and it will be discussed in DSG on 23rd April
Primary Scope (PS) Update • XRN4449 (Priority Services Code - PSR)
• Xoserve are engaging with individual participants to ensure that the testing process is clear and to answer any questions
• There 3 Shippers, 3 Networks and 3 iGT’s participating in the testing of this change
Secondary Scope (SS) Update • The build is complete for XRN4316
• System and Acceptance testing phases have been merged
• XRN4249 – Address Management • The code implementation was agreed in ChMC and the reps were received on the data migration plan
• Based on the reps received the data migration options to be discussed and agreed in DSG on 23rd April
Risks &
Issues • All risks are under control. The nearest term risk is the completion of Acceptance Testing which is currently low.
Cost • Project delivery costs are tracking to approved budgets
Resources • Weekly monitoring of SME resources supporting multiple demands (e.g. Future Releases, UIG etc) and all requirements are
able to be met
UK Link Release 2 - Plan
Primary
Scope Scoping Initiation Delivery Realisation
Stage Scope
Prioritisation
Scope
Defined Funding Initiation
Analysis
and HLD
Detailed
Design Build
Acceptance
Test
Performance
Test
Regression
Test Imp. PIS
Baseline
Plan 07/06/17 25/07/17 09/08/17 Aug 17 Aug 17 20/11/17 29/01/18 18/05/18 18/05/18 22/06/18
29/06/18
(TBC) 30/07/18
Current Plan 07/06/17 11/10/17 10/01/18 13/12/17 16/01/18 29/01/18
(12/01/18) 16/02/18 18/05/18 18/05/18 22/06/18
29/06/18
(TBC) 08/08/18
Secondary
Scope Scoping Initiation Delivery Realisation
Stage Scope
Prioritisation
Scope
Defined Funding Initiation
Analysis
and HLD
Detailed
Design Build
Acceptance
Test
Performance
Test
Regression
Test Imp. PIS
Baseline
Plan 07/06/17 25/07/17 07/02/18 NA NA 09/02/18 09/03/18 18/05/18 18/05/18 22/06/18
29/06/18
(TBC) 30/07/18
Current Plan 07/06/17 27/11/17 07/02/18 NA NA 16/02/18
09/03/18
09/03/18
30/03/18
06/04/18
18/05/18 18/05/18 22/06/18 29/06/18
(TBC) 08/08/18
RAG Key – Milestones are end dates:
Milestone date forecast to be missed Milestone date forecast to be at risk Milestone date forecast to be met Milestone completed Planning/Milestone date to be confirmed
Actions
Action 1 : Shipper organisations who are participating in the
industry testing need to provide key contact details, for
communications to be issued directly.
Xoserve will be contacting the individual participants to ensure that we
have the details before the testing commences
Action 2 : Implementation plan - LC to confirm the rejection
code per file type.
If files are submitted after the cut off mentioned in the file format
transition plan capturing the last inbound old file format, it will be
rejected as a file level rejection (ERR rejection)
Action 3 : Implementation plan - LC to clearly advise timings
in the lower level implementation plans.
The timings mentioned in the file formats transition plan in Appendix A
refers to the processing times of the files
Decision Required – XRN4249 Migration Plan Approval
Background
• October 2017 ChMC agreed a [target] R2 implementation of 29th June 2018
• Assessment has identified that 2 CRs in scope of R2 will require data cleansing /migration
activities to be completed (XRN4449 & XRN3283)
• Due to the scale of data migration activities ([2] days) it is recommended that these are
completed during non business days. This removes risk to core business processes (e.g. June
18 Capacity invoice) and allows downstream GT portfolio files to be provided
• Further, it has been identified that there are electricity related changes being implemented on
28th June 2018 and therefore Xoserve has been tasked to consider the option of combining the
electricity change implementation along with R2 on 28th June 2018
Implementation Options Considered
OPTION PROS CONS
Option 1:
Deploy as per agreed
R2 date (Imp
commences at the end
of the business day on
the 29th June 2018
over the weekend of
30th June & 01st July)
1. Aligned to approved Imp dates for R2 CRs
2. Avoids operational impacts as the Release will
be implemented during non-business hours
(maintenance windows)
3. Ensures that data cleansing/migration activities
allow full GT Portfolio files to be created and
submitted over the weekend
4. No CDSP outage required, file processing
updates will follow BAU batch processes
1. Need to gain industry agreement since this is not
aligned to the agreed R2 imp date of 29th June 2018
2. Possible challenges for Shippers to manage the
deployments for Electricity and Gas June 18 changes
during different implementation windows
Option 2:
Deploy R2 on 29th
June 2018 within the
scheduled
maintenance window
1. Aligns to agreed R2 implementation date
1. Imp activities would continue during business hours
and may cause operational impacts (e.g.
performance)
2. Data migration will extend beyond the maintenance
window and may impact on BAU processes
Option 3:
Deploy on 28th June
2018 to align to
Electricity release
1. Aligns to a June 18 implementation for
Electricity and Gas changes for Shippers
1. Does not align to the agreed ChMC R2 date of 29th
June 2018
2. Implementation activities would continue during
business hours and may cause operational impacts
to BAU processes (e.g. performance)
Option 1 File Formats – Input Files Transition Plan
Change ID Last inbound in Old File
Format
XRN4303
(UKLP267)
29/06/2018 - SFN – 20:00PM
XRN3283 29/06/2018 - ACR – 17:00PM
XRN4449
(UKLP273)
29/06/2018 - CNC – 18:00PM
29/06/2018 - CNF – 23:45PM
As the implementation is on 30th June all files in the old file format will be processed by
11:59PM on 29th June 2018
Any files submitted from 30th June 00:00AM should be submitted in the new file format. These
files will be held in AMT and processed only after the after implementation is completed on 01st
July 2018
Any files received in the old file format (eg post the below date/times) after R2 implementation
is complete on 01st July will be rejected
The detail of the file processing times will shared in the lower level cutover/implementation plan
Option 1 File Formats – All impacted File Formats Transition Plan
Note: This table aligns to Option 1 and based on the chosen option this may have to be revisited.
Full details will be defined in the lower level cutover/implementation plan
Change ID Last inbound in Old
File Format (Time =
File Processing)
Last Outbound in Old File
Format
(Time = File Processing)
First Inbound in New File
Format
(Time = File Processing)
First outbound processed in New File
format
(Time = File Processing)
XRN3477
(UKLP112)
NA 29/06/2018
AES – 23:30PM
NA 02/07/2018
AES – 23:30PM
XRN4303
(UKLP267)
29/06/2018
SFN – 20:00PM
29/06/2018
SFR will be processed as usual
as there is no file format change
30/06/2018
SFN – 20:00PM
(Files will be held and
processed on 01/07/18)
01/07/2018
SFR will be processed as usual as there is
no file format change
XRN3283 29/06/2018
ACR – 17:00PM
29/06/2018
ARS will be processed as usual
as there is no file format change
02/07/2018
ACR – 8:00AM
02/07/2018
ARS will be processed as usual as there is
no file format change
XRN4449
(UKLP273)
29/06/2018
CNC – 18:00PM
CNF – 23:45PM
29/06/2018
CNR and CFR will be processed
depending on the batch job
execution but will be completed
by 23:59PM
30/06/2018
IDL – 10:00AM
EDL – 06:00AM
EWS – 06:00AM
02/07/2018
CNC – 18:00PM
CNF – 11:00AM
02/07/2018
CFR – 12:15PM
CNR – 18:00PM
Refresh of Portfolio Files (EQL & EWS) –
17:00PM
01/07/18
IDL – 10:00AM
EDL – 06:00AM
EWS – 06:00AM
Introduction/Problem Statement
Change XRN4249 is part of the scope of changes planned to be implemented as part of UK
Link Release 2 on the 29th June 2018.
Following analysis of this change, discussion was held with Customers at both ChMC and
DSG. Concerns were raised around the migration of the PAF updates from when the process
was suspended in April 2017. These concerns relate to the volume of updates required over
the period April 17 through to June 18 that could have a downstream impact to Customer
systems and business processes.
To minimise the impact of loading all retrospective PAF updates from April 2017, Xoserve are
recommending a staggered approach to migrate the data over a number of weekends. This
would have checkpoints built into the plan to review the process and agree the volume of
updates to be loaded on the next planned date. This approach is expected to reduce the
impacts to Customer systems and business processes.
Data Migration Plan
No Activity Start Date End Date
1 Code Deployment as part of R2 Cutover/Implementation 30/06/2018 01/07/2018
2 Initial 10K Load 07/07/2018 07/07/2018
3 NAC File / Portfolio Files / Daily Delta on the back of the initial 10K address update 08/07/2018 08/07/2018
4 Data Load to SAP BW 09/07/2018 09/07/2018
5 Agreement with Shippers to load safe volume (100k) records into SAP ISU (BW?) 09/07/2018 13/07/2018
5 Load the safe volume (100k) records 14/07/2018 14/07/2018
6 NAC File / Portfolio Files / Daily Delta on the back of the initial safe volume (100K) address
update
15/07/2018 15/07/2018
7 Daily Load to SAP BW 16/07/2018 16/07/2018
8 Agreement with Shippers to load the next set of safe volume records (100k) into SA 16/07/2018 20/07/2018
9 Load the 2nd set of safe volume (100K) records into SAP ISU 21/07/2018 21/07/2018
10 NAC File / Portfolio Files / Daily Delta on the back of the 2nd set of safe volume (100K)
address update
22/07/2018 22/07/2018
11 Agreement with Shippers to load the remaining updates (approx. 40K) 23/07/2018 27/07/2018
12 GB places the first Regular PAF file received 28/07/2018 28/07/2018
13 Load the remaining updates (approx. 40K) into SAP ISU 28/07/2018 28/07/2018
14 NAC File / Portfolio File / Daily Delta on the back of the remaining (approx. 40K) address
updates
29/07/2018 29/07/2018
15 Daily Load to SAP BW 30/07/2018 30/07/2018
16 PO Team to pull the first regular file from GB Mailing shared area 01/08/2018 01/08/2018
17 First regular file load into SAP ISU (and SAP BW) - Proposed 1st production BAU run 05/08/2018 05/08/2018
18 NAC File / Daily Delta on the back of the first regular PAF file 06/08/2018 06/08/2018
Next Steps
Present options to Customers at the Delivery Sub Group on 09th April
Agree if proposed approach is acceptable to Customers
Split XRN4249 into 2 Change Packs, to agree: Implementation of the SAP ISU solution to reinstate the GB Mailing Update file process
Agreement of the proposed Data Migration Plan to apply updates from April 17 to June 18
Update the DSC ChMC Implementation Plan to reflect XRN4249 code
implementation and Data Migration Plan
Review and approve proposed Data Migration plan with ChMC on 11th April
XRN4572 – UK Link Release 3 - Design
23rd April 2018 Overall Project RAG Status G
Plan/Time Risks and Issues Cost Resources
RAG Status A G G G
Status Explanation
Objective Full project delivery of UK Link Future Release 3 Scope
Plan/Time
• Approval of BER for Full Delivery cost and scope achieved at Change Management Committee (ChMC) on 11th April.
• Design commenced on 5th March and due to conclude by first week of May (including CP approval).
• All 14 Change Packs have been published to plan for the CRs in scope of Release 3
• 4 x Change Packs published on 21st March. Representation period closed on 4th April.
• 5 x Change Packs published on 4th April. Representation period closed on 18th April.
• 2 x Change Packs published on 11th April. Representation period open until 25th April.
• 3 x Change Packs published on 16th April. Representation period open until 30th April.
• High Level Design Engagement at last DSG was well received, final session planned for 23rd April.
• Cadent & NG design overview sessions are in progress to ensure all requirements for XRN 4454 are successfully catered
for within Design.
• Initial Market Trial engagement to commence with DSG over the next 8 weeks.
• Build for Release 3 commences on 30h April as per plan.
Risks and
Issues
• XRN4431 agreement on solution at risk (dependent on Change Pack sign off).
• Notional Go Live Date dependent on Design closure and a number of plan variables e.g. Market Trials, training
requirements and cutover/implementation approach
• R3 Delivery plan has a degree of parallelism due to timescales. Risk is closely managed, plan is holding trajectory as
forecast to date.
Cost • Costs are holding approved budget
Resources • Weekly monitoring of SME resources supporting multiple demands (e.g. Future Releases)
• Currently we have SMEs booked to support all Detailed Design discussions.
UK Link Release 3 - Plan
Primary
Scope Scoping Initiation Delivery Realisation
Stage Scope
Prioritisation
Scope
Defined Funding Initiation
Analysis
and HLD
Detailed
Design Build
Acceptance
Test
Performance
Test Market Trials
Regression
Test Imp. PIS
Baseline
Plan 10/01/18 07/02/18 11/04/18 13/04/18 13/04/18 27/04/18 N/A N/A N/A N/A N/A N/A N/A
Current
Plan 10/01/8 07/02/18 11/04/18 13/12/17 13/04/18 02/05/18*
30/04/18
09/07/18 13/08/18 10/09/18 27/08/18 02/10/18 06/01/19
RAG Key – Milestones are end dates:
Milestone date forecast to be missed Milestone date forecast to be at risk Milestone date forecast to be met Milestone completed Planning/Milestone date to be confirmed
*including CP signoff
Release 3 Plan Overview
1. Release 3 Plan is based on Design outputs of 14 CRs & need date of hitting November Release.
2. All phases required to deliver Release 3 have been factored in, including Market Trials
3. Market Trials is expected to include all 14 CRs and XRN 4453 expected to be the most complex.
4. MT will be open to testing for 5 weeks including defect retests. Connectivity testing expected during MT preparation phase with all parties.
5. Integrated Dress Rehearsal also expected to be undertaken with Market parties to ensure Cutover practice and transition arrangements are practiced before Go-Live
6. Further engagement on MT and IDRs expected to occur through DSG
7. High Level MT plan agreement required to finalise plan and achieve commitment to November 2018 implementation from all parties
Mar 2018
12 19 26
Apr 2018
9 16 235
May 2018
14 21 28 4
June 2018
18
Jul 2018 Aug 2018 Sep 2018
17 242 7 11 6 10
Oct 2018
Detailed Design
13 20 27 39 162 23 8 15 221
Nov 2018
29 12 19 26
1 3 5 6 9 11 12 14 15 27 28 294 8 13 21 2622 23 2416 251917 20 32 3330 34 3718 31 35 36
Dec 2018
3 10 17 24 31
2 7 10
25 30
38 39 42 4340 4441
30 5
Build
System Testing Perf. Testing
Regression Testing IDR
IDR Prep (2
weeks)
MT Prep(5 weeks)
Market Trials (5 weeks)
CTGY
GO LIVE
Post Implementation Support
CTGYGo Live
Acceptance Testing
MT Approach
Test ScenariosMT
Planning
Training Approach
Training plan Training execution
R3.0 Scope of changes
# Change Number Change Description
1 XRN3656 Read Validation Tolerances
2 XRN4273 Installed Status of Failed MOD614
3 XRN4337 To change the optionality of the Supply Point confirmation reference for the T51 file
4 XRN4431 Reads failing market breaker tolerance to be accepted for correct date following AQ Correction
5 XRN4443 File Format Changes Aug 16 Unique Sites (deferred items from CR252)
6 XRN4453 File Format Should Have changes
7 XRN4454 DN Sales (Outbound Services) Requirements for UKLP enduring solution
8 XRN4458 Class 4 CSEPS Reconciliation Variance Identification
9 XRN4481 Resolution of penny mismatches within invoice supporting information for Core invoices.
10 XRN4486 Meter Type O = Oriffice to be an acceptable value in file formats and reports
11 XRN4495 Energy Tolerance Rejection Code
12 XRN4534 Amendment to RGMA Validation Rules for Meter Asset Installation Date
13 XRN4538 Insertion of Maximum Number of Occurrences in Meter Inspection Date Notice (MID) File
14 XRN4539 New File Level Rejection
R3 Change Summary
Direct Change Impact Process Areas
Wider Impacts considered whilst defining solution
Design Summary – XRN4273
File Format Change Process
Yes RGMA
Batch Job Reporting Requirement
No change No
Application Topology Impacted Applications
Incoming to SAP ISU Outgoing from SAP ISU
Change ID Solution / Process Changes
XRN4273
(Installed Status
of Failed
MOD614)
This change is to include a new value F (Failed IHD Asset) for this field. List out the impacted file types and configure the new value
in Market flow to avoid warning. Impacts functions in both ISU and Marketflow applications. As part of this change, new allowable
values will be introduced in ‘In Home Display Status’ of ‘F’ - ‘Failed IHD Asset’. High Level changes needed within application
outlined below:
• This changes is to Add ‘F’ as new allowable value for field IHD_INSTALL_STATUS in S98 record type .
• Impacted file types are PAC,CRS, NMR,TRS,CFR,NRF,SNR,MRI,TRF,ONJOB and ONUPD .
• Xoserve Testing is primarily around Market Flow and SAP ISU application for all Site types and classes along with unique sites
Performance Impact
Envisaged? CR Complexity
No Low
File Format Change Process
Yes Winter Consumption
Batch Job Reporting Requirement
No change No
Performance Impact
Envisaged? CR Complexity
No Medium
Change ID Solution / Process Changes
XRN4337
(To change the
optionality of the Supply
Point confirmation
reference for the T51 file)
This change is for NRL process. T51 (Winter consumption calculation failure) segment is sent to the shipper which has a
Live contract as on the file creation date and also to the incoming shipper if the confirmation status is CO. High Level
changes needed within Xoserve applications outlined below:
• Supply point confirmation reference number is a mandatory data item in this segment which impacts SPA required
process optionality needs to be changed from mandatory to optional .
• Xoserve Testing spans across SAP PO and Market flow applications. Impacted files due to the change are: JOB, UPD,
PAC (S98), CRS (S98), NMR (S98), TRS (S98), CFR (S98), NRF (S98), SNR (S98), MRI (S98), TRF (S98).
Application Topology Impacted Applications
Incoming to SAP ISU Outgoing from SAP ISU
Design Summary – XRN4337
File Format Change Process
Yes All
Batch Job Reporting Requirement
No change No
Performance Impact
Envisaged? CR Complexity
No Medium
Change ID Solution / Process Changes
XRN4453
(File Format ‘Should
Have’ changes)
This change was raised during UKLINK programme and deferred. It contains c.230 changes out of which majority are
cosmetic corrections and c.11 changes are related to functionality/format changes which form the design outlined below.
The changes include Optionality changes, adding new fields and hierarchy changes for file types like
FSI,CUN,CCN,CIN,ZCS,SFR. Changes, not limited to below, but needed to be carried out within files and application is
outlined below:
• Change IGT_PROJECT_REFERENCE filed Optionality from ’ M’ to ‘O’ in C65,C64,C67 Record type for CUN,CIN and
CCN.
• Add new filed as NWO_NAME in K29 record type for FSI file type and Optionality of field is ‘M’.
• The hierarchy Level of the I09 record to be changed from 3 to level 4 for ZCS file type .
• Hierarchy change from /Q28/K42/I09 to /Q28/K42/K80/I09
• Impacted file types are FSI, CUN, CCN, CIN, ZCS and SFR for this change.
• Xoserve Testing spans across all functionality, hierarchy and format changes.
Application Topology Impacted Applications
Incoming to SAP ISU Outgoing from SAP ISU
Design Summary – XRN4453
File Format Change Process
No SPA / Reads
Batch Job Reporting Requirement
No No
Performance Impact
Envisaged? CR Complexity
No Medium
Change ID Solution / Process Changes
XRN4458
(Class 4 CSEPS
Reconciliation Variance
Identification)
This change will introduce new rules for identification of rec variances for CSEP sites. The process will be initiated from SPA
area. While performing the meter read reconciliation or adjustments during the period for all IGT sites linked to a project,
system has to see if there is a change in either the Max AQ or Max SOQ for the concerned CSEP during the billing period. If
there is a change, all rec adjustments billing and Support information will need to consider correct time slices and applicable
rates for charging on primary and amendment invoices.
• Xoserve Testing is across CSEP Amendment, read reconciliation, adjustment billing.
Application Topology Impacted Applications
Incoming to SAP ISU Outgoing from SAP ISU
Design Summary – XRN4458
File Format Change Process
Yes Billing
Batch Job Reporting Requirement
No change No
Performance Impact
Envisaged? CR Complexity
No Medium
Change ID Solution / Process Changes
XRN4481
(Resolution of penny
mismatches within
invoice supporting
information for Core
invoices)
Penny mismatches were identified while validating the financial values within invoice supporting information against the
actual invoice values for Capacity and Commodity invoices. This change is to make necessary field level amendments in
ZCS, COM, CZI and COI files which will help to validate the thin supporting information files generated from ISU with the
SAP BW thick supporting files without any penny differences. These files are important for Billing. High Level changes
needed within Xoserve applications outlined below:
• This change is to make necessary field level amendments in ZCS, COM, CZI and COI files which will help to validate the
thin supporting information files generated from ISU with the SAP BW thick supporting files without any penny differences
• This change requires Xoserve testing in Billing, BW and integration space.
Application Topology Impacted Applications
Incoming to SAP ISU Outgoing from SAP ISU
Design Summary – XRN4481
File Format Change Process
Yes SPA
Batch Job Reporting Requirement
No change No
Performance Impact
Envisaged? CR Complexity
No Low
Change ID Solution / Process Changes
XRN4486
(Meter Type O = Orifice
to be an acceptable value
in file formats and
reports)
Current UK Link file format has following meter type values: D - Diaphragm of Unknown Material, R - Rotary, L - Leather
Diaphragm, S - Synthetic, T - Turbine, U - Ultrasonic, Z – Unknown. During migration and IDR few MPRNs were identified
with meter Type value as O (Orifice).
Change is identified in 4 SAP BW files and involves regression impacts.
New Allowable value for meter Type ‘O’ = Orifice .
Application Topology Impacted Applications
Incoming to SAP ISU Outgoing from SAP ISU
Design Summary – XRN4486
File Format Change Process
No RGMA
Batch Job Reporting Requirement
No change No
Performance Impact
Envisaged? CR Complexity
No Complex
Change ID Solution / Process Changes
XRN4534
(Amendment to RGMA
Validation Rules for
Meter Asset Installation
Date)
Currently, when an asset install comes through a ONJOB or ONUPD once the contract is live for a date prior to the contract
going live, system will allow asset installation on or after CO date (ONJOB) / LI date (ONUPD). As part of this change, the
system will be modified to allow asset install on any date provided there is no other shipper.
• This rule is applicable to both Green Field and Brown Field sites as follows:
a) If the site is green field (1st LI confirmation) and is/was not attached to any device then LI shipper can send the
device activity request for any date in the past (Not earlier to LIS date)
b) If the site is brown field and is not attached to any device then LI shipper can send the device activity request for
any date in the past but not in ownership of the last shipper provided the last shipper is different to the current LI
shipper. Device activity date cannot go beyond the last read date present in the system for the MPRN.Existing
LIS date validation applicable.
• Xoserve testing is needed from RGMA perspective and also changes related to Metering, AQ and Billing as downstream
processes
Application Topology Impacted Applications
Incoming to SAP ISU Outgoing from SAP ISU
Design Summary – XRN4534
File Format Change Process
Yes Marketflow
Batch Job Reporting Requirement
No change No
Performance Impact
Envisaged? CR Complexity
No Low
Change ID Solution / Process Changes
XRN4539
(New File Level
Rejection)
Change involved in FRJ file type, rejection code need to be added. Design to cater to all the possible scenarios.
There are certain file types where the L1 records are defined as mandatory. System expects at least one mandatory
record in the file with all valid fields. If it is not received then reject the whole file and create a FRJ response with error
code FIL00020 (No Valid Message - File contains incorrectly formatted records).
File level rejection testing is to be undertaken by Xoserve at Market flow interface.
Application Topology Impacted Applications
Incoming to SAP ISU Outgoing from SAP ISU
Design Summary – XRN4539
Recap – Design Summary for 8 Changes
# Change
Number
Impacted Process
Area Complexity
Impacts to
File Formats?
Impacts on
Exceptions?
Performance
Testing Required?
External Screen
Changes?
1 XRN4273
Marketflow, SAP PO
Low No No No No
2 XRN4337
Marketflow, SAP PO
Medium Yes No No No
3 XRN4453
Marketflow, SAP PO,
Reads
Medium Yes No No No
4 XRN4458 Reads Medium No No No No
5 XRN4481
Marketflow, SAP PO,
Billing, Invoicing,
SAP BW
Medium Yes No No No
6 XRN4486
Marketflow, SAP PO,
SPA, SAP BW
Medium Yes No No No
7 XRN4534 RGMA Complex No No No No
8 XRN4539 Marketflow Low No No No No
Glossary of Terms
# Abbreviation Description - Definition
1 ISU Industry Specific Solution for Utilities
2 RGMA Review of Gas Metering Arrangements
3 SAP PO SAP Process Orchestration
4 SAP BW SAP Business Warehouse
5 CMS Contact Management Service
6 SPA Supply Point Administration
February 2019 Release
3 implementations are proposed annually within the gas industry
In previous years these dates have been determined as ‘the Friday
following the last Thursday in February and June, and that following the
first Thursday in November’. These are aligned to SPAA release dates
Xoserve have provisioned for 2 major system releases in the budget plan
for 2018-2019 and 2019-2020 with these proposed for June and
November
However, to support additional industry change, it is proposed to
implement in February where Xoserve does not need to introduce system
changes
Current process
Following internal Xoserve agreement and ChMC approval to proceed with a change:
Evaluation
Quotation
Report (EQR)
produced
Business
Evaluation
Report (BER)
produced
Taken to
ChMC for
approval
Taken to
ChMC for
approval
Xoserve
completes
detailed
design
Change Pack is
issued with the
solution and
associated impacted
documents
• The EQR estimates the cost for the
BER to be produced
• The BER estimates the
implementation costs of the change
• Both are required for external funding
to be approved
Proposed ‘documentation only’ process
Whereby it is a documentation process change, and therefore no impact to
Xoserve, no EQR or BER is required as there is no approval for external funding
necessary
The process will be that a change proposal (CP) is raised. The CP will go through
internal Xoserve approval and ChMC approval to ensure the industry supports the
change
An Xoserve Reference Number (XRN) is assigned to the CP which is added to the
change register, this will allow participants to see the change through its lifecycle
A Change Pack will be issued to the industry that details the solution, with 6
months notice of the change; this will be approved at ChMC within the
implementation plan
Exemptions
Changes will not be considered for a documentation release
where:
Large scale testing is required i.e. market trials. Testing would be
considered on a case by case basis per each change, based on
industry requirements
There is a system impact to Xoserve
Interface impacts
6 months notice has not been given whereby Users need to make
system changes
Proposed February Release change
Currently it is proposed to introduce one change in February 2019: Ability
to Accept Extended Reading Indexes of up to 12 Characters
This was issued for early views in the Change Pack 1884.3 on 9th March
Users confirmed 6 months was required for the system changes that
needed to be implemented to support 12 character indexes
There are no system impacts for Xoserve
Further information will be issued within the Change Proposal and
Change Pack in May
Next Steps
A Change Proposal will be issued to the industry in readiness for ChMC in
May
Following approval an XRN will be assigned to the change
A Change Pack will be issued to notify the industry of the change and
invite representation comments
Users will vote to proceed at ChMC based on the representation
comments and approvals within the implementation plan
The XRN will be added onto the change register
February release will be included on the ‘Plan on a Page’ for visibility
Actions Title Meeting Date Action Owner Status Update
0109 22/01/2018
XRN3656 -Read Validation Tolerances - Analysis from
across the industry / Xoserve analysis needs to be
completed prior to the 5th February meeting. Xoserve (RH) Open
This information is currently not available from SAP-BW until after R2.
Request for the industry to share any analysis undertaken by 5th
March DSG meeting
0110 22/01/2018
XRN4484 - Remove restriction on nominated SOQ (as
per MOD 445)- To issue within a Change Pack for
ratifying at ChMC Xoserve Open This is an internal impact to Xoserve. A CP will be issued when the
change is being delivered
0209 19/02/2018
XRN4449 - PSR - Xoserve to issue the final version of
PSR mapping rules via the [email protected] box
account. Xoserve Open Require confirmation from Tahera regarding the latest mapping rules.
0304 05/03/2018
XRN4449 - Customer Team to write out to request any
further organisations wanting to test, to confirm by Friday
16th March. DSG Open
0307 05/03/2018 XRN4449 - Xoserve (CF) to assess whether there is a
limit on the number of test files that can be submitted. Xoserve Open
0308 05/03/2018 Meeting participants to provide a direct contact who will
be part of the XRN4449 process. DSG Open
0311 05/03/2018 Volume of CNC Update - Daily Cap to be defined by
Xoserve to share to Shippers. Xoserve Open
0312 05/03/2018 Release 3.0 Update - Xoserve (PD) to assess feasibility
of booking early engagement meetings in advance. Xoserve Open
0317 19/03/2018 Defect Dashboard - to be confirmed which date and
defect release it is proposed to be completed within. Xoserve Open
0322 19/03/2018 XRN4249 - Catch up exercise - Xoserve (CF) to provide
the plan for catch up activies. Xoserve Open
0323 19/03/2018 Implementation Plan - Xoserve to confirm this can be
completed and discussions at the next DSG to discuss Xoserve Open
0401 09/04/2018 Xoserve (DJ) to advise where in the process defect 655
currently is and if a fix has been identified. Xoserve Open
0402 09/04/2018 Xoserve (EL) to provide an update on ASP penny-
mismatching. Xoserve Open
0403 09/04/2018
Shipper organisations who are participating in the industry
testing need to provide key contact details, for
communications to be issued directly. DSG Open
0404 09/04/2018 Xoserve (LC) to confirm the rejection code per file type. Xoserve Open
Actions (Continued)
Title Meeting Date Action Owner Status Update
0405 09/04/2018 Xoserve (LC) to clearly advise timings in the lower
level implementation plans. Xoserve Open
0406 09/04/2018
Xoserve (RH) to make documentation clear that the
number of needs codes are per MPRN and not per
file. Xoserve Open
0407 09/04/2018
Xoserve (LW) to speak with (MD) about training
process. (ES) to compile an information document
and send out to the industry. Xoserve Open
0408 09/04/2018
Npower (JB) to provide further details on the issue for
Npower on implementing XRN4431. Xoserve (MD) to
organise a teleconference with meeting participants to
further discuss this issue. Npower/Xoserve Open
0409 09/04/2018 Xoserve (PD) to outline the impacts to DES
separately for XRN4454. Xoserve Open
0410 09/04/2018 Xoserve (RH) to provide a list of workarounds which
will be retired as a result of XRN4454. Xoserve Open
0411 09/04/2018 Xoserve (RH) to correct the error within the
documentation. Xoserve Open 0411 was corrected and issued in a revised change summary -
1917 on the 11th April.
0412 09/04/2018 Xoserve (RH) to update the meeting times for DSG
on Xoserve.com Xoserve Open
0413 09/04/2018 Xoserve (RH) to send out a notification about AQs of
1. Xoserve Open
Overview
Negative Consumption is generated when a Shipper submits a
subsequent Actual read that is less than the last Xoserve Estimated read
on UK Link (without a TTZ count).
This occurs in UK Link when Xoserve provides Estimated Readings in the
following scenarios:
Change of Shipper event
Class change
LDZ / exit zone change
A new fail to calculate reason was introduced where an AQ calculation
was not calculated owing to negative consumption. This was applied to
negative consumption's created from legacy meter readings where read
validations were less stringent.
Overview
Negative consumption generated post 01st June 2017 is
considered ‘valid’ with the introduction of more stringent Meter
Read validations
Negative Consumption is included within AQ Calculations
Reads can be replaced by the User registered on the date of the
Meter Reading. With the exceptions of:
Readings connected to RGMA updates
Actual Reads on Class 1 and Class 2 SMPs
Increase in AQs of 1 / Understated AQs
There has been an increase in the number of AQs of 1 and
understated AQs as a result of a lower actual meter reading being
submitted following an Xoserve estimated reading
This has occurred where the transfer reading is the AQ closing
reading, and therefore not taken into account with the AQ
calculation. The next meter reading, which is an actual, is the AQ
opening read. Only the negative consumption is considered within
the AQ calculation
Analysis shows the maximum impact is less than 0.03% of total
NDM AQ, therefore this is not considered a high material impact
Options – for DSG discussion
1. Shipper Action
Replace the Xoserve estimated reading and submit a subsequent meter reading which
will trigger a new rolling AQ calculation. The AQ will be a correct reflection of the gas
being consumed on the SMP. These meter readings can be submitted at the same
time.
Considerations
If this action is completed the SMP will have a reflective AQ
There are no impacts to UNC rules/calculations with this solution
This retains the original requirement from Nexus that all reconcilable reads should be
used for AQ calculation
Any UIG implications will be rectified once the readings are taken into account within
reconciliation
Options – for DSG discussion
2. Apply Fail to Calculate validation for all negative consumption period
Extend the code previously introduced whereby negative consumption is excluded
from AQ calculations and the prevailing AQ is carried forwards
Considerations
The prevailing AQ will be in situ until there are 9 months of accurate readings and a
new AQ can be calculated, impacts NDM gas nominations, any further estimated
transfer reads (should it transfer) will generate poor estimates
Less meter points will be subject to regular rolling AQ updates
UNC Modification 0638V and 0570 are both implemented which enact the CMA order
and the requirements for all Users to submit reads (0638V - monthly where smart and
AMR is present and annual read submission with 0570). PAC are monitoring
performance and may choose to incentivise Read submission
3. Another AQ correction reason – for example- the last calculated AQ is
not a reflection of the annual AQ
Considerations
Would correct the AQ
Creates a back stop date however analysis on SMPs impacted do not have a frequent
read submission profile.
Yes leave in question do DSG have further solution options
4. Option for the system to recalculate the estimated transfer read based
on previous read and latest submitted actual
Would require further analysis and complete impact assessment
Other Options – for DSG discussion