HomeMy WebLinkAboutRESPONSE - RFP - 8348 TRANSFORT NETWORK MONITORING TOOLTransFort Network Monitoring Tool Proposal
WM Proposal: #8116086
Prepared for:
Financial Services – Purchasing Division
215 N. Mason St. 2nd Floor
PO Box 580
Fort Collins, CO 80522
August 05, 2016
TransFort Network Monitoring Tool Proposal
Table of Contents
1 INTRODUCTION .................................................................................................................................................... 3
1.1 DBE GOAL ............................................................................................................................................................. 3
1.2 BASIS OF PROPOSAL.................................................................................................................................................. 3
1.2.1 General ........................................................................................................................................................... 3
1.2.2 User Interface ................................................................................................................................................. 4
1.2.3 Reporting ........................................................................................................................................................ 4
1.2.4 Dashboards ..................................................................................................................................................... 5
1.2.5 Notification ..................................................................................................................................................... 5
1.2.6 Kepware OPC Server ....................................................................................................................................... 5
1.2.7 Client Browsing ............................................................................................................................................... 5
2 SCOPE OF SERVICES .............................................................................................................................................. 6
2.1 TNMT DESIGN ........................................................................................................................................................ 6
2.1.1 Architecture Drawing: ..................................................................................................................................... 6
2.1.2 Architecture: ................................................................................................................................................... 6
2.1.3 Reporting ........................................................................................................................................................ 7
2.1.4 Maintenance ................................................................................................................................................. 10
3 SCHEDULE ........................................................................................................................................................... 11
4 PROJECT TEAM ................................................................................................................................................... 11
4.1 ASSIGNED RESOURCES ............................................................................................................................................ 11
4.2 ORGANIZATION CHART ............................................................................................................................................ 13
5 QUALIFICATIONS ................................................................................................................................................ 13
5.1 AUTOMATION EXPERIENCE ....................................................................................................................................... 13
5.2 ICONICS SYSTEM INTEGRATOR PARTNERS (SIP) ......................................................................................................... 14
6 PROJECT MANAGEMENT .................................................................................................................................... 14
6.1 RESPONSIBILITIES ................................................................................................................................................... 14
6.1.1 WM Project Manager ................................................................................................................................... 14
6.2 COST TRACKING AND CONTROLS ............................................................................................................................... 15
7 SCOPE ................................................................................................................................................................. 15
7.1 SOFTWARE DESIGN & DEVELOPMENT ........................................................................................................................ 15
7.1.1 Design Activities ............................................................................................................................................ 15
7.1.2 SCADA Programming Activities: .................................................................................................................... 15
8 PRICING SUMMARY ............................................................................................................................................ 16
8.1 COST SUMMARY .................................................................................................................................................... 16
8.1.1 Engineering ................................................................................................................................................... 16
8.1.1 Software ........................................................................................................................................................ 17
8.2 INVOICE SCHEDULE ................................................................................................................................................. 17
8.3 TIME & EXPENSE FIELD SERVICES .............................................................................................................................. 17
9 CLARIFICATIONS ................................................................................................................................................. 18
10 EXCLUSIONS ....................................................................................................................................................... 18
TransFort Network Monitoring Tool Proposal
1 Introduction
Wunderlich-Malec (WM) is pleased to provide this proposal for the design and implementation of a
TransFort Network Monitoring Tool (TNMT) to be utilized by TransFort (The transit service for the City of
Fort Collins) in Fort Collins, CO.
The City of Fort Collins (City) is requesting proposals from qualified firms to design, with option to
implement, a network monitoring tool built from an existing platform already in use by TransFort. The
existing platform is the ICONICS Genesis64 system. The firm will recommend a design utilizing this
system and detail how it will monitor the network’s status and translate that status-data into the
ICONICS GUI component GraphWorX.
TransFort seeks solutions for a tool to monitor all transit related network systems for the purpose of “at-
a-glance” awareness and proactive maintenance. The GUI will display a map-like overlay indicating the
location of a given device, its type, and the network status. The desired network status indicator is color
coded; for example, red would mean there is no network connectivity, green would indicate consistent
and steady communication, and yellow might signify a potential problem such as latency or
interruptions to the communication. The following conditions will apply:
1. The interface will monitor a flood ping, or utilize a similar method, to capture network connectivity
from all devices. The current topology functions using LAN, WiFi, and Cellular solutions.
2. The given thresholds for connectivity or network latency need to be modifiable at any given time,
for any length of time.
3. The GUI must be searchable by network condition (color), region, location, TAG, IP Address, and
device type.
4. The designed system must produce email and/or text alerts for devices that are losing network
connectivity, or have lost network connectivity, to an unlimited number of users, customizable by
TransFort to add and remove users frequently and at will.
1.1 DBE Goal
This is a federally funded project and the DBE goal is 5%.
Neither WM or RSI Company is not CDOT certified as DBE, therefore WM took the steps
necessary to achieve the DBE goal which by their scope, intensity, and appropriateness to the
objective, could reasonably be expected to obtain sufficient DBE participation, even if the goal is
not met.
Since WM does not meet the project DBE goal, we have include a memo (attached) detailing our
good faith effort in achieving the DBE goal.
1.2 Basis of Proposal
The basis of this proposal is the RFP 8348 TRANSFORT NETWORK MONITORING TOOL provided
by the City of Fort Collins on 07/08/2016 on the Rocky Mountain E-Purchasing System. The
primary project requirements are as follows:
1.2.1 General
a) The GUI must be built upon an existing ICONCIS Genesis 64 platform
b) The Reporting functionality must be built upon an existing SQL Server 2008 R2
database
TransFort Network Monitoring Tool Proposal
c) If possible, utilize the existing Crystal Reports 2008 site licensing in lieu of third party
report licensing
d) Utilize ODBC for the interface for accessing the TNMT data stored in the SQL Server.
e) Provide project management, customer communication, project status reports on a
regular basis to ensure project success.
f) The Professional shall provide network access to the raw database as well as
standard reports for staff assigned to work with the data from the TNMT. The
database requires access using standard ODBC protocols. TransFort currently utilizes
Microsoft SQL 2008 R2 as its enterprise database. Data Storage shall make use of
the existing TransFort hardware and software as much as possible.
1.2.2 User Interface
a) The GUI will display a map-like overlay indicating the location of a given device, its
type, and the network status.
b) The desired network status indicator is color coded; for example, red would mean
there is no network connectivity, green would indicate consistent and steady
communication, and yellow might signify a potential problem such as latency or
interruptions to the communication
c) The GUI must be searchable by network condition (color), region, location, TAG, IP
Address, and device type
1.2.3 Reporting
a) The TNMT must be capable of storing event data for each day of each year and
grouped by various categories including:
o Tag
o Location
o Device Type
o Connectivity
o Date & Time
b) The reporting function should provide a fully integrated solution supporting ad-hoc
and standard reports based on data generated by user entry and data import.
c) The reporting feature should include a power-user query writing function that
allows data analysts to write more complex and graphically designed reports. All
tables and columns must be available to select power-users with no restrictions on
joins. ANSI-92 JOIN syntax is preferable through the reporting tool; however, ANSI-
89 and other JOIN syntax standards will be considered. Query writing tools with the
ability to write complex joins on multiple join filters with a preference allowing for
table aliasing.
d) In addition to a built-in query writing function, the network monitoring tool must
allow system administrators to access all columns and tables through ODBC via the
central relational database management system for the purpose of writing data
integrity reports, creating data exports to a disparate data warehouse and other
data analyst tasks.
e) The report function must provide security controls to manage user access to reports
and dashboards based on security group level.
TransFort Network Monitoring Tool Proposal
f) The report writing portion should allow reports to be designed for viewing in
graphical, tabular or a combination of both formats.
g) The report writing component should allow users to clone and modify reports based
on standard canned reports.
h) The report writing feature should allow reports to be published using standard
scheduling recurrence logic (nth day, week template, nth month, monthly, weekly,
daily, day of week etc.). Logic should permit event based scheduling which allows
for triggering of reports due to absence or presence of data (Late PM for example).
Reports should be deliverable in multiple formats such as PDF, XLSX, DOC, CSV and
other formats.
i) Standard reports should be available in a commercial “off the shelf” format, based
on transit industry standards, FTA and NTD requirements.
j) The reporting element should contain a dashboard interface that allows users to
configure charts, gauges and other widgets. Dashboards should be based on real-
time information (where available). Refresh rate for dashboards which use imported
data from existing disparate data sources will be assessed and determined during
operational and design review during project implementation.
1.2.4 Dashboards
a) The reporting feature should provide a library of standard dashboard measurements
with definitions of key performance indicators. Definitions should include
methodology of measurements, such as connectivity, ping rate and latency.
b) The report writing component should allow users to clone and modify dashboards
based on standard dashboards.
c) The report writing function should provide a library of standard gauges, graphs,
charts and widgets that can be edited by users.
d) The report writing portion should allow dashboards to be configured by users to
control maximum and minimum limits on gauges. Users should have the ability to
set alerts which change the appearance of gauges when a user-defined threshold
has been exceeded.
1.2.5 Notification
a) The reporting element should allow for notifications, either through the report
writing tool or a dedicated notifications module within the application in order to
send alerts and notifications to users based on events within the application.
1.2.6 Kepware OPC Server
a) Install Kepware SNMP OPC Server on one server machine
b) Configure the “Ping” portion of the SNMP OPC Server option for Genesis64.
1.2.7 Client Browsing
a) Configure Genesis64 to allow WebHMI connectivity within the Fort Collins district.
TransFort Network Monitoring Tool Proposal
2 Scope of Services
2.1 TNMT Design
2.1.1 Architecture Drawing:
Windows Server 2008 R2 (existing)
TRANSFORT Network
DMZ
City Network
ICONICS GENESIS64 v10.92
ICONICS Hyper
Historian Express
ICONICS
AlarmWorX64
Kepware KepServerEX
With Ping Driver
Remote
Devices Remote
Devices Remote
Devices Remote
Devices
Data Data
MobileHMI
Anyglass Users
HTML5
City SQL Server
Data
City outgoing email
SMTP Server
Windows Server 2008 or newer (new)
ICONICS
AlarmWorX64-MMX RSI Datalink Software ICONICS MobileHMI
Reports
2.1.2 Architecture:
The above drawing is our recommended architecture for the system. Note that there
are many ways to architect this system and the City’s network structure can affect the
architecture dramatically. We think this is the most reliable and secure option.
RSI Company does not provide network design or configuration services. We would rely
on the City’s resources to provide the networking configuration.
We are suggesting that a DMZ (De-Militarized Zone) be placed between the Transfort
network SCADA system and the City’s business network, but as mentioned, this is not a
requirement. If the existing SCADA PC has access to the city’s network email server and
SQL Server, the software currently shown in the DMZ could reside on the existing SCADA
Server.
GENESIS64 (existing software):
The GENESIS64 software is existing, but RSI Company is recommending that the
software be upgraded to v10.92. The upgrade will provide the ICONICS Hyper Historian
Express software for historical trending of the remote device data. Also part of
GENESIS64 is the AlarmWorX64 software that will provide alarming information and
storage.
TransFort Network Monitoring Tool Proposal
Hyper Historian Express is a data historian that will store each devices online status and
ping time at a rate determined by the City.
AlarmWorX64 will provide the alarming functions to generate alarms when a device’s
ping time is out of specification or offline.
This upgrade to v10.92 also includes a major update to ICONICS AssetWorX software.
We intend to use AssetWorX in the design of this system to provide system organization
and to store device metadata such as device name, type, location, etc…
KepWare KepServerEx (new software):
This software (with the ping driver option) will use ICMP to ping the remote devices. It
returns 2 tags per device: Status (online/offline) and Ping Time (in mS). The
KepServerEx will provide this information to GENESIS via the OPC UA protocol.
ICONICS AlarmWorX-MMX (new software): The AlarmWorX-MMX software will provide
remote notification of alarms via email. This software must have access to both ICONICS
AlarmWorX64 software as well as the City’s SMTP Server, which is uses to send emails.
ICONICS MobileHMI (new software):
MobileHMI is an add-on product to GENESIS64. The purpose of this software is to
provide the SCADA Screens (map overlay) to users. MobileHMI uses HTML5 as the
technology for the screens. This gives lots of flexibility to support many devices
including smart phones, tablets, and PCs.
RSI Datalink (new software):
The RSI Datalink software is developed and supported by RSI Company specifically to
transfer Hyper Historian and AlarmWorX data to a company SQL Server. Its job will be
to periodically grab historical data from Hyper Historian Express and AlarmWorX and
transfer this data to a SQL Server on the City’s network. It was designed by RSI
Company to specifically provide this function, and is currently being used by several
Colorado companies.
Hardware:
The existing Windows Server 2008 R2 server can be used as is. We don’t see a need to
upgrade the system hardware at this time.
We do suggest that the City install a new server to house AlarmWorX-MMX, MobileHMI
and RSIDatalink. This new server should sit in the DMZ portion of the network to
provide connectivity and server as a mediator for data exchange between the SCADA
system and the City’s business network.
As mentioned above, this server is optional. If the City can provide all the connectivity
needed using a single existing server and is comfortable with the security configuration,
all of the software can be housed on a single server.
2.1.3 Reporting
As mentioned, the RSI Datalink software will extract the historical data and alarms from
GENESIS64. This data will be placed in a SQL Server on the City’s network. From that
TransFort Network Monitoring Tool Proposal
SQL Server, any reporting package (such as Crystal Reports) can be used to create
reports.
The following information will be collected and transferred to the SQL Database for each
device.
Device Type
Location
Ping Time (mS)
Status (online / offline)
Date / Time of device dropping offline
Date / Time of device returning online
Date / Time of device in a warning (large ping time) condition
Date / Time of device returning to normal condition
Once in SQL, the reporting package will be used to create reports viewable by City
employee’s. RSI Company has not used Crystal Reports for many years, however given
that the City already has a license, we will work with the city to create the needed
reports using Crystal Reports.
Below are some example reports that we see may be needed. These are not actual
reports and are intended only as examples.
Ping Data Report, provides summarized ping data for a specific device for the period
specified:
TransFort Network Monitoring Tool Proposal
Device Offline Report, provides all offline devices for the period specified:
TransFort Network Monitoring Tool Proposal
Alarm Summary Report, provides all alarms for devices during the period specified:
2.1.4 Maintenance
SCADA systems are inherently designed to operate for many years with very little
maintenance. We recommend that the City evaluates the system on a yearly basis.
The Server hardware usually determines when it is time for upgrading. When the
hardware is no longer under warrantee, it’s time to upgrade the system.
Operating system updates should be performed as needed based on the City’s IT
department standards.
TransFort Network Monitoring Tool Proposal
The SCADA software itself should only be updated / patched when needed for
functionality, security, or bug fix – don’t fix it if it isn’t broke!
3 Schedule
We propose the following schedule with key milestone dates. The proposed targets are flexible and can
be adjusted based on Fort Collins feedback.
Milestone Proposed Target
Receipt of Order September 2016
Order Software September 2016
Design Activities Complete November 2016
Implementation Complete – Genesis64 fully functional December 2016
We may be able to improve upon the above schedule if necessary. WM has a large talent pool of
experienced automation engineers trained and certified with ICONICS Genesis64, SQL Server, and
reporting systems. These resources could be added to the project team to assist with software
development and project execution.
4 Project Team
The assigned resource team will work together for the duration of the project and include four
automation engineers from our Golden, CO. The team members and their strengths are listed below:
4.1 Assigned Resources
Russ Ropken – Lead Systems Consultant: Russ is RSI Company’s project manager and lead
control systems consultant. Russ has been in the automation industry for 24+ years, and is RSI
Company’s founder and Vice President. Russ has served as RSI Company’s lead consultant and
project manager since 2002. Russ is responsible for reviewing design specifications, quality
assurance, and automation design. He has experience with a wide variety of SCADA, PLC, and
HMI applications. Russ also has extensive experience the database and Windows .NET
programming.
Project Responsibilities:
• Design Review
• Report System Design
• Alarm Notification Design
• GENSIS64 Design
• MobileHMI Design
• SQL / Data transfer Design
• Web Design
TransFort Network Monitoring Tool Proposal
Mike Norman (Golden, CO): – WM Project Manager and Quality Assurance
Mike has over 28 years’ experience in controls and project management. Mike has worked in
the system integration area for the past 18 years.
Project responsibilities shall include:
• Project Management
• Quality Assurance
• Maintaining Customer Relationship
• Application Design Standards
• Graphics review
• Application configuration review
Rob Reitz (Golden, CO) – WM Lead Applications/Consulting Engineer
Rob has been involved in a wide variety of controls systems and SCADA systems for over 30
years. He served as the lead automation engineer overseeing all water, waste water, and
distribution and collection for the City of Longmont for the past 5 years. His focus has been in
the design, implementation, and management of process control and automation projects. Rob
has spent the past 5 years working exclusively with ICONICS HMI/SCADA system as well as
custom reporting using SQL server. He has extensive process experience in several areas related
to automation services including: Field verification / reverse engineering existing design,
network design, HMI programming, testing, installation verification and commissioning.
Project responsibilities shall include:
• Design Review Participation
• ICONICS Software Configuration and Programming Review
• Design Oversight
• Consulting Support
Matias Rocha (Golden, CO) – WM Applications Engineers
Matias currently work as a Controls Engineers and has been focused on various automation
projects for the past 5 years. During this time, they have designed and implemented several
automation solutions utilizing ICONICS Genesis64, SQL Server, and Ethernet Networks. As such
Matias is well versed with the project life cycle expectations from design through testing. In
addition, Matias has significant expertise with the ICONICS and SQL platforms as well as a wide
variety of networking protocols.
Project responsibilities shall include:
• Management of project technical aspects
• Software Design and Configuration
• Development of Application Standard
• Vendor Technical Support Communication
• Implementation
• Testing
TransFort Network Monitoring Tool Proposal
4.2 Organization Chart
Below is our proposed organizational configuration for this project. Resumes are available upon
request.
TransFort Network Monitoring Tool Project Team
TBD
Ft Collins - TransFort
Project Manager
Mike Norman
WM
(Project Manager, QA)
Russ Ropken
RSI Company
(Lead Consultant)
Matias Rocha
WM
(Application
Engineer)
Rob Reitz
WM
(Lead Application
Engineer)
5 Qualifications
5.1 Automation Experience
WM is providing the following capabilities for the design, supply, installation and integration of
process control systems for building management systems:
• Automation/Engineering support contracts
• Process control design, development, integration, installation, and commissioning
• Project coordination services for electrical, instrumentation, and controls effort
• Hardware controller programming
• SCADA programming
• Calibration Services
• Control panel design, procurement, assembly, testing, and installation
• Feasibility studies & automation plans
• Information Systems Development
• Legacy System Migration
• Instrumentation Commissioning
• Production Data Collection
• Data Acquisition Systems
• LAN/WAN Connectivity
TransFort Network Monitoring Tool Proposal
5.2 ICONICS System Integrator Partners (SIP)
Since 2004, WM has been a member of the ICONICS’ Systems Integrator Partner (SIP) program.
Our current SIP membership status is “Gold Certified”, ICONICS’ highest level of certification. SIP
Certification programs provide systems integrators with credentials to identify their company’s
proficiency with ICONICS products. These designations allow ICONICS customers and distributors
to locate systems integrators with proven ability to develop ICONICS solutions for their
applications and efficiently deploy projects. SIP membership is offered as an annual subscription
through local sales channels, and directly with ICONICS in circumstances where there is no
suitable ICONICS Channel in the local area. WM obtains their annual SIP membership through
Process Control Dynamics, Inc (PCD). SIP Certification also provides WM access to ICONICS
Technical Support as well as ICONICS provided training seats.
6 Project Management
6.1 Responsibilities
We are committed to managing this project effectively and will use all necessary tools to ensure
the project’s success. We anticipate providing one Project Manager Resource.
6.1.1 WM Project Manager
The WM Project Manager will have the following responsibilities:
• Works closely with the Fort Collins Owner’s Representative to manage scope,
schedule, and budget
• Ensures expectations are met for schedule, deliverables, and budget
• Single point of contact for project communication with WM staff
• Assigns tasks to WM team members
• Defines all objectives for WM team
• Identifies resource requirements
• Assigns responsibility to WM team
• Sequences deliverables
• Schedules resources
• Manages change
TransFort Network Monitoring Tool Proposal
• Monitors and protects the plan
• Participates in weekly meetings
• Cost Management
• Schedule Management
6.2 Cost Tracking and Controls
The proposed schedule defines all project deliverables, activities, responsibilities, and invoice
milestones. Upon being awarded the project, WM will work with Fort Collins to modify the
schedule if required. Schedule progress will be continuously tracked and reviewed with Fort
Collins on a bi-weekly basis throughout the project. WM will also provide a monthly status
report detailing project status, issues, and financials.
Although we’re proposing to implement the BMS Upgrade project on a “Fixed Price” basis, it is
worth mentioning that WM has implemented a central accounting system to assure that
accurate cost data is available on all of our projects.
WM’s central accounting system (servers located at corporate office) is used for all project
related accounting. This system is accessible from all of our office locations. Labor costs are
updated on a weekly basis and expense costs are updated on a bi-weekly basis. Detailed reports
can be generated for project management personnel.
7 Scope
7.1 Software Design & Development
The existing BMS application will be analyzed and modified with the current ICONICS Genesis32
software to ensure proper functionality. After proper functionality is demonstrated, WM will
upgrade the BMS to ICONICS Genesis64.
7.1.1 Design Activities
The existing ICONICS application will be evaluated to determine the proper integration
approach for this project.
The design activities are as follows:
• Reverse engineer existing application to determine appropriate direction for TNMT
integration
• Identify all appropriate device names and IP addresses
• Identify direction for AssetWorX and GridWorX integration
• Further analyze report requirements to refine design
• Evaluate existing graphics to determine plan for TNMT GUI
• Develop common templates to be used for all field devices
• Conduct four design reviews with Fort Collins
7.1.2 SCADA Programming Activities:
The SCADA programming activities are as follows:
• Configure ICONICS AssetWorX
• Configure ICONICS Hyper Historian for Report Structure
• Install and configure Kepware SNMP OPC software
TransFort Network Monitoring Tool Proposal
• Implement WebHMI functionality for client browsers within the Fort Collins network
8 Pricing Summary
8.1 Cost Summary
Based on the proposed schedule and the associated resources required, the “fixed price” for this
project is $71,440. Summarized pricing details are detailed below:
8.1.1 Engineering
Task Total Cost
Engineering
On Site Visit & Project Kickoff Meeting $3,714.00
Project Management $2,480.00
Quality Assurance, Quality Control $2,480.00
Design & Development $42,242.00
Option
Implementation $12,857.00
Other
Documentation: O&M Manual $3,680.00
Onsite Testing $1,380.00
Onsite Training $460.00
Expenses - Mileage $660.00
Total Cost $69,953.00
TransFort Network Monitoring Tool Proposal
8.1.1 Software
Task Total Cost
Kepware KepServerEX: SNMP Server Suite $1,259.25
Kepware 1 Year Support and Maintenance Agreement $228.85
Total Cost $1,488.10
8.2 Invoice Schedule
Our proposed invoicing schedule will be as follows:
Invoice Cost
4 Equal Monthly Payments $17,860
8.3 Time & Expense Field Services
The proposed fixed price engineering effort includes all necessary field services for local
resources based out of our Longmont, CO office to execute the defined project scope. As such
we currently do not anticipate any T&E field services. The following table provides hourly field
service rates which would be applicable in case future T&E field services are needed:
Resource Rate
Russ Ropken $195
Mike Norman $155
Rob Reitz $145
Matias Rocha $125
Julianne Fantich $105
TransFort Network Monitoring Tool Proposal
9 Clarifications
1. The City will provide and maintain its own hardware. This project integrates existing data sources,
which the City is responsible for providing, and the Professional will provide the importing of said
data into the designed GUI.
2. WM/RSI will investigate during the design phase of the project if additional products may be
required. Due to SAP ownership of Crystal Solutions, it is difficult to investigate product capabilities
at this time.
3. The scope above is based on the assumption that 3 reports will be provided which are detailed
above in the Scope of Services section of this proposal.
4. The City will provide all necessary device naming and IP address detail in Excel format.
5. The City will provide a technician to assist WM with system checkout and testing (technician will be
located at the field device end and available via phone)
10 Exclusions
1. Any applicable sales or use tax.
2. All hardware
3. All operating systems software
4. Any after hours, weekend, or holiday support
5. Installation services related hardware mounting, conduit run, cable routing, wire termination, new
fiber, etc.