Agreement with Badger Meter Inc

1 
01/28/2025 
EQUIPMENT PURCHASE AND SERVICES AGREEMENT 
This Equipment Purchase and Services Agreement (“Agreement”) is entered into and effective between CITY OF 
GLENDALE, an Arizona municipal corporation (“City”) and Badger Meter, Inc., a Wisconsin corporation with 
offices located at 4545 W. Brown Deer Road, Milwaukee, Wisconsin 53223 (“Badger Meter” or "Contractor")  , and 
authorized to do business in the State of Arizona, (“Contractor”) as of the 
 (“Effective 
Date”). 
RECITALS 
A.
City desires to purchase certain equipment (“Equipment”) from Contractor for the Advanced Meter
Infrastructure (AMI) project (the “Project”), as set forth in the attached Exhibit A, Schedule of Values
(“SOV”) containing the City’s specifications, standards and criteria;
B.
Contractor is also providing the City with certain professional services (“Services”) to install the equipment
for the Project, as set forth in the attached Exhibit B, Scope of Work (“SOW”) and ensure it is performing
to meet the City’s specifications, industry standards, and the quality standards set forth in this Agreement;
and
C.
City and Contractor desire to memorialize their agreement with this document.
AGREEMENT 
The parties hereby agree as follows: 
1.
Schedule.  The Equipment and Services identified in the SOV and performed in accordance with the SOW
will be built, delivered, installed and provided by the Contractor in a timely and efficient manner. Contractor
will also ensure the equipment will perform as described in the attached as Exhibit C.
2.
Contractor’s Work.
2.1 
Relationship Between the Parties. Contractor is supplying the Equipment and performing the 
Services required under this Agreement as an independent contractor.  Contractor and its employees, 
and any Subcontractor and its employees, are not City employees and are not entitled to any benefit 
provided to City employees other than those explicitly provided by this Agreement.  This Agreement 
further does not create any benefits, rights or obligations for any third party not in privity to this 
contract. 
2.2 
Standard and Warranty. 
a.
The Contractor expressly warrants the Equipment in accordance with the standard
manufacturer warranties included in Exhibit C herein (the “Warranties”) and further agrees that the
Equipment will:
i.
Conform in all respects to the City’s specifications, drawings, requirements, or other
descriptions.
ii.
Be fit for the purpose or purposes of intended use.
iii. Conform to all applicable local, state, and federal laws, ordinances and regulations.
iv. Be of good quality, merchantable, of good workmanship, or material best suited for
the intended purposes, and free from defects of any kind or nature whatsoever.
b.
With respect to the installation services that are being provided as part of the Services, the
Contractor warrants that such services will be free from defects in workmanship for a period of
twelve (12) months from the date of installation as recorded in the work order management system
utilized for the Project.

2 
01/28/2025 
c.
All Equipment delivered or supplied hereunder will be free and clear of all liens, 
encumbrances, claims, and security interest of whatever nature and substance. Upon request, the 
Contractor shall supply the City with documentation satisfactory to it, evidencing the absence of such 
liens, encumbrances, claims, and security interests. 
d. 
All warranty periods shall begin upon when the Equipment is installed. 
e. 
Contractor must provide, install and operate the Equipment and perform the Services in 
accordance with the attached SOW, any applicable standards of due diligence, care, and quality 
associated with the successful furnishing of equipment for projects that are equivalent in size, scope, 
quality, and other criteria as identified in this Agreement.   
g. 
The City has expressly consented to allowing Contractor to engage certain subcontractors to 
perform some or all of Contractor’s obligations under this Agreement as further stated in the attached 
SOW.  The City shall not be liable to subcontractor for any claims, including claims for payment for 
Services rendered, of any kind.
2.3 
Licensing.  Contractor further warrants that: 
a. 
Contractor currently holds all appropriate and required licenses, registrations and other 
approvals necessary for the lawful furnishing of the Equipment and Services as contained in 
the SOW (“Approvals”); and 
b. 
Neither Contractor nor any Subcontractor has been debarred or otherwise legally excluded 
from contracting with any federal, state, or local governmental entity (“Debarment”). 
(1) 
City is under no obligation to ascertain or confirm the existence or issuance of any 
Approvals or Debarments, or to examine Contractor's contracting ability. 
(2) 
Contractor must notify City immediately if any Approvals or Debarment changes 
during the Agreement's duration. The failure of the Contractor to notify City as 
required will constitute a material default under the Agreement. 
c. 
Background Check.  In accordance with the City’s current background check policies, the 
City may conduct criminal, driver history, and all other requested background checks of 
Contractor personnel who would perform services under the Agreement who will have 
access to the City’s information, data, or facilities. Any officer, employee, or agent that fails 
the background check must be replaced immediately for any reasonable cause not prohibited 
by law. 
d. 
Security Clearance.  The City will have final authority, based on security reasons: (i) to 
determine when security clearance of Contractor personnel is required; (ii) to determine the 
nature of the security clearance, up to and including fingerprinting Contractor personnel; 
and (iii) to determine whether any individual or entity may provide services under this 
Agreement. If the City objects to any Contractor personnel for any reasonable cause not 
prohibited by law, then Contractor will, upon notice from the City, remove any such 
individual from performance of services under this Agreement.  
e. 
Safeguarding Contractor and City Property.  Without limiting the scope or obligation to 
indemnify the City as provided in Section 7.2 below and subject to the SOW and the 
Warranties, Contractor agrees:  (i) to bear all risk of loss, injury, or destruction of its own 
Equipment incidental to Contractor providing the Services under this Agreement and that 
such loss, injury, or destruction will not release Contractor from any obligation hereunder; 
and (ii) it is responsible for any damage or loss to City real or personal property when such 
property is the responsibility of or in the custody of Contractor or its personnel. 
2.4 
Compliance.   
a. 
Equipment as provided in the SOV and Services as provided in the SOW will be furnished, 
installed and operated in compliance with applicable federal, state, county and local statutes,

3 
01/28/2025 
rules, regulations, ordinances, building codes, life safety codes, and other specifications, 
standards and criteria designated by City, including its Drug-Free Workplace policy.  
b.   
Nothing in this Agreement requires the City to accept Equipment or Services that does not 
meet the specifications, standards and criteria contained in the Warranties or the SOW.  In 
the event the Equipment does not meet the specifications, standards and criteria contained 
in the Warranties, the City may, at its sole discretion: (i) reject the Equipment and terminate 
this Agreement; or (ii) give the Contractor a reasonable time to cure any defect or non-
compliance. 
c. 
Contractor must not discriminate against any employee or applicant for employment on the 
basis of race, color, religion, sex, national origin, age, marital status, sexual orientation, gender 
identity or expression, genetic characteristics, familial status, U.S. military veteran status or 
any disability. Contractor will require any Sub-contractor to be bound to the same 
requirements as stated within this section. Contractor, and on behalf of any subcontractors, 
warrants compliance with this section. 
3. 
Compensation.   
a. 
The total not-to-exceed amount available under this Agreement for City’s purchase of Equipment 
and Services and for Contractor’s satisfactory performance of all related obligations as specified in this 
Agreement, the SOV and the SOW shall not exceed $29,045,000.00.  Based on the estimate provided by 
Contractor, the not-to-exceed amount has been calculated to include a base amount of $ 26,438,976.67 to 
perform the work identified in the SOW and provide the Equipment for the Project identified in the SOV, 
plus a contingency fund of the total not-to-exceed amount, equal to $2,606,023.33, for unforeseen or 
unanticipated costs.  Any contingency funds may only be used to pay for additional Equipment and/or 
Services authorized by the City through a Change Order as described in this section. Additional funds for 
performing work, activities or tasks for other parts of the overall projects may, but are not required to, be 
available under separate contracts or agreements. 
b. 
Change Orders.  Based on the field conditions or other issues encountered during the implementation 
of the SOW, the City may authorize changes to the SOW without amending this Agreement. Amending this 
Agreement is not required if:  (1) the total value of all Change Orders authorized by the City does not exceed 
the total amount of Compensation in subsection 3(a) above, which includes the contingency funds set aside 
for such purpose; and (2) if the total value of all Changes Orders does exceed the total amount of 
Compensation in subsection 3(a) above and the total of a single or all change orders combined to be approved 
is less than one hundred thousand dollars ($100,000.00). Any single change order or combination of change 
orders which will increase the compensation amount by one hundred thousand dollars ($100,000.00) or more 
above the total approved amount (including the contingency funds) in subsection 3(a) above must be 
approved by an affirmative vote of the city council.  
c. 
All Change Orders must be approved by the City prior to the Contractor initiating the performance 
of the new, additional or changed Work. 
d. 
The City may also authorize minor changes to the Scope of Work by issuing a Field Order, provided 
such Field Orders do not increase the cost of the work to be performed or materially affect the mutually 
agreed upon schedule for the Project. The Contractor shall proceed with the performance of any Field Orders 
as required by the City, within two days after formal written documentation has been sent to the Contractor’s 
project manager for the Project to effect the minor change incorporated into the Field Order.  The Contractor 
but may dispute whether it is entitled to an increase to its Compensation based on the cost of implementing 
such Field Order as provided in Section 16 of this Agreement only after the work has been completed.  
e. 
The Contractor shall execute and provide to the City, within 10 calendar days of the Effective Date 
of this Agreement, Performance and Payment Bonds with surety in an amount equal to 100% of the amount 
of the Compensation (including the contingency funds) available under subsection a above. The sureties of 
all Bonds shall be placed or obtained from such surety company or companies as are approved by the City 
and are authorized to transact business in the State of Arizona.

4 
01/28/2025 
4.
Billings and Progress Payments.
4.1 
Payment for Equipment. Consistent with Section 9 of the SOW, invoices will automatically be 
generated when Equipment manufactured by Badger Meter are shipped. The Contractor will  be paid  
by ACH NET 30 days from the date the equipment is received in MSI’s warehouse and accepted by 
the City. All other invoices will be paid within 30 days of their acceptance by the City. The City must 
provide written notice of non-acceptance of delivered Equipment due to non-conformance with the 
purchase order within five (5) days of receipt of the Equipment (the “Inspection Period”). If no 
written notice is received by the Contractor within the Inspection Period, the Equipment will be 
deemed to be accepted for purposes of this Section 4.1.    
4.2 
Applications for Services. 
a. 
Subject to Section 9 of the SOW, Contractor will submit its invoice (“Payment Application”) 
for Services monthly to City’s Project Manager and City will remit progress payments based 
upon the Payment Application as stated below.
b. 
The City will process and remit payment of 95% of the charges incurred and billed by 
Contractor in the prior month within 30 days, unless the Equipment delivered and installed 
or the Services performed do not meet the City’s specifications or the City rejects the 
Payment Application for any other reason.  The remaining 5% of the Contractor charges 
incurred in the prior month will be retained to ensure timely and adequate performance of 
the work remaining under the SOW.  The 5% retainage due and owing will be released upon 
closeout of the Project pursuant to Section 10 of the SOW. 
4.3 
Review and Withholding.  City’s Project Manager will timely review and certify Payment Applications. 
a. 
If the Payment Application is rejected, the City will issue a written listing of the items not 
approved for payment. 
b. 
City may withhold an amount sufficient to pay expenses that City reasonably expects to incur 
in correcting the deficiency or deficiencies rejected for payment. 
5. 
Termination. 
5.1 
For Convenience.  City may terminate this Agreement for convenience, without cause, by delivering 
a written termination notice stating the effective termination date, which may not be less than thirty 
(30) days following the date of delivery of notice.  
a. 
Contractor will not be compensated for Equipment unless it has been delivered to City and 
meets the City’s specifications. 
b. 
Contractor will be equitably compensated for Equipment installed and Services furnished 
prior to receipt of the termination notice and for reasonable costs incurred. 
c. 
Contractor will also be compensated for any approved effort expended, and approved costs 
incurred, that are directly associated with project closeout and delivery of the required items to the 
City. 
5.2 
For Cause.  In addition to the remedy contained in Section 2.4(b.) above, the City may terminate this 
Agreement for cause if Contractor fails to cure any breach of this Agreement within seven (7) days 
after receipt of written notice specifying the breach. 
a. 
Contractor will not be entitled to further payment until after City has determined its damages. 
If the City’s damages resulting from the breach, as determined by City, are less than the 
equitable amount due but not paid Contractor for Equipment furnished, City will pay the 
amount due to Contractor, less City’s damages, in accordance with the provisions of Section 
4. 
b. 
If City’s direct damages exceed amounts otherwise due to Contractor, Contractor must pay 
the difference to City immediately upon demand; however, Contractor will not be subject to

5 
01/28/2025 
consequential damages more than $2,000,000 or the amount of this Agreement, whichever 
is greater. 
5.3 
Lack of Appropriations.  Nothing in this Agreement guarantees that some or all of the funds 
necessary to comply with all of the City’s obligations under this Agreement will be appropriated or 
otherwise be available.  The City agrees to seek such appropriations in good faith from the City 
Council and agrees not to use the lack of appropriation as a substitute for termination for 
convenience.  If sufficient funds are not appropriated or otherwise available, the City may unilaterally 
terminate this Agreement after providing thirty (30) days written notice.  In the event the City 
provides such notice, the City will not be entitled to a refund or offset of any amounts previously 
paid but will not pay any amounts that become due after providing such notice; provided, however, 
the City will remain responsible for the payment of any Goods delivered to the City and any Services 
that have been rendered prior to the expiration of the notice period stated above. 
5.4  
Force Majeure.  Failure by either party to perform its duties and obligations will be excused by 
unforeseeable circumstances entirely beyond its control, including acts of nature, acts of the public 
enemy, riots, fire, explosion, legislation, and pandemic. The party whose performance is so affected 
will, within five (5) calendar days of the unforeseeable circumstance, notify the other party of all 
pertinent facts and identify the force majeure event. The party whose performance is so affected 
must also take all reasonable steps, promptly and diligently, to prevent such causes if it is feasible to 
do so or to minimize or eliminate the effect thereof. The delivery or performance date will be 
extended for a period equal to the time lost by reason of delay, plus such additional time as may be 
reasonably necessary to overcome the effect of the delay, provided however, under no circumstances 
will delays caused by a force majeure extend beyond one hundred-twenty (120) calendar days from 
the scheduled delivery or completion date of a task unless agreed upon by the parties. 
a.  
Force majeure shall not include the following circumstances: 
i.  Late delivery of equipment or materials caused by congestion at a manufacturer’s 
plant or elsewhere, or an oversold condition of the market; or 
ii.  Late performance by a subcontractor unless the delay arises out of a force majeure 
occurrence in accordance with this force majeure term and condition; or 
iii.  Inability of either the Contractor or any subcontractor to acquire or maintain any 
required insurance bonds, licenses, or permits. 
b. 
A party may terminate this Agreement immediately for cause should a Force Majeure 
be alleged but determined not to exist to excuse performance. 
6. 
Conflict.  Contractor acknowledges this Agreement is subject to A.R.S. § 38-511, which allows for 
cancellation of this Agreement in the event any person who is significantly involved in initiating, negotiating, 
securing, drafting, or creating the Agreement on City’s behalf is also an employee, agent, or Contractor of any 
other party to this Agreement.  Contractor also agrees that this Agreement may be terminated for an act of a 
public employee prohibited by A.R.S. § 38-504. 
7. 
Insurance.  For the duration of the term of this Agreement, Contractor shall procure and maintain insurance 
against claims for injuries to persons or damages to property which may arise from or in connection with 
manufacturing and installing the Equipment and delivering the Services to the City’s specifications or any 
other act or activity related to performance under this Agreement. Such insurance shall cover Contractor, its 
agent(s), representative(s), employee(s), and any subcontractors and shall name the City, its employees, elected 
officials, representatives and volunteers as additional insured. 
7.1 
Minimum Scope and Limit of Insurance.  Coverage must be at least as broad as: 
a. 
Commercial General Liability (CGL): Insurance Services Office Form CG 00 01 or 
equivalent, including products and completed operations, with limits of no less than 
$2,000,000 per occurrence for bodily injury, personal injury, and property damage

6 
01/28/2025 
b.
Automobile Liability:  Insurance Services Office Form Number CA 0001 covering Code 1 
(any auto) or equivalent, with limits no less than $2,000,000 per accident for bodily injury 
and property damage. 
c. 
Professional Liability.  Contractor must maintain a Professional Liability insurance covering 
errors and omissions arising out of the work or services performed by Contractor, or anyone 
employed by Contractor, or anyone for whose acts, mistakes, errors and omissions 
Contractor is legally liability, with a liability insurance limit of $2,000,000 for each claim and 
a $4,000,000 annual aggregate limit. For the avoidance of doubt, the Technology Errors and 
Omissions endorsement that is part of the Contractor’s cybersecurity policy which has full 
prior acts cover will be accepted for purposes of this section.  
d. 
Worker’s Compensation: Insurance as required by the State of Arizona, with Statutory 
Limits, and Employers’ Liability insurance with a limit of no less than $2,000,000 per 
accident for bodily injury or disease. 
7.2 
Indemnification. 
a. 
To the fullest extent permitted by law, Contractor must defend, indemnify, and hold 
harmless City and its elected officials, officers, employees and agents (each, an “Indemnified 
Party,” collectively, the “Indemnified Parties”) for, from, and against any and all claims, 
demands, actions, damages, judgments, settlements, personal injury (including sickness, 
disease, death, and bodily harm), property damage (including loss of use), infringement, 
governmental action and all other losses and expenses, including attorneys' fees and litigation 
expenses (each, a “Demand or Expense” collectively “Demands or Expenses”) asserted by 
a third-party (i.e. a person or entity other than City or Contractor) and that arises out of or 
results from the breach of this Agreement by the Contractor or the Contractor’s negligent 
actions, errors or omissions (including any Subcontractor or Subcontractor or other person 
or firm employed by Contractor), whether sustained before or after delivery of the 
Equipment. 
b. 
This indemnity and hold harmless provision applies even if a Demand or Expense is in part 
due to the Indemnified Party’s negligence or breach of a responsibility under this Agreement, 
but in that event, Contractor will be liable only to the extent the Demand or Expense results 
from the negligence or breach of a responsibility of Contractor or of any person or entity 
for whom Contractor is responsible. 
c. 
Contractor is not required to indemnify any Indemnified Parties for, from, or against any 
Demand or Expense resulting from an Indemnified Party’s sole negligence or other fault 
solely attributable to any Indemnified Party. 
7.3 
Other Insurance Provisions.  The insurance policies required by the Section above must contain, or 
be endorsed to contain the following insurance provisions: 
a. 
The City, its officers, officials, employees and volunteers are to be covered as 
additional insureds of the CGL and automobile policies for any liability arising from or in 
connection with the performance of all tasks or work necessary to build and deliver the 
Equipment as specified by the City. Such liability may arise, but is not limited to, liability for 
materials, parts or equipment furnished in connection with any tasks, or work performed by 
Contractor or on its behalf and for liability arising from automobiles owned, leased, hired or 
borrowed on behalf of the Contractor. General liability coverage can be provided in the form 
of an endorsement to the Contractor’s existing insurance policies, provided such 
endorsement is at least as broad as ISO Form CG 20 10, 11 85 or both CG 20 10 and CG 
23 37, if later revisions are used or the equivalent of such endorsements. 
b. 
For any claims related to this Equipment, the Contractor’s insurance coverage shall be 
primary insurance with respect to the City, its officers, officials, employees, and volunteers. 
Any insurance or self-insurance maintained by the City, its officers, officials, employees or 
volunteers shall be in excess of the Contractor’s insurance and shall not contribute with it.

7 
01/28/2025 
c.
Each insurance policy required by this Section shall provide that coverage shall not be 
canceled, except after providing notice to the City. 
7.4 
Acceptability of Insurers.  Insurance is to be placed with insurers with a current A.M. Best rating of 
no less than A-: VII, unless the Contractor has obtained prior approval from the City stating that a 
non-conforming insurer is acceptable to the City. 
7.5 
Waiver of Subrogation.  Contractor hereby agrees to waive its rights of subrogation which any 
insurer may acquire from Contractor by virtue of the payment of any loss. Contractor agrees to 
obtain any endorsement that may be necessary to affect this waiver of subrogation. The Workers’ 
Compensation Policy shall be endorsed with a waiver of subrogation in favor of the City for all work 
performed by the Contractor, its employees, agent(s) and subcontractor(s). 
7.6 
Verification of Coverage.  Within fifteen (15) days of the Effective Date of this Agreement, 
Contractor shall furnish the City with original certificates and amendatory endorsements, or copies 
of any applicable insurance language making the coverage required by this Agreement are effective. 
All certificates and endorsements must be received and approved by the City before work 
commences. Failure to obtain, submit or secure the City’s approval of the required insurance policies, 
certificates or endorsements prior to the City’s agreement that work may commence shall not waive 
the Contractor’s obligations to obtain and verify insurance coverage as otherwise provided in this 
Section. The City reserves the right to require complete, certified copies of all required insurance 
policies, including any endorsements or amendments, or their equivalent required by this Agreement 
at any time during the Term stated herein. 
Contractor’s failure to obtain, submit or secure the City’s approval of the required insurance policies, 
certificates or endorsements shall not be considered a Force Majeure or defense for any failure by 
the Contractor to comply with the terms and conditions of the Agreement, including any schedule 
for building or delivering the equipment in accordance with the SOW. 
7.7 
Subcontractors.  Contractor shall require and shall verify that all subcontractors maintain insurance 
meeting all requirements of this Agreement. 
7.8  
Special Risk or Circumstances.  The City reserves the right to request a modification of these 
insurance requirements, including any limits of coverage, based on the nature of the risk, prior 
experience, insurer, coverage or other circumstances unique to the Contractor, the SOW or the 
insurer by providing thirty (30) days prior written notice and subject to the Contractor’s mutual 
written approval of such modification, which such approval shall not be unreasonably withheld.  Any 
failure of the Contractor to agree to such modification shall not be considered a waiver of any rights 
or recovery available or owed to the City under this Agreement. 
 
8. 
E-verify, Records, and Audits.  
a. 
Immigration compliance.  To the extent applicable under A.R.S. § 41-4401, the Contractor warrants 
their compliance and that of its subcontractors with all federal immigration laws and regulations that relate to 
their employees and compliance with the E-verify requirements under A.R.S. § 23-214(A). The Contractor or 
subcontractor’s breach of this warranty shall be deemed a material breach of the Agreement and may result 
in the termination of the Agreement by the City under the terms of this Agreement. The City retains the legal 
right to randomly inspect the papers and records of the other party to ensure that the other party is complying 
with the above-mentioned warranty. The Contractor and subcontractor warrant to keep their respective 
papers and records open for random inspection during normal business hours by the other party. The parties 
shall cooperate with the City’s random inspections, including granting the inspecting party entry rights onto

8 
01/28/2025 
their respective properties to perform the random inspections and waiving their respective rights to keep such 
papers and records confidential. 
b. 
Contractor must preserve the records related to this Agreement for six (6) years after completion of 
the SOW. The City or its authorized agent reserves the right to inspect any records related to the performance 
of work specified herein at reasonable times. 
 
c. 
The parties agree that documents and records developed, generated, exchanged, maintained, or 
retained related to this Agreement will be subject to public inspection and disclosure to comply with Arizona 
public records laws (A.R.S. §39-121 et seq.) unless they are determined to be confidential or sensitive or 
contain proprietary or trade secrets as defined by the Arizona Trade Secrets Act by an administrative or 
governmental body or court of competent jurisdiction. 
9.  
No Boycott of Israel.  To the extent A.R.S § 35-393 through § 35-393.03 are applicable, the parties hereby 
certify that they are not currently engaged in, and agree for the duration of the Agreement to not engage in, a 
boycott of goods or services from Israel, as that term is defined in A.R.S § 35-393. 
10. 
Uyghur Forced Labor Prevention Act (UFLPA). Contractor certifies that it does not currently, and during 
the term of this Agreement, will not use: 
a.  
the forced labor of ethnic Uyghurs in the People’s Republic of China;  
b.
any goods or services produced by the forced labor of ethnic Uyghurs in the People’s 
Republic of China; and  
c. 
any contractors, subcontractors or suppliers that use the forced labor or any goods or 
services produced by the forced labor of ethnic Uyghurs in the People’s Republic of China. 
11. 
INTENTIONALLY OMITTED.  
12. 
Notices. 
12.1 
A notice, request or other communication that is required or permitted under this Agreement (each 
a “Notice”) will be effective only if: 
a. 
The Notice is in writing; and 
b. 
Delivered in person or by overnight courier service (delivery charges prepaid), certified or 
registered mail (return receipt requested). 
c. 
Notice will be deemed to have been delivered to the person to whom it is addressed as of 
the date of receipt, if: 
(1) 
Received on a business day before 5:00 p.m. at the address for Notices identified 
for the Party in this Agreement by U.S. Mail, hand delivery, or overnight courier 
service; or 
(2) 
As of the next business day after receipt, if received after 5:00 p.m. 
d. 
The burden of proof of the place and time of delivery is upon the Party giving the Notice. 
e. 
Digitalized signatures and copies of signatures will have the same effect as original signatures. 
12.2 
Representatives. 
a. 
Contractor.  Contractor’s representative (the “Contractor’s Representative”) authorized to 
act on Contractor’s behalf with respect to the Agreement, and his or her address for Notice 
delivery is: 
Badger Meter Inc.
Attn: Legal Department 
4545 W.  Brown Deer Road 
 
Milwaukee, WI 53223

9 
01/28/2025 
b. 
City.  City’s representative (“City’s Representative”) authorized to act on City’s behalf, and 
his or her address for Notice delivery is: 
Ron Serio, Water Services Director 
 
City of Glendale 
 
7070 W Northern Avenue 
 
Glendale, AZ  85303 
With required copy to:
City Manager 
City Attorney 
City of Glendale 
City of Glendale 
5850 West Glendale Avenue 
5850 West Glendale Avenue 
Glendale, Arizona  85301 
Glendale, Arizona  85301 
c. 
Concurrent Notices. 
(1) 
All notices to City’s representative must be given concurrently to City Manager and 
City Attorney. 
(2) 
A notice will not be deemed to have been received by City’s representative until the 
time that it has also been received by the City Manager and the City Attorney. 
(3) 
City may appoint one or more designees for the purpose of receiving notice by 
delivery of a written notice to Contractor identifying the designee(s) and their 
respective addresses for notices. 
d. 
Changes.  Contractor or City may change its representative or information on Notice, by 
giving Notice of the change in accordance with this section at least ten days prior to the 
change. 
13. 
Entire Agreement; Survival; Counterparts; Signatures. 
13.1 
Integration.  This Agreement contains, except as stated below, the entire agreement between City 
and Contractor and supersedes all prior conversations and negotiations between the parties regarding 
the Equipment, the Services or this Agreement. 
a. 
Neither Party has made any representations, warranties, waivers or agreements as to any 
matters concerning the Agreement’s subject matter. 
b. 
Representations, statements, conditions, waivers, or warranties not contained in this 
Agreement will not be binding on the parties. 
c. 
The solicitation, any addendums and the response submitted by the Contractor are 
incorporated into this Agreement as if attached hereto. Any Contractor response modifies 
the original solicitation as stated. Inconsistencies between the solicitation, any addendums 
and the response or any excerpts attached as Exhibit A and this Agreement will be resolved 
by the terms and conditions stated in this Agreement.  
13.2 
Interpretation. 
a. 
The parties fairly negotiated the Agreement’s provisions to the extent they believed necessary 
and with the legal representation they deemed appropriate. 
b. 
The parties are of equal bargaining position and this Agreement must be construed equally 
between the parties without consideration of which of the parties may have drafted this 
Agreement. 
c. 
The Agreement will be governed by and interpreted in accordance with the laws of the State 
of Arizona. Venue for any disputes arising under this Agreement shall be Maricopa County, 
Arizona.

10 
01/28/2025 
13.3
Survival. Except as specifically provided otherwise in this Agreement, each warranty, representation, 
indemnification and hold harmless provision, insurance requirement, and every other right, remedy 
and responsibility of a Party, will survive completion of the Equipment, or the earlier termination of 
this Agreement. 
13.4 
Amendment.  No amendment to this Agreement will be binding unless in writing and executed by 
the parties. Electronic signature blocks do not constitute execution for purposes of this Agreement. 
Any amendment may be subject to City Council approval. 
13.5 
Remedies.  All rights and remedies provided in this Agreement are cumulative and the exercise of 
any one or more right or remedy will not affect any other rights or remedies under this Agreement 
or applicable law. 
13.6 
Severability.  If any provision of this Agreement is voided or found unenforceable, that determination 
will not affect the validity of the other provisions, and the voided or unenforceable provision will be 
reformed to conform with applicable law. 
13.7 
Counterparts.  This Agreement may be executed in counterparts, and all counterparts will together 
comprise one instrument. 
13.8 
Assignment.  This Agreement may not be assigned, either in whole or in part, without first receiving 
the City’s written consent. Any attempted assignment, either in whole or in part, without such consent 
will be null and void and in such event the City will have the right, at its option, to terminate the 
Agreement. 
13.9 
Binding Effect. This Agreement will be binding upon and inure to the benefit of the parties and 
their respective permitted successors and assigns.13.10 
Use of City Name or Trademark.  
Nothing in this Agreement gives the Contractor any right to use the name, logo, trademark, 
copyrighted materials or similar identifying features of the City of Glendale in any advertising or 
publicity without obtaining the prior written consent of the City. 
14. 
Term.  
The term of this Agreement commences upon the Effective Date and continues until all Equipment is 
installed and accepted by the City and all Services are performed to the City’s satisfaction, or for a three (3) 
year period beginning on the Effective Date of this Agreement, whichever is shorter. In the event all tasks 
required by the SOW, including the installation of the Equipment and performance of all Services has not 
been completed before the Term expires, the parties may agree in writing to up to three (3) six-month 
extensions (a total of 18 months) to complete the work in the SOW.   For purposes of the Agreement 
“accepted” means the Contractor has delivered and properly installed the Equipment and all Services have 
been provided and implemented in accordance with the SOW.  
15. 
Liquidated Damages. 
 
The City, in its sole unreviewable discretion,  may assess liquidated damages in the amount of $1,000 per day 
per violation for any failure by the Contractor to:  (i)  install the Equipment in compliance with the schedule 
contained in the SOW; (ii)fail or refuse to provide the Services contracted for under this Agreement or 
perform them in compliance with the SOW; or (iii) meet any other material provision of the SOW that 
prevents the Equipment from being fully functional by the agreed upon Project Completion Date.   Nothing 
in this provision, however, waives any right the City may have to seek any other damages or remedies available 
to it under this Agreement, including any damages or remedies for a breach of warranty that may be provided 
in Section 2.2 above, the SOV or the SOW.  
16. 
Dispute Resolution.   
a. 
Any controversy or claim arising out of or relating to this contract, or the breach thereof, shall be 
settled by arbitration administered according to the American Arbitration Association’s Commercial 
Arbitration Rules, and judgment on the award rendered by the arbitrator may be entered in any court having 
jurisdiction thereof.

11 
01/28/2025 
b.
Contractor agrees that during the pendency of any dispute between the parties, Contractor will 
continue to perform its obligations until the dispute is settled, instructed to cease performance by the City, 
enjoined or prohibited by judicial action, or otherwise required or obligated to cease performance by other 
provisions in this Agreement.  
17. 
Cooperative Use of Contract.   This agreement may be extended for use by other governmental agencies 
and political subdivisions of the State upon the Contractor’s mutual written agreement.  Any such usage by 
other entities must be in accord with the ordinances, charter, rules and regulations of the respective entity and 
the approval of the Contractor and City.  For a list of SAVE members, click on the following link: 
http://www.mesaaz.gov/business/purchasing/save
18. 
Exhibits.  The following exhibits, with reference to the term in which they are first referenced, are 
incorporated by this reference. 
Exhibit A 
Schedule of Values 
Exhibit B 
Scope of Work 
Exhibit C 
Manufacturer’s Equipment Warranties 
Exhibit D 
RFP Response Workbook 
 
(The remainder of this page left blank intentionally. Signatures appear on the following page.)

12 
01/28/2025 
The parties enter into this Agreement effective as of the date shown above.
City of Glendale, 
an Arizona municipal corporation 
____________________________________
ATTEST: 
Julie K. Bower 
(SEAL) 
City Clerk 
APPROVED AS TO FORM: 
Michael D. Bailey 
City Attorney 
Badger Meter, Inc., 
a Wisconsin corporation 
____________________________________
By:  
Its:

EXHIBIT A
Equipment Purchase Agreement 
SCHEDULE OF VALUES 
 
 
     .

ITEM
BMI Description
Unit
QUANTITY 
PER CONTRACT
TOTAL UNIT PRICE
 IN CONTRACT - 
EXCL TAX
ORIGINAL TOTAL 
EXT PRICE IN 
CONTRACT EXCL 
TAX
TOTAL EXT PRICE IN 
CONTRACT EXCL TAX 
- w/ Change Orders
RADAR Service Units
Unit
QUANTITY 
PER CONTRACT
TOTAL UNIT PRICE
 IN CONTRACT - 
EXCL TAX
ORIGINAL TOTAL 
EXT PRICE IN 
CONTRACT EXCL 
TAX
TOTAL EXT PRICE IN 
CONTRACT EXCL TAX 
- w/ Change Orders
1
RADAR STD ACOUSTICS SERV UNIT - Year 1
EA
0
15.00
$  
   
-
$  
   
-
$  
   
2
RADAR STD ACOUSTICS SERV UNIT - Year 2
EA
0
15.00
$  
   
-
$  
   
-
$  
   
3
RADAR STD ACOUSTICS SERV UNIT - Year 3
EA
0
15.00
$  
   
-
$  
   
-
$  
   
4
RADAR STD ACOUSTICS SERV UNIT - Year 4
EA
0
15.23
$  
   
-
$  
   
-
$  
   
5
RADAR STD ACOUSTICS SERV UNIT - Year 5
EA
0
15.45
$  
   
-
$  
   
-
$  
   
6
RADAR STD ACOUSTICS SERV UNIT - Year 6
EA
0
15.69
$  
   
-
$  
   
-
$  
   
7
RADAR STD ACOUSTICS SERV UNIT - Year 7
EA
0
15.92
$  
   
-
$  
   
-
$  
   
8
RADAR STD ACOUSTICS SERV UNIT - Year 8
EA
0
16.16
$  
   
-
$  
   
-
$  
   
9
RADAR STD ACOUSTICS SERV UNIT - Year 9
EA
0
16.40
$  
   
-
$  
   
-
$  
   
10
RADAR STD ACOUSTICS SERV UNIT - Year 10
EA
0
16.65
$  
   
-
$  
   
-
$  
   
11
RADAR STD ACOUSTICS SERV UNIT - Year 11
EA
0
16.90
$  
   
-
$  
   
-
$  
   
12
RADAR STD ACOUSTICS SERV UNIT - Year 12
EA
0
17.15
$  
   
-
$  
   
-
$  
   
13
RADAR STD ACOUSTICS SERV UNIT - Year 13
EA
0
17.41
$  
   
-
$  
   
-
$  
   
14
RADAR STD ACOUSTICS SERV UNIT - Year 14
EA
0
17.67
$  
   
-
$  
   
-
$  
   
15
RADAR STD ACOUSTICS SERV UNIT - Year 15
EA
0
17.93
$  
   
-
$  
   
-
$  
   
16
RADAR STD ACOUSTICS SERV UNIT - Year 16
EA
0
18.20
$  
   
-
$  
   
-
$  
   
17
RADAR STD ACOUSTICS SERV UNIT - Year 17
EA
0
18.48
$  
   
-
$  
   
-
$  
   
18
RADAR STD ACOUSTICS SERV UNIT - Year 18
EA
0
18.75
$  
   
-
$  
   
-
$  
   
19
RADAR STD ACOUSTICS SERV UNIT - Year 19
EA
0
19.03
$  
   
-
$  
   
-
$  
   
20
RADAR STD ACOUSTICS SERV UNIT - Year 20
EA
0
19.32
$  
   
-
$  
   
-
$  
   
SIM Leak Detection Service Units
21
SIM LEAK DECTECTION 500BM SERV UNIT - Year 1
EA
0
15.00
$  
   
-
$  
   
-
$  
   
22
SIM LEAK DECTECTION 500BM SERV UNIT - Year 2
EA
0
15.00
$  
   
-
$  
   
-
$  
   
23
SIM LEAK DECTECTION 500BM SERV UNIT - Year 3
EA
0
15.00
$  
   
-
$  
   
-
$  
   
24
SIM LEAK DECTECTION 500BM SERV UNIT - Year 4
EA
0
15.23
$  
   
-
$  
   
-
$  
   
25
SIM LEAK DECTECTION 500BM SERV UNIT - Year 5
EA
0
15.45
$  
   
-
$  
   
-
$  
   
26
SIM LEAK DECTECTION 500BM SERV UNIT - Year 6
EA
0
15.69
$  
   
-
$  
   
-
$  
   
27
SIM LEAK DECTECTION 500BM SERV UNIT - Year 7
EA
0
15.92
$  
   
-
$  
   
-
$  
   
28
SIM LEAK DECTECTION 500BM SERV UNIT - Year 8
EA
0
16.16
$  
   
-
$  
   
-
$  
   
29
SIM LEAK DECTECTION 500BM SERV UNIT - Year 9
EA
0
16.40
$  
   
-
$  
   
-
$  
   
30
SIM LEAK DECTECTION 500BM SERV UNIT - Year 10
EA
0
16.65
$  
   
-
$  
   
-
$  
   
31
SIM LEAK DECTECTION 500BM SERV UNIT - Year 11
EA
0
16.90
$  
   
-
$  
   
-
$  
   
32
SIM LEAK DECTECTION 500BM SERV UNIT - Year 12
EA
0
17.15
$  
   
-
$  
   
-
$  
   
33
SIM LEAK DECTECTION 500BM SERV UNIT - Year 13
EA
0
17.41
$  
   
-
$  
   
-
$  
   
Page  of

ITEM
BMI Description
Unit
QUANTITY 
PER CONTRACT
TOTAL UNIT PRICE
 IN CONTRACT - 
EXCL TAX
ORIGINAL TOTAL 
EXT PRICE IN 
CONTRACT EXCL 
TAX
TOTAL EXT PRICE IN 
CONTRACT EXCL TAX 
- w/ Change Orders
34
SIM LEAK DECTECTION 500BM SERV UNIT - Year 14
EA
0
17.67
$  
   
-
$  
   
-
$  
   
35
SIM LEAK DECTECTION 500BM SERV UNIT - Year 15
EA
0
17.93
$  
   
-
$  
   
-
$  
   
36
SIM LEAK DECTECTION 500BM SERV UNIT - Year 16
EA
0
18.20
$  
   
-
$  
   
-
$  
   
37
SIM LEAK DECTECTION 500BM SERV UNIT - Year 17
EA
0
18.48
$  
   
-
$  
   
-
$  
   
38
SIM LEAK DECTECTION 500BM SERV UNIT - Year 18
EA
0
18.75
$  
   
-
$  
   
-
$  
   
39
SIM LEAK DECTECTION 500BM SERV UNIT - Year 19
EA
0
19.03
$  
   
-
$  
   
-
$  
   
40
SIM LEAK DECTECTION 500BM SERV UNIT - Year 20
EA
0
19.32
$  
   
-
$  
   
-
$  
   
Page  of

14 
01/28/2025 
EXHIBIT B
Equipment Purchase Agreement 
SCOPE OF WORK

15 
01/28/2025 
EXHIBIT C
Equipment Purchase Agreement 
Manufacturer’s Equipment Warranties

Warranty and Additional Exclusions 
Each unit, software and service is provided subject to the warranty terms in the Badger Meter 
Terms and Conditions of Sale, along with the applicable terms and limitations therein, which is 
available at: 
 as well as the additional 
conditions and exclusions listed below. 
All Syrinix
units are to be installed in accordance with the technical 
installation documentation and other guidance separately provided. An electronic copy of 
applicable operating and installation documentation will be made available via the RADAR 
platform. 
Please note that this proposal does not include the provision of any of the following by 
 unless expressly agreed otherwise in writing: 
site access and preparation including any connection, valves and tappings required for 
the connection of each unit; 
field work including unit preparation, connection, testing and operation unless agreed 
otherwise in writing; 
local duties and taxes; 
all applicable/required permits, licenses and analogous fees; 
civil, structural, architectural and design work of any kind; 
interconnections, pipes, valves and fittings which are not part of the supplied 
equipment; all testing and system verifications other than to 
 standards; 
painting or special finishes; and 
all items not specifically listed. 
Battery life is exempt from the product warranty but if used in areas of good signal and in 
accordance with our standard operating instructions will deliver the battery life between 
charges as indicated. 
Any warranty claims must be made by contacting 
 to obtain a return 
authorization and then returning the unit back 
responsibility to cover the costs of the return carriage. 
 reserves 
the right to charge for costs incurred where any fault is a result of a breach by the user. 
Please note that this warranty does not cover: 
any excluded matter detailed above, communications interruptions due to third party 
intervention and/or failure including but not limited to communications network provider, 
unauthorized access and/or tampering or other form of interference, whether related to 
hardware, communications and/or software; 
failures interruptions and damage resulting directly or indirectly from Acts of God, war, 
terrorism, civil, disobedience, theft, extreme weather, floods, storms, lightning, tornado, 
hurricane, fire, combustion, explosion, landslip, volcano and earthquake, extreme 
temperature, external electrical irregularity including surge and failure, acoustic 
interference, 
damage from water borne materials, corrosion from unanticipated liquids and materials 
and external electromagnetic interference and all and any external events analogous to 
any of the above; 
theft, vandalism, or other damaging acts whether intentional or accidental; 
battery failure beyond that level of warranty provided by the manufacturer (please see 
above) 
Page 42 of 55

installation, commissioning, use and/or removal (temporary or permanent), tampering, 
and unapproved opening;
intentional or accidental abuse, interference, misuse or neglect of the hardware failures 
resulting from the negligence to perform preventative maintenance
damages or defects in the product which are caused by initial start-up, repairs or 
attempted repairs performed by anyone other than a 
 authorized service 
provider 
installation guidance;
unavailability of GPS or communications networks;
customer in default of any payment obligations to 
;
abuse by abnormal system conditions including but not limited to temperature, chemical 
or debris;
goods that have been improperly stored by owner or its representative prior to 
installation and start-up;
equipment/programming which has been revised or altered by others.
The information provided in this document is confidential and should not be 
reproduced, used or disclosed in any way, without the prior written consent of 
.
Page 43 of 55

16 
01/28/2025 
EXHIBIT D
Equipment Purchase Agreement 
RFP Response Workbook

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
1.1
Water Meters
Design
Meters shall comply with the lead-free requirements as defined in NSF/ANSI 61 and NSF/ANSI 
372 and by the 2014 provisions of the Safe Drinking Water Act which defines lead-free as not 
more than a weighted average of 0.25% lead when used with respect to the wetted surfaces 
of pipes, pipe fittings, plumbing fittings, and fixtures.
Must Have
Yes
1.2
Water Meters
Design
All Meters shall have cast on them, in raised characters, the meter size and direction of flow 
through the meter.
Must Have
Yes
1.3
Water Meters
Design
All Meters shall have the manufacturer's serial numbers stamped on the meter main case and 
on top of the reading lid.
Must Have
Yes
1.4
Water Meters
Registers
The registers shall provide for visual register reading at the meter and encoded data for use 
by advanced metering systems.
Must Have
Yes
1.5
Water Meters
Registers
The register shall be straight reading type with test and low flow indicators and shall be 
constructed to register in  gallons.
Must Have
Yes
1.6
Water Meters
Registers
All register electronics and/or reduction gearing shall be contained in a hermetically sealed, 
tamper proof enclosure constructed of corrosion-resistant material and shall be secured to 
the upper main case by means of a locking device or integrated into the maincase.  
Must Have
Yes
1.7
Water Meters
Registers
The register box and reading lid must be constructed of bronze or suitable engineered plastic.  
The register lens shall be constructed of high-impact tempered glass
Must Have
Yes
1.8
Water Meters
Registers
The register shall encode a minimum of 9-meter registration digits configured based on the 
meter size. 
Must Have
Yes
1.9
Water Meters
Design - Registers
Registers shall offer support for remote programming of alarm and meter configurations 
through the Endpoint via 2-way communication. 
Desired
No
Although our registers do not support remote programming of alarms and meter 
configurations, consumption based alarms using "Events" can be configured in BEACON 
without the need to program the encoder.
"Events" empowers users to proactively monitor their data by setting system thresholds, 
selecting which data to monitor, and establishing conditions for each event type. While 
BEACON monitors the incoming data in real-time, it can quickly identify anomalies and act 
by sending notifications to the right personnel. This includes not only user-defined flow 
and endpoint communication events, but also temperature and pressure events when 
using our E-Series G2 Ultrasonic meters. The ability to monitor flow, communication, water 
temperature and water pressure events lets utilities immediately confirm customer-
reported issues. Such monitoring can eliminate the need for unnecessary truck rolls. By 
leveraging these capabilities, utility operations can be improved by identifying and 
addressing issues before customers notice them and/or become larger problems.
1.10
Water Meters
Design - Registers
The register shall support localized interval data history storage and retrieval for all available 
measurements (consumption, temperature, pressure, etc.), with configurable interval periods 
down to 5 minutes or less and a minimum storage capacity of 288 consecutive intervals. 
Desired
No
To protect against data loss, the system has multiple levels of redundancy. As a standard, 
the ORION Cellular endpoint can store up to 42 days of 15-minute interval data, equating 
to 4,032 data points which can be extracted at the meter, if needed. Moreover, BEACON 
provides the ability to access the past three years of 15-minute data from all endpoints in 
the system. Interval data, alarms, events, and diagnostic information is stored in BEACON.
While localized data extraction can be performed, our standard interval for all 
measurements is 15 minutes. 
1.11
Water Meters
Design - Registers
The register shall provide configurable alarms for leak, broken pipe, reverse flow, and tamper 
conditions. 
Must Have
No
Using the PCU, alarms can be turned on or off. While thresholds for alerts are factory set 
and not configurable, the pressure and temperature limits in our E-Series Ultrasonic meters 
do allow for configurable thresholds. Additionally, the customer can reconfigure the 
duration for which alarms will last and how long they are sent to BEACON, with the 
exception of the leak alarm, which clears automatically. Importantly, our BEACON software 
enhances this capability by providing the City with customizable alerts for these critical 
conditions through “Events”. This flexibility empowers the City to respond promptly and 
effectively to any potential issues.
1.12
Water Meters
Design - Meter Height
5/8"x3/4", 3/4" and 1" meters shall not exceed 4" from centerline to top of register. 
Must Have
Yes
1.13
Water Meters
Registers
Encoder registers shall have a minimum battery life of twenty years.
Must Have
Yes
1.14
Water Meters
Design
Meters shall be maintenance free and contain no internal moving parts.
Must Have
Yes
1.15
Water Meters
Design
All nuts, washers, and bolts in meter and on meter body shall be stainless steel.
Must Have
Yes
1.16
Water Meters
Headloss
Meters shall not exceed a maximum allowable pressure loss of 10 pounds per square inch at 
the safe maximum operating capacity for a given meter size. 
Must Have
Yes
1.17
Water Meters
Accuracy
Meters shall be able to sense and indicate reverse flow. 
Must Have
Yes
1.18
Water Meters
Pressure Capacity
Meters shall operate properly under a continuous working pressure of 150 pounds per square 
inch (psi) without leakage or damage to any meter components. 
Must Have
Yes
1.19
Water Meters
Design - Registers
Ultrasonic meters shall have an electronic register with LCD display and shall be capable of 
meeting the register features described in this section. Electronic registers shall be factory 
sealed. The Owner will not accept any register filled with oil or any substance intended to 
prevent moisture intrusion
Must Have
Yes
1.20
Water Meters
Design - Registers
Registers shall be capable of being located within a pit (underground) environment and 
perform accurately in hot temperatures and submerged in water. 
Must Have
Yes
1.21
Water Meters
Design - Registers
 Battery life remaining shall be displayed on the register.
Desired
Yes
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)
1.22
Water Meters
Connectors
Encoded registers shall be compatible with Itron inline connector or Nicor connector and shall 
be supplied with a 5’ wire. The connector type will be determined by the chosen AMI vendor.  
Field splicing of wires as the standard installation method is not acceptable. 
Desired
Yes
1.23
Water Meters
Design - Registers
Register shall clearly differentiate the billing read (1000 gallons) and the raw read (1/10 
gallon).
Must Have
Yes
1.24
Water Meters
Design - Registers
Register dial numbers shall be easily distinguishable in low light environment from at least 5 
feet away.
Desired
Yes
1.25
Water Meters
Design - Registers
Reads shall still be obtainable on-site in the event of the LCD screen failing or battery failure.
Desired
No
In the event the battery fails, data will be unretrievable. If the LCD fails, data can be 
retrieved locally.
1.26
Water Meters
Design - Registers
The register lens shall resist breakage and scoring under normal conditions.
Must Have
Yes
1.27
Water Meters
Design - Registers
The register/encoder programmer shall be capable of applying the same settings across 
multiple registers/encoders without requiring re-entry of the settings.
Desired
Yes
Our E-Series Ultrasonic meters can come factory programmed without the need for 
programming to be performed in the field.
1.28
Water Meters
Design - Registers
Register shall use high resolution ASCII encoder protocol.
Must Have
Yes
1.29
Water Meters
Design - Registers
Register shall be non-removable from the meter  and must have a lid that covers/protects the 
register display.
Desired
Yes
1.30
Water Meters
Advanced Features
Meter shall optionally be able to record and relay temperature and pressure measurements.
Strongly Desired
Yes
1.31
Water Meters
Advanced Features
The meter shall provide configurable thresholds for temperature and pressure high/low 
alarms.
Strongly Desired
Yes
1.32
Water Meters
Design-Lay Length
Meters shall be available in common lay lengths as indicated in AWWA Standard  C715-18.
Must Have
Yes
1.33
Water Meters
Operating Characteristics
The meter shall offer empty pipe alarms
Desired
Yes
1.34
Water Meters
Proposal Requirements
All complete operating and parts manuals shall be furnished upon delivery at no additional 
cost to the Owner. Manuals and other materials shall show all meter specifications and 
mechanical troubleshooting in paper and electronic media. 
Must Have
Yes
1.35
Water Meters
Shut-Off Valves
Remotely actuated shutoff valves shall be optionally integrated with the meter and support 
on-demand state changes and confirmation via Endpoint communications. Valve states shall 
include open, closed, and reduced flow.
Nice To Have
No
As a separate option from the standard E-Series Ultrasonic meter, Badger Meter also offers 
the  E-Series Ultrasonic Plus with Integrated Valve. The valve features three positions: 
open, partially closed, and restricted. While not intended to provide a complete shut-off, 
the E-Series Ultrasonic Plus with Integrated Valve allows utilities to restrict water flow to a 
minimum of 0.125 gpm for humanitarian reasons. Additionally, the valve actuation can 
either be scheduled for a specific date in the future or during the next communication 
cycle.
1.36
Water Meters
Type
Meters shall be solid state, battery operated meters with electronics in a totally encapsulated, 
waterproof housing. Meter and register shall be a single unit with no moving parts in the flow 
path, however, meters with removable and replaceable electronics are allowable.
Must Have
Yes
1.37
Water Meters
Design
The meters external casing shall be constructed of composite plastic, lead-free bronze alloy or 
stainless-steel enclosure, which permanently houses the meter elements. Flow tubes shall be 
constructed of lead-free bronze or stainless-steel.  
Must Have
Yes
1.38
Water Meters
Operating Capacity
Meters shall have the capability to operate under flow conditions as specified in AWWA 
Standard  C715-18
Must Have
Yes
1.39
Water Meters
Operating Characteristics
Main case connections for 1-1/2” and 2” meters must have standard ANSI integral flanges 
cast into the meter casing or swivel with elliptical flange and have a bolt pattern with enough 
clearance for bolts to be inserted from opposite side of meter. 
Must Have
Yes
1.40
Water Meters
Accuracy
Meters sizes 5/8", 5/8" x 3/4", 3/4", and 1" shall meet or exceed current AWWA  C715-18 
(R22) new meter low, normal, and high flow new meter accuracy standards for a minimum 
period of twenty years from the date of manufacture. 
Must Have
Yes
1.41
Water Meters
Accuracy
Meters sizes starting at 1-1/2" and larger shall meet or exceed current AWWA  C715-18 (R22) 
new meter low, normal, and high flow new meter accuracy standards for a minimum period 
of ten years from the date of manufacture. 
Must Have
Yes
1.42
Water Meters
Environmental tolerances 
Water Meters shall operate over a temperature range of at least -30º F to 140º F, and a 
humidity range of at least 0% to 100% non-condensing.
Must Have
Yes

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement (Yes / 
No)
Comments
2.1
Non-Metallic Meter Covers
General
Meter covers shall be non-metallic, black in color, and constructed of high-impact, no break 
polymer or composite plastic. 
Must Have
Yes
2.2
Non-Metallic Meter Covers
General
Meter covers shall be field locatable through use of a metal detector.
Desired
Yes
DFW uses a magnent for locating molded in the lids- no 
metal attachment
2.3
Non-Metallic Meter Covers
General
Meter covers shall fit within the existing City of Glendale meter boxes without the need for 
meter box replacement or modifications. 
Must Have
Yes
City of Glendale has installed DFW lids- We have all sizes
2.4
Non-Metallic Meter Covers
Duty Rating - Regular Duty
Regular Duty meter covers in areas not expected to be exposed to vehicular traffic shall be 
rated to withstand at least a 20,000-pound load, plus impact, as measured via testing in 
accordance with paragraph 6.1 of AASHTO M306 without any damage of permanent 
deformation in excess of 1/8". 
Must Have
Yes
All materials quoted from DFW meet AASHTO H20 
standards, not M306. Per Addendum 5 the City will accept 
H20 20k load testing standards.
2.5
Non-Metallic Meter Covers
Duty Rating - Traffic Rated
Traffic Rated meter covers in areas exposed to vehicular traffic shall be rated to withstand at 
least a 40,000-pound load, plus impact, as measured via testing in accordance with 
paragraph 6.1 of AASHTO M306 without any damage of permanent deformation in excess of 
1/8". 
Must Have
Yes
Per the City in Addendum 5, AASHTO H20 is acceptable. For 
larger high traffic rated cover needs, further evaluation will 
be needed.  YES, DFW MEETS THE H-20 REQUIREMENT 
ALLOWED IN ADDENDUM 5.  
2.6
Non-Metallic Meter Covers
Size and Geometry
The specified meter covers shall come in sizes compatible with the City's existing water meter 
boxes
Must Have
Yes
Glendale MAG/Tucson sizes. Glendale has used DFW 
products in City
2.7
Non-Metallic Meter Covers
Design
The cover shall withstand a temperature range of -40-degree F to 190-degree F and shall be 
resistant to ultraviolet light degradation, corrosion, and be unaffected by rain or 
condensation, frost-proof, and compatible with rugged service and long life. 
Must Have
Yes
There is no standardized test for tempature variation.  See 
attached local references of Cities near Glendale that see 
the most extreme of the AZ weather.
2.8
Non-Metallic Meter Covers
Design
The cover shall have a slip-resistant surface having a molded tread pattern for skid resistance. Must Have
Yes
DFW has molded thread pattern and has minnimum 
coefficeint friction of 0.50 to exceed testing requirements of 
Western Underground 3.6
2.9
Non-Metallic Meter Covers
Design
As required for the proposed endpoints, each cover shall be furnished with a recess and a 
hole to accommodate the selected AMI transmitter OR shall optionally be available with 
mounting brackets to facilitate under-the-cover installation of an endpoint. 
Must Have
Yes
DFW has mold inserts for all meter manufactures, different 
depths, and sizes according manufactures size for ADA, to 
sit flush with top of lid
2.10
Non-Metallic Meter Covers
Design
Meter covers shall be designed to prevent being easily displaced or from floating during rain 
events through integrated weighting or another appropriate mechanism. 
Must Have
Yes
DFW has anti float blended material with min relative 
density of 1.10 according to ASTM d792-08 test methods. 
Does not include metal for weight
2.11
Non-Metallic Meter Covers
Design
Each cover shall have molded in its superior part of its body the words "Water Meter" The 
words shall be legible and shall be molded permanently in the body of the Lid. 
Desired
Yes
DFW has "Water Meter" molded on the lids and can do 
custom city logo at no additional charge
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
3.1
AMI Endpoints
Backfilling Reads 
AMI system shall recover and retransmit missing reads from each endpoint to backfill 
missing interval data on a daily basis. 
Must Have
Yes
3.2
AMI Endpoints
Batteries
The expected battery life of Endpoints shall be at least twenty (20) years. The Owner 
expects Endpoint low battery alarms to be fully warranted prior to failure. 
Must Have
Yes
3.3
AMI Endpoints
Batteries
The Endpoint shall alert when the battery is reaching end-of-life. 
Desired
Yes
3.4
AMI Endpoints
Data transmission accuracy and 
security 
AMI system shall include provisions to ensure immunity from outside (electromagnetic) 
interference as well as fading and other forms of signal degeneration or attenuation (such 
as multi-path fading), to prevent accidental loss or interception of customer or meter 
reading data. 
Must Have
Yes
3.5
AMI Endpoints
Environmental tolerance 
Endpoints must operate in conditions subject to indefinite water submergence (i.e., meter 
vaults). 
Must Have
Yes
Being submerged in water will affect signal propagation 
which will affect any RF transmitting device. If installed 
outdoors, the ORION Cellular endpoints must be 
installed through RF-friendly lids, per the ORION Water 
Endpoint Installation Manual, to optimize signal 
propagation and endpoint performance. Per the ORION 
Water Endpoint Installation Manual, ORION Cellular 
endpoints must be installed through RF-friendly lids to 
optimize signal propagation and endpoint performance. 
Beyond the endpoint mounting, the equipment is 
suitable for submerging in water.
3.6
AMI Endpoints
Environmental tolerance 
Endpoint enclosure should be composed of UV-inhibiting ABS or similar material. All 
materials used in the Endpoint must be non-hazardous.
Must Have
Yes
3.7
AMI Endpoints
Environmental tolerance 
Ruggedized connection cables shall be available for installations that require extra 
protection from rodents or physical damage. 
Must Have
Yes
To enhance durability and match the ruggedness of our 
products, all component wires can be fitted with rodent 
prevention sleeves, safeguarding against potential 
damage from insects, rodents, and other wildlife.
3.8
AMI Endpoints
Hydrant Meter
Endpoints shall be compatible with temporary hydrant meters. 
Must Have
Yes
3.9
AMI Endpoints
ID Number
Each Endpoint shall have a unique, permanent ID number that is transmitted with the meter 
readings. 
Must Have
Yes
3.10
AMI Endpoints
Extended Protocols
Endpoints must be capable of accepting extended protocols for meter level alarms and over 
the air register communication.
Must Have
Yes
Please see our compatibility statement available in our 
Product Data Sheet or Installation Manual.
3.11
AMI Endpoints
Labeling
Endpoints shall be permanently labeled with manufacturer’s name, model number, owner 
name (Glendale), a tamper warning, Endpoint identification number, required FCC labeling, 
input/output connections, and date of manufacture. 
Must Have
No
The ORION Cellular endpoints are permanently labeled 
with the following information:
   Endpoint manufacturer and model
   Numeric serial number
   Barcoded serial number
   Federal Communications Commission (FCC) ID
When wired to a Badger Meter encoder, the encoder 
contains the following information:
    Manufacturer’s name
    Meter model
    Unit of measure
    Date of manufacture
Further physical labeling of other attribute would not be 
available on the product. Note that attributes such as 
tamper warnings and date of manufacture are readily 
available in BEACON.
3.12
AMI Endpoints
Labeling
Endpoints shall be labeled with a bar code of the Endpoint identification number.  The label 
shall be weatherproof and attached to the Endpoint where normal installation will not 
obscure it.
Must Have
Yes
3.13
AMI Endpoints
Leak detection - Mains
AMI system shall provide acoustic or pressure based distribution system leak detection and 
to transmit this data via the data collector network to the control computer. 
Strongly Desired
Yes
Badger Meter offers a variety of different pressure and 
acoustic sensors using the very same cellular network as 
the AMI.
3.14
AMI Endpoints
Meter Interface Unit (Endpoint) Endpoints must be available in versions that work in water meter vaults as well as inside 
buildings. 
Must Have
Yes
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)
3.15
AMI Endpoints
Meter Reading Intervals
Changes to meter reading and Endpoint transmission intervals shall be able to be  
configured to reset automatically after a given time period.  
Nice To Have
No
The ORION Cellular has a standard of 15-minute 
intervals with a transmission rate of four times per 
weekday and once per weekend day. Three of these 
weekday transmissions are configurable by the City to 
support business processes. These transmissions do not 
automatically reset after a given time period but can be 
reset manually at any given time.
This would include the entire fleet of endpoints and are 
unable to change the transmissions times for individual 
endpoints.
3.16
AMI Endpoints
Endpoints for different meter 
types and installation 
circumstances  
The proposed Endpoint model shall accommodate different meter register manufacturers. 
Must Have
Yes
3.17
AMI Endpoints
Multiple meters/registers 
Endpoints shall optionally provide multiple ports to handle dual-register meters or ancillary 
devices
Desired
No
The ORION endpoint does not include dual port 
endpoint connections, but two endpoints can be 
connected when two encoders are used.
3.18
AMI Endpoints
Number of digits 
Endpoint shall transmit the same number of digits provided by the encoder register with no 
truncation of data. 
Must Have
Yes
3.19
AMI Endpoints
Other detection features
AMI endpoint shall report reverse flow alarms from the meter.
Must Have
Yes
3.20
AMI Endpoints
Other detection features
AMI system shall have the ability to accept other detection parameters from the meter, 
such as pressure and temperature, and to transmit this via the data collector network to the 
control computer. 
Desired
Yes
3.21
AMI Endpoints
Other detection features
AMI shall provide interface units that connect to third party sensors (including but not 
limited to water quality, temperature, pressure) through common interfaces such as 4-20 
ma or MODBUS such that data are transmitted via the data collector network to the head-
end.
Nice To Have
Yes
Badger Meter offers Telog recording telemetry units 
that enable the transmission of data from third party 
sensors through a common backhaul device to Badger 
Meter Software.  These units are designed to collect 
data from various sensors by recording its data 
interface.  Telog supports multiple data interfaces, 
including Analog (4-20mA, 0-5 vdc), Digital 
(Pulse/Relay), Encoder, or Modbus
3.22
AMI Endpoints
Pit Set Endpoints
Pit-set Endpoints shall meet performance requirements using an under-lid or through lid 
installation with composite pit and vault lids
Must Have
Yes
3.23
AMI Endpoints
Programmability
The Endpoint shall be able to be initialized or programmed during or prior to field 
installation. 
Strongly Desired
Yes
ORION Cellular endpoints are pre-configured in the 
factory to recognize the device they are connected to 
and do not require field programming.
3.24
AMI Endpoints
Programmability
The system shall be capable of over the air reprogramming of an Endpoint.  This 
functionality should allow for all functions available via a programming handheld as well as 
firmware upgrade.
Desired
Yes
3.25
AMI Endpoints
Programmability
Firmware updates shall be possible both over the air and in the field.
Must Have
Yes
3.26
AMI Endpoints
Programmability
AMI Endpoints shall be capable of being read via walk-by and drive-by devices in the event 
of network issues, without the need for the mobile collector to have internet access. 
Must Have
Yes
In the rare event the cellular communications network 
fails the ORION Cellular endpoint is capable of 
transmitting a mobile RF message to support a walk-by 
method of collection.
3.27
AMI Endpoints
Programmability
Meter reading and Endpoint transmission intervals shall be configurable through remote 
electronic communication with the Endpoint (including via two-way). 
Desired
Yes
The ORION Cellular endpoint offers two-way 
communication, however the endpoint collects as a 
standard 15-minute intervals. The transmission of the 
data is configurable for three of the four communication 
call-ins per weekday.
3.28
AMI Endpoints
Tamper detection 
The system shall provide tamper detection capability which, when the meter, Endpoint or 
any wiring between components has been tampered with, shall cause a tamper message to 
be immediately transmitted to the AMI software.  
Must Have
Yes
3.29
AMI Endpoints
Water Proofing
Endpoints shall be provided in waterproof casing rates IP8 or better (submersion up to 1 
meter of depth) in accordance with IP code, IEC standard 60529. 
Must Have
Yes
Assumes that the writer intended to list IP68.

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)
3.30
AMI Endpoints
Meter Reading Intervals
Endpoints shall provide for at least hourly interval meters reads.
Must Have
Yes
3.31
AMI Endpoints
Meter Reading Intervals
Endpoints shall provide for 15-minute interval data. 
Nice To Have
Yes
3.32
AMI Endpoints
Meter Reading Intervals
The Endpoint shall support localized interval data history storage and retrieval for all 
available measurements, with a minimum storage capacity of thirty-five (35) consecutive 
days of hourly interval data. Describe the retrieval process.
Must Have
Yes
Using the Product Configuration Utility (PCU) software, 
an infrared (IR) communication cable and Windows 
tablet/laptop/handheld localized data retrieval is 
available. Connect the IR communication device to the 
endpoint, the the troubleshooting process can begin.
3.33
AMI Endpoints
Public Relations
The Endpoint shall NOT transmit any personally identifiable information. 
Must Have
Yes
3.34
AMI Endpoints
RF Operation
The utility shall have the ability to configure priority-mode communications on individual 
Endpoints. 
Desired
No
The system provides for immediate notification when 
high-priority system exceptions occur, based on the 
utility’s identification of the high-priority exceptions in 
BEACON, however, these notifications are for the entire 
population of endpoints. Once programmed in BEACON, 
when a high-priority status exception is reported to an 
ORION Cellular endpoint, an immediate off-schedule 
transmission from that endpoint will be triggered. This 
enables prompt notification of the condition to the 
utility so that corrective action may be taken 
immediately, thereby removing any latency of a 
standard radio transmission. For example, this 
functionality is available for endpoint reported 
conditions such as endpoint tamper (cut-wire) and 
encoder communication error as well as for meter-
reported conditions such as meter exceeding max flow.
3.35
AMI Endpoints
Environmental tolerances 
AMI endpoints shall operate over a temperature range of at least -30º F to 140º F, and a 
humidity range of at least 0% to 100% non-condensing.
Must Have
Yes

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
4.1
Data Collection System
Backhaul
Collectors shall have the capability for redundant backhaul with automatic switchover.
Must Have
Not Applicable 
Badger Meter's AMI solution leverages the current cellular 
infrastructure 
4.2
Data Collection System
Backhaul
The AMI system shall be able to use Fiber backhaul for primary and cellular backhaul for 
secondary.  
Desired
Not Applicable 
Badger Meter's AMI solution leverages the current cellular 
infrastructure 
4.3
Data Collection System
Data Persistence
The Respondent's proposed hardware shall retain minimum of 30 days of data in event the 
collector loses backhaul connectivity. 
Must Have
Yes
Badger Meter's Cellular Orion end point retains 42 days of data 
4.4
Data Collection System
Batteries
The AMI system shall have battery backup for all data collector components. 
Must Have
Yes
4.5
Data Collection System
Communication to control 
computer 
Collectors shall have multiple network connectors including  fiber optic, wireless 
broadband/cellular, and ethernet. 
Must Have
Not Applicable 
Badger Meter's AMI solution leverages the current cellular 
infrastructure 
4.6
Data Collection System
Data transmission accuracy and 
security 
AMI system shall provide full end to end encryption at a minimum of AES-128 for all data 
communicated between the Endpoint and data collectors, and the data collectors and the 
system head-end. AMI Vendor to provide specific information about encryption methods 
utilized, including encryption levels and standards.
Must Have
Yes
4.7
Data Collection System
Data transmission accuracy and 
security 
The AMI system shall provide the ability to disable and enable encryption when required to 
support system maintenance and troubleshooting. 
Desired
Not Applicable 
Maintence and troubleshooting of the NaaS(Cellular AMI) is 
included in Badger Meter's offering 
4.8
Data Collection System
Data transmission accuracy and 
security 
Owner shall retain ownership of all system data and have full access to it at any and all times 
to utilize or export to third parties as they see fit, even in a hosted environment.
Must Have
Yes
4.9
Data Collection System
Electrical Isolation  
Data collector system equipment shall be electrically isolated to protect against power surges 
or lightning strikes. 
Must Have
Not Applicable 
Badger Meter's AMI solution leverages the current cellular 
infrastructure that has multiple layers of redundancy to protect 
against power surges and lightning strikes 
4.10
Data Collection System
Environmental tolerances 
Data Collection Equipment shall operate over a temperature range of at least -30º F to 140º 
F, and a humidity range of at least 0% to 100% non-condensing.
Must Have
Yes
4.11
Data Collection System
FCC compliance
All applicable AMI system components must comply with FCC regulations 47CFR §15 
(regulations regarding unlicensed transmissions).
Must Have
Yes
4.12
Data Collection System
Intrusion Alarms
Proposed solution must support real-time flags for intrusion at AMI collector equipment sites. 
This may include, but is not limited to, door open alarms and data access alarms.
Must Have
Yes
4.13
Data Collection System
Endpoint Coverage
The data collection network shall provide 100% coverage of all Endpoints with at least 1 
collector.
Must Have
Yes
4.14
Data Collection System
Physical Data Interfaces
System shall provide password protected access to any physical data interfaces on the 
equipment itself, shall be required along with documentation on updating and maintaining 
the user access.
Desired
Yes
4.15
Data Collection System
Programming
Collectors shall be capable of interfacing with Owner's laptops for troubleshooting and 
maintenance.  Additionally, collectors must have a method for local interface that allows 
download of data in the event of a backhaul failure.
Must Have
Not Applicable 
Badger Meter's AMI solution leverages the current cellular 
infrastructure 
4.16
Data Collection System
Read Success Rate
Proposed solution shall consist of a sufficient number of data collectors and repeaters to 
obtain at least one meter register reading within a three-day interval from at least 99.5% of 
all meters on which the system is installed, to obtain at least one read per day from at least 
99% of meters on which the system is installed, and to obtain at least 99% of all readings 
taken hourly or at more frequent intervals, unless there are temporary physical barriers 
beyond the control of the Owner or the Proposer. 
Must Have
Yes
4.17
Data Collection System
Redundancy
The data collection network shall maintain at least a 2:1 coverage redundancy on no less than 
100% of all endpoints. 
Must Have
Not Applicable 
Badger Meter's AMI solution leverages the current cellular 
infrastructure 
4.18
Data Collection System
Protecting Data
The system shall have a method that allows collectors to detect unauthorized access and 
send an alert to head-end system.
Must Have
Yes
4.19
Data Collection System
Stored data system integrity 
and security
The system shall have the capability to prevent loss of stored meter reading and meter alarm 
data. 
Must Have
Yes
4.20
Data Collection System
Time Synchronization
The proposed system shall support automatic Endpoint clock synchronization with Collectors 
and the Head End System. Time synchronization of all elements in an AMI system is required, 
which here means that the internal clocks on all devices shall be in synch to the single second 
or better. 
Must Have
Yes
4.21
Data Collection System
Time Synchronization
Time sync configurations shall be set before or when equipment is installed in the field.
Desired
Yes
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
5.1
Portable Interrogation, Field 
Programming and Testing 
Devices  
Functions/modes of operation  The unit shall be capable of reading and downloading data from the Endpoints. 
Strongly Desired
Yes
5.2
Portable Interrogation, Field 
Programming and Testing 
Devices  
Design - Registers
The programmer for meter register and encoder shall be ruggedized (able to stand up to field 
environment and drops)
Desired
Yes
5.3
Portable Interrogation, Field 
Programming and Testing 
Devices  
Functions/modes of operation  
The unit shall be capable of programming the Endpoint with any information required for 
operation and not pre-programmed at the factory. It shall be capable of providing 
instructions to the Endpoint concerning the make, model and data protocol of the meter 
being connected, should the Endpoint not be able to determine this itself. 
Strongly Desired
Yes
5.4
Portable Interrogation, Field 
Programming and Testing 
Devices  
Functions/modes of operation  The handheld unit shall be able to program a programmable meter register. 
Must Have
Yes
5.5
Portable Interrogation, Field 
Programming and Testing 
Devices  
Mobile Meter Reading
System shall be capable of reading meters in both walk-by or mobile drive-by mode. 
Must Have
Yes
Cellular-based AMI systems provide greater reliability 
than is available in both mobile and traditional data-
collector based radio frequency (RF) systems. Thus, there 
is limited, if any, need for mobile backup. In the event the 
utility requires a mobile backup read, the use of a 
handheld meter reading device can be utilized for mobile 
reading purposes. Mobile reads would be completed by 
having a meter reader walk by the location of the ORION 
Cellular unit and gather the required endpoint reading to 
be loaded into BEACON.
5.6
Portable Interrogation, Field 
Programming and Testing 
Devices  
Bar code reader
The unit shall contain an integral optical character reader or other device or function to 
capture meter and Endpoint numbers from bar codes or other machine readable information 
contained attached to the units.
Strongly Desired
Yes
5.7
Portable Interrogation, Field 
Programming and Testing 
Devices  
Data Loss Prevention
All units must ensure against accidental data loss in case of a dead battery.
Must Have
Yes
5.8
Portable Interrogation, Field 
Programming and Testing 
Devices  
Encryption
Handheld shall have the ability to temporarily disable encryption on the endpoint if required 
for maintenance without intervention from the head end for maintenance and configuration. Nice To Have
Yes
Badger Meter offers several handheld device options for 
troubleshooting and mobile data collection for back-up 
capabilities.
Additionally, the Badger Meter IR Communication Device 
can be used to activate or inactivate the endpoint, verify 
encoder connection, and confirm network 
communication. This device can be used as a standalone 
tool, or connected with the Product Configuration Utility 
software via a handheld, tablet, or laptop.
5.9
Portable Interrogation, Field 
Programming and Testing 
Devices  
Functions/modes of operation  The unit shall remotely be able to locate and diagnose problems with a meter register or 
Endpoint unless the system incorporates an alternate way to make such diagnoses. 
Strongly Desired
Yes
5.10
Portable Interrogation, Field 
Programming and Testing 
Devices  
Functions/modes of operation  The unit shall be able to ascertain the condition or remaining life of the battery in an 
Endpoint and the water meter register.
Strongly Desired
Yes
5.11
Portable Interrogation, Field 
Programming and Testing 
Devices  
Functions/modes of operation  The programming/installation field tool shall provide immediate feedback of Endpoint 
programming success and signal strength to the network.
Must Have
Yes
5.12
Portable Interrogation, Field 
Programming and Testing 
Devices  
Mobile Solution
Field applications shall be made available in Android, iOS, or Windows compatible installers 
for use with the utility's own hardware.
Desired
Yes
5.13
Portable Interrogation, Field 
Programming and Testing 
Devices  
Mobile Solution
Programming field tools shall support cellular and/or wireless connectivity.
Desired
Yes
5.14
Portable Interrogation, Field 
Programming and Testing 
Devices  
Off-Line Operations
The field programmer shall be able to perform all functions without the need to be connected 
to the internet. 
Strongly Desired
Yes
5.15
Portable Interrogation, Field 
Programming and Testing 
Devices  
Data Export
The field tool shall retain a log or have the capability to export programming and read history 
in a common format. 
Strongly Desired
Yes
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
6.1
AMI System Software
General
Any Proposer-supplied, on-premise database used to store and manage meter readings 
must be a non-proprietary and SQL-compliant
Must Have
Not applicable
Our BEACON software is a cloud-based Software as a Service.
6.2
AMI System Software
General
The AMI system shall provide direct linking to system data to support the export of data via 
either ODBC database connections or API connections.  
Must Have
Yes
6.3
AMI System Software
General
The Respondent shall maintain and provide a detailed data dictionary and the full database 
schema to the Owner.
Must Have
Yes
6.4
AMI System Software
General
The AMI system shall provide reports which detail all past and current two-way commands 
including the user who initiated them, date stamps, their success rates, and data responses. Must Have
Yes
6.5
AMI System Software
General
Report formats shall be user-customizable with full access to all tables and fields, using a 
built-in report writer or a third-party commercially available report writer that is included 
with the control computer software. Reports must be able to be directed to a printer, 
screen or locally accessible data file.  The control computer software should enable users to 
do ad hoc queries.  
Desired
Yes
6.6
AMI System Software
General
The system shall maintain log files of application events (errors, warnings, etc.) including file 
processing stats and scheduled events. These logs must be accessible and searchable via 
the system interface. 
Must Have
Yes
6.7
AMI System Software
General
AMI system shall allow user defined, multi-faceted role-based security levels for activities 
within the system. Example: (Division Assignment + Role = permission/access) 
Must Have
Yes
6.8
AMI System Software
General
System shall have the ability to enforce security by Active Directory (AD) group 
memberships and support Single Sign-On across all applications. 
Must Have
Yes
6.9
AMI System Software
Software-as-a-Service
Proposer shall maintain redundant and geographically dispersed data centers such as to 
provide a backup site.
Must Have
Yes
6.10
AMI System Software
General
Vendor shall represent and warrant that the software, as delivered to the Owner, does not 
contain any program code, virus, worm, trap door, back door, timer, or clock that would 
erase data or programming or otherwise cause the software to become inoperable, 
inaccessible, or incapable of being used in accordance with its user manuals, either 
automatically, upon the occurrence of Licensor-selected conditions, or manually on the 
command of a person.
Must Have
Yes
6.11
AMI System Software
Software-as-a-Service
Hosted services includes off-site backups and a restore/recovery process in cases where a 
data center outage is for an extended time.  
Must Have
Yes
6.12
AMI System Software
Software-as-a-Service
Hosted environments must be a Tier 1 Data center, maintain high availability architecture 
and achieve at least 99.9% application uptime. 
Must Have
Yes
6.13
AMI System Software
Software-as-a-Service
Hosted environment compliant with SOC Type II.  Independent audit report must be 
available upon request.
Must Have
Yes
6.14
AMI System Software
Software-as-a-Service
Hosting environment is certified to ISO 27001 and NIST 800-53
Must Have
Yes
6.15
AMI System Software
MDMS
The City requires that users in the Meter Data Management System be able to identify a 
group of meters and customers from a map (by drawing a polygon or box) and output 
consumption / metering data in a table format that can be exported to Excel.
Strongly Desired
Yes
6.16
AMI System Software
General
The AMI HES and/or the MDMS shall allow users to subscribe to emailed reports of all (or 
specifically targeted) device alarms over user-defined periods (daily, weekly, monthly).
Strongly Desired
Yes
6.17
AMI System Software
General
A user-programmable scheduler agent shall be available to perform scripted actions related 
to program operations and integrations.
Must Have
Yes
6.18
AMI System Software
Head End
The Headend software shall allow for access to all system data via database connection or 
APIs. 
Must Have
Yes
6.19
AMI System Software
Head End
The Head End system shall supply basic functionality for Endpoint management, alarm 
management, two-way firmware upgrades and commands, network monitoring, and API-
based data integration.
Must Have
Yes
6.20
AMI System Software
Head End
The AMI Solution Head End must have sufficient data processing performance to support 
hourly interval meter reading data updated multiple times per day from 100,000 water 
meters
Must Have
Yes
6.21
AMI System Software
Head End
The AMI Solution Head End must have sufficient data processing performance to support 
every 15 minute handling of 15 minute meter reading data from 100,000 water meters
Strongly Desired
Yes
6.22
AMI System Software
Head End
The AMI Solution Head End must have sufficient data storage to support 3 years worth of 
hourly interval meter reading data from 100,000 water meters
Must Have
Yes
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)
6.23
AMI System Software
Head End
The Head End system shall supply map visualizations to help the AMI system administer/ 
manage system performance and visualize alarms and notifications. Minimum requirements 
are to see on a map:
Map data shall be exportable.  
Must Have
Yes
6.24
AMI System Software
Head End
The software shall provide the user with reports of the current status and reading history of 
individual accounts and selectable groups of accounts. 
Must Have
Yes
6.25
AMI System Software
Head End
The software shall allow endpoints to be assigned to group en-mass or via an upload 
process, in addition to adding endpoints to a group individually. 
Desired
Yes
6.26
AMI System Software
Head End
The software shall be able to sort and list accounts and their meter reading data, and to 
provide configurable sorting and filtering. 
Must Have
Yes
6.27
AMI System Software
Head End
The AMI Solution shall manage the associated AMI network equipment providing 
configurable reports on system status, health, throughput, and connectivity though all 
levels of the network
Must Have
Yes
ORION Cellular NaaS eliminates many of the traditional fixed network 
operating expenses such as infrastructure, or the need for designing, 
permitting, installing, maintaining, troubleshooting, and supporting a 
separate telecommunications network. Our ORION Cellular NaaS includes 
endpoints that collect and transmit new 15-minute interval readings four 
times per weekday and once per weekend day directly to cellular carriers' 
communication towers into BEACON.
6.28
AMI System Software
Head End
The Head End system shall provide a performance dashboard that can be configured to 
display key system metrics including but not limited to overall register read success rates, 
individual daily register read success rates, overall interval read success, and average data 
collector redundancy.  
Must Have
Yes
6.29
AMI System Software
Head End
The AMI Solution shall have the capability for a utility user to enable proactive alerts  
regarding system status, system health and other important system admin concerns.
Must Have
Yes
6.30
AMI System Software
Head End
Software shall (1) operate the control computer that interacts with other AMI system 
components to obtain meter readings and perform all over the air communication (2) 
manage the database of meter readings and other information, and (3) interface to the 
Owners' and other information systems. These applications may be integrated or separate.
Must Have
Yes
6.31
AMI System Software
Head End
Time reported is configurable to report in local time in all software interfaces.  Vendor is 
responsible for time conversion to local time.
Must Have
Yes
6.32
AMI System Software
Head End
The AMI system shall be capable of relaying data from acoustic leak sensors through the 
AMI network, and making it available for analysis and export via the user interface. 
Strongly Desired
Yes
Badger Meter offers acoustic leak detection devices that use the same 
cellular network as the ORION Cellular NaaS solution which would be 
made available for analysis and export of data.
6.33
AMI System Software
Head End
The Headend shall provide an aggregated view of all parameters that have been 
programmed into Endpoint, Register, and any other connected devices, with filtering 
options to easily search for and export all devices sharing a common parameter (i.e.- alarm 
thresholds, reading dials, resolution, etc.). 
Must Have
Yes
6.34
AMI System Software
MDMS
The MDMS software shall provide a complete set of APIs for use accessing system data and 
implementing integrations. 
Must Have
Yes
6.35
AMI System Software
MDMS
The MDMS software shall allow for, at minimum, read-only access to all databases. The 
Respondent shall provide updated database schemas for all software, both at time of 
deployment and after each update.  
Must Have
No
We do not allow direct access to the databases in our cloud-platform.
6.36
AMI System Software
MDMS
The AMI system shall provide leak alerts which indicate if there is an abnormal increase in 
water consumption, if there is no time interval (e.g., at night) when the rate of consumption 
is zero, or if there is a “running continuously” condition. Leak alert thresholds shall be 
configurable.   
Must Have
Yes
6.37
AMI System Software
MDMS
The MDMS shall supply basic functionality for reading data validation and editing, reporting 
on alarms/reads/exceptions, delivery of billable reads to CIS, and long-term storage of all 
reading and alarm data received from the Head End.
Must Have
Yes
6.38
AMI System Software
MDMS
The MDMS shall indicate when there is an extended period of no flow through the meter, 
or an unusually low consumption over a regular reading interval and be able to provide a list 
of daily, weekly, or monthly alarms via email to select users.
Must Have
Yes

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)
6.39
AMI System Software
MDMS
The MDMS shall allow meters to be grouped into multiple different user-configurable 
groups by the user for meter reading and data analysis. Examples of groups include routes, 
customer types, billing cycle, pressure districts, and geographic areas.   Grouping must be 
able to managed in the User Interface, including adding and removing meters from the 
group. The software shall allow endpoints to be assigned to group en-mass or via an upload 
process, in addition to adding endpoints to a group individually. 
Must Have
Yes
6.40
AMI System Software
MDMS
The MDMS shall provide the ability to create a Virtual Meter from a grouping of meters. 
Virtual Meters shall sum the consumption for a grouping of meters and present the total 
consumption in a report for each interval period. 
Must Have
Yes
Virtual meters is on the development roadmap.
6.41
AMI System Software
MDMS
Virtual Meters must be able to be managed in the User Interface, including adding and 
removing meters from the group. Meter shall be able to be assigned to multiple virtual 
meters. The software shall allow endpoints to be assigned to virtual meters groups en-mass 
or via an upload process, in addition to adding endpoints to a virtual meter group 
individually.  
Must Have
No
Virtual meters is on the development roadmap.
6.42
AMI System Software
MDMS
The MDMS shall provide geographic, non-revenue dashboards that compare water 
production from SCADA against aggregated consumption from meter groups. 
Desired
Yes
This is supported through BEACON's DMA feature. 
6.43
AMI System Software
MDMS
The MDMS shall display other detection parameters gathered by the meter, including 
temperature and pressure. 
Strongly Desired
Yes
6.44
AMI System Software
MDMS
The MDMS shall flag and report any unauthorized usage, if the customer account record 
indicates that service has been shut off.
Must Have
Yes
6.45
AMI System Software
MDMS
The MDMS shall display an aggregated view of all alarms received from devices, with 
detailed history available for individual devices. The view(s) shall clearly differentiate 
between active vs. historical alarms, and provide filtering and export options.
Must Have
Yes
6.46
AMI System Software
MDMS
The MDMS shall receive updated data from the Head End at the following minimum 
frequencies: general alarms = 1 hour, critical alarms = immediate, reading data = twice per 
day
Must Have
Yes
6.47
AMI System Software
MDMS
Validation and estimation processes in the MDMS shall function regardless of data import 
method.
Must Have
Yes
6.48
AMI System Software
MDMS
The MDMS shall allow the option of applying multipliers to read values for display, 
reporting, and export purposes. The system must support individual multipliers for each 
meter record.
Must Have
No
6.49
AMI System Software
MDMS
Software shall identify accounts where usage violates temporary restrictions (e.g., apparent 
outdoor irrigation usage during non-allowed times or days)
Must Have
Yes
6.50
AMI System Software
MDMS
MDMS shall identify irrigation usage from consumption patterns and time of use. 
Desired
Yes
6.51
AMI System Software
Installation Management 
System 
Installation Management System must contain information about the meter exchange 
including photographs. 
Must Have
Work Order Management system contains information such as photos, 
account ID, location, etc. See Schedule of Work submission for 
screenshots and additional details
6.52
AMI System Software
Installation Management 
System 
Installation Management System must have a meter inventory management capabilities 
which includes assignment of inventory in different statuses (in stock, quarantined, etc.) 
and which must be accessible by Owner. 
Must Have
Proposal includes digital inventory management sofware that shall serve 
as centralized and realtime tracking tool for products. Utilizes barcode 
scanning and interfaces with WOMS
6.53
AMI System Software
Installation Management 
System 
Installation Management System must have a configurable installation workflow such that 
installers are guided with a prescribed installation procedure including photos and data to 
be captured during the install
Must Have
Yes, this is a basic capability of the proposed WOMS. See Schedule of 
Work for more information. 
6.54
AMI System Software
Installation Management 
System 
Installation Management System must have the ability to status install with configurable 
statuses (installed, escalated to utility, meter/service repair, etc.)
Must Have
Yes, this is a basic capability of the proposed WOMS. 
6.55
AMI System Software
Installation Management 
System 
Installation Management System must have the capability for reporting or data exports on 
the status of installation work
Must Have
Yes, this is a basic capability of the proposed WOMS. 
6.56
AMI System Software
Installation Management 
System 
Installation Management System must have the capability to confirm customer 
communications have been sent before the install is scheduled
Desired
Traditional mailed notifications will be sent and managed per RFP. Mailer 
will contain QR code. All mailed accounts will be contained on 
documented list with completed mailing dates.
6.57
AMI System Software
Customer Portal
Vendor shall provide a customer portal that displays interval usage information. 
Must Have
Yes
6.58
AMI System Software
Customer Portal
Customer portal shall display usage information from the MDM after information has gone 
through VEE Processing (measurements). 
Desired
Yes
Data doesn’t go through a VEE process.
6.59
AMI System Software
Customer Portal
Customer portal shall support single sign on for City staff.
Desired
Yes
6.60
AMI System Software
Customer Portal
The Customer Portal shall have different interfaces for the utility user and the end customer 
user.  A utility user must be able to view the end customer view in the event they must 
provide phone support to the end customer. 
Must Have
Yes
6.61
AMI System Software
Customer Portal
End Customer interface must be compatible with commonly available devices, browsers, 
and operating systems that a customer could use for the lifetime of the system. 
Must Have
Yes
6.62
AMI System Software
Customer Portal
The End Customer user interface must be available for use on mobile devices, whether on a 
mobile browser or separate application. 
Must Have
Yes
6.63
AMI System Software
Customer Portal
The End Customer must be able to receive notifications through the Customer Portal 
system, text and email.
Must Have
Yes

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)
6.64
AMI System Software
Customer Portal
Portal shall provide customer-configurable threshold alerts based on meter consumption 
data, notifying customers when they have exceeded their usage threshold. 
Must Have
Yes
6.65
AMI System Software
Customer Portal
End Customer accounts must be able to have access to more than one meter under one 
account.
Must Have
Yes
6.66
AMI System Software
Customer Portal
End Customer must be able to have access to more than one account under a single portal 
user name.
Must Have
Yes
6.67
AMI System Software
Customer Portal
Customer portal shall be designed to be compliant with American with Disabilities Act web 
accessibility guidelines and to meet the most current standards from the World Wide Web 
Consortium's (W3C) Web Content Accessibility Guidelines (WCAG). Section 508
Must Have
Yes
ADA guidelines are leveraged in updates to the BEACON consumer portal. 
The VertexOne Digital Suite currently adheres to the Web Content 
Accessibility Guidelines 2.2, Level AA.
6.68
AMI System Software
Customer Portal
Customer portal shall have the capability to provide End Customer with notifications of high 
and unusual patterns of water consumption.
Must Have
Yes
This is also supported with the optional VertexOne offering.
6.69
AMI System Software
Customer Portal
Customer portal shall alert customer via phone or text message of a suspected pipe burst. 
Strongly Desired
Yes
A leak alrert can be configured aleting the customer of unusal water flow 
which could be from a pipe burst. This is also supported with the optional 
VertexOne offering.
6.70
AMI System Software
Customer Portal
Customer portal should provide water saving tips and tools to the End Customers, as 
applicable based on customer usage consumption pattern and promotion of water saving 
devices, etc.
Must Have
Yes
Badger Meter partilly complies with this requirement on the basis of 
availability of affordability programs- but Badger Meter does not support 
enrollment into these programs. 
6.71
AMI System Software
Customer Portal
Customer portal shall be able to direct End Customer to water conservation and efficiency 
programs available at City of Glendale or through third party
Strongly Desired
Yes
6.72
AMI System Software
Customer Portal
Customer portal shall be able to direct End Customer to availability and enrollment to 
specific customer affordability programs.
Strongly Desired
Yes
6.73
AMI System Software
Customer Portal
Customer Portal shall provide End Customer the ability to set communication preference, 
such as viewing information in English and Spanish
Must Have
Yes
6.74
AMI System Software
Customer Portal
Customer Portal shall provide the End Customer the ability to prepare printable consumer 
water consumption reports that compares consumption to other customer groups (similar 
to energy consumption reports).
Must Have
Yes
Supported by optional VertexOne offering.
6.75
AMI System Software
Customer Portal
Customer portal shall allow End Customer to make, modify, reschedule, or cancel online 
payments or automatic payments.
Must Have
Yes
Supported by optional VertexOne offering.
6.76
AMI System Software
Customer Portal
Customer portal shall integrate with third-party payment applications.
Must Have
Yes
EyeOnWater can provide a link to your payment provider but does not 
display bills directly. VertexOne currently has a pre-built integrations to 
provide a seamless customer experience with your payment vendor, 
Paymentus. With this integration, customers can make payments directly 
from the VertexOne application.  With Paymentus, VertexOne leverages a 
fully integrated iFrame. Customers can pay through the Paymentus iFrame 
without ever leaving the VertexOne Digital portal.
VertexOne solutions can further integrate with any third-party payment 
solution capable of mapping to the VertexOne APIs.
6.77
AMI System Software
Customer Portal
Customer portal shall integrate with Paymentus for on-line payment processing functions. 
Must Have
Yes
Please see the response to requirement 6.76, above. VertexOne has an 
official partnership with Paymentus. There are approximately 40 live 
clients leveraging the VertexOne / Paymentus integrated solution.
6.78
AMI System Software
Customer Portal
Customer portal shall provide customizable online audit for customers to self-diagnose high 
water consumption.
Must Have
Yes
Supported by optional VertexOne offering.
6.79
AMI System Software
Customer Portal
Customer portal shall provide customers with analytics for understanding contributing 
factors for high water consumption including detailed water consumption insights.
Must Have
Yes
Supported by optional VertexOne offering.
6.80
AMI System Software
Customer Portal
Customer portal shall provide end user ability to compare two or more billing periods.
Must Have
Yes
6.81
AMI System Software
Customer Portal
Customer portal shall provide end user ability to forecast or project future periods.
Must Have
Yes
Supported by optional VertexOne offering.
6.82
AMI System Software
Customer Portal
Portal must conform with design and style of corporate website and vendor must be able to 
update the design and style in accordance with the latest Owner branding and 
communication requirements.
Must Have
Yes
6.83
AMI System Software
Customer Portal
Customer portal must integrate with telephony and billing systems to enable customer to 
contact customer service representatives through 'Click to Chat', 'Click to Call' or similar 
links.
Strongly Desired
Yes
6.84
AMI System Software
Customer Portal
Customer portal must integrate with outage management systems and provide ability for 
real time information and visual outage reporting using data and ArcGIS maps.
Strongly Desired
Yes
6.85
AMI System Software
Customer Portal
Capability to enroll in notifications/alerts based  on communication preferences for no 
additional cost including: Bill threshold alerts, bill available, bill due in x days, bill paid 
including text, email.
Must Have
Yes
6.86
AMI System Software
Customer Portal
Ability for customers to initiate service orders via the customer portal. Service order to 
integrate with NorthStar CIS for processing.  
Strongly Desired
Yes

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)
6.87
AMI System Software
Customer Portal
Ability to conduct customer surveys. 
Desired
Yes
6.88
AMI System Software
Customer Portal
Ability to link to printable electronic copy of bill on the customer portal
Must Have
Yes
Supported by optional VertexOne offering.
6.89
AMI System Software
Customer Portal
Ability to have the bill message and newsletter available online via a customer portal. 
Must Have
Yes
Supported by optional VertexOne offering.
6.90
AMI System Software
Customer Portal
Portal provides the ability to request service, including service connections, transfers, 
disconnections, new customer move-in with deposit, etc. 
Must Have
Yes
Supported by optional VertexOne offering.
6.91
AMI System Software
Customer Portal
Portal to provide updated account information, including current balances, payment 
history, billable water usage, due dates, past due amounts, and shut off date, when 
applicable. 
Must Have
Yes
Supported by optional VertexOne offering.
6.92
AMI System Software
Customer Portal
Portal to provide ability to pay bill via credit card, debit card, and ACH. 
Must Have
Yes
Supported by optional VertexOne offering.
6.93
AMI System Software
Customer Portal
Portal to provide ability to pay bill via advanced payment methods such as Google Pay, 
Apply Pay, and Venmo
Desired
Yes
Supported by optional VertexOne offering.
6.94
AMI System Software
Customer Portal
Portal to provide links to a PDF renderings of the bill statement and any correspondence for 
customer to download or print.  
Must Have
Yes
Supported by optional VertexOne offering.
6.95
AMI System Software
Customer Portal
Portal provides ability to opt-in and opt-out of electronic billing, with an option to not 
receive a paper bill. CIS and corresponding bill printing processes are updated automatically 
based on changes made in the portal. 
Must Have
Yes
Supported by optional VertexOne offering.
6.96
AMI System Software
Customer Portal
Portal provides a way to customers to request a payment extensions and payment plans, 
based on eligibility rules. 
Must Have
Yes
Supported by optional VertexOne offering.
6.97
AMI System Software
Customer Portal
Portal provides customer the ability to enroll or unenroll from automatic payment debiting, 
either by credit card or bank account. 
Must Have
Yes
Supported by optional VertexOne offering.
6.98
AMI System Software
Customer Portal
Ability to modify existing payment options, such as changing a credit card.
Must Have
Yes
Supported by optional VertexOne offering.
6.99
AMI System Software
Customer Portal
Ability to notify users if autopayment methods have expired/no longer usable. Notification 
can happen through various communication channels.
Must Have
Yes
Supported by optional VertexOne offering.
6.100
AMI System Software
Customer Portal
 Ability to send alerts in the customer portal. Alerting in the customer portal could be used 
for new bill alert, or dunning.
Must Have
Yes
6.101
AMI System Software
Customer Portal
Portal should be flexible about hiding and displaying information tailored to Owner's needs. Must Have
Yes
Supported by optional VertexOne offering.
6.102
AMI System Software
Customer Portal
Customer portal shall display water consumption through interactive charts and graphs. 
Must Have
Yes
6.103
AMI System Software
Customer Portal
Customer portal shall be PCI Compliant
Must Have
Yes
6.104
AMI System Software
Customer Portal
Portal utilizes interval data to estimate water usage types - i.e. breakdown of water use, 
clothes washing, showing, etc. 
Desired
Yes
6.105
AMI System Software
Customer Portal
Capable of encouraging water conservation such as customers can compare usage to typical Strongly Desired
Yes
6.106
AMI System Software
Customer Portal
End Customer notification from the Customer Portal must include alerts that the Owner can 
push to all or targeted customers with specific attributes (e.g. consumption, location, 
payment timeliness). 
Must Have
Yes
Supported by optional VertexOne offering.
6.107
AMI System Software
Customer Portal
Portal allows the Owner to create a water budget based on each customer's household 
characteristics and to display a comparison of actual usage compared to the water budget. 
Strongly Desired
Yes
6.108
AMI System Software
Customer Portal
Portal can prompt customers to sign-up for water saving features when they sign-in to the 
portal. 
Desired
Yes
6.109
AMI System Software
Customer Portal
Portal can send a personalized customer sign-up link that does not require the customer to 
look-up their account number to enroll in the portal. 
Must Have
Yes
Supported by optional VertexOne offering.
6.110
AMI System Software
Customer Portal
Provide ability for customers to make account profile changes (email, phone,  etc.) and then 
pass these updates to the CIS
Must Have
Yes

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
7.1
System Integration
Integration
AMI head-end shall integrate with NorthStar CIS via standard and readily available APIs.
Must Have
Yes
7.2
System Integration
Integration
AMI head-end shall integrate with the Customer Portal via standard and readily available 
APIs. 
Must Have
Yes
BEACON and VertexOne solutions can both integrate with 
the Northstar CIS via readilly avialbale  APIs
7.3
System Integration
Integration
Customer portal shall integrate with Northstar CIS via standard and readily available APIs. 
Must Have
Yes
BEACON and VertexOne solutions can both integrate with 
the Northstar CIS via readilly avialbale  APIs
7.4
System Integration
Integration
The MDMS shall receive and return meter level inquiry and commands to support NorthStar 
CIS process integration for processes including but not limited to on-demand read, 
disconnect, and soft-disconnect.
Must Have
Yes
In the monitoring section of BEACON, users will be able to 
select individual accounts and create groups through 
filters, giving the City the capability to select a date range 
and interval of reads using the actions command and 
export feature to fulfill this requirement. Additionally, the 
ORION Cellular NaaS solution comes standard with four 
daily communications per day of 15-minute interval data. 
This means that the utility will always have fresh, sub-
daily reads to reference with customers and internal 
operations. Three of the daily communications are 
configurable and are typically scheduled every few hours 
during business hours. This access enables utilities to 
promptly detect and respond to irregularities or 
anomalies, ultimately, making the need for reactive on-
demand readings less critical.
As the City sets the call-in schedule for the ORION Cellular 
endpoints, BEACON can configure the system so that final 
and special reads completed during standard office hours 
are no more than six hours old, depending on the City’s 
configurable schedule.
7.5
System Integration
Integration
MDMS shall send billing meter reads to NorthStar CIS.
Must Have
Yes
7.6
System Integration
Integration
AMI head end shall send meter events, including but not limited to register-level alarms 
(leak, reverse flow, high flow, swapped meter, tamper, etc.) and endpoint events (low 
battery, meter communication failed, non-numeric read, meter read malfunction, etc.) to 
MDMS
Must Have
Yes
7.7
System Integration
Integration
AMI head-end and MDMS shall synchronize device information and master data with 
NorthStar CIS, including but not limited to meter and Endpoint information. 
Must Have
Yes
7.8
System Integration
APIs
AMI system software (including the headend, MDMS, and customer portal) shall integrate 
with NorthStar CIS and other applicable City information systems via standard and readily 
available APIs, which shall expose all pertinent AMI system data. 
Must Have
Yes
Yes. Addtionally, the optional VertexOne add-on provides 
standard APIs for each function enabled in their self-
service platform. VertexOne, optionally, can provide their 
iPaaS middleware layer to map / translate the VertexOne 
standard APIs to the available CIS APIs. VertexOne and 
the AMI system are fully integrated.
7.9
System Integration
Customer Account Information 
Update
As customer account information changes throughout each day in the NorthStar CIS, the 
relationships between the meter, register and MIU and associated information in the 
headend, MDMS, and Customer Portal need to stay in sync. This interface shall ensure that 
when billing reads, consumption analysis, or alarms are identified in the AMI software, they 
are associated to the correct customer and location. 
Must Have
Yes
Yes. Additonally, the optional VertexOne add on pulls 
Customer, Account and Billing data in real-time from the 
CIS via standard APIs and pulls AMI data through standard 
interfaces. Additionally, VertexOne updates thier  
VXsmart analytics data warehouse daily to ensure data 
currency for anlytics and reporting needs.
7.10
System Integration
Meter Read Request and 
Response
Interface shall be a two-way interface between the MDMS and Northstar to request and 
receive reads for billing.  
Must Have
Yes
7.11
System Integration
Meter Exchange Completed 
Workorder Data
Interface shall send the completed work order information back into the Northstar billing 
system to manage meter installation and change out work orders so the CIS is up-to-date 
after the work is completed. Interface shall contain all relevant information for the correct 
automated creation of the installed water meter, including but not limited to meter model 
and size information, read multipliers, meter dial configurations, meter and endpoint IDs, 
and start/stop meter reads, service line materials of construction, etc.  
Must Have
No
We largely believe that we can comply with this request, 
and we've been engaged in active conversations with the 
WOMs provider rep (InfraMap) and Northstar. Having 
said that, we had some open coordination questions 
about how data would map into Northstar. At the time of 
this response we simply did not feel comfortable 
signaling full compliance. 
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)
7.12
System Integration
Interval Read Integration to 
Northstar
AMI system shall provide interval meter read data to Northstar billing system via an 
interface such that the interval meter reads and usage can be accessed via the Northstar 
billing user interface without the need to separately access the AMI system software. 
Must Have
Yes
7.13
System Integration
Automated Move-in/Move-Out
Move-in/Move-out meter reads (start reads and final reads) shall be initiated from 
the Northstar user interface and obtained automatically from the MDMS via an 
integration with the Northstar billing system without the needs access the AMI 
system software. 
Must Have
Yes
BEACON supports off-cycle billing reads through a 
publicly documented REST API.  The Northstar CIS would 
need to implement this API to retrieve the billing read.
7.14
System Integration
Virtual Disconnect
Meters can be marked as virtually disconnected in the Northstar billing software and 
updated as such in the MDMS automatically via an interface with the Northstar 
billing software. The MDMS shall then alert to usage on the virtually shut account, 
shall make these alerts available via a report from the AMI software, and shall pass 
these alerts to the Northstar software via an interface such that they will display on 
the appropriate accounts.  
Must Have
Yes
Northstar must update BEACON with the virtually shut 
account information.  Northstar can then request reads 
based on the accounts being virtuall shut.  Alternatively, 
BEACON could push any reads on virtuall shut meters to 
Northstar, but this would require an extra line-item.
7.15
System Integration
Leak Alerts Integration to 
Northstar
MDMS shall provide leak alerts to Northstar billing system software such that the 
alert can be displayed on the customer account. 
Must Have
Yes
Nothstar can request leak information from BEACON or, 
with an extra line-item BEACON can push leak 
information to Nortstar.

Requirement ID
Area
Sub-Area
Requirement Description
Priority
Ability to Meet Requirement 
(Yes / No)
Comments
8.1
Support
Compliance
Vendor shall obtain all Federal, State and local permits required for the installation and 
operation of the system and any other approvals.
Must Have
Yes
ORION Cellular NaaS eliminates many of the traditional 
fixed network operating expenses such as infrastructure, 
or the need for designing, permitting, installing, 
maintaining, troubleshooting, and supporting a separate 
telecommunications network. Our ORION Cellular NaaS 
includes endpoints that collect and transmit new 15-
minute interval readings four times per weekday and once 
per weekend day directly to cellular carriers' 
communication towers into BEACON.
8.2
Support
Component firmware
Proposer shall include firmware for all system components, including Endpoints, DCUs and 
portable interrogator/programming/testing units, at no additional cost or separate annual 
maintenance fee. Additionally, all updates, including firmware, MUST include release notes 
at every release.
Strongly Desired
Yes
8.3
Support
Component firmware
Proposer shall provide any available upgrades or patches to firmware to correct problems, 
add new standard features, and ensure system compatibility and full functionality for a 
minimum of 15 years or the expected life of the components at no additional cost, including 
installation. 
Strongly Desired
Yes
8.4
Support
Security
AMI System shall have third party vendor access to system prohibited unless allowed by 
Owner's authorized personnel.
Strongly Desired
Yes
RFP 25-14 AMI REQUIREMENTS  (ATTACHMENT B)