DSG CSS Consequential Change. 22 nd January PDF Free Download

DSG CSS Consequential Change 22 nd January 2019

Agenda Actions from previous meeting Gemini Topics for finalisation: Meter Readings at Transfer Management of Market Participant Data Management of MAP Id against Supply Meter Point High level design options New Topics for discussion: SPA Updates RGMA Meter Sector Code Meter Point Creation Meter Point Status Data Cleansing Update Customer road map

CSS Consequential Gemini High Level System Solution Impact Assessment

Customers Xoserve Switch can be requested anytime between D-5 and D - Switch is 30 secured with status CO @00:00:00 on D-2 Existing Process Switch Goes Live with status LI @00:00:00 D-2 D-1 D D+1 UKLINK Batch runs at 10 / 11 AM MDS & AAQ File is generated and sent to Gemini File Upload program is run & entries stored in DB MDS / AAQ values 06:00 -> ACT_Number Job 10 mins To generate unique id for new meter id combination received in MDS 11:00 -> Demand Estimation & UIG suite of job run Generate the nominations for D day Cyclic Job runs every 2/3 hours to reflect actual positions based on shipper nomination for DM sites Confirmed Nomination position Allocation Run NDM/UIG CON File Processing (run till close out) Maintenance Window 3 AM to 5 AM Gas Nomination ID received from UK Link Commence Gas Nomination submission for D View initial gas allocation position & UIG portion Finalise Gas nomination position Finalise gas purchases Revised gas allocation & UIG portion

Customers Xoserve POST CSS Switch can be requested anytime between D-1 and D - Switch is secured 28 @17:00:00 on D-1 Switch Goes Live @00:00:00 D-1 D D+1 Owing to CSS, if the file generation is moved to D-1, consideration is information will be received by 17:30 SAP ISU could take c1.5 hours to update custom tables and generate MDS/AAQ files Gemini will then need to schedule ACT_NUMBER job on receipt of MDS/AAQ file Run the Demand Estimation and UIG suite of jobs Considering concurrency with other jobs (which has potential to overrun as well), infrastructure capacity needs to be assessed 10% increase in To-Be volumes has been considered for MDS/AAQ process Impacts to external stakeholder unknown at this stage 17:30* -> CSS sends the confirmed position at 17:00 Entries made in trigger table Batch run to generate consolidated MDS/AQQ file 20:00* -> ACT_Number Job 10 mins To generate unique id for new meter id combination received in MDS 20:15* -> Demand & UIG suit of job run 45 to 50 min Generate the nominations for D day Will Reflect actual positions based on shipper nomination for DM Confirmed Nomination position Allocation Run NDM/UIG CON File Processing (run till close out) Maintenance Window 3 AM to 5 AM All timings are indicative and need further analysis Gas Nomination ID received from UK Link from ~20:00 hours Commence Gas Nomination submission for D View initial gas allocation position & UIG portion after 20:15 hours Finalise Gas nomination position Finalise gas purchases Revised gas allocation & UIG portion

CSS Consequential Gemini Change Overview Currently Gemini receives all the Portfolio updates on D-2 from SAP ISU on a daily basis via MDS/AAQ files. As part of this change, Gemini will receive the changes for switching data effective on D day on D-1 evening post CSS gate closure. Solution Options 1 Gemini to receive Portfolio updates on D-2 and D-1 for effective D day 2 Gemini to receive Portfolio updates on D-1 for effective D day

Current Functionality : Gemini Gemini : As-Is Design Gemini receives all the Portfolio updates based on the below triggers on D-2 with effective date as D day from SAP ISU on a daily basis via MDS/AAQ files - o Class Change o AQ-Correction o SOQ Change Through Contract Change o Withdrawal Process o Isolation o Registration Process o Address Change (CMS) o Post Code Change Through Internal Screens o Site Takeover Process o EUC Change o SMP AQ Monthly Calculations o RATCHET o SOLR o Reconnection o SMP Exit Zone change for IGT site The NTS / LDZ Unique sites are been manually created by Business (received as Worki tem from SAP ISU) via online screen on D-2 (Business days). Activity Number for active DM meter types are created by Shipper via online screen or system generated. Shipper do place DM nominations within a window i.e. D-35 05:00 to D-1 12:00 for gas flow D day via online screen / API / interfaces. Activity Number for NDM / UG meter types are created by the system on D-1 06:00 DM Nomination are being estimated on D-1 at 08:00 for active DM meter ids in case they are not present in the system. Shipper can re-nominate for DM meter types within a window D-1 14:00 to D 04:59. NDM / UG Nominations for D and D+1 are been calculated in the system using the AQ values, DM Nominations and Weather values Gemini sends the data to internal & NG systems on scheduled times on a daily basis.

Option 1 Gemini to receive Portfolio updates on D-2 and D-1 for effective D day 1 Triggers for Changes on D-2 Class Change AQ- Correction SOQ Change through Contract Change Process on D-2 Triggers for Process on D-1 Changes on D-1 System Generates Activity numbers [DM/ NDM /UG Meters] Registration process Withdrawal process System Generates Activity numbers [DM/ NDM /UG Meters] Isolation Address Change Post Code Change through Internal screen Site Takeover Process EUC Change SMP AQ Monthly calculation Ratchet SOLR Reconnection SMP Exit Zone change for IGT site Shippers can nominate / re-nominate for DM meters on D-2 for any new / existing meter id for the ones triggered as part of D-2 updates. In case of no DM Nomination for any active meter id, the estimation will run on D-1 at 800 hour bar for the NDM / UG nomination process The NDM / UG Nomination run for D day will be triggered on D-1 as in with the data present in the system Estimation will run for the missing DM Re-Nomination for the active meter id The NDM / UG Nomination run for D day will be triggered on D-1 as in with the data present in the system

Option 1 - High Level Impact Assessment 1 Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU API SAP BW CMS DES Assumptions MDS/AAQ files needs to be received and loaded before D-1 midnight, however a tool will be built to correct the data. No scheduling changes will be made for NDM & UG Nomination / Allocation / Invoicing suite No changes required in pre / post closeout processes in Gemini For Gas Year change, MDS/AAQ files will be loaded on D-2 and any changes can be updated on D-1 Last Sync message will be received from CSS by 6:00 pm Pros DM Nominations will be applicable for 13 triggers received on D-2 updates within its timelines Cons Technically complex for Gemini to handle 2 files loading D+1 and D updates sequentially on D-1 Overall Impact Incorrect mapping will be present for Future dates i.e. D+1 while D will contain the corrected record which will leads to incorrect NDM/UG Nominations Medium

Option 1 - System Impact Assessment 1 System Component: Development Type: Impacted User(s): Build Type: Gemini Process Code Code Change / Scheduling Shippers Existing SAP ISU Process Code Code Change Gemini Existing Change Description: System will be amended to load the D-2 and D-1 updates in Gemini followed by creation of activity number and estimation process. Code Changes will be done to send the 13 triggered on D-2 and rest 2 in D-1. Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: A A G G A A A A A G G A A A

Option 1 - Process Impact Assessment 1 Process Area Complexity File Formats Exception External Screens Batch Jobs Performance Test? Meter Details M N n/a N Y Y Nomination / Renomination M N n/a N N Y Gas Trades n/a n/a n/a n/a n/a n/a Measurements n/a n/a n/a n/a n/a N Allocation n/a n/a n/a n/a n/a Y Invoicing n/a n/a n/a n/a n/a Y Interfaces M N n/a n/a Y Y External System M N n/a n/a N Y API n/a n/a n/a n/a n/a N

Option 2 Gemini to receive Portfolio updates on D-1 for effective D day 2 Triggers for Changes on D-1 Class Change AQ- Correction SOQ Change through Contract Change Process on D-1 System Generates Activity numbers [DM/ NDM /UG Meters] Isolation Address Change Post Code Change through Internal screen Site Takeover Process EUC Change Estimation will run for the missing DM Re-Nomination for the active meter id SMP AQ Monthly calculation Ratchet SOLR Reconnection SMP Exit Zone change for IGT site NDM / UG Nomination run for D day will be triggered on D-1 as in with the data present in the system Registration process Withdrawal process

Option 2 - High Level Impact Assessment 2 Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU API SAP BW CMS DES Assumptions MDS/AAQ files needs to be received and loaded before D-1 midnight, however a tool will be built to correct the data. No scheduling changes will be made for NDM & UG Nomination / Allocation / Invoicing suite No changes required in pre / post closeout processes in Gemini For Gas Year change, MDS/AAQ files will be loaded on D-2 and any changes can be updated on D-1 Last Sync message will be received from CSS by 6:00 pm Pros Technically less complex for Gemini to handle 1 file loading D updates on D-1 Correct records will be stored in the system across for all the processes Overall Impact Medium Cons Nominations cannot be submitted by the shippers for all DM meter ids received in the file UG Nominations will be calculated based on the DM Nomination estimates and AQ present in the system NDM Nominations will be calculated based on the AQ values present at that time in the system

Option 2 - System Impact Assessment 2 System Component: Development Type: Gemini Process Code Code Change / Scheduling SAP ISU Process Code Code Change Impacted User(s): Build Type: Shippers Existing Gemini Existing Change Description: System will be amended to load the D-1 updates in Gemini followed by creation of activity number and estimation process. Code Changes will be done to send the updates to D-1. Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: A G G G A A A A G G G A A A

Option 2 - Process Impact Assessment 2 Process Area Complexity File Formats Exception External Screens Batch Jobs Performance Test? Meter Details L N n/a N Y Y Nomination / Renomination M N n/a N N Y Gas Trades n/a n/a n/a n/a n/a n/a Measurements n/a n/a n/a n/a n/a n/a Allocation n/a n/a n/a n/a n/a Y Invoicing n/a n/a n/a n/a n/a Y Interfaces L N N N Y Y External System M N n/a n/a N Y API n/a n/a n/a n/a n/a n/a

Additional Design Considerations MDS/AAQ files received post midnight on D-1 will fail to load in Gemini. A tool may have to be built to load the data for any rejections or failures to avoid mismatches. DM Re-nomination timelines will be reduced for the D-1 updates for effective date D. The timelines will be applicable post loading of the files till D However, re-nominations can be placed by the shippers considering the lead time (2 hours from the request) and flow rate validation If the Shipper doesn t make a Re-nomination for the Day irrespective of the Estimated DM Nominations perceived to be an accurate reflection of the usage for the D day, for the purpose only of determining the Scheduling Charges the nominated quantity shall deemed to be zero (as is) Data and process impacts to other systems MIS, GCS, MIPI, IAP, SAP BW to be assessed Changes to NTS / LDZ Unique sites work items that are manually created on D-2 needs to be discussed

Topics for finalisation Meter Readings at Transfer Management of Market Participant Data Management of MAP Id against Supply Meter Point

CSS Impact Assessment Switching Processes High Level System Solution Impact Assessment

CSS Consequential UK Link High Level System Solution Impact Assessment

Contents Overall Assumptions Solution options for CSSC Category 1 requirements (Excluding Gemini, DES and BW impact) Nomination Enquiry Nomination Process Shipper Transportation Rates Settlement Details (aka Shell Record) Change of Supplier Change of Shipper Only Forced / Auto Confirmation Shipper Withdrawal

Overall Assumptions For high level design all interactions between CSS Provider and UKLink will be via Marketflow through IX and EFT All NTS sites are out of scope for CSS and hence, will continue to operate as is (BAU) Batch schedules need to be revisited as part of detail design to accommodate the faster switching timelines Shipper File formats impacted by CSS consequential need to be revisited and might require system changes The proposed solution options may change due to refinement and further changes to CSSC requirements and considerations during Detail design phase APIs are being considered as part of the solution options

Nomination Enquiry

Change Overview Nomination Enquiry UK Link will still allow for a proposing shipper to submit a Nomination Enquiry Request (NOM - S47) independent to a CSS switch to enable them to obtain the current values of Supply Meter Point. Solution Options 1 Nomination Enquiry will continue As Is 2 Nomination Enquiry via new API service and the existing file 3 Nomination Enquiry via a new API only

Option 1 - High Level Impact Assessment 1 1. Nomination Enquiry will continue As Is Nomination Enquiry will continue As Is via the file received from the Shippers. UK Link will allow the proposing Shipper to submit current S47 segment to obtain the Supply Meter Point details. All the current validations will be applied on S47 segment. Potential changes to file format with respect to withdrawal flag sent in the response (S59 segment) are anticipated. Impacted Systems Impact Gemini Assumptions All current Nomination Enquiry validations will continue to be applied Batch processing schedule might change Marketflow SAP PO SAP ISU CMS API SAP BW DES Overall Impact No Impacts

Option 1 - System Impact Assessment 1 SAP ISU SAP PO Marketflow System Component: Development Type: Impacted User(s): Build Type: SPA File Formats File Formats Code change Configuration Change Configuration Change Shippers Shippers Shippers Existing Existing Existing Change Description: Code changes will be done related to withdrawal flag File format change with respect to withdrawal flag File format change with respect to withdrawal flag Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: G G G G G G G G G G G G G G G G G G G G G Performance Impact:

Option 1 - Process Impact Assessment 1 Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test? SPA L Y N N Y N Metering (Reads) n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Reconciliation n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Capacity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Commodity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Amendment n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Other n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Rolling AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Formula Year AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N

Option 2 - High Level Impact Assessment 2 2. Nomination Enquiry Process via new API service or existing File Nomination Enquiry process will be received via new API service or existing File. Shippers can send the enquiry file via API or can send the same way as they are doing today. UK Link will allow the proposing Shipper to submit S47 segment to obtain the Supply Meter Point details. All the current validations will be applied on S47 segment. Potential changes to file format with respect to withdrawal flag sent in the response (S64 segment) are anticipated. Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU CMS Assumptions Existing business rules will be applied around enquiry via new API service. Data elements for the new API service will mirror the existing file All current Nomination Enquiry validations will continue existing file interface. API SAP BW DES Overall Impact Medium

Option 2 - System Impact Assessment 2 SAP ISU SAP PO Marketflow API System Component: Development Type: Impacted User(s): Build Type: Process Code Configuration & File Formats File Formats Configuration Code Change Configuration Change Configuration Change Configuration Change Shippers Shippers Shippers Shippers New New Existing New Change Description: Requirement Clarity: New Interface to be built for Nomination Enquiry via API New interface to be built in order to receive the Nomination Enquiry file via API. File format change with respect to withdrawal flag File format change with respect to withdrawal flag New interface to be built in order to receive the Nomination Enquiry. Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: A A G A G G G G A A G A A A G A A A G A G G G G A A G A

Option 2 - Process Impact Assessment 2 Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test? SPA M Y N N N N Metering (Reads) n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Reconciliation n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Capacity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Commodity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Amendment n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Other n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Rolling AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Formula Year AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N

Option 3 - High Level Impact Assessment 3 2. Nomination Enquiry Process via new API service or existing File Nomination Enquiry process will be received via new API service which will mirror the current enquiry file. Impacted Systems Impact Gemini Assumptions Existing business rules will be applied around enquiry via new API service. Data elements for the new API service will mirror the existing file Marketflow SAP PO SAP ISU CMS API SAP BW DES Overall Impact Medium

Option 3 - System Impact Assessment 3 SAP ISU SAP PO API System Component: Development Type: Impacted User(s): Build Type: Process Code Configuration & File Formats Configuration Code Change Configuration Change Configuration Change Shippers Shippers Shippers New New New Change Description: Requirement Clarity: New Interface to be built for Nomination Enquiry via API New interface to be built in order to receive the Nomination Enquiry file via API. File format change with respect to withdrawal flag New interface to be built in order to receive the Nomination Enquiry. Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: G G G G G G

Option 3 - Process Impact Assessment 3 Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test? SPA M N N N N N Metering (Reads) n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Reconciliation n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Capacity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Commodity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Amendment n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Other n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Rolling AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Formula Year AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N

Nomination Process

Nomination Process Change Overview Currently UK Link requires the proposing (or current registered) shipper to submit a Nomination Request (NOM) to obtain details of the Transportation charges, to support Network referrals and for changes to Class, batch frequency or MRF on the MPRN for the large competitive supply meter points where AQ is greater than 73,200. Post CSS, a version of the Nomination request from a proposing or registered shipper for any large supply meter points will used to support the Network appraisal (referrals). Switching can still take place through CSS without a nomination being submitted. Solution Options 1 Nomination Process

Option 1 - High Level Impact Assessment 1 1. Nomination Process UK Link will still need to allow for a proposing (or current registered) shipper to submit a Nomination Request (NOM) independent of a switch request to enable the transporter to assess the impact on the changes where necessary. Potential changes to File format with respect to withdrawal flag sent in the Nomination offer (S64 segment) are anticipated. Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU API SAP BW CMS DES Assumptions No Impacts to Nomination cancellation process UK Link will send the relevant notifications to the DMSPs(GCC file) that is currently issued at Nomination. A Shipper can still send multiple Nomination request. All Nomination validations will continue to be As Is. Batch processing schedule might change Overall Impact Low

Shipper Transportation Rates

Shipper Transportation Charges Change Overview Shipper users will be able to access transportation charges, this will be an extract of existing transportation rates. If shipper needs any specific rate with respect to change of Class, MRF, batch frequency and any referrals, the Shipper must correct process in order to obtain an offer. Shippers will query transportation rate via a new API Service. Validation rules will be build within UK Link to restrict the invalid requests. This services will only provide data for transportation rates for Large supply meter points Solution Options 1 Transportation rate extract to shippers via new API Service (Supporting multiple MPRNs)

Option 1 - High Level Impact Assessment 1 1- Transportation rate extract to shippers via new API Service (Supporting multiple MPRNs) Shipper API service will be designed to provide facility to extract current transportation rate values. This service will enable Shippers to query data from UK Link for multiple MPRNs. Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU API SAP BW CMS DES Assumptions Any shipper can request for transportation rate data for LSP sites even if the site is outside of their portfolio Existing business rules will be applied around querying transportation rate data through API service route(nomination Request Equivalent ) Any changes to existing MRF, Batch, Class, Capacity will still be received via Nomination request Real time transportation rates will be provided without validity period and are subjected to change based on existing business rules Overall Impact Medium

Option 1 - System Impact Assessment 1 SAP ISU SAP PO API System Component: Process Code Configuration Configuration Development Type: Impacted User(s): Build Type: Code Change Configuration code Configuration Code Shippers Shippers Shippers New Service for Shippers New Service for Shippers New Service for Shippers Change Description: Code development to fetch real time transportation rate data System to make the configuration to pass Data to Shipper API System to make the configuration for API to send data to Shippers Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: G G G G G G G G G Performance Impact:

Option 1 - Process Impact Assessment 1 Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test? SPA M N N N N Y Metering (Reads) n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Reconciliation n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Capacity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Commodity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Amendment n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Other n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Rolling AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Formula Year AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N

Settlement Details (AKA Shell Record)

Settlement details (AKA shell record) Change Overview Shippers will continue to provide and maintain the settlement details that are required in UK Link for the Supplier/Shipper's registration period. Details provided by a shipper as part of the current confirmation process that are not provided to UK Link via the CSS Registration Synchronization message, can be provided by the shipper to ensure the relevant settlement details are applied from the shipper's confirmation effective date. This will include items such Class, Meter Read Frequency, SOQ/SHQ, Contact details etc. Where a shipper have provided any settlement details, they will be linked to the CSS switch and applied on the effective date of the switch. Incase of no details provided, default values will be applied based on the rules defined. Solution Options 1 New Batch interface and response for Settlement details (AKA Shell record)

Option 1 - High Level Impact Assessment 1 1- New Batch interface for Settlement details (AKA Shell record) As part of the solution, two new file based interfaces will be built Interface 1: to receive the settlement details from shippers via Marketflow and Interface 2: to send the responses back to shippers via Marketflow. In case of multiple settlement details being sent the latest valid data will be applied when the secured sync message is received from CSS. In case of no settlement details received from shipper when the secured sync is received, default settlement details will be applied based on the rules defined. Settlement details will be validated on receipt and re-validated when switch is secured; response will be sent to shipper only if validation fails (Rejection). Matching / linking will be based on MPRN, Shipper and Supplier, and if provided the CSS Registration Identifier. Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU API SAP BW Overall Impact Medium CMS DES Assumptions If settlement details has transporter Nomination reference, offer data will take precedence in calculation of transportation rates. If no settlement details are received by UK Link from shipper, offer details will not be applied. Proposal for 3:00 PM cut off to receive settlement details. Rules for the application of settlement details will be defined for all the possible switching scenarios and site types. Settlement details may be received after switch Validation (VL), hence the notification will have rates calculated based on default values which are subjected to change till the status is changed to Secured (SC). Latest Valid settlement details received will be applied when switch is secured. File Formats and Validity Period of Settlement details will be received before DD Phase.

Option 1 - System Impact Assessment 1 System Component: Development Type: Impacted User(s): Build Type: SAP ISU SAP PO Marketflow SPA Configuration Configuration Code Change Configuration code Configuration Code Shippers Shippers Shippers 2 New Interfaces for Shippers 2 New Interfaces for Shippers 2 New Interfaces for Shippers Change Description: 2 new interfaces will be built Interface 1 - To receive the settlement details(aka shell record) Interface 2 - To send the response to shippers System will be configured to cater the 2 new interfaces between ISU and marketflow System will be configured to cater the 2 new interfaces between ISU and marketflow Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: A G A G G G G G G

Option 1 - Process Impact Assessment 1 Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test? SPA M Y N N Y Y Metering (Reads) n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Reconciliation n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Capacity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Commodity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Amendment n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Other n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Rolling AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Formula Year AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N

Change of Supplier (with or without change of Shipper)

Supplier Switching Solution Options Change Overview Currently any changes to the supplier are received via GEA or Reconfirmation process by shippers to UKLink. Post CSS implementation, the supplier switching process will be mastered by CSS. This will include below requests from CSS: Change of Supplier with same shipper Change of Supplier with different shipper UK Link will receive notifications from the CSS as part of Registration Sync message to advise of the current status of Supplier switches once they have been successfully Validated, Confirmed and Secured. However, on receipt of Registration sync from the CSS, UKLink is expected to perform high level validations (e.g. MPRN, Org ID etc.) and notify response to CSS in case of failures/warnings as new interface. UK Link will record the incoming Shipper and Supplier details and is expected to notify. Gaining shipper following the receipt of validated (VL) sync message (Current world equivalent of CFR) Gaining and Losing shippers(ceased Responsibility) following receipt of Secured (SC) sync (Current world equivalent TRF, MRI & PAC) i Registration Sync for VL Status 1a 2a Minimum changes to existing CFR File New interface for Gaining shipper notification Registration Sync for SC Status 1b 2b Minimum changes to existing TRF, MRI & PAC Files New Interface to combine existing files and remove redundant information

Option 1 - High Level Impact Assessment 1a 1. Registration Sync for VL Status - Minimum changes to existing CFR File New Registration Sync interface will be build to notify any switching triggers from CSS system to ISU via Marketflow. Marketflow is expected to generate a delivery receipt acknowledgment to CSS on receipt of these sync messages. Once received at ISU, validations will be performed to verify the Registration sync messages and in case of failures, rejection response will be sent via new interface to notify CSS If Validation is successful, switch will be created with VL status in ISU and gaining shipper will be notified in CFR file Minimum changes to existing CFR file format to include the settlement data details if received or default values that will be applied. Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU API SAP BW CMS DES Assumptions CNF will no longer be used to receive a switch request except for NTS sites. If received it will be rejected Supplier sync without shipper change will be treated as reconfirmation process If no settlement details received, CFR will be sent with data based on agreed default values Registration sync will be validated at ISU, if failed, rejection will be notified to CSS (VL) and gaining shipper will not be notified Losing shipper will not be notified on validated sync Overall Impact High

Option 1 - System Impact Assessment 1a SAP ISU SAP PO Marketflow System Component: Development Type: Impacted User(s): SPA Configuration Configuration Code Change Configuration Change Configuration Change Shippers & CSS Provider Shippers & CSS Provider Shippers & CSS Provider Build Type: 1- Existing for Shippers 2- New for CSS provider 1- Existing for Shippers 2- New for CSS provider 1- Existing for Shippers 2- New for CSS provider Change Description: 1. New Interface to receive Supplier Switch 2. New Interface to reject the invalid Sync 3. CFR to gaining shipper with minimum File format changes 1. System to be configured to cater to 2 new interface 2.Change to existing interface between ISU and marketflow 1. System to be configured to cater to 2 new interface 2.change to existing interface between ISU and marketflow Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact:

Option 1 - Process Impact Assessment 1a Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test? SPA H Y Y N Y Y Metering (Reads) n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Reconciliation n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Capacity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Commodity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Amendment n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Other n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Rolling AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Formula Year AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N

Option 2 - High Level Impact Assessment 2a 2. Registration Sync for VL Status - New interface for Gaining shipper notification New Registration Sync interface will be build to notify any switching triggers from CSS system to ISU via Marketflow Marketflow is expected to generate a delivery receipt acknowledgment to CSS on receipt of these sync messages Once received at ISU, validations will be performed to verify the Registration sync messages and in case of failures, rejection response will be sent via new interface to notify CSS If Validation is successful, switch will be created with VL status in ISU and gaining shipper will be notified in new file format which will include settlement details if received or default values that will be applied. Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU API SAP BW Overall Impact High CMS DES Assumptions CNF will no longer be used to receive a switch request except for NTS sites. If received will be rejected Supplier sync without shipper change will be treated as reconfirmation process If no settlement details received, new interface will be sent based on agreed default values Registration sync will be validated at ISU, if failed, rejection will be notified to CSS (VL) Losing shipper will not be notified on validated sync Objection/Annulment window will be managed by CSS

Option 2 - System Impact Assessment 2a SAP ISU SAP PO Marketflow System Component: SPA Configuration Configuration Development Type: Code Change Configuration Change Configuration Change Impacted User(s): Shippers & CSS Provider Shippers & CSS Provider Shippers & CSS Provider Build Type: 3 New Interfaces (2- CSS Provider, 1-Shipper) 3 New Interfaces (2- CSS Provider, 1-Shipper) 3 New Interfaces (2- CSS Provider, 1-Shipper) Change Description: 1. New Interface to receive Supplier Switch sync 2. New Interface to reject the invalid Sync 3. New interface to gaining shipper on Validated sync 1. System to be configured to cater to 3 new interface between ISU and Marketflow 1. System to be configured to cater to 3 new interface between ISU and Marketflow Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact:

Option 2 - Process Impact Assessment 2a Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test? SPA H Y Y N Y Y Metering (Reads) n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Reconciliation n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Capacity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Commodity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Amendment n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Other n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Rolling AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Formula Year AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N

Option 1 - High Level Impact Assessment 1b 1. Registration Sync for SC Status - Minimum changes to existing TRF, MRI & PAC Files Registration Sync interface will be built to notify any switching triggers from CSS system to ISU via Marketflow Marketflow is expected to generate a delivery receipt acknowledgment to CSS on receipt of these sync messages Once received at ISU, validations will be performed to verify the Registration sync messages and in case of failures, rejection response will be sent via new interface to notify CSS Irrespective of warning notification, switch will be updated to Secured status in ISU and gaining shipper will be notified with minimum changes in existing files (TRF/MRI/PAC) to accommodate settlement details and losing shipper will be notified in TRF file with ceased responsibility Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU API SAP BW CMS DES Assumptions Last sync message from CSS will be received by 18:00 hrs Registration sync will be validated in ISU, if failed, warning will be issued to CSS (SC) with rejection but switch will go live UK Link will receive the sync messages in sequence and will process in batches Batch schedule need to be reviewed Transportation rates derived based on defaults will be sent if settlement data is not received by shipper or rejected on re-validation at the time of secured Overall Impact High

Option 1 - System Impact Assessment SAP ISU SAP PO Marketflow 1b System Component: SPA Configuration Configuration Development Type: Impacted User(s): Code Change Configuration Change Configuration Change Shippers & CSS Provider Shippers & CSS Provider Shippers & CSS Provider Build Type: 2 - Existing to Shippers 2 - New for CSS Provider 2 - Existing to Shippers 2 - New for CSS Provider 2 - Existing to Shippers 2 - New for CSS Provider Change Description: Requirement Clarity: 1. New Interface to receive Supplier Switch sync 2. New Interface to send warning for the invalid Sync 3. TRF/MRI to gaining shipper with minimum File format changes 4. TRF to Losing Shipper (AS IS) 1. System to be configured to cater to 2 new interface 2. Change to existing interface between ISU and marketflow 3. TRF to losing shipper (AS IS) 1. System to be configured to cater to 1 new interface 2.Change to existing interface between ISU and marketflow 3. TRF to losing shipper (AS IS) Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact:

Option 1 - Process Impact Assessment 1b Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test? SPA H Y Y N Y Y Metering (Reads) n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Reconciliation n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Capacity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Commodity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Amendment n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Other n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Rolling AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Formula Year AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N

Option 2 - High Level Impact Assessment 2b 2. Registration Sync for SC Status - New Interface to combine existing files and remove redundant information Registration Sync interface will be built to notify any switching triggers from CSS system to ISU via Marketflow. Marketflow is expected to generate a delivery receipt acknowledgment to CSS on receipt of these sync messages. Once received at ISU, validations will be performed to verify the Registration sync messages and in case of failures, rejection response will be sent via new interface to notify CSS Irrespective of warning notification, switch document will be updated to Secured status in ISU and New File format will be developed to combine the notifications sent to gaining shipper for TRF/MRI/PAC files along with details for settlement details and losing shipper will be notified in TRF file with ceased responsibility Impacted Systems Impact Marketflow SAP PO SAP ISU API Gemini SAP BW CMS DES Assumptions Last sync message from CSS will be received no later than 18:00 hrs Registration sync will be validated at ISU, if failed, warning will be issued to CSS (SC) with rejection but switch will go live UKLink will receive the sync messages in sequence and processes these in batches Batch schedule need to be reviewed Transportation rates will be derived based on default values if settlement details are not received by shipper or rejected on re-validation at the time of secured Overall Impact High

Option 2 - System Impact Assessment 2b SAP ISU SAP PO Marketflow System Component: Development Type: SPA Configuration Configuration Code Change Configuration Change Configuration Change Shippers & CSS Provider Shippers & CSS Provider Shippers & CSS Provider Impacted User(s): Build Type: 1 Existing to Shippers 1 New FF for shippers 2 New for CSS Provider 1 Existing to Shippers 1 New FF for shippers 2 New for CSS Provider 1 Existing to Shippers 1 New FF for shippers 2 New for CSS Provider Change Description: 1. New Interface to receive Supplier Switch secured sync 2. New Interface to send warning for the invalid Sync 3. New File format to club the proposing shipper notification. 4. TRF to Losing Shipper (AS IS) 1. System to be configured to cater to 2 new interfaces between CSS and ISU 2. New File format to club the proposing shipper notification 3. TRF to losing shipper (AS IS) 1. 1. System to be configured to cater to 2 new interfaces between CSS and ISU 2. New File format to club the proposing shipper notification 3. TRF to losing shipper (AS IS) Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact:

Option 2 - Process Impact Assessment 2b Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test? SPA H Y Y N Y Y Metering (Reads) n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Reconciliation n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Capacity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Commodity n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Amendment n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Invoicing Other n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Rolling AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N Formula Year AQ n/a / H / M / L n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N n/a / Y / N

Change of Shipper Only

Change of Shipper Only Change Overview Currently, shipper submits the shipper transfer request via Confirmation process to UKLink whereas post CSS implementation, CSS will initiate Change of Shipper Event Sync to UKLink with no change in supplier details and below changes will be considered: Where the energy supplier makes a change to the Shipper associated to their registration via the CSS process, then a synchronization message will be received via Registration Sync by UK Link to update this data This is an update/event for CSS and hence, validated, confirmed and secured sync messages will not be received from CSS On receipt of Registration sync from the CSS, UKLink is expected to perform high level validations (e.g.. MPRN, Org ID etc.) and notify response to CSS in case of failures/warnings as new interface UKLink will treat this as a existing shipper transfer process and expected to notify gaining shipper on receipt and after the gate closure whereas losing shipper will be notified of ceased responsibility. Solution CSS can Options: cancel a futuristic change of shipper request with a synchronization message to UK Link to notifying it of the cancellation. ilenotifications on Receipt of Change of Shipper Event Sync 1a 2a Minimum changes to existing CFR File New interface for Gaining shipper notification Notifications post Gate Closure on D-1 1b 2b Minimum changes to existing TRF, MRI & PAC Files New Interface to combine existing files and remove redundant information

Option 1 - High Level Impact Assessment 1a 1. Notifications on Receipt of Change of Shipper Event Sync - Minimum changes to existing CFR File New Registration Sync interface will be build to notify any switching triggers from CSS system to ISU via Marketflow Marketflow is expected to generate a delivery receipt acknowledgment to CSS on receipt of these sync messages Once received at ISU, validations will be performed to verify the Registration sync messages and in case of failures, rejection response will be sent via new interface to notify CSS If Validation is successful, switch will be created for effective date and gaining shipper will be notified in CFR file with minimum changes to existing file format to include the settlement details if received or defaults that will be applied. Impacted Systems Impact Gemini Marketflow SAP PO SAP ISU API SAP BW Overall Impact High CMS DES Assumptions CNF will no longer be used to receive a switch request except for NTS sites. If received will be rejected Offer will not be mandatory for LSP sites GEA file will not be used for Supplier changes If no settlement data received, CFR will be sent with transportation rates derived based on default values Registration sync will be validated at ISU, if failed, rejection will be notified to CSS Losing shipper will not be notified on receipt of change of shipper only sync Change of Shipper cancellation sync will be received before gate closure

Option 1 - System Impact Assessment 1a SAP ISU SAP PO Marketflow System Component: Development Type: Impacted User(s): Build Type: SPA Configuration Configuration Code Change Configuration Change Configuration Change Shippers & CSS Provider Shippers & CSS Provider Shippers & CSS Provider 1-Existing for Shippers 2- New for CSS provider 1-Existing for Shippers 2- New for CSS provider 1-Existing for Shippers 2- New for CSS provider Change Description: 1. New Interface to receive change of shipper sync 2. New Interface to reject the invalid Sync 3. CFR to gaining shipper with minimum File format changes 1. System to be configured to cater to 2 new interface 2.Change to existing interface between ISU and marketflow 1. System to be configured to cater to 2 new interface 2.change to existing interface between ISU and marketflow Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact:

DSG CSS Consequential Change. 22 nd January 2019