Design,_Installation,_Maintenance_and_Repair_of_a_Supervisory_Control_and_Data_Acquisition_(SCADA)_System..pdf

CITY OF ZEPHYRHILLS

2026-007

DESIGN, INSTALLATION, MAINTENANCE AND REPAIR OF A SUPERVISORY

CONTROL AND DATA ACQUISITION (SCADA) SYSTEM.

AN EQUAL OPPORTUNITY EMPLOYER

FLORIDA TAX EXEMPT #85-8012740166C-4

FEDERAL IDENTIFICATION NUMBER #59-6000455

I. INTRODUCTION TO REQUEST FOR QUALIFICATIONS

II. SCOPE OF WORK

III. EVALUATION CRITERIA & RANKING PROCESS

IV. EVALUATION DOCUMENTS

V. RESPONSE PACKAGE CRITERIA

VI. RESPONSE SUBMITTAL

VII. ADDITIONAL CONDITIONS

VIII. VENDOR REQUIREMENTS AND ACKNOWLEDGEMENTS

1. INTRODUCTION TO REQUEST FOR QUALIFICATIONS

1.1. Invitation

The City of Zephyrhills (the “City”), invites responses (“Responses”) from Vendors which offer to provide the services described in Section “Scope of Work".

1.2. Vendor

A Vendor is an individual, firm, or corporation submitting a Response to the City for the services requested in the RFQ.

1.3. Agreement Terms and Conditions

The Vendor(s) selected to provide the service(s) requested herein (the “Successful Vendor(s)”) shall be required to execute an Agreement with the City. In the event that the proposer to whom the contract is awarded does not execute a contract within thirty (30) days after such award, the

City of Zephyrhills may give notice to such proposer of intent to award the contract to the next ranked Vendor, or to call for new responses.

After a contract is signed, failure to comply with any of the terms and conditions of this RFQ by the awarded Vendor will be cause for termination of the "Design, Installation, Maintenance and Repair of a Supervisory Control and Data Acquisition (SCADA) System." Agreement.

1.4. Additional Information or Clarification

Requests for additional information or clarifications must be made in the City's e-Procurement

Portal at https://procurement.opengov.com/portal/zephyrhillsfl and in accordance with the Cone of Silence. The Cone of Silence is applied to all communications concerning any bid, RFP or

RFQ before intent to award are issued. Any request for additional information, or for questions seeking clarifications must be received in writing no later than Monday, November 23, 2026 by

9:00 am.

The City will issue responses to inquiries and any other corrections or amendments it deems necessary through the City's e-Procurement Portal located at https://procurement.opengov.com/portal/zephyrhillsfl, prior to the Response Submission Date.

Vendors should not rely on any representations, statements or explanations other than those made in this RFQ or any written addendum to this RFQ. Where there appears to be conflict between the RFQ and any addenda issued, the last addendum issued shall prevail.

It is the Proposer’s responsibility to assure receipt of all addenda. Proposers will be required to acknowledge all addendum within their submission through the eProcurement Portal.

All communications are to be directed to the Purchasing Agent through the City's e-Procurement

Portal located at https://procurement.opengov.com/portal/zephyrhillsfl.

1.5. Award of Agreement

An Agreement may be awarded to the Successful Proposer(s) by the City Council as applicable, based upon the requirements reflected herein. The City reserves the right to execute or not execute, as applicable, an Agreement with the Successful Proposer(s) that is determined to be in the City’s best interest.

https://procurement.opengov.com/portal/zephyrhillsfl https://procurement.opengov.com/portal/zephyrhillsfl

1.6. Agreement Execution

By submitting a Response, the Proposer(s) agree to be bound to and execute the Agreement for: Design, Installation, Maintenance and Repair of a Supervisory Control and Data

Acquisition (SCADA) System. Without diminishing the foregoing, the Proposer may request clarification and submit comments or proposed revisions to the language concerning the

Agreement for City’s consideration. Any such comments or proposed revisions identified after the Response has been received need not be considered by the City. None of the foregoing shall preclude the City from seeking to negotiate changes to the Agreement during the negotiation process.

1.7. Response Package

Careful attention must be given to all requested items contained in this RFQ. Proposers are invited to submit Responses in accordance with the requirements of this RFQ. PLEASE READ

THE ENTIRE SOLICITATION BEFORE SUBMITTING A RESPONSE. Proposers shall make the necessary entry in all blanks and forms provided for the Response.

1. Each Response that is submitted for evaluation must meet the requirements specified in the RFQ.

2. Failure to submit all required items in the manner specified may result in your submittal being found unacceptable.

3. Any submittal found unacceptable will not be considered for selection for this project.

1.8. Changes/Alterations

Proposer may change or withdraw a Response at any time prior to Response Submission

Deadline by clicking on "Unsubmit" Proposal via eProcurement Portal. All changes or withdrawals shall be made City's e-Procurement Portal located at https://procurement.opengov.com/portal/zephyrhillsfl. Oral/Verbal modifications will not be allowed. Written modifications will not be accepted after the Response deadline.

1.9. Discrepancies, Errors, and Omissions

Any discrepancies, errors, or ambiguities in the RFQ or addenda (if any) should be reported to the City of Zephyrhills Purchasing Agent in the manner prescribed in RFQ Section “Additional

Information or Clarification”. Should it be necessary, the City will issue a written addendum to the RFQ clarifying such conflicts or ambiguities.

1.10. Disqualification

The City reserves the right to disqualify Responses before or after the submission date, upon evidence of collusion with intent to defraud or other illegal practices on the part of the

Proposer. It also reserves the right to waive any immaterial defect or informality in any

Response; to reject any or all Responses in whole or in part, or to reissue a Request for

Qualifications.

1.11. Reject Responses

The City of Zephyrhills, Florida reserves the right to reject any or all responses, waive informalities, request additional information and to negotiate a contract with the most qualified

Vendor for professional services at compensation which the agency determines is fair, competitive and reasonable in keeping with the best interests of the City.

1.12. Vendor’s Expenditures

Proposers understand and agree that any expenditure they make in preparation and submittal of

Responses or in the performance of any services requested by the City in connection with the

Responses in response to this RFQ are exclusively at the expense of the Proposers. The City shall not pay or reimburse any expenditure or any other expense incurred by any Proposer in preparation of a Response or anticipation of an Agreement award or to maintain the approved status of the Successful Proposer(s) if an Agreement is awarded.

1.13. Compliance with Applicable Law

The laws of the State of Florida shall govern the agreement. Comply with all applicable federal, state, county and municipal laws, ordinances, regulations and rules related to the services to be performed there under. Conduct no activity or provide any service that is unlawful or offensive.

1.14. Conflicts of Interest

No Vendor shall be eligible for selection on any project and no work shall be assigned to a

Vendor which conflicts with or is duplicative of any work by the Vendor or any affiliated business entity, including, but not limited to, partnerships, joint ventures, and subsidiaries of the same parent corporation or Vendor.

1.15. Indemnification

Indemnity: Vendor shall defend, indemnify and hold harmless the City of Zephyrhills and all of the City of Zephyrhills’s officers, agents, and employees from and against all claims, liability, loss and expense, including reasonable costs, collection expenses, attorneys’ fees, and court costs which may arise because of the negligence (whether active or passive), misconduct, or other fault, in whole or in part (whether joint, concurrent, or contributing), of Vendor, its officers, agents or employees in performance or non-performance of its obligations under the Agreement generated from this solicitation. Vendor recognizes the broad nature of this indemnification and hold harmless cause, as well as the provision of a legal defense to the City of Zephyrhills when necessary, and voluntarily makes this covenant and expressly acknowledges the receipt of such good and valuable consideration provided by the City of Zephyrhills in support of these indemnification, legal defense and hold harmless contractual obligations in accordance with the laws of the State of Florida. This clause shall survive the termination of the Agreement from this solicitation. Compliance with any insurance requirements required elsewhere within the

Agreement shall not relieve the Vendor of its liability and obligation to defend, hold harmless and indemnify the City of Zephyrhills as set forth in this article of the Agreement.

It is further agreed that liability and exposure for indemnification (including, but not limited to the amounts of any indemnification owed by a governmental entity) will be limited to and governed by the provisions of Section 768.28(5), Florida Statutes.

Insurance: Vendor shall, at its sole costs and expense, procure and maintain throughout the term of the contract, Comprehensive General Liability and Worker's Compensation insurance, including Employer Liability insurance, with minimum policy limits of

1.16. Insurance

Vendor shall, at its sole cost and expense, procure and maintain throughout the term of the contract, Comprehensive General Liability and Worker’s Compensation insurance, including

Employer Liability insurance, with minimum policy limits of $1,000,000 combined Single

Limits, or to the extent and in such amounts as required and authorized by Florida law, and will provide endorsed certificates of insurance generated and executed by a licensed insurance broker, brokerage or similar licensed insurance professional evidencing such coverage, and naming the City of Zephyrhills as a named, additional insured, as well as furnishing the City of

Zephyrhills with a certified copy, or copies, of said insurance policies. Certificates of insurance and certified copies of these insurance policies must accompany the signed contract. Said insurance coverages procured by the Vendor as required herein shall be considered, and the

Vendor agrees that said insurance coverages it procures as required herein shall be considered, as primary insurance over and above any other insurance, or self-insurance, available to the City of

Zephyrhills, and that any other insurance, or self-insurance available to the City of Zephyrhills shall be considered secondary to, or in excess of, the insurance coverage(s) procured by the

Vendor as required.

Nothing shall be construed to extend the City of Zephyrhills’s liability beyond that provided in section 768.28, Florida Statutes.

1.17. Termination (Cause and/or Convenience)

A. This contract may be terminated in whole or in part in writing by either party in the event of substantial failure by the other party to fulfill its obligations under this contract through no fault of the terminating party, provided that no termination may be effected unless the other party is given (1) not less than thirty (30) calendar days written notice

(delivered by certified mail, return receipt requested) of intent to terminate and (2) an opportunity for consultation with the terminating party prior to termination.

B. This contract may be terminated in whole or in part in writing by the local government for its convenience, provided that the other party is afforded the same notice and consultation opportunity specified in 1(a) above.

C. If termination for default is effected by the local government, an equitable adjustment in the price for this contract shall be made, but (1) no amount shall be allowed for anticipated profit on unperformed services or other work, and (2) any payment due to the

Vendor at the time of termination may be adjusted to cover any additional costs to the local government because of the Vendor's.

If termination for convenience is effected by the local government, the equitable adjustment shall include a reasonable profit for services or other work performed for which profit has not already been included in an invoice.

For any termination, the equitable adjustment shall provide for payment to the Vendor for services rendered and expenses incurred prior to receipt of the notice of intent to terminate, by the Vendor relating to commitments which had become from prior to receipt of the notice of intent to terminate.

D. Upon receipt of a termination action, the Vendor shall (1) promptly discontinue all affected work (unless the notice directs otherwise) and (2) deliver or otherwise make available to the local government all data, drawings, reports specifications, summaries and other such information, as may have been accumulated by the Vendor in performing this contract, whether completed or in process.

E. Upon termination, the local government may take over the work and may award another party a contract to complete the work described in this contract.

F. If, after termination for failure of the Vendor to fulfill contractual obligations, it is determined that the Vendor had not failed to fulfill contractual obligations, the termination shall be deemed to have been for the convenience of the local government. In such event, adjustment of the contract price shall be made as provided in paragraph (c) above.

1.18. RFQ Availability

RFQ documents, plans, addendums can be viewed and downloaded from the City's e-

Procurement Portal at https://procurement.opengov.com/portal/zephyrhillsfl . Registration is

FREE. It is your responsibility to ensure you have downloaded all addendums published before the bid opening. You must be a registered vendor for the City of Zephyrhills prior to any work with the City. Should you have questions concerning this site, contact Customer Support via the

City's e-Procurement Portal to provide assistance. Responses will be opened after the deadline online. A listing of those Vendors who submitted a response will be posted.

1.19. Response Submission

One electronic response package shall be submitted through the City's e-Procurement Portal located at https://procurement.opengov.com/portal/zephyrhillsfl, prior to the Opening time of

Monday, December 7, 2026 by 9:00 am.

The City shall not, under any circumstances, be responsible for delays caused by the issues caused in uploading or for other delays. All responses must be manually and duly signed by authorized authority to bind said Vendor or individual, and Vendor must affix their corporate seal (if any) to the response. In the absence of a corporate seal, the response must be notarized by a Notary public.

The submittal of a response by a preparer will be considered by the City as constituting an offer by the Vendor to perform the required services at the stated fees.

Each Vendor is solely responsible for the reading and completely understanding the requirement of this RFQ. The opening time shall be and must be scrupulously observed. Under no circumstances will responses delivered to the office be accepted. All responses are to be uploaded via City's e-Procurement Portal online. Late submissions will not be accepted.

1.20. Appropriations Clause

The City, as an entity of government, is subject to the appropriation of funds by its legislative body in an amount sufficient to allow continuation of its performance in accordance with the terms and conditions of this contract for each and every fiscal year following the fiscal year in which this contract shall remain in effect. Upon notice that sufficient funds are not available in the subsequent fiscal years, the City shall therefore be released of all terms and other conditions.

1.21. Oral Presentations

At the City's sole discretion, a formal oral presentation may be required by each Vendor that is short list selected during the initial review process. The City will provide a week's notice, if selected. If required, presentations should be in support of the Vendor's response or to exhibit or otherwise demonstrate the information contained herein. If the Committee wishes additional clarification of any information, Vendors maybe requested to submit that information in writing.

1.22. Acceptance of Applicable Policies & Procedures.

A. Vendors responding to this RFQ agree by submission of such response to accept and comply with the City policies and procedures that apply to the selection process for this project.

B. All Vendors should be licensed in the State of Florida and professionally qualified.

C. Any concerns, or issues, relating to current policies and procedures may be addressed with City staff, but separate from this selection process.

1.23. Evaluation Committee Process

The City Manager will appoint a ranking committee who will review and evaluate the qualifications of all interested Vendors. This committee shall select at least three (3) Vendors that are licensed in the State of Florida and are otherwise professionally qualified.

The ranking committee will present their recommendations to the City Manager based on their review of the written responses. The City Manager will present the Committee’s recommendations to City Council for their consent for approval. A member from the ranking committee will be present to respond to any detailed questions the Council may have. City

Council will vote on the Committee’s recommendation.

1.24. Written Selection Process

Step 1. The City will review submittals for responsiveness and responsibility. Those found responsive and responsible based on an initial review shall proceed to Step 2.

Step 2. The City Evaluation Committee comprised of City management and staff will evaluate the responses using the criteria below. Responses will be evaluated and ranked or scored.

1.25. Formal Interview Evaluation Criteria

• Overall impression of key team members

• Methodology presented to assure success

• Ability of principals to promote confidence in the ability of the Vendor to complete the project(s) within the time and cost budgeted

• Ability of te4am members to communicate during the interview process

• Vendor's ability to effectively answer questions and problem solve in the meeting

• Overall impression of the Vendor

1.26. Interview Format

The Vendors selected to make a presentation to the Evaluation Committee will be notified by the

City. Each Vendor selected for further consideration shall be notified in writing and informed of a place and time for the interview sessions. The time allotted to each Vendor for the presentation and interview shall not exceed forty five (45) minutes. (5 Minutes for setup, 20 minutes for presentation, 5 minutes for questions and 5 minutes for knock-down). All members of the

Evaluation Committee will be present during the formal interview.

1.27. Issues to Address at Interview

The intent of the formal interview process is to provide the evaluation committee with in-depth information from the Vendor in order to make a final selection of the best-suited Vendor for the contract. What makes you better suited for this solicitation than the other Vendors. Vendors should focus their presentations on the detailed plan for the tasks, evaluations, interviews, schedule and quality of the services to be provided and any unique characteristics or services the

Vendor offers.

Vendors are discouraged from reviewing company history and past experience evaluated during the written submittals unless this information is relevant to the discussion.

1.28. Award Criteria

The evaluation committee recommendation will be made from their in depth review of the written responses and the evaluation of the interview responses based on various criteria including but not limited to:

• Approach to the implementation, performance and satisfaction of City requirements

• Demonstrated professional skills and credentials.

• Demonstrated understanding and success of similar projects

• Demonstrated ability to communicate well.

• Ability to perform the work within the stated timeframe.

1.29. Hourly Rate/Fees

Hourly Rate/Fees will be solicited from the short-listed candidates invited to interview by email to be delivered by the designated date on the Timetable. Hourly Rates/Fees may be negotiated further with the number one selected Vendor.

If there is no date listed or should the interviews be waived then the fees will be expected the

Tuesday after the Council meeting.

All Hourly Rate/Fees shall be sent to the Purchasing Agent, at kbarnhill@zephyrhills.gov. Mark your emails “FEE RATES-2026-007-Company Name” in the subject line.

1.30. Final Evaluation

Upon completion of the evaluation process by the Evaluation Committee, the Vendors will be ranked in descending order of recommendation. The Evaluation Committee shall present their final ranking to the City Manager for presentation to the City Council for approval of the committee’s recommendation. The City will begin negotiations with the number one ranked

Vendor. Should the City be unable to negotiate a satisfactory contract with the top-ranked

Vendor at a price determined to be fair and reasonable, negotiations shall be terminated with that

Vendor and the City shall initiate negotiations with the second ranked Vendor to arrive at an acceptable contract, and so on.

The final negotiated contract is presented to City Council for approval and authorization by the

City Manager.

1.31. Exception to the RFQ

Vendors may take exceptions to any of the terms of this RFQ unless the RFQ specially states where exceptions may not be taken. Should a Vendor take exception where none is permitted, the response will be rejected as nonresponsive. All exceptions taken must be specific, and the

Vendor must indicate clearly what alternative is being offered to allow the City a meaningful opportunity to evaluate and rank responses.

Where exceptions are permitted, the City shall determine the acceptability of the proposed exceptions and the responses will be evaluated based on the responses as submitted. The City, after completing evaluations, may accept or reject the exceptions. Where exceptions are rejected, the City may request that the Vendor furnish the services or goods described herein, or negotiate an acceptable alternative.

1.32. Openness of Procurement Process

Written competitive responses, other submissions, correspondence, and all records made thereof, as well as negotiations conducted pursuant to this RFQ, shall be handled in compliance with

Chapters 119 and 286 Florida Statutes. The City gives no assurance as to the confidentiality of any response once submitted.

1.33. Cooperative Purchases

This is a cooperative purchase contract. State law allows any government agency and any accredited school in the state to buy off this contract without going to bid, as long as it does not conflict with any of their local regulations.

1.34. Negotiations

The City may award a contract on the basis of initial offers received, without further negotiations, or may negotiate a final contract. Therefore, each initial offer should contain the

Vendor’s best terms from a cost or price and technical standpoint.

The City reserves the right to enter into contract negotiations with the selected Vendor. If the

City and the selected Vendor cannot negotiate a successful contract, the City may terminate said negotiations and begin negotiations with the next selected Vendor. This process will continue until a contract has been executed or all Vendors have been rejected. No Vendor shall have any rights against the City arising from such negotiations.

1.35. Right to Protest

Any actual or prospective Vendor who is aggrieved in connection with the solicitation or award of a contract may seek resolution of its complaints by contacting the City Manager. All Protests must be presented one (1) week after the solicitation deadline or one (1) week after Council approval of ranking.

1.36. Public Records

In accordance with 119.0701 F.S. Vendor shall:

IF A VENDOR HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER

119, FLORIDA STATUTES, TO THE CONSULTANT’S DUTY TO PROVIDE PUBLIC

RECORDS RELATING TO THIS AGREEMENT OR CONTRACT, THEY SHALL

CONTACT THE CUSTODIAN OF PUBLIC RECORDS AT:

RICARDO QUINONES, CITY CLERK

CITY OF ZEPHYRHILLS

5335 8TH STREETH

ZEPHYRHILLS, FLORIDA 33542

RQUINONES@CI.ZEPHYRHILLS.FL.US

813-780-0000

1.37. ACH-EFT Payments

The City will make payments for services provided under this contract by means of an ACH-

EFT process. This method is quicker and eliminates fraud activity. This will need to be setup before any payment processing. The City reserves the right to revise this program as necessary.

2. SCOPE OF WORK

2.1. Introduction

It is the intent of this Request for Qualifications for the selection of

Design, Installation, Maintenance and Repair of a Supervisory Control and Data Acquisition

(SCADA) System.

The City has standardized our Lift Stations, Potable Water Wells, and the Water Tower location with Badger Meters (FKA SmartCover, FKA Data Flow Systems) SCADA System.

2.2. Scope of Work

The scope of services is anticipated to include, but is not limited to:

DATA FLOW SYSTEMS

TAC II SCADA SCADA SYSTEM

TECHNICAL SPECIFICATION

2.3. SCADA SERVER – HARDWARE & SOFTWARE

HYPER SCADA SERVER

• The Hyper SCADA Server (HSS) shall be a self-contained data collection and information server housed in a wall-mounted enclosure. It shall use a Modular Backplane for power distribution and modularity. The HSS shall contain dual CPU’s for Hot-Standby Redundancy, network switchgear, fiber optic converter, power supply units, backup batteries, and surge protection.

• The HSS shall be wall mounted in a climate-controlled facility. The HSS enclosure shall feature a clear window on the front door to allow observing of status LED’s without opening the door.

• The HSS shall connect to a Primary Workstation Computer via a direct Ethernet connection. This direct connection permits Primary Workstation Computer access to the HSS should a separate local area network (LAN) experience a failure. The Primary Workstation Computer will be designated as a data back-up location. The owner’s personnel shall be able to sign onto the system from properly configured workstation computer(s) connected to the HSS via a network or phone line connection.

mailto:LHILLMAN@CI.ZEPHYRHILLS.FL.US

HYPER SERVER MODULE

• The Hyper Server Module (HSM) shall be an embedded computer that includes a CPU, memory, storage, two on-board voice-grade modems, and network interface.

• All communications to and from the HSM shall be through the network connection and module-mounted modems.

• A button shall be provided to direct the CPU to an orderly shutdown process. Status LEDs shall be provided to indicate CPU activity and system status. Configuration straps at the card edge shall be provided to enable system-level configuration. Replacement of an HSM shall not require the use of tools and shall be nothing more than changing the module in the card edge connector.

COMMUNICATION PROTOCOLS

• The communication protocols supported by the system shall include: 1) TAC II Radio, 2) DFP Radio,

3) Net-DFP, 4) MODBUS ASCII, 5) MODBUS RTU, and 6) MODBUS TCP.

• The HSS shall be capable of simultaneously polling multiple communications links, including Cellular

• All RTUs utilizing TAC II and DFP radio protocols shall have the capability of being used as a digipeater for relaying messages from the HSS to any other RTU. The response messages from the destination RTU shall be digipeated to the HSS by the same RTU that forwarded the message to the destination RTU. Mapping of digipeating shall be user-configurable from any workstation computer.

Modifications or programming at the RTUs shall not be required. Four (4) levels of digipeating shall be supported.

• The system shall be capable of utilizing up to 505 radio addresses per communications link, and up to

15 function modules per RTU.

• All remote interfaces directly connected to the HSS shall be fiber optic isolated for transient voltage protection.

2.4. HT4 SCADA Software

General

• The SCADA Software shall be the latest version of Linux-based HT4.

Software Licensing

• HT4 shall have licenses to allow a minimum of 60 concurrent users.

• HT4 shall have licenses for unlimited tags and screens.

Critical Data Redundancy

• HT4 shall feature an automated backup routine to protect the system from the loss of critical data.

• The data redundancy process shall use a designated Windows workstation as a backup location. This workstation shall be equipped with a hard drive large enough to hold all of the system's backup data and shall be configured as a remote backup location. Data backup shall occur every night at midnight. HT4 shall first make a local copy of the data (stored on the HSM) and then backup the data to the designated Windows computer. An entry shall be made in the current day's Access Log to indicate if the previous day's backup was successful or failed.

Drivers

• HT4 shall utilize one to seven concurrent communication drivers.

• HT4 shall support the following driver types:

• TAC II Radio – An efficient serial radio protocol incorporating time-stamped data.

• DFP (Derivative Fractional Protocol) – An optimized serial radio protocol utilizing store and forward techniques.

• Net DFP – An optimized network and cellular protocol utilizing store and forward techniques.

• Modbus – HT4 supports Modbus ASCII, Modbus RTU, and Modbus TCP.

• Standard 5-digit registers must be used and formatted with 0XXXX for digital outputs, 1XXXX for digital inputs, 3XXXX for analog inputs, and 4XXXX for analog outputs with the

DFS device being the Master in the Modbus communications architecture. Packing Modbus digital input, digital output, and analog input registers into the 4XXXX range is not permitted.

• Analog points over the Modbus link shall be unsigned integers (0-65535, 16 bit, point type AI or AO) or 32-bit floating points (point type EI or EO)

System Partitioning

• HT4 shall be supplied with system partitioning.

• The system-partitioning feature shall allow up to eight independent systems to run concurrently on the

HSS.

• Each partition user shall have all the features mentioned in this specification for the RTUs assigned to that partition only. Alarms, reports, and displays from RTUs assigned to one partition shall not be accessible to users in other partitions. In effect, the partitioning system shall appear to each user as if theirs is the only partition on the system; the other partitions shall be invisible to the user.

• All partitions shall have their own full-function access to the auto dialer / voice / pager / E-mail functions.

System User Permissions

• HT4 shall allow user permissions with password protection for control functions, acknowledgment functions, shutdown functions and configuration functions.

• Each user shall be assigned to a system partition.

RTU Configurations

• Configuration of RTUs in the polling database shall be accomplished using fill-in-the-blank questions.

The configuration process shall offer the following options:

• Driver type

• Driver name

• Driver number

• RTU (station) name

• RTU number

• Radio features

• Polling priority

• Digipeating path (TAC II Radio driver only)

• I/O type

• Point name and characteristics

Alarm Configuration

• HT4 shall allow users to configure alarms for all system I/O points. All alarms may be configured with any or all of the following options:

• Announce locally via speakers connected to any or all workstations.

• Call out an announcement to a list of configured telephone numbers.

• Email via third-party relay server.

• Delay before alarm becomes active in the system.

• Time allowed to pass before an acknowledged and still-active alarm is re-announced

(Snooze).

Scheduled and Auto Controls

• HT4 shall allow users to create scheduled controls and auto controls.

• Scheduled controls allow controls to occur on selected days of the week at specific times. Digital controls can be scheduled to come on or go off at a specific time. Analog controls can be scheduled to be set to a desired engineering value.

• Auto controls can be used to automate and facilitate the controlling of hardware in the field. Configuring an auto control instructs the system to perform a certain function when a specific event occurs.

Modbus TCP/IP Emulation

• HT4 shall act as a Modbus TCP/IP slave device for any configured point. This shall include any physical and virtual RTU I/O point in the system.

• The native Modbus register format shall be utilized. Five (5) digit registers must be used and formatted with 0XXXX for digital outputs, 1XXXX for digital inputs, 3XXXX for analog inputs, and 4XXXX for analog outputs.

• Paired Modbus registers shall be configurable as EO or EI points to represent Modbus floating point values.

System Activity Logs and Journals

• HT4 shall maintain time-stamped data logs pertaining to system activities. These shall include:

• System access – Each entry includes the username and IP address (where applicable) of individual who:

• Shutdown the system

• Started the system

• Logged in to the system

• Logged out of the system

• Made or changed a configuration

• Alarms – Each entry includes a source [the value that caused the alarm, the user-name of the individual who acknowledged the alarm, or the phone number called (callout number)] and the alarm activity that was recorded:

• Alarm occurred

• Alarm was acknowledged

• System called out an alarm alert

• Alarm was still active after snooze time

• Controls – Each entry includes the username of the individual who attempted the control and the control activity that was recorded:

• A user without control permission attempted to control a point

• An attempt to control the point was made

• Control was successful

• Control was not successful

• Radio errors – Each entry lists the type of error that was recorded:

• No response from station

• Station response was aborted

• Address format was bad

• Message format was bad

• Checksum or CRC error occurred

• Status change journal – One journal is created per day to record changes in status. An entry is made each time a digital point's value goes from 1 (one) to 0 (zero) or an analog point's value changes more than the configured threshold.

Comment Log

• HT4 shall include an electronic journal to allow users to manually record notes on system operation and other significant events.

• HT4 shall allow the user to enter items into the operations log from any workstation computer.

• The time and date of for a new comment shall default to the current date and time. A specific date may be selected using the date selector tool.

• Comments may be generic to the system or may be for a particular station by entering a station number in the Station box.

• Log entries can be viewed from the Comment Log itself or can be included in one of the pre-configured reports.

• Each entry in the Comment Log shall include the username of the individual who added the comment.

• The Comment Log shall allow a user to search and view notes based on a date range.

• The Comment Log shall allow a user to filter by a station number.

2.5. Viewers

Stats Viewer

• HT4 shall include a screen that displays information on the current status of important system-level points.

• For redundant systems, the statistics shall be for the active Hyper Server Module (where applicable).

• The Stats viewer displays the following:

• CPU usage

• System date and time

• Backup status

• CPU temperature

• Redundant HSM status

• Hard Disk Driver (HDD) usage

• RAM memory usage

• HSM up time

• AC power status

• Number of drivers

• Number of stations

• Number of points

• Number of TCP connections

• Battery voltage

• Driver loop times

Stations Viewer

• HT4 shall automatically generate default viewing screens for each RTU when the site is configured.

These screens shall display all configured monitor and control points for an RTU in a real-time tabular and graphical format.

• Digital input and output points shall have their status displayed.

• Analog input and output points shall have their status displayed in text and bar graph format.

• Clicking a digital or analog monitor point shall generate a trend of the point’s activity over the last 24 hours.

• Clicking a digital or analog control point shall allow the user to set the point to a particular state or value.

Screens Viewer

• HT4 shall include a tool for viewing custom-designed screens.

• Custom screens shall be capable of displaying the status of points and shall allow users to initiate controls.

• Custom screens shall be capable of displaying a series of snapshots from network camera(s) at a configured rate.

• Custom screens shall be capable of displaying data from different sites on the same screen.

• Custom screens shall be capable of displaying trends.

Trend Viewer

• HT4 shall allow the user to view trends of historical values.

• The trend viewer shall be capable of displaying up to 12 variables on the same time/value axis.

• Trends containing multiple points can be displayed individually (single), each point in a separate panel

(combined), or all points in the same panel (overlay).

• For each entry in the display list, the user shall be able to assign a given point name and color.

• A movable, vertical line shall act as a time cursor on the display. This cursor shall be moved by dragging the line to the left or right. The line shall select a particular date and time that corresponds with the values displayed at the right of the screen.

• The trend viewer shall be automatically updated as data arrives from the RTUs.

• Trend Viewer shall provide tools for:

• Zooming in (decreasing the time span)

• Zooming out (increasing the time span)

• Panning backward and forward in time

• Users shall have the option of:

• Setting a range for a trend (minimum and maximum values for the trend's y-axis).

• Applying a smoothing algorithm to create a smooth trend line.

• Adding reference lines (lines that represent critical values that are being monitored).

• Displaying a grid in the trend’s background.

• Manually setting the time span

• Defining default and global trend settings

• Users shall have the option of saving a trend (requires Configure Telemetry permission).

Alarm Viewer

• HT4 shall have an alarm viewer that allows users to sort alarms by:

• Time alarm occurred

• RTU address

• User-defined name of point

• User-defined alarm name

• Status of alarm (ALARM, ACKNOWLEDGED, CLEARED)

• The alarm viewer shall present all alarms that are still unresolved (acknowledged or not) and all alarms that are resolved and unacknowledged.

• For each alarm, the alarm viewer shall display the date and time the alarm occurred, the user-name of the individual who acknowledged the alarm, and the date and time that the alarm was acknowledged.

Camera Viewer

• HT4 shall be capable of displaying live video from network cameras installed on the same network as the HSS.

2.6. System Reports

Detail Report

• The system shall include a Detail Report.

• For the period specified by the user, the report shall display, print, or write to a file a list of all activity at a given RTU or a group of RTUs.

• The user shall have the option of specifying the report for one or more stations for any configured point type.

• When specifying the time period of the report, the user shall have the option of specifying:

• Range between two previous dates

• Range between two previous dates with an added daily time filter

• Current date

• Current date with an added daily time filter

• The report shall allow the user to specify:

• All the points at a remote terminal unit

• All the points on a module at a remote terminal unit

• A specific point at the remote terminal unit

• All the points in a defined grouping (keyword)

• The report shall include:

• User-defined name of the point

• The state or analog value of the point

• The time the point made the transition to the state or analog value

• Every point state change or analog value change for the specified period

• The time-stamp shall be the time of actual occurrence of the event and not the time the message was received.

• Report data shall be displayed in HTML format.

• The user shall be able to specify a text file format (.txt) or a spreadsheet file format (.csv) for export.

Derived Flow Report

• The system shall include a Derived Flow Report.

• For the period specified by the user, the report shall display, print, or write to a file:

• The number of cycles of lift station pumps

• The average inflow in GPM or MGD

• The average outflow (pump rate) in GPM or MGD

• The total flow in gallons or million gallons

• The user shall have the option of specifying the report for one or more stations for configured derived flow points.

• When specifying the time period of the report, the user shall have the option of specifying:

• Range between two previous dates

• Range between two previous dates with an added daily time filter

• Current date

• Current date with an added daily time filter

• Derived flows calculated using pump capacities and run times are not acceptable because of the inaccuracy created by different head pressures. Derived flow calculations must use the “fill the bucket” method of calculating the flows.

• Report data shall be displayed in HTML format.

• The user shall be able to specify a text file format (.txt) or a spreadsheet file format (.csv) for export.

Pump Activity Report

• The system shall include a Pump Activity Report.

• The report shall provide information on how long a digital point was on and how many times a digital point turned on, as well as the average and total accumulated time the point was on. Although this report shall be intended for pumping activity, it shall be capable of being used for other digital-type activity.

• For the period specified by the user, the report shall display, print, or write to a file:

• Number of cycles of the monitored function

• Average cycle of the monitored function

• Total on time of the monitored point

• Minimum and maximum amount of time the monitored function was on

• The user shall have the option of specifying the report for one or more stations for configured pump points.

• When specifying the time period of the report, the user shall have the option of specifying:

• Range between two previous dates

• Range between two previous dates with an added daily time filter

• Current date

• Current date with an added daily time filter

• Report data shall be displayed in HTML format.

• The user shall be able to specify a text file format (.txt) or a spreadsheet file format (.csv) for export.

Pulse Report

• The system shall include a Pulse Report.

• The report shall provide a cumulative total or daily totals for the monitored function for the period specified by the user.

• For the period specified by the user, the report shall display, print, or write to a file the configured unit of measurement for each configured pulse accumulation point.

• The user shall have the option of specifying the report for one or more stations for configured pulse points.

• When specifying the time period for the report, the user shall have the option of specifying:

• Range between two previous dates

• Range between two previous dates with an added daily time filter

• Current date

• Current date with an added daily time filter

• Report data shall be displayed in HTML format.

• The user shall be able to specify a text file format (.txt) or a spreadsheet file format (.csv) for export.

Analog (Flow) Report

• The system shall include an Analog Flow Report.

• For the period specified by the user, the report shall display, print, or write to a file:

• The total time the device was enabled

• The average flow in GPM or MGD

• The totalized flow in gallons or million gallons

• The user shall have the option of specifying the report for one or more stations for configured analog flow points.

• The user shall have the option of generating a cumulative total or daily totals for the specified time period.

• When specifying the time period for the report, the user shall have the option of specifying:

• Range between two previous dates

• Range between two previous dates with an added daily time filter

• Current date

• Current date with an added daily time filter

• Report data shall be displayed in HTML format.

• The user shall be able to specify a text file format (.txt) or a spreadsheet file format (.csv) for export.

Radio Error Report

• The system shall include a Radio Error Report.

• For the period specified by the user, the report shall display, print, or write to a file a list of all radio errors that occurred.

• The report shall include the following:

• “No response” errors from a poll

• “Aborted response” errors from a poll

• “Bad response” errors from a poll (bad address format, bad message format, bad checksum or

CRC)

• Total error count

• The online/offline status of the radio link to each remote terminal unit

• The total number of times the remote terminal unit was offline

• The total time the remote terminal unit was offline

• The user shall have the option of generating a categorized analysis (Summary) or a chronological listing

(Detailed) of any errors that occurred during the specified period.

• The user shall have the option of filtering by driver.

• When specifying the time period for the report, the user shall have the option of specifying:

• Range between two previous dates

• Range between two previous dates with an added daily time filter

• Current date

• Current date with an added daily time filter

• Report data shall be displayed in HTML format.

• The user shall be able to specify a text file format (.txt) or a spreadsheet file format (.csv) for export.

MIN-MAX-AVG Report

• The system shall include a Min-Max-Avg Report.

• For the specified period, the report shall display or print a list of daily analog data, such as pressure and flow measurements, chlorine residuals, turbidity, and tank levels.

• The report shall show the minimum, maximum, and average values for the specified period.

• When specifying the period for the report, the user shall have the option of specifying:

• Range between two previous dates

• Current date

• Report data shall be displayed in HTML format. The report shall print in a print-friendly format.

Snapshot Report

• The system shall include a Snapshot Report.

• For the specified period, the report shall display or print a list of daily analog data such as pressure and flow measurements, chlorine residuals, turbidity, and tank levels.

• For the specified period, the report shall show the value of each point on a user-defined interval.

• When specifying the period for the report, the user shall have the option of specifying:

• A range between two previous dates

• The current date

• Report data shall be displayed in HTML format. The report shall print in a print-friendly format.

Digipeat Configuration Report

• The system shall include a Digipeat Report.

• The report shall display or print the configuration of all DFS stations that are digipeating and provide their digipeating paths.

• Report data shall be displayed in HTML format. A print-friendly version of the report shall be available.

Modbus Map Report

• The system shall include a Modbus Map Report.

• The Modbus Map Report shall display or print the configuration of Modbus-emulated DFS points.

• Report data shall be displayed in HTML format. A print-friendly version of the report shall be available.

Station Configuration Report

• The system shall include a Station Configuration Report.

• The Station Configuration Report shall display or print a table listing all currently configured stations

• When an individual station is selected from the base report, the report shall display or print a detailed listing of that station’s I/O points and their configurations.

• Report data shall be displayed in HTML format. A print-friendly version of the report shall be available.

ODBC Connectivity

• The system shall provide ODBC connectivity for creating custom reports.

• ODBC-compliant spreadsheet or database software may be used to extract data from the SQL tables reports.

Report Scheduler

• HT4 shall allow the user to schedule a report to be printed daily at a specific hour.

• Users may utilize Windows Task Scheduler to automate reports that run on a different interval (e.g., weekly or monthly).

2.7. Tools

RTU Battery Test

• HT4 shall provide the capability of full-load testing of RTU batteries from any workstation computer via the SCADA system.

Telemetry Traffic Tool

• HT4 shall provide users a tool for viewing radio and network communications.

• The telemetry traffic tool shall enable a user to:

• Determine the version of software that a particular station is running.

• Control a digital or analog point to a specific state or value. (Configuration permissions required.)

• Temporarily change the polling priority of a station or take it out of service. (Configuration permissions required.)

• View communications of all stations configured under the selected driver.

• Filter communications by station, module, or message.

System Tool

• HT4 shall provide users who have high-level permissions the ability to:

• Stop and start telemetry

• Reboot the Hyper Server Module

• Test the server’s battery

• Return the server to AC power

• Reset hardware on the HSS bus

• Check the SQL database

File Upload/Download/Delete

• HT4 shall provide an interface through which users can upload the following file types to the Hyper

Server Module:

• Images for use in custom screens

• Custom HTML pages that are linked to from custom screens

• Images used in custom HTML pages

• TCU auto-download configuration files

• HT4 shall provide an interface through which users can download and delete (where allowed) the following file types from the Hyper Server Module:

• Report files (.csv and .txt) generated from pre-configured reports (download and delete)

• Ladder logic .vlb files for ladders that have been installed on the server (download only)

• Custom screen images (download only)

• Driver communication log files generated from the telemetry traffic tool (download only)

Module Patching and Firmware Updating

• HT4 shall provide users with the means to maintain the latest firmware level on all field modules.

• This tool shall…