230000001291.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 2 to

Contract Number MA230000001291

C O

N

TR

AC

TO

R

Kapsch TrafficCom USA, Inc.

2855 Premiere Parkway

Duluth GA 30097

David Hernandez

845-220-7802 david.hernandez2@kapsch.net

VS0008701

ST

AT

E

Pr og ra m

M an ag er

Various Various

C on tr ac t Ad m in is tr at or Corbin Montry DTMB

517-599-0012 montryc@michigan.gov

CONTRACT SUMMARY

Connected Vehicle – Advanced Traffic Management System (CV-ATMS)

INITIAL EFFECTIVE DATE

July 25, 2023

INITIAL EXPIRATION DATE

July 24, 2028

INITIAL AVAILABLE OPTIONS

5 - 1 Year

EXPIRATION DATE BEFORE

July 24, 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

$5,557,655.00

VALUE OF CHANGE NOTICE

$45,539.97

ESTIMATED AGGREGATE CONTRACT VALUE

$5,603,194.97

DESCRIPTION

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

Effective 03/25/2026, the parties hereby agree to add the following Statement of Work for modifications to the Connected Vehicle - Advanced Traffic Management System modules (CV-ATMS). The primary goal is to refine the release schedule, including new models to enhance existing work zone functionality, descope requirements, and to update the application to be compliant with the WCAG 2.1 AA standard. This contract is hereby increased by $45,539.97.

The contract is amended to incorporate the below updated ADA Compliance Language. This language replaces, in its entirety, the previous WCAG 2.0 Level AA language. All other terms, conditions, specifications and pricing remain the same. Per contractor and agency agreement, and DTMB Central Procurement Services approval.

Updated ADA Compliance Language:

5. ADA COMPLIANCE:

The State is required to comply with the Americans with Disabilities Act of 1990 (ADA) and has adopted standards and procedures regarding accessibility requirements for websites, applications, content, and electronic documents. Due to a change in the law, the State is required to comply with specific accessibility standards for websites, applications, content and documents.

Starting 4/24/2026, throughout the Term, all websites, applications, software, content, and electronic documents, including but not limited to mobile applications, text, images, sounds, videos, controls, animations, links, and documents (including files in the following formats: PDF, word processing, presentation, and spreadsheet), created, provided, or made available by the Contractor under this Contract, must comply with WCAG 2.1 Level AA.

CHANGE NOTICE NO. 2 TO CONTRACT NO. MA230000001291

Program Managers for

Multi-Agency and Statewide Contracts

AGENCY NAME PHONE EMAIL

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

MDOT Joseph Gorman 517-282-0315 GormanJ4@michigan.gov

Michigan.gov/MiProcurement

Version 2023-1 1 of 11

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

MDOT – CV-ATMS – Scope, Schedule, and Budget Revisions

Period of Coverage:

10/1/25 – 8/14/26

Requesting Department:

Michigan Department of Transportation

Date:

9/15/25

Agency Project Manager:

Joe Gorman

Phone:

517-282-0315

DTMB Project Manager:

Dave Work

Phone:

517-719-2250

Brief description of services to be provided:

MDOT is requesting modifications to the Kapsch Contract (MA230000001291) for the Connected Vehicle - Advanced Traffic Management System modules (CV-ATMS). The primary goal is to refine the release schedule, including new models to enhance existing work zone functionality and to update the application to be compliant with the WCAG 2.1 AA standard.

BACKGROUND:

The MDOT implementation of CV-ATMS to improve transportation safety, mobility and system performance that will integrate, remotely operate and manage field devices for Connected Vehicles. The application will also provide a message credential solution for vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) communications, along with a Lane Closure Request Application, Weather, and Smart Work Zone applications throughout the MDOT Regions that utilize the software to manage traffic on the roadways.

PROJECT OBJECTIVE:

This SOW includes the following work items:

• Work Zone: Two-way State Route Road Restrictions $ 98,459.00

• Work Zone: Detour Description $ 10,274.00

• Work Zone: Banned Word Support $ 9,418.00

• ADA WCAG 2.1AA Remediation $ 42,286.00

• Descoped Requirements -$114,897.03

Total: $ 45,539.97

Building on the existing work zone functionality within CV-ATMS with the additional items above will allow MDOT to improve overall support of work zones. The ADA WCAG 2.1 AA remediations are needed to achieve ADA compliance standards.

Version 2023-1 2 of 11

Work Zone: Two-way State Route Road Restrictions:

MDOT needs to efficiently manage work zones consisting of closures in multiple directions on non-divided routes as a single event within the system and publish the event as two related closures to comply with the WZDx/Connected Work Zone (CWZ) Standard.

Kapsch will implement a supporting workflow:

1. The Direction will be populated based on the event location/network point/node selection.

Additionally, a bi-direction check-box will be made available on the Basic tab of the Work Zone event.

2. If selected, the event description will be updated based on the direction of the event like NB/SB or EB/WB.

3. The system will simultaneously display a lane restriction entry block for each bound, pre-populated with provided lane configurations.

4. The event will be published externally as two separate closures, one for each direction.

5. The externally published events will be automatically related through a method defined in the WZDX/CWZ standard.

Additionally, vehicle impact will be populated based on pre-determined lane status logic for all closure types.

Work Zone: Detour Description:

Kapsch will implement a workflow to include a detour description within a work zone event description. This will consist of a free form text field that will be added as requested to the Detour information in the Advanced tab of the Work Zone event. When the vehicle impact is a total closure, the text filed will become editable. If populated, “Detour:” and the entered text will be automatically appended to the event description text field. This change will be visible prior to saving the event, update without user interaction to refresh the event description, and persist through event descriptions updates such as the addition or configuration of lanes restrictions.

Work Zone: Banned Word Support:

Kapsch will implement a global list of banned words as part of a software deployment. The list will be configurable at the system administrator level during deployment. This list will minimally apply to all free text fields published to the public. MDOT to provide the list of words to be included in this list. The System Configuration document will be updated to include instructions to add or remove words in the future by administrators.

Version 2023-1 3 of 11

ADA WCAG 2.1AA Remediation:

The following is a list of American Disabilities Act WCAG 2.1 AA requirements to be addressed within this SOW. This list is not considered to be exhaustive, and additional remediation may be necessary following review of software by the State.

Standard Guideline Standard Description Notes

1.3 Adaptable 1.3.4

Orientation

WCAG

2.1 AA

Content does not restrict view to a single display orientation

There are no Orientation restrictions on CV-ATMS

1.3 Adaptable 1.3.5

Identify Input Purpose

WCAG

2.1 AA

The purpose of input fields collecting user information can be programmatically determined

CV-ATMS form fields do not have any autocomplete functionality. Kapsch to make all fields accessible using screen reader technology.

1.4 Distinguishable 1.4.10

Reflow

WCAG

2.1 AA

Content can be presented without scrolling in two dimensions at 320px width

No horizontal scrolling in the CV-ATMS system.

1.4 Distinguishable 1.4.11 Non-

text Contrast

WCAG

2.1 AA

UI components and graphics have contrast ratio of at least 3:1

CV-ATMS UI is updated to support at least 3:1 contrast ratio

1.4 Distinguishable 1.4.12 Text

Spacing

WCAG

2.1 AA

No loss of content when text spacing is adjusted

CV-ATMS uses Fixed-width containers which don't accommodate increased text spacing.

1.4 Distinguishable 1.4.13

Content on Hover or Focus

WCAG

2.1 AA

No loss of content when text spacing is adjusted

CV-ATMS UI is updated to support Hover/focus content

2.1 Keyboard

Accessible

2.1.4 Character Key Shortcuts

WCAG

2.1 A

Single-character shortcuts can be turned off, remapped, or are active only on focus

CV-ATMS does not use any single-character shortcuts

2.5 Input Modalities 2.5.1 Pointer

Gestures

WCAG

2.1 A

Multi-point or path-based gestures have

CV-ATMS does not use any single-character shortcuts

Version 2023-1 4 of 11 single-pointer alternative

2.5 Input Modalities 2.5.2 Pointer

Cancellation

WCAG

2.1 A

Functions use up-events rather than down-events

2.5 Input Modalities 2.5.3 Label

in Name

WCAG

2.1 A

Accessible name contains the visible text label

2.5 Input Modalities 2.5.4 Motion

Actuation

WCAG

2.1 A

Motion-triggered functionality has UI component alternative

4.1 Compatible 4.1.3 Status

Messages

WCAG

2.1 AA

Status messages can be programmatically determined without focus

Descoped Requirements:

The following is a list of requirements to be descoped from the project.

A B C

Table Row Original Order

Bus.

Spec.

Number

Bus.

Spec.

Type

Business Specifications

8 FIELD DEVICES

8.12 The CV-ATMS must send and receive the following information between the CV-ATMS and field device:

156 8.12.7 O Video/image analytics alert triggers

9 DEVICE CONFIGURATION AND MONITORING

9.2 The CV-ATMS must enable field device configuration and device management using the following methods:

161 9.2.2 R SSH

163 9.2.4 O Web Socket/Web URL Service

164 9.2.5 O Secure CLI service

Version 2023-1 5 of 11

165 9.2.6 O Secure API service

179 9.5 R

The CV-ATMS must forward a Real-time Position Correction Message in one of multiple formats (NMEA, SBAS, VRF-RTK) from a State-owned multiple GNSS source with multiple satellite constellations to broadcast to the field device and then outbound from the RSU V2X device to equipped vehicles.

215 9.15 R

The CV-ATMS must enable field device configuration and setup by implementing vendor supplied and system ingested SNMPv3 "customized" MIBs and provide system configuration and deployment support of those custom variables by site/supplier device type.

218 9.18 O

The CV-ATMS should enable, ping, verify, etc. with field devices to store location destination 'endpoint and port number' or file path in the user interface Last Known Working Configuration of the field device to a destination.

220 9.20 O

The CV-ATMS should enable the storage, retrieval, and redeployment of Last Known Working Configuration settings to a Device ID/Site ID to be tested and validated within the user interface after deployed device POST process to verify the re-deployed device configuration settings to a new user selected field device.

10 DATA MANAGEMENT AND EXCHANGE

281 10.6 R The CV-ATMS must be capable of receiving data from all edge processed information.

398 17 ROADWAY FLOODING

399 17.1 O The CV-ATMS should ingest data from MDOT’s supervisory control and data acquisition (SCADA) pump station system.

400 17.2 O

The CV-ATMS should utilize, as a minimum, weather analytics and MDOT pump station information to identify flooding based on user-defined thresholds.

401 17.3 O The CV-ATMS should utilize, as a minimum, weather analytics and MDOT pump station

Version 2023-1 6 of 11 information to predict flooding based on user-defined thresholds.

439 22 WRONG WAY DRIVING

440 22.1 O The CV-ATMS should interface with Wrong Way Driver systems to receive alert messages by location/site.

454 26 SCADA PUMP STATION SYSTEM

455 26.1 O

The CV-ATMS should have the ability to pull and ingest data from MDOT’s SCADA Pump Station Monitoring System which currently uses MultiSmart hardware, with software provided by Kennedy Industries (KI System Master Software).

Revised Release Schedule

The project requirements will be revised to be released on the following schedule with no additional cost to the State of Michigan.

Release 1

Release 1 will contain all elements necessary for lane closure request functionality including the business specifications in the following categories:

1. GENERAL

2. DATA STORAGE

3. NETWORK PROTOCOLS

4. SYSTEM ADMINISTRATION

5. GUI

6. MAP

14. LANE CLOSURE REQUEST

19. NOTIFICATIONS

21. REPORTS

23. MI-DRIVE

25. ATMS

Business specifications 4.9, 6.10.2, and 6.18 will be excluded from this release.

Version 2023-1 7 of 11

Release 1a

Release 1a will contain any remaining business specifications previously demonstrated to SOM.

Release 2

Release 2 will contain updated work zone functionality including:

1. Default Map Layering in Work Zone Event Map

2. Automated Event Description

3. Select event extends by segment

4. Auto Selection of TSC and County

5. Full Event Cloning

Release 3

Release 3 will contain all remaining business specifications and updated work zone functionality including:

1. Updated Link Selection

2. Two-way Route Road Restrictions

3. Addition of Detour Description field.

4. Refined Vehicle Impact Logic

5. Simplified Event Scheduler

Version 2023-1 8 of 11

No changes will be made to the cost of Licensing Subscription and Operations and Maintenance fees; however, payment for these items is being revised to a monthly payment with release based partial payment.

Partial Payment Table

Accepted Release

Monthly Payment*

Licensing Subscription

1 $13,249.80 1a $5,299.92

2 $2,208.30 3 $1,324.98

All $22,083.00

Operations and Maintenance

1 $9,651.56 1a $3,860.62

2 $1,608.59 3 $965.16

All $16,085.93 *An additional $4.00 will be paid for Licensing Subscription in January of each year

Version 2023-1 9 of 11

SCOPE OF WORK:

Development and deployment of enhancements to the existing CV-ATMS application. Conduct design meetings to confirm work zone enhancements meet MDOT’s expectations. Support DTMB in implementation steps, and DTMB developers that are accessing the exposed feeds. Additional activities requiring Kapsch support include: Internal project management, verification of work zone and ADA conformance, Unit and Integration testing of solution.

Total for above activities: $45,539.97

The deadline to complete this work in the Development environment is 4/6/2026.

TASKS:

Conduct meetings with MDOT and DTMB to confirm functionality.

Confirm functionality of new development meeting MDOT’s expectations.

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

Support testing and validation activities related to additional enhancements.

DELIVERABLES:

Solution implementation in existing CV-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.

Version 2023-1 10 of 11

Payment Schedule Milestones:

• Release 3 - QA Implementation and Integration Acceptance (4/6/26) – 50% $22,769.99

• Release 3 - Production Implementation and Integration Acceptance (6/23/26) – 50%

$22,769.98

• Single payment for ADA

PROJECT SCHEDULE:

Project Schedule Milestones from the 1/27/2026 schedule:

Release 2:

• User Acceptance Testing: In-Progress

Release 1a:

• User Acceptance Testing: In-Progress

Release 3:

• Deployment to DEV/Software Demonstration: 4/24/26

• Ready to begin User Acceptance Testing: 4/27/26

Version 2023-1 11 of 11

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: Joe Gorman Department: Transportation Area: Bureau of Field Services, TSMO Address: 8885 Ricks Rd City/State/Zip: Lansing, Michigan 48917 Phone Number:

Email Address: GormanJ4@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.

No overtime will be permitted.

STATE OF MICHIGAN

CENTRAL PROCUREMENT SERVICES

Department of Technology, Management, and Budget

320 S. WALNUT ST., LANSING, MICHIGAN 48933

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

Change Notice Number 1 to

Contract Number 230000001291

Various

Robin Lampert david.hernandez2@kapsch.net

David Hernandez

Duluth, GA 30097

Kapsch TrafficCom USA, Inc.

VS0008701

845-220-7802

2855 Premiere Parkway

(517) 582-2746

S T

A T

E

P ro g ra m

M a n a g e r

C o n tra ct

A d m in istra to r

C O

N T R A C T O

R

DTMB

lampertr1@michigan.gov

$5,557,655.00

July 25, 2023 July 24, 2028

CONNECTED VEHICLE – ADVANCED TRAFFIC MANAGEMENT SYSTEM (CV-ATMS)

July 24, 2028

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

5 - 1 Year

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

☐ P-Card ☐ PRC ☐ Other ☒ Yes ☐ No

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

OPTION LENGTH OF OPTION EXTENSION LENGTH OF EXTENSION REVISED EXP. DATE

☐ ☐ July 24, 2028

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$0.00 $5,557,655.00

Effective February 13, 2024, the following amendments are incorporated into this Contract per attached Statement of Work. This change includes the following:

• replacement of DYNAC module with EcoTraffiX to meet additional business needs

• revised schedule and milestone dates

• clarification of deliverables and payment timing

Please note the Contract Administrator has been changed to Robin Lampert.

All other terms, conditions, specifications, and pricing remain the same. Per contractor and agency agreement, DTMB Central Procurement Services approval, and State Administrative Board approval on February 13, 2024.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

CONTRACT SUMMARY

MDOT

AGENCY NAME PHONE EMAIL

Multi-Agency and Statewide Contracts

Program Managers for

CHANGE NOTICE NO. 1 TO CONTRACT NO. 230000001291

Dave Work 517-719-2250 WorkD@michigan.govDTMB

Elise Feldpausch 517-636-0036 FeldpauschE1@michigan.govMDOT

Version 2021-1 CN 1 - 230000001291 1 of 21

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

CV-ATMS (IMP)

Period of Coverage:

2/12/24 – 1/31/25

Requesting Department:

DTMB

Date:

1/3/24

Agency Project Manager:

Elise Feldpausch

Phone:

(517) 636-0036

DTMB Project Manager:

Dave Work

Phone:

(517) 719-2250

BACKGROUND:

The State of Michigan (SOM) is deploying a new Connected Vehicle – Advanced Traffic Management System (CV-ATMS) that must provide the following high-level functionality to improve transportation safety, mobility, and system performance:

Connected Vehicles o Integrate and configure field devices through a map-based, user interface.

Remotely operate, monitor, and manage field devices.

o Collect, ingest, store, and analyze data generated from field devices.

o Enhance MDOT’s use of field device, mobile, and fixed data.

o Manage data, data exchange, certificate management, security, and message assembly.

o Provide a solution that provides the following functions:

▪ Basic processes to generate MAP, Traveler Information Message (TIM), and Basic Infrastructure Message (BIM) messages.

▪ Process for converting Signal Phase and Timing (SPaT) from traffic signal controllers into Society of Automotive Engineers (SAE) SpaT.

Michigan.gov/MiProcurement

▪ Basic Simple Network Management Protocol (SNMP) manager for interfacing to field devices.

Security Credentials Management System (SCMS) o Provide a message credential solution for vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) communication using a Public Key Infrastructure (PKI)-based approach that employs emerging industry standards, as developed by CAMP and others, of encryption and certificate management to facilitate trusted communication.

Version 2021-1 CN 1 - 230000001291 2 of 21 o The SCMS solution is anticipated to be a Software as a Service (SaaS) solution which supplies certificates and other elements to MDOT devices. MDOT does not intended to own the SCMS solution provided by the CV-ATMS Contractor.

o The supplied SCMS solution is not intended to be integrated into the CV-ATMS (i.e., it shall be a stand-alone system)

Applications o Provide an application development platform that allows for scalability as new needs are discovered.

o Provide a collection of applications that share and disseminate solution information to the users of the system.

o Lane Closure Request Application – to provide a system capable of managing MDOT’s lane closure request process. The process includes collecting, mapping, communicating, and reporting planned closures associated with road work, special events, or other circumstances that require closing lane(s) along MDOT roadways.

▪ MDOT’s Lane Closure Notification/Request Form is used for input into the

CVBO.

o Weather Application – to provide a system that ingests various near real-time weather and environmental data points, observations, and feeds capable of the following functionality:

▪ Converting the information into a geospatial shape with associated weather attributes to distribute notifications to users within the affected area.

▪ Identifying active and predictive roadway flooding.

o Smart Work Zone Application – to collect work zone data from temporary infrastructure and field devices to assess various factors such as work zone limits, if work zone workers are present, active/deactive work zones, etc.

Michigan.gov/MiProcurement

▪ This application includes a Work Zone Data Exchange (WZDx) module

Interfaces o Manage inbound/outbound interfaces using APIs to facilitate sharing data with internal and external systems.

o Provide an expandable data ingestion methodology for accepting data from a variety of data sources.

o Provide processes capable of processing, converting, translating, securing, and storing data that is ingested.

o Ingest and analyze data generated from interfaces.

General Requirements o Provide system administration, monitoring, notifications, dashboards, and reports.

Version 2021-1 CN 1 - 230000001291 3 of 21 o Provide the ability to accommodate multiple sources and types of data.

o Provide data storage that is expandable to include a variety of data types as they become available.

o Include processes to translate data into useable formats, and to move data to other systems where needed.

o Provide a means for accessing data from the database.

o Provide a collection of web services that can access and process the stored data to provide information and share the data

DEFINITIONS

The following terms have the meanings set forth below. All initial capitalized terms that are not defined in this Schedule shall have the respective meanings given to them in Section 1 of the Contract Terms and Conditions.

Term Definition

CMCC Connected Mobility Control Center

CV-ATMS

Connected Vehicle – Advanced Traffic Management System, a System being delivered by the Contractor

CVBO Connected Vehicle Back Office

DYNAC

DYNAC is the trademark name of one of the Contractor’s products.

ETX EcoTraffiX

TRIP Traffic Intelligence Platform

Refinement of Initial Plan

Kapsch recommended implementing EcoTraffiX (ETX) in place of DYNAC. ETX supports some additional Business Specifications that were not supported in the original Contract’s Schedule A – Table 1 – Business Specification Worksheet. These changes are described in Schedule A – Business Specification Changes of this Statement of Work (SOW). In addition, this change requires fewer virtual servers and will save the State’s internal costs may potentially facilitate future enhancements.

Changes to the milestones, deliverables, and schedule are incorporated into Schedule B – Deliverables, Milestones, and Payments.

Business Specifications that were included in the initial Contract as Optional will be incorporated or removed as determined during the Requirements Verification.

PROJECT OBJECTIVE:

• Configuration, customization, testing, and implementation of the functionality identified in the CV-ATMS Contract project using ETX in place of DYNAC.

• Interface with relevant MDOT systems and databases.

Version 2021-1 CN 1 - 230000001291 4 of 21

• Contractor provided training.

• Contractor provided user manuals and technical documentation.

SCOPE OF WORK:

CV-ATMS integrates several Contractor applications into one platform.

• ETX: Operational GUI + Applications

• CMCC: Connected Vehicle Manager

• MDP: Mobility Data Platform, data repository, exchange, and analytics subsystems

Software

Deploy ETX as the operational console for the CV-ATMS Solution.

Infrastructure

The table below outlines the current infrastructure needs to deploy the CV-ATMS solution per environment. The final design and server counts will be defined in the System Architecture and Design Plan.

Infrastructure Currently Under Implementation / Newly Proposed Solution

Component

CPU -

Cores

Memory in GB Storage Type

ETX Operational Console and Application Servers 20 128 4 TB Kubernetes Cluster

Qlik Sense Server 5 16 .5 TB Windows Virtual Machine

Mobility Data Platform 40 60 20 TB Kubernetes Cluster

MDOT Connectors 4 8 .5 TB Kubernetes Cluster

CMCC 16 64 2.5 TB Kubernetes Cluster

Section 27. Maintenance Releases; New Versions of the Software Contract Terms and Conditions will continue to apply to the Connected Vehicle – Advanced Traffic Management System (CV-ATMS).

DELIVERABLES:

Deliverables will not be considered complete until the Agency Project Manager has formally accepted them. Deliverables include the CV-ATMS system, project management and system documentation, training, testing, go-live, a warranty period, and on-going maintenance and support. Each deliverable associated with a payment is described in Schedule B – Deliverables, Milestones, and Payments.

Version 2021-1 CN 1 - 230000001291 5 of 21

ACCEPTANCE CRITERIA:

Acceptance criteria for the system is defined in Schedule I of the Contract. Acceptance criteria for documentation is defined is the Terms and Conditions, section 10.

Documentation will follow the State’s SUITE standards or substitute formats, which have to be agreed to in writing by the State. Required project documents are listed in Schedule B – Deliverables, Milestones, and Payments.

PROJECT CONTROL, MEETINGS, AND REPORTS:

Weekly Project Status Meetings: After the project kickoff, the Contractor Project Manager will schedule weekly project status meetings for the duration of the development phase. Contractor personnel will distribute the agenda for each meeting and a weekly report at least three business days in advance. Contractor will capture meeting minutes, action items, risks, decisions, issues, accomplishments, and track actions in a rolling action item list, and publish the data within three business days after each meeting. Each agenda will include a two-week outlook for upcoming deliverables, progress report update, discussion of issues and risks, action items, and schedule milestones and re-baselines.

A weekly progress report must be submitted by the Contractor to the Agency and DTMB Project Managers throughout the life of this project. The contents for these reports are documented in the Contract’s Statement of Work, section 22.

A monthly status report must be created and submitted by the Contractor throughout the term of the project prior to a monthly Project Status Meeting. The Relationship Manager and MDOT/DTMB Project and Program Managers will be members of the Monthly Project Status Meetings and include others as determined by the State’s Program Managers and the Relationship Manager and documented in the Communications Plan. Monthly Status Meetings will be held monthly for the duration of the project, or at a modified frequency as mutually agreed in writing by both parties. The Relationship Managers may also utilize other meetings as agreed in the Communication Plan. If escalation is required, the appropriate roster is listed in the Communication Plan.

The Contractor with meet with the State of Michigan/MDOT’s team at minimum quarterly to discuss the product roadmap and the direction of the Kapsch TRIP system development as described in the Statement of Work, section 9.

Other meetings as documented in the Contract’s Statement of Work section 21 will still apply. Meetings can be cancelled by mutual agreement in writing.

Contractor will coordinate and provide the schedule of meetings with the integration 3rd parties.

Version 2021-1 CN 1 - 230000001291 6 of 21

PAYMENT SCHEDULE:

Payment will be made on satisfactory acceptance of each deliverable. DTMB will pay Contractor upon receipt of properly completed invoice(s) which shall be submitted to the billing address on the State issued delivery 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, fees, and the delivery order number.

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 Contractor Relationship Manager will be one of the Key Personnel until the end of the warranty period. The designated Kapsch Relationship Manager is:

Frank Meehan 910-232-2834 Frank.Meehan@kapsch.net

The SOM Program Managers will serve in the role of Relationship Managers for SOM.

They are

Elise Feldpausch (MDOT) 517-636-0036 FeldpauschE1@michigan.gov

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

The Relationship and Program Managers will serve as the primary points of contact for addressing escalations for programmatic issues with the project. The Relationship Manager and Program Managers will be responsible for facilitating communication, resolving conflicts, and ensuring alignment between the State and Contractor.

This delivery order is a release from Contract Number 230000001291. This delivery order, statement of work, and the terms and conditions of Contract Number 230000001291 constitute the entire agreement between the State and the Contractor.

mailto:Frank.Meehan@kapsch.net mailto:FeldpauschE1@michigan.gov mailto:WorkD@michigan.gov

CN 1 - 230000001291 7 of 21

SCHEDULE A – BUSINESS SPECIFICATION CHANGES

Business Specification Type is R for Required or O for Optional.

Bus.

Spec.

Number

Business Specification Bus.

Spec.

Type

Description of What Will Be Provided

1.4 The CV-ATMS must have

documented Application Program Interface(s) (APIs) that supports current recognized industry standards that will enable all data collected through the CV-ATMS to be shared and integrated with other systems.

R CV-ATMS offers two standards-based APIs that allow publishing and consuming information.

a. There is a synchronous REST API that facilitates administration and consultation tasks (registration of new datasets and topics, consultation of available topics, consultation of schemas and formats, etc.), as well as synchronous publication and consumption of data.

b. Additionally, an asynchronous API based on STOMP over WebSocket is also offered, which allows systems to subscribe to topics and receive information events as soon as they are published.

An ETX implementation exceeds the original Kapsch response for this requirement.

The two APIs mentioned are available as they are provided by MDP component.

In addition to that, ETX component compliments those two APIs with a third one (called ETX External API) focused on ITS devices operation (sending/receiving commands), assets, etc.

1.5 The CV-ATMS must be able

to scale without a decrease in performance (map lag, field device layer displays, display of lists, execution of queries, etc.) with increased operational demands.

R CV-ATMS is virtualized and scaling system architecture/hosting platform will support increased operational demands with no degradation in performance. The software application has no limits on the data demands.

An ETX implementation exceeds the original Kapsch response for this requirement.

With ETX component the CV-ATMS can be fully deployed using containers orchestrator (Kubernetes). This approach enhances scalability and reduces cost of ownership.

CN 1 - 230000001291 8 of 21

Bus.

Spec.

Number

Business Specification Bus.

Spec.

Type

Description of What Will Be Provided

1.8 The CV-ATMS must allow for

the implementation of new software components (e.g., firmware, server, etc.)

without disruption to the rest of the system.

R The CV-ATMS Solution runs in a redundant system architecture that supports updating software modules on one set of virtualized servers while the other is running.

An ETX implementation exceeds the original Kapsch response for this requirement.

Kubernetes deployments of replicated services are coordinated with a load-balancer, which redirects traffic to the different running replicas while one of them is stopped and replaced by the new version.

If the service is not replicated, the download of the new version (new image) is done without interrupting the execution of the service to be replaced, and only when the new container is ready to execute, the old one is stopped and the new one is executed, resulting in minimal service downtime.

The various components that use the service to be replaced re-establish the connection as soon as the replaced service is available.

4.1 The CV-ATMS must comply

with Access Control and Authentication of the statement of work regarding login and authentication capabilities.

R Kapsch supports external user authentication (SAML, SSO, etc.) and will enhance and extend existing user authentication per MDOT Access Control and Authentication requirements.

An ETX implementation exceeds the original Kapsch response for this requirement.

With ETX, all components in the CV-ATMS will use a shared Keycloak instance that provides multiple authentication mechanisms.

Due to the change to ETX, this requirement no longer requires customization and can be achieved with configuration.

CN 1 - 230000001291 9 of 21

Bus.

Spec.

Number

Business Specification Bus.

Spec.

Type

Description of What Will Be Provided

4.2 The CV-ATMS must provide

role-based access controls and allow authorized users to define and assign different user access levels which enable and/or restrict all features, functions and/or data available based on permissions of the user.

R The user permissions application in CV-ATMS contains role-based permissions that allow defining access levels based on specific system features.

An ETX implementation exceeds the original Kapsch response for this requirement.

ETX has a users management & roles module that provides roles and permission profiles that can be managed by organizations, even allowing cross-organization roles.

4.4 The CV-ATMS must provide

the ability to generate automated emails to users regarding access information for their user accounts, such as notifications to update a password.

R The current functionality in our user permissions application does not include email notifications. This will be added during this project.

An ETX implementation exceeds the original Kapsch response for this requirement.

This is standard functionality in Keycloak. The business specification is now a current capability and does not require customization.

5.14 The CV-ATMS must provide

the ability for individual users to update, edit, and save user preference settings of the initial page entry and display within the system.

Once saved, those settings must apply only to the individual’s user account.

R This is standard functionality in the Kapsch solution.

An ETX implementation exceeds the original Kapsch response for this requirement.

Map rotation is supported with the change to ETX.

6.4 The CV-ATMS map must

include intuitive map navigation controls, including a compass if the map can be rotated.

R This is standard functionality in the Kapsch solution. An ETX implementation exceeds the original Kapsch response for this requirement with support for map rotation. Note that the compass is not visualized in the map, but there is a quick button to reset the north orientation.

CN 1 - 230000001291 10 of 21

Bus.

Spec.

Number

Business Specification Bus.

Spec.

Type

Description of What Will Be Provided

6.6 The CV-ATMS map should

have an interactive (point and click) distance measurement tool.

O This optional feature is one is lost in the new configuration, but will be added in a future enhancement.

19.4 The CV-ATMS should be

configurable so that notification recipients can receive notifications based on their permissions, area of responsibility, and other user attributes.

O An ETX implementation exceeds the original Kapsch response for this requirement.

Due to the change to ETX, this requirement no longer requires customization.

ETX notification functionality includes notifications based upon permissions and areas of responsibility as current capability.

CN 1 - 230000001291 11 of 21

SCHEDULE B – DELIVERABLES, MILESTONES, AND

PAYMENTS

Each milestone, with its deliverables, is defined in more detail below the table. With the exception of the Go Live, dates may be modified by mutual agreement of the Program Managers in writing.

On-Going Project Costs

ID Milestone Deliverable Frequency Payment

1 General Project

Management

Kick-Off Project Status Meetings Updates to Project Documentation

Monthly for 15 months

$42,744.07 / month $641,161.05 total

2 Training Initial Trainings 3 Sessions $5,333.33 / session $16,000 / total

3 Acceptance of Initial Project Documentation

Baseline Project Schedule Risk Management Plan Quality Management Plan

4/16/2024 Paid on initial acceptance

$19,809.40/ document $59,428.20 / total

1 General Project Management

To be paid monthly for the anticipated project term of 15 months.

2 Training

Three sessions, scheduled every four months for 12 months, beginning 60 days prior to Software Testing and Acceptance

3 Initial Project Documentation

Paid on initial approval; updated as needed throughout the project.

• Project Schedule

The Contractor’s Project Schedule will include o project tasks, including inputs, approach, outputs, constraints, and critical path items.

o a Work Breakdown Structure (WBS) in chart format illustrating tasks, sub-tasks, predecessors, meetings, trainings, workshops, and deliverables on a timeline.

CN 1 - 230000001291 12 of 21 o After the Kick-off meeting a plan with the total number for business specifications and assignment to deployments and releases will be delivered within 1 month. An updated baseline Schedule, including the plan of software/application deployments, will be made available for State’s approval upon the completion of the Requirements Validation Milestone.

o detail through all project phases, including documentation, software development, testing, integration, transition, and training.

• Risk Management Plan

The Contractor’s Project Schedule will o address the processes for identifying, assessing, mitigating, and monitoring the risks expected or encountered during the project’s life cycle.

o identify the roles and responsibilities of all participating organizations for risk management.

o identify 1) risks; 2) assess the relative level of risk as either: likely, probable, improbable, and impossible;

3) prioritize risks; 4) identify risk mitigation for likely, probable, and improbable risks, 5) define methods for monitoring risks, and 6) identify risk owner/lead.

• Quality Management Plan

The Contractor’s Quality Management Plan will o define how the Contractor will demonstrate compliance with the Contract business specifications and/or standards.

o describe the self-check process and/or procedures performed to ensure deliverables meet business specifications and the documentation and/or records are maintained.

o define quality staff and demonstrate that all quality staff are qualified, experienced, and have the proper skills/background.

o define procedures that ensure any and all failures, malfunctions, deficiencies, defects, deviations, etc., are corrected and/or documented according to the Quality Management Plan and Contract requirements.

CN 1 - 230000001291 13 of 21

Project Deliverables

ID Milestone Deliverable Due Date Payment

4 Validate Requirements Requirements Confirmation Document 4/25/2024 $19,809.40

5 System Architecture, Installation and

Operations Planning

System Architecture and Design Plan System Installation Guide SCMS Operations Plan

4/26/2024 10/1/2024 10/14/2024

$19,809.40/ document

$59,428.20 / total

6 System User Doc System User Doc 8/30/2024 $19,809.40

7 Software Development

Plan

Software Development Plan 5/14/2024 $19,809.40

8 Interface Control Plan Interface Control Plan 7/18/2024 $19,809.40

9 Data Dictionary Data Dictionary 8/15/2024 $19,809.40

10 Configuration

Management Plan

Configuration Management Plan 8/21/2024 $19,809.40

11 Transition Plan Transition Plan to Production Environment (Note: Initial Draft 6/27/2024)

12/1/2024 $19,809.40

12 Standards Document Standards Document (Note: Initial Draft 6/31/2024)

10/18/2024 $19,809.40

13 Provision Environments Validate Test and Production Environments Development

– 4/15/2024 Training/QA – 11/25/2024 Production 2/1/2025 n/a

CN 1 - 230000001291 14 of 21

14 Software and Application

Development, Configuration, and

Testing

Software Development, Configuration, and Testing Kapsch will conduct multiple deployments to the development environment as interfaces are developed and configured. The deployment schedule will be determined as part of the Project Schedule. Each deployment would be paid proportionally to a total of 50% of the Software development and configuration as part of release 1.

User Acceptance Testing Plan

12/19/24 $ 1,056,613.00 / total

Acceptance of User Acceptance Testing (UAT) Results

3/3/2025 $528,306.50

Release 1 Go-Live By 3/31/2025 $528,306.50

15 Incorporated Optional

Business Specifications

Development, Configuration, and

Testing

This milestone includes the Business Specifications that were noted as optional in the Contract and included into the requirements during Requirements Verification. Each deployment would be paid proportionally to a total of 50% of the Software development and configuration as part of release 2.

3/12/2025 $275,350.00 / total

Acceptance of User Acceptance Testing (UAT) Results

5/19/2025 $ 137,675.00

Release 2 Go-Live 6/25/2025 $ 137,675.00

CN 1 - 230000001291 15 of 21

16 Project Close Out Updates to Documentation Requirements Confirmation Document, System Architecture and Design Plan, SCMS Operations Plan, Systems User Documentation, System Installation Guide, Interface Control Plan, Data Dictionary, Configuration Management Plan, Standards Documentation During the course of the project, Kapsch will work closely with DTMB/MDOT to determine which documents need updating as the system delivery progresses

6/24/2025 $19,805,65

17 Solution Integration and Acceptance

Integration of Field Devices Successful Burn-In Period Warranty Period & Final Acceptance

5/1/2025 7/3/2025 10/2/2025

$148,357.50 $49,452.50 included

4. Validate Requirements o Contractor will organize meetings where the Contractor must review each business specification and demonstrate how each will be met. Any adjustments and/or proposed workarounds must be approved by the State.

o Once the business specifications have been reviewed and approved, they will all be required and may also be referred to as requirements.

o At the conclusion of the requirement confirmation meetings a Draft Requirements Confirmation Document deliverable must be provided to the State to document the results of the validation sessions, requirement revisions, and/or approved workarounds.

5. System Architecture, Installation and Operations Planning

• System Architecture and Design Plan

The Contractor will include the following in the System Architecture and Design Plan:

o detailed design plans of the network components, including physical and logical cores, physical and logical servers, physical and logical access, Virtual Local Area Networks (VLANs), Virtual Private Network

(VPN) users, equipment vicinity, and rack layout as applicable.

CN 1 - 230000001291 16 of 21 o detailed descriptions of:

▪ All servers such as application servers, database servers, communication servers, directory servers, clock servers, test servers, backup servers, Internet Information Services (IIS) servers, and others;

▪ Typical workstations configurations including monitors and printers;

▪ Uninterruptible Power Supplies (UPS), switches, power switches, routers, firewalls; and

▪ Field devices that will be managed or monitored by the system.

o interfaces between subsystems and external systems.

o security compliance.

o information requested by the State during the Enterprise Architecture Solution Assessment (EASA).

• System Installation Guide

The System Installation Guide (SIG) developed by the Contractor will define the installation, integration, and configuration of all CV-ATMS hardware, software, and modules, supporting operating systems, databases, 3rd party software, and any other software as needed for a full and complete solution.

• SCMS Operations Plan

The SCMS Operations Plan developed by the Contractor will o detail all functionality of the SCMS solution, including all interfaces for MDOT personnel.

o detail the process for initial bootstrapping of all devices by MDOT, including RSU and OBU.

o detail the process for initial bootstrapping of all devices by MDOT partners in a separate, stand-alone appendix, that can be provided to MDOT partners as needed.

o document the method for certificate revocation, both automated and manual.

o document the method for decommissioning of devices.

o document the process for certificate reloading on all devices, including the requirements for the MDOT system (e.g., IPv6, tunnels, firewalls, Internet access).

6. System User Documentation

The System User Documentation (SUD) developed by the Contractor will

CN 1 - 230000001291 17 of 21 o detail all functionality of the CV-ATMS.

o include user guides for each specific application within the CV-ATMS.

o include troubleshooting techniques and other user help information.

o be updated in conjunction with each system update/release and include an update log.

7. Software Development Plan

Contractor will include narrative descriptions and screenshots for phasing, software development, downstream impacts (detailed in the Risk Management Plan), configuration, and/or customization of the Commercially Off the Shelf (COTS) product(s).

8. Interface Control Plan

Contractor will include o the physical, functional, and content characteristics of both internal and external interfaces to a system, and the responsibilities of the organizations on both sides of the interface.

o 3rd party vendors and other existing hardware and software providers that the CV-ATMS will interface and integrate with.

9. Data Dictionary

The Data Dictionary delivered by the Contractor will contain the information necessary to describe CV-ATMS and API data elements, including name, type, max length, description, mandatory/optional.

10. Configuration Management Plan

The Configuration Management Plan delivered by the Contractor will o define the set-up and configuration of maps, user access, alerts, logs, standard reports, dashboards, schedules, etc.

o define the set-up and configuration of devices for each device type, make, and model to be integrated and the associated standards and protocols being used.

o outline processes, procedures, and responsibilities for documenting and implementing changes, modifications, and enhancements. This includes the design requirements, acceptance, and approval authorities.

CN 1 - 230000001291 18 of 21

11. Transition Plan (see Schedule G for transition requirements)

Contractor will define the transition sequence, schedule, cutover timeline, and responsibilities of the Contractor’s team and the State team from pre-transition through post go-live. In addition, the document will describe roll back plans in case something goes wrong during the cutover process. As part of this document, Contractor will work with the State to identify and document all specific requirements/constraints (e.g., minimize disruptions to operations, avoid transitioning during major or special events, etc..) that would impact scheduling and planning.

12. Standards Documentation

Based on the use…