1 / 7

PNUNC AMR3 Topic Workgroup 12 th May, 2010.

PNUNC AMR3 Topic Workgroup 12 th May, 2010. Transporter response to actions.

caldwell-dunlap
Download Presentation

PNUNC AMR3 Topic Workgroup 12 th May, 2010.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PNUNC AMR3 Topic Workgroup 12th May, 2010.

  2. Transporter response to actions. • AMR004: Transporters (CW) to provide supporting justification as to why, and what type of AMR asset information they believe they would require in a future unbundled solution and whether or not it is appropriate for them to specify AMR equipment standards

  3. Transporter response to actions • AMR005: …consider what constitutes an appropriate upper threshold level for DM Mandatory sites and whether more rigorous business rules will be needed in the unbundled world.

  4. Transporter requirements for AMR information in an unbundled DM regime • Current requirements: • Information provided split into Firm and Interruptible Supply Points • 6 a.m. daily read • Hourly reads provided every 4 hours • Daily data • Required for energy settlement/allocation • FTi • Hourly data • Required for system operation (incl emergency & interruption management) • Re-sync information resulting from maintenance & or fault investigation.

  5. Transporter requirements for AMR information in an unbundled DM regime • Inappropriate for Transporters to be specifying equipment standards.

  6. DM eligibility • No aspiration to amend DM mandatory threshold which appears optimal. • Business rules anticipated to be more rigorous than DME given: • requirement for ‘within day’ data • implications to the industry of non-receipt of accurate and timely reads for daily settlement.

  7. Possible next steps • DM data requirements ‘wider’ and more complex than the issues identified under Project Nexus • Unbundling benefits could in principle be realised ahead of Project Nexus timescales subject to appropriate funding • Consideration should be given to progress initiative as separate development outside of Project Nexus remit • Could be UNC Modification Proposal raised for development within UNC Distribution Workstream? • Scope to address all aspects of existing DM regime (DMM, DMV, telemetry, etc).

More Related