Request for Proposal - Granicus

Request for Proposal July 9, 2014 Advanced Metering Infrastructure, Meter Data Management & Outage Management System

Advertise Date: JULY 9, 2014 Due Date: SEPTEMBER 9, 2014

Prepared by: Azusa Light & Water 729 N. Azusa Avenue Azusa, CA 91702 In consultation with: UtiliWorks Consulting, LLC 2351 Energy Dr., STE 1200 Baton Rouge, LA 70808

Azusa AMI RFP of 47 6/17/2014

General Information, Terms and Definitions

Acronyms used in this RFP

AES Advanced Encryption Standard

ALW Azusa Light & Water

AMI Collector Receives data via RF from AMI Endpoints and AMI Repeaters

AMI Endpoint Transmitter that sends data from the meter to a collection point

AMI Headend Software Software that comprises the AMI application

AMI Repeater Relays RF signals from the AMI Endpoint to the AMI Collector

AMI System Advanced Meter Infrastructure System (including 2-way, network communications)

API Application Programming Interface

Backhaul Communications Facilitates transfer of data from AMI Collector to AMI Server (via Private RF, Public RF, Fiber Optic, etc.)

CIS Customer Information System (Utility Billing System)

CSR Customer Service Representative

DA Distributed Automation (of Electric Distribution System)

FSR Field Service Representative

GIS Geographic Information System

GPS Global Positioning System

IEEE Institute of Electrical and Electronics Engineers

MDM or MDMS Meter Data Management System

OMS Outage Management System

RF Radio Frequency

SCADA Supervisory Control and Data Acquisition

SGS Smart Grid as a Service

S&S Systems & Software (CIS System Support Vendor)

SSID Service Set Identification

TCP Transmission Control Protocol

UDP User Datagram Protocol

VLAN Virtual Local Area Network

Azusa AMI & MDM Project of 47 06/17/14

Table of Contents

1 INSTRUCTIONS .......................................................................................................... 6

1.1 PURPOSE AND APPLICABILITY OF THIS DOCUMENT ................................................................. 6

1.2 PROPOSER TEAMING ....................................................................................................... 6

1.3 EQUIPMENT LEAD TIMES .................................................................................................. 7

1.4 INTENT TO PROPOSE DUE DATE ......................................................................................... 7

1.5 PROPOSAL DUE DATE ...................................................................................................... 7

1.6 PROPOSAL SUBSCRIPTION ................................................................................................. 7

1.7 ALW CONTACT INFORMATION .......................................................................................... 7

1.8 QUESTIONS ................................................................................................................... 7

1.9 PRE-PROPOSAL MEETING – ATTENDANCE MANDATORY ........................................................ 8

1.10 PROPOSAL SUBMISSION ................................................................................................... 8

1.11 TERMS OF WITHDRAWAL ................................................................................................. 8

1.12 DISPOSITION OF PROPOSALS ............................................................................................. 8

1.13 FALSE OR MISLEADING STATEMENTS .................................................................................. 9

1.14 CLARIFICATION OF PROPOSAL ............................................................................................ 9

1.15 ACCEPTANCE OF PROPOSAL CONTENT ................................................................................. 9

1.16 RESPONSIVENESS ............................................................................................................ 9

1.17 NON-APPROPRIATION OF FUNDS ....................................................................................... 9

1.18 LINE ITEM PURCHASING ................................................................................................... 9

1.19 PROPOSAL APPROVAL, AGREEMENT TYPE AND AGREEMENT EXECUTION PROCESS ....................... 9 1.19.1 Insurance and Business License ................................................................................................ 10 1.19.2 Proposer to Execute Contract ................................................................................................... 10 1.19.3 Purchase Order and Notice to Proceed ..................................................................................... 10

1.20 EQUAL EMPLOYMENT OPPORTUNITY COMMISSION (EEOC) ................................................. 10

STATEMENT OF WORK .................................................................................................... 12

2 BACKGROUND ........................................................................................................ 12

2.1 ALW SERVICE AREA AND OPERATIONS ............................................................................. 12 2.1.1 Goals and Objectives ..................................................................................................................... 13 2.1.2 Electric Operations ........................................................................................................................ 14 2.1.3 Water Distribution Operations ...................................................................................................... 15 2.1.4 ALW’s IT Systems ........................................................................................................................... 16 2.1.5 Enquesta – Customer Information System (CIS) ............................................................................ 16 2.1.6 Meter Reading and Billing ............................................................................................................. 17 2.1.7 Disconnect/Reconnect Process ...................................................................................................... 18 2.1.8 Past Due Notices and Work Orders ............................................................................................... 19

3 SUMMARY OF WORK .............................................................................................. 20

3.1 INTRODUCTION ............................................................................................................ 20

3.2 ASSUMPTIONS.............................................................................................................. 21

3.3 SUPPORTING DOCUMENTATION ....................................................................................... 22

3.4 PHASE I - AMI SYSTEM .................................................................................................. 22 3.4.1 Design/Construct/Operate AMI Communications Infrastructure .................................................. 22 3.4.2 AMI Headend Software ................................................................................................................. 24 3.4.3 AMI Network and Deployment Tools ............................................................................................ 24


3.4.4 AMI Computer Hardware .............................................................................................................. 24 3.4.5 Network Operations Center (NOC) ................................................................................................ 24 3.4.6 Electric Meters ............................................................................................................................... 24 3.4.7 Optional Electric Meter Adders ..................................................................................................... 25 3.4.8 Water Meters ................................................................................................................................ 25 3.4.9 MDM System ................................................................................................................................. 26 3.4.10 MDM Computer Hardware ....................................................................................................... 27 3.4.11 Customer Engagement Solutions .............................................................................................. 27 3.4.12 Systems Integration .................................................................................................................. 28 3.4.13 Downtown Public Wi-Fi Network .............................................................................................. 29 3.4.14 AMI Pilot Demonstration .......................................................................................................... 31 3.4.15 Phase I Option – Prepay System ............................................................................................... 33

3.5 PHASE II – WATER SYSTEM REQUIREMENTS ...................................................................... 33 3.5.1 Water System Enhancements ........................................................................................................ 33 3.5.2 Scheduling of Water System Enhancements ................................................................................. 34

3.6 PHASE III – ELECTRIC SYSTEM REQUIREMENTS ................................................................... 34 3.6.1 Electric System Enhancements ...................................................................................................... 34 3.6.2 Scheduling Electric System Enhancements .................................................................................... 35 3.6.3 Other Info to be Provided – Volt-VAR Management / Reduction and DA ..................................... 35

3.7 SERVICES REQUESTED .................................................................................................... 35

3.8 ADDITIONAL FUNCTIONAL CAPABILITIES ............................................................................ 36

4 GENERAL RESPONSE REQUIREMENTS ...................................................................... 37

4.1 COMPANY/STAFF QUALIFICATIONS .................................................................................. 37

4.2 PRODUCT OVERVIEW ..................................................................................................... 37

4.3 PRODUCT DEVELOPMENT ............................................................................................... 37

4.4 PROPOSER REFERENCES ................................................................................................. 38

4.5 WORK PLAN ................................................................................................................ 38

4.6 PROJECT SCHEDULE ....................................................................................................... 38

4.7 DATA REQUESTS ........................................................................................................... 38

4.8 TESTING ...................................................................................................................... 38

4.9 TRAINING .................................................................................................................... 39

4.10 USER GROUPS .............................................................................................................. 39

4.11 SCALABILITY ................................................................................................................. 39

4.12 SOFTWARE RELEASES ..................................................................................................... 39

4.13 MAINTENANCE AND SUPPORT ......................................................................................... 40

4.14 PRODUCT LICENSING ..................................................................................................... 40

4.15 DOCUMENTATION ......................................................................................................... 40

4.16 HARDWARE/SOFTWARE SPECIFICATIONS ........................................................................... 40

4.17 SYSTEM SECURITY ......................................................................................................... 40

4.18 SCOPE EXCLUSIONS/ADDENDA ........................................................................................ 40

5 PROPOSAL RESPONSE FORMAT AND CONTENT ....................................................... 41

5.1 TABLE OF CONTENTS ..................................................................................................... 41

5.2 SECTION 1 – COVER LETTER (3 PAGES MAXIMUM) .............................................................. 41

5.3 SECTION 2 – TECHNICAL PROPOSAL.................................................................................. 41

5.4 SECTION 3 – COST PROPOSAL ......................................................................................... 43

5.5 SECTION 4 – REFERENCES (8 PAGES MAXIMUM) ................................................................ 44

5.6 SECTION 5 -- COST-BENEFIT ESTIMATE ............................................................................. 44

5.7 SECTION 6 – ATTACHMENTS ........................................................................................... 44


5.8 SECTION 7 – APPENDICES ............................................................................................... 45

6 PROPOSAL EVALUATION ......................................................................................... 45

6.1 PROPOSER SHORT-LIST .................................................................................................. 45

6.2 EVALUATION CRITERIA ................................................................................................... 45

6.3 RANKING..................................................................................................................... 45

7 PROPOSAL TIMELINE ............................................................................................... 46

7.1 SCHEDULE OF EVENTS .................................................................................................... 46

APPENDICES ................................................................................................................... 47


1 Instructions

1.1 Purpose and Applicability of this Document

Azusa Light & Water (ALW) is soliciting proposals from firms interested in designing, financing, building, installing, and operating an advanced metering infrastructure (AMI) system to serve the ALW service territory. ALW expects the proposed system to read both electric and water meters through a wireless network, provide consumption data and service enhancements to customers, and provide new diagnostic and remote control capabilities to the water and electric utility managers for improved operations management.

A “turnkey” set of integrated solutions is the preferred type of service(s) being sought by this RFP, and a hosted solution or “Smart Grid as a Service” or “SGS” is the anticipated business model being pursued by this RFP. However, ALW is open to receiving proposals on other operating or business models.

ALW prefers to pay for capital equipment and ongoing services over time through a per meter monthly fee. ALW will consider paying lump sum amount(s) for meters as an option to lower monthly fee. Cost proposals should be structured to: (1) have minimal net cost impacts on rate payers; and (2) provide ALW with an infrastructure ownership right after a defined period of time.

This RFP requires a demonstration pilot project to be implemented to test the basic technology being proposed for full deployment throughout ALW’s service territory. The AMI pilot project shall include business process changes to demonstrate the efficiencies achieved by using the AMI system for meter reading, shutoffs and turn-ons, and other core functions expected of this technology.

Only upon the completion of a successful demonstration will ALW commit to the full scope of services applicable to our entire service territory.

ALW desires that the wireless network deployed as part of the AMI system be scalable to provide wireless internet service to the public in designated and agreed upon geographic areas of the City of Azusa.

The AMI system is expected to provide leak detection and outage management as well, as further described in this RFP.

1.2 Proposer Teaming

Given that the AMI infrastructure specified by this RFP requires the use of equipment and software applications that may be supplied by different vendors, Proposers are encouraged to team up with vendors that are industry leaders in their respective fields in order to offer a bundled, state-of-the-art, proven and comprehensive solution.


1.3 Equipment Lead Times

To satisfy requirements of this RFP Proposer shall specify, where applicable, the anticipated lead times required for any and all equipment to be acquired to satisfy the requirements of this RFP.

1.4 Intent to Propose Due Date

Intent to propose to this RFP must be provided by 12 noon, Pacific Standard Time (PST), on Monday, July 28, 2014. Communication of intent shall be made as specified in the Acknowledgement Form below (Page 10). ALW reserves the right to extend this date and time.

1.5 Proposal Due Date

The deadline for submission of proposals in response to this RFP is 5:00 p.m., PST, on Tuesday, September 9, 2014.

1.6 Proposal Subscription

ALW will be managing the procurement of services and systems for this project and will be assisted by UtiliWorks Consulting, LLC. All questions, clarifications, and responses relating to this RFP shall be in writing and addressed via email subscription. To subscribe, send an email with the subject line AZUSA AMI RFP to [email protected] and request to be added to the distribution list.

UtiliWorks Consulting, LLC is not to be contacted directly by the Proposer.

1.7 ALW Contact Information

With regard to this RFP, Proposer can contact ALW’s designated Contact as follows:

Mr. Cary Kalscheuer Assistant Director – Customer Care & Solutions

Azusa Light & Water 729 N. Azusa Ave.

Azusa, CA 91702 Telephone: (626) 812-5207

Fax: (626) 812-0963 E-mail: [email protected]

1.8 Questions

If you have any questions regarding this RFP, email them to ALW’s designated point of contact with reference to AZUSA’s AMI RFP in the subject line. Questions are to be received no later than ten (10) business days prior to the proposal deadline (August 30, 2014) unless extended.

mailto:ckalscheuer@

mailto:[email protected]


1.9 Pre-Proposal Meeting – Attendance Mandatory

Given the scope of this project and anticipated cost, it is mandatory all parties or firms intending to propose on this RFP attend a Pre-Proposal Meeting at the following time and location:

DATE: Thursday, July 31, 2014 TIME: 10:00 a.m. PST LOCATION: 1st Floor Conference Room 729 N. Azusa Avenue Azusa, CA 91702

A conference call line will be available for participants that are unable to attend in person.

Questions for discussion at the pre-proposal meeting must be submitted via email no later than 10 a.m. on July 29, 2014. Email questions to [email protected] and reference AZUSA’S AMI RFP in subject line. A meeting notice will be sent via email to the designated Proposer contacts Tuesday, July 29, 2014 with details.

1.10 Proposal Submission

Five (5) original hardcopies and one electronic version (on CD or USB drive) of the respondent’s proposal in its entirety must be received by ALW no later than 5:00 p.m. PST on Tuesday, September 9, 2014, at the following address:

Mr. George F. Morrow Director of Utilities Azusa Light & Water 729 N. Azusa Avenue Azusa, CA 91702

The sealed box or sealed envelope should be plainly marked with “Sealed Offer on AZUSA AMI Project”.

It shall be the responsibility of the Proposer to ensure that the proposal is received by ALW by the time stated herein. Late proposals will not be considered.

1.11 Terms of Withdrawal

All proposals shall be firm offers valid for a period of 6 months (January 29, 2015) following the deadline dated for submission of proposals noted herein.

1.12 Disposition of Proposals

All proposals submitted to ALW in response to this RFP will become the property of ALW and will not be returned. All expenses incurred in preparing and submitting proposals shall be at the sole cost and expense of the Proposer. ALW reserves the right to reject any and all proposals submitted in response to this RFP.



1.13 False or Misleading Statements

If, in the opinion of ALW or its Consultant, a proposal contains false or misleading statements or references that do not support a function, attribute, capability or condition as contended by the Proposer, the entire proposal shall be rejected.

1.14 Clarification of Proposal

ALW reserves the right to obtain clarification of any point in the Proposer’s proposal or to obtain additional information necessary to properly evaluate a particular proposal. Failure of a Proposer to respond to such a request for additional information or clarification may result in rejection of the Proposer’s proposal.

1.15 Acceptance of Proposal Content

The contents of the proposal of the successful Proposer will become a contractual obligation if a contract ensues. Failure of the successful Proposer to accept this obligation may result in cancellation of the award.

1.16 Responsiveness

Proposals shall be responsive to all requirements of this RFP.

1.17 Non-Appropriation of Funds

A contract award is anticipated to result from this RFP, and if such award is made, it will be awarded to the most responsive and responsible Proposer complying with all the provisions of this RFP, and providing a price that is reasonable and in the best interest of ALW. The award of contract pursuant to the RFP, however, is contingent on funding or agreement by ALW of payment terms. Funding and payment terms may require a budget amendment or rate adjustment to be approved by ALW’s Utility Board prior to contract award.

1.18 Line Item Purchasing

ALW specifically reserves the right to buy items or services offered on a line-item basis from any Proposer. In order to facilitate the integration of multiple Proposer applications, each Proposer shall be willing to cooperate with other Proposers by supplying interface information that allows devices and/or applications to be integrated. If a Proposer’s devices or applications include proprietary communication protocols or otherwise cannot interface with non-proposed devices, Proposer shall disclose these device limitations as part of its proposal.

1.19 Proposal Approval, Agreement Type and Agreement Execution Process The successful Proposer will be required to execute a Design, Build, and Operate Contract with ALW which incorporates by reference the negotiated Work Statement and payment schedule. Proposers are required to submit a sample “Design, Build, Operate Agreement” with proposals for purposes of facilitating contract negotiations.


ALW anticipates that award of contract for this engagement will be made within 6 months of receipt of Proposals. After approval of award by the Utility Board/City Council, the City Clerk will forward the Design, Build and Operate Agreement in triplicate to the selected firm for signature. Following summarizes the “anticipated” approval process and requirements for the issuance of notice to proceed:

1.19.1 Insurance and Business License

The awarded firm shall provide to ALW the worker’s compensation, comprehensive general and automobile liability, and the professional liability insurance coverages, endorsements and certifications as specified in Appendix 10 of this RFP. The awarded firm shall also obtain a City of Azusa business license.

1.19.2 Proposer to Execute Contract

The contract shall be signed by the awarded firm in triplicate and three (3) originals shall be returned together with the insurance certificates within fifteen (15) calendar days from the date of receipt of notice of award along with a valid business license. No contract shall be binding upon the City until completely executed by the awarded firm and the City and approved by the City Attorney. Failure to execute the contract agreement and file acceptable insurance and business license within the time limit may be just cause for annulment of the award.

1.19.3 Purchase Order and Notice to Proceed

Following receipt by ALW of executed agreement, insurance documents and business license, and after the City has executed the agreement; the City of Azusa will issue a Purchase Order and Notice to Proceed to the awarded firm along with a signed contract. These documents will provide final approval and authorization for the underwriting firm to commence work.

1.20 Equal Employment Opportunity Commission (EEOC)

During the performance of this contract, the Proposer agrees not to discriminate against any employee or applicant for employment because of race, national origin, age, religion, gender, sexual orientation, marital or veteran status or physically challenging condition. Provide a statement of compliance.


Acknowledgement Form

If Proposer organization intends to respond to this RFP, please complete the following information below. Transmit the completed form to Cary Kalscheuer at Azusa Light & Water via U.S. Mail, Email or FAX by 12 noon PST on Monday, July 28, 2014:

Mr. Cary Kalscheuer Assistant Director – Customer Care & Solutions

Azusa Light & Water 729 N. Azusa Ave.

Azusa, CA 91702 Telephone: (626) 812-5207

Fax: (626) 812-0963 E-mail: [email protected]

Check one:

( ) Yes, our organization intends to respond to AZUSA’S AMI RFP.

( ) No, our organization will NOT be able to respond to AZUSA’S AMI RFP.

Date:_______________________________________________

Company: __________________________________

Contact: __________________________________

Address: __________________________________

City: ____________________State: Zip Code: _____

Phone: Fax: ____________

Email: _

Interested parties that do not provide notification of their intent to respond to the RFP may be disqualified.

Following receipt of above, information will be communicated to Proposer to allow Proposer to download or receive files that make up the attachments to this RFP.



Statement of Work

2 Background

2.1 ALW Service Area and Operations

ALW is a public Electric and Water utility in Los Angeles County, California, serving approximately 15,713 electric and 9,308 water customers within the incorporated City of Azusa. Most of the services within Azusa are concentrated within a 7.3 square mile area. The water utility also serves 13,346 water customers outside the City of Azusa in a service territory that includes portions of neighboring cities of Glendora, Covina, West Covina and Irwindale, and also portions of unincorporated areas of Los Angeles County. Below shows general service territory:

For access to an online interactive map of Azusa, go to: http://gis.ci.azusa.ca.us/hp .

http://gis.ci.azusa.ca.us/hp


2.1.1 Goals and Objectives

Operational efficiencies are expected to be realized from this project by three ALW operating divisions, Customer Service, Water Operations, and Electric Operations. While the goals of each division are set forth below, this RFP principally seeks to achieve the goals of the Customer Service Division in the initial first phase in ALW’s AMI deployment. All Proposers, however, are to propose solutions in response to this RFP that will enable ALW’s Electric and Water Divisions to realize their goals as set forth below in subsequent or concurrent phases of ALW’s modernization effort utilizing the advanced metering infrastructure deployed in phase one. The proposed meters and communication equipment in phase one must be compatible, interoperable and configured to work with all equipment and devices to be deployed in phases two and three to allow the other divisions to achieve the goals below.

Customer Service o Automatically read 100% of all water and electric meters through a

wireless network on a monthly basis three (3) business days prior to billing customers.

o Reduce meter reading errors and check read work orders. o Automatically identify meters that are not working properly or

communicating with the network. o Allow ALW staff to remotely disconnect and reconnect electric utility

services and detect theft when meters are off. o Provide all Customer Service Representatives (CSRs) with user

interface to look up customer usage data for both water and electric services on a near real time basis, display historic usage by month, and by billing cycle date ranges.

o Improve accuracy of metering to properly bill customers for water and electricity actually used.

o More efficiently analyze customer usage data to detect theft, leaks, and other like concerns that may be of interest to ALW or Customers.

o Provide customers with a web portal, integrated into ALW’s existing website, and a mobile application that will allow customers to look up their individual water or electricity consumption on a monthly, weekly, daily and hourly basis, and compare their usage to similar types of customers.

o Offer electric customers the ability to prepay their utility bills through variety of methods, including mobile phone app, under the condition that if electricity is not prepaid, electricity will be shut off automatically.

o Identify water customers with probable leaks and proactively notify customer to check for leaks and make repairs to reduce water loss and costs.

o Identify customers that may be violating water use restrictions by irrigating their landscapes on non-permitted days considering their street address.

o Geocode all installed meters to enable field staff to quickly find them using mobile applications.


o Provide capability to provide Wi Fi service to downtown Azusa as part of AMI pilot project

Water Distribution Operations o Improve accuracy of metering to reduce water losses. o Perform trend analysis on water meter types to predict when the

meters will need replacement. Integrate water meter data with the existing SCADA system to allow the water production operators to monitor the amount of water flow from one pressure zone to another pressure zone using meters at each zone connection regulator. Correlate interzone flow with service meter demand in each zone to determine the water loss in each zone.

o Integrate meter data with Azusa’s Water System hydraulic model to allow the operators to monitor the flows in the water system on a real time basis.

o Increase efficiency of Water System by using analytics to identify and replace inaccurate meters; detect and replace leaking water pipelines; detect customer side leaks; and reduce water theft due to continuous flow monitoring in the system.

o Installation of in-line leak detection may be considered as an option if the technology is cost effective.

Electric Operations o Implement an Outage Management System (OMS) with outage

mapping o Implement transformer load management o Implement theft detection system o Learn more about Volt-VAR management / reduction programs and

how these can be implemented considering current electric distribution system

o Eventually Integration of Distributed Automation (DA) devices with SCADA and the AMI network

2.1.2 Electric Operations

Additional information about ALW’s Electric division is provided here for reference and to ensure that proposed solutions and equipment will meet the future needs of the Electric division. See Appendix 3 for electronic file of electric distribution system map, including location of vertical infrastructure. If additional information is required, please send an information request to this RFP’s point of contact.

ALW serves its electric customers through two (2) distribution substations and a total of twenty (20) circuits and about 130 miles of distribution lines with a summer electric peak demand of 67.5 MW and annual sales of 236,527 MWh in FY 2012. The total residential population served is about 47,000. Retail consumption is about one-third residential, one-third commercial and one-third industrial.


Wholesale power is purchased and imported to Azusa through long term contracts and currently contracted resources are well in excess of retail demand. All contract power is sold into the California market through the California Independent System Operator (CAISO), and only power needed to serve local load is purchased back. This results in net wholesale revenue to the Electric Utility.

The Electric Division includes 22 fulltime staff, a Power Resources Manager, an Operations Manager, a Field Supervisor, Linemen, Meter Shop staff, and Engineers. The total annual budget for the Electric Division is about $47 million, including power purchase arrangements.

Operation of the electric system is monitored by a SCADA system which conveys information on the status of two electric distribution stations and the 12 KV circuits emanating therefrom.

2.1.3 Water Distribution Operations

Additional information about ALW’s Water division is provided here for reference and to ensure that proposed solutions and equipment will meet the future needs of the Water division. See Appendix 4 for electronic file of water distribution system map. If additional information is required, please send an information request to this RFP’s point of contact.

The City of Azusa Water System serves an equivalent population of 110,000 people. In addition to the City of Azusa, the water system also serves portions of the cities of West Covina, Covina, Irwindale, and Glendora, and a portion of Los Angeles County adjacent to those cities, as noted previously.

The water system is comprised of approximately 300 miles of pipelines of various sizes which serve nearly 23,000 service connections. Those connections collectively serve residential, commercial and industrial demand, and also fire protection service connections.

The area served by the Azusa Water System is approximately 29.3 square miles and is divided into four pressure zones ranging from 590 feet in water elevation to 1023 feet. The system water is boosted to pressure zone 1023 and gravity fed to the other three zones. The system has thirteen reservoirs with a combined capacity of 38 million gallons.

The Water System relies on several sources of water supply. These are: (i) underground water, which is pumped from 11 deep wells currently in operation within the Main San Gabriel Basin, Intermediate San Gabriel Basin, and Upper San Gabriel (Canyon) Basin; (ii) surface water from the San Gabriel River, which is filtered and treated at the Hsu Water Filtration Plant, located in north Azusa; (iii) treated water purchased from the Upper San Gabriel Valley Municipal Water District (“Upper San Gabriel Valley MWD”); and (iv) untreated State Water Project water purchased from the San Gabriel Valley Municipal Water District. The Water System has interconnections with other water purveyors and is able to receive or supply water from or to other systems on an emergency basis.

Operation of the Azusa Water System is controlled through a SCADA system that is monitored and operated by the System Production Operators. The SCADA system


monitors well pump operation, water treatment plant operation, booster pump operation, and pressure regulators which control water pressures throughout the system.

2.1.4 ALW’s IT Systems

The following table lists each IT system name, business function, and manufacturer used by ALW:

Business Function System Name Manufacturer or Service Provider

CIS/Billing Enquesta Systems & Software (S&S)

Work Order Management (related to Customer Service)

Enquesta S&S

Financial Management Bi-Tech Sungard

Meter Reading MVRS Itron

Interval Data Collection MV90 Itron

SCADA – Electric Single Windows

SCADA Master Survalent Technology

Facilities Control--SCADA–Water PWS Water Automation

Emerson Process Management

Mapping (Non-Utility) ArcGIS ESRI

Call Center Software Change in progress to inContact

InContact

City and Utilities Web Portal – for Electronic Bill Pay and Requests to Start Service

City and third party web pages

Civic Plus InfoSend Paymentus To-Turn-It-On

Local Area Network Novell/Linux Novell

Outage Management System None N/A

Load Management System None N/A

2.1.5 Enquesta – Customer Information System (CIS)

Enquesta is the key Customer Information System (CIS) that currently supports utility billing, past due notices, disconnect notices, and work order management. BiTech by Sungard is the City’s financial system and performs accounting, budget management, and purchasing functions. The CIS files are uploaded to the Bitech system to update the General Ledger accounts used by the Utility, that is, the CIS is not integrated with BiTech. The Customer Service Division currently uses Version 4.0 of Enquesta, and this version does not include a module offered by S&S called WebConnect. WebConnect would allow electronic payments to be made in the ALW office and online, and


would automatically post such payments to our CIS in near real time. ALW is currently considering the implementation of WebConnect during this next year. The WebConnnect module would provide a web interface to customers to make payments online and also features a mobile application to allow customers to pay using their smart phones. Currently, ALW allows for electronic payments online only via the Web. Web pages have been designed and are integrated into ALW’s current website at http://www.ci.azusa.ca.us/index.aspx?NID=209 or http://www.azusalw.com . Third-party payment vendors provide online payment options to ALW customers and process such payments. InfoSend provides for ongoing ACH payments to be made by customers for free, and Paymentus accepts credit and debit card one-time payments for a convenience fee. Both payment vendors’ systems are not integrated with Enquesta to provide our CSRs with real time payment status. Files must be uploaded daily to update Enquesta. WebConnect is being considered by ALW to address this issue, which will be particularly helpful in voiding Disconnect Work Orders for customers that pay late. WebConnect also offers an API for MDM data to be upload into the CIS. S&S has designed software interfaces to present customer usage info to ALW CSRs via Enquesta, and this same system can present customers with usage info via the Web, however, this system appears limited in its functionality. More information about WebConnect and the status of ALW’s consideration of this module will be provided to Proposers of record during the RFP Process.

2.1.6 Meter Reading and Billing

The Customer Service Division is responsible for managing retail utility services offered and provided to customers, including signing up new customers for service, utility billing, meter reading, disconnects and reconnects of services, collections, payment processing and write-offs. The Customer Service Division is responsible for issuing work orders to replace both water and electric meters, administers the CIS, promotes water and energy conservation and enforces water use restrictions.

Most meters are read using an Itron FC200 hand held unit and data is downloaded into an Itron MVRS computer where a batch file is prepared and downloaded into the CIS. Scheduling meter reading factors in Meter Reader leave time, holidays, the CIS billing schedule, and how long it takes to complete meter reading routes. There are currently 6,026 AMR Electric Meters and 817 AMR Water Meters in our service territory that have reduced meter reading times.

There are currently 4 fulltime Meter Readers and one part time Meter Reader that read all routes for ALW.

The CIS billing schedule is set annually to cover 19 billing cycles per month and the bill date is the most important factor affecting meter reading scheduling.

The CIS platform includes an Oracle Database. After the MVRS batch file is downloaded into the CIS, ALW staff review the reads for usage irregularities or

http://www.ci.azusa.ca.us/index.aspx?NID=209

http://www.azusalw.com/


exceptions. If irregularities are found, work orders are issued to field services representatives or Meter Readers to do check reads. Over 700 check reads are done annually.

Once exceptions have been reviewed and corrected, the billing process is run in Enquesta to generate a utility billing file, which is sent to a third party bill print provider, InfoSend, for bill print and mailing.

Currently, it is preferable that meters be read no more than 7 days prior to the bill date. Each billing cycle typically goes through the following milestones:

Date new bill is mailed (“bill date”)

Due date is 20 days after bill date

ACH payment is collected on Due Date or next ACH date after Due Date

Delinquency charge to be imposed 3 days after bill Due Date

Past Due Notices are sent out with Delinquency Charge 23 days after bill date

Disconnect Notices are mailed 14 days or more after Past Notice is mailed

Shut off occurs 8 days after Disconnect Notice is sent out

Although ALW Rules and Regulations drive billing cycle milestones, other factors limit how many bills (i.e., cycles) can be billed at one time, including the following:

Current work schedule is Monday through Thursday

Shut-offs are limited to Monday through Wednesday

How many shutoffs can be accomplished by existing Field Services staff (currently, 2 fulltime FSRs) in one day (currently, about 70 shutoffs maximum)

How many walk in customers can be handled at one time by existing customer service staff once customers are shut off

The CIS system design and functionality – which is task or work order driven system

As a result of these limitations, the current billing cycles are spread out over each month such that about 13 days per month are used to bill current customers. Consequently, this spreads out the mailing of past due notices and disconnect notices, and distributes disconnects and reconnects, to manageable levels given existing manual techniques and staffing levels.

Payments by customers are made by a variety of means; however, most payments are by check mailed to the Lockbox service provider, RT Lawrence. Customers may also sign up for electronic payment with ALW; however, ALW does not currently offer or provide a Pre-Pay option to customers.

2.1.7 Disconnect/Reconnect Process

ALW currently uses a manual process to effect service disconnections. The Enquesta CIS generates a file of customers that have received a disconnect notice and who have not paid within 7 days of the disconnect notice. If the amount owed is over $60, the customer is placed on a shutoff list. Work orders are generated by the Enquesta system in bulk for all the customers on the shutoff list.

The Field Service Representatives (FSR) take the hardcopy work orders and drive to the service location and typically will shut off water service first if the customer is


inside the City of Azusa and has both water and electric service. Once the shutoff is made the FSR calls the office and lets a Customer Service Representative (CSR) know that the customer has been shutoff. The meter read is provided to the CSR at time of shutoff. There are currently 2 fulltime FSRs performing the shutoff function.

The CSR enters the meter reads into the customer’s account and notes the customer has been shutoff and the time and date. This forces the customer to come into the office to make payment, and once payment is made a reconnection work order is generated and forwarded to FSR. The FSR then takes the work order to the field to turn the customer back on, and fills out the work order with the read and time the meter was turned back on. (Some reconnect work orders may be called or dispatched to the FSR in the field.)

The reconnect work order is then sent back to the office where a CSR updates the customer record. As noted above, over 6,000 customers are shutoff annually, and over 6,000 reconnects are processed annually. Below table shows distribution of shutoffs based on how many times single customers are shutoff. About 60% of all shutoffs occur at customer premises with more than one shutoff per year.

Azusa Light & Water Shut Offs

July 1, 2011 – June 30, 2012

# of Customers

# of Times

Customer Shutoff

Total Shutoffs

1 8 8

8 7 56

26 6 156

41 5 205

136 4 544

327 3 981

847 2 1,694

2,290 1 2,290

3,676

5,934

2.1.8 Past Due Notices and Work Orders

During FY 2011-12, ALW sent out 100,200 past due notices and 31,300 disconnect notices. The following work order counts were processed during FY 2011-12:

12,848 disconnects/reconnects of customers for non-payment.

6,331 Move outs/in

768 check reads

2 Water leaks


3 Summary of Work

This section summarizes the overall project and outlines how proposals are to be formulated in response to this solicitation. It is important to note that some of the materials and services referenced in this section are more specifically defined in the Attachments that are to be filled out by proposers. These Attachments are Excel Files and are listed in Appendix 9. All proposals shall meet the technical and general requirements outlined in this RFP and the Attachments. Any exceptions shall be clearly noted in the proposal.

The proposal shall provide a complete description and underlying specifications of the proposed materials along with any optional features that the Proposer may deem to be desirable to ALW.

Proposers shall provide service pricing based on a monthly customer or meter charge, and shall also provide the cost basis for these monthly service charges. Both one-time capital costs and ongoing maintenance costs are to be provided in the format as set forth in Attachment 1 – AMI_MDM_OMS Cost Proposal. Proposer shall also specify in Attachment 1, where applicable, the lead times required for any and all equipment.

3.1 Introduction

This project is broken down into three phases. Phase I is intended to convert ALW’s meter inventory from a manually read system to one that can be read through a fixed wireless network. Automatic or remote meter shut off and reconnect is also to be included as part of the AMI system functionality, along with a customer engagement solution consisting of a web portal and mobile application to allow customers to view water and electricity usage information on a near real time basis. The wireless network deployed to read meters is also to provide public Wi Fi internet access in at least one designated public area and scalable to provide internet services to other areas in the future. These functions are the primary goal of this RFP and may be considered as Phase I of the project.

ALW is interested in receiving proposals from firms that are able to remotely and securely read meters and store data generated by meters and other devices at a secure offsite location, as well as maintain the local AMI network, including all network devices, through a service level agreement. Hence, and as noted previously, a hosted solution or Smart Grid as a Services (SGS) model is the anticipated business solution being pursued by this RFP; however, ALW is open to other models being proposed.

Responses to this RFP should include design of the meter reading wireless network, installation and testing of network devices, installation and testing of new meters, meter transmitters/receivers at the customer premise, deployment of a meter data management (MDM) system, including generation of files from the MDM that can be downloaded and then uploaded into ALW’s CIS for billing purposes. Through this RFP, ALW is not seeking to integrate the MDM with the CIS, however, integration service proposals may be submitted as an option. ALW’s CIS vendor does have a standard application programming interface (API) for this purpose.


It is understood that several other value-added features and functions will be available through the AMI system at the outset and over time to Utility Managers and Customers. These additional features are included in the Goals and Objectives Section of this RFP (Section 2.1.1) for the Water and Electric Divisions. Proposed equipment, software, and devices deployed in Phase I shall be compatible and configured to operate and integrate with all equipment, software and devices proposed for Phases II and III. For purposes of this solicitation, Proposers shall provide pricing for services, equipment and devices to fulfill the goals of the Water Operations Division as part of Phase II. To complete services solicitation through this RFP, proposers are to provide pricing for services, equipment and devices to fulfill the goals of the Electric Operation’s Division as part of Phase III. These subsequent phases of this project may be approved separately and may be scheduled concurrently with other phases as agreed to by the parties. It is the preference of ALW that the following Phase III activities be implemented concurrently with Phase I Services: (1) Outage Management System with Mapping; (2) Transformer load management; and (3) Electricity Theft Detection.

3.2 Assumptions

Please note the following assumptions when preparing proposal:

All electric meters, except for approximately 37 TOU meters, will be replaced with new metering equipment factory integrated with the AMI Endpoints. Proposers are welcome to submit service concepts to replace ALW’s TOU meters and integrate the read data into the MDM. Proposers should discuss the benefits of integrating the TOU meters into proposed solution.

ALW plans to deploy remote service disconnect/reconnect to 100% of residential electric meters.

All water meter registers will be replaced and about 85% of all water meters 2” and smaller will be replaced. That is, ALW is not intending to replace meters 3” and larger through this project unless they are found to be registering usage inaccurately.

All 5/8” water meters will be replaced with 3/4” water meters.

ALW will likely manually disconnect water meters located outside of the incorporated area of the City of Azusa, however, Proposers may submit options to remotely disconnect/reconnect these water meters (network communication frequencies and devices to remotely shut off / reconnect water meters should be compatible with networks used to read and control electric meters).

It is preferred that electric meters be capable of wireless communication with in-home appliances or devices and that customer engagement solution be capable of controlling smart appliances using mobile application.

Although this RFP doesn’t solicit proposals on demand reduction (DR) programs, installed meters should be capable of this functionality should ALW desire to develop and deploy a DR program in the future.


All network computer equipment shall be scalable and sized initially for Full Scale Deployment to read and control meters, not just to cover the Pilot Phase.

While various AMI network options are available, Proposers should read about the Wi-Fi Network requirements in this RFP and consider using that network for the backbone of the AMI network.

Backhaul of network shall be to ALW Main Office at 729 N. Azusa Ave., Azusa CA 91702.

3.3 Supporting Documentation

Proposer should examine all of the supporting documentation in the Appendices included in this solicitation to ensure that the response is as detailed as possible and that appropriate materials and services are quoted. Supporting documentation and maps are summarized below and referenced accordingly throughout the documents:

Appendix 1 – Map of Electric Service Territory

Appendix 2 – Map of Water Service Territory

Appendix 3 – Map of Electric Distribution System

Appendix 4 – Map of Water Distribution System

Appendix 5 – Map of the Pilot Area

Appendix 6 – List of Meters in Pilot Area

Appendix 7 – List of All Electric Meters throughout Service Territory

Appendix 8 – List of All Water Meters throughout Service Territory

Appendix 9 – Excel Files to be used by Proposers in submitting Attachments: o Attachment 1 – AMI – MDM -- OMS Cost Proposal o Attachment 5 – AMI System Requirements o Attachment 6 – MDM System Requirements o Attachment 7 – OMS Requirements

Appendix 10 – Sample contract sections

Appendix 11 – Sample: (1) work order for meter replacements; (2) billing file to be uploaded to CIS; and (3) work order for disconnect and reconnects.

Additional interactive map info is also available online at http://gis.ci.azusa.ca.us/hp. Field or site visits are strongly recommended before submitting any proposals, as Azusa is a foothill community located adjacent to the San Gabriel Mountains. Portions of Azusa extend up the San Gabriel Canyon. Areas of Azusa north of Foothill Boulevard can be hilly and the availability of vertical infrastructure varies in different residential areas.

3.4 Phase I - AMI System

3.4.1 Design/Construct/Operate AMI Communications Infrastructure

Proposer shall assess the topography of the ALW service territory, existing poles that can be used for network devices, and provide a cost proposal to design and construct AMI communications network capable of fulfilling the goals of the various Divisions included in this RFP.

http://gis.ci.azusa.ca.us/hp


In general the AMI system is considered to be a data collection Field Area Network (FAN) consisting of various apparatus designed to automate the meter reading function while having the capability to execute remote commands acting either upon the attached meter or upon itself. As there are many possible implementations of systems with similar functionality, the Metering System is treated as a single entity with the primary aggregation point located at the AMI Headend. This RFP specification attempts to remove constraints upon proposals in order to elicit the best possible system configuration.

Each Proposer shall complete Attachment 5 – AMI System Requirements as listed in Appendix 9 of this RFP. In this Attachment, the AMI system requirements outlined are expressed in categories and subcategories of features that have similar characteristics or functions. The categories include such items as the following: Interoperability, Data, Security, Alarms and Events, Meter Tampering Events, Installation Features, Local Connectivity, Time Management, System Performance and Reliability, as well as other items.

A point-by-point response must be completed and submitted in the Microsoft Excel format using Attachment 5 – AMI System Requirements. Referring to a particular requirement is done by specifying the Sub-Category and the Requirement ID number, for example:

“Events-52” refers to the requirement, “Transmit lower priority events to the headend during the next available transmission cycle.”

Attachment 5 will be made into a requirements document and attached to the final contract awarded to Proposer. Requirement ID numbers will not change throughout the project lifecycle. If a requirement is revised during the project, a new version of the requirements document will be created and re-issued along with a new version number.

As this project’s intent is to use recognized standards for interoperability and utility best practices, requirements expressed should be considered as supplemental to recognized standards, where they are applicable.

In addition to information required in Excel file for Attachment 5, proposals shall include a detailed description of the total system and include block diagrams of the network architecture. Description is to include what communications frequencies are proposed to be used, what devices will be deployed in the field, what software will be used, and what security devices or protocols will be put into place to safeguard the AMI network. The proposal shall include a description of any licensed or unlicensed frequencies and state the benefits of using the proposed frequency as opposed to other competitive frequencies.

As part of proposed costs to construct the AMI network, vendor shall guarantee that the network signal propagates to all customer meter locations as listed in Appendices of this RFP.

Construction of the AMI network shall result in all system assets being inventoried and geo-coded, as part of documentation of the “As-Built” system. As-built diagrams


and equipment inventory shall be provided to ALW along with expected life of system devices, replacement schedule or device maintenance schedule.

3.4.2 AMI Headend Software

Provide core AMI Headend software and corresponding costs including core modules, optional modules, and related products or services that address the specific requirements listed in Attachment 5 of proposal. List other functions performed or that will be performed as a result of future development. Both one-time costs and maintenance costs should be clearly expressed.

3.4.3 AMI Network and Deployment Tools

Provide a description of recommended tools and equipment required to deploy the proposed AMI network infrastructure that address the requirements listed in Attachment 5 of proposal.

3.4.4 AMI Computer Hardware

Provide a description of recommended computer hardware that addresses the requirements listed in Attachment 5 of the proposal. Provide all hardware specifications. All computer equipment shall be sized for Full Scale Deployment, not just to cover the Pilot Phase.

As noted, it is preferred that an outside service provider maintain all hardware and software used to operate the AMI network along with all hardware and software used to store data collected from the network and metering devices.

3.4.5 Network Operations Center (NOC)

Given that the preferred business model being pursued by this RFP is a SGS, it is assumed that the Proposer will host computer hardware and software necessary to maintain the AIM network from an offsite location or NOC. Please describe where the NOC is located, what equipment it includes, the physical security of the facility, network security protocols, reliability of NOC to perform AMI network monitoring and maintenance, and what uptime guarantees can be provided to ALW.

3.4.6 Electric Meters

Provide and install electric meters that are factory integrated with the AMI Endpoints that meet the requirements outlined in Attachment 5. ALW currently uses a variety of different types of meters. See Appendix 7 for detailed meter listing. Below is list of form types and counts.


Electric Meters

Meter Description Quantity

Form 1S - 1φ, Self-Contained 161

Form 2S - 1φ, Self-Contained 13,935

Form 3S - 1φ, Self-Contained 76

Form 5S - 3φ or 1φ Network, Instr Rated 43

Form 6S - 3φ, Instr Rated 7



Form 10S - 3φ or 1φ Self-Contained 6

Form 12S - 3φ or 1φ Self-Contained Network 209

Form 14S - 3φ or 1φ Self-Contained 224

Form 15S - 3φ or 1φ, Self-Contained 7




Total 15,441

(NOTE: At the time above table was formulated, there were approximately 600 meters that were not identified by form type in our CIS and are excluded from above table. Therefore, the above table may be amended with a notice to all Proposers of record during this RFP process.)

3.4.7 Optional Electric Meter Adders

Recommend optional electric meter functionality that would be beneficial to ALW. Include optional features or functions in Attachment 5 of proposal.

3.4.8 Water Meters

About 15% of all water meters are less than 5 years old and ALW does not desire to replace these meters as part of this project. Meters 3” or larger are expensive and make up a small percentage of ALW’s overall meter count, and therefore ALW does not desire to replace these meters as part of this RFP. Therefore, this RFP requires proposers to provide and replace 85% of all water meters 2” and smaller as indicated in table below, with meter registers that are factory integrated with AMI Endpoints. All other meter registers are to be retrofit with AMI registers that are integrated with AMI Endpoints. Any meters than cannot be retrofit should be replaced with registers that are factory integrated with AMI Endpoints. Water Meters and Registers are to meet the requirements outlined in Attachment 5. Additionally, and as noted previously, all 5/8” meters are to be replaced with 3/4” meters.


Size Count % of Meters <5 years Retrofit Replace

3/4" 16,982 75% 2480 15% 85%

5/8" 1,771 8% 3 0% 100%

1" 1,926 9% 493 26% 74%

1 1/2" 290 1% 48 17% 83%

2" 963 4% 178 18% 82%

3" 157 1% 50 32% 68%

4" 141 1% 32 23% 77%

5" 1 0 0% 100%

6" 162 1% 22 14% 86%

8" 109 24 22% 78%

10" 29 13 45% 55%

12" 1

22,533 99% 3,343 15% 85% Note that most water meters used by ALW are manufactured by Badger (See Appendix 8 for complete listing of all meters including meter manufacturer). Proposers may, as an option, request ALW to replace defective meters from our current inventory of meters as part of this project. It is further noted that most water meters located outside of the City of Azusa are read bi-monthly. It is the intent that all meters be read monthly at the completion of this project.

3.4.9 MDM System

Provide core MDM software and corresponding costs including core modules, optional modules, and related products or services that address the specific requirements listed in MDM System Requirements as set forth in Excel File as listed in Appendix 9. This is to be filled out and attached to proposals as Attachment 6.

The MDM System Requirements set forth in Attachment 6 are expressed in categories of features that have similar characteristics or functions. The categories include the following:

Meter Data Collection

User Interface

Events

Electric Meter Remote Disconnect/Reconnect

Service Outage

User Authentication

Systems Integration

Data Retention

Software Releases

Additional Functionality


A point-by-point response must be completed and submitted in the Microsoft Excel format presented as Attachment 6 – MDM System Requirements. Referring to a particular requirement is done by specifying the Category and the Requirement ID number, for example:

“Meter Data Collection-5” refers to the requirement, “Receive engineering unit data from electric meters, including but not limited to voltage, current, and phasing.”


As this project’s intent is to use recognized standards for interoperability and utility best practices, requirements expressed should be considered as supplemental to recognized standards, where they are applicable.

The MDM CSR user interface should provide easy-to-read analytic information showing whether a customer may have a water leak, was using excess amounts of water or electricity during a given period, and whether a customer who was shutoff was actually using water or electricity, i.e., provide theft detection alerts.

Preferable functionality should include special reports that can be run following reading cycles on specific topics, such as water leak report, theft report, outage report, etc., that query specified customer records for such information. Proposals that include more of these types of reports will be favored, so please include all proposed analytic reports that can be provided from the MDM for use by Customer Service or other Divisions.

Describe any other functions that may be of interest to ALW or developed in the future. Both one-time costs and ongoing maintenance costs should be expressed clearly in Attachment 1 of Cost Proposal.

3.4.10 MDM Computer Hardware

Provide description of all recommended MDM computer hardware, including the specifications for such hardware that addresses the requirements listed in Attachment 6. Provide description of where hardware is to be located, how it will be secured and how it will be maintained. All computer equipment shall be sized for Full Scale Deployment, not just to cover the Pilot Phase.

As noted, it is preferred that an outside service provider maintain all hardware and software used to operate the MDM System along with all hardware and software used to store data collected from the network and metering devices

3.4.11 Customer Engagement Solutions

Immediately following deployment of the AMI network and installation of the AMI meters, the Service Provider shall launch at least two customer engagement solutions: (1) customer web portal, and (2) mobile app to display consumption data


for both water meters and electric meters to ALW customers of record. As an option, and in addition to these engagement solutions, Proposers shall provide cost to integrate MDM with Enquesta and provide customers with similar information using S&S’s WebConnect. These Customer Engagement Solutions shall be developed and tested concurrently as the AMI network is built out and be ready for public launch once the AMI network is reading meters for billing purposes.

The web portal shall be configured to restrict access to only customers of record. Thus, portal registration must include security information from CIS record to restrict registration and login to only existing customers. The web portal shall be designed to open within ALW’s website and shall provide customers with settings to display water and electricity consumption by hours during a day, week, month, quarter or year, using line and bar chart displays.

Web portal shall also display comparative customer information, i.e., neighbor to neighbor, customer type to type (meter type/size – rate/customer code), overall average usage of customer types, and provide customers with an energy/water use efficiency chart which plots customer’s usage on chart in comparison to an efficient customer and average customer.

Proposers may wish to include additional features and functions for web portal and or mobiles app to distinguish their proposal. Additional features might include the following:

Options that allow customers to control in-home appliances

Settings that allow customers to receive alerts regarding possible water leaks

Settings that allow customers to receive usage alerts if electricity or water usage is above certain thresholds

Text messages about power outages and power restoration

Features that allow customers to prepay their electric utility bills

Proposals that include more robust customer portal features and functions will be viewed more favorably. Proposers with operating customer engagement solutions as opposed to shell demonstrations of what “can be” developed will be preferred.

3.4.12 Systems Integration

Proposed systems are preferably proposed as an integrated solution. Proposers are to provide a description of how proposed systems are integrated, and summarize any work to be performed through this project for data exchange/integration design, support, implementation, and testing services regarding the following systems:

The selected AMI system and the selected MDM system

How MDM system will produce read files for billing purposes to be uploaded to the CIS (Enquesta), how meter replacements will be processed before and after mass change out of meters, and how remote disconnects and reconnects will be processed

Option to integrate with MDM with CIS

Integration of MDM System with Water Division SCADA System (Phase II)

Integration of MDM System with a OMS with Mapping (Phase III)


Include cost estimates in Attachment 1 for the expected level of effort, recognizing that the exact scope of services will be further developed in contract negotiations with the selected Proposer. Proposer shall specify all meter data elements that the proposed AMI system is currently designed to receive from electric and water meters and process for delivery to the MDM system. Preference is for bundled operating and integrated systems, not for work building interfaces to connect and integrate separate systems to meet the requirements of this RFP.

3.4.13 Downtown Public Wi-Fi Network

As part of this RFP, and as part of Phase I of this project, ALW is soliciting proposed costs on installation of a high bandwidth capacity network to provide wireless internet service to the Civic Center and Downtown Area. This area is encompassed by the following streets:

9th Street – from N. San Gabriel Ave to N. Dalton Ave.

N. San Gabriel Ave from 9th Street to 6th Street

6th Street – from N. San Gabriel Ave to N. Azusa Ave.

N. Azusa Ave. from 6th Street to Foothill Blvd.

Footill Blvd. from Azusa Ave. to N. Dalton Ave.

N. Dalton Ave – from Foothill Blvd. to 9th St.


The wireless signal should provide service to all outdoor areas and extension into some indoor spaces is acceptable. Parties may negotiate extension of signal into some indoor spaces, such as the Senior Center and Library. Proposers should anticipate that the signal will be backhauled to 729 N. Azusa Avenue where an internet connection will be provided. Proposers should describe how this network can be expanded to provide a high-speed backbone for AMI network with low latency for applications such as Distributed Automation and Outage Management System. The basic anticipated attributes of this network are set forth below:

High bandwidth capacity to handle multiple applications. Applications include Advanced Metering Infrastructure (AMI), Distributed Automation, Outage Management System, Web access, e-mail access, and other portable computing applications.

o Traffic from each application must be capable of being segmented using unique VLAN ID’s.

o Every Application/VLAN traffic must be capable of being Prioritized over applications.

o Application Data rates must be capable of being restricted using Standards based Rate limiting.

High security. Offers a high level of security at multiple layers using industry-standard security technologies.

o AES encryption of data is essential

o Ability to suppress the broadcast of SSID’s from the AP’s

Scalable to expand into other geographic areas. Offers ability to expand into other area of service areas and potentially the entire City of Azusa. The network must be able to be upgraded and expanded with no down time or re-configuration of existing Network devices.

High availability. Delivers 99.99% availability within the network coverage area. Loss of one device should not cause a network disruption or reduction in services.

Fault tolerant and redundant. Provides automatic fail-over protection at multiple levels, including at the wireless link and the connection to the wired network. Network should be capable of being “Self-healing” and “Self Optimizing” requiring little or no intervention from IT department.

Interference resilient. Offers protection against local environmental disrupters and resiliency for interference. Network devices should be able to avoid “Self Interference” as well as being able to change channels and/or frequencies in cases of congestion.

Standard IEEE 802.11a/b/g/n wireless Ethernet compliant. Interoperates with standard IEEE 802.11a/b/g/n networking devices.

Standard IEEE 10/100BASE-T wired Ethernet compliant. Interoperates with standard IEEE 10/100BASE-T networking devices.

Standard IETF TCP/UDP/IP compliant. Interoperates with IETF IP v4 as well as IETF TCP and UDP.


Distributed architecture. Uses distributed intelligence to optimize the network, make path selection and routing decisions, enforce security and QoS policies, etc. That is, network must not rely on a centralized controller for its operation. It must remove potential single-points-of-failure and eliminate unnecessary network traffic.

Centralized management control. Provides central management and control over the network. However, the network’s operation must not rely on on-going communications with the central management and control system.

Layer 3-based. Path selection protocol based on Layer 3 routing.

An ALW login page is to be provided to users and require agreement with basic terms and conditions for use of Public Wi Fi Network. Such page is to be easily editable to provide the public with different public service announcements desired by ALW or the City of Azusa. Proposers may refer to Map of Electric Distribution System as listed in Appendix 3 for vertical infrastructure to formulate diagram of network and cost proposal. In providing cost proposal, please list all equipment and devices in Attachment 1.

3.4.14 AMI Pilot Demonstration

Given the scope and cost of this project, it is required that Proposer demonstrate the technical feasibility of their proposed equipment and services by offering a Pilot program. Proposers may offer this pilot demonstration at no charge, or include a separate cost estimate for the pilot program per the cost sheet provided in Attachment 1. It is desirable that such pilot program demonstrate the full capabilities of the proposed AMI system across a wide spectrum of representative customers and meter types, both water and electric. The proof of concept will focus primarily on fulfilling the goals of the Customer Service Division.

ALW’s high level requirements underlying the Pilot Project are outlined below:

Replace water and electric meters as specified by this RFP on meter reading routes or billing cycles 17-4 and 17-5. See Appendix 5 “Map of Pilot Area” and Appendix 6 “List of Meters in Pilot Area”.

Provide all meter replacement information as required for billing purposes to Customer Service Division. See Appendix 11 for data required with meter replacements.

Configure and deploy AMI infrastructure to read meters on meter reading routes 17-4 and 17-5. This includes integration between the selected AMI Headend system and selected MDM system.

Configure and deploy an MDM System o To produce billing file from MDM system in format that can be read

by ALW’s CIS. See Appendix 11 for file format sample. o To remotely disconnect and reconnect customers as specified by this

RFP and provide all pertinent information for ALW’s CIS. See Appendix 11 for data required for disconnects and reconnects.

Go live with remote reading of routes 17-4 and 17-5, and production of billing files from MDM System. Go live to include demonstration of remote


disconnect and reconnect, with system generating work order completion files for manual entry into CIS, including meter no., closing and opening reads.

Any other functionality mutually agreed to by Proposer and ALW to be demonstrated.

Proposers to provide estimated deployment schedule for the Pilot project in format similar to that outlined below:

Event Schedule Description

AMI Network Design / Deployment & Meter Replacements

No. of Weeks Design AMI Network and install all network devices. Replace all meters in pilot area.

Alpha Phase No. of Weeks

Installation of the MDM System and AMI Headend. Focusing specifically on integration of metering data from the AMI Headend to the MDMS, with the MDMS providing read files to the CIS for billing purposes. The goal is to demonstrate the ability to produce a bill from automated meter data at the beginning of the Beta phase of development.

Beta Phase No. of Weeks

Field deployment of a pre-determined quantity of metering hardware and backhaul network infrastructure. Business process changes and improvements are implemented. Test and execute remote disconnects/reconnects, and read full meter routes.

User Training No. of Days Train the workforce so that they understand the concepts and operations of the newly deployed systems and work processes and methods.

System Acceptance Testing

No. of Weeks

Conducted by ALW to verify that all requirements have been met by the deployed system. Client resources work through all of the user scenarios factored into the system design through the use of test scripts. Errors and bugs are logged and resolved, then re-tested until complete.

ALW will create criteria for evaluating performance of awarded Proposer’s demonstration project. Criteria may include, but not be limited to, the following:

Proposer’s organizational skills in planning demonstration project

Proposer’s scheduling of project and “on-time” implementation of project


Ease of implementation as evidenced by number of issues or bugs that surface

Severity of problem issues or bugs that result from project implementation, e.g., system devices not working properly, integration issues of different systems, programming issues, file format issues, work process re-engineering issues, training of key staff, etc.

Competence of Proposer’s staff to quickly resolve issues with minimal involvement of ALW staff

Budget for project and ability of Proposer to stay within budget Significant deviations from project schedule, budget, system performance standards, or inability of Proposer to resolve issues in reasonable timeframe, may be grounds for discontinuing pilot demonstration. As part of the proposed pilot demonstration, Proposers are required to place pulled meters into inventory until completion of the pilot. If the pilot project fails to meet expectations, ALW prefers that the Proposer re-install old meters/registers.

3.4.15 Phase I Option – Prepay System

It is desirable that Proposers include a Prepayment solution which allows ALW to set up electric customers as a Prepay account. ALW’s current CIS vendor does not offer prepay functionality and so it is desirable that proposals include this functionality as an option that can be operated as a stand-alone solution.

Any proposed prepay system should provide customer with near real time usage and dollar balance, and provide customer with a convenient payment option(s), which, when used, automatically updates the customer record by increasing kWh energy balance or dollar balance.

The system should also generate text and email notices to customer of payment balance, especially when balance gets low and threatens shut off. Once payment balance has lapsed, system should provide notice to customer and automatically shut off service.

It appears that such systems would have to be integrated with MDM System. Please provide full description of how proposed solution would work and any extra programming this system would involve.

ALW anticipates that this Prepay feature may not be deployed until the later stages of the project, however, ALW desires early functional testing of this feature if it is available. Testing may be included in pilot demonstration.

3.5 Phase II – Water System Requirements

3.5.1 Water System Enhancements

Proposer shall provide a scope of work for services and supplies necessary to meet the goals and requirements of the Water Division as set forth in Section 2.1.1 of this RFP. Scope of work and proposed costs shall include the following items:


Integrate meter data with the existing SCADA system to allow the production operators to monitor the amount of flow from one pressure zone to another pressure zone using meters at each zone connection regulator.

Correlate interzone flow with service to all meters in each zone or multiple zones to determine the water loss in each zone.

Integrate meter data with Azusa’s Water System hydraulic model to allow the operators to monitor the flows in the water system on a real time basis.

Make use of analytics to identify and replace inaccurate meters.

Perform trend analysis on water meter types to predict when the meters will need replacement.

Based on measured water loss as determined by analytics, install leak detection equipment, including in-line leak detection devices, in strategic locations to identify pipeline leaks.

Provide analytics to detect customer side leaks and reduce water theft due to continuous flow monitoring in the system.

3.5.2 Scheduling of Water System Enhancements

Proposers may schedule the above described Water System Enhancements to be developed and implemented concurrently with Phase I AMI Project following successful completion of Pilot program. Proposer may wish to demonstrate how some of these Enhancements could be performed jointly during the proposed Pilot and how they will be integrated with the AIM project.

3.6 Phase III – Electric System Requirements

3.6.1 Electric System Enhancements

Proposer shall provide a scope of work for services, equipment and supplies necessary to meet the goals and requirements of the Electric Division for the following items:

Outage Management System (OMS) with outage mapping

Transformer Load Management

Theft Detection System

Proposer shall assess the Map of the Electric Distribution System in Appendix 3, including all system devices on the Map, and formulate a proposal to provide ALW with above solutions or systems. Both one-time capital costs and ongoing maintenance costs are to be provided in the format as set forth in Attachment 1 – AMI_MDM_OMS Cost Proposal. Each Proposer shall also complete Attachment 7 – AMI_OMS Requirements.

The proposed OMS should be one that functions within the AMI architecture. The OMS requirements outlined in Attachment 7 are expressed in categories of features that have similar characteristics or functions. The categories include the following:

AMI Data Communications

Incident Analysis Requirements

Geographic Display Requirements

Outage Reporting Requirements

Future Integration of Systems


A point-by-point response must be completed and submitted in the Microsoft Excel format presented as Attachment 7 – OMS Requirements. Referring to a particular requirement is done by specifying the Category and the Requirement ID number, for example:

“Incident Analysis-13” refers to the requirement, “The system should provide a “map display” function that provides the capability to select an outage and center the outage location in the graphic display window.”


In addition, Proposers shall fully describe proposed Transformer Load Management system and devices. Proposals shall include description of how these systems work with the AMI meters placed into the service through this project. The Transformer Load Management system must be in operation at other utilities and Proposers should explain how well their system works and what advantages it provides over competitive systems.

Also, Proposers shall fully describe proposed Theft Detection System and devices. Proposals shall include description of how these systems work with the AMI meters placed into the service through this project. Proposed Theft Detection System must be in operation at other utilities and Proposers should explain how well their system works and what advantages it provides over competitive systems.

3.6.2 Scheduling Electric System Enhancements

Proposers may schedule the above described Electric System Enhancements to be developed and implemented concurrently with Phase I AMI Project following successful completion of Pilot program. Proposer may wish to demonstrate how some of these Enhancements could be performed jointly during the proposed Pilot and how they will be integrated with the AIM project.

3.6.3 Other Info to be Provided – Volt-VAR Management / Reduction and DA

ALW desires Proposers to provide a description of their service offerings with respect to Volt-VAR management / reduction programs and Distributed Automation (DA).

Proposers are requested to elaborate on what services they offer in these areas, and how these solutions can be implemented through a subsequent project. Proposed Volt-VAR management and load reduction devices, as well as other DA devices, must be interoperable with Proposer’s AMI Project system devices.

It is highly desirable to ALW, that Proposers offer competitive Volt-VAR management / reduction programs and have robust DA capabilities so that these may be later added to our Electric Distribution System following this AMI Project, so Proposers are encouraged to demonstrate their capabilities in these areas with their Proposal.

3.7 Services Requested

Provide a scope of work for implementation services to support this project based upon the information provided. Include cost estimates in Attachment 1 for the


expected level of effort, recognizing that the exact scope of services will be further developed in contract negotiations with the selected Proposer. Proposers should address the following services in developing their professional services recommendations:

Proposer shall work with ALW staff in developing and re-engineering basic work processes, and shall provide training on new work processes

Proposer shall provide training on the use of any proposed software and field equipment

Proposer will be responsible for the configuration and testing of all software and product(s) before release to ALW for acceptance testing

Proposer shall verify product performance in the ALW environment and provide technical support as needed

Proposer should provide options for additional professional services that may bring value to the project beyond the level required for the basic configuration and testing

3.8 Additional Functional Capabilities

The Proposer may wish to propose on other additional features and functions of the AMI meters or network not specifically included above, which it believes will benefit the ALW. Proposer should address each of these areas in their technical response and provide a cost estimate in Attachment 1.


4 General Response Requirements

This section provides an overview of what information is generally required from Proposers. Section 5 of this RFP sets forth the format for how proposals are to be organized and includes a ‘Technical Proposal’ section. While Proposers have some discretion in organizing their proposals, it is anticipated that much of the content included in this section will be provided in the ‘Technical Proposal’ section of your proposal (See Section 5 of this RFP).

4.1 Company/Staff Qualifications

Provide the following information in your response:

Name of firm and mailing address, phone and fax number of the proposer’s principal place of business.

Mailing address, phone and fax number of the office in which the project team will work.

Names and positions of persons to be assigned to this project, including a description of their chief role.

Mailing address, staffing and degree of participation by any firms submitting jointly as part of project proposal.

Resumes and relevant experience of key staff to be assigned by proposer to this project. These should clearly demonstrate the qualifications of key personnel to perform required tasks of this RFP.

Overall company experience in AMI deployments, network operations, systems integration. Include a brief company history, including ownership, size, capital position, financial health, market share statistics, number of offices nationally, and clients in California and nationally.

If appropriate, describe the relationships amongst the different entities proposing jointly, how long you have worked together, what projects were successfully implemented jointly, and whether any of the companies submitting jointly have vested interest in one another.

Proposer shall attest to the availability of key staff to fulfill the obligations of this engagement in a professional and timely manner. If there are any scheduling issues of concern, then proposing firms shall disclose those other commitments in its Proposal and indicate how such other commitments will be addressed to mitigate their effect on services rendered to ALW.

4.2 Product Overview

Provide a product overview and discuss the evolution of the proposed AMI product and the MDM product from the first major release through to the present. Include the historical timeline. Include a clear explanation on how the AMI network is managed in areas lacking AC Power. Specify product(s) warranty.

4.3 Product Development

Provide a copy of the AMI product and the MDM product development roadmap outlining the vision and strategy for the future of the proposed AMI System. Include


a description of the upgrades/enhancements that are in the planning or design stage. Include an estimated release schedule for planned upgrades/enhancements.

4.4 Proposer References

The City considers references for both the overall solution and implementation of that solution to be important in its decision to award a contract. Include Proposer references based on the guidelines established in Section 5.5. References will be contacted by the City and/or its consultant for those Proposers that are short-listed during the selection process.

4.5 Work Plan

Proposer should give an introduction and overview of the approach your firm would use in fulfilling the obligations set forth in the Statement of Work of this RFP by breaking down the scope into a specific list of tasks. The task listing should cover all the features and functions set forth in the Statement of Work and clearly describe how your firm will go about designing and constructing the AMI network, process to replace meters, integrate the AMI headend with the MDMS, integrate the MDMS with CIS, and fulfill other deployments required by this RFP.

It is extremely important that Proposer work plans include a detailed description of how your team will manage meter replacements. Proposals are to include a step-by-step description of how meters will be replaced, meter read data gathered, and how our CIS account records will be updated with the pertinent information to process a meter change outs. Proposals that include an automated process for updating ALW’s CIS shall include a full description of the database fields that will be updated and how the update will be executed.

ALW prefers the designated Proposer Project Manager (PM) along with key Proposer team members to be on site during this engagement. The City expects weekly project status meetings and written status reports. If Proposer has an alternative approach, please specify in the response why this approach is advantageous to the ALW.

4.6 Project Schedule

ALW prefers that project proposers provide a schedule for the primary tasks that make up proposed work plan. A Gantt chart format is preferred.

4.7 Data Requests

Proposer shall itemize all documents or data the proposer expects ALW to provide in carrying out this project.

4.8 Testing

Describe the proposed test plan/strategy and testing tools to be employed to support and ensure user acceptance for both Pilot Project and for Full Scale Deployment. Include Proposer’s high level test plan as Attachment 2.


4.9 Training

Describe roles and responsibilities of Proposer as SGS service provider, and ALW personnel in working with AMI systems. Provide a discussion of the proposed training plan/strategy for ALW for designated roles and responsibilities. At a minimum, training to include:

Headend software system overview training

Headend software system admin training

Diagnostic and troubleshooting training of field and communications equipment

MDM software system overview training

MDM software system admin training

MDM software end user training

CSR Training on processing Meter Replacements, Billing Cycle Remote Reading, Remote Check Reads, Remote Disconnect/Reconnect, Billing File downloads from MDM and uploads to CIS

Customer Engagement Solutions training

OMS software system overview training

OMS software system admin training

OMS software end user training

Describe classes/courses proposed in the training plan. Provide suggested training schedule over the duration of the project. Include Proposer’s high level training plan and user training materials as Attachment 3.

4.10 User Groups

Describe any existing user groups that are currently supported and summarize typical meeting schedules, meeting sites, and practices. Include any electronic bulletin board or internet services.

4.11 Scalability

For both the AMI and MDM system, proposer should provide documentation to support future scalability and expandability beyond what is initially required to support implementation. Documentation should specify hardware, network, and licensing that may be required to support scalability.

4.12 Software Releases

For AMI, MDM and OMS systems, provide the implementation process for releasing and applying software and firmware upgrades, bug fixes, and patches. Include overall implementation timeframe, vendor effort/time/resources, and client effort/time/resources. Discuss the quality assurance (QA) procedures currently in place to ensure bug fixes, patches, and upgrades are fully tested and validated prior to release. Discuss QA procedures currently in place to ensure the identification and correction of system security vulnerability.


4.13 Maintenance and Support

Service provider would also be responsible for ensuring that critical data from the network is available to ALW and Customers alike through a service level agreement (SLA) that would guarantee uptime and response times to fix network issues. Proposers to put forth draft terms and conditions of such SLA as Attachment 4. The SLA should clearly indicate the severity levels, description of each level, guaranteed response times, and associated cost.

Summarize AMI system, MDM system and OMS maintenance agreements including terms and conditions.

4.14 Product Licensing

Describe the terms of the proposed AMI Headend software, MDM software, and OMS software license agreements. Describe how Proposer calculates the user count when calculating the licensing cost. Specify whether there are any additional licensing costs/fees associated with the setup/maintenance of a separate test and development environment.

4.15 Documentation

Proposer shall provide complete documentation and instructions for the installation and maintenance of the AMI System before initial implementation of the software and field equipment. Written and electronic copies of such documentation shall be required during the submittal process requiring approval from ALW.

4.16 Hardware/Software Specifications

Proposer shall provide specifications for all computer hardware and operating system software necessary for implementation.

4.17 System Security

Proposer shall describe the strategies and methodologies of computer system security for all systems to be deployed through this project. The Proposer shall provide level of compliance for the latest North American Electric Reliability Corporation (NERC) Critical Infrastructure Protection (CIP) version. In addition, the Proposer shall describe security characteristics included in metering and communications equipment.

4.18 Scope Exclusions/Addenda

In reviewing this RFP, Proposer may encounter tasks, which, in the opinion of some, may be unnecessary, or, may have been omitted. At the Proposer’s discretion, it may identify such tasks and either comment on why they should or should not be included as part of this RFP.


5 Proposal Response Format and Content

At the conclusion of this RFP process, ALW must fully understand the capabilities and costs of the proposed system from each Proposer. This includes, but is not limited to:

Level of service to be provided through a SGS agreement, including roles and responsibilities of Proposer and ALW over time through the term of the service and purchase agreement

Total cost and effort required of purchasing the AMI system including electric and water metering devices, communications equipment, headend software and hardware, and any optional components

Total cost and effort required of purchasing an MDM system including software and hardware, and any optional components

Total cost and effort required of purchasing an OMS including software and hardware, and any optional components

Ongoing costs of services and transition to full ownership of systems by ALW

More complete understanding of the skillsets required to utilize and manage the AMI system, MDM system and OMS over time and on an ongoing basis

The level of effort and cost to train ALW personnel on all aspects of the system and system components

This section describes the required proposal response format and content. Proposers are instructed to follow this format without deviation to aid ALW to review and compare all proposals. Additionally, relevant support information may be submitted in the appendices. The following describes the response format:

5.1 Table of Contents

Include a Master Table of Contents in the response.

5.2 Section 1 – Cover Letter (3 pages maximum)

Highlight the key aspects of the response, as well as the unique advantages of the Proposer’s offer. Indicate to whom all proposal communications should be addressed, including an e-mail address.

5.3 Section 2 – Technical Proposal

Describe the technical aspects of the product and service offering as requested in Sections 3 of this solicitation. Pay particular attention to describing clearly and concisely the functional and performance benefits of the offering.

Provide an overview of how the system is commissioned -- basic steps, programming/configuration of elements, necessary or optional tools if any and all software recommended or required.

Describe in detail how meter exchanges will be accomplished and how account records will be updated in our CIS. This description should be step-


by-step and should include what method will be used to update CIS database, i.e., automated via mass batch files, or manual. If automated, description should include list of fields Proposer is committing to update. This section shall include description of work that ALW staff is expected to perform.

Describe any tools available in the proposed system to aid in configuration, network analysis, and troubleshooting.

Describe how data integrity and security measures are built into the software, particularly those designed to protect data during transmission and storage.

Provide any information on support plans and optional services, including ongoing and annual fees, with respect to a full deployment project.

A point-by-point response must be completed and submitted in the Microsoft Excel format provided in Attachment 5 – AMI System Requirements. Attachment 5 contains the following three (3) tabs:

Instructions

AMI System Req

Response Options

A point-by-point response must be completed and submitted in the Microsoft Excel format provided in Attachment 6 – MDM System Requirements. Attachment 6 contains the following three (3) tabs:

Instructions

MDM System Req

Response Options

A point-by-point response must be completed and submitted in the Microsoft Excel format provided in Attachment 7 – OMS Requirements. Attachment 7 contains the following three (3) tabs:

Instructions

MDM System Req

Response Options

As outlined in the Instructions tab provided in each workbook, Proposer shall select one of the following statements of conformance from the drop down menu along with supporting explanation or description:

Current Base – The function is provided in the base product today. No modification is required. No additional cost.

Future Base Release – This function will be provided in a future base release that will be a general release within 18 months from submission of this response. No modification is required. Vendor will indicate timing of when desired functionality will be available.

Modification – This business function can be supported by modifying an existing screen, existing view or existing native report. There would be no


change in the system source code required and would not break the system upgrade path. One time modification.

Third Party System – This function is provided in another product which is integrated with the base. No modification is required. Vendor must indicate estimated cost if applicable.

Customization – This requires a specific enhancement to be developed for ALW and will be an additional cost. This enhancement would include, but not be limited to revisions to the source code of the core system, database objects, and/or custom reports. This type of customization is assumed to break the upgrade path of the core system. Vendor must indicate estimated cost.

Not Provided – This functionality is not provided by the vendor in the proposed solution.

5.4 Section 3 – Cost Proposal

Proposer shall submit a cost estimate for both the Pilot project and Full Scale Deployment. The cost schedules must be completed and submitted in the Microsoft Excel format provided in Attachment 1 – AMI_MDM_OMS Cost Proposal. The cost estimate should include all costs related to implementing the detailed requirements in this RFP, whether such implementation requires customization to the software or not.

Attachment 1 contains the following five (5) tabs:

Instructions

1a. Pilot Cost Proposal

1b. Full Deploy Budgetary Proposal

1c. Additional Offerings

Payment Plan Options

As outlined in the Instructions tab, Proposer shall populate the Item, Quantity, Unit Price, and, if applicable, Equipment Lead Time for both the Pilot and Full Deployment. The Total Cost column will populate automatically based on Quantity * Unit Price; however, Proposer must verify. A Notes/Comments column is also provided for Proposer explanation and clarification. Provide the cost detail for a Downtown Wi Fi Service, Customer Prepay, Integration with CIS WebConnect, and any additional offerings in the Additional Offerings tab.

Proposer may be required to provide supplemental information necessary to explain or justify the total price. Additive or deductive options may also be provided.

Proposer shall include payment plan options to ALW in the Payment Plan Options tab, which includes at a minimum:

(1) a monthly subscription per meter for ongoing SGS services; and

(2) a monthly subscription per meter for ongoing SGS services, assuming ALW purchases all meters and registers


Each of the above options shall include a date or year at which time ALW would take ownership of all equipment, software, and networking devices, for all systems. Proposers shall include options for ongoing SGS services after ALW takes ownership. Pricing shall be stated in terms monthly per meter service charges. It is assumed that these monthly service charges will significantly step-down after ALW takes ownership of the system.

Note that the initial service charges, number of years before ALW takes ownership, and the step-down service charges after ALW takes ownership of system, will be significant factors in evaluating proposals.

5.5 Section 4 – References (8 pages maximum)

Provide a comprehensive list of contacts where similar work has been performed by Proposer, including mass meter exchanges and CIS database updates, installations of the software, and ongoing support services in the following format:

Utility Name City/State Installation Date Account Size

Provide six (6) detailed references for which similar services have been provided in the last three years, preferably to municipal utilities, by the staff to be assigned to this project. These references shall be provided with the following information:

Organization Name

Address

City/State/Zip

Contact Name

Telephone

E-mail Address

Project Name

Project Start Date

Project End Date

Project Scope

5.6 Section 5 -- Cost-Benefit Estimate

Proposers are requested, but not required, to provide an estimate of the dollar value of the benefits ALW would realize from approval of your cost proposal. Estimates maybe based on Proposer’s prior experience in implementing similar projects.

5.7 Section 6 – Attachments

As referenced in this RFP, the Proposer must include the following attachments to the response:


Attachment 1 – AMI-MDM-OMS Cost Proposal

Attachment 2 – Test Plan

Attachment 3 – Training Plan

Attachment 4 – Service Level Agreements

Attachment 5 – AMI System Requirements

Attachment 6 – MDM System Requirements

Attachment 7 – OMS Requirements

5.8 Section 7 – Appendices

Include relevant material(s) needed to aid in the understanding of the proposal content. This may include additional detail which will enhance the response or will aid in ALW’s evaluation of proposals but was not specifically solicited.

6 Proposal Evaluation

6.1 Proposer Short-List

ALW may elect to conduct oral interviews with a short-list of Proposers whose proposals are ranked the highest after the initial evaluation. In preparation for such interviews, additional information or product demonstrations may be requested from the Proposer.

6.2 Evaluation Criteria

The proposals submitted in response to this request will be evaluated by the ALW selection committee. This committee will evaluate the proposals using a criteria that includes such factors as:

Proposed systems features and functions

Experience and qualifications of firm and assigned staff, including experience with mass meter exchanges and CIS updates of meter data

Performance of Proposer in providing similar services to other utilities as verified through references, especially for mass meter exchanges

Feasibility to integrate all proposed systems with each other and existing ALW CIS

Proposed cost of systems and financing plan

ALW reserves the right to consider other factors in addition to the Proposal in making its final decision.

6.3 Ranking

All proposals will be reviewed and ranked according to the Evaluation Criteria above and any or all Proposers may be selected for interviews or oral presentations. ALW makes no commitment to any respondent to this RFP beyond consideration of the written response to this RFP. Proposers not selected will be notified of the selection outcome.


7 Proposal Timeline

7.1 Schedule of Events

Event Date

RFP Release TBD

Intent to Propose Notice due TBD

Pre-Proposal Meeting TBD

Proposer Questions due TBD

Proposal Response due TBD

Response Evaluation TBD

Short List Presentations TBD

Final Vendor Selection TBD

Start Contract Negotiation/Design Work Target - TBD

Contract Approval Target - TBD

Start of Implementation Target - TBD


Appendices

Request for Proposal - Granicus

Documents

Transcript of Request for Proposal - Granicus