Appendix 1 Functional Requirements For the POR ... · Appendix 1 Functional Requirements For the...

Information Services

Appendix 1 Functional Requirements

For the

POR/Consolidated Billing

Initiative

Prepared by: Chris Higgins

Prepared date: 11/07/2014

Information Services Software Requirements Specifications (SRS) POR/Consolidated Billing

of 22

File Name: S:\Procurement\RFPs\2015\rfp 29191 CIS Plus Modifications - POR Consolidated Billing\POR-RFP-Appendix-1-Functional-Requirements-

FINAL.doc

This information is proprietary & confidential - For PGW internal use only

© 2014 PGW. All rights reserved.

Revision Log

Date Revision # Author Change Description

11-07-2014 1.0 Chris Higgins Initial Document

12-04-2014 1.1 Chris Higgins Edits incorporated


of 22

File Name: S:\Procurement\RFPs\2015\rfp 29191 CIS Plus Modifications - POR Consolidated Billing\POR-RFP-Appendix-1-Functional-Requirements-

FINAL.doc



Table of Contents

1 INTRODUCTION ..........................................................................................................................4

1.1 Purpose ............................................................................................................................................. 4

1.2 Scope ................................................................................................................................................ 4

1.3 Definitions, Acronyms, and Abbreviations ...................................................................................... 5

1.4 Document Conventions/Requirements Traceability ........................................................................ 5

2 OVERALL DESCRIPTION ............................................................................................................7

2.1 Product Perspective .......................................................................................................................... 7

2.2 Product Functions and Benefits ....................................................................................................... 7

2.3 Conceptual Diagram ........................................................................................................................ 7

2.4 User Characteristics ......................................................................................................................... 7

2.5 Constraints ....................................................................................................................................... 7

2.6 Assumptions and Dependencies ...................................................................................................... 7

3 SPECIFIC REQUIREMENTS .........................................................................................................8

3.1 Customer Enrollment Eligibility Requirements ............................................................................... 8

3.2 Supplier Participation For Existing Dual-Billing Choice Customers .............................................. 8

3.3 Eligibility Review ............................................................................................................................ 9

3.4 Processing for Entrances and Exits into POR .................................................................................. 9

3.5 Rates (Rate Ready) ........................................................................................................................ 11

3.6 POR Finance and General Ledger Modifications ......................................................................... 12

3.7 Payment remittance to NGS ........................................................................................................... 14

3.8 Non-residential Sales Taxes (Options) .......................................................................................... 15

3.9 BCCS ............................................................................................................................................. 15

3.10 Reporting ....................................................................................................................................... 18

3.11 Cost Recovery Tracking ................................................................................................................ 19

3.12 EDI Transactions List .................................................................................................................... 21

4 DELETED REQUIREMENTS ......................................................................................................22


December 4, 2014 of 22 File Name: S:\Procurement\RFPs\2015\rfp 29191 CIS Plus Modifications - POR Consolidated Billing\POR-RFP-Appendix-1-Functional-Requirements-FINAL.doc



1 Introduction

1.1 Purpose

Pursuant to a settlement reached in Pa. PUC v. Philadelphia Gas Works – Docket No. R-

2008-2073938 and Pa. PUC v. Philadelphia Gas Works – Docket No. R-2009-2139884

Philadelphia Gas Works (PGW) will implement a Purchase of Receivable Program (“POR”)

and Consolidated Billing system. As authorized by Pennsylvania Public Utility Commission

(“PUC”) regulation, in this POR program a natural gas supplier will elect to sell its

receivables to PGW at a discounted rate, for collection by PGW. 52 Pa. Code § 62.224.

These suppliers will be required to use PGW’s Consolidated Billing, through which PGW

will bill customers for the purchased supplier receivables in the regular monthly bill. This

bill will include PGW’s distribution charges, the purchased gas supply charges, and other

relevant charges.

The combined Purchase of Receivables and Consolidated Billing System will be available to

Natural gas suppliers (“NGS”) providing basic gas supply service to Rate GS Commercial

and Industrial customers (using no more than 5,000 Mcf per year) and Rate GS Residential

customers. Participating NGS’ will provide customer enrollment and rate-ready billing data

to PGW through EDI data transfers. PGW will then purchase the recievable from the NGS

at the time of customer billing. PGW will remit payment for the receivable, less the

following discounts:

1. A 2% POR Administrative Discount; plus

2. An Uncollectible Discount, currently: Residential – 4.68%, Commercial – 0.28%,

and Industrial – 0.30%.

Currently, PGW does not have any residential customers who shop for natural gas supply.

PGW’s commercial and industrial customers who are shopping for natural gas supply

currently receive two bills – one from PGW for distribution and other charges, and one from

their natural gas supplier for gas charges. The dual billing program will continue to exist for

some customers. Howerver, it is expected that a number of suppliers will participate in the

POR and Consolidated Billing programs and that this participation will significantly

increase the number of shopping customers, particulary among PGW’s residential and small

business customers.

In order to implement POR and Consolidated Billing, PGW will make significant

modifications to its billing system, BCCS. These modifications will provide the foundation

upon which competitive suppliers can provide alternatives to PGW customers for

commodity supply. PGW utilizes an Electronic Data Interchange (EDI) for data exchanges

with natural gas suppliers.

1.2 Scope

PGW’s objective is to procure vendor services for the modification of the code of the BCCS

application to incorporate the Purchase of Receivables (POR) and Consolidated Billing. The





scope covers the use of the Natural programming language specifically as it relates to

PGW’s BCCS (SPL CisPlus+) application, SysQL, Smalltalk, UNIX Shell scripting and

Oracle Utilities Business Intelligence (OUBI). The project, including development and

Quality Assurance testing, must be completed before the end of July 2015.

1.3 Definitions, Acronyms, and Abbreviations

The table below defines all terms, acronyms, and abbreviations referenced in this SRS.

Term Definition

BCCS Billing Collection & Customer Service system

CB Consolidated Billing

Choice Programming in which customers shop for commodity

through third party suppliers

CRP Customer Responsibility Program

EDI Electronic Data Interchange

MCF One Thousand Cubic Feet

NGS Natural Gas Supplier

PAR Payment Arrangent Customers

POR Purchase of Receivables

PTC Price to Compare

R&CE Restructuring & Consumer Education Surcharge

SA Service Agreement

Shopping Customer Customer who is purchasing commodity through a third party

supplier

1.4 Document Conventions/Requirements Traceability

1.4.1 Traceability

To facilitate forward and backward traceability, all requirements are given a unique

identifier (e.g., 3.1.11.2) that will remain with the requirement throughout the life of this

project (for this software release and all that follow). To maintain these unique identifiers,

requirements are added and deleted as follows:





Added Requirements: Any requirement added after the first approved version of

this SRS is inserted at the end of the appropriate section. The version indicator,

“[vX.X],” appears after the requirement to identify the document version in which

the requirement was added.

Deleted Requirements: For any requirement deleted after the first approved version

of this SRS, the requirement text is replaced by “deleted” and the requirement text is

moved to Appendix A. Deleted Requirements. The unique identifier remains attached

to the deleted requirement in the document.

1.4.2 Prioritizing Requirements

Priority identifiers ([MH], [SH] or [NH]) appear at the end of each requirement.

Requirements are prioritized based on the following definitions:

Must Have [MH]: Essential to the project and must be implemented in an agreed

manner before the system can be released. These requirements are non-negotiable.

Should Have [SH]: Important to the project and should be implemented if at all

possible. Implies that the system is not unacceptable if these requirements are absent.

Nice to Have [NH]: Beneficial to the business/project, but not necessary for the

project to succeed. These requirements are negotiable based on timeline, scope,

risks, and availability of qualified resources.





2 Overall Description

2.1 Product Perspective

Modifications need to be made to existing applications and a new interface screen needs to

be created.

2.2 Product Functions and Benefits

This project is being undertaken to address the settlement mentioned in section 1.1.

2.3 Conceptual Diagram

2.4 User Characteristics

2.5 Constraints

Kubra billing capabilities

Project deadline of end of July 2015

2.6 Assumptions and Dependencies

2.6.1 Assumptions

Any functionality that is outside BCCS will be maintained in .Net Admin screens

2.6.2 Dependencies





3 Specific Requirements

This section contains all software requirements in sufficient detail to enable developers to

design a system to satisfy those requirements and testers to verify that the system satisfies

those requirements.

3.1 Customer Enrollment Eligibility Requirements

3.1.1 Eligibility criteria to be checked at all Choice enrollments and switches.

3.1.2 Rate General Service Commerical & Industrial [MH]

3.1.2.1 Customer annual usage under 5,000 Mcf per year (Rolling 12 months) at time of

switch [MH]

3.1.2.1.1 5,000 Mcf per year will be designed to be a variable amount that can be adjusted

through administration screens. [MH]

3.1.3 All Rate General Service Residential customers regardless of MCF annual usage[MH]

3.1.4 Active linked (to a premise) PGW customer [MH]

3.1.5 Budget Customers are eligible [MH]

3.1.6 Payment Arrangement Customers (PAR) are eligible [MH]

3.1.7 Senior Citizen Discount Customers are eligible [MH]

3.1.7.1 Discount on PGW distribution charges only, not NGS commodity charges [MH]

3.1.8 CRP customers are Not Eligible [MH]

3.2 Supplier Participation For Existing Dual-Billing Choice Customers

3.2.1 Standard EDI Transactions will be used for all communication between the Supplier and

PGW. [MH]

3.2.2 Each supplier will have to elect to be all in (POR/Consolidated billing) or all out for

eligible customers. [MH]

3.2.3 Converting eligible current dual-billing Choice customers to the POR/Consolidated Bill

Program (One time process) [MH]

3.2.3.1 PGW to provide NGSs with current dual-billing customers and 12 months of usage

through EDI [MH]

3.2.3.2 If NGS opts-in, current customers that meet all the criteria outlined in 3.1 will be

converted to POR/Consolidated billing [MH]

3.2.3.2.1 NGS to provide notification of POR participation, BCCS to be updated

accordingly [MH]

3.2.3.2.2 Customers who meet section 3.1 POR criteria will be





3.2.3.2.2.1 Option 1: PGW to drop customer from the current dual-billing enrollment

and send EDI notification of drop & POR enrollment request; or [MH]

3.2.3.2.2.2 Option 2: PGW to auto-convert to POR assuming NGS has separately

established and provided enrollment rates. [MH]

3.3 Eligibility Review

3.3.1 Usage based eligibility criteria shall be reviewed on the anniversary date (most recent

switch date) for all POR/Dual Billing customers. [MH]

3.3.2 Existing Dual-Billing customers

3.3.2.1 If the customer is below 5,000 Mcf and the supplier elects to participate in POR/CB,

then PGW shall drop the customer from dual-billing .

3.3.2.2 For dropped dual-billing customers due to falling within POR usage criteria, PGW

will send EDI to NGS notifying of drop and requesting POR re-enrollment. [MH]

3.3.3 Existing POR/CB customers

3.3.3.1 If the customer is above 5,000 Mcf then PGW shall drop the customer from POR or

convert to dual-billing automatically through EDI (TBD in Design).

3.3.3.2 For dropped POR customers due to exceeding usage criteria, PGW will send EDI to

NGS notifying of drop and reequesting dual-billing re-enrollment. [MH]

3.3.3.3 If the customer enrolls in CRP, PGW to process POR/CB drop and EDI notification.

3.4 Processing for Entrances and Exits into POR

3.4.1 Customer Enrollments

3.4.1.1 NGS to submit enrollment EDI including selected rate [MH]

3.4.1.2 PGW to validate customer POR eligibility based upon section 3.1 [MH]

3.4.1.3 PGW to automatically mail confirmation letter to customer [MH]

3.4.1.4 PGW to wait XX days from the date the confirmation letter is mailed before

initiating switch to NGS rate [MH]

3.4.1.4.1 The wait period to be coded as variable that can be controlled and updated

through POR administrative screens

3.4.1.5 Two options for timing of switch:

3.4.1.5.1 Option 1: If the wait period completes before the 15th

day of the month, the

switch will occur at the next meter-read. If the wait period completes on or after

the 15th

day of the month, the switch will occur at the following month’s meter-

read.

3.4.1.5.2 Option 2: Switch to occur on the first billing cycle after the completion of the

waiting period following mailing of enrollment confirmation letter [MH]





3.4.1.6 Potentially allow for instant connects switching customer to supplier as of their first

PGW billing [SH]

3.4.2 PGW Dropping Customers[MH]

3.4.2.1 Causes/Reasons

3.4.2.1.1 GSC/GSI usage exceeds 5,000 MCF per section 3.1

3.4.2.1.2 Customer requests a drop

3.4.2.1.3 CRSO – Customer Requested Shutoff

3.4.2.1.4 NPSO – Non-Payment Shutoff

3.4.2.2 Drop process

3.4.2.2.1 PGW drops customer from supplier through EDI transaction notifying NGS of

drop[MH]

3.4.2.2.2 PGW to send a letter to the customer confirming drop [MH ]

3.4.2.2.3 Customer will automatically be put back on PGW billing rates for commodity

[MH]

3.4.2.3 Bankruptcies[MH]

3.4.2.3.1 PGW turns off and drops the pre-petition account, establishes a new SA for the

post-petition account [MH]

3.4.2.3.2 PGW to systematically enroll customer with new post-petition account SA with

supplier with no lapse in supplier billing at the pre-existing supplier rate[MH]

3.4.2.3.3 EDI transaction notifying NGS of new customer account number [MH]

3.4.2.4 Customer moves to new PGW service - Option 1[MH]

3.4.2.4.1 PGW will provide the Supplier that served the Customer at the old location with

the Customer’s new service and mailbill address through EDI. [MH]

3.4.2.4.2 PGW will perform drop and NGS notification per 3.4.3.2 above. [MH]

3.4.2.4.3 New service agreement (SA) will utilize PGW commodity rates. [MH]

3.4.2.5 Customer moves to new PGW service – Option 2 [NH]

3.4.2.5.1 PGW will provide the Supplier that served the Customer at the old location with

the Customer’s new service and mailbill address through EDI. [MH]

3.4.2.5.2 PGW to automatically enroll customer’s new SA with pre-existing supplier at the

pre-existing rate with no lapse in supplier billing.

3.4.2.6 If customer moves outside the city and/or does not initiate new PGW service

request:

3.4.2.6.1 PGW will perform drop and NGS notification per 3.4.3.2 above

3.4.2.6.2 If available, PGW will provide the Supplier that served the Customer at the old

location with the Customer’s new mailing or forwarding address [NH]





3.4.3 NGS Drop Customers (due to withdrawal or discontinuance) [MH]

3.4.3.1 EDI transaction from NGS required. [MH]

3.4.3.2 The drop will occur as of the next meter-read date

3.4.3.3 PGW will send a NGS drop letter to the customer [MH]

3.4.3.4 Customer will automatically be put back on PGW billing rates for commodity. [MH]

3.4.3.5 Customer will continue to be billed existing NGS commodity rate until the drop date

which will occur as of the next meter-read date [MH]

3.4.4 Choice Customer Letters

3.4.4.1 Customer Enrollment Letter

3.4.4.2 Notice of Enrollment of Meter Read Error (Potentially two letters depending on

issues)

3.4.4.3 Notice of Customer Cancellation (Within waiting period)

3.4.4.4 Notice of Customer Termination (Customer Drop)

3.4.4.5 Notice of Supplier Termination (Supplier Drop)

3.4.4.6 Notice of Supplier Withdrawal

3.5 Rates (Rate Ready)

3.5.1 NGS will set-up rates via a secure Web portal supplied by PGW [MH]

3.5.1.1 This portal will interface with BCCS and create the new rate in BCCS’s tables [MH]

3.5.1.2 NGS password protection

3.5.2 Each NGS will have the ability to set up multiple rates [MH]

3.5.3 Rate Types [MH]

3.5.3.1 Fixed per MCF rates [MH]

3.5.3.2 Variable per MCF rates[MH]

3.5.3.3 Fixed PTC – Price to compare – percentage off of current PGW rate [MH]

3.5.3.4 Variable PTC – Price to compare – percentage off of current PGW rate [MH]

3.5.4 The current rate in the system will be used at the time of billing. [MH]

3.5.5 Current billing engine will not change [MH]

3.5.6 Rate portal will also include red flag controls/reporting as error check on obvious NGS

rate inputting errors (TBD during Design) [MH]

3.5.7 After rates are established, NGS’ will include the selected rate for each customer at time

of EDI enrollment





3.6 POR Finance and General Ledger Modifications (also see Appendix 2 – Sample T-Accounts)

3.6.1 Choice POR Accounting

3.6.1.1 PGW Bills Customer[MH]

3.6.1.1.1 Debit receivables full billing amount (NGS commodity and PGW distribution

charges and sales taxes)

3.6.1.1.2 Credit PGW distribution charge revenues to new POR revenue GL account

3.6.1.1.3 Credit NGS commodity charges, less POR Admin and Uncollectibles discounts,

to new POR NGS Payables GL account

3.6.1.1.4 Credit Uncollectible discount income as offset to bad debt expense

3.6.1.1.5 Credit POR Admin discounts income to new POR Admin Income GL account

3.6.1.1.6 Credit sales tax(es) as appropriate – see section 3.8

3.6.1.2 Customer pays to PGW [MH]

3.6.1.2.1 Debit cash full payment amount (commodity and distribution charges)

3.6.1.2.2 Credit receivable full payment amount (commodity and distribution charges)

3.6.1.3 PGW pays to NGS [MH]

3.6.1.3.1 Credit NGS commodity charges (and potentially sales taxes per section 3.8), less

POR Admin and Uncollectibles discounts, and less any fees for NGS cancel/re-

bills (see section 3.9.5), to cash

3.6.1.3.2 Debit NGS commodity charges (and potentially sales taxes per section 3.8), less

POR Admin and Uncollectibles discounts, and less any fees for NGS cancel/re-

bills (see section 3.9.5), to new POR NGS payables GL account

3.6.1.4 PGW remits sales tax(es) as appropriate – see section 3.8

3.6.1.4.1 Option 1 - PGW distribution charge taxes for non-exempt customers

3.6.1.4.2 Option 2 - NGS commodity charge taxes for non-exempt customers

3.6.1.4.3 Option 3 – PGW distribution charge taxes and NGS commodity charge taxes for

non-exempt customers

3.6.2 POR Cost and Recovery Accounting (also refer to section 3.11)

3.6.2.1 POR Admin Discount recoveries

3.6.2.1.1 A POR Administrative Discount of 2% of NGS commodity billings will be

charged to suppliers

3.6.2.1.2 This percentage to each supplier will be built as a variable and controlled within

administration screens, variable can be set to 0% [MH]

3.6.2.1.3 100% of POR Admin Discount recoveries booked to new POR Admin Income

GL account

3.6.2.1.4 POR/CB Build – capital project





3.6.2.1.4.1 POR Admin recovery amount for POR/CB Build capped at 10% of project

costs up to $165,800

3.6.2.1.4.2 Credit PGW POR/CB Build capital project account sub 05 reimbursement for

POR Admin Recovery amount

3.6.2.1.5 EDI Build – capital project

3.6.2.1.5.1 POR Admin recovery amount for EDI Build capped at $35,000

3.6.2.1.5.2 Credit PGW EDI Build capital project account sub 05 reimbursement for

POR Admin Recovery amount

3.6.2.1.6 POR Operating Costs (see section 3.11)

3.6.2.1.6.1 All POR Admin operating costs booked to new POR Admin Income GL

account

3.6.2.1.6.2 Journal Entries to be placed in department budgets where POR Admin

recovery costs are incurred to off-set these operating costs

3.6.2.2 R&CE Surcharge Recoveries (see section 3.11)

3.6.2.2.1 No need for new GL accounts

3.6.2.2.2 R&CE surcharge recoveries to be treated same as other PGW surcharge revenues

3.6.2.2.3 PGW to develop BCCS/ Excel reports to be developed for cost & recovery

tracking

3.6.3 Uncollectibles

3.6.3.1 Uncollectible Discount will be charged to the NGSs: [MH]

3.6.3.1.1 Residential – 4.68% [MH]

3.6.3.1.2 Commercial – .28% [MH]

3.6.3.1.3 Industrial – .30% [MH]

3.6.3.2 This percentage to each supplier will be built as a variable and controlled within

administration screens [MH]

3.6.4 Create new POR GL account number(s) [MH]

3.6.4.1 PGW POR revenue GL account (distribution charges) [MH]

3.6.4.2 PGW uncollectibles offset to bad debt expenses – Single GL account for all rate

classes [MH]

3.6.4.3 PGW POR Admin Income GL account [MH]

3.6.4.4 POR NGS payables GL account - Single account for all participating NGS’

(supported by report for payments by NGS) [MH]

3.6.4.5 Shopping write-off reactivation SAs GL account [MH]

3.6.4.6 New Other Revenue GL account for NGS cancellation fees [MH]





3.7 Payment remittance to NGS

3.7.1 PGW will remit payment for the receivable on the 25th

day of the month following the

billing month [MH]

3.7.2 NGS must first register for PayMode in order for PGW to make electronic payments;

PGW will also first need NGS Tax ID #s (W9 form) [MH]

3.7.3 Net payment to each supplier will be calculated based on their commodity billings minus

the following discounts: [MH]

3.7.3.1 Administrative Discount [MH]

3.7.3.2 Uncollectible Discount [MH]

3.7.3.3 Cancel/Re-bill charges

3.7.4 BCCS Payment Mechanism [MH]

3.7.4.1 Establish new BCCS NGS accounts for POR payment purposes [MH]

3.7.4.1.1 Option #1 – Utilize existing BCCS NGS accounts used for billing (Cycle 30)

3.7.4.1.2 Option #2 – Establish new BCCS NGS accounts for POR payments

3.7.4.2 At Billing systematically create transactions to transfer the payables to the A/R

supplier account. To occur daily after billing, bringing accounts payable to $0 every

night [MH]

3.7.4.3 At revenue month end identify/aggregate appropriate daily A/R supplier transfers

associated with the prior revenue month & create “refund” adjustment [MH]

3.7.4.4 This NGS payment transaction will be picked up by APEX [MH]

3.7.4.4.1 Modify APEX to not cut daily check for these daily transactions [MH]

3.7.4.4.2 APEX will automatically pick-up revenue month end amounts for ACH

payments

3.7.4.4.3 APEX file transfer from BCCS to Oracle A/P to start payment process [MH]

3.7.4.4.4 A/P to receive & review APEX file; [MH]

3.7.4.4.4.1 Submit file report via email to business for approval; (email to include e-

signature functionality for authorization) [MH]

3.7.4.4.4.2 A/P to approve APEX file; automatically sent to Treasury;

3.7.4.4.4.3 Treasury runs ACH payment process [MH]

3.7.4.4.4.4 Oracle to send file back to BCCS to document on NGS payment account that

payment was remitted (currently in place for checks, need to introduce this

payment ID field/process for POR ACH payment process) [MH]

3.7.4.5 An NGS payment will then be sent to each Supplier via wire to ensure timeline,

appropriate EDI notifications be transmitted. [MH]





3.8 Non-residential Sales Taxes (Options)

3.8.1 Final Design to be based on implementing one of the following four options regarding

Sales Taxes:

3.8.1.1 Do not tax distribution for POR (Option #1)

3.8.1.1.1 Remit commodity taxes to the supplier

3.8.1.2 Do not tax distribution for POR (Option #2)

3.8.1.2.1 Remit commodity taxes to the Commonwealth

3.8.1.3 Tax distribution for POR (Option #3)

3.8.1.3.1 Remit commodity taxes to the Commonwealth

3.8.1.4 Tax distribution for POR (Option #4)

3.8.1.4.1 Remit commodity taxes to the supplier

3.9 BCCS

3.9.1 POR Choice Setup [MH]

3.9.1.1 All enrollments are SA/premise/service point level within the BCCS. [MH]

3.9.1.2 New POR Choice SA type will be required [MH]

3.9.1.3 Write-off reactivations for POR Choice customers will require a new SA [MH]

3.9.1.4 Capture & store risk based score at time of each switch [MH]

3.9.2 NGS Rates

3.9.2.1 Rates to be captured through PGW-NGS rate screen interface

3.9.2.2 Rates to be established in BCCS

3.9.2.3 POR Customers to be enrolled with pre-established NGS rate, customer rate data to

be stored within BCCS so as to:

3.9.2.3.1 Identify accurate NGS rate for billing

3.9.2.3.2 Maintain current rate class & customer class identification

3.9.3 PGW Choice Customer Bill [MH]

3.9.3.1 POR & Dual-Billing Billing Summary - No need to change [MH]

3.9.3.2 POR/CB bills Supply Charges [MH]

3.9.3.2.1 NGS POR charges as line-item replacing GCR charge line-item within existing

billing section, does not require new section[MH]

3.9.3.2.2 NGS name must be included on the NGS charges lin [MH]

3.9.3.3 POR/CB bills NGS Information [MH]

3.9.3.3.1 Insert “Your Natural Gas Supplier” section on page 1 to include the following:

NGS Name, Address, Phone, and internet address





3.9.3.3.2 Should appear consistent with existing NGS contact information section in

current PGW dual-billing bill [MH]

3.9.3.4 For both Choice POR/CB bills & Dual-billing bills, update “Natural Gas Supplier”

section on page 2:

3.9.3.4.1 First sentence to be modified to: “If you have selected a Natural Gas Supplier

other than PGW, the Natural Gas Supplier is responsible for the billing of

Natural Gas Supplier charges, unless your charges are consolidated on your

PGW bill.” [MH]

3.9.3.4.2 The remainder of this section to remain as is for both Dual-Billing and POR bills

3.9.3.5 Messaging [MH]

3.9.3.5.1 Update heading for existing Message Center section to be called PGW Messages

[MH]

3.9.3.5.2 Add new message section, to be called Supplier Messages, below PGW

Messages for NGS-specific messaging to be received from suppliers through

EDI. The supplier message section will consist of 4 lines of up to 100 characters

per line. A blank line counts as 100 characters. [MH]

3.9.3.5.3 Any PGW supplied general Choice messages will be processed through the

current Kubra process and placed on the bill. [MH]

3.9.3.6 Additional shopping information

3.9.3.6.1 Optional - Include supplier logo for shopping customers (per PUC Gas RMI

proceeding). [SH]

3.9.3.6.1.1 Black and white in JPEG format.

3.9.3.6.1.2 Location to be placed on page one next to new Your natural gas supplier

section, see 3.9.3.3

3.9.3.6.1.3 Standard size to be established

3.9.3.6.2 Optional - Additional option to include shopping information box on all

customer bills(Per PUC Gas RMI proceeding). [SH]

3.9.3.6.2.1 Information includes customer’s account number, customer’s rate class, and

additional copy required by PUC in the Electric RMI.

3.9.3.6.2.2 Separate section to be located at the end of the bill.

3.9.4 Payment distribution methodogy towards oldest debt remains the same

3.9.4.1 All payments go to oldest (including pre- current shopping status) arrearage

3.9.4.2 Appropriate as without sufficient payments, current supply will be unpaid;

3.9.5 Cancelling and Re-Billing [MH]

3.9.5.1 Cancel/Re-bills due to PGW error;





3.9.5.1.1 No changes to PGW Cancel/Re-bill process [MH]

3.9.5.1.2 EDI communications to the supplier [MH]

3.9.5.1.2.1 Usage

3.9.5.1.2.2 Billing information [MH]

3.9.5.2 Mass cancels [MH]

3.9.5.2.1 No changes to PGW process

3.9.5.2.2 No mass cancels on behalf of suppliers [MH]

3.9.5.3 NGS requested cancel & re-bills: [MH]

3.9.5.3.1 Supplier to initiate EDI rate change for specific customer(s) prospective bills.

[MH]

3.9.5.3.2 Manual communication from supplier to PGW to notify of retroactive rate

error.[MH]

3.9.5.3.3 PGW to perform manual cancel – re-bill [MH]

3.9.5.3.4 PGW to manually enter a customer contact [MH]

3.9.5.3.5 PGW to charge NGSs for billing errors and delays [MH]

3.9.5.3.5.1 The fee will automatically be created on the suppliers account

3.9.5.3.5.2 Fee would be variable that can be adjusted through administrative screens

3.9.5.3.5.3 Total of all adjustments will be netted from the monthly payment that is paid

to the supplier on the 25th

of the month

3.9.6 BCCS Customer contacts

3.9.6.1 POR/CB enrollment - systematic

3.9.6.2 POR/CB drop (including cause) - systematic

3.9.6.3 POR/CB Supplier cancel/re-bill - manual

3.9.7 Interfaces [MH]

3.9.7.1 Rate screens [MH]

3.9.7.1.1 Mechanism for supplier to enter and maintain their rates in BCCS [MH]

3.9.7.1.2 NGS data entry error protocols to be developed [MH]

3.9.7.2 Admin screens [MH]

3.9.7.2.1 All BCCS data to be maintained in the character soft tables [MH]

3.9.7.2.2 Any functionality that is outside BCCS will be maintained in .Net admin screens

[MH]





3.9.7.2.3 Admin screens to provide control of adjustable variables: POR/CB usage

eligibility threshold; Choice enrollment waiting period; POR Admin Discount;

Uncollectibles Discount; NGS Cancel/Re-bill fees

3.9.7.3 Kubra interface (See section 3.9.3)[MH]

3.9.7.3.1 Updates required for the print file that is sent to Kubra for billing [MH]

3.9.7.3.2 New mapping required for customer billing [MH]

3.9.7.4 EDI [MH]

3.9.7.4.1 All EDI transactions will be formatted through our current vendor (Seeburger)

[MH]

3.9.8 Impact on Budget Billing and PAR [MH]

3.9.8.1 Remit payment to NGS based on actual billings, regardless of Budget Billing or

PARs (Based on usage not asked to pay) [MH]

3.9.8.2 Budget is currently reviewed quarterly based on GCR quarterly updates [MH]

3.9.8.3 For POR customers on a budget the review process will be one of the following two

options [MH]

3.9.8.3.1 Continue with current quarterly reviews; or [MH]

3.9.8.3.2 Review budget each time NGS rate changes for customer in addition to their

quarterly review (based on their start date) [MH]

3.9.8.3.3 Need to update communications to customers that budget is likely to change

more often if on supplier variable rate. This communication will be through Bill

Message or a separate letter. [MH]

3.10 Reporting

3.10.1 New Reports

3.10.1.1 Shopping customer bill comparison (against PGW PTC) [MH]

3.10.1.2 Variable rates

3.10.1.2.1 Variability [MH]

3.10.1.2.2 Impact on Customer bills [MH]

3.10.1.2.3 Impact on PGW collections [MH]

3.10.1.2.4 Impact on budget billing

3.10.1.3 Uncollectible Metrics

3.10.1.3.1 Track all uncollectibles for POR shopping customers vs. non-shopping

customers at the SA/premise level [MH]

3.10.1.3.1.1 Uncollectibles defined based on PGW write-offs





3.10.1.3.1.2 SA write off amounts will be captured at the time the account is

written off [MH]

3.10.1.3.2 Monthly report providing cumulative data from POR launch through the end of

current month [MH]

3.10.1.3.3 Additional report over twelve and twenty-four month rolling reporting period

[MH]

3.10.1.3.4 Breakout by POR shopping status and all rate classes [MH]

3.10.1.3.5 Aggregate all shopping SA write-offs and non-shopping SA write-offs [MH]

3.10.1.3.6 POR Uncollectibles

3.10.1.3.6.1 Numerator: Total POR SA write-off amounts

3.10.1.3.6.2 Denominator: POR SA Utility revenues + NGS payables + POR bad

debt expenses + POR Admin Income (Total POR Billings)

3.10.1.3.7 Non-Shopping Uncollectibles

3.10.1.3.7.1 Numerator: Total Non-Shopping SA write-off amounts

3.10.1.3.7.2 Denominator: Non-Shopping SA Utility revenues (Total Non-

Shopping Billings)

3.10.1.4 Sales taxes: Compare NGS info provided on customer tax status & percentages

against PGW data [MH]

3.10.1.5 POR Costs & Recoveries

3.10.1.5.1 Total PORAdmin discount recovery [MH]

3.10.1.5.2 Start accumulating with “Go Live”/Start of Recoveries [MH]

3.10.1.5.3 Historical monthly incremental and cumulative recoveries [MH]

3.10.1.6 Monthly and Cumulative POR Participation Report [MH]: Customer participation,

usage, total commodity billings, Admin discount, Uncollectible discount

3.10.2 Updates to existing reports (e.g., A1, GSR, Waterfall, etc.)

3.11 Cost Recovery Tracking

3.11.1 Cost of Implementation (Five total POR/CB Cost Categories)

3.11.1.1 EDI Build

3.11.1.1.1 Recovery cap: EDI implementation cost: $35,000; fully spent

3.11.1.1.2 Timing: Completed by time of go-live, no further costs incurred

3.11.1.1.3 Recovery source: 100% cost recovery through POR Admin Discount





3.11.1.1.4 Cost tracking (capital project): Vendor fees

3.11.1.2 EDI Transactional Fees:

3.11.1.2.1 Recovery cap: Annual recovery amounts capped based on annual unique

customer enrollment/switch rates

3.11.1.2.1.1 If <= 50,000 unique enrollment/switches within a year, the recovery

amount shall be $65,000

3.11.1.2.1.2 If > 50,000 unique enrollment/switches within a year, the recovery

amount shall be $65,000 plus an additional $1.30 per unique

enrollments/switches for all POR unique enrollments/switches greater than

50,000 within a year

3.11.1.2.2 Recovery source: 100% cost recovery through POR Admin Discount for initial

three years from go-live date

3.11.1.2.3 Timing: Costs and recoveries to begin at POR/CB go-live, both will be ongoing

at least through current three year recovery period

3.11.1.2.4 Cost tracking (operating costs): Vendor fees

3.11.1.3 Billing O&M cost:

3.11.1.3.1 Recovery cap: Up to $108,000 total for initial three years from go-live date [MH]

3.11.1.3.2 Recovery source: 100% POR Admin Discount

3.11.1.3.3 Timing: Costs and recoveries to begin at POR/CB go-live, both will be ongoing

at least through current three year recovery period

3.11.1.3.4 Cost tracking (operating costs):

3.11.1.3.4.1 Vendor fees

3.11.1.3.4.2 PGW Operating Labor

3.11.1.4 POR/CB Build

3.11.1.4.1 Recovery cap: Up to $1,658,00

3.11.1.4.2 Recovery source:

3.11.1.4.2.1 POR Admin Discount: 10% of total project costs, up to $165,800

3.11.1.4.2.2 PGW R&CE surcharge: 90% of total project costs, up to $1,492,000

3.11.1.4.3 Timing: Completed by time of go-live, no further costs incurred

3.11.1.4.4 Cost tracking (capital project):

3.11.1.4.4.1 Vendor fees (POR/CB developer & billing vendor)

3.11.1.4.4.2 PGW Operating Labor

3.11.1.5 POR Marketing:

3.11.1.5.1 Recovery cap: Up to $1,000,000 total

3.11.1.5.2 Recovery source:





3.11.1.5.2.1 POR Admin Discount: 50% of total project costs, up to $500,000

3.11.1.5.2.2 PGW R&CE surcharge: 50% of total project costs, up to $500,000

3.11.1.5.3 Timing: Majority of costs incurred before go-live, some may occur after go-live

3.11.1.5.4 Cost tracking (operating costs): Vendor fees

3.11.2 POR/CB Recovery Sources

3.11.2.1 R&CE Surcharge

3.11.2.1.1 Total R&CE cost recovery cap: up to $1,992,000 [MH]

3.11.2.1.1.1 POR/CB Build: 90% of total project costs, up to $1,492,000

3.11.2.1.1.2 POR Marketing: 50% of total project costs, up to $500,000

3.11.2.1.2 To be recoverd through the distribution rate across all firm customers [MH]

3.11.2.1.3 R&CE recoveries to be treated same as other PGW surcharge revenues [MH]

3.11.2.1.4 PGW to develop BCCS/Excel reports for cost & recovery tracking [MH]

3.11.2.2 POR Admin Discount

3.11.2.2.1 Total POR Admin Discount recovery cap: based on POR activity levels

3.11.2.2.1.1 EDI Build: up to $35,000

3.11.2.2.1.2 EDI Fees: capped based on activity levels

3.11.2.2.1.3 Billing System O&M: Up to $108,000 total over three years

3.11.2.2.1.4 POR/CB Build: 10% of total project costs, up to $165,800

3.11.2.2.1.5 POR Marketing: 50% of total project costs, up to $500,000

3.11.2.2.2 To be recovered as 2% discount on NGS’ POR commodity billings

3.11.2.2.2.1 Percent discount will be built as a variable controlled within

administration screens, can be set to 0%.

3.11.2.2.2.2 To be tracked and reported per sections 3.6 and 3.10

3.12 EDI Transactions List

3.12.1 867 : Historical usage, Monthly usage [MH]

3.12.2 814 : Enrollment, Drop, Change, Reinstatement, Advance Notice of Intent to Drop. [MH]

3.12.3 810 : Invoice. ESP/LDC Consolidated Bill [MH]

3.12.4 820 : Payment/Remittance [MH]

3.12.5 568 : Collections [MH]

3.12.6 248 : Write-off [MH]

3.12.7 824 : Application Advice [MH]

3.12.8 Any additional EDI message needs identified in design.





4 Deleted Requirements

The following table contains all requirements marked as “deleted” in section 3 of this

document.

Unique Identifier Original Requirement Text

Appendix 1 Functional Requirements For the POR ... · Appendix 1 Functional Requirements For the...

Documents

Transcript of Appendix 1 Functional Requirements For the POR ... · Appendix 1 Functional Requirements For the...