D4. SCOPE OF SERVICES
D4.1 The Services required under this Contract shall consist of a benefit analysis and feasibility study of EVP for the City of Winnipeg. The objective is to provide decision makers with a basis on which to assess transportation implications of city-wide EVP implementation and the benefits it
may provide.
(a) Describe the existing WFPS system for route selection and assess WFPS experience with
existing hardwired fire hall pre-emption systems in Winnipeg.
(b) Using different types of roadway classifications estimate the number of active emergency
vehicles expected per day and quantify the anticipated impacts to traffic including traffic signal
coordination recovery time and queue recovery time.
(c) Quantify the time-savings achievable for the WFPS through EVP in Winnipeg.
(d) Compile and assess intersection collisions involving emergency vehicles over the past five
years. Estimate potential changes in collision frequency with EVP and potential cost savings.
(e) Determine if EVP should be implemented at all signal-controlled intersections or is there a
hierarchy of priority locations that EVP would be more suited for.
(f) Research other similar cities with EVP systems and the benefits and lessons learned from
those implementations. Include a survey of the type of EVP system used, policies for truncating
traffic signal phases and pedestrian clearance times. Summarize which vehicle types are using EVP.
(g) Provide overview of off-the-shelf EVP solutions that are compatible with the City’s current
traffic controllers and Signals Traffic Management System (Transparity) software. Include a Class 4 cost estimate for installation per intersection and per emergency vehicle.
(h) Provide a cost-benefit analysis for the installation and incorporation of EVP in Winnipeg
based on the findings of this study. This should include factors such as collision reduction,
time-savings, traffic impacts, EVP system costs, WFPS facility location requirements, and other
factors as determined by the study.
D4.1.1 The Services required under D4.1 shall be in accordance with the City’s Project
Management Manual http://winnipeg.ca/infrastructure/asset-management-
program/templates-manuals.stm#2 and templates http://winnipeg.ca/infrastructure/asset-
management-program/templates-manuals.stm#4 . Notwithstanding the foregoing, the Consultant is being engaged by the City for its professional expertise; the Consultant shall bring to the Project
Manager’s attention any aspect of the City’s Project Management Manual or templates which the
Consultant is of the opinion is not consistent with good industry practice.
D4.2 Throughout the Project, the Consultant should coordinate with the City’s Project Manager. The City’s Project Manager will be:
(a) Kept informed by the Consultant’s Project Manager of progress on a regular basis.
(i) Monthly progress meetings will be held.
(ii) The Consultant should distribute agendas one (1) week in advance and minutes one
(1) week after each progress meeting.
(b) Copied on all Project correspondence.
(c) Advised of significant problems/issues as they arise, resolution options to be considered,
and recommended solutions for consideration and approval by the City prior to implementation.
(d) Involved in any meetings with stakeholders, based on the City’s Project Manager’s
availability.
(e) Advised of any potentially controversial issues as they arise.
(f) Advised of any additional work considered, prior to it being completed, beyond the original
scope of services.
(g) Consulted prior to any changes being made to the City approved project schedule. The City’s
Project Manager shall confirm any schedule changes in writing.
The City will establish a Technical Working Group comprised of Winnipeg Fire & Paramedic Services,
D4.3 Traffic Signals Branch, and Innovation & Technology staff. Throughout the Project,
with the City of Winnipeg’s Technical Working Group.
D4.3.1 The City is anticipating an active and involved Technical Working Group for this
Project.
D4.3.2 The personnel assigned to the City’s Technical Working Group will be determined
at project kickoff.
D4.3.3 The City’s Technical Working Group will be involved in the day-to-day technical
aspects of the Project, specific to their respective disciplines, level of commitment, and
availability. They will be engaged and kept informed of the Project’s progress through:
(a) Monthly Technical Working Group meetings to be organized by the consultant and to be held for the duration of the project.
(i) The Consultant should distribute agendas one (1) week in advance and minutes one (1) week
after each Technical Working Group meeting.
(b) Circulation of Project documentation for review.
(c) Additional consultation and collaboration as needed.
D4.4 The Consultant should submit a draft final report to the City by August 12, 2022, for review.
(a) The draft report should include the results of all items pertaining to D4.1, as described
above.
(b) The City will complete the review and return the draft final report with comments by
September 9, 2022.
D4.5 The Consultant should submit a final report for review and approval by the City by September 30, 2022, for review and approval.
(a) The final report should include the results of all items pertaining to D4.1, as described
above.
(b) Allow suitable time for City review, comments, and approval of the final report.
