CN-550000-BED12-L0010000.pdf

FLORIDA DEPARTMENT OF TRANSPORTATION

STANDARD WRITTEN AGREEMENT

375-040-07

PROCUREMENT

03/17

MODIFICATION # 1

Agreement No. BED12

Financial Project I.D. 417738-2-93-02

Vendor No. F814806310-001

Procurement No. DOT-RFP-22-5005-AADC

DMS Catalog Class No. 46161500

Renewal # 1

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

DEPARTMENT OF TRANSPORTATION, hereinafter called the "Department" and Traffop Corp. , duly authorized to conduct business in the State of Florida, hereinafter called the "Vendor."

WITNESSETH:

WHEREAS, the Department and the Vendor heretofore on 2/10/2022 ,entered into an agreement, hereinafter called the

"Original Agreement," whereby the Department retained the Vendor to furnish certain services in connection with District Five

Automated Approach and Detector Channel Prediction and Configuration Service ; and

WHEREAS, said Original Agreement has a renewal option that provides for a renewal if mutually agreed to by both parties and subject to the same terms and conditions of the Original Agreement and any written amendments signed by the parties;

NOW, THEREFORE, this Agreement witnesseth that for and in consideration of the mutual benefits to flow each to the other, the parties agree as follows:

1. Said Original Agreement is renewed for a period beginning 4/11/2023 and ending 4/10/2024 .

2. Upon execution of this Agreement, the Department has made available additional funding in the amount of

$177,283.00 . This brings the total available for the Agreement to $374,603.00

3. Furthermore, per Original Agreement Exhibit "B," Method of Compensation, Section 2.0, Optional Services are being added in accordance with the attached Exhibit "A," Scope of Services.

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: A5E8F011-08AC-4C90-980F-6B3C41B00A13

9/14/2022 | 9:05 AM EDT

STANDARD WRITTEN AGREEMENT

375-040-07

PROCUREMENT

03/17

Traffop Corp.

STATE OF FLORIDA

DEPARTMENT OF TRANSPORTATION

Name of Vendor

BY: BY:

Authorized Signature

Kurtis McBride 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

CEO

SCOPE OF SERVICES

Supplemental Amendment #1

CONTRACT BED12

Financial Project ID: 417738-2-93-02

Description: District Five Automated Approach and Detector Channel Prediction and Configuration Service County: District-Wide

1. PURPOSE

The Florida Department of Transportation (DEPARTMENT) hosts its own local ATSPM (Automated Traffic Signal Performance Measures) instance.

(http://atspm.cflsmartroads.com/atspm) which was connected to approximately 700 signal and has been expanded to +900 signals. The system existing system provided reliable service for the DEPARTMENT prior to expansion of the number of signals. In addition to recent reliability due to scale the local ATSPM system requires significant oversite and staff resources to maintain functionality across the multiple controller vendors and traffic controller firmware modifications.

After the success of the initial deployment and requirements testing of the Automated Approach and Detector Channel Prediction and Configuration Service (AADC Service), the decision was made to perform a proof-of-concept deployment for direct retrieval of data for three intersections. This proof-of-concept was used to demonstrate the reliable retrieval of data and uncover any necessary modifications to expand the proof-of-concept from 3 intersections to 100 and beyond.

The purpose of this amendment is to make necessary modifications to the AADC Service to make direct ATSPM controller data retrieval a part of the Service in order to reduce and eliminate the obstacles to exchanging ATSPM data between the DEPARTMENT and other entities. These modifications will save the DEPARTMENT oversite and staff resources while maintaining interoperability between the multiple traffic signal controllers used throughout the District.

2. BACKGROUND

The existing high-level architecture of the DEPARTMENT ATSPM system, that is used both in the operations center and as a data provider to other downstream systems such as the Regional Integrated Corridor Management Software (R-ICMS) and others can be seen in (Figure 1).

DocuSign Envelope ID: 13C440E3-0503-46B5-A8BE-AFE755806DCC

A-1

Exhibit "A" http://atspm.cflsmartroads.com/atspm

Figure 1. The modified UDOT system used to retrieve and disseminate ATSPM data

ATSPM data is collected from controllers in its original form and disseminated to downstream systems which then perform decoding of the controller files. Data on the controllers is stored in one-minute files. For Intelight controllers which do not have files, those files are created when data is retrieved. The ability to retrieve one-minute files and pass them further downstream is essential due to the possible near three-minute predictions in the downstream systems.

Two primary challenges with the current setup were the impetus for the AADC Service proof of concept; the first one is that as the number of intersections has grown to 900+ it has put stress on the existing system and the reliability of data retrieval. The second challenge is that downstream systems are supposed to decode the raw controller data and each controller has a different format. This puts a heavy burden on staff for custom

DocuSign Envelope ID: 13C440E3-0503-46B5-A8BE-AFE755806DCC

A-2 solutions to provide data to the downstream systems and complicates the decoding process.

3. SCOPE

Task 1:

Provide optimized transfer of high-resolution files from the controller

Historically the speed at which the files are picked up from the controller has not been the primary concern in other agencies ATSPM systems. Traffop’s process that gets the data from the controller goes through every single file on the controller and compares it with the files already retrieved in the previous runs. This process was created with reliability and not efficiency in mind. It tries to ensure that all the files are always retrieved. In the case of the DEPARTMENT, there are many more files on the controllers since one-minute files are used (1,440 files in 24 hours versus 96 when 15-minute files are used). In this task, Traffop developers would optimize this process for speed and retrieve only the last few files since the last successful retrieval. This will significantly reduce the time that it takes to perform the retrieval process.

Use existing Internal API that can support 50k calls per day.

Expanding the proof-of-concept deployment from the initial three intersections to one hundred intersections to further test the viability of Traffop as a retrieval and distribution system is a critical next step. This expansion should be accomplished in the shortest amount of time. To achieve that the intermediary step of using an existing internal API for the next ninety-seven signals is proposed. The additional intersections would be added to the system to directly communicate with Traffop on-premise service and the internal API would be accessed for all one hundred signals at once in three minutes intervals by the newly built file unification and distribution process (this process is being built in parallel to Traffop deployment and is handled by a third party).

Task 2:

Distribute pickup of files between multiple on-premises services

Another capability necessary for scalable and fast retrieval is distributing the task of retrieval between multiple on-premise services. This process is also called scaling out.

For example, if we used one on-premise service to retrieve high-resolution data from 1,000 signals it would perform that process slower than five different on-premise services retrieving data from 200 signals each. Traffop’s developers would modify Traffop’s on-premise service and the corresponding cloud components to distribute signals between multiple on-premise services.

DocuSign Envelope ID: 13C440E3-0503-46B5-A8BE-AFE755806DCC

A-3

Implement an Open API that can support 4M calls per day.

To achieve the ultimate goal of fast, reliable, and automated transfer of high-resolution signal event data between Traffop’s ATSPM software and third parties Traffop would need to modify the existing API with the implementation of a dedicated open third-party application programming interface (API). This new architecture would allow for the new file standardization and distribution process to make API calls from Traffop cloud server and further distribute them to third party systems (Figure 2).

The requirements for this interface are as follows:

1. Ensure all data and communication between API and third-party is safe and secure.

2. Provide protection and safeguards for the safety of the agency’s data and configuration (roles, permissions, read-only, etc).

3. Ensure seamless integration from the start of data exchange, to minimize breaking changes required at the later stage after creating cross-application dependencies.

4. Limit abuse or overuse of cloud resources (additional unnecessary computing and storage access costs).

5. Gain insights for the agency with accurate third-party data usage of APIs.

6. Provide easy-to-access documentation for use of the proposed API.

The new third-party API will support the following:

1. Streamlined authentication/key request process.

2. Provide a rate-limiting mechanism.

3. Provide a count tracking mechanism.

4. Add the ability to assign user roles, groups, and permissions.

5. Ensure API conventions.

6. Determine public/private endpoints and create proper documentation.

7. Create a mechanism for users to see API statistics usage.

8. Upscale backend services and add cashing to handle an expected 4 million API calls per day.

DocuSign Envelope ID: 13C440E3-0503-46B5-A8BE-AFE755806DCC

A-4

Figure 2. The new architecture for retrieval and dissemination of ATSPM data

Task 3:

900 Signal Service for one-year At the completion of Tasks 1 and Tasks 2 the remainder of the Department’s ATSPM signalized intersections will be included into the service for a period of one year. This task will be an extension of the contract for year for a total of 900 signals in the system.

4. IMPLEMENTATION SCHEDULE AND MILESTONE DELIVERABLES

Milestone 1: This would involve implementing Task 1

The effort for this stage would be 30 hours and the expected timeframe for completion would be up to 3 weeks.

Deliverables for Milestone 1:

- Optimization of file transfer process to support the DEPARTMENT’s 1-minute file structure.

- Screen Shots showing successful direct connection and high-resolution data completeness from the AADC Service notification system.

- Internal API enhancement to support 50k calls per day

A-5

Milestone 2: This would involve implementing Task 2

The effort for this stage would be 525 hours and the expected timeframe for completion would be up to 6 months.

Deliverables for Milestone 2:

- On-Premise services design specifications for deployment on the DEPARTMENT’s servers

- Configuration of On-Premise services

- Implementation of the Open API that can support 4M calls per day

- Documentation on the Open API

- API Key

- Screen shots of API statistics usage mechanism in the Service

Schedule:

The schedule for these enhancements will begin at the execution of Letter of Authorization #1 by the DEPARTMENT and Vendor.

Milestone 1

Completion: October 9, 2022

Milestone 2

Completion: April 9, 2023

Milestone 3

Begin Monthly Service of 800 Additional Signals: April 10, 2023

End Monthly Services of 800 Additional Signals: April 9, 2024

5. LENGTH OF SERVICES

The Services requested under this Supplemental Amendment are to be completed by such time as will support the Department schedule of April 9, 2024. The existing contract time will be extended by one year to support this schedule.

6. SUMMARY OF COMPENSATION

Compensation for these software features modifications and/or enhancements is in based on Table 3 of the Bid Price Proposal Form for the BED12 contract to be paid upon completion of milestone.

DocuSign Envelope ID: 13C440E3-0503-46B5-A8BE-AFE755806DCC

A-6

A-7

FUNDS APPROVAL

BED12

9/8/2022

CONTRACT INFORMATION

FUNDS APPROVAL INFORMATION

FUNDS APPROVED/REVIEWED FOR ROBIN M. NAITOVE, CPA, COMPTROLLER ON 9/8/2022

Action: Renewal

Reviewed or Approved: APPROVED

Organization Code: 55054030511

Expansion Option: A2

Object Code: 132748

Amount: $177,283.00

Financial Project: 41773829302

Work Activity (FCT): 683

CFDA:

Fiscal Year: 2023

Budget Entity: 55150200

Category/Category Year: 088866/23

Amendment ID: L001

Sequence: 00

User Assigned ID: AMD 1

Enc Line (6s)/Status: 0002/04

Total Amount: $177,283.00

Contract: BED12

Contract Type: B1 - OTHER CONTRACTUAL SERVICE (OTHER CS)

Vendor Name: TRAFFOP CORP

Vendor ID: F814806310001

Beginning Date of This Agreement: 02/10/2022

Ending Date of This Agreement: 04/02/2024

Contract Total/Budgetary Ceiling: bc = $374,603.00

Method of Procurement: B - REQUEST FOR PROPOSAL (287.057,F.S.)

Description: District Five Automated Approach and Detector Channel Prediction Service

Page1 of 1

To: Jennifer.Allcock@dot.state.fl.us

WITNESSETH: