mod0700 extraordinary dsg
play

MOD0700 - Extraordinary DSG 27 th August 2019 AUGE Set new weighting - PowerPoint PPT Presentation

MOD0700 - Extraordinary DSG 27 th August 2019 AUGE Set new weighting factors for UIG Extract from Class 3 Supply Point Migration Workshop: https://www.xoserve.com/news/class-3-supply-point-migration-workshop-actions- and-next-steps/ Impact of


  1. MOD0700 - Extraordinary DSG 27 th August 2019

  2. AUGE Set new weighting factors for UIG Extract from Class 3 Supply Point Migration Workshop: https://www.xoserve.com/news/class-3-supply-point-migration-workshop-actions- and-next-steps/

  3. Impact of weighting factors • A significant number of class 4 sites in EUC1 and EUC2 that could potentially benefit from moving to a class 3 product. • Increase in class changes prior to the effective date of change. • Class 3 sites are daily read and therefore could increase the number of daily reads. • This could impact UK Link and it’s ability to process the reads.

  4. MOD0700 • MOD0700 has been introduced to look at implementing changes to minimise impact of mass migration of EUC 1 Supply Points into Class 3 product, specifically: – Number of class changes processed – Number of reads being processed through to read validation

  5. Scope of MOD700 Requirements Modifications required to existing PAR reports (Read Submission and Read Validation) Reporting New “Batch” Process Reconciliation ASP/AML Billing Read Read Class Change Read Submission Read Validation Staging Selection (SPC File) - Significant Increase - Significant increase D+10 Rule - To reduce the number of reads in read submissions in number of submitted that are processed through to expected class - UNC changes to read validation changes processed specify weekly (7 day) - Specifically limiting 1 read per Shipper or less batch through SPC file Batch to move through to read validation - To monitor and limit submissions of reads. and down stream processing the number of class changes Significant Moderate No Change Change Change

  6. Class Change - SPC File SPC File RT_S34_MRF_AND_BATCH_FREQ_CHANGE_REQUEST 1000 Record Limit RT_S35_CANCEL_MRF_AND_BATCH_FREQ_CHANGE_REQ 1000 Record Limit RT_S36_SMP_CAPACITY_CHANGE_REQ 1000 Record Limit RT_S37_CANCEL_SMP_CAPACITY_CHG 1000 Record Limit Record Type RT_C38_CLASS_CHANGE 1000 Record Limit RT_C39_CLASS_CHANGE_CANCELLATION 1000 Record Limit RT_U80_NTS_OPT_RATE_CHANGE 1000 Record Limit RT_U81_NTS_OPT_RATE_CANCEL 1000 Record Limit • The above provides a view of the SPC file structure • Each record type has a limit of 1000 records, meaning the maximum number of records within a single SPC file is 8,000 if all allowable record were utilised (FIL000018) • Vast majority of records contained within a BAU SPC file are C38’s (Class Change) • SPC file max processing capacity is currently set at 26,000 within the UK Link IS Service Definition document

  7. How to Determine SPC Limit? • The method for defining the limit it not yet confirmed but will need to take into consideration the following: – Processing of SPC files for non class change activities (so not effected by MOD700) – Max number of SPC files that can be processed though AMT and SAP ISU – Customer forecasts for class changes currently being provided to Customer Advocates, 2 way communication regarding peek system times will also take place • Please also note: – Files that pass AMT validation but result in breach of allocation shall be rejected back to the submitting Shipper, however the mechanism for this has not yet been agreed (Email or UK Link Communication (IX)) – Likely that SPC max submissions within the UK Link IS Service Definition document will be increased, however this has not yet been agreed

  8. Read Submission to Read Validation Overview Read Pending * Inner EUC 1 Validation (P) Tolerance All reads passed through to Opening validation read validation Reads, (EUC1) may be Replacement removed Reads (inc Class Read Accepted Change) • Shipper preferred read prioritised (if Validation Reads (U) present) Reads with a EUC 2-9 All • If the Shipper preferred read fails or TTZ > 1 Reads is not available within the batch passed to read validation then the last read will be selected Reads that fail from the batch validation will • If last read fails then the next be rejected UBR Read available read is selected (if no Reads that Shipper preferred read is contained D+10 Pending pass Read within the batch) Validation Validation (E) Validation • Only 2 attempts to validate a are marked reading will be carried out from a as Uploaded Shipper batch Reads in a batch outside of D+10 will be Remaining Reads that rejected Assured (A) EUC 1 cyclic aren't selected within the reads batch are marked as Unassured (N) Assured or Not Assured Reads and will count towards read performance Rejected Reads (F)

  9. Scenario 1a: First Read Accepted (No Shipper Preferred Read) Read Read Staging Submission Area Step 1: D+10 check Reads older than D+10 E F E F E F E E E E E E E E E E Rejected and set to “F”, other UBR reads are marked as “E” Shipper Step 2: Read Selection Submits No Shipper preferred read present so latest E E E E E E E E E E E read is selected for Read Validation step Batch of Reads Step 3: Read Validation Selected read passes Read Validation and U E A E A E A E A E A E A E A E A A E E set to “U” for further processing into UKL, all other reads within the batch set to “A” F = Rejected E = Pending for Upload U = Uploaded/Accepted A = Assured N = Not assured

  10. Scenario 1b: Shipper Preferred Read Accepted Read Read Staging Submission Area Step 1: D+10 check Reads older than D+10 E F E F E F E E E E E E E E E E Rejected and set to “F”, other UBR reads are marked as “E” Shipper Step 2: Read Selection Submits Shipper preferred read is selected for Read E E E E E E E E E E E Validation step Batch of Reads Step 3: Read Validation Selected read passes Read Validation and E A U E E E A E A E A E A E A E A A E A E set to “U” for further processing into UKL, all other reads within the batch set to “A” F = Rejected E = Pending for Upload U = Uploaded/Accepted A = Assured N = Not assured

  11. Scenario 2a: First Read Failed, Second Read Accepted Read Read Staging Submission Area Step 1: D+10 check Reads older than D+10 E F E F E F E E E E E E E E E E Rejected and set to “F”, other UBR reads are marked as “E” Shipper Step 2: Read Selection Submits No Shipper preferred read present so latest E E E E E E E E E E E E read is selected for Read Validation step Batch of Reads Step 3: Read Validation Selected read fails Read Validation “F”, next read E A E A E A E A E A E A A E A E U E E E E F passes and is set to “U” for further processing into UKL, all other reads within the batch set to “A” F = Rejected E = Pending for Upload U = Uploaded/Accepted A = Assured N = Not assured

  12. Scenario 2b: First Read Failed (Shipper Preferred), Second Read Accepted Read Read Staging Submission Area Step 1: D+10 check Reads older than D+10 E F E F E F E E E E E E E E E E Rejected and set to “F”, other UBR reads are marked as “E” Shipper Step 2: Read Selection Submits Shipper preferred read is selected for Read E E E E E E E E E E E E Validation step Batch of Reads Step 3: Read Validation Selected read fails Read Validation “F”, next read E A E A E A E A E E F E A E A A E A E E U E E passes and is set to “U” for further processing into UKL, all other reads within the batch set to “A” F = Rejected E = Pending for Upload U = Uploaded/Accepted A = Assured N = Not assured

  13. Scenario 3: Both Selected Reads Fail Read Read Staging Submission Area Step 1: D+10 check Reads older than D+10 E F E F E F E E E E E E E E E E Rejected and set to “F”, other UBR reads are marked as “E” Shipper Step 2: Read Selection Submits Shipper preferred read or latest read (where E E E E E E E E E E E E no preferred read is present/specified) is Batch of selected for Read Validation step Reads Step 3: Read Validation Selected reads fail Read Validation and are set to E N E N E N N E N E E N E N N E F E E E F E “F”, no further reads are considered for processing into UKL, all other reads within the batch set to “N” F = Rejected E = Pending for Upload U = Uploaded/Accepted A = Assured N = Not assured

  14. Scenario 4: Both Selected Reads Fail, Batch Re- Submitted, Read Accepted Read Read Staging Submission Area Step 1: D+10 check Reads older than D+10 E F E F E F E F E F E F E E E E E E E Rejected and set to “F”, other UBR UBR reads are marked as “E” Shipper Re- Shipper Step 2: Read Selection Submits Submits Shipper preferred read or latest read (where E E E E E E E E E E E E no preferred read is present/specified) is Batch of Batch of selected for Read Validation step Reads (D+3) Reads Step 3: Read Validation Selected reads fail Read Validation and are set to E A N E N A E A N N E A N E A E N A E N A A N E A F E E E U F E “F”, no further reads are considered for processing into UKL, all other reads within the batch set to “N” F = Rejected E = Pending for Upload U = Uploaded/Accepted A = Assured N = Not assured

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend