250000001313.pdf

Michigan.gov/MiProcurement

2025-1 1

SOFTWARE CONTRACT TERMS AND CONDITIONS

These Terms and Conditions, together with all Schedules (including the Statement(s) of Work), Exhibits and any other applicable attachments or addenda (Collectively this “Contract”) are agreed to between the State of Michigan (the “State”) and IDSi International Inc (“Contractor”), a New Jersey Corporation. This Contract is effective on September 1, 2025 (“Effective Date”), and unless terminated, will expire on August 31, 2030 (the “Term”).

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

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

“Acceptance” has the meaning set forth in Section 9.

“Acceptance Tests” means such tests as may be conducted in as described in Section 9 and any applicable Statement of Work to determine whether the Software meets the requirements of this Contract and the Documentation.

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

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

“Allegedly Infringing Materials” has the meaning set forth in Section 18.

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

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

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

“Change Notice” means a writing executed by the parties to the Contract memorializing a change to the Contract.

“Change Proposal” has the meaning set forth in Subsection 2.2.

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

2025-1 2

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

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

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

“Contract Change” has the meaning set forth in Subsection 2.2.

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

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

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

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

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

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

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

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

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

“Digital Accessibility Standards” means the accessibility standards provided in the SOM Digital Standards, located at https://www.michigan.gov/standards.

“Disaster Recovery Plan” refers to the set(s) of documents, instructions, and procedures which enable the Contractor to respond to accidents, disasters, emergencies, or threats without any stoppage or hindrance in its key operations and to the actions the Contractor takes to meet the Recovery Point and Recovery Time Objectives.

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

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

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

https://www.michigan.gov/som/footer/policies/som-applications-and-site-standards

2025-1 3

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

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

“Hardware” means all computer hardware or other equipment provided by Contractor under this Contract, if any, including but not limited to any related accessories.

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

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

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

“Integration Testing” has the meaning set forth in Section 9.

“Intellectual Property Rights” means all or any of the following: (a) patents, patent disclosures, and inventions (whether patentable or not); (b) trademarks, service marks, trade dress, trade names, logos, corporate names, and domain names, together with all of the associated goodwill;

(c) copyrights and copyrightable works (including computer programs), mask works and rights in data and databases; (d) trade secrets, know-how and other confidential information; and (e) all other intellectual property rights, in each case whether registered or unregistered and including all applications for, and renewals or extensions of, such rights, and all similar or equivalent rights or forms of protection provided by applicable law in any jurisdiction throughout the world.

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

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

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

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

2025-1 4

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

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

“Nonconformity” or “Nonconformities” means any failure or failures of a Deliverable, to conform to the requirements of this Contract.

“Offshore Resources” mean resources, including Contractor Personnel, outside of the United States or its territories.

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

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

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

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

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

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

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

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

2025-1 5

“Services” means any of the services, including but not limited to, Hosted Services, installation, configuration, implementation, and/or Support Services, that the Contractor is required to or otherwise does provide under this Contract.

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

“Site” means any physical location(s) designated by the State in, or in accordance with, this Contract or a Statement of Work for delivery and installation of the Deliverable, if applicable.

“Software” means TIER II Manager licensed to the State, including any Maintenance Releases or New Versions provided to the State and any Customizations or Configurations made by or for the State.

“Solicitation” means the State’s request to solicit responses for a Solution under this Contract.

“Solution” means Deliverables and Services singularly or in any combination thereof, as applicable, set forth in a Statement of Work.

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

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

“State” means the State of Michigan.

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

“State Hosted” means the Operating Environment is not provided by Contractor or one or more of its Permitted Subcontractors.

“State Materials” means all materials and information, including but not limited to documents, data, know-how, ideas, methodologies, specifications, software, hardware, content and technology, in any form or media, directly or indirectly provided or made available to Contractor by or on behalf of the State in connection with this Contract.

“State Program Managers” are the individuals appointed by the State, or their designees, to (a) monitor and coordinate the day-to-day activities of this Contract; (b) co-sign off on Acceptance of the Deliverables; and (c) perform other duties as may be specified in a Statement of Work. Program Managers will be identified in Schedule A or subsequent Change Notices.

“State Systems” means the information technology infrastructure, including the computers, software, databases, electronic systems (including database management systems) and networks, of the State or any of its designees.

2025-1 6

“Statement of Work” means any statement of work entered into by the parties and incorporated into this Contract. The initial Statement of Work is attached as Schedule A.

“Stop Work Order” has the meaning set forth in Section 15.

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

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

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

“System Integration Testing” has the meaning set forth in Schedule I.

“Technical Specification” means, with respect to any Software, the document setting forth the technical specifications for such Software and included in a Statement of Work.

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

“Testing Period” has the meaning set forth in Section 9.

“Third-Party Components” means all components, including Open-Source Components, that are included in or used in connection with the Software and are specifically identified by Contractor in the Contractor’s Software Bill of Materials, in an applicable Statement of Work or elsewhere in this Contract, or as otherwise required by this Contract, including without limitation as part of the State’s Security Accreditation Process defined in Schedule E – Data Security Requirements.

“Transition Period” has the meaning set forth in Section 16.

“Transition Responsibilities” has the meaning set forth in Section 16.

“Unauthorized Removal” has the meaning set forth in Subsection 2.5.

“Unauthorized Removal Credit” has the meaning set forth in Subsection 2.5.

“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. User Data does not include any data in the possession of or collected by Contractor prior to or independently of the performance of the Services or any use of the Software under this Contract.

“Warranty Period” means the 90 calendar-day period commencing on the date of the State's Acceptance of the Software or System (if Contractor is providing Hardware under this Contract) for which Support Services are provided free of charge.

“Work Product” means everything made or created by Contractor, regardless of whether created, developed, or generated by a human, non-human, or some combination thereof, specifically and solely for the State and which is not generally available to Contactor’s other customers, that Contractor is required to, or otherwise does, provide to the State under this Contract including but not limited to Customizations, application programming interfaces, computer scripts, macros, user interfaces, reports, project management documents, forms, templates, and other State-

2025-1 7 specific documents and related materials together with all ideas, concepts, processes, and methodologies developed in connection with this Contract whether or not embodied in this Contract.

2. Duties of Contractor. Contractor will provide the Solution pursuant to Statement(s) of Work entered into under this Contract. Contractor will provide the Solution in a timely, professional manner and in accordance with the terms, conditions, and Specifications set forth in this Contract and the Statement(s) of Work.

2.1 Statement of Work Requirements. No Statement of Work will be effective unless signed by each party’s Contract Administrator. The term of each Statement of Work will commence on the parties' full execution of a Statement of Work and terminate when the parties have fully performed their obligations. The terms and conditions of this Contract will apply at all times to any Statements of Work entered into by the parties and incorporated into this Contract. The State will have the right to terminate such Statement of Work as set forth in Section 16. Contractor acknowledges that time is of the essence with respect to Contractor’s obligations under each Statement of Work and agrees that prompt and timely performance of all such obligations in accordance with this Contract and the Statements of Work (including the Implementation Plan and all Milestone Dates) is strictly required.

2.2 Change Control Process. The State may at any time request in writing (each, a “Change Request”) changes to the Contract, including without limitation changes to the Solution or adding a new Statement of Work (each, a “Contract Change”). Upon the State’s submission of a Change Request, the parties will evaluate and implement all Contract Changes in accordance with this Section.

(a) As soon as reasonably practicable, and in any case within 20 Business Days following receipt of a Change Request, Contractor will provide the State with a written proposal for implementing the requested Contract Change (“Change Proposal”), setting forth:

(i) a written description of the proposed Contract Changes to any part of the Solution;

(ii) an amended Implementation Plan reflecting: (A) the schedule for commencing and completing any addition or modification to the Solution;

and (B) the effect of such Contract Changes, if any, on completing any other Services under a Statement of Work;

(iii) any additional State Resources Contractor deems necessary to carry out such Contract Changes; and

(iv) any increase or decrease in Fees resulting from the proposed Contract Changes, which increase, or decrease will reflect only the increase or decrease in time and expenses Contractor requires to carry out the Contract Change.

(b) Within 30 Business Days following the State’s receipt of a Change Proposal, the State will by written notice to Contractor, approve, reject, or propose modifications to such Change Proposal. If the State proposes modifications, Contractor must modify and re-deliver the Change Proposal reflecting such modifications, or notify

2025-1 8 the State of any disagreement, in which event the parties will negotiate in good faith to resolve their disagreement. Upon the State’s approval of the Change Proposal or the parties’ agreement on all proposed modifications each parties’ Contractor Administrator will sign a Change Notice.

(c) However, if the parties fail to enter into a Change Notice within 15 Business Days following the State’s response to a Change Proposal, the State may, in its discretion:

(i) require Contractor to perform or provide the Solution under the existing Statement of Work without the Contract Change;

(ii) require Contractor to continue to negotiate a Change Notice;

(iii) initiate a Dispute Resolution Procedure; or

(iv) notwithstanding any provision to the contrary in a Statement of Work, terminate this Contract under Subsection 16.1.

(d) No Contract Change will be effective until the parties have executed a Change Notice. Notwithstanding the foregoing, no Change Notice executed after the Effective Date will be construed to amend or modify this Contract in any way, unless it specifically states its intent to do so and cites the section or sections amended. Except as the State may request in its Change Request or otherwise in writing, Contractor must continue to perform its obligations in accordance with a Statement of Work pending negotiation and execution of a Change Notice.

Contractor will use its best efforts to limit any delays or Fee increases from any Contract Change to those necessary to perform the Contract Change in accordance with the applicable Change Notice. Each party is responsible for its own costs and expenses of preparing, evaluating, negotiating, and otherwise processing any Change Request, Change Proposal, and Change Notice.

(e)The performance of any functions, activities, tasks, obligations, roles and responsibilities comprising the Solution as described in this Contract are considered part of the Solution and, thus, will not be considered a Contract Change. This includes the delivery of all Deliverables in accordance with their respective Specifications, and the diagnosis and correction of Nonconformities discovered in Deliverables prior to their Acceptance by the State or, subsequent to their Acceptance by the State, as necessary for Contractor to fulfill its associated warranty requirements and its Support Services under this Contract.

(f) Contractor may, on its own initiative and at its own expense, prepare and submit its own Change Request to the State. However, the State will be under no obligation to approve or otherwise respond to a Change Request initiated by Contractor.

2.3 Contractor Personnel.

(a) Contractor is solely responsible for all Contractor Personnel and for the payment of their compensation, including, if applicable, withholding of income taxes, and the payment and withholding of social security and other payroll taxes, unemployment insurance, workers’ compensation insurance payments and disability benefits.

2025-1 9

(b) Prior to any Contractor Personnel performing any Services, Contractor will:

(i) ensure that such Contractor Personnel have the legal right to work in the United States;

(ii) upon request, require such Contractor Personnel to execute written agreements, in form and substance acceptable to the State, that bind such Contractor Personnel to confidentiality provisions that are at least as protective of the State’s information (including all Confidential Information) as those contained in this Contract; and

(iii) upon request, or as otherwise specified in a Statement of Work, perform background checks on all Contractor Personnel prior to their assignment.

The scope is at the discretion of the State and documentation must be provided as requested. Contractor is responsible for all costs associated with the requested background checks. The State, in its sole discretion, may also perform background checks. Pursuant to Michigan law, all agencies subject to IRS Pub. 1075 are required to ask the Michigan State Police to perform fingerprint background checks on all employees, including Contractor and subcontractor employees, who may have Access to any database of information maintained by the federal government that contains confidential or personal information, including, but not limited to, federal tax information. Further, pursuant to Michigan law, any agency described above is prohibited from providing Contractors or subcontractors with the result of such background check. For more information, please see Michigan Public Act 427 of 2018.

(c) Contractor and all Contractor Personnel will comply with all rules, regulations, and policies of the State that are communicated to Contractor in writing, including security procedures concerning systems and data and remote access, building security procedures, including the restriction of access by the State to certain areas of its premises or systems, and general health and safety practices and procedures.

(d) The State reserves the right to require the removal of any Contractor Personnel found, in the judgment of the State, to be unacceptable. The State’s request must be written with reasonable detail outlining the reasons for the removal request.

Replacement personnel for the removed person must be fully qualified for the position. If the State exercises this right, and Contractor cannot immediately replace the removed personnel, the State agrees to negotiate an equitable adjustment in schedule or other terms that may be affected by the State’s required removal.

2.4 Contractor Project Manager. Throughout the Term of this Contract, Contractor must maintain a Contractor employee acceptable to the State to serve as Contractor Project Manager, who will be considered Key Personnel of Contractor.

(a) Contractor Project Manager must:

(i) have the requisite authority, and necessary skill, experience, and qualifications, to perform in such capacity;

2025-1 10

(ii) be responsible for overall management and supervision of Contractor’s performance under this Contract; and

(iii) be the State’s primary point of contact for communications with respect to this Contract, including with respect to giving and receiving all day-to-day approvals and consents.

(b) Contractor Project Manager must attend all regularly scheduled meetings as set forth in the Implementation Plan and will otherwise be available as set forth in a Statement of Work.

(c) Contractor will maintain the same Contractor Project Manager throughout the Term of this Contract, unless:

(i) the State requests in writing the removal of Contractor Project Manager;

or

(ii) the State consents in writing to any removal requested by Contractor in writing; or

(iii) the Contractor Project Manager ceases to be employed by Contractor, whether by resignation, involuntary termination or otherwise.

(d) Upon the occurrence of any event set forth in Subsections 2.4(c)(i-iii) above, Contractor will promptly replace its Contractor Project Manager. Such replacement will be subject to the State's prior written approval.

2.5 Contractor’s Key Personnel.

(a) The State has the right to recommend and approve in writing the initial assignment, as well as any proposed reassignment or replacement, of any Key Personnel. Before assigning an individual to any Key Personnel position, Contractor will notify the State of the proposed assignment, introduce the individual to the State Program Managers or their designees, and provide the State with a resume and any other information about the individual reasonably requested by the State.

The State reserves the right to interview the individual before granting written approval. In the event the State finds a proposed individual unacceptable, the State will provide a written explanation including reasonable detail outlining the reasons for the rejection.

(b) Contractor will not remove any Key Personnel from their assigned roles on this Contract without the prior written consent of the State. The Contractor’s removal of Key Personnel without the prior written consent of the State is an unauthorized removal (“Unauthorized Removal”). An Unauthorized Removal does not include replacing Key Personnel for reasons beyond the reasonable control of Contractor, including illness, disability, leave of absence, personal emergency circumstances, resignation, or for cause termination of the Key Personnel’s employment. Any Unauthorized Removal may be considered by the State to be a material breach of this Contract.

(c) It is further acknowledged that an Unauthorized Removal will interfere with the timely and proper completion of this Contract, to the loss and damage of the State, 2025-1 11 and that it would be impracticable and extremely difficult to determine and remedy the actual damage sustained by the State as a result of any Unauthorized Removal.

Therefore, Contractor and the State agree that in the case of any Unauthorized Removal in respect of which the State does not elect to exercise its rights under Section 16, Contractor will issue to the State an amount equal to $25,000 per individual (each, an “Unauthorized Removal Credit”).

(d) Contractor acknowledges and agrees that each of the Unauthorized Removal Credits assessed under Subsection 2.5(c) above: (i) is a reasonable estimate of and compensation for the anticipated or actual harm to the State that may arise from the Unauthorized Removal, which would be impossible or very difficult to accurately estimate; and (ii) may, at the State’s option, be credited or set off against any Fees or other charges payable to Contractor under this Contract.

2.6 Subcontractors. Contractor must obtain prior written approval of the State, which consent may be given or withheld in the State’s sole discretion, before engaging any Permitted Subcontractor to provide Services to the State under this Contract. Engagement of any subcontractor or Permitted Subcontractor by Contractor does not relieve Contractor of its representations, warranties or obligations under this Contract. Without limiting the foregoing, Contractor will:

(a) be responsible and liable for the acts and omissions of each such subcontractor (including such Permitted Subcontractor and Permitted Subcontractor's employees who, to the extent providing the Solution, will be deemed Contractor Personnel) to the same extent as if such acts or omissions were by Contractor or its employees;

(b) be responsible for all fees and expenses payable to, by or on behalf of each subcontractor and Permitted Subcontractor in connection with this Contract, including, if applicable, withholding of income taxes, and the payment and withholding of social security and other payroll taxes, unemployment insurance, workers' compensation insurance payments and disability benefits; and

(c) notify the State of the location of the Permitted Subcontractor and indicate if it is located within the United States.

3. Notices. All notices and other communications required or permitted under this Contract must be in writing and will be considered given and received: (a) when verified by written receipt if sent by courier; (b) when received if sent by mail without verification of receipt; or (c) when verified by automated receipt or electronic logs if sent by facsimile or email.

If to State: If to Contractor:

Todd Huhn

320 South Walnut St.

Lansing, MI 48909 huhnt@michigan.gov

Shilpa Mohan

2125 Center Ave, Suite 611

Fort Lee, NJ 07024 shilpamo@hazconnect.com

201-302-9494

2025-1 12

4. Insurance. Contractor must maintain the minimum insurances identified in the Insurance Schedule attached as Schedule C.

5. Licensing.

5.1 Contractor is providing Hosted Services and Support Services of the Software.

5.5 State License Grant to Contractor. The State hereby grants to Contractor a limited, non-exclusive, non- transferable license (i) to use the State's (or individual agency’s, department’s or division’s) name, trademarks, service marks or logos, solely in accordance with the State’s specifications, and (ii) to display, reproduce, distribute and transmit in digital form the State’s (or individual agency’s, department’s or division’s) name, trademarks, service marks or logos in connection with promotion of the Services as communicated to Contractor by the State. Use of the State’s (or individual agency’s, department’s or division’s) name, trademarks, service marks or logos will be specified in the applicable Statement of Work. Contractor is provided a limited license to State Materials for the sole and exclusive purpose of providing the Services.

6. Third-Party Components. At least 30 days prior to adding new third-party components, Contractor will provide the State with notification information identifying and describing the addition. Throughout the Term, on an annual basis, Contractor will provide updated information identifying and describing any third-party components included in the Software. Contractor is responsible for ensuring that all Third-Party Components are properly licensed for the State’s use.

7. Intellectual Property Rights

7.1 Ownership Rights in Software

(a) For purposes of this Section 7 only, the term “Software” does not include Customizations.

(b) Subject to the rights and licenses granted by Contractor in this Contract and the provisions of Subsection 7.1(c):

(i) Contractor reserves and retains its entire right, title, and interest in and to all Intellectual Property Rights arising out of or relating to the Software; and

(ii) none of the State or Authorized Users acquire any ownership of Intellectual Property Rights in or to the Software or Documentation as a result of this Contract.

(c) As between the State, on the one hand, and Contractor, on the other hand, the State has, reserves, and retains, sole and exclusive ownership of all right, title and interest in and to State Materials, User Data, including all Intellectual Property Rights arising therefrom or relating thereto.

7.2 The State is and will be the sole and exclusive owner of all right, title, and interest in and to all Work Product created, developed, or generated exclusively for the State under this Contract, including all Intellectual Property Rights. In furtherance of the foregoing:

(a) Contractor will create all Work Product as work made for hire as defined in Section 101 of the Copyright Act of 1976; and

2025-1 13

(b) to the extent any Work Product does not qualify as, or otherwise fails to be, work made for hire, Contractor hereby:

(i) assigns, transfers, and otherwise conveys to the State, irrevocably and in perpetuity, throughout the universe, all right, title, and interest in and to such Work Product, including all Intellectual Property Rights; and

(ii) irrevocably waives claims Contractor may now or hereafter have in any jurisdiction to so-called “moral rights” or rights of droit moral with respect to the Work Product.

8. Software Implementation.

8.1 Implementation. Contractor will as applicable; deliver, install, configure, integrate, and otherwise provide and make fully operational the Software on or prior to the applicable Milestone Date in accordance with the criteria set forth in a Statement of Work and the Implementation Plan.

8.2 Site Preparation. Unless otherwise set forth in a Statement of Work, Contractor is responsible for ensuring the relevant Operating Environment is set up and in working order to allow Contractor to deliver and install the Software on or prior to the applicable Milestone Date. Contractor will provide the State with such notice as is specified in a Statement of Work, prior to delivery of the Software to give the State sufficient time to prepare for Contractor’s delivery and installation of the Software. If the State is responsible for Site preparation, Contractor will provide such assistance as the State requests to complete such preparation on a timely basis.

9. Software Acceptance Testing.

9.1 Acceptance Testing.

(a) Unless otherwise specified in a Statement of Work, upon installation of the Software, or in the case of Contractor Hosted Software, when Contractor notifies the State in writing that the Solution is ready for use, Acceptance Tests will be conducted as set forth in this Section 9 to ensure the Software conforms to the requirements of this Contract, including the applicable Specifications and Documentation.

(b) All Acceptance Tests will take place at the designated Site(s) in the Operating Environment described in a Statement of Work, commence on the Business Day following installation of the Software, or the receipt by the State of the notification referenced in Subsection 9.1(a), and be conducted diligently for up to 30 Business Days, or such other period as may be set forth in a Statement of Work (the “Testing Period”). Acceptance Tests will be conducted by the party responsible as set forth in a Statement of Work or, if a Statement of Work does not specify, the State, provided that:

(i) for Acceptance Tests conducted by the State, if requested by the State, Contractor will make suitable Contractor Personnel available to observe or participate in such Acceptance Tests; and

2025-1 14

(ii) for Acceptance Tests conducted by Contractor, the State has the right to observe or participate in all or any part of such Acceptance Tests.

9.2 Contractor is solely responsible for all costs and expenses related to Contractor’s performance of, participation in, and observation of Acceptance Testing.

(a) Upon delivery and installation of any application programming interfaces, Configuration or Customizations, or any other applicable Work Product, to the Software under a Statement of Work, additional Acceptance Tests will be performed on the modified Software as a whole to ensure full operability, integration, and compatibility among all elements of the Software (“Integration Testing”). Integration Testing is subject to all procedural and other terms and conditions set forth in this Section.

(b) The State may suspend Acceptance Tests and the corresponding Testing Period by written notice to Contractor if the State discovers a material Nonconformity in the tested Software or part or feature of the Software. In such event, Contractor will immediately, and in any case within 10 Business Days, correct such Nonconformity, whereupon the Acceptance Tests and Testing Period will resume for the balance of the Testing Period.

9.3 Notices of Completion, Non-Conformities, and Acceptance. Within 15 Business Days following the completion of any Acceptance Tests, including any Integration Testing, the party responsible for conducting the tests will prepare and provide to the other party written notice of the completion of the tests. Such notice must include a report describing in reasonable detail the tests conducted and the results of such tests, including any uncorrected Nonconformity in the tested Software.

(a) If such notice is provided by either party and identifies any Nonconformities, the parties’ rights, remedies, and obligations will be as set forth in Subsection 9.4 and Subsection 9.5.

(b) If such notice is provided by the State, is signed by the State Program Managers or their designees, and identifies no Nonconformities, such notice constitutes the State's Acceptance of such Software.

(c) If such notice is provided by Contractor and identifies no Non-Conformities, the State will have 30 Business Days to use the Software in the Operating Environment and determine, in the exercise of its sole discretion, whether it is satisfied that the Software contains no Nonconformities, on the completion of which the State will, as appropriate:

(i) notify Contractor in writing of Nonconformities the State has observed in the Software and of the State’s non-acceptance thereof, whereupon the parties’ rights, remedies and obligations will be as set forth in Subsection

9.4 and Subsection 9.5; or

(ii) provide Contractor with a written notice of its Acceptance of such Software, which must be signed by the State Program Managers or their designees.

2025-1 15

9.4 Failure of Acceptance Tests. If Acceptance Tests identify any Non-Conformities, Contractor, at Contractor’s sole cost and expense, will remedy all such Nonconformities and re-deliver the Software, in accordance with the requirements set forth in the Contract.

Redelivery will occur as promptly as commercially possible and, in any case, within 30 Business Days following, as applicable, Contractor’s:

(a) completion of such Acceptance Tests, in the case of Acceptance Tests conducted by Contractor; or

(b) receipt of the State’s notice under Subsection 9. (a) or (c)(i), identifying any Nonconformities.

9.5 Repeated Failure of Acceptance Tests. If Acceptance Tests identify any Nonconformity in the Software after a second or subsequent delivery of the Software, or Contractor fails to re-deliver the Software on a timely basis, the State may, in its sole discretion, by written notice to Contractor:

(a) continue the process set forth in this Section 9;

(b) accept the Software as a nonconforming deliverable, in which case the Fees for such Software will be reduced equitably to reflect the value of the Software as received relative to the value of the Software had it conformed; or

(c) deem the failure to be a non-curable material breach of this Contract and a Statement of Work and terminate this Contract in accordance with Section 16.

9.6 Acceptance. Acceptance (“Acceptance”) of the Software (subject, where applicable, to the State’s right to Integration Testing) will occur on the date that is the earliest of the State’s delivery of a notice accepting the Software under Subsection 9.3(b), or (c)(ii).

Acceptance of the Software may be conditioned upon System Acceptance, if Contractor is providing Hardware, under the terms of this Contract.

10. Non-Software Acceptance.

10.1 If Contractor is providing Hardware under this Contract, Contractor will comply with the requirements for delivery, acceptance and warranty of Hardware as set forth in Schedule H.

10.2 System Acceptance. If Contractor is providing Hardware under this Contract, Contractor will comply with the requirements for acceptance testing of the Software and Hardware together as a System, as set forth in Schedule I.

10.3 All other non-Software Deliverables are subject to inspection and testing by the State within 30 calendar days of the State’s receipt of them (“State Review Period”), unless otherwise provided in the Statement of Work. If the non-Software Deliverables are not fully accepted by the State, the State will notify Contractor by the end of the State Review Period that either: (a) the non-Software Deliverables are accepted but noted deficiencies must be corrected; or (b) the non-Software Deliverables are rejected. If the State finds material deficiencies, it may: (i) reject the non-Software Deliverables without performing any further inspections; (ii) demand performance at no additional cost; or (iii) terminate this Contract in accordance with Section 16.

2025-1 16

10.4 Within 10 Business Days from the date of Contractor’s receipt of notification of acceptance with deficiencies or rejection of any non-Software Deliverables, Contractor must cure, at no additional cost, the deficiency and deliver unequivocally acceptable non- Software Deliverables to the State. If acceptance with deficiencies or rejection of the non- Software Deliverables impacts the content or delivery of other non-completed non- Software Deliverables, the parties’ respective Program Managers must determine an agreed to number of days for re-submission that minimizes the overall impact to the Contract. However, nothing herein affects, alters, or relieves Contractor of its obligations to correct deficiencies in accordance with the time response standards set forth in this Contract.

10.5 If Contractor is unable or refuses to correct the deficiency within the time response standards set forth in this Contract, the State may cancel the order in whole or in part. The State, or a third party identified by the State, may provide the non-Software Deliverables and recover the difference between the cost to cure and the Contract price plus an additional 10% administrative fee.

11. Assignment. Contractor may not assign this Contract or any of its rights or delegate any of its duties or obligations hereunder, voluntarily, or involuntarily, whether by merger (regardless of whether it is the surviving or disappearing entity), conversion, consolidation, dissolution, or operation of law to any other party without the prior written approval of the State. Upon notice to Contractor, the State, in its sole discretion, may assign in whole or in part, its rights or responsibilities under this Contract to any other governmental entity if such assignment is made reasonably necessary by operation of controlling law or regulation. If the State determines that a novation of the Contract to a third party is necessary, Contractor will agree to the novation and provide all necessary documentation and signatures.

12. Change of Control. Contractor will notify the State, within 30 calendar days of any public announcement or otherwise once legally permitted to do so, of a change in Contractor’s organizational structure or ownership. For purposes of this Contract, a change in control means any of the following:

(a) a sale of more than 50% of Contractor’s stock;

(b) a sale of substantially all of Contractor’s assets;

(c) a change in a majority of Contractor’s board members;

(d) consummation of a merger or consolidation of Contractor with any other entity;

(e) a change in ownership through a transaction or series of transactions;

(f) or the board (or the stockholders) approves a plan of complete liquidation.

A change of control does not include any consolidation or merger effected exclusively to change the domicile of Contractor, or any transaction or series of transactions principally for bona fide equity financing purposes. In the event of a change of control, Contractor must require the successor to assume this Contract and all of its obligations under this Contract.

13. Ordering, Invoices and Payment.

13.1 Authorizing Document. The document for the Contract will be a delivery order. No work should start until the delivery order is received by the Contractor.

2025-1 17

13.2 Invoices must conform to the requirements communicated from time-to-time by the State. All undisputed amounts are payable within 45 days of the State’s receipt. Contractor may only charge for the Solution provided as specified in Statement(s) of Work. Invoices must include an itemized statement of all charges.

13.3 The State has the right to withhold payment of any disputed amounts until the parties agree as to the validity of the disputed amount. The State will notify Contractor of any dispute within a reasonable time. Payment by the State will not constitute a waiver of any rights as to Contractor’s continuing obligations, including claims for deficiencies or substandard Deliverables. Contractor’s acceptance of final payment by the State constitutes a waiver of all claims by Contractor against the State for payment under this Contract, other than those claims previously filed in writing on a timely basis and still disputed.

13.4 The State will only disburse payments under this Contract through Electronic Funds Transfer (EFT). Contractor must register with the State at http://www.michigan.gov/SIGMAVSS to receive electronic fund transfer payments. If Contractor does not register, the State is not liable for failure to provide payment.

13.5 Right of Setoff. Without prejudice to any other right or remedy it may have, the State reserves the right to set off at any time any amount then due and owing to it by Contractor against any amount payable by the State to Contractor under this Contract.

13.6 Taxes. The State is exempt from federal excise tax, state, and local sales taxes, and use taxes if the Solution purchased under this Contract is for the State’s exclusive use.

Contractor will not include the collection of taxes for which the State is exempt in any invoices or payments related…