HomeMy WebLinkAbout2019-09-17; Municipal Water District; Resolution 1621RESOLUTION NO. 1621
A RESOLUTION OF THE BOARD OF DIRECTORS OF THE CARLSBAD
MUNICIPAL WATER DISTRICT OF THE CITY OF CARLSBAD, CALIFORNIA,
APPROVING THE 2019 SUPERVISORY CONTROL AND DATA ACQUISITION
MASTER PLAN, CAPITAL IMPROVEMENT PROGRAM (CIP) PROJECT NO.
5542-2.
WHEREAS, the Board of Directors of the Carlsbad Municipal Water District (CMWD Board) of
the City of Carlsbad, California has determined it necessary, desirable and in the public interest to
prepare a 2019 Supervisory Control and Data Acquisition (SCADA) Master Plan; and
WHEREAS, on June 28, 2005, the CMWD Board adopted Resolution No. 1249, approving plans
and specifications and authorizing the district secretary to advertise for bids for SCADA Improvements
to the recycled water distribution system, CIP Project No. 36753; and
WHEREAS, on June 16, 2009, the CMWD Board adopted Resolution No. 1359, adding the
position classification of SCADA Technician and amending the salary schedule for Carlsbad Municipal
Water District (CMWD); and
WHEREAS, on May 23, 2017, the CMWD Board adopted Resolution No. 1567, authorizing
execution of a master agreement with Brown and Caldwell for professional engineering services for
work related to the SCADA Master Plan for Sewer, Water and Recycled Water Systems, CIP Project No.
5542;and
WHEREAS, the attached 2019 SCADA Master Plan was completed by Brown and Caldwell in
accordance with the tasks outlined in their master agreement; and
WHEREAS, the 2019 SCADA Master Plan represents a comprehensive program for
implementation of an integrated new modern SCADA system; and
WHEREAS, staff recommends that the CMWD Board approve the 2019 SCADA Master Plan.
NOW, THEREFORE, BE IT RESOLVED by the Board of Directors of the Carlsbad Municipal Water
District of the City of Carlsbad, California, as follows:
1. That the above recitations are true and correct.
2. That the CMWD Board approves the 2019 SCADA Master Plan, a copy of which is on file
in the City Clerk's office.
September 17, 2019 Item #13 Page 7 of 8
PASSED, APPROVED AND ADOPTED at a Joint Special Meeting of the Board of Directors of the
Carlsbad Municipal Water District of the City of Carlsbad, California and the City Council of the City of
Carlsbad, California on the 17th day of September 2019, by the following vote, to wit:
AYES: Hall, Blackburn, Bhat-Patel, Schumacher, Hamilton.
NAYS: None.
ABSENT: None. MJHt/iJ?
1 ~ J-/ectol Gomez1
~,b1 BARBARA ENGLESON, SECRETARY De p_v-f,Ji
(SEAL) C/:j
Cleo/
September 17, 2019 Item #13 Page 8 of 8
SCADA
Master Plan
June 2019 | FINAL
Prepared for City of Carlsbad Utilities and Carlsbad Municipal Water District
450 B Street, Suite 1500
San Diego, California 92101
SCADA Master Plan
Prepared for
City of Carlsbad/Carlsbad Municipal Water District
Carlsbad, California
June 2019
ii
SC07221_FINAL_Carlsbad SCADA Master Plan
Table of Contents
List of Figures ............................................................................................................................................... v
List of Tables ............................................................................................................................................... vi
List of Abbreviations ................................................................................................................................... vii
Executive Summary ................................................................................................................................... viii
Introduction, Objectives, and Approach ............................................................................................ viii
Existing System Evaluation ................................................................................................................ viii
Operational Needs and Deficiencies Assessment ........................................................................... viii
Standardization .................................................................................................................................. viii
Implementation Plan ............................................................................................................................ ix
Communications Study ........................................................................................................................ ix
1. Introduction, Objectives, and Approach ...........................................................................................1-1
1.1 Introduction .............................................................................................................................1-1
1.2 Vision Statement.....................................................................................................................1-1
1.3 Approach .................................................................................................................................1-1
1.3.1 Existing System Evaluation ......................................................................................1-2
1.3.2 Operational Needs and Deficiencies Assessment .................................................1-2
1.3.3 PLC and HMI Standardization ..................................................................................1-2
1.3.4 Implementation Plan ................................................................................................1-2
1.3.5 Communications Study ............................................................................................1-3
2. Existing System Evaluation ...............................................................................................................2-1
2.1 Introduction .............................................................................................................................2-1
2.2 Approach .................................................................................................................................2-1
2.3 Existing Water and Recycled Water SCADA System Overview .............................................2-2
2.3.1 Water and Recycled Water System Architecture ....................................................2-2
2.3.2 Water and Recycled Water System Condition Assessment and Data Collection .2-8
2.3.3 Water and Recycled Water System External Data Sources ...................................2-9
2.4 Existing Sewer SCADA System Overview ............................................................................ 2-10
2.4.1 Sewer System Architecture ................................................................................... 2-10
2.4.2 Sewer System Condition Assessment and Data Collection ................................ 2-13
2.4.3 Sewer System External Data Sources .................................................................. 2-14
3. Operational Needs and Deficiencies Assessment ..........................................................................3-1
3.1 Introduction .............................................................................................................................3-1
3.1.1 Approach ...................................................................................................................3-1
3.2 Operational Needs ..................................................................................................................3-2
3.2.1 Site Visits ..................................................................................................................3-2
City of Carlsbad / CMWD SCADA Master Plan Table of Contents
iii
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.2 State of the Industry Workshop ...............................................................................3-8
3.2.3 Enterprise Data Mapping Workshop .................................................................... 3-14
3.2.4 Operations Shadowing .......................................................................................... 3-16
3.2.5 Levels of Automation ............................................................................................. 3-23
3.2.6 Staffing Needs ....................................................................................................... 3-25
3.2.7 SCADA Equipment Resource and Space Needs .................................................. 3-27
3.3 Operational Needs and Opportunities Summary ............................................................... 3-32
4. PLC and HMI Standardization ..........................................................................................................4-1
4.1 Introduction .............................................................................................................................4-1
4.2 RFP Approach and Development ...........................................................................................4-1
4.2.1 Approach ...................................................................................................................4-1
4.2.2 HMI Software RFP Development .............................................................................4-4
4.2.3 PLC Hardware RFP Development ............................................................................4-6
4.3 HMI Evaluation ........................................................................................................................4-8
4.3.1 Round 1 Proposal .....................................................................................................4-8
4.3.2 Round 2 Demonstration and Site Visits ............................................................... 4-10
4.3.3 HMI Recommendations ........................................................................................ 4-11
4.4 PLC Evaluation ..................................................................................................................... 4-11
4.4.1 Proposal ................................................................................................................. 4-11
4.4.2 PLC Recommendations ......................................................................................... 4-12
4.5 LC and HMI Standards ........................................................................................................ 4-12
4.5.1 SCADA System Standards ..................................................................................... 4-12
4.5.2 SCADA System Standards Governance ................................................................ 4-13
5. Implementation Plan .........................................................................................................................5-1
5.1 Introduction .............................................................................................................................5-1
5.2 Approach .................................................................................................................................5-1
5.2.1 Improvements ...........................................................................................................5-1
5.2.2 Phase Breakdown ....................................................................................................5-1
5.3 Implementation Phase ...........................................................................................................5-1
5.3.1 Phase 1: Foundational Structures ...........................................................................5-1
5.3.2 Phase 2: Immediate Improvements/Needs ...........................................................5-2
5.3.3 Phase 3: Core System Upgrades .............................................................................5-2
5.3.4 Phase 4: Future Improvements ...............................................................................5-3
5.3.5 Implementation Contract Management ..................................................................5-4
5.4 Climate Action Plan .................................................................................................................5-5
5.4.1 Project Contributions to CAP Goals .........................................................................5-5
5.5 Implementation Plan ..............................................................................................................5-6
5.5.1 Schedule ...................................................................................................................5-6
5.5.2 Alternative Delivery Methods ...................................................................................5-7
5.5.3 Opinion of Probable Cost ...................................................................................... 5-10
City of Carlsbad / CMWD SCADA Master Plan Table of Contents
iv
SC07221_FINAL_Carlsbad SCADA Master Plan
5.6 Workforce Assessment ........................................................................................................ 5-12
5.6.1 Staffing Options ..................................................................................................... 5-12
5.6.2 Skills Sets Evaluation ............................................................................................ 5-13
5.6.3 Workload Projections ............................................................................................ 5-14
5.6.4 Recommendations ................................................................................................ 5-15
6. Radio Communications System .......................................................................................................6-1
6.1 Overview ..................................................................................................................................6-1
6.2 Summary .................................................................................................................................6-1
6.3 Alternative Communications Systems ...................................................................................6-1
6.3.1 Cellular Telemetry .....................................................................................................6-2
6.3.2 Fiber Optic .................................................................................................................6-2
6.4 Radio Frequency Comparison ................................................................................................6-2
6.4.1 Unlicensed Frequencies ...........................................................................................6-2
6.4.2 Licensed Frequencies ..............................................................................................6-3
6.5 Site List ....................................................................................................................................6-3
6.6 Site Description .......................................................................................................................6-5
6.6.1 Report Heading Descriptions and Definitions ........................................................6-5
6.6.2 dBm Range Table .....................................................................................................6-6
6.7 Recommendations..................................................................................................................6-6
Appendix A: List of Sites ........................................................................................................................... A-1
Appendix B: Field Survey Data Reports .................................................................................................. B-1
Appendix C: Radio Communications Field Report ..................................................................................C-1
Appendix D: Site Notes ............................................................................................................................ D-1
Appendix E: Workshop Notes ................................................................................................................... E-1
Appendix F: Additional Observations ....................................................................................................... F-1
Appendix G: HMI Software RFP ............................................................................................................... G-1
Appendix H: PLC Hardware RFP .............................................................................................................. H-1
Appendix I: HMI Software RFP Addendum No. 1 ..................................................................................... I-1
Appendix J: PLC Hardware RFP Addendum No. 1 ................................................................................... J-1
Appendix K: HMI Software Demonstrations ........................................................................................... K-1
Appendix L: HMI Software Reference-Check Script ................................................................................ L-1
Appendix M: Implementation Schedule .................................................................................................. M-1
Appendix N: Opinion of Probably Construction Costs ............................................................................ N-1
Appendix O: Workload Projections .......................................................................................................... O-1
Appendix P: Radio Communications Site Map ........................................................................................ P-1
Appendix Q: Radio Communications Site Report ................................................................................... Q-1
City of Carlsbad / CMWD SCADA Master Plan Table of Contents
v
SC07221_FINAL_Carlsbad SCADA Master Plan
List of Figures
Figure 2-1 Levels of Technology Aging ....................................................................................................2-2
Figure 2-2. Water and Recycled Water System Architecture Diagram (1 of 2) .....................................2-4
Figure 2-3. Water and Recycled Water System Architecture Diagram (2 of 2) .....................................2-5
Figure 2-4. Water and Recycled Water Control System Data Flow ........................................................2-6
Figure 2-5. Existing HMI Architecture ......................................................................................................2-7
Figure 2-6. Sewer System Architecture Diagram ................................................................................. 2-11
Figure 2-7. Sewer Control System Data Flow ....................................................................................... 2-12
Figure 3-1. Levels of Automation Maturity ........................................................................................... 3-10
Figure 3-2. Enterprise Data Map ........................................................................................................... 3-17
Figure 3-3. Combined IT/OT/Automation Server Room Layout Example ........................................... 3-28
Figure 3-4. Server Rack Layout Example .............................................................................................. 3-28
Figure 3-5. Automation/OT Lab/Tech Area Layout Example ............................................................... 3-29
Figure 3-6. Decentralized Control Room Layout Example ................................................................... 3-31
Figure 3-7. Summary of Needs ............................................................................................................. 3-34
Figure 3-8. Prioritized Progression of Level of Automation ................................................................. 3-35
Figure 4-1 HMI Evaluation Criteria ...........................................................................................................4-2
Figure 5-1. Design-Build Delivery .............................................................................................................5-7
Figure 5-2. Sample Progressive DB Project Development Process .......................................................5-8
Figure 5-3. Summary of Estimate Ranges ............................................................................................ 5-11
Figure 5-4. Scheduled Implementation Costs ...................................................................................... 5-12
Figure 5-5. Project Workload by Year ................................................................................................... 5-15
Figure 6-1. Signal Strength .......................................................................................................................6-6
Figure 6-2. Radio Study Block Diagram - Backbone ...............................................................................6-7
Figure 6-3. Radio Study Block Diagram – Elm Reservoir to Maerkle Tower .........................................6-8
Figure 6-4. Radio Study Block Diagram – Elm Reservoir to Tap Reservoir to D Site ............................6-9
Figure 6-5. Radio Study Block Diagram – D Site to Elm Reservoir to La Costa Hi ............................ 6-10
Figure 6-6. Radio Study Block Diagram – Maerkle Tower to TAP Reservoir to CMWD Building ....... 6-11
City of Carlsbad / CMWD SCADA Master Plan Table of Contents
vi
SC07221_FINAL_Carlsbad SCADA Master Plan
List of Tables
Table 2-1. Summary of Visited Sites for the Water and Recycled Water Systems ...............................2-3
Table 2-2. Current PLC Hardware and Communications for Water and Recycled Water Systems .....2-8
Table 2-3. Current HMI Computer Software ............................................................................................2-9
Table 2-4. Current Radio Hardware .........................................................................................................2-9
Table 2-5. Sewer Lift Station PLC Hardware ........................................................................................ 2-13
Table 2-6. Current Cellular Monitoring Hardware ................................................................................ 2-14
Table 3-1. Site Visits –lessons learned ...................................................................................................3-7
Table 3-2. Site Visits –Additional Observations ......................................................................................3-7
Table 3-3. State of the Industry–Findings Summary ........................................................................... 3-12
Table 3-4. State of the Industry –Additional Observations ................................................................. 3-13
Table 3-5. Enterprise and Data Mapping –Findings Table .................................................................. 3-16
Table 3-6. Operations Shadowing –Findings Summary ...................................................................... 3-22
Table 3-7. Operations Shadowing –Additional Observations .............................................................. 3-22
Table 3-8. Levels of Automation–Findings Summary .......................................................................... 3-25
Table 3-9. SCADA Equipment and Space Needs –Additional Observations ...................................... 3-27
Table 3-10. SCADA Equipment Resource and Space Needs –Core Deficiencies and Desires ......... 3-32
Table 3-11. SCADA Equipment and Space Needs –Additional Observations .................................... 3-32
Table 4-1. Evaluation Scoring ..................................................................................................................4-5
Table 4-2. Evaluation Scoring ..................................................................................................................4-7
Table 4-3. HMI Software RFP Scores .......................................................................................................4-9
Table 4-4. HMI Software Demonstration Scores ................................................................................. 4-10
Table 4-5. HMI Software Final Scores .................................................................................................. 4-11
Table 4-6. PLC Hardware RFP Scores ................................................................................................... 4-12
Table 5-2. Design-Build Method Comparison ...................................................................................... 5-10
Table 5-3. Skill Set Requirements ........................................................................................................ 5-13
Table 5-4. Workforce Role Summary .................................................................................................... 5-14
Table 6-1. Desktop Radio Study List ........................................................................................................6-4
Table 6-2. Field Study Report Heading Descriptions ..............................................................................6-5
City of Carlsbad / CMWD SCADA Master Plan Table of Contents
vii
SC07221_FINAL_Carlsbad SCADA Master Plan
List of Abbreviations
AACE Advancement of Cost Engineering International
ANSI American National Standards Institute
AMR automated meter reading
AMI automated meter infrastructure
APCD Air Pollution Control District of San Diego
County
BC Brown and Caldwell
bps bits per second
CAP climate action plan
City City of Carlsbad
CM&I Construction Management and Inspection
CMSS computerized maintenance management
system
CMWD Carlsbad Municipal Water District
CWA San Diego County Water Authority
DB design-build
DBA database administrator
DBB design-bid-build
DCS Distributed Control System
EWA Encina Wastewater Authority
FCC Federal Communications Commission
GBPS gigabits per second
GHz gigahertz
GIS geographic information system
HDD hard disk drive
HMI human machine interface
I/O inputs and outputs
IEUA Inland Empire Utilities Agency
IOT internet of things
IP Internet protocol
IRWD Irvine Ranch Water District
ISA International Society of Automation
IT information technology
kbps kilobits per second
LIMS Laboratory Information Management System
MCC motor control center
MHz megahertz
MSA Master Services Agreement
N/A not applicable
NAS network attached storage
O&M operations and maintenance
OIT operator interface terminal
OT Operational Technology
OS operating system
PCS process control system
PLC programmable logic controller
PRV pressure reducing valves
RAID redundant arrays of independent disks
RIO remote inputs and outputs
RFP request for proposal
ROI return on investment
RTU remote telemetry unit
SCADA supervisory control and data acquisition
SDCWA San Diego County Water Authority
SI system integrator
SQL Structured Query Language
TDS total dissolved solids
TM technical memorandum
UPS uninterruptible power supply(ies)
VHF very high frequency
VPN virtual private network
WAN wide area network
viii
SC07221_FINAL_Carlsbad SCADA Master Plan
Executive Summary
Introduction, Objectives, and Approach
The City of Carlsbad (City) and the Carlsbad Municipal Water District’s (CMWD) current supervisory
control and data acquisition (SCADA) systems that provide monitoring and control of the water and
sewer systems has gradually grown over the years and includes a variety of equipment in the field of
varying age, with some equipment already at the end of its useful life. The current water/recycled
water SCADA system provides some level of remote controls and monitoring of the sites. The current
wastewater SCADA system only provides remote monitoring of sewer sites with no remote control.
Existing System Evaluation
Remote sites were surveyed to assess the current condition, performance, security, age, and support
of SCADA equipment. Each wastewater, water, and recycled water site is physically monitored
through local instruments, local control panels, and motor control centers (MCCs). Wastewater sites
are not capable of remote control and are only monitored through cellular communications to a web-
based system. Water and recycled water sites are monitored and controlled locally and remotely via
the local programmable logic controller (PLC). Sites with more advanced PLCs are capable of
additional local operator control and monitoring through hand switches, indicator lights, or Operator
Interface Terminal (OIT) nodes on the panel. At some sites, additional legacy controllers exist that are
abandoned in-place and still wired into the system, but not in use. Each local PLC on the
water/recycled water SCADA system communicates via radio network to the Human-machine
Interface (HMI) monitoring location at the CMWD building. The existing systems are at the end of
their useful life and require a complete upgrade.
Operational Needs and Deficiencies Assessment
Through a series of workshops and site visits, the City/CMWD identified the needs and deficiencies
of the existing system that must be incorporated in the new SCADA system. Activities included site
visits to other utility agencies, workshops to inform and gather data, operations shadowing for the
current system, and evaluation of staffing and space needs. The key objective of these activities was
to ensure all operational needs are identified and ensure the future SCADA system will provide
targeted improvements in areas of need. Findings were documented in this section to guide
technology selection and develop tasks for the implementation plan.
Standardization
To address the needs of the SCADA systems, requests for proposal (RFPs) were developed so that
the City/CMWD may standardize on HMI software and PLC hardware with a long-term contract.
Proposals from vendors and distributers were evaluated based on the established technical criteria
and long-term cost-competitiveness. Top vendors were invited to interview with the City/CMWD to
answer further questions about their proposal and demonstrate their product. Based on the
interviews and proposals, the final vendors were selected to provide the HMI software and PLC
Hardware for the city. This section of the Master Plan documents the selection process and provides
context for how the decision was made.
City of Carlsbad / CMWD SCADA Master Plan Executive Summary
ix
SC07221_FINAL_Carlsbad SCADA Master Plan
Implementation Plan
The implementation plan is broken down into the four separate phases to maintain an overall
organizational framework and manage task sequencing. Each phase builds upon the tasks
completed in previous phases. Phase 1 includes tasks needed to prepare for design and
improvements in Phases 2 and 3. Phase 2 includes design and construction for wastewater system
improvements and Phase 3 includes design and construction for potable water and recycled water
system improvements. Phase 4 includes an optional smart utility master plan and associated
implementation tasks to be considered upon completion of the first three phases. The long-term goal
of these improvements is to use the upgraded control system as a base to implement a smart utility
concept to integrate external data and software packages with the control system HMI to provide
better operational intelligence.
Communications Study
A field survey was performed to document the existing communication system hardware including
the type of communication, radio frequency, radio type, antenna direction, antenna heights, and
location. The radio desktop survey involved 60 sites (33 Potable, 11 Reclaim, 14 Wastewater, and 2
Operations). Seven master sites were designated, and the study was conducted between 23 and 26
GHz to develop a backbone for all other remote sites. Each remote site study was conducted at
unlicensed 900 MHz, 3.6 GHz, and 5 GHz bands. The best connectivity across the network was
found using the unlicensed 900 MHz band. Desktop study results will need to be confirmed via field
surveys prior to implementation.
1-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Section 1
Introduction, Objectives, and
Approach
1.1 Introduction
The City of Carlsbad (City) and the Carlsbad Municipal Water District’s (CMWD) current supervisory
control and data acquisition (SCADA) system that provides monitoring and control of the water and
sewer systems has gradually grown over the years and includes a variety of equipment in the field of
varying age, with some equipment already at the end of its useful life. This is typical for many
municipalities where the control systems grew as accessories in response to the growth of the
process systems.
The existing water system for the City/CMWD is comprised of 8 reservoirs, 4 pump stations and 75
pressure regulating sites, as well as a hydroelectric facility. The existing recycled water system is
comprised of 3 reservoirs, 3 pump stations, and 4 pressure regulation stations. The water system
currently utilizes Opto22 based equipment at the sites to collect process data and relay it back to the
main operations center via cellular modems. At the main office, there is a stand-alone operator
interface system with no current backup or redundancy in place.
The existing wastewater system for the City/CMWD has 12 active lift station sites that are currently
monitored using a Mission based SCADA platform that provides information back to the City via
cellular modems. This Mission based SCADA system utilizes a web-based graphic user interface to
provide information to the City/CMWD’s users. The wastewater system also currently utilizes about
30 smart manhole covers that have been strategically placed to provide a second backup and alarm
at high levels in critical areas. As a backup to the primary system (Mission), phone based autodialers
(Verbatim) are used at every site to send critical alarms to on-call staff.
1.2 Vision Statement
The City/CMWD have developed the following vision statement to guide project goals and maintain a
well-defined and consistent final vision for the Master Plan project:
“To have a uniform, fully integrated SCADA system that provides utility-wide
enterprise business intelligence to optimize operations and have the flexibility for
growth and adaptability in the future.”
1.3 Approach
The City/CMWD has requested Brown and Caldwell (BC) perform an assessment of their existing
SCADA system and develop an overall SCADA Master Plan. The Master Plan is intended to define the
current state of the system, identify needs and deficiencies, analyze alternatives for improvements,
and present a recommended implementation path to provide a foundation for future improvements
and use. The Master Plan is broken down into four phases to address each of these specific goals.
The following are the phase-specific approaches used in each of the phases of the Master Plan.
City of Carlsbad / CMWD SCADA Master Plan Section 1
1-2
SC07221_FINAL_Carlsbad SCADA Master Plan
1.3.1 Existing System Evaluation
Section 2 addresses the first phase of the Master Plan; reviewing the existing SCADA system and
identifying the components, architecture, and condition of the equipment. An important shadowing
phase will be implemented to understand how Operations uses the SCADA system. Other City/CMWD
personnel were shadowed to understand their roles and how they currently use or could use data
from the SCADA system.
1.3.2 Operational Needs and Deficiencies Assessment
Section 3 addresses the second phase of the Master Plan; assessing the future use and needs of
the SCADA systems. BC met with individuals responsible for operating and maintaining the potable
and recycled water systems and the sewer system to develop an understanding of how each of the
users interact, utilize, and maintain the current SCADA system. Interviews were conducted with
Operations staff to document the difficulties they experience in day-to-day operations and what
improvements they would want to see in the future. Workshops were conducted with the core team
and other staff who use SCADA data to document what information is important to them and what
future data or information they would find useful.
1.3.3 PLC and HMI Standardization
Section 4 addresses the third phase of the Master Plan; selecting the best technology to address the
needs of the SCADA systems. BC developed requests for proposal (RFPs) so that the City/CMWD may
standardize the HMI software and PLC hardware to be used at all sites in the water, recycled water
distribution and sewer collection systems. Proposals were reviewed and scored based on the scoring
system detailed in the RFPs. The top vendors were invited to interview with the City/CMWD to answer
further questions about their proposal and demonstrate their product. Based on the interviews and
proposals, the final vendors were selected to provide the HMI software and PLC Hardware for the
City. With the HMI and PLC now standardized, the City/CMWD will be able to focus on the fourth
phase of the Master Plan, implementation planning.
1.3.4 Implementation Plan
Section 5 addressed the fourth phase of the Master Plan; developing a project and phasing
methodology to address the challenges and deficiencies noted in Phases 1 and 2 of the Master Plan.
Implementation projects have been developed and categorized into phases based on immediate
needs and sequencing requirements. The four implementation phases are as follows:
1. Foundational Structures
2. Immediate Improvements/Needs
3. Core System Upgrades
4. Future Improvements
Each phase consists of a series of tasks developed to meet the needs of the City/CMWD. Each task
has an estimated cost and scheduled duration that can be used to determine cost estimates and
schedules for the implementation plan.
City of Carlsbad / CMWD SCADA Master Plan Section 1
1-3
SC07221_FINAL_Carlsbad SCADA Master Plan
1.3.5 Communications Study
Section 6 provides a communication study for the city/CMWD’s radio network. This section
documents a software study of the existing and potential radio links needed for the radio
communications system. Multiple frequencies were considered for each of the remote site links
during the study to determine the optimal frequency band for use across the radio network.
Alternative communication methods were evaluated and may be considered as additional options if
any remote site radio links are found to not be feasible during the future field survey.
2-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Section 2
Existing System Evaluation
2.1 Introduction
This section is intended to document the City/CMWD’s existing SCADA system to assess the current
condition, performance, security, age, and support. The baseline conditions of the City/CMWD’s
SCADA systems are documented to provide an understanding of the current state and where
improvements need to be made in the future.
2.2 Approach
For the first phase, identifying system components, 12 sites were to be visited over 2 days to
effectively evaluate the existing SCADA system. During the 2-day site visits, remote sites were
surveyed to assess the current condition, performance, security, age, and support of SCADA
equipment. The data were collected within a smart phone-based application tool and provided as
individual field survey reports. Three main segments, along with their supporting structures that
make up a SCADA system, were surveyed:
• Local Automated Control and Monitoring;
• Communications; and
• Operator Access.
The three main segments, as indicated in Figure 2 1 but not including the field equipment segment,
were selected as the three major components of a SCADA system. Each of the segments will typically
have a different lifecycle duration, allowing a survey of the three different segments to capture the
current state of the entire SCADA system. Each of these main SCADA system segments, along with
their supporting structures, were evaluated based upon security, redundancy, reliability, support, and
future expandability.
City of Carlsbad / CMWD SCADA Master Plan Section 1
2-2
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 2-1 Levels of Technology Aging
2.3 Existing Water and Recycled Water SCADA System Overview
This section provides an overview of existing water and recycled water system architecture, condition
assessment and data collection, and external data sources.
2.3.1 Water and Recycled Water System Architecture
The existing water system is comprised of 4 turnouts, 8 reservoirs, 4 pump stations, and 77
pressure-regulating sites, as well as a hydroelectric facility. The turnouts (sources of potable water)
are connections to San Diego County Water Authority (SDCWA). CR3, CR4, and CR6 (previously
known as CR1) are connected to SDCWA via the Tri Agency Pipeline. CR2 is connected to VAL 2 from
pipelines 1 and 2 through a connection to Vallecitos Water District. The existing recycled water
system is comprised of three reservoirs, three pump stations, and five pressure-regulation stations.
The water and recycled water systems currently utilize OPTO 22-based equipment at the sites to
collect process data and relay it back to the main operations center via Ethernet radios. At the main
office at the CMWD building there are two computers set up in a redundant configuration running
Wonderware InTouch human machine interface (HMI) software.
A summary of key water and recycled water system sites visited are shown below in Table 2-1. A full
list of sites is included in Appendix A: List of Sites. Details of the visited sites are included in the
detailed report provided in Appendix B: Field Survey Data Reports.
City of Carlsbad / CMWD SCADA Master Plan Section 1
2-3
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 2-1. Summary of Visited Sites for the Water and Recycled Water Systems
Site Name Site ID Site Type System Make Model Radio
Communications
Bressi WPS9 Booster Station Potable OPTO 22 SNAP PAC Ethernet
Maerkle Booster WPS7 Booster Station Potable OPTO 22 SNAP PAC Ethernet
Maerkle Hydro-Electric WR8 Hydro Electric Potable OPTO 22 SNAP PAC Ethernet
Avenida Encinas PRS70 PRV Recycled OPTO 22 SNAP PAC Ethernet
Ayres PRS21 PRV Potable OPTO 22 SNAP PAC Ethernet
Carlsbad 3 PRS73 Turnout Potable OPTO 22 SNAP PAC Ethernet
D Tanks and Pump Station
MCP-1 WPS6 Booster
Station/Reservoir Potable OPTO 22 SNAP PAC Ethernet
D Tanks and Pump Station
MCP-2 WPS6 Booster
Station/Reservoir Recycled OPTO 22 SNAP PAC Ethernet
The existing SCADA system architecture diagram for the water and recycled water system as shown
on the following page has not been field-verified. These data were collected from the Water
Department SCADA & Security Network Analysis Final Report, June 12, 2012 and feedback from
CMWD staff.
2.3.1.1 Control Philosophy
The water and recycled water SCADA system provides local automated control and remote
monitoring and control. Each facility is physically monitored through local instruments, local control
panels, and motor control centers (MCCs) which are monitored and controlled via the local
programmable logic controller (PLC). Each local PLC communicates via radio network to the HMI
monitoring location at the CMWD building. Figure 2 1 and Figure 2 3 below present a general
overview of this structure. Figure 2 4 illustrates the water and recycled water control system data
flow.
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-4
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 2-2. Water and Recycled Water System Architecture Diagram (1 of 2)
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-5
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 2-3. Water and Recycled Water System Architecture Diagram (2 of 2)
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-6
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 2-4. Water and Recycled Water Control System Data Flow
2.3.1.1.1 Local Automated Control
The PLCs utilize a variety of input and output (I/O) modules to interface with the local monitoring and
control devices. Software logic within the PLC provides signal conditioning, monitoring, alarm
generation, and control logic to interface with the I/O modules.
Each PLC currently utilizes ethernet ports to provide high speed and throughput communication on
the local network and with the radio system.
2.3.1.1.2 Remote Monitoring and Control
The PLCs at the remote sites communicate over the radio to the HMI system at the main office.
Through these communications, the HMI system presents monitor status and values and
annunciates alarms based on equipment conditions. Through the HMI client, the operator can adjust
available setpoints and manually command available equipment functions.
2.3.1.2 Communications: Radio Communications Architecture
The radio communications system consists of a single radio network that transmits remote site
monitoring and control information directly to and from the division office HMI location. The system
architecture uses a polled method, where the remote site radio communicates directly with the end
network connection location, or node, for monitoring and controls communications.
2.3.1.3 HMI System
CMWD utilizes a computer-controlled monitoring and data collection system that provides operators
with a graphical HMI into the control system. The CMWD HMI system is located at the CMWD building
and provides monitoring of the remote connected sites. It consists of a single SCADA server and two
view nodes (computers). There is no backup for the SCADA server computer. The SCADA server is
connected to the remote sites via the radio system. Figure 2 5 presents a high-level overview of the
HMI architecture. The radio system is an unlicensed system using Ubiquiti Ethernet radios.
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-7
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 2-5. Existing HMI Architecture
The SCADA server hosts applications such as I/O drivers, alarming, and historian information. There
are two view nodes or clients on the SCADA workstations. The workstations are the interface
between Operators and the SCADA system. Monitoring and control is accessed from the SCADA
workstations. The HMI system utilizes Wonderware InTouch software for graphics presentation and
development, providing a flexible platform that has been specifically configured for the CMWD
operators to monitor and control remote sites.
2.3.1.3.1 Backup
The CMWD has no running backup in place for the current HMI workstation. The workstation is
provided with an uninterruptable power supply capable of supporting the system for 30 minutes of
lost power.
2.3.1.3.2 Alarming
The computers run separate dedicated software to provide alarming annunciation to the operators.
This software, SCADAlarm, monitors each of the individual alarm registers within the HMI application
for change and allows the operators to receive notifications remotely. Currently, the system will
provide a voice call to the operator with the alarm message if an alarm is unacknowledged or in an
alarm state for more than 5 minutes. SCADAlarm software is provided by Invensis (Wonderware
software product) and is no longer supported by Invensis.
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-8
SC07221_FINAL_Carlsbad SCADA Master Plan
2.3.2 Water and Recycled Water System Condition Assessment and Data Collection
BC staff visited six of the existing water and two recycled water system sites in October 2017 to
gather data for this Master Plan and evaluate the current condition and performance. A detailed
report for each site, including the collected data, system evaluation, and site photographs, is
provided in Attachment B.
2.3.2.1 Programmable Logic Controllers
All PLCs used in the CMWD water and recycled water system are OPTO 22 SNAP PACs. For sites
requiring more I/Os, multiple OPTO 22 PLCs are linked together using an ethernet connection. All
communication from the PLCs is communicated over ethernet through a local network switch to a
radio and transmitted directly back to the main office. Some control of the system is available via
SCADA at the main office and local operator interface terminal (OIT) nodes at the sites. Local control
of the system is available through hand switches on the remote telemetry unit cabinet and the MCC.
Table 2 2 presents the PLC hardware and communications methods at each of the water system
sites included in the field survey.
Table 2-2. Current PLC Hardware and Communications for Water and Recycled Water Systems
Site Name Make Model Radio
Communications
Local
Communications
Bressi OPTO 22 SNAP PAC Ethernet None
Maerkle Booster OPTO 22 SNAP PAC Ethernet None
Maerkle Hydro-Electric OPTO 22 SNAP PAC Ethernet None
Avenida Encinas OPTO 22 SNAP PAC Ethernet None
Ayres OPTO 22 SNAP PAC Ethernet None
Carlsbad 3 OPTO 22 SNAP PAC Ethernet None
D Tanks and Pump Station MCP-1 OPTO 22 SNAP PAC Ethernet None
D Tanks and Pump Station MCP-2 OPTO 22 SNAP PAC Ethernet None
2.3.2.2 HMI System
The HMI system is displayed at the control room at the CMWD building and consists of a SCADA
server and two view nodes. The computer specifications are listed below:
• Wonderware Server
− Manufacturer: Hewlett Packard
− Model HP Pavilion
• Wonderware View Nodes (Quantity 2)
− Manufacturer: Hewlett Packard
− Model: HP EliteDesk 800 G1 TWR
− Processor: Intel 13-4130 at 3.40 gigahertz
− Ram: 8.00 gigabytes
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-9
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 2 3 presents information on the current software used for the HMI system on the workstation
computer.
Table 2-3. Current HMI Computer Software
Function Name Version Notes
Operating System Windows XP Professional Main operating system platform for the computer.
HMI Client and Engineering Workstation
Wonderware InTouch Used as the main HMI client and engineering development for the HMI Communications Protocol
Converter
Invensys/Wonderware FSGateway
OPC Server OPTO Controller OPC Data Access Server
Alarm Server
SCADAlarm Remote alarm notifications via phone call to operators. This software is a legacy product and is no longer supported by Wonderware/Invensis.
2.3.2.3 Network
2.3.2.3.1 Radio Communications – Hardware
The radio communications system utilizes Ubiquiti powered-over-ethernet radios and antennas for
communication with the remote sites. The radios utilize a high-frequency radio band to transmit data
and communicate with the system via ethernet connection to the PLC. These radios utilize an
unlicensed radio frequency; therefore, no permitting is required.
2.3.2.3.2 Site Radio Hardware
The specific radio platform(s) used at sites visited is presented in Table 2 4 below.
Table 2-4. Current Radio Hardware
Site Name Make Communications Protocol
Bressi Ubiquiti Ethernet
Maerkle Booster Ubiquiti Ethernet
Maerkle Hydro-Electric Ubiquiti Ethernet
Avenida Encinas Ubiquiti Ethernet
Ayres Ubiquiti Ethernet
Carlsbad 3 Ubiquiti Ethernet
D Tanks and Pump Station MCP-1 Ubiquiti Ethernet
D Tanks and Pump Station MCP-2 Ubiquiti Ethernet
2.3.3 Water and Recycled Water System External Data Sources
Data from External Sources will need to be incorporated into the new SCADA system. Some of these
external data sources include AMI, Encina Wastewater Authority (EWA) flows, the Carlsbad Water
Recycling Facility recycled water, Vallecitos Water District for CR2 SDCWA connection, Vallecitos
Water District/Mahr Reclaimed Water Reservoir for recycled water, and SDCWA for recycled water.
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-10
SC07221_FINAL_Carlsbad SCADA Master Plan
2.4 Existing Sewer SCADA System Overview
This section discusses existing sewer system architecture, condition assessment and data collection,
and external data sources.
2.4.1 Sewer System Architecture
The existing wastewater system has 12 active lift station sites that are currently monitored using a
Mission Communications SCADA platform that provides information back to the City via cellular
modems. This Mission Communications based SCADA system utilizes a web-based graphic user
interface to provide information to City users. As a backup to the primary system (Mission), phone-
based autodialers (Verbatim) are used at critical sites to send critical alarms to on-call staff.
The existing SCADA system architecture diagram for the sewer system as shown on the following
Figure 2 6 has not been field-verified.
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-11
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 2-6. Sewer System Architecture Diagram
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-12
SC07221_FINAL_Carlsbad SCADA Master Plan
2.4.1.1 Control Philosophy
The City sewer SCADA system provides local automated control and remote monitoring. Each facility
is monitored and controlled through local instruments, control panels, and MCCs controlled via the
local PLC.
Figure 2 7 presents a general overview of this structure.
Figure 2-7. Sewer Control System Data Flow
2.4.1.1.1 Local Automated Control
The PLCs utilize a variety of I/O modules to interface with the local monitoring and control devices.
Software logic within the PLC provides signal conditioning, monitoring, alarm generation, and control
logic to interface with the I/O modules.
The lift station PLCs currently utilize serial communication to provide low-speed, low-throughput
communication with the cellular monitoring system and the alarm dialer.
Automated control of the sewer lift stations is provided by wetwell level controllers (i.e., E.G. Controls
DigiGage 2300 or the Fluid Solutions MicroMAC 2300). The level controllers use bubbler-type level
sensors to start, stop, and cycle the lift station pumps. In addition to the bubbler level sensors,
submersible and ultrasonic-type level sensors have been added for redundant level measurement.
2.4.1.1.2 Remote Monitoring
Through the Mission CPN-625 cellular monitoring system connected to the PLC, the site
communicates over cellular data to the monitoring system hosted by Mission Communications.
Mission Communications provides a web-based monitoring interface that allows the system to be
monitored from an internet connection. This is a monitoring system only; no remote control or
setpoints are possible with any of the sewer lift stations.
As a backup to the Mission cellular monitoring system, an on-site RACO Verbatim Alarm Dialer
provides critical alarm notifications from the PLC as pre-recorded phone messages.
2.4.1.2 Communications: Cellular Data Communications Architecture
The remote sites communicate back to the HMI system directly using a Mission CPN-625 cellular
monitoring system that sends data to a hosted webservice that can be accessed from any internet-
connected computer.
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-13
SC07221_FINAL_Carlsbad SCADA Master Plan
2.4.1.2.1 HMI System
Mission Communications provides a web-based monitoring interface that allows the system to be
monitored from an internet connection. The Mission Communications system provides monitoring
only and does not provide any system alarming.
2.4.1.2.2 Alarming
Each remote site has a Verbatim remote dialer as backup for alarming at the lift station sewer sites.
Digital inputs are wired directly to the Verbatim alarm system. When an alarm is triggered, the
Verbatim autodialer, dials a preprogrammed set of phone numbers until the alarm is acknowledged.
2.4.2 Sewer System Condition Assessment and Data Collection
BC staff visited six of the existing sewage system sites in October 2017 to gather data for this Master
Plan and evaluate the current condition and performance. A detailed report for each site that
includes collected data, system evaluation, and site photographs is located in Attachment B.
2.4.2.1 Programmable Logic Controllers
A variety of PLCs are used for the local control and monitoring of the City sewer lift stations. Some of
the PLCs are simply used to pass monitoring signals on to the cellular monitoring system and
autodialer. Sites with more advanced PLCs are capable of additional local operator control and
monitoring through hand switches, indicator lights, or OIT nodes on the panel. At some sites,
additional legacy controllers exist that are abandoned in-place and still wired into the system, but not
in use.
Table 2-5 presents each of the surveyed site PLC hardware and communications methods.
Table 2-5. Sewer Lift Station PLC Hardware
Site Name Site ID Make Model Radio
Communications Make2 Model3 Communication
s Protocol
Poinsettia SLS15 Dutec IO Plexer Serial Mission CPN-625 Serial
El Fuerte SLS21 Allen Bradley SLC 5/03 Serial Mission CPN-625 Serial
Cannon SLS17 Allen Bradley SLC 5/03 Serial Mission CPN-625 Serial
Home Plant SLS27 OPTO 22 B3000-B Serial Mission CPN-625 Serial
Knots SLS16 OPTO 22 SNAP-PS5 Serial Mission CPN-625 Serial
Batiquitos SLS4 Dutec IO Plexer Serial Mission CPN-625 Serial
2.4.2.2 HMI System
Currently, the HMI system can be accessed remotely through any internet-connected computer by
logging in to the Mission Communications system. The HMI provides system data for monitoring
purposes; however, no control of the system is available.
2.4.2.3 Network
2.4.2.3.1 Site Cellular Monitoring Hardware
The specific cellular monitoring platform(s) and communication protocols used at each site is
presented in Table 2-6 below.
City of Carlsbad / CMWD SCADA Master Plan Section 2
2-14
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 2-6. Current Cellular Monitoring Hardware
Site Name Site ID Make Model Communications
Protocol
Poinsettia SLS15 Mission CPN-625 Serial
El Fuerte SLS21 Mission CPN-625 Serial
Cannon SLS17 Mission CPN-625 Serial
Home Plant SLS27 Mission CPN-625 Serial
Knots SLS16 Mission CPN-625 Serial
Batiquitos SLS4 Mission CPN-625 Serial
2.4.3 Sewer System External Data Sources
The wastewater system also currently utilizes about 30 smart manhole covers that have been
strategically placed to provide a second backup and alarm at high levels in critical areas. These
devices sense high level and notify on-call personnel of high-level conditions within the sewer
collection system.
The City currently uses six flow meters from upstream agencies and four flow meters on the influent
lines of the Encina Water Pollution Control Facility to determine total wastewater flow generated
within the city. This data is used by the EWA for billing and informational purposes. The flow data can
be downloaded from a web-based graphical information system in addition to monthly flow summary
reports provided by EWA.
3-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Section 3
Operational Needs and
Deficiencies Assessment
This section will document the steps that have been taken to identify the needs and deficiencies
based on the existing system and future objectives that should be incorporated in the new SCADA
system.
3.1 Introduction
The second phase of the Master Plan is to identify the needs and deficiencies based on the existing
system and future objectives that should be incorporated in the new SCADA system. This section
documents activities used to identify needs and deficiencies, including site visits to other Utilities,
workshops used to inform and gather data, operations shadowing to understand how the systems
are currently operated and identifying needs, staffing for a new SCADA system, and space needs. All
the findings and future objectives will be summarized in section 3.3 of the Master Plan. This section
references “the team” and “stakeholders” in multiple places in the document. “The team” is the
Core team of City/CMWD staff who are fully engaged in this Master Plan. The “stakeholders” are
either the Steering Committee made up of senior staff or additional staff engaged in the Master Plan
as needed.
As the team looks at the needs of the overall SCADA system, the key objectives are ensuring
operations staff have all the needs met for current and future use and ensuring the needs of
enterprise users are met. The Master Plan will consider the needs of all users by ensuring a strong
foundational SCADA system that can grow to meet future automation needs.
3.1.1 Approach
City staff went to visit other Utilities that had gone through the process of either expanding or
completely changing their SCADA systems in the recent past. The intent was to learn how they went
through the process and the possible pitfalls to watch out for as this team go through the same. City
staff visited the following Utilities:
• Irvine Ranch Water District (IRWD)
• Inland Empire Utilities Agency (IEUA)
• City of Oceanside
The site visits were followed by a state of the industry workshop to provide a big picture of what
challenges other similar utilities are facing, current technologies they are using, and what they’re
doing with these technologies to respond to these challenges. The state of the industry workshop
provided the team information on how other utilities facing similar challenges are leveraging
technology to find solutions.
This was followed by an interactive data mapping workshop for the enterprise needs assessment.
This workshop was designed for full participation by each of the stakeholders from different
departments within the City/CMWD who rely on data from other sources. The intent was for the team
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-2
SC07221_FINAL_Carlsbad SCADA Master Plan
to understand how data needs impact the whole organization and may not be obvious to a single
group.
BC completed the evaluation and discovery by spending 2 days shadowing operations staff to
observe and attain a third-person perspective of how operations staff went through their daily
routines, how operations staff interfaced with the existing SCADA system, and where technology
could be leveraged.
3.2 Operational Needs
This section will provide details for all the activities that have been listed above It will include staffing
information and space needs for a new SCADA system.
3.2.1 Site Visits
City staff visited three separate agencies to review and discuss their SCADA systems. The agencies
visited were the Irvine Ranch Water District, Inland Empire Utilities Agency and the City of Oceanside.
In these visits, discussions were held to learn about each agency’s selection process for the
technologies selected, and the lessons learned through the upgrade process. For each of the sites
visited, the TM will document available details for support, standardization, communications,
enterprise connectivity, cyber security and network planning, migration and delivery methods, and
staffing.
3.2.1.1 Irvine Ranch Water District (IRWD)
A site visit to IRWD was set up for City/CMWD personnel on January 22, 2018. IRWD provided a
presentation of their district before moving into a discussion about their initial needs, how they
addressed those needs, how they selected the technology suited to address their needs, and
“lessons learned” from the process.
IRWD is very spread out physically with many pump stations, reservoirs, lift stations, stormwater, and
urban runoff sites connected to their SCADA system. To upgrade their SCADA system, IRWD
underwent a master planning process which allowed them to identify their major needs to be
addressed and evaluate the best solutions. IRWD selected Wonderware for their HMI and Schneider
Electric’s Modicon PLCs for their SCADA system.
3.2.1.1.1 Support
One of the key SCADA software selection criteria IRWD used was that the selected system would be
widely supported, and they would not be limited from a support standpoint. They selected a system
that would continue to be enhanced and actively supported by the manufacturer, fulfilling their long-
term support needs.
3.2.1.1.2 Standardization
IRWD has standardized the main HMI system on the Wonderware System Platform and standardized
the field on Schneider Electric’s Modicon PLCs. IRWD recommends using as much standard off-the-
shelf software as possible to avoid the need for additional scripting.
IRWD has developed standards for their HMI programming and PLC programming. IRWD system
administrator believes that standards that are designed to be too rigid can end up adding costs
instead of reducing them due to additional customization or over-design. By standardizing from the
beginning, elements of the SCADA system, any system maintenance, programming, replacement or
expansion becomes easier and more cost-effective. When applying standards to packaged systems,
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-3
SC07221_FINAL_Carlsbad SCADA Master Plan
it is most important to focus on the data exchange between the packaged system and the SCADA
system to ensure easy integration without the need for scripting.
3.2.1.1.3 Communications
IRWD developed a licensed 300 MHz radio communications backbone for their SCADA system. All
remote sites are connected over this backbone. As a backup to their SCADA system, IRWD uses
Mission Controls for monitoring specific parts of the system in addition to the call-out system they
have in place. The communications backbone creates a strong foundation for the overall network for
now and future growth.
3.2.1.1.4 Enterprise Connectivity
IRWD does not currently have a fully integrated enterprise system but are taking steps towards
developing one. IRWD currently uses Hach WIMS as a centralized data system to generate SCADA
data reports. Additional data is collected during field rounds using DoForms, a cloud-based software
capable of automatically loading the collected data into the main database. IRWD is now working to
transition to a new Maximo computerized maintenance management system (CMMS) that they will
be able to integrate with their SCADA towards more enterprise connectivity. This added connectivity
will help centralize more data and allow for better coordination of day-to-day operations with long-
term asset management.
3.2.1.1.5 Cyber Security and Network Planning
From their experience upgrading the SCADA system and associated network, IRWD recommends
having Information Technology (IT) involved in the core team working on the upgrade. Involvement of
IT allows for coordination with the business network while maintaining the separation from the
process network vital for cyber security. Within the process network, planning and network
segmentation will also allow for easier maintenance. With the rising need for stronger cyber security,
IRWD also recommends the use of two-factor authentication for the network to prevent unauthorized
access.
3.2.1.1.6 Migration and Delivery Methods
IRWD went through a detailed process to see what the best technology was for SCADA systems a few
years ago. The conclusion of the exercise showed that upgrading the system they had was the best
financial and technical option for them.
Some key insights and/or tips they shared with our team were:
• Require the manufacturer to provide training onsite
• For system integration and upgrades, require the system integrator (SI) to maintain licensing
costs through construction and 2 to 3 years beyond that
• Confirm the selected SI can do the work contracted
• Confirm sufficient in-house support for the overall installation
• When looking at different manufacturers, ensure the uptime ratio meets standards
3.2.1.1.7 Staffing
IRWD has an automation manager for their SCADA system, a supervisor, two programmers, and
three technicians. They are working on cross-training to help staff become more versatile. Although
they have a separation between IT and Operational Technology (OT), they recommend having a close
working relationship.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-4
SC07221_FINAL_Carlsbad SCADA Master Plan
IRWD doesn't have a dedicated control room; instead, operations use a decentralized approach to
operator control. Operations staff have cubicles in the operations building and can monitor and
control the system using a mobile platform on laptops and tablets. IRWD is now considering adding a
main control room, as well as additional door security to control rooms.
3.2.1.2 Inland Empire Utilities Agency (IEUA)
A site visit to IEUA was set up for City personnel on January 23, 2018. IEUA provided a
question/answer session followed by a walkthrough of the control room at RP-5, as well as a tour of
the Carbon Canyon facility server room and control room.
The IEUA facilities are very spread out physically, covering an area of 242 square miles with
wastewater treatment facilities, lift stations, pump stations, recycled water, and groundwater
recharge sites. The facilities are controlled by a SCADA system that covers the northern and southern
sections of the service area. Redundancy in the SCADA system is provided by servers in the north
and in the south, such that one server system is in control of the entire facility at any time and if it
fails, the other server takes over. To upgrade their SCADA system, IEUA went through a master
planning process which allowed them to identify major needs to be addressed and evaluate the best
solutions. Through their selection process IEUA chose the Rockwell PlantPAx solution for controllers
and HMI.
3.2.1.2.1 Support
A critical issue IEUA faced leading into their master plan was the limited support of their Invensys
Foxboro Distributed Control System (DCS). IEUA could not find SI’s to support the programming
needs of the system and were subjected to unpredictable cost hikes by the Invensys Foxboro support
services. IEUA prioritized selecting a system that would have strong local support from the supplier
and multiple system integrators to meet their long-term support needs.
3.2.1.2.2 Standardization
During their master plan, IEUA evaluated potential vendors to develop a short-list of vendors to
review in detail. The detailed evaluation process was carried out by IEUA staff to make a final
decision. Through the selection process, Rockwell Automations hardware/software was chosen to
standardize the control system to meet the support needs of IEUA. By selecting the HMI and PLC
from the same manufacturer and using programming standards provided by the manufacturer, IEUA
reduced the effort required in development and maintenance of standards. To take full advantage of
all the features of the PlantPAx system, IEUA was intent on using Rockwell Automation Trained SI’s.
The SIs needed to be recognized by Rockwell Automation as having the right proficiency, ensuring
programming standards are setup from the beginning. This proved to be a little challenging 5 years
ago but is no longer an issue. IEUA negotiated a long-term service and pricing agreement with
Rockwell Automation for a 10-year term. The HMI graphics standards developed by IEUA were based
on the High-Performance HMI methodology.
3.2.1.2.3 Communications
To address the communication needs of such a large, distributed system, IEUA developed their own
radio communications backbone for the SCADA system using licensed 300 MHz microwave radios to
create a backbone ring and a foundational communications network. The process to obtain the
Federal Communications Commission license was long and meticulous.
The IEUA SCADA can be accessed remotely over a virtual private network (VPN) by any on-call
operators, automation technicians, and maintenance staff using laptops. In addition to the remote
SCADA access, any critical alarms are sent out to staff through a software-based call-out dialer
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-5
SC07221_FINAL_Carlsbad SCADA Master Plan
system (WIN-911) and a backup cellular radio calling system (RACO). IEUA’s analysis results
indicated Rockwell’s web-based interface was poor and could not be used satisfactorily with the
iPads. These issues were mitigated with the use of laptops with VPN connectivity.
3.2.1.2.4 Enterprise Connectivity
IEUA currently uses Rockwell’s Factory Talk VantagePoint software to generate SCADA data reports
and connect the SCADA data to the Laboratory Information Management System (LIMS). An
enterprise historian has been set up in the demilitarized zone (DMZ) as part of their cyber security.
In the future, IEUA hopes to address the need for increased business connectivity with their SCADA
system. By connecting the data collected by SCADA to the IEUA business systems, efficient analysis
of the data can provide the ability to make better-informed business decisions. For now, the
additional connectivity has been put “on the back-burner” until all sites have been converted to the
new SCADA system. IEUA is working towards enterprise level integration.
3.2.1.2.5 Cyber Security and Network Planning
IEUA’s automation manager mentioned they have completed cyber security checks and were in the
process of doing a detailed SCADA system penetration test used to identify weaknesses in the
security. There is a shift in focus towards understanding the balance of cyber security with increased
data access and technology use with emphasis being placed on security.
3.2.1.2.6 Migration and Delivery Methods
The process IEUA envisioned has taken longer than anticipated, and they are currently half-way
through the 10-year long-term system support contract. IEUA used Design-Bid-Build for the first
phase and has moved to a Design-Build for the second phase project migration since the first phase
took longer than desired. IEUA stressed the importance of documentation for control panels, wiring,
and control strategies. During the IEUA construction process, sequencing requirements and plans
were essential. Coordinating supplemental or filler work for any unplanned or unscheduled
stoppages was necessary. IEUA has a full-time inspection staff member, specialized in construction
management, and a third-party inspector who worked on the whole process. Server and control
rooms at Carbon Canyon were undersized; it was highly recommended to obtain sufficient space and
adequate temperature control for these rooms to accommodate any expansion.
3.2.1.2.7 Staffing
IEUA automation staff consists of eight people. Staff were trained by setting up on-site training with
Rockwell. They have an automation manager, supervisors, and technical staff.
3.2.1.3 City of Oceanside
The City project manager set up a site visit to the City of Oceanside for staff in January 2018. The
City of Oceanside has a water filtration facility (potable water), groundwater purification facility
(desalter), two wastewater treatment facilities, 77 remote sites for pump stations, lift stations,
reservoirs, and pressure regulating stations. Oceanside has recently gone through a SCADA upgrade
project and were willing to share their experiences through the process. In January 2016, the city
council approved construction contracts worth $8.7M of SCADA upgrades to all their facilities. The
City of Oceanside is just north of the City of Carlsbad and is of similar size.
3.2.1.3.1 Support
The City of Oceanside had entered into a long-term contract with a system integrator to ensure long-
term support. Outside of the long-term contract, system integrators capable of supporting the City of
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-6
SC07221_FINAL_Carlsbad SCADA Master Plan
Oceanside’s Wonderware ArchestrA HMI system are readily available in the area if necessary. The
city staff have had previous success with the following Wonderware integrators:
• TSI (on current upgrade project)
• Tesco
• San Diego Distributor for Wonderware
• Enterprise Automation
• Trimax
3.2.1.3.2 Standardization
Oceanside’s SCADA system HMI is based on the Wonderware ArchestrA System Platform. The system
is installed on virtual servers with an ACP Thinmanager for the view clients. Win-911 autodialer is the
alarming software used for alarm notification. Overall, the City of Oceanside is happy with
Wonderware system functionality. Representatives of the city did express concern to the undesired
price of upkeep and the added components of the Wonderware system.
The City of Oceanside has an installed base of Schneider Electric Modicon PLCs. They decided to
keep these and standardize on new processors that are Unity capable. The three main facilities had
Modicon Quantum PLCs that were upgraded to have unity capable processors. Original programming
for the PLCs was converted for Unity and adjusted as appropriate for new functions and frames. The
new PLCs support Modbus-TCP protocol over Ethernet communication. These sites will receive fiber
upgrades or new fiber for a plantwide communication network. The plant upgrades will also include
PLC I/O signals for improved control and monitoring. The 77 remote sites have older versions of the
Modicon platform, predominantly Modicon Compact and Micro PLCs, and are being upgraded to
Modicon M340s (project is ongoing).
3.2.1.3.3 Communications
The City of Oceanside has a microwave communication backbone. The microwave backbone also
ties into a fiber Wide Area Network (WAN) maintained by IT. Users have permissions set up based on
their assigned security login; this determines the level of access to the appropriate system functions.
The remote sites are getting a new radio network, with redundant radios at the six critical repeater
sites, and cellular modems at the difficult sites that are not radio friendly. The radios and cellular
modems will replace the aging and difficult to maintain leased telephone line communication
network.
3.2.1.3.4 Enterprise Connectivity
The City of Oceanside currently uses virtualized servers. Oceanside has integrated CMMS using
Lucity with their SCADA data sources. Oceanside is working toward enterprise level integration.
3.2.1.3.5 Cyber Security and Network Planning
Cyber security and network planning information is not available.
3.2.1.3.6 Migration and Delivery Methods
The estimate for the work has gone from $4 million to $8 million (the construction contract alone
was for $8.7M). City of Oceanside as-built documentation was not well maintained; therefore, they
recommended identifying all existing I/O plus any future I/O expected to minimize change costs.
They also recommended identifying the severity of alarms and incorporating this into the standards
documentation.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-7
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.1.3.7 Staffing
The City of Oceanside emphasized the importance of having a program manager/network manager
and cross-training staff to maintain appropriate staffing. The City of Oceanside used a third-party
contractor for their staff management, which enabled them to bring in external staffing expertise as
needed.
3.2.1.4 Site Visits – lessons learned
Table 3-1 provides the takeaways of the three site visits in specific categories.
Table 3-1. Site Visits –lessons learned
Area Lessons learned
Foundational Structure
Focus on implementing a foundational communications network including licensed radios
Setup standards for programming from the beginning
Combine Information Technology/Operational Technology for integration, planning and maintenance of the process network
Technology Selection
Focus on long-term support
Choose technology that allows standard configuration of end goals, without the need for customized scripting to achieve desired functionality
Enterprise Connectivity Look at the advantages of integrating CMMS with SCADA data sources
Other agencies are working towards enterprise level integration, but have not yet achieved full integration
Cyber Security Shift focus towards understanding the balance of cyber security with increased data access and technology use
3.2.1.5 Additional Observations
Table 3-2 provides additional observations annotated during the site visits. These observations are
important to capture for inclusion in the implementation stage of this project.
Table 3-2. Site Visits –Additional Observations
Area Observations
Field Instruments Add other instruments for preferred monitoring, control, and alarming functions
Add more water flow monitoring
Control Hardware
Standardize PLC and enter into long-term service and equipment agreement
Provide remote control of the wastewater system
Select system with strong water/wastewater presence that is actively supported by the manufacturer and is widely supported by many certified SIs
Utilize as much off the shelf options and as little customization as possible
Develop hardware, programming, and data exchange/connectivity standards that still provide flexibility for unique situations, such as packaged systems
Communications
Conduct communications study
Address recommendations from communications study
Evaluate licensed, high band-width communications backbone
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-8
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 3-2. Site Visits –Additional Observations
Area Observations
HMI
Standardize HMI and enter into long-term service and equipment agreement
Select system with strong water/wastewater presence that is actively supported by the manufacturer and is widely supported by many certified SIs
Utilize as much off the shelf options and as little customization as possible
Provide tiered level access, with extra screens for monitoring only
Provide single HMI system for multiple operations groups with access to appropriate operations screens per operator's login information
Provide remote monitoring capabilities
Develop alarm criticality standards
Safety and Security Security system should allow remote access via laptop/tablet
Consider back-up alarming system, such as Mission
Data Storage
Provide enterprise historian based on Structured Query Language (SQL)
Coordinate with IT on server/historian needs
Provide means for automatic/mobile collection of data in the field
Develop baseline connectivity requirements for all utilities software, including SCADA
Data Presentation/
Connectivity
Create baseline connectivity requirements for software connectivity
Complete a Technology Master Plan or Smart Utility Master Plan to promote evolution to Smart Utility
Migration Consider specialized construction management and inspection (CM&I) staff
Staffing
Staff up to support SCADA improvements
Evaluate staffing needs to support new systems created through this process (network, servers, instruments,
PLCs, HMIs)
Develop and train staff to support new systems created through this process (network, servers, instruments, PLCs, HMIs)
Space Provide adequate server room space for current and future needs
Provide dedicated space for each operations crew (water and wastewater) to serve as Control Room
Appendix C provides a complete summary of all the additional observations during this phase of this
project.
3.2.2 State of the Industry Workshop
BC provided a “State of the Industry” workshop with the City of Carlsbad on January 30, 2018 to
present where water/wastewater SCADA technology stands today. BC presented how others in the
industry are addressing their needs which are similar to the needs of the City.
3.2.2.1 Industry Challenges
The Water and waste water industry face significant challenges of aging assets, budget constraints,
stricter regulations, and a workforce gap. Technology has great value, but it is complex and rapidly
evolving. Most utilities produce vast amounts of data that is stored but not used in a clear way.
Utilities that invested in distributed control systems 25 years ago are now faced with systems that
have reached the end of their useful life. Utilities are now faced with the challenge of selecting new
systems with complex technology that is evolving rapidly.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-9
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.2.2 Use of Innovative Technology
BC presented various innovative technologies such as cloud computing and the use technologically
advanced field sensors that are part of the Internet of Things (IoT) technology. The presentation
covered aspect of the technology that may be considered “bleeding-edge” and others that may be
“leading-edge”. Bleeding-edge is the use of new technology that has not been widely used and tested
to understand whether it meets the claims of its capabilities. Using leading-edge technology is a
safer way to implement. This is technology that has been tested in the field and shows favorable
results.
3.2.2.3 Focus on Enterprise Connectivity
To harness and support the new data sources available through advances in technology, SCADA and
enterprise data systems must be planned out with the connectivity to share the data as needed. A
determination of what data is needed where and what technology will be needed to create the data
connections will need to be made. Creating a fully connected system across process and enterprise
data networks is the key to creating a system that is beneficial to the users and provides the
information in the context and format each user needs to be successful at their role. The future
system should provide a foundation that allows analyzing data from multiple sources spread across
a wide data network, including remote connectivity, to enable well informed decision making.
3.2.2.4 Progression of Automation Maturity toward enterprise connectivity
To leverage data from multiple sources and have it available to all users, in multiple departments, a
system that has full enterprise connectivity would meet the needs of the City. Most utilities take a
phased approach to reaching full enterprise connectivity. The chart below shows the different levels
of maturity that a system can go through before it’s a fully integrated enterprise system. The chart
also shows where the City may be with the automation of the sewer system, the water/recycled
water system and generally where 90 percent of the water/wastewater facilities in the country are.
This chart is very general, but it provides phases that are useful to know as we move forward with the
master planning and implementation. One of the things to keep in mind is that the chart focuses on
the SCADA development, whereas similar steps need to be taken for all systems that will be
integrated into the final enterprise system.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-10
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 3-1. Levels of Automation Maturity
The levels of maturity above are based on how systems are monitored and controlled from very basic
local hand station control to complex system-wide control where multiple sites can be manipulated
based on information (data) from other remote sites and/or other non-SCADA systems. Following are
some more details about the levels of maturity provided in the figure above.
3.2.2.4.1 Level 0 Maturity
Level 0: Manual Operations is defined by the following elements-
• All control is done in hand mode. This is done from local control panels or manual control
stations next to the equipment.
3.2.2.4.2 Level 1 Maturity
Level 1: Basic Monitoring is defined by the following elements-
• Loop Controller/PLC: This provides basic local control functionality, such as controlling the level
in a wetwell by monitoring the level and controlling pumps.
• Local Data Loggers and OITs: Done using chart recorders or simple operator terminals.
• Control modes (local only): Local and local/automatic modes using basic loop controllers.
3.2.2.4.3 Level 2 Maturity
Level 2: Automated Monitoring is defined by the following elements-
• Digital Controller Loop/PLC: Using local PLCs for loop controls as opposed to stand-alone loop
controllers.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-11
SC07221_FINAL_Carlsbad SCADA Master Plan
• Network with central HMI/SCADA servers: Local area networking for the SCADA system that
allows centralized monitoring and possibly some control.
• Control modes (remote-auto): Some remote-control capability.
3.2.2.4.4 Level 3 Maturity
Level 3: Fully Automatic Monitoring & Control/Basic Integration is defined by the following elements:
• Full automation: This provides complete PLC control locally and remotely from the SCADA
system.
• Process interlocks exchanged over network: Controls are no longer only local and can respond to
changes in other parts of the plant or facility.
• Automated closed-loop control around a setpoint: PLC based loop control that can respond to
changes in other locations.
• Control modes (remote-auto): Fully automated remote monitoring and controls.
*Most utilities in the U.S. have achieved level 3 maturity*
3.2.2.4.5 Level 4 Maturity
Level 4: Situational Awareness/ Enhanced SCADA is defined by the following elements-
• Operational flexibility: Data is available throughout the system and operations staff have
mobility. Complete remote access to SCADA system.
• Don’t need operator 24/7: Based on operational flexibility, facilities don’t need to be staffed
24/7.
• Historical data management: Historical data is easier to access and use. It can readily be used
for trouble shooting and reporting. *Carlsbad is doing some level 4 tasks manually*
• Decision support system provides operator advice: SCADA system provide more data in context
so it’s easier for operations staff to make decisions.
• Control Modes (remote-optimize): Optimized remote control that can use data from multiple
sources.
3.2.2.4.6 Level 5 Maturity
Level 5: Optimization and Business Performance is defined by the following elements-
• System-wide proactive control tools: Possible use of modeling software connectivity for
predictive control.
• Tools for operations optimization analysis: Use of tools other than the SCADA system to help with
optimization.
• Business systems integration (SCADA, UMS, GIS, hydraulic model)
• Control modes (predictive)
The enterprise system can be leveraged to deliver savings by improving CMMS service requests
based on predictive data; saving energy costs by pumping during times when costs are lowest and
maintaining the water balances as needed; using staff time more effectively and efficiently for
operations, engineering, report generation, and learning; and providing information to all levels and
departments.
3.2.2.4.7 Evolution of an enterprise-wide Utility
Realization of an enterprise utility with optimization and business performance requires progression
through levels of system maturity to a fully mature automation and business system. The most basic
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-12
SC07221_FINAL_Carlsbad SCADA Master Plan
level begins with simple manual operations, to which monitoring, control, and data integration can
be added at each step toward full implementation.
The City has expressed a desire to work towards an enterprise-wide (smart) utility. As described in
the SCADA Master Plan’s Vision Statement, all the improvements in this project will support the
move toward an enterprise-wide system.
The key step for both the water/recycled water and wastewater systems will be migrating to a fully
automated system, which will be accomplished through this SCADA master plan and subsequent
implementation plan. Simpler systems like sewer lift stations may not have a huge impact with
added controls and monitoring when it comes to daily operations. However, the value of building in
fully automatic monitoring and control for such a system is not in how the process runs but in the
data that can be collected and used for system optimization. The City will also have some
connectivity improvements to make with other data sources, such as CMMS and advanced metering
infrastructure (AMI). The SCADA Master Plan will be focused on the foundational step of bringing the
SCADA technology to the point that can support the City through this progression and can integrate
with other systems. The Master Plan will identify the connectivity issues with other data sources as a
future improvement.
3.2.2.5 Staffing for Technology
Along with the implementation of increased data connectivity and innovative technologies comes the
need for staff that can manage the new system. To maintain the required network, server, and
security needed for increased data connectivity and innovative technology integration, the City may
need involvement from IT or will need to hire the person with those skills to support the SCADA
system (OT). Limited access to IT personnel and absence of OT creates a gap that will need to be
filled for successful evolution to an enterprise system, with staff to support SCADA the most pressing
need. The City will need to bring on staff capable of filling these new roles or set up other ways like
external contracts to get the support necessary.
3.2.2.6 State of the Industry Workshop – Findings
The State of the Industry workshop provided material that all the stakeholders who attended could
discuss and debate. There were key lessons that came out of this workshop that re-emphasized
things that were learned in the site visits. The desire to move to an enterprise-wide system was
clearly stated and the necessary foundation to achieve that goal will be provided in the SCADA
master plan.
Table 3-3 provides a summary of State of the Industry findings.
Table 3-3. State of the Industry–Findings Summary
Area Findings
Foundational Structure Leverage technology available to build optimization modeling
Leverage mobile technology to allow remote control and monitoring
Enterprise-wide (Smart) Utility Achieve Level 4 maturity in progress to Level 5 or enterprise-wide utility
Technology Selection Technology that will meet future needs
Enhanced SCADA/ High performance HMI
Enterprise Connectivity Create a fully connected system across process and enterprise data networks to allow for information exchange
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-13
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.2.7 Additional Observations
Table 3-4 provides additional observations annotated during the site visits. These observations are
important to capture for the inclusions in the implementation stage of this project.
Table 3-4. State of the Industry –Additional Observations
Area Observations
Field Instruments Add more sewer flow monitoring instruments
Connect all existing field instruments to the control system
Control (PLC) Hardware
Standardize PLC and enter into long-term service and equipment agreement
Provide remote control of the wastewater system
Select manufacturer with strong water/wastewater presence
Develop hardware, programming, and data exchange/connectivity standards
Add ability to receive third party data
HMI
Standardize HMI and enter into long-term service and equipment agreement with manufacturer
Select system with strong water/wastewater presence that is actively supported by the manufacturer and is widely supported by many certified system integrators
Utilize as much off the shelf options and as little customization as possible
Provide tiered level access, with extra screens for monitoring only
Provide single HMI system for multiple operations groups with access to appropriate operations screens
per operator's login information.
Develop programming, high performance graphics, and data exchange/connectivity standards that provide flexibility for unique situations such as packaged systems
Provide remote monitoring and control capabilities
Safety and Security Remote access via laptop/tablet requires additional safety measures
Complete Department of Homeland Security audit and achieve required cybersecurity level
Data Storage
Provide enterprise historian based on SQL
Integrate other data sources besides SCADA into enterprise historian or use data warehouse
Develop baseline connectivity requirements for all utilities software, including SCADA
Data Presentation/ Connectivity
Create baseline connectivity requirements for software connectivity
Utilize technology to present/access data
Create dashboards to address user needs/questions
Integrate SCADA and enterprise historian with other business systems data
Integrate CMMS and SCADA data sources for predictive maintenance
Migration Consider specialized CM&I staff to facilitate migration
Staffing
Staff up to support SCADA improvements
Evaluate staffing needs to support new systems created through this process
Develop and train staff to support new systems created through this process
Appendix D: Site Notes provides a complete summary of all the additional observations during this
phase of this project.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-14
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.3 Enterprise Data Mapping Workshop
BC facilitated a data mapping workshop to help all stakeholders understand where and how data is
generated (source) and all the departments that use the data (users) that’s been generated. The
required connections between data sources and the end users was mapped out to show the
connectivity that would be necessary to establish an enterprise-wide network. By identifying what
additional data would help each user group to make better informed decisions, the connectivity
needs of the group were established in the data map. While the SCADA migration will not resolve all
connectivity issues, the data map provides a vision of enterprise connectivity that will guide this
project. In the workshop, each department went over their normal activities and where they got the
data they needed (sources) to get their work done. The discussions brought out difficulties faced and
what could be done to alleviate these obstacles. These discussions are provided in the sections
below.
3.2.3.1 Operations – Water/Recycled Water
Water and recycled water operations staff currently use the SCADA system as the source of
information required for daily operation. Additional system data is recorded manually in a notebook.
Water data comes from San Diego County Water Authority and Vallecitos, Recycled water data comes
from Encina (as operators of the Carlsbad Water Recycling Facility), Vallecitos, and Leucadia.
It would be beneficial to centralize the control systems for water/recycled water and wastewater to
have a single historian database. To meet the direct needs of the operations staff, the monitoring
and control system will need to be expanded to include additional process automation and more
real-time monitoring data. The current manual data recording system using a notebook should be
replaced with a system to streamline the data collection, storage, and collection. Additional data will
need to be brought in to track water demand, water purchasing needs, weather forecasts, and water
quality.
3.2.3.2 Operations – Wastewater
Wastewater operations staff currently use web-based access to the Mission monitoring system as a
source of system data. The monitoring system provides some trends and a view-only daily report.
Encina maintains flow meters in the system that the city would like to monitor and historize data. The
collection system has sewer SmartCovers in place, which they are using to provide level/flow from
sewer manhole covers that have not been integrated with other data systems.
As stated in the water/recycled water section, it would be beneficial to centralize the control systems
for water/recycled water and wastewater to have a single historian database. This will require new
monitor/control PLCs to collect data at sites, integration of the SmartCovers, and use of a mobile
platform for manual data collection to streamline collection, storage, and reporting of data.
3.2.3.3 Maintenance – Water and Wastewater
The maintenance group currently uses a CMMS software for their maintenance planning, but faces
challenges in coordinating with other groups, with direct meetings being required to get information
needed to make decisions. To improve efficiency in coordinating information for maintenance
purposes, it would help to be able to automate the flow of data into the CMMS from a variety of
different systems. The City would like to look for a replacement of the existing CMMS system, but
haven’t been given approval yet to do so.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-15
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.3.4 Meter – Customer Services
The current metering system is being converted to an Advanced Metering Infrastructure (AMI) system
that can retrieve data using iTron collectors and send it to a cloud-based system. The data will then
be imported into the utility billing system. The new system will be able to track usage with real-time
data and can be accessed with a web-based software called WaterSmart, which also functions as a
customer portal. The AMI system will need to be able to provide accurate meter readings to the
finance group to coordinate sales and billing. To have good data to provide water balance
information for management, AMI data will need to be readily available in a local data warehouse
that is compatible with the historian.
3.2.3.5 Engineering, Finance, Business Systems Specialists, Management Analysts, and
Regulatory Reporting
Data for departments and systems such as asset management, AMI, GIS, CMMS, LIMS (if
applicable), finance and engineering will all need to be coordinated from multiple sources. These
sources will require versatility to be able to manipulate and query data from across all the systems.
To allow for this kind of capability, all data will need to be pushed to and stored in an enterprise data
warehouse. The City has started using Tableau, a business intelligence and analytics software, that
could be used as an interface to access the data warehouse to allow the end-user to effectively and
efficiently access whatever data is needed.
City staff also expressed concern about inability for internal software to connect to one another and
push data to an enterprise-level data warehouse, especially for software procured outside of Utilities
for use with other departments. Baseline connectivity requirements should be developed in
coordination with City IT for all software interacting with Utilities.
3.2.3.6 Other Departments and Agencies
3.2.3.6.1 Coordination with City IT
BC has worked with the team and City IT to understand the existing infrastructure,
hardware/software, communications and networking that can be shared with a future Utilities
enterprise system. The team has also discussed the preferences for City IT in hardware/software
choices that will be taken into consideration moving forward.
For software products, the City uses many Microsoft products, including Microsoft Server 2016,
Windows 10 Professional, MS SQL, and Windows Security. The city also uses HP software for the
document management system across all departments. The preferred virtualization software is
VMware, and the City IT do not want to use Hyperware or Citrix for virtualization.
The City is currently working on a project to use the large amounts of dark fiber that is in place, but
unused. Further coordination may be needed between departments to get access to this fiber for use
in communications for Smart Utility concepts.
3.2.3.6.2 Coordination with Encina
BC will work with the team to coordinate with Encina to determine the best ways to exchange critical
live data from their system into the new Carlsbad SCADA system.
3.2.3.7 Enterprise Data Map
Enterprise data mapping from appropriate data sources provide routes to reach operational and
enterprise goals. Data mapping allows staff to understand the various data sources and the users of
the data. This is an important step in planning how these data sources should come together into a
data warehouse for easy access by the users. The outcome of the data mapping workshop is shown
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-16
SC07221_FINAL_Carlsbad SCADA Master Plan
in Table 3-5 and Figure 3-2. The interconnectivity of many different data sources will be able to
answer questions or fulfill users’ needs through increased access. This can help guide the evolution
of the City of Carlsbad Utilities towards an enterprise-wide system.
3.2.3.8 Enterprise Data Mapping Workshop – Findings
The City/CMWD have a vision on where they want to be collaborating existing data connections with
future data connections giving user access to fulfill needs and answer necessary questions. These
elements revolve around utilizing enterprise database and software connecting with appropriate
users to establish relationships between data sources.
Table 3-5. Enterprise and Data Mapping –Findings Table
Area Findings
Foundational Structure
Expand the system for a centralized historian for water, recycled water, and wastewater
Combine Information Technology/Operational Technology for integration, planning and maintenance of
the process network if and where possible
Reporting data pushed to and stored on enterprise data warehouse
Careful review of the data stored in the data warehouse will provide a single reliable source of data
Enterprise Connectivity Potential early benefits of integrating CMMS with SCADA data sources
Link enterprise historian with new technology foundation to create enterprise database
Cyber Security Shift focus towards understanding the balance of cyber security with increased data access and technology use
3.2.4 Operations Shadowing
Operations shadowing was conducted to understand current SCADA system monitoring and control
practices, workflow, routines, and systems. This shadowing focused on the day to day functions and
practices of the OT and their use of the current system.
3.2.4.1 Water and Recycled Water Operations Shadowing
CMWD operations currently operates a SCADA system for monitoring and control of the potable
water and recycled water systems. The control room is located at the City of Carlsbad Utility
Department at the CMWD Building at 5950 El Camino Real, Carlsbad, CA. The operations staff uses
a Wonderware inTouch HMI (stand-alone) to monitor and control certain portions of the water and
recycled water systems. The duty operator, this task is rotated weekly between the operations staff,
will typically perform all operations tasks for the assigned week. The remaining operators will be
available if needed to assist, but are otherwise assigned other duties by the water operations
supervisor. The stand-alone Wonderware InTouch was last updated in 2014 and is configured as a
redundant system using two PC’s located in the same room.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-17
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 3-2. Enterprise Data Map
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-18
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.4.1.1 Water Operations Normal Daily Duties
The daily routine for the duty operator begins with reviewing the HMI system. The operators review
the system from screen to screen. They look for current reservoir levels to ensure reservoir levels are
within their proper ranges. Operations must verify there is adequate storage of water to meet
demand, while also making sure the reservoirs where demand is lower are not filled too high or the
risk of degrading water quality can become an issue. Trend displays are reviewed for each site to
look at pump performance; i.e., to look for any unusual patterns in the tank filling process.
The duty operator also reviews the current flow from the turnouts. In reviewing the system for current
water capacity and anticipating the future demand for the water system, the operator may determine
that a flow change could be required. If a flow change is required, the operator will notify SDCWA of
required flow change. Flow changes are only allowed three times per day, at 8:00 am, 2:00 pm, and
8:00 pm. The operator will compare the flow changes on the trend displays to confirm they match
the recent flow changes recorded in the Flow Book. The Flow Book is a manual log of all flow
changes from all turnouts that can supply water to the district. There is an opportunity to better
automate this data logging, historize data, securely store data, and address changes based on data.
Operations also operates and controls pressure reducing valves (PRVs) within the distribution
system. If water is required in a certain zone, the operator can manipulate these PRVs to increase or
reduce flow into that zone. The SCADA system is designed such that the operator must “click and
hold” the open or close button on the SCADA system for an amount of time to get the valve to
operate for a certain distance. Fine tuning the flows at the PRVs is difficult using this method.
Due to the manual operation of the dosing control at the Maerkle site, operations would rather
manipulate water connection CWA #3 than the connection that fills the Maerkle reservoir. Water
connection CWA #6 also cannot provide flow less than 4 cubic feet per second (CFS) due to the flow
meter capabilities of CWA. During the summer, this is typically not an issue, However, during the
winter months of lower water usage, operations must watch water levels very carefully at Santa Fe
#2 reservoir and D3 tank. There is a need for reactive control of flow through valves.
The alarm page is reviewed for any previous alarms and currently active alarms. The alarm page has
a mixture of alarms and non-alarm notifications. The communication statistics are reviewed for any
communications that seem abnormal. While most sites have consistent communication
performance, some sites have sporadic communications and typically don’t stay at 100%
throughput. Based on the history of each site, operations will determine if communications for a
given site is not within typical parameters.
The system is also reviewed for any water loss events. Operators review trend displays and look for
any unusual or rapid level changes in reservoirs or lower than normal pressures within the
distribution system. If a water loss event is determined to have occurred, then a manual calculation
for water lost will be performed so this amount can be accounted for and logged appropriately with
the proper reporting agency. A water balance could be automated to help account for water loss and
automated reporting, create a centralized historical record, and make data available to multiple
users across the enterprise.
The duty operator will also perform routine tasks in the field as part of the weekly duties. Every
Wednesday, Saturday, and Sunday, the duty operator will visit each reservoir site. At each site, the
operator will check the reservoir level onsite, either by manual site gauge on the tank or a pressure
gauge to compare with the reading that is received via the SCADA system. The operator will also
check for chlorine residual and Total Dissolved Solids (TDS) at each reservoir site to confirm the
levels are within acceptable limits. This helps operations determine if additional measures are
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-19
SC07221_FINAL_Carlsbad SCADA Master Plan
required to maintain water quality within the system. The operator also performs a physical
inspection of the site to look for evidence of intrusion.
The Santa Fe reservoir only has solar power available. This tank is also embedded in the side of a hill
and is not exposed at the bottom. Currently the only way to get a chlorine residual sample is to open
the hatch on top of the reservoir and use a drop tube to get a water sample. Additional chlorine
monitoring would be beneficial.
One of the key sites within the potable water system is Maerkle. The Maerkle site is visited everyday
due to its importance and criticality within the system. It is also the only site in the water system with
a backup generator. However, the generator status is not visible via the SCADA system, but should
be connected.
Maerkle is also the only site within the system capable of boosting chlorine if needed. Chlorine
residual is reported on their SCADA. Chlorine can be added when necessary if the incoming residual
is too low or if chlorine residual in the reservoir is too low. The chlorine dosing process is manually
set and is an open-loop control system with no feedback. There is a chlorine analyzer onsite, but this
is not used for trimming the dosing controls. Operations has developed a “recipe” book to help guide
operations to setpoints needed based on previous empirical results observed depending on flows
and incoming water quality. There is no NH3 (ammonia) residual monitoring at Maerkle. Additional
water quality monitoring and some feedback on the automated chemical dosing would improve
operations at Maerkle.
3.2.4.1.2 Water Operations Other Duties
Another major service the operations staff provide is during abnormal operations scenarios.
Depending on the situation, the duty operator may handle the situation or other operations staff may
assist if more than one person is needed to assist in the operation for any event.
One situation that can arise is water quality can degrade in any reservoir or tank. In this case, the
typical remedy is to use as much water as possible, then recharge the reservoir with more water,
thereby diluting the existing water with degrading water quality. This “fill” and “draw” operation will
repeat until the staff is confident the water quality has stabilized in the reservoir. During this cycle of
“fill” and “draw”, daily residual readings are taken to monitor the water quality to track the progress
of the reservoir dilution operation. Since no analyzers are in place other than Maerkle, the residual
must be taken locally from a hand sample taken at the reservoir. It should be noted that the
occurrences of poor water quality have decreased since water operations has started operating the
reservoir at a lower water level. This reduces the retention time for water within the reservoirs.
Additional analyzers at all reservoirs would be beneficial.
Any water shutdowns, water leaks, or water loss events also must be handled. In some cases, such
as hit fire hydrants and other water leaks, valving may be required to isolate the leak. Operations will
calculate water loss incurred during these events to report to the appropriate reporting agency.
The Calavera potable pump station is typically only used when water connection CWA #4 is at zero
flow. When demand is low, a jockey pump (smaller pump) is available to maintain pressure. The
jockey pump cannot be started remotely and must be started locally at the pump station. The SCADA
system cannot monitor the status of the jockey pump. The pumps at Calavera potable pump station
are also at a high point in the system. In the past, air has been trapped in the pump and the air-vac
has not operated properly. The air and water heated up causing the pump to overheat and causing
the bearings to overheat and requiring the bearings to be replaced. The mixture of control equipment
on site can be confusing to maintain. Adding pump status and temperature monitoring and control to
the Calavera Pump Station would assist operations. Operations has remote capabilities during
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-20
SC07221_FINAL_Carlsbad SCADA Master Plan
business hours, through a remote login with a tablet. Alarms are called out to the on-duty operator
cell phone.
3.2.4.2 Wastewater Operations Shadowing
The City of Carlsbad operations currently operates a series of sewer lift stations to control the flow of
sewer until it reaches the Encina Water Pollution Control Facility, run by the Encina Wastewater
Authority, a joint powers authority owned by six agencies in north county San Diego, including
Carlsbad.
Wastewater ops currently uses Mission monitoring system, which provides view only access to the lift
stations’ status. The crew room located at the City of Carlsbad Utility Department at the CMWD
Building at 5950 El Camino Real, Carlsbad, CA provides access to the Mission monitoring system
and the Smart Cover monitoring system. Smart Cover monitoring is positioned at key points, critical
alarms are sent via Smart Cover monitoring system. The operations staff uses both web-based
systems to monitor status of the lift stations within the city.
Typically, the duty operator, a task that is rotated weekly between the operations staff, will perform
all operations tasks for the assigned week. The remaining operators will be available if needed to
assist, but are otherwise assigned duties by the wastewater supervisor.
3.2.4.2.1 Wastewater Operations Normal Daily Duties
The daily routine for the duty operator begins with reviewing the Mission system. The operators
review the system from screen to screen. They look for any levels that are out of normal range. The
operators also review trend screens for each site to look for any abnormalities, such as wetwells
emptying in an unusual pattern indicating a potential pumping problem. The operators also look for
any changes in pump run sequencing, also indicating a potential pump problem. Operators will also
review the Smart Cover system to look for any abnormalities. The Mission system and the Smart
Cover system can be viewed over the internet at the wastewater crew room or from any other
internet connection and will notify the on-duty operator of any alarm conditions via cell phone.
The duty operator will also discuss any alarms or events that may have transpired in the last 24
hours with the operations team and wastewater supervisor to keep all operators informed of latest
events and to get additional direction for any upcoming events that may impact daily operations. The
duty operator will also go to different sites in the field for daily checks and visual inspection of the lift
stations. The duty operator visits the large lift stations on Monday, Wednesday, and Friday each
week and will visit the smaller lift stations on Tuesday and Thursday. These are the normal routine
checks. An alarm or other event could trigger an unscheduled visit if deemed necessary by the duty
operator or the wastewater supervisor.
Operators always travel with a portable “sniffer” while onsite. This device confirms no presence of
combustible or toxic gas that can be a byproduct of the sewer collection process. Sites have unused
hardwired sensors for explosive gas and oxygen detection. The city has found these devices to be
quite expensive to maintain and have abandoned using and maintaining these at the sewer lift
stations where these are installed. The operations team has found the portable version to be more
reliable and easier and cheaper to maintain. They calibrate the devices monthly to make sure they
are in proper working condition.
While on site at each lift station, the operator will perform a visual inspection of the site looking for
anything unusual that could indicate intrusion into the site or any other abnormality. The operator will
manually log runtimes for pumps, flow meter readings, utility power meter, generator hours, and
wetwell level. The duty operator will also perform a visual inspection of the wetwell, drywell,
generator block temperature, and any other mechanical equipment.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-21
SC07221_FINAL_Carlsbad SCADA Master Plan
Another important check while onsite is to observe each pump running. In cases of stations with
larger flows, each pump will run during the normal course of filling the wetwell while the operator is
onsite. At some sites, the flow is not large enough to trigger a pump run while the operator is onsite,
so these pumps will be run in hand. The purpose of observing each pump running is to confirm the
correct flow for each pump. If for some reason there is a noticeable drop in flow, this could be an
indication of a pump blockage or even an impending pump or motor failure. This observation will
also allow the operator to hear the pump start and electrical equipment engage listening for any
unusual sounds for the motor, pump, piping, or electrical equipment. Current process after hours
uses an auto dialer in the case of an alarm to call out to the on-duty operator cell phone.
3.2.4.2.2 Wastewater Operations Other Duties
The wastewater operations staff is also available to address any unusual or abnormal duties
required to maintain the wastewater operations facilities. The Air Pollution Control District of San
Diego County (APCD) administers permits for odor control, such as at the El Fuerte Lift Station. If an
inspection is scheduled by APCD, the operations staff will assist the APCD staff while onsite as they
view records and logs kept and maintained by the City of Carlsbad wastewater operations staff.
APCD has requested that these logs remain manual, but there is an opportunity to also log the data
centrally.
Part of the routine maintenance and checks for the operations team is a monthly check of the
generators. Operations will simulate a power failure by turning off the incoming breaker. This will
cause the generator to automatically start and power the station. The staff will observe the station
function while on generator power to confirm the station behaves properly while on generator power.
This test confirms the power supply of the generator, Automatic Transfer Switch (ATS), and that all
necessary equipment onsite operates properly under generator power.
The Poinsettia Lift Station is a very critical site for the city’s wastewater system. If the station fails,
there is less than 30 minutes before potential leaks and spills could occur. Therefore, this site has a
mobile pump/generator installed. While this pump is mounted on a trailer designed to be a mobile
pump, it is already connected with inlet and outlet pipes and with level sensors in place for it to serve
as a backup if required. Otherwise, this mobile pump would take longer to take to the site and get
piped in to the system than would be necessary, so it stays parked at Poinsettia. While the site still
has a backup generator, the extra pump onsite adds another necessary level of redundancy to the
site. The operations staff also performs visual checks of this pump to ensure its readiness, if
required. This pump is not connected to the Mission reporting system, but the discharge piping is
oriented such that the lift station flow meter would include any flow from the mobile pump if it were
to be used.
3.2.4.3 Operations Shadowing – Needs and Opportunities
The operations shadowing findings summary is provided in Table 3-6.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-22
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.4.4 Additional Observations
Table 3-7 provides additional operations shadowing observations.
Table 3-7. Operations Shadowing –Additional Observations
Area Deficiencies and Desires
Field Instruments
Add more water quality monitoring (chlorine, TDS, pH, ammonia)
Add automated chemical dosing, especially at Maerkle
Add generator monitoring and control at Maerkle
Add jockey pump monitoring and control and temperature monitoring at Calavera Pump Station
Control Hardware Provide remote control of the wastewater system
HMI Develop programming, high performance graphics, and data exchange/connectivity standards
Provide remote monitoring capabilities
Table 3-6. Operations Shadowing –Findings Summary
Focus Needs Opportunities
Field Instruments/Control
Hardware
No remote control for wastewater Establish remote control capabilities for wastewater
Reactive control of water quality and flow through valves Improve fine tuning of chemical dosing and valve
operation
Manual control of equipment Automate locally controlled equipment
Mixture of control equipment onsite, can be confusing to maintain Eliminate unnecessary control hardware
Generator run/fail status at sites Add generator run/fail status signals to SCADA system
Additional analyzers at reservoirs Add analyzers at reservoirs to monitor chlorine residual
Pump status signals for some pumps no on SCADA Add status signals for pumps that don’t have them;
include all equipment health signals
Air monitoring at El Fuerte Add air monitoring signals as needed
Data Storage No centralized historical records
Historize additional data connected to the SCADA system
Securely store data and make available to multiple users across the enterprise
Provide the ability to address future data needs as
requirements change and the system matures
Manual records with no backup data Collect key data across the system into the historian
Staffing
Operations strategies are via tribal knowledge Capture institutional knowledge into the system
No online or “living” training documentation Establish operations and maintenance training.
No source for technology training Identify source for technical training as required
Safety & Security No 24/7 video monitoring of sites Identify video surveillance technologies to minimize communications bandwidth impact
Intrusion monitoring Add intrusion monitoring to all sites
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-23
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 3-7. Operations Shadowing –Additional Observations
Area Deficiencies and Desires
Safety and Security Provide video security at remote sites
Provide intrusion alarms at all remote sites
Data Storage
Provide enterprise historian based on SQL
Coordinate with IT on server/historian needs
Provide means for automatic collection of data in the field
Integrate other data sources besides SCADA into enterprise historian
Develop baseline connectivity requirements for all utilities software, including SCADA
Data Presentation/ Connectivity
Create baseline connectivity requirements for software connectivity
Utilize technology to present/access data
Create dashboards to address user needs/questions (water balance, preventative maintenance, ROIs, production reporting, etc.)
Integrate SCADA and enterprise historian with other business systems
Integrate CMMS and SCADA data sources for predictive maintenance
Migration
Consider specialized CM&I staff
Refine I/O, network diagram, wiring diagrams, and control strategies documentation to prepare for design
Clean up existing/abandoned hardware
Staffing
Staff up to support SCADA improvements
Evaluate staffing needs support new systems created through this process (network, servers, instruments, PLCs, HMIs)
Develop and train staff to support new systems created through this process (network, servers, instruments, PLCs, HMIs)
Space Provide adequate server room
Provide dedicated space for each operations crew to serve as Control Room
3.2.5 Levels of Automation
After going through multiple workshops with City staff, the City would like to have a fully automated
SCADA system that provides control and monitoring of all sites. In addition, the City has also
indicated a desire to have enterprise-wide system connectivity. This master plan will cover the
automation of the SCADA system, but it provides the City with information on what steps could be
taken with other systems for an enterprise-wide system.
3.2.5.1 Current Level of Automation
There are several platforms for current systems in place and an array of communication systems
which must be standardized to reach an industry standard level of automation. The city also needs
server redundancy to accommodate potential failure. The current state of the systems is a result of
an ad-hoc approach to expansion and replacement of the systems. Support for these systems are
difficult due to the circumstances. Water/Recycle Water System and Wastewater do not have
consistency in development standards. There is a lack of documentation requiring OT to have
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-24
SC07221_FINAL_Carlsbad SCADA Master Plan
extensive trail knowledge to run and maintain the system. A planned approach using master plan
methodology will prevent future inconsistency in the systems.
3.2.5.1.1 Water/Recycle Water System
The water/recycle control systems currently are close to the Level 3 automation maturity level. There
are a few opportunities to increase the level of automation that would close the gap from a Level 2 to
a Level 3, such as more automated chemical dosing and improved remote control.
Chemical injection occurs at one location into the system, chemical dosing functions only manually.
Water flow changes from SDCWA are selected based on not changing the flow at the Maerkle
reservoir to prevent changing the chemical dosing. If water enters the system in a zone where usage
is lower, it can lead to water quality issues if not monitored closely. An online closed-loop control of
the chemical dosing would allow for proper chemical dosing, regardless of the water source selected.
There are also a few sites where not all equipment or conditions are monitored or can be remotely
controlled. Adding control and monitoring, to these sites would provide a more robust and fully
automated water system. Live data from third party agencies would also be beneficial.
3.2.5.1.2 Wastewater System
The wastewater system for the City of Carlsbad is at an automation maturity level closer to Level 1,
providing basic control for the lift stations. Currently the pump stations are controlled by local pump
controllers. Operations also has separate monitoring and separate alarming systems with no ability
to control equipment or change control setpoints. Alarm setpoints are also locally set and cannot be
modified remotely.
Providing a single system that maintains alarm and control setpoints would simplify operations.
Remote access could be provided to the system for ease of operating use. For redundancy
considerations, an alarming system with a different communications network could also add to the
reliability of receiving timely SCADA information in event of equipment, power, or communication
network failures. The sewer system needs more flow monitoring, either by the City or by connecting
with Encina. This would progress the wastewater system to a Level 3 automation maturity.
3.2.5.2 Progression to Level 4 Automation
Once all the sites within the City reach a Level 3 automation maturity level, the operational flexibility
will be very close to what is expected with Level 4 maturity since the current system doesn’t require
24/7 on-site monitoring. The system that delivers Level 4 must maintain this flexibility already in
place with the City while adding features to assist with operator control of the system. Historical data
from the SCADA system needs to be accessible and meaningful for the various departments and/or
systems that would need this data. Further intelligence could be applied to the control system to
provide operations with information to assist in decision-making for specific operating conditions.
Optimization modes for operations could be added in the HMI that would tailor the controls for given
operational scenarios based on demands and the current state of the system. Implementation of a
full remote control mode for the system would increase operator access for both ease of operations
and increased access to system data.
For a level 4 automation maturity system, the system screens and information contained in them
would be done in such a way that trail knowledge is embedded into the system. This would facilitate
transitions and the training of new operations staff.
3.2.5.3 Progression to Level 5 Automation
Level 5 automation maturity level takes the SCADA system from a reactive control system to one that
is proactive. The system would use all inputs to look for what the future would be for the state of the
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-25
SC07221_FINAL_Carlsbad SCADA Master Plan
system and anticipate the future operational scenarios and base reactions on what will be required
vs. what is required right now. The system can optimize resources (water and/or energy) if a less
severe reaction can be determined that would maintain the integrity of the current state of the
system and still satisfy the predicted state of the system.
This maturity level also needs data to be available from various business systems, CMMS, GIS,
hydraulic model, that is contextually relevant, timely, and meets the business needs.
3.2.5.4 Levels of Automation – Needs and Opportunities
A summary of levels of automation findings is provided in Table 3-8.
Table 3-8. Levels of Automation–Findings Summary
Focus Needs Opportunities
Control Hardware
Limited installed base of equipment locally Vendor should be widely established in the
water/wastewater market
Not easily supported Easily programmed conforming to IEC 61131 (formally IEC
1131)
Multiple systems installed at a single site Standardize and maintain long-term product lifecycle
No consistency between water/recycle system and wastewater system Develop standards across systems
HMI
Lacks documentation Develop HMI interfaces that are intuitive and descriptive for users
Multiple platforms for different operations Provide single platform to support both sides of operations
Limited redundancy for existing hardware or software Implement levels of redundancy to mitigate failure risks
Separate alarming and monitoring for wastewater Integrate alarming solutions and establish criticality standards
Communication
Multiple systems Establish system-wide communications backbone
No set growth plan, system has grown ad-hoc with limited bandwidth Provide for future growth as needs develop
No timely support Supported by local vendors/contractors
3.2.6 Staffing Needs
As the SCADA system develops, so will the staffing needs for the City. Requirements and skill sets
will evolve as the system progresses through the SCADA system lifecycle. The needs in the following
areas will be further defined as part of the implementation plan in Section 5, but the key roles that
will need to be filled are noted here.
3.2.6.1 Skillset Requirements
Skillsets can reside in a variety of sources including existing City staff, directly hiring additional
resources, or using third party consultants and contractors to supplement staff. As these skillsets are
dependent on the individual capabilities, below is an overview of the specific individual skillsets that
are recommended to be included for each of the project and maintenance phases. While each of the
project phases will have overlapping requirements, specific skillsets within each of the phases can
promote effective delivery within each phase. Skillsets marked with an asterisk (*) are typically
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-26
SC07221_FINAL_Carlsbad SCADA Master Plan
required for the primary design and implementation of SCADA projects and potential future
upgrades.
Note. Core implementation and construction resources such as engineers and general electrical and
controls contractors are assumed to be third parties hired on an as needed basis by the City and are
not included in the skillset requirements below.
• *Project Management: Project management of the engineering and planning development
including managing deliverables, schedule, scope, and budget.
• *Construction Management: Management of the project during construction including oversight
of contractors, scope, quality, schedule, and budget.
• *Procurement and Contract Management: Development of the procurement contracts, selection
process, and conditions for hiring of outside services and procurement of required hardware and
software.
• *Construction Inspection: Site and work-based inspection and quality control of third party
contractors and consultants work including electrical, instrumentation, network, and controls.
• *Construction Operations Management: SCADA migrations and updates require periods of
manual operations, bypass, and shutdown and startup coordination to ensure system remains
operational during construction.
• Technology Management: Management of the additions and modifications of the system to set
overall direction, policies, level of technology integration, and user management. Maintain
system standards, select balance of technology updates, and manage technology patches and
versions to ensure technology stability and reliability.
• Network and Security Management: Additions and modifications to the network and subsequent
systems need to be managed and secured; this includes developing policies, coordinating
network modifications, and managing access and network stability.
• Analytics Translation: As each of the systems and sources of data become more integrated,
maintaining an understanding of how each of the data sources is structured, the limitations and
capabilities of the technology, and the data presentation structures and standards development.
To supplement, the additional skillset of understanding core business and strategic processes to
provide coordination to present the information effectively to users and leaders in making
effective business decisions.
• SCADA Programming: Programming and configuration of the PLC’s, OIT’s, and HMI platform
including general troubleshooting and maintenance, additions, and firmware updates.
• Information Technology Maintenance: Maintaining and managing the SCADA and user
computers, servers, and associated network including troubleshooting, additions, hardware
updates, virus/malware management, and software patches.
• Historical Database Management: Maintaining and managing the SCADA and associated
informational databases including archiving, data redundancy, validation, and query/aggregation
management.
• Field Technician: Maintain and manage field instruments to ensure system operability, including
testing, scheduled preventative maintenance, troubleshooting, fault analysis, replacement, and
installation of field instrumentation.
Each of these skillsets can be fulfilled by leveraging existing City staff, adding to the City staff
resource pool, or by using a variety of third party consultants and contractors. Section 5 will provide
a detailed comparison of these skillsets to the existing City staff and resources to provide an
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-27
SC07221_FINAL_Carlsbad SCADA Master Plan
understanding of which of these skillsets currently reside within the City and compare options for
adding staff or using third party resources to fulfill the remaining skillset gaps.
3.2.6.2 Additional Observations
Table 3-9 provides additional observations for SCADA equipment and space needs.
Table 3-9. SCADA Equipment and Space Needs –Additional Observations
Area Needs
Staffing Needs
Staff up to support SCADA improvements
Evaluate staffing needs support new systems created through this process (network, servers,
instruments, PLCs, HMIs)
Develop and train staff to support new systems created through this process (network, servers, instruments, PLCs, HMIs)
3.2.7 SCADA Equipment Resource and Space Needs
The City should provide space adequate for the network and server infrastructure required to
operate the new SCADA system, the staff to utilize the new SCADA system, and sufficient space for
future expansion.
3.2.7.1 SCADA Server Space
The physical and performance needs for the SCADA server room are similar to those of an IT server
room. The following items should be taken into consideration when assessing SCADA equipment and
space needs:
• The room will require an estimated footprint of 360 square feet to provide the space needed for
equipment as well as space for rack clearances to meet building and electric codes, and
separations to provide airflow for heat dissipation.
• Redundant Uninterruptible Power Supplies (UPSs) should provide adequate backup power for all
server equipment.to effectively monitor and control the SCADA system during a power outage at
the control center.
• Redundant dedicated air conditioners should be provided in the event of failure of one of the
units. The air conditioners should also be connected to an emergency generator in case of power
loss. Note that the building air conditioner should not be connected to the server room.
• The room should be equipped with a security door to limit access to authorized personnel.
• Dry fire suppression cylinders should be provided for fire protection.
• Additional wiring should be provided from the SCADA server room to the control spaces.
• Additional space should be considered for: the radio communications equipment; one or two
workstations for the servers; and room to allow the system to grow as the utility evolves.
The IT and OT/automation servers could be co-located in one room to reduce costs since both server
rooms require the same physical infrastructure. A layout for the combined room would require two
racks for the two systems, as well as a spare rack to provide space for future expansion. The figures
below provide an example of a combined IT and OT/Automation server room and an example layout
for one of the server racks.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-28
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 3-3. Combined IT/OT/Automation Server Room Layout Example
Figure 3-4. Server Rack Layout Example
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-29
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.7.2 Automation/OT Work Space
Space should be considered for the needs of an evolving Automation/OT staff. Two distinct spaces
should be considered for the Automation/OT staff space; an Automation/OT workspace to conduct
computer work and monitor the SCADA system, and a separate Automation/OT lab/equipment space
to stage, test, and troubleshoot equipment.
For the Automation/OT workspace, each member of the Automation/OT group should have a
dedicated desk space with a thin client or separate HMI, to monitor the system.
The Automation/OT lab/tech area should be dedicated for staff to stage, test, and troubleshoot
instruments and equipment. A high work bench and wall space should be provided to facilitate work
on the instruments and equipment and mount tools. The lab space could possibly be in the
warehouse. Figure 3-5 below provides an example layout for the Automation/OT lab/tech area.
Figure 3-5. Automation/OT Lab/Tech Area Layout Example
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-30
SC07221_FINAL_Carlsbad SCADA Master Plan
3.2.7.3 Decentralized Control Rooms
Each water and wastewater operations group should have a dedicated control room, and staff will
also have business space requirements. There are two common philosophies regarding control
rooms and business work space: centralized control room and decentralized control room.
The centralized control room is the more traditional use, where only operations are conducted in the
control room. However, a centralized control room may not be feasible, if business work space must
also be provided elsewhere.
As the use of laptops and mobile devices has expanded, some agencies are considering
decentralized control rooms, where the crew have offices or cubicles where both operations and
business is conducted. Water operations currently has a hybrid centralized setup, with SCADA
equipment and business computers co-existing in the same room.
Wastewater operations does not currently have a dedicated control room, but the way they do work
will likely change as the system becomes more automated. The city should consider how to provide
wastewater operations with a control room.
If the city is willing to proceed with decentralized control rooms, certain requirements should be
accommodated in each decentralized control room area.
• Secure access to the control system
• A dedicated work station space for the HMIs
• Dedicated work spaces for business use.
• A wall display of monitors to display different HMI screens simultaneously for a larger group
during emergency situations.
• Sufficient works space to spread out drawings and system maps.
• Low-walled or glass partitions between desks to create physical separation but still promote
collaboration.
• Extra wiring and a UPS to support the control system.
Figure 3-6 below provides an example layout of one of the decentralized control/crew rooms.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-31
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 3-6. Decentralized Control Room Layout Example
3.2.7.4 Core Deficiencies and Desires – SCADA Equipment Resource and Space Needs
SCADA equipment resource and space needs core deficiencies and desires are provided in Table
3-10.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-32
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 3-10. SCADA Equipment Resource and Space Needs –Core Deficiencies and Desires
Area Deficiencies and Desires
Foundational Structure Specific space for network and server infrastructure
Space for staff to operate new system
3.2.7.5 Additional Observations
Table 3-11 provides additional observations for SCADA equipment and space needs.
Table 3-11. SCADA Equipment and Space Needs –Additional Observations
Area Deficiencies and Desires
Space
Provide adequate server room
Provide adequate OT space
Provide dedicated space for each operations crew to serve as Control Room
3.3 Operational Needs and Opportunities Summary
After going through multiple site visits and workshops with City staff, the City has stated that they
would like to have a fully automated SCADA system that provides control and monitoring of all sites.
In addition, the City has also indicated a desire to have enterprise-wide system connectivity. This
master plan will cover the automation of the SCADA system, but it provides the City with information
on what steps could be taken with other systems for an enterprise-wide system. This leaves several
opportunities to improve the SCADA system. These are categorized into nine areas:
1. Field Instruments: The SCADA system will need to provide more data collection in the field. We
have identified the need for additional analyzers, flow monitoring, pump monitoring and controls,
backup generator monitoring, site intrusion monitoring, and a general need for additional data
for improved controls.
2. Control Hardware:
− The SCADA system will also need to be modular and adaptable, which will allow the system
to easily expand in the future as the need increases. Modularity will also allow the
installation of the same platform of system across different size facilities, sized correctly for
the field conditions to minimize cost and easily expandable as required. Reliable and flexible
field programming will enable the system to be scalable to fit the City needs regardless of
the size or IO requirements at each site. Support for the system should be easily available.
Easily understandable training tailored to fit the different needs of operations and
maintenance personnel.
− Control of equipment in the water and recycled water systems is for the most part uniform
across pump stations. There are a few pump stations where full control of some equipment
is missing. The control for pressure reducing stations in the system is not consistently
reliable. A reliable way to control the valves can improve the efficiency of moving water
between zones. The wastewater system does not have any remote access to controls, with
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-33
SC07221_FINAL_Carlsbad SCADA Master Plan
read-only access. Programming and control is not consistent between facilities.
Programming standards are not in place to ensure consistent control across the system
3. Communications: Currently both water/recycle system and the wastewater system are using
different communication networks to the remote sites. A single high-bandwidth communication
backbone would allow for unlimited growth opportunities at each site. A higher bandwidth
solution would provide the ability to add video monitoring of sites to confirm other site alarms
and surveillance of remote sites for security. The communications solution should be sized for
future growth to accommodate all existing sites and the addition of new facilities to the SCADA
network.
4. HMI: The current SCADA and control systems are a mixture of different technologies and
communications that have been added as needed over the lifetime of the SCADA system. The
technology used should be standardized for simplicity, ease of use and maintenance.
5. Safety and Security: Safety and security is a major priority. Video security at remotes sites would
allow for situational awareness. Achieving a higher level of cybersecurity protects critical
infrastructure and protects data.
6. Data Storage: Data and access to data is an essential ingredient and result of a well-planned
SCADA system. The data, once applied with context has different uses for different levels and
departments within an organization. For operations needs data should be provided with context
to facilitate decision making.
7. Data Presentation: The current HMI system for the water/recycle system does present the data
within the system. There is a shortage of summary screens. Reviewing overall state of the
system is quite “click intensive”, meaning, an operator must go from screen to screen to review
the current state of the water/recycle systems. The wastewater system has a standard view
template as provided by Mission systems with very little historical data available other than trend
screens for levels, flows and pumps running. The SCADA system should have the ability to push
data to a database structure that allows other data sources and access and utilize this data
effectively. Access to data from other departments within the city is a valuable tool to reach
higher levels of automation maturity. The current information produced is difficult to reconcile
due to the timing of the data received. The data is not provided with context for the departments
that could use the data. The manual process of getting this data also adds to the time lag. This
process of pushing data to a database structure, should be one that occurs with as little manual
intervention as possible.
8. Staffing: Support is essential to developing and maintaining a state-of-the-art SCADA system. A
system should be easy to support. Multiple qualified third-party integrators/consultants should
be available to provide support when needed. The City does not have many choices for support
of the current system. Training for different levels within the City to meet the needs of the
various level of users is essential to keeping staff engaged with the system. Keeping the training
current will ensure the system is maintained and kept up to date.
9. Space: Provide sufficient space for network and server infrastructure to operate the future
SCADA system, staff to operate the new system, and future expansion.
Each item above was assigned an appropriate Level of Automation in the progression towards an
enterprise-wide system for the utility. Then each item was prioritized to identify how the issue can be
addressed. Figure 3-7 displays the needs, priority level, and how they will be addressed for each area
discussed above.
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-34
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 3-7. Summary of Needs
City of Carlsbad / CMWD SCADA Master Plan Section 3
3-35
SC07221_FINAL_Carlsbad SCADA Master Plan
The master plan document will define the five planning elements that will be developed and
provided.
1. Master Plan, creation of which will be addressed during the master planning process.
2. Foundational Structures, which are needed to progress successfully with the SCADA
Implementation Plan and can be completed concurrently with the Master Plan.
3. Immediate Improvements, which will be identified in the SCADA Implementation Plan as the
most urgent work.
4. Core Improvements, which will be completed through the SCADA Implementation Plan.
5. Future Improvements, which will be able to build upon the SCADA Implementation Plan and will
be key components of a future Technology/Smart Utility Master Plan.
These findings will lead to a full implementation plan that will guide the process of moving towards
full automation maturity:
Figure 3-8. Prioritized Progression of Level of Automation
4-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Section 4
PLC and HMI Standardization
4.1 Introduction
Based on the needs and deficiencies identified in the second phase of the Master Plan, PLC and HMI
technology were selected to meet the future vision for the SCADA system. These technologies will
become the standard for the future SCADA system, allowing the City/CMWD to enter into a long-term
contract for both PLC hardware and HMI software. This section presents a methodical selection
process, using an RFP followed by interviews, demonstrations, and reference checks to determine
the best fit for the City/CMWD’s needs.
4.2 RFP Approach and Development
4.2.1 Approach
The major findings from the second phase of the Master Plan were categorized into ten major
categories of system improvement opportunities (listed on the right in Figure 4-1). These ten
categories were used to establish criteria around which the City/CMWD can standardize HMI
software and PLC hardware. The process of standardizing HMI software and PLC hardware required
the development of an RFP to solicit proposals from vendors and distributers that were evaluated
based on the established technical criteria and long-term cost-competitiveness. The included Figure
4-1 provides an overview of how the evaluation criteria were established from the needs and desires
that were determined through the second phase of the Master Plan. The 10 key areas that formed
the requirements of the HMI system are provided in more detail below and after the Figure.
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-2
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 4-1 HMI Evaluation Criteria
Section 4
4-3
SC07221_FINAL_Carlsbad SCADA Master Plan
4.2.1.1 Foundational HMI
HMI software shall meet the foundational HMI needs the City/CMWD has for a functional HMI
system. The new HMI system will need to provide control, monitoring, trending, alarming, data
storage (historian) and reporting for both the water and wastewater systems. The software will have
the capability of being easily deployed for a system the size and scope of the City/CMWD’s current
water and sewer collection systems and will have the features required to work within the provided
network architecture including interfacing with the communications network and possible use
interfaces.
4.2.1.2 Alarming with Criticality Management
HMI software shall have an effective and easy-to-use alarming system and alarm criticality
management. Notification capabilities, alarm logging, and management features will be a priority for
the alarming system evaluation. The HMI system should be able to assist the City/CMWD with
establishing a standard for how alarms are managed, tracked, and processed to allow the system to
be streamlined for operator efficiency and ease-of-use. The intent is to use alarms in a way that is
useful in the management of the system and ensure no nuisance alarms.
4.2.1.3 High Performance HMI
HMI software shall utilize “high performance HMI” concepts to create an intuitive and informational
user interface. The high performance HMI will make the new HMI simple, intuitive and easy to learn.
Process information will be portrayed in a manner that is contextual and assists the operator with
efficient decision-making without requiring institutional knowledge gained only through experience
with the system. Software will be evaluated for any features that will help build a high performance
HMI.
4.2.1.4 Redundancy
HMI software shall support redundancy and failover for multiple modes of system failure. The goal of
this evaluation criteria is to ensure continual function of critical system aspects in case of failure of
both hardware and software. Transitions during failover should be as seamless as possible to
prevent the loss of process control or system data.
4.2.1.5 Historian and Data Access
HMI software shall include a data historian that will log historical data that can be accessed for
reporting and analytical use. Software will be evaluated based on the features and functionality of
the historical database, data access capabilities, and value added through providing business
intelligence insight, chain of custody management, and data filtering and validation. The historian
has to be compatible with Microsoft SQL for connectivity with other City/CMWD systems.
4.2.1.6 Enterprise Systems Compatibility
HMI software shall interface with enterprise business applications across the proposed network
architecture. To interface with the enterprise business applications, compatibility will be required
with the software used on the enterprise system and the database system used to host the software
data. HMI software will be evaluated based on compatibility with the proposed enterprise software
and any advantages that can be offered interfacing with said software.
4.2.1.7 Security
HMI software shall meet or exceed the security standards required by the City/CMWD. Specific
security criteria have been established by working with the City/CMWD’s IT personnel to determine
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-4
SC07221_FINAL_Carlsbad SCADA Master Plan
the best questions to ask the proposers to evaluate the quality of their cyber-security practices.
Specific security requirements have been provided for the proposer’s response to ensure compliance
with industry best-practices.
4.2.1.8 Future Development
HMI software shall offer features and functionality that will be conducive to efficient future
development and programming of the HMI system. The software will be evaluated on any capabilities
offered that will allow for programming standardization using templates, objects, or other pre-canned
solutions. The software will also be evaluated on its ability to facilitate future system expansion and
changes economically and with minimal disruption. These features are important for reducing
external factors that impact total long-term cost of maintaining the HMI system.
4.2.1.9 Optimization Capabilities
HMI software shall incorporate additional associated products or features that can use process data
to optimize the water or sewer collection system efficiency through direct control or by guiding
operator decision making. Use of optimization products or features will allow the City/CMWD to
realize long-term value through increased efficiency and decreased costs.
4.2.1.9.1 Future Stability and Support
The HMI software proposer shall provide direct support options for the HMI software including
warranty, software updates/upgrades, and priority technical support. The proposer will also be
evaluated on assurance of the longevity of the company and proposed product, industry-specific
support capabilities, and availability of local vendors and integrators/contractors that will be able to
support the product.
4.2.2 HMI Software RFP Development
Based on the criteria developed through an understanding of the City/CMWD’s needs from phase
two of the Master Plan, an RFP was developed to provide a clear evaluation process for proposed
HMI software. The RFP was coordinated with the City/CMWD’s procurement rules to offer a fair and
unbiased system for picking an HMI software to standardize on. An evaluation framework was
developed to allow for scoring of responses across the array of selection criteria. Responses were
evaluated using proposed fixed and long-term costs, a series of guided response questions, and
structured requirement response tables.
4.2.2.1 Proposal Evaluation Framework
The City/CMWD used a point-scoring system to allow the City’s selection committee to evaluate the
submitted proposals in a clear and methodical manner. Points were awarded across the following
sections of the proposal; Fee Proposal Schedule (cost), Technical Requirements, Technical Criteria,
Industry Presence, and Value Added. The combined scores from all these sections contributed to a
total first round score. The top four highest scoring proposals were short-listed to be included in the
second round of evaluation. Table 4-1 below contains a full breakdown of the proposal scoring point
distribution.
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-5
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 4-1. Evaluation Scoring
Evaluation Criterion Maximum Points
Fee proposal schedule (cost) 100
Technical requirements 50
Technical criteria
• Foundational HMI criteria 30
• Alarming with criticality management criteria 10
• High performance HMI criteria 10
• Redundancy criteria 10
• Historian and data access criteria 10
• Enterprise system connectivity criteria 10
• Security criteria 10
• Future development criteria 10
• Optimization capabilities criteria 10
• Future stability and support criteria 20
Industry presence 40
Value added 30
Maximum total points: round 1 350
4.2.2.2 Fee Proposal Schedule (cost)
Each proposer was required to provide a fee proposal schedule to determine a relative cost of the
HMI software over a ten-year span. Costs include the cost of software licensing and support, as well
as any other cost needed to meet the technical requirements defined in Section 3 of the HMI
Software RFP. All requirements of the Fee Proposal Schedule can be found in Section 4 of Appendix
G: HMI Software RFP. The fee proposal was reviewed by the City’s contracts/procurement staff
separately, so it would not influence the technical review of the proposals.
4.2.2.3 Technical Requirements
A series of technical requirements were developed to ensure the proposers ability to provide key
features in the HMI software that will meet the City/CMWD’s needs developed during the second
phase of the Master Plan process. The technical requirements are a series of functionality and
performance specifications corresponding to the ten established categories of evaluation criteria.
Proposers addressed each specification with a response of “Compliant”, “Exception” or “Not
Compliant”. Explanations were only required for an “Exception” response. A response table was
provided in the RFP for proposers to fill in their responses in a standard format. The complete list of
technical requirements is available in Section 5 of Appendix G: HMI Software RFP.
4.2.2.4 Technical Criteria
A series of open-ended response questions were developed to determine how proposers would meet
the needs of the City/CMWD beyond the basic technical requirements. Questions focused on the ten
categories of evaluation criteria developed during the second phase of the Master Plan. The open-
ended questions allowed proposers to provide detailed descriptions of their unique approach and
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-6
SC07221_FINAL_Carlsbad SCADA Master Plan
potential advantages of their product that would fulfill the criteria beyond the basic requirements for
the HMI software. The complete list of technical requirements is available in Section 6 of Appendix G:
HMI Software RFP.
4.2.2.5 Industry Presence
All proposers were required to provide data on their product’s industry presence among Public
Water/Wastewater agencies in North America, California, and within 100 miles of the City. The data
was intended to provide an indication of the potential longevity and stability of the product/firm, and
likelihood of having strong local support from vendors, contractors, and system integrators. Industry
Presence also required that proposers provide local references to be used later in the selection
process. The complete list of Industry Presence questions is available in Section 7 of Appendix G:
HMI Software RFP.
4.2.2.6 Value-Added
Proposers were given a value-added considerations section where they could freely describe any
additional product or service combinations that would add value and benefit the City/CMWD.
Potential areas of value-added include; cost reductions in purchase of additional products, available
products that may be integrated with the HMI system to provide long-term efficiency and savings, or
any other offerings that the proposer believes may add value for the owner. A complete description
of value-added requirements is available in Section 8 of Appendix G: HMI Software RFP.
4.2.3 PLC Hardware RFP Development
To support the PLC hardware needs for the new SCADA system standardization, an RFP was
developed to provide a clear evaluation process for proposed PLC hardware. The RFP was
coordinated with the City/CMWD’s procurement rules to offer a fair and unbiased system for
selecting PLC hardware to standardize on. An evaluation framework was developed to allow for
scoring of responses for basic PLC requirements and some key evaluation criteria common to the
HMI software criteria. Responses were evaluated using proposed fixed and long-term costs, a series
of guided response questions, and a structured requirement response table. PLC programming
software is specific to the PLC and is sold by the PLC manufacturer. It is not a critical part of the
evaluation criteria.
4.2.3.1 Proposal Evaluation Framework
The City/CMWD used a point-scoring system to allow the selection committee to evaluate the
submitted proposals in a clear and methodical manner. Points were awarded across the following
sections of the proposal; Fee Proposal Schedule (cost), Technical Requirements, Technical Criteria,
Industry Presence, Value Added, and References. The combined scores from all these sections
contributed to a final total for the evaluation. The proposal with the highest point total was selected
for standardization. Table 4-2 below contains a full breakdown of the proposal scoring point
distribution.
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-7
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 4-2. Evaluation Scoring
Evaluation Criterion Maximum Points
Fee proposal schedule (cost) 100
Technical requirements 50
Technical criteria
• Foundational PLC criteria 20
• Security criteria 20
• Future development criteria 10
• Future stability and support criteria 30
Industry presence 40
Value added 30
References 50
Maximum total points 350
4.2.3.2 Fee Proposal Schedule (cost)
Each proposer was required to provide a fee proposal schedule to determine the relative cost of the
PLC Hardware over a ten-year span. Costs included the cost of hardware and support, as well as any
other cost needed to meet the technical requirements defined in Section 3 of the PLC Hardware RFP.
All requirements of the Fee Proposal Schedule can be found in Section 4 of Appendix H: PLC
Hardware RFP. The fee proposal was reviewed by the City’s contracts/procurement staff separately,
so it would not influence the technical review of the proposals.
4.2.3.3 Technical Requirements
A series of technical requirements were developed to ensure the proposers ability to provide key
features in the PLC hardware that will meet the City/CMWD’s needs developed during the second
phase of the Master Plan process. The technical requirements are a series of functionality and
performance specifications corresponding to the ten established categories of evaluation criteria.
Proposers addressed each specification with a response of “Compliant”, “Exception” or “Not
Compliant”. Explanations were only required for an “Exception” response. A response table was
provided in the RFP for proposers to fill in their responses in a standard format. The complete list of
technical requirements is available in Section 5 of Appendix H: PLC Hardware RFP.
4.2.3.4 Technical Criteria
A series of open-ended response questions were developed to determine how proposers would meet
the needs of the City/CMWD beyond the basic technical requirements. Questions focused on the
four evaluation criteria relevant to PLC selection; Foundational PLC, Security, Future Development,
and Future Stability and Support. The open-ended questions allowed proposers to provide detailed
descriptions of their unique approach and potential advantages of their product that would fulfill the
criteria beyond the basic requirements for the PLC Hardware. The complete list of technical
requirements is available in Section 6 of Appendix H: PLC Hardware RFP.
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-8
SC07221_FINAL_Carlsbad SCADA Master Plan
4.2.3.5 Industry Presence
All proposers were required to provide data on their product’s Industry Presence among Public
Water/Wastewater agencies in North America, California, and within 100 miles of the City. The data
was intended to provide an indication of the potential longevity and stability of the product/firm, and
likelihood of having strong local support from vendors, contractors, and system integrators. Industry
Presence also required that proposers provide local references to be used later in the selection
process. The complete list of Industry Presence questions is available in Section 7 of Appendix H:
PLC Hardware RFP.
4.2.3.6 Value-Added
Proposers were given a value-added considerations section where they could freely describe any
additional product or service combination that would add value and benefit the City/CMWD.
Potential areas of value-added include; cost reductions in purchase of additional products, available
products that may be integrated with the PLC hardware to provide long-term efficiency and savings,
or any other offerings that the proposer believes may add value for the owner. A complete
description of Value-Added requirements is available in Section 8 of Appendix H: PLC Hardware RFP.
4.3 HMI Evaluation
4.3.1 Round 1 Proposal
4.3.1.1 Submission Process
The HMI Software RFP was posted on July 18, 2018 with a pre-proposal meeting set for August 2,
2018. Prospective vendors in attendance at the pre-bid meeting were given the opportunity to ask
questions regarding the requirements of the RFP. In response to questions posed during the pre-bid
meeting, an addendum was released on August 16, 2018 providing answers to all vendor questions
from the pre-proposal meeting. The addendum is included in Appendix I: HMI Software RFP
Addendum No. 1. All proposals were due on August 23, 2018. Six proposals were received from
vendors for evaluation. Proposed products included; Ignition from Inductive Automation, WinCC OA
from Siemens, FactoryTalk from Rockwell Automation, ClearSCADA from Schneider Electric, VT
SCADA from Trihedral, and Wonderware from Schneider Electric.
4.3.1.2 Scoring
The City/CMWD formed a Selection Committee to evaluate and provide scores for the proposals.
Each member of the Selection Committee reviewed the proposals and provided a score for each of
the evaluation criteria. Scores from individual committee members were averaged together to
determine the final proposal scores in Table 4-3 below. Fee proposal scores were determined
separately by the contract administrator to avoid bias due to cost during the evaluation process.
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-9
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 4-3. HMI Software RFP Scores
Evaluation
Criterion
Maximum
Points ClearSCADA
Factory-
Talk Ignition VTSCADA WinCC OA Wonderware
Fee proposal
schedule (cost)
100 0 0 100 80 0 0
Technical requirements 50 44 43 44 43 43 49
Technical criteria:
1. Foundational HMI criteria 30 25 17 25 27 23 18
2. Alarming with criticality management
criteria
10 8 7 9 10 7 1
3. High
performance HMI
criteria
10 8 6 9 9 7 4
4. Redundancy criteria 10 7 6 8 9 6 2
5. Historian and data access criteria
10 8 5 9 8 7 1
6. Enterprise system
connectivity
criteria
10 7 2 7 9 6 2
7. Security criteria 10 8 5 8 8 8 8
8. Future
development criteria
10 8 4 9 9 7 1
9. Optimization
capabilities criteria
10 8 3 7 8 7 8
10. Future stability
and support criteria
20 16 9 16 15 14 16
Industry presence 40 26 29 33 15 19 39
Value added 30 13 8 15 9 12 17
Total points 350 187 143 300 258 164 167
The top four scoring proposers were chosen from the first round to move on to the second round of
evaluation. Due to the low scores received during the proposal evaluation, WinCC OA and FactoryTalk
were eliminated from consideration in the second round. Scores were based on the responses
provided in the proposals. The RFP had a detailed scoring method for the cost score based on the
lowest cost proposal.
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-10
SC07221_FINAL_Carlsbad SCADA Master Plan
4.3.2 Round 2 Demonstration and Site Visits
4.3.2.1 Demonstrations
Each of the four remaining proposers were invited to give an on-site demonstration of their software
and to answer a series of scripted questions for further evaluation by the Selection Committee. The
script was developed with questions based on the ten evaluation criteria established during the
second phase of the Master Plan. Script questions were designed based on the information gained
during review of the proposals to gain additional details and live demonstrations of the software’s
functionality. A full list of the script questions is included in Appendix K: HMI Software
Demonstrations. Each committee member assigned the demonstrated HMI software a score out of
70 based on the answers given to the script questions. All scores were averaged together for a final
demonstration score. Final scores for each proposer are included in Table 4-4 below.
Table 4-4. HMI Software Demonstration Scores
Committee Member Maximum Points ClearSCADA Ignition VTSCADA Wonderware
Total points 70 35 58 51 66
4.3.2.2 Reference Check
Based on the cumulative score from the first-round proposal evaluation and the scores from the
demonstrations, the top two proposers were selected for a reference check. References were
contacted for both VT SCADA and Ignition and asked a series of questions developed for the
reference check. The full list of example reference-check questions is included in Appendix L: HMI
Software Refrerence-Check Script.
4.3.2.3 Site-Visits
Site-visits were scheduled for reference water/wastewater agencies to see live HMI installations of
the top scoring HMI software.
Staff from the City/CMWD conducted a site-visit to Olivenhain Municipal Water District in Encinitas,
California to see a live installation of the Ignition HMI software. The site visit gave the operators that
will be using the system a chance to see a fully-functional system and ask any remaining questions
that would help the staff feel comfortable with their final decision. Once the site visit was concluded,
the final scores could be determined, and a selection of HMI software could be made.
4.3.2.4 Final Scores
All HMI Software proposers were given a final cumulative score based on their performance during
both rounds of evaluation. The final scores for all proposers are tabulated in Table 4-5 below.
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-11
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 4-5. HMI Software Final Scores
Evaluation
Criterion
Maximum
Points ClearSCADA
Factory-
Talk Ignition VTSCADA
WinCC
OA Wonderware
Round 1 - RFP 350 187 143 300 258 164 167
Round 2 - Demo 70 35 --- 58 51 --- 66
Round 2 –
References
50 --- --- 50 35 --- ---
Round 2 – Site Visits 30 --- --- 30 --- --- ---
Total points 500 222 143 438 344 164 233
Based on the final scores, Ignition by Inductive Automation was selected as the HMI software on
which the City/CMWD will standardize for their future HMI system.
4.3.3 HMI Recommendations
From the results of the RFP process, the City/CMWD has selected Ignition by Inductive Automation
as the HMI Software on which standards will be developed. During the implementation phase of the
SCADA Master Plan, one of the first projects the City/CMWD will need to complete is the
development of an HMI Standards document. The HMI Standards document will include all
requirements for how the HMI software shall be configured across all projects, allowing for
consistency in form and function.
4.4 PLC Evaluation
4.4.1 Proposal
4.4.1.1 Submission Process
The PLC Hardware RFP was posted on July 18, 2018 with a pre-proposal meeting set for August 2,
2018. Prospective vendors in attendance at the pre-bid meeting were given the opportunity to ask
questions regarding the requirements of the RFP. In response to questions posed during the pre-bid
meeting, an addendum was released on August 16, 2018 providing answers to all vendor questions
from the pre-proposal meeting. The addendum is included in Appendix J: PLC Hardware RFP
Addendum No. 1. All proposals were due on August 23, 2018. Four proposals were received from
vendors for evaluation. Proposed products included platforms from; Opto 22, Rockwell Automation,
Schneider Electric, and Siemens.
4.4.1.2 Scoring
The City/CMWD formed a Selection Committee to evaluate and provide scores for the proposals.
Each member of the Selection Committee reviewed the proposals and provided a score for each of
the evaluation criteria. Scores from individual committee members were averaged together to
determine the final proposal scores in Table 4-6 below. Fee proposal scores were determined
separately by the contract administrator to avoid bias due to cost during the evaluation process.
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-12
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 4-6. PLC Hardware RFP Scores Maximum Points Opto 22 Rockwell Automation Schneider Electric Siemens
Total points 350 216 221 183 163
Based on the scoring of the proposals, Rockwell Automation’s Allen Bradley platform was selected
for standardization.
4.4.2 PLC Recommendations
From the results of the RFP process, the City/CMWD has selected the Allen Bradley platform from
Rockwell Automation as the PLC Hardware on which standards will be developed. During the
implementation phase of the SCADA Master Plan, one of the first projects the City/CMWD will need
to complete is the development of an PLC Standards document. The PLC Standards document will
include all requirements for how the PLC Hardware shall be configured and programmed across all
projects, allowing for consistency in form and function.
4.5 LC and HMI Standards
BC recommends the City/CMWD develop programming standards for the HMI and PLC to guide
implementation plan projects being developed as part of the Master Plan. Developing a good set of
standards lays down the foundation for a solid SCADA system from the onset. Enforcing the
standards as the City/CMWD moves into the implementation phase will be the critical step in
ensuring success. In the long term, good governance of the SCADA system will provide a tool that is
useful in improving the efficiency not only in operations but within all aspects of the utility that uses
real-time data.
4.5.1 SCADA System Standards
As the City/CMWD SCADA system grows and changes in complexity and technology, it is critical to
define and standardize the implementation and configuration practices to ensure that the system is
easy to maintain, expand, and develop. SCADA system standards provide an organization’s staff and
contractors with a clear set of guidelines to follow when modifying or adding elements to a SCADA
system. When standards are well-developed and documented, expectations for quality, work
approach, and results are easily ascertainable from the standards documents. This helps an
organization ensure that work is performed in a consistent and desirable manner throughout the
SCADA system and establishes a basis for effectively managing the performance of internal and
contracted staff.
With the selection of new PLC and HMI platforms, the City/CMWD has an opportunity to document
how this new technology should be integrated into a high-functioning SCADA system before the
integration work is started.
To support this transition and development of the City/CMWD’s future SCADA system, BC
recommends that the following standards documents be developed to capture preferences and
standard programming object libraries.
4.5.1.1 PLC Programming Standards
This standards documentation will consist of written guidelines with screenshots and programming
files that specify requirements and standard programming objects for all Allen Bradley PLC platform
programming and configuration work. The programming standards will provide requirements for
City of Carlsbad / CMWD SCADA Master Plan Section 4
4-13
SC07221_FINAL_Carlsbad SCADA Master Plan
detailed documentation within the programs and as supplemental documents. Effort to develop
these standards is captured in the implementation plan.
4.5.1.2 HMI Graphics Standards
This standards documentation will consist of written guidelines with screenshots and programming
files that specify requirements and standard programming objects for programming and
configuration work associated with the Ignition HMI platform. Effort to develop these standards is
captured in the implementation plan.
4.5.2 SCADA System Standards Governance
The development of SCADA system standards often entails a significant investment of time and
money for an organization. This investment is wasted if standards are not enforced or maintained. To
ensure that any standards documents that are developed remain a valuable resource for the
City/CMWD, it is important that the standards be perceived as living documents and responsibility
for their maintenance and enforcement is clearly assigned.
It is recommended that the SCADA system standards be managed, maintained, and updated by a
SCADA manager. The SCADA manager will be technically qualified and willing to participate in
maintaining the standards.
It is expected that a SCADA system standards manager will be required to enforce and continue to
develop the standards. This may be a single individual, or a team of individuals assigned to this role.
The individual(s) in charge of the standards documentation is responsible for revising the standards,
to incorporate any modifications or additions that need to be made as the SCADA system evolves,
and for reviewing the work products of internal and contracted staff to ensure that the standards are
being followed. It is also the responsibility of this individual to maintain careful version control of the
standards documents and files and to ensure that work being put out to bid has appropriate
references to relevant City/CMWD SCADA system standards so that bidding contractors are aware of
the standards and include effort to adhere to them in their bids.
5-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Section 5
Implementation Plan
5.1 Introduction
The fourth phase of the master plan is to develop a 5-year implementation plan that provides the
necessary projects to upgrade the overall SCADA system to the recommended system. The
implementation plan is provided with cost estimates (the engineers’ opinion of probable cost) for the
projects that can be used for budgetary purposes. A workforce assessment was also done to identify
any additional resources that would be needed for the future SCADA system upgrades and
maintenance.
5.2 Approach
A summary of all improvements and the breakdown of the overall implementation plan is discussed
in this section.
5.2.1 Improvements
The overall goal of the SCADA implementation plan is to migrate three utility systems, wastewater,
potable water, and recycled water, over to the new standardized HMI and PLC platforms. Migration to
these platforms will enable improvements to be made in monitoring and control to meet City/CMWD
needs. The long-term goal of these improvements is to use the upgraded control system as a base to
implement a smart utility concept to integrate external data and software packages with the control
system HMI to provide better operational intelligence. The standardized HMI and PLC platforms are
defined in TM-3: PLC and HMI Standardization.
5.2.2 Phase Breakdown
The implementation plan is broken down into the four separate phases to maintain an overall
organizational framework and manage task sequencing. Each phase builds on the tasks completed
in previous phases. Phase 1 includes tasks needed to prepare for design and improvements in
Phases 2 and 3. Phase 2 includes design and construction for wastewater system improvements
and Phase 3 includes design and construction for potable water and recycled water system
improvements. Phase 4 includes a smart utility master plan and associated implementation tasks.
5.3 Implementation Phase
This section defines the individual tasks that will be included in each of the phases of the
implementation plan. The individual tasks serve as the basis for estimating costs for the phases and
building an overall implementation schedule.
5.3.1 Phase 1: Foundational Structures
Foundational structures required for implementation include the development of standards,
documentation of the current systems, and preparation of staff resources and space requirements
for the control system migration. These tasks are intended to improve efficiency and ensure quality
during design and implementation in future phases. The following tasks are included in this phase:
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-2
SC07221_FINAL_Carlsbad SCADA Master Plan
1. Develop PLC and HMI programming standards
2. Develop system integrator pre-qualification requirements
3. Hiring process for new SCADA system manager
4. Document wastewater system and process control to prepare for design
5. Document water/recycled water system and process control to prepare for design
6. Wastewater control and communications system hardware standards development
7. Develop required spaces for HMI network/server room, operational technology lab/technician
area, and operations control room
5.3.2 Phase 2: Immediate Improvements/Needs
This phase primarily addresses modifications needed for the wastewater control system. The current
system allows monitoring, but not control of lift stations, via cellular data. The wastewater system
migration is identified as a priority because the current system has limited capabilities and the
transition to a new system will allow the existing monitoring system to be kept online, reducing
complexity during commissioning. The wastewater system will be an ideal test-case for the new
HMI/PLC platforms before upgrading the water and recycled water systems in the next phase. The
following tasks are included in this phase:
1. Wastewater system PLC replacement design, including:
a. Design for wastewater instrumentation improvements
b. Coordination with control system hardware standards development
c. Development of cutover and sequencing plans
2. Wastewater system competitive bid and contractor selection
3. Wastewater system PLC replacement, including:
a. Factory testing of new systems
b. Testing and commissioning/startup of new systems
4. Wastewater system and core backbone communications upgrades
5. Installation and configuration of redundant HMI servers
6. Configuring wastewater system HMI to enable remote control of wastewater system
7. Providing tiered access levels for HMI
8. Providing wastewater system remote HMI access via laptops/tablets
9. Setting up structured query language-based HMI historian
10. Integrating HMI historian with information technology (IT) requirements
11. Connecting control system to third-party wastewater data from Smart Covers
12. Automating collection of data from the field
13. Training staff for improvements
14. Adding wastewater system flow monitoring
15. Adding suction and discharge pressure monitoring for wastewater system
16. Adding wastewater system permanent gas detection monitoring
5.3.3 Phase 3: Core System Upgrades
Core system upgrades focus on migration and improvements for the water and recycled water
systems. These systems will build on the new HMI platform and radio communications backbone
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-3
SC07221_FINAL_Carlsbad SCADA Master Plan
established during the Phase 2 improvements. Phase 3 includes many more sites than Phase 2,
which contributes to the larger cost and lengthened schedule for implementation. The following
tasks are included in this phase:
1. Water/recycled water control and communications system hardware standards development
2. Water/recycled water system PLC replacement design
a. Coordinated with control system hardware standards development
b. Includes development of cutover and sequencing plans
3. Water/recycled water system PLC replacement competitive bid and contractor selection
4. Water/recycled water system PLC replacement, including:
a. Factory testing of new systems
b. Testing and commissioning/startup of new systems
5. Water/recycled water system communications upgrades
6. Configuring system HMI for water/recycled water system
7. Providing Multiple Access Groups for HMI
8. Adding water/recycled water system remote HMI access via laptops/tablets
9. Training staff for improvements
10. Completing cybersecurity audit and implement recommendations
11. Design for water/recycled water system instrumentation improvements
12. Water/recycled water system instrumentation improvements competitive bid and contractor
selection
13. Automated water/recycled water system chemical dosing
14. Adding generator monitoring and control at Maerkle
15. Adding jockey pump monitoring and control at Calavera Pump Station
16. Connecting existing field instruments at water/recycled water system sites
17. Adding water/recycled water system water quality monitoring
18. Adding water/recycled water system flow monitoring
19. Adding water/recycled water system permanent gas detection monitoring
20. Adding video security at remote sites for wastewater, water, and recycled water systems
21. Connecting control system to third party water/recycled water data
22. Clean up of existing/abandoned hardware for wastewater, water, and recycled water systems
5.3.4 Phase 4: Future Improvements
Phase 4 is an optional phase which includes the development of a technology/smart utility master
plan to guide additional build-out and integration of software and data systems. These tasks focus
on improvements to the base control system developed in Phases 2 and 3 to add data connectivity
and presentation to support decision-making throughout the utility operations and business systems.
Once Phases 1, 2, and 3 have been completed, the City/CMWD will evaluate whether they will move
forward with Phase 4 and the development of a smart utility master plan. The following tasks are
included in this phase:
1. Completing the technology/smart utility master plan
2. Integrating outside data sources into HMI historian
3. Utilizing technology to present/access data, create data dashboards
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-4
SC07221_FINAL_Carlsbad SCADA Master Plan
4. Integrating HMI historian data with other business systems
5. Integrating computerized maintenance management system with HMI historian data
5.3.5 Implementation Contract Management
The SCADA improvement implementation plan will require several contracts between different
entities and the City/CMWD. To clarify how the different contracts will need to be structured to
execute work, Table 5-1 provides a high-level run-down of key information for each contract. The
budget provided for each contract is based on the maximum estimated cost using a class 3 estimate
(-20% to +30%). Full cost estimate ranges for individual tasks as part of these projects are included
in Appendix N: Opinion of Probable Construction Costs.
Table 5-1. Contract Management
Project/Contract Contract
Type
Prime
Contractor Goal of Project Budget Notes
New HMI and PLC programming standards
development
Existing MSA Design Consultant
Develop HMI and PLC software standards to be
used for future projects
$219,828
Phase 2 wastewater PLC replacement –
design and bid
package
Competitive
bid
Design
Consultant
Design for wastewater system PLC replacements, instrumentation
improvements, and
communications upgrade
$367,939 Includes development of control and communications system hardware
standards for wastewater system
Phase 2 wastewater PLC replacement – installation
Competitive bid System Integrator
Installation of wastewater
control system hardware,
communications hardware installation and configuration, PLC programming, HMI
programming, installation of
instrumentation improvements
$4,171,597 System integrator will be responsible for procurement of PLC/HMI hardware/software
Phase 3
water/recycled water PLC replacement – design and bid
package
Competitive bid Design Consultant
Design for water and recycled water system PLC replacements and communications upgrade
$443,346
Includes development of control and communications system hardware standards for water and recycled water system
Phase 3
water/recycled
water PLC replacement – installation
Competitive
bid
System
Integrator
Installation of water/recycled water control system hardware,
communications hardware installation and configuration, PLC programming, HMI programming
$6,868,597
System integrator will be responsible for
procurement of PLC/HMI hardware/software
Phase 3 instrumentation improvements –
design and bid
package
Competitive bid Design Consultant
Design for water and recycled water system instrumentation
improvements
$309,483
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-5
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 5-1. Contract Management
Project/Contract Contract
Type
Prime
Contractor Goal of Project Budget Notes
Phase 3 water/recycled
water
instrumentation improvements – installation
Competitive
bid
System
Integrator
Installation of water/recycled water
instrumentation
improvements and integration into control system
$3,067,033 Includes removal/clean-up of abandoned
control system hardware
5.4 Climate Action Plan
The City developed a Climate Action Plan (CAP) to reduce city-wide greenhouse gas emissions and
combat climate change. To support these goals, the City plans to reduce greenhouse gas emissions
from water utilities, conveyance, treatment, and distribution by 8 percent by 2035. The CAP
recommends action be taken to improve water utilities (including water supply, wastewater, and
recycled water) conveyance, treatment and distribution, and other system improvements. The
projects included in the City’s SCADA Master Plan have been developed to support the goals of the
overall CAP and take action, as recommended, to improve the water utilities system.
5.4.1 Project Contributions to CAP Goals
The following sections provide overviews of how each phase of the implementation plan will
contribute to achieving the goals of the City’s CAP.
5.4.1.1 Foundation Structures
The foundation structures of the implementation plan will provide the key pre-requisites, information,
and preliminary work needed for the design and construction tasks in subsequent phases.
Preparation of standards, requirements, and system documentation will increase efficiency during
design and construction. Implementation of the recommended tasks during this phase is critical to
ensure the quality and timely delivery of later tasks.
5.4.1.2 Immediate Improvements/Needs
The focus of the second phase, immediate improvements/needs, is to migrate the wastewater
system to the new PLC and HMI platforms. Migration of the wastewater system will provide operators
with additional remote monitoring points and the capability to control lift stations remotely, reducing
the need to travel to the remote sites. Additional lift station data will be easily available, better
informing operator decisions and increasing system efficiency. Over time, the increased access to
system data will provide insight into possible issues or maintenance needs in the wastewater
collections system. Improvements will enable informed decisions to reduce system energy use while
maintaining an effective collections system.
5.4.1.3 Core System Upgrades
The core system upgrades made in the third phase of implementation will migrate the water and
recycled water systems to the new PLC and HMI platforms. Additional monitoring and control
capabilities will be added to the systems. System upgrades will improve decision-making and
optimize system efficiency through improved automated and remote control. Additional data
collection from remote sites and third-party data sources will improve operational decisions when
requesting water from external sources to meet system water demands. The increased efficiencies
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-6
SC07221_FINAL_Carlsbad SCADA Master Plan
from improved data availability will reduce the overall energy impact of the systems and their
contributions to green-house gas emissions.
5.4.1.4 Future Improvements
The fourth phase, future improvements, will include an additional Master Plan to develop projects
that will develop the wastewater, water, and recycled water systems towards the Smart Utility
concept through increased data connectivity and access. Through the integration of the new HMI
platform with external software packages and data sources, advanced analytics and effective data
presentation will be possible. The additional insight gained through these improvements will provide
the City/CMWD with highly improved insight into what areas of the system can be modified or run
differently to increase efficiency. Understanding of possible efficiency gains will better guide future
improvements to further reduce the energy impact of the water utility systems.
5.5 Implementation Plan
This section contains detailed information on the schedule and opinion of probable cost for the
SCADA implementation plan.
5.5.1 Schedule
A project schedule is provided in Appendix M: Implementation Schedule. The implementation plan
follows a staged structure with four sequential implementation phases.
5.5.1.1 Schedule for Phases 1, 2, and 3
Phase 1 of the implementation plan is scheduled to begin in the first quarter of fiscal year (FY) 2019
with the development of PLC and HMI programming standards. This task will be completed under an
existing Master Service Agreement (MSA) with BC. Once a budget has been approved by City council,
additional pre-design work may begin that is not included in the MSA. The projected date for the
additional pre-design work to begin is September 2, 2019.
Once the pre-design work associated with the wastewater system is complete, Phase 2 of
implementation may begin with the wastewater system PLC replacement design in the third quarter
of FY 2019. The projected start of construction during Phase 2 is November 27, 2020. Work on
Phase 2 of the implementation plan will conclude in the second quarter of FY 2021.
Phase 3 of the implementation plan will begin shortly after the start of construction for Phase 2. This
will allow design for Phase 3 to take place during construction for Phase 2, allowing the schedule to
be condensed and for construction for Phase 3 to begin shortly after the conclusion of all Phase 2
work. Construction for Phase 3 is projected to begin on November 5, 2021. A second design period
will begin towards the end of the first construction project (the SCADA migration) to prepare for a
second construction project to make system instrumentation improvements and remove abandoned
hardware. Phase 3 will conclude in the second quarter of FY 2024.
5.5.1.2 Consideration for Timeline of Future Phases
Once work concludes on Phase 3 of the implementation plan, Phase 4 may begin with the
development of a Smart Utility Master Plan. The Smart Utility Master Plan would give the City/CMWD
an opportunity to evaluate new software and technologies to integrate with the new SCADA platform
and other data systems. Several projects have already been identified by the City/CMWD to be
implemented during this phase based on current needs. Additional projects can be developed
through the master planning process based on the future needs of the City/CMWD. At completion of
the implementation projects for the SCADA system, the City/CMWD can evaluate their needs and
decide whether to move forward with Phase 4 and the Smart Utility Master Plan.
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-7
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 5-1. Design-Build Delivery
5.5.2 Alternative Delivery Methods
The terms ‘alternative delivery,’ ‘integrated delivery,’ or
‘collaborative delivery’ are used somewhat
interchangeably to refer to project delivery models,
other than design-bid-build (DBB), that emphasize
greater integration between design and construction.
Design-build (DB) is the most common alternative
delivery method and involves hiring a single entity for
both design and construction, as shown in the adjacent
Figure 5-1.
In practice, there are several variations of the DB
delivery model. Fixed-price DB involves a design and
price competition where potential design-builders
provide a technical proposal and fixed price to
complete the specified work. Fixed-price DB delivery
can be more or less:
• Prescriptive, where technical requirements are defined in detail perhaps to the point of providing
a 30-percent design with the Request for Proposal (RFP) package; or
• Performance-based, where technical requirements are defined in terms of compliance with
recognized standards and performance-based outcomes.
With prescriptive and performance-based DB, the owner has limited input into the design process,
except to confirm that the design conforms to the specified technical requirements and is consistent
with the selected design-builder’s proposal. Changes to any element of the project at a later date can
often lead to change orders.
Distinct from DB, construction manager at risk (CMAR) delivery, like DBB, involves two contracts with
the owner: one for the designer and one for construction. Unlike DBB, however, with CMAR
contracting, the contractor is hired early (typically at or before completion of 30-percent design) and
works collaboratively with the owner and designer as the design progresses. The CMAR contractor
typically provides cost estimating, constructability reviews, and input to value engineering sessions
during this period. The California Pubic Contract Code, Section 20146(a) authorizes CMAR
contracting for counties and ‘public entities’ where members of the County Board of Supervisors
make up the governing body of the ‘public entity.’ As such, it appears that CMAR contracting would
not be an option for the SCADA Master Plan projects.
Another variation is progressive DB, which involves selection of the design-builder primarily on
qualifications with some pricing information (such as a percent fee for overhead and profit, a percent
fee or fixed fee for general conditions, and or fixed billing rates). The selected design-builder then
works with the owner to advance the design to the point where guaranteed pricing, either a
guaranteed maximum price or fixed price, can be negotiated. Compared to fixed-price DB,
progressive DB allows for a greater degree of collaboration with the owner up until the final concept
is selected and guaranteed pricing is negotiated. However, because most pricing is negotiated rather
than obtained through competitive bidding, progressive DB does not necessarily lead to the lowest
price.
A typical progressive DB project development process is shown in Figure 5-2 below.
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-8
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 5-2. Sample Progressive DB Project Development Process
Owners typically select DB for the following reasons:
• A history of problems with low-bid, DBB contracting; such as disputes between designers and
contractors, excessive claims, cost over-runs, and schedule delays.
• Single point of accountability; the owner is not in the middle of disputes between the designer
and constructor.
• Greater risk transfer; risks related to the interface of design and construction, such as
ambiguous construction documents, are typically transferred to the design-builder. The design-
builder also often takes on more risk for schedule and may take performance risk, in situations
where performance requirements can be well defined and measured.
• Earlier price certainty; with fixed-price DB, pricing is obtained at the proposer selection state;
with progressive DB, this typically occurs at about 60 percent design completion.
The Public Contract Code Division 2, Part 3, Chapter 4, Section 22161 authorizes local agencies to
use DB contracting. ‘Local agency’ is defined to include, among other things, counties, cities, and
special districts that operate wastewater facilities, solid waste management facilities, water recycling
facilities, or fire protection facilities. As such, DB contracting could potentially be implemented by the
City although legal review should be conducted to confirm that the CMWD would qualify. Under
Section 22161, projects must be worth at least $1 million to qualify for DB contracting, and the use
of DB contracting must be approved by the governing body of the local agency.
5.5.2.1 Design-Build and the SCADA Master Plan Projects
For the SCADA Master Plan projects, efficiency and risk management benefits could result from
having an integrated team that includes the designer, system integrator, and electrical contractor.
This would avoid finger-pointing and would allow qualifications and experience to be considered in
the selection.
However certain other issues should be considered when determining whether some form of DB
delivery would make sense for implementing the Master Plan. Several of these issues are inter-
related and involve the phasing and timing of work in one way or another.
The phasing plan recommended in this TM involves four phases for implementing the Master Plan:
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-9
SC07221_FINAL_Carlsbad SCADA Master Plan
• Phase 1, among other things, involves establishing standards and system integrator pre-
qualification requirements. The value of the Phase 1 work is estimated at approximately $0.46
to $0.75 million under a design-bid-build method.
• Phase 2, among other things, involves design and replacements of PLCs, installing redundant
HMI servers, and upgrading the core communication system. The value of the Phase 2 work is
estimated at approximately $2.6 to $4.2 million under a design-bid-build method.
• Phase 3, among other things, involves design and replacement of the water and recycled water
PLCs, communication system upgrades, configuring the system HMI for the water/recycled water
system, and providing for remote monitoring and chemical dosing. Phase 3 work is estimated at
$6.6 to $10.7 million under a design-bid-build method.
• Phase 4 involves future work, such as evolving to a Smart Utility.
In order to implement DB delivery, Phase 1 could easily be expanded to include pre-qualification
requirements for the designer and electrical contractor in addition to the system integrator.
Phases 2 and 3 would be the most likely candidates for considering DB delivery. Given the overall
goal of the SCADA implementation plan is to “migrate the three utility systems, wastewater, potable
water, and recycled water, over to the new standardized HMI and PLC platforms,” the integration
benefits from DB would be more fully achieved by issuing a single DB contract for the two phases.
This would allow a single integrator to work on both phases and would have the benefit of continuity
between the phases. Because Phase 3 is planned to begin soon after Phase 2, the work could easily
be combined into a single contract with scheduling constraints that dictate when Phase 3 could
begin.
Another benefit to combining Phases 2 and 3 is that the combined value would be more attractive to
the contracting community (i.e., Phase 2 on its own may be on the small side to be attractive to the
DB market for SCADA-type work).
The biggest challenge to procuring Phases 2 and 3 together is that the work for Phase 2 would be
under the City while Phase 3 work would be under CMWD. As such, a decision as to who should be
the contracting party would need to be made between the City and CMWD. In addition, the contract
would likely need to include requirements about keeping costs segregated so that they could be paid
from the appropriate fund.
If the two phases cannot be combined, the benefits of DB delivery would be more limited in that
separate DB contracts would be required for each phase, creating the risk of a misalignment
between phases due to each DB contract potentially having a different integrator.
5.5.2.2 Which Type of Design-Build Delivery?
If the City and CMWD wish to move ahead with Phases 2 and 3 as a single DB project, they would
also have to select the type of DB delivery to use. The selection of fixed-price DB versus progressive
DB involves tradeoffs, as noted in Table 5-2 below.
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-10
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 5-2. Design-Build Method Comparison
Select Fixed-Price DB if: Select Progressive DB if:
• Early possible pricing / most competitive pricing is most
important AND
• Project requirements can be well defined either on a prescriptive or performance basis or some combination thereof AND
• There is sufficient time to develop those documents prior to the time required for issuing an RFP
• A high degree of interaction between the City and CMWD and the selected DB is desirable, especially with respect to design and system integration AND
• Project requirements cannot be well defined without the involvement of
the designer/system integrator AND
• It is desirable to expedite the procurement process AND
• Open-book negotiated pricing is acceptable
5.5.2.3 Recommendations
Based on the feedback from experienced DB experts at BC, there may not be significant cost savings
using the DB method of project delivery for a project of this scale. At a larger scale, projects tend to
achieve more cost savings by using DB delivery due to added complexity in the construction phase. It
may be possible to somewhat reduce the project schedule by using the DB method and combining
projects, but there will likely not be any major time savings. Development of more detailed costs and
schedule to determine possible DB savings would require the development of a 30% design for the
projects.
Any cost or schedule savings will largely depend on the quality of the construction manager used in
the DB project. It is important to use a trusted construction manager that is experienced in DB
delivery and will focus on providing the most benefit to the City/CMWD. An experienced DB
construction manager will be able to identify opportunities for condensing schedules and reducing
costs by considering sequencing and constructability early in the DB process.
5.5.2.4 Next Steps
If the City and CMWD are interested in potentially pursuing DB delivery, BC recommends Phase 1
include a “market sounding” of potential DB teams. This typically involves two-steps. The first step is
informal outreach out to potential designers, integrators, and electrical contractors to verify that
there is sufficient market interest to justify moving forward. The second step involves individual
interviews of project teams to further confirm interest, obtain input on the procurement process, and
identify any issues or concerns that could be an impediment to obtaining sufficient market response
to Requests for Qualifications and/or RFPs.
5.5.3 Opinion of Probable Cost
The opinion of probable cost for the implementation plan tasks are included in Appendix N: Opinion
of Probable Construction Costs. The costs were divided among the three utility systems (wastewater,
water, and recycled water) based on which system would benefit from the given task. Figure 5-3
provides a summary of the ranges of the opinion of probable cost for each of the utility systems.
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-11
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 5-3. Summary of Estimate Ranges
Opinions of probable cost provided within this TM are for planning purposes only and are not
intended to provide actual cost of hardware, installation, or professional services. The opinion of
probable costs is based upon Association for the Advancement of Cost Engineering International
(AACE) criteria for Class 3 estimates; these conceptual estimates are used to prepare planning cost
estimates. The expected accuracy for a Class 3 estimate can range from 20 to +30 percent
depending on the basis of the cost estimate.
Construction cost estimates, financial analyses, and feasibility projects are subject to many
influences including, but not limited to, price of labor and materials, unknown or latent conditions of
existing equipment or structures, and time or quality of performance by third parties. Such influences
may not be precisely forecasted and are beyond the control of BC. Actual costs incurred may vary
substantially from the estimates provided. BC does not warrant or guarantee the accuracy of
construction or development cost estimates.
5.5.3.1 Scheduled costs
Based on the proposed implementation schedule, the opinion of probable cost can be scheduled out
across the span of the implementation project to determine how the costs will break down by fiscal
years. Figure 5-4 below provides the cost incurred by each utility system (wastewater, water, and
recycled water) for each fiscal year through the end of Phase 3.
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-12
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 5-4. Scheduled Implementation Costs
5.6 Workforce Assessment
This section provides a summary of skill set requirements to support the proposed implementation
plan projects and how current City/CMWD staffing aligns with these roles. The section also includes
workload projections for these roles on identified SCADA projects, where workforce shortages are
anticipated in the next 5 years, and how workforce shortages may be remedied through staff
augmentation.
5.6.1 Staffing Options
Two different sources of labor are considered when evaluating staffing options to cover workforce
shortages: contract labor and direct hire. Each option has advantages and disadvantages depending
on the long- and short-term staffing needs and the availability of required skill-sets.
Contract labor yields production at comparatively low initial hiring and training costs, with high long-
term marginal cost. Contract labor is the preferred method for staffing short-term resource needs or
providing specific external expertise. It is recommended that the City/CMWD maintain a list of
prequalified firms for contract labor to ensure that the project requirements are being assessed and
executed by competent individuals. Contracted labor may result in workers with less familiarity with
City/CMWD systems; however, they typically maintain a high standard within specific provided skill
sets. By using prequalified firms consistently and maintaining programming standards, familiarity
with City/CMWD systems can be built over time to increase labor efficiency when using contract
labor to address workforce needs.
Contrary to contract labor, direct hire staff have increased initial hiring and training expense but
decreased long-term marginal cost of employment. Directly hiring staff is the preferred method for
long-term resource needs or developing internal organizational expertise. Overhead costs should be
considered when directly hiring staff, particularly during training periods. Hiring should be based on
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-13
SC07221_FINAL_Carlsbad SCADA Master Plan
projected workload demand to keep utilization rates high. Skill sets must be clearly defined and
vetted during the hiring process to ensure hired staff meet job expectations.
5.6.2 Skills Sets Evaluation
For SCADA or data-centric implementation projects and ongoing maintenance efforts to be
successful, it is important that individuals with the right skill sets are involved and that these
resources have availability to adequately support the schedule requirements of the work to be done.
Skill sets can be acquired from a variety of sources including existing City/CMWD staff, directly hiring
additional resources, or using third-party consultants and contractors to supplement City/CMWD
staff. An overview of the specific individual skill sets that will be required for implementing the
implementation plan projects, as well as the associated follow-on maintenance activities, are listed
in Table 5-3. In many cases, one individual may be capable of fulfilling more than one of the skill sets
requirements. However, reasonable staff workload levels must be maintained to avoid over-
commitment scenarios, leading to staff-shortages or burn-out.
Note: Core implementation and construction resources such as engineers and general electrical and
controls contractors are assumed to be third parties hired on an as-needed basis by the City/CMWD
and are not included in the skill set requirements listed in Table 5-3.
Table 5-3. Skill Set Requirements
Skill Set Description
Analytics translation
Responsible for developing and maintaining standards for data visualization and analytics interfaces for end users, coordinating with end users to determine data analytics requirements, and directing technical resources in the data science program implementation efforts. Must understand core business and strategic processes to
present data effectively to end users and assist leaders in making effective business decisions.
Construction inspection Site- and work-based inspection and quality control of third-party contractors’ and consultants’ work, including electrical, instrumentation, network infrastructure, and controls.
Construction management Management of the project during construction, including oversight of contractors, scope, quality, schedule, and budget.
Construction operations
management
Support SCADA migrations and updates by coordinating outages, manual operations, bypass planning, and
shutdown and startup activities to ensure that systems remain operational during construction.
Database administrator Design, maintain, and manage PCS and other informational databases including archiving, data redundancy,
validation, and query/aggregation development and management.
IT maintenance Maintaining and managing the PCS and user computers, servers, and associated network including troubleshooting, additions, hardware updates, virus/malware management, and software patches.
Network administrator Management and configuration of network resources and associated upgrades. Responsible for developing policies, coordinating network modifications, maintaining domain controllers, and managing network stability.
Procurement and contract
management
Development of the procurement contracts, selection process, and conditions for hiring of outside services and
procurement of required hardware and software.
Project management Project management of the engineering and planning development including managing deliverables, schedule, scope, and budget.
SCADA programming Programming and configuration of PLCs, OITs, and HMI platform, including general troubleshooting and maintenance, additions, and firmware updates.
Security administrator Securing of network resources and management of associated upgrades. Responsible for developing security
policies, coordinating network security modifications, and managing access.
Technology management Management of the additions and modifications of the system to set overall direction, policies, standards, level of technology integration, and user management. Maintain system standards, select balance of technology
updates, and manage technology patches and versions to ensure technology stability and reliability.
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-14
SC07221_FINAL_Carlsbad SCADA Master Plan
5.6.2.1 Existing Workforce Summary
To help the City/CMWD assess its current coverage of the required skill sets among City/CMWD
staff, Table 5-4 lists the staff members whom BC believes will participate in the implementation plan
projects along with the skill sets they are anticipated to contribute to these efforts. The table should
not be mistaken for an assessment of staff capabilities and captures only what BC believes to be
each staff member’s current primary role(s) within the organization based on discussions with staff
during the Staffing Assessment Workshop. City/CMWD staff may need to fill skill set roles that are
not attributed to them in Table 5-4 to support implementation plan efforts, ongoing and future
design and construction projects, and routine operations and maintenance activities.
Table 5-4. Workforce Role Summary
Staff Member Analytics Translation Construction Inspection Construction Management Construction Operations Management Database Administrator IT Maintenance Procurement and Contract Management Project Management Network Administrator SCADA Programming Security Administrator Technology Management Asset Manager
Water Operations Supervisor
Wastewater Operations Supervisor
Water Operations Staff 1
Water Operations Staff 2
Wastewater Operations Staff 1
Wastewater Operations Staff 2
City IT Team
City DBA
Management Analyst
Meter Supervisor
Business Specialist 1
Business Specialist 2
City CM&I
5.6.3 Workload Projections
Workload estimates were developed for all implementation tasks to determine the hours of effort
that would be required in each of the skill sets during each year of implementation. Based on the
scheduling of implementation tasks, workload was distributed over the 5 fiscal years from the start
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-15
SC07221_FINAL_Carlsbad SCADA Master Plan
of the implementation plan. The resulting skill-set and workload projections provide insight into the
staffing needs the City/CMWD will face over the course of the implementation plan as well as during
long term support of the control system improvements. Figure 5-5 provides the distribution of
workload across different skill set over the 5 years of the implementation plan. A year-by-year
breakdown of how this workload could be distributed across existing staff and new hires is provided
in Appendix O: Workload Projections.
Figure 5-5. Project Workload by Year
5.6.4 Recommendations
This subsection provides recommendations for augmenting the City/CMWD staff to support the
implementation plan for the next 5 years and to maintain the new SCADA system and additional
assets resulting from the implementation plan. The recommendations are based on the projected
workload and understanding of staff availability (Appendix O: Workload Projections) to support the
implementation and running of the new SCADA system.
City of Carlsbad / CMWD SCADA Master Plan Section 5
5-16
SC07221_FINAL_Carlsbad SCADA Master Plan
5.6.4.1 SCADA System Manager
Based on the results of the workload projections, the City/CMWD has a near-term need to hire on a
SCADA system manager prior to project implementation to provide the skillsets required for the
SCADA improvement projects. The skillsets needed for the SCADA system manager include SCADA
programming, project management, database administration, network administration, security
administration, and technology management. These skills will be required to coordinate and manage
work with the system integrator, develop and enforce City/CMWD design and programming
standards, and maintain hardware and software for the new PLC and HMI platforms. The SCADA
system manager will also be responsible for managing the work of a SCADA system analyst, who will
be responsible for junior-level SCADA programming and maintenance needs.
The SCADA system manager should be hired before starting any major implementation projects,
while standards are being developed. This will provide the opportunity for the SCADA system
manager to provide their input and “buy-in” to the programming and hardware standards. Once
implementation begins, the SCADA system manager will be heavily utilized supporting and managing
the implementation projects.
5.6.4.2 SCADA System Analyst
To support the long-term needs of the City/CMWD, a SCADA system analyst should be hired to work
under the SCADA system manager. The junior level SCADA system analyst will help support the
SCADA system manager to alleviate projected work overloads and should be trained by the SCADA
system manager to be able to assume their roles and responsibilities as needed. The SCADA system
analyst should have a similar technical skillset to the SCADA system manager but will not be
expected to have as much experience or project management skills. Over time, the SCADA system
analyst should develop the skills to take more responsibility from the SCADA system manager and
bridge any gap if the SCADA system manager is unavailable or leaves the City/CMWD.
The SCADA system analyst should be hired before the implementation projects are complete to
provide an opportunity for the analyst to familiarize themselves with the new equipment and
standards before installation is completed and long-term support of the system is needed.
5.6.4.3 Construction Management and Inspections
The City/CMWD will need to involve their construction management (CM&I) group for construction
management tasks during the execution of the implementation projects. To supplement the
availability of the CM&I group, use of a third-party contractor for construction management services
should be considered. The City/CMWD has an existing relationship with Rockwell Construction
Services (RCS) through previous contracts and could use RCS to cover workload related to
construction management and inspection services. Contracting labor through RCS would allow the
City/CMWD to reduce the workload impact on their CM&I group during implementation.
6-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Section 6
Radio Communications System
6.1 Overview
To develop a detailed plan for migration in the future towards a communications system that
supports the SCADA needs of the City/CMWD. Brown and Caldwell (BC) performed a field survey to
document the existing communication system hardware including the type of communication, radio
frequency, radio type, antenna direction, antenna heights, and location. This report is included in
Appendix C: Radio Communications Field Report.
Using the information collected during the filed survey BC performed a desktop radio path study
(radio study). A radio study is conducted using software to model radio paths and generate radio link
profiles. The software that BC used, LinkPlanner(v4.8.8) by Cambium Networks, integrates with
Google Earth to locate radios sites and provide the topology between the sites to generate the radio
link profile. This document contains the findings of the radio study for water and wastewater sites
identified through field survey and by the City/CMWD.
The findings of the radio study are theoretical. The software does not account for radio interference,
or recent construction. These findings must be verified by a radio frequency (RF) site survey (radio
survey). A radio survey is a field study where mobile radio equipment is set up at each either end of a
radio link. The equipment is manipulated (antenna height, radio frequency) to determine the
antenna height and type for a given frequency. The radio survey also notes if there is interference
(other radios) it the area.
6.2 Summary
The desktop radio path study involved 60 sites (32 Potable, 11 Reclaim, 13 Wastewater, and 2
Operations). Seven master sites were designated, to act as a redundant ring. The study for these
sites was conducted between the frequencies of 23 and 26 GHz. This frequency band provides for is
ideal for a long-range high bandwidth network. This was done to develop a backbone for all other
remote sites. These sites are listed in Table 6-1. Desktop Radio Study List and shown in the
Appendix P: Radio Communications Site Map.
Each remote site study was conducted at three bandwidths; 900 MHz, 3.6 GHz, and 5 GHz. Of the
remote sites studied, the data collected suggested the 900 MHz frequency attained the best
predicted connectivity across the network under current site conditions. The study information below
is conducted at unlicensed 900 MHz frequency.
6.3 Alternative Communications Systems
To provide a comprehensive view of potential means of communication between the City’s
water/wastewater sites BC briefly evaluated using cellular telemetry and fiber optic lines. Early into
the evaluation the City determined that the cellular telemetry was not preferred and that the City’s
fiber optic network does not have the capacity to service the water/wastewater sites. The
technologies are described below.
City of Carlsbad / CMWD SCADA Master Plan Section 6
6-2
SC07221_FINAL_Carlsbad SCADA Master Plan
6.3.1 Cellular Telemetry
Cellular telemetry uses mobile broadband technology. This technology is managed and made
available through third-party providers. Cellular services generally do not include data management
support. Customers of cellular services are limited in the ability to troubleshoot communication
subject to the third-party providers. Cellular services are charged a monthly premium based amount
of data transmitted per site. Feasibility of cellular services is dependent upon third-party providers.
This is not be a preferred option of communications for the City/CMWD. Cellular technology may be
considered if radio telemetry is not feasible for remote sites.
6.3.2 Fiber Optic
Fiber optic is a physical communication medium that uses light pulses to send data over an optical
fiber. Fiber optic communication is ideal for transmitting data over large distances. Fiber optics
require large capital investments for new installation. The City/CMWD would be better served using
existing dark fiber in their fiber optic network. The existing fiber optics network does not provide full
coverage to remote sites. The City/CMWD is currently evaluating their fiber optic network to
determine what dark fiber is available for use. The City/CMWD may consider tying into key
communication sites using existing dark fiber to add redundancy in the future.
6.4 Radio Frequency Comparison
Wireless communications use radio frequencies to send data. The use of radio frequencies in the
United States is regulated by the Federal Communications Commission (FCC). The FCC designates
two types of radio frequencies for use licensed and unlicensed. The three radio frequencies surveyed
fall in to both categories. Each of the frequency categories and their advantages and disadvantages
are discussed below.
The radio study conducted by BC was performed using computer software and did not included a
radio survey. As such the findings and recommendations do not consider the possibility of any radio
interference issues. A radio survey is required to determine if unlicensed radio frequencies can be
reliably used in the communications network design. The radio survey is outside of the scope of this
Master Plan.
6.4.1 Unlicensed Frequencies
Unlicensed frequencies are widely used in consumer electronics (telephone, wireless routers, etc.).
The frequencies include 900 MHz, 2.4 GHz, 5.8 GHz and additional frequencies.
Unlicensed radios are commonly used for high-speed, point-to-point radio communications systems
within the water/wastewater industry. This technology has become very popular because of the easy
radio setup and no associated FCC licensing requirements. These radios make use of Frequency
Hopping Spread Spectrum (FHSS) radio technology to minimize interference from other radio
systems in the area on the same frequency band. 5.8 GHz radio technology can reach speeds of 456
Mbps over distances up to 60 miles depending on manufacturer and field conditions.
In FHSS, the radio transmitter and radio receiver are synchronized to hop between subsets of
available frequencies in a pseudo-random sequence known to both sender and receiver. A short
burst of data is transmitted on the current narrowband channel, then the transmitter and receiver
tune (hop) to the next frequency in the sequence for the next data transmission. The radios hop to a
new frequency more than twice per second to minimize the chance of any other radios transmitting
on the same radio frequency at the same time. FHSS is the most common method used to allow
multiple transmitter and receiver pairs to operate in the same space at the same time.
City of Carlsbad / CMWD SCADA Master Plan Section 6
6-3
SC07221_FINAL_Carlsbad SCADA Master Plan
6.4.2 Licensed Frequencies
Licensed frequencies are those which are not available for use by the public. There are fees,
registration and periodic renewal with the FCC required for licensed radios. The FCC licenses
frequencies by region and restricts use of the licensed frequency to the registrant. Licensed
frequencies typically allow for greater speeds as the transmit power of the radios can be greater than
those of unlicensed radios resulting in a better signal. The CMWD currently operates a select number
of licensed radios in the 3.6 GHz range.
6.5 Site List
The table below list all sites analyzed as part of the desktop radio study. This list includes both water,
reclaimed water, and wastewater sites. More details on these sites are presented in Appendix Q:
Radio Communications Site Report Site Reports along with Table 6-1. Desktop Radio Study List.
City of Carlsbad / CMWD SCADA Master Plan Section 6
6-4
SC07221_FINAL_Carlsbad SCADA Master Plan
Table 6-1. Desktop Radio Study List
Site Name Type
Master Sites
CMWD Building Admin Building
D Site Potable
Elm Reservoir Potable
La Costa Hi Reservoir Potable
Maerkle Tower Radio Tower
Santa Fe 2 Potable
TAP Reservoir Potable
D Site
Ayers PRV Potable
Batiquitos LS Wastewater
Encina Pump Station Reclaim
Encina Reclaim PRV Reclaim
Foxes Landing LS Wastewater
Knots Lane LS Wastewater
La Costa Lo Reservoir Potable
Lower El Fuerte PRV Reclaim
Palomar West PRV Potable
Sand Shell LS Wastewater
Twin D Reclaim Pump Station Reclaim
Upper El Fuerte PRS Potable
Zodiac PRV Potable
Elm Reservoir
Chinquapin LS Wastewater
Ellery Reservoir Potable
Home Plant LS Wastewater
May Company PRS Potable
Pine Beach Bathroom Wastewater
Skyline Reservoir Potable
Tamarack/Frazee Beach Bathroom Wastewater
Tanglewood PRS Potable
Terramar LS Wastewater
La Costa Hi
CWA #2 Potable
Mahr Reservoir Potable
Melrose & Corintia Meter Reclaim
Table 6-1. Desktop Radio Study List
Site Name Type
Maerkle Tower
Bressi Potable Pump Station Potable
Bressi Reclaim Pump Station Reclaim
C Reservoir Reclaim
Calavera Recycle Pump Station Reclaim
Cannon LS Wastewater
CWA #3 Potable
El Fuerte LS Wastewater
Faraday Reclaim PRS Reclaim
Maerkle Control Potable
Maerkle Hydro Electric Potable
Maerkle Lower Chlorine Station Potable
Maerkle Upper Chlorine Station Potable
Point D PRV North Potable
Rancho Carlsbad PRS Potable
Robertson Ranch PRS Potable
Santa Fe 2
CWA #6 Potable
Santa Fe 1 Reservoir Potable
Melrose PRV Potable
La Costa PRS Reclaim
Poinsettia LS Wastewater
TAP Reservoir
Calavera Potable Pump Station Potable
CWA #4 Potable
Elm TAP PRS Potable
Laguna/Kelly Potable
Lake Calavera
TAP 4 Potable
Villas LS Wastewater
City of Carlsbad / CMWD SCADA Master Plan Section 6
6-5
Use of contents on this sheet is subject to the limitations specified at the end of this document.
SC07221_FINAL_Carlsbad SCADA Master Plan
6.6 Site Description
Below are descriptions of report table headings, definitions of radio terminology, and dBm range
table.
6.6.1 Report Heading Descriptions and Definitions
Below are heading descriptions for each of the site reports. Included also are additional definitions
of communication specific terminology.
Table 6-2. Field Study Report Heading Descriptions
Heading Descriptions
Subscriber Module (SM) Remote Site
Band Radio Frequency Band: 900 MHz for remote sites/23GHz for Master Sites
Bandwidth Range of frequency within a given frequency band
SM Latitude Subscriber Module latitude coordinate
SM Longitude Subscriber Module longitude coordinate
SM Height (ft) Subscriber Module calculated antenna height
Range (mi.) Distance between SM and AP
Antenna Magnetic Azimuth (deg) Antenna Direction in degrees from magnetic North, SM to AP
Aggregate Throughput (Mbps) The predicted sum of the data rates delivered from SM to AP in megabits per second (Mbps). Acceptable
throughput is dependent on polling times and number of data points at a specific remote site.
Predicted Receive Power The predicted receive power measure in dBm with tolerance
Link Predicted Availability (%) Calculation of predicted availability of link, SM to AP
Access Point (AP) Name Node Site
AP Latitude Access Point latitude coordinate
AP Longitude Access Point longitude coordinate
AP Height (ft) Access Point calculated antenna height
Profile Type Line of sight availability
Additional Definitions
Fresnel Zone One of a series of cylindrical ellipses between the transmitting and receiving radio antennas. The radio signals between the transceivers propagate through the region inside the ellipses.
Received Power The power of the radio signal at the receiving radio antenna measured in decibels in reference to one milliwatt (dBm)
Throughput Rate of message delivery over a communications channel. Measured in megabits per second (mpbs)
Radio Path Profile A graphical representation of the line of sight between two radio antennas, including land elevation between two sites, antenna heights, and the Fresnel zone.
Header (Client, Section Title, or Report Title) References
6-6
SC07221_FINAL_Carlsbad SCADA Master Plan
6.6.2 dBm Range Table
Signal strength is measured in dBm (decibels relative to one milliwatt). Levels of acceptability are
listed below. Marginal may be an acceptable received signal. All signals should be field verified.
Figure 6-1. Signal Strength
6.7 Recommendations
Based on the results of the radio path study, the following figures show a recommended block
diagram layout for the city/CMWD combined SCADA radio communications network. These diagrams
are based on theoretical results and are intended only to provide information for a future radio
survey conducted before construction.
City of Carlsbad / CMWD SCADA Master Plan Section 6
6-7
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 6-2. Radio Study Block Diagram - Backbone
City of Carlsbad / CMWD SCADA Master Plan Section 6
6-8
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 6-3. Radio Study Block Diagram – Elm Reservoir to Maerkle Tower
Header (Client, Section Title, or Report Title) References
6-9
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 6-4. Radio Study Block Diagram – Elm Reservoir to Tap Reservoir to D Site
Header (Client, Section Title, or Report Title) References
6-10
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 6-5. Radio Study Block Diagram – D Site to Elm Reservoir to La Costa Hi
Header (Client, Section Title, or Report Title) References
6-11
SC07221_FINAL_Carlsbad SCADA Master Plan
Figure 6-6. Radio Study Block Diagram – Maerkle Tower to TAP Reservoir to CMWD Building
City of Carlsbad / CMWD SCADA Master Plan
A-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix A: List of Sites
City of Carlsbad
Site Inventory
Water System
1 of 5
Site Name Site ID
Site
Type System
PLC
Make
PLC
Model
Radio
Communications
Site
Surveyed
Bressi WPS9 Booster
Station POTABLE Opto 22 SNAP PAC Ethernet Yes
BRESSI RC PUMP STATION WPS11 Booster
Station RECYCLED
BUENA VISTA PUMP STATION WPS3 Booster
Station POTABLE
CALAVERA HILLS RC PUMP STATION WPS8 Booster
Station RECYCLED
CALAVERA PUMP STATION WPS1 Booster
Station POTABLE
CARLSBAD WATER RECYCLING FACILITY WPS13 Booster
Station RECYCLED
D SITE RC PUMP STATION WPS6 Booster
Station RECYCLED
ELLERY PUMP STATION WPS2 Booster
Station POTABLE
ENCINAS RC TREATMENT PLANT PS WPS5 Booster
Station RECYCLED
Maerkle Booster WPS7 Booster
Station POTABLE Opto 22 SNAP PAC Ethernet Yes
Maerkle Hydro-Electric Hydro Electric Opto 22 SNAP PAC Ethernet Yes
ALGA 1 PRS43 PRV POTABLE None
ALGA 2 PRS44 PRV POTABLE None
ALICANTE PRS PRS69 PRV POTABLE None
AVENIDA ENCINAS PRS70 PRV RECYCLED Yes
Ayres PRS21 PRV POTABLE Opto 22 SNAP PAC Ethernet Yes
BLACKRAIL PRS45 PRV POTABLE None
BOLERO PRS37 PRV POTABLE
BUENA VISTA PRS60 PRV POTABLE None
CAMINO DE LAS ONDAS PRS PRS26 PRV POTABLE None
CANNON PRS PRS52 PRV POTABLE None
CANNON RD PRV PRS83 PRV POTABLE None
CARLSBAD #1/ SDCWA-1 PRS PRS22 PRV POTABLE None
City of Carlsbad
Site Inventory
Water System
2 of 5
Site Name Site ID
Site
Type System
PLC
Make
PLC
Model
Radio
Communications
Site
Surveyed
CARLSBAD #2 PRS PRS76 PRV POTABLE None
CHESTNUT ECR PRS12 PRV POTABLE None
CLEARVIEW / MACARTHUR PRS PRS74 PRV POTABLE None
COLIBRI PRS PRS40 PRV POTABLE None
COLLEGE EAST PRS55 PRV POTABLE None
COLLEGE NORTH PRS PRS19 PRV POTABLE None
COLLEGE SOUTH PRS PRS18 PRV POTABLE None
COLLEGE WEST PRS54 PRV POTABLE None
CWRF EFFLUENT METER PRS88 PRV POTABLE None
D2 POTABLE MAKE-UP PRS PRS23 PRV POTABLE None
D3 EFFLUENT FLOW CTRL VLT PRS24 PRV POTABLE None
D3 INFLUENT FLOW CTRL VLTS PRS25 PRV POTABLE None
DONNA & BASWOOD PRS PRS75 PRV POTABLE None
E RESERVOIR PRS PRS51 PRV POTABLE None
ELLERY HDR PRV POTABLE
ELLERY SUS PRS63 PRV POTABLE
ELM RESERVOIR NORTH VAULT PRS PRS61 PRV POTABLE None
ELM RESERVOIR SOUTH VAULT PRS PRS62 PRV POTABLE None
ELM TAP PRS3 PRV POTABLE
ENCINAS PRS30 PRV POTABLE None
ENCINAS RC PRS PRS70 PRV RECYCLED None
FARADAY PRS80 PRV RECYCLED
FARADAY LOWER PRS PRS72 PRV POTABLE None
FOX TAIL LOOP PRS PRS20 PRV POTABLE None
FROST PRS PRS84 PRV POTABLE None
GROSSE PRS PRS9 PRV POTABLE None
HAILEY PRS11 PRV POTABLE None
HILTON PRS PRS71 PRV POTABLE None
JACKSPAR PRS56 PRV POTABLE
KELLY PRS17 PRV POTABLE
KELLY VAULT PRS PRS58 PRV POTABLE None
City of Carlsbad
Site Inventory
Water System
3 of 5
Site Name Site ID
Site
Type System
PLC
Make
PLC
Model
Radio
Communications
Site
Surveyed
L.C. LO PRS89 PRV POTABLE None
LA COSTA PRS35 PRV RECYCLED
LA COSTA HIGH PRS PRS35 PRV POTABLE None
LA COSTA LOW 2 PRS90 PRV POTABLE None
LA COSTA LOW PRS PRS42 PRV POTABLE None
LA GOLONDRINA PRS PRS39 PRV POTABLE None
LAGUNA RIVIERA PRS57 PRV POTABLE
LAKE SHORE GARDENS PRS PRS28 PRV POTABLE None
LANIKAI PRS PRS29 PRV POTABLE None
LAPIS PRS PRS15 PRV POTABLE None
LAS ONDAS PRS45 PRV POTABLE None
LOWER EL FUERTE PRS38 PRV POTABLE
MAERKLE CONTROL VAULT PRS93 PRV POTABLE None
MAERKLE EFFLUENT VAULT PRS94 PRV POTABLE None
MAY CO PRS7 PRV POTABLE
MELROSE PRS33 PRV POTABLE
OLYMPIA PRS PRS4 PRV POTABLE None
Palomar East Vault PRS92 PRV POTABLE None
PALOMAR OAKS PRS32 PRV POTABLE None
PALOMAR WEST PRS31 PRV POTABLE
POINSETTIA & EAST RC PRS PRS14 PRV RECYCLED None
POINSETTIA & EAST PRS (P)PRS13 PRV POTABLE None
POINSETTIA WEST PRS PRS27 PRV POTABLE None
POINT D PRS49 PRV POTABLE
POINT D SOUTH PRS PRS1 PRV POTABLE None
RANCHO CARLSBAD PRS PRS8 PRV POTABLE None
RANCHO PANCHO PRS PRS34 PRV POTABLE None
RIDE AMERICA PRS PRS50 PRV POTABLE None
RISING GLENN PRS PRS64 PRV POTABLE None
SAGE HIGH SCHOOL PRS PRS85 PRV POTABLE None
SALK PRS PRS81 PRV POTABLE None
City of Carlsbad
Site Inventory
Water System
4 of 5
Site Name Site ID
Site
Type System
PLC
Make
PLC
Model
Radio
Communications
Site
Surveyed
SANTA FE II VAULT PRS95 PRV POTABLE None
SDCWA #3 CARLSBAD PRS PRS73 PRV POTABLE None
SIERRA MORRENA PRS PRS6 PRV POTABLE None
SKYLINE EAST PRS PRS66 PRV POTABLE None
SKYLINE WEST PRS PRS65 PRV POTABLE None
T.A.P. SUSTAINING PRS10 PRV POTABLE
TAMARACK POINT PRS PRS5 PRV POTABLE None
TANGLEWOOD PRS48 PRV POTABLE
TAP #3 PRS PRS10 PRV POTABLE None
TAP #4 CANNON / SDCWA-4 PRS PRS47 PRV POTABLE None
TAP HI/LO PRS2 PRV POTABLE
TWIN D PRV RECYCLED None
TWIN D POTABLE PRV RECYCLED None
UNICORNIO PRS PRS41 PRV POTABLE None
UPPER EL FUERTE PRS36 PRV POTABLE
WHIPTAIL PRS PRS82 PRV POTABLE None
ZODIAC PRS16 PRV POTABLE
B (T.A.P.)WR5 Reservoirs POTABLE
BUENA VISTA WR17 Reservoirs POTABLE
C WR6 Reservoirs RECYCLED
D1 WR10 Reservoirs RECYCLED
D2 WR11 Reservoirs RECYCLED
D3 WR9 Reservoirs POTABLE
E WR4 Reservoirs POTABLE
ELLERY WR2 Reservoirs POTABLE
ELM WR1 Reservoirs POTABLE
LA COSTA HI WR13 Reservoirs POTABLE
LA COSTA LO WR12 Reservoirs POTABLE
LAKE CALAVERA WR19 Reservoirs POTABLE
MAERKLE # 1 DAM WR8 Reservoirs POTABLE
MAERKLE #2 TANK WR7 Reservoirs POTABLE
City of Carlsbad
Site Inventory
Water System
5 of 5
Site Name Site ID
Site
Type System
PLC
Make
PLC
Model
Radio
Communications
Site
Surveyed
PAJAMA WR16 Reservoirs POTABLE
SANTA FE 1 WR15 Reservoirs RECYCLED
SANTA FE 2 WR14 Reservoirs POTABLE
SKYLINE WR3 Reservoirs POTABLE
Carlsbad 3 Turnout POTABLE Opto 22 SNAP PAC Ethernet Yes
D Tanks and Pump Station MCP-1 WPS6
Booster
Station /
Reservoir
POTABLE Opto 22 SNAP PAC Ethernet Yes
D Tanks and Pump Station MCP-2 WPS6
Booster
Station /
Reservoir
RECYCLED Opto 22 SNAP PAC Ethernet Yes
City of Carlsbad
Site Inventory
Sewer System
Site Name Site ID Make Model Radio Communications
PLC
Make
PLC
Model Communications Protocol
Site
Surveyed
Analog
Inputs
Discrete
Inputs
Batiquitos SLS4 Dutec IO Plexer Serial Mission CPN-625 Serial 0 25
Cannon SLS17 Allen Bradley SLC 5/03 Serial Mission CPN-625 Serial Yes 2 13
Chinquapin LS SLS5 Opto 22 B3000 O22 1 3
El Fuerte SLS21 Allen Bradley SLC 5/03 Serial Mission CPN-625 Serial Yes 1 11
Encina AH LS SLS19 Dutec IO Plexer None
Encina-Buena Vista LS SLS20 None
Fox's LS SLS2 Dutec IO Plexer Mission 0 21
Gateshead LS SLS12 N/A None
Home Plant SLS27 Opto 22 B3000-B Serial Mission CPN-625 Serial Yes 0 16
Knots SLS16 Opto 22 SNAP-PS5 Serial Mission CPN-625 Serial Yes 1 7
Poinsettia SLS15 Dutec IO Plexer Serial Mission CPN-625 Serial Yes 5 32
Sand Shell LS SLS18 Opto 22 B3000 Serial Mission CPN-626 Serial 2 7
Simsbury LS SLS13 Dutec IO Plexer Serial Mission CPN-627 Serial 0 12
Terramar LS SLS24 Opto 22 B3000 Serial Mission CPN-628 Serial 1 2
Villas LS SLS9 Opto 22 B3000 Serial O22 CPN-629 Serial 1 2
City of Carlsbad / CMWD SCADA Master Plan
B-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix B: Field Survey Data Reports
Created 2017-10-12 17:19:00 UTC by Derek Schell
Updated 2017-10-18 02:26:19 UTC by Derek Schell
Location 33.1618759688, -117.256372478
Site Name Carlsbad 3
Process Type Inter-connection Point
Power Available 120 VAC
Cell Service Available?Yes
Backup Power None
Site Security Locked Vault
General Notes None.
Signal Description Flow - Magnetic
Signal Notes Owned by Supplier
Carlsbad 3Carlsbad 3
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
Flow - MagneticFlow - Magnetic
Page: 1 of 9
Signal Photo(s)
Signal Description Pressure
Signal Notes Only downstream pressure provided, supplier owned
PressurePressure
Page: 2 of 9
Signal Photo(s)
Panel Name RTU
PLC Description Primary
PLC Make Opto 22
PLC Model SNAP
Communications Type(s)Ethernet
PLC Notes None.
RTURTU
Opto 22Opto 22
Page: 3 of 9
PLC Photos
Panel Notes None.
Page: 4 of 9
Panel Photos
Page: 5 of 9
Network Photos
Area Around Panel / Space
Radio Notes POE based radio mounted on external mast
Page: 6 of 9
Radio Photos
Site Overview(s)
PhotosPhotos
Page: 7 of 9
Page: 8 of 9
Misc Photos
Page: 9 of 9
Created 2017-10-11 20:56:48 UTC by Derek Schell
Updated 2017-10-18 15:31:53 UTC by Derek Schell
Location 33.115727515, -117.2582315
Site Name Poinsettia
Process Type Lift Station
Power Available 480 VAC
Cell Service Available?Yes
Backup Power Generator
Site Security Locked buildings, fence
General Notes Emergency bypass onsite
LCP Description MCC
LCP Notes None
LCP Photo(s)
PoinsettiaPoinsettia
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
MCCMCC
Page: 1 of 36
Page: 2 of 36
Page: 3 of 36
Signal Description Flow - Magnetic
Signal Notes None
Signal Photo(s)
Flow - MagneticFlow - Magnetic
Page: 4 of 36
Signal Description Level - Bubbler
Level - BubblerLevel - Bubbler
Page: 5 of 36
Signal Notes None
Signal Photo(s)
Page: 6 of 36
Signal Description Level - Submersible
Signal Notes None
Signal Photo(s)
Level - SubmersibleLevel - Submersible
Page: 7 of 36
Panel Name Main Control Panel
Main Control PanelMain Control Panel
Page: 8 of 36
PLC Description Legacy
PLC Make IO Plexer
PLC Model Dutec
Communications Type(s)Serial
PLC Notes None.
PLC Photos
IO PlexerIO Plexer
Page: 9 of 36
PLC Description Primary - Mission
MissionMission
Page: 10 of 36
PLC Make Mission
PLC Model CPN-625
Communications Type(s)Onboard Cellular
PLC Notes None.
PLC Photos
PLC Description Alarm Dialer
PLC Make Verbatim
PLC Model VSS
Communications Type(s)Phone Line
PLC Notes None.
VerbatimVerbatim
Page: 11 of 36
PLC Photos
Panel Notes None.
Panel Photos
Page: 12 of 36
Page: 13 of 36
Page: 14 of 36
Area Around Panel / Space
Page: 15 of 36
Panel Name Bubbler Control Panel
Bubbler Control PanelBubbler Control Panel
Page: 16 of 36
PLC Description Primary - Level Controller
PLC Make EG Controls
PLC Model DigiGage 2300
Communications Type(s)None
PLC Notes None
Panel Notes None.
Panel Photos
EG ControlsEG Controls
Page: 17 of 36
Page: 18 of 36
Page: 19 of 36
Area Around Panel / Space
Panel Name Odor Control Panel
Odor Control PanelOdor Control Panel
Page: 20 of 36
PLC Description Primary
PLC Make Allen Bradley
PLC Model MicroLogix 1500
Communications Type(s)Serial
PLC Notes None.
PLC Photos
Allen BradleyAllen Bradley
Page: 21 of 36
Panel Notes None.
Panel Photos
Page: 22 of 36
Page: 23 of 36
Area Around Panel / Space
Make Mission
Model Onboard Cellular
Communications Medium Onboard Cellular
Radio Notes Legacy Leased Line Equipment also
Radio Photos
MissionMission
Page: 24 of 36
Site Overview(s)
PhotosPhotos
Page: 25 of 36
Page: 26 of 36
Page: 27 of 36
Page: 28 of 36
Page: 29 of 36
Page: 30 of 36
Misc Photos
Page: 31 of 36
Page: 32 of 36
Page: 33 of 36
Page: 34 of 36
Page: 35 of 36
Page: 36 of 36
Created 2017-10-12 18:18:10 UTC by Derek Schell
Updated 2017-10-18 15:33:39 UTC by Derek Schell
Location 33.1293875445, -117.265664488
Site Name Bressi
Process Type Booster Pump Station
Power Available 480 VAC
Cell Service Available?Yes
Backup Power None
Site Security Locked Vault
General Notes None.
Signal Description Flow
Signal Notes None
Signal Photo(s)
Signal Description Pressure - Relief Line
Signal Notes None
BressiBressi
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
FlowFlow
Pressure - Relief LinePressure - Relief Line
Page: 1 of 14
Signal Photo(s)
Signal Description Pressure - Discharge
Signal Notes None
Signal Photo(s)
Pressure - DischargePressure - Discharge
Page: 2 of 14
Panel Name Potable Water RTU
Potable Water RTUPotable Water RTU
Page: 3 of 14
PLC Description Primary
PLC Make Opto 200
PLC Model SNAP
Communications Type(s)Ethernet
PLC Notes None.
PLC Photos
Opto 200Opto 200
Page: 4 of 14
Panel Notes None.
Panel Photos
Page: 5 of 14
Page: 6 of 14
Network Photos
Page: 7 of 14
Area Around Panel / Space
Panel Name RTU-2
Panel Notes None.
Panel Photos
RTU-2RTU-2
Page: 8 of 14
Page: 9 of 14
Make Ubiquiti
UbiquitiUbiquiti
Page: 10 of 14
Radio Notes Power Over Ethernet based radio
Radio Photos
Site Overview(s)
PhotosPhotos
Page: 11 of 14
Page: 12 of 14
Page: 13 of 14
Misc Photos
Page: 14 of 14
Created 2017-10-12 18:33:24 UTC by Derek Schell
Updated 2017-10-18 15:35:29 UTC by Derek Schell
Location 33.1378552364, -117.274117135
Site Name Ayres
Process Type PRV
Power Available 120 VAC
Cell Service Available?Yes
Backup Power None
Site Security Locked Panels/Vault
General Notes None.
Signal Description Flow
Signal Notes None
Signal Photo(s)
Panel Name Main Control Panel
PLC Description Primary
AyresAyres
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
FlowFlow
Main Control PanelMain Control Panel
Opto22Opto22
Page: 1 of 9
PLC Make Opto22
PLC Model SNAP-PAC-EB2
Communications Type(s)Ethernet
PLC Notes None.
PLC Photos
Panel Notes None.
Panel Photos
Page: 2 of 9
Page: 3 of 9
Network Photos
Page: 4 of 9
Area Around Panel / Space
Make Ubiquiti
Model Power Bridge
Communications Medium Ethernet
Radio Notes None.
Radio Photos
UbiquitiUbiquiti
Page: 5 of 9
Page: 6 of 9
Site Overview(s)
PhotosPhotos
Page: 7 of 9
Page: 8 of 9
Page: 9 of 9
Created 2017-10-11 22:09:27 UTC by Derek Schell
Updated 2017-10-18 02:34:53 UTC by Derek Schell
Location 33.145099883, -117.30428176
Site Name Cannon
Process Type Lift Station
Power Available 480 VAC
Cell Service Available?Yes
Backup Power Generator
Site Security Locked Building/Fence
General Notes None.
LCP Description MCC
LCP Notes None
LCP Photo(s)
CannonCannon
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
MCCMCC
Page: 1 of 31
Page: 2 of 31
Page: 3 of 31
Signal Description Flow - Ultrasonic
Signal Notes Clamp on
Signal Photo(s)
Flow - UltrasonicFlow - Ultrasonic
Page: 4 of 31
Signal Description Level - Bubbler
Level - BubblerLevel - Bubbler
Page: 5 of 31
Signal Notes None
Signal Photo(s)
Page: 6 of 31
Signal Description Level - Submersible
Level Level - Submersible- Submersible
Page: 7 of 31
Signal Notes None
Signal Photo(s)
Odor Control PanelOdor Control Panel
Page: 8 of 31
Panel Name Odor Control Panel
Panel Notes Explosion Proof
Panel Photos
Page: 9 of 31
Panel Name Main Control Panel
PLC Description Legacy
PLC Make Allen Bradley
PLC Model SLC 5/03
Communications Type(s)Serial
PLC Notes None.
PLC Photos
Main Control PanelMain Control Panel
Allen BradleyAllen Bradley
Page: 10 of 31
PLC Description Primary
MissionMission
Page: 11 of 31
PLC Make Mission
PLC Model CPN-625
Communications Type(s)Onboard Cellular
PLC Notes None.
PLC Photos
Page: 12 of 31
PLC Description Legacy
PLC Make Opto 22
PLC Model SNAP - PS5
Communications Type(s)Serial
PLC Notes None.
PLC Photos
Opto 22Opto 22
Page: 13 of 31
Page: 14 of 31
PLC Description Alarm Dialer
PLC Make Verbatim
PLC Model VSS
Communications Type(s)Serial
PLC Notes Connected to SLC 5/03
VerbatimVerbatim
Page: 15 of 31
PLC Photos
Panel Notes None.
Panel Photos
Page: 16 of 31
Page: 17 of 31
Network Photos
Page: 18 of 31
Page: 19 of 31
Area Around Panel / Space
Panel Name Bubbler Panel
PLC Description Primary
PLC Make EG Controls
PLC Model DigiGage 2300
Communications Type(s)None
PLC Notes None
Bubbler PanelBubbler Panel
EG ControlsEG Controls
Page: 20 of 31
PLC Photos
Panel Notes None.
Panel Photos
Page: 21 of 31
Page: 22 of 31
Area Around Panel / Space
Make Mission
MissionMission
Page: 23 of 31
Model Onboard
Communications Medium Onboard Cellular
Radio Notes None
Page: 24 of 31
Radio Photos
Site Overview(s)
PhotosPhotos
Page: 25 of 31
Page: 26 of 31
Page: 27 of 31
Page: 28 of 31
Misc Photos
Page: 29 of 31
Page: 30 of 31
Page: 31 of 31
Created 2017-10-11 17:22:41 UTC by Derek Schell
Updated 2017-10-18 01:49:45 UTC by Derek Schell
Location 33.0912406231, -117.310474143
Site Name Knots
Process Type Lift Station
Power Available 480 VAC
Cell Service Available?Yes
Backup Power Generator
Site Security Locked building and gate
General Notes None.
LCP Description MCC
LCP Notes None
LCP Photo(s)
KnotsKnots
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
MCCMCC
Page: 1 of 29
Page: 2 of 29
Signal Description Flow
FlowFlow
Page: 3 of 29
Signal Notes None
Signal Photo(s)
Page: 4 of 29
Signal Description Level-Bubbler
Signal Notes None
Signal Photo(s)
Level-BubblerLevel-Bubbler
Page: 5 of 29
Signal Description Level-Submersible Pressure
Level-Submersible PressureLevel-Submersible Pressure
Page: 6 of 29
Signal Notes None
Signal Photo(s)
Main Control PanelMain Control Panel
Page: 7 of 29
Panel Name Main Control Panel
PLC Description Legacy
PLC Make Opto-22
PLC Model SNAP-PS5
Communications Type(s)RS-232
PLC Notes None.
PLC Photos
Opto-22Opto-22
Page: 8 of 29
PLC Description Alarm Dialer
PLC Make Verbatim
PLC Model VSS
Communications Type(s)Phone Line
PLC Notes None.
VerbatimVerbatim
Page: 9 of 29
PLC Photos
PLC Description Mission
PLC Make Mission
PLC Model CPN-625
Communications Type(s)Onboard Cell
PLC Notes None.
PLC Photos
MissionMission
Page: 10 of 29
Page: 11 of 29
Page: 12 of 29
Panel Notes None.
Panel Photos
Page: 13 of 29
Page: 14 of 29
Page: 15 of 29
Page: 16 of 29
Network Photos
Page: 17 of 29
Area Around Panel / Space
Panel Name Bubbler Control Panel
PLC Description Level Controller
PLC Make Fluid Solutions
PLC Model MicroMAC 2300
Communications Type(s)None.
PLC Notes Primary Controller
PLC Photos
Bubbler Control PanelBubbler Control Panel
Fluid SolutionsFluid Solutions
Page: 18 of 29
Panel Notes None.
Page: 19 of 29
Panel Photos
Page: 20 of 29
Area Around Panel / Space
Make Mission
Model Onboard
Communications Medium Cellular
Radio Notes None.
Radio Photos
MissionMission
Page: 21 of 29
Page: 22 of 29
Site Overview(s)
PhotosPhotos
Page: 23 of 29
Page: 24 of 29
Page: 25 of 29
Page: 26 of 29
Page: 27 of 29
Page: 28 of 29
Misc Photos
Page: 29 of 29
Created 2017-10-12 16:30:36 UTC by Derek Schell
Updated 2017-10-18 15:33:10 UTC by Derek Schell
Location 33.1501515722, -117.261547381
Site Name Maerkle Booster
Process Type Booster Station
Power Available 480 VAC
Cell Service Available?Yes
Backup Power Generator
Site Security Fence, cameras, locked building
General Notes Chlorine injection system planned to be replaced
LCP Description MCC
LCP Notes None
LCP Photo(s)
Maerkle BoosterMaerkle Booster
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
MCCMCC
Page: 1 of 32
Page: 2 of 32
Page: 3 of 32
Page: 4 of 32
Page: 5 of 32
Page: 6 of 32
Page: 7 of 32
LCP Description Ammonia CP
Ammonia CPAmmonia CP
Page: 8 of 32
LCP Notes None
LCP Photo(s)
LCP Description Scrubber LCP
LCP Notes None
Scrubber LCPScrubber LCP
Page: 9 of 32
LCP Photo(s)
Signal Description Flow-Pump 4
Signal Notes None
Signal Photo(s)
Flow-Pump 4Flow-Pump 4
Page: 10 of 32
Signal Description Pressure
PressurePressure
Page: 11 of 32
Signal Notes None
Signal Photo(s)
Signal Description CL2 Monitoring
Signal Notes None
Signal Photo(s)
CL2 MonitoringCL2 Monitoring
Page: 12 of 32
Page: 13 of 32
Signal Description Chlorine tank valves
Signal Notes None
Chlorine tank valvesChlorine tank valves
Page: 14 of 32
Signal Photo(s)
Signal Description Scales
Signal Notes None
ScalesScales
Page: 15 of 32
Signal Photo(s)
Signal Description Chlorine Analyzer
Signal Notes None
Signal Photo(s)
Chlorine AnalyzerChlorine Analyzer
Page: 16 of 32
Page: 17 of 32
Signal Description Ammonia Analyzer
Ammonia AnalyzerAmmonia Analyzer
Page: 18 of 32
Signal Notes None
Signal Photo(s)
Panel Name CP-1
PLC Description Opto
PLC Make Opto-22
PLC Model SNAP PAC
Communications Type(s)Ethernet
PLC Photos
CP-1CP-1
Opto-22Opto-22
Page: 19 of 32
Page: 20 of 32
Panel Notes Has remote Wonderware Node
Panel Photos
Page: 21 of 32
Page: 22 of 32
Page: 23 of 32
Network Photos
Page: 24 of 32
Page: 25 of 32
Page: 26 of 32
Area Around Panel / Space
Radio Notes POE roof mounted
Radio Photos
Site Overview(s)
PhotosPhotos
Page: 27 of 32
Page: 28 of 32
Page: 29 of 32
Misc Photos
Page: 30 of 32
Page: 31 of 32
Page: 32 of 32
Created 2017-10-11 17:54:36 UTC by Derek Schell
Updated 2017-10-18 01:47:27 UTC by Derek Schell
Location 33.0930404272, -117.300039344
Site Name Batiquitos
Process Type Lift Station
Power Available 480 VAC
Cell Service Available?Yes
Backup Power Generator
Site Security Locked building and fence
General Notes None.
LCP Description MCC
LCP Notes None
LCP Photo(s)
BatiquitosBatiquitos
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
MCCMCC
Page: 1 of 36
Page: 2 of 36
Page: 3 of 36
Page: 4 of 36
Signal Description Flow - Magnetic
Signal Notes None
Signal Photo(s)
Flow - MagneticFlow - Magnetic
Page: 5 of 36
Page: 6 of 36
Signal Description Level -Ultrasonic
Signal Notes Secondary
Level -UltrasonicLevel -Ultrasonic
Page: 7 of 36
Signal Photo(s)
Signal Description Level - Bubbler
Signal Notes None
Level - BubblerLevel - Bubbler
Page: 8 of 36
Signal Photo(s)
Signal Description Level - Submersible
Signal Notes None
Level - SubmersibleLevel - Submersible
Page: 9 of 36
Signal Photo(s)
Panel Name Bubbler Control Panel
PLC Description Level Controller
PLC Make E.G. Controls
PLC Model DigiGage 2300
Communications Type(s)None.
PLC Notes None.
Bubbler Control PanelBubbler Control Panel
E.G. ControlsE.G. Controls
Page: 10 of 36
PLC Photos
Panel Notes None.
Panel Photos
Page: 11 of 36
Page: 12 of 36
Area Around Panel / Space
Panel Name RTU Panel
PLC Description Primary
PLC Make Mission
PLC Model CPN-625
Communications Type(s)Onboard Celluar
PLC Notes None.
RTU PanelRTU Panel
MissionMission
Page: 13 of 36
PLC Photos
Panel Notes None.
Panel Photos
Page: 14 of 36
Page: 15 of 36
Page: 16 of 36
Page: 17 of 36
Area Around Panel / Space
Page: 18 of 36
Page: 19 of 36
Panel Name Verbatim
PLC Description Alarm Dialer
PLC Make Verbatim
PLC Model VSS
Communications Type(s)Phone Line
PLC Notes None.
VerbatimVerbatim
VerbatimVerbatim
Page: 20 of 36
PLC Photos
Panel Notes None.
Panel Photos
LegacyLegacy
Page: 21 of 36
Panel Name Legacy
PLC Description Legacy
PLC Make Dutec
PLC Model IO Plexer
Communications Type(s)RS-232
PLC Notes Data Aq only, no control
PLC Photos
DutecDutec
Page: 22 of 36
Page: 23 of 36
Panel Notes None.
Page: 24 of 36
Panel Photos
Page: 25 of 36
Network Photos
Area Around Panel / Space
Make Mission
MissionMission
Page: 26 of 36
Model Onboard
Communications Medium Onboard Cellular
Radio Notes None.
Radio Photos
Site Overview(s)
PhotosPhotos
Page: 27 of 36
Page: 28 of 36
Page: 29 of 36
Page: 30 of 36
Page: 31 of 36
Page: 32 of 36
Page: 33 of 36
Misc Photos
Page: 34 of 36
Page: 35 of 36
Page: 36 of 36
Created 2017-10-11 21:38:18 UTC by Derek Schell
Updated 2017-10-18 15:32:10 UTC by Derek Schell
Location 33.1374176173, -117.258019019
Site Name El Fuerte
Process Type Lift Station
Power Available 480 VAC
Cell Service Available?Yes
Backup Power Generator
Site Security Building/Fence
General Notes Bioxide not in use because of low flow
LCP Description MCC
LCP Notes None
LCP Photo(s)
El FuerteEl Fuerte
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
MCCMCC
Page: 1 of 40
Page: 2 of 40
Page: 3 of 40
LCP Description Grinder
LCP Notes None
LCP Photo(s)
GrinderGrinder
Page: 4 of 40
Page: 5 of 40
Signal Description Level - Bubbler
Signal Notes None
Signal Photo(s)
Level - BubblerLevel - Bubbler
Page: 6 of 40
Page: 7 of 40
Signal Description Level - Submersible
Level - SubmersibleLevel - Submersible
Page: 8 of 40
Signal Notes None
Signal Photo(s)
Flow - MagneticFlow - Magnetic
Page: 9 of 40
Signal Description Flow - Magnetic
Signal Notes None
Signal Photo(s)
Page: 10 of 40
Panel Name Main Control Panel
PLC Description Legacy
PLC Make Allen Bradley
PLC Model SLC5/03
Communications Type(s)Serial
PLC Notes None
PLC Photos
Main Control PanelMain Control Panel
Allen BradleyAllen Bradley
Page: 11 of 40
Page: 12 of 40
PLC Description Alarm Dialer
PLC Make Verbatim
PLC Model VSS
Communications Type(s)Phone Line
PLC Notes Used to have a gateway direct to SLC 5/03, now hardwired
VerbatimVerbatim
Page: 13 of 40
PLC Photos
PLC Description Primary - Mission
PLC Make Mission
PLC Model CPN-625
Communications Type(s)Onboard Cellular
PLC Notes None.
PLC Photos
MissionMission
Page: 14 of 40
Page: 15 of 40
PLC Description Legacy
PLC Make Opto22
PLC Model SNAP
Communications Type(s)Serial
PLC Notes None.
PLC Photos
Opto22Opto22
Page: 16 of 40
Page: 17 of 40
Panel Notes None.
Panel Photos
Page: 18 of 40
Page: 19 of 40
Page: 20 of 40
Network Photos
Page: 21 of 40
Page: 22 of 40
Area Around Panel / Space
Panel Name Bubbler Control Panel
PLC Description Level Controller
PLC Make EG Controls
PLC Model DigiGage 2300
Communications Type(s)None.
PLC Notes None.
PLC Photos
Bubbler Control PanelBubbler Control Panel
EG ControlsEG Controls
Page: 23 of 40
Panel Notes None.
Panel Photos
Page: 24 of 40
Page: 25 of 40
Page: 26 of 40
Area Around Panel / Space
Panel Name Odor Control Panel
PLC Description Primary
PLC Make Allen Bradley
PLC Model MicroLogix 1500
Communications Type(s)Serial
PLC Notes None.
Odor Control PanelOdor Control Panel
Allen BradleyAllen Bradley
Page: 27 of 40
PLC Photos
Panel Notes None.
Panel Photos
Page: 28 of 40
Page: 29 of 40
Area Around Panel / Space
Make Mission
MissionMission
Page: 30 of 40
Model Onboard Cellular
Communications Medium Onboard Cellular
Radio Notes None.
Page: 31 of 40
Radio Photos
Site Overview(s)
PhotosPhotos
Page: 32 of 40
Page: 33 of 40
Page: 34 of 40
Page: 35 of 40
Page: 36 of 40
Misc Photos
Page: 37 of 40
Page: 38 of 40
Page: 39 of 40
Page: 40 of 40
Created 2017-10-12 17:00:45 UTC by Derek Schell
Updated 2017-10-18 15:33:22 UTC by Derek Schell
Location 33.1527575478, -117.26144881
Site Name Maerkle Hydro-elec
Process Type Hydroelectric
Cell Service Available?Yes
Backup Power None
Site Security Locked Building
General Notes None.
LCP Description VCP-101
LCP Notes None
LCP Photo(s)
Maerkle Hydro-elecMaerkle Hydro-elec
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
VCP-101VCP-101
Page: 1 of 16
Page: 2 of 16
LCP Description MCC-101
LCP Notes None
LCP Photo(s)
MCC-101MCC-101
Page: 3 of 16
Signal Description Flow - Magnetic
Flow - MagneticFlow - Magnetic
Page: 4 of 16
Signal Notes None
Signal Photo(s)
Page: 5 of 16
Signal Description Pressure
Signal Notes None
Signal Photo(s)
PressurePressure
Page: 6 of 16
Signal Description Vibration
VibrationVibration
Page: 7 of 16
Signal Notes None
Signal Photo(s)
Page: 8 of 16
Panel Name RTU-101
PLC Description Primary
PLC Make Opto 22
PLC Model SNAP-PAC-R1
Communications Type(s)Ethernet
PLC Notes None.
RTU-101RTU-101
Opto 22Opto 22
Page: 9 of 16
PLC Photos
Panel Notes None.
Panel Photos
Page: 10 of 16
Page: 11 of 16
Network Photos
Page: 12 of 16
Area Around Panel / Space
Radio Notes POE radio
Page: 13 of 16
Radio Photos
Site Overview(s)
PhotosPhotos
Page: 14 of 16
Page: 15 of 16
Page: 16 of 16
Created 2017-10-12 17:44:31 UTC by Derek Schell
Updated 2017-10-18 02:24:28 UTC by Derek Schell
Location 33.1122048525, -117.286850838
Site Name D Tanks and Pump Station
Process Type Potable and Reclaimed Tanks, Reclaimed Booster Pump Station
Power Available 480 VAC
Cell Service Available?Yes
Backup Power None
Site Security Locked fence/building
General Notes Several Leased Cellular Antennas on tanks
LCP Description MCC
LCP Notes None
LCP Photo(s)
D Tanks and Pump StationD Tanks and Pump Station
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
MCCMCC
Page: 1 of 21
Page: 2 of 21
Page: 3 of 21
Page: 4 of 21
Signal Description Level - Ultrasonic
Signal Notes None
Signal Photo(s)
Level - UltrasonicLevel - Ultrasonic
Page: 5 of 21
Signal Description Flow - Magnetic
Flow - MagneticFlow - Magnetic
Page: 6 of 21
Signal Notes None
Signal Photo(s)
Panel Name D3 Tank Panel
Panel Notes Radio Switch Panel
Panel Photos
D3 Tank PanelD3 Tank Panel
Page: 7 of 21
Page: 8 of 21
Network Photos
Area Around Panel / Space
Panel Name MCP 1
MCP 1MCP 1
Page: 9 of 21
PLC Description Primary
PLC Make Opto 22
PLC Model SNAP
Communications Type(s)Ethernet
PLC Notes None.
PLC Photos
Panel Notes None.
Panel Photos
Opto 22Opto 22
Page: 10 of 21
Page: 11 of 21
Page: 12 of 21
Area Around Panel / Space
Panel Name MCP-2
MCP-2MCP-2
Page: 13 of 21
PLC Description Primary
PLC Make Opto 22
PLC Model SNAP
Communications Type(s)Ethernet
PLC Notes None.
PLC Photos
Opto 22Opto 22
Page: 14 of 21
Panel Notes None.
Panel Photos
Page: 15 of 21
Page: 16 of 21
Network Photos
Page: 17 of 21
Area Around Panel / Space
Radio Notes POE Based Radio On Site, Mounted top of tank
Radio Photos
Page: 18 of 21
Site Overview(s)
PhotosPhotos
Page: 19 of 21
Page: 20 of 21
Page: 21 of 21
Created 2017-10-11 16:23:23 UTC by Derek Schell
Updated 2017-10-18 01:52:24 UTC by Derek Schell
Location 33.1651920593, -117.35477359
Site Name Home Plant
Process Type Lift Station
Power Available 480 VAC
Cell Service Available?Yes
Backup Power Generator
Site Security Gate and building
General Notes Biofilter onsite
LCP Description MCC
LCP Notes None
LCP Photo(s)
Home PlantHome Plant
GeneralGeneral
Instrumentation/ControlInstrumentation/Control
MCCMCC
Page: 1 of 42
Page: 2 of 42
Page: 3 of 42
Page: 4 of 42
Page: 5 of 42
Page: 6 of 42
Page: 7 of 42
Page: 8 of 42
Page: 9 of 42
Signal Description Level-Bubbler
Level-BubblerLevel-Bubbler
Page: 10 of 42
Signal Notes None
Signal Photo(s)
Page: 11 of 42
Page: 12 of 42
Signal Description Level - Submersible
Signal Notes Compressor failures caused this to no longer be primary
Level - SubmersibleLevel - Submersible
Page: 13 of 42
Signal Photo(s)
Signal Description Flow
Signal Notes None
Signal Photo(s)
FlowFlow
Page: 14 of 42
Panel Name RTU Panel
RTU PanelRTU Panel
Page: 15 of 42
PLC Description Alarm Dialer
PLC Make Verbatim
PLC Model VSS
Communications Type(s)Phone Dialer
PLC Photos
PLC Description Mission
PLC Make Mission
PLC Model CPN-625
Communications Type(s)Onboard Cell
PLC Photos
VerbatimVerbatim
MissionMission
Page: 16 of 42
Page: 17 of 42
PLC Description Legacy
PLC Make Opto 22
PLC Model B3000-B
Communications Type(s)RS-232
PLC Photos
Opto 22Opto 22
Page: 18 of 42
Page: 19 of 42
Page: 20 of 42
Panel Notes None.
Panel Photos
Page: 21 of 42
Page: 22 of 42
Page: 23 of 42
Network Photos
Page: 24 of 42
Page: 25 of 42
Area Around Panel / Space
Panel Name Level Controller Panel
PLC Description Level Controllers
PLC Make E.G. Controls
PLC Model DigiGage 2300
PLC Notes Bubbler is no longer in use, submersible is primary
PLC Photos
Level Controller PanelLevel Controller Panel
E.G. ControlsE.G. Controls
Page: 26 of 42
Page: 27 of 42
Panel Notes None.
Panel Photos
Page: 28 of 42
Page: 29 of 42
Make Mission
Model Onboard
Communications Medium Onboard Cellular
Radio Photos
MissionMission
Page: 30 of 42
PhotosPhotos
Page: 31 of 42
Site Name Plate
Site Overview(s)
Page: 32 of 42
Page: 33 of 42
Page: 34 of 42
Page: 35 of 42
Page: 36 of 42
Page: 37 of 42
Misc Photos
Page: 38 of 42
Page: 39 of 42
Page: 40 of 42
Page: 41 of 42
Page: 42 of 42
City of Carlsbad / CMWD SCADA Master Plan
C-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix C: Radio Communications Field Report
City of Carlsbad – Task Order 2
Field Survey Report
January 2019
Page 1 of 249
City of Carlsbad – Field Study Report
This page intentionally left blank.
Page 2 of 249
City of Carlsbad – Field Study Report
Section 1
Introduction
1.1 Overview
To develop a detailed plan for migration in the future towards a communications system that
supports the SCADA needs of the City, the existing communications system needs to be
understood.
BC performed a field survey to document the existing communication system hardware
including the type of communication, radio frequency, radio type, antenna direction, antenna
heights, and location. During the survey, BC interviewed operations staff to identify any
operations requirements for site-to-site process coordination, current process operations
requirements were undefined.
BC documented the field survey using a custom Fulcrum application. This application allowed
BC employees to gather and record all field information, GPS data, photos and answers to
interview questions electronically.
This document contains the findings of the field survey reports for each water and recycled
water site visited. These findings will be used to develop a theoretical paper radio
communications study.
1.2 Scope
BC performed a field survey to document the existing communication system hardware
including the type of communication, radio frequency, radio type, antenna direction, antenna
heights, and location. During the surveys, BC interviewed operations staff to identify any
operations requirements for site-to-site process coordination. Required process coordination
and dependencies will be considered in the communications path study and
recommendations.
1.3 Report Heading Descriptions
Field Study Report Heading Descriptions
Heading Descriptions
Title Site name
Created Date and time of entry created
Updated Date and time of entry last modified
Location Latitude and Longitude of site
Site Information
Site Name Site name as stated by operator
Site Photos Photo(s) of site taken by BC
Site to Site Coordination Radio name(s) of radio connection
Page 3 of 249
City of Carlsbad – Field Study Report
Field Study Report Heading Descriptions
Heading Descriptions
Process Coordination Indication of operational requirements via operator interview
Communication Information
Communication Type Ethernet or serial based communications
Communication Photos Communication type photo taken by BC
Radios
Radio Name Radio named as stated by operator or Ubiquiti radio export
Radio Type Radio type as stated by operator or Ubiquiti radio export
Radio Type Photos Photo(s) of Radio taken by BC
Radio Frequency Radio frequency as stated by operator or Ubiquiti radio export
Antenna Type Radio antenna type as observed by BC
Antenna Direction Antenna Direction recorded with GPS
Antenna Direction Photos Photo of antenna direction
Antenna Height Photos Photo of antenna height
Antenna Height Antenna height estimated in feet
1.4 Site List
Site and radio names were attained during the field investigation with city operations staff.
Field Report Heading Descriptions
Site Name (as stated by the Operator) Radio Name
Ayers PRV Potable Ayers PRV
Bressi Potable Pump Station Bressi Potable PMP Station
Bressi Reclaim Pump Station Bressi RC Pump Sta.
C Reservoir AP C RES AP
C Reservoir Station C RES Station
Calavera Potable Pump Station Calavera POT PM ST
Calavera Reclaim Pump Station Calavera RC Pump Sta.
CMW Building (900MHz) CMW Admin Free wave
CMW Building (Air Fibre) Master at HQ
CWA # 4 AP CWA#4 365 AP
CWA #2 (VWD) VWD #2
CWA #4 Station CWA #4 Station
CWA #6 CWA #6
Page 4 of 249
City of Carlsbad – Field Study Report
Field Report Heading Descriptions
Site Name (as stated by the Operator) Radio Name
CWA 3 Station CEA #3 Station
D3 East Sector D3 east sector
D3 Reservoir Repeater Unknown
D3 to North Sector D3 to Lake Calavera
D3 Tower to Maerkle Tower D3 Sta 2 M tower
D3 West Sector D3 West Sector
Ellery Reservoir Ellery Sta.
Elm Reservoir Elm East Sector
Elm Reservoir Repeater Elm RES REPEATER
Elm Tap PRS Elm Tap
Encina AP 2 Encina PRV Encina AP 2 Encina PRV
Encina Reclaim PRV Encina Sta. PRV
Encina Reclaim Pump Station ENCINA PUMP STATION
Encina to Palomar West Encina 2 Pal. W NE AP
Faraday Reclaim PRS Faraday RC PRS
La Costa Hi Reservoir LCHI2Mahr AP @ LCH
La Costa Hi to Maerkle Tower LCHI STA 2 MTOWER
La Costa Hi to Melrose & Corintia LCHIAP2M&C
La Costa Lo Reservoir Repeater (900 MHz) La Costa lo Repeater
La Costa Lo Station Repeater La Costa Lo Station
La Costa Lo to Ayres PRV La Costa Lo AP Sector
La Costa Reclaim PRS La Costa PRS
Laguna /Kelly PRS Laguna/Kelly PRS
Lake Calavera lake Calavera 2D3
Lower El Fuerte PRS Lower El Fuerte PRS
M.Tower AP2D3 M.Tower AP2D3
Maerkle Apple Wood Gate Camera MRKLAPPLEWOODGATE
Maerkle Control Maerkle Control
Maerkle Dam Camera Maerkle Dam Camera
Maerkle Hydro HydroElectric
Maerkle Lower Chlorine Station Maerkle scada lower
Maerkle Lower Chlorine Station Camera MRKLLOWERCL2STATION
Maerkle Sunny Creek Gate Camera MRKLSUNNYCREEK
Maerkle Tank Camera MRKLRESDOOR
Maerkle to La Costa Hi M.Tower AP 2 LCHI
Maerkle Tower Free wave Maerkle Free Wave Omni
Page 5 of 249
City of Carlsbad – Field Study Report
Field Report Heading Descriptions
Site Name (as stated by the Operator) Radio Name
Maerkle Tower to SantaFe 2 M.Tower AP 2 SF2
Maerkle Tower to TAP M.Tower AP2TAP
Maerkle Upper Chlorine Station MRKLUPCL2-SCADA
Maerkle Upper Chlorine Station Camera MRKLUPPERCL2STATION
Mahr Reservoir Station-Mahr
May Company PRS May Co. PRS
Melrose & Corintia Meter Vault Melrose & Corintia Station
Melrose PRV Potable Melrose PRV Potable
MRKL-WAP-NORTH MRKL-WAP-NORTH
MRKL-WAP-SOUTH MRKL-WAP-South
Palomar West PRV Palomar WestPRV Station
Point D PRV North Point D PRV
Rancho Carlsbad PRS Rancho Carlsbad PRV
Robertson Ranch PRS Robertson Ranch Sta.
SantaFe 1 Reservoir Repeater SF 1 Res Repeaters
SantaFe 2 Res. Repeater to Maerkle 900 SF 2 Res Repeater
SantaFe 2 Station to Maerkle Tower SF2 STA 2 MTOWER
SantaFe 2 to SantaFa 1 (future) SF2 AP 2 SF 1
SantaFe 2 To West Sector SF2WEST Sector
Skyline Reservoir Skyline Res.
Tanglewood PRS Tabglewood PRS
TAP 4 Station TAP-4 Station
TAP North Sector TAP5G North Sector
TAP RES - B Repeater FreeWave B Res Repeater
TAP Reservoir to Maerkle Tower TAP STA 2MTOWER
TAP to CWA 4 TAP 2 CWA #4
TAP to Ellery TAP AP 2 ELLERY
TAP West AP TAP WEST AP
TAP West Sector Unknown
Twin D Reclaim Pump Station Dsitestation
Upper El Fuerte PRS Upper El Fuerte
Zodiac PRV Zodiac PRV Radio
Sites Not Surveyed
Maerkle Lake Gate Camera* Maerkle Lake Gate Camera
*This radio was found after the city provided additional Ubiquiti radio information.
Page 6 of 249
Created 2019-01-09 16:03:45 UTC by Klint Fletcher
Updated 2019-06-19 19:43:57 UTC by Klint Fletcher
Location 33.105308, -117.267398
Site Name Ayers PRV Potable
Site Photos
Site to Site Coordination La Costa Lo AP Sector
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Radio Name Ayers PRV
Radio Type NanoStation M365
Ayers PRV PotableAyers PRV Potable
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 7 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 118•SE
Page: 2 of 3
Page 8 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 3 of 3
Page 9 of 249
Created 2019-01-07 20:53:31 UTC by Klint Fletcher
Updated 2019-02-01 04:25:16 UTC by Klint Fletcher
Location 33.1293092575, -117.265866492
Site Name Bressi Potable Pump Station
Site Photos
Site to Site Coordination MRKL-WAP-SOUTH
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Radio Name Bressi Potable PMP Station
Radio Type PowerBridge M365
Bressi Potable Pump StationBressi Potable Pump Station
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 10 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 344•N
Page: 2 of 3
Page 11 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 3 of 3
Page 12 of 249
Created 2019-01-07 20:44:38 UTC by Klint Fletcher
Updated 2019-06-19 21:17:29 UTC by Klint Fletcher
Location 33.1291826908, -117.265834808
Site Name Bressi Reclaim Pump Station
Site Photos
Site to Site Coordination M.Tower South Sector
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Radio Name Bressi RC Pump Sta.
Radio Type NanoBeam 5 AC
Bressi Reclaim Pump StationBressi Reclaim Pump Station
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 13 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Directional Array
Antenna Direction 345•N
Page: 2 of 3
Page 14 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 3 of 3
Page 15 of 249
Created 2019-01-08 19:19:53 UTC by Klint Fletcher
Updated 2019-02-01 04:30:23 UTC by Klint Fletcher
Location 33.1606722437, -117.280418649
Site Name C Reservoir Station
Site Photos
Site to Site Coordination M. Tower North Sector
Process Coordination SCADA
Communication Type Ethernet
C Reservoir StationC Reservoir Station
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 16 of 249
Communication Photos
Radio Name C RES Station
Radio Type PowerBeam 5AC 19
RadiosRadios
Page: 2 of 4
Page 17 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 90•E
Page: 3 of 4
Page 18 of 249
Antenna Direction Photos
Antenna Height 40 ft
Antenna Height Photos
Page: 4 of 4
Page 19 of 249
Created 2019-01-08 19:12:14 UTC by Klint Fletcher
Updated 2019-02-01 04:30:09 UTC by Klint Fletcher
Location 33.160686, -117.280465
Site Name C Reservoir AP
Site Photos
Site to Site Coordination Calavera POT PM ST
Rancho carlsbad PRV
Process Coordination SCADA
Process Dependencies Calavera POT PM ST
Communication Type Ethernet
Radio Name C RES AP
Radio Type Rocket M365
C Reservoir APC Reservoir AP
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 20 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 187•S
Antenna Height 40 ft
Page: 2 of 3
Page 21 of 249
Antenna Height Photos
Page: 3 of 3
Page 22 of 249
Created 2019-01-08 19:50:15 UTC by Klint Fletcher
Updated 2019-02-01 04:30:59 UTC by Klint Fletcher
Location 33.168464, -117.295223
Site Name Calavera Potable Pump Station
Site Photos
Site to Site Coordination C RES AP
Process Coordination SCADA (remote manual)
Process Dependencies TAP Reservoir
Communication Type Ethernet
Calavera Potable Pump StationCalavera Potable Pump Station
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 23 of 249
Communication Photos
Radio Name Calavera POT PM ST
Radio Type Rocket M365
RadiosRadios
Page: 2 of 4
Page 24 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Parabolic
Antenna Direction 108•E
Page: 3 of 4
Page 25 of 249
Antenna Direction Photos
Antenna Height 20 ft
Antenna Height Photos
Page: 4 of 4
Page 26 of 249
Created 2019-01-08 19:34:33 UTC by Klint Fletcher
Updated 2019-02-01 04:30:40 UTC by Klint Fletcher
Location 33.159767, -117.291564
Site Name Calavera Reclaim Pump Station
Site Photos
Site to Site Coordination M. Tower North Sector
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Calavera Reclaim Pump StationCalavera Reclaim Pump Station
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 27 of 249
Communication Photos
Radio Name Calavera RC Pump Sta.
Radio Type Rocket 5AC PTMP
RadiosRadios
Page: 2 of 4
Page 28 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 91•E
Page: 3 of 4
Page 29 of 249
Antenna Direction Photos
Antenna Height 22 ft
Antenna Height Photos
Page: 4 of 4
Page 30 of 249
Created 2019-01-07 15:35:31 UTC by Klint Fletcher
Updated 2019-02-01 04:19:48 UTC by Klint Fletcher
Location 33.1325536827, -117.26829364
Site Name CMW Building (900MHz)
CMW Building (900MHz)CMW Building (900MHz)
Site InformationSite Information
Page: 1 of 6
Page 31 of 249
Site Photos
Site to Site Coordination Reservoir D Site
Process Coordination SCADA
Page: 2 of 6
Page 32 of 249
Communication Type Serial
Communication Photos
Radio Name CMW Admin Free wave
Radio Type FGR-115RC
Radio Type Photos
Communication InformationCommunication Information
RadiosRadios
Page: 3 of 6
Page 33 of 249
Page: 4 of 6
Page 34 of 249
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 186•S
Page: 5 of 6
Page 35 of 249
Antenna Direction Photos
Antenna Height 45 ft
Antenna Height Photos
Page: 6 of 6
Page 36 of 249
Created 2019-01-07 15:54:52 UTC by Klint Fletcher
Updated 2019-02-01 04:20:03 UTC by Klint Fletcher
Location 33.1324871723, -117.268231027
Site Name CMW Building (Air Fibre)
Site Photos
Site to Site Coordination Maerkle to HQ AF Slave
Process Coordination SCADA
Communication Type Ethernet
CMW Building (Air Fibre)CMW Building (Air Fibre)
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 37 of 249
Communication Photos
Radio Name Master at HQ
Radio Type Air Fiber
Radio Frequency 24 GHz
Antenna Type Parabolic
Antenna Direction 3•N
RadiosRadios
Page: 2 of 4
Page 38 of 249
Antenna Direction Photos
Antenna Height 45 ft
Page: 3 of 4
Page 39 of 249
Antenna Height Photos
Page: 4 of 4
Page 40 of 249
Created 2019-01-09 17:38:36 UTC by Klint Fletcher
Updated 2019-02-01 04:41:40 UTC by Klint Fletcher
Location 33.110245, -117.236876
Site Name CWA #2 (VWD)
Site Photos
Site to Site Coordination Maerkle Tower(unknown)
Process Coordination SCADA (monitor flow)
Communication Type Serial
Radio Name VWD #2
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
CWA #2 (VWD)CWA #2 (VWD)
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 41 of 249
Antenna Direction Photos
Antenna Height 30 ft
Antenna Height Photos
Page: 2 of 2
Page 42 of 249
Created 2019-01-09 19:04:19 UTC by Klint Fletcher
Updated 2019-02-01 04:35:13 UTC by Klint Fletcher
Location 33.161806, -117.256393
Site Name CWA 3 Station
Site Photos
Site to Site Coordination CWA #4 365 AP
Process Coordination SCADA(monitor) flow
Communication Type Ethernet
Radio Name CEA #3 Station
Radio Type NanoStation M365
CWA 3 StationCWA 3 Station
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 43 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 297•NW
Page: 2 of 3
Page 44 of 249
Antenna Direction Photos
Antenna Height 45 ft
Antenna Height Photos
Page: 3 of 3
Page 45 of 249
Created 2019-01-09 19:29:57 UTC by Klint Fletcher
Updated 2019-02-01 04:34:29 UTC by Klint Fletcher
Location 33.167231, -117.265717
Site Name CWA # 4 AP
Site Photos
Site to Site Coordination CWA #3 Station
TAP -4 Station
Process Coordination SCADA(monitor)
Communication Type Ethernet
Radio Name CWA#4 365 AP
Radio Type PowerBridge M365
CWA # 4 APCWA # 4 AP
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 46 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 115•SE
Page: 2 of 3
Page 47 of 249
Antenna Direction Photos
Antenna Height 45 ft
Antenna Height Photos
Page: 3 of 3
Page 48 of 249
Created 2019-01-09 19:33:13 UTC by Klint Fletcher
Updated 2019-02-01 04:34:40 UTC by Klint Fletcher
Location 33.167181, -117.265594
Site Name CWA #4 Station
Site Photos
Site to Site Coordination TAP 2 CWA #4
Process Coordination SCADA(monitor) flow
Communication Type Ethernet
Radio Name CWA #4 Station
Radio Type NanoStation M5
CWA #4 StationCWA #4 Station
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 49 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Directional Array
Antenna Direction 290•W
Page: 2 of 3
Page 50 of 249
Antenna Direction Photos
Antenna Height 45 ft
Antenna Height Photos
Page: 3 of 3
Page 51 of 249
Created 2019-01-09 18:44:05 UTC by Klint Fletcher
Updated 2019-02-01 04:35:26 UTC by Klint Fletcher
Location 33.131157, -117.208203
Site Name CWA #6
Site Photos
Site to Site Coordination SF 1 Res. Repeater
Process Coordination SCADA (monitor) flow
Communication Type Serial
Radio Name CWA #6
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 226•SW
CWA #6CWA #6
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 52 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 2 of 2
Page 53 of 249
Created 2019-01-07 21:48:24 UTC by Klint Fletcher
Updated 2019-02-01 04:26:45 UTC by Klint Fletcher
Location 33.1122579938, -117.286908422
Site Name D3 East Sector
Site Photos
Site to Site Coordination Zodiac PRV
Aires PRV
La Costa Low repeater
Process Coordination SCADA (remote manual)
Process Dependencies Aires PRV (flow control)
Communication Type Ethernet
D3 East SectorD3 East Sector
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 54 of 249
Communication Photos
Radio Name D3 east sector
Radio Type Rocket M365
RadiosRadios
Page: 2 of 4
Page 55 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 47• NE
Page: 3 of 4
Page 56 of 249
Antenna Direction Photos
Antenna Height 79 ft
Antenna Height Photos
Page: 4 of 4
Page 57 of 249
Created 2019-01-07 21:57:50 UTC by Klint Fletcher
Updated 2019-03-11 21:18:39 UTC by Klint Fletcher
Location 33.1123983069, -117.28662109
Site Name D3 Reservoir Repeater
Site Photos
Site to Site Coordination D Res Repeater (unknown)
Process Coordination Unknown (possible Lower el fuerte)
Communication Type Serial
Radio Name Unknown
Radio Type FreeWave
D3 Reservoir RepeaterD3 Reservoir Repeater
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 58 of 249
Radio Type Photos
Radio Frequency 2.4 GHz
Antenna Type Omni
Antenna Height 55 ft
Page: 2 of 3
Page 59 of 249
Antenna Height Photos
Page: 3 of 3
Page 60 of 249
Created 2019-01-07 21:27:29 UTC by Klint Fletcher
Updated 2019-03-12 02:01:21 UTC by Klint Fletcher
Location 33.1122642802, -117.28695008
Site Name D3 to North Sector
Site Photos
Site to Site Coordination Lake Calavera
Process Coordination SCADA (remote manual)
Communication Type Ethernet
D3 to North SectorD3 to North Sector
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 61 of 249
Communication Photos
Radio Name D3 to Lake Calavera
Radio Type Rocket M365
RadiosRadios
Page: 2 of 4
Page 62 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 311• NW
Page: 3 of 4
Page 63 of 249
Antenna Direction Photos
Antenna Height 78 ft
Antenna Height Photos
Page: 4 of 4
Page 64 of 249
Created 2019-01-07 21:14:40 UTC by Klint Fletcher
Updated 2019-02-01 04:25:35 UTC by Klint Fletcher
Location 33.1122580776, -117.287138924
Site Name D3 Tower to Maerkle Tower
Site Photos
Site to Site Coordination M.Tower AP2D3
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Radio Name D3 Sta 2 M tower
Radio Type Rocket M5
D3 Tower to Maerkle TowerD3 Tower to Maerkle Tower
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 65 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 8•N
Page: 2 of 3
Page 66 of 249
Antenna Direction Photos
Antenna Height 75 ft
Antenna Height Photos
Page: 3 of 3
Page 67 of 249
Created 2019-01-07 21:35:21 UTC by Klint Fletcher
Updated 2019-03-12 01:57:27 UTC by Klint Fletcher
Location 33.1123018731, -117.286937507
Site Name D3 West Sector
Site Photos
Site to Site Coordination Encina Pump Station
TWIN D Pump Station <d site station>
Elm Tap
Skyline Res.
Process Coordination SCADA (remote manual)
Process Dependencies CWRF
Twin D Pump Station
Communication Type Ethernet
D3 West SectorD3 West Sector
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 68 of 249
Communication Photos
Radio Name D3 West Sector
Radio Type Rocket M365
RadiosRadios
Page: 2 of 4
Page 69 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 280• W
Page: 3 of 4
Page 70 of 249
Antenna Direction Photos
Antenna Height 78 ft
Antenna Height Photos
Page: 4 of 4
Page 71 of 249
Created 2019-01-08 22:44:33 UTC by Klint Fletcher
Updated 2019-02-01 04:34:04 UTC by Klint Fletcher
Location 33.165461, -117.322827
Site Name Ellery Reservoir
Site Photos
Site to Site Coordination TAP AP 2 Ellery
Process Coordination SCADA (remote manual) clay valve operation.
Communication Type Ethernet
Radio Name Ellery Sta.
Radio Type Rocket 5AC PTMP
Ellery ReservoirEllery Reservoir
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 72 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 76•E
Page: 2 of 3
Page 73 of 249
Antenna Direction Photos
Antenna Height 35 ft
Antenna Height Photos
Page: 3 of 3
Page 74 of 249
Created 2019-01-08 22:21:30 UTC by Klint Fletcher
Updated 2019-02-01 04:33:43 UTC by Klint Fletcher
Location 33.172674, -117.330113
Site Name Elm Reservoir Repeater
Site Photos
Site to Site Coordination B Res Repeater
Process Coordination SCADA (remote manual for May Company)
Communication Type Serial
Radio Name Elm RES REPEATER
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 130•SE
Elm Reservoir RepeaterElm Reservoir Repeater
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 75 of 249
Antenna Direction Photos
Antenna Height 53 ft
Antenna Height Photos
Page: 2 of 2
Page 76 of 249
Created 2019-01-08 22:26:02 UTC by Klint Fletcher
Updated 2019-06-19 19:47:39 UTC by Klint Fletcher
Location 33.172677015, -117.330152756
Site Name Elm Reservoir
Site Photos
Site to Site Coordination TAP WEST AP
Process Coordination SCADA (level monitor only)
Communication Type Ethernet
Radio Name Elm East Sector
Radio Type Rocket M365
Elm ReservoirElm Reservoir
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 77 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 65•NE
Page: 2 of 3
Page 78 of 249
Antenna Direction Photos
Antenna Height 50 ft
Antenna Height Photos
Page: 3 of 3
Page 79 of 249
Created 2019-01-08 21:59:05 UTC by Klint Fletcher
Updated 2019-06-19 19:51:45 UTC by Klint Fletcher
Location 33.171419, -117.315742
Site Name Elm Tap PRS
Site Photos
Site to Site Coordination D32LakeCal
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Radio Name Elm Tap
Radio Type PowerBridge M365
Elm Tap PRSElm Tap PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 80 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 131•SE
Page: 2 of 3
Page 81 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 3 of 3
Page 82 of 249
Created 2019-01-09 15:40:42 UTC by Klint Fletcher
Updated 2019-02-01 04:36:44 UTC by Klint Fletcher
Location 33.1142867916, -117.318775915
Site Name Encina AP 2 Encina PRV
Site Photos
Site to Site Coordination Encina Sta. PRV
Process Coordination SCADA (monitor only)
Communication Type Ethernet
Radio Name Encina AP 2 Encina PRV
Radio Type NanoStation M365
Encina AP 2 Encina PRVEncina AP 2 Encina PRV
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 83 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 158•S
Page: 2 of 3
Page 84 of 249
Antenna Direction Photos
Antenna Height 30 ft
Antenna Height Photos
Page: 3 of 3
Page 85 of 249
Created 2019-01-09 15:47:25 UTC by Klint Fletcher
Updated 2019-02-01 04:37:43 UTC by Klint Fletcher
Location 33.110193, -117.318045
Site Name Encina Reclaim PRV
Site Photos
Site to Site Coordination Encina AP 2 Encina PRV
Process Coordination SCADA (monitor)
Communication Type Ethernet
Radio Name Encina Sta. PRV
Radio Type NanoStation M365
Encina Reclaim PRVEncina Reclaim PRV
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 86 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 328•NW
Page: 2 of 3
Page 87 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 3 of 3
Page 88 of 249
Created 2019-01-09 15:17:48 UTC by Klint Fletcher
Updated 2019-02-01 04:38:03 UTC by Klint Fletcher
Location 33.114295, -117.318871
Site Name Encina Reclaim Pump Station
Site Photos
Site to Site Coordination D32LakeCal
Process Coordination SCADA(remote manual)
Runs off level of D1/D2
Communication Type Ethernet
Radio Name ENCINA PUMP STATION
Radio Type Rocket M365
Encina Reclaim Pump StationEncina Reclaim Pump Station
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 89 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Parabolic
Antenna Direction 65•NE
Page: 2 of 3
Page 90 of 249
Antenna Direction Photos
Antenna Height 40 ft
Antenna Height Photos
Page: 3 of 3
Page 91 of 249
Created 2019-01-09 15:34:43 UTC by Klint Fletcher
Updated 2019-02-01 04:36:57 UTC by Klint Fletcher
Location 33.1142739673, -117.318777843
Site Name Encina to Palomar West
Site Photos
Site to Site Coordination PALOMAR WestPRV Station
Process Coordination SCADA(remote manual) of Pal West
Communication Type Ethernet
Radio Name Encina 2 Pal. W NE AP
Radio Type Rocket M365
Encina to Palomar WestEncina to Palomar West
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 92 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 18•N
Page: 2 of 3
Page 93 of 249
Antenna Direction Photos
Antenna Height 40 ft
Antenna Height Photos
Page: 3 of 3
Page 94 of 249
Created 2019-01-09 15:09:32 UTC by Klint Fletcher
Updated 2019-02-01 04:36:31 UTC by Klint Fletcher
Location 33.139066, -117.291469
Site Name Faraday Reclaim PRS
Site Photos
Site to Site Coordination Maerkle Tower
Process Coordination SCADA (remote manual)
Communication Type Serial
Radio Name Faraday RC PRS
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 30•NE
Faraday Reclaim PRSFaraday Reclaim PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 95 of 249
Antenna Direction Photos
Antenna Height 15 ft
Antenna Height Photos
Page: 2 of 2
Page 96 of 249
Created 2019-01-09 16:31:04 UTC by Klint Fletcher
Updated 2019-06-19 19:50:57 UTC by Klint Fletcher
Location 33.105735, -117.23486
Site Name La Costa Hi Reservoir
Site Photos
Site to Site Coordination Station-Mahr
Process Coordination SCADA(monitor)
Communication Type Ethernet
Radio Name LCHI2Mahr AP @ LCH
Radio Type NanoStation M365
La Costa Hi ReservoirLa Costa Hi Reservoir
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 97 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 165•S
Page: 2 of 3
Page 98 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 3 of 3
Page 99 of 249
Created 2019-01-09 16:28:27 UTC by Klint Fletcher
Updated 2019-02-01 04:39:56 UTC by Klint Fletcher
Location 33.105767, -117.234764
Site Name La Costa Hi to Maerkle Tower
Site Photos
Site to Site Coordination M.Tower AP 2 LCHI
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Radio Name LCHI STA 2 MTOWER
Radio Type Rocket 5AC PTMP
La Costa Hi to Maerkle TowerLa Costa Hi to Maerkle Tower
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 100 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 345•N
Page: 2 of 3
Page 101 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 3 of 3
Page 102 of 249
Created 2019-01-09 16:33:44 UTC by Klint Fletcher
Updated 2019-06-19 19:48:34 UTC by Klint Fletcher
Location 33.105715, -117.234888
Site Name La Costa Hi to Melrose & Corintia
Site Photos
Site to Site Coordination Melrose & Cortina Station
Process Coordination SCADA(remote manual)
Communication Type Ethernet
Radio Name LCHIAP2M&C
Radio Type NanoStation M365
La Costa Hi to Melrose & CorintiaLa Costa Hi to Melrose & Corintia
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 103 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 59•NE
Page: 2 of 3
Page 104 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 3 of 3
Page 105 of 249
Created 2019-01-09 17:17:34 UTC by Klint Fletcher
Updated 2019-01-31 22:20:14 UTC by Klint Fletcher
Location 33.1016879948, -117.251534527
Site Name La Costa Lo Reservoir Repeater (900 MHz)
Site Photos
Site to Site Coordination Unknown (not functional)
Communication Type Serial
Radio Name La Costa lo Repeater
Radio Type FreeWave
Radio Frequency 900 MHz
La Costa Lo Reservoir Repeater (900 MHz)La Costa Lo Reservoir Repeater (900 MHz)
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 1
Page 106 of 249
Created 2019-01-09 17:12:21 UTC by Klint Fletcher
Updated 2019-02-01 04:41:12 UTC by Klint Fletcher
Location 33.101638, -117.251623
Site Name La Costa Lo Station Repeater
Site Photos
Site to Site Coordination D3EastSector
Process Coordination Repeater Ayres
Process Dependencies SCADA (remote manual)
Communication Type Ethernet
Radio Name La Costa Lo Station
Radio Type PowerBridge M365
La Costa Lo Station RepeaterLa Costa Lo Station Repeater
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 107 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 297•NW
Page: 2 of 3
Page 108 of 249
Antenna Direction Photos
Antenna Height 45 ft
Antenna Height Photos
Page: 3 of 3
Page 109 of 249
Created 2019-01-09 17:14:31 UTC by Klint Fletcher
Updated 2019-02-01 04:41:03 UTC by Klint Fletcher
Location 33.1016492795, -117.251802852
Site Name La Costa Lo to Ayres PRV
Site Photos
Site to Site Coordination Ayres PRV
Process Coordination SCADA(remote manual)
Communication Type Ethernet
Radio Name La Costa Lo AP Sector
Radio Type Rocket M365
La Costa Lo to Ayres PRVLa Costa Lo to Ayres PRV
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 110 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 297•NW
Page: 2 of 3
Page 111 of 249
Antenna Direction Photos
Antenna Height 45 ft
Antenna Height Photos
Page: 3 of 3
Page 112 of 249
Created 2019-01-09 16:12:59 UTC by Klint Fletcher
Updated 2019-06-19 19:43:27 UTC by Klint Fletcher
Location 33.117875, -117.25006
Site Name La Costa Reclaim PRS
Site Photos
Site to Site Coordination SF 2 Res Repeater
Process Coordination SCADA (monitor)
Communication Type Serial
Radio Name La Costa PRS
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 57•N
La Costa Reclaim PRSLa Costa Reclaim PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 113 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 2 of 2
Page 114 of 249
Created 2019-01-08 23:16:58 UTC by Klint Fletcher
Updated 2019-02-01 04:36:05 UTC by Klint Fletcher
Location 33.1525159089, -117.310426074
Site Name Laguna /Kelly PRS
Site Photos
Site to Site Coordination B Res Repeater
Process Coordination SCADA (remote manual)
Communication Type Serial
Radio Name Laguna/Kelly PRS
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 22•N
Laguna /Kelly PRSLaguna /Kelly PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 115 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 2 of 2
Page 116 of 249
Created 2019-01-08 21:39:43 UTC by Klint Fletcher
Updated 2019-02-01 04:32:43 UTC by Klint Fletcher
Location 33.169694, -117.28738
Site Name Lake Calavera
Site Photos
Site to Site Coordination D3 5G N-Sector
Process Coordination SCADA level monitor
Communication Type Ethernet
Lake CalaveraLake Calavera
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 117 of 249
Communication Photos
Radio Name lake Calavera 2D3
Radio Type Rocket M5
RadiosRadios
Page: 2 of 4
Page 118 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 176•S
Page: 3 of 4
Page 119 of 249
Antenna Direction Photos
Antenna Height 16 ft
Antenna Height Photos
Page: 4 of 4
Page 120 of 249
Created 2019-01-09 17:04:42 UTC by Klint Fletcher
Updated 2019-02-01 04:40:51 UTC by Klint Fletcher
Location 33.095077, -117.250145
Site Name Lower El Fuerte PRS
Site Photos
Site to Site Coordination Lost radio comms
Process Coordination SCADA(remote manual)
Communication Type Serial
Radio Name Lower El Fuerte PRS
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 265•W
Lower El Fuerte PRSLower El Fuerte PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 121 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 2 of 2
Page 122 of 249
Created 2019-01-07 17:10:40 UTC by Klint Fletcher
Updated 2019-02-01 04:20:44 UTC by Klint Fletcher
Location 33.1526470324, -117.260276517
Site Name M.Tower AP2D3
Site Photos
Site to Site Coordination D3 (D site)
Process Coordination SCADA (remote)
Process Dependencies Twin D recycled Pump Station
Communication Type Ethernet
Radio Name M.Tower AP2D3
Radio Type Rocket M5
M.Tower AP2D3M.Tower AP2D3
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 123 of 249
Radio Type Photos
Radio Frequency 5GHz
Antenna Type Parabolic
Antenna Direction 207• SW
Page: 2 of 3
Page 124 of 249
Antenna Direction Photos
Antenna Height 30 ft
Antenna Height Photos
Page: 3 of 3
Page 125 of 249
Created 2019-01-07 19:44:48 UTC by Klint Fletcher
Updated 2019-02-01 04:24:48 UTC by Klint Fletcher
Location 33.1565752952, -117.256722674
Site Name Maerkle Apple Wood Gate Camera
Site Photos
Site to Site Coordination MRKL-WAP-NORTH
Process Coordination Camera
Communication Type Ethernet
Radio Name MRKLAPPLEWOODGATE
Radio Type NanoStation M365
Maerkle Apple Wood Gate CameraMaerkle Apple Wood Gate Camera
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 126 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 187•S
Page: 2 of 3
Page 127 of 249
Antenna Direction Photos
Antenna Height 15 ft
Antenna Height Photos
Page: 3 of 3
Page 128 of 249
Created 2019-01-08 18:47:59 UTC by Klint Fletcher
Updated 2019-03-11 20:22:22 UTC by Klint Fletcher
Location 33.1379029295, -117.274053181
Site Name Maerkle Control
Site Photos
Site to Site Coordination MRKL-WAL-SOUTH
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Radio Name Maerkle Control
Radio Type PowerBridge M365
Maerkle ControlMaerkle Control
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 129 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 43•NE
Page: 2 of 3
Page 130 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 3 of 3
Page 131 of 249
Created 2019-01-07 19:10:12 UTC by Klint Fletcher
Updated 2019-03-11 20:26:23 UTC by Klint Fletcher
Location 33.1507906504, -117.25981174
Site Name Maerkle Dam Camera
Site Photos
Site to Site Coordination MRKL-WAP-SOUTH
Process Coordination Camera
Communication Type Ethernet
Radio Name Maerkle Dam Camera
Radio Type Nano station M365
Maerkle Dam CameraMaerkle Dam Camera
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 132 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 335 •NW
Page: 2 of 3
Page 133 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 3 of 3
Page 134 of 249
Created 2019-01-07 19:00:26 UTC by Klint Fletcher
Updated 2019-02-01 04:22:59 UTC by Klint Fletcher
Location 33.152854736, -117.261486109
Site Name Maerkle Hydro
Site Photos
Site to Site Coordination MRKL-WAP-NORTH
Process Coordination SCADA (remote manual) valve control
Communication Type Ethernet
Radio Name HydroElectric
Radio Type Power Bridge M365
Maerkle HydroMaerkle Hydro
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 135 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 83•E
Page: 2 of 3
Page 136 of 249
Antenna Direction Photos
Antenna Height 13 ft
Antenna Height Photos
Page: 3 of 3
Page 137 of 249
Created 2019-01-07 19:26:30 UTC by Klint Fletcher
Updated 2019-02-01 04:23:42 UTC by Klint Fletcher
Location 33.1505492097, -117.261680737
Site Name Maerkle Lower Chlorine Station Camera
Site Photos
Site to Site Coordination MRKL-WAP-SOUTH
Process Coordination Camera
Communication Type Ethernet
Radio Name MRKLLOWERCL2STATION
Radio Type Nano station M365
Maerkle Lower Chlorine Station CameraMaerkle Lower Chlorine Station Camera
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 138 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 20•N
Page: 2 of 3
Page 139 of 249
Antenna Direction Photos
Antenna Height 12 ft
Antenna Height Photos
Page: 3 of 3
Page 140 of 249
Created 2019-01-07 19:30:05 UTC by Klint Fletcher
Updated 2019-02-01 04:24:03 UTC by Klint Fletcher
Location 33.150384, -117.261473
Site Name Maerkle Lower Chlorine Station
Site Photos
Site to Site Coordination M. Tower South Sector
Process Coordination SCADA
Communication Type Ethernet
Radio Name Maerkle scada lower
Radio Type PowerBeam 5AC
Maerkle Lower Chlorine StationMaerkle Lower Chlorine Station
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 141 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 25• NE
Page: 2 of 3
Page 142 of 249
Antenna Direction Photos
Antenna Height 31 ft
Antenna Height Photos
Page: 3 of 3
Page 143 of 249
Created 2019-01-07 19:22:46 UTC by Klint Fletcher
Updated 2019-02-01 04:23:26 UTC by Klint Fletcher
Location 33.1506936299, -117.262269482
Site Name Maerkle Sunny Creek Gate Camera
Site Photos
Site to Site Coordination MRKL-WAP-SOUTH
Process Coordination Camera
Communication Type Ethernet
Radio Name MRKLSUNNYCREEK
Radio Type M365
Maerkle Sunny Creek Gate CameraMaerkle Sunny Creek Gate Camera
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 144 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 33•NE
Page: 2 of 3
Page 145 of 249
Antenna Direction Photos
Antenna Height 15 ft
Antenna Height Photos
Page: 3 of 3
Page 146 of 249
Created 2019-01-07 18:48:29 UTC by Klint Fletcher
Updated 2019-02-01 04:22:47 UTC by Klint Fletcher
Location 33.1533278106, -117.260758979
Site Name Maerkle Tank Camera
Site Photos
Site to Site Coordination MRKL-WAP-NORTH
Process Coordination Camera
Communication Type Ethernet
Radio Name MRKLRESDOOR
Radio Type NanoStation M365
Maerkle Tank CameraMaerkle Tank Camera
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 147 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 123•SE
Page: 2 of 3
Page 148 of 249
Antenna Direction Photos
Antenna Height 15 ft
Antenna Height Photos
Page: 3 of 3
Page 149 of 249
Created 2019-01-07 17:51:20 UTC by Klint Fletcher
Updated 2019-02-01 04:20:57 UTC by Klint Fletcher
Location 33.1524814479, -117.260255981
Site Name Maerkle to La Costa Hi
Site Photos
Site to Site Coordination La Costa Hi
Process Coordination SCADA (via AirFiber)
Communication Type Ethernet
Radio Name M.Tower AP 2 LCHI
Radio Type Rocket M5
Maerkle to La Costa HiMaerkle to La Costa Hi
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 150 of 249
Radio Type Photos
Radio Frequency 5GHz
Antenna Type Parabolic
Antenna Direction 137 • SE
Page: 2 of 3
Page 151 of 249
Antenna Direction Photos
Antenna Height 60 ft
Antenna Height Photos
Page: 3 of 3
Page 152 of 249
Created 2019-01-07 16:52:23 UTC by Klint Fletcher
Updated 2019-02-01 04:20:18 UTC by Klint Fletcher
Location 33.1525236927, -117.260223879
Site Name Maerkle Tower Free wave
Site Photos
Site to Site Coordination D site
Lower el fuerte
Upper el fuerte
CWA 2
CWA 6
Laguna Riviera
May Company
Tangle wood
Elm Reservoir
Process Coordination SCADA
Communication Type Serial
Maerkle Tower Free waveMaerkle Tower Free wave
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 3
Page 153 of 249
Communication Photos
Radio Name Maerkle Free Wave Omni
Radio Type FreeWave
Radio Type Photos
Radio Frequency 900 MHz
Antenna Type Omni
Antenna Direction N/A
RadiosRadios
Page: 2 of 3
Page 154 of 249
Antenna Direction Photos
Antenna Height 90 ft
Antenna Height Photos
Page: 3 of 3
Page 155 of 249
Created 2019-01-07 18:17:08 UTC by Klint Fletcher
Updated 2019-02-01 04:21:38 UTC by Klint Fletcher
Location 33.1524304021, -117.260348098
Site Name Maerkle Tower to SantaFe 2
Site Photos
Site to Site Coordination Santa Fe 2
Process Coordination SCADA
Communication Type Ethernet
Radio Name M.Tower AP 2 SF2
Radio Type Rocket M5
Maerkle Tower to SantaFe 2Maerkle Tower to SantaFe 2
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 156 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 97•E
Page: 2 of 3
Page 157 of 249
Antenna Direction Photos
Antenna Height 45 ft
Antenna Height Photos
Page: 3 of 3
Page 158 of 249
Created 2019-01-07 18:23:59 UTC by Klint Fletcher
Updated 2019-02-01 04:21:52 UTC by Klint Fletcher
Location 33.152572685, -117.260298058
Site Name Maerkle Tower to TAP
Site Photos
Site to Site Coordination TAP STA 2 MTOWER
Process Coordination SCADA
Communication Type Ethernet
Radio Name M.Tower AP2TAP
Radio Type Rocket 5AC
Maerkle Tower to TAPMaerkle Tower to TAP
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 159 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 308•NW
Page: 2 of 3
Page 160 of 249
Antenna Direction Photos
Antenna Height 20 ft
Antenna Height Photos
Page: 3 of 3
Page 161 of 249
Created 2019-01-07 18:44:23 UTC by Klint Fletcher
Updated 2019-02-01 04:22:28 UTC by Klint Fletcher
Location 33.1530067837, -117.25942391
Site Name Maerkle Upper Chlorine Station Camera
Site Photos
Site to Site Coordination MRKL-WAP-SOUTH
Process Coordination Camera
Communication Type Ethernet
Radio Name MRKLUPPERCL2STATION
Radio Type NanoStation M365
Maerkle Upper Chlorine Station CameraMaerkle Upper Chlorine Station Camera
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 162 of 249
Radio Type Photos
Radio Frequency 3.65 MHz
Antenna Type Directional Array
Antenna Direction 226• SW
Page: 2 of 3
Page 163 of 249
Antenna Direction Photos
Antenna Height 15 ft
Antenna Height Photos
Page: 3 of 3
Page 164 of 249
Created 2019-01-07 18:33:51 UTC by Klint Fletcher
Updated 2019-02-01 04:22:06 UTC by Klint Fletcher
Location 33.152955, -117.259615
Site Name Maerkle Upper Chlorine Station
Site Photos
Site to Site Coordination MRKL-WAP-NORTH
Process Coordination SCADA
Communication Type Ethernet
Radio Name MRKLUPCL2-SCADA
Radio Type Nano Station M364
Maerkle Upper Chlorine StationMaerkle Upper Chlorine Station
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 165 of 249
Radio Type Photos
Radio Frequency 3.65GHz
Antenna Type Directional Array
Antenna Direction 235•SW
Page: 2 of 3
Page 166 of 249
Antenna Direction Photos
Antenna Height 6 ft
Antenna Height Photos
Page: 3 of 3
Page 167 of 249
Created 2019-01-09 17:52:26 UTC by Klint Fletcher
Updated 2019-06-19 19:51:25 UTC by Klint Fletcher
Location 33.0943, -117.222926
Site Name Mahr Reservoir
Site Photos
Site to Site Coordination LCHI2Mahr AP 2 LCHI
Process Coordination SCADA (monitor) lake level
Communication Type Ethernet
Radio Name Station-Mahr
Radio Type PowerBridge M365
Mahr ReservoirMahr Reservoir
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 168 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 302•NW
Page: 2 of 3
Page 169 of 249
Antenna Direction Photos
Antenna Height 15 ft
Antenna Height Photos
Page: 3 of 3
Page 170 of 249
Created 2019-01-08 22:08:15 UTC by Klint Fletcher
Updated 2019-02-01 04:33:12 UTC by Klint Fletcher
Location 33.173909, -117.324253
Site Name May Company PRS
Site Photos
Site to Site Coordination Tanglewood
Process Coordination SCADA (remote manual) PRS
Process Dependencies Clay valve that fills Elm RES
Communication Type Serial
Radio Name May Co. PRS
Radio Type Freewave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 147•SE
May Company PRSMay Company PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 171 of 249
Antenna Direction Photos
Antenna Height 15 ft
Antenna Height Photos
Page: 2 of 2
Page 172 of 249
Created 2019-01-09 17:46:46 UTC by Klint Fletcher
Updated 2019-02-01 04:42:05 UTC by Klint Fletcher
Location 33.1073535012, -117.226857876
Site Name Melrose & Corintia Meter Vault
Site Photos
Site to Site Coordination LCHIAP2M&C
Process Coordination SCADA(monitor)
Communication Type Ethernet
Radio Name Melrose & Corintia Station
Radio Type NanoStation M365
Melrose & Corintia Meter VaultMelrose & Corintia Meter Vault
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 173 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 225•SW
Page: 2 of 3
Page 174 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 3 of 3
Page 175 of 249
Created 2019-01-09 16:21:55 UTC by Klint Fletcher
Updated 2019-02-01 04:39:45 UTC by Klint Fletcher
Location 33.123407, -117.238686
Site Name Melrose PRV Potable
Site Photos
Site to Site Coordination SF2West Sector
Process Coordination SCADA (monitor)
Communication Type Ethernet
Radio Name Melrose PRV Potable
Radio Type NanoStation M365
Melrose PRV PotableMelrose PRV Potable
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 176 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 50•NE
Page: 2 of 3
Page 177 of 249
Antenna Direction Photos
Antenna Height 20 ft
Antenna Height Photos
Page: 3 of 3
Page 178 of 249
Created 2019-01-07 17:56:30 UTC by Klint Fletcher
Updated 2019-02-01 04:21:08 UTC by Klint Fletcher
Location 33.1525510596, -117.260273332
Site Name MRKL-WAP-NORTH
Site Photos
Site to Site Coordination HydroElectric
MRKLAPPLEWOODGATE
MRKLRESDOOR
MRKLUPCL2-SCADA
Process Coordination SCADA
Process Dependencies Calavera Potable
Communication Type Ethernet
Radio Name MRKL-WAP-NORTH
Radio Type Rocket M365
MRKL-WAP-NORTHMRKL-WAP-NORTH
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 179 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Parabolic
Antenna Direction 296•NW
Page: 2 of 3
Page 180 of 249
Antenna Direction Photos
Antenna Height 95 ft
Antenna Height Photos
Page: 3 of 3
Page 181 of 249
Created 2019-01-07 18:10:32 UTC by Klint Fletcher
Updated 2019-02-01 04:21:21 UTC by Klint Fletcher
Location 33.1524937274, -117.260289341
Site Name MRKL-WAP-SOUTH
Site Photos
Site to Site Coordination MRKL-WAP-SOUTH
Bressi Potable PMP Station
Maerkle Control
MRKLAKE
MRKLAKEGATE
MRKLLOWERCL2STATION
MRKLSUNNYCREEK
MRKLUPPERCL2STATION
Point D PRV
Process Coordination SCADA
Communication Type Ethernet
Radio Name MRKL-WAP-South
Radio Type Rocket 365
MRKL-WAP-SOUTHMRKL-WAP-SOUTH
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 182 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Height 90 ft
Page: 2 of 3
Page 183 of 249
Antenna Height Photos
Page: 3 of 3
Page 184 of 249
Created 2019-01-09 15:53:38 UTC by Klint Fletcher
Updated 2019-02-01 04:38:33 UTC by Klint Fletcher
Location 33.121773, -117.313316
Site Name Palomar West PRV
Site Photos
Site to Site Coordination Encina 2 Pal. W NE AP
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Radio Name Palomar WestPRV Station
Radio Type NanoStation M365
Palomar West PRVPalomar West PRV
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 185 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 187•S
Page: 2 of 3
Page 186 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 3 of 3
Page 187 of 249
Created 2019-01-09 19:56:56 UTC by Klint Fletcher
Updated 2019-06-19 19:41:39 UTC by Klint Fletcher
Location 33.130004, -117.266345
Site Name Point D PRV North
Site Photos
Site to Site Coordination MRKL-WAP-SOUTH
Process Coordination SCADA (monitor) pressure
Communication Type Ethernet
Radio Name Point D PRV
Radio Type NanoStation M365
Point D PRV NorthPoint D PRV North
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 188 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 2•N
Page: 2 of 3
Page 189 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 3 of 3
Page 190 of 249
Created 2019-01-08 18:55:49 UTC by Klint Fletcher
Updated 2019-06-19 19:52:27 UTC by Klint Fletcher
Location 33.1469157804, -117.289622231
Site Name Rancho Carlsbad PRS
Site Photos
Site to Site Coordination C RES AP
Process Coordination SCADA monitoring
Communication Type Ethernet
Radio Name Rancho Carlsbad PRV
Radio Type PowerBridge M365
Rancho Carlsbad PRSRancho Carlsbad PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 191 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 14•N
Page: 2 of 3
Page 192 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 3 of 3
Page 193 of 249
Created 2019-01-08 23:26:35 UTC by Klint Fletcher
Updated 2019-06-19 19:47:03 UTC by Klint Fletcher
Location 33.1559177078, -117.299625989
Site Name Robertson Ranch PRS
Site Photos
Site to Site Coordination M.Tower.North Sector
Process Coordination SCADA(monitor only)
Communication Type Ethernet
Radio Name Robertson Ranch Sta.
Radio Type NanoBeam 5AC 19
Robertson Ranch PRSRobertson Ranch PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 194 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 80•E
Page: 2 of 3
Page 195 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 3 of 3
Page 196 of 249
Created 2019-01-09 18:40:20 UTC by Klint Fletcher
Updated 2019-02-01 04:35:03 UTC by Klint Fletcher
Location 33.136114, -117.21397
Site Name SantaFe 1 Reservoir Repeater
Site Photos
Site to Site Coordination To SF 2 Res. Repeater
From CWA #6
Process Coordination SCADA(monitor) flow
Communication Type Serial
Radio Name SF 1 Res Repeaters
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 207•SW
SantaFe 1 Reservoir RepeaterSantaFe 1 Reservoir Repeater
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 197 of 249
Antenna Direction Photos
Antenna Height 38 ft
Antenna Height Photos
Page: 2 of 2
Page 198 of 249
Created 2019-01-09 18:10:38 UTC by Klint Fletcher
Updated 2019-02-01 04:42:46 UTC by Klint Fletcher
Location 33.123576, -117.225464
Site Name SantaFe 2 Res. Repeater to Maerkle 900
Site Photos
Site to Site Coordination To maerkle
Repeat
La Costa PRS
SF1 Res Repeater
Process Coordination SCADA(monitor)
Communication Type Serial
Radio Name SF 2 Res Repeater
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 307•NW
SantaFe 2 Res. Repeater to Maerkle 900SantaFe 2 Res. Repeater to Maerkle 900
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 199 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 2 of 2
Page 200 of 249
Created 2019-01-09 18:07:15 UTC by Klint Fletcher
Updated 2019-03-12 02:20:19 UTC by Klint Fletcher
Location 33.123548, -117.225321
Site Name SantaFe 2 Station to Maerkle Tower
Site Photos
Site to Site Coordination M.Tower AP 2 SF2
Process Coordination SCADA (monitor)
Communication Type Ethernet
Radio Name SF2 STA 2 MTOWER
Radio Type Rocket 5AC PTMP
SantaFe 2 Station to Maerkle TowerSantaFe 2 Station to Maerkle Tower
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 201 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 306•NW
Page: 2 of 3
Page 202 of 249
Antenna Direction Photos
Antenna Height 15 ft
Antenna Height Photos
Page: 3 of 3
Page 203 of 249
Created 2019-01-09 18:14:18 UTC by Klint Fletcher
Updated 2019-06-19 22:58:08 UTC by Klint Fletcher
Location 33.123494, -117.225424
Site Name SantaFe 2 to SantaFe 1 (future)
Site Photos
Site to Site Coordination SF1 Station
Process Coordination Future (not in use)
Communication Type Ethernet
Radio Name SF2 AP 2 SF 1
Radio Type PowerBeam 5AC 300
SantaFe 2 to SantaFe 1 (future)SantaFe 2 to SantaFe 1 (future)
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 204 of 249
Radio Type Photos
Antenna Type Parabolic
Antenna Direction 8•N
Antenna Direction Photos
Page: 2 of 3
Page 205 of 249
Antenna Height 15 ft
Antenna Height Photos
Page: 3 of 3
Page 206 of 249
Created 2019-01-09 18:04:32 UTC by Klint Fletcher
Updated 2019-03-12 02:20:38 UTC by Klint Fletcher
Location 33.123628, -117.225368
Site Name SantaFe 2 To West Sector
Site Photos
Site to Site Coordination Melrose PRV Potable
Process Coordination SCADA(monitor)
Communication Type Ethernet
Radio Name SF2WEST Sector
Radio Type Rocket M365
SantaFe 2 To West SectorSantaFe 2 To West Sector
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 207 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 173•S
Page: 2 of 3
Page 208 of 249
Antenna Direction Photos
Antenna Height 15 ft
Antenna Height Photos
Page: 3 of 3
Page 209 of 249
Created 2019-01-08 23:06:14 UTC by Klint Fletcher
Updated 2019-02-01 04:35:53 UTC by Klint Fletcher
Location 33.150711, -117.319517
Site Name Skyline Reservoir
Site Photos
Site to Site Coordination D32LakeCal
Process Coordination SCADA (remote manual) fly valve operation / level monitoring
Communication Type Ethernet
Radio Name Skyline Res.
Radio Type Rocket M365
Skyline ReservoirSkyline Reservoir
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 210 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Parabolic
Antenna Direction 128•SE
Page: 2 of 3
Page 211 of 249
Antenna Direction Photos
Antenna Height 35 ft
Antenna Height Photos
Page: 3 of 3
Page 212 of 249
Created 2019-01-08 22:16:22 UTC by Klint Fletcher
Updated 2019-06-19 19:48:51 UTC by Klint Fletcher
Location 33.1717338395, -117.322272912
Site Name Tanglewood PRS
Site Photos
Site to Site Coordination Elm RES. Repeater
Process Coordination SCADA (monitoring)
Communication Type Serial
Radio Name Tabglewood PRS
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Antenna Direction 258•W
Tanglewood PRSTanglewood PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 213 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 2 of 2
Page 214 of 249
Created 2019-01-09 19:20:41 UTC by Klint Fletcher
Updated 2019-02-01 04:34:49 UTC by Klint Fletcher
Location 33.167304, -117.266775
Site Name TAP 4 Station
Site Photos
Site to Site Coordination CWA#4 365 AP
Process Coordination SCADA(monitor) flow
Communication Type Ethernet
Radio Name TAP-4 Station
Radio Type NanoStation M365
TAP 4 StationTAP 4 Station
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 215 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 75•E
Page: 2 of 3
Page 216 of 249
Antenna Direction Photos
Antenna Height 25 ft
Antenna Height Photos
Page: 3 of 3
Page 217 of 249
Created 2019-01-08 20:27:38 UTC by Klint Fletcher
Updated 2019-02-01 04:31:12 UTC by Klint Fletcher
Location 33.1719104061, -117.295768429
Site Name TAP North Sector
Site Photos
Site to Site Coordination Not in service
Communication Type Ethernet
Radio Name TAP5G North Sector
Radio Type Rocket M5
TAP North SectorTAP North Sector
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 218 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Directional Array
Antenna Direction 332•NW
Page: 2 of 3
Page 219 of 249
Antenna Direction Photos
Antenna Height 42 ft
Page: 3 of 3
Page 220 of 249
Created 2019-01-08 20:52:56 UTC by Klint Fletcher
Updated 2019-02-01 04:32:30 UTC by Klint Fletcher
Location 33.1717298599, -117.295748899
Site Name TAP RES - B Repeater FreeWave
Site Photos
Site to Site Coordination Laguna/Kelly PRS
ELM RES. Repeater
Process Coordination SCADA (remote manual)
Communication Type Serial
Radio Name B Res Repeater
Radio Type FreeWave
TAP RES - B Repeater FreeWaveTAP RES - B Repeater FreeWave
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 221 of 249
Radio Type Photos
Radio Frequency 900 MHz
Antenna Type Omni
Antenna Direction Photos
Page: 2 of 3
Page 222 of 249
Antenna Height 35 ft
Antenna Height Photos
Page: 3 of 3
Page 223 of 249
Created 2019-01-08 20:13:03 UTC by Klint Fletcher
Updated 2019-02-01 04:31:27 UTC by Klint Fletcher
Location 33.171882, -117.295833
Site Name TAP Reservoir to Maerkle Tower
Site Photos
Site to Site Coordination M Tower AP2TAP
Process Coordination SCADA (monitor)
Process Dependencies Calavera PoT Pump Station
Communication Type Ethernet
TAP Reservoir to Maerkle TowerTAP Reservoir to Maerkle Tower
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 224 of 249
Communication Photos
Radio Name TAP STA 2MTOWER
Radio Type Rocket M5
RadiosRadios
Page: 2 of 4
Page 225 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 126•SE
Page: 3 of 4
Page 226 of 249
Antenna Direction Photos
Antenna Height 42 ft
Antenna Height Photos
Page: 4 of 4
Page 227 of 249
Created 2019-01-08 20:22:41 UTC by Klint Fletcher
Updated 2019-02-01 04:31:40 UTC by Klint Fletcher
Location 33.17189842, -117.295750491
Site Name TAP to CWA 4
Site Photos
Site to Site Coordination CW 4 Station
Process Coordination SCADA monitoring
Communication Type Ethernet
TAP to CWA 4TAP to CWA 4
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 228 of 249
Communication Photos
Radio Name TAP 2 CWA #4
Radio Type NanoStation 365
RadiosRadios
Page: 2 of 4
Page 229 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 90•E
Page: 3 of 4
Page 230 of 249
Antenna Direction Photos
Antenna Height 42 ft
Antenna Height Photos
Page: 4 of 4
Page 231 of 249
Created 2019-01-08 20:24:57 UTC by Klint Fletcher
Updated 2019-02-01 04:31:52 UTC by Klint Fletcher
Location 33.1718793512, -117.295792485
Site Name TAP to Ellery
Site Photos
Site to Site Coordination Ellery Sta.
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Radio Name TAP AP 2 ELLERY
Radio Type Rocket 5AC PTMP
TAP to ElleryTAP to Ellery
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 232 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Parabolic
Antenna Direction 240•W
Page: 2 of 3
Page 233 of 249
Antenna Direction Photos
Antenna Height 42 ft
Antenna Height Photos
Page: 3 of 3
Page 234 of 249
Created 2019-01-08 20:35:17 UTC by Klint Fletcher
Updated 2019-02-01 04:32:15 UTC by Klint Fletcher
Location 33.1718959892, -117.295799945
Site Name TAP West AP
Site Photos
Site to Site Coordination Elm East Sector
Process Coordination SCADA (monitor)
Process Dependencies May co PRS (via FreeWave)
Communication Type Ethernet
Radio Name TAP WEST AP
Radio Type Rocket M365
TAP West APTAP West AP
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 235 of 249
Radio Type Photos
Radio Frequency 365 GHz
Antenna Type Directional Array
Antenna Direction 252•W
Page: 2 of 3
Page 236 of 249
Antenna Direction Photos
Antenna Height 42 ft
Antenna Height Photos
Page: 3 of 3
Page 237 of 249
Created 2019-01-08 20:31:31 UTC by Klint Fletcher
Updated 2019-02-01 04:32:03 UTC by Klint Fletcher
Location 33.1718679518, -117.295780163
Site Name TAP West Sector
Site Photos
Site to Site Coordination For future use
Radio Type Rocket M5
TAP West SectorTAP West Sector
Site InformationSite Information
RadiosRadios
Page: 1 of 3
Page 238 of 249
Radio Type Photos
Radio Frequency 5 GHz
Antenna Type Directional Array
Antenna Direction 252•W
Page: 2 of 3
Page 239 of 249
Antenna Direction Photos
Antenna Height 42 ft
Antenna Height Photos
Page: 3 of 3
Page 240 of 249
Created 2019-01-07 22:12:27 UTC by Klint Fletcher
Updated 2019-06-19 19:42:57 UTC by Klint Fletcher
Location 33.112563, -117.287276
Site Name Twin D Reclaim Pump Station
Site Photos
Site to Site Coordination D32LakeCal
Process Coordination SCADA (remote manual)
Communication Type Ethernet
Twin D Reclaim Pump StationTwin D Reclaim Pump Station
Site InformationSite Information
Communication InformationCommunication Information
Page: 1 of 4
Page 241 of 249
Communication Photos
Radio Name Dsitestation
Radio Type Nano station M365
RadiosRadios
Page: 2 of 4
Page 242 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 117•SE
Page: 3 of 4
Page 243 of 249
Antenna Direction Photos
Antenna Height 17 ft
Antenna Height Photos
Page: 4 of 4
Page 244 of 249
Created 2019-01-09 17:00:09 UTC by Klint Fletcher
Updated 2019-02-01 04:40:41 UTC by Klint Fletcher
Location 33.097501, -117.245168
Site Name Upper El Fuerte PRS
Site Photos
Site to Site Coordination D Res Repeater (maybe)
Process Coordination SCADA(monitor)
Communication Type Serial
Radio Name Upper El Fuerte
Radio Type FreeWave
Radio Frequency 900 MHz
Antenna Type Yagi
Upper El Fuerte PRSUpper El Fuerte PRS
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 2
Page 245 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 2 of 2
Page 246 of 249
Created 2019-01-09 17:31:40 UTC by Klint Fletcher
Updated 2019-02-01 04:41:23 UTC by Klint Fletcher
Location 33.105757, -117.252906
Site Name Zodiac PRV
Site Photos
Site to Site Coordination D3EastSector
Process Coordination SCADA(monitor)
Communication Type Ethernet
Radio Name Zodiac PRV Radio
Radio Type NanoStation M365
Zodiac PRVZodiac PRV
Site InformationSite Information
Communication InformationCommunication Information
RadiosRadios
Page: 1 of 3
Page 247 of 249
Radio Type Photos
Radio Frequency 3.65 GHz
Antenna Type Directional Array
Antenna Direction 281•W
Page: 2 of 3
Page 248 of 249
Antenna Direction Photos
Antenna Height 10 ft
Antenna Height Photos
Page: 3 of 3
Page 249 of 249
City of Carlsbad / CMWD SCADA Master Plan
D-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix D: Site Notes
Site Visit Minutes
Document1
9665 Chesapeake Drive, Suite 201
San Diego, CA 92123
T: 858.514.8822
F: 858.514.8833
Prepared for: City of Carlsbad/CMWD
Project Title:SCADA Master Plan for Sewer, Water, and Recycled Water Systems
Project No.:5542
Purpose of Meeting:IRWD Site Visit Date: January 22, 2018
Meeting Location:IRWD, Operations Center Time: 10:00 a.m.
Minutes Prepared by:Majid Karim, BC
Attendees:Lindsey Stephenson, City of Carlsbad Jose Zepeda, IRWD
Eric Sanders, City of Carlsbad Robert Tomasello, IRWD
Jesse Castaneda, City of Carlsbad Joe Lam, IRWD
Ray Martinez, City of Carlsbad Majid Karim, BC
Omar Agaz, City of Carlsbad Billy Tieman, BC
Stephanie Harrison, City of Carlsbad
Summary
The site visit at Irvine Ranch Water District (IRWD) was set up for the City of Carlsbad/CMWD
personnel to see SCADA systems at other Agencies. The main intent was to get a first-hand account
of how they went about making decisions for their SCADA system and to get lessons learned along
the way. IRWD provided a presentation of their District before moving into the agenda that we had
provided.
Visit Notes:
1. IRWD is very spread out physically with many lift stations, pump stations, stormwater/urban
runoff sites and all the remote facilities are connected to their SCADA system.
2. IRWD used the "Automation Exchange Program with Control Magazine" to get a list of
vendors to prequalify - they selected the top 3 HMI manufacturers who would be evaluated in
detail for the selection process. The district developed a detailed questionnaire for each of
the vendors to respond to for the selection process (they provided a copy of their selection
questions).
3. One of the key criteria the district wanted to ensure was that the selected system would be
widely supported and they would not be limited from a support standpoint. They did not want
a system that would be supported by only one entity.
a. What kind of support can you get? Make sure the supplier has good local support.
4. Keep your executives involved in the process to always have their buy-in.
Header (Client Name, Meeting Title)Meeting Date
2
Document1
5. They stated that it’s not enough for the sales people to tell you what the system can do, verify
that those features have been implemented in the field and they are in use by someone –
you don’t want to be the beta site.
6. Ask vendors to show you specialized scripting that they've used to show anything in their
demo:
a. Look at uptime of the system; get references for the systems you're looking at.
7. IRWD has standardized on Wonderware System Platform for the main SCADA/HMI system
and they have standardized on Modicon Programmable Logic Controllers (PLC’s) for the field.
8. They recommend using as much Off-the-shelf Software as possible; avoid too much scripting.
9. They developed their own radio communications backbone for the SCADA system. All remote
sites are in some way connected over this backbone.
10. As a backup to their SCADA system, they use Mission Controls for specific parts of the
system. This is in addition to the call-out system they have in place. Backup systems are
independent of the SCADA system. Redundancy in the control systems
11. IRWD doesn't have a dedicated control room; Operations does everything with mobile
platforms - laptops, iPad using a decentralized approach. Ops staff have cubicles in the
operations building.
a. Jose mentioned that they are now considering a centralized control room (no
explanation as to why)
12. Other software that IRWD uses are:
a. HACH WIMS - mainly used for SCADA data report; Jose thought Hach WIMS as a good
start for a centralized data system
b. DuForms – cloud-based software used to document field rounds; automatically loads
into the SCADA system when they enter the operations center
13. They are currently working to tie their CMMS system into their SCADA enterprise:
a. IRWD is currently transitioning to Maximo for their CMMS
14. With a SCADA system comes cost; you'll need this with whatever vendor you have. A lot of
software vendors are moving more to a subscription based system like Office 365
a. Licensing can get very intricate
15. Planning out your network - look at segregating your network so maintenance is easier
16. Joe recommends having IT involved in the Core team - Separation between IT and OT
17. The big thing that IRWD is looking at now is Cyber Security; 2-factor authentication is
absolutely necessary
18. When it comes to updating the SCADA system, documentation is very important
19. IRWD automation staff consists of 9 people; Manager, 2 programmers, 1 supervisor for PLCs,
3 technicians (I believe 2 staff from IT are included in count)
20. They recommended having standards for the SCADA system; With Standards, you start slow.
Don't look at it like it'll solve all your issues, maintain some flexibility
a. Need to have flexibility when it comes to packaged systems - a standard of data
transfer when it comes to vendor packages is more important.
21. Training for staff is very important:
Header (Client Name, Meeting Title)Meeting Date
3
Document1
a. On-site training is the best if you can do that
b. Don't do training too early - may lose benefit of training if it can't be applied.
22. IRWD is looking at doing another Standards, Master Plan upgrade
23. Jose - offered to talk to operations and maintenance folks again later if we'll get more as
we're further down in the Master Planning process.
24. Walked over to one of the field control panel locations. They showed us an MBR packaged
control system with a local OIT and the Plant Control System that could do control the MBR
system as well.
Action Required
The following are a list of actions required as a result of the meeting discussion:
1. Site Visit notes to document findings – No action required.
Site Visit Minutes
Document1
9665 Chesapeake Drive, Suite 201
San Diego, CA 92123
T: 858.514.8822
F: 858.514.8833
Prepared for: City of Carlsbad/CMWD
Project Title:SCADA Master Plan for Sewer, Water, and Recycled Water Systems
Project No.:5542
Purpose of Meeting:IEUA Site Visit Date: January 23, 2018
Meeting Location:IEUA, Main Building B Time: 10:00 a.m.
Minutes Prepared by:Majid Karim, BC
Attendees:Lindsey Stephenson, City of Carlsbad Jesse Pompa, IEUA
Eric Sanders, City of Carlsbad David Malm, IEUA
Jesse Castaneda, City of Carlsbad Don Hamlett, IEUA
Ray Martinez, City of Carlsbad Gary Dix, IEUA
Omar Agaz, City of Carlsbad Nick, IEUA
Stephanie Harrison, City of Carlsbad Majid Karim, BC
Kyle, City of Carlsbad Billy Tieman, BC
Summary
The site visit to Inland Empire Utilities Agency (IEUA) was set up for the City of Carlsbad/CMWD
personnel to see SCADA systems at other Agencies. The main intent was to get a first-hand account
of how they went about making decisions for their SCADA system and to get lessons learned along
the way. IEUA provided a question/answer session followed by a walkthrough of the Control Room at
RP-5, Server Room and a visit to the Carbon Canyon Facility.
Visit Notes:
1. IEUA is very spread out physically with several wastewater treatment facilities, lift stations,
pump stations, groundwater recharge sites and all the remote facilities are connected to
their SCADA system.
2. IEUA used an evaluation process during the Master Plan to get a short-list of vendors to
review in more detail. There was no RFP process to solicit bids from the short-list vendors.
3. One of the key criteria the Agency wanted to ensure was that the selected system would be
widely supported and they would not be limited from a support standpoint. They did not want
a system that would be supported by only one entity.
a. This was driven by the experience they had with the Invensys Foxboro Distributed
Control System (DCS) where they could not find system integrators that could support
the programming needs.
b. Invensys Foxboro doubled the cost of support services at one point. The
unpredictable nature of their cost structure and hikes was difficult for the Agency.
Header (Client Name, Meeting Title)Meeting Date
2
Document1
c. What kind of support can you get? Make sure the supplier has good local support.
4. Keep your executives involved in the process to always have their buy-in. IEUA did this by
setting up a core team and a steering committee to guide the project during the Master Plan.
The core team will remain active throughout the design and implementation phases.
5. IEUA has standardized on Rockwell Automations hardware/software for the SCADA System:
a. Plant PAX System for the SCADA/HMI.
b. ControlLogix Programmable Logic Controllers (PLC’s) for the field.
c. The selection was based on programming advantages that are gained by having the
HMI and PLC by the same manufacturer (follows the DCS model).
d. Programming standards are very closely aligned with Rockwell Automation templates
and programming blocks; one less thing for IEUA staff to maintain.
6. Other software that IEUA uses:
a. VantagePoint - mainly used for SCADA data report.
b. Enterprise Historian – OSI PI.
c. VantagePoint is also connected to the Laboratory Information Management System
(LIMS)
7. They developed their own radio communications backbone for the SCADA system using
licensed microwave radios at 300 MHz. All remote sites are connected over this backbone
using licensed microwave radios.
8. IEUA has put the business connectivity “on the back-burner” for now and will revisit it when
all the sites have been converted to the new SCADA system.
9. On call Operators, Automation Techs and Maintenance staff use laptops that can remotely
connect to the SCADA system over a Virtual Private Network (VPN) connection.
10. For critical items backup, IEUA uses a software based call-out dialer system (WIN911) and a
cellular radio (RACO) calling system.
11. Firmware upgrades are becoming more common due to security concerns.
12. IEUA has a north SCADA system and a south SCADA system, based on geographic boundaries
since the service area is 242 sq. miles. Each system is redundant and can also back up the
other system.
13. With a SCADA system comes cost; you'll need this with whatever vendor you have. A lot of
software vendors are moving more to a subscription based system like Office 365
a. Licensing can get very intricate
14. IEUA automation staff consists of 8 people
15. Training for staff is very important:
a. On-site training was done for IEUA staff
16. Discussion on field work during conversion of SCADA system:
a. Having detailed documentation of the control panels and wiring is a must; if this is
not available, have a project to develop it first.
b. Have detailed documentation on how the cut-over will be done; include personnel
needed, the amount of time estimated and the failover if not successful.
Header (Client Name, Meeting Title)Meeting Date
3
Document1
c. Include small work that could be done if the main shutdown work is completed ahead
of schedule (filler work).
d. You need to have detailed control strategies for all the programming.
e. Make sure you have lots of documentation.
f. For upcoming projects, IEUA has a pre-project for the as-built documentation.
17. Walked through the control room at RP-5 and the server room. Got some idea of room sizes.
18. Visited the Carbon Canyon Facility and looked at the control room there and walked through
their High Performance HMI screens.
Action Required
The following are a list of actions required as a result of the meeting discussion:
1. Site Visit notes to document findings – No action required.
Operations Shadowing Minutes
Document1
9665 Chesapeake Drive, Suite 201
San Diego, CA 92123
T: 858.514.8822
F: 858.514.8833
Prepared for: City of Carlsbad/CMWD
Project Title:SCADA Master Plan for Sewer, Water, and Recycled Water Systems
Project No.:5542
Purpose of Meeting:City of Carlsbad Water/Recycle Site Visits Date: February 14, 2018
Meeting Location:City of Carlsbad, Utility Department Time: 7:00 a.m.
Minutes Prepared by:Billy Tieman, BC
Attendees:Ray Martinez, City of Carlsbad/CMWD
Billy Tieman, BC
Summary
The operations shadowing for the City of Carlsbad/CMWD followed water/recycle operations for a
day to understand what their needs may be for a SCADA system. During the shadowing, BC observed
the duties for the operators while making daily round to selected sites. Typically, the city/CMWD
takes chlorine residual and TDS readings at all reservoirs every Wednesday, Saturday, and Sunday
visits the larger lift stations on Mondays, Wednesdays, and Fridays.
Control Room - morning at console
Check tank levels
Check pressures
Maerkle
o Check residuals
Scan system from screen to screen
o Check pump performance
Review level changes vs. pump running
Look for discrepancies
o Look for any water events
High flow
Hit hydrants
If found, need to calculate water loss
Check alarms
o Alarms and “info” on same screen, no filter
Review communications stats
o Look for abnormal
Header (Client Name, Meeting Title)Meeting Date
2
Document1
o Not all are 100% normally
Duty Operator / morning checkins
Get samples
Check inventories
Discuss alarms overnight if any
Daily assignments (by Eric Sanders – Supervisor)
Everyday
o Go to Maerkle
Wed, Sat, & Sun – every reservoir
o Check CL2 residuals
o Check TDS
Don’t know blend of Desal vs. WTP water
Flow changes
o All changes recorded in flow book
Manually entered
No backup copies
Recycled system
o Check pump performance
Review level changes vs. pump running
Look for discrepancies
Use jockey pumps 24/7 to maintain pressure during the day
o Typically, no notification of production issues at CWRF
Can order water from Mahr (Vallecitos)
CWA #3
Has two customers b/w 3 PR stations. CWA #3 must have flow or these two customers don’t
have water
o 1 farmer
o 1 customer
Have a jockey pump to keep pressure if CWA #3 does down.
CWMD will manipulate water at this connection rather than vary the lake flow (Maerkle)
o Due to changing residual dosing at Maerkle
Maerkle Dosing
Manually set dosing
This drives using other water connections (CWA #3) so they done have to manipulate dosing
setpoints
No ammonia monitoring (only chlorine)
CWA #6
Cannot order lower than 4 CFS
Their flow meter will not register lower flow than 4 CFS
CWA #6 fills Santa Fe #3
o SF #2 fills D3
Header (Client Name, Meeting Title)Meeting Date
3
Document1
Have to carefully fill/draw both tank in winter to prevent bad WQ
Hydro Station
Only works when flow is at 7 CFS
All PRVs
Are open/close commands (no setpoints)
They time the length they hold the open/close button at SCADA to determine how far to
open/close PRVs
Fine tuning PRVs is difficult
Calavera Potable PS
Not normally running
Has jockey pump
o Must be started on site
o Cannot see status on SCADA
Use pump station only when CWA #4 is at 0 (zero) flow
Jockey pump is for when flow is too low for normal pump
Possibly has UPS, (can see “no power” alarm at SCADA
Can see from SCADA
o Pressure (up/.down)
o Flow
o Pump 1 & 2
o Cannot see JP
ISSUE
o Air gets trapped in pump (highest point in system)
Air Vac gets stuck closed
Air gets hot, water gets hot, bearings fail on pump
Is it possible to monitor temp of pump surface or water?
“B” Reservoir
Sample point
Manual gauge for tank pressure in manway, compare to tank level on SCADA
TAP high/low PRV
6 or 7 radios located here
Have cameras, but not compatible with current version of Wonderware
Can see from SCADA
o Level
o Up stream pressure
o Flow
Intrusion and physical inspection of site
Elm Reservoir
2 radios
No line of site
Header (Client Name, Meeting Title)Meeting Date
4
Document1
Still on 900 MHz
Repeater site
o May Co. and Tanglewood repeat back to here
Hydraulic issue
o Must do deep cycle on water
o Water will go back quick
Can see from SCADA
o Level
Manually check residual and TDS
Ellery Res and Ellery PRV
Old HACH broken, “waiting” to replace based on master plan
Can see from SCADA
o Level
o Pressure upstream
o Valve position
o Flow
o Open/close actuator
Manual samples
Physical inspection of site
New telemetry pole being installed for sheriff dept.’
o May be able to use tower for communications
Pump station abandoned 6 months ago
o Still has connections for mobile pump if necessary
Skyline Res and PRV
Can see from SCADA
o Level
o Flow
o Upstream pressure
o Open/close
o Valve position
Physical inspection of site
Manual samples
Only enter PRV vault for vault inspections
o Every two months
Rebuild cla-valve every 3 -5 years
Header (Client Name, Meeting Title)Meeting Date
5
Document1
Santa Fe #2 Res
No power – only solar
Physical issues
o Skateboarders and other intrusions
Reservoir in ground (partially exposed)
o 2-3 ft on south side
o 20-25 ft on north side
Weather station on top or reservoir
Drop sample into tank from latch
Can sample pump be used
o Tank at half full or less
o Ground level is above the water level in tank
La Costa High Res
Can see from SCADA
o Level
Vault has inlet/outlet pipe only
Pax mixer
o Shuts off at 5 ft level
o Can remotely restart mixer
D Tank / Raphie PRV
Can see from SCADA
o Level
Manual residuals
Open/close tank valve (PRV)
Maerkle
No Generator status from Maerkle
Recycle system
20 sites that TDS and chlorine residual
o Res/TF(CWRF) /various distribution points
Sludge/non-suspended solids in tanks
o After 6 months had 3 inches
No backup power at any recycled site
Operations Shadowing Minutes
Document1
9665 Chesapeake Drive, Suite 201
San Diego, CA 92123
T: 858.514.8822
F: 858.514.8833
Prepared for: City of Carlsbad/CMWD
Project Title:SCADA Master Plan for Sewer, Water, and Recycled Water Systems
Project No.:5542
Purpose of Meeting:City of Carlsbad Wastewater Site Visits Date: February 21, 2018
Meeting Location:City of Carlsbad, Utility Department Time: 7:00 a.m.
Minutes Prepared by:Billy Tieman, BC
Attendees:Omar Agaz, City of Carlsbad
Billy Tieman, BC
Summary
The operations shadowing for the City of Carlsbad followed wastewater operations for a day to
understand what their needs may be for a SCADA system. During the shadowing, BC observed the
duties for the operators while making daily round to selected sites. Typically, the city visits the larger
lift stations on Mondays, Wednesdays, and Fridays. The smaller lift stations are typically visited on
Tuesdays and Thursdays. For the purposes of this shadowing, both large and small lift stations were
visited to understand daily operations duties at both types of locations. While visiting the stations,
certain SCADA/control system equipment was also listed to gain a feel for how the operations staff
was interacting with the local control system on site.
Control Room
Mission system
Check each station
o Look for abnormalities
o New mission system at Batiquitos
Smart covers in strategic locations
o Contract with Smart Cover
o Batteries last 6-9 months
Replacement part of contract
o Mounted under manholes
o Green reflectors
Collections
o Maintain sewer lines
o Manholes
Header (Client Name, Meeting Title)Meeting Date
2
Document1
o Easements
Operations
o Lift stations
o Plus monitoring
Last 10 years standardizing pumps, controllers, valves, and other physical equipment
El Fuerte
Allen Bradley Panel View Plus 1000 OIT
Allen Bradley SLC 5/03 PLC
Mission
Opto 22
Verbatim Autodialer
Digigage
o Local Pump Controller
APCD – Air Pollution Control District
o Odor control
o Air quality compliance
o Only paper copy onsite for local records
Online sensors (H2S, combustible gas, O2)
o Too expensive to maintain
o Scott
O2
H2S
Methane
Use portable sniffer for LEL readings
o Calibrate monthly
Manual records
o Power meter
o Flow meter
o Level wetwell
Visual Inspection
o Scrubber
o Dry well
o Wet well
Surge Tank
o Manual gauge
o Reduce surge, when pump station shuts off
Poinsettia
Manual readings
Digigage
o Local Pump Controller
I/O plexer
o Feeds Mission system
Header (Client Name, Meeting Title)Meeting Date
3
Document1
Manually run generator monthly
Biosulfite added for odor control
Mobile pump and generator
o Mobile pump wired in with separate control floats/signals
o Does not report to Mission that external pump is on
Bataquitos LS (next to lagoon)
Manual readings
Digigage
o Local Pump Controller
Milltronics Hydroranger
o Don’t use
IO plexer still on site
Have to run pumps locally or in hand to clean wetwell
Can send extra influent to bypass (overflow) area
Surge tank
Outside fuel tank
Knotts (in subdivision)
Manual readings
Deep pit
Vacuum truck would handle W/W in
o 1 fill for the day
Home plant (2359 Carlsbad Blvd) by traffic circle
Old and New PS
2 outlet force mains
Bioscrubber
Wetwell sprinkler to break up fats, oils and greases (FOG)
City of Carlsbad / CMWD SCADA Master Plan
E-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix E: Workshop Notes
State of the Industry Minutes
Document1
9665 Chesapeake Drive, Suite 201
San Diego, CA 92123
T: 858.514.8822
F: 858.514.8833
Prepared for: City of Carlsbad/CMWD
Project Title:SCADA Master Plan for Sewer, Water, and Recycled Water Systems
Project No.:5542
Purpose of Meeting:State of the Industry Workshop Date: January 30, 2018
Meeting Location:City of Carlsbad, Public Works Time: 9:00 a.m.
Minutes Prepared by:Majid Karim, BC
Attendees:Wendy Chambers, City of Carlsbad Lindsey Stephenson, City of Carlsbad
Terry Smith, City of Carlsbad Eric Sanders, City of Carlsbad
Aaron Beanan, City of Carlsbad Jesse Castaneda, City of Carlsbad
Mark Biskup, City of Carlsbad Stephanie Harrison, City of Carlsbad
Tom Klein, RCS JP Semper, BC
Mike Karl, BC Derek Schell, BC
Billy Tieman, BC Majid Karim, BC
Summary
1. Initial review of the Agenda and objectives of the meeting; review of the Master Plan
progression and MSA potential work.
2. Mike Karl presented on the following issues:
a. Industry Challenges
b. Cutting edge technologies; used a bell curve to show where most utilities fell with a
very few that were in the cutting edge.
c. Innovative technologies; Use of mobile technologies with smart phones and tablets
d. Progression toward Smart Utility
e. Case studies; Suez and Jordan Valley Water Conservancy District (JVWCD)
f. Update on what we saw during site visits
3. Poster Board for ideas on sticky notes
Discussions
1.Data connectivity with water/wastewater modeling (hydraulic models) – is this being done with
live data? It can be, or it can be data that’s imported.
Header (Client Name, Meeting Title)Meeting Date
2
Document1
City: In an ideal world we would want live modeling; we want to be in the leading edge of
technology.
2. IOT sensor slide got everyone’s attention: small, wireless, low cost, low maintenance sensors:
3. Discussions about a Utility level warehouse; Data sharing between departments and multiple
software platforms.
4. Discussions about asset management software and CMMS software that the City is looking
at bringing on in the near future.
5. The “Levels of Maturity” slide provides information on the steps to a highly automated facility
as follow:
a. Level 0: Manual operations
b. Level 1: Basic monitoring
c. Level 2: Automated monitoring (basic control)
d. Level 3: Fully automated monitoring and control (basic integration)
e. Level 4: Situational awareness – enhanced SCADA
f. Level 5: Optimization and Business performance
6. BC explained the projects that come out of the SCADA master plan will bring the City to a
level 3; The City said they wanted to be at a 4 or 5 and did not want to get stuck at a 3. City is
analyzing data like Level 4, but they are doing it manually. The SCADA Master Plan projects
will lay the foundation to automate the Level 4/5 activities
7. City wants a master plan that does not need a “champion” and can go up the maturity chart
without getting stuck at level 3. The master plan needs to be resilient enough to consider
activities beyond a Level 3 to empower Level 4/5 activities. May be covered in future task
orders.
8. Selecting the right technology lays the foundation for a SCADA system to go up the maturity
chart. During the IEUA site visit we learned that they are in a holding pattern when it comes
to implementing the higher levels. There were questions about whether they would have to
redo their master plan if it’s on hold too long. What can we learn from them? Master plan
needs appropriate resources to implement activities. Utilities can also initiate some of the
initial activities required for design – communications study, documentation, IT coordination,
etc.
9. Smart utility adds context/wisdom to data and allows situational awareness of using the
data. There was a discussion on high performance HMIs and the benefits they provide.
10. City wanted to know if there were any utilities in Southern California that were on a 4 or 5 on
the maturity curve. Mike mentioned there were a few but not within California.
11. City mentioned that there is a big difference between wastewater treatment plants and lift
stations when it comes to automation. Could these possibly need different technologies due
to the difference in sophistication? The discussion also covered the data need of the overall
enterprise without impact operations.
12. There was a comment that training is very dependent on the operators themselves; some
like to get into a lot of details about how the system works and others just want to learn how
to use the system for their specific use.
Header (Client Name, Meeting Title)Meeting Date
3
Document1
13. When discussing the needs of the City as a whole, there was a comment of whether it would
make sense to start the planning from a maturity level 5 standpoint and work backwards.
Would it be useful to have some guiding standards that everyone is looking at so the City
gets new software for other uses (CMMS, asset management, finance, etc.) there would be
certain requirements that would have to be met.
14. The City mentioned that they have constraints within the City and have to work with other
departments that are not within their control (Public Works).
15. In discussions about technologies, there are vendors that are in the forefront when it comes
to compatibility with Microsoft and others so it becomes easier to build using commercial off-
the-shelf (COTS) software packages. This becomes more important as you go up the maturity
curve.
16. There was a discussion about the need for having standards at the PLC, HMI, and possibly
the Smart Utility levels. The merit of closely tying the City standards to selected vendor
standards so the responsibility of maintaining the standards is with the vendor and not the
City.
17. There were discussions on having a strong communications backbone; use of licensed radios
as done at IEUA seemed to be a preference.
18. There was mention of using actual data to analyze the return on investment (ROI) of the
upgrades as we move forward.
19. From the site visits, one of the lessons was the City may need to have a person(s) that are
qualified in control systems to work on the effort as it progresses.
Action Required
The following are a list of actions required as a result of the meeting discussion:
1. Get job descriptions from IEUA and IRWD for their SCADA staff; something that the City can use as
a base when looking at hiring.
2. Map out constraints the City has; older systems, etc.
Enterprise Data Mapping
Document1
9665 Chesapeake Drive, Suite 201
San Diego, CA 92123
T: 858.514.8822
F: 858.514.8833
Prepared for: City of Carlsbad/CMWD
Project Title:SCADA Master Plan for Sewer, Water, and Recycled Water Systems
Project No.:5542
Purpose of Meeting:Enterprise Data Mapping Workshop Date: February 13, 2018
Meeting Location:City of Carlsbad, Public Works Time: 9:00 a.m.
Minutes Prepared by:Majid Karim, BC
Attendees:Lindsey Stephenson, City of Carlsbad Aaron Beanan, City of Carlsbad
Tye Gillespie, City of Carlsbad Eric Sanders, City of Carlsbad
Ligeia Heage, City of Carlsbad Jesse Castaneda, City of Carlsbad
Greg MacLellan, City of Carlsbad Mario Remillard, City of Carlsbad
Timothy Smith, City of Carlsbad Derek Schell, BC
Tom Klein, RCS Billy Tieman, BC
Majid Karim, BC
Summary
1. This workshop was specifically designed to be interactive.
2. Participants in the team provided information on the following:
a. Do they need data from others in the Utility?
b. Do they prepare reports that are presented or used in documents?
c. Where does the information come from?
d. Do they receive conflicting information from multiple sources?
3. The intent of the workshop was to understand data flow within the utility, and as such all
departments were represented.
4. The City’s steering committee has made it clear that the goal is to be fully automated and
move to integrating live modeling into automation.
Discussions
1. Eric Sanders provided information in the Water and Recycled Water systems:
a. The task of Purchasing water & making sure City meets demand; Information
gathered on tank levels and system from SCADA as the source.
Header (Client Name, Meeting Title)Meeting Date
2
Document1
b. Use information from the weather forecast to determine daily needs based on
storage and water quality.
c. The Maerkle reservoir site has chlorine system that can be used to add chlorine to
the system as needed. There is a manual “cookbook” at Maerkle that provides data
based on past experience (trail knowledge).
d. Currently manual readings are recorded in notebook; looking to move to tablets
e. Hydro generators used at Maerkle as much as possible;
f. For Maerkle, there is some data available on the SCADA system but additional data is
needed to make it complete.
g. Operations maintains lower levels in reservoirs to avoid the need for chlorine
addition. This is done based on system operations experience.
h. Data collected is being stored in spreadsheets.
i. The City has 3 options during the day (specific times) to purchase water - 1 hour
ahead of need. This is done by sending emails to the providers.
j. Emails sent to SDCWA for 3 connections.
k. Emails sent to Vallecitos for 2 connections.
l. Would like to see more automation at Maerkle instead of getting alarms and trying to
figure out what steps are needed. Some alarm responses can be automated.
m. There is a need to capture system institutional knowledge from experienced
operations staff.
n. Need more real-time information on the distribution lines to better understand overall
water balance.
o. The goal for water quality is a 100% compliance.
p. Potential for automating data received from other utilities such as CWRF, Vallecitos,
Encina; currently receive spreadsheets from Encina.
q. Lucadia has a direct connection to a golf course but the future relationship is not
known.
2. Ligeia Heage provided information on the Analyst’s needs:
a. Discussed the different sources of data that are needed for reports:
i. Production data comes from IT; crystal report
ii. Sales data
iii. Need good data for water loss
iv. Needs data by type of meter; residential, business
v. Water production data – needed by source and where it’s used
vi. Cost of service
b. In a perfect world would have a data warehouse.
c. Lot changing with the AMI world – need AMI information and tier 1, 2, 3 data.
Header (Client Name, Meeting Title)Meeting Date
3
Document1
d. Data needs for the analyst are not based on instantaneous data or even hourly data.
More interested in longer periods where the data has been compiled into a useable
form.
e. The reports that are prepared rely entirely on all manual data entry.
f. Analyst has to compares different sources of data and needs to make a judgement
call on which data is the most accurate.
g. Analyst needs to physically enter data into federal or State web sites.
h. Analyst would need something like IBM SPSS statistical analysis software to manage
the quantity of data they deal with. This cannot be done in Excel (pain point).
i. Should be able to break out water produced by different sources and have
information on where this water was sold.
j. Data needs to be aligned with cost of service data.
3. Mario Remillard provided information on the Automated Meter Infrastructure:
a. The City is in the process of installing and bringing online the new Advanced Metering
Infrastructure (AMI) and sales per pressure zones.
b. The current AMR software is called WaterSmart and is cloud hosted by the
manufacturer. Not sure if WaterSmart will continue to be used with iTron.
c. The new AMI software, iTron, has the following key features:
i. Provides accurate meter readings to finance
ii. AMR driveby system currently being used; verifying accuracy at this time
iii. Currently read the first 4 business days
iv. Currently converting these to an AMI system iTron
v. AMI provides realtime data - entire system polled every hour
d. Harris billing system is the current system.
e. The City has 114 meter routes; 29,500 meter accounts.
f. Application called Watersmart to work with AMI software; it's also a customer portal.
g. The AMI system needs production information from operations to produce reports.
4. Greg MacLellan provided information on producing reports:
a. Get's data from Operations (Eric), cross-connection group, and others to produce
reports.
b. Produces water maintenance reports
c. CMMS software is Hansen.
d. Produces maps with GIS data and correlates them with water/wastewater items.
e. Reports for monthly business meeting - visual backup.
f. Apparent water loss was very difficult to determine.
g. Reports are being tried to benchmark work.
h. CMMS used to be a timekeeping tool and then evolved into all kinds of other things.
i. Some of the data that's collected is used for determining costs toward customers.
Header (Client Name, Meeting Title)Meeting Date
4
Document1
5. Jesse Castaneda provided information on wastewater:
a. On the collection side, Jesse would like to see the SmartCovers integrated into the
SCADA system.
b. Flows are being measure at all lift stations.
c. Currently working on getting the SmartCovers to provide flow information as well.
d. All information is manually entered into forms; This will be entered into some
electronic format in the near future.
e. Would be good to add flowmeters into the collection system.
f. Ongoing maintenance of collection system lines includes CCTV of pipelines and
maintenance of lines identified as needing work.
g. The wastewater operations receives some trends from Mission controls – The web-
based monitoring system currently used.
h. Daily reports from Mission - view only; can be sent in Excel format.
6. Tye Gillespie provided information on asset management:
a. Long-term issue is to look for ways to capture cost.
b. Impact of different users and the impact they have on the overall systems.
c. Currently tracking costs per assets.
d. Linear assets are quite well dialed in.
e. Vertical assets are not that well defined.
f. Someone (operations?) provides lift station information on power etc.
g. Dealing with 10 different types of systems with 3 folks is very challenging.
h. A lot of data is very manual and getting data to time-match is very difficult (Issue
about time-matching data came up several times from different people. Real
problem).
i. Need to continually adapt to changes.
7. Timothy Smith provided information on water operations and maintenance:
a. Cannot get any information automatically.
b. Has to go get it from individuals instead of pulling it up on a computer.
c. Need to get a system in place where data can be extracted without going to
individuals.
d. Getting it to work with the CMMS software is challenging.
e. Too many different systems are needed to get anything done.
f. CCTV is a data hog (bandwidth as well).
g. There needs to be a way to automate information that goes into the CMMS for them
to take action.
h. Can't track the hydro electric information from the Maerkle site so it has to be
manually entered.
i. Need more information to make better decisions.
Header (Client Name, Meeting Title)Meeting Date
5
Document1
j. In order to make any decisions, needs meetings, information from all other parties,
finance, etc. The process is very time-consuming.
Action Required
This was an information gathering workshop so there are no actions that are required.
City of Carlsbad / CMWD SCADA Master Plan
F-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix F: Additional Observations
F-2
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix F
Additional Observations
The observations provided in the table below are implementation specific in achieving the goals of
the Master Plan.
Area Deficiencies and Desires
Field Instruments
Connect all existing field instruments
Add more water quality monitoring (chlorine, TDS, pH, ammonia)
Add automated chemical dosing, especially at Maerkle
Add more water flow monitoring
Add more sewer flow monitoring
Add generator monitoring and control at Maerkle
Add jockey pump monitoring and control and temperature monitoring at Calavera pump station
Add other instruments for preferred monitoring, control, and alarming functions
Control Hardware (PLC)
Standardize PLC and enter into long-term service and equipment agreement
Provide remote control of the wastewater system
Select system with strong water/wastewater presence that is actively supported by the manufacturer and
is widely supported by many certified system integrators
Utilize as much off the shelf options and as little customization as possible
Develop hardware, programming, and data exchange/connectivity standards that still provide flexibility for unique situations, such as packaged systems
Add ability to receive third party data (AMI; Encina Wastewater Authority - wastewater and CWRF;
Vallecitos Water District - Meadowlark, Mahr and water transfers; SDCWA; Smart Covers; Leucadia Water District - Gafner; etc.)
Communications
Conduct communications study
Evaluate licensed, high-band width communications backbone
Address recommendations from communications study
City of Carlsbad / CMWD SCADA Master Plan Appendix F
F-3
SC07221_FINAL_Carlsbad SCADA Master Plan
Area Deficiencies and Desires
HMI
Provide redundant servers
Standardize HMI and enter into long-term service and equipment agreement
Select system with strong water/wastewater presence that is actively supported by the manufacturer and
is widely supported by many certified system integrators
Utilize as much off the shelf options and as little customization as possible
Provide tiered access levels, with extra screens for monitoring only
Provide single HMI system for multiple operations groups with access to appropriate operations screens
per operator's login information.
Develop programming, high performance graphics, and data exchange/connectivity standards that still provide flexibility for unique situations, such as packaged systems
Provide remote monitoring capabilities
Develop alarming criticality standards
Remove nuisance alarms
Safety and Security
Provide video security at remote sites
Provide permanent gas detection monitoring
Complete Department of Homeland Security audit and achieve required cybersecurity level
Consider back-up alarming system, such as Mission
Remote access via laptop/tablet
Data Storage
Provide enterprise historian based on SQL
Coordinate with IT on server/historian needs
Provide means for automatic collection of data in the field
Integrate other data sources besides SCADA into enterprise historian
Develop baseline connectivity requirements for all utilities software, including SCADA
Data Presentation/ Connectivity
Utilize technology to present/access data
Create dashboards to address user needs/questions (water balance, preventative maintenance, ROIs, production reporting, etc.)
Create baseline connectivity requirements for software connectivity
Integrate SCADA and enterprise historian with other business systems
Integrate CMMS and SCADA data sources for predictive maintenance
Complete a Technology Master Plan or Smart Utility Master Plan to promote evolution to Smart Utility
Migration
Refine I/O, network diagram, wiring diagrams, and control strategies documentation to prepare for
design
Consider specialized CM&I staff
Clean up existing/abandoned hardware
Require SI bidders to demonstrate they can complete work - redundant experts, current projects, revenue stream,
Require SI to maintain licensing during construction and for 2-3 years after to force support
City of Carlsbad / CMWD SCADA Master Plan Appendix F
F-4
SC07221_FINAL_Carlsbad SCADA Master Plan
Area Deficiencies and Desires
Staffing
Staff up to support SCADA improvements
Evaluate staffing needs support new systems created through this process (network, servers, instruments, PLCs, HMIs)
Develop and train staff to support new systems created through this process (network, servers, instruments, PLCs, HMIs)
Space
Staff up to support SCADA improvements
Evaluate staffing needs support new systems created through this process (network, servers, instruments, PLCs, HMIs)
Develop and train staff to support new systems created through this process (network, servers, instruments, PLCs, HMIs)
Staff up to support SCADA improvements
City of Carlsbad / CMWD SCADA Master Plan
G-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix G: HMI Software RFP
REQUEST FOR PROPOSALS FOR A MASTER SOFTWARE AND
SERVICE AGREEMENT FOR THE
HUMAN MACHINE INTERFACE
RFP19-480UTIL
City of Carlsbad
Carlsbad Municipal Water District
1635 Faraday Avenue
Carlsbad, CA 92008
July 2018
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 1 of 11
NOTICE INVITING PROPOSALS
The City of Carlsbad (City) and the Carlsbad Municipal Water District (CMWD), a subsidiary district to the
City of Carlsbad, are soliciting proposals for Human Machine Interface (HMI) and Programmable Control
Logic (PLC) systems on which to standardize the water, recycled water, and sewer Supervisory Control and
Data Acquisition (SCADA) systems. To achieve this, City/CMWD is concurrently conducting the separate
Request for Proposals (RFP) process to standardize on a manufacturer for both the HMI and PLC and enter
into negotiations for a long-term agreement with each of the selected manufacturers.
This RFP is specifically for the HMI. The companion RFP for the PLC may be found on the City/CMWD’s bid
website. Proposals may be submitted on one or both systems, but separate proposals are required.
City/CMWD anticipate that a manufacturer’s authorized distributor may be working in close coordination
with the respective manufacturer, but the final agreement will be executed directly with the
manufacturer, or provisions must be provided by the manufacturer to guarantee the agreement for its
full term, regardless of a change in the manufacturer’s authorized distributor.
Until 2:00 pm PST on August 23, 2018, the City/CMWD shall accept sealed proposals, clearly marked as
such, at the location identified in instructions. The envelope enclosing the proposal shall be sealed, and
delivered or mailed to the City of Carlsbad.
A non-mandatory pre-proposal meeting will be held at the date and time specified in the RFP schedule at
5950 El Camino Real, Carlsbad, CA 92008.
All questions regarding this RFP shall be submitted in writing, via email, prior to the deadline specified in
the RFP schedule. The RFP number must be referenced in the email title, and addressed solely to.
Graham Jordan, Contract Administrator
PWContractAdmin@carlsbadca.gov
Key dates for the RFP schedule are included in the following table. A more detailed schedule is provided
in the RFP.
ACTIVITY SCHEDULE
RFP Issued July 18, 2018
Pre-Proposal Meeting August 2, 2018, 1:00 PM PST
Deadline for questions August 10, 2018, 5:00 PM PST
Final Q&A and/or addendum issued August 16, 2018
Proposals due August 23, 2:00 PM PST
A Selection Committee will evaluate the proposals using established review criteria. During the evaluation
process, City/CMWD reserves the right, where it may serve City/CMWD’s best interest, to request
additional information or clarifications from firms submitting proposals. The top two or three
manufacturers are anticipated to be invited to participate in a second round of evaluations. Upon
completion of the evaluation process, a long-term services agreement will be negotiated. The contract
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 2 of 12
will be approved by the City Council/Board of Directors and will be administered through staff at
City/CMWD. Details for are provided in the RFP.
City/CMWD reserves the right to retain all proposals submitted and to use any ideas in a proposal
regardless of whether that proposal is selected. By submitting a proposal, the firm is providing a guarantee
to the city that, if chosen, they will be able to provide the proposed services during the period of time
discussed in this Request for Proposal (RFP). There is no expressed or implied obligation for City/CMWD
to reimburse responding firms for any expenses incurred in preparing proposals in response to this
request. City/CMWD reserves the right to reject any or all proposals for any reason and seek new
proposals or take other action.
This RFP contains instructions governing the proposals to be provided, requirements which must be met
for eligibility consideration and general evaluation criteria. Proposals should be simple and economical,
providing a straight-forward and concise description of the proposer’s ability to meet the requirements
specified in this RFP.
For this RFP, the proposal must remain valid for at least ninety (90) days. Additionally, the contents of the
proposal of the successful bidder shall become the basis for the contractual obligations when a contract
is awarded. The payment amount for the services to be rendered will be negotiated with the firm selected
and said firm will be required to enter into a formal agreement with City/CMWD. City/CMWD reserves
the right to delete or amend any of the services as listed and described in this RFP.
If a satisfactory contract cannot be negotiated, negotiations will be formally terminated. Contract
negotiation will then begin with the next alternate proposer.
We look forward to your response.
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 3 of 12
TABLE OF CONTENTS
1. Purpose
2. Background
3. Instructions to Proposers
4. Attachments
A. Evaluation Criteria
B. General Provisions
C. Sample Master Software and Service Agreement
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 4 of 12
SECTION 1: PURPOSE
The City of Carlsbad (City) and Carlsbad Municipal Water District (CMWD), collectively called City/CMWD
or Owner, have initiated a master planning effort to evaluate and upgrade the Supervisory Control and
Data Acquisition (SCADA) elements for their sewer, water, and recycled water systems to provide for
operational flexibility with enhanced system monitoring and control to maintain quality and improve
system efficiencies. Additionally, City/CMWD desires to have a SCADA system that supports enterprise
connectivity throughout the utility and can help the utility develop into a smarter, more sustainable utility.
City/CMWD anticipates that implementing this master plan will provide City/CMWD with a standardized,
state of the art SCADA system, complying with all security measures recommended by Homeland Security
and other regulatory agencies. The vision statement of the master plan is:
To have a uniform, fully integrated SCADA system that supports utility-wide business intelligence to
optimize operations and provide flexibility for future growth and adaptability as a smart utility.
To date on the SCADA master plan, City/CMWD have evaluated the existing SCADA system and completed
an operational needs and deficiencies assessment.
As noted in the vision statement, a key component of the master planning effort is to have standardized
equipment. The next key step in the master planning process is to conduct this RFP process to standardize
on specific manufacturers for the PLC and HMI that will be utilized through the implementation of the
future SCADA system. The results of the existing system evaluation and the operational needs and
deficiencies assessment have been used to develop the evaluation criteria for this RFP. A best-value
evaluation will be utilized to provide City/CMWD with the best manufacturer to meet the needs of the
users.
This RFP is specifically to standardize on the HMI manufacturer. This RFP encompasses only the selection
of the materials and establishing material and service costs that will serve as the basis of the negotiations.
This RFP does not include implementation services. The companion RFP for the PLC may be found on the
City/CMWD’s bid website. Manufacturers may submit proposals on one or both systems, but separate
proposals are required.
City/CMWD intends to standardize on the HMI manufacturer and enter into a master software and service
agreement with the selected manufacturer. The negotiated agreement will establish core pricing for
products and services for 10 years, with an established annual escalation rate for the full term. The
selected manufacturer will be required to honor pricing terms with City/CMWD staff and
vendors/contractors authorized to work on City/CMWD projects.
City/CMWD anticipate that a manufacturer’s authorized distributor may be working in close coordination
with the respective manufacturer, but the final agreement will be executed directly with the
manufacturer, or provisions must be provided by the manufacturer to guarantee the agreement for its
full term, regardless of a change in the manufacturer’s authorized distributor.
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 5 of 12
SECTION 2: BACKGROUND
The City of Carlsbad
The City of Carlsbad, California is located 35 miles north of the City of San Diego on the Southern California
coast. The city has a population of nearly 107,000 and serves an area of 39 square miles. With three
lagoons, more than 45 miles of trails, and a third of its land set aside as open space, Carlsbad has been
widely recognized for its responsible approach to growth management and maintaining a high quality of
life for residents and businesses as it approaches build out. Carlsbad is a popular tourist destination, home
to LEGOLAND, the Flower Fields, and nearly seven miles of coastline. The city is also known as a hub for
the golf industry and leading high tech and biotech companies.
The City incorporated in 1952 and has a council/manager form of government. The City Council consists
of a mayor and four council members. Other elected officials include the City Clerk and City Treasurer.
The City has a long standing track record of political stability and fiscal responsibility and holds a AAA
credit rating from Standard & Poor’s. The City’s operating budget for the current fiscal year is in excess of
$250 million. The City’s Capital Improvement Program includes approximately $64 million in
appropriations for the most recent fiscal year, with 235 projects planned over the next 15 years at a cost
of about $463 million. The City has approximately 650 full-time employees and 350 part-time employees.
More information is available on the City’s website.
Utilities Department
The Carlsbad Municipal Water District (CMWD) is a subsidiary district to the City of Carlsbad. The City
owns the sewer system, and CMWD owns the water and recycled water systems. All three systems
operate under the umbrella of the City of Carlsbad Utilities Department.
The Utilities Divisions’ mission is: Provide quality utility services in a fiscally and environmentally
responsible manner for the Carlsbad community.
Sewer System
The City provides wastewater collection services to 30.5 square miles, approximately 78 percent of the
city limits, through six interceptor lines, approximately 270 miles of collection pipelines, and 12 active lift
stations.
The lift stations are currently monitored using a Mission Communications SCADA platform that provides
information back to the city via cellular modems. This Mission Communications based SCADA system
utilizes a web-based graphic user interface to provide information to the city users. As a backup to the
primary system (Mission), phone-based autodialers (Verbatim) are used at critical sites to send critical
alarms to on-call staff.
Water and Recycled Water System
CMWD provides water and recycled water services to approximately 85 percent of the city limits.
For the water system, CMWD imports treated water from the San Diego County Water Authority and
delivers approximately 14,000 afy of potable water to its customers through a widespread system,
consisting of over 450 miles of pipelines and 17 pressure zones. The existing water system is comprised
of 4 turnouts, 8 reservoirs, 4 pump stations and 77 pressure-regulating sites, as well as a hydroelectric
facility.
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 6 of 12
For the recycled water system, CMWD delivers approximately 4,000 afy of recycled water to its customers
through a widespread system. The existing recycled water system is comprised of 3 reservoirs, 3 pump
stations, and 5 pressure-regulation stations.
The water and recycled water systems currently utilize OPTO 22-based equipment at the sites to collect
process data and relay it back to the main operations center via Ethernet radios. All the PLCs used in the
CMWD water and recycled water system are OPTO 22 SNAP PACs. For sites requiring more I/Os, multiple
OPTO 22 PLCs are linked together using an ethernet connection.
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 7 of 12
SECTION 3: INSTRUCTIONS TO PROPOSERS
RFP Schedule
The anticipated RFP schedule is provided in the following table:
ACTIVITY SCHEDULE
RFP Issued July 18, 2018
Pre-Proposal Meeting August 2, 2018, 1:00PM PST
Deadline for questions August 10, 2018, 5:00 PM PST
Final Q&A and/or addendum issued August 16, 2018
Proposals due August 23, 2018 2:00 PM PST
Proposers Notified for Second Round Week of September 10, 2018
Second Round Evaluation September 17, 2018 through October 5, 2018
Selection Committee recommends Manufacturer * October 2018
Negotiations completed* October and November 2018
City Council/CMWD Board consideration and
authorization of agreement * Early 2019
*Anticipated dates
Pre-Proposal Meeting
A non-mandatory pre-proposal meeting will be held at the date and time specified in the RFP schedule at
5950 El Camino Real, Carlsbad, CA 92008.
Inquiries
Questions related to the RFP must be submitted via email only by the deadline on the schedule to:
Graham Jordan, Contract Administrator
PWContractAdmin@carlsbadca.gov
RFP number must be referenced in the email title. Responses to any inquiries not including the RFP
number in the email title may be delayed. Questions will not be accepted in any other format. Responses
to the questions, that change any part of the RFP, will be provided via Addendum on PlanetBids.
Any questions submitted after the deadline identified will not be answered. Proposers are cautioned
regarding the non-binding nature of oral communications with City/CMWD staff, such as opinion,
comments, explanations, responses to informal questions, etc.
Addenda
City/CMWD reserves the right to revise the RFP prior to the date that the proposals are due. Addenda
must be acknowledged and included in the proposal.
Submittal Deadline
Until the deadline identified in the RFP Schedule, City/CMWD shall accept sealed proposals, clearly
marked as such, at the address below by mail, delivery service, or by deposit in the Bid Box located in the
first floor lobby.
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 8 of 12
Proposal for HMI
RFP19-480UTIL
Attn: Purchasing Officer
1635 Faraday Avenue
Carlsbad, CA 92008
Proposals and/or modifications received subsequent to the hour and date specified in the schedule will
not be considered and will be returned to the proposer.
Proposal Requirements
Submit 7 original copies and one electronic copy on a thumb drive of the proposal. Include a Table of
Contents at the front of the proposal, and submit the proposal in the exact order listed in the Response
Structure in Attachment A Evaluation Criteria. One hard copy of financial and one of cost proposal
information shall be submitted in sealed separate envelope marked confidential, with a separate thumb
drive also marked confidential and containing an electronic version of the confidential files.
This RFP contains instructions governing the proposals to be provided, requirements which must be met
for eligibility consideration and general evaluation criteria. Only proposals prepared in compliance with
the instructions and document formats specified by this RFP will be considered compliant. To ensure that
misrepresentation does not occur, please seek clarification of any requirements that are not understood.
Proposals must be prepared simply and effectively, providing a straightforward, concise description of
capabilities to satisfy the requirements of this RFP. Emphasis should be on completeness and clarity of content
with sufficient detail to allow for accurate evaluation and comparative analysis.
The contents of the proposal of the successful proposal will be incorporated into the contractual
obligations when a contract is awarded.
Evaluation Criteria
In accordance with the Carlsbad Municipal Code, a best value evaluation will be conducted to select the
manufacturer.
For the first round of evaluation, each proposal will be evaluated using the evaluation criteria established
in Attachment A. Each proposal will be ranked by a selection committee to create a shortlist of the top
two to three manufacturers, who will be invited in for a second round of evaluation.
For the second round, the top two to three manufacturers will be invited to return for additional
evaluation. Detailed evaluation criteria for the second round will be provided to the shortlist at the time
of notification and will include a detailed evaluation of the references provided, a customized
demonstration at a City/CMWD location in Carlsbad, as well as a site visit to a reference near Carlsbad.
The anticipated timeframe for the second round of evaluation is provided in the RFP schedule. The
Selection Committee will participate in the second evaluation round and further evaluate the
manufacturers. The scoring criteria for the second round will be cumulative to the points from the first
round.
Costs shall be scored independently from the other evaluation criteria to ensure qualifications review
remains unbiased from the cost proposal.
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 9 of 12
Negotiations
After discussion and ranking by the Selection Committee, the recommended manufacturer will be asked
to enter into negotiations for the master software and service agreement to refine scope and establish
fees. Multiple meetings are anticipated through this process. The final agreement will be executed directly
with the manufacturer, or provisions must be provided by the manufacturer to guarantee the agreement
for its full term, regardless of a change in the manufacturer’s authorized representative.
The selected manufacturer will be expected to sign an agreement with the City/CMWD. In the event that
an agreement cannot be reached with the highest-ranking vendor, City/CMWD will terminate
negotiations and enter into negotiations with the next highest-ranking vendor.
Award of Master Software and Service Agreement
Upon successful negotiations with the preferred manufacturer, the Selection Committee will recommend
the manufacturer to the City Council/Board of Directors to standardize the PLC/HMI equipment on that
manufacturer and authorize a master software and service agreement with the manufacturer.
City/CMWD and the manufacturer will then enter into the master software and service agreement as
outlined in Attachment C.
The following requirements will be incorporated into the master agreement:
• The costing provided in the proposal, including escalation rates, shall be the basis of the
negotiations. The quantities provided are not exact and are anticipated based on the owner’s
future needs, and have been provided in the RFP for the purposes of fair evaluation between
vendors.
• City/CMWD anticipate that a manufacturer’s authorized distributor may be working in close
coordination with the respective manufacturer on this RFP, but the final agreement will be
executed directly with the manufacturer, or provisions must be provided by the manufacturer
to guarantee the agreement for its full term, regardless of a change in the manufacturer’s
authorized distributor.
• The term of this agreement will be effective for a period of 10 years.
• The manufacturer shall provide an extended warranty to be no less than 2 years from date of
delivery to City/CMWD or City/CMWD vendors/contractors on all products procured on
behalf of the City/CMWD.
• The selected manufacturer will be required to honor pricing terms with City/CMWD staff and
vendors/contractors working on City/CMWD projects.
• This RFP, its general provisions (Attachment B), and the terms and conditions identified in the
sample Master Software and Service Agreement (Attachment C) shall be incorporated in any
agreement resulting from this solicitation. Any agreement shall be governed by and construed
in accordance with the Carlsbad Municipal Code, and the laws of San Diego County and the
State of California.
• A sample of the Master Software and Service agreement is provided as Attachment C for your
review. These terms and conditions will form the basis of key sections of the required
agreement between City/CMWD and the successful proposer. Any requests to use an
alternative contract/agreement form, such as a proprietary licensing or maintenance
agreement, must be presented at the time of the proposal.
• Any exceptions to city contract are to be stated in bidder’s proposal.
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 10 of 12
Legal and Contractual Guidelines
By virtue of submitting a proposal, interested parties are acknowledging:
• This RFP, its general provisions (Attachment B), and the terms and conditions identified in the
sample Master Software and Service Agreement (Attachment C) shall be incorporated in any
agreement resulting from this solicitation. Any agreement shall be governed by and construed
in accordance with the Carlsbad Municipal Code, and the laws of San Diego County and the
State of California.
• A sample of the Master Software and Service agreement is provided as Attachment C for your
review. These terms and conditions will form the basis of key sections of the required
agreement between City/CMWD and the successful proposer. Any requests to use an
alternative contract/agreement form, such as a proprietary licensing or maintenance
agreement, must be presented at the time of the proposal.
• Any exceptions to city contract are to be stated in bidder’s proposal.
• City/CMWD reserves the right to reconsider any proposal submitted at any stage of the
procurement. It also reserves the right to meet with select proposers at any time to gather
additional information. Furthermore, City/CMWD reserves the right to delete or add
functionality (i.e., modules and components) until the final contract signing.
• All third-party solutions proposed as part of this package are subject to the same guidelines
of this RFP, unless otherwise stated.
• City/CMWD reserves the right to reject any or all proposals and to waive technicalities and
informalities when such waiver is determined by City/CMWD to be in their best interest.
• This request does not commit City/CMWD to retain any vendors, to pay costs incurred in the
preparation of proposals, or to proceed with the project. Please note that City/CMWD
reserves the right to take any or no action based on responses to this request for proposal,
including the acceptance or rejection of proposals and the inclusion and deletion of any
combination of the work items for the project. City/CMWD reserves the right to reject any or
all proposals and to negotiate with any qualified applicant.
• City/CMWD reserves the right to retain all proposals submitted and to use any ideas in a
proposal regardless of whether that proposal is selected. By submitting a proposal, the firm
is providing a guarantee to City/CMWD that, if chosen, they will be able to provide the
proposed services during the period of time discussed in this Request for Proposal (RFP).
There is no expressed or implied obligation for City/CMWD to reimburse responding firms for
any expenses incurred in preparing proposals in response to this request.
• Proposals (including accompanying materials) will become the property of City/CMWD.
Proposals will be held in confidence to the extent permitted by law. After award of a contract
or after rejection of all proposals, the proposals will be public records subject to disclosure
under the California Public Records Act (Government Code Section 6250 et seq.)
• Any restrictions on the use of data contained within a proposal must be clearly stated in the
proposal itself. Proprietary information submitted in response to this RFP should be provided
in a separate envelope marked “Confidential” by the proposer and then will be handled in
accordance with applicable City Procurement Regulations and the California Public Records
Act. If you have proprietary information, products or services, please identify them as such in
your submittal.
• City/CMWD reserves the right to request additional information from proposers prior to final
selection and to consider information about a proposer other than that submitted in the
proposal.
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 11 of 12
• Failure to comply with the requirements of the RFP may result in disqualification.
• City/CMWD reserves the right to request information or clarification on any on-going
litigation or pending litigation.
• Regarding intellectual property and work for hire, selected vendor/contractor understands
and agrees that any and all materials and deliverables that are subject to independent
copyright protection that are developed in connection with the performance of any resulting
contract (Works) shall constitute a work for hire as that term is defined in the Copyright Act
of 1976 (Act), as amended. As a result, all right, title and interest in and to all such Works shall
belong exclusively to the city, including without limitation all copyrights and other intellectual
property rights therein. If for any reason a Work is not deemed to be a work for hire,
Vendors/Contractors shall be required to grant, transfer, and assign, free of charge,
exclusively to the city, all title, rights and interest in and to said Work, including all copyrights
and other intellectual property rights. The vendor/contractor will further agree to execute
and deliver to the city a confirmatory grant and assignment of all rights in and to Works and
to execute any other proper document the city deems necessary to ensure the complete and
effective transfer of all rights in Works to the city. In the event that vendor/contractor utilizes
a sub-contractor(s) for any portion of the Work that is in whole or in part of the specified
deliverable(s) to the City/CMWD, vendors/contractors shall include a statement in the
vendor/contractor-subcontractor agreement (Subcontractor Agreement) that identifies that
the deliverable/work product to the city is a work-for hire as defined in the Act and that all
intellectual property rights in the deliverable/work product, whether arising in copyright,
trademark, service mark or other belongs to and shall vest in the city. Further, the
Subcontractor Agreement shall require that the subcontractor grants, transfers, and assigns,
free of charge, exclusively to the city, all titles, rights and interests in and to said
deliverable/work, including all copyrights and other intellectual property rights.
• Regarding ownership of independent works, in accordance with the preceding paragraph,
Works developed for the City/CMWD in connection with any resulting contract are the
exclusive property of the City/CMWD. Vendor/contractor agrees to deliver all Works to the
city/CMWD upon completion of the order. Works include but are not limited to editorial
drafts, original copy, photographs, proofs, corrected proofs, camera-ready boards and similar
editorial materials, designs, mock-ups, layouts, arrangements, “look and feel,” and all
negatives, flats, engravings, photostats, drawings and other production materials and
content. For IT procurements for the development of original software for a specific
city/CMWD application or purpose, Works include but are not limited to executable code,
source code, fixes, patches, updates, upgrades, documentation embedded or otherwise,
original copy, and other production materials. Vendor/contractor shall be responsible for
delivering all Works to the city no later than fifteen (15) working days from the date of any
final contract deliverables. In the event the vendor/contractor fails to return all such materials
by this deadline and the city desires to use Works again, vendor/contractor shall provide the
city/CMWD with equivalent materials, at its own expense, or reimburse the city/CMWD, in
full, for the cost of developing equivalent materials.
• Regarding IP warranty and indemnification, the vendor/contractor represents and warrants
that any materials or deliverables, including all Works, provided under any resulting contract
are either original, not encumbered and do not infringe upon the copyright, trademark,
patent or other intellectual property rights of any third party, or are in the public domain. If
deliverables, materials or Works provided hereunder become the subject of a claim, suit or
allegation of copyright, trademark or patent infringement, city/CMWD shall have the right, in
its sole discretion, to require vendor/contractor to produce, at vendor/contractor’s own
City of Carlsbad/Carlsbad Municipal Water District
RFP for HMI
Page 12 of 12
expense, new non-infringing materials, deliverables or Works as a means of remedying any
claim of infringement in addition to any other remedy available to the city under law or equity.
Vendor/contractor further shall agree to indemnify and hold harmless the city/CMWD, its
officers, employees and agents from and against any and all claims, actions, costs, judgments
or damages of any type alleging or threatening that any materials, deliverables, supplies,
equipment, services or Works provided under this contract infringe the copyright, trademark,
patent or other intellectual property or proprietary rights of any third party (third party claims
of infringement). If a third party claim of infringement is threatened or made before
vendor/contractor receives payment under any resulting contract, city shall be entitled, upon
written notice to vendor/contractor, to withhold some or all of such payment.
ATTACHMENT A: EVALUATION CRITERIA
[Remainder of this page intentionally left blank]
9665 Chesapeake Drive, Suite 201
San Diego, California 92123
HMI Software RFP
Selection Criteria
Prepared for
City of Carlsbad, California
July 2018
ii
Table of Contents
List of Figures ............................................................................................................................................... v
List of Tables ................................................................................................................................................ v
List of Abbreviations ................................................................................................................................... vi
Section 1: Introduction .............................................................................................................................1-1
1.1 Objectives and Project Overview .....................................................................................................1-1
1.2 Evaluation Structure ........................................................................................................................1-1
1.2.1 Evaluation Methodology ....................................................................................................1-2
1.2.2 Technical Specifications ....................................................................................................1-2
1.2.3 Fee Proposal Schedules ....................................................................................................1-2
1.2.4 Technical Requirements ....................................................................................................1-2
1.2.5 Technical Criteria ...............................................................................................................1-2
1.2.6 Industry Presence ..............................................................................................................1-2
1.2.7 Value Added ........................................................................................................................1-3
1.3 Response Structure .........................................................................................................................1-3
Section 2: Evaluation Methodology .........................................................................................................2-1
Section 3: Technical Specifications .........................................................................................................3-1
3.1 System Architecture .........................................................................................................................3-1
3.2 Costing Definition .............................................................................................................................3-1
3.2.1 Software Licensing .............................................................................................................3-2
3.2.2 Operations and Maintenance Training .............................................................................3-2
3.2.3 Software Maintenance and Technical Support ................................................................3-2
Section 4: Fee Proposal Schedules (Cost) ..............................................................................................4-1
Section 5: Technical Requirements .........................................................................................................5-1
5.1 Foundational HMI Requirements ....................................................................................................5-1
5.1.1 General SCADA HMI Software Requirements ...................................................................5-1
5.1.2 Conditional Control and Data Change Logic .....................................................................5-1
5.1.3 Defined Failure Events .......................................................................................................5-1
5.1.4 Development Environment Views .....................................................................................5-2
5.1.5 General-Purpose I/O Communications Server .................................................................5-2
5.1.6 HMI Application Control Logic ...........................................................................................5-2
5.1.7 HMI Application Logic Scripts ............................................................................................5-2
5.1.8 HMI Application Manager ..................................................................................................5-2
5.1.9 HMI Data Change, Event Logging, and Window Logic .....................................................5-3
5.1.10 HMI Development Software Requirements ......................................................................5-3
5.1.11 HMI Function Logic.............................................................................................................5-3
5.1.12 HMI Keyboard Control Logic ..............................................................................................5-3
HMI Software RFP Selection Criteria Table of Contents
iii
5.1.13 Import/Export Utility ...........................................................................................................5-3
5.1.14 Windows Service Support ..................................................................................................5-3
5.1.15 Basic Software Compatibility .............................................................................................5-4
5.1.16 Full-Function Operator Workstation (HMI) ........................................................................5-4
5.2 Alarming with Criticality Management Requirements ...................................................................5-5
5.2.1 Alarm Management and Notification ................................................................................5-5
5.2.2 Alarm Management Functions ..........................................................................................5-5
5.2.3 Alarm Summary/Alarm History Object ..............................................................................5-6
5.3 High-Performance HMI Requirements ............................................................................................5-7
5.3.1 Display Navigation ..............................................................................................................5-7
5.3.2 Graphical Objects ...............................................................................................................5-7
5.3.3 Graphics Display Development .........................................................................................5-8
5.3.4 Object and Code Reuse .....................................................................................................5-8
5.3.5 Object Animation ................................................................................................................5-8
5.3.6 Object Model ......................................................................................................................5-9
5.3.7 Real-Time Trend Viewing ...................................................................................................5-9
5.3.8 Runtime Data Viewer .........................................................................................................5-9
5.3.9 Template Derivation, Object Instantiation, and Inheritance ...........................................5-9
5.4 Redundancy Requirements .......................................................................................................... 5-10
5.4.1 Alarm Redundancy .......................................................................................................... 5-10
5.4.2 Application Log Files ....................................................................................................... 5-10
5.4.3 Application Redundancy/SCADA System Failover ........................................................ 5-10
5.4.4 Communications Redundancy ....................................................................................... 5-10
5.4.5 Remote Client Access Server Failover ........................................................................... 5-10
5.5 Historian and Data Access Requirements .................................................................................. 5-11
5.5.1 Data Compression ........................................................................................................... 5-11
5.5.2 Database Summary System ........................................................................................... 5-11
5.5.3 Disk Storage Management ............................................................................................. 5-11
5.5.4 Dynamic Configuration and Bumpless Data Initialization ............................................ 5-11
5.5.5 Event Action ..................................................................................................................... 5-11
5.5.6 Event Configuration ......................................................................................................... 5-12
5.5.7 Event System Configuration ........................................................................................... 5-12
5.5.8 Historical Data Acquisition and Retrieval ...................................................................... 5-12
5.5.9 Historical Data Collection (Historian) ............................................................................. 5-12
5.5.10 Historical Data Collector Interface to Other Relational Databases .............................. 5-13
5.5.11 Historical Data Collector Redundancy ........................................................................... 5-13
5.5.12 Historical Data Point Configuration ................................................................................ 5-13
5.5.13 Historical Trend Viewing ................................................................................................. 5-13
5.5.14 HTML Reporting Client Tool ............................................................................................ 5-14
5.5.15 Manual Data, Out-of-Sequence Data, and Superseded Data ...................................... 5-14
5.6 Enterprise Systems Connectivity Requirements ......................................................................... 5-14
HMI Software RFP Selection Criteria Table of Contents
iv
5.6.1 Microsoft Excel Reporting Tool ....................................................................................... 5-14
5.6.2 Microsoft Word Reporting Tools ..................................................................................... 5-15
5.6.3 Standardized Database Tables ...................................................................................... 5-15
5.7 Security Requirements ................................................................................................................. 5-15
5.7.1 Audit Trail ......................................................................................................................... 5-15
5.7.2 Logging Operator Actions ................................................................................................ 5-15
5.7.3 Multi-User Development Environment ........................................................................... 5-16
5.7.4 Operator Security ............................................................................................................ 5-16
5.7.5 Runtime and Development Security .............................................................................. 5-16
5.7.6 View-only Graphics Display Workstation ........................................................................ 5-16
5.7.7 Multi-factor Authentication ............................................................................................. 5-17
5.8 Future Development Requirements ............................................................................................ 5-17
5.8.1 Platform-Independent Scripting Tools ........................................................................... 5-17
5.8.2 Communications Architecture ........................................................................................ 5-17
5.9 Optimization Capabilities Requirements ..................................................................................... 5-18
5.9.1 Process Data Analysis Workstation ................................................................................ 5-18
5.9.2 Real-Time and Historical Trend Analysis Tool ................................................................ 5-18
5.10 Future Stability and Support Requirements ................................................................................ 5-18
5.10.1 Warranty, Software Maintenance, and Technical Support ........................................... 5-18
5.10.2 Priority Telephone Support ............................................................................................. 5-19
5.10.3 SCADA System Software Installation, Licenses, and Support ...................................... 5-19
Section 6: Technical Criteria ....................................................................................................................6-1
6.1 Foundational HMI Criteria ...............................................................................................................6-1
6.2 Alarming with Criticality Management Criteria ...............................................................................6-1
6.3 High-Performance HMI Criteria .......................................................................................................6-2
6.4 Redundancy Criteria ........................................................................................................................6-2
6.5 Historian and Data Access Criteria .................................................................................................6-2
6.6 Enterprise Systems Connectivity Criteria .......................................................................................6-2
6.7 Security Criteria ................................................................................................................................6-3
6.8 Future Development Criteria ...........................................................................................................6-3
6.9 Optimization Capabilities Criteria ...................................................................................................6-4
6.10 Future Organizational Stability and Support Criteria .....................................................................6-4
Section 7: Industry Presence ...................................................................................................................7-1
Section 8: Value Added Consideration ....................................................................................................8-1
Section 9: Evaluation Criteria – Round 2 ................................................................................................9-1
9.1 Customized Demonstration and Interview .....................................................................................9-1
9.2 Industry References .........................................................................................................................9-1
9.3 Site Visit to Local Reference ...........................................................................................................9-1
Appendix A: Cover Sheet ........................................................................................................................... A-1
Appendix B: Technical Requirement Response Tables ......................................................................... B-1
HMI Software RFP Selection Criteria Table of Contents
v
Appendix C: Technical Criteria Scoring Tables ........................................................................................C-1
List of Figures
Figure 3-1. Conceptual system block diagram ........................................................................................3-1
List of Tables
Table 2-1. Evaluation Criteria ...................................................................................................................2-1
Table 4-1. HMI Software License Costs ...................................................................................................4-1
Table 4-2. Operations and Maintenance Training Costs ........................................................................4-2
Table 4-3. Software Maintenance and Technical Support Costs ...........................................................4-2
Table 5-1. Basic Software Compatibility Requirements .........................................................................5-4
Table 6-1. External Business Applications ..............................................................................................6-3
Table B-1. Foundational Requirements Response ................................................................................ B-2
Table B-2. Alarming with Criticality Management Requirements Response ........................................ B-3
Table B-3. High-Performance HMI Requirements Response ................................................................ B-3
Table B-4. Redundancy Requirements Response ................................................................................. B-3
Table B-5. Historian and Data Access Requirements Response .......................................................... B-4
Table B-6. Enterprise Systems Connectivity Requirements Response ................................................ B-4
Table B-7. Security Requirements Response ......................................................................................... B-4
Table B-8. Future Development Requirements Response .................................................................... B-5
Table B-9. Optimization Capabilities Requirements Response ............................................................ B-5
Table B-10. Future Stability and Support Requirements Response ..................................................... B-5
Table C-1. Foundational Criteria Scoring .................................................................................................C-2
Table C-2. Alarming with Criticality Management Criteria Scoring .........................................................C-2
Table C-3. High-Performance HMI Criteria Scoring .................................................................................C-3
Table BC-4. Redundancy Criteria Scoring ................................................................................................C-3
Table C-5. Historian and Data Access Criteria Scoring ...........................................................................C-3
Table C-6. Enterprise Systems Connectivity Criteria Scoring .................................................................C-3
Table C-7. Security Criteria Scoring .........................................................................................................C-4
Table C-8. Future Development Criteria Scoring .....................................................................................C-4
Table C-9. Optimization Capabilities Criteria Scoring .............................................................................C-4
Table C-10. Future Stability and Support Criteria Scoring......................................................................C-5
HMI Software RFP Selection Criteria Table of Contents
vi
List of Abbreviations
AMI automated meter infrastructure
BMP bitmap
CD compact disc
City City of Carlsbad
CMMS computerized maintenance management
system
CMWD Carlsbad Municipal Water District
CPU central processing unit
CSV comma-separated values
DDE Dynamic Data Exchange
DI discrete input
DMZ demilitarized zone
DNP3 Distributed Network Protocol
DOCX Microsoft Word (file extension)
DXF drawing interchange format (file extension)
GIS geographic information system
GUI graphical user interface
HMI human-machine interface
HTML Hypertext Markup Language
ID identifier
I/O inputs and outputs
JPEG Joint Photographic Experts Group
LAN local area network
LIMS laboratory information management
system
OCX Object Linking and Embedding Control
OLE Object Linking and Embedding
OPC Open Platform Communications
OS operating system
Owner The City of Carlsbad and Carlsbad
Municipal Water District
PC personal computer
PDF Portable Document Format
PID proportional-integral-derivative
PIN personal identification number
PLC programmable logic controller
PNG portable network graphic
RFP Request for Proposals
ROC receiver operating characteristic
RTU remote terminal unit
SCADA supervisory control and data acquisition
SMTP Simple Mail Transfer Protocol
SQL Structured Query Language
TCP/IP Transmission Control Protocol/Industrial
Protocol
USB universal serial bus
WAN wide area network
XLSX Microsoft Excel (file extension)
XML eXtensible Markup Language
1-1
Section 1: Introduction
This section presents objectives and project overview, the RFP evaluation structure, and the RFP
response structure.
1.1 Objectives and Project Overview
The City of Carlsbad (City) and the Carlsbad Municipal Water District’s (CMWD) (collectively,
City/CMWD or Owner) desire to select an HMI software package to standardize the Owner’s HMI
system and enter into a master software and service agreement. The overall HMI system will have a
centralized HMI server that can be accessed through decentralized control rooms for the
water/recycled water and wastewater groups. The future system will include primary server and
control rooms in a separate physical building from the secondary server room and access locations.
System data will be communicated from remote sites to the server locations via a variety of
communications mediums including radio, cellular, leased line, and fiber.
The Owner has identified a list of key needs that will be addressed with the new HMI software. The
evaluation will be organized according to these key needs:
1. Foundational HMI: the software will need to provide the foundational functionality assumed of all
HMI software.
2. Alarming with Criticality Management: The software will need to provide an alarming system with
criticality management for process alarms.
3. High Performance HMI: The software will need to support the development of a “High
Performance HMI” user interface using standardized manufacturer templates.
4. Redundancy: The software will need to provide capabilities for redundancy and automatic fail-
over features.
5. Historian and Data Access: Data collected by the HMI system will need to be stored in a
historical database that will allow the owner to easily access past data and trends without the
need for additional scripting.
6. Enterprise Systems Connectivity: The proposed HMI software will need to provide the future
capability to share data with the owner’s business systems including systems for the CMMS,
LIMS, GIS, AMI, Billing, Finance, and Hydraulic Model without the need for customized
programming.
7. Security: The HMI software will need to provide security to protect the system from unauthorized
access and use.
8. Future Development: The HMI software will need to provide features that will allow for future
development and expansion of the HMI system.
9. Optimization Capabilities: The HMI software will need to provide features that will enable the
owner to optimize the control of the water and wastewater systems based on system data.
10. Future Stability and Support: The HMI software manufacturer will need to provide assurance of
future stability and ongoing support of the proposed software.
1.2 Evaluation Structure
These instructions were developed to aid in response development and guide proposers through the
requirements of this RFP. Additional proposal requirements, such as number of copies and RFP
schedule, are provided in Instructions to Bidders in the Request for Proposals. This section is
intended to provide a brief overview of each section for clarity and is not intended to provide
HMI Software RFP Selection Criteria Section 2
1-2
additional requirements or prompt additional response. The details of each evaluation portion of the
RFP are provided in subsequent sections:
1.2.1 Evaluation Methodology
The evaluation methodology section provides details on how the proposer’s responses will be scored
and how different portions of the response will be weighted relative to each other. Proposers should
ensure proposals address each of these scoring categories. Each scoring category will have a
corresponding section in this document to provide an explanation of what should be included in the
response.
1.2.2 Technical Specifications
The technical specifications section provides a general overview of the RFP objective to allow the
proposer to understand what the owner wants to achieve with this RFP. A basic network topology is
provided to help proposers understand the system layout and is not intended to provide system
details.
The system and costing definitions provide the proposer with the necessary information to develop
cost information for the fee proposal schedules. The system and costing definitions are intended to
be a high-level project outline that shall be used to determine quantities and components that will be
required to meet the owner’s needs. Proposers are responsible for determining how to best provide
an overall product that will meet these definitions as well as the requirements and criteria in the
technical requirements section and the technical criteria section.
1.2.3 Fee Proposal Schedules
The fee proposal schedules section will provide details on how proposers should provide costs for
evaluation. Cost tables are provided for proposers to include line items for each component needed
to achieve the system and costing definitions from the technical specifications section while
complying with the technical requirements and technical criteria.
1.2.4 Technical Requirements
The technical requirements section details each of the requirements the proposed product must
meet to be considered for selection. Tables provided in Appendix B shall be used to respond to this
section. Instructions are provided in Appendix B of this document.
1.2.5 Technical Criteria
The technical criteria section consists of a series of questions and prompts the proposer must
provide responses to. The questions are intended to provide a means to evaluate how each proposer
will be able to meet the needs of the owner. Format for response scoring is included in Appendix C of
this document.
1.2.6 Industry Presence
Each proposer must provide information about the proposed product installed base in the public
water/wastewater industry. Proposers must also provide vendors and contractors/integrators
capable of supporting the product for evaluation. This section will be an open response.
HMI Software RFP Selection Criteria Section 2
1-3
1.2.7 Value Added
The value added section will give proposers an opportunity to respond with any additional value their
product may contribute outside of the cost, technical requirements, and technical criteria. This
section will be an open response for the proposer to explain the added value they can provide.
1.3 Response Structure
All proposals are to be organized into the following sections and sequence to provide a structured
format so that reviewers can systematically evaluate responses. Each copy of the response package
must include all the sections in the order indicated, and shall be clearly labeled. Attachments should
be clearly referenced and identified to facilitate the review process. Additional proposal
requirements, such as number of copies and RFP schedule, are provided in Instructions to Bidders in
the Request for Proposals
Each response shall include the following sections in the order shown:
1. Table of Contents
2. Cover sheet (Appendix A)
3. Acknowledgement of addenda
4. Proposed network block diagram
5. Technical requirements response table (Appendix B)
6. Technical criteria written responses
7. Supporting documents for technical criteria
a. Screen shot from a lift station project
b. Screen shot from a pump station project
c. Third-party venerability report
d. List of training courses and schedule for 2018
8. Value added response
9. Industry presence response
10. Fee Proposal in a separate envelop marked confidential
11. Financial report in a separate envelope marked confidential
2-1
Section 2: Evaluation Methodology
The Owner’s choice of control system software will be made by a team of individuals evaluating the
proposals, herein referred to as the City’s Selection Committee. The criteria that will be used for
evaluating the proposals are described in detail below. The HMI evaluation process will be split into
two rounds. The first round is the response to this RFP and if selected, the second round will include
providing a demonstration of the functionality based on specific requirements and visits to reference
sites among other things. The owner anticipates inviting the top two or three vendors in for the
second round. If invited to participate in the second round, scores from the first and second round
will be cumulative.
The relative importance of the evaluation criteria that will be applied during the proposal review
process is shown in Table 2-1 below. Each proposal will be evaluated on the following point-weighted
scoring system. Each criterion will be rated on a scale between zero and its maximum points, where
zero indicates that no information was given in the proposal, and one is the lowest score based on
provided information, up to the maximum points identified for that criterion. All proposals will be
evaluated based on the criteria found below.
Table 2-1. Evaluation Criteria
Evaluation Criterion
Maximum
Points Score Comments
Fee proposal schedule (cost) 100
Technical requirements 50
Technical criteria
Foundational HMI criteria 30
Alarming with criticality management criteria 10
High performance HMI criteria 10
Redundancy criteria 10
Historian and data access criteria 10
Enterprise system connectivity criteria 10
Security criteria 10
Future development criteria 10
Optimization capabilities criteria 10
Future stability and support criteria 20
Industry presence 40
Value added 30
Maximum total points: round 1 350
Customized demonstration and Q&A 70
Industry references 50
Site visit to reference 30
Maximum total points: round 2 150
Total: Rounds 1 and 2, cumulative 500
3-1
Section 3: Technical Specifications
This section presents the required technical specifications for the project, including system
architecture and costing definitions. The system and costing definitions provide the proposer with
the necessary information to develop cost information for the fee proposal schedules. The system
and costing definitions are intended to be a high-level project outline that shall be used to determine
quantities and components that will be required to meet the owner’s needs. Proposers are
responsible for determining how to best provide an overall product that will meet these definitions as
well as the requirements and criteria in the technical requirements section and the technical criteria
section.
3.1 System Architecture
Figure 3-1 presents the conceptual architecture of the future supervisory control and data
acquisition (SCADA) system, including a primary location with a backup in a separate physical
location. The vendor shall include in the proposal an equivalent document specific to its SCADA
system and any recommendations for specific software, communication architecture, and specifics
on the operating system (OS). For the purposes of this document, a thick client is defined as a fully
functional workstation capable of workload independent of the server. The thin client is defined as a
workstation dependent on the server for the bulk of its processing workload.
Figure 3-1. Conceptual system block diagram
3.2 Costing Definition
The proposer shall demonstrate the manufacturer of the software is able to provide the owner an
HMI software package that meets the objectives of the system architecture above, demonstrate
technical criteria as described by the proposer in response to the technical criteria section, and meet
the technical requirements described in the technical requirements section.
HMI Software RFP Selection Criteria Section 3
3-2
3.2.1 Software Licensing
The proposed HMI software package shall meet the needs of a system with the following minimum
requirements:
1. One SCADA system server pair, consisting of one duty server and one redundant backup server
2. 5,000 device tags
3. 100 main displays (not including pop-ups)
4. 1,000 historian tags
5. 50 view-only licenses
6. 25 concurrent thin client HMI nodes with data analysis tools
7. Two concurrent thick client HMI nodes with data analysis tools
8. One alarm notification server pair, consisting of one duty server and one redundant backup
server with cellular modems and unlimited alarms
9. Concurrent development capability with licensing to support one developer
3.2.2 Operations and Maintenance Training
The proposer shall provide costs for training staff for the HMI software package equivalent to the
following:
1. Operations training for four separate classes with six attendees for each class at the owner’s
facility.
2. Programming training for four separate classes with six attendees for each class at the owner’s
facility.
3. Server system maintenance training for two separate classes with four attendees for each class
at the owner’s facility.
3.2.3 Software Maintenance and Technical Support
The proposer shall provide software maintenance and technical support for the HMI software
package equivalent to the following:
1. Set up a long-term contract, minimum ten years, with the owner for software maintenance. When
listing annual costs, provide the escalation used.
2. Set up a long-term contract, minimum ten years, with the owner to provide technical support as
described in Section 5.10. When listing annual costs, provide the escalation used.
4-1
Section 4: Fee Proposal Schedules (Cost)
The proposer shall provide a fee schedule for the cost of the human-machine interface (HMI)
software license and support in a separate sealed envelope by the date shown under the selection
schedule on the Notice Inviting Bidders. The separate sealed envelope with the fee proposal shall
include one hard copy and one copy in digital format (Portable Document Format [PDF] or Word
[DOCX] format) on a universal serial bus (USB).
The costs will be evaluated by the Contract Administrator, independantly from the qualifications
review by the Committee. The calculation will be conducted over a 10-year term. The quantities are
not exact and are anticipated based on the owner’s future needs, and have been provided here for
the purposes of fair evaluation between vendors. For the selected manufacturer, these costs shall
be the basis of future negotiations. All fee submittals will be subject to negotiation during final
contract negotiations.
The low cost shall receive maximum points; any costs within 5 percent of low cost will receive 95
percent of the points; if within 10 percent of low cost, receive 90 percent of the points; if within 20
percent of low cost, receive 80 percent of the points; if within 30 percent of low cost, receive 70
percent of the points; and continuing by 10 percentage ranges.
Each proposer shall complete the fee schedules in this section, a detailed list for the system, and its
associated unit costs including all software, licenses, drivers, options, etc. to meet the requirements
defined in the technical specifications.
Note that the proposed costs refer to the cost to the City for each item listed.
Hardware shall not be included in pricing from the HMI software vendors. The proposer shall take
into consideration the labor, material, rental, and any associated cost to perform or provide any unit
of work.
The proposer shall use the following tables (4-1 through 4-4) to provide a fee schedule for evaluation
that will represent the total cost to meet the requirements defined in the technical specifications.
Table 4-1. HMI Software License Costs
Component Quantity Unit
(ls, each, etc.) Unit Cost Total Component
Cost
SCADA system server pair $ - $ -
Device tags $ - $ -
Displays $ - $ -
Historian tags $ - $ -
Thin client HMI $ - $ -
Thick client HMI $ - $ -
Alarm management system $ -
Concurrent development $ - $ -
Subtotal $ -
HMI Software RFP Selection Criteria Section 4
4-2
Table 4-2. Operations and Maintenance Training Costs
Component Quantity Component Cost Total Component Cost
Operation training $ - $ -
Programming training $ - $ -
Server system maintenance training $ - $ -
Subtotal $ -
Table 4-3. Software Maintenance and Technical Support Costs
Component Escalation Rate Quantity Component Cost Total Component Cost
Year 1 Software Maintenance LS $ - $ -
Year 2 Software Maintenance LS $ - $ -
Year 3 Software Maintenance LS $ - $ -
Year 4 Software Maintenance LS $ - $ -
Year 5 Software Maintenance LS $ - $ -
Year 6 Software Maintenance LS $ - $ -
Year 7 Software Maintenance LS $ - $ -
Year 8 Software Maintenance LS $ - $ -
Year 9 Software Maintenance LS $ - $ -
Year 10 Software Maintenance LS $ - $ -
Year 1 Technical Support LS $ - $ -
Year 2 Technical Support LS $ - $ -
Year 3 Technical Support LS $ - $ -
Year 4 Technical Support LS $ - $ -
Year 5 Technical Support LS $ - $ -
Year 6 Technical Support LS $ - $ -
Year 7 Technical Support LS $ - $ -
Year 8 Technical Support LS $ - $ -
Year 9 Technical Support LS $ - $ -
Year 10 Technical Support LS $ - $ -
Subtotal $ -
HMI Software RFP Selection Criteria Section 4
4-3
Table 4-4. Costs for Term of Agreement
Component Basis Cost
HMI Software License Costs Subtotal from Table 4-1 $ -
Operations and Maintenance Training Costs Subtotal from Table 4-2 $ -
Software Maintenance, and Technical Support Subtotal from Table 4-3 $ -
Total Cost $ -
5-1
Section 5: Technical Requirements
The technical requirements provided in this section shall be used by the proposer to respond to the
tables in Appendix B: Technical Requirement Response Tables.
5.1 Foundational HMI Requirements
This section presents foundational HMI requirements for the project.
5.1.1 General SCADA HMI Software Requirements
The SCADA software shall consist of an HMI system with support for supervisory process control and
real-time data acquisition. The HMI system shall also support alarm and event management,
historical data collection, report generation, local or remote telemetry communications to
programmable logic controllers (PLCs) and/or remote terminal units (RTUs), Internet/Intranet access,
and change control. The software shall be easy to use with an object-oriented graphics development
environment and shall have an open architecture. The end-user should only have to customize
project specific details that may not be standard in the water/wastewater industry. The software
shall be compatible with Windows Desktop and multiple mobile Os’s such as tablets and smart
phones. The system shall have built-in flexibility to permit easy configuration in accordance with
specific end-user requirements, as well as quick and easy modification by end users in the field.
The software shall consist of a suite of off-the-shelf modular components from a single software
manufacturer that are tightly integrated to perform all SCADA system functions. The suite shall
contain an HMI for process visualization, real-time relational database for historical data collection,
client tools for trending and reporting within the HMI and as standalone, and communication drivers
for PLC/RTUs. The suite shall be scalable so that a small standalone application can easily be
expanded into a large distributed control network with either single or redundant database servers,
or redundant communication servers providing information to multiple workstation clients. If the
manufacturer uses any third-party software as an integral part of the foundational system, define the
relationship with the provider of the third-party software.
5.1.2 Conditional Control and Data Change Logic
The system shall support configuration of objects that perform application control based upon a
user-definable state of an object and attribute, or the result of an expression involving multiple
object tag names/hierarchical names. This includes discrete object tag names/hierarchical names,
on/off state alarm states (e.g., lo, lo-lo, hi, hi-hi), or equivalence to a specific value. It shall be
possible to define condition logic scripts that execute once when the condition expression becomes
true, once when the condition expression becomes false, while the condition is true, or while the
condition is false at a user-definable rate of 500 milliseconds minimum, or when the value changes.
5.1.3 Defined Failure Events
The SCADA system shall detect the following events within the SCADA system and network objects:
• Communications failure to a single RTU/PLC
• Communications failure to multiple RTUs/PLCs
• Communications failure to communications server
• Application logic failure
• Alarm printer failure (e.g., offline, out of paper)
• Alarm manager failure
HMI Software RFP Selection Criteria Section 5
5-2
• Historical data collector rate of collection deviation
• Low disk space on any historical data collector on the network
The SCADA system shall detect any or all the possible failures and allow client data recovery without
user intervention.
5.1.4 Development Environment Views
The development environment shall have the ability to view and configure the application from a
plant model perspective and an application object deployment perspective.
5.1.5 General-Purpose I/O Communications Server
General-purpose communication between I/O servers and devices shall be available for support
using Distributed Network Protocol (DNP3), Transmission Control Protocol/Industrial Protocol
(TCP/IP), and Modbus TCP Ethernet. There shall be support for several hundred various devices
using Open Platform Communications (OPC) Protocol. An I/O server toolkit shall be available for third
parties to develop custom I/O servers.
5.1.6 HMI Application Control Logic
The SCADA system software shall include a scripting language that allows execution of commands
and mathematical and logical operations based on specified system conditions or user actions. The
scripting shall be easy to program using English-like statements and shall not require any knowledge
of any other programming logic. Users shall be able to edit or modify the logic scripts while the
system is monitoring the process. Furthermore, it shall not be necessary to invoke any other
application to compile the changes. The scripting language shall include selection boxes and pull-
down menus to permit statements to be created without having to type tag names or specific
commands. Buttons shall be available for easy selection of basic commands and operations such as
if, then, else, else if, and, or, not, add, subtract, multiply, divide, equal to, not equal to, greater than,
and less than. Additionally, a full library of more complex math and system script functions shall be
available. A validate button shall be included to ensure proper syntax and provide indication of errors
to eliminate any problems at runtime. Online help for each script function shall include actual
working examples that can be copied and pasted into the script editor.
5.1.7 HMI Application Logic Scripts
The system shall have the ability to execute user-defined logic scripts. Logic scripts shall be created
in a statement-based programming environment. No compilers or linkers shall be required.
The system logic shall be able to automatically perform functions such as increase/decrease set
points, totalize, and check the status of process set points to act.
The system logic shall be able to monitor the status of each tag name in the system and perform
specific functions based on the type and status of an alarm condition. Alarm type may be lo, lo-lo, hi,
hi-hi, deviation, or rate of change. Alarm status may be acknowledged or unacknowledged.
The system shall have the ability to perform application control turn on/off discrete points, show
windows, download procedure, control processes (i.e., recipes), etc. This application logic shall also
start and stop other application programs such as Excel, Word, and other OS-based applications.
5.1.8 HMI Application Manager
Each application shall include an application manager with a Windows Explorer-like browser to
simplify management of windows (i.e., displays), scripts, tag names, alarms, and application
HMI Software RFP Selection Criteria Section 5
5-3
documentation. A tag name cross-referencing index shall provide an efficient means of identifying
where all tag names, links, and objects are used throughout all windows in the application.
5.1.9 HMI Data Change, Event Logging, and Window Logic
The system shall have the ability to execute system logic when the value of a tag name changes. The
system shall have the ability to execute a Windows logic script upon a user-definable state of a tag
name, or the result of an expression.
Any configured integer, floating point, Boolean, or string tag may also be configured as an event. The
point shall be logged as an event any time its value changes (beyond a preset range).
Events shall be logged to a historical database. Items to be logged in addition to the event itself shall
include date and time of the event and event priority.
5.1.10 HMI Development Software Requirements
All development and configuration shall persist in one or more common file or database repositories
that provide a single point of configuration. Furthermore, there shall be a common naming
convention for objects and tag names that is enforced by the development tools.
5.1.11 HMI Function Logic
The system shall support creating logic blocks and saving the logic as a function. These function
scripts shall be able to run on a process thread independent of the HMI process. Function scripts
shall run on a separate process thread, and not impact the performance of the HMI operations.
Function scripts shall be able to be called from any of the logic types defined in earlier sections,
including a call from a function script to another function script.
5.1.12 HMI Keyboard Control Logic
The system shall have the ability to perform application control whenever a user presses a key on
the keyboard. This includes whenever the key is pressed or released, or while the key is held down at
a definable interval. The system will support any of the keys on a standard personal computer (PC)-
compatible keyboard.
5.1.13 Import/Export Utility
The development environment shall include a utility to support, import, or export into a human-
readable file format such as comma-separated values (CSV) file format or Excel (XLSX) for editing in
a spreadsheet application such as Excel. It shall be possible to instantiate templates and application
objects from the CSV load by populating only the appropriate columns in the spreadsheet that are
required for instantiation/configuration of the desired objects.
5.1.14 Windows Service Support
The operator interface workstation shall be able to be run as a Windows service as opposed to an
application. This provides Windows service capabilities for key HMI components, such as historical
logging alarms and I/O communications. The service capabilities allow continuous operation through
OS logons and logoffs, such as operator shift changes.
All SCADA software shall support running as a Windows service so that, following a power failure or
when the machine is turned on, an automatic startup to the runtime mode will occur. This function
ensures unmanned station startup without compromising OS security.
HMI Software RFP Selection Criteria Section 5
5-4
5.1.15 Basic Software Compatibility
Table 5-1 lists basic software compatibility requirements for the HMI software. For items in the list
below that require a response other than Yes/No, provide responses on a separate sheet (one sheet,
single sided) titled “Basic Software Compatibility” and provide responses in the same order.
Table 5-1. Basic Software Compatibility Requirements
Software Requirement
Server OS Windows Server 2016 (redundant servers)
Workstation OS Windows® 10 Enterprise (64-bit)
Workstation Web browser Microsoft Explorer 11 or later, Google Chrome V.62 or later, and Firefox V. 56 or later
Historian OS Windows Server 2016 (redundant servers)
System security method Integrated with Windows® Security
Antivirus software compatible List supported software vendors
License method, updates, and terms Describe (include time period)
Server requirements Server class, hardware specifications, etc.
HMI system architecture Specify quantity, role of server, etc.
Online backup management Describe
Database compatibility Ability to automatically send all SCADA data or only select sets of SCADA data to a separate SQL database
Virtualization support Support running SCADA servers on a virtual machine
Local Windows account Support running all SCADA software as a standard Windows user account
(i.e., not an administrator account)
Server side account Run as service, not as logged-in user
Microsoft software updates Support the installation of monthly Microsoft updates to all SCADA computers and servers
5.1.16 Full-Function Operator Workstation (HMI)
SCADA system operators shall be able to execute all monitoring and supervisory control functions
from the full-function thick-client operator workstation. Typical operator commands include modifying
set points for control loops, alarm acknowledgment, set point adjustment auto/manual switching,
on/off control of field devices, and taking points or devices on/off scan. Operators shall be able to
access all SCADA tag name/hierarchical names or graphic displays from any workstation on the
network without knowing which historical data collector or server the point or display resides on. The
system software shall include an object-oriented color graphics display generator with full animation
capabilities to provide users with a realistic visualization of the system process. All graphical editing
operations shall be point-and-click—selecting icons from floating and docking toolbar pull-down
menus or keyboard commands. It shall be possible to perform a functional test of any graphic display
by switching to the runtime mode with a single mouse click. The graphics editor shall include a broad
library of complex objects and process symbols, such as meters, pushbuttons, sliders, gauges,
pumps, motors, tanks, valves, trends, alarms, and controller faceplates. All complex objects shall be
scalable to any size and may include animation links to provide dynamic response based on real-
time data or user action.
HMI Software RFP Selection Criteria Section 5
5-5
5.2 Alarming with Criticality Management Requirements
This section presents alarming with criticality management requirements for the project, including
alarm management and notification, alarm management functions, and alarm summary/alarm
history object.
5.2.1 Alarm Management and Notification
Alarms shall be detected and reported by an alarm manager service that shall support no less than
200 simultaneous alarm client displays. In the event of an alarm storm (i.e., hundreds or thousands
of alarms detected within 1 second) the alarm manager service shall report, and the client shall
display, up to 1,000 new alarms within 10 seconds of detection.
The system shall be able to alarm system resources (central processing unit [CPU] utilization memory
etc.).
Alarms shall be logged to a historical database. Alarm events to be recorded shall include alarm
instantiation, alarm return-of-normal, and alarm acknowledgment. Items to be logged in addition to
the alarm event shall include date and time of the alarm event, alarm group, alarm description,
alarm data type (e.g., real/integer/Boolean), alarm type (e.g., lo-lo, lo-hi, hi-hi, receiver operating
characteristic [ROC] deviation disc, etc.), operator name, and operator node of alarm
acknowledgement and alarm priority.
An alarm purge service shall be provided to automatically purge and optionally archive alarms that
are older than a user-defined period of days online.
Alarms may be printed to a locally connected or network printer. The alarms printed from a node may
be filtered to all alarms, unacknowledged alarms only, acknowledged alarms only, alarms from a
particular alarm group, group alarms from a particular priority, or alarms from multiple alarm
providers. Also, the owner would like to have the ability to filter alarms by dates and affected
PLC/RTU.
It shall notify of operations and maintenance personal using alarm dialing (text-to-speech and pre-
recorded messages), text, and email notification (either in software or third-party software to be
included in purchase price), based upon areas and priorities. It shall also be able to notify operations
based upon text-to-speech software with redundancy that matches the overall SCADA system
software.
5.2.2 Alarm Management Functions
Operators shall be able to view current and historical alarm information from a full-screen alarm
summary display, and/or on a small scrolling region and the bottom of any display (alarm banner).
The alarm information shall be displayed in chronological order with the most recent alarm at the
top. The information capable of being displayed for each alarm shall include the time and date
description, tag name, alarm state, alarm type (e.g., lo, lo-lo, hi, hi-hi, rate-of-change, etc.) value,
acknowledging operator, acknowledging node, priority-level alarm, or process area group name and
class.
HMI Software RFP Selection Criteria Section 5
5-6
It shall be possible for operators to filter the alarm display based on priority-level alarm groups or
process areas. In distributed network systems, alarms shall be viewed and acknowledged from any
workstation, and the information shall be distributed to all clients. The alarm summary will be able to
display the name of the operator and the node acknowledging the alarm.
It shall be possible to configure the system such that the operator is notified of an alarm no matter
which display the operator is currently viewing. The notification shall include the option of a pop-up
alarm display window, flashing process symbol such as a process vessel, alarm text message that is
available on each display, or dedicated alarm display window anywhere on the screen. A configurable
audible signal shall be provided.
The alarm summary display shall provide the built-in horizontal and vertical scroll bars to page
through alarms. The display of these scroll bars shall be user-configurable.
The alarm summary display shall allow for dynamic resizing of the column widths by simply selecting
a column line and dragging it to set the column width.
The alarm display shall support up to eight different combinations of colors based on the priority of
the alarm and whether it is acknowledged or unacknowledged. The colors shall be user-selectable
via configuration from a minimum of 256 colors.
The system shall provide a method of notifying users when a new alarm has occurred. The alarm
display object shall automatically scroll to a new alarm when the user has scrolled down the alarm
list from the top.
The alarm display shall retrieve alarm information by submitting an alarm query to the alarm server.
The alarm query shall allow specification of a priority range alarm, acknowledge state alarm group,
alarm history, or summary. Combinations of the parameters can be specified for the query to
produce selected results.
Operators shall be able to create new alarm queries at runtime and save the queries for reuse.
Operators shall be able to select and acknowledge alarms individually by group or remote site.
Operators shall also be able to acknowledge only those alarms visible in the display, only those
selected, only the most recent alarm, or all alarms in the system. The alarm display shall allow
alarms to be selected by clicking on them with the mouse at runtime.
Operators shall be able to suppress alarms on the local display. Suppressing alarms on one operator
interface shall not affect the display of alarms on another operator interface. Un-suppressing
previously suppressed alarms shall be via simple mouse click.
Operators shall be able to select an alarm from the alarm summary display, and the system shall
switch to the corresponding screen of the section of the control system where the alarm originated.
It shall be possible to inform operators of an alarm condition via an audible tone, pop-up display, or
any combination of animation types on the screen.
5.2.3 Alarm Summary/Alarm History Object
Alarms shall be displayed by configuring a user-defined alarm summary object that may be placed by
itself or along with other objects in a window. The object can be sized and then double-clicked to
launch a configuration dialog.
Default alarm object configurations shall be displayed with the option to change any configuration
parameter for runtime viewing.
HMI Software RFP Selection Criteria Section 5
5-7
The alarm configuration shall include parameters with check boxes to select and enable/disable how
the alarms appear at runtime.
Alarms shall be color-coded per the state and priority of the alarm, including an acknowledged alarm,
unacknowledged alarm, and alarm that has returned to normal—but is not yet acknowledged.
5.3 High-Performance HMI Requirements
This section presents high-performance HMI requirements for the project.
5.3.1 Display Navigation
Operators shall interface to all process and SCADA activities through easily recognized pull-down or
full-screen menus.
The system runtime software shall support operator access to multiple displays at one time,
including split screens where operators may view more than one process area at a time. In addition,
the system shall support unlimited use of pop-up displays for additional help or diagnostic
information.
The system runtime software shall support multiple monitors using commercially available multiple-
monitor graphics adapter cards.
Operators shall have access to context-sensitive online help or instructions from any display at any
time during operation of the system with a single keystroke or mouse click.
Operators shall be able to access displays via a pointing device and/or soft key menus with a choice
of function keys, cursor control keys, or any single key on the keyboard. Display navigation shall not
normally require the use of typing text commands into an alphanumeric keyboard. Supported
pointing devices shall include a mouse, touchscreen, light pen, or trackball.
Operators shall be able to easily identify which objects are selectable from any display by simply
dragging the pointing device over the object. Displaying a halo around the object shall provide
confirmation that an object can be selected. Typical objects include process device symbols (e.g.,
pump motors etc.), controller faceplates, buttons, switches, or sliders.
5.3.2 Graphical Objects
The graphics editor shall include a set of basic drawing tools to create simple or complex objects.
Selecting an icon on the drawing toolbar shall easily create simple objects, which include lines,
rectangles, polygons, ellipses, circles, and filled shapes or text. Any of these objects can be assigned
various attributes, such as line color, fill color, size, and orientation, and can be made static or
dynamic. Text objects shall be scalable and use true fonts in bold, italic, or underline. All objects
shall be scalable and moved in any direction one pixel at a time, or dragged with a mouse.
The graphics editor shall support standard object manipulation functions, such as cut, copy, paste,
and delete. Alignment tools shall be included to simplify proper object placement and arrangement.
Align commands shall be included to align objects based on justification to the left, right, center, top,
or bottom. Object commands shall also be included to space vertically and horizontally, move to
back, move to front, rotate, or group and ungroup.
The graphics editor shall include a broad library of complex objects and process symbols, such as
meters, pushbuttons, sliders, gauges, pumps, motors, tanks, valves, trends, alarms, controller
faceplates, and bitmaps. All complex objects shall be scalable to any size, and may include
animation links to provide dynamic responses based on real-time data or user action.
HMI Software RFP Selection Criteria Section 5
5-8
5.3.3 Graphics Display Development
The SCADA system software shall include an object-oriented color graphics display generator with full
animation capabilities to provide users with a realistic visualization of the SCADA system process.
The graphics display generator must allow SCADA screens to be built once and used on any
size/resolution display. All graphical editing operations shall be point-and-click, selecting icons from
floating and docking toolbars, pull-down menus, or keyboard commands. The development
environment shall be able to run in a Remote Desktop Services session. The display editor shall
include tools for display, drawing, linking, and animation.
5.3.4 Object and Code Reuse
The development environment shall promote code reuse through standard templates that may be
customized to create new object instances.
5.3.5 Object Animation
The color of an object can use any one of up to 256 colors, 128 standard colors, and up to 128 user-
defined colors. A user-defined color palette can be created, exported, and imported. The color palette
shall be based on 16.7 million colors. The system will also support users choosing transparent colors
for all graphical objects and backgrounds.
A percentage of fill for up, down, left, or right object directions can be based on a tag or hierarchical
name.
An object may blink based upon any Boolean expression alarm event or upon a designated group of
alarms. The blink shall be adjustable to slow, medium, or fast.
Each object shall have a visibility attribute option, allowing for visibility of the object based upon the
status of a discrete point alarm or operator security level.
The system shall support object animation via resizing, moving, and/or rotating based upon a
change in a tag or hierarchical name.
Objects shall be animated based upon any user-defined criteria made up of tag names or variables
in the system. This includes the use of expressions containing mathematical functions and the
status of analog and discrete values in the system.
The graphics editor shall allow object layering to activate specific objects based upon conditions in
the process.
Graphics development tools shall allow object placement via a snap-to-grid feature with configurable
grid spacing.
Graphics development tools shall support an undo/redo feature with a configurable number of levels
and command displays.
The system shall support a library of self-rendering objects that change visual properties based on
dialog box entries made during development. For example, consider a standard set point loader
object that has a graduated scale and a default range of 0 to 100. Dialog box entries shall allow
changes to the range of the set point loader, number of major and minor divisions on the scale, and
text font used for labels. The object shall then redraw itself with new number of tick marks, new
spacing, new labels, and new font.
The system shall support the import of drawing interchange format (DXF) files (AutoCAD) with the
drawing elements imported as native objects. It shall be possible to animate these objects using the
full set of object animation properties as specified in earlier sections.
HMI Software RFP Selection Criteria Section 5
5-9
The graphics editor shall also allow users to import drawings and images in bitmap (BMP), portable
network graphic (PNG), and Joint Photographic Experts Group (JPEG) file formats.
The graphics development environment shall support copying single or multiple animated graphic
objects and symbols. Immediate substitution of tag names for the duplicated object shall be possible
without leaving the graphics editor.
The graphics development environment shall support copying single or multiple animated graphic
objects and symbols from one window or display to another, retaining all the animation
characteristics, links, and attributes. This function will eliminate duplication of effort. In addition, it
shall be possible to import windows from another application in this same fashion.
Users shall be able to add tag or hierarchical names to an object while building a display without
exiting the graphics editor.
Online context-sensitive help shall support display building. Users shall be able to access immediate
help on all configuration subjects by pressing a single function key.
Users shall be able to define graphic screens while the system is monitoring the process.
5.3.6 Object Model
The development environment shall use the concept of application objects. These objects may
represent real-world devices, such as proportional-integral-derivative (PID) loops, motors, pumps,
valves, etc.; informational objects such as external database readers and writers; and eXtensible
Markup Language (XML) readers and writers, etc. Application objects shall closely model the physical
representation of plant equipment and devices and will not be bound to a separate data tag
database topology. This shall include the ability to create complex multi-variable data objects.
5.3.7 Real-Time Trend Viewing
Users shall be able to trend up to 256 different tag names in real time, including analog discrete
string or event tag names within the same trend. Users shall pick tag names from the browser. The
time span and vertical range of the trend shall be user-configurable at runtime. Standard time spans
shall be configured for the last 5, 10, 30, or 60 minutes, or the last 8 or 24 hours. Users shall be
able to adjust the range of the tag names in runtime.
5.3.8 Runtime Data Viewer
The runtime environment shall provide a utility to view the real-time status of any application object
attribute.
5.3.9 Template Derivation, Object Instantiation, and Inheritance
New templates shall be derived from an existing templates base (supplied by the software
manufacturer) or user-defined. A template shall inherit the entire configuration of the parent object
when generating a new template instance. Templates may contain other templates in a hierarchy.
Templates may be derived from another template.
HMI Software RFP Selection Criteria Section 5
5-10
5.4 Redundancy Requirements
This section presents system redundancy requirements for the project.
5.4.1 Alarm Redundancy
The system shall provide (for alarm handling) standby application objects that become active upon
failure of execution of active objects or failure to communicate with the active objects. Separate
configuration of alarms in standby objects is not required. As with application, redundancy objects
are allocated to a primary manager object that—in turn—ensures that contained standby objects are
created and deployed as standby for alarm handling.
5.4.2 Application Log Files
Application log files shall reside on the local hard drive for a user-defined number of days. Each
network node shall maintain an independent log file for the applications that are unique to each
node. A new log file will be created and archived daily per the user-specified time and location. The
viewer shall support color distinctions for different threads, processes, or programs. The log file
viewer shall support viewing remote node application log files.
5.4.3 Application Redundancy/SCADA System Failover
The SCADA system software shall provide redundancy for all functions within a normal SCADA
controls environment. The specific components that require redundancy within the SCADA system
are (1) application object/application object hosting PLC/RTU communications alarm logging, (2)
reporting (i.e., remote notification), and (3) logging historical process data. In redundant
configuration, there shall be a primary and backup system object that manages contained primary
and backup objects. The system shall execute and synchronize active objects with standby objects.
In the event of detection of any failure in active object execution or communication with the active
object, standby objects shall begin executing and communicating within the system. This redundancy
must support offsite backup.
Configuration of application redundancy shall be configured through a GUI that does not require any
scripting.
5.4.4 Communications Redundancy
The SCADA system shall monitor the status of communications to the communications server(s), and
the status of the communication server to each PLC/RTU. In the event of a communications failure,
the SCADA system shall transfer communications responsibility to a designated standby
communications server.
5.4.5 Remote Client Access Server Failover
Remote client access thin clients, concurrent or dedicated, shall be capable of automatically failing
over to a redundant remote client access server. No operator intervention shall be required. The
system shall support execution of the visualization software and engineering development tools in
remote client access sessions while enforcing the configured OS security model.
HMI Software RFP Selection Criteria Section 5
5-11
5.5 Historian and Data Access Requirements
This section presents historian and data access requirements for the project.
5.5.1 Data Compression
The database shall support high-speed data acquisition and efficient data compression. Data
compression for the historical data collector shall not use any algorithms that do not allow for
storage of the tag data at their scanned rates. The stored data records shall be able to recreate the
process data in a lossless format.
The historical data collector shall store string or text data. Each string may be up to 512 characters
long. With each string value stored, a quality field shall be stored as well.
5.5.2 Database Summary System
The historical data collector shall provide user-configurable data summary tables for any analog tag
name, and will automate the collection of aggregate historical information based on a declared
event. The summary system shall support minimum, maximum, average, and summed calculation
types for minute, hourly, daily, weekly, and monthly frequencies. The summary system shall store the
tag name value type of calculation and frequency as defined for each tag name.
5.5.3 Disk Storage Management
The historical data collector shall not require specialized tools for disk storage management. It shall
be possible to automatically archive (i.e., back up) and retrieve historical data files using standard
Windows copy techniques. It shall be possible to retrieve select portions of archived data without
retrieving all archived data. Retrieval of the archive data shall automatically place these data online
and make them available for retrieval by the historical data collector.
Additionally, the historical data collector shall approach zero administration as nearly as possible.
The historical data collector shall provide for a mechanism whereby current files on a disk drive that
is nearly full will automatically be moved to a secondary device. The files and available space on the
secondary drive shall also be monitored, such that when a user-defined threshold is reached, the
oldest files may be automatically deleted to preserve the integrity of the system. Historical files shall
never be deleted from the primary storage device if an appropriate secondary device is configured.
5.5.4 Dynamic Configuration and Bumpless Data Initialization
The historical data collector shall automatically begin acquiring tag data immediately after a tag
configuration has been committed to the database. Adding a single tag, or multiple tags, to an
existing historical data collector database shall not affect the data acquisition of previously defined
tag names. Client connections will not be affected during reconfiguration because of dynamic
configuration. Additionally, there will be no loss of data for tags where data acquisition configuration
is not changed. Tags that require a change in data acquisition configuration will lose data during the
period of re-initialization.
5.5.5 Event Action
The historical data collector event detectors shall determine that an event has occurred, and trigger
an associated action. Event detectors shall scan for events at the user-defined rate for each event.
Users shall be able to select from any one of the following four actions when an event is detected:
• Execute a Structured Query Language (SQL) statement to perform an SQL query on the
database.
HMI Software RFP Selection Criteria Section 5
5-12
• Take a snapshot and recording the time stamp and values of one or more selected analog or
discrete tags.
• Send a Microsoft Exchange or Simple Mail Transfer Protocol (SMTP) email message to
designated recipients.
• Change the cyclic time and/or value delta storage rate for one or more analog tag names. The
ability to modify the storage rate based on an event allows for fast logging of data to gather more
valuable process data to assist in troubleshooting.
5.5.6 Event Configuration
Using a point-and-click approach, the system shall allow users to create/define event tag names and
associate event tag names to event detectors and the resulting actions. Users shall be able to insert
a time delay in milliseconds before the event action is triggered, and establish the priority of the
event as normal or critical. It shall be possible to detect an event based on a scheduled time interval;
a specific analog value crossing a threshold; or a discrete value from 0 to 1 (leading edge), 1 to 0
(trailing edge), or both. An event editor shall be provided to support complex event detectors and
event actions.
5.5.7 Event System Configuration
The historical data collector shall contain an event subsystem to monitor, record, and/or respond to
process or system events, and to trigger some type of action when the event is detected. The event
system shall detect an event occurrence using predefined and configurable criteria, historically log
when an event occurs, and trigger designated configurable event actions based on the event
detection. Event attributes shall be logged to the database, will include the date and time that the
event occurred, and will include the event criteria that were satisfied.
5.5.8 Historical Data Acquisition and Retrieval
The historical data collector shall acquire data via automatic and manual methods. Automatic data
acquisition shall be through industry-standard data transports. Data acquisition via Dynamic Data
Exchange (DDE) and OPC in addition to proprietary transports shall be supported. The method for
retrieving data shall be SQL. It shall be possible to store data at one resolution, and query at another.
Methods shall exist to query and retrieve data cyclically with millisecond resolution, no matter the
storage mode. It shall be possible to query and retrieve data in delta with user-selected deadband
criteria and millisecond resolution, no matter the storage mode. It shall be possible to query and
retrieve evenly spaced data over long periods when the criterion is a row count, no matter the
storage mode.
5.5.9 Historical Data Collection (Historian)
Historical collection of data from SCADA objects shall be entered once at the time of configuration of
those objects using the corresponding object editor in the SCADA system. The historical data
collector shall automatically acquire the configuration parameters upon deployment of the
configured application objects.
The SCADA system software shall provide a real-time relational database for long-term process data
storage. The historical data collector shall store real-time and historical data for each analog,
discrete, or string tag name. The historical data collector shall also store summary event alarm and
configuration data. The database engine for the collector shall be based on a full licensed copy of
Microsoft SQL Server, and support client/server architecture. Users shall not be required to know
Microsoft SQL Server to install and implement the historical data collector. The historical data
HMI Software RFP Selection Criteria Section 5
5-13
collector database shall acquire and store process data at full resolution. The historical data
collector database shall include normalized extension tables for real-time data, and include a set of
client tools for data analysis and reporting, such as those described in earlier sections. The historical
data collector shall be able to run in a standalone mode without connection to, or configuration from,
the SCADA system.
While there are always physical limiting factors such as disk space, there shall be no programmatic
limit to the amount of data stored online. Additionally, there shall be no performance penalty for
long-term data storage. There shall be no discernible difference in data retrieval speed based on its
age. For example, the retrieval of 2 hours of data stored 2 years prior shall be the same as that for 2
hours of data stored 1 day ago.
5.5.10 Historical Data Collector Interface to Other Relational Databases
The historical data collector shall use Microsoft’s Data Transformation Services to simplify the
transfer of historical process data with other SQL server databases like Microsoft SQL Server or
Oracle. The historical data collector database shall include an Object Linking and Embedding (OLE)
database provider so that any other SQL client can access the real-time or historical process data
from the historical data collector.
5.5.11 Historical Data Collector Redundancy
The system shall allow active object value historical data collection. Upon failure of execution of
active primary objects, standby objects shall be activated and shall assume the task of providing
data for historical collection. Separate configuration of historical collection for standby objects shall
not be required. If the historical data collector is offline or unreachable, the engines servicing active
objects shall store the historical data locally, and forward the buffered data to the historical data
collector when the server is available. Primary and standby object engines shall synchronize any
buffered historical data. If the historical data collector is offline or unreachable and the primary
object engine fails, the failover engine shall assume the task of storing historical data locally, and
forward the buffered data to the historian when the server is available. There shall be no practical
limit (other than disk space) as to the size of the locally stored historical data.
5.5.12 Historical Data Point Configuration
The historical data collector shall include a database editor to modify the parameters of any tag
name without using the SCADA database editor as an option. It shall be possible to configure the
data storage rate for each point based on a user-defined rate frequency (i.e., cyclic storage) or upon
change (i.e., delta storage). Cyclic storage rates shall be configurable per point from 1 second, up to
several hours. The historical data collector database shall support a 500-millisecond resolution for
tag names that are configured with delta storage.
5.5.13 Historical Trend Viewing
Users shall be able to plot historical data for any tag name or groups of tag names in the database
based any user-selected start and stop time. Two hairline cursors may be turned on and dragged
across the trend area to provide users with the exact value for each trended tag name at the point of
intersection. The time span and value between the cursors shall also be displayed. It shall be
possible to overlay data from different start/end times to compare the performance of
equipment/compare the process for different time intervals. It shall be possible to overlay live trends
onto history traces to compare performance. The trend tool shall display statistical data for each
trended analog tag name within the period selected. Statistical values shall include the minimum,
maximum, average, and standard deviation. Icons or menu pull-down commands shall be available
HMI Software RFP Selection Criteria Section 5
5-14
for analyzing the data, such as horizontal, vertical, or rubber band zooming; pan left or right; and
zoom between the hairline cursors. It shall also be possible for users to create text annotations
anywhere on the trend. These annotations shall be visible from other workstations on the network
with the same trend tool. It shall be possible to export the data in the trend area into an Excel (XLSX)
file. Printing of the trends with all statistical data shall be supported.
5.5.14 HTML Reporting Client Tool
A client tool shall be included that allows users to generate reports on any tag names. The client tool
shall have a user interface that allows selection of tag names and previously created reports and
report formats. The report tool shall allow users to set up, modify, and generate reports that present
report data professionally and reliably. Types of information supported shall include historical and
current data values, tag name configuration, information, graphs, statistics, annotations, event and
summary information, and results from a query. Reports shall be generated based on data stored
over a specified period in minutes, hours, days, weeks, or months. It shall also be possible to
generate reports on demand by users at runtime. Finished reports shall be formatted in Hypertext
Markup Language (HTML) so that they can be viewed with a Web browser, stored on the server disk,
or sent to a printer.
5.5.15 Manual Data, Out-of-Sequence Data, and Superseded Data
The historical data collector shall support manual data, out-of-sequence data, and superseded data.
Manually entered data such as lab data and out-of-sequence data (e.g., batched history data from an
RTU) shall be treated by the retrieval engine as if it were stored automatically. Any collected data
may be superseded by manually inserting the correct data value and a flag denoting that the
previous data have been superseded. The original data shall not—and cannot—be modified or
destroyed. An SQL client tool may request original data, superseded data, or both. Manual data, out-
of-sequence data, and superseded data shall be inserted into the Historian via an SQL insert
statement or in bulk via CSV file. Only users with proper login credentials shall be allowed to
manually insert or modify data.
All stored data shall contain data quality attributes. The primary data quality attribute shall reflect
data quality as defined in OPC. Additional quality attributes shall be used for initial data (e.g., startup
flag) and superseded data.
5.6 Enterprise Systems Connectivity Requirements
This section presents enterprise systems connectivity requirements for the project, including
Microsoft Excel reporting tool, Microsoft Word reporting tools, and standardized database tables.
5.6.1 Microsoft Excel Reporting Tool
Data analysis software shall be included that allows users to easily select tag names and historical
values from the real-time or historical database via a browser, and then use them in a standard Excel
spreadsheet for reporting or presentation to management. Tag names shall be selected using drag-
and-drop or point-and-click commands. Writing macros to retrieve data shall not be required. The tag
values selected can be output to specific cells in the spreadsheet and processed as number data
types. Users shall be able to select historical data for the most recent values, or go back and select
any start or stop time as far back as the data are available. The historical data can be recalled at the
granularity that it was stored, or in a selected number of data points over a period of time. Users
shall be able to retrieve raw historical data or summarized data such as the minimum, maximum, or
HMI Software RFP Selection Criteria Section 5
5-15
average over a predetermined period. Once they are in the spreadsheet, updates to the current
values shall be refreshed with a single mouse click.
The quality of the data shall be analyzed and displayed. Users shall be able to select if poor-quality
data will be displayed or replaced with an interpolated value. Users shall be able to specify relative or
absolute value choices.
5.6.2 Microsoft Word Reporting Tools
Data analysis software shall be included that allows users to easily select tag names from the real-
time or historical database via a browser, and then use them in a standard Word document for
reporting. Selecting tag names shall be accomplished using drag-and-drop or point-and-click
commands. Writing macros shall not be required to retrieve the data. The tag names selected can be
output to specific values or arrays using standard Word tables. Users shall have the choice of
selecting real-time absolute relative or configurable base dates and times. Users shall be able to
retrieve raw historical data; summarized data, such as the minimum, maximum, or average over a
predetermined period; or data stored in the historical data collector. Users shall be able to select if
poor-quality data are to be displayed or replaced with an interpolated value.
5.6.3 Standardized Database Tables
Setting up the database tables shall be automatically configured and require no database
engineering. Data definitions including the creation of database objects such as tables, indexes,
constraints, defaults, rules, stored procedures, triggers, and views shall follow a standard published
and readily available database scheme.
This standard database schema shall outline the relationship between tables, table columns, keys,
and indexes, and shall allow for third-party development of client applications. Database device sizes
shall be dynamically allocated during database installation depending on the number of tag names
to be stored within the historical data collector.
5.7 Security Requirements
This section presents security requirements for the project.
5.7.1 Audit Trail
The development environment shall provide an audit trail of check-out/check-in and revision history
for each template or application object that includes a user identifier (ID), time and date stamp, and
detailed summary of the changes made.
Any runtime changes to a configured variable shall provide an audit trail of user ID, full user name,
previous value, and new value. Attributes configured for verification shall provide an audit trail of
user ID, full user name, verifier user name, full user name, previous value, and new value.
5.7.2 Logging Operator Actions
All operator actions shall be logged to an event logger. The event logger shall keep track of each new
operator log on, log off, set point change, or device control.
Each event log shall record the date, time, operator logged in, and type of action taken (e.g., set
point change, state change, etc.).
HMI Software RFP Selection Criteria Section 5
5-16
5.7.3 Multi-User Development Environment
The development environment shall provide a simultaneous multi-user development environment
where users are subject to security permissions based on individual system-wide roles.
5.7.4 Operator Security
The operator workstation shall use the security model defined by the configuration database.
The software shall use data-level security, where the ability to modify a set point or other value is
determined in the configuration database. Any changes to the data level security model shall be
seen by all operator stations without any modifications to the operator stations.
The security system shall be capable of disabling access to all Windows controls (e.g., file menu,
close, minimize, etc.) and keyboard commands (Ctrl-Esc, Alt-Tab, and Ctrl-Alt-Delete).
5.7.5 Runtime and Development Security
The HMI software will provide for at least four security groups and at least 20 logins with access
levels and logins configurable during runtime. The HMI software security function shall allow for
creation of operator roles that can be assigned to security groups. Operator roles shall allow for
assignment of configuration database permissions, and for runtime operational permissions and
access to visualization of certain windows. At a minimum, runtime operational permissions shall
control the following:
• Privilege to acknowledge an alarm in the runtime environment
• Privilege to modify configuration attributes that allow users to configure the attribute’s value (i.e.,
a PLC register that defines a discrete input [DI])
• Privilege to modify operational attributes that allow users with operational permissions to do
certain normal day-to-day tasks like changing set point output and control mode for a PID object
or commanding a device object
• To open and view a process or application window
• The modification of tune attributes, which allows users to tune the attribute in the runtime
environment (examples of tuning are attributes that adjust alarm set points and PID sensitivity)
Users assigned to operator roles shall inherit all parameters that were assigned to the role and
security group.
Runtime changes to object values shall be subject to security authorization. Permissions that are
configured using the development environment shall be automatically checked at runtime for
authorization, including verification of identity and access permission related to the originator of the
runtime change request.
Users shall log in before any change to any object attribute that has been constrained is allowed.
The runtime architecture shall conform to the object attribute security model defined in the
configuration environment.
5.7.6 View-only Graphics Display Workstation
The SCADA system software shall support view-only graphics workstations for managers or
supervisory personnel who wish to have access to all displays and trends, but do not have process
control or alarm acknowledgement responsibilities. No modifications to the SCADA HMI configuration
shall be required for this functionality. The view-only graphics display HMI shall be able to run in a
Remote Desktop Services session.
HMI Software RFP Selection Criteria Section 5
5-17
5.7.7 Multi-factor Authentication
Provide support for a multi-factor authentication system for access to the SCADA system. Multi-factor
authentication technologies use authentication factors from at least two of three generally accepted
categories: something known (e.g., a password or personal identification number [PIN]), something
possessed (e.g., a one-time password token or a smart card), and something unique about the user
(e.g., fingerprint or iris pattern). Systems that use two or more factors are described as using multi-
factor authentication; systems that use only two factors are described as using two-factor
authentication. User IDs are not considered factors in a multi-factor authentication system. It is
expected that each proposer includes the type of authentication the SCADA system can provide.
5.8 Future Development Requirements
This section presents future development requirements for the project, including platform-
independent scripting support and tools and communications architecture.
5.8.1 Platform-Independent Scripting Tools
The data analysis software shall provide platform-independent scripting objects for the trend and
query clients so that they may be embedded into SCADA HMI, or any other platform-independent
scripting container. A query client shall be included to allow users to execute SQL queries that return
a result set from any SQL server database into a tabular data grid. The query platform-independent
scripting tool shall support multiple data server sources for simultaneous data display.
5.8.2 Communications Architecture
The runtime environment shall be based on distributed peer-to-peer system architecture. It shall be
possible to scale the architecture from a single self-contained node to more than 50 nodes. The
architecture shall contain a multi-computer model that is a single distributed namespace in the
runtime environment, and does not require replication of data from one node to another.
Application objects and their attributes shall be accessible by the objects’ hierarchical names or
globally unique tag names.
The architecture shall allow for remote redeployment of application objects and associated programs
without reloading software.
The architecture shall allow centralized administration and control of the runtime state of the
distributed system.
The architecture shall operate in real time and be able to handle millisecond transaction and event
speeds.
The architecture shall be able to monitor and respond to high volumes of asynchronous data and
event messages at a rate of thousands of messages per second.
Application objects shall have the ability to connect to any I/O server using the DDE, DDE-Net, and
OPC protocols. I/O shall be defined as any input and/or output variable including individual data
acquisition points and any variable parameter generated for exchange between objects in the
system. At a minimum, the data types supported shall be Boolean float string, internationalized
string integer (e.g., 8-, 16-, and 32-bit signed and unsigned), time, and elapsed time.
HMI Software RFP Selection Criteria Section 5
5-18
5.9 Optimization Capabilities Requirements
This section presents optimization capabilities requirements of the project, including a process data
analysis workstation and a real-time and historical trend analysis tool.
5.9.1 Process Data Analysis Workstation
The SCADA system software shall include a set of easy-to-use client software tools for real-time and
historical data analysis and system reports. This client analysis software may be used by engineering
maintenance or supervisory personnel who need information from the SCADA system, but do not
require access to graphic displays. The client tools shall be able to access data from multiple
historical data collectors on the SCADA system network. Users shall be required to log in with a
password to access the database server. Users shall not have to know the location of the server on
the network—only the name of the server. The data analysis software shall include tools for
advanced trending analysis, X-Y plotting of tag names, and viewing of reports in spreadsheet or
freeform format. All tools shall support full mouse right-click capability for quick menu selection of
available functions. The client tools shall be available as a standalone program or as a platform-
independent scripting control for embedding into SCADA so that any full-function or view-only
operator workstation may have the same capability or any user interface that supports the platform-
independent scripting tools.
5.9.2 Real-Time and Historical Trend Analysis Tool
A client tool shall be included that allows users to view any or all the tag names in either a trend
chart or tabular format. The client tool shall have a user interface that allows for easy selection of tag
names using an Explorer-like browser with a search filter to quickly find tag names in a historical
data collector with thousands of points. Users shall be able to create folders for selected groups of
tag names, and plot them individually or in groups by dragging them into the trend area. Users shall
be able to save trend files for recall later. It shall be possible for users to switch from real-time to the
historical viewing mode using a simple check box. Users shall be able to toggle viewing trends either
in the superimposed or stacked mode. In the superimposed mode, all trends overlap and are in a
single-scale range based on the largest vertical scale range in the group. In the stacked mode, each
trend has its own vertical scale range. Trend plots shall automatically be scaled based on the widest
vertical range of the tag name or optimized based on the maximum and minimum range within the
selected period.
5.10 Future Stability and Support Requirements
This section presents future stability and support requirements for the project, including warranty,
software maintenance, and technical support; priority telephone support; and SCADA system
software installation, licenses, and support.
5.10.1 Warranty, Software Maintenance, and Technical Support
The software warranty shall begin when it has been installed and is in productive use. After the end
of the warranty period, users may continue to receive technical support via phone, email, or the
technical support website. To ensure that users always have access to the latest software releases,
long-term warranty, and technical support, the vendor shall offer an extended support program for a
fixed annual fee that entitles users to receive software upgrades, priority telephone support,
electronic support, electronic file download, newsletter, and tech support compact disc (CD).
HMI Software RFP Selection Criteria Section 5
5-19
The extended support program shall entitle users to receive the latest SCADA system software
releases and version upgrades as they become available. To ensure quality support for all users, all
software licenses at the site must be maintained at the same version level.
5.10.2 Priority Telephone Support
The extended support program shall include priority telephone support 24 hours a day, 7 days a
week, 365 days a year. A technical support engineer who has been certified by the software vendor
based on a certified support testing program shall provide telephone support. A person (not an
automated line) shall provide unlimited telephone support when calling during normal business
hours. A voice-mail technical support system shall be acceptable only outside of normal business
hours. A support engineer shall return voice mail a minimum of 2 hours after leaving a message with
the voicemail system.
5.10.3 SCADA System Software Installation, Licenses, and Support
The SCADA software shall be easily installed from a single CD or a set of CDs (or USB drive) using a
standard installation program. During the installation procedure, users shall be able to select the
features and functions required for each workstation or server in the SCADA system. While loading
the selected software, it shall be possible to redirect the location of software components. The
SCADA software shall be licensed using software license files that can be easily restored to the
system in case of hard drive failure. No hardware keys shall be required to run the software.
6-1
Section 6: Technical Criteria
Please provide written responses to each of the questions below as a separate attachment to the
proposal. All responses to section 6 shall align with the numbering in the section to facilitate the
review process. The questions do not need to be repeated Total length of all responses must not
exceed 15 pages with a minimum font size of 11 points in Microsoft Word (Franklin Gothic or
equivalent). This page count is specifically for this section and does not include written responses
needed in any other sections. There are at least 65 questions in this section so answers will have to
be brief and to the point to manage the page limitation.
6.1 Foundational HMI Criteria
6.1.1 Describe how development, configuration, testing, and deployment can be achieved
through the proposed software without causing disruption of the running process system.
6.1.2 Describe the extent of product support documentation that will be available for the
proposed software.
6.1.3 Describe how data will be viewable from workstations remote from the operations control
stations. Indicate if server load sharing will be used and what configuration will be needed
for remote workstations. How will remote workstations select a server to connect to if the
primary servers are not in service?
6.1.4 Describe any features to support a radio communications network for data acquisition from
multiple remote sites. Include available polling schemes, synchronization method, and
tools for configuration of radio master connections.
6.1.5 Describe how synchronization is achieved for remote sites and remote or redundant
servers. How will synchronization be configured?
6.1.6 List all supported standard protocols and available custom protocol drivers for both serial
and Ethernet protocols.
6.1.7 List all mobile SCADA applications written for the IOS and Android OSs and briefly describe
what features these applications provide.
6.1.8 List all web-based SCADA applications and briefly describe what features these
applications provide.
6.1.9 Provide a screen shot of an example project at a wastewater lift station (not included in
page count).
6.1.10 Provide a screen shot of an example project at a water pump station (not included in page
count).
6.1.11 Identify all parties that will be signatories to the contracts for purchase, maintenance,
support and services
6.2 Alarming with Criticality Management Criteria
6.2.1 Describe how alarm events and alarm criticality are configured and managed.
6.2.2 What standard are the alarm management tools based on?
6.2.3 Describe how alarm events are logged and how they can be accessed in the alarm
database. Include what data are captured in a logged event.
6.2.4 Describe available capabilities for remote alarm notification and how remote alarm
notifications would be configured and managed.
HMI Software RFP Selection Criteria Section 6
6-2
6.3 High-Performance HMI Criteria
6.3.1 Describe any human factors or intuitive design features included in the system that will
help to guide operators in monitoring and control of the system.
6.3.2 Describe how any software features can reduce the required learning curve for new system
programmers or operators.
6.3.3 Describe any available pre-canned graphics templates, pop-up screens, faceplates, or
objects for the software that will provide value for application in the water and wastewater
industry.
6.3.4 Describe any available pre-canned status indicators that will allow for monitoring of the
control hardware, communications network, and server and data availability.
6.3.5 Describe how the system will support real-time data access for graphical display of states
and values. How will required update frequencies be achieved (less than 1 second on
control room local area network [LAN] and less than 2 seconds over wide area network
[WAN])?
6.4 Redundancy Criteria
6.4.1 Describe any features that will support the transition of the system to an alternative site in
the case of catastrophic system failure or major hardware failure at a single site.
6.4.2 Describe how redundancy will be provided for all critical SCADA functions so there will be
no single point of failure for critical functions. Critical SCADA functions include any
component that will, during failure, disrupt the ability for the system to continue to provide
monitoring and control of the system (e.g., graphical user interface [GUI], input and output
(I/O) servers, real-time databases, historians, alarming, user access).
6.4.3 Describe how critical system components will be monitored for failure and how the
monitoring system can be configured and updated for new or removed components.
6.4.4 Describe how modular components may be used for the system to allow for failover to a
hot standby in case of software or hardware failure. Provide a description of how the
standby component will be continuously updated with synchronized data to be available for
failover.
6.5 Historian and Data Access Criteria
6.5.1 Describe how real-time and historical data are accessed for reporting and analytics.
6.5.2 Describe any tools available for the generation of automated data reports from the
historian on a periodic basis.
6.5.3 Describe additional tools and functionality for real-time and historical data operational
business intelligence insight, chain-of-custody management, and filtering and validation.
6.6 Enterprise Systems Connectivity Criteria
6.6.1 Describe how the proposed system will integrate process data with enterprise business
applications across the network demilitarized zone (DMZ). Provide examples of prior
successful process data integration with enterprise business applications. Include a
description of how the system will be integrated and a prior example for each of the
business applications included in Table 6-1.
HMI Software RFP Selection Criteria Section 6
6-3
Table 6-1. External Business Applications
Business Application Software Vendor
Asset management InfoMaster
CMMS Infor Public Sector (Hansen)
GIS ArcMap
Customer information interface WaterSmart
Advanced Meter Infrastructure System Itron
Document management system HPRM
System model H2OMap, InfoWater, and InfoSWMM
6.6.2 Describe any relationships with the enterprise software providers listed above.
6.6.3 Describe the capabilities of your software to integrate with third party databases using SQL.
6.7 Security Criteria
6.7.1 Which security standards or frameworks does your product comply with or undergo
evaluations by?
6.7.2 Describe the security training your software developers have been through.
6.7.3 Do you have third-party vulnerability audits of your software/product? Are the reports made
available to clients? Provide a copy of the most recent third-party vulnerability audit report
as an appendix to your responses (not included in page count).
6.7.4 Describe your vulnerability disclosure/notification procedure to clients when vulnerabilities
are discovered.
6.7.5 Describe your patching and update procedure and cadence.
6.7.6 If vulnerabilities are discovered by your clients, how do you prefer to be notified?
6.7.7 Have you or any of your clients had a data breach or security incident because of a
vulnerability in the software/product that you have proposed? If so, describe the support
provided to your client.
6.7.8 Are there any current known and unpatched vulnerabilities in the software/product that
you have proposed?
6.7.9 Do you have a formal security program/department in your organization? If so, describe it.
6.7.10 What methods are employed to protect data, including authentication in the
software/product you are proposing?
6.7.11 Describe how user roles and privileges can be configured and updated for access security.
6.7.12 Describe how the proposed HMI system could support adding all SCADA
computers/servers to the owner’s Microsoft Active Directory Domain. How can the Active
Directory Domain for the SCADA system be used for user authentication and role-based
security groups?
6.8 Future Development Criteria
6.8.1 Describe how sites could be added to or removed from the system without disrupting
operations. Include specifically how database tags and graphics could be added or
removed during runtime without needing a system reboot.
HMI Software RFP Selection Criteria Section 6
6-4
6.8.2 Describe how existing development standards can be implemented using templates and
objects for future programming work.
6.8.3 Indicate the available programming languages that are supported in the software
development kit, if provided.
6.8.4 Describe how scalability is achieved with the proposed software. How will features
accommodate growth and change of the process, network architecture, and integrated
technologies over time?
6.9 Optimization Capabilities Criteria
6.9.1 Describe any associated products that would integrate with the HMI system to provide
optimization of water quality, energy usage, and pump production for water distribution and
sewer collection systems. Provide an explanation of the optimization methods and what
process data will be needed for implementation.
6.9.2 Describe any associated products that would integrate with the HMI system to track asset
and maintenance management and assist with predictive maintenance.
6.9.3 Describe any associated products that would integrate with the HMI system to support user
decision making, training, and standard operating procedures.
6.9.4 Describe any associated products that would integrate with the HMI system to provide
automatic data validation to detect and correct missing, poor-quality, or suspect data.
6.10 Future Organizational Stability and Support Criteria
6.10.1 How many years has the manufacturer’s current company organization been in business?
If the product will be provided by a third-party distributer, provide this information for the
distributer as well.
6.10.2 Provide documentation of manufacturer’s organizational structure and segmentation. What
are the type and number of employees committed to development, administration,
marketing, and technical support of the proposed product? What is the ratio of technical
support employees to the total install base of the HMI software under support contract? If
the product will be provided by a third-party distributer, provide this information for the
distributer as well.
6.10.3 Provide the manufacturer’s audited financial statements from the three most recently
reported years. What percentage of revenue is derived from industrial automation software
products? How much revenue was generated by the proposed HMI software products in
the three most recently reported years? If the product will be provided by a third-party
distributer, provide this information for the distributer as well. Provide the financial
statements as an appendix to the 15-page technical criteria response in a separate
envelope marked confidential.
6.10.4 Provide the manufacturer’s business and product development plans for the proposed
product and support services. If the product will be provided by a third-party distributer,
provide this information for the distributer as well.
6.10.5 Describe the approach to backwards compatibility and obsolescence for the proposed
product.
6.10.6 Describe the training programs and products offered to provide training for development,
administration, and operations levels of the offering. Attach a training course description
and schedule for 2018 as an appendix to the 15-page response.
HMI Software RFP Selection Criteria Section 6
6-5
6.10.7 Describe the warranty policy that will be provided for the HMI software.
6.10.8 Provide any technical support options/tiers and capabilities offered in addition to the
options required for cost comparison in section 4.
6.10.9 Describe the technical support program escalation process. How does the escalation
process change for different tiers of technical support offerings?
6.10.10 Describe your product development quality assurance/management program. What is your
product testing process prior to product release?
6.10.11 Provide a contact name, phone number, website, and address for the regional sales
representative for this product.
7-1
Section 7: Industry Presence
Responses to this section are requested as a written response to be included as an appendix with
the proposal. Total length of the response must not exceed 5 pages with a minimum font size of 11
points in Microsoft Word (Franklin Gothic or equivalent). Proposers shall provide the following in
response to this section:
1. A list of public water/wastewater agencies in North America, including at least three within
California, using your platform to indicate the installed base of the product. For each installation
include agency name, location, tag count, and date of installation.
2. A list of at least 3 references of public water/wastewater agencies within 100 miles of Carlsbad
using the proposed product. Provide the agency name, contact names, phone numbers, emails,
I/O count, and date of installation. This list will be used as part of the evaluation process to
assess local industry presence in Round 1. Under Round 2, these references will then be
formally contact for short listed proposers. If selected for the second round, at least one of the
references, preferably in north county San Diego, must be willing to host the owner’s staff.
Evaluation criteria for Round 2 are explained in section 9.
3. Data on the average size of system installations in the water/wastewater industry. Include
information on the number of tags used, number of remote sites, total flow capacity (in millions
of gallons per day), number of employees, and any other useful metrics.
4. A list of vendors and contractors/integrators capable of supporting your platform that are
located within 90 miles of Carlsbad, California. Provide a contact name, phone number, website,
and address for each. Describe any qualification or certification process that is provided for
contractors/integrators for this product.
8-1
Section 8: Value Added Consideration
Responses to this section are requested as a written response to be included as an appendix with
the proposal. The proposer shall provide any additional value that may be gained by the owner
through additional products or cost benefits associated with the HMI software. In the written
response, the proposer shall provide a description of what additional products or cost benefits are
available and how the owner will obtain value through the purchase and use of additional products
with the proposed SCADA system. The “value added” may include any cost reductions in purchase of
additional products, available products that may be integrated with the HMI system to provide long-
term efficiency and savings, or any other offerings that the proposer believes may add value for the
owner. Total length of the response must not exceed 5 pages with a minimum font size of 11 points
in Microsoft Word (Franklin Gothic or equivalent).
9-1
Section 9: Evaluation Criteria – Round 2
After round 1 scoring has been completed, the owner will determine a short-list of proposers to be
evaluated in round 2. Round 2 will consist of a customized demonstration and interview, a review of
industry references, and a site visit to a local reference.
9.1 Customized Demonstration and Interview
The owner intends to ask the shortlisted proposers to provide a customized demo on-site for the
Selection Committee, followed by an interview. Details of the requirements for the demo will be
provided at the time the proposer is notified that they have made it into the second round. Proposers
should plan to have technical staff join marketing staff.
9.2 Industry References
Under Round 1, all proposers were required to provide a list references of at least three
water/wastewater public agencies within 100 miles of Carlsbad, California. One reference, preferably
in north county San Diego, must be willing to host the owner’s staff. The owner intends to contact the
references as part of the second round of the evaluation process.
9.3 Site Visit to Local Reference
The owner intends to conduct a site visit with one of the provided references as a part of the
evaluation process. The site visit will allow the owner to evaluate the HMI software in use as a
running installation.
HMI Software RFP Selection Criteria
A-1
Appendix A: Cover Sheet
City of Carlsbad
Water/Wastewater HMI Software RFP
General Information
This form must be signed by a person authorized to make proposals and enter into contract
negotiations on behalf of your company. To be considered for this project, the submittals must be
completed in accordance with this RFP and this cover sheet must be attached.
Failure to submit this form will result in your proposal being deemed non-responsive.
Authorized Official (Signature) Date
Print Name of Authorized Official Title of Authorized Official
Company Name Contact Person
Address District, State, Zip
Phone Number Fax Number
Email Address Federal Tax ID Number
HMI Software RFP Selection Criteria
B-1
Appendix B: Technical Requirement Response Tables
B-2
Appendix B
Technical Requirement Response
Tables
The response shall give a “compliant,” “exception,” or “not compliant” answer for each specification
numbered paragraph and associated lettered sub-paragraph. A “compliant” answer can be made
only if the proposed HMI software can provide the specified function without the addition of external
program applications, or internal programming or scripting. With the “exception” answer, provide a
brief description (i.e., additional software package required, custom programming required,
applications scripting required) to comply with the specification. If a specification requirement
cannot be met by the proposed HMI software, the proposer shall mark that item as “not compliant.”
Table B-1. Foundational Requirements Response
Section Requirement Response Comments
5.1.1 General SCADA HMI software requirements
5.1.2 Conditional control and data change logic
5.1.3 Defined failure events
5.1.4 Development environment views
5.1.5 General-purpose I/O communications
server
5.1.6 HMI application control logic
5.1.7 HMI application logic scripts
5.1.8 HMI application manager
5.1.9 HMI data change, event logging, and window logic
5.1.10 HMI development software requirements
5.1.11 HMI function logic
5.1.12 HMI keyboard control logic
5.1.13 Import/export utility
5.1.14 Windows® service support
5.1.15 Basic software compatibility
5.1.16 Full-function operator workstation (HMI)
HMI Software RFP Selection Criteria Appendix B
B-3
Table B-2. Alarming with Criticality Management Requirements Response
Section Requirement Response Comments
5.2.1 Alarm management and notification
5.2.2 Alarm management functions
5.2.3 Alarm summary/alarm history object
Table B-3. High-Performance HMI Requirements Response
Section Requirement Response Comments
5.3.1 Display navigation
5.3.2 Graphical objects
5.3.3 Graphics display development
5.3.4 Object and code reuse
5.3.5 Object animation
5.3.6 Object model
5.3.7 Real-time trend viewing
5.3.8 Runtime data viewer
5.3.9 Template derivation, object instantiation, and inheritance
Table B-4. Redundancy Requirements Response
Section Requirement Response Comments
5.4.1 Alarm redundancy
5.4.2 Application log files
5.4.3 Application redundancy/SCADA system failover
5.4.4 Communications redundancy
5.4.5 Remote client access server failover
HMI Software RFP Selection Criteria Appendix B
B-4
Table B-5. Historian and Data Access Requirements Response
Section Requirement Response Comments
5.5.1 Data compression
5.5.2 Database summary system
5.5.3 Disk storage management
5.5.4 Dynamic configuration and bumpless data initialization
5.5.5 Event action
5.5.6 Event configuration
5.5.7 Event system configuration
5.5.8 Historical data acquisition and retrieval
5.5.9 Historical data collection
5.5.10 Historical data collector interface to other relational databases
5.5.11 Historical data collector redundancy
5.5.12 Historical data point configuration
5.5.13 Historical trend viewing
5.5.14 HTML reporting client tool
5.5.15 Manual data, out-of-sequence data, and superseded data
Table B-6. Enterprise Systems Connectivity Requirements Response
Section Requirement Response Comments
5.6.1 Microsoft Excel reporting tool
5.6.2 Microsoft Word reporting tools
5.6.3 Standardized database tables
Table B-7. Security Requirements Response
Section Requirement Response Comments
5.7.1 Audit trail
5.7.2 Logging operator actions
5.7.3 Multi-user development environment
5.7.4 Operator security
5.7.5 Runtime and development security
5.7.6 View-only graphics display workstation
5.7.7 Multi-factor authentication
HMI Software RFP Selection Criteria Appendix B
B-5
Table B-8. Future Development Requirements Response
Section Requirement Response Comments
5.8.1 Platform-independent scripting tools
5.8.2 Communications architecture
Table B-9. Optimization Capabilities Requirements Response
Section Requirement Response Comments
5.9.1 Process data analysis workstation
5.9.2 Real-time and historical trend analysis tool
Table B-10. Future Stability and Support Requirements Response
Section Requirement Response Comments
5.10.1 Warranty, software maintenance, and technical support
5.10.2 Priority telephone support
5.10.3 SCADA system software installation, licenses, and support
HMI Software RFP Selection Criteria
C-1
Appendix C: Technical Criteria Scoring Tables
C-2
Appendix C
Technical Criteria Scoring Tables
Responses for section 6 will be scored using the tables below. Each row in the tables corresponds to
one of the criteria listed in section 6. All responses to section 6 shall align with these tables to
provide a structured format so that reviewers can systematically evaluate responses. Total length of
all responses must not exceed 15 pages with a minimum font size of 11 points in Microsoft Word
(Franklin Gothic or equivalent). There are at least 65 questions in this section so answers will have to
be brief and to the point to manage the page limitation.
Table C-1. Foundational Criteria Scoring
Section Score Comments
6.1.1
6.1.2
6.1.3
6.1.4
6.1.5
6.1.6
6.1.7
6.1.8
6.1.9
6.1.10
Table C-2. Alarming with Criticality Management Criteria Scoring
Section Score Comments
6.2.1
6.2.2
6.2.3
6.2.4
Header (Client, Section Title, or Report Title) Appendix C
C-3
Table C-3. High-Performance HMI Criteria Scoring
Section Score Comments
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
Table BC-4. Redundancy Criteria Scoring
Section Score Comments
6.4.1
6.4.2
6.4.3
6.4.4
Table C-5. Historian and Data Access Criteria Scoring
Section Score Comments
6.5.1
6.5.2
6.5.3
Table C-6. Enterprise Systems Connectivity Criteria Scoring
Section Score Comments
6.6.1
6.6.2
6.6.3
Header (Client, Section Title, or Report Title) Appendix C
C-4
Table C-7. Security Criteria Scoring
Section Score Comments
6.7.1
6.7.2
6.7.3
6.7.4
6.7.5
6.7.6
6.7.7
6.7.8
6.7.9
6.7.10
6.7.11
6.7.12
Table C-8. Future Development Criteria Scoring
Section Score Comments
6.8.1
6.8.2
6.8.3
6.8.4
Table C-9. Optimization Capabilities Criteria Scoring
Section Score Comments
6.9.1
6.9.2
6.9.3
6.9.4
Header (Client, Section Title, or Report Title) Appendix C
C-5
Table C-10. Future Stability and Support Criteria Scoring
Section Score Comments
6.10.1
6.10.2
6.10.3
6.10.4
6.10.5
6.10.6
6.10.6
6.10.7
6.10.8
6.10.9
6.10.10
6.10.11
6.10.12
ATTACHMENT B: GENERAL PROVISIONS
[Remainder of this page intentionally left blank]
Attachment B
Page 1 of 11
CITY OF CARLSBAD
GENERAL PROVISIONS
PLEASE READ CAREFULLY THESE PROVISIONS ARE A PART OF YOUR BID AND ANY CONTRACT Pursuant to the Notice to Bidders, the specifications, bidding instructions and requirements on file
with the City, the conditions of these General Provisions, and subject to all provisions of the Ordinances of the City of Carlsbad, the Bidder proposes to furnish to the City of Carlsbad, complete at the prices stated in the bid document, the items or services described in the bid document. The
person signing the bid warrants that the bid is genuine and not sham or collusive, or made in the interest of, or on behalf of, any person, firm or corporation not named in the bid document; that the Bidder has not directly or indirectly induced or solicited any other Bidder to submit a sham bid, or any other person, firm or corporation to refrain from bidding, and that the Bidder has not, in any manner, sought by collusion to secure any advantage over other bidders. In submitting this proposal, the Bidder agrees that: A. Bidder has carefully examined the specifications and all provisions relating to the items to be furnished, or the work to be done, attached and incorporated into the proposal and understands the meaning, intent and requirements of them, and agrees to the same.
B. Bidder will, for the prices quoted, enter into a written contract and furnish the item(s) or complete the work in the time specified, and in strict conformity with the City of Carlsbad
specifications for the item(s) or work. 1. FORMS
If the Purchasing Officer furnishes forms and specifications for proposals and bids, no proposals or bids will receive consideration unless made upon forms so furnished. BIDS MUST BE SUBMITTED IN A SEALED ENVELOPE WITH BID NUMBER ON THE OUTSIDE, COMPLETE WITH THE SPECIFICATIONS AS FURNISHED AND DELIVERED TO CITY OF CARLSBAD PURCHASING DEPARTMENT OR DEPOSITED IN THE BID BOX AT 1635 FARADAY
AVENUE, CARLSBAD CA 92008-7314, PRIOR TO THE TIME SET FOR OPENING. 2. PRICES All prices and notations must be in ink or typewritten. Mistakes may be crossed out and corrections typed or written with ink next to them. Such modifications must be initialed in ink by the person signing the bid.
Bids shall indicate the unit price extended to indicate the total price for each item bid. Any difference between the unit price correctly extended and the total price shown for all items bid shall be resolved in favor of the unit price, except when the Bidder clearly indicates that
the total price for all items bid is based on consideration of being awarded the entire lot, and that an adjustment of the total price is being made in consideration of receiving the entire bid.
Attachment B
Page 2 of 11
3. GUARANTEE OF GOOD FAITH (As required on Proposal Form)
Cash, uncertified personal and company checks and certificates of deposit are not acceptable as a guarantee of good faith. Each proposal must be accompanied by an unconditional certified check, or a bank or postal money order, or bid bond executed as surety by a corporation authorized to issue surety bonds in the State of California. Such check, money order or bond shall be made payable to the City of Carlsbad and shall be in the amount specified on the Proposal Form. If the Bidder fails to execute the contract within ten (10) days from the date of the City’s mailing of notice that the contract is ready for signature, the City will either award the contract to the next lowest Bidder or will reject all other bids and call for new bids. The Bidder who has failed to so execute the contract shall be liable to the City for the sum--not exceeding the amount of the check, money order or bond, by which the amount of the contract covering the proposal, executed by and between the City and a third party, may exceed the amount bid
by the original successful Bidder. Such portion of check, money order or bond as equals the sum shall be declared forfeited to the City of Carlsbad and shall be collected and paid to the City. The Bidder may also be subject to debarment or suspension.
IMPORTANT: Failure to furnish a proper guarantee of good faith with the bid when such is required will automatically void the bid.
4. ITEMS OFFERED If the item offered has a trade name, brand and/or catalog number, such shall be stated in the bid. If the Bidder proposes to furnish an item of a different manufacturer or vendor other than that mentioned in the bid specifications, Bidder must specify maker, brand, quality, catalog number, or other trade designation. Unless such is noted on the bid form, it will be deemed that the item offered is that designated in the bid specifications even though the bid may state "or equal". 5. SAMPLES
Samples, when required, shall be furnished prior to bid closing date and time, or within time specified in the bid. The City reserves the right to reject bids submitted without the required samples, or to require samples for alternate bids or items offered as "equals". Samples of items, when required, must be furnished free of expense to the City. If they are not destroyed by tests, samples will, upon request, be returned at the bidder's expense.
6. ALTERNATIVE PROPOSALS To be responsive to the bid, Bidder must submit a proposal that meets all specific bid requirements. Bidder may propose "equals" as provided for in accordance with Item 8 of these General Provisions. Once Bidder has proposed a product which is responsive to the specification, Bidder may thereafter include with the bid any additional proposals or alternative products that are not "equals" but that Bidder believes can or may meet or exceed City's requirements, and which offer City additional advantages or benefits based on the state of the art that were not, or could not, be contemplated by City when the requirements were prepared. The City reserves the right to evaluate and accept or reject such alternatives, as
though they were part of the original specifications, without advertising for further bids, or to re-advertise based on such proposed state of the art alternatives when in the best interests of the City. Any awards so made will be based on cost analysis considerations that result in the optimum economic advantage to the City.
Attachment B
Page 3 of 11
7. EXPIRATION OF BID
All bids shall be considered as firm for a period of ninety (90) calendar days, commencing the day following the date of bid closing and expiring at midnight of the last day, unless otherwise stated in the body of the solicitation. The Bidder may specify a date that the bid expires, provided the date is specific and is entered on the Proposal or Request for Bid form. 8. BRAND NAME Whenever reference to a specific brand name is made in this Request for Bid, it is illustrative and to be construed as a specification which describes a component that has been tested or evaluated by the City as best meeting the specific operational, design, performance,
maintenance, quality or reliability standards and requirements of the City, thereby incorporating these requirements by reference within the specification. An equivalent or "equal" may be offered by the Bidder, subject to testing and evaluation at the option of the
City or prior to and after the award of bid. The City reserves the sole right to reject a substituted component that will not fulfill requirements. It shall be the sole responsibility of the Bidder to provide at Bidder's expense any product information, test data, and other
information or documents the City may require to fully evaluate or demonstrate the acceptability of the offered substitute. Where appropriate, independent testing or evaluation at qualified test facilities, at Bidder's expense, including destructive testing, may be required as a condition of acceptance. 9. VERIFY BID PRICES Bidders must verify their price quotations prior to bid submission, as withdrawal or correction may not be permitted after the bid has been opened. 10. DELIVERY
A. Bidder shall state delivery terms on the Proposal Form unless already specified, in which case delivery shall be made within the time set forth. Where time is stated in a number of days, it shall include Saturdays, Sundays and holidays. Delivery is part of the consideration and must be adhered to as specified.
B. Bidder will not be held liable for failure to make delivery because of strikes, conscription of property, governmental regulations, acts of God, or any other cause beyond the bidder’s reasonable control; provided a written extension of time is obtained from the City Manager. C. All prices shall be F.O.B. destination. Bids other than F.O.B. destination shall be considered non-responsive and will be rejected. Prices shall include all freight, delivery and set-up charges. 11. FIRM PRICES AND PRICE ADJUSTMENT
Prices on bid shall be firm prices not subject to escalation. In the event the specifications provide for escalation, the maximum limit shall be shown, or the bid shall not be considered. In the event of a decline in market price(s) below the price(s) bid, the City of Carlsbad shall receive the benefit of such decline.
Attachment B
Page 4 of 11
Manufacturer's general price increases to the trade or industry may be passed on to the City.
Prices bid must be firm for the first ninety (90) days on an annual agreement; with a thirty (30) day notification of any price increases thereafter. If any price increase occurs, there will be a one (1) week, or one time, order protection provided at the last effective price. All price increases or notices must be in writing from not only the vendor but also the manufacturer. The City reserves the right NOT to accept the request. 12. TAXES Each bidder shall include all applicable sales taxes as a separate item in their bid. The amount of local city sales tax included in any bid submitted by a local (Carlsbad) vendor shall be credited by the City against said bid. The City is exempt from Federal Excise Tax.
13. MODIFICATION OR WITHDRAWAL OF BIDS
Bids may be modified or withdrawn by written notice received prior to the exact hour and date specified for receipt of bid. A bid may also be withdrawn in person by a Bidder, or the Bidder’s authorized representative, prior to the exact hour and date set for receipt of bids.
14. LATE BIDS AND MODIFICATIONS OR WITHDRAWALS Bids, modifications of bids, or withdrawals received at the office designated in the solicitation, after the exact hour and date specified for receipt, will not be considered. They will be rejected as a late bid and will be returned to bidder unopened. 15. NO BIDS If no bid is to be submitted, the bid should be marked "NO BID" and reason stated on the Proposal Form, which should be returned in order to maintain the Bidder's name in City's vendor
file for further solicitations. A letter or postcard may be submitted instead a blank proposal form. If a Bidder fails to respond to two Requests to Bid without returning a "NO BID" response, the Purchasing Officer reserves the right to delete the Bidder from the vendor file for future
solicitation. 16. CONFIDENTIAL INFORMATION
Any information deemed confidential or proprietary should be clearly identified by the Bidder as such. It will be protected and treated with confidentiality only to the extent permitted by California state law considering public information. Otherwise the information shall be considered a public record. Any data to be returned should be so marked and will be returned if not essential to the bid or contract record. 17. SIGNATURE All bids must be signed, with the firm named as indicated. A bid by a corporation must be signed by a duly authorized officer, employee or agent, with his or her title. Obligations assumed by
such signature must be fulfilled.
Attachment B
Page 5 of 11
18. QUALITY
Unless otherwise required in the specifications, all goods furnished shall be NEW and UNUSED and the BEST OF THEIR KIND. 19. LITIGATION WARRANTY The Bidder, by bidding, warrants that Bidder is not currently involved in litigation, arbitration, or an administrative proceeding concerning the materials, or Bidder's performance, concerning the same or similar material to be supplied pursuant to this contract or specification, and that no judgments, awards or administrative determinations have been made against Bidder, on the basis of Bidder's performance in supplying or installing the same or similar material, unless such fact is disclosed to the City in the bid. Disclosure will not disqualify the Bidder. The City
reserves the right to evaluate bids, on the basis of the facts surrounding such litigation, arbitration, or administrative proceeding and to require Bidder to furnish the City with a surety bond executed by a surety company authorized to do business in the State of California and
approved by the City of Carlsbad, in a sum equal to one hundred percent (100%) of the contract price, conditional on the faithful performance by Bidder of the contract, in the event the bid is awarded to Bidder, notwithstanding the litigation, arbitration, or administrative proceeding.
20. ROYALTIES, LICENSES AND PATENTS Unless otherwise specified, the Bidder shall pay all royalties, license and patent fees. The Bidder warrants that the materials to be supplied do not infringe any patent, trademark or copyright, and further agrees to defend any and all suits, actions and claims for infringement that are brought against the City, and to defend, indemnify and hold harmless the City from all loss or damages whether general, exemplary or punitive, as a result of any actual or claimed infringement asserted against the City, the Bidder, or those furnishing material to Bidder pursuant to this contract.
21. PERFORMANCE STANDARDS Performance of work, and acceptability of equipment or materials supplied, pursuant to any contract or award, shall be to the satisfaction of the City. 22. WARRANTIES
A. All material, labor or equipment provided under the contract shall be warranted by Bidder, and/or manufacturer, for at least twelve (12) months after final acceptance by City, except automotive equipment which will be warranted for a minimum 12,000 miles or 12 months, whichever occurs first. Greater warranty protection will be accepted. Lesser warranty protection must be indicated by Bidder on the bid proposal as an exception. B. Bidder shall be considered primarily responsible to the City for all warranty service, parts and labor applicable to the goods or equipment provided by Bidder under this bid or award, irrespective of whether Bidder is an agent, broker, fabricator or manufacturer's dealer. Bidder shall be responsible for ensuring that warranty work is performed at a local agency
or facility convenient to City and that services, parts and labor are available and provided to meet City's schedules and deadlines. City may require Bidder to post a performance bond after contract award to guarantee performance of these obligations. Bidder may
Attachment B
Page 6 of 11
establish a service contract with a local agency satisfactory to City, to meet this obligation if Bidder does not ordinarily provide warranty service.
23. ADDENDA The effect of all addenda to the bid documents shall be considered in the bid, and said addenda shall be made part of the bid documents and shall be returned with them. Before submitting a bid, each Bidder shall ascertain whether or not any addenda have been issued, and failure to cover in this bid any such addenda issued, may render the bid invalid and result in its rejection. 24. SPECIFICATIONS TO PREVAIL The detailed requirements of the specifications shall supersede any specific requirement of
these General Provisions which are in conflict therewith. The City reserves the right of being sole judge of bid meeting specifications. Requests for interpretation of bid specifications shall be made in writing to the Purchasing Officer at least five days prior to the date of the bid
opening. 25. FAITHFUL PERFORMANCE BOND
The successful Bidder may be required to furnish the City with security for the faithful performance of the contract, in a sum up to One Hundred Percent (100%) of the amount of the contract price. This security may take the form of a bond executed by a surety company authorized to do business in the State of California and approved by the City or Carlsbad, or a money order or certified check drawn on a solvent bank. Such bond or deposit shall be forfeited to the City in the event the Bidder fails or refused to fulfill the requirements and all terms and conditions of the contract. 26. AWARD OF CONTRACT
A. Bids will be analyzed and the award will be based on the best value to the City. The decision will be based on objective and other predetermined criteria as set forth in the Invitation to Bid. Factors to be considered include, but are not limited to: cost, conformance to the solicitation, supplier’s qualifications, past performance, customer service and warranties.
B. The City reserves the right to perform a pre-award survey of the bidder to determine capability to perform, including but not limited to, facilities, financial responsibility, materials/supplies, and past performance. The determination of the City as to the bidder's prospective ability to perform the contract shall be conclusive. C. The City reserves the right to reject any item or items therein; to waive informalities, technical defects and minor irregularities in bids received; and to select the bid(s) deemed most advantageous to the City. The City will however consider bids submitted on an "all or nothing" basis if the bid is clearly designated as such. D. The City reserves the right to award one or more contracts on the bids submitted, whether
by award of all items to one Bidder, or by award of separate items or groups of items to various Bidders, as the interests of the City may require, unless the Bidder clearly specifies otherwise in his bid.
Attachment B
Page 7 of 11
E. Upon acceptance by the City of Carlsbad, the solicitation, bid, proposal, or price quotation, and a purchase order issued to the successful Bidder within the time specified, shall be
deemed to result in a binding contract without further action required by either party. Items are to be furnished as described in the bid and in strict conformity with all instructions, conditions, specifications and drawings contained in the complete contract. 27. DOCUMENTATION Due to the time constraints that affect contract performance, all required documents, certificates of insurance and bonds or deposits shall be provided to the City (Attention: Purchasing Department) within ten (10) days following award, or date of request, by City, whichever is later. Any failure to comply may result in bid being declared non-responsive and rejected, and/or at City's option the bid bond will be attached for damages suffered.
28. PURCHASE ORDERS
All goods and services will be ordered by means of a Purchase Order. (THE CITY WILL NOT BE RESPONSIBLE FOR ARTICLES OR SERVICES FURNISHED WITHOUT A PURCHASE ORDER.)
29. SELLER'S INVOICE Invoices shall be prepared and submitted in duplicate to: Accounts Payable, City of Carlsbad, 1635 Faraday Avenue, Carlsbad, CA 92008-7314. Separate invoices are required for each Purchase Order. Invoices shall contain the following information: Purchase Order number, item number, description of supplies or services, sizes, units of measure, quantities, unit prices and extended totals. 30. INSPECTION AND ACCEPTANCE
Inspection and final acceptance will be at destination unless specified otherwise, and will be made by the City department shown in the "Ship To:" address or other duly authorized representative of the City. Until delivery and final acceptance, and after any rejection, risk of loss will be on the Bidder, unless loss results from the sole negligence of the City. 31. LOST AND DAMAGED SHIPMENTS
Risk of loss or damage to items prior to the time of their receipt and final acceptance by the City is upon the Bidder. The City has no obligation to accept damaged shipments and reserves the right to return, at the Bidder's expense, damaged merchandise even if the damage was not apparent or discovered until after receipt of the items. 32. LATE SHIPMENTS Bidder is responsible to notify the City department receiving the items and the Purchasing Officer, of any late or delayed shipments. The City reserves the right to cancel all or any part of an order if the shipment is not made as promised.
Attachment B
Page 8 of 11
33. COMPLIANCE WITH INDUSTRIAL SAFETY CODES
All equipment, instruction manuals, spare parts and other items furnished shall, where applicable, conform with the Safety Orders of the California Division of Industrial Safety. Material Safety Data Sheets (MSDS) shall be supplied, for each applicable item, with the initial order. All containers shall be labeled per OSHA specifications. 34. WAIVER The failure of the City to enforce a particular condition or provision of any contract awarded hereunder shall not constitute a waiver of that provision or condition or its enforceability by the City.
35. CONSEQUENCES OF VIOLATIONS OF LAW REGARDING ANTI-COMPETITIVE
BUSINESS PRACTICES OR UNFAIR TRADE PRACTICES
Any acts or omissions of Bidder in violation of federal, state or municipal law, or City policies and regulations regarding anti-competitive practices, unfair trade practices, collusion, contingent fees, gratuities, kickbacks, contemporaneous employment or similar violations
creating an unfair influence on the public bidding and award process, pertaining to this contract or proposal, may void this contract. In addition to all other remedies or damages allowed by law, Bidder shall be liable to City for all damages City thereby suffers or incurs, including costs for substitute performance, and may also be subject to debarment. 36. CONFLICT OF INTEREST No employee, or member of the employee's immediate family, or elected or appointed member of City government, may participate directly or indirectly in the procurement process pertaining to this bid, if they:
A. Have a financial interest, or other personal interest, which is incompatible with the proper discharge of their official duties in the public interest, or would tend to impair their independence, judgment or action in the performance of their official duties. B. Are negotiating for, or have an arrangement concerning, prospective employment with Bidder.
The Bidder warrants to the best of his knowledge that the submission of the bid will not create such conflict of interest. In the event such a conflict occurs, the Bidder is to report it immediately to the Purchasing Officer. For breach or violation of this warranty, the City shall have the right to annul this contract, at its discretion, without liability. Bidder may also be subject to damages and/or debarment or suspension. 37. CITY PROVISIONS TO PREVAIL Except as specified in the specifications, the City's standard General Provisions shall govern any contract award. Any standard terms and conditions of Bidder, submitted by Bidder, shall
not be acceptable to City unless expressly assented to by City by separate documents. The City reserves the right to reject Bidder's bid as non-responsive, to consider the bid without Bidder's standard terms and conditions, or to require Bidder to delete reference to such, as a condition of evaluation or award of the bid. If, after award of contract, Bidder (contract vendor)
Attachment B
Page 9 of 11
shall provide materials, or services, accompanied by new or additional standard terms or conditions, they too shall be considered void, and City may require deletion thereof as a further
condition of performance by vendor. To the extent not otherwise provided for by the contract documents, the California Commercial Code shall apply. 38. AMENDMENTS AND MODIFICATIONS The Purchasing Officer may at any time, by a written order, and without notice to the sureties, make a modification to the contract or an amendment to the Purchase Order, within the general scope of this contract, in (1) drawings, designs, or specifications, where the supplies to be furnished are to be specially manufactured for the City in accordance therewith; (2) method of shipment or packing; and (3) place of delivery. If any such change causes an increase or decrease in the cost of, or the time required for, performance of this contract, whether changed
or not changed by any such order, an equitable adjustment shall be made by written modification of the contract or amendment to the Purchase Order. Any claim by the Bidder for adjustment under this clause must be asserted within 30 days from the date of receipt by the
Bidder of the notification; provided that, if Purchasing Officer decides that the facts justify such action, the Purchasing Officer may receive and act upon any such claim, if asserted prior to final payment under this contract. Failure to agree to any adjustment shall be a dispute,
concerning a question of fact, within the meaning of the clause of these provisions entitled "Disputes". However, nothing in this clause shall excuse the Bidder from proceeding with the contract as changed. 39. DISPUTES Except as otherwise provided in this contract, any dispute concerning a question of fact arising under this contract, which is not disposed of by agreement, shall be decided by the Purchasing Officer, who shall reduce this decision to writing or mail or otherwise furnish a copy thereof to the Bidder. The decision of the Purchasing Officer shall be final and conclusive unless, within 30 days from the date of receipt of such copy, the Bidder mails or otherwise furnishes to the
Purchasing Officer a written appeal addressed to the City Manager. The decision of the City Manager, or his duly authorized representative for the determination of such appeals, shall be final and conclusive. In connection with any appeal proceeding under this clause, the Bidder shall be afforded an opportunity to be heard and to offer evidence in support of the Bidder’s appeal. Pending final decision of a dispute hereunder, the Bidder shall proceed diligently with the performance of the contract, and in accordance with the Purchasing Officer's decision.
40. TERMINATION FOR DEFAULT A. The City of Carlsbad, California, hereafter referred to as the City may by written notice of default to the Bidder (subject to the provisions of paragraph (C) below) terminate the whole or any part of this contract, in any one of the two following circumstances: 1. If the Bidder fails to make delivery of the supplies or to perform the services, within the time specified herein, or any extension thereof; or 2. If the Bidder fails to perform any of the other provisions of this contract, or so fails
to make progress to endanger performance of this contract in accordance with its terms, and in either of these two circumstances does not cure such failure within a period of ten (10) days after receipt of notice from the Purchasing Officer specifying such failure.
Attachment B
Page 10 of 11
B. In the event the City terminates this contract, in whole or in part, as provided in paragraph
(A) of this clause, the City may procure, upon such terms and in such manner as the Purchasing Officer may deem appropriate, supplies or services similar to those so terminated, and the Bidder shall be liable to the City for any excess costs for such similar supplies or services; provided, that the Bidder shall continue the performance of this contract to the extent not terminated under the provisions of this clause. C. The Bidder shall not be liable for any excess costs, if the failure to perform the contract arises out of causes beyond the control and without the fault or negligence of the Bidder. Such causes may include, but are not restricted to, acts of God or of the public enemy, acts of the City in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restriction, strikes, freight embargoes, and unusually severe
weather; but in every case the failure to perform must be beyond the control and without the fault or negligence of the Bidder.
D. If, after notice of termination of this contract under the provisions of this clause, it is determined for any reason that the Bidder was not in default under the provisions of this clause, or that the default was excusable under the provisions of this clause, the rights
and obligations of the Bidder shall be the same as if notice of termination for convenience had been issued pursuant to such clause. 41. TERMINATION FOR CONVENIENCE The Purchasing Officer, by written notice, may terminate this contract, in whole or in part, when it is in the best interest of the City. If this contract is for supplies and is so terminated, the Bidder shall be compensated in accordance with his auditable costs to point of Notification of Termination. To the extent that this contract is for services and is so terminated, the City shall be liable only for payment in accordance with the payment provisions of this contract, for the actual services rendered to the effective date of termination.
42. LABOR PRACTICES The Bidder shall comply with all Federal and State Laws, and City Ordinances where applicable, relating to fair labor practices and discrimination in the employment of persons.
43. INSURANCE Unless otherwise provided, Bidder shall cause City to be named as an additional insured on liability and/or products liability insurance concerning Bidder's performance, products, or equipment in amounts, scope and duration as may be required by the Purchasing Officer. Bidder shall provide evidence of Workers' Compensation Insurance covering all employees. 44. LIABILITY AND INDEMNIFICATION Bidder agrees to defend, indemnify, protect and hold City, and its agents, officers and employees, harmless from and against any and all claims asserted, or liability established for
damages or injuries to any person or property, including injury to Bidder's employees, agents or officers which arise from or are connected with, or are caused or claimed to be caused by the acts or omissions of Bidder, and its agents, officers or employees, in performing the work or services or supplying the materials or equipment herein, and all expenses of investigating
Attachment B
Page 11 of 11
and defending against same; provided, however, that Bidder's duty to indemnify and hold harmless shall not include any claims or liability arising from the established sole negligence
or willful misconduct of the City, its agents, officers or employees. This shall not prejudice the right of the City to appear in such suit, participate in the defense, and take such actions as may be necessary to protect the interests of the City. 45. EQUAL OPPORTUNITY POLICY The City of Carlsbad will not discriminate with regard to race, religious creed, color, national origin, ancestry, disability, marital status, veteran’s status, sex, or sexual orientation or age in the award of contracts. 46. ANNUAL APPROPRIATION OF FUNDS
Multi-year term supply and service contracts and leases are subject to annual appropriation of funds by the City Council. Payments made under term contracts and leases are considered
items of current expense. Purchase Orders are funded when issued, therefore are current expense items and are not subject to any subsequent appropriation of funds.
In the event sufficient funds are not appropriated for the payment of lease payments, or anticipated term contract payments, required to be paid in the next occurring lease or contract term, and if no funds are legally available from other sources, the lease or contract may be terminated at the end of the original term or renewal term and the City shall not be obligated to make further payments beyond the then current original or renewal term. The City will provide notice of its inability to continue the lease or contract at such time as the Purchasing Officer is aware of the non-appropriation of funds. However, failure to notify does not renew the term of the lease or contract. If a lease is canceled, the events of default will occur as described in the lease and/or Item 40 of these General Provisions. The City has no monetary obligation in event of termination or reduction of a term contract, since such contracts represent estimated quantities and are not funded as a contract except to the extent of the Purchase Orders already
issued. 47. TEN PERCENT (10%) RETENTION The City reserves the right to withhold a ten percent (10%) retention on all Purchase orders until the supplies, services or equipment have been accepted.
48. QUANTITIES Estimated quantities are given as a basis for comparison of bids. The City does not, expressly or by implications, agree that the actual quantities will be purchased.
ATTACHMENT C: SAMPLE MASTER SOFTWARE AND SERVICE AGREEMENT
[Remainder of this page intentionally left blank]
General Counsel Approved Version 6/12/18 1
SAMPLE ONLY – DO NOT COMPLETE
MASTER AGREEMENT FOR SOFTWARE AND SERVICES
(NAME OF CONTRACTOR)
THIS AGREEMENT is made and entered into as of the ______________ day of ___________________, 20___, by and between the CARLSBAD MUNICIPAL WATER DISTRICT, a Public Agency organized under the Municipal Water Act of 1911, and a Subsidiary
District of the City of Carlsbad, ("CMWD"), and ______________________________, a _______________, ("Contractor").
RECITALS
A. CMWD requires the professional services of a _______________________________ that is experienced in _______________. B. Contractor has the necessary experience in providing professional services and advice related to ___________________________. C. Contractor has submitted a proposal to CMWD and has affirmed its willingness and ability to perform such work.
NOW, THEREFORE, in consideration of these recitals and the mutual covenants contained herein, CMWD and Contractor agree as follows:
1. SCOPE OF WORK CMWD retains Contractor to perform, and Contractor agrees to render, those services (the
"Services") that are defined in attached Exhibit "A", which is incorporated by this reference in accordance with this Agreement’s terms and conditions.
2. STANDARD OF PERFORMANCE While performing the Services, Contractor will exercise the reasonable professional care and skill customarily exercised by reputable members of Contractor's profession practicing in the
Metropolitan Southern California Area, and will use reasonable diligence and best judgment while exercising its professional skill and expertise.
3. TERM The term of this Agreement will be effective for a period of ________ from the date first above
written. The Executive Manager may amend the Agreement to extend it for ____ additional ______ year periods or parts thereof. Extensions will be based upon a satisfactory review of Contractor's performance, CMWD needs, and appropriation of funds by the CMWD Board of
Directors. The parties will prepare a written amendment indicating the effective date and length of the extended Agreement.
4. TIME IS OF THE ESSENCE Time is of the essence for each and every provision of this Agreement.
5. COMPENSATION The total fee payable for the Services to be performed during the initial Agreement term will be ____________ dollars ($_________). No other compensation for the Services will be allowed
except for items covered by subsequent amendments to this Agreement. If the City elects to extend the Agreement, the amount shall not exceed ________________________________________ dollars ($_________) per Agreement year.
General Counsel Approved Version 6/12/18 2
CMWD reserves the right to withhold a ten percent (10%) retention until CMWD has accepted the work and/or Services specified in Exhibit "A".
Incremental payments, if applicable, should be made as outlined in attached Exhibit "A".
6. STATUS OF CONTRACTOR Contractor will perform the Services in Contractor's own way as an independent contractor and in pursuit of Contractor's independent calling, and not as an employee of CMWD. Contractor will
be under control of CMWD only as to the result to be accomplished, but will consult with CMWD as necessary. The persons used by Contractor to provide services under this Agreement will not be considered employees of CMWD for any purposes.
The payment made to Contractor pursuant to the Agreement will be the full and complete compensation to which Contractor is entitled. CMWD will not make any federal or state tax withholdings on behalf of Contractor or its agents, employees or subcontractors. CMWD will not be required to pay any workers' compensation insurance or unemployment contributions on behalf of Contractor or its employees or subcontractors. Contractor agrees to indemnify CMWD and the City of Carlsbad within thirty (30) days for any tax, retirement contribution, social security, overtime payment, unemployment payment or workers' compensation payment which
CMWD may be required to make on behalf of Contractor or any agent, employee, or subcontractor of Contractor for work done under this Agreement. At CMWD’s election, CMWD may deduct the indemnification amount from any balance owing to Contractor.
7. SUBCONTRACTING Contractor will not subcontract any portion of the Services without prior written approval of
CMWD. If Contractor subcontracts any of the Services, Contractor will be fully responsible to CMWD for the acts and omissions of Contractor's subcontractor and of the persons either directly or indirectly employed by the subcontractor, as Contractor is for the acts and omissions
of persons directly employed by Contractor. Nothing contained in this Agreement will create any contractual relationship between any subcontractor of Contractor and CMWD. Contractor will be responsible for payment of subcontractors. Contractor will bind every subcontractor and every subcontractor of a subcontractor by the terms of this Agreement applicable to Contractor's work unless specifically noted to the contrary in the subcontract and approved in writing by CMWD.
8. OTHER CONTRACTORS CMWD reserves the right to employ other Contractors in connection with the Services.
9. INDEMNIFICATION Contractor agrees to indemnify and hold harmless CMWD and the City of Carlsbad, their
officers, officials, employees and volunteers from and against all claims, damages, losses and expenses including attorneys fees arising out of the performance of the work described herein caused by any negligence, recklessness, or willful misconduct of the Contractor, any
subcontractor, anyone directly or indirectly employed by any of them or anyone for whose acts any of them may be liable.
The parties expressly agree that any payment, attorney’s fee, costs or expense CMWD or the City of Carlsbad incurs or makes to or on behalf of an injured employee under the their self-administered workers’ compensation is included as a loss, expense or cost for the purposes of
this section, and that this section will survive the expiration or early termination of this Agreement.
General Counsel Approved Version 6/12/18 3
10. INSURANCE Contractor will obtain and maintain for the duration of the Agreement and any and all
amendments, insurance against claims for injuries to persons or damage to property which may arise out of or in connection with performance of the services by Contractor or Contractor’s agents, representatives, employees or subcontractors. The insurance will be obtained from an
insurance carrier admitted and authorized to do business in the State of California. The insurance carrier is required to have a current Best's Key Rating of not less than "A-:VII"; OR with a surplus line insurer on the State of California’s List of Approved Surplus Line Insurers
(LASLI) with a rating in the latest Best’s Key Rating Guide of at least “A:X”; OR an alien non-admitted insurer listed by the National Association of Insurance Commissioners (NAIC) latest quarterly listings report.
10.1 Coverages and Limits. Contractor will maintain the types of coverages and minimum limits indicated below, unless the Risk Manager or Executive Manager approves a lower amount. These minimum amounts of coverage will not constitute any limitations or cap on Contractor's indemnification obligations under this Agreement. CMWD, its officers, agents and employees make no representation that the limits of the insurance specified to be carried by Contractor pursuant to this Agreement are adequate to protect Contractor. If Contractor believes that any required insurance coverage is
inadequate, Contractor will obtain such additional insurance coverage, as Contractor deems adequate, at Contractor's sole expense. The full limits available to the named insured shall also be available and applicable to CMWD as an additional insured.
10.1.1 Commercial General Liability (CGL) Insurance. Insurance written on an “occurrence” basis, including personal & advertising injury, with limits no less than $2,000,000
per occurrence. If a general aggregate limit applies, either the general aggregate limit shall apply separately to this project/location or the general aggregate limit shall be twice the required occurrence limit.
10.1.2 Automobile Liability (if the use of an automobile is involved for Contractor's
work for CMWD). $2,000,000 combined single-limit per accident for bodily injury and property damage. 10.1.3 Workers' Compensation and Employer's Liability. Workers' Compensation limits as required by the California Labor Code. Workers' Compensation will not be required if
Contractor has no employees and provides, to CMWD's satisfaction, a declaration stating this. 10.1.4 Professional Liability. Errors and omissions liability appropriate to
Contractor’s profession with limits of not less than $1,000,000 per claim. Coverage must be maintained for a period of five years following the date of completion of the work.
10.2. Additional Provisions. Contractor will ensure that the policies of insurance required under this Agreement contain, or are endorsed to contain, the following provisions:
10.2.1 CMWD will be named as an additional insured on Commercial General Liability which shall provide primary coverage to CMWD.
10.2.2 Contractor will obtain occurrence coverage, excluding Professional Liability, which will be written as claims-made coverage.
General Counsel Approved Version 6/12/18 4
10.2.3 This insurance will be in force during the life of the Agreement and any extensions of it and will not be canceled without thirty (30) days prior written notice to CMWD
sent by certified mail pursuant to the Notice provisions of this Agreement. 10.3 Providing Certificates of Insurance and Endorsements. Prior to CMWD's execution of
this Agreement, Contractor will furnish certificates of insurance and endorsements to CMWD. 10.4 Failure to Maintain Coverage. If Contractor fails to maintain any of these insurance
coverages, then CMWD will have the option to declare Contractor in breach, or may purchase replacement insurance or pay the premiums that are due on existing policies in order to maintain the required coverages. Contractor is responsible for any payments made by CMWD
to obtain or maintain insurance and CMWD may collect these payments from Contractor or deduct the amount paid from any sums due Contractor under this Agreement. 10.5 Submission of Insurance Policies. CMWD reserves the right to require, at anytime, complete and certified copies of any or all required insurance policies and endorsements.
11. BUSINESS LICENSE Contractor will obtain and maintain a City of Carlsbad Business License for the term of the
Agreement, as may be amended from time-to-time. 12. ACCOUNTING RECORDS
Contractor will maintain complete and accurate records with respect to costs incurred under this Agreement. All records will be clearly identifiable. Contractor will allow a representative of CMWD during normal business hours to examine, audit, and make transcripts or copies of
records and any other documents created pursuant to this Agreement. Contractor will allow inspection of all work, data, documents, proceedings, and activities related to the Agreement for a period of three (3) years from the date of final payment under this Agreement.
13. OWNERSHIP OF DOCUMENTS All work product produced by Contractor or its agents, employees, and subcontractors pursuant
to this Agreement is the property of CMWD. In the event this Agreement is terminated, all work product produced by Contractor or its agents, employees and subcontractors pursuant to this Agreement will be delivered at once to CMWD. Contractor will have the right to make one (1) copy of the work product for Contractor’s records.
14. COPYRIGHTS Contractor agrees that all copyrights that arise from the services will be vested in CMWD and Contractor relinquishes all claims to the copyrights in favor of CMWD.
15. NOTICES The name of the persons who are authorized to give written notices or to receive written notice
on behalf of CMWD and on behalf of Contractor under this Agreement.
For CMWD For Contractor
Name Name
Title Title
Carlsbad Municipal Water District Address
Address
General Counsel Approved Version 6/12/18 5
Phone
Phone E-mail Each party will notify the other immediately of any changes of address that would require any
notice or delivery to be directed to another address.
16. CONFLICT OF INTEREST
Contractor shall file a Conflict of Interest Statement with the City Clerk in accordance with the requirements of the City of Carlsbad Conflict of Interest Code. The Contractor shall report investments or interests in all categories. Yes No
17. GENERAL COMPLIANCE WITH LAWS Contractor will keep fully informed of federal, state and local laws and ordinances and regulations which in any manner affect those employed by Contractor, or in any way affect the performance of the Services by Contractor. Contractor will at all times observe and comply with these laws, ordinances, and regulations and will be responsible for the compliance of
Contractor's services with all applicable laws, ordinances and regulations. Contractor will be aware of the requirements of the Immigration Reform and Control Act of 1986
and will comply with those requirements, including, but not limited to, verifying the eligibility for employment of all agents, employees, subcontractors and consultants that the services required by this Agreement.
18. DISCRIMINATION AND HARASSMENT PROHIBITED Contractor will comply with all applicable local, state and federal laws and regulations prohibiting
discrimination and harassment. 19. DISPUTE RESOLUTION If a dispute should arise regarding the performance of the Services the following procedure will be used to resolve any questions of fact or interpretation not otherwise settled by agreement
between the parties. Representatives of Contractor or CMWD will reduce such questions, and their respective views, to writing. A copy of such documented dispute will be forwarded to both parties involved along with recommended methods of resolution, which would be of benefit to
both parties. The representative receiving the letter will reply to the letter along with a recommended method of resolution within ten (10) business days. If the resolution thus obtained is unsatisfactory to the aggrieved party, a letter outlining the disputes will be forwarded
to the Executive Manager. The Executive Manager will consider the facts and solutions recommended by each party and may then opt to direct a solution to the problem. In such cases, the action of the Executive Manager will be binding upon the parties involved, although
nothing in this procedure will prohibit the parties from seeking remedies available to them at law. 20. TERMINATION
In the event of the Contractor's failure to prosecute, deliver, or perform the Services, CMWD may terminate this Agreement for nonperformance by notifying Contractor by certified mail of the termination. If CMWD decides to abandon or indefinitely postpone the work or services
contemplated by this Agreement, CMWD may terminate this Agreement upon written notice to Contractor. Upon notification of termination, Contractor has five (5) business days to deliver any documents owned by CMWD and all work in progress to CMWD address contained in this
General Counsel Approved Version 6/12/18 6
Agreement. CMWD will make a determination of fact based upon the work product delivered to CMWD and of the percentage of work that Contractor has performed which is usable and of
worth to CMWD in having the Agreement completed. Based upon that finding CMWD will determine the final payment of the Agreement.
Either party upon tendering thirty (30) days written notice to the other party may terminate this Agreement. In this event and upon request of CMWD, Contractor will assemble the work product and put it in order for proper filing and closing and deliver it to CMWD. Contractor will be
paid for work performed to the termination date; however, the total will not exceed the lump sum fee payable under this Agreement. CMWD will make the final determination as to the portions of tasks completed and the compensation to be made.
21. COVENANTS AGAINST CONTINGENT FEES Contractor warrants that Contractor has not employed or retained any company or person, other than a bona fide employee working for Contractor, to solicit or secure this Agreement, and that Contractor has not paid or agreed to pay any company or person, other than a bona fide employee, any fee, commission, percentage, brokerage fee, gift, or any other consideration contingent upon, or resulting from, the award or making of this Agreement. For breach or violation of this warranty, CMWD will have the right to annul this Agreement without liability, or,
in its discretion, to deduct from the Agreement price or consideration, or otherwise recover, the full amount of the fee, commission, percentage, brokerage fees, gift, or contingent fee.
22. CLAIMS AND LAWSUITS By signing this Agreement, Contractor agrees that any agreement claim submitted to CMWD must be asserted as part of the agreement process as set forth in this Agreement and not in
anticipation of litigation or in conjunction with litigation. Contractor acknowledges that if a false claim is submitted to CMWD, it may be considered fraud and Contractor may be subject to criminal prosecution. Contractor acknowledges that California Government Code sections
12650 et seq., the False Claims Act applies to this Agreement and, provides for civil penalties where a person knowingly submits a false claim to a public entity. These provisions include false claims made with deliberate ignorance of the false information or in reckless disregard of the truth or falsity of information. If CMWD seeks to recover penalties pursuant to the False Claims Act, it is entitled to recover its litigation costs, including attorney's fees. Contractor acknowledges that the filing of a false claim may subject Contractor to an administrative debarment proceeding as the result of which Contractor may be prevented to act as a Contractor on any public work or improvement for a period of up to five (5) years. Contractor
acknowledges debarment by another jurisdiction is grounds for CMWD to terminate this Agreement.
23. JURISDICTION AND VENUE Any action at law or in equity brought by either of the parties for the purpose of enforcing a right or rights provided for by this Agreement will be tried in a court of competent jurisdiction in the
County of San Diego, State of California, and the parties waive all provisions of law providing for a change of venue in these proceedings to any other county.
24. SUCCESSORS AND ASSIGNS It is mutually understood and agreed that this Agreement will be binding upon CMWD and Contractor and their respective successors. Neither this Agreement nor any part of it nor any
monies due or to become due under it may be assigned by Contractor without the prior consent of CMWD, which shall not be unreasonably withheld.
General Counsel Approved Version 6/12/18 7
25. ENTIRE AGREEMENT This Agreement, together with any other written document referred to or contemplated by it,
along with the purchase order for this Agreement and its provisions, embody the entire Agreement and understanding between the parties relating to the subject matter of it. In case of conflict, the terms of the Agreement supersede the purchase order. Neither this Agreement nor
any of its provisions may be amended, modified, waived or discharged except in a writing signed by both parties.
26. AUTHORITY The individuals executing this Agreement and the instruments referenced in it on behalf of Contractor each represent and warrant that they have the legal power, right and actual authority
to bind Contractor to the terms and conditions of this Agreement. CONTRACTOR CARLSBAD MUNICIPAL WATER DISTRICT, a Public Agency organized under the Municipal Water Act of 1911, and a Subsidiary District of the City of Carlsbad
By: By:
(sign here) President or Executive Manager or Division Director as authorized by the
Executive Manager
(print name/title)
ATTEST:
By:
(sign here) BARBARA ENGLESON
Secretary
(print name/title)
If required by CMWD, proper notarial acknowledgment of execution by contractor must be
attached. If a corporation, Agreement must be signed by one corporate officer from each of the following two groups.
Group A Group B Chairman, Secretary, President, or Assistant Secretary, Vice-President CFO or Assistant Treasurer
Otherwise, the corporation must attach a resolution certified by the secretary or assistant secretary under corporate seal empowering the officer(s) signing to bind the corporation.
APPROVED AS TO FORM: CELIA A. BREWER, General Counsel
By:_____________________________ Assistant General Counsel
General Counsel Approved Version 6/12/18 8
EXHIBIT “A”
SCOPE OF SERVICES Itemized List of what Contractor will do for CMWD and at what price.
City of Carlsbad / CMWD SCADA Master Plan
H-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix H: PLC Hardware RFP
REQUEST FOR PROPOSALS FOR A MASTER PURCHASE AND
SERVICE AGREEMENT FOR THE
PROGRAMMABLE LOGIC CONTROLLER
RFP19-481UTIL
City of Carlsbad
Carlsbad Municipal Water District
1635 Faraday Avenue
Carlsbad, CA 92008
July 2018
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 1 of 11
NOTICE INVITING PROPOSALS
The City of Carlsbad (City) and the Carlsbad Municipal Water District (CMWD), a subsidiary district to the
City of Carlsbad, are soliciting proposals for Human Machine Interface (HMI) and Programmable Control
Logic (PLC) systems on which to standardize the water, recycled water, and sewer Supervisory Control and
Data Acquisition (SCADA) systems. To achieve this, City/CMWD is concurrently conducting the separate
Request for Proposals (RFP) process to standardize on a manufacturer for both the HMI and PLC and enter
into negotiations for a long-term agreement with each of the selected manufacturers.
This RFP is specifically for the PLC. The companion RFP for the HMI may be found on the City/CMWD’s bid
website. Proposals may be submitted on one or both systems, but separate proposals are required.
City/CMWD anticipate that a manufacturer’s authorized distributor may be working in close coordination
with the respective manufacturer, but the final agreement will be executed directly with the
manufacturer, or provisions must be provided by the manufacturer to guarantee the agreement for its
full term, regardless of a change in the manufacturer’s authorized distributor.
Until 2:00 pm PST on August 23, 2018, the City/CMWD shall accept sealed proposals, clearly marked as
such, at the location identified in instructions. The envelope enclosing the proposal shall be sealed, and
delivered or mailed to the City of Carlsbad.
A non-mandatory pre-proposal meeting will be held at the date and time specified in the RFP schedule at
5950 El Camino Real, Carlsbad, CA 92008.
All questions regarding this RFP shall be submitted in writing, via email, prior to the deadline specified in
the RFP schedule. The RFP number must be referenced in the email title, and addressed solely to.
Graham Jordan, Contract Administrator
PWContractAdmin@carlsbadca.gov
Key dates for the RFP schedule are included in the following table. A more detailed schedule is provided
in the RFP.
ACTIVITY SCHEDULE
RFP Issued July 18, 2018
Pre-Proposal Meeting August 2, 2018, 2:00 PM PST
Deadline for questions August 10, 2018, 5:00 PM PST
Final Q&A and/or addendum issued August 16, 2018
Proposals due August 23, 2:00 PM PST
A Selection Committee will evaluate the proposals using established review criteria. During the evaluation
process, City/CMWD reserves the right, where it may serve City/CMWD’s best interest, to request
additional information or clarifications from firms submitting proposals. Upon completion of the
evaluation process, a long-term services agreement will be negotiated. The contract will be approved by
the City Council/Board of Directors and will be administered through staff at City/CMWD. Details for are
provided in the RFP.
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 2 of 11
City/CMWD reserves the right to retain all proposals submitted and to use any ideas in a proposal
regardless of whether that proposal is selected. By submitting a proposal, the firm is providing a guarantee
to the city that, if chosen, they will be able to provide the proposed services during the period of time
discussed in this Request for Proposal (RFP). There is no expressed or implied obligation for City/CMWD
to reimburse responding firms for any expenses incurred in preparing proposals in response to this
request. City/CMWD reserves the right to reject any or all proposals for any reason and seek new
proposals or take other action.
This RFP contains instructions governing the proposals to be provided, requirements which must be met
for eligibility consideration and general evaluation criteria. Proposals should be simple and economical,
providing a straight-forward and concise description of the proposer’s ability to meet the requirements
specified in this RFP.
For this RFP, the proposal must remain valid for at least ninety (90) days. Additionally, the contents of the
proposal of the successful bidder shall become the basis for the contractual obligations when a contract
is awarded. The payment amount for the services to be rendered will be negotiated with the firm selected
and said firm will be required to enter into a formal agreement with City/CMWD. City/CMWD reserves
the right to delete or amend any of the services as listed and described in this RFP.
If a satisfactory contract cannot be negotiated, negotiations will be formally terminated. Contract
negotiation will then begin with the next alternate proposer.
We look forward to your response.
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 3 of 11
TABLE OF CONTENTS
1. Purpose
2. Background
3. Instructions to Proposers
4. Attachments
A. Evaluation Criteria
B. General Provisions
C. Sample Master Purchase and Service Agreement
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 4 of 11
SECTION 1: PURPOSE
The City of Carlsbad (City) and Carlsbad Municipal Water District (CMWD), collectively called City/CMWD
or Owner, have initiated a master planning effort to evaluate and upgrade the Supervisory Control and
Data Acquisition (SCADA) elements for their sewer, water, and recycled water systems to provide for
operational flexibility with enhanced system monitoring and control to maintain quality and improve
system efficiencies. Additionally, City/CMWD desires to have a SCADA system that supports enterprise
connectivity throughout the utility and can help the utility develop into a smarter, more sustainable utility.
City/CMWD anticipates that implementing this master plan will provide City/CMWD with a standardized,
state of the art SCADA system, complying with all security measures recommended by Homeland Security
and other regulatory agencies. The vision statement of the master plan is:
To have a uniform, fully integrated SCADA system that supports utility-wide business intelligence to
optimize operations and provide flexibility for future growth and adaptability as a smart utility.
To date on the SCADA master plan, City/CMWD have evaluated the existing SCADA system and completed
an operational needs and deficiencies assessment.
As noted in the vision statement, a key component of the master planning effort is to have standardized
equipment. The next key step in the master planning process is to conduct this RFP process to standardize
on specific manufacturers for the PLC and HMI that will be utilized through the implementation of the
future SCADA system. The results of the existing system evaluation and the operational needs and
deficiencies assessment have been used to develop the evaluation criteria for this RFP. A best-value
evaluation will be utilized to provide City/CMWD with the best manufacturer to meet the needs of the
users.
This RFP is specifically to standardize on the PLC manufacturer. This RFP encompasses only the selection
of the materials and establishing material and service costs that will serve as the basis of the negotiations.
This RFP does not include implementation services. The companion RFP for the HMI may be found on the
City/CMWD’s bid website. Manufacturers may submit proposals on one or both systems, but separate
proposals are required.
City/CMWD intends to standardize on the PLC manufacturer and enter into a master purchase and service
agreement with the selected manufacturer. The negotiated agreement will establish core pricing for
products and services for 10 years, with an established annual escalation rate for the full term. The
selected manufacturer will be required to honor pricing terms with City/CMWD staff and
vendors/contractors authorized to work on City/CMWD projects.
City/CMWD anticipate that a manufacturer’s authorized distributor may be working in close coordination
with the respective manufacturer, but the final agreement will be executed directly with the
manufacturer, or provisions must be provided by the manufacturer to guarantee the agreement for its
full term, regardless of a change in the manufacturer’s authorized distributor.
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 5 of 11
SECTION 2: BACKGROUND
The City of Carlsbad
The City of Carlsbad, California is located 35 miles north of the City of San Diego on the Southern California
coast. The city has a population of nearly 107,000 and serves an area of 39 square miles. With three
lagoons, more than 45 miles of trails, and a third of its land set aside as open space, Carlsbad has been
widely recognized for its responsible approach to growth management and maintaining a high quality of
life for residents and businesses as it approaches build out. Carlsbad is a popular tourist destination, home
to LEGOLAND, the Flower Fields, and nearly seven miles of coastline. The city is also known as a hub for
the golf industry and leading high tech and biotech companies.
The City incorporated in 1952 and has a council/manager form of government. The City Council consists
of a mayor and four council members. Other elected officials include the City Clerk and City Treasurer.
The City has a long standing track record of political stability and fiscal responsibility and holds a AAA
credit rating from Standard & Poor’s. The City’s operating budget for the current fiscal year is in excess of
$250 million. The City’s Capital Improvement Program includes approximately $64 million in
appropriations for the most recent fiscal year, with 235 projects planned over the next 15 years at a cost
of about $463 million. The City has approximately 650 full-time employees and 350 part-time employees.
More information is available on the City’s website.
Utilities Department
The Carlsbad Municipal Water District (CMWD) is a subsidiary district to the City of Carlsbad. The City
owns the sewer system, and CMWD owns the water and recycled water systems. All three systems
operate under the umbrella of the City of Carlsbad Utilities Department.
The Utilities Divisions’ mission is: Provide quality utility services in a fiscally and environmentally
responsible manner for the Carlsbad community.
Sewer System
The City provides wastewater collection services to 30.5 square miles, approximately 78 percent of the
city limits, through six interceptor lines, approximately 270 miles of collection pipelines, and 12 active lift
stations.
The lift stations are currently monitored using a Mission Communications SCADA platform that provides
information back to the city via cellular modems. This Mission Communications based SCADA system
utilizes a web-based graphic user interface to provide information to the city users. As a backup to the
primary system (Mission), phone-based autodialers (Verbatim) are used at critical sites to send critical
alarms to on-call staff.
Water and Recycled Water System
CMWD provides water and recycled water services to approximately 85 percent of the city limits.
For the water system, CMWD imports treated water from the San Diego County Water Authority and
delivers approximately 14,000 afy of potable water to its customers through a widespread system,
consisting of over 450 miles of pipelines and 17 pressure zones. The existing water system is comprised
of 4 turnouts, 8 reservoirs, 4 pump stations and 77 pressure-regulating sites, as well as a hydroelectric
facility.
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 6 of 11
For the recycled water system, CMWD delivers approximately 4,000 afy of recycled water to its customers
through a widespread system. The existing recycled water system is comprised of 3 reservoirs, 3 pump
stations, and 5 pressure-regulation stations.
The water and recycled water systems currently utilize OPTO 22-based equipment at the sites to collect
process data and relay it back to the main operations center via Ethernet radios. All the PLCs used in the
CMWD water and recycled water system are OPTO 22 SNAP PACs. For sites requiring more I/Os, multiple
OPTO 22 PLCs are linked together using an ethernet connection.
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 7 of 11
SECTION 3: INSTRUCTIONS TO PROPOSERS
RFP Schedule
The anticipated RFP schedule is provided in the following table:
ACTIVITY SCHEDULE
RFP Issued July 18, 2018
Pre-Proposal Meeting August 2, 2018, 2:00 PM PST
Deadline for questions August 10, 2018, 5:00 PM PST
Final Q&A and/or addendum issued August 16, 2018
Proposals due August 23, 2018 2:00 PM PST
Selection Committee recommends Manufacturer * September 2018
Negotiations completed* October and November 2018
City Council/CMWD Board consideration and
authorization of agreement * Early 2019
*Anticipated dates
Pre-Proposal Meeting
A non-mandatory pre-proposal meeting will be held at the date and time specified in the RFP schedule at
5950 El Camino Real, Carlsbad, CA 92008.
Inquiries
Questions related to the RFP must be submitted via email only by the deadline on the schedule to:
Graham Jordan, Contract Administrator
PWContractAdmin@carlsbadca.gov
RFP number must be referenced in the email title. Responses to any inquiries not including the RFP
number in the email title may be delayed. Questions will not be accepted in any other format. Responses
to the questions, that change any part of the RFP, will be provided via Addendum on PlanetBids.
Any questions submitted after the deadline identified will not be answered. Proposers are cautioned
regarding the non-binding nature of oral communications with City/CMWD staff, such as opinion,
comments, explanations, responses to informal questions, etc.
Addenda
City/CMWD reserves the right to revise the RFP prior to the date that the proposals are due. Addenda
must be acknowledged and included in the proposal.
Submittal Deadline
Until the deadline identified in the RFP Schedule, City/CMWD shall accept sealed proposals, clearly
marked as such, at the address below by mail, delivery service, or by deposit in the Bid Box located in the
first floor lobby.
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 8 of 11
Proposal for PLC
RFP19-481UTIL
Attn: Purchasing Officer
1635 Faraday Avenue
Carlsbad, CA 92008
Proposals and/or modifications received subsequent to the hour and date specified in the schedule will
not be considered and will be returned to the proposer.
Proposal Requirements
Submit 7 original copies and one electronic copy on a thumb drive of the proposal. Include a Table of
Contents at the front of the proposal, and submit the proposal in the exact order listed in the Response
Structure in Attachment A Evaluation Criteria. One hard copy of financial and one of cost proposal
information shall be submitted in sealed separate envelope marked confidential, with a separate thumb
drive also marked confidential and containing an electronic version of the confidential files.
This RFP contains instructions governing the proposals to be provided, requirements which must be met
for eligibility consideration and general evaluation criteria. Only proposals prepared in compliance with
the instructions and document formats specified by this RFP will be considered compliant. To ensure that
misrepresentation does not occur, please seek clarification of any requirements that are not understood.
Proposals must be prepared simply and effectively, providing a straightforward, concise description of
capabilities to satisfy the requirements of this RFP. Emphasis should be on completeness and clarity of content
with sufficient detail to allow for accurate evaluation and comparative analysis.
The contents of the proposal of the successful proposal will be incorporated into the contractual
obligations when a contract is awarded.
Evaluation Criteria
In accordance with the Carlsbad Municipal Code, a best value evaluation will be conducted to select the
manufacturer.
Each proposal will be evaluated using the evaluation criteria established in Attachment A. Costs shall be
scored independently from the other evaluation criteria.
Negotiations
After discussion and ranking by the Selection Committee, the recommended manufacturer will be asked
to enter into negotiations for the master purchase and service agreement to refine scope and establish
fees. Multiple meetings are anticipated through this process. The final agreement will be executed directly
with the manufacturer, or provisions must be provided by the manufacturer to guarantee the agreement
for its full term, regardless of a change in the manufacturer’s authorized representative.
The selected manufacturer will be expected to sign an agreement with the City/CMWD. In the event that
an agreement cannot be reached with the highest-ranking vendor, City/CMWD will terminate
negotiations and enter into negotiations with the next highest-ranking vendor.
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 9 of 11
Award of Master Purchase and Service Agreement
Upon successful negotiations with the preferred manufacturer, the Selection Committee will recommend
the manufacturer to the City Council/Board of Directors to standardize the PLC/HMI equipment on that
manufacturer and authorize a master purchase and service agreement with the manufacturer.
City/CMWD and the manufacturer will then enter into the master purchase and service agreement as
outlined in Attachment C.
The following requirements will be incorporated into the master agreement:
• The costing provided in the proposal, including escalation rates, shall be the basis of the
negotiations. The quantities provided are not exact and are anticipated based on the owner’s
future needs, and have been provided in the RFP for the purposes of fair evaluation between
vendors.
• City/CMWD anticipate that a manufacturer’s authorized distributor may be working in close
coordination with the respective manufacturer on this RFP, but the final agreement will be
executed directly with the manufacturer, or provisions must be provided by the manufacturer
to guarantee the agreement for its full term, regardless of a change in the manufacturer’s
authorized distributor.
• The term of this agreement will be effective for a period of 10 years.
• The manufacturer shall provide an extended warranty to be no less than 2 years from date of
delivery to City/CMWD or City/CMWD vendors/contractors on all products procured on
behalf of the City/CMWD.
• The selected manufacturer will be required to honor pricing terms with City/CMWD staff and
vendors/contractors working on City/CMWD projects.
• This RFP, its general provisions (Attachment B), and the terms and conditions identified in the
sample Master Purchase and Service Agreement (Attachment C) shall be incorporated in any
agreement resulting from this solicitation. Any agreement shall be governed by and construed
in accordance with the Carlsbad Municipal Code, and the laws of San Diego County and the
State of California.
• A sample of the Master Purchase and Service agreement is provided as Attachment C for your
review. These terms and conditions will form the basis of key sections of the required
agreement between City/CMWD and the successful proposer. Any requests to use an
alternative contract/agreement form, such as a proprietary licensing or maintenance
agreement, must be presented at the time of the proposal.
• Any exceptions to city contract are to be stated in bidder’s proposal.
Legal and Contractual Guidelines
By virtue of submitting a proposal, interested parties are acknowledging:
• This RFP, its general provisions (Attachment B), and the terms and conditions identified in the
sample Master Purchase and Service Agreement (Attachment C) shall be incorporated in any
agreement resulting from this solicitation. Any agreement shall be governed by and construed
in accordance with the Carlsbad Municipal Code, and the laws of San Diego County and the
State of California.
• A sample of the Master Purchase and Service agreement is provided as Attachment C for your
review. These terms and conditions will form the basis of key sections of the required
agreement between City/CMWD and the successful proposer. Any requests to use an
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 10 of 11
alternative contract/agreement form, such as a proprietary licensing or maintenance
agreement, must be presented at the time of the proposal.
• Any exceptions to city contract are to be stated in bidder’s proposal.
• City/CMWD reserves the right to reconsider any proposal submitted at any stage of the
procurement. It also reserves the right to meet with select proposers at any time to gather
additional information. Furthermore, City/CMWD reserves the right to delete or add
functionality (i.e., modules and components) until the final contract signing.
• All third-party solutions proposed as part of this package are subject to the same guidelines
of this RFP, unless otherwise stated.
• City/CMWD reserves the right to reject any or all proposals and to waive technicalities and
informalities when such waiver is determined by City/CMWD to be in their best interest.
• This request does not commit City/CMWD to retain any vendors, to pay costs incurred in the
preparation of proposals, or to proceed with the project. Please note that City/CMWD
reserves the right to take any or no action based on responses to this request for proposal,
including the acceptance or rejection of proposals and the inclusion and deletion of any
combination of the work items for the project. City/CMWD reserves the right to reject any or
all proposals and to negotiate with any qualified applicant.
• City/CMWD reserves the right to retain all proposals submitted and to use any ideas in a
proposal regardless of whether that proposal is selected. By submitting a proposal, the firm
is providing a guarantee to City/CMWD that, if chosen, they will be able to provide the
proposed services during the period of time discussed in this Request for Proposal (RFP).
There is no expressed or implied obligation for City/CMWD to reimburse responding firms for
any expenses incurred in preparing proposals in response to this request.
• Proposals (including accompanying materials) will become the property of City/CMWD.
Proposals will be held in confidence to the extent permitted by law. After award of a contract
or after rejection of all proposals, the proposals will be public records subject to disclosure
under the California Public Records Act (Government Code Section 6250 et seq.)
• Any restrictions on the use of data contained within a proposal must be clearly stated in the
proposal itself. Proprietary information submitted in response to this RFP should be provided
in a separate envelope marked “Confidential” by the proposer and then will be handled in
accordance with applicable City Procurement Regulations and the California Public Records
Act. If you have proprietary information, products or services, please identify them as such in
your submittal.
• City/CMWD reserves the right to request additional information from proposers prior to final
selection and to consider information about a proposer other than that submitted in the
proposal.
• Failure to comply with the requirements of the RFP may result in disqualification.
• City/CMWD reserves the right to request information or clarification on any on-going
litigation or pending litigation.
• Regarding intellectual property and work for hire, selected vendor/contractor understands
and agrees that any and all materials and deliverables that are subject to independent
copyright protection that are developed in connection with the performance of any resulting
contract (Works) shall constitute a work for hire as that term is defined in the Copyright Act
of 1976 (Act), as amended. As a result, all right, title and interest in and to all such Works shall
belong exclusively to the city, including without limitation all copyrights and other intellectual
property rights therein. If for any reason a Work is not deemed to be a work for hire,
Vendors/Contractors shall be required to grant, transfer, and assign, free of charge,
City of Carlsbad/Carlsbad Municipal Water District
RFP for PLC
Page 11 of 11
exclusively to the city, all title, rights and interest in and to said Work, including all copyrights
and other intellectual property rights. The vendor/contractor will further agree to execute
and deliver to the city a confirmatory grant and assignment of all rights in and to Works and
to execute any other proper document the city deems necessary to ensure the complete and
effective transfer of all rights in Works to the city. In the event that vendor/contractor utilizes
a sub-contractor(s) for any portion of the Work that is in whole or in part of the specified
deliverable(s) to the City/CMWD, vendors/contractors shall include a statement in the
vendor/contractor-subcontractor agreement (Subcontractor Agreement) that identifies that
the deliverable/work product to the city is a work-for hire as defined in the Act and that all
intellectual property rights in the deliverable/work product, whether arising in copyright,
trademark, service mark or other belongs to and shall vest in the city. Further, the
Subcontractor Agreement shall require that the subcontractor grants, transfers, and assigns,
free of charge, exclusively to the city, all titles, rights and interests in and to said
deliverable/work, including all copyrights and other intellectual property rights.
• Regarding ownership of independent works, in accordance with the preceding paragraph,
Works developed for the City/CMWD in connection with any resulting contract are the
exclusive property of the City/CMWD. Vendor/contractor agrees to deliver all Works to the
city/CMWD upon completion of the order. Works include but are not limited to editorial
drafts, original copy, photographs, proofs, corrected proofs, camera-ready boards and similar
editorial materials, designs, mock-ups, layouts, arrangements, “look and feel,” and all
negatives, flats, engravings, photostats, drawings and other production materials and
content. For IT procurements for the development of original software for a specific
city/CMWD application or purpose, Works include but are not limited to executable code,
source code, fixes, patches, updates, upgrades, documentation embedded or otherwise,
original copy, and other production materials. Vendor/contractor shall be responsible for
delivering all Works to the city no later than fifteen (15) working days from the date of any
final contract deliverables. In the event the vendor/contractor fails to return all such materials
by this deadline and the city desires to use Works again, vendor/contractor shall provide the
city/CMWD with equivalent materials, at its own expense, or reimburse the city/CMWD, in
full, for the cost of developing equivalent materials.
• Regarding IP warranty and indemnification, the vendor/contractor represents and warrants
that any materials or deliverables, including all Works, provided under any resulting contract
are either original, not encumbered and do not infringe upon the copyright, trademark,
patent or other intellectual property rights of any third party, or are in the public domain. If
deliverables, materials or Works provided hereunder become the subject of a claim, suit or
allegation of copyright, trademark or patent infringement, city/CMWD shall have the right, in
its sole discretion, to require vendor/contractor to produce, at vendor/contractor’s own
expense, new non-infringing materials, deliverables or Works as a means of remedying any
claim of infringement in addition to any other remedy available to the city under law or equity.
Vendor/contractor further shall agree to indemnify and hold harmless the city/CMWD, its
officers, employees and agents from and against any and all claims, actions, costs, judgments
or damages of any type alleging or threatening that any materials, deliverables, supplies,
equipment, services or Works provided under this contract infringe the copyright, trademark,
patent or other intellectual property or proprietary rights of any third party (third party claims
of infringement). If a third party claim of infringement is threatened or made before
vendor/contractor receives payment under any resulting contract, city shall be entitled, upon
written notice to vendor/contractor, to withhold some or all of such payment.
ATTACHMENT A: EVALUATION CRITERIA
[Remainder of this page intentionally left blank]
9665 Chesapeake Drive, Suite 201
San Diego, California 92123
PLC Hardware RFP
Selection Criteria
Prepared for
City of Carlsbad, California
July 2018
ii
Table of Contents
List of Figures .............................................................................................................................................. iii
List of Tables ............................................................................................................................................... iii
List of Abbreviations ................................................................................................................................... iv
Section 1: Introduction .............................................................................................................................1-1
1.1 Objectives and Project Overview .....................................................................................................1-1
1.2 Evaluation Structure ........................................................................................................................1-1
1.2.1 Evaluation Methodology ....................................................................................................1-1
1.2.2 Technical Specifications ....................................................................................................1-1
1.2.3 Fee Proposal Schedules (Cost) .........................................................................................1-2
1.2.4 Technical Requirements ....................................................................................................1-2
1.2.5 Technical Criteria ...............................................................................................................1-2
1.2.6 Industry Presence ..............................................................................................................1-2
1.2.7 Value Added ........................................................................................................................1-2
1.3 Response Structure .........................................................................................................................1-2
Section 2: Evaluation Methodology .........................................................................................................2-1
Section 3: Technical Specifications .........................................................................................................3-1
3.1 PLC Communications System .........................................................................................................3-1
3.2 Costing Definitions ...........................................................................................................................3-2
3.2.1 Supply PLC Hardware/Software ........................................................................................3-2
3.2.2 Provide System Training ....................................................................................................3-2
3.2.3 Provide Technical Support and Software Maintenance ..................................................3-3
Section 4: Fee Proposal Schedules (Cost) ..............................................................................................4-1
Section 5: Technical Requirements .........................................................................................................5-1
5.1 PLC Requirements ...........................................................................................................................5-1
5.1.1 Approvals and Operating Environment .............................................................................5-1
5.1.2 Modular PLC .......................................................................................................................5-1
5.1.3 Redundancy ........................................................................................................................5-1
5.1.4 CPU Module ........................................................................................................................5-1
5.1.5 Communications ................................................................................................................5-1
5.1.6 Power Supply ......................................................................................................................5-2
5.1.7 I/O Modules ........................................................................................................................5-2
5.1.8 I/O Characteristics .............................................................................................................5-2
5.1.9 Wiring Connections ............................................................................................................5-2
5.1.10 Diagnostics .........................................................................................................................5-2
5.1.11 Accuracy ..............................................................................................................................5-3
5.1.12 PLC Firmware .....................................................................................................................5-3
PLC Hardware RFP
Selection Criteria Table of Contents
iii
5.1.13 Functions ............................................................................................................................5-3
5.1.14 Native Programming Environment ....................................................................................5-4
5.1.15 Priority Telephone Support ................................................................................................5-5
Section 6: Technical Criteria ....................................................................................................................6-1
6.1 Foundational PLC .............................................................................................................................6-1
6.2 Security .............................................................................................................................................6-1
6.3 Future Development ........................................................................................................................6-2
6.4 Future Organizational Stability and Support ..................................................................................6-2
Section 7: Industry Presence ...................................................................................................................7-1
Section 8: Value Added Consideration ....................................................................................................8-1
Appendix A: Cover Sheet .............................................................................................................................. 1
Appendix B: Technical Requirement Response Tables ............................................................................. 1
Appendix C: Technical Criteria Scoring Tables ........................................................................................... 1
List of Figures
Figure 3-1. PLC communication layout ....................................................................................................3-1
List of Tables
Table 2-1. Response Scoring Table .........................................................................................................2-1
Table 4-1. PLC Hardware and Software Costs ........................................................................................4-2
Table 4-2. System Training Costs.............................................................................................................4-2
Table 4-3. Software Maintenance and Technical Support Costs ...........................................................4-3
Table 4-4. Costs for Term of Agreement ..................................................................................................4-3
Table B-1. Technical Specification Requirement Response Table ........................................................... 2
Table C-1. Foundational Criteria Scoring .................................................................................................... 2
Table C-2. Security Criteria Scoring ............................................................................................................ 2
Table C-3. Future Development Criteria Scoring ........................................................................................ 2
Table C-4. Future Stability and Support Criteria Scoring ........................................................................... 3
PLC Hardware RFP
Selection Criteria Table of Contents
iv
List of Abbreviations
°F degree(s) Fahrenheit
AC alternating current
AI analog input
AO analog output
AWG American Wire Gauge
City City of Carlsbad
CPU central processing unit
DC direct current
DI discrete input
DNP3 Distributed Network Protocol
DO discrete output
DOCX Microsoft Word (file extension)
EEPROM electrically erasable, programmable, read-
only memory
GOOP Graphical Object-Oriented Programming
HMI human-machine interface
IEC International Electrotechnical Commission
I/O inputs and outputs
mA milliampere(s)
OIT operator interface terminal
OS operating system
PDF Portable Document Format
PLC programmable logic controller
RAM random-access memory
RFP Request for Proposals
SCADA supervisory control and data acquisition
UL Underwriters Laboratories, Inc.
USB universal serial bus
VAC volt(s) alternating current
VDC volt(s) direct current
1-1
Section 1: Introduction
This section presents objectives and project overview, the RFP evaluation structure, and the RFP
response structure.
1.1 Objectives and Project Overview
The City of Carlsbad (City) and the Carlsbad Municipal Water District’s (CMWD) (collectively,
City/CMWD or Owner) desire to select a PLC hardware package to standardize the Owner’s control
system and enter into a long-term purchase and services agreement. The PLC product will support a
centralized human-machine interface (HMI) system that can be accessed through decentralized
control rooms for the water/recycled water and wastewater groups. System data will be
communicated from remote sites to a central location over a high speed/high band-width
communications network.
The Owner has identified a list of key needs that will be addressed with the new PLC hardware. The
evaluation will be organized according to these key needs:
1. Foundational PLC: the PLC hardware will need to provide foundational functionality assumed of
all PLC hardware.
2. Redundancy: The PLC hardware will need to provide capabilities for redundancy and automatic
fail-over features.
3. Security: The PLC hardware will need to provide security to protect the system from unauthorized
access and use.
4. Future development: The PLC hardware will need to provide features that will allow for future
development and expansion of the control system.
5. Future stability and support: The PLC hardware manufacturer will need to provide assurance of
future stability and ongoing support of the proposed PLC hardware.
1.2 Evaluation Structure
These instructions were developed to aid in response development and guide proposers through the
requirements of this RFP. Additional proposal requirements, such as number of copies and RFP
schedule, are provided in Instructions to Bidders in the Request for Proposals. This section is
intended to provide a brief overview of each section for clarity and is not intended to provide
additional requirements or prompt additional response. The details of each evaluation portion of the
RFP are provided in subsequent sections:
1.2.1 Evaluation Methodology
The evaluation methodology section provides details on how the proposer’s responses will be scored
and how different portions of the response will be weighted relative to each other. Proposers should
ensure proposals address each of these scoring categories. Each scoring category will have a
corresponding section in this document to provide an explanation of what should be included in the
response.
1.2.2 Technical Specifications
The technical specifications section provides a general overview of the RFP objective to allow the
proposer to understand what the owner wants to achieve with this RFP. A basic diagram of the PLC
communication system is provided to help proposers understand the system layout and is not
intended to provide system details.
PLC Hardware RFP
Selection Criteria Section 1
1-2
The costing definitions provide the proposer with the necessary information to develop cost
information for the fee proposal schedules. The costing definitions are intended to be a high-level
project outline that shall be used to determine quantities and components that will be required to
meet the owner’s needs. Proposers are responsible for determining how to best provide an overall
product that will meet these definitions as well as the requirements and criteria in the technical
requirements section and the technical criteria section.
1.2.3 Fee Proposal Schedules (Cost)
The fee proposal schedules section will provide details on how proposers should provide costs for
evaluation. Cost tables are provided for proposers to include line items for each component needed
to achieve the system and costing definitions from the technical specifications section while
complying with the technical requirements and technical criteria.
1.2.4 Technical Requirements
The technical requirements section details each of the requirements the proposed product must
meet to be considered for selection. Tables provided in Appendix B shall be used to respond to this
section. Instructions are provided in Appendix B of this document.
1.2.5 Technical Criteria
The technical criteria section consists of a series of questions and prompts the proposer must
provide responses to. The questions are intended to provide a means to evaluate how each proposer
will be able to meet the needs of the owner. Format for response scoring is included in appendix C of
this document.
1.2.6 Industry Presence
Each proposer must provide information about the proposed product installed base in the public
water/wastewater industry. Proposers must also provide vendors and contractors/integrators
capable of supporting the product for evaluation. This section will be an open response.
1.2.7 Value Added
The value added section will give proposers an opportunity to respond with any additional value their
product may contribute outside of the cost, technical requirements, and technical criteria. This
section will also be an open response for the proposer to explain the added value they can provide.
1.3 Response Structure
All proposals are to be organized into the following sections and sequence to provide a structured
format so that reviewers can systematically evaluate responses. Each copy of the response package
must include all the sections in the order indicated, and shall be clearly labeled. Attachments should
be clearly referenced and identified to facilitate the review process. Additional proposal
requirements, such as number of copies and RFP schedule, are provided in Instructions to Bidders in
the Request for Proposals.
Each response shall include the following sections in the order shown:
1. Table of Contents
2. Cover sheet (Appendix A)
3. Acknowledgement of Addenda
4. Technical requirements response tables (Appendix B)
PLC Hardware RFP
Selection Criteria Section 1
1-3
5. Technical criteria written responses
6. Supporting documents for technical criteria
a. Third party vulnerability audit report
b. List of training courses and schedule for 2018
7. Value added response
8. Industry presence response
9. Fee Proposal in a separate envelop marked confidential
10. Financial reports in separate envelope marked confidential
2-1
Section 2: Evaluation Methodology
The Owner’s choice of control system software will be made by a team of individuals evaluating the
proposals, herein referred to as the City’s Selection Committee. The criteria that will be used for
evaluating the proposals are described in detail below.
The relative importance of the evaluation criteria that will be applied during the proposal review
process is shown in Table 2-1 below. Each proposal will be evaluated on the following point-weighted
scoring system. Each criterion will be rated on a scale between zero and its maximum points, where
zero indicates that no information was given in the proposal, and one is the lowest score based on
provided information, up to the maximum points identified for that criterion. All proposals will be
evaluated based on the criteria found below.
Although no interview process is anticipated, City/CMWD reserve the right to interview the top two to
three candidates.
Table 2-1. Response Scoring
Evaluation Criterion
Maximum
Points Score Comments
Fee proposal schedule (cost) 100
Technical requirements 50
Technical criteria
Foundational PLC criteria 20
Security criteria 20
Future development criteria 10
Future stability and support criteria 30
Industry presence 40
Value added 30
References 50
Maximum total points 350
3-1
Section 3: Technical Specifications
This section presents the required technical specifications for the project, including PLC
communications system and costing definitions. The system and costing definitions provide the
proposer with the necessary information to develop cost information for the fee proposal schedules.
The system and costing definitions are intended to be a high-level project outline that shall be used
to determine quantities and components that will be required to meet the owner’s needs. Proposers
are responsible for determining how to best provide an overall product that will meet these
definitions as well as the requirements and criteria in the technical requirements section and the
technical criteria section.
3.1 PLC Communications System
Figure 3-1 presents conceptual communications connections for the PLC redundant master
controllers and an example remote site PLC. The two master controllers will be set up as a primary
unit with a hot standby for failover. Each of the master controllers should include all required
additional hardware to provide a complete operating PLC unit including power supply,
communications cards/modules, and backplanes. One remote site controller will be required for
every remote site in the conceptual system. Each remote-site PLC should include all required
additional hardware to provide a complete operating PLC unit including power supply,
communications cards/modules, and backplanes.
Figure 3-1. PLC communication layout
PLC Hardware RFP
Selection Criteria Section 3
3-2
3.2 Costing Definitions
The proposer shall demonstrate the manufacturer of the hardware is able to provide the owner a PLC
hardware/software package with the technology and support services needed to support the owner’s
current control system needs and meet the owner’s supervisory control and data acquisition (SCADA)
upgrade project goals and needs. The package must meet the objectives of the PLC communications
system above, demonstrate technical criteria as described by the proposer in response to the
technical criteria section, and meet the technical requirements described in the technical
requirements section.
Qualified PLC hardware vendors must have the capability to perform the tasks described in the
remainder of this section.
3.2.1 Supply PLC Hardware/Software
The PLC hardware vendor shall be able to provide all the required PLC hardware and programming
software and licenses to the owner to provide the specified PLC system functionality that is in line
with the owner’s project goals, including all ancillary equipment such as the chassis, power supplies,
communications cards, redundancy modules, interconnecting cables and anything else that would
be required for a fully functioning system.
1. Two PLC master controllers (one primary and one hot-standby) with communication capability as
shown in Figure 3-1.
2. Thirty-six PLC remote site controllers with communication capability as shown in Figure 3-1.
3. Thirty-six modules to support eight analog inputs (isolated).
4. Thirty-six modules to support four analog outputs (isolated).
5. Thirty-six modules to support 16 discrete inputs (isolated).
6. Thirty-six modules to support 16 discrete outputs (relay).
7. .
8. Two programming software packages and licenses.
3.2.2 Provide System Training
The PLC hardware vendor shall provide a comprehensive training program for the owner’s staff on
the design, operation, configuration, and maintenance of the PLC hardware and software. The
training will include instruction on all system configuration functions and procedures.
The PLC hardware vendor shall prepare training materials that describe through text and illustrations
all the system functions. All training materials shall be provided to the owner in electronic and hard-
copy format. Training shall be conducted at the owner’s facilities and provide all hardware and
software required for training, the same as it was being held at the vendors training facility. Training
will include:
1. Operations training for four separate classes with six attendees for each class at the owner’s
facility.
2. Programming training for four separate classes with six attendees for each class at the owner’s
facility.
PLC Hardware RFP
Selection Criteria Section 3
3-3
3.2.3 Provide Technical Support and Software Maintenance
The proposer shall provide technical support and software maintenance for the PLC hardware/
software package equivalent to the following:
1. Set up a long-term contract, minimum 10 years, with the owner for hardware maintenance
(software/firmware updates and patches) for quantities given. When listing annual costs,
provide the escalation used.
2. Set up a long-term contract, minimum 10 years, with the owner to provide technical support as
described in Section 5. When listing annual costs, provide the escalation used.
4-1
Section 4: Fee Proposal Schedules (Cost)
The proposer shall submit a fee for the cost of the PLC systems, software licenses and support in a
separate sealed envelope by the date shown under the selection schedule on the Notice Inviting
Bidders. The separate sealed envelope with the fee proposal shall include one hard copy and one
copy in digital format (Portable Document Format [PDF] or Word [DOCX] format) on a universal serial
bus (USB).
The costs will be evaluated by the Contract Administrator, independently from the qualifications
reviewed by the selection committee. The calculation will be conducted over a 10-year term. The
quantities are not exact and are anticipated based on the Owner’s future needs, and have been
provided here for the purposes of fair evaluation between vendors.
The low cost shall receive maximum points; any costs within 5 percent of low cost will receive 95
percent of the points; if within 10 percent of low cost, receive 90 percent of the points; if within 20
percent of low cost, receive 80 percent of the points; if within 30 percent of low cost, receive 70
percent of the points; and continuing by 10 percentage ranges.
Each proposer shall complete the fee schedules in this section, a detailed list for the system, and its
associated unit costs including all software, licenses, drivers, options, etc. to meet the requirements
defined in the technical specifications.
The proposed fee schedules shall be based on programmable logic controller (PLC) hardware with
modules capable of monitoring/controlling the provided inputs and outputs (I/O) within the PLC
communications system presented in Section 3.1. All hardware and additional modules/components
required for the conceptual site shall be presented as individual line-item costs in the proposed fee
schedules.
Note that the proposed costs refer to the cost to the City for each item listed. Include all costs for
ancillary equipment such as the chassis, power supplies, communications cards, redundancy
modules, interconnecting cables and anything else that would be required for a fully functioning
system. The proposer shall take into consideration the labor, material, rental, and any associated
cost to perform or provide any unit of work.
The proposer shall use Tables 4-1 through 4-4 to provide a fee schedule for evaluation that will
represent the total cost to meet the requirements defined in the technical specifications.
PLC Hardware RFP
Selection Criteria Section 4
4-2
Table 4-1. PLC Hardware and Software Costs
Component Quantity
Unit
(LS, each,
etc.)
Unit Cost Total Component
Cost
Master controllers $ - $ -
Remote Site Controllers $ - $ -
Module to support 8 Analog Inputs $ - $ -
Module to support 4 Analog Outputs $ - $ -
Module to support 16 Discrete Inputs $ - $ -
Module to support 16 Discrete Outputs $ - $ -
Two programming software packages and licenses $ - $ -
Subtotal $ -
Table 4-2. System Training Costs
Component Quantity Component Cost Total Component
Cost
Operations training $ - $ -
Programming training $ - $ -
Subtotal $ -
PLC Hardware RFP
Selection Criteria Section 4
4-3
Table 4-3. Software Maintenance and Technical Support Costs
Component Escalation Rate Unit Component Cost Total Component Cost
Year 1 Software Maintenance LS $ - $ -
Year 2 Software Maintenance LS $ - $ -
Year 3 Software Maintenance LS $ - $ -
Year 4 Software Maintenance LS $ - $ -
Year 5 Software Maintenance LS $ - $ -
Year 6 Software Maintenance LS $ - $ -
Year 7 Software Maintenance LS
Year 8 Software Maintenance LS
Year 9 Software Maintenance LS
Year 10 Software Maintenance LS
Year 1 Technical Support LS
Year 2 Technical Support LS
Year 3 Technical Support LS
Year 4 Technical Support LS
Year 5 Technical Support LS
Year 6 Technical Support LS
Year 7 Technical Support LS
Year 8 Technical Support LS
Year 9 Technical Support LS
Year 10 Technical Support LS
Subtotal $ -
Table 4-4. Costs for Term of Agreement
Component Basis Cost
PLC Hardware/Software Subtotal from Table 4-1 $ -
Operations and Maintenance Training Costs Subtotal from Table 4-2 $ -
Software Maintenance, and Technical Support Subtotal from Table 4-3 $ -
Total Cost $ -
5-1
Section 5: Technical Requirements
The technical requirements provided in this section shall be used by the proposer to respond to the
tables in Appendix B: Technical Requirement Response Tables.
5.1 PLC Requirements
This section presents general PLC requirements for the project.
5.1.1 Approvals and Operating Environment
PLCs shall be microprocessor-based, capable of receiving discrete input (DI) and analog input (AI)
and—through programming—able to control discrete output (DO) and analog output (AO) functions,
perform data-handling operations, and communicate with external devices. PLCs shall meet the
requirements of Underwriters Laboratories, Inc. (UL) 508 devices, and shall be labeled. PLCs shall
function properly at temperatures between 32 and 122 degrees Fahrenheit (°F) at 5 to 95 percent
relative humidity non-condensing, and shall tolerate storage temperatures between -40°F and
+140°F at 5 to 95 percent relative humidity non-condensing.
5.1.2 Modular PLC
PLCs shall be based on a modular, field-expandable design, allowing the system to be tailored to the
process control application. The system shall be expandable using additional hardware and/or user
software. As a minimum, the PLC shall include integrated power supply, central processing unit (CPU)
integrated Modbus/TCP and Ethernet communications, and built-in I/O, and shall be networkable to
smart equipment over standard fieldbus.
5.1.3 Redundancy
The master PLC must support controller redundancy to provide higher system availability. The
secondary controller in the redundancy scheme must be capable of hot standby functionality,
allowing for bumpless switchover from primary to secondary controllers. Redundancy may not be
required for the remote PLCs.
5.1.4 CPU Module
The CPU module shall be a self-contained, microprocessor-based unit that provides time of day,
scanning, application (based on International Electrotechnical Commission [IEC] 61131-3
development logic) program execution, storage of application programs, storage of numerical values
related to the application process and logic, I/O bus traffic control, peripheral and external device
communications, and self-diagnostics.
5.1.5 Communications
The integrated communications options shall allow secure peer-to-peer communication with other
PLCs, and shall allow the PLC to communicate with an operator interface terminal (OIT), central
station, or HMI. The PLC shall use the manufacturer’s standard communication architecture and
protocol, Ethernet architecture and protocol, or a combination of these. The communication port
shall allow PLC programming to be done locally using a laptop computer, or from the central station
or remote workstation.
PLC Hardware RFP
Selection Criteria Section 5
5-2
The PLCs shall be able to be used as standalone control systems for remote SCADA with telemetry
communication networking. Communication networking shall support proven methods using cellular,
licensed radio, leased telephone lines, and direct fiber-optic cable (e.g., single-mode and multi-
mode).
In addition, specify if Distributed Network Protocol (DNP3), report by exception, or other secured and
encrypted store- and forward-based communication protocols are supported.Error! Reference source n
ot found.
5.1.6 Power Supply
Power supply modules shall use alternating current (AC) power with a nominal voltage of 120 volts
alternating current (VAC) ± 5 percent, or shall use direct current (DC) power with a nominal voltage of
24 volts direct current (VDC) ± 5 percent. The power supply module shall monitor the incoming line
voltage level and provide over-current and over-voltage protection. If the voltage level is detected as
being out of range, the power supply module shall continue to provide power for an adequate
amount of time to allow for a safe and orderly shutdown. Power supply shall be able to withstand a
power loss for a minimum of 20 milliseconds while remaining in operation and providing adequate
power to all connected modules.
Provide power supply with an indicating light that illuminates when the module is operating properly.
5.1.7 I/O Modules
Modules shall be self-contained, microprocessor-based units that provide an interface to field
devices. Each module shall contain visual indication to display the on/off or active/fault status of
individual inputs or outputs.
5.1.8 I/O Characteristics
Each controller shall allow for AI, AO, DI, DO, and high-speed digital inputs. During normal operation,
a malfunction in any I/O channel shall affect operation of that channel only, and shall not affect
operation of the CPU or any other channel.
AI modules shall be available as 4–20 milliamperes (mA) VDC, isolated and non-isolated. All AI
modules shall have differential inputs. DI modules shall be available as 12–24 VDC, high speed, sink
and source. AO modules shall be available as 4–20 mA VDC, isolated. DO modules shall be available
in 24 VDC, relay, sink, and source.
5.1.9 Wiring Connections
Wiring connections shall be heavy-duty, self-lifting, pressure-type screw terminals to provide easy
wire insertion and secure connections. The terminals shall accept two No. 14 American Wire Gauge
(AWG) wires. A hinged protective cover shall be provided over the wiring connections.
5.1.10 Diagnostics
Each PLC shall have diagnostic routines implemented in firmware. The CPU shall continuously
perform self-diagnostic routines that will provide information on the configuration and status of the
CPU, memory, communications, and I/O. The diagnostic routines shall be regularly performed during
normal system operation. A portion of the scan time of the controller shall be dedicated to
performing these housekeeping functions. In addition, a more extensive diagnostic routine shall be
performed at startup and during normal system shutdown. The CPU shall log I/O and system faults in
fault tables that shall be accessible for display. When a fault affects I/O or communications modules,
the CPU shall shut down only the hardware affected and continue operation by using the healthy
PLC Hardware RFP
Selection Criteria Section 5
5-3
system components. All faults shall be annunciated at the central station. Diagnostic software shall
be usable in conjunction with the portable tester.
5.1.11 Accuracy
Controllers shall have an accuracy of ± 0.25 percent of input span.
5.1.12 PLC Firmware
Each PLC shall be provided with the manufacturer’s standard OS firmware package. The PLC shall
maintain a point database in its memory that includes all parameters, constraints, and the latest
value or status of all points connected to the PLC. Execution of the PLC application programs shall
use the data in memory resident files. The OS shall support a full complement of process control
functions. It shall be possible to define these functions using a mix of function blocks, ladder logic
diagrams, sequential function charts, and text programming. Programming methods and interactions
shall be based on IEC 61131-3. A combination of the programming methods shall be possible within
a single controller. The OS shall allow software loading locally or from the central station. It shall also
support data entry and diagnostics using an operator interface panel attached directly to the PLC.
Each PLC shall be able to operate in standalone mode:
• Startup: The PLC shall have startup software that causes automatic commencement of
operation without human intervention, including startup of all connected I/O functions. A PLC
shall be capable of having a restart program. The restart program will be based on detection of
power failure at the PLC with the ability to include start time delays between successive
commands to prevent demand surges or overload trips.
• Failure mode: Upon failure for any reason, each PLC shall be able to perform an orderly
shutdown, and force all PLC outputs to a predetermined (i.e., failure mode) state, consistent with
the failure modes shown and the associated control device.
5.1.13 Functions
The controller shall be able to scan inputs, control outputs, and read and write to its internal
memory. The controller shall be able to periodically perform self-diagnostics to verify that it is
functioning properly. The controller shall be able to support the following functions that would be
developed in resident application logic:
• Analog monitoring: Measure and transmit all analog values including calculated analog points.
• Logic (virtual): Development of logic (virtual) points that are software points entered in a point
database and are not directly associated with a physical I/O function. Logic (virtual) points can
be analog or digital points created by calculation from any combination of digital and analog
points, or other data having all the properties of real points—including alarms—without the
associated hardware.
• State variables: If an analog point represents more than two (up to eight) specific states, each
state is nameable. For example, a level sensor can be displayed at its measured engineering
units plus a state variable with named states usable in programs or for display, such as low
alarm, low, normal, high, high alarm.
• Analog totalization: Totalize analog points measuring flow rate and displayed as a daily total on
an OIT and/or HMI.
• Trending: Trend any analog or calculated point in real time.
• Alarm processing: Support alarm processing for AI, DI, and fieldbus alarms for all real and virtual
points connected to the PLC:
PLC Hardware RFP
Selection Criteria Section 5
5-4
Digital alarms: digital alarms are those abnormal conditions indicated by a DI’s change of
state.
Analog alarms: analog alarms are those conditions higher or lower than a defined value, as
measured by an AI.
• Constraints: Provide capability to define constraints in the resident application logic for control
points, such as maximum starts (i.e., cycles) per hour, minimum off time, minimum on time, high
limit (value in engineering units and operator-adjustable), and low limit (value in engineering
units and operator-adjustable).
• Control sequences and control loops: Support the following control:
Proportional control, proportional plus integral control, and proportional plus integral plus
derivative control.
Two-position control for a two-state device by comparing a set point against a process
variable and an established dead band.
Floating point control exercising control when an error signal exceeds a selected dead band,
and maintaining control until the error is within the dead band limits.
Signal selection to allow selection of the highest or lowest analog value from a group of
analog values as the basis of control, including the ability to cascade analog values so that
large numbers of inputs can be reduced to one or two outputs.
Signal averaging to allow mathematical calculation of the average analog value from a group
of analog values as the basis of control, including the ability to weight the individual analog
values so that the function output can be biased (as necessary) to achieve proper control.
5.1.14 Native Programming Environment
Provide the capability for PLC programs to be developed in a native programming environment to
achieve the sequences of operation, parameters, constraints, and interlocks necessary to provide
control of the process systems connected to the control system in conjunction with the HMI
Graphical Object-Oriented Programming (GOOP). All application programs will be resident in the PLC
and execute in the PLC, and will coordinate with each other, to ensure that conflicts or contentions
remain unresolved:
• Program inputs and outputs: Provide capability to program inputs in a resident application
program to calculate the required program outputs. Where specific program inputs are not
available, a default value or virtual point appropriate for the equipment being controlled and the
proposed sequence of operation will be provided to replace the missing input, thus allowing the
application program to operate.
• Program development approaches: Native programming environment shall be fully compatible
with the IEC 61131-3 standard and support development of the following program types: ladder
logic, function block diagram, sequential function chart, structured text.
• Annotation: Native programming environment shall allow programmers to add annotation at the
rung, routine, and program levels. All tags shall be provided with a description field that has a
maximum character count of 120, at a minimum.
• Object-oriented programming: Native programming environment shall allow for variables and
programming to be grouped into “classes” and applied to separate “objects” (or “instances” of
the “class”) based on like equipment or concepts. Modifications to a class shall be automatically
applied to any objects created from that class by the PLC software.
PLC Hardware RFP
Selection Criteria Section 5
5-5
• Module-based analog scaling: Native programming environment platform shall support scaling
of analog inputs and outputs on a per point basis via software-configurable settings within the
associated analog input and output modules.
5.1.15 Priority Telephone Support
The extended support program shall include priority telephone support 24 hours per day. A technical
support engineer who has been certified by the software vendor based on a certified support testing
program shall provide telephone support. A person (not an automated line) shall provide unlimited
telephone support when calling during normal business hours. A voice-mail technical support system
shall be acceptable only outside of normal business hours. A support engineer shall return voice mail
a minimum of 2 hours after leaving a message with the voicemail system.
6-1
Section 6: Technical Criteria
Please provide written responses to each of the questions below as a separate attachment to the
proposal. All responses to section 6 shall align with the numbering in the section to facilitate the
review process. The questions do not need to be repeated. Total length of all responses must not
exceed 10 pages with a minimum font size of 11 points in Microsoft Word (Franklin Gothic Book or
equivalent), This page count is specifically for this section and does not include written responses
needed in any other section. Proposers shall provide responses that are brief and to the point to
manage the page limitation.
6.1 Foundational PLC
6.1.1 Describe the communication, security, and authentication protocols supported between PLC
and PLC and between HMI and PLC.
6.1.2 How much on-board memory will be available for program storage on the PLC as provided in
the fee schedules? What other memory options are available? Are additional expansion
memory slots available?
6.1.3 Provide a selection of system installation references for installed systems involving the
integration of vendor package control systems at the proposed PLC platform. Provide end-
user reference information and a brief system description for a minimum of three installed
systems (preferably for other water/wastewater systems) where the proposed PLC platform
has been used to provide monitoring and/or control of a vendor package control system
based on a PLC or other controller from another manufacturer.
6.1.4 Describe how the stored PLC programming is stored as a backup in the case of a power
failure and how the programming can be automatically restored to the PLC.
6.1.5 Identify all parties that will be signatories to the contracts for purchase, maintenance,
support and services
6.2 Security
6.2.1 Describe any security standards or frameworks that your product complies with and
undergoes evaluations for.
6.2.2 Describe the security training your developers have been through.
6.2.3 Do you have third-party vulnerability audits of your product? Are the reports made available
to clients? Provide a copy of the most recent report as an appendix to these responses (not
included in page count).
6.2.4 Describe your vulnerability disclosure/notification procedure to clients when vulnerabilities
are discovered.
6.2.5 Describe your patching and update procedure and cadence.
6.2.6 If your clients discover vulnerabilities, how do you prefer to be notified?
6.2.7 Have you or any of your clients had a data breach or security incident because of a
vulnerability in the product that you have proposed? If so, describe the support provided to
your client.
6.2.8 Does the product that you have proposed have any current known and unpatched
vulnerabilities?
6.2.9 Do you have a formal security program/department in your organization? If so, describe it.
6.2.10 What methods are employed to protect data, including authentication, in the product you are
proposing?
PLC Hardware RFP
Selection Criteria Section 6
6-2
6.2.11 Describe how user roles and privileges can be configured and updated for secure access.
6.3 Future Development
6.3.1 Describe any pre-canned scripting or functions available for PLC programming.
6.3.2 Describe any features in the PLC native programming environment that will support the
development of programming standards.
6.3.3 Describe how purchasers of the proposed PLC platform are notified by the distributor and/or
manufacturer of relevant firmware and software revision updates and how purchasers can
obtain these revisions. Indicate whether revisions must be installed sequentially or if all
relevant updates are carried forward with future revisions so that all necessary updates can
be acquired through installing the most current version.
6.4 Future Organizational Stability and Support
6.4.1 How many years has the manufacturer’s current company organization been in business? If
the product will be provided by a third-party distributer, provide this information for the
distributer as well.
6.4.2 Provide documentation of manufacturer’s organizational structure and segmentation. What
are the type and number of employees committed to development, administration,
marketing, and technical support of the proposed product? What is the ratio of technical
support employees to the total install base of the PLC hardware under support contract? If
the product will be provided by a third-party distributer, provide this information for the
distributer as well.
6.4.3 Provide the manufacturer’s audited financial statements from the three most recently
reported years. What percentage of revenue is derived from industrial automation software
products? How much revenue was generated by the proposed products in the three most
recently reported years? If the product will be provided by a third-party distributer, provide
this information for the distributer as well. Provide the financial statements as an appendix to
the technical criteria response in a separate envelope marked confidential.
6.4.4 Provide the manufacturer’s business and product development plans for the proposed
product and support services. If the product will be provided by a third-party distributer,
provide this information for the distributer as well.
6.4.5 Describe your approach to backwards compatibility and obsolescence for your proposed
product.
6.4.6 Describe the training programs and products offered to provide training for project
development, administration, and operations levels of the offering. Attach a training course
description and schedule for 2018 as an appendix..
6.4.7 Describe the warranty policy that will be provided for the PLC hardware.
6.4.8 Provide release date and product lifecycle status information for the major hardware and
software components included in the proposed PLC platform. This information shall
document when the proposed hardware and software product lines were initially released to
the marketplace as well as the release dates for the specific controller and communications
hardware included in the proposal. The Proposer shall also include a statement from the
manufacturer indicating the present lifecycle status of the proposed PLC platform hardware
and software.
6.4.9 Provide any technical support options/tiers and capabilities offered in addition to the options
required for costing definitions in Section 3.
PLC Hardware RFP
Selection Criteria Section 6
6-3
6.4.10 Describe your product development quality assurance/management program. What is your
product testing process prior to product release?
6.4.11 Describe the technical support program escalation process. How does the escalation process
change for different tiers of technical support offerings?
6.4.12 Describe your product development quality assurance/management program. What is your
product testing process prior to product release?
6.4.13 Provide a contact name, phone number, website, and address for the regional sales
representative for this product.
7-1
Section 7: Industry Presence
Responses to this section are requested as a written response to be included with the proposal.
Total length of the response must not exceed five pages with a minimum font size of 11 points in
Microsoft Word (Franklin Gothic Book or equivalent). Proposers shall provide the following in
response to this section:
1. A list of public water/wastewater agencies in North America, including at least three within
California, using your product to indicate the installed base of the product. For each installation
include agency name, location, I/O count, and date of installation.
2. A list of at least 3 references of public water/wastewater agencies within 100 miles of Carlsbad
using the proposed product. Provide the agency name, contact names, phone numbers, emails,
I/O count, and date of installation. This list will be used as part of the evaluation process to
establish local industry presence. At least 3 will be contacted for the reference evaluation as
well.
3. Data on the average size of system installations in the water/wastewater industry. Include
information on the number of I/O used, number of remote sites, total flow capacity (in millions of
gallons per day), number of employees, and any other useful metrics.
4. A list of vendors and contractors/integrators capable of supporting your platform that are
located within 90 miles of Carlsbad, California. Provide a contact name, phone number, website,
and address for each. Describe any qualification or certification process that is provided for
contractors/integrators for this product.
8-1
Section 8: Value Added Consideration
Responses to this section are requested as a written response to be included as an appendix with
the proposal. The proposer shall provide any additional value that may be gained by the owner
through additional products associated with the PLC system. In the written response, the proposer
shall provide a description of what additional products are available and how the owner will obtain
value through the purchase and use of additional products with the proposed PLC system. The
“value added” may include any cost reductions in purchase of additional products, available
products that may be integrated with the PLC hardware to provide long-term efficiency and savings,
or any other offerings that the proposer believes may add value for the owner. Total length of the
response must not exceed five pages with a minimum font size of 11 points in Microsoft Word
(Franklin Gothic Book or equivalent).
PLC Hardware RFP
Selection Criteria Section 6
8-2
PLC Hardware RFP
Selection Criteria
1
Appendix A: Cover Sheet
8-1
City of Carlsbad
Water/Wastewater PLC Hardware RFP
General Information
This form must be signed by a person authorized to make proposals and enter into contract
negotiations on behalf of your company. To be considered for this project, the submittals must be
completed in accordance with this RFP and this cover sheet must be attached.
Failure to submit this form will result in your proposal being deemed non-responsive.
Authorized Official (Signature) Date
Print Name of Authorized Official Title of Authorized Official
Company Name Contact Person
Address District, State, Zip
Phone Number Fax Number
Email Address Federal Tax ID Number
PLC Hardware RFP
Selection Criteria
1
Appendix B: Technical Requirement Response Tables
2
Appendix B: Technical Requirement Response Tables
The response shall give a “compliant,” “exception,” or “not compliant” answer for each specification
numbered paragraph and associated lettered sub-paragraph. A “compliant” answer can be made
only if the proposed HMI software can provide the specified function without the addition of external
program applications, or internal programming or scripting. With the “exception” answer, provide a
brief description (i.e., additional software package required, custom programming required,
applications scripting required) to comply with the specification. If a specification requirement
cannot be met by the proposed HMI software, the proposer shall mark that item as “not compliant.”
Table B-1. Technical Specification Requirement Response Table
Section Requirement Response Comments
5.1.1 Approvals and operating environment
5.1.2 Modular PLC
5.1.3 Redundancy
5.1.4 CPU module
5.1.5 Communications
5.1.6 Power supply
5.1.7 I/O modules
5.1.8 I/O characteristics
5.1.9 Wiring connections
5.1.10 Diagnostics
5.1.11 Accuracy
5.1.12 PLC firmware
5.1.13 Functions
5.1.14 Native programming environment
5.1.15 Priority telephone support
PLC Hardware RFP
Selection Criteria
1
Appendix C: Technical Criteria Scoring Tables
2
Appendix C: Technical Criteria Scoring Tables
Responses for section 6 will be scored using the tables below. Each row in the tables corresponds to
one of the criteria listed in section 6. All responses to section 6 shall align with these tables to
provide a structured format so that reviewers can systematically evaluate responses. Total length of
all responses must not exceed 10 pages with a minimum font size of 11 points in Microsoft Word
(Franklin Gothic Book or equivalent). Answers should be kept brief
Table C-1. Foundational Criteria Scoring
Section Score Comments
6.1.1
6.1.2
6.1.3
6.1.4
6.1.5
Table C-2. Security Criteria Scoring
Section Score Comments
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.2.7
6.2.8
6.2.9
6.2.10
6.2.11
Table C-3. Future Development Criteria Scoring
Section Score Comments
6.3.1
6.3.2
6.3.3
PLC Hardware RFP
Selection Criteria Appendix C
3
Table C-4. Future Stability and Support Criteria Scoring
Section Score Comments
6.4.1
6.4.2
6.4.3
6.4.4
6.4.5
6.4.6
6.4.6
6.4.7
6.4.8
6.4.9
6.4.10
6.4.11
6.4.12
6.4.13
6.4.14
ATTACHMENT B: GENERAL PROVISIONS
[Remainder of this page intentionally left blank]
Attachment B
Page 1 of 11
CITY OF CARLSBAD
GENERAL PROVISIONS
PLEASE READ CAREFULLY
THESE PROVISIONS ARE A PART OF YOUR BID AND ANY CONTRACT Pursuant to the Notice to Bidders, the specifications, bidding instructions and requirements on file with the City, the conditions of these General Provisions, and subject to all provisions of the Ordinances of the City of Carlsbad, the Bidder proposes to furnish to the City of Carlsbad, complete at the prices stated in the bid document, the items or services described in the bid document. The
person signing the bid warrants that the bid is genuine and not sham or collusive, or made in the interest of, or on behalf of, any person, firm or corporation not named in the bid document; that the Bidder has not directly or indirectly induced or solicited any other Bidder to submit a sham bid, or any
other person, firm or corporation to refrain from bidding, and that the Bidder has not, in any manner, sought by collusion to secure any advantage over other bidders.
In submitting this proposal, the Bidder agrees that: A. Bidder has carefully examined the specifications and all provisions relating to the items to be furnished, or the work to be done, attached and incorporated into the proposal and understands the meaning, intent and requirements of them, and agrees to the same. B. Bidder will, for the prices quoted, enter into a written contract and furnish the item(s) or complete the work in the time specified, and in strict conformity with the City of Carlsbad
specifications for the item(s) or work. 1. FORMS If the Purchasing Officer furnishes forms and specifications for proposals and bids, no proposals or bids will receive consideration unless made upon forms so furnished. BIDS MUST BE
SUBMITTED IN A SEALED ENVELOPE WITH BID NUMBER ON THE OUTSIDE, COMPLETE WITH THE SPECIFICATIONS AS FURNISHED AND DELIVERED TO CITY OF CARLSBAD PURCHASING DEPARTMENT OR DEPOSITED IN THE BID BOX AT 1635 FARADAY
AVENUE, CARLSBAD CA 92008-7314, PRIOR TO THE TIME SET FOR OPENING. 2. PRICES
All prices and notations must be in ink or typewritten. Mistakes may be crossed out and corrections typed or written with ink next to them. Such modifications must be initialed in ink by the person signing the bid. Bids shall indicate the unit price extended to indicate the total price for each item bid. Any difference between the unit price correctly extended and the total price shown for all items bid shall be resolved in favor of the unit price, except when the Bidder clearly indicates that the total price for all items bid is based on consideration of being awarded the entire lot, and that an adjustment of the total price is being made in consideration of receiving the entire bid.
Attachment B
Page 2 of 11
3. GUARANTEE OF GOOD FAITH (As required on Proposal Form)
Cash, uncertified personal and company checks and certificates of deposit are not acceptable as a guarantee of good faith. Each proposal must be accompanied by an unconditional certified check, or a bank or postal money order, or bid bond executed as surety by a corporation authorized to issue surety bonds in the State of California. Such check, money order or bond shall be made payable to the City of Carlsbad and shall be in the amount specified on the Proposal Form. If the Bidder fails to execute the contract within ten (10) days from the date of the City’s mailing of notice that the contract is ready for signature, the City will either award the contract to the next lowest Bidder or will reject all other bids and call for new bids. The Bidder who has failed to so execute the contract shall be liable to the City for the sum--not exceeding the amount of the check, money order or bond, by which the amount of the contract covering the proposal, executed by and between the City and a third party, may exceed the amount bid by the original successful Bidder. Such portion of check, money order or bond as equals the sum shall be declared forfeited to the City of Carlsbad and shall be collected and paid to the City. The Bidder may also be subject to debarment or suspension.
IMPORTANT: Failure to furnish a proper guarantee of good faith with the bid when such is required will automatically void the bid.
4. ITEMS OFFERED
If the item offered has a trade name, brand and/or catalog number, such shall be stated in the bid. If the Bidder proposes to furnish an item of a different manufacturer or vendor other than that mentioned in the bid specifications, Bidder must specify maker, brand, quality, catalog number, or other trade designation. Unless such is noted on the bid form, it will be deemed that the item offered is that designated in the bid specifications even though the bid may state "or equal". 5. SAMPLES Samples, when required, shall be furnished prior to bid closing date and time, or within time specified in the bid. The City reserves the right to reject bids submitted without the required samples, or to require samples for alternate bids or items offered as "equals". Samples of items, when required, must be furnished free of expense to the City. If they are not destroyed by tests, samples will, upon request, be returned at the bidder's expense.
6. ALTERNATIVE PROPOSALS
To be responsive to the bid, Bidder must submit a proposal that meets all specific bid requirements. Bidder may propose "equals" as provided for in accordance with Item 8 of these General Provisions. Once Bidder has proposed a product which is responsive to the specification,
Bidder may thereafter include with the bid any additional proposals or alternative products that are not "equals" but that Bidder believes can or may meet or exceed City's requirements, and which offer City additional advantages or benefits based on the state of the art that were not, or could not, be contemplated by City when the requirements were prepared. The City reserves the right to evaluate and accept or reject such alternatives, as though they were part of the original specifications, without advertising for further bids, or to re-advertise based on such proposed state
of the art alternatives when in the best interests of the City. Any awards so made will be based on cost analysis considerations that result in the optimum economic advantage to the City.
Attachment B
Page 3 of 11
7. EXPIRATION OF BID
All bids shall be considered as firm for a period of ninety (90) calendar days, commencing the day following the date of bid closing and expiring at midnight of the last day, unless otherwise stated in the body of the solicitation. The Bidder may specify a date that the bid expires, provided the date is specific and is entered on the Proposal or Request for Bid form. 8. BRAND NAME Whenever reference to a specific brand name is made in this Request for Bid, it is illustrative and to be construed as a specification which describes a component that has been tested or evaluated by the City as best meeting the specific operational, design, performance, maintenance, quality or reliability standards and requirements of the City, thereby incorporating these requirements by reference within the specification. An equivalent or "equal" may be offered by the Bidder, subject to testing and evaluation at the option of the City or prior to and after the award of bid. The City reserves the sole right to reject a substituted component that will not fulfill
requirements. It shall be the sole responsibility of the Bidder to provide at Bidder's expense any product information, test data, and other information or documents the City may require to fully evaluate or demonstrate the acceptability of the offered substitute. Where appropriate,
independent testing or evaluation at qualified test facilities, at Bidder's expense, including destructive testing, may be required as a condition of acceptance.
9. VERIFY BID PRICES Bidders must verify their price quotations prior to bid submission, as withdrawal or correction may not be permitted after the bid has been opened. 10. DELIVERY A. Bidder shall state delivery terms on the Proposal Form unless already specified, in which case delivery shall be made within the time set forth. Where time is stated in a number of days, it shall include Saturdays, Sundays and holidays. Delivery is part of the consideration and must be adhered to as specified. B. Bidder will not be held liable for failure to make delivery because of strikes, conscription of property, governmental regulations, acts of God, or any other cause beyond the
bidder’s reasonable control; provided a written extension of time is obtained from the City Manager.
C. All prices shall be F.O.B. destination. Bids other than F.O.B. destination shall be considered non-responsive and will be rejected. Prices shall include all freight, delivery and set-up charges.
11. FIRM PRICES AND PRICE ADJUSTMENT Prices on bid shall be firm prices not subject to escalation. In the event the specifications provide for escalation, the maximum limit shall be shown, or the bid shall not be considered. In
the event of a decline in market price(s) below the price(s) bid, the City of Carlsbad shall receive the benefit of such decline.
Attachment B
Page 4 of 11
Manufacturer's general price increases to the trade or industry may be passed on to the City. Prices bid must be firm for the first ninety (90) days on an annual agreement; with a thirty (30)
day notification of any price increases thereafter. If any price increase occurs, there will be a one (1) week, or one time, order protection provided at the last effective price. All price increases or notices must be in writing from not only the vendor but also the manufacturer. The City reserves the right NOT to accept the request. 12. TAXES Each bidder shall include all applicable sales taxes as a separate item in their bid. The amount of local city sales tax included in any bid submitted by a local (Carlsbad) vendor shall be credited by the City against said bid. The City is exempt from Federal Excise Tax. 13. MODIFICATION OR WITHDRAWAL OF BIDS Bids may be modified or withdrawn by written notice received prior to the exact hour and date
specified for receipt of bid. A bid may also be withdrawn in person by a Bidder, or the Bidder’s authorized representative, prior to the exact hour and date set for receipt of bids.
14. LATE BIDS AND MODIFICATIONS OR WITHDRAWALS Bids, modifications of bids, or withdrawals received at the office designated in the solicitation,
after the exact hour and date specified for receipt, will not be considered. They will be rejected as a late bid and will be returned to bidder unopened. 15. NO BIDS If no bid is to be submitted, the bid should be marked "NO BID" and reason stated on the Proposal Form, which should be returned in order to maintain the Bidder's name in City's vendor file for further solicitations. A letter or postcard may be submitted instead a blank proposal form. If a Bidder fails to respond to two Requests to Bid without returning a "NO BID" response, the Purchasing Officer reserves the right to delete the Bidder from the vendor file for future solicitation. 16. CONFIDENTIAL INFORMATION
Any information deemed confidential or proprietary should be clearly identified by the Bidder as such. It will be protected and treated with confidentiality only to the extent permitted by California state law considering public information. Otherwise the information shall be
considered a public record. Any data to be returned should be so marked and will be returned if not essential to the bid or contract record.
17. SIGNATURE All bids must be signed, with the firm named as indicated. A bid by a corporation must be signed by a duly authorized officer, employee or agent, with his or her title. Obligations assumed by such signature must be fulfilled.
Attachment B
Page 5 of 11
18. QUALITY
Unless otherwise required in the specifications, all goods furnished shall be NEW and UNUSED and the BEST OF THEIR KIND. 19. LITIGATION WARRANTY The Bidder, by bidding, warrants that Bidder is not currently involved in litigation, arbitration, or an administrative proceeding concerning the materials, or Bidder's performance, concerning the same or similar material to be supplied pursuant to this contract or specification, and that no judgments, awards or administrative determinations have been made against Bidder, on the basis of Bidder's performance in supplying or installing the same or similar material, unless such fact is disclosed to the City in the bid. Disclosure will not disqualify the Bidder. The City reserves the right to evaluate bids, on the basis of the facts surrounding such litigation, arbitration, or administrative proceeding and to require Bidder to furnish the City with a surety bond executed by a surety company authorized to do business in the State of California and
approved by the City of Carlsbad, in a sum equal to one hundred percent (100%) of the contract price, conditional on the faithful performance by Bidder of the contract, in the event the bid is awarded to Bidder, notwithstanding the litigation, arbitration, or administrative proceeding.
20. ROYALTIES, LICENSES AND PATENTS
Unless otherwise specified, the Bidder shall pay all royalties, license and patent fees. The Bidder warrants that the materials to be supplied do not infringe any patent, trademark or copyright, and further agrees to defend any and all suits, actions and claims for infringement that are brought against the City, and to defend, indemnify and hold harmless the City from all loss or damages whether general, exemplary or punitive, as a result of any actual or claimed infringement asserted against the City, the Bidder, or those furnishing material to Bidder pursuant to this contract. 21. PERFORMANCE STANDARDS Performance of work, and acceptability of equipment or materials supplied, pursuant to any contract or award, shall be to the satisfaction of the City. 22. WARRANTIES
A. All material, labor or equipment provided under the contract shall be warranted by Bidder, and/or manufacturer, for at least twelve (12) months after final acceptance by City, except
automotive equipment which will be warranted for a minimum 12,000 miles or 12 months, whichever occurs first. Greater warranty protection will be accepted. Lesser warranty protection must be indicated by Bidder on the bid proposal as an exception.
B. Bidder shall be considered primarily responsible to the City for all warranty service, parts and labor applicable to the goods or equipment provided by Bidder under this bid or award, irrespective of whether Bidder is an agent, broker, fabricator or manufacturer's dealer. Bidder shall be responsible for ensuring that warranty work is performed at a local agency or facility convenient to City and that services, parts and labor are available and provided
to meet City's schedules and deadlines. City may require Bidder to post a performance bond after contract award to guarantee performance of these obligations. Bidder may
Attachment B
Page 6 of 11
establish a service contract with a local agency satisfactory to City, to meet this obligation if Bidder does not ordinarily provide warranty service.
23. ADDENDA The effect of all addenda to the bid documents shall be considered in the bid, and said addenda shall be made part of the bid documents and shall be returned with them. Before submitting a bid, each Bidder shall ascertain whether or not any addenda have been issued, and failure to cover in this bid any such addenda issued, may render the bid invalid and result in its rejection. 24. SPECIFICATIONS TO PREVAIL The detailed requirements of the specifications shall supersede any specific requirement of these General Provisions which are in conflict therewith. The City reserves the right of being sole judge of bid meeting specifications. Requests for interpretation of bid specifications shall be made in writing to the Purchasing Officer at least five days prior to the date of the bid
opening. 25. FAITHFUL PERFORMANCE BOND
The successful Bidder may be required to furnish the City with security for the faithful performance of the contract, in a sum up to One Hundred Percent (100%) of the amount of the
contract price. This security may take the form of a bond executed by a surety company authorized to do business in the State of California and approved by the City or Carlsbad, or a money order or certified check drawn on a solvent bank. Such bond or deposit shall be forfeited to the City in the event the Bidder fails or refused to fulfill the requirements and all terms and conditions of the contract. 26. AWARD OF CONTRACT A. Bids will be analyzed and the award will be based on the best value to the City. The decision will be based on objective and other predetermined criteria as set forth in the Invitation to Bid. Factors to be considered include, but are not limited to: cost, conformance to the solicitation, supplier’s qualifications, past performance, customer service and warranties.
B. The City reserves the right to perform a pre-award survey of the bidder to determine capability to perform, including but not limited to, facilities, financial responsibility, materials/supplies, and past performance. The determination of the City as to the
bidder's prospective ability to perform the contract shall be conclusive. C. The City reserves the right to reject any item or items therein; to waive informalities,
technical defects and minor irregularities in bids received; and to select the bid(s) deemed most advantageous to the City. The City will however consider bids submitted on an "all or nothing" basis if the bid is clearly designated as such. D. The City reserves the right to award one or more contracts on the bids submitted, whether by award of all items to one Bidder, or by award of separate items or groups of items to
various Bidders, as the interests of the City may require, unless the Bidder clearly specifies otherwise in his bid.
Attachment B
Page 7 of 11
E. Upon acceptance by the City of Carlsbad, the solicitation, bid, proposal, or price quotation, and a purchase order issued to the successful Bidder within the time specified, shall be
deemed to result in a binding contract without further action required by either party. Items are to be furnished as described in the bid and in strict conformity with all instructions, conditions, specifications and drawings contained in the complete contract. 27. DOCUMENTATION Due to the time constraints that affect contract performance, all required documents, certificates of insurance and bonds or deposits shall be provided to the City (Attention: Purchasing Department) within ten (10) days following award, or date of request, by City, whichever is later. Any failure to comply may result in bid being declared non-responsive and rejected, and/or at City's option the bid bond will be attached for damages suffered. 28. PURCHASE ORDERS
All goods and services will be ordered by means of a Purchase Order. (THE CITY WILL NOT BE RESPONSIBLE FOR ARTICLES OR SERVICES FURNISHED WITHOUT A PURCHASE ORDER.)
29. SELLER'S INVOICE
Invoices shall be prepared and submitted in duplicate to: Accounts Payable, City of Carlsbad, 1635 Faraday Avenue, Carlsbad, CA 92008-7314. Separate invoices are required for each Purchase Order. Invoices shall contain the following information: Purchase Order number, item number, description of supplies or services, sizes, units of measure, quantities, unit prices and extended totals. 30. INSPECTION AND ACCEPTANCE Inspection and final acceptance will be at destination unless specified otherwise, and will be made by the City department shown in the "Ship To:" address or other duly authorized representative of the City. Until delivery and final acceptance, and after any rejection, risk of loss will be on the Bidder, unless loss results from the sole negligence of the City. 31. LOST AND DAMAGED SHIPMENTS
Risk of loss or damage to items prior to the time of their receipt and final acceptance by the City is upon the Bidder. The City has no obligation to accept damaged shipments and reserves
the right to return, at the Bidder's expense, damaged merchandise even if the damage was not apparent or discovered until after receipt of the items.
32. LATE SHIPMENTS Bidder is responsible to notify the City department receiving the items and the Purchasing Officer, of any late or delayed shipments. The City reserves the right to cancel all or any part of an order if the shipment is not made as promised.
Attachment B
Page 8 of 11
33. COMPLIANCE WITH INDUSTRIAL SAFETY CODES
All equipment, instruction manuals, spare parts and other items furnished shall, where applicable, conform with the Safety Orders of the California Division of Industrial Safety. Material Safety Data Sheets (MSDS) shall be supplied, for each applicable item, with the initial order. All containers shall be labeled per OSHA specifications. 34. WAIVER The failure of the City to enforce a particular condition or provision of any contract awarded hereunder shall not constitute a waiver of that provision or condition or its enforceability by the City. 35. CONSEQUENCES OF VIOLATIONS OF LAW REGARDING ANTI-COMPETITIVE
BUSINESS PRACTICES OR UNFAIR TRADE PRACTICES
Any acts or omissions of Bidder in violation of federal, state or municipal law, or City policies and regulations regarding anti-competitive practices, unfair trade practices, collusion, contingent fees, gratuities, kickbacks, contemporaneous employment or similar violations
creating an unfair influence on the public bidding and award process, pertaining to this contract or proposal, may void this contract. In addition to all other remedies or damages allowed by law, Bidder shall be liable to City for all damages City thereby suffers or incurs, including costs
for substitute performance, and may also be subject to debarment. 36. CONFLICT OF INTEREST No employee, or member of the employee's immediate family, or elected or appointed member of City government, may participate directly or indirectly in the procurement process pertaining to this bid, if they: A. Have a financial interest, or other personal interest, which is incompatible with the proper discharge of their official duties in the public interest, or would tend to impair their independence, judgment or action in the performance of their official duties. B. Are negotiating for, or have an arrangement concerning, prospective employment with Bidder.
The Bidder warrants to the best of his knowledge that the submission of the bid will not create such conflict of interest. In the event such a conflict occurs, the Bidder is to report it immediately
to the Purchasing Officer. For breach or violation of this warranty, the City shall have the right to annul this contract, at its discretion, without liability. Bidder may also be subject to damages and/or debarment or suspension.
37. CITY PROVISIONS TO PREVAIL Except as specified in the specifications, the City's standard General Provisions shall govern any contract award. Any standard terms and conditions of Bidder, submitted by Bidder, shall not be acceptable to City unless expressly assented to by City by separate documents. The
City reserves the right to reject Bidder's bid as non-responsive, to consider the bid without Bidder's standard terms and conditions, or to require Bidder to delete reference to such, as a condition of evaluation or award of the bid. If, after award of contract, Bidder (contract vendor)
Attachment B
Page 9 of 11
shall provide materials, or services, accompanied by new or additional standard terms or conditions, they too shall be considered void, and City may require deletion thereof as a further
condition of performance by vendor. To the extent not otherwise provided for by the contract documents, the California Commercial Code shall apply. 38. AMENDMENTS AND MODIFICATIONS The Purchasing Officer may at any time, by a written order, and without notice to the sureties, make a modification to the contract or an amendment to the Purchase Order, within the general scope of this contract, in (1) drawings, designs, or specifications, where the supplies to be furnished are to be specially manufactured for the City in accordance therewith; (2) method of shipment or packing; and (3) place of delivery. If any such change causes an increase or decrease in the cost of, or the time required for, performance of this contract, whether changed or not changed by any such order, an equitable adjustment shall be made by written modification of the contract or amendment to the Purchase Order. Any claim by the Bidder for adjustment under this clause must be asserted within 30 days from the date of receipt by the
Bidder of the notification; provided that, if Purchasing Officer decides that the facts justify such action, the Purchasing Officer may receive and act upon any such claim, if asserted prior to final payment under this contract. Failure to agree to any adjustment shall be a dispute,
concerning a question of fact, within the meaning of the clause of these provisions entitled "Disputes". However, nothing in this clause shall excuse the Bidder from proceeding with the contract as changed.
39. DISPUTES Except as otherwise provided in this contract, any dispute concerning a question of fact arising under this contract, which is not disposed of by agreement, shall be decided by the Purchasing Officer, who shall reduce this decision to writing or mail or otherwise furnish a copy thereof to the Bidder. The decision of the Purchasing Officer shall be final and conclusive unless, within 30 days from the date of receipt of such copy, the Bidder mails or otherwise furnishes to the Purchasing Officer a written appeal addressed to the City Manager. The decision of the City Manager, or his duly authorized representative for the determination of such appeals, shall be final and conclusive. In connection with any appeal proceeding under this clause, the Bidder shall be afforded an opportunity to be heard and to offer evidence in support of the Bidder’s appeal. Pending final decision of a dispute hereunder, the Bidder shall proceed diligently with the performance of the contract, and in accordance with the Purchasing Officer's decision.
40. TERMINATION FOR DEFAULT
A. The City of Carlsbad, California, hereafter referred to as the City may by written notice of default to the Bidder (subject to the provisions of paragraph (C) below) terminate the whole or any part of this contract, in any one of the two following circumstances:
1. If the Bidder fails to make delivery of the supplies or to perform the services, within the time specified herein, or any extension thereof; or 2. If the Bidder fails to perform any of the other provisions of this contract, or so fails to make progress to endanger performance of this contract in accordance with its
terms, and in either of these two circumstances does not cure such failure within a period of ten (10) days after receipt of notice from the Purchasing Officer specifying such failure.
Attachment B
Page 10 of 11
B. In the event the City terminates this contract, in whole or in part, as provided in paragraph
(A) of this clause, the City may procure, upon such terms and in such manner as the Purchasing Officer may deem appropriate, supplies or services similar to those so terminated, and the Bidder shall be liable to the City for any excess costs for such similar supplies or services; provided, that the Bidder shall continue the performance of this contract to the extent not terminated under the provisions of this clause. C. The Bidder shall not be liable for any excess costs, if the failure to perform the contract arises out of causes beyond the control and without the fault or negligence of the Bidder. Such causes may include, but are not restricted to, acts of God or of the public enemy, acts of the City in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restriction, strikes, freight embargoes, and unusually severe weather; but in every case the failure to perform must be beyond the control and without the fault or negligence of the Bidder.
D. If, after notice of termination of this contract under the provisions of this clause, it is determined for any reason that the Bidder was not in default under the provisions of this clause, or that the default was excusable under the provisions of this clause, the rights
and obligations of the Bidder shall be the same as if notice of termination for convenience had been issued pursuant to such clause.
41. TERMINATION FOR CONVENIENCE The Purchasing Officer, by written notice, may terminate this contract, in whole or in part, when it is in the best interest of the City. If this contract is for supplies and is so terminated, the Bidder shall be compensated in accordance with his auditable costs to point of Notification of Termination. To the extent that this contract is for services and is so terminated, the City shall be liable only for payment in accordance with the payment provisions of this contract, for the actual services rendered to the effective date of termination. 42. LABOR PRACTICES The Bidder shall comply with all Federal and State Laws, and City Ordinances where applicable, relating to fair labor practices and discrimination in the employment of persons.
43. INSURANCE Unless otherwise provided, Bidder shall cause City to be named as an additional insured on
liability and/or products liability insurance concerning Bidder's performance, products, or equipment in amounts, scope and duration as may be required by the Purchasing Officer. Bidder shall provide evidence of Workers' Compensation Insurance covering all employees.
44. LIABILITY AND INDEMNIFICATION Bidder agrees to defend, indemnify, protect and hold City, and its agents, officers and employees, harmless from and against any and all claims asserted, or liability established for damages or injuries to any person or property, including injury to Bidder's employees, agents
or officers which arise from or are connected with, or are caused or claimed to be caused by the acts or omissions of Bidder, and its agents, officers or employees, in performing the work or services or supplying the materials or equipment herein, and all expenses of investigating
Attachment B
Page 11 of 11
and defending against same; provided, however, that Bidder's duty to indemnify and hold harmless shall not include any claims or liability arising from the established sole negligence
or willful misconduct of the City, its agents, officers or employees. This shall not prejudice the right of the City to appear in such suit, participate in the defense, and take such actions as may be necessary to protect the interests of the City. 45. EQUAL OPPORTUNITY POLICY The City of Carlsbad will not discriminate with regard to race, religious creed, color, national origin, ancestry, disability, marital status, veteran’s status, sex, or sexual orientation or age in the award of contracts. 46. ANNUAL APPROPRIATION OF FUNDS Multi-year term supply and service contracts and leases are subject to annual appropriation of funds by the City Council. Payments made under term contracts and leases are considered
items of current expense. Purchase Orders are funded when issued, therefore are current expense items and are not subject to any subsequent appropriation of funds.
In the event sufficient funds are not appropriated for the payment of lease payments, or anticipated term contract payments, required to be paid in the next occurring lease or contract term, and if no funds are legally available from other sources, the lease or contract may be
terminated at the end of the original term or renewal term and the City shall not be obligated to make further payments beyond the then current original or renewal term. The City will provide notice of its inability to continue the lease or contract at such time as the Purchasing Officer is aware of the non-appropriation of funds. However, failure to notify does not renew the term of the lease or contract. If a lease is canceled, the events of default will occur as described in the lease and/or Item 40 of these General Provisions. The City has no monetary obligation in event of termination or reduction of a term contract, since such contracts represent estimated quantities and are not funded as a contract except to the extent of the Purchase Orders already issued. 47. TEN PERCENT (10%) RETENTION The City reserves the right to withhold a ten percent (10%) retention on all Purchase orders until the supplies, services or equipment have been accepted.
48. QUANTITIES
Estimated quantities are given as a basis for comparison of bids. The City does not, expressly or by implications, agree that the actual quantities will be purchased.
ATTACHMENT C: SAMPLE MASTER PURCHASE AND SERVICE AGREEMENT
[Remainder of this page intentionally left blank]
1 General Counsel Approved Version 1/17/18
SAMPLE ONLY – DO NOT COMPLETE
MASTER PURCHASE AND SERVICE AGREEMENT FOR «PROJNAME»
«COMPANY» THIS AGREEMENT is made and entered into as of the ____SAMPLE__________ day of _____SAMPLE______, 20___, by and between the Carlsbad Municipal Water District, a Public Agency organized under the Municipal Water Act of 1911, and a Subsidiary District of the City of
Carlsbad, hereinafter referred to as "CMWD", and «COMPANY», a «Entity», hereinafter referred to as "Seller."
RECITALS
A. The parties to this Agreement will purchase from Seller and Seller will sell to
CMWD, «PROJNAME» during the term of this Agreement. B. To expedite these contemplated purchases, the parties are willing to enter into this
exclusive Agreement that sets forth the terms and conditions that will govern all such transactions between them.
NOW, THEREFORE, in consideration of these recitals and the mutual covenants contained herein, CMWD and Seller agree as follows:
1. Definitions
1.1. Buyer. With respect to purchase orders issued by CMWD, the term “Buyer” means Carlsbad Municipal Water District.
1.2. Products. The term “Product” means those goods listed in Table 1 for which Buyer issues to Seller a purchase order during the term of this Agreement. Products and specified terms
are described in Table 1 and Exhibit “A” – Request for Bid, which are attached hereto and incorporated herein by this reference in accordance with the terms and conditions set forth in this Agreement. In the event of an inconsistency between the Product description of Table 1 and
Exhibit “A”, the inconsistency will be resolved with Exhibit “A” taking precedence.
2. Issuance of Purchase Orders. Buyer may issue purchase orders to Seller from time to time for the purchase of Products. Each purchase order shall contain a description of the Products
ordered, the quantities and prices, the terms and place of delivery, and will reference Carlsbad Municipal Water District Bid #__________. Every purchase order issued by Buyer to Seller following the date of this Agreement and bearing such a notation shall be governed by and be
deemed to include the provisions of this Agreement, Exhibit “A” or the placed purchase order, the inconsistency will be resolved in the following descending order of precedence: (1) this Agreement, (2) Exhibit “A”, and (3) the purchase order.
CMWD will indicate its specific requirements on its purchase order documents including but not limited to delivery address and instructions. There will be no minimum order and all items must be available for the term of this Agreement. All items will be delivered F.O.B. Destination, Freight Prepaid and Allowed, and at the prices set forth in Table 1.
3. Term. This Agreement will be effective for a period of «PSATermWord» («PSATerm») years from the date first above written. The City Manager may amend the Agreement to extend
2 General Counsel Approved Version 1/17/18
it for «PSAExtWords» («PSAEXT») additional «EXTLengthWords» («EXTLength») year periods
or parts thereof in an amount not to exceed «EXTCostWord» («EXTCostNum») per Agreement year. Extensions will be based upon a satisfactory review of Contractor's performance, City needs, and appropriation of funds by the City Council. The parties will prepare a written
amendment indicating the effective date and length of the extended Agreement. 4. Compensation. The total amount for the purchase of «PROJNAME» over the «PSATermWord» («PSATerm») year period shall not exceed «COSTWORDS» dollars («COST»). The annual amount for all purchases will not exceed «EXTCostWord» dollars
(«EXTCostNum») per Agreement year during the initial «PSATermWord» («PSATerm») year. The City reserves the right to withhold a ten percent (10%) retention until City has accepted the work and/or Services specified in Exhibit “A”.
5. Termination. CMWD may terminate this Agreement at any time with thirty (30) days written notice to Seller. Seller may terminate this Agreement at any time with ninety (90) days written notice to CMWD.
6. Delivery.
6.1. The delivery for purchase orders placed pursuant to this Agreement shall be as specified in the City’s purchase order.
6.2. Time is of the essence on orders and delay in delivery will cause injury to the Buyer.
Should the Seller be obstructed or delayed in the production or delivery of Product(s) required hereunder by any act or omission of the City or by strikes, and act of God, or by no fault of the Seller in its ability to obtain materials (“Delaying Event”), then the time for delivery of the order shall be extended for such period as may be either agreed to between Seller and City or equal to the period of time of the Delaying Event.
6.3. Notwithstanding any other provision of this Agreement, if delivery cannot be made within forty-five (45) days after receipt of a purchase order, Buyer may, upon knowledge of the fact and regardless whether or not the delay would be excusable, terminate the purchase order by written notice to Seller. The termination shall be without cost to Buyer and shall discharge all
obligations and liabilities of the Buyer/Seller under the purchase order except as to Products previously delivered and accepted by Buyer.
7. Passage of Title and Risk of Loss. Unless otherwise specified in a particular purchase
order placed pursuant to this Agreement, title to and risk of any loss of or damage to the Products shall pass from Seller to Buyer when the Products are accepted in writing by the Buyer using a shipping acknowledgement form submitted by the Seller with each shipment.
8. Inspection of Product. Seller shall inspect and test all Products prior to shipment to Buyer. In addition, all Products shall be subject to final inspection and acceptance by Buyer at Buyer’s facility. Final inspection and acceptance or rejection will be made by Buyer within thirty
(30) days after receipt of Products, and failure of Buyer to reject any Product within thirty (30) days after receipt shall constitute acceptance. Should Buyer reject any Product for failure to conform to the requirements of a purchase order, Buyer shall notify Seller in writing of the
rejection, giving detailed reasons for the rejection. Seller shall then have the option to repair or replace the nonconforming Product within ten (10) days at Buyer’s designated delivery facility. If Seller fails to act to correct any nonconforming Product within this time period, then Buyer may
3 General Counsel Approved Version 1/17/18
return any nonconforming Product(s) to Seller. Rejected items to be returned to Seller shall be
shipped at Seller’s risk and expense.
9. Warranty. Seller warrants to Buyer that all Products delivered under this Agreement shall be free from defects in materials and workmanship, that all Products will conform to the requirements of the order including, but not limited to, the applicable descriptions, specifications, and drawings agreed to by the parties and, to the extent the items are not manufactured pursuant to detailed designs furnished by Buyer, that all Products will be free from defects in design and suitable for the intended purposes. In addition, Seller warrants that all Products will, at the time of deliver, be free from any security interest or other lien or encumbrance.
10. Indemnification. Seller agrees to indemnify and hold harmless CMWD and the City of Carlsbad and its officers, officials, employees and volunteers from and against all claims, damages, losses and expenses including attorneys fees arising out of the performance of the work described herein caused by any willful misconduct or negligent act or omission of the Seller, any subcontractor, anyone directly or indirectly employed by any of them or anyone for whose acts any of them may be liable. The parties expressly agree that any payment, attorney’s fee, costs or expense CMWD or the City of Carlsbad incurs or makes to or on behalf of an injured employee under CMWD’s self-administered workers’ compensation is included as a loss, expense or cost for the purposes of this section, and that this section will survive the expiration or early termination of this Agreement. 11. Insurance. Seller will obtain and maintain for the duration of the Agreement and any and all amendments, insurance against claims for injuries to persons or damage to property which may arise out of or in connection with performance of the services by Seller or Seller’s agents, representatives, employees or subcontractors. The insurance will be obtained from an insurance carrier admitted and authorized to do business in the State of California. The insurance carrier is required to have a current Best's Key Rating of not less than "A-:VII"; OR with a surplus line insurer on the State of California’s List of Approved Surplus Line Insurers (LASLI) with a rating in the latest Best’s Key Rating Guide of at least “A:X”; OR an alien non-admitted insurer listed by the National Association of Insurance Commissioners (NAIC) latest quarterly listings report. 10.1 Coverages and Limits. Seller will maintain the types of coverages and minimum limits indicated below, unless Risk Manager or City Manager approves a lower amount. These minimum amounts of coverage will not constitute any limitations or cap on Seller’s indemnification obligations under this Agreement. City, its officers, agents and employees make no representation that the limits of the insurance specified to be carried by Seller pursuant to this Agreement are adequate to protect Seller. If Seller believes that any required insurance coverage is inadequate, Seller will obtain such additional insurance coverage, as Seller deems adequate, at Seller’s sole expense. The full limits available to the named insured shall also be available and applicable to the City as an additional insured. 10.1.1 Commercial General Liability Insurance. $2,000,000 combined single-limit per occurrence for bodily injury, personal injury and property damage. If the submitted policies
contain aggregate limits, general aggregate limits will apply separately to the work under this Agreement or the general aggregate will be twice the required per occurrence limit. 10.2. Additional Provisions. Seller will ensure that the policies of insurance required under this Agreement contain, or are endorsed to contain, the following provisions:
4 General Counsel Approved Version 1/17/18
10.2.1 CMWD will be named as an additional insured on Commercial General
Liability which shall provide primary coverage to the City. 10.2.2 Seller will obtain occurrence coverage, excluding Professional Liability,
which will be written as claims-made coverage. 10.2.3 This insurance will be in force during the life of the Agreement and any extensions of it and will not be canceled without thirty (30) days prior written notice to City sent by certified mail pursuant to the Notice provisions of this Agreement.
10.3 Providing Certificates of Insurance and Endorsements. Prior to CMWD’s execution of this Agreement, Seller will furnish certificates of insurance and endorsements to CMWD.
10.4 Failure to Maintain Coverage. If Seller fails to maintain any of these insurance coverages, then CMWD will have the option to declare Seller in breach, or may purchase replacement
insurance or pay the premiums that are due on existing policies in order to maintain the required coverages. Seller is responsible for any payments made by CMWD to obtain or maintain insurance and CMWS may collect these payments from Seller or deduct the amount paid from
any sums due Seller under this Agreement. 10.5 Submission of Insurance Policies. CMWD reserves the right to require, at anytime,
complete and certified copies of any or all required insurance policies and endorsements. 12. Notices. All notices and other communications require or authorized under this Agreement shall be given in writing either by personal delivery or by first class mail addressed to the respective party.
The name of the persons who are authorized to give written notice or to receive written notice on behalf of City and on behalf of Seller under this Agreement are: For City: For Seller:
Name «PROJMGR» Name «CONTACTFIRST» «CONTACTLAST»
Title «PMTitle» Title Project Manager Dept «Pmdept» Address «Companyaddress» CITY OF CARLSBAD «Companycity», «COMPANYSTATE»
«COMPANYZIP»
Address «Pmaddress» Phone «CONTACTPHONE»
«PMCity», «PMSTATE»
«PMZip»
Email «contactemail»
Phone «PROJMGRPHONE»
Each party will notify the other immediately of any changes of address that would require
any notice or delivery to be directed to another address.
13. Compliance with Laws. Seller will comply with all applicable local, state and federal laws
and regulations prohibiting discrimination and harassment and, if required, will obtain and
5 General Counsel Approved Version 9/27/17
maintain a City of Carlsbad Business License for the term of this Agreement and any amendments
to the Agreement.
14. Claims and Lawsuits. By signing this Agreement, Seller agrees it may be subject to civil penalties for the filing of false claims as set forth in the California False Claims Act, Government Code sections 12650, et seq., and Carlsbad Municipal Code sections 3.32.025 et seq. Seller further acknowledges that debarment by another jurisdiction is grounds for CMWD to terminate this Agreement.
15. Venue and Jurisdiction. Seller agrees and stipulates that the proper venue and jurisdiction for resolution of any disputes between the parties arising out of this Agreement is the Superior Court of California, County of San Diego, California.
16. Assignment. Seller may not assign this Agreement or any part of it, nor may it assign any monies due or that may become due under it, without the prior written consent of CMWD.
17. Amendments. This Agreement may be amended by mutual consent of CMWD and Contractor. Any amendment will be in writing, signed by both parties, with a statement of estimated changes in charges or time schedule.
18. Authority. The individuals executing this Agreement and the instruments referenced in it on behalf of Seller each represent and warrant that they have the legal power, right and actual authority to bind Seller to the terms and conditions of this Agreement.
Executed by Contractor this___________ day of _______________________, 20____.
SELLER CARLSBAD MUNICIPAL WATER DISTRICT, a Public Agency organized
under the Municipal Water Act of 1911, and a Subsidiary District of the City of Carlsbad
«COMPANY», a «Entity»
By: By:
(sign here) [INSERT TITLE OF PERSON
AUTHORIZED TO SIGN (City Manager or Mayor or Division Director as authorized by the City Manager)]
(print name/title) ATTEST:
By:
(sign here) BARBARA ENGLESON
City Clerk
(print name/title)
Proper notarial acknowledgment of execution by Contractor must be attached. If a corporation, Agreement must be signed by one corporate officer from each of the following two groups:
Group A Group B Chairman, Secretary,
6 General Counsel Approved Version 9/27/17
President, or Vice-President Assistant Secretary, CFO or Assistant Treasurer
Otherwise, the corporation must attach a resolution certified by the secretary or assistant secretary under corporate seal empowering the officer(s) signing to bind the corporation.
CARLSBAD MUNICIPAL WATER DISTRICT, a Public Agency organized under the Municipal Water Act of 1911, and a Subsidiary District of the City of Carlsbad
APPROVED AS TO FORM:
CELIA A. BREWER, General Counsel BY: _____________________________ Assistant General Counsel
7 General Counsel Approved Version 9/27/17
EXHIBIT “A” TABLE 1 COST OF SERVICES
ITEM
NO.
UNIT QTY DESCRIPTION UNIT
PRICE
«TASK1» «UOM1» «QTY1» «SOW1» «SOWCOST1»
«TASK2» «UOM2» «QTY2» «SOW2» «SOWCOST2»
«TASK3» «UOM3» «QTY3» «SOW3» «SOWCOST3»
«TASK4» «UOM4» «QTY4» «SOW4» «SOWCOST4»
«TASK5» «UOM5» «QTY5» «SOW5» «SOWCOST5»
«TASK6» «UOM6» «QTY6» «SOW6» «SOWCOST6»
«TASK7» «UOM7» «QTY7» «SOW7» «SOWCOST7»
«TAS
K8»
«UO
M8»
«QT
Y8»
«SOW8» «SOWCOST8»
«TASK9» «UOM9» «QTY9» «SOW9» «SOWCOST9»
«TASK10» «UOM10» «QTY10»
«SOW10» «SOWCOST10»
«TASK11» «UOM11» «QTY11»
«SOW11» «SOWCOST11»
«TASK12» «UOM12» «QTY12»
«SOW12» «SOWCOST12»
«TASK13» «UOM13» «QTY13»
«SOW13» «SOWCOST13»
«TASK14» «UOM14» «QTY14»
«SOW14» «SOWCOST14»
«TASK15» «UOM15» «QTY15»
«SOW15» «SOWCOST15»
«TASK16» «UOM16» «QTY16»
«SOW16» «SOWCOST16»
8 General Counsel Approved Version 9/27/17
ITEM NO. UNIT QTY DESCRIPTION UNIT
PRICE
«TASK17» «UOM17» «QTY17»
«SOW17» «SOWCOST17»
«TASK18» «UOM18» «QTY18»
«SOW18» «SOWCOST18»
«TASK19» «UOM19» «QTY19»
«SOW19» «SOWCOST19»
«TASK20» «UOM20» «QTY20»
«SOW20» «SOWCOST20»
«TASK21» «UOM21» «QTY21»
«SOW21» «SOWCOST21»
«TASK22» «UOM22» «QTY22»
«SOW22» «SOWCOST22»
«TASK23» «UOM23» «QTY23»
«SOW23» «SOWCOST23»
«TASK24» «UOM24» «QTY24»
«SOW24» «SOWCOST24»
«TASK25» «UOM25» «QTY25»
«SOW25» «SOWCOST25»
TOTAL* $«COST»
TABLE 2 Spending authority will not exceed $«COST» over a «PSATerm» year period. Year Spending Authority
City of Carlsbad / CMWD SCADA Master Plan
I-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix I: HMI Software RFP Addendum No. 1
HMI RFP19-480-UTIL
Addendum
1. Please provide a list of each site and the equipment at each site that needs to be monitored and
controlled. GPS coordinates for each site, or a map showing their locations, would be very
helpful.
To clarify, the purpose of this RFP is to compare all proposals based on a sample
system that is comparable to what is anticipated for the City/CMWD’s future
upgrades. To establish the best value evaluation, all bidders should prepare their
proposals based on the information provided in the RFP.
2. For RFP19-480UTIL on page 1 of 11 in the bottom paragraph states "...a long term services
agreement will be negotiated." Does 'services' refer to integration work or a support contract
(upgrades/technical support)? Thank you in advance.
Services refers to a support contract, not system integration. The City of
Carlsbad/CMWD uses the term “service agreement” not only for professional services
but also for all maintenance and support contracts.
3. We have a question on the 2 year warranty Carlsbad is requesting. It says in the RFP, the 2 year
warranty will start when the software is installed and in use. We don't really have a warranty
like that but we do have maintenance and 24/7 support. What I am looking to propose is a
software bundle that includes the first year of maintenance and 24/7 support. After that,
maintenance and 24/7 support will be only 20% of original license cost yearly for year 2-10. We
do not have escalation as long as the owner (Carlsbad) stays current on annual renewals. In fact,
you can save 5% on maintenance and 24/7 support if you pay years 2-10 in advance. So my
question is, what does Carlsbad expect for the warranty?
Proposers shall provide warranty as requested in the RFP. The methodology used to
achieve the requirements is left up to individual proposers.
4. Does the 24/7 support need to include development and application specific support? We have
a support tier that is non-development and application specific. We also have one that does but
it's more expensive. Please clarify.
The 24/7 support shall include development and application.
5. Will City/CMWD require only one server pair for all three systems (water,recycled water,sewer)?
Or one pair for each system? Will all 3 systems be on the same network?
The RFP requires one server pair for all three systems.
6. Section 3.1: Will the remote access clients always be connected to the city WAN (VPN)? (page
25)
The remote sites shall be connected to the central system at all times.
7. Section 3.2.1, #5: Are the 50-view only licenses remote mobile clients? If not, how many remote
clients are expected? (page 26)
The 50 view-only clients may be on any platform; mobile (tablet, phone) or laptop.
Assume 25 local thin clients and 25 remote clients.
8. Section 3.2.2, #1: Is it acceptable that Operator trainings be provided by the integration firms
that designs your HMI screens? (page 26)
All training shall be provided by the manufacturer or the manufacturer’s authorized
distributor responsible for the support services, as long as training is a standard part
of the distributor’s service and the trainers are manufacturer certified accordingly.
9. Section 3.2.2, #3: Is it acceptable that server system trainings be provided by the integration
firms that designs your HMI system? (page 26)
All training shall be provided by the manufacturer or the manufacturer’s authorized
distributor responsible for the support services, as long as training is a standard part
of the distributor’s service and the trainers are manufacturer certified accordingly.
10. Section 5.1.3: What kind of printer will be used the alarm printer? (page 30)
Delete the requirement for an alarm printer.
11. Section 5.1.5: Will DNP3 be used for real-time or buffered data, or both? (page 31)
DNP3 can be used for both real-time and buffered data to improve the overall
efficiency of the network. DNP3 will be used for both.
City of Carlsbad / CMWD SCADA Master Plan
J-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix J: PLC Hardware RFP Addendum No. 1
PLC RFP19-481-UTIL
Addendum No. 1
1. Please provide a list of each site and the equipment at each site that needs to be monitored and
controlled. GPS coordinates for each site, or a map showing their locations, would be very
helpful.
To clarify, the purpose of this RFP is to compare all proposals based on a sample
system that is comparable to what is anticipated for the City/CMWD’s future
upgrades. To establish the best value evaluation, all bidders should prepare their
proposals based on the information provided in the RFP.
2. Section 1, Page 4, states "This RFP does not include implementation services". Yet, there at
least two areas of the RFP where labor or services are referenced in some form.
a. Section 4, page 4-1 states, "The proposer shall take into consideration the labor,
material, rental and any associated cost to perform or provide any unit of work".
b. Attachment B, Section 10C refers to "set up charges".
Please clarify or confirm that this RFP is for hardware and software only, and does not include
any sort of installation, configuration, programming, integration, etc. (other than training, which
is clear).
The RFP does not include implementation services.
a. Section 4, page 4-1 is in reference to training. See Section 3.2.2 for details
on training. Any costs related to meeting the requirements of Section 3.2.2
should be included in the proposal for training cost.
b. Attachment B, Section 10C: revise as follows:
C. All prices shall be F.O.B. destination. Bids other than F.O.B.
destination shall be considered non-responsive and will be rejected.
Prices shall include all freight, and delivery and set-up charges.
3. Should the quantities in Table 4-1 reflect the number of systems described in Section 3.2.1, and
the quantities in Table 4-2 reflect the quantities described in Section 3.2.2?
That is correct.
4. Appendix B, Page 2, in the text: There are two references to "HMI Software". Please confirm
that this is a typo and the reference should be to "PLC".
Correct, this is a typo. In Appendix B, Page 2, both references to “HMI Software” shall
be changed to “PLC”.
5. Discrete Output Type: Section 3.2.1 calls out the DO type to be relay, but section 5.1.8 states
"relay, sink & source". Please clarify if the DO's should be relay or alternately any of relay, sink
or source. Or if there is some other interpretation.
Discrete Output (DO) modules shall have relay outputs.
6. Section 6.1.3: Can you please clarify what is meant by "from other manufacturer" in this
section? I assume the meaning is to provide references where the proposed PLC system was
integrated with or communicated with a PLC system from another manufacturer?
The intent of Section 6.1.3 is to find out how the proposed PLC system platform
interfaces/exchanges data with PLC platforms from other manufacturers used in
vendor packages.
7. Section 3.2.1: #7 is blank.
Section 3.2.1 #7 is blank and shall be deleted.
8. Financial Reports: our firm is a privately held company, and thus does not make financial
reports or statements available. Will this preclude our firm’s RFP from being accepted or in any
way affect the score?
All proposals will be reviewed. Any vendor who has a problem with providing financial
reports shall submit their concerns in a sealed envelope marked “Financial Report” as
required.
9. What is the Max Switch Over time that you are looking for regarding the Redundant PLC?
Max switchover time for the redundant PLC system shall not exceed 200mS.
10. Does the Redundant PLC have IO attached to it? If so what type and quantities?
Redundant PLC system configuration is manufacturer dependent and shall be done in
accordance with the manufacturers recommended best practice.
11. DNP protocol. Ethernet? What version?
Various protocols are available for DNP3 compliance. Provide the version
recommended by the PLC manufacturer for their equipment.
City of Carlsbad / CMWD SCADA Master Plan
K-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix K: HMI Software Demonstrations
1
City of Carlsbad/Carlsbad Municipal Water District
HMI Demonstration Team Review
Application Development, End-User Graphics, and Display
Item Demo Requirement Key points Notes
1 What template libraries are available that allow for
consistent and structured management of the user
interface as well as the underlying data and
programming configuration?
1) If a vendor has libraries built for water/wastewater,
that’s very useful for us. It also shows us the vendor is
focused on the industry.
2) Having the ability to modify the vendor templates is very
useful so you don’t have to create them from scratch.
3) Do the templates provide easy connectivity with the PLC
program?
2 Demonstrate the development of an object from an
existing template that can quickly and easily be
modified to fit any standards and requirements the
owner may have. Include the ability to trend live
data from the object.
1) Vendor should demonstrate how easy it is to take an
existing library template and modify it to comply with
your standard (when developed).
2) Demonstrate trending live data from the object.
3 Demonstrate HMI display through remote mobile
access. Show any configuration needed to optimize
the user interface for use on smaller sized mobile
devices. Demonstrate the ease of install and
access on a mobile device.
1) Show how you can take a display created for a normal
screen and use it on a mobile device like a tablet or cell
phone without having to recreate it.
2) Show how a screen is installed onto a mobile device.
3) Recreating displays just for mobile devices is not good
– increases configuration work.
4) Mobile HMI display should update with minimal lag time
for operator ease of use.
City of Carlsbad/Carlsbad Municipal Water District – HMI Demonstration Team Review
2
4 How can different data and underlying
programming be structured so that they remain as consistent and standardized as possible?
1) What tools are available to set up the tag database?
5 Demonstrate the process for developing a basic
custom control logic script.
1) How easy is it to develop a basic script? Do you need to
know programming?
2) Is there an intuitive interface to create custom “if this
then that” commands?
6 The owner employs a wide range of personnel skill
sets and competency levels of both system
operations as well as HMI usage. What methods are
available to develop an interface that provides
intuitive methods to allow for experienced operators
to effectively influence and guide inexperienced
operations staff toward operational methods and
goals?
1) Does the system have any built-in “high-performance
HMI” features built-in i.e., how intuitive are the screens
and do they make it easy to capture trail knowledge?
7 What methods and technologies are available to
support easy navigation, access, and presentation
of information for this wide variety of skill sets?
1) Is screen navigation intuitive? Going from an overview
screen to a detailed screen.
2) Is the use of pop-ups, drop-down menus intuitive?
8 What functions are available to relate and compare logs in relation to process values to complete
analyses and event-based troubleshooting?
1) Event-based troubleshooting using time series process data; use of historical trends. How easy is this?
2) What built-in tools does the software provide for
detecting and troubleshooting equipment issues?
3) Are statistical analysis tools available to automatically
detect abnormalities in process data?
9 Provide a demonstration of how a remote site
communications status display can be built,
including configurable polling rate, time from last
poll, time until next poll, configurable polling retries
and communications alarm, and a polling disable
selection. How will this be impacted by a redundant
master controller configuration?
1) Demonstrate a communications display with features to
change polling criteria from the HMI.
2) What features does the software provide to
monitor/alarm system communications?
City of Carlsbad/Carlsbad Municipal Water District – HMI Demonstration Team Review
3
10 Demonstrate alarm management and notification
features such as alarm summary, alarm history, and alarm notification (voice, text, email).
1) How well does software handle alarms overall?
City of Carlsbad/Carlsbad Municipal Water District – HMI Demonstration Team Review
4
Data Storage, Connectivity, and Utilization
Item Demo Requirement Key points Notes
1 How will the proposed software support different
server redundancy schemes for fail-over, load-sharing,
and virtualization?
1) This is very important, and they should discuss
server redundancy, failover and whether they
can use server virtualization.
2 What technology or methods are available to provide
the desired level of quality assurance and quality
control management of the data?
1) How do they ensure the data that’s stored is
good?
2) What safeguards do they have to ensure
quality?
3) Are there tools available to detect and fix data gaps or false data?
3 What technology and methods are available to control
and optimize historical data collection?
1) Do they have event-based data collection to
improve storage efficiency?
2) How effective is the compression of historical
data to use storage space more efficiently?
4 How can historical data be easily accessed securely by
users both within the control system and on the
enterprise network? How will data access be provided
across a network demilitarized zone?
1) How easy is it to use historical data?
2) What methods do they recommend for data
access across the DMZ?
5 The owner currently uses Infor Public Sector for its
centralized maintenance management system; how
can the HMI provide information and integration with
this platform for effective maintenance management?
1) This is to see if they can provide connectivity
for a CMMS system.
6 The owner currently uses Tableau as a business
intelligence platform; how can the proposed software
platform integrate with other databases and be
leveraged for dashboarding and analysis in Tableau?
1) If the software doesn’t use a SQL database,
how can they get it a SQL database?
7 The owner has a wide variety of software systems
outside of its HMI and overall control system tailored
to specific job roles, such as maintenance,
1) This is mainly to find out about the connectivity
of the software. How well does it work with
other software?
City of Carlsbad/Carlsbad Municipal Water District – HMI Demonstration Team Review
5
engineering, water quality, and management. How can
the HMI interface with these types of systems to provide more efficient connection between process
information and other job functions?
8 What native or add-on tools are available for real-time
data analysis?
1) This is to find out what type of data analysis
tools the software has to offer.
2) If they don’t have a software, how do they
typically accomplish this.
9 What native or add-on tools are available for predictive
or optimization-based process control?
1) This is an opportunity for them to demonstrate
any nice features that could help with process
control.
10 Demonstrate the configuration required to generate an
example report from the proposed software.
1) How easy is it to generate reports in the
software?
2) Does the software have the flexibility to output
a report per the owner’s desired format?
City of Carlsbad/Carlsbad Municipal Water District – HMI Demonstration Team Review
6
Security, Stability, and Support
Item Demo Requirement Key points Notes
1 The owner wants to have the flexibility to allow the
development and support of the system from a range
of internal and external sources. What methods or
technologies are available to allow the owner to
effectively manage, log, and control changes being
made by any source?
1) Do they have any tools for version control of
software?
2) Any way to track or log who made the edits to
the system configuration
2 What configuration is required for any third-party
cybersecurity software (including anti-virus, anti-malware, endpoint protection, and firewalls) that
needs to be run on the HMI network/workstations?
1) This is to find out if the software would have
issues with standard Windows anti-virus software.
2) Do they need additional software, so the anti-
virus software works?
3) Any security exceptions that need to be made
for the HMI software will create holes in the
security that can be exploited (e.g. opening
firewall ports, scan exceptions)
3 Demonstrate configuration and use of two-factor
authentication for the proposed software.
1) Two-factor authentication is becoming very
common for better security.
4 The process system is expected to be modified over
time as the owner makes adjustments, process
changes, or optimization changes. What methods or
technologies allow the owner to effectively develop,
test, and implement changes in a method that does
not impact the live system and process?
1) Can changes be developed and tested without
impacting the live system? This is very useful
when implementing changes.
5 Describe how legacy software is currently supported.
What are the plans to support this product in the
future? Describe the product lifecycle.
1) The product should be in the early stages of its
life-cycle (but not new so it’s fully tested).
2) What is the typical life-cycle and how do they
go about phasing-out products?
City of Carlsbad/Carlsbad Municipal Water District – HMI Demonstration Team Review
7
6 Demonstrate the ease of access to online
documentation to troubleshoot an example software issue.
1) Do they have a good website for trouble-
shooting the software?
2) Do they have good online documentation?
7 Demonstrate the ease of access to and use of online
training.
1) Do they have online training videos?
2) Online training courses or other material?
8 What methods and alternatives are available in the
region and nationally to provide product support from
a wide variety of sources?
1) Should provide local product support contacts
like authorized distributors.
2) Manufacturer direct support if available.
9 Describe the pathway for resolving an issue with the
software. How will an issue be escalated through
different levels of support? What is the timeline for
escalation?
1) Vendor should explain the process of
responding to technical support request from
clients and how they get escalated.
2) Will an issue be resolved in a timely manner?
10 Describe any qualification or certification process that
is provided for local integrators for this product. How
can the owner ensure quality and expertise from local
system integrators for the installation and continued
support of the product? Demonstrate the rigor of the
qualification or certification process.
1) We would like to know if the manufacturer
provides System Integrator training and
certifies them or recognizes them as qualified
to work on their products.
2) Is there a rigorous process in place to verify
proper qualification? There should be some
form of test that requires thorough knowledge of the software to pass.
City of Carlsbad / CMWD SCADA Master Plan
L-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix L: HMI Software Reference-Check Script
1
City of Carlsbad/Carlsbad Municipal Water District
HMI Proposal Reference Check
In preparation for a replacement of its Human Machine Interface (HMI), City of Carlsbad and
Carlsbad Municipal Water District (collectively, “the owner”) is developing an understanding of the
technology and features available in the industry and market for HMI software platforms. To help
determine which software will provide the best set of tools to meet its needs, the owner has defined
unique user requirements and characteristics that are important to the owner for its HMI in the
future. The following series of questions is designed to evaluate key criteria for the HMI software
when contacting the references provided by the proposers.
General
1. When did your organization first start utilizing this platform?
2. What specific platform did you start with and are on now?
3. What were the key factors in deciding to install your organization’s current HMI software?
4. What key factors have kept your organization using the HMI software?
5. What features or capabilities, if any, do you feel your organization’s HMI software is missing
the most?
Application Development, End-User Graphics, and Display
6. Has your organization benefitted from the templates offered by the HMI software
manufacturer?
a. Are templates easy to use and adapt to the water/wastewater industry?
b. Has your organization had success in enforcing graphics standards through the use
of templates provided for the HMI software?
7. How satisfied is your organization with the ease of use and configuration for access to the
HMI on mobile devices?
a. Are all HMI screens cleanly reproduced and optimized for mobile devices with
minimal programming and configuration effort?
b. Are there any issues with process data update speeds or lag-time on mobile devices?
Data Storage, Connectivity, and Utilization
8. Have you had any issues with the HMI software during failover to a redundant server,
unplanned power loss, or reconfiguration of the data storage?
9. Does your organization use the HMI software to interface with any external or business-side
software systems (e.g. maintenance, engineering, water quality, water management, and
business intelligence)?
City of Carlsbad/Carlsbad Municipal Water District – HMI Proposal Reference Check
2
a. If so, how well does the HMI interface with these types of systems to provide more
efficient connection between process information and other job functions?
b. How much effort was required to configure the HMI software to interface with other
software systems?
c. Are there any native or add-on tools for the HMI software that you would recommend
that have improved your capability to analyze process data or optimize the process to
gain efficiencies and reduce costs?
10. How does your organization use the HMI software for outputting reports?
a. How much additional effort and configuration is needed to customize the report
output in your required format?
Security, Stability, and Support
11. Was any configuration required to allow your organizations required cybersecurity software
(including anti-virus, anti-malware, endpoint protection, and firewalls) to run on the HMI network/workstations?
12. How accessible is online documentation to help with early-stage troubleshooting of issues
with the software or during upgrades?
a. Is the documentation provided sufficient in most cases?
13. Has your organization taken advantage of any of the software manufacturer’s training
classes (either in-person or online)?
a. If so, how satisfied were members of your organization with the training provided?
14. For any issues requiring contacting the support help line for the HMI software, how would you
rate your satisfaction with the experience?
15. What would you estimate as the response time to help resolve an issue with the HMI
software?
a. How much time was spent waiting on hold to speak with technical support staff?
16. How are you supporting the software development and changes?
a. If ever using third party integrators, describe the quality and availability of system
integrators capable of programming and configuring the HMI software.
b. Are system integrators able to resolve most issues with the software themselves?
c. Are they able to efficiently configure the software and offer an in-depth knowledge of software features?
City of Carlsbad / CMWD SCADA Master Plan
M-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix M: Implementation Schedule
City of Carlsbad / CMWD SCADA Master Plan
M-2
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan Appendix M
M-3
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan Appendix M
M-4
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan
N-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix N: Opinion of Probably Construction Costs
City of Carlsbad / CMWD SCADA Master Plan Appendix N
N-2
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan
O-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix O: Workload Projections
City of Carlsbad / CMWD SCADA Master Plan Appendix O
O-2
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan Appendix O
O-3
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan Appendix O
O-4
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan Appendix O
O-5
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan Appendix O
O-6
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan Appendix O
O-7
SC07221_FINAL_Carlsbad SCADA Master Plan
City of Carlsbad / CMWD SCADA Master Plan
P-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix P: Radio Communications Site Map
City of Carlsbad – Appendix
Site Map with Radio Frequency Paths
June 2019
This appendix contains supporting documentation of maps and tables from the desktop radio path
study. This study is to determine the best connectivity for all sites in the future. The desktop study is
to be followed up by a physical radio path study at the time of implementing the future
communication system. The physical study accounts for changes in the physical space, and external
radio frequency interference.
CMWD Site Map: contains water, reclaim water, wastewater, and operational sites included in the
desktop radio path study. There is no advantage in physically separating communication systems for
water, reclaimed water or wastewater.
Backbone: contains the recommended path for creating a high speed, high bandwidth ring with built-
in fault tolerance (redundancy) between all recommended master sites.
Sites listed below are recommended master sites
City/CMWD Utilities: Main building with SCADA servers (only connected via the Backbone)
D Site: contains all remote sites recommended to connect to the backbone via D Site
Elm Reservoir: contains all remote sites recommended to connect to the backbone via Elm Reservoir
La Costa Hi Reservoir: contains all remote sites recommended to connect to the backbone via La
Costa Hi Reservoir
Maerkle Tower: contains all remote sites recommended to connect to the backbone via Maerkle
Tower
SantaFe 2: contains all remote sites recommended to connect to the backbone via SantaFe 2
TAP Reservoir: contains all remote sites recommended to connect to the backbone via TAP Reservoir
Site Data Summary: contains site to site connection data sets for all recommended master sites and
for all remote sites to recommended master sites.
May Company
PRSElm Reservoir
Elm TAP PRS
Tanglewood
PRS
Ellery
Reservoir
TAP Reservoir
Lake Calavera
Calavera
Potable
Calavera
Recycle
C Reservoir
Skyline
Reservoir
Laguna/Kelly
PRS
Robertson
Ranch PRS
Rancho
Carlsbad PRS
TAP 4 CWA #4
CWA #3
Faraday
Reclaim PRS
Encina Reclaim
PRV
Twin D Reclaim
Pump StationEncina Pump
Station
Bressi Recycle
Pump Station
Bresi Potable
Pump Station
La Costa
Reclaim PRS
Palomar
West PRV
D Site
Lower El
Fuerte PRS
Upper El
Fuerte PRS
Melrose &
Corintia Meter
Maerkle Tower
Ayers PRV
Zodiac PRV
La Costa Lo
Reservoir
La Costa Hi
Reservoir
Maerkle Upper
Chlorine
Station
Maerkle Lower
Chlorine
Station
Maerkle Hydro
Electric
Mahr
Reservoir
Melrose PRV
Maerkle
Control
Santa Fe 2
Reservoir
CWA #6
CWA #2
Santa Fe 1
Reservoir
CMWD
Building
Point D PRV
North
Home Plant LS
Pine Beach
Bathroom
Tamarack/
Frazee Beach
Bathroom
Chinquapin LS
Foxes Landing LS
Terramar LS
Cannon LS
Sand Shell LS
Knots Lane LS Batiquitos LS
Poinsettia LS
Villas LS
El Fuerte LS
5
5
5
La Costa Ave
CMWD Site Map
Legend
Wastewater Site
Reclaim Site
Master Site
Water Site
Site Name Type Site Name Type
CMWD Building Admin
D Site Potable CWA #2 Potable
Elm Reservoir Potable Mahr Reservoir Reclaim
La Costa Hi Reservoir Potable Melrose & Corintia Meter Reclaim
Maerkle Tower Radio Tower
Santa Fe 2 Potable Bressi Potable Pump Station Potable
TAP Reservoir Potable Bressi Reclaim Pump Station Reclaim
C Reservoir Reclaim
Ayers PRV Potable Calavera Recycle Pump Station Reclaim
Batiquitos LS Wastewater Cannon LS Wastewater
Encina Pump Station Reclaim CWA #3 Potable
Encina Reclaim PRV Reclaim El Fuerte LS Wastewater
Foxes Landing LS Wastewater Faraday Reclaim PRS Reclaim
Knots Lane LS Wastewater Maerkle Control Potable
La Costa Lo Reservoir Potable Maerkle Hydro Electric Potable
Lower El Fuerte PRV Reclaim Maerkle Lower Chlorine Station Potable
Palomar West PRV Potable Maerkle Upper Chlorine Station Potable
Sand Shell LS Wastewater Point D PRV North Potable
Twin D Reclaim Pump Station Reclaim Rancho Carlsbad PRS Potable
Upper El Fuerte PRS Potable Robertson Ranch PRS Potable
Zodiac PRV Potable
CWA #6 Potable
Chinquapin LS Wastewater Santa Fe 1 Reservoir Potable
Ellery Reservoir Potable Melrose PRV Potable
Home Plant LS Wastewater La Costa Reclaim PRS Reclaim
May Copmany PRS Potable Poinsettia LS Wastewater
Pine Beach Bathroom Wastewater
Skyline Reservoir Potable Calavera Potable Pump Station Potable
Tamarack/Frazee Beach Bathroom Wastewater CWA #4 Potable
Tanglewood PRS Potable Elm TAP PRS Potable
Terramar LS Wastewater Laguna/Kelly PRS Potable
Lake Calavera
TAP 4 Potable
Villas LS Wastewater
Desktop Radio Study
La Costa Hi
Maerkle Tower
Santa Fe 2
TAP Reservoir
Master Sites
D Site
Elm Reservoir
Elm Reservoir
TAP Reservoir
D Site
Maerkle Tower
La Costa Hi
Reservoir
Santa Fe 2
Reservoir
CMWD
Building
5
5
5
La Costa Ave
Backbone
Legend
Wastewater Site
Reclaim Site
Master Site
Water Site
Site Name Type Site Name Type
CMWD Building Admin
D Site Potable CWA #2 Potable
Elm Reservoir Potable Mahr Reservoir Reclaim
La Costa Hi Reservoir Potable Melrose & Corintia Meter Reclaim
Maerkle Tower Radio Tower
Santa Fe 2 Potable Bressi Potable Pump Station Potable
TAP Reservoir Potable Bressi Reclaim Pump Station Reclaim
C Reservoir Reclaim
Ayers PRV Potable Calavera Recycle Pump Station Reclaim
Batiquitos LS Wastewater Cannon LS Wastewater
Encina Pump Station Reclaim CWA #3 Potable
Encina Reclaim PRV Reclaim El Fuerte LS Wastewater
Foxes Landing LS Wastewater Faraday Reclaim PRS Reclaim
Knots Lane LS Wastewater Maerkle Control Potable
La Costa Lo Reservoir Potable Maerkle Hydro Electric Potable
Lower El Fuerte PRV Reclaim Maerkle Lower Chlorine Station Potable
Palomar West PRV Potable Maerkle Upper Chlorine Station Potable
Sand Shell LS Wastewater Point D PRV North Potable
Twin D Reclaim Pump Station Reclaim Rancho Carlsbad PRS Potable
Upper El Fuerte PRS Potable Robertson Ranch PRS Potable
Zodiac PRV Potable
CWA #6 Potable
Chinquapin LS Wastewater Santa Fe 1 Reservoir Potable
Ellery Reservoir Potable Melrose PRV Potable
Home Plant LS Wastewater La Costa Reclaim PRS Reclaim
May Copmany PRS Potable Poinsettia LS Wastewater
Pine Beach Bathroom Wastewater
Skyline Reservoir Potable Calavera Potable Pump Station Potable
Tamarack/Frazee Beach Bathroom Wastewater CWA #4 Potable
Tanglewood PRS Potable Elm TAP PRS Potable
Terramar LS Wastewater Laguna/Kelly PRS Potable
Lake Calavera
TAP 4 Potable
Villas LS Wastewater
Desktop Radio Study
La Costa Hi
Maerkle Tower
Santa Fe 2
TAP Reservoir
Master Sites
D Site
Elm Reservoir
Elm Reservoir
TAP Reservoir
Encina Reclaim
PRV
Twin D Reclaim
Pump StationEncina Pump
Station
Palomar
West PRV
D Site
Lower El
Fuerte PRS
Upper El
Fuerte PRS
Maerkle Tower
Ayers PRV
Zodiac PRV
La Costa Lo
Reservoir
La Costa Hi
Reservoir
Santa Fe 2
Reservoir
CMWD
Building
Foxes Landing LS
Sand Shell LS
Knots Lane LS Batiquitos LS
5
5
5
La Costa Ave
D Site
Legend
Wastewater Site
Reclaim Site
Master Site
Water Site
Site Name Type Site Name Type
CMWD Building Admin
D Site Potable CWA #2 Potable
Elm Reservoir Potable Mahr Reservoir Reclaim
La Costa Hi Reservoir Potable Melrose & Corintia Meter Reclaim
Maerkle Tower Radio Tower
Santa Fe 2 Potable Bressi Potable Pump Station Potable
TAP Reservoir Potable Bressi Reclaim Pump Station Reclaim
C Reservoir Reclaim
Ayers PRV Potable Calavera Recycle Pump Station Reclaim
Batiquitos LS Wastewater Cannon LS Wastewater
Encina Pump Station Reclaim CWA #3 Potable
Encina Reclaim PRV Reclaim El Fuerte LS Wastewater
Foxes Landing LS Wastewater Faraday Reclaim PRS Reclaim
Knots Lane LS Wastewater Maerkle Control Potable
La Costa Lo Reservoir Potable Maerkle Hydro Electric Potable
Lower El Fuerte PRV Reclaim Maerkle Lower Chlorine Station Potable
Palomar West PRV Potable Maerkle Upper Chlorine Station Potable
Sand Shell LS Wastewater Point D PRV North Potable
Twin D Reclaim Pump Station Reclaim Rancho Carlsbad PRS Potable
Upper El Fuerte PRS Potable Robertson Ranch PRS Potable
Zodiac PRV Potable
CWA #6 Potable
Chinquapin LS Wastewater Santa Fe 1 Reservoir Potable
Ellery Reservoir Potable Melrose PRV Potable
Home Plant LS Wastewater La Costa Reclaim PRS Reclaim
May Copmany PRS Potable Poinsettia LS Wastewater
Pine Beach Bathroom Wastewater
Skyline Reservoir Potable Calavera Potable Pump Station Potable
Tamarack/Frazee Beach Bathroom Wastewater CWA #4 Potable
Tanglewood PRS Potable Elm TAP PRS Potable
Terramar LS Wastewater Laguna/Kelly PRS Potable
Lake Calavera
TAP 4 Potable
Villas LS Wastewater
Desktop Radio Study
La Costa Hi
Maerkle Tower
Santa Fe 2
TAP Reservoir
Master Sites
D Site
Elm Reservoir
May Company
PRSElm Reservoir
Tanglewood
PRS
Ellery
Reservoir
TAP Reservoir
Skyline
Reservoir
D Site
Maerkle Tower
La Costa Hi
Reservoir
Santa Fe 2
Reservoir
CMWD
Building
Home Plant LS
Pine Beach
Bathroom
Tamarack/
Frazee Beach
Bathroom
Chinquapin LS
Terramar LS
5
5
5
La Costa Ave
Elm Reservoir
Legend
Wastewater Site
Reclaim Site
Master Site
Water Site
Site Name Type Site Name Type
CMWD Building Admin
D Site Potable CWA #2 Potable
Elm Reservoir Potable Mahr Reservoir Reclaim
La Costa Hi Reservoir Potable Melrose & Corintia Meter Reclaim
Maerkle Tower Radio Tower
Santa Fe 2 Potable Bressi Potable Pump Station Potable
TAP Reservoir Potable Bressi Reclaim Pump Station Reclaim
C Reservoir Reclaim
Ayers PRV Potable Calavera Recycle Pump Station Reclaim
Batiquitos LS Wastewater Cannon LS Wastewater
Encina Pump Station Reclaim CWA #3 Potable
Encina Reclaim PRV Reclaim El Fuerte LS Wastewater
Foxes Landing LS Wastewater Faraday Reclaim PRS Reclaim
Knots Lane LS Wastewater Maerkle Control Potable
La Costa Lo Reservoir Potable Maerkle Hydro Electric Potable
Lower El Fuerte PRV Reclaim Maerkle Lower Chlorine Station Potable
Palomar West PRV Potable Maerkle Upper Chlorine Station Potable
Sand Shell LS Wastewater Point D PRV North Potable
Twin D Reclaim Pump Station Reclaim Rancho Carlsbad PRS Potable
Upper El Fuerte PRS Potable Robertson Ranch PRS Potable
Zodiac PRV Potable
CWA #6 Potable
Chinquapin LS Wastewater Santa Fe 1 Reservoir Potable
Ellery Reservoir Potable Melrose PRV Potable
Home Plant LS Wastewater La Costa Reclaim PRS Reclaim
May Copmany PRS Potable Poinsettia LS Wastewater
Pine Beach Bathroom Wastewater
Skyline Reservoir Potable Calavera Potable Pump Station Potable
Tamarack/Frazee Beach Bathroom Wastewater CWA #4 Potable
Tanglewood PRS Potable Elm TAP PRS Potable
Terramar LS Wastewater Laguna/Kelly PRS Potable
Lake Calavera
TAP 4 Potable
Villas LS Wastewater
Desktop Radio Study
La Costa Hi
Maerkle Tower
Santa Fe 2
TAP Reservoir
Master Sites
D Site
Elm Reservoir
Elm Reservoir
TAP Reservoir
D Site
Melrose &
Corintia Meter
Maerkle Tower
La Costa Hi
Reservoir
Mahr
Reservoir
Santa Fe 2
Reservoir
CWA #2
CMWD
Building
5
5
5
La Costa Ave
La Costa Hi Reservoir
Legend
Wastewater Site
Reclaim Site
Master Site
Water Site
Site Name Type Site Name Type
CMWD Building Admin
D Site Potable CWA #2 Potable
Elm Reservoir Potable Mahr Reservoir Reclaim
La Costa Hi Reservoir Potable Melrose & Corintia Meter Reclaim
Maerkle Tower Radio Tower
Santa Fe 2 Potable Bressi Potable Pump Station Potable
TAP Reservoir Potable Bressi Reclaim Pump Station Reclaim
C Reservoir Reclaim
Ayers PRV Potable Calavera Recycle Pump Station Reclaim
Batiquitos LS Wastewater Cannon LS Wastewater
Encina Pump Station Reclaim CWA #3 Potable
Encina Reclaim PRV Reclaim El Fuerte LS Wastewater
Foxes Landing LS Wastewater Faraday Reclaim PRS Reclaim
Knots Lane LS Wastewater Maerkle Control Potable
La Costa Lo Reservoir Potable Maerkle Hydro Electric Potable
Lower El Fuerte PRV Reclaim Maerkle Lower Chlorine Station Potable
Palomar West PRV Potable Maerkle Upper Chlorine Station Potable
Sand Shell LS Wastewater Point D PRV North Potable
Twin D Reclaim Pump Station Reclaim Rancho Carlsbad PRS Potable
Upper El Fuerte PRS Potable Robertson Ranch PRS Potable
Zodiac PRV Potable
CWA #6 Potable
Chinquapin LS Wastewater Santa Fe 1 Reservoir Potable
Ellery Reservoir Potable Melrose PRV Potable
Home Plant LS Wastewater La Costa Reclaim PRS Reclaim
May Copmany PRS Potable Poinsettia LS Wastewater
Pine Beach Bathroom Wastewater
Skyline Reservoir Potable Calavera Potable Pump Station Potable
Tamarack/Frazee Beach Bathroom Wastewater CWA #4 Potable
Tanglewood PRS Potable Elm TAP PRS Potable
Terramar LS Wastewater Laguna/Kelly PRS Potable
Lake Calavera
TAP 4 Potable
Villas LS Wastewater
Desktop Radio Study
La Costa Hi
Maerkle Tower
Santa Fe 2
TAP Reservoir
Master Sites
D Site
Elm Reservoir
Elm Reservoir
TAP Reservoir
Calavera
Recycle
C Reservoir
Robertson
Ranch PRS
Rancho
Carlsbad PRS
CWA #3
Faraday
Reclaim PRS
Bressi Reclaim
Pump Station
Bresi Potable
Pump Station
Maerkle Tower
La Costa Hi
Reservoir
Maerkle Upper
Chlorine
Station
Maerkle Lower
Chlorine
Station
Maerkle Hydro
Electric
Maerkle
Control
Santa Fe 2
Reservoir
CMWD
Building
Point D PRV
North
Cannon LS
El Fuerte LS
5
5
5
La Costa Ave
Maerkle Tower
Legend
Wastewater Site
Reclaim Site
Master Site
Water Site
Site Name Type Site Name Type
CMWD Building Admin
D Site Potable CWA #2 Potable
Elm Reservoir Potable Mahr Reservoir Reclaim
La Costa Hi Reservoir Potable Melrose & Corintia Meter Reclaim
Maerkle Tower Radio Tower
Santa Fe 2 Potable Bressi Potable Pump Station Potable
TAP Reservoir Potable Bressi Reclaim Pump Station Reclaim
C Reservoir Reclaim
Ayers PRV Potable Calavera Recycle Pump Station Reclaim
Batiquitos LS Wastewater Cannon LS Wastewater
Encina Pump Station Reclaim CWA #3 Potable
Encina Reclaim PRV Reclaim El Fuerte LS Wastewater
Foxes Landing LS Wastewater Faraday Reclaim PRS Reclaim
Knots Lane LS Wastewater Maerkle Control Potable
La Costa Lo Reservoir Potable Maerkle Hydro Electric Potable
Lower El Fuerte PRV Reclaim Maerkle Lower Chlorine Station Potable
Palomar West PRV Potable Maerkle Upper Chlorine Station Potable
Sand Shell LS Wastewater Point D PRV North Potable
Twin D Reclaim Pump Station Reclaim Rancho Carlsbad PRS Potable
Upper El Fuerte PRS Potable Robertson Ranch PRS Potable
Zodiac PRV Potable
CWA #6 Potable
Chinquapin LS Wastewater Santa Fe 1 Reservoir Potable
Ellery Reservoir Potable Melrose PRV Potable
Home Plant LS Wastewater La Costa Reclaim PRS Reclaim
May Copmany PRS Potable Poinsettia LS Wastewater
Pine Beach Bathroom Wastewater
Skyline Reservoir Potable Calavera Potable Pump Station Potable
Tamarack/Frazee Beach Bathroom Wastewater CWA #4 Potable
Tanglewood PRS Potable Elm TAP PRS Potable
Terramar LS Wastewater Laguna/Kelly PRS Potable
Lake Calavera
TAP 4 Potable
Villas LS Wastewater
Desktop Radio Study
La Costa Hi
Maerkle Tower
Santa Fe 2
TAP Reservoir
Master Sites
D Site
Elm Reservoir
Elm Reservoir
TAP Reservoir
La Costa
Reclaim PRS
La Costa Hi
Reservoir
Melrose PRV Santa Fe 2
Reservoir
CWA #6
Santa Fe 1
Reservoir
CMWD
Building
Poinsettia LS
5
5
5
La Costa Ave
SantaFe 2
Legend
Wastewater Site
Reclaim Site
Master Site
Water Site
Site Name Type Site Name Type
CMWD Building Admin
D Site Potable CWA #2 Potable
Elm Reservoir Potable Mahr Reservoir Reclaim
La Costa Hi Reservoir Potable Melrose & Corintia Meter Reclaim
Maerkle Tower Radio Tower
Santa Fe 2 Potable Bressi Potable Pump Station Potable
TAP Reservoir Potable Bressi Reclaim Pump Station Reclaim
C Reservoir Reclaim
Ayers PRV Potable Calavera Recycle Pump Station Reclaim
Batiquitos LS Wastewater Cannon LS Wastewater
Encina Pump Station Reclaim CWA #3 Potable
Encina Reclaim PRV Reclaim El Fuerte LS Wastewater
Foxes Landing LS Wastewater Faraday Reclaim PRS Reclaim
Knots Lane LS Wastewater Maerkle Control Potable
La Costa Lo Reservoir Potable Maerkle Hydro Electric Potable
Lower El Fuerte PRV Reclaim Maerkle Lower Chlorine Station Potable
Palomar West PRV Potable Maerkle Upper Chlorine Station Potable
Sand Shell LS Wastewater Point D PRV North Potable
Twin D Reclaim Pump Station Reclaim Rancho Carlsbad PRS Potable
Upper El Fuerte PRS Potable Robertson Ranch PRS Potable
Zodiac PRV Potable
CWA #6 Potable
Chinquapin LS Wastewater Santa Fe 1 Reservoir Potable
Ellery Reservoir Potable Melrose PRV Potable
Home Plant LS Wastewater La Costa Reclaim PRS Reclaim
May Copmany PRS Potable Poinsettia LS Wastewater
Pine Beach Bathroom Wastewater
Skyline Reservoir Potable Calavera Potable Pump Station Potable
Tamarack/Frazee Beach Bathroom Wastewater CWA #4 Potable
Tanglewood PRS Potable Elm TAP PRS Potable
Terramar LS Wastewater Laguna/Kelly PRS Potable
Lake Calavera
TAP 4 Potable
Villas LS Wastewater
Desktop Radio Study
La Costa Hi
Maerkle Tower
Santa Fe 2
TAP Reservoir
Master Sites
D Site
Elm Reservoir
Elm Reservoir
Elm TAP PRS TAP Reservoir
Lake Calavera
Calavera
Potable
Laguna/Kelly
PRS
TAP 4 CWA #4
La Costa Hi
Reservoir
CMWD
Building
Villas LS
5
5
5
La Costa Ave
TAP Reservoir
Legend
Wastewater Site
Reclaim Site
Master Site
Water Site
Site Name Type Site Name Type
CMWD Building Admin
D Site Potable CWA #2 Potable
Elm Reservoir Potable Mahr Reservoir Reclaim
La Costa Hi Reservoir Potable Melrose & Corintia Meter Reclaim
Maerkle Tower Radio Tower
Santa Fe 2 Potable Bressi Potable Pump Station Potable
TAP Reservoir Potable Bressi Reclaim Pump Station Reclaim
C Reservoir Reclaim
Ayers PRV Potable Calavera Recycle Pump Station Reclaim
Batiquitos LS Wastewater Cannon LS Wastewater
Encina Pump Station Reclaim CWA #3 Potable
Encina Reclaim PRV Reclaim El Fuerte LS Wastewater
Foxes Landing LS Wastewater Faraday Reclaim PRS Reclaim
Knots Lane LS Wastewater Maerkle Control Potable
La Costa Lo Reservoir Potable Maerkle Hydro Electric Potable
Lower El Fuerte PRV Reclaim Maerkle Lower Chlorine Station Potable
Palomar West PRV Potable Maerkle Upper Chlorine Station Potable
Sand Shell LS Wastewater Point D PRV North Potable
Twin D Reclaim Pump Station Reclaim Rancho Carlsbad PRS Potable
Upper El Fuerte PRS Potable Robertson Ranch PRS Potable
Zodiac PRV Potable
CWA #6 Potable
Chinquapin LS Wastewater Santa Fe 1 Reservoir Potable
Ellery Reservoir Potable Melrose PRV Potable
Home Plant LS Wastewater La Costa Reclaim PRS Reclaim
May Copmany PRS Potable Poinsettia LS Wastewater
Pine Beach Bathroom Wastewater
Skyline Reservoir Potable Calavera Potable Pump Station Potable
Tamarack/Frazee Beach Bathroom Wastewater CWA #4 Potable
Tanglewood PRS Potable Elm TAP PRS Potable
Terramar LS Wastewater Laguna/Kelly PRS Potable
Lake Calavera
TAP 4 Potable
Villas LS Wastewater
Desktop Radio Study
La Costa Hi
Maerkle Tower
Santa Fe 2
TAP Reservoir
Master Sites
D Site
Elm Reservoir
Site Data Summary
Backbone
D Site
Subscriber Module (SM) Name Band Bandwidth
SM
Latitude
SM
Longitude
SM Height
(ft)Range (mi.)
SM Antenna
Magnetic
Azimuth (deg)
Aggregate Throughput
(Mbps)Predicted Receive Power
Link Predicted
Availability (%)Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type
Santa Fe 2 Reservoir 23 GHz 10 MHz 33.12355N 117.22532W 16 2.5631562 272.4 143.397 -43 dBm ± 4 dB 100 CMW Building 33.13249N 117.26823W 46 Line-of-Sight
Elm Reservoir 23 GHz 10 MHz 33.17268N 117.33015W 50 4.859123 137.4 143.384 -49 dBm ± 4 dB 99.9995 D Site 33.11226N 117.28695W 78 Line-of-Sight
La Costa Hi Reservoir 23 GHz 10 MHz 33.10571N 117.23489W 10 3.0527967 267 143.396 -45 dBm ± 4 dB 99.9999 D Site 33.11226N 117.28695W 78 Line-of-Sight
CMWD Building 23 GHz 10 MHz 33.13249N 117.26823W 46 1.4639505 6.9 143.398 -38 dBm ± 4 dB 100 Maerkle Reservoir 33.15265N 117.26028W 30 Line-of-Sight
TAP Reservoir 23 GHz 10 MHz 33.17188N 117.29583W 43 2.4519307 111.4 143.397 -43 dBm ± 4 dB 100 Maerkle Reservoir 33.15257N 117.26030W 20 Line-of-Sight
La Costa Hi 23 GHz 10 MHz 33.10574N 117.23486W 10 1.3465114 12.8 142.811 -52 dBm ± 8 dB 99.9995 Santa Fe 2 Reservoir 33.12355N 117.22532W 16 Non Line-of-Sight
Elm Reservoir 23 GHz 10 MHz 33.17267N 117.33011W 53 1.9290092 80 143.398 -41 dBm ± 4 dB 100 TAP Reservoir 33.17190N 117.29580W 42 Line-of-Sight
Subscriber Module (SM) Name Band Bandwidth
SM
Latitude
SM
Longitude
SM Height
(ft)Range (mi.)
SM Antenna
Magnetic
Azimuth (deg)
Aggregate Throughput
(Mbps)Predicted Receive Power
Link Predicted
Availability (%)Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type
Ayers PRV Reclaim 900 MHz 10 MHz 33.10531N 117.26740W 25 1.241 281.2 55.704 -63 dBm ± 8 dB 100 D Site 33.11226N 117.28714W 75 Non Line-of-Sight
Encina Reclaim PRV 900 MHz 10 MHz 33.11019N 117.31804W 10 1.81 73.9 34.058 -74 dBm ± 11 dB 100 D Site 33.11230N 117.28694W 78 Non Line-of-Sight
Encina Reclaim Pump Station 900 MHz 10 MHz 33.11429N 117.31887W 40 1.857 82.7 56.047 -63 dBm ± 7 dB 100 D Site 33.11230N 117.28694W 78 Near Line-of-Sight
Fox's LS 900 MHz 10 MHz 33.14793N 117.33348W 33 3.658 120.5 30.049 -76 dBm ± 9 dB 100 D Site 33.11240N 117.28662W 55 Non Line-of-Sight
Knots LS 900 MHz 10 MHz 33.09102N 117.31051W 33 2.023 31.7 57.102 -62 dBm ± 7 dB 100 D Site 33.11240N 117.28662W 55 Near Line-of-Sight
La Costa Lo Reservoir 900 MHz 10 MHz 33.10164N 117.25162W 45 2.176 278.2 57.344 -57 dBm ± 5 dB 100 D Site 33.11226N 117.28695W 78 Line-of-Sight
Lower El Fuerte PRS 900 MHz 10 MHz 33.09508N 117.25015W 10 2.441 287.5 57.344 -58 dBm ± 5 dB 100 D Site 33.11226N 117.28695W 78 Line-of-Sight
Palomar West PRV 900 MHz 10 MHz 33.12177N 117.31332W 25 1.663 101.6 35.378 -74 dBm ± 11 dB 100 D Site 33.11230N 117.28694W 78 Non Line-of-Sight
Sand Shell LS 900 MHz 10 MHz 33.10278N 117.31579W 33 1.817 57.1 46.024 -67 dBm ± 9 dB 100 D Site 33.11240N 117.28662W 55 Non Line-of-Sight
Twin D Reclaim Pump Station 900 MHz 10 MHz 33.11256N 117.28728W 17 0.027 120.8 57.344 -35 dBm ± 5 dB 100 D Site 33.11230N 117.28694W 78 Line-of-Sight
Upper El Fuerte PRS 900 MHz 10 MHz 33.09750N 117.24517W 10 2.638 281.2 55.413 -62 dBm ± 6 dB 100 D Site 33.11226N 117.28714W 75 Near Line-of-Sight
Zodiac PRV 900 MHz 10 MHz 33.10576N 117.25291W 10 2.022 271.3 57.344 -56 dBm ± 5 dB 100 D Site 33.11226N 117.28691W 79 Line-of-Sight
N. Batiquitos LS 900 MHz 10 MHz 33.09312N 117.30013W 33 0.619 245 32.96 -73 dBm ± 13 dB 99.9995 Knots LS 33.09102N 117.31051W 33 Non Line-of-Sight
Site Data Summary
Elm Reservoir
La Costa Hi
Subscriber Module (SM) Name Band Bandwidth
SM
Latitude
SM
Longitude
SM Height
(ft)Range (mi.)
SM Antenna
Magnetic
Azimuth (deg)
Aggregate Throughput
(Mbps)Predicted Receive Power
Link Predicted
Availability (%)Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type
Chinquapin LS 900 MHz 10 MHz 33.14599N 117.34381W 33 2.003 11.8 37.237 -73 dBm ± 10 dB 100 Elm Reservoir 33.17267N 117.33011W 53 Non Line-of-Sight
Ellery Reservoir 900 MHz 10 MHz 33.16546N 117.32283W 35 0.654 308 57.344 -47 dBm ± 5 dB 100 Elm Reservoir 33.17268N 117.33015W 50 Near Line-of-Sight
Home Plant LS 900 MHz 10 MHz 33.16535N 117.35483W 33 1.519 59.1 57.344 -53 dBm ± 5 dB 100 Elm Reservoir 33.17267N 117.33011W 53 Line-of-Sight
Pine Beach Bathroom LS 900 MHz 10 MHz 33.15445N 117.35089W 33 1.739 32.2 57.294 -60 dBm ± 7 dB 100 Elm Reservoir 33.17268N 117.33015W 50 Near Line-of-Sight
Skyline Reservoir 900 MHz 10 MHz 33.15071N 117.31952W 35 1.635 326.4 57.338 -58 dBm ± 6 dB 100 Elm Reservoir 33.17268N 117.33015W 50 Near Line-of-Sight
Tamarack/Frazee Beach Bathroom LS 900 MHz 10 MHz 33.14749N 117.34567W 33 1.956 15.9 57.338 -59 dBm ± 6 dB 100 Elm Reservoir 33.17267N 117.33011W 53 Near Line-of-Sight
Tanglewood PRS 900 MHz 10 MHz 33.17173N 117.32227W 25 0.459 266.6 46.304 -66 dBm ± 12 dB 100 Elm Reservoir 33.17267N 117.33011W 53 Non Line-of-Sight
Terramar LS 900 MHz 10 MHz 33.13339N 117.33327W 33 2.714 352.3 55.705 -59 dBm ± 5 dB 100 Elm Reservoir 33.17268N 117.33015W 50 Near Line-of-Sight
May Company PRS 900 MHz 10 MHz 33.17391N 117.32425W 15 0.189 131.1 56.807 -49 dBm ± 9 dB 100 Tanglewood PRS 33.17173N 117.32227W 25 Non Line-of-Sight
Subscriber Module (SM) Name Band Bandwidth
SM
Latitude
SM
Longitude
SM Height
(ft)Range (mi.)
SM Antenna
Magnetic
Azimuth (deg)
Aggregate Throughput
(Mbps)Predicted Receive Power
Link Predicted
Availability (%)Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type
CWA #2 900 MHz 10 MHz 33.11024N 117.23688W 30 0.332 146.8 56.793 -54 dBm ± 9 dB 100 La Costa Hi 33.10577N 117.23476W 10 Non Line-of-Sight
Mahr Reservoir 900 MHz 10 MHz 33.09430N 117.22293W 15 1.049 307.3 57.334 -55 dBm ± 6 dB 100 La Costa Hi 33.10574N 117.23486W 10 Near Line-of-Sight
Melrose & Corintia Meter Vault 900 MHz 10 MHz 33.10735N 117.22686W 25 0.479 244.9 57.239 -52 dBm ± 8 dB 100 La Costa Hi 33.10571N 117.23489W 10 Near Line-of-Sight
Santa Fe 2 Reservoir
Subscriber Module (SM) Name Band Bandwidth
SM
Latitude
SM
Longitude
SM Height
(ft)Range (mi.)
SM Antenna
Magnetic
Azimuth (deg)
Aggregate Throughput
(Mbps)Predicted Receive Power
Link Predicted
Availability (%)Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type
CWA #6 900 MHz 10 MHz 33.13116N 117.20820W 10 0.478 304.1 57.344 -43 dBm ± 5 dB 100 Santa Fe 1 Reservoir 33.13611N 117.21397W 38 Near Line-of-Sight
La Costa Reclaim PRS 900 MHz 10 MHz 33.11787N 117.25006W 25 1.48 63.1 57.344 -54 dBm ± 5 dB 100 Santa Fe 2 Reservoir 33.12358N 117.22546W 10 Near Line-of-Sight
Melrose PRV Potable 900 MHz 10 MHz 33.12341N 117.23869W 20 0.773 77.4 57.344 -48 dBm ± 5 dB 100 Santa Fe 2 Reservoir 33.12363N 117.22537W 15 Line-of-Sight
Poinsettia LS 900 MHz 10 MHz 33.11552N 117.25834W 33 1.986 62.3 57.344 -56 dBm ± 5 dB 100 Santa Fe 2 Reservoir 33.12358N 117.22546W 10 Line-of-Sight
Santa Fe 1 Reservoir 900 MHz 10 MHz 33.13611N 117.21397W 38 1.091 206.2 35.471 -73 dBm ± 12 dB 99.9999 Santa Fe 2 Reservoir 33.12358N 117.22546W 10 Non Line-of-Sight
Site Data Summary
Maerkle Reservoir
Subscriber Module (SM) Name Band Bandwidth
SM
Latitude
SM
Longitude
SM Height
(ft)Range (mi.)
SM Antenna
Magnetic
Azimuth (deg)
Aggregate Throughput
(Mbps)Predicted Receive Power
Link Predicted
Availability (%)Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type
Bressi Potable Pump Station 900 MHz 10 MHz 33.12931N 117.26587W 25 1.63 360 57.344 -54 dBm ± 5 dB 100 Maerkle Reservoir 33.15249N 117.26029W 90 Line-of-Sight
Bressi Reclaim Pump Station 900 MHz 10 MHz 33.12918N 117.26583W 25 1.649 359.8 57.344 -54 dBm ± 5 dB 100 Maerkle Reservoir 33.15265N 117.26028W 30 Line-of-Sight
C Reservoir Station 900 MHz 10 MHz 33.16067N 117.28042W 40 1.292 103.8 57.344 -52 dBm ± 5 dB 100 Maerkle Reservoir 33.15265N 117.26028W 30 Line-of-Sight
Calavera Reclaim Pump Station 900 MHz 10 MHz 33.15977N 117.29156W 22 1.878 93.6 52.722 -65 dBm ± 8 dB 100 Maerkle Reservoir 33.15265N 117.26028W 30 Near Line-of-Sight
Cannon LS 900 MHz 10 MHz 33.14514N 117.30394W 33 2.585 67.1 55.705 -58 dBm ± 5 dB 100 Maerkle Reservoir 33.15252N 117.26022W 90 Line-of-Sight
CWA #3 900 MHz 10 MHz 33.16181N 117.25639W 45 0.67 188.2 56.986 -58 dBm ± 8 dB 100 Maerkle Reservoir 33.15265N 117.26028W 30 Non Line-of-Sight
El Fuerte LS 900 MHz 10 MHz 33.13735N 117.25794W 33 1.054 341.3 35.677 -73 dBm ± 12 dB 99.9999 Maerkle Reservoir 33.15252N 117.26022W 90 Non Line-of-Sight
Faraday Reclaim PRS 900 MHz 10 MHz 33.13907N 117.29147W 15 2.035 51.4 54.621 -64 dBm ± 7 dB 100 Maerkle Reservoir 33.15252N 117.26022W 90 Near Line-of-Sight
Maerkle Control PRV 900 MHz 10 MHz 33.13790N 117.27405W 10 1.283 26.9 57.344 -52 dBm ± 5 dB 100 Maerkle Reservoir 33.15249N 117.26029W 90 Line-of-Sight
Maerkle Hydroelectric 900 MHz 10 MHz 33.15285N 117.26149W 13 0.074 94.8 57.344 -35 dBm ± 5 dB 100 Maerkle Reservoir 33.15255N 117.26027W 95 Line-of-Sight
Maerkle Lower Chlorine Station 900 MHz 10 MHz 33.15038N 117.26147W 31 0.171 12.3 55.828 -53 dBm ± 10 dB 100 Maerkle Reservoir 33.15265N 117.26028W 30 Non Line-of-Sight
Maerkle Upper Chlorine Station 900 MHz 10 MHz 33.15295N 117.25961W 6 0.047 222.7 57.344 -35 dBm ± 5 dB 100 Maerkle Reservoir 33.15255N 117.26027W 95 Line-of-Sight
Point D PRV North 900 MHz 10 MHz 33.13000N 117.26635W 10 1.589 1.3 57.344 -54 dBm ± 5 dB 100 Maerkle Reservoir 33.15249N 117.26029W 90 Line-of-Sight
Rancho Carlsbad PRS 900 MHz 10 MHz 33.14692N 117.28962W 25 1.743 65.8 57.343 -56 dBm ± 6 dB 100 Maerkle Reservoir 33.15249N 117.26029W 90 Near Line-of-Sight
Robertson Ranch PRS 900 MHz 10 MHz 33.15592N 117.29963W 25 2.292 84.1 57.329 -60 dBm ± 6 dB 100 Maerkle Reservoir 33.15265N 117.26028W 30 Near Line-of-Sight
TAP Reservoir
Subscriber Module (SM) Name Band Bandwidth
SM
Latitude
SM
Longitude
SM Height
(ft)Range (mi.)
SM Antenna
Magnetic
Azimuth (deg)
Aggregate Throughput
(Mbps)Predicted Receive Power
Link Predicted
Availability (%)Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type
Calavera Potable Pump Station 900 MHz 10 MHz 33.16846N 117.29522W 20 0.238 340 57.344 -37 dBm ± 5 dB 100 TAP Reservoir 33.17188N 117.29583W 42 Line-of-Sight
CWA #4 900 MHz 10 MHz 33.16718N 117.26559W 45 1.781 269 57.344 -55 dBm ± 5 dB 100 TAP Reservoir 33.17190N 117.29580W 42 Line-of-Sight
Elm Tap PRS 900 MHz 10 MHz 33.17142N 117.31574W 25 1.156 76.8 46.368 -67 dBm ± 10 dB 100 TAP Reservoir 33.17190N 117.29580W 42 Non Line-of-Sight
Laguna/Kelly Reclaim PRS 900 MHz 10 MHz 33.15252N 117.31043W 25 1.582 20.9 43.177 -69 dBm ± 9 dB 100 TAP Reservoir 33.17190N 117.29580W 42 Non Line-of-Sight
Lake Calavera 900 MHz 10 MHz 33.16969N 117.28738W 16 0.511 275.8 35.718 -71 dBm ± 13 dB 99.9999 TAP Reservoir 33.17190N 117.29580W 42 Non Line-of-Sight
TAP 4 Station 900 MHz 10 MHz 33.16730N 117.26677W 25 1.707 268.8 57.344 -54 dBm ± 5 dB 100 TAP Reservoir 33.17173N 117.29575W 35 Line-of-Sight
Villas LS 900 MHz 10 MHz 33.16868N 117.30372W 33 0.507 54 49.636 -64 dBm ± 11 dB 100 TAP Reservoir 33.17173N 117.29575W 35 Non Line-of-Sight
City of Carlsbad / CMWD SCADA Master Plan
Q-1
SC07221_FINAL_Carlsbad SCADA Master Plan
Appendix Q: Radio Communications Site Report
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-2
SC07221_FINAL_Carlsbad SCADA Master Plan
Site Report
This section contains the Radio Link Profiles of the radio links. The radios sites are at either end of
the profile. The profile includes information on the terrain between the sites, the link Fresnel zone,
obstructions, and line from antennas to largest obstruction. Figure 1 is an example of a link profile.
The link profile is explained below.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type CWRF 5.8 GHz 45 MHz 33.113 N 117.3202 W 132 3.3 87 449 -50 dBm +/- 5 dB 100 CPWD 33.125 N 117.2868 W 99 Line of Sight
Figure 1. Example of a Radio Path Profile
The figure represents a cross section view of the radio path. The radio sites are at either end of the
figure. The brown region in represents the topology between the two radio sites. The blue area
represents the Fresnel zone or radio path. The green line along the axis of the Fresnel zone is a
direct line between the two antennas. The red line is a line from each antenna to the highest point
between the antenna.
In the ideal radio path profile, the Fresnel zone is clear of any obstructions. A Fresnel zone free of
obstruction with the right radio/antenna combination of will provide an operational radio link. For
this report the existing antenna heights were used for the Computer Path Study. While some of the
paths show paths with interference the model indicated that the links will perform acceptably. Each
link should be verified with a radio survey.
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-3
SC07221_FINAL_Carlsbad SCADA Master Plan
Master Sites
All master sites are connected as a redundant backbone with a ring topology. Each master site to
master site communication desktop study was conducted at 23GHz. Each Master site will act as the
hub for surrounding remote sites.
CMWD Building to Maerkle Reservoir
The link from the CMWD to the Maerkle Reservoir has line of sight. The predicted received power of -
38 dBM is good.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type CMWD Building
23 GHz 10 MHz 33.13249N 117.26823W 46 1.464 6.9 143.398 -38 dBm
± 4 dB
100 Maerkle Reservoir
33.15265N 117.26028W 30 Line-of-Sight
Figure 2. Radio Path Profile CMWD Building – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-4
SC07221_FINAL_Carlsbad SCADA Master Plan
Elm Reservoir to D Site
The link from the Elm Reservoir to the D Site has line of sight. The predicted received power of -49
dBm is good.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type Elm
Reservoir
23
GHz
10
MHz
33.17268
N
117.33015
W
50 4.85
9123
137.4 143.38
4
-49
dBm ± 4 dB
99.999
5
D
Site
33.11226
N
117.28695
W
78 Line-
of-Sight
Figure 3. Radio Path Profile Elm Reservoir to D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-5
SC07221_FINAL_Carlsbad SCADA Master Plan
La Costa High Reservoir to D Site
The link between the La Costa High Reservoir and the D site has line of sight. The predicted received
power of -45 dBm is good.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type La Costa Hi Reservoi
r
23 GHz 10 MHz 33.10571N 117.23489W 10 3.0527967 267 143.396 -45 dBm ± 4
dB
99.9999 D Site 33.11226N 117.28695W 78 Line-of-Sigh
t
Figure 4. Radio Path Profile La Costa High Reservoir – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-6
SC07221_FINAL_Carlsbad SCADA Master Plan
Santa Fe 2 Reservoir to CMWD Building
The link from the Santa Fe 2 Reservoir to the CMWD building has line of sight. The predicted
received power of -43 dBm is good.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type Santa Fe 2
Reservoir
23 GHz 10 MHz 33.12355N 117.22532W 16 2.5631562 272.4 143.397 -43 dBm
± 4
dB
100 CMWD Building 33.13249N 117.26823W 46 Line-of-
Sight
Figure 5. Radio Path Profile Santa Fe 2 – CMWD
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-7
SC07221_FINAL_Carlsbad SCADA Master Plan
Maerkle Reservoir to TAP Reservoir
The link from the TAP Reservoir to the Maerkle Reservoir has line of sight. The predicted received
power of -43 dBm is good.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type TAP Reservoir 23 GHz 10 MHz 33.17188N 117.29583W 43 2.4519307 111.4 143.397 -43 dBm
± 4
dB
100 Maerkle Reservoir 33.15257N 117.26030W 20 Line-of-
Sight
Figure 6. Radio Path Profile TAP Reservoir – Maerkle
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-8
SC07221_FINAL_Carlsbad SCADA Master Plan
La Costa High Reservoir to Santa Fe 2 Reservoir
The link from the Santa Fe 2 Reservoir to the La Costa Reservoir has line of sight. The predicted
received power of -52 dBm is good.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type La Costa
Hi
Reservoir
23
GHz
10
MHz
33.10574N 117.23486
W
10 1.346511
4
12.8 142.81
1
-52
dB
m ± 8 dB
99.999
5
Santa Fe
2
Reservoir
33.12355N 117.22532
W
16 Non
Line-
of-Sight
Figure 7. Radio Path Profile La Costa High – Santa Fe 2
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-9
SC07221_FINAL_Carlsbad SCADA Master Plan
Elm Reservoir to TAP Reservoir
The link from the Elm Reservoir to the TAP Reservoir has line of sight. The predicted received power
of -41 dBm is good.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type Elm
Reservoir
23
GHz
10
MHz
33.17267
N
117.33011
W
53 1.929009
2
80 143.39
8
-41
dBm ± 4 dB
100 TAP
Reservoir
33.17190
N
117.29580
W
42 Line-
of-Sight
Figure 8. Radio Path Profile Elm Reservoir – TAP Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-10
SC07221_FINAL_Carlsbad SCADA Master Plan
D Site Links
This section contains the results of the desk top study for sites attached to the D site repeater. Each
of the sites assigned to the D Site repeater is operating at a frequency of 900 MHz.
Ayers PRP Reclaim Site
The link from the Ayers PRV to the D site does not have a clear line of sight. The predicted received
power of -63 dBm is good.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type Ayers PRV
Reclaim
90
0 MHz
10
MHz
33.10531N 117.26740
W
25 1.241 281.
2
55.704 -63 dBm
± 8 dB
100 D Site 33.11226N 117.28714
W
75 Non
Line-of-Sight
Figure 9. Radio Path Profile Ayers PRV – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-11
SC07221_FINAL_Carlsbad SCADA Master Plan
Encina Reclaim PRV Site
The link from the Encina Reclaim PRV to the D Site does not have line of sight. The predicted
received power of -74 dBm is marginal to poor. CMWD currently uses Encina reclaim pump station as
a repeater site for Encina Reclaim PRV site. This may be an appropriate repeater if the physical radio
study confirms the signal is poor.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type Encina Reclaim
PRV
900 MH
z
10 MHz 33.11019N 117.31804W 10 1.81 73.9 34.058 -74 dBm ±
11 dB
100 D Site 33.11230N 117.28694W 78 Non Line-
of-
Sight
Figure 10. Radio Path Profile Encina Reclaim PRV – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-12
SC07221_FINAL_Carlsbad SCADA Master Plan
Encina Reclaim Pump Station
The link from the Encina Reclaim pump station to the D site is near line of sight. The predicted
received power of -63 dBm is good.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type Encina
Reclaim Pump Station
900
MHz
10
MHz
33.11429N 117.31887
W
40 1.857 82.7 56.047 -63
dBm ± 7 dB
100 D Site 33.11230N 117.28694
W
78 Near
Line-of-Sight
Figure 11. Radio Path Profile Encina Reclaim PS – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-13
SC07221_FINAL_Carlsbad SCADA Master Plan
Fox’s Lift Station
The link from Fox’s Lift Station to the D site does not have line of sight. The predicted received power
of -76 dBm is marginal.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type Fox's LS 900 MH
z
10 MHz 33.14793N 117.33348W 33 3.658 120.5 30.049 -76 dBm ± 9 dB 100 D Site 33.11240N 117.28662W 55 Non Line-
of-
Sight
Figure 12. Radio Path Profile Fox’s LS – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-14
SC07221_FINAL_Carlsbad SCADA Master Plan
Knots Lift Station
The Knots lift station has near line of sight with a predicted received power of -62 dBm. The
predicted received power is good to marginal.
Desktop Radio Study Subscriber Module (SM) Name Band Bandwidth SM Latitude SM Longitude SM Height (ft) Range (mi.) Antenna Magnetic Azimuth (deg) Aggregate Throughput (Mbps) Predicted Receive Power Link Predicted Availability (%) Access Point (AP) Name AP Latitude AP Longitude AP Height (ft) Profile Type Knots LS 900 MH
z
10 MHz 33.09102N 117.31051W 33 2.023 31.7 57.102 -62 dBm ±
7 dB
100 D Site 33.11240N 117.28662W 55 Near Line-
of-
Sight
Figure 13. Knots Lift Station – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-15
SC07221_FINAL_Carlsbad SCADA Master Plan
La Costa Low Reservoir
The link from the La Costa Low Reservoir to the D site has line of sight. The predicted receive power
of -57 dBm is good.
1) Desktop Radio Study 2) Subscriber Module (SM) Name 3) Band 4) Bandwidth 5) SM 6) Latitude 7) SM 8) Longitude 9) SM 10) Height (ft) 11) Range (mi.) 12) Antenna Magnetic Azimuth (deg) 13) Aggregate Throughput (Mbps) 14) Predicted Receive Power 15) Link Predicted Availability (%) 16) Access Point (AP) Name 17) AP 18) Latitude 19) AP 20) Longitude 21) AP Height (ft) 22) Profile Type 23) La Costa Lo Reservoir
24) 00 MHz
25) 0 MHz
26) 33.10164N 27) 117.25162W 28) 5 29) .176 30) 78.2 31) 7.344
32) -57 dBm ± 5 dB
33) 00 34) Site 35) 33.11226N 36) 117.28695W 37) 8
38)
ine-of-Sight
Figure 14. Radio Path Profile La Costa Low Reservoir – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-16
SC07221_FINAL_Carlsbad SCADA Master Plan
Lower El Fuerte Pressure Reduction Station
The link from the Lower El Fuerte PRS to the D site has line of sight. The predicted received signal
strength of -58 dBm is good.
39) Desktop Radio Study 40) Subscriber Module (SM) Name 41) Band 42) Bandwidth 43) SM 44) Latitude 45) SM 46) Longitude 47) SM 48) Height (ft) 49) Range (mi.) 50) Antenna Magnetic Azimuth (deg) 51) Aggregate Throughput (Mbps) 52) Predicted Receive Power 53) Link Predicted Availability (%) 54) Access Point (AP) Name 55) AP 56) Latitude 57) AP 58) Longitude 59) AP Height (ft) 60) Profile Type 61) Lower
El Fuerte
PRS
62) 00
MH
z
63) 0
MHz
64) 3
3.09508N
65) 117
.25015W
66)
0
67)
.441
68)
87.5
69)
7.344
70) -58 dBm
± 5 dB
71)
00
72)
Site
73) 3
3.11226N
74) 11
7.28695W
75)
8
76) ine-of-
Sight
Figure 15. Lower El Fuerte – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-17
SC07221_FINAL_Carlsbad SCADA Master Plan
Palomar West Pressure Reducing Valve
The link does not have clear line of site and the Fresnel zone is severely impacted by the terrain. The
predicted received power is marginal to poor given the large tolerance of +/- 11 dB at -74 dBm.
Encina Reclaim Pump Station may be an appropriate repeater if the physical radio study confirms
the signal is poor.
77) Desktop Radio Study 78) Subscriber Module (SM) Name 79) Band 80) Bandwidth 81) SM 82) Latitude 83) SM 84) Longitude 85) SM 86) Height (ft) 87) Range (mi.) 88) Antenna Magnetic Azimuth (deg) 89) Aggregate Throughput (Mbps) 90) Predicted Receive Power 91) Link Predicted Availability (%) 92) Access Point (AP) Name 93) AP 94) Latitude 95) AP 96) Longitude 97) AP Height (ft) 98) Profile Type 99) P
alomar
West PRV
100) 00
MH
z
101)
0
MHz
102) 3
3.12177N
103) 117
.31332W
104
5
105)
.663
106)
01.6
107)
5.378
108)
74 dBm
± 11 dB
109)
00
110)
Site
111) 3
3.11230N
112) 11
7.28694W
113)
8
114) on
Line-
of-Sight
Figure 16. Radio Path Profile Palomar West PRV – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-18
SC07221_FINAL_Carlsbad SCADA Master Plan
Sand Shell Lift Station
The from the Sand Shell Lift Station to the D site does not have line of site and the Fresnel zone is
impacted. The predicted received signal strength of -67dBm is good to marginal.
115) Desktop Radio Study 116) Subscriber Module (SM) Name 117) Band 118) Bandwidth 119) SM 120) Latitude 121) SM 122) Longitude 123) SM 124) Height (ft) 125) Range (mi.) 126) Antenna Magnetic Azimuth (deg) 127) Aggregate Throughput (Mbps) 128) Predicted Receive Power 129) Link Predicted A il bilit (%) 130) Access Point (AP) Name 131) AP 132) Latitude 133) AP 134) Longitude 135) AP Height (ft) 136) Profile Type 137) Sand Shell LS
138) 00 MHz
139) 0 MHz
140) 33.10278N 141) 117.31579W 142) 3 143) .817 144) 7.1 145) 6.024
146) -67 dBm ± 9 dB
147) 00 148) Site 149) 33.11240N 150) 117.28662W 151 5
152)
on Line-of-Sight
Figure 17. Radio Path Profile Sand Shell – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-19
SC07221_FINAL_Carlsbad SCADA Master Plan
Twin D Recycle Pump Station
The link from the Twin D Recycle Pump Station to the D site has a clear line of sight and a clear
Fresnel zone. The predicted received signal strength of -35 dBm is very good.
153) Desktop Radio Study 154) Subscriber Module (SM) Name 155) Band 156) Bandwidth 157) SM 158) Latitude 159) SM 160) Longitude 161) SM 162) Height (ft) 163) Range (mi.) 164) Antenna Magnetic Azimuth (deg) 165) Aggregate Throughput (Mbps) 166) Predicted Receive Power 167) Link Predicted Availability (%) 168) Access Point (AP) Name 169) AP 170) Latitude 171) AP 172) Longitude 173) AP Height (ft) 174) Profile Type 175) Twin D
Recycle
Pump Station
176) 00
MH
z
177)
0
MHz
178) 33
.11256N
179) 11
7.28728W
180)
7
181)
.027
182)
20.8
183)
7.344
184)
35 dBm
± 5 dB
185)
00
186)
Site
187) 3
3.11230N
188) 117
.28694W
189
8
190)
ine-of-
Sight
Figure 18. Radio Path Profile Twin D – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-20
SC07221_FINAL_Carlsbad SCADA Master Plan
Upper El Fuerte Pressure Reducing Station
The link from the Upper El Fuerte PRS to the D site has a clear line of sight and a slightly impacted
Fresnel Zone. The predicted received signal strength of -62 dBm is good.
191) Desktop Radio Study 192) Subscriber Module (SM) Name 193) Band 194) Bandwidth 195) SM 196) Latitude 197) SM 198) Longitude 199) SM 200) Height (ft) 201) Range (mi.) 202) Antenna Magnetic Azimuth (deg) 203) Aggregate Throughput (Mbps) 204) Predicted Receive Power 205) Link Predicted Availability (%) 206) Access Point (AP) Name 207) AP 208) Latitude 209) AP 210) Longitude 211) AP Height (ft) 212) Profile Type 213) Upper El Fuerte PRS
214) 00 MHz
215) 0 MHz
216) 33.09750N 217) 117.24517W 218) 0 219) .638 220) 81.2 221) 5.413
222) 62 dBm ± 6 dB
223) 00 224) Site 225) 33.11226N 226) 117.28714W 227 5
228)
ear Line-of-Sight
Figure 19. Radio Path Profile Upper El Fuerte – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-21
SC07221_FINAL_Carlsbad SCADA Master Plan
Zodiac PRV
The link from the Zodiac PRV station to the D site has a clear line of sight and a clear Fresnel zone.
The predicted received signal strength of -56 dBm is good.
229) Desktop Radio Study 230) Subscriber Module (SM) Name 231) Band 232) Bandwidth 233) SM 234) Latitude 235) SM 236) Longitude 237) SM 238) Height (ft) 239) Range (mi.) 240) Antenna Magnetic Azimuth (deg) 241) Aggregate Throughput (Mbps) 242) Predicted Receive Power 243) Link Predicted Availability (%) 244) Access Point (AP) Name 245) AP 246) Latitude 247) AP 248) Longitude 249) AP Height (ft) 250) Profile Type 251) Zodiac
PRV
252) 00
MH
z
253) 0
MHz
254) 3
3.10576N
255) 11
7.25291W
256
0
257)
.022
258)
71.3
259)
7.344
260) 56 dBm
± 5 dB
261)
00
262)
Site
263) 3
3.11226N
264) 11
7.28691W
265)
9
266) ine-
of-
Sight
Figure 20. Radio Path Profile Zodiac – D Site
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-22
SC07221_FINAL_Carlsbad SCADA Master Plan
North Batiquitos Lift Station
Communications with the North Batiquitos Lift Station area repeated at the Knots Lift Station. The
link between North Batiquitos Lift Station and the Knots Lift Station does not have line of sight and
the Fresnel zone is severely impacted. The predicted received signal strength of -73 dBm with a +/-
13 dB tolerance is marginal to weak. No other sites can repeat a signal from North Batiquitos LS.
267) Desktop Radio Study 268) Subscriber Module (SM) Name 269) Band 270) Bandwidth 271) SM 272) Latitude 273) SM 274) Longitude ) 276) Height 277) Range (mi.) 278) Antenna Magnetic Azimuth (deg) 279) Aggregate Throughput (Mbps) 280) Predicted Receive Power 281) Link Predicted Availability (%) 282) Access Point (AP) Name 283) AP 284) Latitude 285) AP 286) Longitude 287) AP Height (ft) 288) Profile Type 289) N. Batiquito
s LS
290) 00 MH
z
291) 0
MHz
292) 33.09312N
293) 117.30013
W
294 3 295) .619 296) 45 297) 2.96
298) 73 dBm
± 13 dB
299) 9.9995 300) nots LS 301) 33.09102N 302) 117.31051W 303) 3
304) on Line-
of-
Sight
Figure 21. North Batiquitos LS – Knots LS
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-23
SC07221_FINAL_Carlsbad SCADA Master Plan
Elm Reservoir Repeater
The sites in this section attached to the network thru the Elm Reservoir access point. The Elm
Reservoir site part of the network backbone.
Chinquapin Lift Station
The link from the Chinquapin Lift Station to the Elm Reservoir does not have line of sight and has a
severely impacted Fresnel zone. The predicted received signal strength of – 73 dBm with a tolerance
of +/- 10 dB is marginal to poor. No other sites were able to repeat a signal from Chinquapin LS.
305) Desktop Radio Study 306) Subscriber Module (SM) Name 307) Band 308) Bandwidth 309) SM 310) Latitude 311) SM 312) Longitude 313) SM 314) Height (ft) 315) Range (mi.) 316) Antenna Magnetic Azimuth (d ) 317) Aggregate Throughput (Mbps) 318) Predicted Receive Power 319) Link Predicted Availability (%) 320) Access Point (AP) Name 321) AP 322) Latitude 323) AP 324) Longitude 325) AP Height (ft) 326) Profile Type 327) Chinquapin LS
328) 00 MHz
329) 0 MHz 330) 33.14599N 331) 117.34381W 332 3 333) .003 334) 1.8 335) 7.237
336) 73 dBm ± 10 dB
337) 00
338) Elm Reservoir
339) 33.17267N 340) 117.33011W 341) 3
342)
on Line-of-Sight
Figure 22. Radio Path Profile Chinquapin – Elm Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-24
SC07221_FINAL_Carlsbad SCADA Master Plan
Ellery Reservoir
The link from the Ellery Reservoir to the Elm Reservoir is near line of sight. The Fresnel zone is
slightly impacted. The predicted received signal strength of -47 dBm is good.
343) Desktop Radio Study 344) Subscriber Module (SM) Name 345) Band 346) Bandwidth 347) SM 348) Latitude 349) SM 350) Longitude 351) SM 352) Height (ft) 353) Range (mi.) 354) Antenna Magnetic Azimuth (deg) 355) Aggregate Throughput (Mbps) 356) Predicted Receive Power 357) Link Predicted A ailabilit (%) 358) Access Point (AP) Name 359) AP 360) Latitude 361) AP 362) Longitude 363) AP Height (ft) 364) Profile Type 365) Ellery Reservoir
366) 00 MHz
367) 0 MHz
368) 33.16546N 369) 117.32283W 370 5 371) .654 372) 08 373) 7.344
374) 47 dBm ± 5 dB
375) 00
376) Elm Reservoir
377) 33.17268N 378) 117.33015W 379) 0
380)
ear Line-of-Sight
Figure 23. Radio Path Profile Ellery Reservoir – Elm Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-25
SC07221_FINAL_Carlsbad SCADA Master Plan
Home Plant Lift Station
The link from the Home Plant lift station to the Elm Reservoir has a clear line of sight and a clear
Fresnel zone. The predicted received signal strength of – 53d dBm is good.
381) Desktop Radio Study 382) Subscriber Module (SM) Name 383) Band 384) Bandwidth 385) SM 386) Latitude 387) SM 388) Longitude 389) SM 390) Height (ft) 391) Range (mi.) 392) Antenna Magnetic Azimuth (deg) 393) Aggregate Throughput (Mbps) 394) Predicted Receive Power 395) Link Predicted A il bilit (%) 396) Access Point (AP) Name 397) AP 398) Latitude 399) AP 400) Longitude 401) AP Height (ft) 402) Profile Type 403) Home Plant LS
404)
00 MHz
405) 0 MHz
406) 33.16535N 407) 117.35483W 408) 3 409) .519 410) 9.1 411) 7.344
412) -53 dBm ± 5 dB
413) 00
414)
lm Reservoir
415) 33.17267N 416) 117.33011W 417) 3
418)
ine-of-Sight
Figure 24. Radio Path Profile Home Plant LS – Elm Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-26
SC07221_FINAL_Carlsbad SCADA Master Plan
Pine Beach Bathroom Lift Station
The link from the Pine Brach Bathroom Lift Station to the Elm Reservoir has a clear line of sight and
a clear Fresnel zone. The predicted received signal strength of -60 dBm is good.
419) Desktop Radio Study 420) Subscriber Module (SM) Name 421) Band 422) Bandwidth 423) SM 424) Latitude 425) SM 426) Longitude 427) SM 428) Height (ft) 429) Range (mi.) 430) Antenna Magnetic Azimuth (d ) 431) Aggregate Throughput (Mbps) 432) Predicted Receive Power 433) Link Predicted Availability (%) 434) Access Point (AP) Name 435) AP 436) Latitude 437) AP 438) Longitude 439) AP Height (ft) 440) Profile Type 441) P
ine Beach Bathroom LS
442)
00 MHz
443) 0 MHz 444) 33.15445N 445) 117.35089W 446 3 447) .739 448) 2.2 449) 7.294
450) 60 dBm ± 7 dB
451) 00
452) Elm Reservoir
453) 33.17268N 454) 117.33015W 455) 0
456)
ear Line-0f-Sight
Figure 25. Radio Path Profile Pine Beach Bathroom LS – Elm Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-27
SC07221_FINAL_Carlsbad SCADA Master Plan
Skyline Reservoir
The link from the Elm Reservoir to the Skyline Reservoir has an impacted Fresnel zone resulting in a
near line of sight profile. The predicted signal strength of -58 dBm is good.
457) Desktop Radio Study 458) Subscriber Module (SM) Name 459) Band 460) Bandwidth 461) SM 462) Latitude 463) SM 464) Longitude 465) SM 466) Height (ft) 467) Range (mi.) 468) Antenna Magnetic Azimuth (deg) 469) Aggregate Throughput (Mbps) 470) Predicted Receive Power 471) Link Predicted A il bilit (%) 472) Access Point (AP) Name 473) AP 474) Latitude 475) AP 476) Longitude 477) AP Height (ft) 478) Profile Type 479) Skyline Reservoir
480)
00 MHz
481)
0 MHz
482) 33.15071N 483) 117.31952W 484) 5 485) .635 486) 26.4 487) 7.294
488) -60 dBm ± 7 dB
489) 00
490) Elm Reservoir
491) 33.17268N 492) 117.33015W 493) 0
494)
ear Line-0f-Sight
Figure 26. Radio Path Profile Skyline Reservoir – Elm Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-28
SC07221_FINAL_Carlsbad SCADA Master Plan
Tamarack/Frazee Beach Bathroom Lift Station
This link from the Tamarack/Frazee Beach LS to the Elm Reservoir has an impacted Fresnel zone
resulting in a near line of sight profile. The predicted received signal strength is good at -59 dBm.
495) Desktop Radio Study 496) Subscriber Module (SM) Name 497) Band 498) Bandwidth 499) SM 500) Latitude 501) SM 502) Longitude 503) SM 504) Height (ft) 505) Range (mi.) 506) Antenna Magnetic Azimuth (deg) 507) Aggregate Throughput (Mbps) 508) Predicted Receive Power 509) Link Predicted A il bilit (%) 510) Access Point (AP) Name 511) AP 512) Latitude 513) AP 514) Longitude 515) AP Height (ft) 516) Profile Type 517) T
amarack/ Frazee Beach Bathroom
LS
518) 00 MHz
519) 0 MHz
520) 33.14749N 521) 117.34567W 522) 3 523) .956 524) 5.9 525) 7.338
526) -59 dBm ± 6 dB
527) 00
528) Elm Reservoir
529) 33.17267N 530) 117.33011W 531) 3
532)
ear Line-0f-Sight
Figure 27. Radio Path Profile Tamarack/Frazee Beach LS – Elm Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-29
SC07221_FINAL_Carlsbad SCADA Master Plan
Tanglewood Pressure Reducing Station
The link from the Tanglewood PRS to the Elm Reservoir does not have a clear line of sight and has a
severely impacted Fresnel zone. The model gives a predicted received signal strength of -66 dBm
with a tolerance of +/- 12 dB which is moderate.
533) Desktop Radio Study 534) Subscriber Module (SM) Name 535) Band 536) Bandwidth 537) SM 538) Latitude 539) SM 540) Longitude 541) SM 542) Height (ft) 543) Range (mi.) 544) Antenna Magnetic Azimuth (deg) 545) Aggregate Throughput (Mbps) 546) Predicted Receive Power 547) Link Predicted A il bilit (%) 548) Access Point (AP) Name 549) AP 550) Latitude 551) AP 552) Longitude 553) AP Height (ft) 554) Profile Type 555) Tanglewood PRS
556) 00 MHz
557) 0 MHz
558) 33.17173N 559) 117.32227W 560) 5 561) .459 562) 66.6 563) 6.304
564) -66 dBm ± 12 dB
565) 00
566) Elm Reservoir
567) 33.17267N 568) 117.33011W 569) 3
570)
ear Line-0f-Sight
Figure 28. Radio Path Profile Tanglewood PRS – Elm Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-30
SC07221_FINAL_Carlsbad SCADA Master Plan
Terramar Lift Station
This link between the Terramar LS and the Elm Reservoir is near line of sight due to a slightly
impacted Fresnel zone. The predicted received power of -59 dBm is good.
571) Desktop Radio Study 572) Subscriber Module (SM) Name 573) Band 574) Bandwidth 575) SM 576) Latitude 577) SM 578) Longitude 579) SM 580) Height (ft) 581) Range (mi.) 582) Antenna Magnetic Azimuth (deg) 583) Aggregate Throughput (Mbps) 584) Predicted Receive Power 585) Link Predicted A il bilit (%) 586) Access Point (AP) Name 587) AP 588) Latitude 589) AP 590) Longitude 591) AP Height (ft) 592) Profile Type 593) Terramar LS
594)
00 MHz
595)
0 MHz
596) 33.13339N 597) 117.33327W 598) 3 599) .714 600) 52.3 601) 5.705
602) -59 dBm ± 5 dB
603) 00
604) Elm Reservoir
605) 33.17268N 606) 117.33015W 607) 3
608)
ear Line-0f-Sight
Figure 29. Radio Path Profile Terramar LS – Elm Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-31
SC07221_FINAL_Carlsbad SCADA Master Plan
May Company Pressure Reducing Station
The May Company PRS is repeated to the Elm Reservoir access point through the Tanglewood PRS.
This link does not have line of sight and has a severely impacted Fresnel zone. The predicted
received signal strength of -49 dBm is good.
609) Desktop Radio Study 610) Subscriber Module (SM) Name 611) Band 612) Bandwidth 613) SM 614) Latitude 615) SM 616) Longitude 617) SM 618) Height (ft) 619) Range (mi.) 620) Antenna Magnetic Azimuth (deg) 621) Aggregate Throughput (Mbps) 622) Predicted Receive Power 623) Link Predicted A il bilit (%) 624) Access Point (AP) Name 625) AP 626) Latitude 627) AP 628) Longitude 629) AP Height (ft) 630) Profile Type 631) May Company PRS
632) 00 MHz
633) 0 MHz
634) 33.17391N 635) 117.32425W 636) 5 637) .189 638) 31.1 639) 6.807
640) -49 dBm ± 9 dB
641) 00
642) Tanglewood PRS
643) 33.17173N 644) 117.32227W 645) 5
646)
on Line-0f-Sight
Figure 30. Radio Path Profile May Company – Tanglewood PRS
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-32
SC07221_FINAL_Carlsbad SCADA Master Plan
La Costa High Reservoir Repeater
The stations in this section connected to the La Costa High Reservoir repeater for network access.
CWA #2
The link from the La Costa High Reservoir to CWA #2 does not have line of sight and has a
moderately impacted Fresnel zone. The predicated received signal strength of -54 DBm is good.
647) Desktop Radio Study 648) Subscriber Module (SM) Name 649) Band 650) Bandwidth 651) SM 652) Latitude 653) SM 654) Longitude 655) SM 656) Height (ft) 657) Range (mi.) 658) Antenna Magnetic Azimuth (deg) 659) Aggregate Throughput (Mbps) 660) Predicted Receive Power 661) Link Predicted A il bilit (%) 662) Access Point (AP) Name 663) AP 664) Latitude 665) AP 666) Longitude 667) AP Height (ft) 668) Profile Type 669) WA #2
670) 00 MHz
671) 0 MHz
672) 33.11024N 673) 117.23688W 674) 0 675) .332 676) 46.8 677) 6.793
678) -54 dBm ± 9 dB
679) 00
680) La Costa Hi
681) 33.10577N 682) 117.23476W 683) 0
684) on Line-0f-Sight
Figure 31. Radio Path Profile CWA #2 – La Costa High Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-33
SC07221_FINAL_Carlsbad SCADA Master Plan
Mahr Reservoir
The link from the La Costa High Reservoir to the Mahr Reservoir has clear line of sight and a clear
Fresnel zone. The predicted received signal strength of -55 dBm is good.
685) Desktop Radio Study 686) Subscriber Module (SM) Name 687) Band 688) Bandwidth 689) SM 690) Latitude 691) SM 692) Longitude 693) SM 694) Height (ft) 695) Range (mi.) 696) Antenna Magnetic Azimuth (deg) 697) Aggregate Throughput (Mbps) 698) Predicted Receive Power 699) Link Predicted A il bilit (%) 700) Access Point (AP) Name 701) AP 702) Latitude 703) AP 704) Longitude 705) AP Height (ft) 706) Profile Type 707) Mahr Reservoir
708)
00 MHz
709)
0 MHz
710) 33.09430N 711) 117.22293W 712) 5 713) .049 714) 07.3 715) 7.334
716) -55 dBm ± 6 dB
717) 00
718) La Costa Hi
719) 33.10574N 720) 117.23486W 721) 0
722)
ear Line-0f-Sight
Figure 32. Radio Path Profile Mahr Reservoir – La Costa High Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-34
SC07221_FINAL_Carlsbad SCADA Master Plan
Melrose and Corintia Meter Vault
The link from the Melrose and Cortina Meter Vault to the La Costa High Reservoir has a near clear
line of sight due to an impacted Fresnel zone. The predicted received signal strength of -52 dBm is
good.
723) Desktop Radio Study 724) Subscriber Module (SM) Name 725) Band 726) Bandwidth 727) SM 728) Latitude 729) SM 730) Longitude 731) SM 732) Height (ft) 733) Range (mi.) 734) Antenna Magnetic Azimuth (deg) 735) Aggregate Throughput (Mbps) 736) Predicted Receive Power 737) Link Predicted A il bilit (%) 738) Access Point (AP) Name 739) AP 740) Latitude 741) AP 742) Longitude 743) AP Height (ft) 744) Profile Type 745) Melrose & Corintia Meter Vault
746) 00 MHz
747) 0 MHz
748) 33.10735N 749) 117.22686W 750) 5 751) .479 752) 44.9 753) 7.239
754) -52 dBm ± 8 dB
755) 00
756) La Costa Hi
757) 33.10571N 758) 117.23489W 759) 0
760)
ear Line-0f-Sight
Figure 33. Radio Path Profile Melrose & Corintia Meter Vault – La Costa High Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-35
SC07221_FINAL_Carlsbad SCADA Master Plan
Maerkle Reservoir Repeater
The sights in this section connect to the network at the Maerkle Reservoir. The Maerkle Reservoir is
part of the network backbone.
Bressi Potable Pumping Station
The link from the Bressi Ranch Potable Pumping Station to the Maerkle Reservoir has a clear line of
sight and a clear Fresnel zone. The predicted received signal strength of -54 dBm is good.
761) Desktop Radio Study 762) Subscriber Module (SM) Name 763) Band 764) Bandwidth 765) SM 766) Latitude 767) SM 768) Longitude 769) SM 770) Height (ft) 771) Range (mi.) 772) Antenna Magnetic Azimuth (deg) 773) Aggregate Throughput (Mbps) 774) Predicted Receive Power 775) Link Predicted A il bilit (%) 776) Access Point (AP) Name 777) AP 778) Latitude 779) AP 780) Longitude 781) AP Height (ft) 782) Profile Type 783) Bressi Potable Pump Station
784) 00 MHz
785) 0 MHz
786) 33.12931N 787) 117.26587W 788) 5 789) .63 790) 60 791) 7.344
792) -54 dBm ± 5 dB
793) 00
794) Maerkle Reservoir
795) 33.15249N 796) 117.26029W 797) 0
798) ine-0f-Sight
Figure 34. Radio Path Profile Bressi Potable PS – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-36
SC07221_FINAL_Carlsbad SCADA Master Plan
Bressi Recyclable Pump Station
The link from the Bressi Recyclable Pump Station to the Maerkle Reservoir has a clear line of sight
and a clear Fresnel zone. The predicted signal strength of -54 dBm is good.
799) Desktop Radio Study 800) Subscriber Module (SM) Name 801) Band 802) Bandwidth 803) SM 804) Latitude 805) SM 806) Longitude 807) SM 808) Height (ft) 809) Range (mi.) 810) Antenna Magnetic Azimuth (deg) 811) Aggregate Throughput (Mbps) 812) Predicted Receive Power 813) Link Predicted A il bilit (%) 814) Access Point (AP) Name 815) AP 816) Latitude 817) AP 818) Longitude 819) AP Height (ft) 820) Profile Type 821) B
ressi Recyclable Pump Station
822)
00 MHz
823)
0 MHz
824) 33.12918N 825) 117.26583W 826) 5 827) .649 828) 59.8 829) 7.344
830) -54 dBm ± 5 dB
831) 00
832) Maerkle Reservoir
833) 33.15265N 834) 117.26028W 835) 0
836) ine-0f-Sight
Figure 35. Radio Path Profile Bressi Recyclable PS – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-37
SC07221_FINAL_Carlsbad SCADA Master Plan
C Reservoir
The link from the C Reservoir to the Maerkle Reservoir has a clear line of sight and a clear Fresnel
zone. The predicated received signal strength of -52 dBm is good.
837) Desktop Radio Study 838) Subscriber Module (SM) Name 839) Band 840) Bandwidth 841) SM 842) Latitude 843) SM 844) Longitude 845) SM 846) Height (ft) 847) Range (mi.) 848) Antenna Magnetic Azimuth (deg) 849) Aggregate Throughput (Mbps) 850) Predicted Receive Power 851) Link Predicted A il bilit (%) 852) Access Point (AP) Name 853) AP 854) Latitude 855) AP 856) Longitude 857) AP Height (ft) 858) Profile Type 859) C
Reservoir Station
860)
00 MHz
861)
0 MHz
862) 33.16067N 863) 117.28042W 864) 0 865) .292 866) 03.8 867) 7.344
868) -
52 dBm ± 5 dB
869) 00
870) M
aerkle Reservoir
871) 33.15265N 872) 117.26028W 873) 0
874)
ine-0f-Sight
Figure 36. Radio Path Profile C Reservoir – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-38
SC07221_FINAL_Carlsbad SCADA Master Plan
Calavera Reclaim Pump Station
The link from the Calavera Reclaim Pump Station to the Maerkle Reservoir has a near line of sight
connection due to a small interference to the Fresnel zone. The predicted received signal strength o
f-65 dBm is good.
875) Desktop Radio Study 876) Subscriber Module (SM) Name 877) Band 878) Bandwidth 879) SM 880) Latitude 881) SM 882) Longitude 883) SM 884) Height (ft) 885) Range (mi.) 886) Antenna Magnetic Azimuth (deg) 887) Aggregate Throughput (Mbps) 888) Predicted Receive Power 889) Link Predicted A il bilit (%) 890) Access Point (AP) Name 891) AP 892) Latitude 893) AP 894) Longitude 895) AP Height (ft) 896) Profile Type 897) C
alavera Reclaim Pump Station
898) 00 MHz
899) 0 MHz
900) 33.15977N 901) 117.29156W 902) 2 903) .878 904) 3.6 905) 2.722
906) -65 dBm ± 8 dB
907) 00
908) Maerkle Reservoir
909) 33.15265N 910) 117.26028W 911) 0
912) earLine-0f-Sight
Figure 37. Radio Path Profile Calavera Reclaim PS – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-39
SC07221_FINAL_Carlsbad SCADA Master Plan
Cannon Lift Station
The link from the Cannon Lift Station to the Maerkle Reservoir has a clear line of site and a clear
Fresnel zone. The predicted received signal strength of -58 dBm is good.
913) Desktop Radio Study 914) Subscriber Module (SM) Name 915) Band 916) Bandwidth 917) SM 918) Latitude 919) SM 920) Longitude 921) SM 922) Height (ft) 923) Range (mi.) 924) Antenna Magnetic Azimuth (deg) 925) Aggregate Throughput (Mbps) 926) Predicted Receive Power 927) Link Predicted A il bilit (%) 928) Access Point (AP) Name 929) AP 930) Latitude 931) AP 932) Longitude 933) AP Height (ft) 934) Profile Type 935) Cannon LS
936)
00 MHz
937)
0 MHz
938) 33.14514N 939) 117.30394W 940) 3 941) .585 942) 7.1 943) 5.705
944) -
58 dBm ± 5 dB
945) 00
946) M
aerkle Reservoir
947) 33.15252N 948) 117.26022W 949) 0
950)
ine-0f-Sight
Figure 38. Radio Path Profile Cannon LS – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-40
SC07221_FINAL_Carlsbad SCADA Master Plan
CWA #3
The link from CWA #3 to the Maerkle Reservoir does not have a line of site connection due to a
severely impacted Fresnel zone. The predicted received power of -58 dBm is good.
951) Desktop Radio Study 952) Subscriber Module (SM) Name 953) Band 954) Bandwidth 955) SM 956) Latitude 957) SM 958) Longitude 959) SM 960) Height (ft) 961) Range (mi.) 962) Antenna Magnetic Azimuth (deg) 963) Aggregate Throughput (Mbps) 964) Predicted Receive Power 965) Link Predicted A il bilit (%) 966) Access Point (AP) Name 967) AP 968) Latitude 969) AP 970) Longitude 971) AP Height (ft) 972) Profile Type 973) CWA #3
974)
00 MHz
975)
0 MHz
976) 33.16181N 977) 117.25639W 978) 5 979) .67 980) 88.2 981) 6.986
982) -58 dBm ± 8 dB
983) 00
984) Maerkle Reservoir
985) 33.15265N 986) 117.26028W 987) 0
988)
on Line-0f-Sight
Figure 39. Radio Path Profile CWA #3 – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-41
SC07221_FINAL_Carlsbad SCADA Master Plan
El Fuerte Lift Station
The link from the El Fuerte Lift Station to the Maerkle Reservoir does not have line of sight. The
predicted received signal strength of -73 dBm with a tolerance of +/- 12 dB is marginal to weak.
CMWD may be an appropriate alternative master site, however the received signal strength is
equivalent to Maerkle Reservoir.
989) Desktop Radio Study 990) Subscriber Module (SM) Name 991) Band 992) Bandwidth 993) SM 994) Latitude 995) SM 996) Longitude 997) SM 998) Height (ft) 999) Range (mi.) 1000) Antenna Magnetic Azimuth (deg) 1001) Aggregate Throughput (Mbps) 1002) Predicted Receive Power 1003) Link Predicted A il bilit (%) 1004) Access Point (AP) Name 1005) AP 1006) Latitude 1007) AP 1008) Longitude 1009) AP Height (ft) 1010) Profile Type 1011) El Fuerte LS
1012
00 MHz
1013
0 MHz
1014) 33.13735N 1015) 117.25794W 101 3 1017) .054 1018) 41.3 1019) 5.677
1020) -73 dBm ± 12 dB
1021 00
1022) Maerkle Reservoir
1023) 33.15252N 1024) 117.26022W 1025 0
1026)
on Line-0f-Sight
Figure 40. Radio Path Profile El Fuerte LS – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-42
SC07221_FINAL_Carlsbad SCADA Master Plan
Faraday Reclaim Pressure Reducing Station
The link from the Faraday Reclaim PRS to the Maerkle Reservoir is near line of sight. The predicted
received power of -64 dBm is good.
1027) Desktop Radio Study 1028) Subscriber Module (SM) Name 1029) Band 1030) Bandwidth 1031) SM 1032) Latitude 1033) SM 1034) Longitude 1035) SM 1036) Height (ft) 1037) Range (mi.) 1038) Antenna Magnetic Azimuth (deg) 1039) Aggregate Throughput (Mbps) 1040) Predicted Receive Power 1041) Link Predicted A il bilit (%) 1042) Access Point (AP) Name 1043) AP 1044) Latitude 1045) AP 1046) Longitude 1047) AP Height (ft) 1048) Profile Type 1049) F
araday Reclaim PRS
1050
00 MHz
1051
0 MHz
1052) 33.13907N 1053) 117.29147W 105 5 1055) .035 1056) 1.4 1057) 4.621
1058) -64 dBm ± 7 dB
1059 00
1060) Maerkle Reservoir
1061) 33.15252N 1062) 117.26022W 1063 0
1064)
ear Line-0f-Sight
Figure 41. Radio Path Profile Faraday Reclaim PRS – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-43
SC07221_FINAL_Carlsbad SCADA Master Plan
Maerkle Control Pressure Reducing Valve
The link from the Maerkle Control PRV to the Maerkle Reservoir has line of sight. The predicated
received power of -52 dBm is good.
1065) Desktop Radio Study 1066) Subscriber Module (SM) Name 1067) Band 1068) Bandwidth 1069) SM 1070) Latitude 1071) SM 1072) Longitude 1073) SM 1074) Height (ft) 1075) Range (mi.) 1076) Antenna Magnetic Azimuth (deg) 1077) Aggregate Throughput (Mbps) 1078) Predicted Receive Power 1079) Link Predicted A il bilit (%) 1080) Access Point (AP) Name 1081) AP 1082) Latitude 1083) AP 1084) Longitude 1085) AP Height (ft) 1086) Profile Type 1087) M
aerkle Control PRV
1088
00 MHz
1089
0 MHz
1090) 33.13790N 1091) 117.27405W 109 0 1093) .283 1094) 6.9 1095) 7.344
1096) -
52 dBm ± 5 dB
1097 00
1098) M
aerkle Reservoir
1099) 33.15249N 1100) 117.26029W 1101 0
1102)
ine-0f-Sight
Figure 42. Radio Path Profile Maerkle Control PRV – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-44
SC07221_FINAL_Carlsbad SCADA Master Plan
Maerkle hydroelectric
The link from the Maerkle Hydroelectric site to the Maerkle Reservoir has line of sight. The predicted
received power of -35 dBm is excellent.
1103) Desktop Radio Study 1104) Subscriber Module (SM) Name 1105) Band 1106) Bandwidth 1107) SM 1108) Latitude 1109) SM 1110) Longitude 1111) SM 1112) Height (ft) 1113) Range (mi.) 1114) Antenna Magnetic Azimuth (deg) 1115) Aggregate Throughput (Mbps) 1116) Predicted Receive Power 1117) Link Predicted A il bilit (%) 1118) Access Point (AP) Name 1119) AP 1120) Latitude 1121) AP 1122) Longitude 1123) AP Height (ft) 1124) Profile Type 1125) M
aerkle Hydroelectric
1126
00 MHz
1127
0 MHz
1128) 33.15285N 1129) 117.26149W 113 3 1131) .074 1132) 4.8 1133) 7.344
1134) -
35 dBm ± 5 dB
1135 00
1136) M
aerkle Reservoir
1137) 33.15255N 1138) 117.26027W 1139 0
1140)
ine-0f-Sight
Figure 43. Radio Path Profile Maerkle Hydroelectric – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-45
SC07221_FINAL_Carlsbad SCADA Master Plan
Maerkle Lower Chlorine Station
The link from the Maerkle Lower Chlorine Station to the Maerkle Reservoir does not have line of
sight. The predicated received signal strength of -53 dBm with a tolerance of +/- 10 dB is good.
1141) Desktop Radio Study 1142) Subscriber Module (SM) Name 1143) Band 1144) Bandwidth 1145) SM 1146) Latitude 1147) SM 1148) Longitude 1149) SM 1150) Height (ft) 1151) Range (mi.) 1152) Antenna Magnetic Azimuth (deg) 1153) Aggregate Throughput (Mbps) 1154) Predicted Receive Power 1155) Link Predicted A il bilit (%) 1156) Access Point (AP) Name 1157) AP 1158) Latitude 1159) AP 1160) Longitude 1161) AP Height (ft) 1162) Profile Type 1163) M
aerkle Lower Chlorine Station
1164
00 MHz
1165
0 MHz
1166) 33.15038N 1167) 117.26147W 116 1 1169) .171 1170) 2.3 1171) 5.828
1172) -53 dBm ± 10 dB
1173 00
1174) Maerkle Reservoir
1175) 33.15265N 1176) 117.26028W 1177 0
1178)
on Line-0f-Sight
Figure 44. Radio Path Profile Maerkle Lower Chlorine Station – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-46
SC07221_FINAL_Carlsbad SCADA Master Plan
Maerkle Upper Chlorine Station
The link from the Maerkle Upper Chlorine Station to the Maerkle Reservoir is line of sight. The
predicted received power of -35 dBm is excellent.
1179) Desktop Radio Study 1180) Subscriber Module (SM) Name 1181) Band 1182) Bandwidth 1183) SM 1184) Latitude 1185) SM 1186) Longitude 1187) SM 1188) Height (ft) 1189) Range (mi.) 1190) Antenna Magnetic Azimuth (deg) 1191) Aggregate Throughput (Mbps) 1192) Predicted Receive Power 1193) Link Predicted A il bilit (%) 1194) Access Point (AP) Name 1195) AP 1196) Latitude 1197) AP 1198) Longitude 1199) AP Height (ft) 1200) Profile Type 1201) M
aerkle Upper Chlorine Station
1202
00 MHz
1203
0 MHz
1204) 33.15295N 1205) 117.25961W 120 1207) .047 1208) 22.7 1209) 7.344
1210) -35 dBm ± 5 dB
1211 00
1212) Maerkle Reservoir
1213) 33.15255N 1214) 117.26027W 1215 5
1216) ine-0f-Sight
Figure 45. Radio Path Profile Maerkle Upper Chlorine Station – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-47
SC07221_FINAL_Carlsbad SCADA Master Plan
Point D Pressure Reducing Valve North
The link from the Point D PRV to the Maerkle Reservoir is line of sight. The predicted received signal
strength of -54 dBm is good.
1217) Desktop Radio Study 1218) Subscriber Module (SM) Name 1219) Band 1220) Bandwidth 1221) SM 1222) Latitude 1223) SM 1224) Longitude 1225) SM 1226) Height (ft) 1227) Range (mi.) 1228) Antenna Magnetic Azimuth (deg) 1229) Aggregate Throughput (Mbps) 1230) Predicted Receive Power 1231) Link Predicted A il bilit (%) 1232) Access Point (AP) Name 1233) AP 1234) Latitude 1235) AP 1236) Longitude 1237) AP Height (ft) 1238) Profile Type 1239) P
oint D PRV North
1240
00 MHz
1241
0 MHz
1242) 33.13000N 1243) 117.26635W 124 0 1245) .589 1246) 22.7 1247) .3
1248) -
54 dBm ± 5 dB
1249 00
1250) M
aerkle Reservoir
1251) 33.15249N 1252) 117.26029W 1253 0
1254)
ine-0f-Sight
Figure 46. Radio Path Profile Point D PRV – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-48
SC07221_FINAL_Carlsbad SCADA Master Plan
Rancho Carlsbad Pressure Reducing Station
The link from the Rancho Carlsbad PRS to the Maerkle Reservoir is near line of sight due to a slight
infringement of the Fresnel zone. The predicted received power of -56 dBm is good.
1255) Desktop Radio Study 1256) Subscriber Module (SM) Name 1257) Band 1258) Bandwidth 1259) SM 1260) Latitude 1261) SM 1262) Longitude 1263) SM 1264) Height (ft) 1265) Range (mi.) 1266) Antenna Magnetic Azimuth (deg) 1267) Aggregate Throughput (Mbps) 1268) Predicted Receive Power 1269) Link Predicted A il bilit (%) 1270) Access Point (AP) Name 1271) AP 1272) Latitude 1273) AP 1274) Longitude 1275) AP Height (ft) 1276) Profile Type 1277) R
ancho Carlsbad PRS
1278
00 MHz
1279
0 MHz
1280) 33.14692N 1281) 117.28962W 128 5 1283) .743 1284) 5.8 1285) 7.343
1286) -56 dBm ± 6 dB
1287 00
1288) Maerkle Reservoir
1289) 33.15249N 1290) 117.26029W 1291 0
1292)
ear Line-0f-Sight
Figure 47. Radio Path Profile Rancho Carlsbad PRS – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-49
SC07221_FINAL_Carlsbad SCADA Master Plan
Robertson Ranch Pressure Reducing Station
The link from the Robertson Ranch pressure reducing station to the Maerkle Reservoir is near line of
sight. There is a small incursion of in to the Fresnel zone. The predicted received power of -60 dBm is
good.
1293) Desktop Radio Study 1294) Subscriber Module (SM) Name 1295) Band 1296) Bandwidth 1297) SM 1298) Latitude 1299) SM 1300) Longitude 1301) SM 1302) Height (ft) 1303) Range (mi.) 1304) Antenna Magnetic Azimuth (deg) 1305) Aggregate Throughput (Mbps) 1306) Predicted Receive Power 1307) Link Predicted A il bilit (%) 1308) Access Point (AP) Name 1309) AP 1310) Latitude 1311) AP 1312) Longitude 1313) AP Height (ft) 1314) Profile Type 1315) Robertson Ranch PRS
1316 00 MHz
1317 0 MHz
1318) 33.15592N 1319) 117.29963W 132 5 1321) .292 1322) 4.1 1323) 7.329
1324) -60 dBm ± 6 dB
1325 00
1326) Maerkle Reservoir
1327) 33.15265N 1328) 117.26028W 1329 0
1330)
ear Line-0f-Sight
Figure 48. Radio Path Profile Robertson Ranch PRS – Maerkle Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-50
SC07221_FINAL_Carlsbad SCADA Master Plan
Santa Fe 2 Reservoir Repeater
CWA #6
Communications from the CWA #6 facility are relayed thru the Santa Fe 1 Reservoir site. The link
from the CWA #6 facility to the Santa Fe 1 Reservoir is near line of sight due to a terrain incursion
into the Fresnel zone. The predicted received signal strength of -43 dBm is good.
1331) Desktop Radio Study 1332) Subscriber Module (SM) Name 1333) Band 1334) Bandwidth 1335) SM 1336) Latitude 1337) SM 1338) Longitude 1339) SM 1340) Height (ft) 1341) Range (mi.) 1342) Antenna Magnetic Azimuth (deg) 1343) Aggregate Throughput (Mbps) 1344) Predicted Receive Power 1345) Link Predicted A il bilit (%) 1346) Access Point (AP) Name 1347) AP 1348) Latitude 1349) AP 1350) Longitude 1351) AP Height (ft) 1352) Profile Type 1353) CWA #6
1354) 00 MHz
1355 0 MHz
1356) 33.13116N 1357) 117.20820W 135 0 1359) .478 1360) 04.1 1361) 7.344
1362) -43 dBm ± 5 dB
1363 00
1364) Santa Fe 1 Reservoir
1365) 33.15265N 1366) 117.21397W 1367 8
1368) ear Line-0f-Sight
Figure 49. Radio Path Profile CWA #6 to Santa Fe 1 Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-51
SC07221_FINAL_Carlsbad SCADA Master Plan
La Costa Pressure Reducing Station
The link from the La Costa pressure reducing station to the Santa Fe 2 Reservoir is near line of sight.
There is a small incursion into the Fresnel zone. The predicted received power of -54 dBm is good.
1369) Desktop Radio Study 1370) Subscriber Module (SM) Name 1371) Band 1372) Bandwidth 1373) SM 1374) Latitude 1375) SM 1376) Longitude 1377) SM 1378) Height (ft) 1379) Range (mi.) 1380) Antenna Magnetic Azimuth (deg) 1381) Aggregate Throughput (Mbps) 1382) Predicted Receive Power 1383) Link Predicted A il bilit (%) 1384) Access Point (AP) Name 1385) AP 1386) Latitude 1387) AP 1388) Longitude 1389) AP Height (ft) 1390) Profile Type 1391) La Costa PRS
1392) 00 MHz
1393
0 MHz
1394) 33.11787N 1395) 117.25006W 139 5 1397) .48 1398) 3.1 1399) 7.344
1400) -54 dBm ± 5 dB
1401 00
1402) Santa Fe 2 Reservoir
1403) 33.12358N 1404) 117.22546W 1405 0
1406)
ear Line-0f-Sight
Figure 50. Radio Path Profile La Costa PRS – Santa Fe 2 Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-52
SC07221_FINAL_Carlsbad SCADA Master Plan
Melrose Pressure Reducing Valve Potable
The link from the Melrose Pressure Reducing valve to the Santa Fe 2 Reservoir has line of sight. The
predicted received power of -48 dBm is good.
1407) Desktop Radio Study 1408) Subscriber Module (SM) Name 1409) Band 1410) Bandwidth 1411) SM 1412) Latitude 1413) SM 1414) Longitude 1415) SM 1416) Height (ft) 1417) Range (mi.) 1418) Antenna Magnetic Azimuth (deg) 1419) Aggregate Throughput (Mbps) 1420) Predicted Receive Power 1421) Link Predicted A il bilit (%) 1422) Access Point (AP) Name 1423) AP 1424) Latitude 1425) AP 1426) Longitude 1427) AP Height (ft) 1428) Profile Type 1429) M
elrose PRV Potable
1430)
00 MHz
1431
0 MHz
1432) 33.12341N 1433) 117.23869W 143 0 1435) .773 1436) 7.4 1437) 7.344
1438) -
48 dBm ± 5 dB
1439 00
1440) S
anta Fe 2 Reservoir
1441) 33.12363N 1442) 117.22537W 1443 5
1444)
ine-0f-Sight
Figure 51. Radio Path Profile Melrose PRV Potable – Santa Fe 2 Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-53
SC07221_FINAL_Carlsbad SCADA Master Plan
Poinsettia Lift Station
The link from the Poinsettia Lift Station to the Santa Fe 2 Reservoir is line of sight. The predicted
received signal strength of -56 dBm is good.
1445) Desktop Radio Study 1446) Subscriber Module (SM) Name 1447) Band 1448) Bandwidth 1449) SM 1450) Latitude 1451) SM 1452) Longitude 1453) SM 1454) Height (ft) 1455) Range (mi.) 1456) Antenna Magnetic Azimuth (deg) 1457) Aggregate Throughput (Mbps) 1458) Predicted Receive Power 1459) Link Predicted A il bilit (%) 1460) Access Point (AP) Name 1461) AP 1462) Latitude 1463) AP 1464) Longitude 1465) AP Height (ft) 1466) Profile Type 1467) P
oinsettia LS
1468)
00 MHz
1469
0 MHz
1470) 33.11552N 1471) 117.25834W 147 3 1473) .986 1474) 2.3 1475) 7.344
1476) -
56 dBm ± 5 dB
1477 00
1478) S
anta Fe 2 Reservoir
1479) 33.12358N 1480) 117.22546W 1481 0
1482)
ine-0f-Sight
Figure 52. Radio Path Profile Poinsettia LS – Santa Fe 2 Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-54
SC07221_FINAL_Carlsbad SCADA Master Plan
Santa Fe Reservoir 1
The link from the Santa Fe 1 Reservoir to Santa Fe Reservoir 2 does not have line of sight. The
predicted received power of -73 dBm with a tolerance of +/- 12 dB is marginal to poor. CMWD
currently uses Santa Fe 2 as a repeater site for Santa Fe Reservoir 1 site. No other sites were able to
repeat a signal from Santa Fe Reservoir 1.
1483) Desktop Radio Study 1484) Subscriber Module (SM) Name 1485) Band 1486) Bandwidth 1487) SM 1488) Latitude 1489) SM 1490) Longitude 1491) SM 1492) Height (ft) 1493) Range (mi.) 1494) Antenna Magnetic Azimuth (deg) 1495) Aggregate Throughput (Mbps) 1496) Predicted Receive Power 1497) Link Predicted Availability (%) 1498) Access Point (AP) Name 1499) AP 1500) Latitude 1501) AP 1502) Longitude 1503) AP Height (ft) 1504) Profile Type 1505)
anta Fe 1 Reservoir
1506) 00 MHz
1507) 0 MHz
1508) 33.13611N 1509) 117.21397W 151 8 1511) .091 1512) 06.2 1513) 5.471
1514) -73 dBm ± 12 dB
1515) 9.9999
1516)
anta Fe 2 Reservoir
1517) 33.12358N 1518) 117.22546W 1519 0
1520)
on Line-0f-Sight
Figure 53. Radio Path Profile Santa Fe 1 Reservoir – Santa Fe 2 Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-55
SC07221_FINAL_Carlsbad SCADA Master Plan
TAP Reservoir Repeater
Calavera Potable Pump Station
The link from Calavera Pump Station the to the TAP Reservoir has line of sight. The predicted
received power of -37 dBm is excellent.
1521) Desktop Radio Study 1522) Subscriber Module (SM) Name 1523) Band 1524) Bandwidth 1525) SM 1526) Latitude 1527) SM 1528) Longitude 1529) SM 1530) Height (ft) 1531) Range (mi.) 1532) Antenna Magnetic Azimuth (deg) 1533) Aggregate Throughput (Mbps) 1534) Predicted Receive Power 1535) Link Predicted A il bilit (%) 1536) Access Point (AP) Name 1537) AP 1538) Latitude 1539) AP 1540) Longitude 1541) AP Height (ft) 1542) Profile Type 1543) Calavera Potable Pump Station
1544) 00 MHz
1545 0 MHz
1546) 33.16846N 1547) 117.29522W 154 0 1549) .238 1550) 40 1551) 7.344
1552) -37 dBm ± 5 dB
1553 00
1554) TAP Reservoir
1555) 33.17188N 1556) 117.29583W 1557 2
1558) ine-0f-Sight
Figure 54. Radio Path Profile Calavera Potable PS – TAP Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-56
SC07221_FINAL_Carlsbad SCADA Master Plan
CWA #4
The link from CWA #4 the to the TAP Reservoir has line of sight. The predicted received signal
strength of -55 dBm is good.
1559) Desktop Radio Study 1560) Subscriber Module (SM) Name 1561) Band 1562) Bandwidth 1563) SM 1564) Latitude 1565) SM 1566) Longitude 1567) SM 1568) Height (ft) 1569) Range (mi.) 1570) Antenna Magnetic Azimuth (deg) 1571) Aggregate Throughput (Mbps) 1572) Predicted Receive Power 1573) Link Predicted A il bilit (%) 1574) Access Point (AP) Name 1575) AP 1576) Latitude 1577) AP 1578) Longitude 1579) AP Height (ft) 1580) Profile Type 1581) CWA #4
1582)
00 MHz
1583
0 MHz
1584) 33.16718N 1585) 117.26559W 158 5 1587) .781 1588) 69 1589) 7.344
1590) -
55 dBm ± 5 dB
1591 00
1592) T
AP Reservoir
1593) 33.17190N 1594) 117.29580W 1595 2
1596)
ine-0f-Sight
Figure 55. Radio Path Profile CWA #4 – TAP Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-57
SC07221_FINAL_Carlsbad SCADA Master Plan
Elm Tap Pressure Reducing Station
The link from the Elm Tap Pressure Reducing Station to the TAP Reservoir does not have line of sight.
The predicted received signal strength of -67 dBm with a tolerance of +/- 10 dB is good to marginal.
1597) Desktop Radio Study 1598) Subscriber Module (SM) Name 1599) Band 1600) Bandwidth 1601) SM 1602) Latitude 1603) SM 1604) Longitude 1605) SM 1606) Height (ft) 1607) Range (mi.) 1608) Antenna Magnetic Azimuth (deg) 1609) Aggregate Throughput (Mbps) 1610) Predicted Receive Power 1611) Link Predicted A il bilit (%) 1612) Access Point (AP) Name 1613) AP 1614) Latitude 1615) AP 1616) Longitude 1617) AP Height (ft) 1618) Profile Type 1619) Elm Tap PRS
1620) 00 MHz
1621
0 MHz
1622) 33.17142N 1623) 117.31574W 162 5 1625) .156 1626) 6.8 1627) 6.368
1628) -67 dBm ± 10 dB
1629 00
1630) TAP Reservoir
1631) 33.17190N 1632) 117.29580W 1633 2
1634)
on Line-0f-Sight
Figure 56. Radio Path Profile Elm Tap PRS – TAP Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-58
SC07221_FINAL_Carlsbad SCADA Master Plan
Laguna/Kelly Pressure Reducing Station
The link from the Laguna/Kelly Pressure Reducing Station to the TAP Reservoir does not have line of
sight. The predicted received power of -69 dBm with a tolerance of +/- 9 dB is good to marginal.
1635) Desktop Radio Study 1636) Subscriber Module (SM) Name 1637) Band 1638) Bandwidth 1639) SM 1640) Latitude 1641) SM 1642) Longitude 1643) SM 1644) Height (ft) 1645) Range (mi.) 1646) Antenna Magnetic Azimuth (deg) 1647) Aggregate Throughput (Mbps) 1648) Predicted Receive Power 1649) Link Predicted A il bilit (%) 1650) Access Point (AP) Name 1651) AP 1652) Latitude 1653) AP 1654) Longitude 1655) AP Height (ft) 1656) Profile Type 1657) Laguna/ Kelly PRS
1658) 00 MHz
1659
0 MHz
1660) 33.15252N 1661) 117.31043W 166 5 1663) .582 1664) 0.9 1665) 3.177
1666) -69 dBm ± 9 dB
1667 00
1668) TAP Reservoir
1669) 33.17190N 1670) 117.29580W 1671 2
1672)
on Line-0f-Sight
Figure 57. Radio Path Profile Laguna/Kelly PRS – TAP Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-59
SC07221_FINAL_Carlsbad SCADA Master Plan
Lake Calavera
The link from Lake Calavera to the TAP Reservoir does not have line of sight. The predicted received
power is marginal to poor. On the current system, Lake Calavera communicates to D Site. This may
be an appropriate alternative if the physical radio study confirms the signal is poor. However, the
radio study indicates this model is provides the best predicted received power.
1673) Desktop Radio Study 1674) Subscriber Module (SM) Name 1675) Band 1676) Bandwidth 1677) SM 1678) Latitude 1679) SM 1680) Longitude 1681) SM 1682) Height (ft) 1683) Range (mi.) 1684) Antenna Magnetic Azimuth (deg) 1685) Aggregate Throughput (Mbps) 1686) Predicted Receive Power 1687) Link Predicted Availability (%) 1688) Access Point (AP) Name 1689) AP 1690) Latitude 1691) AP 1692) Longitude 1693) AP Height (ft) 1694) Profile Type 1695) ake Calavera
1696) 00 MHz
1697) 0 MHz
1698) 33.16969N 1699) 117.28738W 170 6 1701) .511 1702) 75.8 1703) 5.718
1704) -71 dBm ± 13 dB
1705) 9.9999
1706)
AP Reservoir
1707) 33.17190N 1708) 117.29580W 1709 2
1710)
on Line-0f-Sight
Figure 58. Radio Path Profile Lake Calavera – TAP Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-60
SC07221_FINAL_Carlsbad SCADA Master Plan
TAP 4 Station
The link from TAP Station 4 to the TAP Reservoir has line of sight. The predicted received power of -
54 dBm is good.
1711) Desktop Radio Study 1712) Subscriber Module (SM) Name 1713) Band 1714) Bandwidth 1715) SM 1716) Latitude 1717) SM 1718) Longitude 1719) SM 1720) Height (ft) 1721) Range (mi.) 1722) Antenna Magnetic Azimuth (deg) 1723) Aggregate Throughput (Mbps) 1724) Predicted Receive Power 1725) Link Predicted A il bilit (%) 1726) Access Point (AP) Name 1727) AP 1728) Latitude 1729) AP 1730) Longitude 1731) AP Height (ft) 1732) Profile Type 1733) T
AP 4 Station
1734)
00 MHz
1735
0 MHz
1736) 33.16730N 1737) 117.26677W 173 5 1739) .707 1740) 68.8 1741) 7.344
1742) -
54 dBm ± 5 dB
1743 00
1744) T
AP Reservoir
1745) 33.17173N 1746) 117.29575W 1747 5
1748)
ine-0f-Sight
Figure 59. Radio Path Profile TAP 4 Station – TAP Reservoir
City of Carlsbad / CMWD SCADA Master Plan Appendix Q
Q-61
SC07221_FINAL_Carlsbad SCADA Master Plan
Villas Lift Station
The link from the Villas Lift Station to the TAP Reservoir does not have line of sight. The predicted
received signal power of -64 dBm with a tolerance of +/- 11 dB is good to marginal.
1749) Desktop Radio Study 1750) Subscriber Module (SM) Name 1751) Band 1752) Bandwidth 1753) SM 1754) Latitude 1755) SM 1756) Longitude 1757) SM 1758) Height (ft) 1759) Range (mi.) 1760) Antenna Magnetic Azimuth (deg) 1761) Aggregate Throughput (Mbps) 1762) Predicted Receive Power 1763) Link Predicted A il bilit (%) 1764) Access Point (AP) Name 1765) AP 1766) Latitude 1767) AP 1768) Longitude 1769) AP Height (ft) 1770) Profile Type 1771) Villas LS
1772) 00 MHz
1773
0 MHz
1774) 33.16868N 1775) 117.30372W 177 3 1777) .507 1778) 4 1779) 9.636
1780) -64 dBm ± 11 dB
1781 00
1782) TAP Reservoir
1783) 33.17173N 1784) 117.29575W 1785 5
1786)
on Line-0f-Sight
Figure 60. Radio Path Profile Villas LS – TAP Reservoir
San Diego Office
450 B Street, Suite 1500
San Diego, CA 92101
T 858.514.8822