PHILADELPHIA GAS WORKS REQUEST FOR ......2014/10/07 · Philadelphia Gas Works – Request For...

PHILADELPHIA GAS WORKS

REQUEST FOR PROPOSALS

FOR

INTEGRATED GAS MANAGEMENT SYSTEM (IGMS)

Dated: October 7, 2014 RFP NO.: 28946

Table of Contents

1 THE SOLICITATION – NOTICE TO PROPOSERS ............................................................ 4

1.1 SCHEDULE OF EVENTS ........................................................................................................... 4

1.2 PROPOSAL REQUIREMENTS .................................................................................................... 5

2 PROJECT DEFINITION AND REQUIREMENTS ............................................................... 6

2.1 OVERVIEW ............................................................................................................................. 6

2.2 SERVICES TO BE PROVIDED; SCOPE OF WORK ........................................................................ 7

2.3 TERM..................................................................................................................................... 8

2.4 PROPOSAL PRICING ............................................................................................................... 8

2.5 PROPOSER/PERSONNEL MINIMUM REQUIREMENTS .................................................................. 8

2.6 LICENSING ............................................................................................................................. 9

2.7 INFORMATION/PRODUCT ......................................................................................................... 9

2.8 CONFIDENTIALITY ................................................................................................................... 9

2.9 MINORITY PARTICIPATION ..................................................................................................... 10

2.10 INSURANCE .......................................................................................................................... 10

2.11 INDEMNIFICATION ................................................................................................................. 12

2.12 CERTIFICATE OF NON-INDEBTEDNESS ................................................................................... 13

2.13 NON-DISCRIMINATION .......................................................................................................... 13

2.14 MACBRIDE PRINCIPLES ........................................................................................................ 14

2.15 GOVERNING LAWS ............................................................................................................... 14

2.16 CERTAIN REQUIRED DISCLOSURES ....................................................................................... 14

3 INSTRUCTIONS TO PROPOSERS ................................................................................. 16

3.1 PROPOSAL PREPARATION REQUIREMENTS ............................................................................ 16

3.2 DURATION OF PROPOSAL ..................................................................................................... 18

3.3 PROPOSER’S RESPONSIBILITY .............................................................................................. 18

4 PROPOSER INFORMATION ........................................................................................... 20

4.1 PROPOSER .......................................................................................................................... 20

4.2 QUALIFICATIONS STATEMENT ............................................................................................... 20

4.3 BUSINESS EXPERIENCE ........................................................................................................ 21

4.4 FINANCIAL INFORMATION ...................................................................................................... 23

4.5 GENERAL LITIGATION DISCLOSURE ....................................................................................... 25

4.6 BUSINESS ORGANIZATION STATEMENT.................................................................................. 25

4.7 WARRANTIES BY PROPOSER ................................................................................................ 29

5 PROPOSAL EVALUATION, NEGOTIATION AND CONTRACT AWARD ........................ 31

5.1 DISQUALIFICATION OF PROPOSERS ....................................................................................... 31

5.2 QUALIFICATION OF PROPOSERS ............................................................................................ 31

5.3 GENERAL RESERVATION OF RIGHTS ..................................................................................... 31

5.4 AWARD ................................................................................................................................ 34

ATTACHMENT D. REQUIRED 17-1400 DISCLOSURE ......................................................... 35

ATTACHMENT I. DEMOGRAPHIC SURVEY ......................................................................... 37

APPENDIX 1. REQUIREMENTS ............................................................................................. 39

APPENDIX 2. DEVELOPMENT STANDARDS ........................................................................ 75

Philadelphia Gas Works – Request For Proposals INTEGRATED GAS MANAGEMENT SYSTEM (IGMS)

of 77

APPENDIX 3. TESTING AND ACCEPTANCE STANDARDS .................................................. 76


of 77

1 The Solicitation – Notice to Proposers

Notice is hereby given that Philadelphia Gas Works (“PGW”) will receive sealed proposals on or before November 14, 2014, 2:30 p.m. Eastern Time, at the PGW Supply Chain Department, 800 W. Montgomery Avenue, Philadelphia, Pennsylvania 19122, for a comprehensive Integrated Gas Management System (IGMS).

This document outlines PGW’s objectives, describes the general characteristics of the services to be provided, and (without being exhaustive) outlines the principal obligations of PGW and the selected Proposer.

Questions concerning this Request for Proposals shall be directed in writing towards Barbara Thomas, PGW Supply Chain Department, e-mail: [email protected] (with a copy to [email protected]), or PGW Supply Chain Department, 800 W.

Montgomery Avenue, Philadelphia, Pennsylvania 19122. Proposers may not contact

other PGW personnel regarding this RFP.

1.1 Schedule of Events

The projected schedule of events for this Request for Proposals is as follows:

Issue Date of the RFP ................................................................ October 7, 2014 Questions and requests for clarification or information must be received, in writing, at the office of the person listed above by 5 p.m. (EST) ...................................................... October 21, 2014 Mandatory Telephone Conference, 10:00 a.m. .......................... November 6, 2014 Proposal Submission Due Date Must be received, in writing, at the office of the person listed above by 2:30 p.m. (EST) ................................................. November 14, 2014 Finalist Presentations ....................................................... Week of December 1, 2014 Notification Date ......................................................................... December 15, 2014 Contract Start Date .................................................................... As soon as possible following contract

negotiation and execution

The Mandatory Telephone Conference is scheduled for 10:00 a.m. on November 6,

2014 to answer questions and requests for clarification. Proposers should dial as

follows: 1-888-330-1716; Access Code: 1247805. Once the submitted proposals have been reviewed, PGW may select finalists for this RFP. The finalists will then be required to present their proposals at PGW. In addition, finalists will be required to provide PGW with a list of clients that are geographically near to PGW that utilize the proposed IGMS system, which clients have agreed to allow PGW to visit their sites to review the utilization and performance of the proposed IGMS system.

mailto:[email protected]

mailto:[email protected]


of 77

These dates are estimates only and PGW reserves the right to alter this schedule as it deems necessary or appropriate.

1.2 Proposal Requirements

Proposals shall be accepted only from respondents (“Proposers”) who have:

1.2.1 Obtained from PGW a complete set of Proposal Documents and any addenda thereto issued by PGW (sometimes referred to as the “RFP”), consisting of the following five (5) sections; two (2) attachments and three (3) appendices:

Sections:

1 The Solicitation – Notice to Proposers

2 Project Definition and Requirements

3 Instructions to Proposers

4 Proposer Information

5 Proposal Evaluation, Negotiation and Contract Award

Attachments:

D Disclosure Form

I Demographic Survey

Appendices:

1 Requirements

2 Development Standards

3 Testing and Acceptance Standards

1.2.2 Taken part in the Mandatory Telephone Conference; and

1.2.3 Submitted a proposal pursuant to the instructions in this RFP as set forth in Section 3.

In evaluating the proposals, PGW will consider the demonstrated experience and ability of the Proposer to deliver the proposed services, the scope and value of the proposed services, and the financial proposal of each Proposer as described in this RFP.

PGW hereby solicits proposals in accordance with these Proposal Documents.


of 77

2 Project Definition and Requirements

2.1 Overview

2.1.1 Overview of PGW

PGW is a municipally-owned utility operated by the Philadelphia Facilities Management Corporation (hereafter referred to as “PFMC”). The successful Proposer will enter into a negotiated contract with PGW by PFMC. PGW provides natural gas service to approximately 502,000 active accounts within the city of Philadelphia, using 6,000 miles of gas mains and services. PGW is the only utility currently distributing natural gas within the city of Philadelphia, and its mission is to provide safe, reliable natural gas service to the citizens of Philadelphia at a reasonable cost.

2.1.2 Background Information

Currently, PGW does not have Gas Management System (“GMS”) software for its Gas Acquisition, Transportation and Accounting units. The work is facilitated by utilizing MS Excel spreadsheets that encompass the business practices for acquiring, transporting, allocating, storing and accounting for gas supplies required to meet PGW’s customer obligations.

The Natural Gas Choice and Competition Act required PGW to open the Philadelphia market to competition from gas suppliers licensed in Pennsylvania as of September 1, 2003. The PGW Choice Program enables and oversees PUC- and PGW-approved natural gas suppliers servicing customers behind the Philadelphia city gate. An approved choice supplier can supply firm/monthly metered customers and/or interruptible/daily metered customers. These customers are grouped into Firm Transportation (“FT”) pools and Interruptible Transportation (“IT”) pools and are bound by different tariff rules (refer to PGW Service and Supplier Service tariffs for more information, found at www.pgworks.com).

The current PGW Choice Program system is made up of two systems, Retail Operations (“RTO”) and the Electronic Bulletin Board (“EBB”). These two Choice Program systems also communicate with other PGW systems, such as Oracle Financials, the Supervisory Control and Data Acquisition (“SCADA”) system and the PGW Customer Information System (“CIS”). The RTO system receives customer data from the CIS, while weather and system load data is received from SCADA. Internally, RTO classifies the customer and supplier info, allocates capacity and forecasts for FT customers, tracks deliveries and usage and bills all supplier pools according to the applicable rules. The EBB is used as a communication tool with suppliers. Suppliers also use the EBB to view their pool activity, imbalances and billed volumes, as well as to enter nominations and download reports.

The purpose of this RFP is to obtain a system to permit PGW to increase efficiency in the Gas Management area and improve business functions with suppliers while minimizing costs for all parties involved. After extensive internal departmental analysis,


of 77

it has been decided that an Integrated Gas Management System (“IGMS”) incorporating a GMS and the PGW Choice Program system will be needed to accommodate the buying, transportation and accounting of natural gas as well as the management of third party supplier activities behind the Philadelphia city gates.

It is expected that the IGMS will automate and centralize natural gas supply processes as well as minimize the department’s reliance on MS Office software. The current Choice Program systems (RTO and EBB) are outdated, highly customized and expensive to maintain. PGW is interested in the following major areas of improvement in functionality:

The proposed system must be gas industry specific, easy to maintain and operate

and easy to configure to accommodate tariff changes, requiring minimal customizations and lower cost.

The proposed system, by design, should be easy for PGW personnel to learn, minimize PGW’s cost to support and include comprehensive documentation so that the successful Proposer’s personnel and PGW’s personnel can support the system and business process with minimum training.

The system’s reporting capabilities must be robust and comprehensive, allowing PGW and suppliers to minimize the need for additional or separate adhoc inquiries.

The system must have the ability to display the information at the customer level as well as aggregate the customer information at the pool level.

The proposed system must accommodate basic supplier activities such as pool trading, flat forecasting, and commodity payback.

The proposed system should consolidate the GMS and the PGW Choice Program system to improve PGW’s processes, allowing all users to access and share information from one source.

2.2 Services to be Provided; Scope of Work

The Gas Management Department requires a comprehensive IGMS to track all company natural gas activities from the point of purchase by PGW to delivery to a customer’s burner tip, including invoicing of the suppliers enrolled in the PGW Choice Program. This system must give the department automated operational control over its assets and create a seamless informational flow amongst all its functional areas, including gas acquisition, transportation in the interstate pipelines, accounting and retail marketing behind the city gates.

Requirements for the IGMS are provided in Appendix 1. Proposers must indicate, for each requirement, whether the proposed system meets such requirement or not, and whether customization is required. Information Security standards are detailed in Appendix 2. To the extent customization is required; Appendix 3 outlines PGW’s development standards. Finally, Appendix 4 details PGW’s testing and acceptance standards.

The proposed system must (i) automate manual processes that are currently handled by multiple MS Excel files, (ii) eliminate redundancy, (iii) minimize user manual errors, (iv) offer comprehensive reporting, (v) create a seamless work flow from gas acquisition to transportation, supply and control through to accounting and supplier invoicing, (vi)


of 77

migrate current Choice system data into the new platform and (vii) use current interfaces with the SCADA and CIS systems.

2.3 Term

PGW anticipates entering into a software license agreement with the selected proposer which will include ongoing maintenance and support. Spending authority for this project expires on August 31, 2015. All of the acquisition and implementation related tasks must be complete and all cost associated with the project must be invoiced by that date.

2.4 Proposal Pricing

PGW has not predetermined a pricing structure for this project and will consider all pricing proposals. Proposers are encouraged to present proposals offering PGW options including one or more of the following pricing elements:

Firm, fixed price proposal. The proposed price must include all costs to PGW for the pre-packaged software as well as any work required for the interfaces.

Itemize and describe all hardware, software and service components required to meet the objectives.

Describe the pricing model and the associated prices. For example, named user license, concurrent user license or CPU/server license.

Government discounts.

Annual maintenance costs. Identify software to services ratio and the cost of annual maintenance (for example, 18%, 20%, and 25% of the software cost). Proposers must specify how critical updates and software upgrades will be provided to PGW and at what cost.

Proposer must provide a detailed description and cost breakdown for each option being presented. All cost proposals must include a schedule of payment linking payment with critical events/deliverables. Compensation to Proposer shall be dependent upon the successful completion of predetermined milestones.

2.5 Proposer/Personnel Minimum Requirements

Proposers must have at least five (5) years’ experience providing Integrated Gas Management Systems similar to that required pursuant to this RFP. Experience implementing IGMS for state regulated energy utilities, especially for Pennsylvania utilities, is a plus.


of 77

The selected Proposer will be required to provide personnel with demonstrated experience in providing similar services to utilities of comparable size. Personnel involved in custom development and configuration must meet the following minimum requirements:

Minimum 3 years of experience working on projects of comparable size and verifiable skills in the technologies utilized in the development of the proposed system.

Minimum 3 years’ of experience performing structured requirements gathering and systems analysis utilizing workshops, JADs, use cases and other structured methods.

Minimum 3 years project management experience.

Demonstrated ability to develop functional and technical system requirements documentation and business process models.

2.6 Licensing

The Proposer will be authorized to do business in the Commonwealth of Pennsylvania and comply with all pertinent state and federal requirements, codes and regulations.

If Proposer is a “business” as defined in The Philadelphia Code, Section 19-2601, Proposer must have a valid business privilege license, issued by the City of Philadelphia’s Department of Licenses and Inspections, to do business in the City of Philadelphia, prior to entering into any contract with PGW.

2.7 Information/Product

All reports, surveys, tables, charts, diagrams, design work, product recordings and other data (including electronic, audio and video) or documentation prepared or compiled by Proposer in connection with the performance of its obligations under the contract, shall be the sole and exclusive property of PGW. Proposer shall retain in its files, sufficiently detailed working papers relevant to its engagement with PGW. Proposer further agrees that its working papers will be held in the strictest confidence and will not be disclosed or otherwise made available to outside sources, except as required by law, without the written consent of PGW.

2.8 Confidentiality

Proposer must agree to keep confidential any and all information concerning the plans, operations or activities of PGW which may be divulged by PGW or ascertained by Proposer in the course of performing services under any contract with PGW. In the event Proposer is required to disclose confidential information pursuant to a subpoena, order of a court, or other legal process, Proposer shall, upon notice of such required disclosure and prior to disclosure, immediately notify PGW and allow PGW the


of 77

opportunity to inspect the information subject to disclosure, and in the event such disclosure is objectionable under any standard or rule of the court, Proposer shall exhaust all legal means to prevent disclosure.

2.9 Minority Participation

PGW has established an anti-discrimination policy relating to the participation of Minority, Women, and Disabled businesses and persons (collectively, “DBEs”) in contracts. The purpose of PGW’s DBE policy is to provide equal opportunity for all businesses and persons and to assure that PGW funds are not used, directly or indirectly, to promote, reinforce or perpetuate discriminatory practices. Proposers must complete Attachment I (Demographic Survey), attached hereto and submit same with their proposals.

2.10 Insurance

Proposer shall procure and maintain, at its sole cost and expense, insurance with companies carrying an A. M. Best’s rating of not less than A- and acceptable to PGW, with coverage limits of not less than stipulated below.

Philadelphia Gas Works, Philadelphia Facilities Management Corporation and the City of Philadelphia and their respective officers, employees, directors, boards, commissions and agents, shall be included as Additional Insureds on the General Liability, Automobile Liability and Excess/Umbrella Liability Insurance policies. An endorsement is required stating that Proposer’s policies affording Additional Insured status will be primary to any other coverage available to PGW, PFMC, and the City of Philadelphia and their respective officers, employees, directors, boards, commissions and agents, and any insurance maintained by PGW will be excess and non-contributory. No act or omission of PGW, PFMC, and/or the City of Philadelphia and their respective officers, employees, directors, boards, commissions and agents shall invalidate the coverage.

WORKERS' COMPENSATION AND EMPLOYERS' LIABILITY. Workers' Compensation Insurance, as required by statute. Employers' Liability coverage is to be carried with minimum limits of $500,000 each accident/$500,000 disease-policy limit/$500,000 disease-each employee.

GENERAL LIABILITY INSURANCE. Commercial General Liability is required with limits of not less than $1,000,000 for Bodily Injury and Property Damage Each Occurrence; $2,000,000 General Aggregate; $1,000,000 Products/Completed Operations Aggregate and $1,000,000 Personal/Advertising Injury. The policy shall also cover liability arising from liability assumed under an insured contract (including the tort liability of another assumed in a business contract), and Personal Injury (including, but not limited to, coverage for defamation, malicious prosecution and slander). Products/Completed Operations must be included and maintained for at least three (3) years beyond completion of the work required by contract in accordance with the terms thereof. ISO Contractual Liability Limitation


of 77

Endorsement #CG2391093 shall not apply to this Agreement. Such policy must contain a "Severability of Interests" clause. This insurance shall be excess over any other insurance, whether primary, excess, contingent or on any other basis that is available to the Proposer or its subcontractor covering liability for damages because of Bodily Injury or Property Damage for which the Proposer has been included as an Additional Insured. Philadelphia Gas Works, Philadelphia Facilities Management Corporation and the City of Philadelphia and their respective officers, employees, directors, boards, commissions and agents shall be included as Additional Insureds. The Additional Insured Endorsement(s) should also include Products/Completed Operations and “your work”. ISO Endorsement CG20370704 or equivalent should be attached to policy. A copy of the actual Additional Insured Endorsement or policy wording is required.

AUTOMOBILE LIABILITY INSURANCE. Business Automobile Liability covering all owned, non-owned and hired autos is required with limits of not less than $1,000,000 Combined Single Limit for Bodily Injury and Property Damage. Such policy must contain a "Severability of Interests" clause. Philadelphia Gas Works, Philadelphia Facilities Management Corporation and the City of Philadelphia and their respective officers, employees, directors, boards, commissions and agents shall be included as Additional Insureds. A copy of the actual Additional Insured Endorsement or policy wording is required.

EXCESS/UMBRELLA LIABILITY INSURANCE. Proposer shall provide evidence of Excess/ Umbrella Liability Insurance with limits of not less than $3,000,000 in any one claim or occurrence. The Excess/Umbrella policy shall follow form and be excess of all underlying insurance required by this contract except Professional Liability/Errors and Omissions coverage as outlined below. Philadelphia Gas Works, Philadelphia Facilities Management Corporation and the City of Philadelphia and their respective officers, employees, directors, boards, commissions and agents shall be included as Additional Insureds. A copy of the actual Additional Insured Endorsement or policy wording is required.

PROFESSIONAL LIABILITY/ERRORS & OMISSIONS COVERAGE. Evidence of Professional Liability/Errors & Omissions coverage, including Cyber Liability Insurance, must also be provided with limits of not less than $2,000,000 Per Occurrence/Aggregate or Per Claim or Loss/Aggregate with a deductible not to exceed $50,000. Errors & Omissions Insurance shall be applicable to any occurrence arising out of the performance of services pursuant to any statement of work between the parties and shall cover liability arising from information technology services including, but not limited to, intellectual property infringement, privacy infringement, software development services and computer or electronic information technology services. Under an occurrence form, coverage required shall be maintained in full force and effect under the policy during the contract period. Under a claims made form, continuous coverage is required. Should an Extended Discovery Period or "tail" coverage be required in the event coverage is terminated, such coverage must be maintained for a period of not less than three (3) years. This insurance shall be


of 77

primary with respect to any other insurance or self-insurance programs afforded the Proposer.

FIDELITY/BLANKET CRIME INSURANCE. Evidence of Fidelity/Blanket Crime Insurance with an Employee Dishonesty limit of not less than $1,000,000 shall be submitted to PGW prior to the commencement of services. Vendor/Contractor must maintain third party property (includes money, securities and other properties) coverage under Crime policy.

ADDITIONAL PROVISIONS

Certificates of Insurance evidencing all required coverage shall be filed with PGW prior to the commencement of work. Renewal certificates and policies, as required, shall be forwarded to Philadelphia Gas Works for as long as contractor performs the work as specified in this contract. Coverage afforded will not be canceled or materially altered until at least thirty (30) days after prior written notice has been given to PGW.

It shall be the responsibility of the contractor to ensure that all subcontractors carry insurance of not less than coverage and limits specified herein, except to the extent that PGW’s Director of Risk Management may agree to lower limits on a case by case basis depending on the nature of the subcontractor's work. Subcontractor must forward proper evidence of this compliance to Philadelphia Gas Works prior to the inception of any work.

2.11 Indemnification

The Proposer will be required in the contract to indemnify, defend and hold harmless PGW, PFMC, the City of Philadelphia, and each of their respective officers, employees, directors, boards, commissions, and agents, from and against any and all losses, costs (including, but not limited to, litigation and settlement costs and counsel fees), claims, suits, actions, damages, liability and expenses, occasioned wholly or in part by Proposer’s act or omission or negligence or fault or the act or omission or negligence or fault of Proposer’s agents, subcontractors, suppliers, employees or servants in connection with this Agreement, including, but not limited to, those in connection with loss of life, bodily injury, personal injury, damage to property, contamination or adverse effects on the environment, intentional acts, failure to pay such subcontractors and suppliers, any breach of this Agreement, and any infringement or violation of any proprietary right (including, but not limited to, patent, copyright, trademark, service mark and trade secret), regardless of the negligence of PGW, PFMC, and/or the City of Philadelphia. In any and all claims, suits and actions against PGW, PFMC and the City of Philadelphia, and their respective officers, employees, directors, boards, commissions and agents, by any employee of Proposer, any subcontractor, or anyone for whose acts Proposer and its subcontractor is liable, the indemnification obligation set forth in this section shall not be limited in any way by any limitation on the amount or type of third party damages, compensation or benefits payable by or for Proposer or any subcontractor under workers’ compensation acts, disability acts, or other employees’ benefit acts.


of 77

PGW does not indemnify.

2.12 Certificate of Non-Indebtedness

The Proposer will be required to certify and represent that Proposer and Proposer’s parent company(ies) and subsidiary(ies) are not indebted (at the time of signing of the contract) to the City of Philadelphia, PGW or PFMC (collectively the “City”), and will not at any time during the term of the contract (including any extensions or renewals thereof) be indebted to the City, for or on account of any delinquent taxes (including, but not limited to, taxes collected by the City on behalf of the School District of Philadelphia), liens, judgments, fees or other debts for which no written agreement or payment plan satisfactory to the City has been established. In addition to any other rights or remedies available to PGW at law or in equity, Proposer acknowledges that upon any breach or failure to conform to such certification PGW shall have the right to, and may, at the option of PGW, withhold payments otherwise due to Proposer, and, if such breach or failure is not resolved to PGW’s satisfaction within a reasonable time frame as specified by PGW in writing, this will offset any such indebtedness against said payments and/or terminate this Agreement for default (in which case Proposer shall be liable for all excess costs and other damages including reasonable attorney’s fees resulting from the termination).

2.13 Non-Discrimination

Proposer shall not discriminate or permit discrimination against any person because of race, color, religion, national origin, sex or sexual orientation. In the event of such discrimination, PGW may, in addition to any other rights or remedies available under the contract, at law or in equity, terminate any contract with Proposer forthwith.

Proposer shall comply with the provisions of Title VII of the Civil Rights Act of 1964 (42 U.S.C. §200d et seq.), §504 of the Federal Rehabilitation Act of 1973 (29 U.S.C. §794), The Age Discrimination Act of 1975, (42 U.S.C. §6101 et seq.), Title IX of the Education Amendments of 1972, (20 U.S.C. §1681), and 45 C.F.R. Part 92, as they may be amended from time to time, which together prohibit discrimination on the basis of race, color, national origin, sex, handicap, age and religion.

Proposer understands and agrees that no individual with a disability shall, on the basis of the disability, be excluded from participation in any contract of Proposer with PGW or from activities or services provided under such contract. As a condition of accepting and executing such contract, Proposer shall comply with all provisions of the Americans with Disabilities Act, 42 U.S.C. §12101 et seq., and all regulations promulgated thereunder, as the Act and regulations may be amended from time to time, which are applicable (a) to Proposer, (b) to the benefits, services, activities, facilities and programs provided in connection with this Agreement, (c) to PGW, or the Commonwealth of Pennsylvania, and (d) to the benefits, services, activities, facilities and programs of PGW or of the Commonwealth.

Without limiting the generality of the preceding sentence, Proposer shall comply with the “General Prohibitions Against Discrimination,” 28 C.F.R. §35.130, and all other


of 77

regulations promulgated under Title II of “The Americans with Disabilities Act,” as they may be amended from time to time, which are applicable to the benefits, services, programs and activities provided by PGW through contracts with outsider contractors.

2.14 MacBride Principles

Proposer certifies and represents that, to the best of its knowledge, (i) Proposer (including any affiliates under its direct control) does not have, and will not have at any time during the term of any contract with PGW (including any extension or renewal thereof), any investments, licenses, franchises, management agreements or operations in Northern Ireland and (ii) no product to be provided under any contract with PGW will originate in Northern Ireland, unless Proposer has implemented the fair employment principles embodied in the MacBride Principles.

In the performance of any contract with PGW, Proposer covenants that it will not utilize any suppliers, subcontractors at any tier (i) who have (or whose parent, subsidiary, exclusive distributor or affiliates have) any investments, licenses, franchises, management agreements or operations in Northern Ireland or (ii) who will provide products originating in Northern Ireland unless said supplier or subcontractor has implemented the fair employment principles embodied in the MacBride Principles. Proposer further covenants to include the provisions of this paragraph, with appropriate adjustments for the identity of the parties, in all subcontracts and supply agreements which are entered into in connection with the performance of any contract with PGW. Proposer covenants that it will cooperate with PGW and City’s Director of Finance in any manner which PGW and the said Director deem reasonable and necessary to carry out PGW’s and the Director’s responsibilities under Section 17-104 of the Philadelphia Code which embodies the requirements set forth in this section. Proposer understands and agrees that any false certification or representation in connection with this section and any failure to comply with the provisions of this section shall constitute a material breach of any contract with PGW entitling PGW to all rights and remedies provided therein or otherwise available in law (including, but not limited to, Section 17-104 of the Philadelphia Code) or equity. In addition, Proposer understands that false certification or representation in connection with this section is subject to prosecution under Title 18 Pa.C.S.A. Section 4904.

2.15 Governing Laws

Any contract entered into by PGW will be executed in and shall be governed by the laws of the Commonwealth of Pennsylvania.

2.16 Certain Required Disclosures

In accordance with The Philadelphia Code Title 17 Chapter 17-400, persons and entities who wish to provide goods and services to PGW must provide certain information about contributions they have made to elected City officials or candidates for City offices. All Proposers must therefore complete Attachment D and include such completed Attachment with their proposal. Please note that the selected Proposer will


of 77

be required to update such disclosure during the term of its agreement with PGW and for one year thereafter.


of 77

3 Instructions to Proposers

3.1 Proposal Preparation Requirements

3.1.1 Proposals must be prepared in English on 8 ½ x 11 inch paper with tabbed indexes separating the following seven (7) completed sections in the following order:

3.1.1.1 Tab 1: Transmittal letter.

3.1.1.2 Tab 2: Scope of Work. Proposed scope of work, work plan, procedure and timeline to provide the scope of work described in Section 2 of this RFP. Completed Appendix 1 must be included.

3.1.1.3 Tab 3: Proposal Pricing.

3.1.1.4 Tab 4: Completed Section 4 (Proposer Information) of this RFP. All Proposals must include the following information and be signed (at the end of Section 4) as follows:

3.1.1.4.1 If the Proposal is made by an individual, the Proposal must be signed by the individual, the individual’s full name must be typed or printed under the signature line and the Proposal must include the individual’s mailing address.

3.1.1.4.2 If the Proposal is made by a partnership, the Proposal must:

a) be signed by at least one of the general partners with

authority to bind the partnership and the name of the general

partner must be typed or printed under the signature line;

b) include the name and mailing address of the partnership; and

c) attach a copy of the partnership agreement, or other

document authorizing the general partner to sign the

Proposal to bind the partnership;

3.1.1.4.3 If a corporation makes the Proposal, the Proposal must:

a) be signed by the president or vice president of the

corporation, and the secretary or treasurer must attest the

signature and the names of the corporate officers must be

typed or printed under the signature lines;


of 77

b) include the name and mailing address of the corporation; and

c) attach a copy of the corporation’s by-laws or a corporate

resolution authorizing the corporate officer signing the

Proposal to bind the corporation.

3.1.1.4.4 If the Proposal is made by a joint venture, the Proposal must:

a) be signed by all joint venture partners and the names of the

joint venture partners must be typed or printed under the signature lines;

b) include the name and mailing address of the joint venture;

and c) attach a copy of the joint venture agreement or other

documentation signed by each member of the Joint Venture and, if applicable, any documentation necessary to show that the individuals signing on behalf of each joint venture partner are authorized to bind the joint venture.

3.1.1.5 Tab 5: Qualification and Experience of Proposer. Proposers are strongly encouraged to list experience providing similar services.

3.1.1.5.1 Provide the names and resumes of each person who would be participating in this project;

3.1.1.5.2 Indicate whether the individual is a full time employee of Proposer’s organization (and if so for how long) or a subcontractor. If the individual is a subcontractor, list the engagements (and the particular responsibilities on each engagements) that the subcontractor has previously worked for Proposer;

3.1.1.5.3 Indicate the areas of the project that each individual will be involved with or have responsibility for;

3.1.1.5.4 For each such individual, provide a reference list with phone numbers.

3.1.1.6 Tab 6: Prior Work Examples. Provide examples of the following documentation:

Project Status Reports Change Request Forms Test Scripts Test Plans Test Results documentation forms Data Conversion plans


of 77

System Architecture Diagrams (data models, Erwin diagrams, data dictionary documentation)

System Training Plan Manuals Issue Management mechanism (e.g., approach to reporting, tracking,

resolving and document solutions) Change management methodology

3.1.1.7 Tab 7: Completed Attachments D and I, and any other attachments required to be completed under the RFP.

3.1.2 One (1) original Proposal, one (1) copy and one (1) CD containing a searchable PDF readable by Adobe Reader 7.0 or higher of the proposal, must be submitted in a sealed envelope or envelopes addressed to PGW Supply Chain Department, Philadelphia Gas Works, 800 W. Montgomery Avenue, Philadelphia, Pennsylvania 19122. The name and address of the Proposer must also appear on the face of the envelope. The PDF file name should be as follows: PROPOSER_RFP_######.PDF where Proposer is your company name and ###### is the PGW RFP id number.

3.1.3 Failure to answer all questions completely and furnish all information required in these Proposal Documents may result in disqualification of the Proposer. PGW reserves the right to thoroughly investigate the financial status and experience of the Proposer.

3.1.4 It shall be the responsibility of the Proposer to deliver the Proposal and all other required items to the location specified in Section 1 of these Proposal Documents on or before the due date and time set forth in Section 1.1.

3.1.5 Oral communications from PGW personnel or other persons shall not be binding on PGW and shall in no way modify the provisions of the Proposal Documents. Official responses of PGW to inquiries regarding these Proposal Documents shall be issued by PGW in writing as addenda, and only such written responses shall be binding on PGW as modifications to these Proposal Documents.

3.2 Duration of Proposal

In consideration of PGW’s evaluation of the submitted Proposals, each Proposer agrees that its Proposal shall be a firm offer to PGW, and shall remain open for acceptance by PGW for a period of at least one hundred and fifty (150) days beginning with the submission due date set forth in Section 1 of these Proposal Documents, as may be revised by addenda.

3.3 Proposer’s Responsibility

The Proposer shall carefully examine the terms of the Proposal Documents and shall judge for itself all of the circumstances and conditions affecting its Proposal. PGW will


of 77

endeavor to present accurate information, but Proposers are advised to independently verify the accuracy of any information received.


of 77

4 Proposer Information

4.1 Proposer

Submitted by:

[Please type or print]

Name:

Address:

Telephone:

Facsimile:

The undersigned Proposer hereby submits to PGW this Proposal as described herein and in the attached documents.

4.2 Qualifications Statement

The Proposer represents and covenants that the Proposer is fully qualified to provide the requested services to PGW. The undersigned further swears and affirms that the information contained in this response is true, accurate and complete.


of 77

4.3 Business Experience

4.3.1 The following describes other points of service by Proposer and the companies for whom the services were provided. Proposer should include a reference contact at the described companies, and this contact should have direct, specific responsibility for the oversight of the program. In particular, the Proposer should describe all experience with projects similar to this project.


of 77

4.3.2 The Proposer has operated under its current name since ____, a period of ___________ years, and the Proposer (if such be the case) formerly operated under the following name:

_________________________________________________________.

4.3.3 Proposer must attach the resume of the manager which it anticipates will be the contact for the services required by this RFP.

4.3.4 The Proposer submits herewith the following list of three (3) persons or businesses, which have knowledge of the Proposer’s ability to successfully perform the services for which this Proposal is submitted.

REFERENCE NO. 1

Name:

Firm:

Title:

Address:

Telephone:

Facsimile:

Nature of Association:

REFERENCE NO. 2

Name:

Firm:

Title:

Address:

Telephone:

Facsimile:



of 77

REFERENCE NO. 3

Name:

Firm:

Title:

Address:

Telephone:

Facsimile:


4.3.5 The Proposer has not had an agreement canceled or terminated due, in whole or in part, to the fault of Proposer, or a default or breach of contract on the part of the Proposer. (If a contract or agreement has been canceled, please explain.)

4.4 Financial Information

4.4.1 If the Proposer requests that PGW receive and maintain any of the following financial information in confidence, the Proposer understands that such information may not be exempt from disclosure under the Philadelphia Home Rule Charter and/or the Commonwealth Right to Know Act. The Proposer agrees that PGW may make such disclosure or reproduce such financial information as is deemed necessary or convenient by PGW, its officers, agents, or employees, for PGW’s use in Proposal evaluation and comparison; provided, however, that if any person makes a request as contemplated by the Philadelphia Home Rule Charter and/or Commonwealth Right to Know Act to review or be provided with copies of such financial information or any part thereof, and PGW denies such requests, immediately upon notification thereof, the Proposer shall, at its sole cost and expense, defend PGW and its officers, agents, and employees against any action resulting from denial of such request. If the Proposer fails to promptly provide such defense, PGW, its officers, agents, and employees shall be free to grant such requests, and the Proposer shall be deemed to have waived any cause of action, whether in law or in equity, that it may have against PGW respecting such disclosure. The Proposer agrees to indemnify and hold harmless PGW, its officers, agents, and employees from any and all claims, costs, liabilities or damages, including


of 77

attorney’s fees and court costs resulting from PGW’s or Proposer’s acts or omissions pursuant to this Paragraph.

4.4.2 The Proposer has ( ) has never ( ) [check one] had a bond or surety canceled or forfeited. (If the Proposer has had a bond or surety canceled, state the name of the bonding company, date, amount of bond and reason for such cancellation or forfeiture.)

4.4.3 The Proposer has ( ) has never ( ) [check one] been adjudged bankrupt (Chapter 7), or petitioned the court for relief under the Bankruptcy Code or Act for either business reorganization (Chapter 11) or the Wage Earner’s Plan (Chapter 13). If the response is in the affirmative, provide the following information:

4.4.3.1 Date petition filed

4.4.3.2 Case No. and jurisdiction

4.4.3.3 Amount of liabilities and debts

4.4.3.4 Date of discharge or successful completion of reorganization or wage earner’s plan

4.4.4 The Proposer’s bank references are:

Name Address

4.4.4.1.

4.4.4.2.

4.4.4.3.

The undersigned herewith submits a letter from

indicating that the Proposer has an

(name of financial institution)

available working line of credit of no less than ________________Dollars

($___________), or other evidence of Proposer’s capital sufficient to permit it to meet

the obligations contemplated by its Proposal.

4.4.5 The undersigned hereby affirms that the Proposer is authorized to conduct business in the Commonwealth of Pennsylvania, and City of Philadelphia, or will obtain proper authorization to do so before executing an agreement and furnishing the required bond or letter of credit, if any.


of 77

4.5 General Litigation Disclosure

Proposer must describe any pending, contemplated or ongoing administrative or judicial proceedings material to Proposer’s business, finances or products including, but not limited to, any litigation, consent orders, debarment or contracts with any local, state or federal regulatory agency issued to Proposer or to any parent or subsidiary of Proposer:____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________.

4.6 Business Organization Statement

4.6.1 General Information

Name of Firm [Exactly as it would appear on an agreement; if operating under a fictitious name, so indicate.]

Principal Office Address:

Telephone Number:

Form of Business Entity [check one]

( ) Corporation

( ) Partnership

( ) Individual

( ) Joint Venture


of 77

4.6.2 Corporation Statement

If a corporation, answer the following:

Date of incorporation:

Location of incorporation:

Is the corporation authorized to do business in Pennsylvania? Yes ( ) No ( )

If so, as of what date?

The corporation is held: Publicly ( ) Privately ( )

Furnish the name, title, and address of each director and officer of the corporation.

DIRECTORS

Name

Address

Principal Business

Affiliation Other than

Proposer’s Directorship

1.

2.

3.

4.

5.

6.

7.

8.


of 77

SHAREHOLDERS

Name Address Number of Shares Owned

1.

2.

3.

4.

5.

6.

7.

8.

OFFICERS

Name Position

1.

2.

3.

4.


of 77

4.6.3 Partnership Statement

If a partnership, answer the following:

Date of organization:

General Partnership ( ) Limited Partnership ( )

Partnership Agreement recorded? Yes ( ) No ( )

Date Book Page County State

Has the partnership done business in Pennsylvania? Yes ( ) No ( )

When?

Name, address, and ownership share of each general partner owning more than five percent (5%) of the partnership:

Name

Address

% of

Ownership

1. %

2. %

3. %

4. %

5. %

6. %


of 77

4.6.4 Joint Venture Statement

If a Joint Venture, answer the following:

Date of organization:

Joint Venture Agreement recorded? Yes ( ) No ( )

Date Book Page County State

Has the Joint Venture done business in Pennsylvania? Yes ( ) No ( )

When?

Name, address of each Joint Venturer and percent of ownership of each:

Name

Address

% of

Ownership

1. %

2. %

3. %

4. %

5. %

4.7 Warranties by Proposer

4.7.1 The Proposer’s Proposal has been completed to the best of the Proposer’s ability, and the Proposer swears that all information contained herein is true, correct and complete to the best of the Proposer’s knowledge, information and belief.


of 77

4.7.2 By submission of this Proposal, the Proposer acknowledges that PGW has the right to make any inquiry or investigation it deems appropriate to substantiate or supplement information contained in the Proposal, and Proposer authorizes the release to PGW of any and all information sought in such inquiry or investigation.

4.7.3 The Proposer declares by the submission of this Proposal that the Proposal is not made in the interest of, or on behalf of, any undisclosed person, partnership, company, association, organization, or corporation; that the Proposal is genuine and not collusive or sham; that the Proposer has not directly or indirectly induced or solicited any other Proposer to put in a false or sham Proposal, and has not directly or indirectly colluded or agreed with any Proposer or anyone else to put in a sham Proposal or to refrain from proposing; that the Proposer has not directly or indirectly sought by agreement or communication to secure any advantage against PGW; anyone interested in the Proposal as principal are named within the Proposal; that all statements contained in the Proposal are true; that the Proposer has not directly or indirectly divulged information or data relative to the Proposer’s Proposal to any other person, partnership, corporation, or association, except to such person or persons as have a direct financial interest in the Proposer’s general business.

The foregoing Proposal is hereby submitted by the entity signing below in accordance with all terms and conditions as set forth in the Request for Proposals issued by PGW.

PROPOSER:

DATE: ______________________ _________________________

(Corporate Seal if Applicable) Name of Proposer

By: _________________________

(signature)

Name:

Title:

Attest: _________________________

(signature)

Name:

Title:

[Add signature lines as necessary below.]


of 77

5 Proposal Evaluation, Negotiation and Contract Award

5.1 Disqualification of Proposers

5.1.1 If more than one Proposal is received from any individual, firm, partnership, corporation, or association, under the same or different names, said Proposals will not be considered. Reasonable grounds for believing that any Proposer has an interest in more than one Proposal will cause the rejection of all Proposals in which such Proposer is interested. If there is reason to believe that collusion exists among Proposers, none of the participants in such collusion will be considered. Similarly, unsolicited proposals may not be considered.

5.1.2 No Proposal shall be received from, or contract awarded to, any PGW or City employee or official who may have any direct or indirect interest in such submitted Proposal or contract.

5.2 Qualification of Proposers

5.2.1 PGW will carefully consider the Proposer’s qualifications, proposed financial consideration, experience, financial responsibility proposed scope of services, and timeline in evaluating each Proposal. In PGW ’s evaluation, the Proposal as a whole may bear more weight than the individual parts of the Proposal.

5.2.2 Following PGW’s review of the submitted proposals, PGW may select one or more Proposers with which to negotiate. PGW shall notify Proposer(s) of selection for negotiations. The date that the Proposer’s receipt of the notification is confirmed by PGW, is referred to herein as the “Notification Date.”

5.2.3 Respondents to this RFP are subject to Philadelphia Code (Chapter 20-600) and the Pennsylvania Ethics Act (65 P.S. Section 401 et.seq.) All respondents are required to disclose any potential conflict caused by PGW or City employees having a financial interest in the entity entering into a contract or agreement with PGW.

5.3 General Reservation of Rights

5.3.1 This RFP and the process it describes are proprietary to PGW and are for the sole and exclusive benefit of PGW. No other party, including any respondent to this RFP or future Proposer to any RFP which may be issued by PGW, is intended to be granted any rights hereunder. Any response to this RFP, including written documents and verbal communication, may be subject to public disclosure by PGW, or any authorized agent of PGW and any materials submitted or ideas elicited in response to this RFP shall be the sole and absolute property of PGW with PGW having title thereto and unrestricted use thereof.


of 77

5.3.2 PGW reserves the right to reject as informal or non-responsive any Proposal that, in PGW’s sole judgment, is incomplete, is not in conformity with applicable law, is not responsive to this RFP, or contains ambiguities or services not called for by this RFP.

5.3.3 Without limiting the generality of any other provision of this RFP, PGW reserves the right, at any time prior to execution of an agreement with the successful Proposer, to exercise all or any of the following rights and options, which rights and options PGW may exercise to the extent that PGW, in its sole discretion, deems to be in its best interests:

5.3.3.1 To request additional or supplemental information (including but not limited to information inadvertently omitted by any Proposer in response to this RFP) from any or all Proposers;

5.3.3.2 To accept or reject, at any time prior to its execution of an agreement, any or all Proposals or any part thereof submitted in connection with this RFP;

5.3.3.3 To accept or reject any or all of the items in any Proposal and award the contract in whole or in part if it is deemed in PGW’s best interest to do so;

5.3.3.4 To waive any informality, defect, non-responsiveness, or derivation from this RFP that is not, in PGW’s sole judgment, material to the Proposal;

5.3.3.5 To negotiate unacceptable provisions incorporated within an otherwise acceptable Proposal submitted in response to this RFP;

5.3.3.6 To reject without evaluation any Proposal that is incomplete, unclear, conditional, or which contains irregularities of any kind;

5.3.3.7 To reject any Proposal that in the sole discretion of PGW is not in the best interest of PGW;

5.3.3.8 To re-issue this RFP without change or modification;

5.3.3.9 To issue a subsequent RFP for this project with terms and conditions that are substantially different from the terms and conditions set forth in this RFP;

5.3.3.10 To cancel this RFP with or without issuing another RFP;

5.3.3.11 To supplement, amend, substitute, or otherwise modify this RFP at any time prior to execution of a final agreement with a Proposer;


of 77

5.3.3.12 To reject the Proposal of a Proposer that, in PGW ’s sole judgment, has been delinquent or unfaithful in the performance of any contract with PGW, or is financially or technically incapable of performing the services required in this RFP, or is otherwise not a responsible Proposer;

5.3.3.13 To permit or reject, at PGW’s sole discretion, amendments (including information inadvertently omitted), modifications, alterations and/or corrections of Proposals by some or all of the Proposers following Proposal submission;

5.3.3.14 To request that some or all of the Proposers modify Proposals or provide additional information following evaluation by PGW;

5.3.3.15 To conduct such investigations as PGW considers appropriate with respect to the qualifications of any Proposer and/or any information contained in any Proposal;

5.3.3.16 To request clarifications of any unclear Proposal;

5.3.3.17 To negotiate simultaneously, or otherwise, with one or more Proposers;

5.3.3.18 To discontinue and resume negotiations with one or more Proposers;

5.3.3.19 To rescind its rejection of any Proposal(s) and negotiate (or resume negotiations) with a previously rejected Proposer;

5.3.3.20 To not proceed with the process described in this RFP, or to change any time schedules set forth herein;

5.3.3.21 To not enter into an agreement pursuant to this RFP.

5.3.4 PGW intends to enter into contract negotiations with the selected Proposer. However, PGW reserves the right to terminate any negotiations at any time or conduct simultaneous, competitive negotiations with multiple Proposers. PGW reserves the right to negotiate acceptable terms in an otherwise unacceptable Proposal. Such negotiations may result in changes to material terms of this RFP; in such event, PGW shall not be obligated to inform other Proposers of the changes, or permit them to revise their Proposals accordingly, unless PGW, in its sole discretion, determines that doing so and permitting such is in PGW ’s best interest. Should negotiations not prove satisfactory with the recommended Proposer(s), PGW reserves the right to discontinue negotiations with the recommended Proposer(s) and additional firms may be asked to enter into negotiations or PGW may solicit new Proposals or issue a new Request for Proposals.


of 77

5.4 Award

5.4.1 PGW intends to award the agreement to the Proposer whose Proposal best satisfies the scope of services described in Section 2 and is otherwise in the best interest of PGW. The determination of award shall be made by PGW, in its sole discretion, which decision shall be final. PGW may employ such analysis techniques and professional consultants for Proposal evaluation as it deems necessary. PGW may request submission of additional information to assist it in evaluating a Proposal, and the Proposer shall cooperate fully with such request. The contract resulting from this RFP will be awarded to the qualified Proposer whose Proposal PGW believes will be the most advantageous to PGW. PGW may condition an award on the successful Proposer’s agreement to such terms and conditions as required by PGW including, but not limited to, PGW’s indemnification.


of 77

ATTACHMENT D. REQUIRED 17-1400 DISCLOSURE In accordance with the City of Philadelphia’s contract reform legislation, codified as The Philadelphia Code Title 17 Chapter 17-1400, persons and entities who wish to provide goods and services to PGW must provide certain information about contributions they have made to elected City officials or candidates for City offices. Please note that, if selected, you will be required to update such disclosure during the term of your agreement with PGW and for one year thereafter. Therefore, the following information must be provided to PGW: 1. Did you use any consultant with respect to this RFP or the

contract at issue within the prior one year period? If so, you are required to list (in an attachment hereto) the following information for each such consultant: (i) name, (ii) business address, (iii) business phone number and (iv) amount paid or to be paid. As used herein, the term “consultant” means any person or entity used to assist you in obtaining a contract through direct or indirect communication with the City, PGW, any City Agency or any officer or employee of any of them, if such communication is undertaken by the person or entity for payment.

YES

NO

2. Have you or any consultant disclosed above made any

contributions of money or in-kind assistance within the prior two year period to (i) any candidate for nomination or election to any public office in Pennsylvania, (ii) any individual who holds any such office, (iii) any political committee or state party in Pennsylvania or (iv) any group, committee or association organized in support of any such candidate, office holder, political committee or state party in Pennsylvania? If so, you are required to list (in an attachment hereto) the date, amount and recipient of each such contribution. For purposes hereof, (i) contributions made by a person’s immediate family shall be deemed contributions made by that person and (ii) contributions made by an entity’s affiliate or an officer, director, controlling shareholder or partner of an entity’s or such entity’s affiliate shall be deemed contributions made by that entity.

YES

NO


of 77

3. Do you intend to use any subcontractors on this contract? If

so, you are required to list (in an attachment hereto) the following information for each such subcontractor: (i) name, (ii) business address, (iii) business phone number and (iv) amount or percentage to be paid.

YES

NO

4. Within the prior two year period, has any City or PGW officer

or employee asked (i) you, (ii) any of your officers, directors or management employees or (iii) any person or entity representing you, to give money, services, or any other thing of value to any person or entity? If so, you are required to list (in an attachment hereto) the following information for each such officer or employee: (i) name, (ii) title, (iii) date of request, (iv) amount requested and (iv) amount of any payment made in response to request (other than contributions listed under (2) above).

YES

NO

5. Within the prior two year period, has any City or PGW officer

or employee directly or indirectly advised (i) you, (ii) any of your officers, directors or management employees or (iii) any person or entity representing you, that a particular person or entity could be used by you to satisfy any goals in this RFP or contract for the participation of minority, women, disabled or disadvantaged business enterprises? If so, you are required to list (in an attachment hereto) the following information for each such officer or employee: (i) name, (ii) title, (iii) date of advice and (iv) name of person or entity they advised could be used to satisfy such goals.

YES

NO

The undersigned hereby certifies that the information provided herein is true and correct as of the date set forth below. Signature: ________________________________ Title: ____________________________________ Name of Entity: ___________________________ Date: ____________________________________

(Please Print)


of 77

ATTACHMENT I. DEMOGRAPHIC SURVEY A key tenet of PGW’s practice of good corporate citizenship is its commitment to the use, non-discrimination against and development of qualified minority, disabled and women vendors and to non-discrimination in employment. In an effort to insure the full inclusion of all segments of the American population, PGW is requesting that the following information be returned with your proposal: A. Does your organization have a written program which

addresses the utilization of minority business enterprises (MBE), disabled business enterprises (DBE) and women enterprises (WBE) in the manufacturing, distribution of servicing of your product(s)? If so, please furnish a copy of your program. Please provide statistics of MBE, DBE and WBE in (1) manufacturing, (2) distribution, and (3) service for the past two years.

YES

NO

COMMENTS: ___________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ B. Does your organization foster economic growth and

development by providing procurement opportunities to MBE/DBE/WBE firms as material suppliers, contractors, sub-contractors, etc.? If so, please furnish a copy of your company policy or directive.

YES

NO

COMMENTS: ___________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ C. Does your organization have an Affirmative Action Equal

Employment Opportunity Policy? If so, please furnish a copy of this policy.

YES

NO

COMMENTS: ___________________________________________________________ ________________________________________________________________________ ________________________________________________________________________


of 77

D. Please furnish data depicting the composition of your work force by ethnic group gender and their appropriate titles/job classifications.

# OF EMPLOYEES

TITLE CLASS ETHNIC GROUP

GENDER

This information is for PGW use only and will be held in the strictest confidence. As a socially responsible corporation, PGW seeks to insure that its business partners are committed and dedicated to the practice of including all segments of the American population in their business practices. Accordingly, the information requested above must be provided or your proposal may be rejected as non-responsive. If the information was provided to PGW within the past twelve months, please check here:

Signature:__________________________ Title:______________________________ Name of Firm:_______________________ (Please Print)


of 77

Appendix 1. Requirements

GMS Module This group of modules includes the business practices for acquiring, transporting, storing and accounting for gas supplies required to meet the utility’s customer obligations.

Gas Acquisition Provide the capability to create, modify and review gas transactions from nomination to delivery. Maintain on-line information to track the commodity and breakout segment costs, including the commodity, transportation and fuel. The new system should:

o Monitor all gas supply transactions to meet demand requirements based on available capacity and supply options.

o Generate pipeline nominations and track confirmations. o Price reference repository of index price information and for other costs and fees

not generally associated with a published index such as Gas Daily, Inside FERC, Henry Hub, etc. Additional features include:

1. Rapid mass input screen for manual update of index prices; 2. Automated input of downloaded price information such as Platt’s data. 3. Mass recalculation of all physical deals referenced to a price index; 4. Logic to guide application of an index such as validation, last updated or

specific date and other attributes to support flexible use of the data. o Support off-system sales, on-system transportation sales and capacity release

transactions. All transactions will be in accordance with the NAESB Master Contract and also include additional features common to a utility’s business practices.

1. NAESB compliant master contract terms and conditions.

2. FAS 133 Documentation for the Normal Purchase / Sales Exception retained for audit purposes.

3. Purchase status designation of at least: Pending, Rejected, Accepted, Approved, Confirmed and Amended.

4. Time series of status changes with designation of change date and User Stamp.

5. Software security control over which User IDs have deal input/edit and view privileges or no privileges Ability to Copy a Deal day to day or month to month.

6. Ability to have a multi-month period from Deal Start to End Date; for example, a winter season base load period for purchases.

7. Deal Setup Attributes:

a. Counter party and company designated gas trader with contact number.

b. Selection of a daily, Dth/Day, or monthly, Dth/Month, deal quantity


of 77

c. Designation and input of a fixed or indexed deal price

d. Selection of an index adjustment as a +, - or * number—add, subtract or multiply adjustment to the index.

e. Selection of a market service contract for including a 3rd party

transaction fee in the total deal $ amount.

f. Selection of transporter pipeline and transaction point

g. User defined codes to tag deals for reporting and accounting;

i. Deal type such as option, spot, swing, base load, purchase for resale, etc.

ii. Flow type such as firm, spot, or any other defined attribute

iii. Transaction type such as send-out, injection, off system Sale, etc.

h. FERC 552 designation in a drop down list.

i. Comment section for adding Special Provisions to the Confirmation Report.

8. Grid listing of deal data elements with ability to sort by a selected column and to export deals to an excel spreadsheet.

9. Ability to list all deals for a User selected time period, including a multi-month selection.

10. Grid sort attributes such by pipeline, a company defined code for deal and transaction type, and FERC 552 code

11. Ability to show all deals or only deals with a specific counter party

12. Subtotal screen display of sub-total by counter party over a User selected date range1-12 months.

13. Track deal total quantity per day and scheduled quantity to identify unscheduled quantities.

14. Link deals to a scheduling transaction to path gas from a purchase or to a sale point.

15. Generate a deal Confirmation in the company’s format. The preferred format is to display the deal quantity by day and have a dynamic setup for deal terms.

16. Retain deal confirmation data to regenerate a confirmation for internal audit review. Historical retention of each confirmation per the company’s audit requirements.


of 77

17. Provide an effective method for amending a deal to change quantities and reissue a confirmation.

18. Provide a deal status history to track status changes for audit purposes.

19. Provide a calendar view of a deal to highlight the daily quantity, scheduled quantity, remaining to be scheduled and the daily price.

20. Provide a method of updating the deal price by refreshing all deals with updated index prices.

21. Provide a Platt’s upload option for inserting index prices.

22. Provide for gas purchase on an Asset Management contract. The purchase is for injection; thus the deal setup includes the injection path. The purpose is to inject into a storage asset under an asset management contract.

23. Provide for a controlled process for purchasing for injection where the purchase is pathed directly to Storage. The requirement is to simplify filling company managed storage facilities.

24. Provide for multi-pipeline reusable route to be setup to path gas from or to a deal transaction. The route may include any number of paths to complete the purchase or deal disposition.

25. Provide a pathing analysis tool to determine the cost of delivered gas given

a multi-path route for transportation.

Gas Transportation This sub-module would enable the Gas Supply and Acquisition Department’s Natural Gas Transportation area to efficiently integrate and centralize the flow of natural gas based on the various gas day variables; load, weather, supply, demand, and other determinants. This module is to record natural gas scheduled on interstate pipelines and storage contacts; apply rate structures and provide for transaction accounting. The storage module will support standard storage transactions to include WACOG. The required information and services include but are not limited to the following:

o Support for pipeline Activity Numbers for scheduling gas. o Include a NAESB compliant data set to facilitate communication and

synchronization with Pipeline datasets. o Provide for MS Excel file uploads of timely and intraday nominations to pipeline

systems. o Support business processes for interstate pipelines, storage facilities and asset

management contracts for pipeline and storage transactions. o Display daily and monthly scheduled gases in a grid structure to facilitate export

of the data in a User defined excel format. o Support setup of multi pipeline and/or contract routes to path gas from a linked

purchase or pipeline point to a destination point. o Calculate fully loaded delivery cost per Dth from a pipeline purchase or pooling

point to a destination point, such as the City gate delivery point or a storage pool. Manage both quantity and value in the scheduling path.


of 77

o Provide a daily and end of month summary city gate WACOG report breaking out delivered purchase and storage quantities to the city gate.

o Provide a flexible method of entering a revised price or fuel deduction at a receipt point and cascade the change through all linked packages to the destination point

o Provide a flexible method for displaying point balances to easily spot imbalance situations along a pipeline or at a city gate delivery point.

o For a city gate or pipeline pooling point show the imbalance and the transactions into and out of the point. Hot link to a deal or nomination setup screen to clear the imbalance.

o For city gate points include company nominations as well as marketer/customer nominations in the imbalance calculation.

o Provide for pipeline no-notice storage (NNS) or OBA balance daily with an auto-nomination into the OBA or NNS pool points. Transactions from the city gate are to be valued at the daily WACOG at the CG point.

o Import or manually insert daily gate station measurement data to combine with company and marketer/customer nomination to determine the actual imbalance.

o Automatically insert marketer/customer scheduled gas into the imbalance calculation based on nominations made on the applicable gas utility’s pipeline points.

o Support capacity release of demand and storage capacity in a NAESB compliant data set to position for an excel upload of released capacity to the pipeline.

o Support capacity release to on-system marketers with notification or released amounts on the marketer and customer web portal, EBB.

o Support capacity release/assignment in accordance with an asset management contract to include pipeline demand and storage demand and capacity.

o Copy capacity releases from a current to a future month. o Perform a daily aggregation of flowing gas and capacity release per pipeline

contract to track capacity available by zone or per contract. Display the net MDQ by point or zone with a display of total MDQ and the deductions.

o Display storage pools in a grid for excel export with a display of beginning inventory, value and WACOG with injections, withdrawals, adjustments and the ending inventory, value and WACOG.

o Provide for a drill down to view daily transaction over the full month. o Monitor storage capacity available and the injection and withdrawal MDQ as

adjusted for storage capacity and demand releases. o Validate withdrawal and injection against the adjusted IJ and WD MDQ values

and issue a warning should the adjusted MDQ be exceeded.

Gas Accounting Module This sub-module provides auditable vendor invoice reconciliation and customer invoicing, off-system and on-system revenue transactions. It records all gas transactions: nominations, confirmations, metered receipts, on-site storage, non-residential sales, both PGW sales and transport, plant use and deliveries to the city distribution system. Calculates the appropriate unit cost of gas for the various inventories and usages and associate these costs with the appropriate volume statements. Applies actual or estimated costs to the volumes developed in the measurement and reconciliation phase to permit the generation of journal entries for inclusion in the general ledger. The full, costed data


of 77

should permit the generation of management reports of the summary of fuel costs, sales and revenues and the sales and cost details underlying the GCR tariff operation. The following summarizes the features necessary for reconciling end of month gas acquisition contract transactions.

o Access daily pipeline confirmations, compare to nominations, actual usage and monthly pipeline bills

o Calculate total PGW usage utilizing gate station volumes and supplemental gas(net).

o Compare preliminary pipeline metering to daily usage by activity number and gate station.

o Track off-system sales(natural gas, LNG, etc.), on site storage, off system storage and internal plant usage

o For GTS customers track nominations, confirmations daily usage, line loss and over/under.

o Track mark to market position for both financial and physical trading/hedging activities

o Accept volumes from all sources (by activity number) to permit the detailed calculation of the natural gas purchased, utilized, sold and unaccounted for.

o Provide on-line approval of natural gas invoices from suppliers. o Provide daily cash flow requirements for fuel purposes. o Produce fuel cost summary and sales o Provide summary of fuel costs and sales volumes for GCR reconciliation

purposes. o Maintain detailed inventory records by location. o Interface with the general ledger, supplying the necessary natural gas, fuel as

appropriate. o Apply highest avoidable cost of gas to a transaction o Provide for invoice approval at a senior level and issue the invoice by email, fax

or printed PDF o Provide a contract summary for all Vendors to match with Vendor invoices. o Utilize Voucher # with separate Voucher summary details for approved invoices. o Permit partial approval of vendor invoices; for example; for pipelines that invoice

demand charges and capacity release credits separate from commodity charges.

o Provide for a Manual adjustment for rounding errors and a Manual update for all rounding errors to the GL Account category to balance the invoice verses the system totals.

o Upload vendor invoice and calculation documents referenced to the voucher # and to the Contract and invoice month.

o Provide for invoice charge approval and closure of the vendor invoice. o Provide for actual/reconciled vendor expense invoice and company revenue

invoices to be approved and locked for the accounting month. o Provide for excel exports and other transaction summaries for PUC and other

gas utility reporting requirements. o Ability to generate and export reports to MS office programs


of 77

Contract Management & Repository This is a general purpose sub-module for managing all contracts the company utilizes in its business. The following types of contracts and management features are available:

o Support monitoring of compliance with contract terms o Maintain a complete profile of supplier and customer relationships o Provide single source of contract status information o Allow for formula-based pricing o Contract Header with status, approval cycle, term dates, Units/currency, and

alert notices are in the header and common to all contract types. The integration of data and application business processes are structure in a Contract. All transactions require a supporting contract document.

o Contract Amendments are time series and include a document upload and view feature to attach scanned documents, PDF Files or miscellaneous other contract documents indexed by amendment data.

o Additional features for additional terms and conditions, notes/brief and other contract data.

o Contract types include; 1. NAESB master purchase/sell agreements with optional demand

charge/swing fees. 2. Pipeline transportation for interstate pipelines with Demand and

commodity charges and supporting Capacity Release options. Applicable rate types include “Postage Stamp” and “Zone to Zone” with MDQ assignments at the contract level or at applicable zones or receipt/delivery points. Contracts may be seasonal with User defined seasons with seasonal MDQ and commodity charge rates. Capacity balance calculations are available daily to assess capacity remaining after release transactions and deduction of scheduled gas to calculate net available capacity.

3. Storage Operator with support for storage pools with WACOG and FIFO inventory and valuation options. Capacity Release is supported along with storage ratchet monitoring and adjusted with capacity release transactions.

4. Asset Management for both Pipeline and Storage contracts with term capacity release to the asset manager. Scheduling of revenue or expense fees for the asset contract with proper accounting treatment.

5. Marketer pooling agreement to establish the retail choice pool manager terms and conditions for nominations and imbalance determination.

6. Transportation customer time series association of customer assigned premise to the Marketer or pool or Agent affiliation. This function is also available in the BA-CIS module to centralize the contract maintenance after setup.

7. Market trading agreement that is used to support allocation of trading fees, such as ICE, to NAESB physical purchase and sales deals.

8. These are the Contract Types generally associated with the gas utility; however, additional types may be required for specific applications, such as LNG and Propane asset management.


of 77

Reports Ability to generate and export information to MS office programs.

Retail/Integrated Solution Module The Choice/Retail module is integrated at the database level and supports gas suppliers and transportation customers within the same workflow and data structures as the other components of the IGMS. This module is used to setup and maintain the following:

Entity Management/Business Associates This sub-module is repository of information about the company and the third party suppliers. The required information and services include but are not limited to the following

o Entity/BA names, pool IDs, start and end activity dates, Duns numbers, revenue account numbers, addresses, invoice information, contacts, and EBB user criteria and log in credentials.

o Set up entities for Choice activities o Access to setup and maintain entity contract terms and conditions as well as

be able to use free format notes to support narrative text about the entities o Document upload and view capabilities for common file extensions for MS

Office, scanned images, PDF, etc. o Document upload features for the EBB to send to all or selected EBB users. o Export & ad-hoc functionality for entity information

Data Management This sub-module serves as the primary link between the CIS and the Gas Management activities pertaining to retail customers (pooled – aggregated and non-aggregated, or operating as independent commercials operating through an agent or independent /GTS customers). This sub-module is to store, view, and query, customer data for daily administrations of all system entities and their pools, including PGW and its IT and FT pools. The required information and services include but are not limited to the following

o SP management – start and end dates with entities to track all responsible parties for gas service at the premise

o SP/Meter type management to ensure proper relationship between customer and supplier pool.

o View metered daily and monthly consumption o Ability to store and edit volumes, historical and current BTU factors,

historical and current system loss factors, daily system load, daily LNG load. o Ability import Scada data via a synch ad-hoc job (system load, LNG Load,

BTU factors weather data) o Ability to run ad-hoc synch job with the CIS system. o Ability to upload yearly aggregate customer usage profiles to use for

forecasting and capacity allocation o Store historical meter data for regression analysis, design day calculation

and capacity releases. o Forecasting for Firm Transportation (FT) pools. Types of forecasting are:

1. Daily bottom up base/weather dependent forecast 2. Average day forecast 3. Design day forecast 4. Flat monthly forecast


of 77

o Ability to export forecasting volumes to the EBB o Capacity allocation rules and capacity allocation per FT customer and for

entire FT pool for each supplier. o Ability to export to EBB capacity allocation data by customer for each FT

pool as well as the total pool capacity allocation volumes.

Pipeline Contracts This sub-module provides for setup and maintenance of pipeline points, both physical and virtual locations as well as contracted volumes.

o Off-System points for gas delivery pipelines generally include receipt, delivery, pooling, interconnect, storage and injection/withdrawal points. In some circumstances a “Master Point” is needed to group points for a specific purpose; such as, aggregating delivery from multiple pipeline to a single City Gate reference point.

o On-System points for Customers, Marketer retail choice and imbalance pools, Gate Stations and City Gate reference points for gas supply aggregation and On-system imbalance calculation

o Gate Station update program to load pipeline measurement data and reference scheduled gas to determine imbalance positions

Rates This sub- module is the repository of all rates for the interstate off-system pipelines and for the On-system pooling, transportation, imbalance and other rates associated with supporting transportation customer and suppliers operating behind the city gates. The following are noted:

o Pipeline zone to zone rate structures including max rates o Rate override functions to record a time dependent override o Ability to store and edit current & historical design day rates (used for FT

pool invoicing). o Ability to store and edit billing charge components/rates

Settlement, Prices, & Supplier Billing This sub-module serves as an aggregation of nominations, deliveries, usage for supplier position monthly reconciliation and the billing calculations for each supplier pool. The required information and services include but are not limited to the following:

o Ability to import Dictated Daily Quantity (DDQ) volumes from the EBB o Ability to store and edit the DDQ schedules for each FT pool o Actualizing Delivery Schedules for all pools according to pipeline actual

delivery reports o Actual pool usage schedules for daily pools by day and service point ID o Ability to import customer usage information via ad-hoc jobs o Ability to store and edit daily pipeline (Transco and Tetco) and Wacog

prices o Cashout price calculations based on PGW tariff rules o Ability to import, store and edit pool trading information (entered on the EBB

by suppliers) o Calculate usage deltas (initial EBB usage – final EBB usage) created by

meter issues by day for each interruptible pool for the month. o Supplier billing calculation


of 77

o FT pool settlement after customer billing has completed for a given revenue month

o Ability to store and edit imbalance positions o Ability to store and edit payback positions for FT pools o Detailed invoices for all pools showing daily and monthly imbalance volumes

and charges. o Export functionality of all the above information. o Export Supplier billing data to CIS o Export imbalance and payback positions to the EBB for suppliers to view

Reports o Scada data report - BTU values (Transco, Tetco, System), System Load,

LNG Load, Retail Pool load. o Missing usage report – Daily SP missing usage o Log report o Other

Electronic Bulletin Board (EBB) The EBB is the primary communication link to the transportation customer, a customer’s agent and a supplier serving one or more customers in a pool. The company objective is to push all interaction with one of these parties to the EBB. The features include:

o Complete integration with the workstation version of the on-system business processes with near identical display information and control features included in the workstation version.

o General public information postings of documents and messages accessed without a User ID and Password to send public broadcast messages and to post tariff’s, sign-up information and other data relative to managing the end user transportation program.

o Password and User ID enabled security with expiring password reset options for authorized suppliers and users.

o Provide a contact list for all suppliers operating on-system with key contact information.

o Private document and information postings targeted exclusively to authorized EBB Users.

o Display the DDQ for suppliers once the forecasting has been completed. o Provide for nomination input from the city gate point to a pool or individual

customer point/location o Require an upstream pipeline, contract number and supplier info/pool id for

all nominations. o Schedule gas as delivered or receipt quantity with appropriate fuel

adjustment. o Permit daily or multiple day nomination to be entered. o Support a nomination as a receipt and delivery path or as a single receipt

and multiple delivery points. o Permit use of an Activity number to simplify making a nomination o Permit a day ahead change to a nomination. o For pool nominations with a daily target, provide a scheduling imbalance

determination.


of 77

o Provide a Customer listing to include any calculated estimate for daily consumption, such as a Daily Demand Quantity (DDQ) and include a drill down option to view consumption history.

o For all customer pools, provide a daily and end of month rollup to a pool total with determination of daily and monthly imbalance.

o For pools with daily metered customers, provide a pool drilldown to view pool status including daily imbalances. Further drill down to view customers in a pool and daily consumption.

o For pools with cycle read customers, rollup the cycle data and provide a pool total position with drill down to view each customer’s consumption applied.

o Provide an end of month pool imbalance and for cycle read customers, estimate the pool unbilled quantity

o Provide for imbalance trading among suppliers. o Display Capacity released to the marketer or customer on upstream

pipelines and/or storage pools. o Present end of month Imbalance calculations, other revenue determinants

and display the back- up data for invoicing. o Support Microsoft Office, PDF and scanned document upload to the

database for consumption by company personnel. o Provide for email to be generated from the EBB to the company. o Provide a dashboard to view transaction statistics relative to all EBB User

business processes. o Support mobile rendering of the EBB on tablets and smart phones for

revising nominations and viewing business data.

IGMS Interface Requirements The new IGMS system should work with Oracle Financials, CIS and SCADA interfaces. All the data within the current Choice systems should be migrated over to the new IGMS.


of 77

Requirements Matrix

Complete the following matrix:

Gas Management System Module

Requirement / Specification

Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required

Explain how the Requirement is Accomplished,

Suggest an Alternative or Explain Any Required

customizations

1 This group of modules includes the business practices for acquiring, transporting, storing and accounting for gas supplies required to meet the utility’s customer obligations

1.1 Gas Acquisition

1.1.1 Provide the capability to create, modify and review gas transactions from nomination to delivery.

1.1.2 Maintain on-line information to track the commodity and breakout segment costs, including the commodity, transportation and fuel.

1.1.2.1 Monitor all gas supply transactions to meet demand requirements based on available capacity and supply options.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.1.2.2 Price reference repository of index price information and for other costs and fees not generally associated with a published index such as Gas Daily, Inside FERC, Henry Hub, etc. Additional features include:

1. Rapid mass input screen for manual update of index prices;

2. Automated input of downloaded price information such as Platt’s data.

3. Mass recalculation of all physical deals referenced to a price index;

4. Logic to guide application of an index such as validation, last updated or specific date and other attributes to support flexible use of the data.

1.1.3 Support off-system sales, commodity purchases/deals and capacity release transactions. All transactions will be in accordance with the NAESB Master Contract and also include additional features common to a utility’s business practices.

1.1.3.1 NAESB compliant master contract terms and conditions

1.1.3.2 FAS 133 Documentation for the Normal Purchase / Sales Exception retained for audit purposes.

1.1.3.3 Purchase status designation of at least: Pending, Rejected, Accepted, Approved, Confirmed and Amended.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.1.3.4 Time series of status changes with designation of change date and User Stamp.

1.1.3.5 Software security control over which User IDs have deal input/edit and view privileges or no privileges Ability to Copy a Deal day to day or month to month.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.1.3.6 Deal Setup Attributes:

a. Counter party and company designated gas trader with contact number.

b. Selection of a daily, Dth/Day, or monthly, Dth/Month, deal quantity

c. Designation and input of a fixed or indexed deal price

d. Selection of an index adjustment as a +, - or * number—add, subtract or multiply adjustment to the index.

e. Selection of a market service contract for including a 3

rd party transaction fee in the total deal $ amount.

f. Selection of transporter pipeline and transaction point

g. User defined codes to tag deals for reporting and accounting;

i. Deal type such as option, spot, swing, base load, purchase for resale, etc.

ii. Flow type such as firm, spot, or any other defined attribute

iii. Transaction type such as send-out, injection, off system Sale, etc.

h. FERC 552 designation in a drop down list.

i. Integrate the Transaction Confirmation process through the system and capture additional comments.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.1.3.7 Grid listing of deal data elements with ability to sort by a selected column and to export deals to an excel spreadsheet.

1.1.4 Ability Track mark to market position for both financial and physical trading/hedging activities

1.1.4.1 Grid sort attributes such by pipeline, a company defined code for deal and transaction type, and FERC 552 code

1.1.4.2 Ability to show all deals or only deals with a specific counter party

1.1.4.3 Subtotal screen display of sub-total by counter party over a User selected date range1-12 months.

1.1.4.4 Track deal total quantity per day and scheduled quantity to identify unscheduled quantities.

1.1.4.5 Link deals to a scheduling transaction to path gas from a purchase or to a sale point.

1.1.4.6 Handle Deal Confirmations through the system and capture the deal quantity by day and have a dynamic setup for deal terms.

1.1.4.7 Retain deal confirmation data to regenerate a confirmation for internal audit review. Historical retention of each confirmation per the company’s audit requirements.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.1.4.8 Provide an effective method for amending a deal to change quantities and reissue a confirmation.

1.1.4.9 Provide a deal status history to track status changes for audit purposes.

1.1.4.10 Provide a calendar view of a deal to highlight the daily quantity, scheduled quantity, remaining to be scheduled/make-up/retro etc. and the daily price.

1.1.4.11 Provide a method of updating the deal price by refreshing all deals with updated index prices.

1.1.4.12 Provide a Platt’s upload option for inserting index prices.

1.1.4.13 Provide for gas purchase on an Asset Management contract. The purchase is for injection; thus the deal setup includes the injection path. The purpose is to inject into a storage asset under an asset management contract.

1.1.4.14 Provide for a controlled process for purchasing for injection where the purchase is pathed directly to Storage. The requirement is to simplify filling company managed storage facilities.

1.1.4.15 Provide for multi-pipeline reusable route to be setup to path gas from or to a deal transaction. The route may include any number of paths to complete the purchase or deal disposition.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.1.4.16 Provide a pathing analysis tool to determine the cost of delivered gas given a multi-path route for transportation.

1.2 Gas Transportation This sub-module would enable the Gas Supply and Acquisition Department’s Natural Gas Transportation area to efficiently integrate and centralize the flow of natural gas based on the various gas day variables; load, weather, supply, demand, and other determinants. This module is to record natural gas scheduled on interstate pipelines and storage contacts; apply rate structures and provide for transaction accounting. The storage module will support standard storage transactions to include WACOG. The required information and services include but are not limited to the following:

1.2.1 Support for pipeline Activity Numbers for scheduling gas.

1.2.2 Include a NAESB compliant data set to facilitate communication and synchronization with Pipeline datasets.

1.2.3 Provide for MS Excel file uploads of timely and intraday nominations to pipeline systems.

1.2.4 Support business processes for interstate pipelines, storage facilities and asset management contracts for pipeline and storage transactions.

1.2.5 Display daily and monthly scheduled gases in a grid structure to facilitate export of the data in a User defined excel format.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.2.6 Support setup of multi pipeline and/or contract routes to path gas from a linked purchase or pipeline point to a destination point.

1.2.7 Calculate fully loaded delivery cost per Dth from a pipeline purchase or pooling point to a destination point, such as the City gate delivery point or a storage pool. Manage both quantity and value in the scheduling path.

1.2.8 Provide a daily and end of month summary city gate WACOG report breaking out delivered purchase and storage quantities to the city gate.

1.2.9 Provide a flexible method of entering a revised price or fuel deduction at a receipt point and cascade the change through all linked packages to the destination point

1.2.10 Provide a flexible method for displaying point balances to easily spot imbalance situations along a pipeline or at a city gate delivery point.

1.2.11 For a city gate or pipeline pooling point show the imbalance and the transactions into and out of the point. Hot link to a deal or nomination setup screen to clear the imbalance.

1.2.12 For city gate points include company nominations as well as supplier/customer nominations in the imbalance calculation.

1.2.13 Provide for pipeline no-notice storage (NNS) or OBA balance daily with an auto-nomination into the OBA or NNS pool points. Transactions from the city gate are to be valued at the daily WACOG at the CG point.

1.2.14 Import or manually insert daily gate station measurement data to combine with company and supplier/customer nomination to determine the actual imbalance.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.2.15 Automatically insert supplier/customer scheduled gas into the imbalance calculation based on nominations made on the applicable gas utility’s pipeline points.

1.2.16 Support capacity release of demand and storage capacity in a NAESB compliant data set to position for an excel upload of released capacity to the pipeline.

1.2.17 Support capacity release to on-system suppliers with notification or released amounts on the supplier and customer web portal, EBB.

1.2.18 Support capacity release/assignment in accordance with an asset management contract to include pipeline demand and storage demand and capacity.

1.2.19 Copy capacity releases from a current to a future month.

1.2.20 Perform a daily aggregation of flowing gas and capacity release per pipeline contract to track capacity available by zone or per contract. Display the net MDQ by point or zone with a display of total MDQ and the deductions.

1.2.21 Display storage pools in a grid for excel export with a display of beginning inventory, value and WACOG with injections, withdrawals, adjustments and the ending inventory, value and WACOG.

1.2.22 Provide for a drill down to view daily transaction over the full month.

1.2.23 Monitor storage capacity available and the injection and withdrawal MDQ as adjusted for storage capacity and demand releases.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.2.24 Validate withdrawal and injection against the adjusted IJ and WD MDQ values and issue a warning should the adjusted MDQ be exceeded.

1.2.25 Provide the ability for retro and prior period adjustments.

1.2.26 Provide functionality to copy nominations from a current month to a future month.

1.2.27 Provide a filter feature that allows the system to identify the nomination contract (i.e.; Shell Base load 2013-2014 Winter).


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.3 Gas Accounting Module This sub-module provides auditable vendor invoice reconciliation and customer invoicing, off-system and on-system revenue transactions. It records all gas transactions: nominations, confirmations, metered receipts, on-site storage, non-residential sales, both PGW sales and transport, plant use and deliveries to the city distribution system. Calculates the appropriate unit cost of gas for the various inventories and usages and associate these costs with the appropriate volume statements. Applies actual or estimated costs to the volumes developed in the measurement and reconciliation phase to permit the generation of journal entries for inclusion in the general ledger. The full, costed data should permit the generation of management reports of the summary of fuel costs, sales and revenues and the sales and cost details underlying the GCR tariff operation. The following summarizes the features necessary for reconciling end of month gas acquisition contract transactions:

1.3.1 Access daily pipeline reports, actual usage and monthly pipeline bills

1.3.2 Actualize pipeline volumes five (5) business days into the new month.

1.3.3 Access preliminary pipeline invoices for middle and end of month estimated reports.

1.3.4 Enter pricing from OBO, spot gas sheets, and rates from pipeline tariffs.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.3.5 Input gas inventory pricing supplied by Accounting Department.

1.3.6 Generate asset management invoices in accordance with asset management contract.

1.3.7 Input supplier delivered volumes from the PGW Electronic Bulletin Board (EBB).

1.3.8 Track NYMEX price closes on a daily basis to generate comparison charts.

1.3.9 Create comparison report with Natural Gas Estimate, Actual Gas Cost, the PGC Filed Budget, the avoided cost total and the GCR

1.3.10 Calculate total volumes, injections, and withdrawals for estimate purposes that include dollar values

1.3.11 Extracting and inputting tariff rate changes

1.3.12 Calculation of Buyback pricing to be sent to PGW’s CRC department

1.3.13 Ability to extract pipeline volumes designated for Grays Ferry ARS contract for the period beginning November through March with pricing

1.3.14 Calculate total PGW usage utilizing gate station volumes and supplemental gas (net).

1.3.15 Compare preliminary pipeline volumes to PGW nominated gas volumes

1.3.16 Track off-system sales(natural gas, LNG, etc.), on site storage, off system storage and internal plant usage

1.3.17 For GTS customers track nominations, confirmations daily usage, line loss and over/under.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.3.18 Accept volumes from all sources (by activity number) to permit the detailed calculation of the natural gas purchased, utilized, sold and unaccounted for.

1.3.19 Provide on-line approval of natural gas invoices from suppliers and pipelines.

1.3.20 Provide daily cash flow requirements for fuel purposes.

1.3.21 Produce fuel cost summary and sales

1.3.22 Provide summary of fuel costs and sales volumes for GCR reconciliation purposes.

1.3.23 Maintain detailed inventory records by storage location.

1.3.24 Interface with the general ledger, supplying the necessary natural gas, fuel as appropriate.

1.3.25 Apply highest avoidable cost of gas to a transaction

1.3.26 Provide for invoice approval at a senior level and issue the invoice by email, fax or printed PDF

1.3.27 Provide a reconciliation summary for all Vendors to match with Vendor invoices.

1.3.28 Utilize Log# with separate Log summary details for approved invoices.

1.3.29 Daily comparison of PGW capacity release awards to pipeline award data. Generate reports for all capacity release awards for varying time frames in response to Interrogatories.

1.3.30 Access capacity release awards in accordance with Grays Ferry contract for the period beginning May through September


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.3.31 Generate e-mails for end of month reporting of estimates, Cogen memo, and other associated documents

1.3.32 Provide for a Manual adjustment for rounding errors and a Manual update for all rounding errors to the GL Account category to balance the invoice verses the system totals.

1.3.33 Upload vendor invoice and calculation documents referenced to the Log # and to the Contract and invoice month.

1.3.34 Generate expenses for the month including supplier invoices, transportation costs broken down by demand charges per pipeline and supplier.

1.3.35 Provide for excel exports and other transaction summaries for PUC and other gas utility reporting requirements.

1.3.36 Ability to interface with Financial systems for accounting purposes.

1.4 Contract Management & Repository This is a general purpose sub-module for managing all contracts the company utilizes in its business. The following types of contracts and management features are available:

1.4.1 Support monitoring of compliance with contract terms

1.4.2 Maintain a complete profile of supplier and customer relationships

1.4.3 Provide single source of contract status information

1.4.4 Allow for formula-based pricing


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.4.5 Contract Header with status, approval cycle, term dates, Units/currency, and alert notices are in the header and common to all contract types. The integration of data and application business processes are structure in a Contract. All transactions require a supporting contract document.

1.4.6 Contract Amendments are time series and include a document upload and view feature to attach scanned documents, PDF Files or miscellaneous other contract documents indexed by amendment data.

1.4.7 Additional features for additional terms and conditions, notes/brief and other contract data.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.4.8 Contract types include; 1. NAESB master purchase/sell agreements with

optional demand charge/swing fees. 2. Pipeline transportation for interstate pipelines

with Demand and commodity charges and supporting Capacity Release options. Applicable rate types include “Postage Stamp” and “Zone to Zone” with MDQ assignments at the contract level or at applicable zones or receipt/delivery points. Contracts may be seasonal with User defined seasons with seasonal MDQ and commodity charge rates. Capacity balance calculations are available daily to assess capacity remaining after release transactions and deduction of scheduled gas to calculate net available capacity.

3. Storage Operator with support for storage pools with WACOG and FIFO inventory and valuation options. Capacity Release is supported along with storage ratchet monitoring and adjusted with capacity release transactions.

4. Asset Management for both Pipeline and Storage contracts with term capacity release to the asset manager. Scheduling of revenue or expense fees for the asset contract with proper accounting treatment.

5. Marketer pooling agreement to establish the retail choice pool manager terms and conditions for nominations and imbalance determination.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.5 Reports Ability to generate and export reports to MS office programs.

1.5.1 Estimated monthly total volumes and dollars broken out by pipeline and storages (gas supply meeting estimate)

1.5.2 Capacity release award report showing total monthly capacity release volumes and dollars for pipelines.

1.5.3 Reversal of prior month’s capacity releases.

1.5.4 Off system sales

1.5.5 Asset management deals

1.5.6 Pipeline refunds

1.5.7 Natural Gas Cost Estimate that includes total volumes and breakdown by pipeline of the demand charges, commodity charges, and capacity release credits.

1.5.8 Purchase activity

GTS accruals and reversals

Gas purchase estimates

Reversal of gas purchase estimate for prior months

1.5.9 Total natural gas billed – Volumes and dollar amounts

Demand Charges

Purchase Types (SPOT, GTS, Off System etc.)

Natural Gas Refunds (Principal and Interest) by pipeline

Transport fuel by pipeline


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

1.5.10 Natural gas to underground storage – Volumes and dollar amounts per storage entity

Injection fuel by storage facility

Injection charges by storage facility

FT delivered to underground storage by storage facility

1.5.11 Natural gas withdrawn from Storage – volumes and dollar amounts per storage facility

Withdraw fuel by storage facility

Withdraw charges by storage facility

FT withdrawn from underground storage by storage facility

1.5.12 Natural gas storage levels by storage facility

1.5.13 Injection, Withdraw and Ending Balance positions by storage facility

1.5.14 LNG activity reports

2 Retail/Integrated Solution Module The retail module is integrated at the database level and supports gas suppliers and transportation customers within the same workflow processes and data structures as the other components of the IGMS. This module is used to setup and maintain the following:


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

2.1 Entity Management/Business Associates This sub-module is a repository of information about the company and the third party suppliers. The required information and services include but are not limited to the following

2.1.1 Entity/BA names, pool IDs, start and end activity dates, Duns numbers, revenue account numbers, addresses, invoice information, contacts, and EBB user criteria and log in credentials. Set up entities for Choice activities

2.1.2 Access to setup and maintain entity contract terms and conditions as well as be able to use free format notes to support narrative text about the entities

2.1.3 Document upload and view capabilities for common file extensions for MS Office, scanned images, PDF, etc.

2.1.4 Document upload features for the EBB to send to all or selected EBB users.

2.1.5 Export & ad-hoc functionality for entity information

2.2 Data Management This sub-module serves as the primary link between the CIS and the Gas Management activities pertaining to retail customers (pooled – aggregated and non-aggregated, or operating as independent commercials operating through an agent or independent /GTS customers). This sub-module is to store, view, and query, customer data for daily administrations of all system entities and their pools, including PGW and its IT and FT pools. The required information and services include but are not limited to the following


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

2.2.1 SP management – start and end dates with entities to track all responsible parties for gas service at the premise

2.2.2 SP/Meter type management to ensure proper relationship between customer and supplier pool.

2.2.3 View metered daily and monthly consumption. Ability to run ad-hoc synch job with the CIS.

2.2.4 Ability to store and edit volumes, historical and current BTU factors, historical and current system loss factors, daily system load, daily LNG load. Ability to import Scada date via synch ad-hoc job (system load, LNG load, BTU factors, weather data).

2.2.5 Ability to upload yearly aggregate customer usage profiles to use for forecasting and capacity allocation

2.2.6 Store historical meter data for regression analysis, design day calculation, average day, and capacity releases.

2.2.7 Forecasting at the Service Point and Pool level for Firm Transportation (FT) pools. Types of forecasting are:

1. Bottom up base/weather dependent forecast 2. Average day forecast 3. Design day forecast 4. Flat monthly forecast 5. Ability for export forecasting volumes to the EBB

2.2.8 Capacity allocation rules and capacity allocation per FT customer and for entire FT pool for each supplier.

2.2.9 Ability to export to EBB the monthly capacity allocation, design day, and average day forecasting data by customer for each FT pool as well as the total pool capacity allocation volumes.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

2.3 Pipeline Contracts This sub-module provides for setup and maintenance of pipeline points, both physical and virtual locations as well as contracted volumes.

2.3.1 Off-System points for gas delivery pipelines generally include receipt, delivery, pooling, interconnect, storage and injection/withdrawal points. In some circumstances a “Master Point” is needed to group points for a specific purpose; such as, aggregating delivery from multiple pipeline to a single City Gate reference point.

2.3.2 On-System points for Customers, Supplier retail choice and imbalance pools, Gate Stations and City Gate reference points for gas supply aggregation and On-system imbalance calculation

2.3.3 Gate Station update program to load pipeline measurement data and reference scheduled gas to determine imbalance positions

2.4 Rates This sub- module is the repository of all rates for the interstate off-system pipelines and for the On-system pooling, transportation, imbalance and other rates associated with supporting transportation customers andsuppliers operating behind the city gates.

2.4.1 Pipeline zone to zone rate structures including max rates

2.4.2 Rate override functions to record a time dependent override

2.4.3 Ability to store and edit current and historical design day rates (used for FT pool invoicing)

2.4.4 Ability to store and edit billing charge components/rates.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

2.5 Settlement, Prices, & Supplier Billing This sub-module serves as an aggregation of nominations, deliveries, usage for supplier position monthly reconciliation and the billing calculations for each supplier pool. The required information and services include but are not limited to the following:

2.5.1 Ability to import Dictated Delivery Quantity (DDQ) from the EBB.

2.5.2 Dictated Daily the DDQ schedules for each FT pool

2.5.3 Actualizing delivery schedules for all pools according to pipeline actual delivery reports

2.5.4 Actual pool usage schedules for daily pools by day & service point

2.5.5 Ability to import customer usage information via ad-hoc synch jobs with the CIS.

2.5.6 Ability to store and edit daily pipeline (Transco, Tetco) and Wacog prices

2.5.7 Cashout price calculations based on PGW tariff rules

2.5.8 Ability to import, store and edit pool trading information (entered on the EBB by suppliers)

2.5.9 Usage deltas (initial EBB usage – final EBB usage) created by meter issues by day for each interruptible pool for the month.

2.5.10 Supplier billing calculation

2.5.11 FT pool settlement after customer billing for the revenue month

2.5.12 Ability to store and edit imbalance positions


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

2.5.13 Ability to edit payback positions for FT pools

2.5.14 Generate detailed invoices for all pools showing daily and monthly imbalance volumes and charges.

2.5.15 Export functionality of all the above information

2.5.16 Export Supplier billing data to CIS

2.5.17 Export imbalance and payback positions to the EBB for suppliers to view

2.6 Reports

2.6.1 SCADA data report - BTU values (Transco, Tetco, System), System Load, LNG Load, Retail Pool load.

2.6.2 Missing usage report – Daily SP missing usage

2.6.3 Log report

2.6.4 Storage positions for Firm pools, cumulative and for the month

2.6.5 Imbalancing positions by pool

2.6.6 Billing Charges for given period and given supplier pool

2.6.7 Capacity release volumes for given period and given Firm pool

2.6.8 Other

3 Electronic Bulletin Board The EBB is the primary communication link to the transportation customer, a customer’s agent and a supplier serving one or more customers in a pool. The company objective is to push all interaction with one of these parties to the EBB. The features include:


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

3.1 Complete integration with the workstation version of the on-system business processes with near identical display information and control features included in the workstation version.

3.2 General public information postings of documents and messages accessed without a User ID and Password to send public broadcast messages and to post tariff’s, sign-up information and other data relative to managing the end user transportation program.

3.3 Password and User ID enabled security with expiring password reset options for authorized suppliers and users.

3.4 Provide a Contact list for all suppliers operating on-system with key contact information.

3.5 Private document and information postings targeted exclusively to authorized EBB users.

3.6 Display “Choice” pool targets daily for suppliers.

3.7 Provide for nomination input from the city gate point to a pool or individual customer point/location

3.8 Require an upstream pipeline, contract # and Supplier info/ pool ID for all nominations.

3.9 Schedule gas as delivered or receipt quantity with appropriate fuel adjustment.

3.10 Permit daily or multiple day nomination to be entered.

3.11 Support a nomination as a receipt and delivery path or as a single receipt and multiple delivery points.

3.12 Permit use of an Activity number to simplify making a nomination

3.13 Permit a day ahead change to a nomination.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

3.14 For pool nominations with a daily target, provide a scheduling imbalance determination.

3.15 Provide a customer listing to include any calculated estimate for daily consumption, such as a Daily Demand Quantity (DDQ) and include a drill down option to view consumption history.

3.16 For all customer pools provide a daily and end of month rollup to a pool total with determination of daily and monthly imbalance.

3.17 For pools with daily metered customers, provide a pool drilldown to view pool status including daily imbalances. Further drill down to view customers in a pool and daily consumption.

3.18 For pools with cycle read customers, rollup the cycle data and provide a pool total position with drill down to view each customer’s consumption applied.

3.19 Provide an end of month pool imbalance and for cycle read customers, estimate the pool unbilled quantity

3.20 Provide for imbalance trading among suppliers.

3.21 Display Capacity released to the supplier or customer on upstream pipelines and/or storage pools.

3.22 Present end of month Imbalance calculations, other revenue determinants and display the back- up data for invoicing.

3.23 Support Microsoft Office, PDF and scanned document upload to the database for consumption by company personnel.


of 77



Vendor

Capability

(Y)es, (N)o,

(C)ustomization

Required



customizations

3.24 Provide for email to be generated from the EBB to the company.

3.25 Provide a dashboard to view transaction statistics relative to all EBB User business processes.

3.26 Support mobile rendering of the EBB on tablets and smart phones for revising nominations and viewing business data.

4 IGMS Interface Requirements The proposed IGMS system must interface leverage use of existing interfaces with PGW’s current Oracle E-Business Suite Financial System, CIS Plus Customer Information System, and SCADA.


of 77

Appendix 2. Development Standards

Any custom development required to support this solution (interfaces, customizations, etc.) must adhere to PGW’s development standards:

IEEE 12207-2008 – Standard for Systems and software engineering - Software life cycle processes IEEE 1540 – Standard for Software Lifecycle Processes – Risk Management IEEE 829 – Standard for Software and System Test Documentation IEEE 1008 – Standard for Software Unit Testing

PGW Development Environment can accommodate software development in

the following frameworks:

.Net Framework 4.0 and above

VB .NET

ASP .NET

Oracle 11g (preferred) MS SQL Server 2008 (acceptable)

Oracle Financials 12.1.3

Integration with PGW internal systems may be possible using web-services and/or sftp.

Microsoft SSRS for custom reporting.

Programming Standards - Visual Studio 2012 .NET

The following link provides coding conventions (recommendations) for application development. The sub-sections that follow define the basic requirements recommended for all PGW applications that use Visual Studio projects.

http://msdn.microsoft.com/en-us/library/vstudio/h63fsef3(v=vs.110).aspx

Operational Environment

Desktop OS Windows 7

Servers: Windows 2008 or above, SUSE Linux 11

Browser: Internet Explorer 9 and above.


of 77

Appendix 3. Testing and Acceptance Standards PGW considers testing to be an integral part of the entire development and implementation life cycle. PGW requires the successful Proposer to meet our testing standards regardless of where the solution will be hosted. This life cycle includes the following:

Certification Test Plans. PGW will require the successful Proposer to certify in writing that all code provided by the Proposer is free of defects, and must, prior to certification, submit test plans for PGW’s review and comment that describe and support the certification process for each of module of the application (the “Certification Test Plans”). The Certification Test Plans should be comprehensive in nature and assure that each module and the system as a whole meets the functional specifications as defined and agreed to during the design phase and that the system performs in an acceptable manner. The Certification Test Plans shall also describe the unit tests to be performed by the Proposer on the individual components within each module included in the application system. The unit-tested code in each module must be free of defects.

Integration Testing After all modules of the application system have been individually tested and certified, the entire application system will be installed and configured on PGW’s test environment. The successful Proposer is responsible, in conjunction with PGW’s Quality Assurance (QA) Team and business users, for integration testing on the entire application system to assure that the system is ready for PGW acceptance testing. PGW and the Proposer will create an integration test plan, which must be comprehensive enough to demonstrate that sufficient load testing has been accomplished to assure that the application system will meet the response time requirements as defined in the scope of work. Any defects found during integration testing to be the result of code provided by the successful Proposer must be fixed by the Proposer within one day of discovery. The successful Proposer must be able to demonstrate that all round-trip transactions have been tested through the entire transaction flow.

Reliability Testing Reliability testing will be performed by the successful Proposer and PGW’s QA Team and business users to verify that the entire application will satisfy the requirement of processing a normal daily workload of the PGW client departments and personnel. Those PGW business users shall jointly make the final determination as to whether the system passes the reliability test based on a minimum of 95% success rate on functional requirements test cases and must include only “Low Priority” defects. Defects are prioritized as follows:

High – The defect results in the failure of the transaction or application.

Medium – The defect does not result in a failure, but causes the system to produce incorrect, incomplete, or inconsistent results, or the defect impairs the application system’s usability.

Low – The defect does not cause a failure, does not impair usability, and the desired processing results are easily obtained by working around the defect.

Functional, Regression, and Acceptance Testing


of 77

The PGW QA Team and business users will be responsible for fashioning and conducting functional, regression and acceptance testing, with the Proposer’s assistance. The application system and services provided shall not be finally accepted unless and until all Services and Deliverables required under the contract have been completed, delivered and signed off by PGW as being in conformance with the requirements of the scope of work and the terms and conditions of the contract. Once the successful Proposer and PGW have agreed that the system is ready for user acceptance testing, PGW will have 60 days to complete all user acceptance testing activities and either accept or reject the system in part or in whole. During acceptance testing the successful Proposer will have 5 calendar days to correct any reported system application defects identified by PGW. If a defect has not been corrected in 5 days, PGW at its reasonable discretion will have the option of stopping acceptance testing until all reported defects have been corrected. If PGW should identify a significant problem or system defect (one which would prevent the system from being deployed to production) during the final 2 weeks of acceptance testing, all acceptance testing will be halted until the defect is corrected; PGW will have a minimum of 30 days from that point to accept and/or reject the system in whole or in part.

Testing Tools PGW’s QA Team uses the HP Quality Center test tool set to conduct testing. The successful Proposer must provide an electronic version of all test scripts in a format that can be imported into PGW’s version of the HP product to facilitate acceptance testing by PGW.

Testing Standards All testing documentation provided by the successful Proposer must conform to the IEEE 829 as follows:

A Test Plan describes the scope, approach, resources, and schedule of the testing activities. It identifies the items to be tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the risks associated with the plan.

A Test Specification consists of (three document types): 1. A test design specification refining the test approach and identifying the

features to be covered by the design and its associated tests. It also identifies the test cases and test procedures, if any, required to accomplish the testing and specifies the feature pass/fail criteria.

2. A test case specification documenting the actual values used for input along with the anticipated outputs. A test case also identifies constraints on the test procedures resulting from use of that specific test case. Test cases are separated from test designs to allow for use in more than one design and to allow for reuse in other situations.

3. A test procedure specification identifying all steps required to operate the system and exercise the specified test cases in order to implement the associated test design. Test procedures are separated from test design specifications as they are intended to be followed step by step and should not have extraneous detail.

Test reporting consists of (three document types): 1. A test log used by the test team to record what occurred during test

execution. 2. A test incident report describing any event that occurs during the test

execution which requires further investigation. 3. A test summary report summarizing the testing activities associated with one

or more test design specifications.

PHILADELPHIA GAS WORKS REQUEST FOR ......2014/10/07 · Philadelphia Gas Works – Request For...

Documents

Transcript of PHILADELPHIA GAS WORKS REQUEST FOR ......2014/10/07 · Philadelphia Gas Works – Request For...