Texarkana Water Utilities
Request for Proposal
UTILITY BILLING SOFTWARE
May 8, 2016
Proposals Deadline:
June 17, 2016 by 5:00PM CST
TABLE OF CONTENTS
GENERAL DESCRIPTION OF TEXARKANA WATER UTILITIES …
3
INTRODUCTION…………………………………………………………………..
5
CALENDAR OF EVENTS ……………………………………………………….
8
RESPONSE FORMAT …………………………………………………………..
9
1.0
Executive Summary …………………………………………………
10
2.0
Company Background ……………………………………………..
10
3.0
Client References …………………………………………………….
10
4.0
Application Software Specification Chart …………………
10
5.0
Implementation Methodology …………………………………
11
6.0
Support and Maintenance ……………………………………….
11
7.0
Hardware Specifications ………………………………………….
13
8.0
Cost Summary …………………………………………………………
14
9.0
Terms and Conditions ……………………………………………..
16
10.0 Technical RFP Elements ……………………………………………
17
REPRESENTATIVE EVALUATION CRITERIA …………………………..
18
11.0 Appendix A: Billing Software Preferences ………………..
19
12.0 Appendix B: Billing Software Requirements ……………
20
13.0 Appendix C: Performance Bond ……………………………….
24
2
U/B RFP May 2016
GENERAL DESCRIPTION OF TEXARKANA WATER UTILITIES
Texarkana Water Utilities is a joint department of the Cities of Texarkana, Arkansas and Texarkana, Texas
which provides water and sewer services to both cities and the surrounding area. The Utility also provides
solid waste billing and computer networking and maintenance to both Cities. In addition, compost sales,
green waste disposal, residential motor oil disposal and bacteriological water testing is offered to local
citizens and nearby municipalities. The Utility performs functions of capital budgeting and planning,
system operations, maintenance, engineering design, engineering planning, finance and administration
independent of the two cities, yet in conjunction with city activities.
The Customer Service Division provides assistance to customers on a daily basis and is responsible for the
billing, printing and mailing of more than 25,000 bills for water, sewer and/or refuse charges, as well as
handling payments, collections and being a call center for the Utility. Customer Service Specialists process
more than 20,000 payments each month; up to 40% of these payments are brought directly into the office
by our customers. Another 500 to 1,000 customers request additional service and are personally assisted
by our highly trained staff. The Utility receives an average of 275 calls daily from citizens with questions
related to Utility services or other City services. Calls on Utility related subjects such as service availability,
water quality, leaks, mapping, computer services and dozens of others are directed to one of more than
20 different divisions within the Utility.
Approximate breakdown of customer base and other general information:
TX
contract
# of Water
Customers
# of Sewer
Customers
Part of AR system as separate regions
(Funds)
Texas
Leary
Arkansas
Mandeville
Union
13,292
249
10,156
309
1,238
12,747
211
9,052
Water Mains
893 miles
Sewer Mains
558 miles
Fiber Optic Lines
58 miles
Fire Hydrants
3,638
Lift Stations
54
3
U/B RFP May 2016
AR
Wholesale
Customer
Miller
County
PWA
283
Population
Texarkana, Arkansas
30,015
Texarkana, Texas
36,999
Total
67,014
Approximate Monthly Customer Payment Information
Bank draft customers
4,237
Electronic payments – outside bill pay agencies*
3,321
IVR and Web payments
2,862
Direct ACH payments
5
Face-to-face payments
8,875
Mail payments
6,645
Drop Box/Night Deposit
948
* includes: CheckFree, Metavante, MARS, RRFCU, Regions, Paymode – X
4
U/B RFP May 2016
INTRODUCTION
The Client of Texarkana Water Utilities (the Client) is issuing this Request For Proposal (RFP) for the
purpose of soliciting vendor proposals for a utility billing (UB) data processing system (the system) to serve
the current and projected needs of the Client. The application software and hardware configuration
should comply with the minimum specifications as outlined in this RFP.
The Client intends to seek the best solution, based on the representative criteria contained in this RFP, for
its UB data collection, processing and reporting needs. The successful vendor(s) will seek to establish a
turnkey, integrated hardware/software environment for the Client, which will satisfy the specifications
contained in this RFP, bringing to bear whatever vendor resources are required from the areas of
computer systems hardware, software, technical training, conversion, maintenance, and support services.
The Client requests that responding vendors propose the following applications and services:









Utility Billing Software
GAP Study
Installation of software
Conversion of existing data
Training
Interface with ESRI
Interface with Cityworks
Support
Maintenance
The Client desires to contract with a single vendor for all hardware and software and hardware/software
maintenance, installation, conversion and support. However, the Client reserves the right to evaluate
each software application module on its own standard of performance, regardless of whether other or
remaining application modules of the Offeror are considered by the Client. The Client reserves the right
to award the system to any one offeror or a combination of offerors. In addition, the Client reserves the
right to purchase any personal computers or any other hardware needed from an alternate vendor.
One original and three copies of the proposal will be accepted until June 17, 2016 at 5:00PM CST.
Proposals submitted must be binding for no less than one hundred and forty-five (145) days after the date
received. The Client will select the proposal, or combination of proposals, that, in its opinion, is in the
best interest of the Client. The Client reserves the right to reject any or all proposals or portions of a
proposal. The Client also reserves the right to waive minor technicalities in the proposal. The Client not
only reserves the right at the sole discretion of the Client to reject any or all proposals and to waive
technicalities, but also reserves the right of evaluation and the right to determine the methodology for
evaluation of the proposals to determine the best proposal. In addition, to accept the proposal (or
proposals) deemed to be in the best interest of the Client, i.e., the most qualified proposal will not
necessarily be the proposal with the lowest cost. Further, the Client reserves the right to accept a proposal
(or proposals) for any or all items separately or together.
5
U/B RFP May 2016
Vendor inquiries are to be directed to Jim Cornelius, Finance Director. One original and three copies of
the proposal clearly marked “Utility Billing System Proposal", signed by an officer of the company, are
to be submitted in a sealed envelope and addressed on the outside as follows:
Jim Cornelius, Finance Director
Texarkana Water Utilities
Proposal for Utility Billing Software
801 Wood Street
Texarkana, Texas 75501
Proposals may also be hand-delivered to the above address by the date and time specified. It is the
responsibility of the Offeror to deliver the proposal in accordance with these instructions contained above
and/or elsewhere in the RFP. Proposals dispatched, but not received by the Client by proposal closing
time, will be returned, after receipt, unopened to the Offeror.
Performance Bond
The successful respondent to this RFP will be required to furnish a Performance Bond using the form
attached as Appendix C, in the amount of 100% of the total contract price from an approved surety
company authorized to do business in the State of Texas. Such bond shall include all items in the proposal
including software, modifications, training and all other items listed in the proposal. This bond shall
remain in force for a period of (1) year from the date of acceptance of the installed software by the Client,
to guarantee the repair and/or replacement of any defective software which does not adhere to the
functional requirements as specified in the RFP. In addition, the bond shall guarantee the repair and/or
replacement of any defective software which is developed or modified by the vendor at the request of
the Client and accepted by the Client and made a part of the purchase contract.
In case of any defects in the performance of the software during said year, the Client shall notify the
vendor in writing at last known address. If after a reasonable period of time, the vendor has not taken
formal action to correct said defects, the Client will notify the surety.
Oral Presentation
Vendors may be required to make an oral presentation of their proposal to the Client’s Evaluation Team
during the RFP evaluation period. Such a presentation will provide an opportunity for vendors to clarify
their proposals to insure thorough and mutual understanding. The Finance Director will schedule the time
and location for these presentations. Vendors will be informed by telephone and/or mail about details of
the presentation and given sufficient time to prepare for such a presentation. Failure or refusal to make
an oral presentation, if requested, may be cause for rejection of the proposal.
Demonstration
The Client reserves the right to require a demonstration of the proposed software prior to the selection
of a vendor. The Client and vendor will schedule a mutually agreed upon date and location for the
demonstration. The vendor shall be solely responsible for providing demonstration software and all
equipment necessary for such demonstration at no cost to the Utility. Failure or refusal to provide a
demonstration of the proposed software, if requested, may be cause for rejection of the proposal.
6
U/B RFP May 2016
Award of Contract
The final award of the proposal or contract will be made by the Texarkana, Texas City Council and the
Texarkana, Arkansas City Board of Directors. It is anticipated that the contract if awarded, will be awarded
within 145 days of the closing date for receipt of vendor proposals. Vendors must state that their
proposals are valid for at least 145 days from the submission date indicated on page 8 of the RFP.
Contract
In addition to the completed proposal, a resulting contract may be required by the Client, including but
not limited to, written correspondence between the Client and the vendor subsequent to the proposal
submission, facsimiles, and product literature.
Texarkana Water Utilities will not discriminate in the purchase of goods and services on the basis of race,
color, creed, religion, sex, national origin, age, disability, marital status, sexual orientation, gender identity
or genetic information, political opinions or affiliation.
Confidentiality of Documents
Proposals shall be opened to avoid disclosure of contents to competing offerors and kept secret during
the process of negotiation. However, all proposals that have been submitted shall be open for public
inspection after contract award.
Contact with Client Employees
In order to ensure fair and objective evaluation, all questions related to this RFP should be addressed only
to the person(s) so named in this RFP. Contact with any other Client employee, except at the vendor prebid meeting, (if conducted), is expressly prohibited without prior consent of the person(s) so named
herein. Vendors directly contacting other Client employees will risk elimination of their proposal from
further consideration.
7
U/B RFP May 2016
CALENDAR OF EVENTS
Proposal Closing Time/Date by June 17, 2016 @ 5:00PM CST
Review Vendor Proposals by July 1, 2016
Vendor Demos by July 29, 2016
Conduct On-Site Visits To Preview Proposed Software And Hardware Configuration
by August 19, 2016
Contract Negotiations and Award by November 4, 2016
* Dates subject to change
8
U/B RFP May 2016
RESPONSE FORMAT
The RFP Response should be organized in the following order:
Cover Letter
1.0
Executive Summary
2.0
Company Background
3.0
Client References
4.0
Application Software Specification Chart
5.0
Implementation Methodology
6.0
Support and Maintenance
7.0
Hardware Specifications
8.0
Cost Summary
9.0
Terms & Conditions
10.0
Address Technical RFP Elements
11.0
Appendix A: Billing Software Preferences
12.0
Appendix B: Billing Software Requirements
13.0
Appendix C: Performance Bond
9
U/B RFP May 2016
1.0
Executive Summary
The Executive Summary should include a brief overview of the Proposal. It should be prepared in
such a manner as to make it understandable to individuals not familiar with the terminology
peculiar to a project of this type.
2.0
Company Background
The Company Background should provide vendor information including, but not limited to:
2.01 Company Headquarters Information
2.02 Complete list of products provided by the Vendor
2.03 Financial History
2.04 Percentage of Public Sector clients
2.05 Company Awards and Merits
2.06 Number of Years in Public Sector Software
2.07 Total number of Clients
2.08 Software evolution and direction
2.09 Total number of Employees (Include the chart below for Employee Breakdown)
List the number of staff members by primary responsibility:
Development
Support
Implementation
Marketing & Sales
Network Services
Accounting
Total
3.0
Client References
Vendor must supply at least six (6) sites that are currently using a similar system requested by the
Client. Preferably these six (6) references have a customer base of approximately 30,000 accounts
and include at least one reference from the State of Texas and the State of Arkansas. Be sure to
include the total population served by each reference. This reference list is mandatory.
4.0
Application Software Specification Chart
Please answer the provided Application Specification Chart as thoroughly as possible. Please
include cost information in the Cost Summary section of your RFP Response.
Application Software Specification Response Format (Appendices A & B)
Please input an "x" in the appropriate column to the right of the feature/function statement.
Further explanations should be provided in the comments section i.e. the blank row below the
feature/function statement. Each row should have only one "x". Blank rows will be scored as Not
Available.
10
U/B RFP May 2016
5.0
Implementation Methodology
The Vendor’s Implementation section should include information on all facets of the
Implementation process. Please provide thorough information about the following:
5.01
5.02
5.03
5.04
5.05
6.0
Project Management
a. Project Consulting Information
b. Vendor Project Manager Responsibilities
c. Change Management Processes
Training
a. Training Methodology
b. Training Options
c. Training Requirements
d. Syllabus Information
Data Conversion
a. Conversion Methods
b. Conversion process
c. Data Extraction
d. Scheduling
e. Data Validation
Timelines
a. Provide a sample Implementation Gantt Chart
Vendor/Client Responsibilities
a. What is the Client responsible for during Implementation?
b. What services do the Vendor supply?
Support and Maintenance
The Vendor should provide the following Support Information:
6.01
6.02
6.03
Support Options
a. Does the Vendor provide a toll-free support number?
b. Does the Vendor provide Online Support?
c. Other options for support?
Support Group
a. Has an active Support Group in this region
i. Quarterly meetings (optional)
ii. Annual meeting (required)
iii. On-line support group (required)
Support Goals
a. Please provide Response Times and Resolution Times to the following incident levels
i. Emergency
ii. Critical
iii. Standard Help Call
iv. Simplified support agreement
11
U/B RFP May 2016
6.04
6.05
6.06
Problem Escalation Procedures
a. How are incidents handled?
b. What tools do the Vendor Support Staff use?
c. What is the basic chain of command?
System Updates
a. How are system updates managed?
b. How are security updates managed?
c. How often are updates released?
d. What is the typical downtime during an update?
e. Associated costs
Support Services
a. Number of hours included in maintenance/support contract?
b. Services included and/or excluded?
c. Additional hourly cost for excluded or non-covered services?
d. Associated costs
12
U/B RFP May 2016
7.0
Hardware Specifications
Hardware and System Operating Software Requirements
The vendor is encouraged to recommend any enhancements to the minimum requirements stated
below that will improve the overall performance and usability of the system.
Describe the following requirements of the proposed system:
7.01
7.02
7.03
7.04
7.05
7.06
7.07
7.08
7.09
7.10
7.11
7.12
7.13
Server Details
Operating System
Network Environment
Processor Information
Size of Memory
Hard Drive Arrays
Available Disk Space
Workstation Requirements
Printer Compatibility
Please provide all configuration options
Who is responsible for hardware and system software maintenance?
If the hardware and system software is purchased from a third party vendor, who is
responsible for hardware and system software support?
Scanner Hardware Compatibility
13
U/B RFP May 2016
8.0 Cost Summary
Provide total turnkey cost of utility billing software with comprehensive detail of the various
components and ancillary costs using the best estimate for travel costs and other miscellaneous
items. All recurring annual costs must also be specifically detailed. Amounts should be in actual U.S.
dollars and cents, contain no taxes and include all transportation and delivery, FOB, to Client. The
client reserves the right to procure any personal computers or other hardware by other means.
Turnkey Utility Billing System Costs:
o
Software
$____________
o
Data Conversion
$____________
o
Training
$____________
o
Travel
$____________
o
Other (Specify)
$____________
o
-
$____________
o
-
$____________
o
-
$____________
Total
$____________
Recurring annual Costs:
o
Maintenance
$ ____________
o
Licensing
$ ____________
o
Support
$ ____________
o
Other (Specify)
$ ____________
o
-
$ ____________
o
-
$ ____________
o
-
$ ____________
Total
$ ____________
14
U/B RFP May 2016
System Cost Certification
I hereby certify that I have read all items of the RFP and fully understand the requirements listed
herein. I further certify that I am an authorized agent of the Offering Firm and may be held liable for
any or all remedies that may become due to the Client.
SOFTWARE VENDOR
Firm Submitting Proposal: ____________________________
Client: __________________________
Address: __________________________________________
State: _______ Zip Code: __________
Signature: _________________________________
Printed Name: __________________________
Title: _____________________________________
Date: __________________________
HARDWARE VENDOR
Firm Submitting Proposal: ____________________________
Client: __________________________
Address: __________________________________________
State: _______ Zip Code: __________
Signature: _________________________________
Printed Name: __________________________
Title: _____________________________________
Date: __________________________
15
U/B RFP May 2016
9.
Terms and Conditions
Hold Harmless
Vendor shall protect, indemnify, and hold the Client harmless from and against any direct damage,
cost, or liability for any injuries to persons or property arising from negligence and willful misconduct
of the vendor, his employees, agents, or sub-contractors, howsoever caused.
Insurance
Certificates of insurance shall be addressed to the Client. All insurance shall be in effect during the
term of the contract. Vendor shall provide the following coverage:
9.01
9.02
General liability insurance not less than $1 million for bodily injury including accidental death,
to any one person and aggregate. Property damage not less than $1 million for any one
accident or aggregate.
Worker compensation insurance in accordance with provisions of the Labor Code of Texas.
Conversion
Electronic conversion of the Client’s existing data is extremely important. Vendor must address the
conversion methodology and disclose all related conversion costs in the cost summary.
Response Preparation Costs
The Client will not pay any costs incurred by any vendor in the proposal preparation, printing,
demonstration or negotiation process. All costs shall be borne by the proposing vendors with the
exception of costs associated with any Client personnel visits to Vendor offices or other client sites.
16
U/B RFP May 2016
10.




Technical RFP Elements
Support for modern Microsoft operating systems across the software platform. These include
Windows 7, Windows 8, Windows 10, Windows 2008 R2 Server and Windows 2012 Server.
Relational database – support for commonly used relational database for storage of ALL program data
such as Microsoft SQL Server at version 2012 or above. We prohibit the use of flat files for common
data storage.
On-demand cloud capabilities – if needed there should be an easy process for migration of data and
processes into the cloud.
Programming – limited or no use of programming techniques to use old code written in interpreted
languages in a new application unless it has been provably optimized with the database backend and
optimized to run efficiently on a client PC.
17
U/B RFP May 2016
REPRESENTATIVE EVALUATION CRITERIA
The basis for the evaluation of proposals received is included, but not limited to, the following
considerations:















Vendor’s performance record in meeting the requirements of their existing customers (users).
Particular emphasis will be placed in the areas of customer support and the ability to meet the
anticipated future needs of the Client.
Number of satisfied public sector customers (users) in the States of Texas and Arkansas using the
software and hardware configuration being proposed.
Amount and cost of vendor support that will be available for conversion, implementation, assistance,
and on-going modifications.
Proven, existing application systems the vendor has available now for immediate implementation.
The vendor’s capabilities in other systems areas will be treated as a positive factor.
Capability and costs to perform the required conversion of existing data files.
Quality of application software manuals, or other documentation and training aids.
Ease and ability to train user personnel.
Adherence to the requested proposal format, which includes the thoroughness of the proposal as well
as the format of the presentation.
Software and hardware maintenance, support and service capability.
Required experience and number of in-house data processing personnel necessary to operate and
maintain the system.
The number, type and experience of local vendor staff.
Proposer’s ability to support the total system solution, including installation, conversion, software,
training, and hardware/software maintenance, and support.
Responsiveness to software requirements outlined in this RFP.
References from existing clients regarding all aspects of experience with vendor from conversion,
implementation, and after going live.
Demonstrated reporting capability of software including ease of developing, using, and transmitting
by end users and ability to quickly and accurately produce monthly, quarterly and annual reports
needed.
18
U/B RFP May 2016
APPENDIX A
Billing Software Preferences
Application Software Specification Response Format
Please input an "x" in the appropriate column to the right of the feature/function statement. Further
explanations should be provided in the comments section i.e. the blank row below the feature/function
statement. Each row should have only one "x". Blank rows will be scored as Not Available.
A.1.
GAP analysis prior to contract signing – an in-depth evaluation of current work processes,
using this information to document current workflow and how it will be represented and
executed in your software. Determining gaps, if any and utilizing the study as a foundation
for the set up and performance of the software.
A.2.
Unlimited user defined, searchable fields in all areas.
A.3.
Able to support secure kiosk payment stations.
A.4.
Ability to use City Works (in an effective and transparent manner) as its work order software.
A.5.
Services portal – log in by customer, contractor, etc.
A.6.
Ability to tie to “Code Red” for electronic notifications.
A.7.
Mobile app. that is highly functional and provides real-time current account status
information and allows real-time payments.
A.8.
Ability to provide robust, user-friendly, well integrated, feature-rich software modules for
other functional areas such as Finance/General Ledger, Inventory Control, Payroll and
HR/Personnel.
A.9.
Workflow approvals and changes allowed based on role or group permission.
A.10.
Authentication integration with LDAP or Active Directory.
A.11.
Ability to deploy UB client via Microsoft group policy.
19
U/B RFP May 2016
APPENDIX B
Billing Software Requirements
Application Software Specification Response Format
Please input an "x" in the appropriate column to the right of the feature/function statement. Further
explanations should be provided in the comments section i.e. the blank row below the feature/function
statement. Each row should have only one "x". Blank rows will be scored as Not Available.
Software should provide ease of use for Utility end users, allowing them to easily and efficiently meet the
account needs of the customers and the record keeping and billing needs of the Utility. It should include,
but not be limited to the following:
B.1.
Must be able to operate on available Windows-based operating systems, hardware, and
relational data base (on-site). Data storage needs to be on site with possibility of “cloud
based” at a later date if deemed appropriate.
B.2.
Ability to move to paperless environment – new services; receipts; billing; e-notifications.
B.3.
Must be supported by the manufacturer and provide sufficient End of Life notice.
B.4.
PC client software must be a standard and supported by the software provider and the
vendor.
B.5.
Ability to calculate rates, etc. to at least the fourth decimal place.
B.6.
Robust reporting abilities for multiple entities and multiple account types. Ease of editing
reports and their original parameters (via searchable fields?) by all end users to fit the needs
of the requests made by Administration or elected officials.
B.7.
Ease of account set up – information self populates where it is duplicated.
B.8.
Ability to handle face-to-face customers as well as phone calls quickly and easily.
B.9.
Process face-to-face payments quickly with minimum data entry.
B.10.
Ability to apply a partial payment in a desired order of service as designated by the Client.
20
U/B RFP May 2016
B.11.
Ability to accept and properly distribute electronic ACH/bank draft payments i.e. federal
government water and sewer accounts with multiple meters.
B.12.
Ability to accept, compile and process web payments from multiple vendors.
B.13.
Ease of screen navigation – drill down for detail. Can part time users find information easily?
B.14.
Bill multiples (i.e. minimum rates) on all services on one bill (i.e. apartment complexes with
multiple meters).
B.15.
Ability to bill and distribute to correct G/L for accounts that are not location based. (i.e.
dumping charges for pre-treatment).
B.16.
Ability to handle tiered billing, including variations required by different entities and varying
rate structures.
B.17.
Ability to calculate and bill industrial surcharges, including subtraction/addition meters.
B.18.
Encryption for personal information.
B.19.
Functionality that will allow streamlining of current processes in cashiering, customer
service and billing.
B.20.
Advance data clean-up. Conversion of minimum of 15 years data.
B.21.
Ability to fulfill state legislative reporting, data collection requirements for both Texas and
Arkansas as well as the federal government.
B.22.
Ability to add additional service fees as determined by government entities.
B.23.
Ability to create a file (flat, excel, etc.) including all necessary customer info for credit
balance/overpayment refunds that can be imported into laser check software such as
NowChecks to generate refund checks.
21
U/B RFP May 2016
B.24.
Print options that make it easy to provide dated documentation for customer or Utility files.
B.25.
Ability to generate e-bills as requested by customer.
B.26.
Web view for customer of balance history, billing, and usage history on account.
B.27.
Real time single/manual adjustments to balances on accounts.
B.28.
Scanning capabilities. If third party is needed, which third party software is in use with your
customers? Must be either built in or must be compatible with LaserFiche.
_________________________________________________________________
B.29.
Must communicate with handheld meter reading devices (currently Datamatic) and
software for billing purposes.
B.30.
Ability to communicate smoothly with financial software (currently Select) and free upgrade
to communicate with (at this time) an undetermined future financial software.
B.31.
Robust reporting ability. Ability to report by end user on multiple entities and services, either
singly or in any combination.
B.32.
Ability to calculate and bill storm water or similar variable charges.
B.33.
GIS capabilities for integrating with existing ESRI ARCGIS map services.
B.34.
Ability to perform the necessary functions of a backflow prevention program or provide link
with Tokay. Can Tokay data be converted to your application?
B.35.
Ability to securely publish account and balance data to the Internet (Web server).
B.36.
Ability to securely view data catalog.
22
U/B RFP May 2016
B.37.
Ability for end users to easily generate detailed reports “on the fly” that can be saved,
printed and emailed. Support multiple export formats.
B.38.
Ability to quickly and accurately produce reports on water consumption by entity, and or by
fund, on a monthly, quarterly and annual basis including a report of top water/sewer users
by entity and/or by fund i.e. report of top 10 water/sewer users.
B.39.
Ability to quickly and accurately produce reports needed for monthly/yearly accounting
closing including but not limited to refuse reports, sales/usage tax reports, customer
overpayment reports, subsidiary reports for customer deposits, accounts receivable, and
customer payment plans.
B.40.
Ability to accurately track and report on actual monthly payments received by service type
i.e. (refuse).
B.41.
Ability to identify exceptional items (errors) before transactions are posted with specific
account detail indicating the exact account and services containing the errors.
B.42.
Audit features to track data input, changes, and setting modification by user with detail
down to the field level.
B.43.
Group and/or role based security integration with LDAP or Active Directory.
B.44.
Integrated security features to help prevent identity theft.
B.45.
Provide ability to provision test environment to evaluate any changes / updates prior to
migrating to production.
23
U/B RFP May 2016
APPENDIX C
PERFORMANCE BOND
KNOW ALL MEN BY THESE PRESENTS: That __________________________________________
of the City of ___________________________, County of ___________________ and State
of___________________, as Principal, and ________________________authorized under the laws of the
State of Texas to act as Surety on bonds for Principals, are held firmly bound unto the Cities of Texarkana,
Texas, and Texarkana, Arkansas, (OWNER), in the penal sum of (______________________) for the
payment whereof, the said Principal and Surety bind themselves, and their heirs, administrators,
executors, successors and assigns jointly and severally, by these presents.
WHEREAS, the Principal has entered into a certain written Contract with the Owner, dated the
________day of _________________, 20_____, to deliver Utility Billing Software, installation, data
conversion, training, support and related services, as per the Request for Proposal.
Which contract is hereby referred to and made a part hereof as fully and to the same extent as if
copied at length herein.
NOW, THEREFORE, THE CONDITION OF THIS OBLIGATION IS SUCH, that if the said Principal shall
faithfully perform said Contract and shall in all respects duly and faithfully observe and perform all and
singular the covenanted, conditions and agreements in and by said Contract agreed and covenanted by
the Principal to be observed and performed and according to the true intent and meaning of said Contract
and the Specifications hereto annexed, then this obligation shall be void; otherwise to remain in full force
and effect.
Surety, for value received, stipulates and agrees that no change, extension of time, alternation or
addition to the terms of the Contract, or to the work performed there-under, or the specifications,
accompanying the same, shall in anyway effect its obligation on this bond, and it does hereby waive notice
of any such change, extension of item, alteration or addition to the terms of the Contract, or the work to
be performed there-under.
24
U/B RFP May 2016
IN WITNESS WHEREOF, SAID Principal and Surety have signed and sealed this instrument this
_______day of _____________, 20____.
________________________________
Principal
________________________________
Surety
By:
By:
Title
Title
Address:
Address:
25
U/B RFP May 2016