230000000396.pdf

STATE OF MICHIGAN PROCUREMENT

Department Technology, Management and Budget Central Procurement Services 320 S Walnut Street Lansing, MI 48933 P.O. Box 30026, Lansing, MI 48909

CONTRACT CHANGE NOTICE

Change Notice Number 3 to Contract Number MA230000000396

C O

N

TR

A C

TO

R

Parsons Transportation Group Inc. of Michigan

2677 Central Park Blvd Suite 275

Southfield MI 48076

Joseph Brahm

262-391-8056 joseph.brahm@parsons.com

CV0017188

ST

A

TE

Pr og ra m

M an ag er

Various Various

C on tr ac t A dm in is tr at or Corbin Montry DTMB

517-256-9895 montryc@michigan.gov

CONTRACT SUMMARY

Advanced Traffic Management System

INITIAL EFFECTIVE DATE

January 5, 2023

INITIAL EXPIRATION DATE

January 5, 2028

INITIAL AVAILABLE OPTIONS

5 - 1 Year

EXPIRATION DATE

BEFORE

January 4, 2028

PAYMENT TERMS

NET45

DELIVERY TIMEFRAME

N/A

ALTERNATE PAYMENT OPTIONS

P-Card Direct Voucher (PRC) Other

EXTENDED PURCHASING

Yes No

MINIMUM DELIVERY REQUIREMENTS

N/A

DESCRIPTION OF CHANGE NOTICE

OPTION LENGTH OF OPTION EXTENSION LENGTH OF EXTENSION

REVISED EXP. DATE

CURRENT VALUE

$3,436,956.85

VALUE OF CHANGE NOTICE

$89,260.00

ESTIMATED AGGREGATE CONTRACT VALUE

$3,526,216.85

DESCRIPTION

Please note the Program Manager or Contract Administrator may have changed, and are reflected on this Change Notice.

Effective 03/16/2026, the parties hereby agree to add the following Statement of Work for modifications to MDOT's Advance Traffic Management System (ATMS) for the US-23 extension project.

This contract is hereby increased by $89,260.00.

All other terms, conditions, specifications and pricing remain the same. Per contractor and agency agreement, and DTMB Central Procurement Services approval.

CHANGE NOTICE NO. 3 TO CONTRACT NO. MA230000000396

Program Managers for

Multi-Agency and Statewide Contracts

AGENCY NAME PHONE EMAIL

DTMB Dave Work 517-719-2250 WorkD@michigan.gov

MDOT Benjamin Schimberg 517-243-0766 SchimbergB@michigan.gov

Michigan.gov/MiProcurement

Version 2023-1 1 of 4

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

MDOT – ATMS Next Gen – US-23 Flex-lane Extension

Period of Coverage:

3/23/26 – 9/30/26

Requesting Department:

Michigan Department of Transportation

Date:

2/19/26

Agency Project Manager:

Ben Schimberg

Phone:

517-243-0766

DTMB Project Manager:

Dave Work

Phone:

517-719-2250

Brief description of services to be provided:

MDOT is requesting modifications to the Parsons Contract (MA230000000396) for Advanced Traffic Management System (ATMS) configuration, testing support, and documentation. As part of the US- 23 Extension project, there is a need to update ATMS to support the new corridor.

BACKGROUND:

The MDOT implementation of the iNET ATMS product supports Statewide traffic management operations. There are 4 Transportation Operation Centers (TOC) and numerous individual users throughout the MDOT Regions that utilize the software to manage traffic on the roadways.

The US‑23 ATM route extension builds on Michigan’s first flex‑lane deployment and aims to expand active traffic management (ATM) along US‑23 beyond the existing nine‑mile corridor between M‑14 and M‑36. The extension will replicate the existing capabilities and integrate lessons learned from the I‑96 flex route so that the corridor can handle recurring congestion, incidents, special events and winter weather while improving safety and mobility.

PROJECT OBJECTIVE:

The US‑23 ATM route extension will integrate dynamic shoulder lanes, adaptive ramp metering, lane control, variable speed advisories, queue warning and incident detection into a cohesive system.

Work will focus on configuring the ATMS database with new corridor graphics and XML, updating gantry and device configurations, reviewing and expanding automated response plans, and conducting full testing to ensure that lane‑control signs, ramp metering algorithms, detection and communications perform as intended.

Ramp metering is a critical element, as this task will add the first one to the US-23 corridor. Ramp meters use traffic signals on entrance ramps to smooth traffic flow and improve safety. The software will monitor occupancy and volume via inductive loop detectors at multiple points on each ramp and support advanced adaptive metering algorithms. Because of the design that was chosen for the ramp meter location, Parsons is proposing a new software feature to allow for the ramp meter to be driven by Auto Response. This statement of work includes these software adjustments and programs up to 5 different metering rate scenarios to use.

Version 2023-1 2 of 4

SCOPE OF WORK:

1. System Software Design and Development

2. System Unit testing: Parsons internal testing and testing in the MDOT Development environment

3. Package build and submittal to DTMB which shall include:

• Release / build

• Test Cases

• Installation notes

4. Upon acceptance, Deployment to State QA/Test environment

5. QA/Test environment Testing by Parsons and MDOT testing team

6. Formal review of testing results with the testing team and Parsons

7. Assist with software deployment into MDOT’s Production environment

8. Final user acceptance

Total for above activities: $89,260.00

The deadline to complete this work is 6/1/2026.

TASKS:

• Creation of a new ATM corridor graphic and XML files

• Updating gantry numbers and configurations

• Updating and adding auto‑response plans

• Full corridor testing

• Updating system documentation

DELIVERABLES:

Solution implementation in existing ATMS environment. See payment Milestones below.

ACCEPTANCE CRITERIA:

Deliverables will not be considered complete until the Agency and DTMB Project Manager have formally accepted them.

System level acceptance testing will be based on test plans that will be developed to meet the goals set forth in the scope. System level acceptance testing will be scheduled upon completion of modifications and testing of the system in the State’s QA environment using the updated feed.

Testing will include the appropriate level of regression testing based on the nature of the changes and the components affected in the ATMS.

As part of this update, documentation of the installation process will be provided. Included will be a backout process, as well as updated scripts for startup/shutdown and monitoring. Parsons will also provide a test plan and build notes describing the changes that were made and how to test the results of the change.

Version 2023-1 3 of 4

PROJECT CONTROL AND REPORTS:

Individual meetings specific to the US-23 Extension project will be scheduled. The ATMS Core Team will continue to meet on a weekly basis to monitor overall progress.

PAYMENT SCHEDULE:

Payments will be made on an acceptance of Milestone basis. DTMB will pay CONTRACTOR upon receipt of properly completed invoice(s) which shall be submitted to the billing address on the State issued purchase order not more often than monthly. DTMB Accounts Payable area will coordinate obtaining Agency and DTMB Project Manager approvals. All invoices should reflect actual work completed by payment date and must be approved by the Agency and DTMB Project Manager prior to payment. The invoices shall describe and document to the State’s satisfaction a description of the work performed, the progress of the project, and fees. When expenses are invoiced, receipts will need to be provided along with a detailed breakdown of each type of expense.

Payment shall be considered timely if made by DTMB within forty-five (45) days after receipt of properly completed invoices.

Payment Schedule Milestones:

• Solution Design and Development Implementation – 20% $17,852.00

• QA Implementation and Integration Acceptance – 50% $44,630.00

• Production Implementation and Integration Acceptance – 30% $26,778.00

EXPENSES:

The State will NOT pay for any travel expenses, including hotel, mileage, meals, parking, etc.

PROJECT CONTACTS:

The designated Agency Project Manager is:

Name: Ben Schimberg Department: Transportation Area: Bureau of Field Services, TSMO Address: 8885 Ricks Rd City/State/Zip: Lansing, Michigan 48917 Phone Number: 517-243-0766 Email Address: SchimbergB@michigan.gov

The designated DTMB Project Manager(s) is:

Name: Dave Work Department: DTMB Area: Agency Services supporting MDOT Building/Floor: Murray D. Van Wagoner Building, 3rd Floor Address: 425 W. Ottawa Street City/State/Zip: Lansing, Michigan 48909 Phone Number: 517-719-2250

Version 2023-1 4 of 4

Email Address: workd@michigan.gov

AGENCY RESPONSIBILITIES:

The Agency will share the same responsibilities as outlined in the contract.

LOCATION OF WHERE THE WORK IS TO BE PERFORMED:

All work completed by the vendor staff will be at their office physical or remote location(s), or on site when mutually agreed.

EXPECTED CONTRACTOR WORK HOURS AND CONDITIONS:

Work hours are not to exceed eight (8) hours a day, forty (40) hours a week. Normal working hours of 8:00 am to 5:00 pm are to be observed unless otherwise agreed to in writing.

No overtime will be permitted.

STATE OF MICHIGAN

ENTERPRISE PROCUREMENT

DTMB

320 S Walnut Street Lansing, MI 48933 P.O. Box 30026, Lansing, MI 48909

CONTRACT CHANGE NOTICE

CONTRACT SUMMARY

Advanced Traffic Management System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

January 5, 2023 January 5, 2028 5 - 1 Year January 4, 2028

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

N/A

P-Card Direct Voucher (PRC) Other Yes No

2677 Central Park Blvd Suite 275

Southfield Mi 48076

Joseph Brahm

262-391-8056 joseph.brahm@parsons.com

CV0017188

Parsons Transportation Group Inc. of Michigan

C O

N

TR

A C

TO

R

Corbin Montry

517-256-9895

DTMB

Various Various montryc@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

N/ANET45

Change Notice Number 2

Contract Number MA230000000396 to

DESCRIPTION OF CHANGE NOTICE

OPTION EXTENSIONLENGTH OF OPTION LENGTH OF EXTENSION REVISED EXP. DATE

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$3,404,017.00 $32,939.85 $3,436,956.85

Effective 08/15/2025, the parties hereby agree to the following amendments outlined in the attached Statement of Work:

- Deploy module for WZDX output from iNET ATMS.

- Conduct design meetings to confirm WZDX field values.

- Support DTMB in implementation and developer access to feeds.

- Provide internal project management, standards conformance verification, and unit/integration testing.

Primary Goal: Enable output of Work Zone Data Exchange (WZDX) compliant data feeds from the iNET system.

Total Cost: $32,939.85.

AGENCY NAME PHONE EMAIL

MDOT Benjamin Schimberg 517-243-0766 SchimbergB@michigan.gov

DTMB Dave Work 517-719-2250 WorkD@michigan.gov

Program Managers for

Multi-Agency and Statewide Contracts

CHANGE NOTICE NO. 2 TO CONTRACT NO. MA230000000396

Version 2023-1 1 of 3

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

MDOT – ATMS Next Gen – Enable WZDX output

Period of Coverage:

9/1/25 – 2/1/26

Requesting Department:

Michigan Department of Transportation

Date:

8/1/25

Agency Project Manager:

Ben Schimberg

Phone:

517-243-0766

DTMB Project Manager:

Dave Work

Phone:

517-719-2250

Brief description of services to be provided:

MDOT is requesting modifications to the Parsons Contract (MA230000000396) for Advanced Traffic Management System modules. The primary goal is to enable output of Work Zone Data Exchange (WZDX) compliant data feeds from the iNET system.

BACKGROUND:

The MDOT implementation of the iNET ATMS product supports Statewide traffic management operations. There are 4 Transportation Operation Centers (TOC) and numerous individual users throughout the MDOT Regions that utilize the software to manage traffic on the roadways.

PROJECT OBJECTIVE:

Building on the efforts from the implementation of iNET 11 in the ATMS Next-Gen project, which included ingest of WZDX compliant feeds, MDOT is requesting Parson enable the APIs to allow export of WZDX data. This data feed would include all work zone events created within iNET via existing modules. This could include directly entered work zones, or those created automatically via response plans, detected events, and retransmissions of other WZDX data.

SCOPE OF WORK:

Deployment of module to enable WZDX output from existing iNET ATMS implementation. Conduct design meetings to confirm WZDX fields include expected values. Support DTMB in implementation steps, and DTMB developers that are accessing the exposed feeds. Additional activities requiring Parsons support include: Internal project management, verification of WZDX output for standards conformance, Unit and Integration testing of solution.

Total for above activities: $32,939.85

Version 2023-1 2 of 3

The deadline to complete this work is 11/14/2025.

TASKS:

Conduct meetings with MDOT and DTMB to confirm functionality of WZDX API.

Confirm crosswalk of WZDX elements to iNET user interface fields.

Work with DTMB staff to enable module in Dev, QA, and Production ATMS environments.

Support testing and validation activities related to WZDX.

DELIVERABLES:

Solution implementation in existing ATMS environment. See payment Milestones below.

ACCEPTANCE CRITERIA:

Deliverables will not be considered complete until the Agency and DTMB Project Manager have formally accepted them.

PROJECT CONTROL AND REPORTS:

Individual meetings specific to WZDX implementation will be scheduled. The Core Team will continue to meet on a weekly basis to monitor overall progress.

PAYMENT SCHEDULE:

Payments will be made on an acceptance of Milestone basis. DTMB will pay CONTRACTOR upon receipt of properly completed invoice(s) which shall be submitted to the billing address on the State issued purchase order not more often than monthly. DTMB Accounts Payable area will coordinate obtaining Agency and DTMB Project Manager approvals. All invoices should reflect actual work completed by payment date and must be approved by the Agency and DTMB Project Manager prior to payment. The invoices shall describe and document to the State’s satisfaction a description of the work performed, the progress of the project, and fees. When expenses are invoiced, receipts will need to be provided along with a detailed breakdown of each type of expense.

Payment shall be considered timely if made by DTMB within forty-five (45) days after receipt of properly completed invoices.

Payment Schedule Milestones:

• Solution Design and Development Implementation – 20% $6,587.97

• QA Implementation and Integration Acceptance – 50% $16,469.93

• Production Implementation and Integration Acceptance – 30% $9,881.95

EXPENSES:

The State will NOT pay for any travel expenses, including hotel, mileage, meals, parking, etc.

PROJECT CONTACTS:

The designated Agency Project Manager is:

Version 2023-1 3 of 3

Name: Ben Schimberg Department: Transportation Area: Bureau of Field Services, TSMO Address: 8885 Ricks Rd City/State/Zip: Lansing, Michigan 48917 Phone Number: 517-243-0766 Email Address: SchimbergB@michigan.gov

The designated DTMB Project Manager(s) is:

Name: Dave Work Department: DTMB Area: Agency Services supporting MDOT Building/Floor: Murray D. Van Wagoner Building, 3rd Floor Address: 425 W. Ottawa Street City/State/Zip: Lansing, Michigan 48909 Phone Number: 517-719-2250 Email Address: workd@michigan.gov

AGENCY RESPONSIBILITIES:

The Agency will share the same responsibilities as outlined in the contract.

LOCATION OF WHERE THE WORK IS TO BE PERFORMED:

All work completed by the vendor staff will be at their office physical or remote location(s), or on site when mutually agreed.

EXPECTED CONTRACTOR WORK HOURS AND CONDITIONS:

Work hours are not to exceed eight (8) hours a day, forty (40) hours a week. Normal working hours of 8:00 am to 5:00 pm are to be observed unless otherwise agreed to in writing.

ENTERPRISE PROCUREMENT

Department of Technology, Management, and Budget 320 S. Walnut Street 2nd Floor Lansing, MI 48933

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

CONTRACT SUMMARY

Advanced Traffic Management System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

January 5, 2023 January 4, 2028 5 - 12 Months January 4, 2028

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

N/A

P-Card Direct Voucher (PRC) Other Yes No

2677 Central Park Blvd Suite 275

Southfield Mi 48076

Joseph Brahm

262-391-8056 joseph.brahm@parsons.com

CV0017188

Parsons Transportation Group Inc. of Michigan

C O

N

TR

A C

TO

R

Corbin Montry

5175990012

DTMB

Various Various montryc@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

N/ANET45

Change Notice Number 1

Contract Number MA230000000396 to

DESCRIPTION OF CHANGE NOTICE

OPTION EXTENSIONLENGTH OF OPTION LENGTH OF EXTENSION REVISED EXP. DATE

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$3,339,024.00 $64,993.00 $3,404,017.00

Effective 03/24/2025, the parties hereby agree to the following changes outlined in the attached Statement of Work:

- Enhancing the Advanced Traffic Management System (ATMS) video recording module.

- I-96 Corridor Construction Project Testing Support.

- Adding, revising and removing requirements from Project Scope.

- Extended testing support of Ramp Metering module.

- Project Budget and Schedule revisions.

Total Cost: $64,993.00.

Please note the Contract Administrator has been changed to Corbin Montry.

Please note a Program Manager has been changed to Ben Schimberg.

AGENCY NAME PHONE EMAIL

DTMB Dave Work 517-719-2250 WorkD@michigan.gov

MDOT Benjamin Schimberg 517-243-0766 SchimbergB@michigan.gov

Program Managers for

Multi-Agency and Statewide Contracts

CHANGE NOTICE NO. 1 TO CONTRACT NO. MA230000000396

Version 2023-1 1 of 8

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

MDOT – ATMS Next Gen Scope, Video, and I-96 Support

Period of Coverage:

10/11/24 – 10/31/25

Requesting Department:

MDOT – Intelligent Transportation Systems Program Office

Date:

10/11/24

Agency Project Manager:

Ben Schimberg

Phone:

517-243-0766

DTMB Project Manager:

Dave Work

Phone:

517-719-2250

Brief description of services to be provided:

MDOT is requesting scope, schedule, and budget changes to support the implementation of ATMS Next Gen.

BACKGROUND:

The ATMS Next Gen project is implementing software enhancements to the existing State-hosted ATMS software to integrate MDOT’s Intelligent Transportation System (ITS) devices. ATMS will provide MDOT’s Transportation Operation Centers (TOCs) the ability to operate, monitor, and manage ITS devices to support the real-time management of MDOT’s roadways.

The project is delivering enhancements in 5 separate builds. This document is addressing changes (deletions, additions and updates) to the project requirements for the 5th and final build of the project. Significant changes to the video recording module and additional support for testing of Ramp Metering are also included.

PROJECT OBJECTIVE:

• Project Scope Revisions:

o Requirements to be removed from project scope o Requirements to be revised in project scope o Requirement to be enhanced in project scope o Requirements to be added to project scope

• Project Budget Revisions

• Project Schedule Revisions

Project Scope Revisions:

Requirements to be removed from project scope:

• Requirement 4.4 o Remove: The ATMS must timestamp and record all activities and commands performed within the software, both manual and automated features. The ATMS

Version 2023-1 2 of 8 must provide the ability for an authorized user to configure the ATMS to not record specific activities and commands (e.g., PTZ commands).

• Requirement 6.15 o Remove: The ATMS should provide the ability to create a map view on demand by geo-fencing an area (graying out the area outside of the selected area) for use in managing incidents and/or events.

• Requirement 9.11.2 o Remove: Manually override the location of a portable CCTV unit.

• Requirement 11.12 o Remove (Cost $25,945): The ATMS should capture and display wrong way driving detection events detected by vehicle detection systems, by direction and lane for of all lanes in each direction at vehicle detector locations.

• Requirement 12.60 o Remove: The ATMS must auto-generate suggested responses based on real-time weather notifications provided by NWS. Automated responses may include DMS messaging, CCTV camera preset, variable speed advisory, etc.

• Requirement 19.4 o Remove (Cost $35,977): The ATMS should provide call-tracking capable of interfacing with Voice over Internet Protocol (VOIP) phone systems with the ability to populate incoming and outgoing call information into the call log without action by the Traffic Operations Specialist, such as the phone number and time the call was made or received. The State of Michigan currently utilizes the Cisco Unified Communications Manager version 12.5 for its VOIP phone systems.

• Requirement 20.3 o Remove: The ATMS must integrate with social media, at a minimum Twitter, to communicate planned event, incident, and traveler information with the traveling public. The ATMS must prepopulate a social media message based on event details for a user to review, edit, and confirm prior to posting to social media.

Requirements to be revised in project scope:

• Requirement 12.7 o Partial Removal: The ATMS must allow a response plan to use any type of device, such as posting a message to a DMS and repositioning a CCTV camera).

• Requirement 7.10 o Partial Removal: The ATMS user interface must provide the ability to filter field device icons by type, subtype, designated favorites., and a metric for frequently used devices (e.g., number of times accessed, duration of time the device was actively in use).

• Requirement 12.16 o Partial Removal: The ATMS must have the ability of scheduling messages to be posted and removed on individual or a group of DMS with full recurrence capabilities in typical scheduling functions such as time of day (TOD), day of week (DOW), day of month (DOM), and day of year (DOY), and holidays.

• Requirement 12.44

Version 2023-1 3 of 8 o Partial Removal: The ATMS must auto-generate suggested responses based on real-time weather notifications provided by NWS. Automated responses may include DMS messaging, CCTV camera preset, variable speed advisory, etc.

• Requirement 13.10 o Partial Removal: The ATMS must not allow an event to be cleared terminated if there are required fields that are incomplete. Required fields must be configurable (not hard coded) and shall be easily modified for what fields are populated.

• Requirement 13.24 o Revised Requirement: The ATMS must provide the ability to automatically associate an event with a work zone if it occurs within the boundary of an active work zone event. Parsons changed “Nearby Work Zone” to “Work Zone Related”

• Requirement 13.32 o Partial Removal: The ATMS must have the ability to automatically generate an event based upon inputs from third-party systems including SSP, Weather Feed, Waze, etc.

• Requirement 15.8 o Partial Removal: The ATMS must provide the ability to dismiss, acknowledge, and/or combine alerts associated with an event via the GUI and SMS/email.

• Requirement 18.5 o Partial Removal: The ATMS should provide the ability to generate reports which compares current vs. historical travel conditions. Historical travel condition data should be available as defined in the MDOT ITS/TOC Retention Schedule.

Requirement to be enhanced in project scope:

• Enhance Requirement 9.10 (Cost $43,502): The ATMS should be able to record and archive CCTV camera streaming video of a rolling or continuous user defined period on-demand with the requirements listed below:

ID CCTV Video Recording Requirements 1 The ATMS must not inhibit any other CCTV functionality or software capability while video recording is occurring.

2 The ATMS must allow an operator to pre-schedule video recording start and stop times by CCTV camera.

3 The ATMS must provide an operator the option to select a CCTV preset when pre-scheduling a recording and implement that preset at the video recording start time.

4 The ATMS must allow an operator to cancel a pre-scheduled video recording prior to the video recording start time.

5 The ATMS must allow an operator to start and stop a CCTV video recording on demand.

6 The ATMS must allow an operator to stop any active recording, whether pre-scheduled or an on-demand recording.

7 The ATMS must stop an on-demand video recording if the length of recording reaches a system defined maximum duration limit (e.g., 48 hours). The maximum duration limit must be able to be adjusted by an authorized user.

Version 2023-1 4 of 8

8 The ATMS must notify operators upon accessing a CCTV and continuously while open, that the CCTV is actively being recorded, such as a red "recording" dot.

9 The ATMS must allow an operator to view the following information during an active recording:

- The operator that started the recording

- If the recording was pre-scheduled or started on-demand

- If pre-scheduled, identify the scheduled stop date/time This information must not be captured in the recording (e.g., box that displays when hovering over red “recording” dot).

10 The ATMS must log video recording details with each video recording file, which includes but is not limited to: CCTV ID, MDOT Region, recording start date/time, recording end date/time, duration of recording, user that started/schedule recording, user that ended recording, recording category (using dropdown options), user entered description, user entered recording notes, and file size.

9 The ATMS must allow an operator to assign a recording category (using predefined categories) and enter a description and recording notes to a video recording.

10 The ATMS must allow an authorized user to view the video log of all available recordings.

11 The ATMS must allow an authorized user to sort and filter the list of available videos by CCTV ID, MDOT Region, recording start date/time, recording end date/time, duration of recording, user that started/schedule recording, user that ended recording, recording category, and file size.

12 The ATMS must allow an authorized user to perform a word search of the user entered description and recording notes.

13 The ATMS must allow an authorized user to play back available video recordings.

14 The ATMS must provide the ability to limit the number of CCTV cameras that are able to record simultaneously (i.e. 10 CCTV cameras). The maximum number of CCTV cameras that can record simultaneously must be able to be adjusted by an authorized user.

15 The ATMS must store video recordings and the associated information log in accordance with MDOT's retention policy.

16 The ATMS must provide the ability to create and save ad-hoc monthly reports of all available video recordings and associated information log.

17 The ATMS must allow an authorized user (i.e. supervisor) to delete videos via the ATMS user interface.

18 The ATMS must allow an authorized user (i.e. supervisor) to view the remaining video storage space via the ATMS user interface.

19 The ATMS must notify an authorized user (i.e. admin) if the video storage space has reached the remaining capacity threshold (i.e. 5% storage remaining). The video storage remaining capacity threshold must be able to be adjusted by an authorized user (i.e. admin).

20 The ATMS must notify an operator that the video storage space has reached the remaining capacity threshold when the following actions are performed:

• When an operator pre-schedules a video recording.

Version 2023-1 5 of 8

• When an operator attempts to start an on-demand recording.

21 The ATMS must automatically stop and save an active recording if the video storage space is exceeded during a video recording.

22 The ATMS must allow an authorized user to transcode one or more available videos to a lower bit rate.

Requirements to be added to project scope:

• New Requirement #1: Make the Region and Roadway fields mandatory in the DSS Library

DMS message window. Note: Only ADMINS can currently view and edit DSS templates.

o Parsons Time and Cost estimate:

Cost estimate: $4,160.00

• New Requirement #2: Include Surface friction in the plot options for ESS devices.

o Parsons Time and Cost estimate:

Cost estimate: $6,656.00

I-96 Corridor Construction Project Testing Support:

The I-96 construction project requires the support of the vendor, Parsons for configuration, testing and implementation of flex lane and ramp metering technology on the I-96 corridor. Additional activities requiring Parsons support include: Meeting support for MDOT and other consultants, Dot stand-in downloads and testing of gantry signs, Onsite support before go-live, Open to Traffic onsite support.

Total for above activities: $26,127.00

Ramp Metering - Shutdown Gap Approach with Enabled Stop Demand Detector Mode:

The requested enhancement involves configuring the ramp meter to transition between metered and non-metered states based on the actuations of the demand detector. Specifically, a value between 1 and 10 seconds can be set for the ramp meter to monitor the time between demand detector actuations. If the time between actuations exceeds the set value, the ramp meter will transition to a non-metered state (yellow flash). Conversely, if the time between actuations does not exceed the set value, the ramp meter will remain in a metered state. The main reason for proposing this enhancement is to prevent the ramp meter from transitioning abruptly from metering to non-metering state, which could cause unsafe merging conditions on the ramp. This enhancement ensures that the ramp meter controller waits until the ramp clears before transitioning to a non-metering state, addressing the client's safety concerns.

Currently, the system uses the enabledCall Demand Detector Mode. In this mode, if a demand detector fails, the Shutdown gap will never reach the configured value, necessitating manual intervention to switch the meter to yellow flash. To support the main enhancement of the shutdown gap approach and ensure smooth operation, we propose switching to the enabledStop Demand Detector Mode, similar to the approach used by INDOT. In this mode, if a demand detector fails, the meter will automatically transition to yellow flash after the failure threshold is reached, even during regular metering operations. This change is a necessary step to implement the main safety enhancement effectively.

This enhancement primarily aims to improve safety by preventing abrupt transitions from metering to non-metering states, thereby addressing concerns related to unsafe merging conditions on the

Version 2023-1 6 of 8 ramp. The additional task of ensuring automatic transitions in the event of demand detector failures supports the main enhancement, ensuring its effective implementation and enhancing overall traffic management efficiency.

Parsons is requested to develop firmware changes, create and execute test scenarios for local operations as well as ATMS control, and deploy enhancements described above to ramp meter controllers in the I-96 Corridor Project.

Total for above activities: $12,200.00

Project Budget Revisions:

The contract value will be increased by $64,993.00 to accommodate the changes to the requirements.

Vendor cost estimates for the requirements:

• Requirement 9.10 reduction: $ - 43,502.00

• Requirement 11.12 reduction: $ - 21,733.00

• Requirement 19.4 reduction: $ - 35,977.00

• New Requirement #1: $ 4,160.00

• New Requirement #2: $ 6,656.00

• Revised Video Recording Requirements: $ 117,062.00

• I-96 Corridor Testing Support: $ 26,127.00

• I-96 Ramp Meter Development: $ 12,200.00

Total Change Notice: $ 64,993.00

Project Schedule Revisions:

To accommodate the changes in the project scope, an additional 3-months are required for delivery and implementation of the requirements into the state’s QA environment. The additional time is needed for QA and UAT testing, implementation activities and project closure.

SCOPE OF WORK:

The scope of work includes development effort to implement additional requirements, meetings with MDOT and DTMB, and support of installation and testing of all modules and enhancements detailed above.

TASKS:

Technical development is needed from Parsons for the above requirements. DTMB support will also be required for the installation of the software, testing and production implementation.

DELIVERABLES:

Deliverables will include the software enhancements to satisfy the Build-5 requirements of the project. Parsons will provide technical and administrative support for these items, consistent with what has been provided with the first four builds of the project. Release notes, test plans, testing support, installation guide and back-out plans to support the implementation.

Version 2023-1 7 of 8

ACCEPTANCE CRITERIA:

The vendor will provide a Build-5 Test plan for both QA and UAT testing that addresses all the requirements in Build-5. Testing and acceptance will follow the same processes used in the first four builds.

Deliverables will not be considered complete until the Agency and DTMB Project Manager have formally accepted them.

PROJECT CONTROL AND REPORTS:

The Core Team will continue to meet on a weekly basis to monitor project process. At the appropriate times there will be weekly QA and UAT testing touchpoints to monitor and discuss progress during testing.

PAYMENT SCHEDULE:

Payment will be consistent with processes used during the first four builds of the project.

• Vendor payment will be made upon receipt of software

• A final payment will be made upon production implementation and final acceptance of the software

Payments will be made at the time of Solution Integration and Acceptance of the software and final payment will be made at Integration Acceptance. DTMB will pay CONTRACTOR upon receipt of properly completed invoice(s) which shall be submitted to the billing address on the State issued purchase order not more often than monthly. DTMB Accounts Payable area will coordinate obtaining Agency and DTMB Project Manager approvals. All invoices should reflect actual work completed by payment date and must be approved by the Agency and DTMB Project Manager prior to payment. The invoices shall describe and document to the State’s satisfaction a description of the work performed, the progress of the project, and fees. When expenses are invoiced, receipts will need to be provided along with a detailed breakdown of each type of expense.

Payment shall be considered timely if made by DTMB within forty-five (45) days after receipt of properly completed invoices.

Payment Schedule Milestones:

• Solution Integration and Acceptance – 50%

• Integration Acceptance – 50%

Payment shall be considered timely if made by DTMB within forty-five (45) days after receipt of properly completed invoices.

EXPENSES:

The State will NOT pay for any travel expenses, including hotel, mileage, meals, parking, etc.

PROJECT CONTACTS:

The designated Agency Project Manager is:

Name: Ben Schimberg Department: Transportation

Version 2023-1 8 of 8

Area: Bureau of Field Services, TSMO Address: 8885 Ricks Rd City/State/Zip: Lansing, Michigan 48917 Phone Number: 517-243-0766 Email Address: SchimbergB@michigan.gov

The designated DTMB Project Manager(s) is:

Name: Dave Work Department: Technology, Management, and Budget Area: Agency Services supporting MDOT Building/Floor: Van Wagoner Building 3rd Floor Address: 425 West Ottawa Street City/State/Zip: Lansing, Michigan-48821 Phone Number: 517-719-2250 Email Address: WorkD@michigan.gov

AGENCY RESPONSIBILITIES:

Review and approval of the deliverables and submitted invoice(s).

LOCATION OF WHERE THE WORK IS TO BE PERFORMED:

All work completed by the vendor staff will be at their office physical or remote location(s), or on site when mutually agreed.

EXPECTED CONTRACTOR WORK HOURS AND CONDITIONS:

Work hours are not to exceed eight (8) hours a day, forty (40) hours a week. Normal working hours of 8:00 am to 5:00 pm are to be observed unless otherwise agreed to in writing.

NOTICE OF CONTRACT

NOTICE OF CONTRACT NO. 230000000396 .

between

THE STATE OF MICHIGAN

and

C O

N

TR

A C

TO

R

Parsons Transportation Group Inc. of Michigan

ST

A

TE

Pr og ra m

M an ag er

Multi Multi

2677 Central Park Blvd. Suite 275 Southfield, MI 48076 Joseph Brahm

C on tra ct

Ad m in is tra to r Christopher Martin DTMB

262-391-8056 517-643-2833 joseph.brahm@parsons.com martinc20@michigan.gov

CV0017188

CONTRACT SUMMARY

DESCRIPTION: Advanced Traffic Management System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE

INITIAL AVAILABLE

OPTIONS

EXPIRATION DATE BEFORE

CHANGE(S) NOTED BELOW

1/5/2023 1/4/2028 5, one-year 1/4/2028

PAYMENT TERMS DELIVERY TIMEFRAME

Net 45

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

☐ P-card ☐ Payment Request (PRC) ☐ Other ☒ Yes ☐ No

MINIMUM DELIVERY REQUIREMENTS

MISCELLANEOUS INFORMATION

ESTIMATED CONTRACT VALUE AT TIME OF EXECUTION $3,339,024.00

STATE OF MICHIGAN PROCUREMENT

Department of Technology Management & Budget 320 South Walnut Street PO Box 30026 Lansing, MI 48909

CONTRACT NO. 230000000396

Program Managers for Multi-Agency and Statewide Contracts

AGENCY NAME PHONE EMAIL

MDOT Joe McAttee 517-636-6058 mcatteej@michigan.gov DTMB Dave Work 517-719-2250 workd@michigan.gov

CONTRACT NO. 230000000396

FOR THE CONTRACTOR:

Company Name

Authorized Agent Signature

Authorized Agent (Print or Type)

Date

FOR THE STATE:

Signature

Name & Title

Agency

Date

SOFTWARE TERMS AND CONDITIONS

These Terms and Conditions, together with all Schedules (including the Statement(s) of Work), Exhibits and any other applicable attachments or addenda (Collectively this “Contract”) are agreed to between the State of Michigan (the “State”) and Parsons Transportation Group, Inc. of Michigan (“Contractor”), A MICHIGAN CORPORATION. This Contract is effective on 1/5/2023 (“Effective Date”), and unless terminated, will expire on 1/4/2028 (the “Term”).

This Contract may be renewed for up to five additional one-year period(s). Renewal is at the sole discretion of the State and will automatically extend the Term of this Contract. The State will document its exercise of renewal options via Contract Change Notice.

1. Definitions. For the purposes of this Contract, the following terms have the following meanings:

“Acceptance” has the meaning set forth in Schedule I.

“Affiliate” of a Person means any other Person that directly or indirectly, through one or more intermediaries, controls, is controlled by, or is under common control with, such Person. For purposes of this definition, the term “control” (including the terms “controlled by” and “under common control with”) means the direct or indirect ownership of more than fifty percent (50%) of the voting securities of a Person.

“Allegedly Infringing Materials” has the meaning set forth in Section 17.2(b).

“Approved Third Party Components” means all third party components, including Open-Source Components, that are included in or used in connection with the Software and are specifically identified by Contractor in the Contractor’s Bid Response or as part of the State’s Security Accreditation Process defined in Schedule E – Data Security Schedule.

“Authorized Users” means all Persons authorized by the State to access and use the Software under this Contract, subject to the maximum number of users specified in the applicable Statement of Work.

“Business Day” means a day other than a Saturday, Sunday or other day on which the State is authorized or required by law to be closed for business.

“Business Requirements Specification” means the initial specification setting forth the State’s business requirements regarding the features and functionality of the Software, as set forth in a Statement of Work.

“Change” has the meaning set forth in Section 2.2.

“Change Notice” has the meaning set forth in Section 2.2(b).

“Change Proposal” has the meaning set forth in Section 2.2(a).

“Change Request” has the meaning set forth in Section 2.2.

“Confidential Information” has the meaning set forth in Section 22.1.

“Configuration” means State-specific changes made to the Software without Source Code or structural data model changes occurring.

“Contract” has the meaning set forth in the preamble.

“Contract Administrator” is the individual appointed by each party to (a) administer the terms of this Contract, and (b) approve any Change Notices under this Contract. Each party’s Contract Administrator will be identified in a Statement of Work.

“Contractor” has the meaning set forth in the preamble.

“Contractor’s Bid Response” means the Contractor’s proposal submitted in response to the Solicitation Type.

“Contractor Hosted” means the Hosted Services are provided by Contractor or one or more of its Permitted Subcontractors.

“Contractor Personnel” means all employees of Contractor or any subcontractors or Permitted Subcontractors involved in the performance of Services hereunder.

“Contractor Project Manager” means the individual appointed by Contractor and identified in a Statement of Work to serve as the primary contact with regard to services, to monitor and coordinate the day-to-day activities of this Contract, and to perform other duties as may be further defined in this Contract, including an applicable Statement of Work.

“Customization” means State-specific changes to the Software's underlying Source Code or structural data model changes.

“Deliverables” means the Software, and all other documents and other materials that Contractor is required to or otherwise does provide to the State under this Contract and otherwise in connection with any Services, including all items specifically identified as Deliverables in a Statement of Work and all Work Product.

“Deposit Material” refers to material required to be deposited pursuant to Section 28.

“Documentation” means all user manuals, operating manuals, technical manuals and any other instructions, specifications, documents or materials, in any form or media, that describe the functionality, installation, testing, operation, use, maintenance, support, technical or other components, features or requirements of the Software.

“DTMB” means the Michigan Department of Technology, Management and Budget.

“Effective Date” has the meaning set forth in the preamble.

“Fees” means the fees set forth in the Pricing Schedule attached as Schedule B.

“Financial Audit Period” has the meaning set forth in Section 23.1.

“Harmful Code” means any software, hardware or other technologies, devices or means, the purpose or effect of which is to: (a) permit unauthorized access to, or to destroy, disrupt, disable, encrypt, modify, copy, or otherwise harm or impede in any manner, any (i) computer, software, firmware, data, hardware, system or network, or (ii) any application or function of any of the foregoing or the integrity, use or operation of any data Processed thereby; or (b) prevent the State or any Authorized User from accessing or using the Services as intended by this Contract, and includes any virus, bug, trojan horse, worm, backdoor or other malicious computer code and any time bomb or drop dead device.

“HIPAA” has the meaning set forth in Section 21.1.

“Hosted Services” means the hosting, management and operation of the Operating Environment, Software, other services (including support and subcontracted services), and related resources for remote electronic access and use by the State and its Authorized Users, including any services and facilities related to disaster recovery obligations.

“Implementation Plan” means the schedule included in a Statement of Work setting forth the sequence of events for the performance of Services under a Statement of Work, including the Milestones and Milestone Dates.

“Intellectual Property Rights” means all or any of the following: (a) patents, patent disclosures, and inventions (whether patentable or not); (b) trademarks, service marks, trade dress, trade names, logos, corporate names, and domain names, together with all of the associated goodwill; (c) copyrights and copyrightable works (including computer programs), mask works and rights in data and databases; (d) trade secrets, know-how and other confidential information; and (e) all other intellectual property rights, in each case whether registered or unregistered and including all applications for, and renewals or extensions of, such rights, and all similar or equivalent rights or forms of protection provided by applicable law in any jurisdiction throughout the world.

“Key Personnel” means any Contractor Personnel identified as key personnel in the Contract.

“Loss or Losses” means all losses, including but not limited to, damages, liabilities, deficiencies, claims, actions, judgments, settlements, interest, awards, penalties, fines, costs or expenses of whatever kind, including reasonable attorneys' fees and the costs of enforcing any right to indemnification hereunder and the cost of pursuing any insurance providers.

“Maintenance Release” means any update, upgrade, release or other adaptation or modification of the Software, including any updated Documentation, that Contractor may generally provide to its licensees from time to time during the Term, which may contain, among other things, error corrections, enhancements, improvements or other changes to the user interface, functionality, compatibility, capabilities, performance, efficiency or quality of the Software.

“Milestone” means an event or task described in the Implementation Plan under a Statement of Work that must be completed by the corresponding Milestone Date.

“Milestone Date” means the date by which a particular Milestone must be completed as set forth in the Implementation Plan under a Statement of Work.

“New Version” means any new version of the Software, including any updated Documentation, that the Contractor may from time to time introduce and market generally as a distinct licensed product, as may be indicated by Contractor's designation of a new version number.

“Open-Source Components” means any software component that is subject to any open-source copyright license agreement, including any GNU General Public License or GNU Library or Lesser Public License, or other obligation, restriction or license agreement that substantially conforms to the Open Source Definition as prescribed by the Open Source Initiative or otherwise may require disclosure or licensing to any third party of any source code with which such software component is used or compiled.

“Operating Environment” means, collectively, the platform, environment and conditions on, in or under which the Software is intended to be installed and operate, as set forth in a Statement of Work, including such structural, functional and other features, conditions and components as hardware, operating software, system architecture, configuration, computing hardware, ancillary equipment, networking, software, firmware, databases, data, and electronic systems (including database management systems).

“PAT” means a document or product accessibility template, including any Information Technology Industry Council Voluntary Product Accessibility Template or VPAT®, that specifies how information and software products, such as websites, applications, software and associated content, conform to WCAG 2.0 Level AA.

“Permitted Subcontractor” means any third party hired by Contractor to perform Services for the State under this Contract or have access to State Data.

“Person” means an individual, corporation, partnership, joint venture, limited liability company, governmental authority, unincorporated organization, trust, association or other entity.

“Pricing Schedule” means the schedule attached as Schedule B.

“Process” means to perform any operation or set of operations on any data, information, material, work, expression or other content, including to (a) collect, receive, input, upload, download, record, reproduce, store, organize, combine, log, catalog, cross-reference, manage, maintain, copy, adapt, alter, translate or make other improvements or derivative works, (b) process, retrieve, output, consult, use, disseminate, transmit, submit, post, transfer, disclose or otherwise provide or make available, or (c) block, erase or destroy. “Processing” and “Processed” have correlative meanings.

“Representatives” means a party's employees, officers, directors, partners, shareholders, agents, attorneys, successors and permitted assigns.

“RFP” means the State’s request for proposal designed to solicit responses for Services under this Contract.

“Services” means any of the services, including but not limited to, Hosted Services, Contractor is required to or otherwise does provide under this Contract.

“Service Level Agreement” means the schedule attached as Schedule D, setting forth the Support Services Contractor will provide to the State, and the parties' additional rights and obligations with respect thereto.

“Site” means the physical location designated by the State in, or in accordance with, this Contract or a Statement of Work for delivery and installation of the Software.

“Software” means Contractor’s software as set forth in a Statement of Work, and any Maintenance Releases or New Versions provided to the State and any Customizations or Configurations made by or for the State pursuant to this Contract, and all copies of the foregoing permitted under this Contract.

“Source Code” means the human readable source code of the Software to which it relates, in the programming language in which the Software was written, together with all related flow charts and technical documentation, including a description of the procedure for generating object code, all of a level sufficient to enable a programmer reasonably fluent in such programming language to understand, build, operate, support, maintain and develop modifications, upgrades, updates, adaptations, enhancements, new versions and other derivative works and improvements of, and to develop computer programs compatible with, the Software.

“Specifications” means, for the Software, the specifications collectively set forth in the Business Requirements Specification, Technical Specification, Documentation, RFP or Contractor’s Bid Response, if any, for such Software, or elsewhere in a Statement of Work.

“State” means the State of Michigan.

“State Data” has the meaning set forth in Section 21.1.

“State Hosted” means the Hosted Services are not provided by Contractor or one or more of its Permitted Subcontractors.

“State Materials” means all materials and information, including documents, data, know-how, ideas, methodologies,…