CN-550000-BED12-S0010000.pdf

FLORIDA DEPARTMENT OF TRANSPORTATION

STANDARD WRITTEN AGREEMENT

375-040-07

PROCUREMENT

03/17

MODIFICATION # 2

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

Amendment # 2

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, the Department has determined it necessary to amend the agreement to Remove Task 2 of Amendment 1, and make modifications to the AADC Service on Premise process , NOW, THEREFORE, this Agreement witnesseth the following amendment is made;

Task 2 "Distribute pickup of files between multiple on-premises services," identified in Amendment 1, Exhibit "A," is hereby removed.

Amendment 2, Task 1, "Modification of File Retrieval from DEPARTMENT Kafka topic," is being added in accordance with the attached "Scope of Services."

Due to the removal of Amendment 1 Task 2, the contract total is reduced by $78,415.00 .

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.

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

DocuSign Envelope ID: AAD89658-8DF5-4D53-A15E-D946381A0655

CEO

01/26/2023 | 11:17 AM EST

SCOPE OF SERVICES

Supplemental Amendment #2

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 +900 signals. The DEPARTMENT has been experiencing 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. The

DEPARTMENT executed Supplemental Amendment #1, based on this to directly connect the AADC Service for data retrieval. Since executing Supplemental Amendment

#1, the DEPARTMENT has been piloting direct retrieval of raw data locally and use of kafka topics as a replacement to the drop folder file sharing process downstream systems were being fed data with.

The purpose of this amendment is to remove Supplemental Amendment #1 Task #2 and to make necessary modifications to the AADC Service On Premise process to allow data retrieval by the AADC Service from the DEPARTMENT kafka topic. These modifications will save the DEPARTMENT oversite and staff resources while speeding up the distribution of raw event code data to downstream systems.

2. SCOPE

Contract BED12 Supplemental #1 “Task #2 distribute pick up of files between multiple on-premise services” Scope to be removed

BED12 SA#1 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: EDEFE342-F831-449B-A5BD-C72C3C4959ACDocuSign Envelope ID: AAD89658-8DF5-4D53-A15E-D946381A0655 http://atspm.cflsmartroads.com/atspm

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: EDEFE342-F831-449B-A5BD-C72C3C4959ACDocuSign Envelope ID: AAD89658-8DF5-4D53-A15E-D946381A0655

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

BED12 Supplemental Amendment #2 Scope to Be Added

BED12 SA#2 Task 1:

Modification of File Retrieval from DEPARTMENT Kafka topic

The Vendor shall enhance the on-premise file retrieval process to use the DEPARTMENT’s

Kafka process topic for high resolution event code data. The high-resolution data will be exported from Kafka into CSV files by another process developed by the department. The CSV files will be delivered into a drop folder from which on-premise service will retrieve the data and further process it. Under scope of this task Traffop’s development team will develop reading of the Kafka exported CSV file and test the reliability of the new process. This shall be developed, deployed, and tested on up to 100 newly selected intersections for the purpose of bench testing the new data retrieval process. This will bring the total AADC Service intersections during SA#2

Task #1 implementation time to up to 200 intersections. The new on-premise file retrieve process from kafka shall be developed to meet the Service Scalability requirements of a minimum of 2000 signals outlined in Section A. Automated Approach and Detector Channel

Service Requirements 1. Deployment Size and Scalability Requirements of the BED12 contract.

DocuSign Envelope ID: EDEFE342-F831-449B-A5BD-C72C3C4959ACDocuSign Envelope ID: AAD89658-8DF5-4D53-A15E-D946381A0655

3. IMPLEMENTATION SCHEDULE AND MILESTONE DELIVERABLES

Milestone 1: This would involve implementing Task 1

The effort for this stage would be 80 hours development and the expected timeframe for the software enhancement completion would be up to 2 weeks over the course of 1 month. Once the process has been developed, the initial 1-100 proof of concept intersections will be transitioned over to the new file retrieval process. After this transition the new process will be monitored by the Department for up to the day before the “Begin Monthly Service of 800

Additional Signals: April 10, 2023” milestone date per Contract BED12 Supplemental

Amendment #1 Task #3.

- Connection of the Service to use the DEPARTMENT’s Kafka topic for high resolution event code data.

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

Schedule:

The schedule for these enhancements will begin at the execution of this amendment by the DEPARTMENT and Vendor.

Milestone 1

- Begin Monthly Service of 100 Additional Signals February 1, 2023

- Completion of Connection of the AADC Service to use the DEPARTMENT’s Kafka topic for high resolution event code data and transition of the initial 1-100 signals to the kafka retrieval method - March 1, 2023

- Monitor AADC Service connection to Kafka – April 9, 2023

4. LENGTH OF SERVICES

The existing contract time of April 10, 2024 will not be impacted by this amendment.

5. SUMMARY OF COMPENSATION

Compensation for these software features modifications and/or enhancements is based on Table 3 of the Bid Price Proposal Form for the BED12 contract to be paid upon completion of milestone. Due to the removal of SA#1 Task #2, the overall compensation of the BED12 contract is to be reduced by $78,415.00.

DocuSign Envelope ID: EDEFE342-F831-449B-A5BD-C72C3C4959ACDocuSign Envelope ID: AAD89658-8DF5-4D53-A15E-D946381A0655

Summary BED12 Supplemental Amendment #2 Modifications to Compensation

Milestone Table 3 - Optional Services Item Unit Unit Cost Quantity Total

BED12 Contract Encumbered Balance January 9, 2023 349,603.00$

Remove BED12 SA #1

Task #2 Milestone 2

Automated Approach and Detector

Channel Prediction Service modification or enahnacment

Hourly Rate $185 525 ($97,125)

Automated Approach and Detector

Channel Prediction Service (each additional 100 signal batches beyond initial 100 signals) Signals 101-200

February 1, 2023 - April 9, 2023

Monthly $1,700 2.30 $3,910

Automated Approach and Detector

Channel Prediction Service modification or enahnacment

Hourly Rate $185 80 $14,800

($78,415)Total Cost Impact

Add BED12

Supplemental

Amendment #2

Milestone 1

DocuSign Envelope ID: EDEFE342-F831-449B-A5BD-C72C3C4959ACDocuSign Envelope ID: AAD89658-8DF5-4D53-A15E-D946381A0655