|
|
Home Page /
Your City Government /
Bid Opportunities
Bidding Opportunities
The City of Rincon is currently seeking
the following bids:
SCADA SYSTEM BID
SPECIFICATION 070910
The City
of Rincon will be accepting bids for the following listed SCADA
System until 2 PM December 3, 2007. All bids must be sealed and
marked SCADA System Bids. The City of Rincon reserves the right to
reject any/and or all bids that don not meet the specifications
listed, and waive any formalities that are not in the best interest
for Rincon. When bidding this job system consideration for future
expansion to other lift stations.
SUPERVISORY
CONTROL AND DATA ACQUISITION (SCADA) SYSTEM
TECHNICAL
SPECIFICATION
CITY OF RINCON,
GEORGIA
PART 1 –
GENERAL:
1.1
BIDDER QUALIFICATIONS
A.
The City of Rincon, referred to herein as
the Owner, considers the nature of this work to be highly technical and
fully intends to evaluate all proposals for assurance that the proposed
equipment and software meets the specified requirements. It will be
necessary that all proposals include documentation that validates the
system supplier is technically and financially qualified to successfully
perform the Scope of Work. Minimum qualifications include;
1.
The bidder has been
in continuous operation for a minimum of ten (10) years. And that during
these 10 years the bidder’s primary business was and is marketing,
manufacturing, installing and servicing Radio Based SCADA Projects in
the Water and / or Waste Water industries.
2.
The bidder has
successfully completed at least twenty (20) projects of similar size and
scope (Radio Based SCADA Projects in the Water and / or Waste Water
Industries).
3.
The bidder must
employ a staff of competent engineers, technicians and installers who
are factory trained on the proposed SCADA hardware and software.
4.
The bidder must be
bondable and have adequate financial resources to successfully perform
the complete Scope of Work.
1.2
WORK INCLUDED
A.
This section covers work necessary for the
design, engineering submittal and shop drawing documentation, test,
installation, field testing, startup, commissioning and final O&M
documentation for a Supervisory Control and Data Acquisition (SCADA)
system for the owner. Facilities
included are Wastewater Treatment Plant (Central Site), Town Park East
LS (RTU), 9th Street LS (RTU), 4th Street Water
Tower (RTU), Lisa Street Water Tower (RTU), 17th Street Well
(RTU), and Kroger Well (RTU).
B.
Owner will supply 120 VAC commercial
power at all locations and any required
computer furniture at the Central Site. Any required transducers,
sensors, meters, valves etc. either exist or
will be provided and installed by the Owner.
C.
SCADA Scope of Work
1. Description of
Work:
The work
covered by these specifications consists of providing all design, labor,
tools, materials, and testing necessary for the construction of a SCADA
system as described herein. The term contractor, bidder, or supplier
refers to the telemetry system manufacturer.
The system
shall consist of a central site SCADA server connected to remote
equipment sites by way of a radio network communicating over one or more
FCC licensed frequency. The central site SCADA server shall acquire data
from the remote sites, report operational status and alarms, and provide
data logging capability. Each remote site will be equipped with a Remote
Terminal Unit (RTU). The RTU at each remote station shall monitor local
statuses, and transmit those statuses to the central site when polled by
the communication media utilized.
The on-duty,
systems operator shall be capable monitoring statuses and initiating
control functions to the RTUs by utilizing the system’s primary computer
workstation (Primary Workstation), which shall be networked to the SCADA
server. Other networked client workstations shall have monitoring and
control capability only to the extent to which they have proper
configuration and password authority.
Computer
workstations shall have the capacity to perform general-purpose data
processing tasks without interfering with the monitor and control
functions. The SCADA system design shall be capable of supporting the
Primary Workstation, and other desktop and portable client workstations
via telephone line, cellular telephone adapter and LAN/WAN without the
need for specialized software. The SCADA system design shall be capable
of supporting web-enabled hand-held devices, PDAs, web-enabled cellular
phones, cellular phones and alphanumeric pagers.
All products
offered, whether compliant with the system specification or not, shall
be supported by diagrams and/or descriptive literature with the
proposal. Additionally, detailed documentation describing the proposed
system operation is required. Bidders failing to supply these items
shall be disqualified. It is the sole responsibility of the Owner to
determine the "EQUIVALENT" quality, reliability, performance and
versatility of software and equipment that deviates from this Technical
Specification. Prior to award and within 10 days of request, the
successful bidder may be required to perform a live test demonstration
of all proposed hardware and software in a working radio based system at
no cost to the Owner. The demonstration shall take place at the Owner's
facility.
2. Products
Products described by
these specifications are set up as a minimum standard of quality and
function. The use of a manufacturer's name, model or catalog number is
for the purpose of establishing the quality, reliability, performance
and
versatility of
the
product.
Products of
other manufacturers will be considered if the proposed equipment and
software offers equal or superior quality and function, which will be
determined by the owner. Proposed systems must be of a proven design,
manufactured specifically for water and wastewater applications. Systems
that have been designed for other applications, and have been adapted
for this project application, and/or systems using general-purpose
programmable logic controllers and third party software shall be
unacceptable.
3. General
The specified SCADA
system can be described as a distributed intelligence system.
Communications to and from the central site shall be accomplished by one
or more FCC licensed radio link. The remote terminal unit (RTU)
equipment shall be housed in a single NEMA 4X enclosure, painted white
for thermal purposes, and powered by 120V AC commercial power. The
remote monitor system shall be expandable to fulfill a wide variety of
functions such as digital input/output, analog input/output, automatic
pump station control, and normal programmable logic controller
functions, e.g., PID loops. An Uninterruptible Power Source (UPS) shall
be an integral part of the remote station equipment. In order to insure
total system integration and single point responsibility, the SCADA
hardware and application software shall be installed by a single system
supplier.
4. Central
Site Equipment
a. SCADA
Server
The SCADA Server
shall be a self-contained data collection and information server housed
in a wall-mounted box. The SCADA Server shall include a CPU, two
on-board voice modems, and a 10/100base-TX Ethernet network interface.
In addition, it shall contain a network interface hub, fiber optic
converters, power supply unit, integral UPS and surge protection. The
unit shall be wall mounted in an air-conditioned environment.
The SCADA Server
shall provide dial-out capability for alarms, as well as dial-in access
via remote computer and touch tone phone. The SCADA Server shall support
a Browser-based HMI and shall be compatible ODBC compliant application.
The SCADA Server
shall be offered with an option to include redundant hardware that will
provide a hot-standby capability.
The SCADA Server
shall connect to the Primary Workstation via a network connection. This
connection shall be compatible with standard Ethernet networks. The
system supplier shall provide a direct network connection between the
SCADA Server and the Primary Workstation and both shall be located
inside the same building. A user shall be able to sign onto the SCADA
system from any properly configured workstation connected to the SCADA
Server through a network or phone line connection. The SCADA Server
shall be provided with all the software and licenses to allow a minimum
of twenty (20) concurrent users to be signed on to the monitor and
control applications software.
b. Monitor
and Control Application Software
The SCADA Server
shall incorporate the monitor and control applications software. The
monitor and control applications software shall be password protected to
prevent unauthorized users from gaining access to the system.
Additionally, the monitor and control applications software shall
utilize the MySQL database server.
The communications
protocol shall be specifically designed for use on a
time-division-multiplexed radio link. This protocol shall support
sequential global polling (multiple remote terminal units responding in
sequence to a single poll). The protocol shall support time tagged
message structures to provide a minimum timing accuracy of +/- 2
seconds. Timing accuracy is defined as the difference in time from
when an event actually occurs to the time it is actually logged in the
system files.
All RTUs shall have
the capability of being used as a repeater for relaying messages from
the central site to any other RTU and back.
The response messages from the destination RTU shall be repeated to the
SCADA Server by the same RTU that forwarded the message to the
destination RTU. Mapping of this function shall be user-configurable
from any properly configured workstation. The communications driver
shall support four (4) levels of repeating in this manner.
c. Critical
Data Redundancy
The monitor and
control applications software 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 at a
configured time of day. The monitor and control applications software
shall first make a local copy of the data. It shall then attempt to
locate the remote backup machine. For remote backup to occur, the
designated Windows workstation must be on and running. An entry shall be
made in the current day's Access Log to indicate if the previous day's
backup was successful or failed.
5.
Configurations
a. System
Partitioning
The monitor and
control applications software shall be supplied with system
partitioning. The system-partitioning feature shall allow up to eight
independent telemetry systems to run concurrently on the SCADA Server
and utilize one to seven (7) concurrent communications drivers. Each
user shall have all the features mentioned in this specification for the
RTUs assigned to that user 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.
b. System
User Configuration
The monitor and
control applications software shall allow user configurations with
password protection for control functions, acknowledgment functions,
shutdown functions, and configuration functions. Each user shall be
assigned to a system partition.
c. 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:
RTU (station) name
RTU number
Radio features
Polling priority
Digipeating path
I/O type
Point name and
characteristics
d. Report
Scheduler
The monitor and
control applications software shall allow the user to configure
scheduled reports with the following options:
Hour of the day
Day of the week
Day of the month
Last day of the month
e. Alarm
Configuration
The monitor and
control applications software 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:
1. Announce via
speaker(s) on a properly configured operator workstation that is
connected to the SCADA Server
2. Automatic alarm
dialer to a list of configured telephone numbers.
3. Delay before alarm
becomes active in the system.
4. Time allowed to
pass before an acknowledged and still-active alarm is re-announced
(Snooze).
f.
Scheduled and Auto Controls
The monitor and
control applications software 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 reach 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.
6. System
Activity Logs and Journals
The monitor and
control applications software shall maintain time-stamped data logs
pertaining to system activities to include:
System access –
User-name 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 – Alarm
occurred; alarm was acknowledged; system called out an alarm alert;
alarm was still active after snooze time. 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.
Controls – 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. The user-name of the individual who attempted the control is
provided.
Radio errors – 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.
7. Viewers
a. Default
Screen Viewer
The monitor and
control applications software shall automatically generate default
viewing screens for each RTU when the site is configured. These screens
shall display all monitor and control points configured 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 operator to set the point to a particular state or
value.
b. Graphic
Screen Viewer
The monitor and
control applications software shall allow the user to view the animated
graphical screens that are created using the supplied custom screen
designing software. These screens shall be capable of displaying the
status of stations and shall allow users to initiate controls. The
screens shall also be capable of displaying the output of network video
cameras. Custom-configured screens shall have the capability of
displaying data from different sites on the same screen. Users shall
have the capability of configuring composite screen displays from any
properly configured workstation.
c. Text
Screen Viewer
The monitor and
control applications software shall provide an option for viewing
information on a specified station in a plain-text format. This viewer
shall list all of the station’s modules and their corresponding points.
The current state or value of each shall be listed. The viewer shall
include the ability to regulate how often the server retrieves
information and refreshes the display.
d. Trend
Viewer
The monitor and
control applications software shall allow the user to view trends of
collected values. The trend viewer shall display four (4) variables on
the same time/value axis simultaneously. For each entry in the display
list, the operator 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 can 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.
e. Alarm
Viewer
The monitor and
control applications software shall have an alarm display function that
allows users to sort alarms by:
Time alarm occurred.
RTU address.
User-defined name of
point.
User-defined alarm
name.
Status of alarms
(Alarm, Acknowledged, Cleared).
The alarm display
shall present all alarms that are still unresolved, acknowledged or not,
and all alarms that are resolved and unacknowledged. For each alarm, the
viewer shall display the date the alarm occurred, the user-name of the
individual who acknowledged the alarm, and the date and time that the
alarm was acknowledged.
f. Camera
Viewer
The monitor and
control applications software shall be capable of displaying the output
of video surveillance cameras installed on the same Ethernet network.
8. Comment
Log
The monitor and
control applications software shall include an electronic journal to
allow users to manually record notes on system operation and other
significant events. The monitor and control applications software shall
allow the operator to enter items into the operations log from any
properly configured workstation. The manually entered log entries shall
automatically be time-dated. Log entries can be viewed from the Comment
Log itself or can be included in one of the pre-configured reports. The
Comment Log shall allow a user to search and view notes based on a date
range.
9. Reports
(Pre Configured)
a. Detail
Report
The detail report
shall display, print, or write to a file, depending on operator request,
a list of all activity at a given remote terminal unit, or a group of
remote terminal units, for the period specified by the operator. The
operator shall be able to specify a text file format (.txt) or a
spreadsheet file format (.csv) for export and specify the report for one
station, a group of stations, or all the stations in the system.
This report shall be
generated for the period specified by the operator. The operator shall
have the option of specifying a report period of:
A range between two
previous dates.
A range between two
previous dates with an added daily time filter.
The current date.
The current date with
an added daily time filter.
The detail report
program shall also allow the operator 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.
This 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 period specified.
The detail report
time-stamp shall be within +/- 2 seconds of the actual occurrence and
not time of reception of message from the remote terminal unit.
b. Derived
Flow Report
The derived flow
report shall display, print, or write to a file, depending on operator
request, the number of pump cycles and the derived (calculated) inflow
rate, outflow rate, and total flow for a specified time period. The
operator shall be able to specify a text file format (.txt) or a
spreadsheet file format (.csv) for export and specify the report for one
station, a group of stations, or all the stations in the system. For the
specified period, the derived flow report shall provide:
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 MGD.
When specifying the
period of the report, the operator shall have the option of specifying:
A range between two
previous dates.
A range between two
previous dates with an added daily time filter.
The current date.
The 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.
c. Pump
Activity Report
The pump activity
report shall provide information on how long and how many times a
digital event occurred, as well as the average and total accumulated
time of the event. Although this report was designed for pumping
activity, it can be used for other digital-type activity.
For the specified
period, the pump activity report shall display, print, or write to a
file, depending on operator request:
The number of cycles
of the monitored function.
The average cycle of
the monitored function.
The total on time of
the monitored point.
The minimum and
maximum amount of time the monitored function was
on.
The operator shall
have the option of specifying the report for one or all the stations in
the system. The operator shall be able to specify a text file format
(.txt) or a spreadsheet file format (.csv) for export and specify the
report for one station, a group of stations, or all the stations in the
system.
When specifying the
time period, the operator shall have the option of specifying:
A range between two
previous dates.
A range between two
previous dates with an added daily time filter.
The current date.
The current date with
an added daily time filter.
d. Pulse
Report
The pulse report
shall display, print, or write to a file, depending on operator request,
the configured unit of measurement for each configured pulse
accumulation point. The operator shall have the option of specifying the
report for one station, a group of stations, or all the stations in the
system. The pulse report shall provide, depending on the operator
request, a cumulative total or daily totals for the monitored function
for the specified period.
The operator shall
have the option of specifying the report for one or all the stations in
the system. The operator shall be able to specify a text file format
(.txt) or a spreadsheet file format (.csv) for export and specify the
report for one station, a group of stations, or all the stations in the
system.
When specifying the
time period for the report, the operator shall have the option of
specifying:
A range between two
previous dates.
A range between two
previous dates with an added daily time filter.
The current date.
The current date with
an added daily time filter.
e. Analog
(Flow) Report
The analog flow
report shall display, print, or write to a file, depending on the
operator request:
The total time the
device was enabled for the specified period.
The average value in
engineering units for the specified time period
The totalized value
in engineering units for the specified period.
The operator shall
have the option of specifying the report for one station, a group of
stations, or all the stations in the system. The operator shall also
have the option of generating a cumulative total or daily totals for the
specified period. The operator shall be able to specify a text file
format (.txt) or a spreadsheet file format (.csv) for export and specify
the report for one station, a group of stations, or all the stations in
the system.
When specifying the
period for the report, the operator shall have the option of specifying:
A range between two
previous dates.
A range between two
previous dates with an added daily time filter.
The current date.
The current date with
an added daily time filter.
f. Radio
Error Report
The radio error
report shall display, print, or write to a file, depending on the
operator request, a list of all radio errors that occurred during the
specified period. The radio error messages shall be classified as
follows:
No responses from a
poll.
Aborted responses
from a poll.
Bad responses from a
poll.
Total error count.
The status of the
radio link to each remote terminal unit.
The total number of
times the remote terminal unit was off-line.
The total time the
remote terminal unit was off-line.
The operator shall
have the option of generating a categorized analysis (Summary) or a
detailed chronological listing (Detailed) of any errors that occurred
during the specified period. The operator shall be able to specify a
text file format (.txt) or a spreadsheet file format (.csv) for export
and specify the report for one station, a group of stations, or all the
stations in the system. The operator shall also be able to display all
messages in error and display the real-time radio traffic.
When specifying the
period for the report, the operator shall have the option of specifying:
A range between two
previous dates.
A range between two
previous dates with an added daily time filter.
The current date.
The current date with
an added daily time filter.
g. Custom
Reports
Custom
reports shall be generated using spreadsheet software or database
software. Pre-configured reports shall allow operators to export the
report data to a .txt file or .csv file for customization. Additionally,
ODBC-compliant spreadsheet or database software may be used to extract
data from the monitor and control application’s MySQL tables for use in
custom reports.
10. Tools
a. RTU
Battery Test
The monitor
and control applications software shall provide the capability of
full-load testing of RTU batteries from any of the workstations.
b. Redundant
Radio Switching
The monitor
and control applications software shall provide the capability of having
redundant central site radio equipment. The monitor and control
applications software shall offer the user the capability of having the
central site radio equipment switch automatically when the
communications error percentage reaches a configurable level.
Additionally, the user shall have the option of automatically switching
between the redundant radios at a user-specified time every 24 hours.
c. Telemetry
Traffic
The monitor
and control applications software shall provide the operator with a tool
that can be used to troubleshoot radio and network communication
problems. The telemetry traffic tool shall enable operators to:
1.
Determine the version of software that a
particular station is running.
2.
Control a digital or analog point to a
specific state or value.
3.
Temporarily change the polling priority of
a station.
4.
Collect information on a specific
communications driver. Each query and response is logged to a
time-stamped text file.
5.
View communications status of all stations
configured under the specified communications driver. The display can be
filtered by station, module, or message.
d. Telnet
(Console) Access
The monitor
and control applications software shall provide users who have
high-level permissions the ability to modify databases, perform file
maintenance, and initiate system recovery via a command line interface.
e. Server
Controls
The monitor
and control applications software shall provide users who have
high-level permissions the ability to:
1.
Stop and start telemetry.
2.
Reboot the server.
3.
Test the server’s battery.
4.
Reset hardware on the server bus.
5.
Check the MySQL databases.
f. File
Upload / Download
The monitor
and control applications software shall provide an interface through
which operators can upload the following file types to the server:
1.
Custom screen images.
2.
monitor
and control applications software updates.
3.
Custom HTML files and images.
Operators
shall be able to download the following files from the server:
1.
Report files (.csv and .txt) generated
from pre-configured reports.
2.
Driver communication log files generated
from the telemetry traffic tool.
g. Module
Patching
The monitor
and control applications software shall provide operators with the means
to maintain the latest patch level on all RTU modules. This tool shall
allow modules to be updated remotely from any properly configured
workstation.
11. Advanced
Tools
a. Graphic
Creation and Animation
The monitor
and control applications software shall provide an interactive editor
that allows creation of graphic displays using a pointing device. The
graphic package shall be object-based and support a minimum of 48
colors. As a minimum, the following objects shall be supported;
1.
Rectangle/Square/Polygon
2.
Ellipse/Circle
3.
Line
4.
Text block
5.
Video output from surveillance
camera on network
The graphic
editor shall allow the importation of bit-map type displays. Once
imported, these pictures shall be treated as a single object. The system
shall also support conversion and import of vector graphic displays from
packages such as AutoCAD (via export) or Corel Draw.
Each display
shall have the ability to dynamically update elements in the picture.
Defining the method for dynamic update shall be determined by a point
and click or typed command. The animation module shall also include a
predefined list of dynamic link elements which should include, but not
be limited to:
1.
Data
Link Displays alphanumeric values
2.
Time
Link Displays current time
3.
Alarm Summary Link
Displays current alarm info
4.
Multi-pen Trend Link
Displays (4) real-time trends
Dynamic
properties which may be assigned to an object or group of objects shall
include the following:
1.
Color
2.
Foreground Color
3.
Edge Color
4.
Background Color
5.
Fill Percentage
6.
Layer Position
7.
Horizontal (X)
8.
Vertical (Y)
b. Ladder
Logic Builder
The monitor
and control applications software shall provide a tool for constructing
"ladder logic"-style programs that run on the server. Ladder logic is a
graphical (symbols and text) language that is used to plan, maintain,
and control industrial systems.
These ladder
logic programs may be saved on the server as virtual I/O points,
downloaded to enable limp-mode operation at RTUs, or converted to BASIC
where required.
This tool
shall allow an operator to create virtual logic for the server or
program a RTU hardware device from any properly configured workstation.
c. Trend
Builder
The monitor
and control applications software shall provide a tool for building and
saving frequently viewed trends. The saved trends shall be accessible
either from the trend building application or from a link in the trend
viewer that is automatically generated when the trend is saved. This
tool shall allow an operator to create and save trends from any properly
configured workstation.
d.
On Line Help
The monitor and control applications
software shall provide an online “HELP” function. This function shall
provide content relevant to the point of request. This online help
function shall be accessible from all properly configured workstations.
e. Auto-Dial
Voice / Pager / Email (911)
The monitor and control applications
software shall provide local audio and automatic dialing to telephones
and pagers (911). The software shall also support the sending of E-mail
messages. The user shall have the freedom to select any or a combination
of all methods to announce alarm conditions on a point-by-point basis.
As a minimum, the software shall provide the following functions for
each of the system partitions:
1.
Number Configuration - Users
can add or delete phone numbers from the "numbers to be dialed list.” A
minimum of eight phone numbers shall be supported. A 4-digit ID code
shall be required for proper acknowledgment of alarms.
2.
Voice Message Generation -
Users can record a different voice message or text string for each alarm
or monitored point in the system. The monitor and control applications
software shall allow users to record messages from any workstation using
a microphone connected to the workstation. The voice messages shall be
digitized voice stored on the hard disk. The voice and text messages
shall be completely user-configurable and not rely on an existing fixed
vocabulary.
3.
Automatic Dialing/Voice - Upon
alarm detection, the monitor and control applications software shall
start dialing the first phone number. When the phone is answered, the
unit shall identify itself and ask for the ID number. The called party
shall be required to enter an ID number through the touch-tone keypad on
the telephone within five seconds. Upon detection of a correct ID
number, the voice unit shall announce the alarm message(s). The called
party shall have the capability of acknowledging the alarms from the
touch-tone keypad. The unit shall proceed to the next number if no input
is received within five seconds or if a correct ID is not received after
three tries.
4.
Paging - Upon alarm detection,
the monitor and control applications software shall start dialing the
first number to be paged. Upon detecting an answer by the paging system,
the monitor and control applications software shall provide a standard
Alpha message to be sent by the pager. The monitor and control
applications software shall continue to send the page at configurable
intervals for as long as the alarm condition exists.
5.
E-Mail - Upon alarm detection,
the monitor and control applications software shall compile an E-mail
message and send it to the email address of the selected user.
6.
Message Playback - A function
shall be provided to locally play any voice message, and display any
pager or E-mail message for test purposes.
7.
Alarm Response Delay - The response delay
shall allow the alarms to be acknowledged locally before the dialing
sequence is started. The alarm response delay shall be user-configurable
from 1 to 10 minutes. This delay is in addition to any delay configured
for the individual alarm. The monitor and control applications software
also allows operators to select how unacknowledged resolved alarms are
handled (always call out, include when another alarm forces a call out,
never call out).
f. Voice
Call-In Status (411)
The monitor
and control applications software shall provide call-in alarm and status
functions (411). The user shall be able to dial into the system through
a standard telephone and, by entering the proper codes through the
keypad on the telephone, receive the alarm status and/or the status of
an RTU. Call In shall also allow operators to use the telephone to
change the value of control points and configure a new station by
copying the configuration of an existing one.
12. Primary
Workstation
The “Primary
Workstation” shall consist of the following minimum specifications:
Intel Pentium 4 Processor 631 with HT Technology (3.0GHz, 2MB L2 cache,
800MHz FSB), 512MB Dual Channel DDR2 533 SDRAM 2-DIMMs, 80GB Serial
ATA-300 2MB Cache hard drive (7200RPM), Integrated Serial ATA
Controller, 24x CDRW/DVD Combo Drive, 128MB ATI Mobility Radeon X600
Graphics Card, 19" LCD SXGA Color TFT Display, 104 Key Enhanced
Keyboard, Microsoft Optical IntelliMouse, Microsoft Windows XP
Professional w/SP2, Integrated Intel High Definition 5.1 Channel Audio,
Integrated 56K v.90 Modem, 220W AC ADAPTER, Integrated Gigabit Ethernet
10/100/1000 Network Connection, 1st-3rd Yr On-site, Parts & TS Warranty,
and Microsoft Internet Explorer (HMI). There shall be no additional cost
for client licenses if additional “Computers” are added. The system
shall support an unlimited number of concurrent client users.
13. Freshwater Remote Terminal Unit (RTU)
The
Freshwater RTU shall be a modular constructed microcomputer-based data
collection and dissemination subsystem. The RTU shall communicate with
the central site via a two-way radio link and shall be designed to
accommodate plug-in function modules. Function module card connectors
shall be gold-over-nickel plated to inhibit corrosion. The RTU shall be
housed in a white NEMA 4X enclosure. The RTU shall be capable of
operating in a temperature ranging from -10 to 60 Degrees Celsius (14 to
140 Degrees Fahrenheit). Each Freshwater RTU shall include the I/O
module(s) necessary to meet the specified Input / Output (I/O)
requirements for a specific site location.
a.
Service Port
The remote terminal unit shall support a
local serial interface. The local serial interface shall provide local
access to all the functions of the remote terminal unit. The local
serial interface shall support the monitoring of the radio
communications link. The system shall support an automatic antenna
alignment function utilizing the local serial interface.
b. Power
Supply
All function modules in the remote
terminal unit shall run off DC voltage from +7.5 volts to +13 volts.
The power supply module shall supply +12 volts. A battery backup shall
be provided to operate the system for a minimum of 120 minutes in event
of power failure. The power supply shall be surge protected. The power
supply shall be short circuit protected by current limiting. Normal
operation shall automatically resume when the short circuit overload is
removed. The power supply shall be sized to operate the system with the
battery removed. The power supply module shall provide a battery
backed, isolated bias voltage source. The isolated bias voltage source
shall be utilized to monitor the high well alarm so as to make sure the
alarm is detected and reported during power outages. The circuit
breaker for the power supply module shall be part of the power supply
module. Neither the use of tools nor the disconnection of any wires
shall be required to replace the power supply module.
c. Surge
Protection
Multiple staged surge protection shall be
provided for all power supply and power monitoring circuits. One stage
of protection shall be equipped with both energy limiting and clamping
circuits with slow blow fuses designed for overload conditions. This
design shall provide a very high level of non-destructive transient
immunity. With the exception of a direct lightning strike, the device
shall protect the RTU power supply and power monitoring circuits from
damage due to voltage transients. The unit shall provide circuit
protection to withstand multiple transients in excess of 6,500 volts,
3,250 amps, without damage. Damage shall be limited to a blown fuse
when exposed to larger transients. The device shall be
transient-tested to ANSI standard C62.41.
d. Battery
Each remote terminal unit shall have the
uninterruptible power supply (UPS) function built in. The unit’s
internal power supply shall keep the batteries at a float charge. The
batteries shall not be damaged by deep discharges.
e. Radio
Interface
Each remote terminal unit shall require
one radio interface module (RIM). The RIM shall control the terminal
radio during the polling sequence. The radio interface module shall
have a service port to provide communications link monitoring. The
service port shall also provide the capability to directly monitor
and/or control each module in the remote terminal unit. The radio
interface module utilized at the remote terminal units shall be
interchangeable with the radio interface module at the central site.
The system shall be capable of utilizing up to 505 radio interface
modules per communications link and up to 15 function modules per radio
interface module. All communications shall be in ASCII and utilize an
error detecting and correction data transfer protocol. Each radio
interface module shall have a radio transceiver mounted to it. The
radio shall be a FM transceiver. The radio interface module shall
measure and transmit to the central site the received signal strength
(RSS). Replacement of the radio interface module shall trigger an
automatic configuration of the new module to accommodate the site
address and function (plug & play).
f. Function
Modules
The function modules shall be designed so
they do not have configuration switches or straps and may be easily
added in the future. The function modules shall be designed with surge
suppression on all inputs and outputs. The function module card edge
connector fingers shall be gold-over-nickel-over-copper plated to
inhibit corrosion. Replacement of a function module shall not require
the use of tools or the removal of any interface wires. There shall be
no components associated with the function module mounted to the
motherboard (passive backplane). All the function modules shall support
central site access to the revision level of the module.
g. Discrete
Monitoring
Discrete monitoring shall include on/off
or pulsed inputs of 12 to 30 volts AC or DC. Voltages from 100 to 300
volts AC or DC shall be accommodated with the use of an inline voltage
converter device. Status reporting of the digital inputs shall have an
accuracy of +- 2 seconds, the accuracy being defined as time of an
occurrence to actual time recorded by the central site computer.
Discrete monitoring shall not require interfacing relays to monitor 24
VDC, 115 VAC, 220 VAC or 480 VAC. The discrete monitoring module shall
have LEDs to indicate: the status of each input point; receive
communications; transmit communications; CPU fault; and power status.
The configuration of the discrete monitor points as alarm points,
monitor points (pump run time monitors), or pulsed input points shall be
operator changeable. The custom configuration of the discrete monitor
module shall not require any software or firmware changes in the remote
terminal unit. Replacement of the discrete monitor module shall trigger
an automatic configuration of the new module by the central site (plug &
play).
h. Discrete
Control
Discrete control shall provide for remote
control of 60 to 280 volt AC devices. The control relays shall be
solid-state devices with zero crossover detection. Each control point
shall be capable of driving a 0.5 amp load @ 280 volts AC (140 VA), with
inrush current of 5 amps. The discrete control module shall have the
configurable capability to automatically shut down all outputs in the
case of a power loss on any one of three phases. Operator intervention
shall be required to restart a control point after a phase loss
shutdown. Any discrete control point shall have the capability of being
automatically controlled by any discrete monitor point, at the same RTU
or at any other RTU. This shall be accomplished during configuration at
the SCADA Server and shall be available for an unlimited number of
discrete control points. The discrete control module shall have LEDs to
indicate: the status of each output point; receive communications;
transmit communications; CPU fault; and power status. Replacement of
the discrete control module shal |
