CN-550000-BEA16-00120000.pdf

STATE OF FLORIDA DEPARTMENT OF TRANSPORTATION

TASK WORK ORDER FOR PROFESSIONAL SERVICES

375-030-25

PROCUREMENT

06/17

Consultant:

Address:

Date:

7/21/2025

*Limiting or Estimating/Budgeted Amount.

Distribution:

Task Work Order No.:

Contract No.: Payment FM No.:

BEA16 435445-1-82-04

$421,740.00

(name) (title) Signature

James S. Stroz, Jr., P.E. District Traffic Operations Engineer

Other Notes:

An independent assessment of the staff hours and quantities for the proposed services has been performed, and found to be fair, reasonable, and competitive.

(LS2) Lump sum paid based on % of completion

Page 1 Total

Page 2 thru 6 Subtotal

Total

Scope of Work attached

VANASSE HANGEN BRUSTLIN, INC.

225 E. Robinson Street Suite 300 Orlando, FL 32801

(To be entered upon execution of T.W.O.)

Brief Task Description:

In accordance with the above referenced contract, you are authorized to perform the tasks detailed in attached Exhibit A (Scope of Services).

Compensation elements are as follows:

Element Description Amount Estimate/LimitMethod of Compensation

The total amount or the limiting amount of the compensation will be:

All services required under this Task Work Order will be completed on or before:

$12,880.00

$12,880.00 Limit

Cloud Based API Requirement Documentation

Signature

SE Regional Manager

$12,880.00

$0.00

(name) (title)

David Mulholland

$12,880.00

Payment will be authorized based on hours submitted for each monthly progress estimate and is defined in ATTACHMENT "B".

Total authorizations to date (including this one):

Departmental Approval:

Consultant Acceptance:

DocuSign Envelope ID: 7ADDA68C-F4FC-4471-9A49-C788202C33DE

12/20/2021 | 8:36 AM EST

Total Pay Item Quantity Unit Price Total

1 0 HR 131.00$ -$

1 0 HR 98.00$ -$

1 0 HR 95.00$ -$

1 46 HR 160.00$ 7,360.00$

1 46 HR 120.00$ 5,520.00$

Total Hours = 92 Task Work Order Total = 12,880.00$

Description

BEA16 - Task Work Order 10 Details

Junior Programmer

Traffic Data Scientist Junior Traffic Data Scientist Junior Visualization Specialist Programmer

ATTACHMENT A

SCOPE OF SERVICES

ITS Software Integration & Maintenance Services for the SunStore and Future Deployments

Financial Project ID No. 435445-1-82-04

Contract BEA16

District Five

Cloud Based API Requirement Documentation

A. SCOPE OF SERVICE

Vanasse Hangen Brustlin (VHB) will provide the following services related to identifying and documenting

Application Programming Interface (API) requirements that could be provided from an external cloud big data environment, such as FDOT Central Office’s CV2X platform, which are needed to support performance measure use and support for the Florida Department of Transportation (FDOT) District 5

(District).

PROJECT GOALS AND OBJECTIVES

The purpose of this project to provide the District with documented API requirements that could be provided from an external environment to the District to reduce post processing and provide the District a mechanism to directly access and use data in this environment for reporting, performance measure calculation, or other purposes within the Districts RTMC Map and SunStore Data Picker. It is anticipated that the Central Office CV2X platform will provide the District with access to API’s capable of delivering low latency statewide data and metrics. Under this task these technical requirements will be documented to provide Central Office with a clear understanding of what is required to allow the CV2X or other cloud system to fulfill the District needs.

B. TASKS

TASK 1: Cloud Based API Requirement Documentation

Under this task, VHB will document and identify the technical requirements that are required from external APIs to provide the District with data and performance measures to successfully meet the District’s needs. The technical requirements outlined under this task will focus on currently implemented APIs to provide support to existing applications, scripts, and data needs such District 5’s RTMC Map and the SunStore Data Picker.

Documented API technical requirements will include:

- Parameter requirements of APIs to perform requests. These parameters may include o Date and time ranges, examples include:

▪ January 6th, 2021 – March 2nd, 2021 6AM to 9 AM

▪ {20210701T08:00:00.000, 20210701T10:00:00.000} o Day of Week, examples include:

▪ Only Monday’s over a three month period

▪ {Tuesday, Wednesday, Thursday} o Descriptive Location Name, names, or arrays such as:

▪ Roadway ID: 75000000

▪ HERE TMCs: {102+8754, 102-8753, 102P8754}

▪ Bounding box: {-81.5, 35, -81.45, 34.4}

▪ County: {“Orange”} o Specific Attributes or query terms

▪ Crash Code: 02

▪ “District 5”

- Performance measure calculation and data aggregation functional workflows used to query the data from database storage (relational and non-relational). These specialized APIs deliver additional functions or aggregations which are performed server side to reduce the load of the client-side application or script. Examples may include:

o Combining multiple API responses into a single array for response, such as displaying trend data on a specific roadway over a period of time o Summarizing API data into aggregate buckets such as total fatalities occurring on a roadway or average speed on a segment by 15 minute increments o Creating additional performance measures from returned API, for example

▪ Using average speed on a roadway with a known length to determine travel time

▪ Calculating crash rate based on count of crashes on a roadway with known AADT

- Data conflation workflows utilized by API to search, query, and join spatial and tabular data from different sources. Examples may include o Identifying Signal 4 crash events within a proximity to HERE TMC segmentation o Identifying HERE TMC segments occurring within a known distance of a roadway’s beginning and ending mile posts as identified by RCI limits

- The minimal acceptable latency thresholds of data and metrics from source to end use

(application or script). For example o HERE data availability for use in the TMC within 5 minutes of update o Nightly Updates of Signal 4 crash data o Response time of specialized API’s

- Response format that is needed by the District o The District currently uses a JSON format for responses

These technical requirements are intended to display the workflow needed from an external API source and are not intended to provide solutions for how the external environment will accept the incoming parameters or perform calculations.

DELIVERABLES:

- Documentation of API requirements to support District Initiatives from external environment

TASK 2: Meeting and Communication

In task 2, VHB will provide support to the District in communication and meetings with the District, Central Office or other identified stakeholders to discuss and document processes, procedures, and requirements for external APIs to provide data and performance measures via API restful end points in a format that can be readily queried by the District.

It is expected that up to six (6) meetings may require attendance from varying technical staff to assist in communicating the District’s needs and providing technical guidance on the requirements and capabilities of APIs documented under Task 1. Topics for discussion may include but are not limited to:

- What will be the latency of data received via the CV2X platform for each data set

- Are additional cleaning or normalization processes planned for CV2X data

- What are the hot/cold storage plans for data that may requested

- What is the workflow for the District to request new APIs or modify existing APIs

- What procedures will be used for alerting the District of planned or unexpected downtime

DELIVERABLES:

- Attendance at meetings

- Meeting notes

D. Services to be Provided All required hardware, network connectivity and licensed software.

E. PROJECT SCHEDULE

The project is anticipated to be completed by March 31, 2021 with individual tasks being completed as identified in the table below.

Dec 2021 Jan 2022 Feb 2022 Mar 2022

TWO 1: Documentation

TWO 2: Meetings

F. FEE ESTIMATE

Details of the estimated man-hours, out of pocket expenses, and fees for this task assignment are transmitted separately.

Work Order No. 10

JOB CLASSIFICATION MANHOURS SALARY

TOTAL

SALARIES

Financial ID No.: 435445-1-82-04 Traffic Data Scientist 0 131.00$ -$ (Agreement) Junior Traffic Data Scientist 0 $98.00 -$

Visualization Specialist 0 $102.00 -$ Financial ID No. Junior Visualization Specialist 0 $95.00 -$

N/A Programmer 46 $160.00 7,360.00$ (Services) Junior Programmer 46 $120.00 5,520.00$

Loaded Salary Total - Office Overhead 92 12,880.00$

BRIEF DESCRIPTION

Loaded Salary Total - Field Overhead 0 Work Order No. 10

FEE ESTIMATE (Computations)

Total Loaded Salary Costs - Office Costs 12,880.00$

(a) Office Overhead @ 0.00%

NAME OF CONSULTANT (b) Operating Margin @ 0.00%

(c) FCCM @ 0.00%

Vanasse Hangen Brustlin (VHB) (d) Expenses @ 0.00%

Subtotal Subconsultant - Office Costs 12,880.00$

Total Loaded Salary Costs - Field Costs

(a) Field Overhead @ 0.00%

(b) Operating Margin @ 0.00%

(c) FCCM @ 0.00%

(d) Expenses @ 0.00% Subtotal Subconsultant - Field Costs

TOTAL UPSET LIMIT FEE 12,880.00$

Cloud Based API Requirement Documentation

A-T-T-A-C-H-M-E-N-T "B"

GENERAL ENGINEERING CONSULTANT

WORK ACTIVITY

Traffic Data

Scientist Junior Traffic Data Scientist

Visualization Specialist

Junior Visualization

Specialist Programmer Junior

Programmer TOTAL 1 Cloud Based API Requirement Documentation 0 30 38 68 2 Meeting and Communication 16 8 24

GRAND TOTAL 0 0 0 0 46 46 92

API Parameters 4 4 API performance measure & Conflation 4 8 latency and response 4 4 Document writing (All) 12 16 FDOT feedback 2 Document finalizing 6 4

TOTAL TASK 1 30 38

Meeting (6 meetings Brian, Keith, Josie) 16 8

MANHOUR ESTIMATE SHEET

Financial ID No.: 435445-1-82-04

General Engineering Consultant Services

Vanasse Hangen Brustlin (VHB)

Work Order No. 10

Cloud Based API Requirement Documentation