071B2200299.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 32 to

Contract Number MA071B2200299C

C O

N

TR

AC

TO

R

CUSTOMER EXPRESSIONS CORP.

300 March Road, Suite 501

Ottawa, Ontario, Canada 0 K2K 2E2

David McNeill

678-634-6144 dmcneill@caseiq.com

CV0067031

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 Najla Mamou DTMB

517-897-4594

MamouN1@michigan.gov

CONTRACT SUMMARY

CaseIQ Case Management Application, Maintenance & Support and Hosting

INITIAL EFFECTIVE DATE

August 31, 2012

INITIAL EXPIRATION DATE

August 30, 2017

INITIAL AVAILABLE OPTIONS

12 - 1 Year

EXPIRATION DATE BEFORE

August 30, 2029

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS

P-Card Direct Voucher (PRC) Other

EXTENDED PURCHASING

Yes No

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

OPTION LENGTH OF OPTION EXTENSION LENGTH OF EXTENSION

REVISED EXP. DATE

CURRENT VALUE

$8,651,938.60

VALUE OF CHANGE NOTICE

$57,375.00

ESTIMATED AGGREGATE CONTRACT VALUE

$8,709,313.60

DESCRIPTION

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

Effective 09/01/2026, this Contract scope is expanded to purchase and implement an embedded artificial intelligence assistant, Clairia, for an annual fee of $19,125.00/year, update terms & conditions, and add definitions to the Glossary of the Contract.

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 09/01/26.

CHANGE NOTICE NO. 32 TO CONTRACT NO. MA071B2200299C

Program Managers for

Multi-Agency and Statewide Contracts

AGENCY NAME PHONE EMAIL

DTMB John Moore 517-331-5065 MooreJ7@michigan.gov

DTMB Ryan Speidel (517) 241-0552 speidelr2@michigan.gov

DTMB Giget Schlyer 517-582-8330 SchlyerG@michigan.gov

MDHHS Casey Barton 517.331.6943 BartonC3@michigan.gov

DTMB Asha Manday 517-402-3372 mandaya@michigan.gov

Michigan.gov/MiProcurement

Version 2026-1 1 of 12

IT CHANGE NOTICE

TERMS AND CONDITIONS

Changes to be incorporated into existing Contract terms and conditions.

(1) Section 2.006 Order of Precedence is hereby deleted and replaced with the following –

2.006 Entire Agreement and Order of Precedence.

The Contract, including any Statements of Work and Exhibits, to the extent not contrary to the Contract, each of which is incorporated for all purposes, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior agreements, whether written or oral, with respect to the subject matter and as additional terms and conditions on the purchase order must apply as limited by Section 2.005.

In the event of any inconsistency between the documents of this Contract , the order of precedence is: (a) first, this Contract, excluding its schedules, exhibits, and Statement of Work; (b) second, Data Security Requirements, made effective pursuant to Change Notice 21; (c) third, each applicable Statement of Work as of its effective date; and (d) fourth, schedules expressly incorporated into this Contract as of the effective date The Contract may be modified or amended only by a formal Contract amendment.

NO TERMS ON CONTRACTOR’S INVOICES, WEBSITE, BROWSE-WRAP, SHRINK-WRAP,

CLICK-WRAP, CLICK-THROUGH OR OTHER NON-NEGOTIATED TERMS AND CONDITIONS

PROVIDED WITH ANY OF THE SERVICES, OR DOCUMENTATION HEREUNDER, EVEN IF

ATTACHED TO STATE’S DELIVERY OR PURCHASE ORDER, WILL CONSTITUTE A PART OR

AMENDMENT OF THIS CONTRACT OR IS BINDING ON THE STATE OR ANY AUTHORIZED

USER FOR ANY PURPOSE. ALL SUCH OTHER TERMS AND CONDITIONS HAVE NO FORCE

AND EFFECT AND ARE DEEMED REJECTED BY THE STATE AND THE AUTHORIZED USER,

EVEN IF ACCESS TO OR USE OF SUCH SERVICE OR DOCUMENTATION REQUIRES

AFFIRMATIVE ACCEPTANCE OF SUCH TERMS AND CONDITIONS.

(2) Section 2.094 is hereby added to this Contract –

2.094 Data Security Requirements.

Contractor must comply with the requirements of the State’s data security policies as set forth and made effective in Change Notice 21 to this Contract.

(3) 2.201 Nondiscrimination is hereby deleted and replaced with the following –

Version 2026-1 2 of 12

2.201 Nondiscrimination.

Under the Elliott-Larsen Civil Rights Act, 1976 PA 453, MCL 37.2101, et seq., the Persons with Disabilities Civil Rights Act, 1976 PA 220, MCL 37.1101, et seq., and Executive Directive 2019-09, Contractor and its subcontractors agree not to discriminate against an employee or applicant for employment with respect to hire, tenure, terms, conditions, or privileges of employment, or a matter directly or indirectly related to employment, because of race, color, religion, national origin, age, sex, sexual orientation, gender identity or expression, height, weight, marital status, partisan considerations, any mental or physical disability, or genetic information that is unrelated to the person’s ability to perform the duties of a particular job or position.

(4) 2.202 Unfair Labor Practices is hereby deleted and replaced with the following –

2.202 Unfair Labor Practice.

Under MCL 423.324, the State may void this Contract if the name of Contractor, or the name of a subcontractor, manufacturer, or supplier of Contractor, subsequently appears on the Unfair Labor Practice register compiled under MCL 423.322.

(5) 2.205 Strategic Partner is hereby added to this Contract –

2.205 Strategic Partner.

Contractor warrants that it is neither currently engaged in nor will engage in the boycott of a person based in or doing business with a strategic partner as described in 22 USC 8601 to 8606.

(6) 2.242 Service Level Agreement (SLA) is hereby deleted and replaced with the following –

2.242 Support Services.

Contractor will provide the State with the Support Services described in the Service Level Agreement as set forth and made effective in Change Notice 21 to this Contract.

(7) Section 2.243 Liquidated Damages is hereby deleted and replaced with the following –

2.243 Liquidated Damages.

The parties understand and agree that any liquidated damages (which includes but is not limited to applicable credits) set forth in this Contract are reasonable estimates of the State’s damages in accordance with applicable law.

The parties acknowledge and agree that Contractor could incur liquidated damages for more than one event.

Version 2026-1 3 of 12

The assessment of liquidated damages will not constitute a waiver or release of any other remedy the State may have under this Contract for Contractor’s breach of this Contract, including without limitation, the State’s right to terminate this Contract for cause and the State will be entitled in its discretion to recover actual damages caused by Contractor’s failure to perform its obligations under this Contract. However, the State will reduce such actual damages by the amounts of liquidated damages received for the same events causing the actual damages.

Amounts due the State as liquidated damages may be set off against any Fees payable to Contractor under this Contract, or the State may bill Contractor as a separate item and Contractor will promptly make payments on such bills.

(8) Section 2.263 Rights in Data is hereby deleted and replaced with the following –

2.263 Rights in Data.

The State is the owner of all data, including State Data, made available by the State to the Contractor or its agents, Subcontractors or representatives under the Contract. The Contractor will not use State Data for any purpose other than providing the Services, nor will any part of the State’s data be disclosed, sold, assigned, leased or otherwise disposed of to the general public or to specific third parties or commercially exploited by or on behalf of the Contractor. No employees of the Contractor, other than those on a strictly need-to-know basis, have access to the State Data. Contractor will not possess or assert any lien or other right against the State’s data. Without limiting the generality of this Section, the Contractor must only use personally identifiable information as strictly necessary to provide the Services and must disclose the information only to its employees who have a strict need-to-know the information. The Contractor must comply at all times with all laws and regulations applicable to the personally identifiable information.

The State is the owner of all State-specific data under the Contract. The State may use the data provided by the Contractor for any purpose. The State will not possess or assert any lien or other right against the Contractor’s data. Without limiting the generality of this Section, the State may use personally identifiable information only as strictly necessary to utilize the Services and must disclose the information only to its employees who have a strict need to know the information, except as provided by law.

The State must comply at all times with all laws and regulations applicable to the personally identifiable information. Other material developed and provided to the State remains the State’s sole and exclusive property.

(9) Section 2.316 Work Product Representations and Warranties is hereby added to this Contract –

2.316 Work Product Representations and Warranties.

Version 2026-1 4 of 12

Contractor represents and warrants to the State that:

(a) Contractor has all necessary rights, title, and/or licenses required to create, develop, or generate Work Product and/or User Data and to transfer all ownership rights in Work Product to the State as set forth in this Section.

(b) Contractor has verified that no third-party intellectual property has been incorporated into any Work Product and/or User Data created, developed, or generated by any non-human means used by Contractor.

(c) Contractor is the author and creator of all Work Product.

(10) Section 2.340 Artificial Intelligence hereby added to this Contract –

2.340 Artificial Intelligence.

2.341 AI Model Cards.

(a) Contractor will provide a comprehensive model card, or other documentation, for any artificial intelligence (including but not limited to machine learning models, large language models, neural networks, or probabilistic based tools) integrated into the Solution. A comprehensive model card will include model details (name, architecture, training methodology); intended uses and known limitations; description of training data and data sources; evaluation metrics and performance benchmarks; fairness, ethical, and safety considerations; and maintenance plan and update history.

(b) Contractor will provide the initial model card prior to deployment of the applicable model and will update the model card promptly upon any material changes to the model.

Examples of material changes include but are not limited to retraining of the model, changes to input data, or known performance deviations such as performance degradation or risk factors that could impact the quality, behavior, or reliability of the Solution. Contractor will provide the State notice of any material changes to the AI models and will conduct regression testing prior to deployment. Material changes to AI models will not degrade performance or increase risk exposure to the State.

(c) Contractor must deliver model cards in a format reasonably acceptable to the State and the model cards must be kept up to date during the Term.

(d) Audit rights. The State reserves the right to audit at most once per year, the accuracy and completeness of any model card and request clarification or supporting evidence for any claims made therein. Contractor will provide the clarification or supporting evidence within 10 business days of the State’s request. The State may use a qualified independent third-party to conduct and complete or assist in the audit. Contractor will provide reasonable assistance and cooperate with the audit.

2.342 Third-Party Artificial Intelligence.

Version 2026-1 5 of 12

If Contractor integrates a third-party artificial intelligence (including but not limited to machine learning models, large language models, neural networks, or probabilistic based tools) into the Solution, Contractor will ensure that the third-party artificial intelligence model complies with the auditability and documentation requirements in this Contract.

(11) The following definitions are hereby added to the Glossary of this Contract –

“Access” means (1) the ability and means to enter a restricted or locked area, room, or physical container containing State Data; or (2) the ability and means to communicate with or otherwise interact with a system, to use system resources to handle or view information, to gain the information or knowledge of the information the system contains, or to control system components and functions (including physical or technical controls, or having the ability to modify or bypass any or all security controls).

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

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

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

“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).

“Permitted Subcontractor” means any third party used by Contractor to perform Services under this Contract that will have Access to or have the ability to control Access to State Data.

“Processing” means to perform any operation or set of operations on any data, information, material, work, or content, whether or not by automated means, including, but not limited to, collection, recording, input, output, download, reproduce, organization, structuring, storage, translation, adaptation or alteration, retrieval, use, process, transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.

Version 2026-1 6 of 12

“Services” means any function performed for the benefit of the State, including, but not limited to, Hosted Services and Support Services, that Contractor is required to or otherwise does provide under this Contract.

“Software” means Contractor’s software as set forth in a Statement of Work. It also includes Customizations or Configurations made by or for the State pursuant to this Contract, and all copies of the foregoing permitted under this Contract. If Contractor hosted, Software includes Contractor’s Operating Environment.

“Solution” means Software and Services singularly or in any combination thereof, as applicable.

“State Data” means User Data, Work Product, and all data (including, but not limited to, text, sound, software, video, or image files) made available to Contractor or Processed by Contractor in connection with this Contract.

“Support Services” means the maintenance and support services Contractor is required to or otherwise does provide to the State under the Service Level Agreement.

“Term” means the term set forth in the preamble including any renewals, extensions, and any applicable Transition Period.

“User Data” means all data, queries, prompts, information and other content of any type and in any format, medium or form, whether audio, visual, digital, screen, GUI or other, that is input, uploaded to, placed into or collected, stored, Processed, generated or output by any user, device, system or network by or on behalf of the State, including but not limited to any and all works, inventions, data, analyses, information that identifies State or State’s intended users’ devices or equipment, location information, or other information and materials resulting from any use of the Software by or on behalf of the State’s intended users under this Contract, even if not input by a user.

“Work Product” means any data compilations, reports, and other media, materials, or other objects or works of authorship created or produced by the Contractor as a result of and in furtherance of performing the services required by this Contract. Work Product includes all Customizations.

Version 2026-1 7 of 12

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

Clairia for MiCAIS - OCA

Period of Coverage:

07/15/2026 – 08/30/2029

Requesting Department:

Office of the Child Advocate (OCA)

Date:

7/15/2026

Agency Program Managers:

Casey Barton Ryan Speidel

Phone:

517-335-7072 517-241-0552

DTMB Program Managers:

Giget Schlyer John Moore Asha Manday

Phone:

517-582-8330 517-331-5065 517-243-4328

PROJECT BACKGROUND:

The Office of the Child Advocate (OCA) utilizes the Contractor for a case management system, the Michigan Child Advocate Information System (“MiCAIS” or “Solution”).

Contractor has developed an embedded artificial intelligence assistant, Clairia, designed with security, privacy, and compliance protections integrated from inception. Clairia operates as a native component of the Solution and is intended to enhance investigative workflows, reporting, and data analysis.

Clairia is powered by Microsoft’s Azure OpenAI Service and deployed entirely within Contractor’s private Microsoft Azure environment. This architecture ensures that:

• Clairia is privately hosted within Contractor’s Azure tenant and not exposed to public AI endpoints.

• State Data is used solely to generate responses and is never retained, stored, or used for model training.

• Clairia does not connect to or interact with OpenAI-operated services (including ChatGPT or the public OpenAI API).

• All AI functionality is delivered through secure, enterprise-grade Azure OpenAI infrastructure.

By deploying Clairia on private, Contractor-controlled Azure endpoints, Contractor ensures that all State Data remains confidential, segregated, and restricted to its authorized purpose. Contractor will be responsible for ensuring all data processed through the Solution or Clairia is compliant and meets the requirements set forth under the Data Security Schedule originally set forth under Change Notice 21 to this Contract.

Version 2026-1 8 of 12

This project will enable Contractor to implement Clairia for the OCA, integrating the AI assistant into MiCAIS and configuring it to support OCA’s investigative and reporting workflows.

PROJECT OBJECTIVE:

The objective of this project is to implement Clairia as an integrated component of the existing MiCAIS case management system used by the Office of the Child Advocate. Clairia will support OCA staff by enhancing case review processes, generating case timelines, summarizing case materials, and assisting with the drafting of reports and recommendations.

The successful implementation of Clairia will strengthen OCA’s ability to streamline workflows, improve reporting accuracy and consistency, and enhance the agency’s overall capacity to analyze case information and advocate effectively for children.

SCOPE OF WORK:

Implementation of Clairia into the deployed version of the Contractor application, MiCAIS.

The Contractor will enable the features listed above, configured to support OCA’s requirements, workflows, reporting, and case information.

Overview Case IQ’s AI Assistant (“Clairia”) is an artificial intelligence system designed to support investigative case management. Clairia analyzes case data, identifies connections across records within a case, and provides policy-based guidance. The system processes information in a secure manner and is intended to reduce administrative effort, increase efficiency, and improve accuracy for authorized users.

Features and Access Clairia provides two primary modes of assistance:

• Chat Interface – Users may generate outputs including, but not limited to, risk assessments, note analysis, interview questions, case updates, and follow-up communications.

• Copilot Fields – Structured fields that generate consistent outputs such as summaries, timelines, and recommendations.

Access to Clairia is permission-based and may be restricted to designated user groups. All AI-generated content is clearly identified as AI-generated. Chats are automatically stored, private to the initiating user, and may be reviewed, renamed, or deleted at the user’s discretion.

Version 2026-1 9 of 12

Data Sources and Processing Clairia may draw upon individual case records, associated files, and documents within the Case IQ library to generate outputs, subject to user-controlled file selection. All interactions occur within Case IQ’s private Microsoft Azure OpenAI environment.

Information is not shared with OpenAI, added to public datasets, or used to train or improve AI models. Data remains fully controlled and protected by Case IQ.

User Responsibilities and Limitations All AI-generated outputs are intended as suggestions only. Users remain solely responsible for reviewing, validating, and determining the applicability of such outputs in the context of their investigations.

Clairia is advisory in nature and is not a substitute for human investigation, analysis, or professional judgment. Users must exercise appropriate discretion and remain accountable for all final determinations and investigative outcomes. Case IQ makes no representation or warranty that outputs generated by Clairia are complete, accurate, or sufficient for any particular purpose.

DELIVERABLES:

• Clairia Implementation & Configuration o Deployment and activation of Clairia within the MiCAIS environment.

o Initial configuration of Clairia settings, permissions, and system behaviors aligned with OCA workflows and policies.

o Validation testing to ensure Clairia functions correctly within MiCAIS and meets security, privacy, and performance requirements.

• Playbook Development & Governance Setup

Contractor will establish Clairia Playbooks tailored to OCA’s investigative and reporting needs, including:

• Approved prompts and prompt templates.

• Defined usage boundaries and guardrails.

• Establish role-based permissions and access controls.

• Workflow-specific AI behaviors aligned with OCA policies, investigative standards, and reporting requirements.

• Documentation of Playbook configurations for future reference and governance.

• Training & Knowledge Transfer

Version 2026-1 10 of 12

• Delivery of train-the-trainer sessions for designated OCA staff.

• Training materials, user guides, and reference documentation.

• Hands-on demonstrations of Clairia functionality within MiCAIS.

• Guidance on best practices for AI-assisted case review, timeline generation, and report drafting.

• Post-Implementation Capability Outcomes

Upon completion of the project and acceptance of all deliverables, OCA staff will be able to utilize Clairia to its full intended capability, including:

• Reviewing case files and extracting relevant information.

• Generating structured case timelines based on available documentation.

• Producing draft narrative summaries and report sections.

• Supporting data-informed decision-making and trend identification.

• Operating Clairia within MiCAIS in a secure, compliant, and efficient manner.

ACCEPTANCE CRITERIA:

• Clairia Implementation & Configuration o Clairia is deployed and there are no critical issues outstanding o Configurations are functioning as documented and agreed upon o Clairia successfully processes sample data in testing and produces expected results o A functional demonstration confirms Clairia operates reliably within MiCAIS

• Playbook Development & Governance Setup o Playbooks identified in the project scope are created, configured, and accessible to authorized users.

o Playbooks produce consistent, policy‑aligned outputs when tested with representative case scenarios.

o Documentation is provided describing Playbook structure, configuration, and governance expectations.

• Training & Knowledge Transfer o Train‑the‑trainer sessions are completed with designated OCA staff.

o Training materials, guides, and reference documentation are delivered in final form.

Version 2026-1 11 of 12

• Post-Implementation Capability Outcomes o Reviewing case files and extracting relevant information.

o Generating structured case timelines based on available documentation.

o Producing draft narrative summaries and report sections.

PROJECT CONTROL AND REPORTS:

A bi-weekly progress report must be submitted to the State and DTMB Project Managers throughout the life of this project. This report may be submitted with the billing invoice.

Each bi-weekly progress report must contain the following:

1. Hours: Indicate the number of hours expended during the past two weeks, and the cumulative total to date for the project.

2. Accomplishments: Indicate what was worked on and what was completed during the current reporting period.

PAYMENT SCHEDULE:

Payment will be made upon successful completion of the project and only after the State Program Manager and Business Owner have formally accepted all required deliverables.

Clairia deployment and configurations

ID Task Description Total amt/year

1 Contractor costs for CMS AI Assistant (Clairia)

Clairia project - deployment and configuration

$19,125.00

Total Setup Costs for OCA Clairia $19,125.00

Annual Recurring Costs

ID Task Description Total

2 Hosting and Technical Support for Clairia

N/A $19,125.00

Total Annual Cost for OCA Clairia $19,125.00

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 OCA and DTMB Project Manager approvals. All invoices should reflect actual work completed by payment date and must be approved by the OCA and DTMB Project Manager prior to payment. The invoices shall describe and document to the State’s satisfaction a description of the work performed, Version 2026-1 12 of 12 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.

EXPENSES:

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

LOCATION OF WHERE THE WORK IS TO BE PERFORMED:

Consultants will work at: their normal work locations.

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.

This Statement of Work is hereby made part of and incorporated by reference into that certain Contract Number MA071B2200299C executed by and between Contractor and the State.

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

CONTRACT CHANGE NOTICE

Change Notice Number 31 to Contract Number MA071B2200299C

C O

N

TR

A C

TO

R

CUSTOMER EXPRESSIONS CORP.

300 March Road, Suite 501

Ottawa, Ontario, Canada 0 K2K 2E2

David McNeill

678-634-6144 dmcneill@caseiq.com

CV0067031

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 Najla Mamou DTMB

517-897-4594

MamouN1@michigan.gov

CONTRACT SUMMARY

CaseIQ Case Management Application, Maintenance & Support and Hosting

INITIAL EFFECTIVE DATE

August 31, 2012

INITIAL EXPIRATION DATE

August 30, 2017

INITIAL AVAILABLE OPTIONS

12 - 1 Year

EXPIRATION DATE

BEFORE

August 30, 2029

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS

P-Card Direct Voucher (PRC) Other

EXTENDED PURCHASING

Yes No

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

OPTION LENGTH OF OPTION EXTENSION LENGTH OF EXTENSION

REVISED EXP. DATE

CURRENT VALUE

$8,651,938.60

VALUE OF CHANGE NOTICE

$0.00

ESTIMATED AGGREGATE CONTRACT VALUE

$8,651,938.60

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

Effective March 3, 2026, the following amendment is incorporated into this Contract for MDHHS to memorialize the six-month pilot phase of the MIGS Modernization Project.

• The expected closing date on the project changed from July 31, 2026 to September 30, 2026.

• The implementation and completion of Phase 1 will complete the current implementation phase and move to maintenance and support.

• Phase 2 of the MIGS Project has been descoped and removed from the Project.

No additional funding is needed at this time; existing funds on the Contract are adequate to support this change.

Please note the Contract Administrator has been updated to Najla Mamou.

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

CHANGE NOTICE NO. 31 TO CONTRACT NO. MA071B2200299C

Program Managers for

Multi-Agency and Statewide Contracts

AGENCY NAME PHONE EMAIL

DTMB John Moore 517-331-5065 MooreJ7@michigan.gov

DTMB Ryan Speidel 517-241-0552 speidelr2@michigan.gov

DTMB Giget Schlyer 517-582-8330 SchlyerG@michigan.gov

MDHHS Casey Barton 517-335-7072 BartonC3@michigan.gov

DTMB Asha Manday 517-243-4328 mandaya@michigan.gov

Version 2021-1 1 of 8

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

MIGS Modernization for MDHHS

Period of Coverage:

Requesting Department:

Michigan Department of Health and Human Services

(MDHHS)

Date:

1/29/2025

Agency Project Manager:

Casey Barton

Phone:

517-331-6943

DTMB Project Manager:

John Moore

Phone:

(517) 331-5065

PROJECT BACKGROUND:

Michigan Department of Health and Human Services and the Contractor have been working on implementing MIGS Modernization, to upgrade the application to v9 from the current v2 and deployment of v9 in the Contractor’s Azure GovCloud environment. The Contractor continues to be responsible for providing development, support for customized and non-customized functionality, and maintenance of legacy MIGS application (currently v2) and any future versions. V2 of the Software shall be maintained by the Contractor for 6 months after the Go-Live, provided that V9 of Contractor’s software must be compliant with Availability Requirement, as required by the Service Level Agreement. The State in its sole discretion may determine that such maintenance can be terminated sooner than 6 months.

PROJECT OBJECTIVE:

Completion of Phase 1

By this Change Notice DHHS and the Contractor jointly agree to finalize the MIGS Modernization Project with the completion of Phase 1, as outlined in Change No. 22, Section III. Scope of Work.

Phase 1 of MIGS Project Go-Live is targeted to be completed on or about February 13, 2026. Upon the completion of Phase 1 a 90-day warranty period will be provided by the Contractor for all work performed as a part of Phase 1, at no additional cost. Upon the completion of Go-Live and State’s Acceptance of the system, deployed to a production environment, the Contractor will receive a payment of $220,500 for Phase 1 implementation fees (see Payment Details) and $100,000 for Hosted Systems Maintenance Fees – GovCloud Deployment and Support (prorated for the balance of the contract year), as previously set in Change Notice Number 16.

Phase 2 of the MIGS Project and the associated payment for Phase 2 are hereby descoped and removed from the Project.

HOSTING: MIGS - Hosting/Application and Maintenance Cost fee ($24,000 annually) will continue to be applicable per Change Notice Number 26 (plus the additional $100,000 fee listed in the above

Version 2021-1 2 of 8 paragraph). These services shall be provided by Contractor’s personnel separate from Key Personnel, as identified in this SOW.

Except as expressly set forth herein, none of the following terms shall be construed to relieve Contractor of any support or maintenance obligations otherwise set forth in the terms of this Contract.

Six-Month Sprints Pilot Project

Contractor will provide a pilot project consisting of three separate two-month development and support sprints, which will begin upon Phase 1 Go-Live. The State will aspire to let no more than two weeks dwell between the acceptance of one sprint and the beginning of another sprint, provided the State determines that another sprint is necessary.

During this pilot project period, Contractor will provide professional services through Contractor’s Professional Services team consisting of one Business Analyst and two Development Engineers, all of whom will be dedicated to State of Michigan’s system only (i.e.100% allocation to MDHHS’ project). The Business Analyst and the Development Engineers will be Key Personnel and treated as such in accordance with the Terms of the Contract.

Nothing set forth herein shall be construed to relieve Contractor of any support or maintenance obligations otherwise set forth in the terms of the Contract. Contractor will ensure that any Customizations developed during the pilot project shall be compatible with the Contractor’s Software. Contractor will continue providing updates and upgrades of the Software, according to the Service Level Agreement.

Structure of the development/support sprints:

• Sprints will include both new customized development (enhancement requests) and Support and Maintenance Services for both customized and non-customized functionality, in compliance with the Contract’s Service Level Agreement.

• Sprints will exclude Service Availability support and any services related to hosted environment’s support and maintenance. The Contractor will provide additional personnel to provide hosted environment support and maintenance and ensure the Service Availability remains within the contractually agreed to parameters, per Service Level Agreement.

• During the Sprint Planning phase, prior to each two-month sprint, the State and the Contractor will identify and propose each sprint’s deliverables within 30 days prior to the start of the Sprint. Upon such proposal being tendered, State will accept or reject each proposal in its sole reasonable discretion prior to the start of the Sprint.

An approved Sprint Planning documentation will be provided by the State to the Contractor (Form SEM-185 or similar).

• Each sprint will include an Acceptance Testing period, as determined by the State, and agreed upon in advance of sprints, with Contractor. Contractor will provide any requested

Version 2021-1 3 of 8 demonstrations prior to the start of Acceptance Testing and Acceptance Testing support during the Acceptance Testing period.

• The State and the Contractor will initiate the first proposed sprint within 30 days of the V9 go-live.

SCOPE OF WORK

Completion of MIGS Modernization, Phase 1:

• As set forth in Change Notice Number 22, Section III, Scope of Work (additionally see Attachment A for the functionality that must be delivered in Phase 1 Go-Live, with the exceptions of OIGMIGS-31 and OIGMIGS-32, which will be completed immediately post-go-live, as agreed by the parties).

• As set forth in Change Notice Number 26, Contractor will complete the following milestones:

o Office of Inspector General (OIG) Defects Resolution Testing & OIG Training Materials Development o Pre-Prod Validation o Deployment to Production o 90-day Warranty (Hypercare) Support for Software

Six-Month Sprints Pilot Project:

• New customizations (enhancement requests), as requested by the State and incorporated in Sprint’s scope during sprint planning.

o The Key Personnel will provide defects resolution, when the agreed upon Acceptance Criteria have not been met through State’s User Acceptance Testing.

• Any non-customized functionality deployments, as determined by the State.

• Support and maintenance for the customized and non-customized functionality of the application, except for the hosted environment support and maintenance.

o The support of the hosted environment will be provided by supplementary Contractor’s personnel. Contractor will not utilize the resources of the Key Personnel outlined in this Change Notice. If such resources are utilized, the State will receive credit for the hours worked on such services, unless this work takes place between paid-for sprints.

o For clarity, Contractor acknowledges and agrees that any support of and maintenance obligation set forth in the Contract as amended and/or modified include an obligation to provide support and maintenance of not only its underlying iSight software, but also of any customizations created specifically at the request of the State.

Version 2021-1 4 of 8

TASKS:

Technical support is required to assist with the following tasks:

MIGS Modernization Phase 1

• Completion and Go-Live of Phase 1 of the MIGS Modernization Project (see Attachment A)

Six-Month Sprints Pilot Project

• Post Go-Live, tasks will include development and deployment to Production of new customizations (enhancement requests) and any non-customized functionality of the application.

• Maintenance and Support of the Software in its entirety

• Support during User Acceptance Testing

• Resolution of defects after Sprint’s completion

DELIVERABLES:

Deliverables will not be considered complete until the State formally accepts them, which will be communicated via email once finalized. Deliverables for this project include:

• Any new customizations of the application (enhancement requests), as will be identified in the State’s approved Sprint Planning document (SEM-0185 or similar)

• Any non-customized functionality of the application

• Any Contractor’s support and maintenance provided for the customized and non-customized features of the application

ACCEPTANCE CRITERIA:

MIGS Modernization Go-Live

Acceptance will be provided by the State’s Agency and DTMB Project Manager. Contractor will provide resolution of any Critical or High-level defects, as defined in the Service Level Agreement.

Six-Month Sprints Pilot Project

Acceptance Criteria for each deliverable will be determined by State during the Sprint planning process. Acceptance Testing will be conducted in the MIGS UAT environment. State reserves the right to conduct additional UAT testing, including any integration testing, in the PAT environment prior to providing Acceptance.

In consultation with the Contractor, Acceptance of a sprint may be provided if none of the identified defects are classified by the State as critical for the Sprint’s implementation. Any non-critical defects, as identified by the State, may be deferred to the subsequent sprint. Any of the Contractor’s Key Personnel capacity used to resolve such deferred defects will be credited back to the State on the next invoice, if this work takes place during one of the approved sprints.

Version 2021-1 5 of 8

PROJECT CONTROL AND REPORTS:

A bi-weekly Sprint report must be submitted to the Agency and DTMB Project Managers throughout the course of this project. Each monthly Sprint report must contain the following:

1. Sprint accomplishments: Indicate what was worked on and what was completed during the current reporting period.

2. Funds: Indicate the amount of funds expended during the current reporting period, and the cumulative total to date for the project.

3. Issues, Risks and any requested escalations needed to resolve issues or risks.

4. Sprint metrics analysis, including any metrics that will be helpful for the State to analyze Sprint’s performance. Any proposed sprint metrics must be reviewed and approved by the State.

5. Sprint metrics will include a description of resources utilized, actual hours spent by each resource and areas of work performed.

6. At the completion of the second two-month Sprint, Contractor will provide the State with a formal evaluation of the pilot project, including a description of pilot successes, lessons learned, functionality planned and completed, type of work (e.g. customizations built and deployed, maintenance/non-customized functionality deployed, etc.) and the description of sprint metrics used in the pilot and their applicability for the future continuation of the project.

PAYMENT SCHEDULE:

The cost breakdown for the 6-month period will be as follows:

• Each 2-month sprint will be provided by the Contractor at $50,000. 50% of the fee will be invoiced upon the approval of Sprint Planning by MDHHS and DTMB-AS. 50% of the fee will be paid upon the State’s Acceptance of the sprint’s deliverables.

• Any warranty work performed by Key Personnel during the 90-day period after Phase 1 go-live will be credited back to the State on the next due invoice, if this work takes place during one of the approved sprints.

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. Invoices should reflect work planned (1st 50% of each sprint’s payment) or work completed (2nd 50% of each sprint’s payment) 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 planned (and mutually agreed upon) work, actual hours spent, 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 2021-1 6 of 8

PROJECT CONTACTS:

The designated Agency Project Manager is:

Casey Barton, Investigative Analytics Manager

MDHHS/OIG – Operations Division

P.O. Box 30062 Lansing, MI 48909

517-331-6943

BartonC3@michigan.gov

The designated DTMB Project Manager is:

John Moore, State of MI – DTMB AS Supporting MDHHS – Medicaid

Grand Tower 235 S Grand Avenue, 3rd Floor Lansing, MI 48933

517-331-5065 moorej7@michigan.gov

Attachment A.

• Archives 1,2,3 and Production will be migrated to the V9 system with data corrections and reindexing as necessary

List of functionalities to be deployed to production environment with the Phase 1 of MIGS Modernization

OIGMIGS 6 Automatic Case Closure OIGMIGS 43 Time Report Upload OIGMIGS-1 Screening Flow OIGMIGS-10 FEE Flow OIGMIGS-11 Background Check: Internal New Case OIGMIGS-12 FEE: Internal New Case OIGMIGS-13 Form: New Case OIGMIGS-14 Form: Case OIGMIGS-15 Budget Request OIGMIGS-16 Admin Process Flow OIGMIGS-17 Labor Relations Flow OIGMIGS-18 Time Report Flow OIGMIGS-19 Admin Hearing Flow OIGMIGS-2 Prosecutor Flow OIGMIGS-20 Form: Contact OIGMIGS-21 Form: Fraud Allegation OIGMIGS-22 Case Upload OIGMIGS-23 Templates OIGMIGS-24 Emails mailto:moorej7@michigan.gov

Version 2021-1 7 of 8

OIGMIGS-26 Form: File OIGMIGS-27 API Call: DHHS Case # OIGMIGS-28 API Call: Provider # OIGMIGS-29 Cases: Default Grid Layout OIGMIGS-30 Packets OIGMIGS-31 Views OIGMIGS-32 SOP Events OIGMIGS-33 Data Migration OIGMIGS-35 ADA Compliance OIGMIGS-36 User Roles OIGMIGS-37 User Role: FIS/ES Specialist OIGMIGS-38 User Role: Prosecutor OIGMIGS-40 User Role: Overpayment Establishment Analyst/RS OIGMIGS-41 User Role: OIG Overpayment Establishment Analyst/RS (Post Go Live) OIGMIGS-42 FIS/ES Specialist and Supervisor OIGMIGS-44 Fraud: Internal New Case OIGMIGS-45 Set the System Time to EST OIGMIGS-46 Provider: Internal New Case OIGMIGS-47 Form: Cost Avoidance Dispositions OIGMIGS-48 Suggested Links OIGMIGS-49 OIG Related Case Search OIGMIGS-5 System Notifications - Standard Notifications OIGMIGS-50 Employee New Case: Complainant Contact Type Optional OIGMIGS-51 Form: Program Violations OIGMIGS-52 Both: Internal New Case OIGMIGS-53 Form: Admin Actions OIGMIGS-54 Form: New Sub Status OIGMIGS-56 Form: Contact (Auto Deny Functionality) OIGMIGS-57 Time Report: Internal New Case OIGMIGS-61 MIGS Templates OIGMIGS-63 Employee: Internal New Case OIGMIGS-64 Details>Validation Tab OIGMIGS-65 External New Case Creation via the Portal OIGMIGS-66 MIGS UAT Search Bar OIGMIGS-67 Specialized Unit Field Logic OIGMIGS-69 Yellowfin OIGMIGS-7 Background Check Flow OIGMIGS-71 Email Reliability from the MIGS v9 Application to Microsoft Outlook OIGMIGS-75 PAAM Codes OIGMIGS-76 Confirm Button for Workflow Steps OIGMIGS-77 Case Prefix Not Updating After Being Screened In OIGMIGS-79 The "DHHS Lookup Last Update within 3 business days" Logic on the Validation Tab OIGMIGS-8 OIG Closure Flow

Version 2021-1 8 of 8

OIGMIGS-81 Transition Cases from Screening Flow (Screened In) to Another Workflow OIGMIGS-82 Picklists OIGMIGS-84 Forms: Default Grid Layout OIGMIGS-86 Local Offices (Go Live) OIGMIGS-89 Inline Form Redirect/Update

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

CONTRACT CHANGE NOTICE

CONTRACT SUMMARY

CaseIQ Case Management Application, Maintenance & Support and Hosting

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

August 31, 2012 August 30, 2017 12 - 1 Year August 30, 2029

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

300 March Road, Suite 501

Ottawa, Ontario, Canada ON K2K 2E2

David McNeill

678-634-6144 dmcneill@caseiq.com

CV0067031

CUSTOMER EXPRESSIONS CORP.

C O

N

TR

A C

TO

R

Robin Lampert

517-582-2746

DTMB

Various Various

LampertR1@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Change Notice Number 30

Contract Number MA071B2200299C 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

0 Years

$8,651,938.60 $0.00 $8,651,938.60

Effective August 11, 2025, the following changes are incorporated into this Contract.

Responsibility: Contractor

Description: Contractor will configure the production environment where the application will be live.

During the 90-day adoption (postproduction warranty) period, the State will remain under the hypercare of the Project Implementation Team for a period of 30 days. The State will receive care from the Customer Success Manager, Barry Johnson, in day 31 through 90. The Project Implementation Team will still be available to fix any remaining requirements or questions at no additional cost. Contractor will continue to provide support and enablement to ensure strong adoption of the application. The Project Implementation Team Manager, Amy Theoret, is Key Personnel during the hypercare period. The Customer Success Manager in place of a Project Manager, Barry Johnson, is Key Personnel for this Contract.

Responsibility: State

Description: The State will be responsible to provide timely feedback on any issues or questions as they arise.

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

AGENCY NAME PHONE EMAIL

DTMB John Moore 517-331-5065 MooreJ7@michigan.gov

DTMB Ryan Speidel (517) 241-0552 speidelr2@michigan.gov

DTMB Giget Schlyer 517-582-8330 SchlyerG@michigan.gov

MDHHS Casey Barton BartonC3@michigan.gov

DTMB Asha Manday mandaya@michigan.gov

Program Managers for

Multi-Agency and Statewide Contracts

CHANGE NOTICE NO. 30 TO CONTRACT NO. MA071B2200299C

CHANGE NOTICE NO. 30 TO CONTRACT NO. MA071B2200299C

STATE OF MICHIGAN

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

CaseIQ Case Management Application, Maintenance & Support and Hosting

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

August 31, 2012 August 30, 2017 12 - 12 Months August 30, 2029

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

300 March Road, Suite 501

Ottawa, Ontario, Canada ON K2K 2E2

David McNeill

678-634-6144 dmcneill@caseiq.com

CV0067031

CUSTOMER EXPRESSIONS CORP.

C O

N

TR

A C

TO

R

Robin Lampert

517-582-2746

DTMB

Various Various

LampertR1@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Change Notice Number 29

Contract Number MA071B2200299C 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

$8,651,938.60 $0.00 $8,651,938.60

Effective May 1, 2025, the Contract is amended to include the following agreement.

Accessibility Requirements.

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.

Please note (1) a Program Manager has been changed from Pat Thelen to Asha Manday, (2) the vendor address has been updated, and (3) extended purchasing is allowed, but was accidentally marked as "no" in some prior change notices.

DTMB Ryan Speidel (517) 241-0552 speidelr2@michigan.gov

DTMB Giget Schlyer 517-582-8330 SchlyerG@michigan.gov

MDHHS Casey Barton BartonC3@michigan.gov

DTMB Asha Manday mandaya@michigan.gov

Program Managers…