CN-550000-BE823-00030000.pdf

FLORIDA DEPARTMENT OF TRANSPORTATION

STANDARD WRITTEN AGREEMENT

375-040-07

PROCUREMENT

03/17

MODIFICATION # 4

Agreement No. BE823

Financial Project I.D. 437113-1-82-01

Vendor No. F591922964

Procurement No. ITN-DOT-18-19-5001-RMC

DMS Catalog Class No.

81111500, 81112000, 80101507, 80101508, 801111503

Amendment # 4

This Agreement, made and entered into on by and between the STATE OF FLORIDA

DEPARTMENT OF TRANSPORTATION, hereinafter called the "Department" and IBI Group Professional Services (USA), Inc. of 1100

Park Central Boulevard South, Suite 3500, Pompano Beach, Florida 33064 , duly authorized to conduct business in the State of Florida, hereinafter called the "Vendor."

WITNESSETH:

WHEREAS, the Department and the Vendor heretofore on 6/21/2019 , entered into an agreement, hereinafter called the

"Original Agreement," whereby the Department retained the Vendor to furnish certain services in connection with PedSafe/Greenway

Software Development Package ; and

WHEREAS, the Department has determined it necessary to amend the agreement to revise Exhibit "A," Exhibit "B," and

Exhibit "C," and extend the contract for 6 months. , NOW, THEREFORE, this Agreement witnesseth the following amendment is made;

Revised versions of Exhibit "A" Scope of Services, Exhibit "B" Method of Compensation, and Exhibit "C" Minimum Technical Requirements are attached hereto and made a part hereof. These changes are necessary for the Department to meet ATCMTD grant requirements, be scalable with future statewide connected vehicle initiatives, and due to a change in UCF mobile application vendor outside Department or Vendor control.

Additionally, the term of the contract is extended for 6 months, to expire on 12/30/2024 .

Except as hereby modified, amended, or changed, all of the terms and conditions of said agreement and any amendments thereto will remain in full force and effect.

IN WITNESS WHEREOF, the parties have executed this Agreement by their duly authorized officers on the day, month and year set forth above.

DocuSign Envelope ID: AD02621D-C646-4549-B301-5D947A817955

12/7/2022 | 5:44 PM EST

FLORIDA DEPARTMENT OF TRANSPORTATION

STANDARD WRITTEN AGREEMENT

375-040-07

PROCUREMENT

03/17

IBI Group Professional Services (USA), Inc.

STATE OF FLORIDA

DEPARTMENT OF TRANSPORTATION

Name of Vendor

BY: BY:

Authorized Signature

Charles M. Heffinger, Jr., P.E.

(Print/Type) (Print/Type)

Title: Title: Director of Transportation Operations

FOR DEPARTMENT USE ONLY

APPROVED: LEGAL REVIEW

Procurement Services Manager

Paul Lavallee

BY: ______________________________________________

______________________________________________Title:

(Print/Type) James Barbosa

DocuSign Envelope ID: AD02621D-C646-4549-B301-5D947A817955

Director, US Solutions

Director, US Sector Lead, Intelligence

Scope of Services for PedSafe/Greenway Software Development Package

A-i

Exhibit A

Scope of Services for

PedSafe/Greenway Software Development Package

ITN-DOT-18-19-5001-RMC

Version: 1.2

A-ii

Table of Contents

1 PROJECT DESCRIPTION

1.1 PROJECT BACKGROUND

1.2 SOFTWARE DEVELOPMENT PACKAGE CONTEXT

1.2.1 Route and Mode Choice Engine

1.2.2 FL511 Mobile App Enhancement

1.2.3 Transit Kiosk Software

1.3 SSUMPTIONS AND DEPENDENCIES

1.3.1 Assumptions for Route and Mode Choice Application Engine

1.3.2 Assumptions for FL511 Mobile App Enhancement

1.3.3 Assumptions for Transit Kiosk Software

1.3.4 Statutory Project Management and Cyber Security Standards

1.4 TECHNICAL REQUIREMENTS

1.5 SOFTWARE OWNERSHIP

2 APPLICABLE DOCUMENTS

3 SCOPE OF WORK

3.1 DEPARTMENT RESPONSIBILITIES

3.2 VENDOR’S GENERAL OBLIGATIONS

3.3 OTHER PARTICIPANTS’ OBLIGATIONS

3.4 OVERVIEW OF THE PROJECT STEPS

3.5 PROJECT TASKS

3.5.1 Task 1 – VENDOR Responsibilities

3.5.2 Task 2 – Systems Design

3.5.3 Task 3 – System Build

3.5.4 Task 4 – Deployment

3.5.5 Task 5 – System Training

3.5.6 Task 6 – Operations, Maintenance and Support

3.6 SPECIAL SERVICES

4 VENDOR PERFORMANCE

5 CONTRACT DELIVERABLE REQUIREMENTS LIST

List of Tables

TABLE 3: LABOR CATEGORIES AND DESCRIPTIONS

TABLE 4: SERVICE LEVEL KEY PERFORMANCE INDICATORS (KPI) AND LIQUIDATED DAMAGES

A-iii

TABLE 5: CONTRACT DELIVERABLE REQUIREMENTS LIST

List of Figures FIGURE 1: PEDSAFE/GREENWAY ROADSIDE UNIT (RSU) LOCATIONS IN PINE HILLS NEIGHBORHOOD

FIGURE 2: PEDSAFE/GREENWAY ROADSIDE UNIT (RSU) LOCATIONS IN AND AROUND UCF CAMPUS

FIGURE 3: PEDSAFE/GREENWAY TRANSIT KIOSK LOCATIONS ON UCF CAMPUS

FIGURE 4: ROUTE AND MODE CHOICE APPLICATION ENGINE SYSTEM FUNCTIONAL BLOCK DIAGRAM

FIGURE 5: EXAMPLE OF ADMINISTRATIVE DASHBOARD (INITIAL)

FIGURE 6: EXAMPLE OF ADMINISTRATIVE DASHBOARD (POTENTIAL)

FIGURE 7: EXAMPLE OF SUPPORT WEBSITE

FIGURE 9: SYSTEM DEVELOPMENT DIAGRAM

FIGURE 10: NOTATIONAL PROJECT GANTT CHART

A-iv

List of Acronyms and Abbreviations

API ............................................................................. Application Programming Interface

AST ..................................................................................... Agency for State Technology

BSM ............................................................................................... Basic Safety Message

C2C ......................................................................................................... Center to Center

CDR ...............................................................................................Critical Design Review

COTS ........................................................................................ Commercial Off-the-Shelf

CV ....................................................................................................... Connected Vehicle

C-V2X .................................................................................. Cellular vehicle-to-everything

D5.................................................................................................................... District Five

DEP .............................................................................................Data Exchange Platform

EVP ................................................................................. Emergency Vehicle Preemption

FCS ................................................................................ Florida Cybersecurity Standards

FDOT ...................................................................... Florida Department of Transportation

GTFS .......................................................................... General Transit Feed Specification

HTTP ...................................................................................... Hypertext Transfer Protocol

IT .................................................................................................. Information Technology

ISM ..................................................................................... Information Security Manager

KPI ........................................................................................ Key Performance Indicators

LD..................................................................................................... Liquidated Damages

MAP ................................................................................................................... Map Data

NMS ....................................................................................... Network Monitoring System

PDR ......................................................................................... Preliminary Design Review

PSEMP .................................................... Project System Engineering Management Plan

PSM ..........................................................................................Personal Safety Message

REST ............................................................................... Representational State Transfer

RSA ............................................................................................................ Roadside Alert

RSU ............................................................................................................. Roadside Unit

RTVM ......................................................... Requirements Traceability Verification Matrix

SAE ................................................................................ Society of Automotive Engineers

SAT .......................................................................................... Systems Acceptance Test

SDD .......................................................................................... System Design Document

SLA ........................................................................................... Service Level Agreement

SPAT ..........................................................................................Signal Phase and Timing

SSP ................................................................................................. System Security Plan

SwRI .................................................................................... Southwest Research Institute

TCP ................................................................................... Transmission Control Protocol

A-v

TDD ........................................................................................... Test Driven Development

TIM ..................................................................................... Traveler Information Message

TSP ................................................................................................. Transit Signal Priority

TTFB ..................................................................................................... Time to First Byte

TWO ....................................................................................................... Task Work Order

UCF ....................................................................................... University of Central Florida

V2X .................................................................................................. Vehicle-to-everything

WBS ........................................................................................ Work Breakdown Structure

A-6

1 Project Description

The Florida Department of Transportation (herein after DEPARTMENT or FDOT) District Five (herein after “D5”) has identified a need for software development services to design, develop, test, deploy, and support various technologies installed as part of the PedSafe/Greenway Deployment (FPID 440821-1-52-01) project.

The DEPARTMENT is seeking to enter into a contract to procure works-for-hire design, develop, test, deploy, and support (hereinafter “CONTRACT”) multiple software development efforts related to the PedSafe/Greenway Deployment.

The term of the CONTRACT will be four (4) years. The design-build portion of the PROJECT described in Section 3.5 – with the exception of Section 3.5.1 – shall occur in the first two (2) years of the CONTRACT. The operations, maintenance, and support of the system described in Section 3.5.6 shall occur in the remaining two (2) years of the CONTRACT. There will also be additional services, as described in Section 3.6 that may occur at any time throughout the CONTRACT.

The PedSafe/Greenway Software Development Package will consist of three unique software design, development, testing, deployment and integration efforts: route and mode choice engine, FL511 Mobile App Enhancement for Connected Vehicles, and transit kiosk software.

The route and mode choice engine will include a commercial off-the-shelf (COTS) product capable of collecting, storing, and analyzing public and private transportation data in order to produce multi-modal travel recommendations for users regarding available routes and modes of travel.

The FL511 Mobile App Enhancement will be a custom-built modification to the FL511 backend system and Mobile App to incorporate data from the PedSafe/Greenway Software Development project and other identified sources of connected vehicle (CV) messages, such as personal safety messages (PSM) and basic safety messages (BSM), as appropriate. The FL511 enhancement will include a system engineering effort to specify and design the integration of the design, the TravelSafely data exchange API, other 3rd party data exchange API (furnished by Florida’s Turnpike Enterprise), FDOT’s Statewide Data Integration Video Aggregation System (DIVAS), One.Network’s WZDx API, FDOT’s Statewide Data Exchange Platform (DEP), and FDOT District 5’s Route and Mode Choice Engine (RMCE).

Custom-built software to be deployed on transit kiosks will allow users to input origin and destination information to determine the various multi-modal travel options, as well as compare estimated travel time, wait time, cost, and location of each alternative. The application development will leverage data streams provided from the route and mode choice engine.

A-7

The successfully selected software development team (hereinafter “VENDOR”) shall provide a qualified and experienced team. The VENDOR shall use an iterative software development approach described in this scope of services document.

1.1 Project Background

As part of the PedSafe/Greenway Deployment (FPID 440821-1-52-01) project, various innovative technologies will be deployed throughout FDOT District 5. These technologies include, among others, C-V2X-enabled roadside units (RSU) for CV applications deployed at signalized intersections within Orange and Seminole County jurisdictions, as well as transit kiosks within the UCF campus.

The RSU deployment focuses on 33 intersections in and around the UCF main campus in Orlando, FL, as well as a portion of the SR 50 (Colonial Drive) corridor, known colloquially as the Pine Hills neighborhood. Both areas experience large volumes of pedestrian and bicyclist traffic along heavily traveled arterial corridors.

PedSafe/Greenway aims to utilized CV equipment, in conjunction with other advanced sensing and detection technologies, to provide increased levels of safety to vulnerable road users.

At a minimum, all 33 intersections will deploy CV equipment necessary to support the following baseline applications:

Signal phasing and timing (SPAT) and map data (MAP) broadcast Traveler information message (TIM) and roadside alert (RSA) message broadcast BSM receipt and forwarding Emergency vehicle preemption (EVP) and transit signal priority (TSP)

FDOT will select CV equipment based on conformance with the existing national standards in place at the time of deployment to foster interoperability and provide a platform capable of supporting future CV application, research, development, and implementation.

Table 1: Proposed Intersections for RSU Deployment

No. Proposed Intersection (Major Corridor – Intersection)

1 SR 50 (Colonial Dr) CR 435 (Hiawassee Rd)

2 SR 50 (Colonial Dr) Powers Dr

3 SR 50 (Colonial Dr) Paul St

4 SR 50 (Colonial Dr) Hastings St

5 SR 50 (Colonial Dr) SR 435 (Kirkman Rd/Governors Ave)

6 SR 50 (Colonial Dr) Westside Crossing Shopping Ct

A-8

7 SR 50 (Colonial Dr) CR 431 (Pine Hills Rd)

8 SR 434 (Alafaya Trl) Challenger Pkwy

9 SR 434 (Alafaya Trl) Science Dr./Lokanotosa Trl

10 SR 434 (Alafaya Trl) Research Pkwy

11 SR 434 (Alafaya Trl) Central Florida Blvd

12 SR 434 (Alafaya Trl) University Blvd

13 SR 434 (Alafaya Trl) Strategy Blvd

14 SR 434 (Alafaya Trl) Centaurus Blvd (Siemens Ent/UCF Ent)

15 SR 434 (Alafaya Trl) Gemini Blvd/Corporate Blvd

16 SR 434 (Alafaya Trl) McCulloch Rd

17 Gemini Blvd Greek Park Dr

18 Gemini Blvd Centaurus Blvd

19 Gemini Blvd University Blvd

20 Gemini Blvd Andromeda Loop

21 Gemini Blvd Central Florida Blvd

22 Gemini Blvd Hydra Ln

23 Gemini Blvd Libra Dr

24 Gemini Blvd Scorpius St (1)

25 Gemini Blvd Scorpius St (2)

26 Gemini Blvd Orion Blvd

27 Gemini Blvd E Plaza Dr

28 Gemini Blvd W Plaza Dr

29 Gemini Blvd Parking Garage H

30 University Blvd Quadrangle

31 McCulloch Blvd Lockwood Blvd

32 McCulloch Blvd Keats Way/Worchester Dr

33 McCulloch Blvd Old Lockwood Blvd

A-9

Figure 1: PedSafe/Greenway Roadside Unit (RSU) Locations in Pine Hills neighborhood.

Figure 2: PedSafe/Greenway Roadside Unit (RSU) Locations in and Around UCF Campus.

A-10

In an effort to identify technologies bridging the gap to a “smart community”, the deployment will also install 11 transit kiosks at several existing UCF shuttle stop locations on campus in order to deliver users with various transit-related information. Transit kiosks with embedded computing and display platforms capable of supporting custom-built applications will be interactive, allowing for users to input origin-destination information and determine the appropriate mode of transport based on numerous factors including time and cost. Each transit kiosk will be provided with a cellular means of communication to maintain real-time information, as well as provide data streams to the operating entities.

Figure 3: PedSafe/Greenway Transit Kiosk Locations on UCF Campus.

1.2 Software Development Package Context

The PedSafe/Greenway Software Development Package will leverage the technologies installed as part of the PedSafe/Greenway Deployment to optimize the functionality of the hardware, increasing safety for pedestrians, bicyclists and motorists, and providing transit users the ability to access real-time information for multi-modal decisions.

1.2.1 Route and Mode Choice Engine

Based on OpenTripPlanner, the route and mode choice engine will provide FDOT with a multi-modal, multi-provider trip planner application engine for use by the public. The primary purpose of the application engine is to provide a web-based trip routing service enabling third-party navigation applications to retrieve, display multi-modal trips to end users, and monitor trips for exception events. The application engine will comprise four

A-11 major subsystems with the core functionality of the engine, including the representational state transfer (REST) application programming interface (API), routing engine, trip scoring, and real-time trip planning and monitoring (Figure 4).

Figure 4: Route and Mode Choice Application Engine System Functional Block Diagram.

1.2.1.1 REST API Subsystem Definition

The REST API is a web-based application interface that enables third-party applications to submit routing requests and receive results over a secure, industry-standard protocol such as HTTPS.

Third-party applications will interface with the REST API over the web, using an industry-standard protocol such as HTTPS.

1.2.1.2 Routing Engine Subsystem Definition

The routing engine fulfills trip routing requests received through the REST API by determining available trip paths from the trip origin to the destination.

The routing engine is an internal component with no external interfaces. The routing engine will fulfill trip routing requests received from the REST API.

A-12

1.2.1.3 Trip Scoring Subsystem Definition

The trip scoring subsystem will order suggested routes based on the parameters specified in each routing request and, once implemented, any existing user preferences and constraints.

The routing engine is an internal component with no external interfaces. The routing engine will fulfill trip routing requests received from the REST API.

1.2.1.4 Real-Time Trip Planning and Monitoring Subsystem Definition

The real-time trip planning and monitoring subsystem updates trips in response to dynamic changes in travel conditions.

The real-time trip planning and monitoring subsystem is an internal component with no external interfaces. It will monitor real-time feeds in the background and respond when updates are received.

1.2.1.5 GTFS Monitoring Subsystem Definition

The General Transit Feed Specification (GTFS) monitoring subsystem tracks and automatically updates the GTFS feeds used by the application engine to reflect up-to-date transit schedules

The GTFS monitoring subsystem is an internal component with no external interfaces. It will update GTFS feeds in the background.

1.2.1.6 Administrative Dashboard Subsystem

The administrative dashboard is a website enabling authorized personnel to perform basic status monitoring and manual testing of the engine. This will enable non-technical personnel to verify the functionality of the engine independently of third-party applications.

Examples of functions that could fulfill this requirement include a basic log of requests received and a minimal user interface for performing simple routing requests.

The dashboard will be presented as a web interface, accessible through standard web browsers over HTTPS. Figure 5: Example of Administrative Dashboard (Initial). provides an example of what the initial, minimal version of the dashboard might look like. The goal for the initial version of the dashboard should be to provide the basic functionality essential for verifying engine functionality and monitoring use by third-party applications.

Figure 6 then demonstrates a potential advanced version of the dashboard, with functionality expanded to match a more fully featured application engine. As features are added to the application engine, the dashboard should be updated to enable verification and monitoring of the new functionality, as applicable.

A-13

Figure 5: Example of Administrative Dashboard (Initial).

A-14

Figure 6: Example of Administrative Dashboard (Potential).

1.2.1.7 Support Website Subsystem

The support website provides potential third-party application developers with the information needed to use the application engine.

The support website will be presented as a web interface, accessible through standard web browsers over HTTPS. Figure 7 provides an example of what one page of the dashboard might look like. It includes a navigation menu with links to the features that the initial support website should provide. The remaining views would follow a similar format and the same overall layout.

A-15

Figure 7: Example of Support Website.

1.2.1.8 Logging Subsystem

The logging subsystem stores messages logged by other subsystems.

The logging subsystem is an internal component with no external interfaces. It will log messages received from other subsystems in the application engine.

1.2.1.9 Notification Subsystem

The notification subsystem sends notifications of warnings and errors generated by the application engine to project maintainers and stakeholders.

The notification subsystem is an internal component with no external interfaces. It will receive messages generated by other subsystems and send notifications to relevant project maintainers and stakeholders.

A-16

1.2.2 FL511 Mobile App Enhancement

The FL511 Mobile App Enhancements shall include a system architecture and preliminary design to reflect and incorporate all required FL511 backend changes and relevant use case and functional changes related to the use of the FL511 Mobile App to incorporate data from C-V2X devices and other identified sources. Central to this modification is the systems engineering effort required to specify and design the integration of the TravelSafely data exchange API, other 3rd party data exchange API (furnished by Florida’s Turnpike Enterprise), FDOT’s Statewide Data Integration Video Aggregation System (DIVAS), One.Network’s WZDx data API, FDOT’s Statewide Data Exchange Platform (DEP), and FDOT District 5’s Route and Mode Choice Engine (RMCE).

Public Facing Interface

The public facing interface obtains necessary hardware level permissions, uploads Smartphone location data, and serves all published applications to the user. The user may enable and disable any CV applications provided through the FL511 Mobile App at will.

1.2.2.1 Interfaces

The FL511 Mobile App Enhancement will interface with TravelSafely data exchange API, FDOT’s Statewide Data Integration Video Aggregation System (DIVAS), One.Network WZDx data API, FDOT’s Statewide Data Exchange Platform (DEP), FDOT District 5’s Route and Mode Choice Engine (RMCE), Regional Integrated Corridor Management Software (RICMS), and the GTFS-RT Aggregator. Interfaces needed to support data elements as described in the Section 1.2.2 FL511 Mobile App Enhancement for the various application will be built. Consideration for future applications from section 1.2.2 FL511 Mobile App Enhancement will also be made. Interfaces for additional 3rd party data exchange API will be provided, with reasonable assumptions of the 3rd parties interface.

The Department will provide MAP data to the FL511 Mobile App Enhancement via a single modern interface for all field deployed RSUs. The data will be used for future applications and ingested by the backend services of the FL511 Mobile App Enhancement.

1.2.2.2 Data Exchange Platform Application

The Department has contracted with SwRI to build a Data Exchange Platform. The FL511 Mobile App Enhancement will provide TIM generated by FL511 Mobile App Enhancement to the DEP. The DEP may provide TIM to the FL511 Mobile App Enhancement.

A-17

1.2.2.3 TravelSafely Data Exchange and 3rd Party Applications

The FL511 Mobile App Enhancement will include data interfaces as required to the AI Data Exchange and other 3rd Party Applications.

1.2.2.4 Alerts and Notifications

The user may enable and disable any CV applications provided through the FL511 Mobile App at will. Applications will include:

Curve Speed Warning

Congestion Ahead

Crash and/or Road Ranger Ahead

Work Zone Warning

Weather/Visibility Warning

Any TIM from V2X DEP or SunGuide

Signal Phasing and Timing (SPaT)

Pedestrian Warning

1.2.2.4.1 Curve Speed Warning

The Curve Speed Warning application will make use of statically configured speed within geofenced areas. When these speeds are exceeded and the location services places the phone within the geofenced area an auditory alert will be triggered, including verbal direction to reduce speed.

1.2.2.4.2 Congestion Ahead Warning

The Congestion Ahead Warning application will make use of reported head and tail of queue information from SunGuide. When the the location services places the phone within a configurable distance of the tail of the queue with a direction of travel approaching the queue an auditory alert will be triggered, including verbal direction to reduce speed.

1.2.2.4.3 Crash/Road Ranger Ahead

The Crash Ahead Warning application will make use of reported crash location information from SunGuide. When the location services places the phone within a configurable distance of the crash with a direction of travel approaching the crash an auditory alert will be triggered, including verbal direction to use caution.

A-18

The Road Ranger Ahead Warning application will make use of reported Road Ranger location information and Road Ranger Status from SunGuide. When the location services places the phone within a configurable distance of the Road Ranger, with a direction of travel approaching the Road Ranger, and the Road Ranger Status indicates they are on scene an auditory alert will be triggered, including verbal direction to use caution.

When the Road Ranger Ahead Warning and Crash Ahead Warning are within a configurable distance they will be combined into a single auditory alert, including verbal direction to reduce speed.

1.2.2.4.4 Work Zone Warning

The Work Zone Warning application will make use of reported begin and end of Work Zones from SunGuide and One.Network. When the location services places the phone within a configurable distance of the begin of work zone and the work zone is active, with a direction of travel approaching the work zone, an auditory alert will be triggered, including verbal direction to use caution.

1.2.2.4.5 Weather/Visibility Warning

The Weather Warning application will make use of several data points from SunGuide, including but not limited to visibility, wind speed, tornado warning, hurricane warnings, severe weather warnings, and tornado warnings. When the location services places the phone within a configurable distance of the warning, with a direction of travel approaching the warning, an auditory alert will be triggered, including verbal direction to use caution and the alert will be identified.

When the location services places the phone within a configurable distance of the point data location, with a direction of travel approaching the point data location, and a configurable threshold for visibility or wind speed is met (low visibility or high speed), an auditory alert will be triggered, including verbal direction to use caution and the alert will be identified.

1.2.2.4.6 TIM from V2X DEP or SunGuide

The TIM application support will make use of TIMs received from DEP, SunGuide, AI, or other third party. The application will receive the TIM along with the geolocation and direction of travel it is to be effect for. If the user is within the geofenced area and headed in the appropriate direction the application will use images and sounds from its library to interface with the users. In the absence of and image and/or sound no image will be shown or sound played, respectively.

A-19

1.2.2.5 Other 511 Enhancements

Other 511 Enhancements include Multimodal Route Guidance. Crowd Sourced Incident Application .

1.2.2.5.1 Multimodal Route Guidance

The Route and Mode Choice Engine will be incorporated into FL511.

1.2.2.6 Optional 511 Enhancements

Optional 511 Enhancements include Crowd Sourced Incident Application.

1.2.2.6.1 Crowd Sourced Incident Application

FL511 will be enhanced to allow a user to generate a request for assistance on the roadside. If business rules are met, the location services of the user will be used to generate an event in SunGuide to be confirmed by an operator as part of the IDS process. Business rules will include being, reasonably, at a fixed location, being within the service area of a TMC, being within the operating hours of Road Rangers for that section of roadway. A GUI for the configuration of the Crowd Sourced Incident with login verification will be created. If the business rules are not met the GUI with the means to access the request will still be available but greyed out with the reason displayed.

1.2.2.7 Future Connected Vehicle Applications

The software will be built understanding the Department’s desire for future enhancements. This includes supporting future applications including but not limited to: Connection Protection, Passive Ped based on path, SRM to controller, Responder EVP with path, SRM to controller, and RICMS – Diversion Routes.

While these applications will not be included in this scope. The team will design to accommodate seamless growth into these applications without having to remove major parts of this build.

1.2.2.7.1 Connection Protection

The Connection Protection application will make use GTFS-RT data from the GTFS-RT aggregator, location services, and route from the route and mode choice engine. When the location services places the phone on a coincident path with a transit vehicle selected in the route and mode choice engine and there is another connecting leg of the trip. The application will provide a message to be received by a designed endpoint in a format that will trigger an alert to the driver of the connecting vehicle to hold their trip based on the

A-20 projected arrival of the connecting user with a configurable threshold to allow the transfer to occur. The application will provide updated GTFS-RT feed information to correct the information for the queue vehicle and a service alert if appropriate. If the connecting trip exceeds a configurable threshold by route then the user will be informed the connection will not occur and an alternative route plan will be generated. The end point maybe an application that runs on a specialized device on the queued vehicle or via their Computer Aided Dispatch software, as determined in design.

1.2.2.7.2 Passive Ped based on path, SRM to controller

The Passive Pedestrian application will make use location services, and route from the route and mode choice engine. When the location services places the phone on a path selected in the route and mode choice engine using a mode of travel of walking, scooting, or biking and the user is within a configurable distance of a signalized intersection. The application will generate a signal request message to actuate the signal input to the controller as if the pedestrian pressed the pedestrian button for the crossing direction from the path in the route and mode choice engine. The application will inform the user the signal has been actuated and the remaining time until their phase, if available from SPaT data. If the pedestrian departs the signal early then another SRM to cancel the call will be sent. If the pedestrian fails to use the available phase within a configurable time of the phase beginning a haptic response will be generate along with a verbal alert of “walk.”

1.2.2.7.3 Responder EVP with path, SRM to controller

The Emergency Vehicle Preemption application will make use location services, and route from the route and mode choice engine. When the location services places the phone on a path selected in the route and mode choice engine, and the path is coincident with geolocation and direction of two or more signals that has received SRM call requests from the same source within a configurable time period. The application will generate SRM calls to other controllers along the path a prescribed distance of travel away from the signal. The SPaT or SSM will be monitored. If successful preempted a verbal tone will be generated within a configurable distance of each effected intersection.

1.2.2.7.4 RICMS – Diversion Routes

The RICMS Diversion application will make use location services, route from the route and mode choice engine, and RICMS. When the location services places the phone on a path selected in the route and mode choice engine, A-21 and the path is follows a diversion route current active as determine by the status of RICMS. The application will verbal alert informing the user they are on a diversion route with preferential timing due to an incident.

1.2.2.8 Other 511 Enhancements

Other 511 Enhancements include Crowd Sourced Incident Application and Multimodal Route Guidance will be developed.

1.2.2.8.1 Crowd Sourced Incident Application

FL511 will be enhanced to allow a user to generate a request for assistance on the roadside. If business rules are met, the location services of the user will be used to generate an event in Sunguide to be confirmed by an operator as part of the IDS process. Business rules will include being, reasonably, at a fixed location, being within the service area of a TMC, being within the operating hours of Road Rangers for that section of roadway. A GUI for the configuration of the Crowd Sourced Incident with login verification will be created. If the business rules are not met the GUI with the means to access the request will still be available but greyed out with the reason displayed.

1.2.2.8.2 Multimodal Route Guidance

The Route and Mode Choice Engine will be incorporated into FL511.

1.2.3 Transit Kiosk Software

The transit kiosk software will provide an interface into the route and mode choice engine application deployed on transit kiosk hardware.

1.3 Assumptions and Dependencies

Several systems, technology, and institutional assumptions were made in the development of the minimum technical requirements. These assumptions may be improved upon through the development of the PROJECT.

1.3.1 Assumptions for Route and Mode Choice Application Engine

Necessary third-party APIs will be made available for utilization to the VENDOR.

Third-party agency APIs will be made available and remain maintained and operational at all times for utilization by the VENDOR.

All necessary data streams from SunGuide APIs will be made available and remain active throughout the Project for utilization by the VENDOR.

A-22

1.3.2 Assumptions for FL511 Mobile App Enhancement

Users will provide FL511 Mobile App with necessary permissions to access internal phone hardware.

RSUs will be deployed within the project area and ready for utilization prior to the Project initialization.

The FL511 Mobile App will have access to all required device level data and functionality. Examples of device level data and functionality include geolocation, vibration, and camera access.

1.3.3 Assumptions for Transit Kiosk Software

VENDOR shall coordinate with the DEPARTMENT to ensure software is coordinated with, and compatible with, the anticipated hardware platform to be deployed.

Transit Kiosks will be provided by PedSafe/Greenway Deployment (FPID 440821-1-52-01) project. For additional information including hardware specifications, contact the DEPARTMENT.

1.3.4 Statutory Project Management and Cyber Security Standards

Chapter 74-1 F.A.C., Florida Information Technology Project Management and Oversight Standards

Governed by the Agency for State Technology (AST), Chapter 74-1 F.A.C., Florida Information Technology Project Management and Oversight Standards, establishes project management principles that State Agencies are required to follow when implementing information technology projects. The Department must adhere to the State project management standards and ensure that all project documentation created by the Vendor, Department, or in collaboration, is developed and maintained in accordance with Chapter 74-1 F.A.C. The Vendor must be familiar with the State project management standards and be prepared to work with the Department to satisfy all requirements. It is important for the Vendor to recognize that documentation, monitoring, or reporting requirements could change mid-project, based on the project’s AST Risk and Complexity Assessment, outlined in 74-1.002. The Vendor must be adaptable to changes required by Chapter 74-1 F.A.C., without increasing cost to the Department.

Chapter 74-2 F.A.C., Information Technology Security

Governed by the Agency for State Technology (AST), Chapter 74-2 F.A.C., Information Technology Security, also known as the Florida Cybersecurity Standards (FCS), establishes cybersecurity standards for information technology (IT) resources. State Agencies are required to follow these standards in the management and operations of state IT resources. The Department must adhere with the Florida Cybersecurity Standards for all Information Technology projects

A-23 created by the Vendor, Department, or in collaboration. The Vendor must be familiar with the State cybersecurity standards and be prepared to work with the Department to satisfy all requirements.

o Florida Cybersecurity Standards, 74-2 F.A.C. Section 74-2.002 (4) requires that agencies determine the potential security impact of all systems. If the system if found to have a categorization of moderate impact or higher, a system security plan (SSP) will be required. The SSP must address the security setup of the system, ensuring that required security controls are in place and listing the required information described in Section 74-2.003(5)(g)(4). The SSP must be submitted and approved by the FDOT Information Security Manager (ISM).

An SSP template is available from the FDOT ISM.

1.4 Technical Requirements

Functional requirements that the system must meet are included in the attached Exhibit “C” Minimum Technical Requirements. It is the responsibility of the VENDOR to understand all requirements in the requirements documentation and inferred in the descriptions within the Scope of Services. The VENDOR shall be responsible for developing a Final Requirements Specification once the requirements walkthrough is completed with the DEPARTMENT.

The Requirements Specification has been developed by the DEPARTMENT and will be updated to include negotiation conclusions. Exhibit “C” of this document lists each requirement and identifies the responsible party.

DEPARTMENT will have the responsibility for procuring all hardware and COTS software identified by the VENDOR as needed for deployment and operation and maintenance of the developed software. The VENDOR shall recommend minimum hardware and software requirements to support the PROJECT.

1.5 Software Ownership

The DEPARTMENT shall have full ownership of any works of authorship, inventions, improvements, ideas, data processes, computer software programs, source code, source code documentation, drawings, designs, specifications, documents, traffic models, and discoveries (hereafter called intellectual property) conceived, created, or furnished under this CONTRACT, with no rights of ownership to the VENDOR. The VENDOR shall fully and promptly disclose to the DEPARTMENT all intellectual property conceived, created, or furnished under this CONTRACT. The VENDOR hereby assigns to the DEPARTMENT the sole and exclusive right, title, and interest in and to all intellectual property conceived, created, or furnished under this CONTRACT, without further consideration. This CONTRACT shall operate as an irrevocable assignment by the VENDOR to the DEPARTMENT, including all rights therein in perpetuity. The VENDOR shall not copyright or patent any intellectual property conceived, created, or furnished under this CONTRACT without the express written consent of the DEPARTMENT. The VENDOR agrees to execute and deliver all documents requested by the DEPARTMENT to affect the assignment of intellectual property to the DEPARTMENT or the registration or

A-24 confirmation of the DEPARTMENT’s rights in or to intellectual property under the terms of this CONTRACT.

The foregoing shall not apply to any preexisting software, or other work of authorship used by the VENDOR, to create a deliverable, but which exists as a work independent of the deliverable, unless the preexisting software or work was developed by the VENDOR pursuant to a previous contract with the DEPARTMENT or a purchase of the intellectual property by the DEPARTMENT under the contract.

Any preexisting software, or other work of authorship used by the VENDOR, to create a deliverable, or integrated into the deliverable, shall require the written approval of the DEPARTMENT prior to use. Insofar as preexisting software is concerned, that intellectual property remains that of the commercial software publisher; however, all license to use that software, relative to this PROJECT will be irrevocably and perpetually conferred to the DEPARTMENT. Furthermore, the preexisting software owned by the VENDOR and licensed to the DEPARTMENT shall be placed in escrow. The Vendor shall maintain in escrow a copy of the source code for the preexisting software. With each new release of the software provided to the Department, the Vendor shall maintain the updated source code in escrow. In the event the Vendor files for bankruptcy or ceases operations for any reason, the Department shall promptly be provided the current source code in escrow.

The Department will only use the source code to support the licensed software subject to the same nondisclosure provisions of this Contract.

At all times, the DEPARTMENT shall have access to the intellectual property owned by the DEPARTMENT and developed pursuant to this CONTRACT or a previous contract with the DEPARTMENT including source code and its documentation for the purpose of modification, enhancement, or distribution. The DEPARTMENT shall distribute the software to state agencies as required and may distribute the software to other states.

The VENDOR also agrees to execute all papers necessary for the DEPARTMENT to protect their ownership of the rights in the work products.

The VENDOR shall be responsible for the preservation of any and all such work products prior to transmittal to DEPARTMENT and shall replace any such work products that are lost, destroyed, or damaged while in its possession without additional cost to the

DEPARTMENT.

The current FL511 backend and FL511 App has been developed under a separate Contract, and corresponding intellectual property conceived, created, or furnished will not be included in this CONTRACT .

A-25

2 Applicable Documents

Some documents named or referenced throughout this Scope of Services and subsequent Exhibits are include, but are not limited to, the following:

Connecting the East Orlando Communities, Volume 1 – Technical Application (ATCMTD Grant Application)

Concept of Operations for: PedSafe Greenway Deployment

System and Subsystem Requirements for: Study for Route and Mode Choice Application Development

Society of Automotive Engineers (SAE) Standard J2735 – V2X Communications Message Set Dictionary (latest version)

Business Systems Support Office’s Web Application Standards

FDOT District 5 - Installation and Deployment Guide Template

FDOT District 5 – Connected & Autonomous Vehicle Program Resources

FDOT Systems Engineering Management Plan templates, including:

o Project Systems Engineering Management Plan Template o Software Development Plan Template o System Test Template o Test Procedures Template o Test Report Template

In the event of a conflict between the documents referenced herein and the contents of this Scope of Services, this document shall be considered the superseding requirement.

DocuSign Envelope ID: AD02621D-C646-4549-B301-5D947A817955 http://www.cflsmartroads.com/projects/design/future/FDOT-2017-ATCMTD-Vol-1.pdf https://www.sae.org/standards/content/j2735_200911/ https://www.sae.org/standards/content/j2735_200911/ http://www.cflsmartroads.com/projects/technical_docs.html http://www.cflsmartroads.com/projects/CVAV.html http://www.fdot.gov/traffic/its/projects_deploy/semp.shtm

A-26

3 Scope of Work

The VENDOR is responsible for providing a detailed scope of work in a project work plan document that meets the requirements for managing the project contained in this section of the scope of services.

The scope of work described in this section is a general guide and is not intended to be a complete list of all the work necessary to complete the project. One of the early deliverables by the VENDOR will be a detailed work plan. The scope of work contains work tasks that are necessary to meet the DEPARTMENT’s project requirements.

The selected VENDOR shall implement a comprehensive, fully integrated suite of software systems covering the general functional areas and specific requirements detailed in the Requirements Specification.

3.1 DEPARTMENT Responsibilities

The DEPARTMENT will be responsible to:

Designate a project manager.

Form a project steering committee.

Provide all existing documentation in the DEPARTMENT’s possession on the equipment and systems required to interface with each of the proposed software systems.

Coordinate the documentation for interfaces with other projects. Acquire an Interface Control Document from other projects, if required.

Review, Comment, and Approve the documentation and other deliverables.

Monitor the PROJECT’s implementation progress and schedule.

Provide facility access and staff support.

Participate in requirements reviews, integration testing, acceptance testing, implementation, training, and status meetings.

Provide the VENDOR with all information regarding all software packages available.

Provide hardware, commercial software, and communication infrastructure.

Provide all data interface APIs and Static Data required for the proposed software systems.

Create and maintain a project SharePoint site during the contract period to:

o Update project progress o Post documentation o Post meeting agendas, minutes, and action items

A-27

Provide an integration testbed environment for testing all software functions.

Performance, security, and other system functions will be tested in a controlled pre-production environment during the system test phase which will mirror the production environment.

Provide test systems and simulators to support the unit and system testing of the proposed software systems, as appropriate.

3.2 VENDOR’s General Obligations

The VENDOR and subcontractors will be responsible to:

Designate a project manager and key project team members.

Provide a resource loaded Microsoft Project Schedule.

Provide detailed software design and integration with complete software system design documentation.

Complete all activities required, including unforeseen work based on high-level project needs, including future findings related to identified assumptions necessary to complete the software system as identified below.

Identify the hardware requirements for system integration and testing, so the DEPARTMENT can furnish the computer-related equipment and networks.

Schedule and Coordinate with the DEPARTMENT’s project manager to ensure that adequate network infrastructure and data links are provided by the

DEPARTMENT.

Integrate software into an operational system.

Test functional capabilities of the system.

Provide network and workstation security.

Pack, ship, insure, and deliver all parts; training and maintenance materials;

submittals; and documentation to the DEPARTMENT, as directed.

Implement a rigorous, structured integration methodology.

Implement a rigorous configuration management system.

Implement and execute a formal software development process.

Complete documentation for all hardware (as applicable) and software training, including a complete operator/administrator manual; user and service documentation; and the drawings.

Train DEPARTMENT-designated personnel.

Project management and control including attending periodic progress meetings with and reporting to the DEPARTMENT staff.

Maintenance and support of the system for the duration of the contract.

A-28

Standard warranty services for the duration of the contract.

Post integration and testing maintenance support for delivered software within the contract period, renewable in one (1) year increments.

Provide a list of licenses for public domain software used in the CONTRACT before the project award. The VENDOR shall provide the DEPARTMENT with related licenses.

Provide a watchdog system monitoring component which monitors 24/7 and scans for software failure, and provides read-only reports of performance outages and network activity.

3.3 Other Participants’ Obligations

Other agencies and contractors shall participate in the PedSafe/Greenway Software Development effort in the following manner:

Contractors implementing TSM&O related systems shall work with the VENDOR to provide existing system design documents and implementations in support of the PedSafe/Greenway Software Development Package and environment.

FDOT Offices and other Agencies providing data streams and data sets shall make these data resources and associated metadata and documentation available to the VENDOR.

3.4…