Framework Contract for the Provision of Non-Code User Pays Services Schedule 2 Services Schedule Change Procedure UPCO003 IAD Transactional Charging

Transcription

1 Framework Contract for the Provision of n-code User Pays Services Raising a Service Change Preparation & Agreeing of EQR Preparation & Agreeing of BER Design and UP Customer raises CO to Approves CO and asks to prepare EQR prepares EQR for Approves EQR and submits BEO to prepares BER for choose and approve BER for ACS and Contract (if applicable) implements chosen makes changes to Schedules and service becomes binding 13/09/10 15/11/10 03/12/10 19/01/11 13/04/11 Guidance tes Process flow diagrams are for illustration and provide only a summary of the Services Schedule Change Procedure within the n-code User Pays Contract. For a more detailed overview of the process please see the contractual documents on the Joint Office website All decisions made by the Relevant Governance Committee ( ) are made in line with their applicable Terms of Reference (also available on Joint Office website) If you require any further information on the above process please contact.userpays@.com Page 1 of 5

2 Framework Contract for the Provision of n-code User Pays Services Section 2 Raising a Service Change UPUC / Member Proposer UP Customer or raises CO to Acknowledge receipt of Change Order Present CO at UPUC(SG) meeting (al) 03/08/10 13/09/10 Discuss CO at 13/09/10 Add CO to next meeting agenda 13/09/10 Customers of CO and Voting Period 27/09/10 5pm Consider CO and tify of Reject CO (begin Change Process) Collate UP Customer Votes, Calculate outcome in line with ToR and tify of outcome Does proposer wish to raise CO to? Inform CO proposer of rejection decision Does UPUC approve CO? Submit a CO to & Request development of EQR 18/08/10 Begins D+1 of Page 2 of 5

3 Framework Contract for the Provision of n-code User Pays Services Sections 3 & 4 Preparing and Agreeing an Evaluation Quotation Report Proposer End Does Proposer wish to re-submit CO following rejection? Submit new CO to Inform Proposer of rejection UPUC / submit CO to and request development of EQR 15/11/10 Discuss EQR at 30/11/10 5pm Consider EQR and tify of Reject EQR Does UPUC / approve EQR? Is there sufficient funding for Development & costs? 03/12/10 UPUC / submits BEO to Can Service Change be reasonably implemented? Agree additional funding Funding creates an EQR EQR must consist of all points listed Section 3 of Schedule 2 of the Contract Present EQR at UPUC Monthly Customers of EQR and associated Voting Period 15/11/10 16/11/10 Begins D+1 of Explain reasoning to UPUC and refer back to Collate UP Customer Votes, Calculate outcome in line with ToR and tify of outcome 02/12/10 Refer EQR back to to agree funding If funding is not agreed between and, any UP Customer can raise an alternate Change Order to recommence the process Page 3 of 5

4 Framework Contract for the Provision of n-code User Pays Services Sections 5 & 6 Preparing and Agreeing a Business Evaluation Report UPUC / Proposer 03/12/10 submits BEO to creates an BER 2-6 weeks 19/01/11 13/04/11 Discuss BER at Present BER at UPUC Monthly BER must consist of all 19/01/11 points stated in Schedule 2, Sections 13/04/ Customers of BER and associated Voting Period Begins D+1 of Consider BER and tify of Reject BER Can Service Change be reasonably implemented? Explain reasoning to UPUC and refer back to End Collate UP Customer Votes, Calculate outcome in line with ToR and tify of outcome Does Proposer wish to re-submit CO following rejection? Inform Proposer of rejection Does UPUC / approve one of s within BER? Submit new CO to Is there sufficient funding for Development & costs? Agree additional funding notifies of approval of BER and chosen Funding Refer BER back to to agree funding If funding is not agreed between UPUC(SG) and, any UP Customer can raise an alternate Change Order to recommence the process Page 4 of 5

5 Framework Contract for the Provision of n-code User Pays Services Sections 7 & 8 Development and, Post Investment Appraisal UPCEG OFGEM Review & Approve ACS Changes (28 days) Review & Approve Contract Changes / Services Schedule UPUC / notifies of approval of BER and chosen ACS Changes Obtain DN & NTS approval Refer Contract UPCEG for consideration Proceed with of chosen Design Option from approved BER Replacement IAD system implemented Acknowledge receipt of chosen design Agree funding Has funding been Service-line changes to be initially drafted. Prices will be added when actual data provided on replacement IAD system Does BER include any required Contract Changes or changes to the ACS? Refer ACS Ofgem for consideration (28 days) Publish any changes to charges 35 days prior to Contract Changes Obtain DN & NTS approval New charging mechanism will be trialled on replacement IAD system for an agreed period to confirm prices prior to of transactional charging Provide ongoing progress reports to UPUC(SG) including timescales & budgets Complete of chosen Design Option Complete post appraisal and provide report to 2-4 weeks Page 5 of 5