SCHEDULE C – FORM OF PROPOSAL
RFP Project Title:
Transportation Operations Centre ATMS Implementation
RFP Reference No.:
1220-030-2013-011
Name of Proponent:
Contact Person and Title:
Business Address:
Telephone:
Fax:
E-Mail Address:
TO:
City Representative:
Kam Grewal, CMA, BBA, Corporate Audit Manager,
Acting Purchasing and Accounts Payable Manager
Address:
City of Surrey, City Operations Works Yard
Purchasing Section, 1st Floor
6645-148 Street, Surrey, BC Canada V3S 3C7
Telephone:
604-590-7274
Dear Sir:
1.0
I/We, the undersigned duly authorized representative of the Proponent, having received and carefully
reviewed all of the Proposal documents, including the RFP and any issued addenda posted on the City
Website and BC Bid Website, and having full knowledge of the Site, and having fully informed ourselves as
to the intent, difficulties, facilities and local conditions attendant to performing the Services, submit this
Proposal in response to the RFP.
2.0
I/We confirm that the following schedules are attached to and form a part of this Proposal:
Schedule C-1 – Statement of Departures;
Schedule C-2 – Proponent’s Experience, Reputation and Resources;
Schedule C-3 – Proponent’s Technical Proposal (Services);
Schedule C-4 – Proponent's Technical Proposal (Schedule); and
Schedule C-5 – Proponent’s Financial Proposal.
3.0
I/We confirm that this proposal is accurate and true to best of my/our knowledge.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 52 of 72
4.0
I/We confirm that, if I/we am/are awarded the agreement, I/we will at all times be the “prime contractor” as
provided by the Worker's Compensation Act (British Columbia) with respect to the Services. I/we further
confirm that if I/we become aware that another contractor at the place(s) of the Services has been
designated as the “prime contractor”, I/we will notify the City immediately, and I/we will indemnify and hold
the City harmless against any claims, demands, losses, damages, costs, liabilities or expenses suffered by
the City in connection with any failure to so notify the City.
This Proposal is submitted this _____________________ day of _________________________, 20__.
I/We have the authority to bind the Proponent.
_______________________________________
_______________________________________
(Name of Proponent)
(Name of Proponent)
_______________________________________
_______________________________________
(Signature of Authorized Signatory)
(Signature of Authorized Signatory)
_______________________________________
_______________________________________
(Print Name and Position of Authorized
(Print Name and Position of Authorized
Signatory)
Signatory)
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 53 of 72
SCHEDULE C-1 - STATEMENT OF DEPARTURES
1.
I/We have reviewed the proposed Contract attached to the RFP as Schedule “B”. If requested by the City,
I/we would be prepared to enter into that Contract, amended by the following departures (list, if any):
Section
2.
Requested Departure(s) / Alternative(s)
The City of Surrey requires that the successful Proponent have the following in place before commencing
the Services:
a)
Workers’ Compensation Board coverage in good standing and further, if an “Owner Operator” is
involved, personal operator protection (P.O.P.) will be provided,
b)
Workers' Compensation Registration Number _________________________________________;
Prime Contractor qualified coordinator is Name: __________________ and Contact Number:
______________;
c)
Insurance coverage for the amounts required in the proposed Contract as a minimum, naming the
City as additional insured and generally in compliance with the City’s sample insurance certificate
form available on the City’s Website Standard Certificate of Insurance;
d)
City of Surrey business license;
e)
If the Proponent's Goods and Services are subject to HST, the Proponent's HST Number is
____________________________________; and
f)
If the Proponent is a company, the company name indicated above is registered with the Registrar
of Companies in the Province of British Columbia, Canada, Incorporation Number
__________________________________.
As of the date of this Proposal, we advise that we have the ability to meet all of the above requirements
except as follows (list, if any):
Section
3.
Requested Departure(s) / Alternative(s)
I/We offer the following alternates to improve the Services described in the RFP (list, if any):
Section
Requested Departure(s) / Alternative(s)
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 54 of 72
4.
The Proponent acknowledges that the departures it has requested in Sections 1, 2 and 3 of this Schedule
C-1 will not form part of the Contract unless and until the City agrees to them in writing by initialling or
otherwise specifically consenting in writing to be bound by any of them.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 55 of 72
SCHEDULE C-2 - PROPONENT’S EXPERIENCE, REPUTATION AND RESOURCES
Proponents should provide information on the following (use the spaces provided and/or attach additional
pages, if necessary):
(i)
Location of branches, background, stability, structure of the Proponent;
(ii)
Proponent’s relevant experience and qualifications in delivering Services similar to those required
by the RFP;
(iii)
Proponent’s demonstrated ability to provide the Services;
(iv)
Proponent’s equipment servicing resources, capability and capacity, as relevant;
(v)
Proponent’s references (name and telephone number). The City's preference is to have a
minimum of three references;
(vi)
Proponent’s financial strength (with evidence such as financial statements, bank references);
(vii)
Proponents should provide information on the background and experience of all key personnel
proposed to undertake the Services (use the spaces provided and/or attach additional pages, if
necessary):
Key Personnel
Name:
Experience:
Dates:
Project Name:
Responsibility:
_______________________________________________________________________
Dates:
Project Name:
Responsibility:
_______________________________________________________________________
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 56 of 72
Dates:
Project Name:
Responsibility:
_______________________________________________________________________
(viii)
Proponents should provide the following information on the background and experience of all subcontractors proposed to undertake a portion of the Services (use the spaces provided and/or attach
additional pages, if necessary):
DESCRIPTION OF SERVICES
SUB-CONTRACTORS NAME
YEARS OF
TELEPHONE NUMBER
WORKING
AND EMAIL
WITH
CONTRACTOR
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 57 of 72
SCHEDULE C-3 - PROPONENT’S TECHNICAL PROPOSAL (SERVICES)
Proponents should provide the following (use the spaces provided and/or attach additional pages, if
necessary):
(i)
a narrative that illustrates an understanding of the City’s requirements and Services;
(ii)
a description of the general approach and methodology that the Proponent would take in
performing the Services including specifications and requirements;
(iii)
a narrative that illustrates how the Proponent will complete the scope of Services, manage the
Services, and accomplish required objectives within the City’s schedule;
(iv)
a description of the standards to be met by the Proponent in providing the Services;
(v)
describe the process you will follow to accomplish our requirements; and
(vi)
advise what your expectations are for City resources involvement in this process in terms of time
involved.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 58 of 72
Appendix 1: ATMS Requirements Matrix
Functional
Area
General
Req#
REQ1.1
REQ1.2
REQ1.3
REQ1.4
REQ1.5
REQ1.6
REQ1.7
Requirement
Compliance
(FC/PC/NC)
Notes/Explanations for
PC/Clarifications
The ATMS servers shall be
capable of running in hot
standby backup mode.
Upon failure of the primary
server, the backup server
shall automatically and
instantaneously take over
control of the system.
The ATMS shall be capable
of running in a VMWare
virtualized server
environment.
The ATMS client shall be
capable of operating on
Windows 7 x64 and in the
latest versions of Internet
Explorer, Chrome, and
Firefox.
The ATMS server shall be
capable of operating on
Windows Server 2008.
The ATMS shall include an
application manager that
monitors the status of all
application components,
logs events both locally and
to the Windows system log,
and allows components to
be automatically restarted
based on configurable
parameters.
The ATMS shall include an
update manager that is
capable of generating
update tasks and
automatically broadcasting
ATMS updates to servers
and clients.
The ATMS shall offer a
software development kit
to allow integration with
other control systems.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 59 of 72
Functional
Area
GUI
Req#
REQ2.1
REQ2.2
REQ2.3
REQ2.4
REQ2.5
REQ2.6
REQ2.7
Requirement
Compliance
(FC/PC/NC)
Notes/Explanations for
PC/Clarifications
The ATMS shall support the
presentation of system
information on the ESRI
Geographic Information
System (GIS) map based
Graphical User Interface
(GUI), including Google
Maps and Bing Maps.
The ATMS shall support
icon clustering on the map.
As zoom levels change,
icons shall be logically
grouped together to limit
the visual clutter.
Maps shall be able to be
customized by placing
device icons and alarm
icons on them.
Maps shall be able to be
customized by placing userdefined labels, buttons,
hotlinks, and adjustable
width polylines on them.
Labels, buttons, hotlinks,
and lines shall be able to
have scripted actions
associated with them that
commence when the item
is clicked.
The ATMS shall support the
saving of customizable
workspace arrangements
(minimum 16 per user).
The ATMS shall support the
ability to display colorcoded travel time
information on a map GUI.
The ATMS shall support
scalable icons that update
in real time. For example,
camera icons rotating on
the map to display the
direction the camera is
pointing with a transparent
field of view cone depicting
the zoom level.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 60 of 72
Functional
Area
Req#
REQ2.8
Video
System
REQ3.1
Management
REQ3.2
REQ3.3
REQ3.4
REQ3.5
REQ3.6
REQ3.7
Requirement
Compliance
(FC/PC/NC)
Notes/Explanations for
PC/Clarifications
The ATMS shall offer
support for multiple
monitor configurations,
allowing each monitor's
content to be configured
with the available content
types.
The ATMS shall permit
viewing and control of all
existing cameras and be
scalable to allow for the
addition of up to 1000 new
cameras.
The ATMS shall support
viewing and recording of
video in industry standard
formats, including H.264,
MJPEG, and MPEG4.
The ATMS shall support and
manage video recording.
Resolution and frame rate
settings shall be adjustable
per camera stream.
The ATMS shall support
playback of video recording
with standard playback
control functions (play,
variable speed fastforward/reverse, etc)
directly through the ATMS
interface.
The recorded video
playback interface shall
include an
adjustable/expandable
timeline, time search
feature, export feature, and
ability to search based on
alarm events.
The ATMS shall integrate
with all major camera and
encoder manufacturers,
including but not limited to
Axis, Avigilon, Pelco Endura
and Sarix, IQEye, Arecont,
Impath, VBrick, ACTi, Bosch,
Panasonic, Cohu,
Optelecom, and Verint.
The ATMS shall support the
ability to capture and FTP
images from cameras to a
specified network location.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 61 of 72
Functional
Area
Req#
REQ3.8
REQ3.9
REQ3.10
REQ3.11
REQ3.12
REQ3.13
Requirement
Compliance
(FC/PC/NC)
Notes/Explanations for
PC/Clarifications
The ATMS shall support the
ability to transcode JPEG
images in real time from
existing MPEG4/H264
streams and provide them
via HTTP URL for use in 3rd
party web applications.
The ATMS shall support
configurable content
windows that can be
arranged in any manner
and saved as separate
workspaces. This shall
allow video to be organized
by “corridor views”.
The ATMS shall support
advanced scripting to allow
graphical items (hot areas,
links, text lables, etc) on
maps to call up predetermined camera views,
including moving cameras
to presets.
Content windows shall be
able to display different
types of content, including
live video, recorded video,
maps, and web documents.
The ATMS shall support onvideo-window mousebased Pan Tilt Zoom (PTZ)
camera control (joystickstyle directional buttons
shall not be necessary) that
supports scroll wheel zoom
, hot key focus, and variable
pan speeds based on
mouse position.
PTZ control shall include
pan, tilt, zoom, iris, focus
and preset store/recall
using a standard interface
for different brands and
models of cameras.
Camera specific features
shall be supported in an
advanced control screen
accessible from the video
window.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 62 of 72
Functional
Area
Req#
REQ3.14
REQ3.15
REQ3.16
REQ3.17
REQ3.18
REQ3.19
REQ3.20
REQ3.21
REQ3.22
REQ3.23
Requirement
Compliance
(FC/PC/NC)
Notes/Explanations for
PC/Clarifications
The ATMS shall support
drag and drop functionality
for seletion and control of
cameras on the map into
viewing windows
The ATMS shall support a
device search mechanism
to quickly locate devices as
an alternative to the
mapping interface.
The ATMS shall support
context sensitive right-click
menus for devices that
provide access to the
device features/settings.
The ATMS shall include a
video distribution
component that manages
all video and acts as a
virtual video matrix switch.
The ATMS video
distribution server shall
provide mechanisms to
allow video to be streamed
through the video
distribution server in both
WAN and LAN environment
simultaneously.
The ATMS shall support
control of video wall
controllers from major
manufacturers including
BARCO (both CMS and
Appolo platforms), Jupiter,
and Christie.
The ATMS shall maintain
layout geometry
synchronization between
ATMS and video wall
controller.
The ATMS shall support
integration with Crestron
A/V controllers.
The ATMS shall support the
use of saved templates for
configuration of the video
wall and auxiliary displays.
The ATMS shall support
access to video, PTZ and
DMS status via a graphical
web interface.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 63 of 72
Functional
Area
Req#
REQ3.24
REQ3.25
REQ3.26
REQ3.27
REQ3.28
REQ3.29
DMS
Management
REQ4.1
REQ4.2
Requirement
Compliance
(FC/PC/NC)
Notes/Explanations for
PC/Clarifications
The ATMS shall support
video distribution to
external networks for video
sharing.
The video distribution
component shall have a
web status page indicating
status of all streams being
distributed and recorded
with real time bit and frame
rates.
The video distribution
component shall support
transcoding from any
industry standard stream
type to another (i.e. MPEG4
to H.264)
The ATMS web client shall
operate in a standard
browser window and shall
not require downloading of
a plug in (ActiveX or other)
to run video and ATMS
functionality (excluding
video decoding).
The ATMS shall provide
display clients that have
controllable layouts for
software decoding digital
video streams. These
layouts and the content
shall be controllable from
any client workstation.
The ATMS shall support
control of command center
audio visual components
such as DVI switchers,
audio switchers, and
Smartboards.
The ATMS shall support the
ability to control Dynamic
Message Signs (DMS)
through an NTCIP interface,
including NTCIP 1203 v2.
The ATMS shall support
read/write access (get/set)
to DMS device objects,
subject to user group
permissions.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 64 of 72
Functional
Area
Req#
REQ4.3
REQ4.4
REQ4.5
REQ4.6
REQ4.7
Incident
and Event
REQ5.1
Management
REQ5.2
REQ5.3
Requirement
Compliance
(FC/PC/NC)
Notes/Explanations for
PC/Clarifications
The ATMS shall support the
ability to create and save
custom messages, as well
as select messages from a
message library
The ATMS shall support
multiple priority levels of
messaging.
The ATMS shall support real
time previews of messages,
making use of sign
parameters, stored fonts
and graphics to create an
accurate depiction of the
sign face (true WYSIWYG).
The ATMS shall support
scheduling one time or
reoccuring messages.
The ATMS shall support the
ability to create and save
custom messages, as well
as select messages from a
message library.
The ATMS shall support the
ability to manage events.
Events types can include: a.
Planned (events with
anticipated schedules) b.
Incidents (any event
impacting roadway
capacity, such as accidents,
stalls, queues, etc). c.
Weather (environmental
conditions) d. Disaster
(spills, fires, etc)
The ATMS shall support
Automated Incident
Detection (AID) based on
user-definable threshold
values using traffic related
data.
The ATMS shall support the
ability to store relevant
information about an
incident in one place for
easy operator recall.
Events can be tagged with
text, XML or image data.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 65 of 72
Functional
Area
Req#
REQ5.4
Traffic
Data
REQ6.1
Management
REQ6.2
REQ6.3
REQ6.4
REQ6.5
Traffic
Signal
Control
REQ7.1
Management
REQ7.2
Requirement
Compliance
(FC/PC/NC)
Notes/Explanations for
PC/Clarifications
The ATMS shall include a
scripting language and
expression service to allow
the creation of complex
alarm and event responses
that can be triggered based
on system states, device
conditions, or user input.
The ATMS shall provide
remote access to the
existing traffic detectors
and allow remote
downloading of traffic data.
Downloading of data shall
be possible manually, or
automatically a
configurable interval.
The ATMS shall support the
ability to ingest data from
various traffic detector
types, including loop
detectors, radar detectors,
Blue Tooth detectors, video
detectors (ex: Traficon).
(List which ones are
currently supported)
The ATMS shall support the
ability to integrate travel
time data via XML streams
and other means from
sources such as the future
Regional Traffic Data
System (RTDS).
The ATMS shall support the
ability to generate
estimated travel times
between roadway points
based on detector data.
The ATMS shall store traffic
data in an industry
recognized data format,
such as Traffic
Management Data
Dictionary (TMDD).
The ATMS shall support the
ability to integrate with
industry standard traffic
controllers to receive signal
status information.
The ATMS shall support the
ability to control industry
standard traffic controllers.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 66 of 72
Functional
Area
Req#
REQ7.3
Administra
tion
REQ8.1
REQ8.2
REQ8.3
Centre to
Centre
Data
Sharing
REQ9.1
Reporting
REQ10.1
REQ10.2
REQ10.3
REQ10.4
Requirement
Compliance
(FC/PC/NC)
Notes/Explanations for
PC/Clarifications
The ATMS shall support the
ability to integrate with UPS
devices and monitor the
status of the batteries and
hydro connections (as
available from the specific
UPS).
The ATMS shall provide
user authentication
through user name and
password.
The ATMS shall support the
creation of an unlimited
number of users and user
groups. Users are assigned
to user groups and thereby
inherit the access privileges
of that group.
The ATMS shall permit very
granular control of access
privileges on a group level.
Access privileges allow a
user’s access to
administrative functions,
maps, devices, subsets of
device features,
workspaces, and scripts
independently.
The ATMS shall support the
exchange of data with
other agencies via Centre
to Centre (C2C) protocols
(WSDL/SOAP/XML).
The ATMS shall log all
system events, alarms, and
configuration changes.
The ATMS shall support a
search function to search
the log files based on userselectable query criteria.
The ATMS shall support the
generation of event detail
reports that provide a
summary of the logged
details related to each
event.
The ATMS shall support the
generation of system log
reports that provide a
summary of devices and
alarms.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 67 of 72
FC: Fully Compliant means the current version of the ATMS solution fully meets the required functionality without the need for third
party applications.
PC: Partially compliant means the current version of the ATMS solution meets most of the required functionality, some of which
may include the use of third part applications.
NC: Non Compliant means the current version of the ATMS is not capable of meeting the requirement.
Notes: Provide any additional notes that can provide further clarifications
Software Information
Vendor
XXX
Date
XXX
Software Name
XXX
Current Software Version
(as of the closing date of this RFP)
XXX
# of Installations of the current version of the
software in Canada
XXX
# of Installations of the current version of the
software in US
XXX
Closest Office to Surrey with Technical Software
Expertise and Support Capability
XXX
Hourly rate for on-site service (if requested by
City, additional to Warranty requirements)
$##.##/hr
Describe Licensing Structure and Costs for All
Software Components (ex: cost per user,
camera, device, server, backup server, module,
etc)
XXX
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 68 of 72
Instructions:
Complete all highlighted cells, as required. Current Version refers to the version that is
commercially available as of the closing date of this RFP.
Third party applications are defined as separate COTS applications that are required to be
installed and operated separately to perform specific functions. Examples include separate
video management or recording software.
Additional RFP Instructions:
Proponents are instructed to complete the attached table – Appendix 1: ATMS Requirements
Matrix:
Review and complete the table Appendix 1: ATMS Requirements Matrix. The purpose
of this matrix is to assess the functionality of the solution against the high level project
requirements. Please indicate the approximate compliance with each requirement using
the following indicators: Fully Compliant (FC), Partially Compliant (PC), Not Compliant
(NC).
Please note the following guidelines when completing the requirements matrix:
 CoS may request supporting evidence at a later time to substantiate the responses.
 Current version refers to the version of the software that is commercially available as of
the closing date of this RFP.
 Third Party Applications are defined as separate COTS applications that are required to
be installed and operate separately (but may have integrated data exchange) to perform
specific functions. Examples include separate video management and recording
software.
 Fully Compliant (FC) means the current version of the ATMS requirement is fully met
and the functionality is currently provided, without the use of third party applications.
 Partially Compliant (PC) means that the current version of the software meets some
aspects of the requirement or can meet the requirement using additional software
packages integrated into the ATMS.
 Not Compliant (NC) means that the ATMS is not capable of meeting the requirement.
 The requirements matrix shall be completed based on the current version of the
software. If a requirement is not currently met, but will be met by a release of the
software this calendar year, indicate NC and in the Notes field indicate the expected
release date of the software version.
 If a third party applicationis required to provide the necessary functionality for any given
requirements, indicate PC and provide details of what additional software and/or
hardware is required in the Notes field.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 69 of 72
SCHEDULE C-4 - PROPONENT’S TECHNICAL PROPOSAL (TIME SCHEDULE)
The Proponent shall provide an estimated schedule that is to take into account all factors that
might affect delivery of the project. The schedule shall show timelines for all phases of the
project and will be used for future reference for tracking the project (use the spaces provided
and/or attach additional pages, if necessary).
MILESTONE DATES __________________________________
ACTIVITY
SCHEDULE
1
2
3
4
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
5
6
7
8
9
10
Page 70 of 72
SCHEDULE C-5 - PROPONENT’S FINANCIAL PROPOSAL
Indicate the Proponent’s proposed fee (excluding GST), and the basis of calculation (use the spaces provided and/or
attach additional pages, if necessary) as follows (as applicable):
All prices shall be in Canadian Funds and shall remain firm for the duration of the project.
Table 1: Schedule of Rates:
Item
No.
1
Unit
Quantity
ATMS Software Licensing
LS
1
2
ATMS Configuration
LS
1
3
NVR Upgrade
LS
1
4
Testing, Training, and Documentation
Warranty, Software Assurance, and Technical
Support
Additional Components
LS
1
LS
1
LS
1
5
6
Description
Total Price
Subtotal:
PST 7%: (AS APPLICABLE)
GST 5%:
TOTAL PROPOSAL PRICE
Table 2: Optional Prices
The following is a list of Optional Prices and forms part of this RFP, upon the acceptance of any or all of the
Optional Prices. The Optional Prices are an addition to the Total Proposal Price and do not include
applicable taxes. Do NOT state a revised Total Proposal Price.
Description
Unit
Quantity
1
Additional Camera Licensing
LS
1
2
Additional Warranty, Software Assurance, and
Technical Support – 2 year
LS
1
3
Additional Warranty, Software Assurance, and
Technical Support – 4 year
LS
1
4
ATMS Backup Server
LS
1
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Price
(Excluding
applicable taxes)
Page 71 of 72
Additional Expenses:
The proposed Contract attached as Schedule "B" to the RFP provides that expenses are to be included within the
fee, other than the expenses listed in the Contract as disbursements. Details of disbursements are to be shown in
the chart above. Please indicate any expenses that would be payable in addition to the proposed fee and proposed
disbursements set out above:
Payment Terms:
A cash discount of _______% will be allowed if account is paid within _____ days, or the_________ day of the month
following, or net 30 days, on a best effort basis.
Transportation Operations Centre ATMS Implementation RFP #1220-030-2013-011
Page 72 of 72