INRIX_Proposal_for_Ohio_DOT_For_Speed_Data_Service_521B-26_20250915__1_.pdf

INRIX Confidential for Ohio Department of Transportation Only

Response to RFP Speed Data Services

RFP 521B-26

Submitted by INRIX, INC.

1756 114th Avenue SE., Suite 200 Bellevue, WA 98004 Phone: +1 425-284-3800 www.inrix.com

Contact Todd Kell, Director of Public Sector Services

Phone: +1 (804) 512-6601 Email: Todd.Kell@inrix.com

Program Proposal 16th September 2025 http://www.inrix.com/ mailto:Todd.Kell@inrix.com

INRIX Program Proposal for Ohio DOT RFP 521B-26 Speed Data Services

INRIX Confidential for Ohio DOT Only

Contents

Cover Letter/Proposal Highlights

1 Requirements/Specifications

1.1 Proposal Purpose

1.2 Data Collection

1.3 Data Coverage

1.3.1 Routes

1.3.2 Segmentation

2 Prequalification Questionnaire

3 Required Data & Services

3.1 Data and Services

3.1.1 Speed Data

3.1.2 Dangerous Queueing

3.1.3 Bottlenecks

3.1.4 Map Tile Service

3.2 Data Application Programming Interface (API) Requirements

3.2.1 Speed Data APIs

3.2.1.1 Real-Time Data API

3.2.1.2 Historic Data API

3.2.2 Dangerous Queuing API

3.2.3 Bottlenecks API

3.2.3.1 Historic Bottlenecks API

3.2.3.2 Real-Time Bottlenecks API

3.3 Data Querying/Download Tool Requirements

3.4 Initial Data & Services Load Schedule

3.4.1 Speed Data Load Schedule

3.4.2 Dangerous Queueing Load Schedule

3.4.3 Bottlenecks Load Schedule

3.4.4 Map Tile Service Load Schedule

4 Required Analytics Tools & Services

4.1 Speed Data Analytics Tools

4.1.1 Performance Report

4.1.2 User Delay Cost

4.1.3 Performance Charts

4.1.4 Space-Time Congestion Visualization

4.1.5 Bottleneck Visualization

4.1.6 Trend Map

4.1.7 Real-Time Speed and Incidents Map

4.1.8 Massive Data Downloader (Additional)

4.1.9 Advanced INRIX XD Analytics for Arterials: Travel Time Comparison & Cumulative Distribution Charts (Additional)

4.1.10 Advanced INRIX XD Analytics for Arterials: The Travel Time Delta Ranking tool (Additional)

4.1.11 Performance Dashboards (Additional)

4.1.12 Corridor Speed Bins (Additional)

4.1.13 Corridor Time Comparison (Additional)

4.1.14 Temporal Comparison Maps (Additional)

4.1.15 Vehicle Ownership Charts (Additional)

4.1.16 Energy Use and Emission Matrix (Additional)

4.1.17 Energy Use and Emissions Trend Map (Additional)

4.1.18 Energy Use and Emissions Charts (Additional)

4.1.19 MAP-21 (Additional)

4.1.20 NPMRDS Coverage Map (Additional)

4.1.21 Causes of Congestion Graphs (Included when both PDA and RITIS subscriptions are active)

4.2 Analytics Application Programming Interface (API) Requirements

4.2.1 Performance Report API

4.2.2 User Delay Cost API

4.3 Initial Analytics Tools Load Schedule

4.3.1 Speed Data Analytics Load Schedule

5 Optional Data, Services, and Tools

5.1 Traffic Signal Analytics Tools/Platform

5.2 Additional Data, Services, and Tools

5.3 Initial Load Schedule for Optional Data, Services, and Tools

5.3.1 Traffic Signal Analytics Tools/Platform Load Schedule

5.3.2 Additional Data, Services, and Tools Load Schedule

6 Availability & Accuracy

6.1 Data Availability

6.1.1 Real-Time Availability

6.1.2 Map Tile Services Availability

6.1.3 Historical API Availability

6.1.4 Querying and Analytics Tools Availability

6.1.5 Scheduled Maintenance

6.2 Data Accuracy

6.2.1 Periodic Data Accuracy Inspection

6.2.2 Data Sample

6.3 Data Quality

7 Support

7.1 Technical Support

7.2 Ongoing Support

8 Training

9 Qualifications and Experience

9.1 Qualifications

9.2 Experience with Transportation Use Cases

10 Demonstration Period

Page | 1

Cover Letter/Proposal Highlights

Page | 2

Page | 3

Page | 4

Page | 5

INRIX Confidential for Ohio DOT Only

1 Requirements/Specifications

1.1 Proposal Purpose

Access to the data, API, and analytics tool(s) shall be granted to all users from the approved agencies listed in Table 1:

While account access will not generally be given to private/university entities, ODOT or an approved agency account holder shall be able to provide the speed data and/or temporary access to analytics and data querying tools to a consultant(s), university, or a similar entity working on their projects solely for use in that project. At the conclusion of the project, access to the analytics and querying tools will be withdrawn from the entity. ODOT may distribute and/or grant access to the Proposer data to third-party vendors responsible for maintaining ODOT systems, such as the Advanced Traffic Management Systems (ATMS), GPS/AVL system, Traveler Information System (TIS), etc. The third-party vendor shall be prohibited from using or distributing the data for any purpose other than the approved ODOT system.

INRIX Response:

INRIX meets this requirement by continuing to provide access to all data, APIs, and analytics tool(s) to all approved ODOT approved agencies and private and university entities as described above. In addition, the existing 380+ users and credentials will continue to work seamlessly under this contract with no disruption.

1.2 Data Collection

Speed data may be collected in any non-intrusive method that represents data along a segment of roadway.

Proposer(s) must clearly indicate the method(s) and technology being used to collect the data. For example, speed may be collected using probe-based collection methods such as GPS, mobile devices, connected vehicle sensors, etc. The data shall be representative of vehicle mixtures (i.e., passenger vehicles and commercial vehicles/trucks) utilizing Ohio’s roadway system. As part of their response, the Proposer should indicate the average penetration rate within Ohio and include the percent of data from passenger vehicles versus commercial vehicles/trucks. While not required, additional data that differentiates between passenger vehicles and commercial vehicles/trucks should be cited in this section as potentially exceeding the minimum RFP requirements. Speed data shall not include an upper-limit cap to the averaged speeds that were captured along the roadway.

INRIX Response:

INRIX meets this requirement by clearly describing the methods and technology used to collect data. INRIX has intentionally established a ‘network’ of GPS data suppliers. This approach continues for three primary reasons: (1) reduces the risk of a potentially catastrophic impact of losing access to a single source data supplier, (2) allows for the mix of source data to evolve with the overall market, from connected trucks, to adding mobile app/device data, to the emergence of connected cars, and (3) leads to the most cost-effective, complete data portfolio, allowing us to pass efficiencies on to our customers. The quality and the quantity of GPS data used to power INRIX services enable coverage of roads of all types over all days and times of day.

To illustrate the scale of our GPS network, the ‘INRIX Fleet’ (our GPS data portfolio) presently:

Page | 6

INRIX Confidential for Ohio DOT Only

• Includes more than 30 incoming GPS data sources in the US, all providing data in real-time

• Captures daily over 61 billion GPS waypoints in more than 2.4 billion discrete trips, covering more than

14.5 billion miles, sampling roughly 14% of nation’s overall VMT, and 16% in Ohio

• Gets 87% of incoming data from Connected Cars or Trucks with connected car data coming from OEMs, who collectively have 35% of US passenger vehicle market share

• Has 89% of miles traveled coming from passenger vehicles/devices, 6% from local fleets, and 5% from long haul fleets, closely mirroring national averages

• INRIX captures over 800 million points daily in Ohio, with an average of over 25 billion points captured each month for the past 12 months.

• INRIX captured ~18% of Commercial Vehicle miles travelled, and ~8% of passenger miles travelled in Ohio.

Providing speed data without an upper-limit cap to averaged speeds is on the INRIX near-term development roadmap.

1.3 Data Coverage

1.3.1 Routes

Data shall be provided for, at a minimum:

• 100% of Interstate route centerline mileage;

• 99% of non-Interstate National Highway System1 (NHS) route centerline mileage; and,

• 95% of all remaining State Highway System2 (SHS) route centerline mileage.3

The required coverage percentages will be calculated as follows:

The Department will overlay in geospatial software (e.g., ArcGIS Pro) the Proposer-provided shapefile with the National Highway System shapefile maintained by ODOT (see footnote 1) and the State Highway Priority System shapefile maintained by ODOT (see footnote 2). All shapefiles will have their geometry re-projected to the NAD83/Ohio South (EPSG:32123) coordinate reference system. ODOT-maintained shapefiles may be modified to ensure only centerline miles are captured. If the Proposer-provided segmentation overlaps the respective category above without any visible gaps (at a scale of 1:1,500,000) between the ODOT-maintained and Proposer-provided shapefiles (excluding the Lake Erie Islands), as determined in ODOT’s sole discretion, the Department will accept the submittal as prima facie evidence that the required coverage percentages have been met. If the overlap reveals gaps in required coverage, the Department will perform a geospatial intersection of the two data sources using geospatial software (e.g., ArcMap) with a buffer of 35 meters. The coverage percent will be calculated as the total sum of covered centerline miles4 divided by the total centerline miles for each category5.

• Data shall be provided in each direction for all routes. Additionally, for areas where parallel roadways (i.e., Express Lanes and Collector/Distributor sections) exist, additional data segments are required. The Proposer shall provide speed data to ODOT for every route in Ohio for which they have coverage. In the future, any additional Ohio coverage the Proposer adds shall be included at no additional cost for the duration of this contract. In addition to the Ohio routes, data shall be provided for any Interstate, US, and State Routes for adjacent states one county deep.

• The Proposer shall provide a shapefile of their available data segments by uploading the file with their submission in Ohio Buys. The coverage requirement will be scored based on the following ranges of coverage percent:

Page | 7

INRIX Confidential for Ohio DOT Only

INRIX Response:

INRIX meets or exceeds these requirements by providing data on all Interstate and Non-Interstate NHS roadways, and approximately 98% of all other SHS and 75,474 total directional miles of coverage. Please refer to the USA_Ohio_Coverage shapefile uploaded alongwith the INRIX Program Proposal for referring to the Data Coverage information. INRIX encourages customers to inform the INRIX maps team of important road additions through roadnotifications@inrix.com. Road coverage requests can be met through the INRIX bi-annual Map Updates in Spring (March/April) and Fall (September/October).

As requested, INRIX will add roads at no additional cost to ODOT during this contract, and will provide data for any Interstate, US, and State Routes for adjacent states one county deep.

Map Version

Total XD Count

Total XD Directional Mileage

25.1 279,505 76,367

Table 1: XD Count and Mileage coverage.

Due to a continued focus on increased road and data coverage, INRIX currently exceeds all coverage requirements.

Meets Exceeds

Interstate 100% N/A

Non-Interstate NHS 100% N/A

All other SHS ~99%* ~99%*

*Full conflation is required to determine the exact percentage, so approximation is provided.

mailto:roadnotifications@inrix.com

Page | 8

INRIX 25.1 XD network layered (Blue) on top of the Ohio State Highway System (Priority System) in Orange.

Orange only Indicates areas not currently covered by the INRIX network. Ohio State Highway System is 19,282 miles. INRIX XD network is 76,367 directional miles and over 38,000 centerline miles.

1.3.2 Segmentation

Data shall be provided by the vendor in the most granular/high resolution segmentation, shorter than Traffic Message Channel (TMC), available (hereby called high-resolution segments/segmentation”). Segmentation must be fixed except for regularly scheduled segmentation updates. ODOT shall be notified at least 30 days in advance of any regularly scheduled segmentation updates. Any applicable files pertaining to the regularly scheduled segmentation update shall be received by ODOT at least 10 business days in advance of the release. Data shall be provided for each segment representing the average speed of the entire segment across all directional lanes.

Proposers shall discuss the granularity, segmentation, and type and frequency of regularly scheduled segmentation updates for their data as part of this response. If by-lane data is also available, this should be discussed as part of the Proposer’s response.

Page | 9

INRIX Confidential for Ohio DOT Only

INRIX Response:

INRIX meets this requirement by offering data at a high-resolution granularity, smaller than Traffic Message Channel (TMC) standard segmentation. INRIX XD Segments, first introduced in 2013, are similar to TMC Segments in that they delineate a specific section of roadway, but they also address some of the limitations of TMC Segments, such as road coverage, the ability to cover new roads more quickly, segment overlap and gapping, and segment resolution. In addition, each INRIX XD Segment can be broken down into sub-segment offsets that can be specified by the user from 100 meters to full segment length.

In 2025, INRIX will be adding real-time data coverage for special lanes, including facilities like HOV or managed lanes that only have a paint or non-physical barrier. INRIX will provide documentation and any necessary training to ODOT as this data comes online.

2 Prequalification Questionnaire

1. Does the Proposer’s product offer data at a high-resolution granularity, smaller than Traffic Message

Channel (TMC) standard segmentation (see Section I.1.3.2 Segmentation)?

INRIX Response: Yes, INRIX meets this requirement by offering data at a high-resolution granularity, smaller than Traffic Message Channel (TMC) standard segmentation. INRIX XD Segments, first introduced in 2013, are similar to TMC Segments in that they delineate a specific section of roadway, but they also address some of the limitations of TMC Segments, such as road coverage, the ability to cover new roads more quickly, segment overlap and gapping, and segment resolution. In addition, each INRIX XD Segment can be broken down into sub-segment offsets that can be specified by the user from 100 meters to full segment length.

2. Does the Proposer’s product offer data at a minimum frequency (see Section I.3.2.1 Speed Data APIs) of:

a. 1-minute intervals for Real-Time, and

b. 5-minute intervals for Historic?

INRIX Response: INRIX meets these requirements by providing calculated real-time speed and travel time data for each segment of the covered roadway is updated in 1-minute intervals. INRIX exceeds this requirement by providing historic data in 1, 5, 15 and 60-minute intervals.

3. Can the Proposer supply historic Bottleneck data (see Section I.3.1.3 Bottleneck Data) on all State Highway System routes (see Section I.1.3.1 Routes)?

INRIX Response: INRIX meets this requirement by providing bottleneck data for all State Highway System routes.

4. Does the Proposer offer a Map Tile service meeting the specifications of Section I.3.1.4?

INRIX Response: INRIX exceeds this requirement by committing to continue to provide our robust traffic map tiling service that includes real-time speed, congestion levels, historical speed, and comparative speed maps with unparalleled user configuration options – colors, shading, widths, opacity, etc. Users can also adjust the speed/congestion ranges by creating custom speed buckets (http://docs.inrix.com/reference/speedbuckets/).

Page | 10

INRIX Confidential for Ohio DOT Only

3 Required Data & Services

3.1 Data and Services

3.1.1 Speed Data

The following data elements must be provided at a minimum:

The selected Proposer shall provide a shapefile, and optionally a GeoJSON file, with the metadata and linear geometry for all data segments upon contract award and for any subsequent coverage updates and/or map version edits throughout the life of contract.

The Proposer's response shall include, at a minimum, a listing of all data fields, a description of the fields, data type for each field, an example value for each field, and the corresponding Element ID (e.g., M1, S1, etc.) for the following data sets:

• segmentation metadata;

• real-time speed data API;

• historical speed data API; and,

• historical data querying/download tool (if it varies from historical data API).

Page | 11

INRIX Confidential for Ohio DOT Only

Additionally, as part of the response, the Proposer shall include their definition of expected speed, freeflow speed, and confidence value.

The Proposer shall use the response templates in Appendix A - Speed Data Templates as part of the above response.

Additional data elements may be provided in the feed as long as the required data elements from Table 3 and Table 4 are included. The following are not required, but would provide value to the Department if available:

If the Proposer has other fields beyond the minimum, they should be discussed as part of the response. Optional Data Elements can be included in the response templates found in Appendix A - Speed Data Templates.

INRIX Response:

INRIX exceeds these requirements by providing all required parameters and optional elements of interest for all of the following tables:

• Table 3: Required Metadata Elements;

• Table 4: Required Real-time Speed Data Elements

• Table 5: Historical Speed Data and the Historical Data Query Tool have the same elements

This is further outlined in the below tables as requested.

Page | 12

INRIX Confidential for Ohio DOT Only

Note that for some of the listed and required datasets, ODOT has the option to access the data from INRIX or CATT Lab. Where that option exists, tables for both are provided and labeled in the header with “INRIX Field Name” or “CATT Lab Field Name” to differentiate. In some cases, the CATT Lab option could have some latency as compared to the INRIX dataset.

Table 3: Required Metadata Elements

Element

ID

ODOT

Element

Name

INRIX Field Name

Description Data Type

Example Value

M1 Segment ID XDSegID Identifier for the road segment

String (Integer) "1237060387"

M2 Road Number

RoadNumbe r

Road number designation String (Integer) "515"

M3 Travel Direction

Bearing General/overall direction of the roadway by XDGroup.

(note: 'C' stands for Clockwise and 'O' stands for Counterclockwise)

String "S"

M4 Segment Length

Miles Length of the road segment in miles

String (Float) "0.6644922703952 542"

M5 Start Latitude/ Longitude

StartLat Starting latitude of the road segment

String (Float) "36.08591"

M5 Start Latitude/ Longitude

StartLong Starting longitude of the road segment

String (Float) "-115.05498"

M6 End Latitude/ longitude

EndLat Ending latitude of the road segment

String (Float) "36.08071"

M6 End Latitude/ longitude

EndLong Ending longitude of the road segment

String (Float) "-115.04497"

Country Country where the road is located

String "United States"

County County where the road is located

String "Clark"

District District name (empty in this case)

String ""

Page | 13

Element

ID

ODOT

Element

Name

INRIX Field Name

Description Data Type

Example Value

FRC Functional Road Class code String (Integer) "1"

Lanes Number of lanes on the road

String (Float/Integer)

"3.0"

LinearID Identifier for a linear feature (empty in this case)

String ""

NextXDSegI Identifier for the next road segment

String (Integer) "1237063001"

OID Unique identifier for the feature

String (Integer) "11958167"

PostalCode Postal (ZIP) code for the road’s location

String "89122"

PreviousXD Identifier for the previous road segment

String (Integer) "1236918428"

RoadList Pipe-separated list of road names or designations

String "I-515|Las Vegas Expy|US-93|US- 95|Oran K Gragson Hwy"

RoadName Name of the road, including direction

String "I-515 S"

ShapeSRID Spatial Reference System Identifier (e.g., WGS84 =

EPSG:4326)

String (Integer) "4326"

SlipRoad Indicates if the road is a slip road (e.g., ramp)

String (Boolean/Integer)

"1"

SpecialRoa Special road attributes (empty in this case)

String ""

State State where the road is located

String "Nevada"

XDGroup Group identifier for the road segment

String (Integer) "2969385"

Page | 14

INRIX Confidential for Ohio DOT Only

Table 3 A: Required Metadata Elements (PDA Fields)

Element

ID

ODOT Element Name

CATT Lab Field Name

[what we call it in PDA]

Description Data Type Example Value

Required Data Elements

M1 Segment ID tmc TMC code. String 122-04212

M2 Road Number Road

The TMC’s road number. String I-270

M3 Travel Direction Direction The TMC’s direction. String clockwise

M4 Segment Length Miles The TMC’s length in miles.

Floating-point number 0.530751

M5 Start Latitude/ Longitude Start_latitude start_longitude

The TMC’s start latitude and longitude, expressed as a single floating-point number.

Floating-point number

40.10365

-82.94084

M6 End Latitude/ Longitude

End_latitude end_longitude

The TMC’s end latitude and longitude, expressed as a single floating-point number.

Floating-point number

40.10171

-82.931

Additional Data Elements (Optional)

(Add additional lines as necessary)

Table 4: Required Speed Data Elements

Element

ID

ODOT Element Name

INRIX Field Name

Description Data Type Example Value

Required Data Elements

S1 Segment ID code Unique identifier for the segment. The value would be the TMC code or the INRIX XD Segment ID. Required

String 114P04232

Page | 15

INRIX Confidential for Ohio DOT Only

Element

ID

ODOT Element Name

INRIX Field Name

Description Data Type Example Value

S2 Date/Time timestamp The Date and Time recorded as YYYY-MM-

DDTHH:MM:SSZ

string "timestamp":

"2020-12- 12T00:52:43Z"

S3 Recorded Speed speed Current speed on the segment integer "speed": 26

S4 Historical Speed average The typical speed on the segment for the given day and time integer "average": 27

S5 Freeflow Speed reference The free flow speed on the segment for the given day and time integer "reference": 76

S6 Confidence Value score The source of the speed data field returned.

30 = Real-time data 20 = Historical data 10 = Reference speed integer "score": 30

Additional Data Elements (Optional)

TTM Travel Time Minutes Integer 0.357 speedBucket

The amount of congestion on the segment. A lower number represents higher congestion.

0 = speed is 0-31% of reference speed 1 = speed is 32-62% of reference speed 2 = speed is 63-92% of reference speed 3 = speed is <93% of reference speed 255= road segment is closed SpeedBuckets are customizable by ODOT, these are the default values INRIX sets Integer 2

(Add additional lines as necessary)

Page | 16

INRIX Confidential for Ohio DOT Only

Table 4A Required Speed Data Elements (PDA Fields)

Element

ID

ODOT Element Name

CATT Lab Field Name

[what we call it in PDA]

Description Data Type Example Value

Required Data Elements

S1 Segment ID Tmc_code

The reading’s TMC code. String 122+04213

S2 Date/Time

Measurement_tstamp

Timestamp in segment-local time corresponding to the reading’s minute. String

7/27/2025 12:00:00

PM

S3 Recorded Speed speed

The reading’s speed. Integer 17

S4 Historical Speed Historical_average_speed

The reading’s historical average speed.

Integer 70

S5 Freeflow Speed Reference_speed

The reading’s free-flow reference speed.

Integer 68

S6 Confidence Value confidence_value

The reading’s confidence score. Integer 30

Additional Data Elements (Optional)

Table 5: Historical Speed Data

Element

ID

ODOT Element Name

INRIX

Field Name

Description Data Type

Example Value

Required Data Elements

S1 Segment ID XDSegID Unique identifier for the segment. The value would be the TMC code or the INRIX XD Segment ID.

Required

134000446

Page | 17

INRIX Confidential for Ohio DOT Only

Element

ID

ODOT Element Name

INRIX

Field Name

Description Data Type

Example Value

S2 Date/Time measurement_tstamp The Date/Time Recorded

8/2/2021 8:00

S3 Recorded Speed speed Recorded speed on the segment

44.96

S4 Historical Speed average_speed The typical speed on the segment for the day and time

S5 Freeflow Speed reference_speed The free flow speed on the segment for the day and time

S6 Confidence Value C-Value The source of the speed data field returned.

30 = Real-time data 20 = Historical data 10 = Reference speed

Additional Data Elements (Optional) OS6 Accuracy Value cvalue A measure of the confidence in the real-time data. Ranges from 0 to

100. The higher the cvalue, the more confident the data.

Table 5A: Historical Speed Data (PDA Fields)

Element

ID

ODOT Element Name

CATT Lab Field Name

[what we call it in PDA]

Description Data Type Example Value

Required Data Elements

S1 Segment ID Tmc_code

The reading’s TMC code. String 122+04213

S2 Date/Time

Measurement_tstamp

Timestamp in segment-local time corresponding to the reading’s minute. String

7/27/2025 12:00:00

PM

S3 Recorded Speed speed

The reading’s speed. Integer 17

Page | 18

INRIX Confidential for Ohio DOT Only

Element

ID

ODOT Element Name

CATT Lab Field Name

[what we call it in PDA]

Description Data Type Example Value

S4 Historical Speed Historical_average_speed

The reading’s historical average speed.

Integer 70

S5 Freeflow Speed Reference_speed

The reading’s free-flow reference speed.

Integer 68

S6 Confidence Value confidence_value

The reading’s confidence score. Integer 30

Additional Data Elements (Optional)

(Add additional lines as necessary)

Both the INRIX and CATT Lab APIs have the same elements for the Historical Data Query Tool as in Table III:

Historical Speed Data above.

Page | 19

INRIX Confidential for Ohio DOT Only

3.1.2 Dangerous Queueing

The Department requires real-time dangerous queueing event data on the entire National Highway System (as defined above in Section I.1.3.1 Routes) for the purpose of effective traffic management and the safety of the traveling public. Dangerous queueing events, for the purpose of this requirement, are defined as a location where the speed of one segment differs from the speed of the adjoining segment by an established threshold (at least 20 mph difference), resulting in a potentially hazardous speed drop that may require hard braking.

The following dangerous queueing elements must be provided at a minimum:

The Proposer’s response shall include, at a minimum, discussion on the methodology for identifying dangerous queueing events, including the threshold used for identification, the frequency and latency of the feed, a listing of all data fields, a description of the fields, data type for each field, an example value for each field, and the corresponding Element ID (e.g., Q1, Q2, etc.). If the Proposer has other fields beyond the minimum, they should be discussed as part of the response.

The Proposer shall use the response template in Appendix A - Dangerous Queueing Template as part of the above response.

INRIX Response:

INRIX meets this requirement by providing INRIX Traffic Flow Incidents. These alerts provide insight into dangerous queueing and event data on the NHS system and is provided through a JSON or XML web-based API. INRIX Traffic Flow Incidents are algorithmically generated events based on INRIX real-time flow data. They use powerful algorithms to identify traffic slowdowns based on indications in the data that current traffic flow is divergent from the expected traffic for that location at that time. When anomalies are detected, INRIX generates a flow incident.

Flow Incidents are updated at a minimum once per minute. Each Flow Incident includes:

• The segment location

• A roadway description

• Start and end points for the incident

• Incident status

• A congestion report

• The average speed along the congested segment

• The delay impact

Page | 20

INRIX Confidential for Ohio DOT Only

Table A2: Dangerous Queueing Fields

Element

ID

ODOT

Element

Name

Proposer Field Name Description Data Type

Example Value

Required Data Elements

Q1 Id

ID

The unique identifier associated with the Dangerous Slowdown. The same ID value will be associated with the Dangerous Slowdown while it stays in the same location on the road. If it moves to the start of another XD segment the ID will change. String

66bf9c41-9406-44cc-b2dd-e93dbad0364e

Q2 Date/Time occuranceStartTimeUTC

ISO standard time stamp with date and time of slowdown String

2025-07- 27T03:31:35.803Z"

Q3 Segment 1 Speed speedBefore

The speed leading up to the Dangerous Slowdown. Values are in mph or km/h depending upon the input “Units” value. Integer 39

Q4 Segment 2 Speed speedAt

The speed at the Dangerous Slowdown. Values are in mph or km/h depending upon the input “Units” value. Integer 3

Q5 Speed Difference speedDelta speedAt – speedBefore (i.e. if speedAt = 96km/h and speedBefore = 56km/h then speedDelta = 40km/h). Values are in mph or km/h depending upon the input “Units” value. Integer 36

Page | 21

INRIX Confidential for Ohio DOT Only

Element

ID

ODOT

Element

Name

Proposer Field Name Description Data Type

Example Value

Q6 Latitude coordinates Latitude of slowdown

Floating point number -81.11300246697294

Q7 Longitude coordinates Longitude of slowdown

Floating point number 37.632484124752594

Additional Data Elements (Optional) roadName Road name or number string I-70 direction directionality of the road- N = Northbound, S = Southbound, E = Eastbound, W = Westbound, C = Clockwise, AC = Counter-clockwise string E offset

Start and end offset on the segment in meters integer 256

Page | 22

In addition, as the queue event lengthens, shortens, or changes in severity, a new version of the Incident API will be provided. The below image outlines the following API response parameters:

• XDIncidentId: Unique identifier per XDIncident

• Version: There could be subsequent versions for the same XDIncidentID. A new version will include changes in the previous published version (i.e. Incident codes, list of affected Xdsegments, description, head, tail,…).

• Latitude/Longitude coordinates are related to the HEAD of the incident.

• Location: Includes the list of affected XDSegments and their corresponding portion (offset in meters).

This list covers the total incident length between the head and the tail points.

• Head: Indicates where the congestion situation starts. Note that the Head location corresponds to the

Latitude/Longitude coordinates of the incident. In the demo area, INRIX locates the Congestion Alert icon in this point.

• Tail: Indicates where the congestion alert finishes.

INRIX additionally exceeds this requirement by providing Dangerous Slowdowns (DSD). Dangerous Slowdowns are delivered using an API that identifies locations where rapidly forming congestion creates an unexpected slowdown that raises the risk of back-of-queue collisions. Based on the same GPS real-time probe data used to generate speed and travel times, DSD notifications over the INRIX XD segment road network can be used to warn drivers and transportation agencies of sudden reductions in speed or stopped traffic on the roadway.

The service is available on all limited access roadways in the United States and is updated every minute.

Importantly, DSD messages are created regardless of the length of the slowdown; thus, dangerous situations such as a stalled vehicle on a rural interstate can be detected.

Page | 23

INRIX Confidential for Ohio DOT Only

The DSD service analyzes real-time speeds from segment to segment each minute. If there is a greater than 35 mph drop in speed, a DSD alert is created, with the alert located at the upstream end of the initial segment, ensuring that the warning is placed near, but upstream of, the actual slow down. DSDs are assigned one of three levels of severity based on the speed drop, with the most severe DSDs having speed drops of over 60 MPH. Note that not all areas of congestion will create a DSD. For instance, a queue where speeds gradually slow over multiple segments may not trigger the >35 mph minimum threshold.

DSDs are provided via a specific API with a JSON response format. (INRIX Docs Link)

3.1.3 Bottlenecks

The Department requires historic bottleneck data utilizing high-resolution segmentation on the entire State Highway System (as defined above in Section I.1.3.1 Routes) for the purposes of TOAST and its Performance Dashboards. Real-time bottleneck data is optional. Bottleneck data, for the purpose of this requirement, is defined as a location where speeds differ from the reference speed by a percent threshold for a certain amount of time, resulting in a queue of traffic.

The following bottleneck data elements must be provided at a minimum:

The Proposer’s response shall include, at a minimum, discussion on the methodology for identifying bottlenecks, including the percent threshold used for identification, a listing of all data fields, a description of the fields, data type for each field, an example value for each field, and the corresponding Element ID (e.g., B1, B2, etc.). If the Proposer has other fields beyond the minimum, they should be discussed as part of the response.

The Proposer shall use the response template in Appendix A - Bottleneck Data Template as part of the above response.

INRIX Response:

INRIX meets this requirement.

https://docs.inrix.com/traffic/dangerousslowdowns/

Page | 24

INRIX Confidential for Ohio DOT Only

Table A3: Bottleneck Data Fields

Element ID ODOT Element Name

Proposer Field Name Description Data Type Example Value

Required Data Elements B1 Id

Id

Unique identifier for the bottleneck occurrence

String

(UUID)

c04beff4-8915- 4ac7-95d2-

0b192aa2f359 B2 Start Date/Time

StartDate

Start date and time of the bottleneck

DateTime

(ISO 8601)

2025-01- 07T04:51:00Z

B3 Duration EndDate

End date and time of the bottleneck

DateTime

(ISO 8601)

2025-01- 07T04:55:00Z

B4 Start Latitude

FromPointLat

Latitude of the head (start) of the bottleneck Float

39.9612

B5 Start Longitude

FromPointLon

Longitude of the head (start) of the bottleneck Float

-83.0022

B6 End Latitude

ToPointLat

Latitude of the tail (end) of the bottleneck Float 39.9500

B7 End Longitude

ToPointLon

Longitude of the tail (end) of the bottleneck Float -83.0100

B8 Max Length (mi)

MaxLengthMiles

Maximum length of the bottleneck in miles Float 0.5

Additional Data Elements (Optional)

BottleneckSummaryIndex Index linking to the summary record

Integer 1

FromIntersectionName Name of the intersection at the start of the bottleneck

String I-71 @ US-62

ToIntersectionName Name of the intersection at the end of the bottleneck

String I-71 @ SR-56

Direction Direction of travel affected (e.g., NB, SB, EB, WB)

String NB

MaxDurationMinutes Maximum duration of the bottleneck in minutes

Integer 4

Page | 25

INRIX Confidential for Ohio DOT Only

StartSegmentOffsetMiles Offset (in miles) from the start segment

Float 0.0

EndSegmentOffsetMiles Offset (in miles) from the end segment

Float 0.5

The detection of bottlenecks is based on comparisons of speeds to reference speeds, which are the proxy of the free flow or uncongested speed. A potential bottleneck is detected when speeds on a segment drop to 65% of the reference speed, and a bottleneck is published if speeds stay below 65% and causes 120 seconds of delay. So long as the speed remains below 75% of the reference speed, the bottleneck will not be cleared. Although bottleneck locations are associated with INRIX XD Segments, computations to detect bottlenecks are based on finer resolution sub-segments, and the reported length of a bottleneck is the sum of all affected sub-segments. The mapped location of the bottleneck provides the associate XD segments as well as the precise start and end of the bottleneck. Bottleneck versions are continuously tracked, and the average duration, average maximum length, and number of occurrences of all versions of a single bottleneck are tabulated.

3.1.4 Map Tile Service

The Proposer shall make available a tile service that returns images containing traffic graphics. The tile service shall allow for:

• the ingestion of map tile images encompassing the state of Ohio in its entirety, with routes visible at appropriate, progressive scales;

• custom line/segment widths and opacity on the resulting map tile image for each request;

• custom speed/congestion ranges with custom corresponding colors for each request; and,

• the use of Bing Maps Tile System quadkeys to describe the geographic area for which a map tile image is to be returned, or a mechanism for converting Bing Maps Tile System quadkeys to a format supported by the Proposer.

The returned image shall have a transparent background that will allow it to be overlaid on top of other basemaps with only the requested data visible.

The proposer shall discuss their map tile service and their ability to meet the above requirements as part of this response.

INRIX Response:

INRIX exceeds this requirement by committing to continue to provide our robust traffic map tiling service supports public-facing platforms that perform during emergent situations such as major winter storms, tropical events and flooding. The map tiling service includes real-time speed, congestion levels, historical speed, and comparative speed maps with unparalleled user configuration options – colors, shading, widths, opacity, etc. Users can also adjust the speed/congestion ranges by creating custom speed buckets (http://docs.inrix.com/reference/speedbuckets/).

Ohio will not be limited in spanning geographic boundaries of the state of Ohio and can achieve this through utilizing quadkeys as represented through the Bing Maps Tile System. The returned image has a transparent http://docs.inrix.com/reference/speedbuckets/

Page | 26

INRIX Confidential for Ohio DOT Only background that allows it to be overlaid on top of other basemaps with only the requested data visible. See the below image for a sample call and response.

Query: https://tile-api.inrix.com/v1/tiles

/032001003333130?FRCLevel=1,2,3,4,5&roadSegmentType=XDS&coverage=255&speedbucketid=54135&penWidth=17.4 &opacity=80&accessToken={token}

A 256 x 266 map tile in PNG format showing all roads including parts I-70 and I-71 interchange in Columbus. The White areas are transparent https://tile-api.inrix.com/v1/tiles

Page | 27

INRIX Confidential for Ohio DOT Only

3.2 Data Application Programming Interface (API) Requirements

3.2.1 Speed Data APIs

INRIX provides APIs for Real Time Speeds as well as for Historical speeds. INRIX has been providing real time and historical speed data to agencies and enterprise customers globally since 2005. Speed data is based on GPS probe data from millions of vehicles globally, including to US state departments of transportation, federal agencies, international traffic agencies, as well as local government customers. INRIX serves quarter of a million segment speed calls per month to ODOT.

3.2.1.1 Real-Time Data API

High-resolution segmented, real-time data shall be provided through a web-based API in either JSON or XML format. Data shall be provided from the API meeting the specifications of Section I.3.1.1 Speed Data for all timestamps and available according to the requirements in Section I.6 Availability and Accuracy.

Real-time data shall be updated and provided at a maximum interval of 1 minute. The Proposer’s real-time API must be capable of supporting at least 15 requests per minute from ODOT.

The Proposer should specify the format of their Real-time API response and discuss the update intervals as part of their response.

The real-time API must be immediately ingestible by the OHGO inSIGHT ATMS to support travel time calculations for Intelligent Transportation System (ITS) devices, such as Dynamic Message Signs. The Proposer must demonstrate that their real-time API is currently being ingested by existing inSIGHT ATMS platforms and is fully compatible for integration into the OHGO inSIGHT ATMS upon contract award. Solutions that require development or configuration post-award will be considered non-responsive.

INRIX Response: INRIX Segment Speed API (INRIX)

Overview of INRIX Segment Speeds API

INRIX proposes our Segment Speeds API to fulfill the Ohio Department of Transportation’s (ODOT) requirements for high-resolution, real-time traffic speed data. The API is designed to support transportation agencies with reliable, actionable traffic insights for real-time traffic management. This API is currently in place, requires no development time or modifications, and can deliver fully to the inSIGHT ATMS upon contract award. The API is fully operational and is providing segment speed data into inSIGHT ATMS deployments in Ohio, Massachusetts, Louisiana and Wisconsin.

API Response Format

The INRIX Segment Speeds API supports data delivery in both JSON and XML formats, as required. For this response, we demonstrate the JSON format, as specified in the provided API call (format=json). The API provides comprehensive speed data for specified segments, including attributes such as reference speed, measured speed, average speed, travel time, confidence value, and sub-segment details at a specified resolution (e.g., 250 meters).

Update Interval

The INRIX Segment Speeds API delivers real-time data updates at a maximum interval of 1 minute, meeting ODOT’s requirement for real-time data refreshes. Data is sourced from INRIX’s extensive network of over 275 million GPS-

Page | 28

INRIX Confidential for Ohio DOT Only enabled vehicles and devices, combined with traditional traffic flow data and contextual inputs (e.g., incidents, weather). This ensures that speed data reflects current road conditions with minimal latency.

API Capacity and Request Handling

The INRIX Segment Speeds API is designed to handle high request volumes, supporting at least 15 requests per minute from ODOT, as specified. The API call provided (https://segment-api.inrix.com/v1/segments/speed) demonstrates our capability to process targeted queries for specific segment IDs (e.g., 475509146) with customizable parameters like resolution and output fields. INRIX’s cloud-based infrastructure ensures scalability and reliability, with proven performance serving transportation agencies globally across nearly 8 million kilometers of roads.

Availability and Accuracy (Section I.6)

INRIX meets the availability and accuracy requirements of Section I.6 through robust data validation and comprehensive coverage. The API’s confidence value (cValue, 0-100) ensures high accuracy, with values like 95 in the sample response indicating strong data reliability based on real-time GPS probe density and historical trends.

INRIX’s XD segmentation provides much higher resolution compared to traditional TMC segments, it also covers many more roads, ensuring high-resolution data for freeways, highways, arterials, and secondary roads across Ohio. The API is available 24/7 with uptime guarantees, as outlined in the INRIX documentation, ensuring continuous access for ODOT’s needs.

Additional Features and Benefits:

• Customizable Queries: The API call demonstrates flexibility, allowing ODOT to query specific segments (e.g., IDs=475509146) with tailored parameters like resolution (resolution=250) and output fields (SpeedOutputFields=all). The API can be queried for the whole state, for specific Functional Road classes within the state, for specific roads, etc.

• Scalability: The API integrates seamlessly with systems like Advanced Traffic Management Systems (ATMS) or INRIX Mission Control for real-time visualization.

• Historical Data: INRIX offers archived speed data from January 2014, supporting historical analysis alongside real-time insights.

Conclusion

INRIX’s Segment Speeds API, as demonstrated by the provided API call, fully meets ODOT’s requirements for high-resolution, real-time traffic speed data delivered via a web-based API in JSON format. With 1-minute update intervals, the capacity to handle at least 15 requests per minute, and compliance with Sections I.3.1.1 and I.6, INRIX is well-equipped to support ODOT’s traffic management objectives. For further details or to initiate API access, please contact support@inrix.com or visit https://docs.inrix.com/traffic/segmentspeed/.

https://docs.inrix.com/traffic/segmentspeed/

Page | 29

INRIX Confidential for Ohio DOT Only

3.2.1.2 Historic Data API

Historical data shall be provided through a web-based API in JSON, XML, or CSV format; or a compressed data file containing any of the four previous data formats. Data shall be provided from the API meeting the specifications of Section I.3.1.1 Speed Data for all timestamps and available according to the requirements in Section I.6 Availability and Accuracy.

Historical speed data shall be provided and accessible for time periods as recent as two days (48 hours) old, as a minimum. Historical speed data must be available in 5-minute, 15-minute, and 1-hour time granularity intervals.

The Proposer should specify the format of their Historic API response and discuss the update intervals as part of their response.

INRIX Response:

Historical Speed Data Provision via RA Data Download (Speed Archive) API

Historical speed data is provided through the Roadway Analytics (RA) Data Download (Speed Archive) API, which supports delivery in multiple formats, including JSON, XML, and CSV. Data can be accessed directly via the web-based API or as compressed files containing the same formats, ensuring flexibility for integration and analysis.

The API delivers data that fully complies with the specifications outlined in Section I.3.1.1 (Speed Data) and Section I.6 (Availability and Accuracy). All available timestamps are supported, and data is accessible for periods as recent as two days (48 hours) old, at minimum.

Time Granularity:

Historical speed data is available in 5-minute, 15-minute, and 1-hour intervals, allowing users to select the temporal resolution that best fits their analysis needs.

Data Format:

The RA Data Download API response includes, for each road segment and time interval:

• Segment identifier (XDSEGID)

• Measured speed (SPEED)

• Historical average speed (NAS_SPEED)

• Reference speed (REF_SPEED)

• Delta (difference between average and current speed)

• Data source indicator (CS_STYLE_SCORE)

• Estimated travel time (TRAVEL_TIME_MIN)

• Congestion level (CONGESTION_LEVEL)

• Confidence value (CVALUE)

• Minimum and maximum observed speeds (MIN_SPEED, MAX_SPEED)

• Time bin (TIME_BIN)

These fields are provided in the selected output format (JSON, XML, or CSV), and a README file describing the schema is included in each compressed archive for user reference 1 2.

Update Intervals:

Historical speed data is updated daily, ensuring that new data is available within 48 hours of collection. The API

Page | 30

INRIX Confidential for Ohio DOT Only is designed to provide timely access to recent and historical data, supporting both operational and analytical use cases.

Summary: The RA Data Download (Speed Archive) API meets all requirements for historical speed data accessibility, format, and update frequency as specified in the RFP. The proposer can provide additional technical documentation and sample output files upon request.

3.2.2 Dangerous Queuing API

Dangerous queueing event data shall be provided through a real-time, web-based API in either JSON or XML format. Data shall be provided from the API meeting the specifications of Section I.3.1.2 Dangerous Queueing for all timestamps and available according to the requirements in Section I.6 Availability and Accuracy.

Real-time data shall be updated and provided at a maximum interval of 1 minute. The Proposer’s real-time API must be capable of supporting at least 15 requests per minute from ODOT.

The Proposer must specify the format of the Dangerous Queuing API response and describe the update intervals as part of their submission. The API feed must be fully developed, currently operational, and have a demonstrated history of delivering data to customers. The Proposer must also provide real-world sample data that reflects actual traffic conditions involving dangerous queuing scenarios. This data should illustrate the API’s ability to detect, report, and update queuing events with sufficient accuracy and timeliness to support operational decision-making.

INRIX Response:

Dangerous Queueing Event Data Provision via INRIX Dangerous Slowdowns (DSD) API

Dangerous queueing event data is provided through the INRIX Dangerous Slowdowns (DSD) API, a real-time, web-based service designed to deliver advance warning of back-of-queue slowdowns and other sudden speed drops on the roadway. This data exceeds the “Dangerous Queueing Event” requirement. The API is available in both JSON and XML formats, supporting seamless integration with ODOT systems and workflows. This API is currently in place, fully operational and requires no development time. Existing users include North Carolina DOT, which is using the DSD API as part of a federally funded grant project to push road condition/ event alerts to the broadest audience possible via major distribution channels.

Other agencies currently using this API include:

• Tennessee DOT

• Arizona DOT

• Pennsylvania Turnpike

• Vermont DOT

• Alaska DOT

Page | 31

NCDOT selected vendors (ingesting the DSD API) and distribution channels receiving the alerts for broad use.

API Specifications and Compliance:

• The DSD API meets the requirements of Section I.3.1.2 (Dangerous Queueing) by reporting all qualifying events for all timestamps and is engineered to comply with Section I.6 (Availability and Accuracy).

• The API is accessible via secure HTTP endpoints, requiring token-based authentication for each request 1 3.

• Data is available for all relevant road segments and geographies, with flexible query options (e.g., bounding box, point/radius, or geoId).

Update Intervals and Performance:

• Dangerous Slowdowns data is updated and made available in real time, with a maximum update interval of 1 minute, ensuring timely detection and reporting of dangerous queueing events 4.

• The API is designed to support at least 15 requests per minute from ODOT, with robust backend infrastructure and monitoring to ensure high availability and responsiveness 1.

API Response Format:

• The API response includes, for each event:

o Unique event ID and version o Severity level o Speed before and at the slowdown o Speed delta (difference) o Location (latitude/longitude, segment code, offset) o Occurrence start time (UTC) o Road name, direction, and optional mile marker

Page | 32

Dangerous Slowdowns API Response.

Page | 33

INRIX Confidential for Ohio DOT Only

• Example JSON response:

"dangerousSlowdowns": [ "id": "8341848|3559026", "version": 2, "severity": 3, "speedBefore": 51, "speedAt": 12, "speedDelta": 39, "location": { "geometry": { "coordinates": [104.722923, -3.012] },…