DSG CSS Consequential Change 22 nd January 2019 Agenda Actions - - PowerPoint PPT Presentation
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
– Meter Readings at Transfer – Management of Market Participant Data – Management of MAP Id against Supply Meter Point – High level design options
– SPA Updates – RGMA – Meter Sector Code – Meter Point Creation – Meter Point Status
D-2 D D-1
Switch is secured with status CO @00:00:00 on D-2
Switch Goes Live with status LI @00:00:00
MDS & AAQ File is generated and sent to Gemini UKLINK Batch runs at 10 / 11 AM
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
D+1
Confirmed Nomination position
Run – NDM/UIG
Processing (run till close out)
Maintenance Window – 3 AM to 5 AM
Switch can be requested anytime between D-5 and D - 30
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
Xoserve
Customers
D D-1
Switch is secured @17:00:00
Switch Goes Live @00:00:00 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
D+1
Confirmed Nomination position
Run – NDM/UIG
Processing (run till close out)
Maintenance Window – 3 AM to 5 AM
17:30* -> CSS sends the confirmed
position at 17:00 Entries made in trigger table Batch run to generate consolidated MDS/AQQ file
moved to D-1, consideration is information will be received by 17:30
update custom tables and generate MDS/AAQ files
ACT_NUMBER job on receipt of MDS/AAQ file
suite of jobs
jobs (which has potential to overrun as well), infrastructure capacity needs to be assessed
been considered for MDS/AAQ process
unknown at this stage
Switch can be requested anytime between D-1 and D - 28
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
Customers
Xoserve
Finalise Gas nomination position Finalise gas purchases Revised gas allocation & UIG portion
need further analysis
CSS Consequential – Gemini
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
Gemini to receive Portfolio updates on D-2 and D-1 for effective D day Gemini to receive Portfolio updates on D-1 for effective D day 1 2
Current Functionality : Gemini
MDS/AAQ files -
(Business days).
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 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 System Generates Activity numbers [DM/ NDM /UG Meters] 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
Triggers for Changes on D-1
Registration process Withdrawal process System Generates Activity numbers [DM/ NDM /UG Meters] 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
Process on D-2 Process on D-1
Impacted Systems
Assumptions
loaded before D-1 midnight, however a tool will be built to correct the data.
NDM & UG Nomination / Allocation / Invoicing suite
processes in Gemini
be loaded on D-2 and any changes can be updated on D-1
CSS by 6:00 pm
Overall Impact
Medium
Marketflow
SAP PO
SAP ISU
Gemini
SAP BW CMS DES API
Impact
1
Pros Cons
DM Nominations will be applicable for 13 triggers received on D-2 updates within its timelines Technically complex for Gemini to handle 2 files loading D+1 and D updates sequentially on D-1 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
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: Gemini SAP ISU Process Code Process Code Code Change / Scheduling Code Change Shippers Gemini Existing Existing 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. A A A A G G G G A A A A A A
1
Process Area Complexity File Formats Exception External Screens Batch Jobs Performance Test?
Meter Details M N n/a N Y Y Nomination / Re- nomination 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
1
2 Triggers for Changes on D-1 Class Change AQ- Correction SOQ Change through Contract Change 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 Registration process Withdrawal process System Generates Activity numbers [DM/ NDM /UG Meters] Estimation will run for the missing DM Re-Nomination for the active meter id NDM / UG Nomination run for D day will be triggered on D-1 as in with the data present in the system Process on D-1
Option 2 – Gemini to receive Portfolio updates on D-1 for effective D day
Impacted Systems
Assumptions
loaded before D-1 midnight, however a tool will be built to correct the data.
NDM & UG Nomination / Allocation / Invoicing suite
processes in Gemini
be loaded on D-2 and any changes can be updated on D-1
CSS by 6:00 pm
Marketflow SAP PO
SAP ISU
Gemini
SAP BW CMS DES API
Impact
2
Pros Cons
Technically less complex for Gemini to handle 1 file loading D updates on D-1 Nominations cannot be submitted by the shippers for all DM meter ids received in the file Correct records will be stored in the system across for all the processes 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
Overall Impact
Medium
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Gemini SAP ISU Process Code Process Code Code Change / Scheduling Code Change Shippers Gemini Existing Existing 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. A A G G G G G G A A A A A A
2
Process Area Complexity File Formats Exception External Screens Batch Jobs Performance Test?
Meter Details L N n/a N Y Y Nomination / Re- nomination 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 Other (Specify) n/a n/a n/a n/a n/a n/a
2
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
Gemini, DES and BW impact)
Marketflow through IX and EFT
(BAU)
faster switching timelines
require system changes
CSSC requirements and considerations during Detail design phase
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
Nomination Enquiry will continue As Is Nomination Enquiry via new API service and the existing file Nomination Enquiry via a new API only 1 2 3
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
Assumptions
continue to be applied
Overall Impact
No Impacts Marketflow SAP PO SAP ISU Gemini SAP BW CMS DES API
Impact
1
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact:
1
SAP ISU SAP PO Marketflow SPA File Formats File Formats Code change Configuration Change Configuration Change Shippers Shippers Shippers Existing Existing Existing 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 G G G G G G G G G G G G G G G G G G G G G
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 RGMA 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
1
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
Assumptions
around enquiry via new API service.
mirror the existing file
will continue existing file interface.
Overall Impact
Medium
Marketflow
SAP PO SAP ISU
Gemini SAP BW CMS DES
API Impact
2
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow API Process Code Configuration & File Formats File Formats Configuration Code Change Configuration Change Configuration Change Configuration Change Shippers Shippers Shippers Shippers New New Existing New 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
Nomination Enquiry. 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
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
2
Nomination Enquiry process will be received via new API service which will mirror the current enquiry file.
Impacted Systems
Assumptions
around enquiry via new API service.
mirror the existing file
Overall Impact
Medium
Marketflow
SAP PO SAP ISU
Gemini SAP BW CMS DES
API Impact
3
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO API Process Code Configuration & File Formats Configuration Code Change Configuration Change Configuration Change Shippers Shippers Shippers New New New 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
Nomination Enquiry. A A A G G G A A A A A A A A A G G G A A A
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
3
Nomination Process
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
Nomination Process 1
UK Link will still need to allow for a proposing (or current registered) shipper to submit a Nomination Request (NOM) independent
Potential changes to File format with respect to withdrawal flag sent in the Nomination offer (S64 segment) are anticipated.
Impacted Systems
Assumptions
the DMSPs(GCC file) that is currently issued at Nomination.
request.
As Is.
Overall Impact
Low Marketflow
SAP PO
SAP ISU
Gemini SAP BW CMS DES API
Impact
1
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow SPA File Formats File Formats Code change Configuration Change Configuration Change Shippers Shippers Shippers Existing Existing Existing 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 G G G G G G G G G G G G G G G G G G G G G
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 RGMA 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
1
Shipper Transportation Charges
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
Transportation rate extract to shippers via new API Service (Supporting multiple MPRNs) 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
Assumptions
data for LSP sites even if the site is outside of their portfolio
querying transportation rate data through API service route(Nomination Request Equivalent )
Capacity will still be received via Nomination request
without validity period and are subjected to change based on existing business rules
Marketflow
SAP PO SAP ISU
Gemini SAP BW CMS DES
API Impact
1
Overall Impact
Medium
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO API Process Code Configuration Configuration Code Change Configuration code Configuration Code Shippers Shippers Shippers New Service for Shippers New Service for Shippers New Service for Shippers 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 A A A G G G A A A G G G A A A G G G A A A
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
1
Settlement details (AKA shell record)
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
New Batch interface and response for Settlement details (AKA Shell record) 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
Assumptions
reference, offer data will take precedence in calculation of transportation rates.
from shipper, offer details will not be applied.
details.
be defined for all the possible switching scenarios and site types.
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).
applied when switch is secured.
details will be received before DD Phase.
Overall Impact
Medium
Marketflow SAP PO SAP ISU
Gemini SAP BW CMS DES API
Impact
1
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: 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 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 A A A A G A A A A G G G A A A G G G A A A
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 RGMA 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
1
Solution Options
i
Supplier Switching
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)
2a 1a 1b 2b Minimum changes to existing CFR File New interface for Gaining shipper notification Minimum changes to existing TRF, MRI & PAC Files New Interface to combine existing files and remove redundant information Registration Sync for VL Status Registration Sync for SC Status
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
Assumptions
request except for NTS sites. If received it will be rejected
treated as reconfirmation process
sent with data based on agreed default values
failed, rejection will be notified to CSS (VL) and gaining shipper will not be notified
sync
Overall Impact
High Marketflow SAP PO
SAP ISU
Gemini SAP BW CMS DES API
Impact
1a
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow 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 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
new interface 2.Change to existing interface between ISU and marketflow
cater to 2 new interface 2.change to existing interface between ISU and marketflow A A A A A A A A A A A A A A A A A A A A A
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
1a
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
Assumptions
request except for NTS sites. If received will be rejected
treated as reconfirmation process
will be sent based on agreed default values
failed, rejection will be notified to CSS (VL)
sync
by CSS
Overall Impact
High Marketflow SAP PO
SAP ISU
Gemini SAP BW CMS DES API
Impact
2a
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow SPA Configuration Configuration Code Change Configuration Change Configuration Change Shippers & CSS Provider Shippers & CSS Provider Shippers & CSS Provider 3 New Interfaces (2- CSS Provider, 1-Shipper) 3 New Interfaces (2- CSS Provider, 1-Shipper) 3 New Interfaces (2- CSS Provider, 1-Shipper) 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
new interface between ISU and Marketflow
cater to 3 new interface between ISU and Marketflow A A A A A A A A A A A A A A A A A A A A A
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
2a
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
Assumptions
18:00 hrs
failed, warning will be issued to CSS (SC) with rejection but switch will go live
sequence and will process in batches
will be sent if settlement data is not received by shipper or rejected on re-validation at the time of secured
Overall Impact
High Marketflow SAP PO
SAP ISU
Gemini SAP BW CMS DES API
Impact
1b
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow SPA Configuration Configuration Code Change Configuration Change Configuration Change Shippers & CSS Provider Shippers & CSS Provider Shippers & CSS Provider 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 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)
to cater to 1 new interface 2.Change to existing interface between ISU and marketflow
(AS IS) A A A A A A A A A A A A A A A A A A A A A
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
1b
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
Assumptions
no later than 18:00 hrs
failed, warning will be issued to CSS (SC) with rejection but switch will go live
sequence and processes these in batches
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 Marketflow SAP PO
SAP ISU
Gemini SAP BW CMS DES API
Impact
2b
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow SPA Configuration Configuration Code Change Configuration Change Configuration Change Shippers & CSS Provider Shippers & CSS Provider Shippers & 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 1 Existing to Shippers 1 New FF for shippers 2 New for CSS Provider 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.
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) A A A A A A A A A A A A A A A A A A A A A
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
2b
Change of Shipper Only
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. ➢ CSS can cancel a futuristic change of shipper request with a synchronization message to UK Link to notifying it of the cancellation.
Solution Options:
ile
2a 1a 1b 2b Minimum changes to existing CFR File New interface for Gaining shipper notification Minimum changes to existing TRF, MRI & PAC Files New Interface to combine existing files and remove redundant information Notifications on Receipt of Change of Shipper Event Sync Notifications post Gate Closure on D-1
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
Assumptions
request except for NTS sites. If received will be rejected
with transportation rates derived based on default values
failed, rejection will be notified to CSS
change of shipper only sync
received before gate closure
Overall Impact
High Marketflow SAP PO
SAP ISU
Gemini SAP BW CMS DES API
Impact
1a
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow 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 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
new interface 2.Change to existing interface between ISU and marketflow
cater to 2 new interface 2.change to existing interface between ISU and marketflow A A A A A A A A A A A A A A A A A A A A A
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
1a
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 effective date in ISU and gaining shipper will be notified in new file format inline to the CSS switching requirements which will include settlement details if received or default details that will be applied.
Impacted Systems
Assumptions
request except for NTS sites. If received will be rejected
with transportation rates derived based on default values
failed, rejection will be notified to CSS
change of shipper sync
received before gate closure
Overall Impact
High Marketflow SAP PO
SAP ISU
Gemini SAP BW CMS DES API
Impact
2a
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow SPA Configuration Configuration Code Change Configuration Change Configuration Change Shippers & CSS Provider Shippers & CSS Provider Shippers & CSS Provider 3 New Interfaces (2- CSS Provider 1-Shipper) 3 New Interfaces (2- CSS Provider 1-Shipper) 3 New Interfaces (2- CSS Provider 1-Shipper) 1. New Interface to receive Change
2. New Interface to reject the invalid Sync 3. New interface to gaining shipper
new interface between ISU and Marketflow
cater to 3 new interface between ISU and Marketflow A A A A A A A A A A A A A A A A A A A A A
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
2a
On D-1 post gate closure, gaining shipper will be notified with minimum changes in existing files (TRF/MRI) to accommodate settlement details and losing shipper will be notified in TRF file with ceased responsibility CSS will not send any Change of Shipper sync messages post receipt of request, except for shipper cancellation sync Change of shipper will go effective from the date provided on Change of Shipper Event Sync There is a risk to process multiple files at around same time with redundant information to shippers
Impacted Systems
Assumptions
inline to existing business rules
Gate closure
smooth file flows post gate closure
values will be sent if settlement details are not received by shipper or rejected on re-validation at the time of gate closure
notification
Overall Impact
Medium Marketflow SAP PO
SAP ISU
Gemini SAP BW CMS DES API
Impact
1b
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow SPA Configuration Configuration Code Change Configuration Change Configuration Change Shippers Shippers Shippers 2 - Existing to Shippers 2 - Existing to Shippers 2 - Existing to Shippers 1. TRF/ MRI to gaining shipper with minimum File format changes 2. TRF to Losing Shipper (AS IS) 1. Change to existing interface between ISU and marketflow 2. TRF to losing shipper (AS IS) 1. 1Change to existing interface between ISU and marketflow 2. TRF to losing shipper (AS IS) A A A A G G G G G A A A A A A A A A A A A
1b
Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test?
SPA M 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
1b
2, Notifications post Gate Closure on D-1 - New Interface to combine existing files and remove redundant information
On D-1 post gate closure, gaining shipper will be notified with New File format which will be developed to combine TRF/MRI files along with any details for settlement data. Losing shippers will be notified in TRF file with ceased responsibility. CSS will not send any Change of Shipper sync messages post receipt of request, except for shipper cancellation sync. Change of shipper will go effective from the date provided on Change of Shipper Event Sync.
Impacted Systems
Assumptions
inline to existing business rules
Gate closure
smooth file flows post gate closure
values will be sent if settlement details are not received by shipper or rejected on re-validation at the time of gate closure
notification
Overall Impact
High Marketflow SAP PO
SAP ISU
Gemini SAP BW CMS DES API
Impact
2b
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow SPA Configuration Configuration Code Change Configuration Change Configuration Change Shippers & CSS Provider Shippers & CSS Provider Shippers & CSS Provider 1 Existing to Shippers 1 New FF for shippers 1 Existing to Shippers 1 New FF for shippers 1 Existing to Shippers 1 New FF for shippers 1. New File format to combine the proposing shipper notification 2. TRF to Losing Shipper (AS IS) 1. New File format to combine the proposing shipper notification 2. TRF to Losing Shipper (AS IS) 1. New File format to combine the proposing shipper notification 2. TRF to Losing Shipper (AS IS) A A A A A A A A A A A A A A A A A A A A A
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
2b
Forced / Auto Confirmations
Currently Forced/Auto confirmations are handled within UK Link system. However post CSS implementation, this process will be mastered by CSS. Where a forced / auto confirmation is triggered in UK Link (based on current business rules), UK Link will notify CSS via a new
sync message. The request will be subject to the standard initial registration validation checks by the CSS
Solution Options
Forced / auto confirmation update sync to CSS and response from CSS 1
Any forced/Auto confirmation updates will be notified from UK Link to CSS via new interface and CSS will then initiate Registration Sync request to UKLINK. This will be a cyclic update from UK Link to CSS
Impacted Systems
Assumptions
for any sites in scope based on existing UKLink business process
faster switching timelines for domestic and non-domestic sites
unregistered iGT sites
back of these new interfaces and detailed validations will be defined before detail design phase
UKLink
Marketflow SAP PO SAP ISU
Gemini SAP BW CMS DES API
Impact
1
Overall Impact
Medium
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow SPA Configuration Configuration Code Change Configuration code Configuration Code CSS Provider CSS Provider CSS Provider New interfaces for CSS New interfaces for CSS New interfaces for CSS 2 New Interfaces Functionality within SAP ISU will be build to send Auto confirmation updates to CSS and Rejection response from CSS to ISU 2 New Interfaces System to make the configuration for 2 new interfaces from ISU to CSS and 1 Inbound from CSS to ISU 2 New Interfaces System to make the configuration for 2 new interfaces from ISU to CSS and 1 Inbound from CSS to ISU A A A A A A A A A G G G A A A G G G G G G
1
Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test?
SPA M Y Y 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
1
Shipper Withdrawals
Currently Shipper Withdrawal is received from Shipper via WAO file. However post CSS consequential, WAO files will be decommissioned except for NTS sites. This process will be mastered by CSS.
Solution Options
RMP status update sync to CSS and response from CSS 1
On change of any RMP Status (to Dormant or Terminated), UK Link will notify CSS via new interface ‘SupplyMeterPointSync’. The energy supplier can then initiate the deactivation of their regsitration via the CSS process, this will trigger the registration sync message to update the status of the current supplier (and shipper) registration to "Inactive“.
Impacted Systems
Assumptions
Voluntary Withdrawal except for NTS sites
inactive registration sync
responsibility
based on the mapping structure defined within UKLink
validations will be defined before detail design phase
Marketflow SAP PO SAP ISU
Gemini SAP BW CMS DES API
Impact
1
Overall Impact
Medium
System Component: Development Type: Impacted User(s): Build Type: Change Description: Requirement Clarity: Change Complexity: Integration Complexity: Test Data Prep Complexity: Test Execution: Regression Testing Impact: Performance Impact: SAP ISU SAP PO Marketflow SPA Configuration Configuration Code Change Configuration code Configuration Code CSS Provider CSS Provider CSS Provider New Interfaces for CSS New Interfaces for CSS New Interfaces for CSS 2 New Interfaces - Functionality within SAP ISU will be build to send change of meter point status and its response from CSS to ISU system 2 New Interfaces System to make the configuration for 2 new interfaces from ISU to CSS and 1 Inbound from CSS to ISU 2 New Interfaces System to make the configuration for 2 new interfaces from ISU to CSS and 1 Inbound from CSS to ISU A A A A A A A A A G G G A A A G G G G G G
1
Process Area Complexity File Formats Exceptions External Screens Batch Jobs Performance Test?
SPA M 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
1
High Medium Low
Scale of change
involving majorly new objects
requirements involving mix of new and existing objects
for existing objects
functionality
tuning
tuning
Testing involved
number of testing scenarios (cross stream/downstream impacts)
impacted leading to considerable no. of scenarios needs to tested
less testing
Meter Point Status (status
Isolation status (the ability of the meter to pass gas) Withdrawal status Confirmation status RMP status (as held by CSS) LI N (or blank) N LI Operational LI Y N LI Dormant LI N (or blank) Y LI Operational LI Y Y SU Dormant CA or CL N (or blank) N LI Operational CA or CL Y N LI Dormant CA or CL N (or blank) Y SU Operational CA or CL Y Y SU Dormant DE N (or blank) N LI Terminated DE Y N LI Terminated DE N (or blank) Y SU Terminated DE Y Y SU Terminated EX Y N LI Terminated EX Y Y SU Terminated EX Nil value Y SU Terminated