FOR REFERENCE ONLY NOT FOR BID SUBMITTAL

Transcription

1 LIFT STATION TELEMETRY / INSTRUMENTATION & CONTROL SYSTEM GENERAL SPECIFICATIONS PART 1 - GENERAL 1.1 Summary A. It is the intent of this specification to provide a control and monitoring system for a pump station. All components specified or required for a complete, operable system shall be included. B. It is the intent of this document to provide a description of the functions and hardware required to meet the customer s needs. C. The end user will be completing the install of the equipment, and the vendor of equipment will provide start-up and training. D. The supply of any pump control equipment shall be accompanied by a new appropriately sized power supply, and backup battery for each station. 1.2 Definitions A. LCD: Liquid Crystal Display B. LED: Light Emitting Diode C. COM: Communications D. LAN: Local Area Network E. PVC: Poly Vinyl Chloride F. CMF: Central Monitoring Facility 1.3 Submittals A. A detailed site survey of the required work shall be provided to the end user to ensure a clear communication of required. 1.4 Quality Assurance A. Electrical Component Standard: Provide components that comply with NFPA 70 and that are listed and labelled by UL where applicable. B. Listing and Labelling: Provide products specified in this Section that are listed and labelled. 1.5 Warranty 1. The Terms Listed and Labelled : As defined in the National Electrical Code, Article Listing and Labelling Agency Qualifications: A Nationally Recognized Testing Laboratory (NRTL) as defined in OSHA Regulation A. General Warranty: The special warranty specified in this Article shall not deprive the Owner of other rights the Owner may have under other provisions of the Contract Documents and shall be in addition Specifications 42

2 to, and run concurrent with other warranties made by the Contractor under requirements of the Contract Documents. B. Warranty period for any pump control equipment: Five (5) Years from the date of Substantial Completion and Acceptance unless otherwise indicated in other sections of this specification. PART 2 - PRODUCTS 2.1 Manufacturers A. Manufacturers: Subject to compliance with requirements, manufacturers offering products that may be incorporated in the Work include, but are not limited to the following: 1. Pump Control Equipment: a. Flygt b. Products of other manufacturers assembled to provide all specified functions, including reliability equal to or exceeding that of the manufacturer listed in (a) above. 2. The pump controller shall be Multismart Model MSU3MP2 or equal. 2.2 Pump Control Equipment The pump controller shall provide user ready automatic control of pumps with an intuitive HMI interface. The pump controller shall contain pre-designed operational parameters that are selected and configured via the user interface (HMI). The minimum features available in the pump controller shall include: A. Pump control of up to 6 pumps; including pump grouping and pump alternation. B. Intelligent Hand-Off-Auto Control: Hand mode (semi-automatic, non-maintained manual mode), the pump switches off at the deactivation set point and then resets to Auto mode for the next pump run cycle. Hand mode (fully manual, maintained mode). To pump beyond the off (deactivation) set point, the Hand-Off-Auto button must be held down by the user for failsafe control. C. Level set point adjustment for pump activation, deactivation and station level alarms. D. Level device input capability shall include: 4-20mA analog signal, conductive probe or floats. E. Redundant level device input capability with automatic input fault control (input device switching). F. Selectable charge (fill) or discharge (empty) modes. G. Pre-configured station optimization features shall include: Maximum pump off time Maximum pumps to run Maximum starts per hour Inter-pump start and stop time delays Maximum pump run time Specifications 43

3 Blocked pump detection Well washer control capability Well clean out control capability Pump operation control (profile programming) capability H. Locked level alarm function to indicate a level device fault. User-defined % change within a specified time period Different set point values for low use or high use time periods (user defined) I. Pump alternation modes shall include: Fixed lead pump assignment Normal alternation User defined alternation using N:1 ratio Run most efficient pump using N:1 ratio Alternation by the number of hours run or the number of starts within a specified time period J. Pump decommissioning modes shall include: Decommissioned pump is automatically removed from the pump controller. Internal remote monitoring data tag shall flag the decommissioned status of a pump K. Up to (6) unique user defined profiles of set points shall be available to control pumps during specific site conditions or events. Features shall include: Automatic profile change based on date and time Profile selection option from SCADA (remote control), digital input, logic tag or local display HMI L. A datalogger for user-defined faults and events shall include: Recording of up to 50,000 events to internal flash memory Download capability of up to 10,000,000 events by writing directly to an SD card or USB Specifications 44 FTP data transfer and download data capability of event and fault logs in the form of a (csv) file for Microsoft Excel analysis M. 3-phase supply voltage monitoring and supply fault management for the following conditions: Under-voltage Over-voltage Phase fail Phase rotation N. Monitoring of dc power supply, battery voltage, and internal controller temperature O. Flow measurement: Calculated flow via liquid level draw down data

4 P. Fault module capability as follows: Pump hold out function Automatic restart function after fault condition is no longer present Manual reset of fault required (if user intervention of fault reset is selected) Q. Remote control via remote telemetry monitoring to include the following: R. Security (when in combination with a telemetry option specified in this document) Changing the mode of pumps (hand/off/auto operations) Reset of pump faults and station faults Changing pump and alarm set points Changing operational profiles User defined password management for access to programming areas in the controller Automatic data logging of personnel who have entered the programming areas Automatic logging of all unsuccessful login attempts with a date and time stamp Digital input option for controlled access to programming areas S. SD and USB type access ports shall be available for the following operations: Firmware upgrades Save and load pump controller configuration Download data logs Export or import MODBUS and DNP3 points list Input /Output Characteristics The pump controller inputs and outputs shall be modular and shall be expandable. Available I/O types shall include: A. Digital inputs (voltage free input), also configurable as counters B. Digital outputs (240V, 5A resistive) C. Analog inputs (10bit) D. Analog outputs (10bit) User defined digital inputs Digital Inputs shall be configurable based on specific pump sensor arrangements: A. Seal sensor (conductive) B. PTC Thermistor C. Flygt FLS & CLS Specifications 45

5 D. Conductive probe (for liquid level sensing) Dedicated pump monitoring inputs The pump controller shall provide support for the following pump monitoring inputs: A. Insulation resistance test (IRT) with user selectable test voltage up to 1000VDC B. 3-phase current monitoring, derived from external current transformer devices with a 0.5% input resolution tolerance User interface The pump controller shall include a graphical user interface (HMI) display for configuration settings, control operations, and advanced programming. The following display characteristics shall be provided: Status indication The following parameters shall be available to be displayed on the main screen: A. Liquid level in percentage, meters, feet or other custom defined units B. Set points for pump control and alarms C. Pump status (running or stopped) D. Pump availability E. Pump fault indication F. 3-phase voltage supply values G. Date and time indication H. User configurable options to display pump information and station status Information screens The following parameters shall be available via a user key press from the main screen: A. Hours Run accumulators for each pump and the pump station with the following information: minutes run for last pump cycle total minutes (hourly) total hours today, total hours yesterday total hours this week, total hours last week total accumulated hours B. Pump Start accumulators for each pump & the station with the following comparisons pump starts this hour, pump starts last hour pump starts today, pump starts yesterday pump starts this week, pump starts last week total accumulated pump starts Specifications 46

6 C. Flow values station inflow rate pump flow rate total station volume overflow data (including overflow start time, duration, estimated volume) D. Power and Efficiency pump efficiency in gallons or litres per KWHr - or KVAh power in kw, KVA power factor energy accumulators per pump in KWHr and KVAH E. Insulation resistance value for each pump motor in (Ohms) F. I/O Status Digital I/O status and accumulated values Analog I/O status and values in (ma) or scaled values 3-phase voltage, frequency, phase angle, power factor G. Database viewer to review all statistics, data information and available tags in real time H. Communications information and statistics Control Functions The pump controller display interface shall be capable of performing the following control operations: A. Pump control mode for each pump (Hand-Off-Auto) B. Pump fault reset C. Level alarm reset Fault screen The main screen shall include a Fault button which takes the user to a Fault screen and allows them to check all current and unacknowledged alarms. The fault screen will provide fault details along with a date and time stamp for each fault occurrence. A fault reset option shall be presented to the user when alarms can be acknowledged or reset. History screen The main screen shall include a History button which takes the user to a History screen which allows them to view the following information: A. Viewing of all faults and events B. Information filtering capability Specifications 47

7 Configuration screens The user configuration screens shall provide capability to change pump control settings as follows: A. Setup Wizard function to configure the pump controller settings by user input to specific questions B. Set point programming of alarms and pump activation/deactivation. C. Enable or disable alarms D. Set alternation mode for pumps E. Configure I/O as follows: Assign primary/backup level to any input, e.g. 4-20mA or conductive probe Assign pre-defined or user-defined faults to any digital input Zero and span analog inputs Configure digital output source Configure analog output source F. Configure faults as follows: display the fault to the local screen only manual reset (local) or remote reset operation before pump becomes available auto-restart (after fault condition clears) with configurable restart time auto-restart user-selectable number of times within time window before locking out customized text for fault and event name G. Configure station optimization parameters H. Configure supply protection Under and over voltage alarm points Volts phase imbalance and volts phase rotation set points DC supply alarm set point I. Configure motor protection Under current set points Over current set points Ground/earth fault set points Phase failure set points Specifications 48 J. Configure communications ports, speeds and addresses. Configuration program backup, restore and firmware upgrades The pump controller configuration interface shall allow the user to save and restore pump controller configurations onto a portable SD card or USB storage device. The pump controller shall allow for the import of DNP3 and Modbus point lists and custom logic scripts via the SD or USB ports.

8 The pump controller configuration interface shall allow the user to backup system log files, alarm and event log files, and custom scripts via the SD or USB ports. Firmware upgrades shall be possible by using a firmware upgrade file on a portable SD card or USB storage device. Communications Physical The pump controller shall include the following data communication ports: A. (2) Ethernet ports (10Mbit/s) B. (2) RS232 ports (115kBit/s) C. (2) RS485 ports (115kBit/s) D. (1) USB device port E. (1) SD card port Communication Types The pump controller shall support the following communication types: A. TCP/IP B. UDP C. RS232 D. RS485 E. Private radio over RS232 F. PSTN G. Wireless LAN H. Cellular data I. Cellular voice Communication Protocols The pump controller shall support DNP3 (master & slave, level 2 compliant), including: A. Change of state reporting B. Native date/time and quality stamps for each data point C. Event buffering for different classes of data D. Support for multiple masters and slaves to be configured on the unit E. DNP Security (for securing communications between master station and RTU) The pump controller shall support Modbus (master & slave) including: A. Modbus TCP B. Modbus RTU Specifications 49

9 C. Modbus ASCII D. Support for multiple masters and slaves Performance and Environmental Characteristics The pump controller shall meet the following performance and environmental characteristics: A. Central Processing Unit Speed: 566MHz B. Central Processing Unit RAM Size: 256MByte C. Central Processing Unit Flash Memory Size: 64MByte D. Real Time Clock E. Working temperature -10 C to +60 C F. Storage temperature -40 C to +90 C G. Humidity 5% to 95% (non-condensing) H. IP Rating Controller Base Unit: IP20, NEMA 1 I. Display Interface IP65, NEMA 4 Warranty The pump controller shall be provided with a 5 year limited manufacturer s warranty. 2.3 Control Panel Construction & Assembly (If Needed) A. Manufacturers: Subject to compliance with requirements, manufacturers offering products that may be incorporated in the work include, but are not limited to the following: 1. Control Panel Equipment: a. Flygt (Xylem) b. Products of other manufacturers assembled to provide all specified functions, including reliability equal to or exceeding that of the manufacturers listed above. B. General Requirements: 1. Control Panels shall be manufactured in accordance with ISO specifications and shall be so constructed for the application of a UL Listing Label by an approved UL Control Panel Assembly Facility. 2. All electrical connections shall be properly inspected and torqued in compliance with ISO specifications. External connections to the control panel shall be by way of numbered terminal blocks. 3. Control Panels shall be properly checked and load tested with power applied. A control panel test log shall be supplied with the control panel. 4. Control Panels shall be supplied from a UL approved control panel assembly facility with all of the required labels properly attached. Specifications 50

10 C. Control Panel Enclosure Environmental Rating: 1. Control Panel Enclosure rating shall be specified in accordance with the project requirements or the contract drawings as either NEMA 3R, 12, 4 (Painted Steel) or 4X (Stainless Steel). D. Control Panel Enclosure Specific Construction Requirements: 1. Enclosure shall be sized according to physical and functional device requirements. 2. Enclosure seams shall be continuously welded and ground smooth. 3. Enclosure door opening flange trough shall exclude liquids and contaminants. 4. Enclosure shall include an integral body grounding stud and sub-panel mounting studs. 5. Enclosure shall be wall mounted, unless otherwise specified. 6. Enclosure door shall have hidden hinges for a clean, aesthetic appearance. 7. Enclosure door opening angle shall be standard, full access, 135 degree opening radius. 8. Enclosure door shall be interchangeable and removable by pulling a captive hinge pin. 9. Enclosure door shall have a high-impact thermoplastic data pocket mounted on the inner side of the enclosure door. 10. Enclosure door shall have a seamless, foam-in-place, one-piece gasket to provide an oil-tight, dust-tight seal against contaminants. 11. Enclosure shall have a three-point latching system with a zinc die-cast handle that is painted with black textured polyester powder paint. 12. Enclosure handles shall be capable of being padlocked. 13. Steel sub-panel shall be white. 14. When enclosure cut-outs for instruments and other devices are required, holes shall be cut, punched, or drilled and finished with rounded edges. 15. A door stiffener shall be used where applicable to prevent door deflection under instrument loading or operation. E. Instrument Location Requirements: 1. Instruments or control devices designated for sub-panel (back) mounting shall be located in a manner that will allow for maintenance and adjustment. 2. Instrument mounting height shall not exceed 6-6 to the top of the instrument and shall not be lower than 3-0 to the bottom of the instrument (unless otherwise specified). F. Wiring Requirements: 1. Wiring for AC and DC control circuits shall be Type SIS or Type MTW stranded copper and shall be sized for the applied voltage and current. Unless otherwise noted, control circuit wiring shall not be smaller than No. 16 AWG. 2. Cable wiring for analog signal circuits shall be twisted, shielded pairs of stranded copper conductors that shall not be smaller than No. 20 AWG. 3. Wiring for special signalling equipment such as communications, digital data, and multiplexed signals shall be provided by the equipment supplier. 4. Wiring shall be numbered and marked at each termination point. 5. Terminal blocks for internal or external wiring shall be DIN rail mounted, individual screw compression type terminals with machine printed labels. Specifications 51

11 G. Nameplate Requirements: 1. Nameplates are defined as inscribed, plastic plates mounted above or near a panel face mounted component. Unless otherwise noted, nameplates shall be engraved, rigid, laminated plastic with an adhesive back. Nameplate color shall be white with black letters. 2. Component Labels are defined as printed, vinyl labels mounted above, below or near a sub-panel (back) mounted component for identification. Printed vinyl labels shall be white in color with black letters and an adhesive back. H. Grounding: 1. The main Control Panel enclosure shall be properly grounded in accordance with the National Electrical Code and local code requirements. 2. Each analog signal loop shall only have its shield wire connected to ground at a single point for the loop. Shields shall be grounded at control panels where signals are input to the receiving device and not at the source of the transmitting device. I. Electrical Transient (Surge) Protection: 1. All electrical and electronic components of the main Control Panel shall be protected against damage due to electrical transients induced in interconnecting lines from lightning discharges and surges in nearby electrical systems. 2. The transient surge protector shall be rated for 25kA per phase or larger. J. Circuit Breakers: 1. Power Circuit Breakers shall be thermal magnetic type designed for AC current with a minimum interrupting capacity of 15,000 amperes. 2. Control Circuit Breakers shall be in accordance with section UL 489 with a minimum interrupting capacity of 10,000 amperes. K. Control Power Transformers: 1. Control Power Transformers required to provide control system and accessory power shall be machine tool type control transformers with epoxy encapsulated coils or resin impregnated coils, high quality silicon steel laminations, copper magnet wire, moulded-in terminals and 55 C rise (Class 10 insulation system). L. Voltage/Phase Monitor: 1. The voltage-phase monitor shall continually measure the voltage of each of the three phases of the incoming power to the equipment and provide protection for three phase motors, as well as sensitive electronics, etc. The phase monitor shall sense the following conditions: under- and over-voltage, voltage unbalance, phase loss and phase reversal. Q. Enclosure Condensation Heater: 1. There shall be a 120VAC, 50 watt enclosure heater inside the control panel. 2. The heater shall be a silicone rubber, insulated strip type enclosure heater. 3. The heater shall be Chromalox Model #SL-B P, or approved equal. Specifications 52

12 PART 3 - TELEMTRY NETWORK 3.1 Description A. A cellular based technology service will be used for interfacing all eight (8) of the current remote stations together. B. The work will retrofit the existing control panels with a modem to provide remote access. The network will meet the following minimum requirements: 3.2 Cloud Based SCADA 1. Provide OTA Over The Air diagnostics and remote programming capability via Ethernet 2. Dynamic and scalable to allow future expansion, including adding process controls and additional sites 3. Built around open architecture hardware and software to allow future expansion 4. Designed and installed to allow operations to control and monitor process variables A. The summary of this section is to retrofit the existing control panels with a cloud based SCADA system that enables the users to remotely monitor sites, and requires minimum initial investment with lower long term maintenance cost. B. The cloud based SCADA will include the following hardware and features. 1. Use supported field hardware for local control and data acquisition 2. Use cellular communications via an activated cellular modem and through a secure and private VPN connection to remote servers. This is a Cloud-based service. a. Accepted Cloud-Based Services Providers 1. Flygt 2. Services of other manufacturers that provide all specified functions including reliability equal to or exceeding that of the manufacturer listed in (1)above. 3. The communications protocol will be the DNP3 which includes: a. Change of state reporting b. Native date/time and quality stamps for each data point c. Event buffering for digital status data 4. HMI will be based on a well-supported global SCADA platform and accessible via mobile devices such as tablets and smart phones as well as any PC running Internet Explorer version 5 or higher. 5. System Configuration/Daily Operations a. Software configuration and operational actions shall be protected from unauthorized access by a password/pass-code security system. The security model must be centralized, such that each user may use the same password to access the following SCADA features; 1. Development environment 2. Runtime displays 3. Alarm management 4. Alarm dialer (incoming and outgoing calls) Specifications 53

13 b. Software help manuals shall be provided to assist operators and administrative personnel with daily operations and software configuration. The latest versions of all manuals shall be made available for download from the software manufacturer s website. 6. Graphics and Displays a. Software shall support both animated and static graphic objects. Animated graphic objects shall provide real-time process information to the user via displays. Alarms and process data depicted on displays shall be updated immediately upon receiving new data. b. Standard tag types with graphics shall be provided for the following; 1. Analog/discrete inputs 2. Analog/discrete outputs. Outputs sent to field devices must include feedback 3. Multi-position switches. Position changes sent to field devices must include feedback of status received and verification of field action taken. For example, a switch intended to turn on a pump shall generate an alarm if the pump running status is not received within a predefined timeout. 4. Alarms c. Software shall include pre-built displays for standard HMI features. The following pre-built displays shall be provided as a minimum; 1. Alarm display that can be filtered by name and includes current, unacknowledged, disabled and history 2. Trending/Tabular viewing of historical data 3. Report creator d. Software shall include a menu for navigating from one display to another. Menu shall be configurable to allow logical grouping of displays where necessary. e. Operators, with sufficient security privileges, shall have access to system setpoints and control points and shall have the ability to modify these points. f. It shall be possible to determine the properties of any I/O value displayed by selecting it with the mouse. This shall be done in real-time and shall display the following data: 1. Name, description and logical system area 2. Scaling of field data 3. I/O address 4. Alarm properties g. Software shall support background bitmaps on graphical pages h. Software shall be capable of displaying multiple graphical windows simultaneously. 7. Historical and Real-Time Data Management a. Software shall provide historical data storage. A synchronization scheme shall be included, ensuring an exact copy of all historical data resides on three server workstations. In the event that the primary or backup historical data storage servers are not synchronized, the outdated server will backfill all missing data from the server with the most recent historical data. b. The system will maintain all tag properties in a relational database. c. Software shall display historical and real-time data in both plot and tabular format. Historical and real-time plotted values shall be shown in a continuous, uninterrupted, scrolling fashion. These shall be displayed in strip-chart style with the vertical axis depicting the variable value and the horizontal axis representing time. Each display shall be scaled in appropriate coordinates for the specific tag being monitored. The plot s time frame shall be operator selectable from a minimum of one second to five years. Time intervals shall be clearly marked on the x-axis with date/time stamps and shall scroll with the data. d. User shall be able to see the value of plotted tags for any selected point in time Specifications 54

14 e. Software shall be capable of displaying an unlimited number of analog and digital tag plots on a single display. Color shall be used to differentiate between tags. Means must be provided to quickly determine the name and description of each tag displayed. f. Scaling of each displayed tag plot shall, at the user s choice, be either independently configurable or shall follow the scaling of the tag. Changing the scaling of the tag plot shall not affect the scaling of the tag. g. Where data is not available over duration for a particular variable, data plots shall show no data. At no time shall the gap be replaced with a connection between the last good value and the next good value. h. Means must be provided to do the following; 1. Stop the plots from scrolling 2. Zoom in both the time (x) and value (y) axis 3. Pan/Scroll along the time axis or select a particular date to display 4. Move analog tag plots vertically (in the value axis), either individually or as a group 5. Display statistical data, including average, minimum and maximum values, for each plot. i. Ability to print displayed plots shall be provided. j. Presently viewed plot values shall be exportable to comma separated value (.csv) file or directly to a database, for use by 3rd-party data analysis software. k. Software shall be capable of saving groups of tags for later recall. There shall be no limit to the number of these groups. 8. Alarm and Event Management a. A minimum of the last 10,000 alarms and events shall be stored. A synchronization scheme shall be included, ensuring an exact copy of all alarm history resides on three server workstations. In the event that the primary or backup alarm history storage servers are not synchronized, the outdated server will backfill all missing data from the server with the most recent alarm history. b. Alarms and events records shall include; 1. Time/Date stamp 2. The name and description of the alarm tag 3. Priority 4. Status of Alarm (i.e. Active, Acknowledged, Cleared). Alarm Acknowledgement records shall include the name of the user. c. When an alarm condition occurs, the following sequence shall be provided: 1. An audible tone shall annunciate from each of the clients that have access to this alarm. This audible tone shall repeat until the alarm is acknowledged. 2. The alarm shall be added to the alarm history. 3. In the event the alarm has not been acknowledged within a user configurable time period, a telephone dialer shall begin notifying users on predefined rosters. d. Software shall provide user-configurable settings for deadband and delay on analog alarms. e. Users must be notified, both visibly and audibly, of the occurrence of an alarm, regardless which display is presently being viewed. f. An alarm shall be acknowledged by selecting the alarm event from the alarm summary interface and then choosing an Acknowledge button. Alarms shall not be acknowledged simply by clicking on the alarm event. This two-step approach alleviates inadvertent alarm acknowledgement actions. g. Alarm acknowledgement shall immediately be propagated to all user interfaces. h. Operators shall be able to filter the alarms display to show current, unacknowledged, disabled or historical alarm. Alarms shall be filterable by priority or by alarm areas/groups. Specifications 55

15 i. Software shall allow the project to be split into functional areas such that the alarms a user sees/acknowledges are determined by the areas to which the user has access. j. The application shall include a telephone dialer. The dialer shall support text-to-speech, and be automatically synchronized with the tag database at all times. k. The telephone dialer shall share the SCADA system security, requiring users to enter a security code from a telephone keypad to access data and to acknowledge alarms. All alarm acknowledgements shall be recorded in the application event log. l. The telephone dialer shall be capable of contacting different groups of system users based upon the service needs of the alarm. Each group should be capable of making up to 30 actions ( , SMS or text-to-speech phone call) to up to 30. Once the list of actions is complete, it must be able to repeat or activate another group of actions. Systems shall be able to make groups active/inactive to allow for shift changes and duty rosters. Changes to users in groups and active/inactive status changes shall be made without stopping and restarting the application or computer. There shall be no limit to the number of active and inactive groups. The telephone dialer must be able to switch between groups based on time of day or changes in system values. Changes to these groups shall require sufficient user privileges. m. The software must be configurable to detect rapid changes in value or lack of change over a defined period. 9. Report Generation System a. Software shall be capable of producing reports using historical data. Reports may be created for one-time use. b. Report generation shall be invoked either on demand, by a monitored event, or on a scheduled basis. c. The report generation system shall be field configurable, allowing an operator to create, modify and generate reports and export data to third party software. The report generation system shall be capable of displaying reports to the user interface display or of exporting files per the following: 1. To a comma separated value (.csv) file 2. To a text file 3. Directly to a new MS Excel spreadsheet 4. Via d. Reports generated via an Internet client shall be able to be printed to a local printer. e. Reports shall be able to display any analog, digital or calculated tag data from the historical database. 10. Application Upgrades/Support/Diagnostics/Debugging a. Users shall be notified of application upgrades and the user shall not incur a cost for the upgrade. b. Support must include phone and contact. c. Training shall be available for users of all levels (i.e. Operators, Developers, Administrators) 11. Security a. A password protected security system shall support an unlimited number of users, each user having a set of configurable privileges. Privileges for system configuration, data viewing, and operational activities shall be enabled or disabled on an individual user basis b. User accounts shall be able to be duplicated and assigned to new users. c. User passwords shall be encrypted using an algorithm that shall render their file storage unreadable. Specifications 56

16 d. User passwords must be configurable to exceed a minimum length, contain alphabetic, numeric or special characters, or expire after a pre-set period e. System shall allow creation of additional security privileges where necessary. The system shall allow any number of combinations to access control setpoints remotely. Thus a custom security privilege can be created for each individual user role. f. Changes to user access privileges can be made while the application is running and shall become effective immediately. Networked users whose accounts have been altered shall be affected by the changes immediately, not after stopping and starting the application. g. Security system shall be multi-session. It will validate multiple users simultaneously and record their session activity concurrently for all users. 12. Internet Connectivity and Handheld Device Support a. Internet connectivity shall not require the installation or configuration of a 3rd party Internet Server product (e.g. Miscrosoft IIS, Apache). b. On-line configuration changes shall be pushed immediately to all Internet client interfaces without requiring the browser interface to be restarted or refreshed. c. Internet clients shall require only the latest version Microsoft Internet Explorer to communicate with the application. Internet clients shall require no software to be manually installed. Upon first contact with the Internet server serving the application, the Internet client shall automatically synchronize with the application and download any necessary files. All subsequent connections to the server shall synchronize the Internet client with the server. d. Internet client shall cache displays in order to reduce display access time. e. Internet client interfaces shall have graphical displays identical to the standard client and server interfaces and shall not require separate development time or a separate development interface. The automatic display generation process shall not distort the graphical layout of any display. f. Software shall support access to alarms and real-time status information via hand-held devices. 13. Redundancy and Load Sharing a. Software shall support a minimum of three levels of redundancy for I/O communications (i.e. primary server, 1st backup server, 2nd backup server). Software shall support a minimum of two levels of redundancy for all other services. In the event of primary server failure, software shall be capable of automatic fail-over to a backup server. No manual intervention shall be required. b. Software shall support distribution of services across any number of computers to facilitate load sharing. c. All servers shall be aware of which server is in control of each software process. No two servers shall perform the same function at the same time. This ensures efficient use of network communications and connections to I/O devices. d. Software must not require each redundant server to use a second network card to monitor the status of the primary server. e. Backup servers shall be capable of load-sharing the various system operations (including I/O communications and data logging, alarm management, network communications management, security management). Specifications 57

17 PART 4 - EXECUTION 4.1 Start-up 4.2 Training A. Field service rep shall go to site for 1 day to start up the first station. B. Additional start-up visits can be provided upon request from end user. A. Field service rep shall go to site for 1 day to train end user to make custom configurations. B. Additional training can be provided upon request from end user. Part 5 - EXCLUSIONS 5.1 Bid Exclusions A. Installation of equipment provided. END OF SECTION Contractors submitting bids must provide a list of five (5) references and specific locations where the proposed equipment and programming is presently being used. Bids will be received by the City of Sidney at the office of the City Purchasing Agent, 201 W. Poplar Street, Sidney, OH until 11:30 a.m. (EST) on Thursday, November 29, at which time all bids received will be publicly opened and read aloud. Questions regarding specifications can be directed to: William C. Blakely, Utilities Director wblakely@sidneyoh.com Questions regarding bid submittal can be directed to: Lori Werling, Engineering/Public Works lwerling@sidneyoh.com Specifications 58