3200068.pdf

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

STATE OF MICHIGAN PROCUREMENT

Department Technology, Management and Budget Central Procurement Services

CONTRACT CHANGE NOTICE

CONTRACT SUMMARY

Law Enforcement Information Network - Disaster Rec

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

January 1, 2013 December 31, 2017 13 - 1 Year December 31, 2025

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

400 Quadrange Drive, Suite F

Bolingbrook IL 60440

Marc Smith

630-754-8820 x149 msmith@openfox.com

CV0017417

COMPUTER PROJECTS OF

ILLINOIS, INC.

C O

N

TR

A C

TO

R

Jarrod Barron

(517) 249-0406

DTMB

Various Various

BarronJ1@michigan.gov

C on tr ac t A dm in is tr at or

Pr og ra m

M an ag er

ST

A

TE

Change Notice Number 21

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

5 Years December 31, 2030

$4,181,001.94 $1,096,602.46 $5,277,604.40

DESCRIPTION

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

Effective 12/16/2025, the parties exercise all five available option years and add $1,096,602.46 to cover the cost of ongoing maintenance services through 12/31/2030 per the attached documentation. All other terms, conditions, specifications and pricing remain the same. Per Contractor, Agency, DTMB Central Procurement and State Administrative Board approval on 12/16/2025.

AGENCY NAME PHONE EMAIL

DTMB Jim Coggin 517-243-5265 CogginJ@michigan.gov

MSP Kevin Collins 517-284-3046 CollinsK@michigan.gov

Program Managers for

Multi-Agency and Statewide Contracts

CHANGE NOTICE NO. 21 TO CONTRACT NO. MA071B3200068C

CHANGE NOTICE 21 COST SUMMARY

Calendar Year Cost 2026 $ 198,457.41 2027 $ 208,380.28 2028 $ 218,799.29 2029 $ 229,739.26 2030 $ 241,226.22

TOTAL $ 1,096,602.46

CHANGE NOTICE 21 COST BREAKDOWN BY CALENDAR YEAR

01/01/2026 - 12/31/2026

Product Description Qty. Unit Price Total Price

MSG-SPT-1

Software Licenses, Maintenance, and Support on the OpenFox® software for production systems A and B.

$70,426.40

$140,852.80

HOT-SPT-1

Software Licenses and Maintenance and Support on the OpenFox® Hotfiles

$28,538.50

$28,538.50

ARC-SPT-1

Support on the OpenFox® Archive

$14,498.95

$14,498.95

MSG-SPT-MSC-1

OpenFox® State Specific Customizations 1

$14,567.16

$14,567.16

Totals $198,457.41

01/01/2027 - 12/31/2027

Product Description Qty. Unit Price Total Price

MSG-SPT-1

Software Licenses, Maintenance, and Support

$73,947.72

$147,895.44

$29,965.43

$29,965.43

$15,223.90

$15,223.90

$15,295.52

$15,295.52

Totals $208,380.28

01/01/2028 - 12/31/2028

MSG-SPT-1

Software Licenses, Maintenance, and Support

$77,645.11

$155,290.21

$31,463.70

$31,463.70

$15,985.09

$15,985.09

$16,060.29

$16,060.29

Totals $218,799.29

01/01/2029 - 12/31/2029

MSG-SPT-1

Software Licenses, Maintenance, and Support

$81,527.36

$163,054.72

$33,036.88

$33,036.88

$16,784.35

$16,784.35

$16,863.31

$16,863.31

Totals $229,739.26

01/01/2030 - 12/31/2030

MSG-SPT-1

Software Licenses, Maintenance, and Support

$85,603.73

$171,207.46

$34,688.73

$34,688.73

$17,623.56

$17,623.56

$17,706.47

$17,706.47

Totals $241,226.22

STATE OF MICHIGAN

ENTERPRISE PROCUREMENT

DTMB

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

CONTRACT CHANGE NOTICE

CONTRACT SUMMARY

Law Enforcement Information Network - Disaster Rec

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

January 1, 2013 December 31, 2017 13 - 1 Year December 31, 2025

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

400 Quadrange Drive, Suite F

Bolingbrook IL 60440

Marc Smith

630-754-8820 x149 msmith@openfox.com

CV0017417

COMPUTER PROJECTS OF

ILLINOIS, INC.

C O

N

TR

A C

TO

R

Jarrod Barron

(517) 249-0406

DTMB

Various Various

BarronJ1@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Change Notice Number 20

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

$4,181,001.94 $0.00 $4,181,001.94

DESCRIPTION

Effective 7/16/2025, the parties add the following language to the Contract:

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

Per Contractor, Agency, and DTMB Procurement approval.

DTMB Jim Coggin 517-243-5265 CogginJ@michigan.gov

MSP Kevin Collins 517-284-3046 CollinsK@michigan.gov

Program Managers for

CHANGE NOTICE NO. 20 TO CONTRACT NO. MA071B3200068C

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

Law Enforcement Information Network - Disaster Rec

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

January 1, 2013 December 31, 2017 13 - 12 Months December 31, 2025

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

400 Quadrange Drive, Suite F

Bolingbrook IL 60440

Marc Smith

630-754-8820 x149 msmith@openfox.com

CV0017417

COMPUTER PROJECTS OF

ILLINOIS, INC.

C O

N

TR

A C

TO

R

Jarrod Barron

(517) 249-0406

DTMB

Various Various

BarronJ1@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Change Notice Number 19

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

$4,019,301.94 $161,700.00 $4,181,001.94

DESCRIPTION

Effective 8/26/2024, the parties add $161,700.00 for the services detailed in the attached NCIC ERPO Implementation statement of work. All other terms, conditions, specifications, and pricing remain the same. Per contractor, agency and DTMB procurement approval.

Internal State Note: Remaining Ad Board funds after this CN: $51,299.99.

MSP Kevin Collins 517-284-3046 CollinsK@michigan.gov

DTMB Jim Coggin 517-243-5265 CogginJ@michigan.gov

Program Managers for

CHANGE NOTICE NO. 19 TO CONTRACT NO. MA071B3200068C

Michigan State Police

NCIC ERPO Implementation

Statement of Work

MI-2024-001

Computer Projects of Illinois, Inc.

400 Quadrangle Drive, Suite F

Bolingbrook, IL 60440

(630) 754-8820

Revision Tracking The following is the document control for the revisions to this document:

Revision Date of Issuance Author(s) Brief Description of Change

0.00 02/01/2024 Travis Santa Maria Final business requirements and processing rules received from Customer

1.00 02/05/2024 Lori Ambrose Version 1.00 for CPI and Customer acceptance

1.01 03/15/2024 Travis Santa Maria Incorporated Customer-requested modifications to ERPO requirements

1.02 04/09/2024 Lori Ambrose Made State-specific customizations to CPI’s standard SOW template

1.03 04/12/2024 Lori Ambrose Merged ERPO Scope of Work and proposed State-specific SOW template

1.04 04/28/2024 Travis Santa Maria & Lori Ambrose

Additional clarifications and revisions requested by Customer

1.05 05//17/2024 Lori Ambrose Made Customer-requested modifications to:

Section 8.2 noted “None identified as of the date of CPI Signature of Acceptance on page 2” Section 14.3.3 fourth bullet point, remove “with” Section 14.3.4 third paragraph, insert “a value of “Y” in”

2.00 05/20/2024 Lori Ambrose Version 2.00 for CPI and Customer acceptance

2.01 05/21/2024 Lori Ambrose Modified last line in Section 2.3 to remove “NIC” from NAM/RAC/SEX/DOB/NIC.

2.02 06/25/2024 Lori Ambrose Clarifications and revisions to Section 10 per CPI Legal Counsel

Definitions The following are definitions of terms, abbreviations and acronyms used in this document:

Term, Abbreviation or Acronym Definition AICPA American Institute of Certified Public Accountants AKA Alias CAB Change Advisory Board CJIS Criminal Justice Information Services CPI Computer Projects of Illinois, Inc.

CRO Clear Extreme Risk Protection Order CSUP Cancel Supplemental CTI Court ORI CTRO Clear Temporary Extreme Risk Protection Order Customer (“MSP”) Michigan State Police DB Database DKT Court Docket Number DOB Date of Birth DOW Date of Order DOX Expiration Date DTMB Michigan Department of Technology, Management and Budget EIE Entered in Error ENRO Enter Supplemental Extreme Risk Protection Order ERO Enter Extreme Risk Protection Order EROC Enter Extreme Risk Protection Order - Caution ERPO Extreme Risk Protection Order ESUP Enter Supplemental ETRC Enter Temporary Extreme Risk Protection Order - Caution ETRO Enter Temporary Extreme Risk Protection Order EXP Record Expiration Date FBI Federal Bureau of Investigations FRD Functional Requirements Document FTP File Transfer Protocol FTP File Transfer Protocol HFS OpenFox HotFile System LEIN Law Enforcement Information Network M&S Addendum CPI Central Site Maintenance and Support Addendum MKE Message Key Transactions MRO Modify Extreme Risk Protection Order MTRO Modify Temporary Extreme Risk Protection Order NAM Name NCIC National Crime Information Center NIC NCIC Number

Term, Abbreviation or Acronym Definition NIST National Institute of Standards and Technology Nlets The International Justice and Public Safety Network OCA Originating Case Agency OPR Operator Name ORI Originating Agency Identifier PCL Program Control Log PCR Project Change Request PNO Protection Order Number PO Purchase Order or Billing Authority PROD OpenFox Production environment PRR Production Readiness Review QW Query Wanted RFC Request For Change RSX Race/Sex SOW Statement of Work SVC Service Information SVD Service Date SYSIDNO System Identification Number TEST OpenFox Test environment TOU Technical and Operational Update UAT User Acceptance Testing VPN Virtual Private Network XNRO Cancel Supplemental Extreme Risk Protection Order XRO Cancel Extreme Risk Protection Order XTRO Cancel Temporary Extreme Risk Protection Order

CPI Reviewers and Approvers The following are the required CPI Reviewer(s) and Approver(s) of this document:

Role/Department Reviewer Name Review Date Director, Sales and Marketing Marc Smith C/R 02/05/2024 Director, Project Management Lori Ambrose C/R 02/04/2024 Project Advisory Board Kevin Sawatzky, Steve Sawatzky, Paul Jones R/A 02/05/2024

TABLE OF CONTENTS

1 Introduction 8 2 Scope of Work 8

2.1 New Extreme Risk Protection Order HotFile 9

2.2 MKE Configuration 9

2.3 OpenFox HotFiles Logic and Processing Configuration 9

2.4 Message Switch Modifications 10

2.5 Validations File Transfer Process Modifications 10

2.6 Hardware Configuration 10

2.7 Testing Strategy 10

2.7.1 Integration Testing 10

2.7.2 User Acceptance Testing 10

2.8 Training and Documentation Services 11

2.9 Project Exclusions 11

3 Assumptions, Constraints, and Dependencies 11 4 Project Risks 12 5 Work Requirements 13

5.1 CPI Responsibilities 13

5.2 Customer Responsibilities 14

6 Deliverable and Milestone Schedule 15 7 Deliverable and Project Acceptance 16

7.1 Deliverable and UAT Acceptance Period 16

7.1.1 Non-Software Deliverable 16

7.1.2 Software Deliverable 17

7.2 Acceptance Criteria 17

7.3 Acceptance or Rejection 18

7.3.1 Acceptance 18

7.3.2 Rejection 18

8 Period of Performance 19

8.1 Project Start Date 19

8.2 Predecessor Projects 19

8.3 Estimated Time 19

9 Place of Performance 20 10 Security Policies 20

11 Other Requirements 20 12 Primary Contacts 21 13 Pricing and Maintenance 22

13.1 Pricing 22

13.1.1 Supplemental Services 22

13.2 Invoicing 22

13.3 Maintenance 22

13.4 Project Change Request Process 23

13.5 Not Work for Hire 23

14 Appendices 25

14.1 Appendix A: TOU 21-4 25

14.2 Appendix B: ERPO Scan Line Configurations 25

14.3 Appendix C: ERPO Business Rules 26

14.3.1 ERPO Service Status 26

14.3.2 ERPO Enter Transactions 27

14.3.3 ERPO Modify Transactions 27

14.3.4 ERPO Cancel Transactions 28

14.3.5 ERPO Enter Supplemental Transactions 29

14.3.6 ERPO Cancel Supplemental Transactions 30

14.3.7 Section 2.2.7 ERPO Record Retention 30

14.3.8 Control Terminal Rights 30

14.3.9 LEIN Response Example Format 31

[REMAINDER OF THIS PAGE INTENTIONALLY LEFT BLANK]

Project Title:

NCIC ERPO Implementation

CPI Project ID/Quote #:

MI-2024-001

Agency:

Michigan State Police

Date:

06/25/2024

Requested By:

Kevin Collins

Phone:

(517) 284-3046

Prepared By:

Travis Stanta Maria

Phone:

(630) 754-8820 x154

1 INTRODUCTION

This Statement of Work (“SOW”) outlines the Project scope and costs required for Computer Projects of Illinois, Inc. (“CPI”) to implement Technical and Operational Update (“TOU”) 21-4 for Extreme Risk Protection Order (“ERPO”) transactions for the Michigan State Police (“Customer”). Additionally, the Customer has requested a corresponding in-state OpenFox ERPO HotFile and custom Message Keys (“MKE”). Law Enforcement Information Network (“LEIN”) and “OpenFox” are used interchangeably throughout this document to refer to the licensed OpenFox® software.

The scope of work outlined in this SOW is based on business requirements and/or discovery information received from the Customer. The terms in this SOW supersede all previous estimates or verbal discussions related to the Project. If there are any desired deliverables or milestones not listed in this SOW, those requests will be managed via the Project Change Request (“PCR”) Process outlined in Section 13.4.

This SOW is attached to, and incorporated as part of the State of Michigan Department of Technology, Management, and Budget Contract Number 071B3200068 (the “Agreement”) between CPI and the Customer as amended through the Contract Change Notice Process.

2 SCOPE OF WORK

CPI will complete the following tasks to support the creation and use of the new ERPO hotfile.

● Create new OpenFox ERPO HotFile Database (“DB”) tables and logic procedures.

● Modify the OpenFox HotFiles query logic to return NCIC and in-state ERPO responses for Query Wanted (“QW”) transactions.

● Add a synchronous and asynchronous interface to simplify and streamline the ERPO transaction process.

● Configure a new station and file route for the ERPO transactions.

● Configure new MKE to process ERPO transactions.

● Configure logic in the OpenFox HotFiles for ERPO transaction processing to National

Crime Information Center (“NCIC”).

● Modify the monthly NCIC batch Validation file process to include the NCIC ERPO file.

2.1 New Extreme Risk Protection Order HotFile

CPI will create a new OpenFox HotFile to store and disseminate ERPO information. In-state ERPO records will follow the business rules and retention policies outlined in Section 14.3.7.

NCIC ERPO records will follow the business rules and retention policies outlined in the NCIC Technical and Operational Update (“TOU”) 21-4 found in Section 14.1.

2.2 MKE Configuration

CPI will configure MKEs to permit data transfer to the OpenFox HotFiles and NCIC. The below ERPO transactions will be configured:

● Enter Extreme Risk Protection Order (“ERO” & “OERO”)

● Enter Extreme Risk Protection Order - Caution (“EROC” & “OEROC”)

● Enter Temporary Extreme Risk Protection Order (“ETRO” & “OETRO”)

● Enter Temporary Extreme Risk Protection Order - Caution (“ETRC” & “OETRC”)

● Modify Extreme Risk Protection Order (“MRO” & “OMRO”)

● Modify Temporary Extreme Risk Protection Order (“MTRO” & “OMTRO”)

● Cancel Extreme Risk Protection Order (“XRO” & “OXRO”)

● Cancel Temporary Extreme Risk Protection Order (“XTRO” & “OXTRO”)

● Clear Extreme Risk Protection Order (“CRO” & “OCRO”)

● Clear Temporary Extreme Risk Protection Order (“CTRO” & “OCTRO”)

● Enter Supplemental Extreme Risk Protection Order (“ESUP” & “ENRO”)

● Cancel Supplemental Extreme Risk Protection Order (“CSUP” & “XNRO”)

The Customer’s scan line and business requirements for the keys listed above are outlined in Section 14.2 and Section 14.3, respectively.

2.3 OpenFox HotFiles Logic and Processing Configuration

For ERPO transactions, the OpenFox HotFiles will update the in-state record and create the corresponding NCIC transaction for submission through the OpenFox Message Switch.

If NCIC accepts the transaction and provides an NCIC Number / record identifier (“NIC”) back to the OpenFox HotFiles database, that NIC will be stored as part of the in-state record. A transaction will be created by the OpenFox HotFiles for submission back to the end user, including the NIC.

If NCIC rejects the message, the OpenFox HotFile database will receive a rejected message and remove the record. The OpenFox HotFile DB will then create the applicable rejection message for submission back to the end user through the OpenFox Message Switch.

CPI will modify the OpenFox HotFiles Query processing for “QW” and its sub-variants (“QWA” and “ZW”) to return matching records from the in-state OpenFox ERPO HotFile for queries made by NIC number or NAM/RAC/SEX/DOB.

2.4 Message Switch Modifications

CPI will modify Message Field Code (“MFC”) edit checks to support the new NIC Number formats for ERPO transactions. These edits will be configured to Modify, Clear, and Cancel transactions as outlined in Section 2.2.

2.5 Validations File Transfer Process Modifications

CPI will modify the Customer’s current batch Validations processing to include:

● Code changes to parse and load ERPO records from the NCIC Validations file.

● Modify the File Transfer Protocol (“FTP”) and Print file generation process to include

NCIC ERPO records.

2.6 Hardware Configuration

The existing hardware platform will remain unchanged and no additional third-party products are included.

2.7 Testing Strategy

2.7.1 Integration Testing

CPI will perform integration testing of its components and software.

2.7.2 User Acceptance Testing

The Customer is responsible for User Acceptance Testing (“UAT”). For each software deliverable tendered by CPI pursuant to this SOW, the Customer shall develop and execute a UAT Test Plan to ensure the system functions in accordance with this SOW, as amended through the PCR Process, and/or Functional Requirements Document (“FRD”) deliverable, if applicable. If the FRD and/or Customer's UAT Test Plan are agreed to in writing by all parties prior to CPI’s acceptance of this SOW, then copy(ies) are attached to this SOW as Exhibit(s) and will become part of the Agreement between the parties upon acceptance of the SOW. If no FRD and/or Customer UAT Test Plan is attached at the time of CPI’s acceptance, and the

Customer requests CPI’s review and approval of the Customer’s UAT Test Plan, then a written PCR is required to amend the SOW in accordance with the PCR Process outlined in Section

13.4. The Customer is responsible for timely testing and approving the final product prior to production implementation in accordance with Section 7.1 (“Deliverable and UAT Acceptance Period”).

2.8 Training and Documentation Services

CPI-provided training is not required or included.

2.9 Project Exclusions

The following are outside the scope of the Project and are not covered by this SOW:

● Processing for any transactions not listed in Section 2.2.

● Additional spawning on other message keys.

● Any consultation services related to the implementation of this Project.

● The “Q” transaction, as currently configured, spawns a “QW” transaction which will return an ERPO record if one exists. Therefore, no modification to the “Q” transaction is required for ERPO processing.

● CPI Engineering resource(s) attendance at regularly scheduled or periodic Project meetings, unless specifically provided for in the scope of work and at the sole discretion of the CPI Project Manager

● Any other changes, products, or services not explicitly included within this SOW

3 ASSUMPTIONS, CONSTRAINTS, AND DEPENDENCIES

This SOW is based upon the requirements and discovery information provided by the Customer to CPI and supported by written documentation. Changes in Project scope or assumptions after this SOW is approved and a Purchase Order (“PO”) is issued will be managed by the PCR Process outlined in Section 13.4. The following assumptions were made when preparing this

SOW:

● Background-cleared CPI resources will be brought in and out of the Project as needed, according to the Project staffing plan and at the direction of the resource managers.

● All CPI services will be performed during normal CPI business hours (8:30 am – 5:00 pm Central, Monday – Friday), unless otherwise agreed to in writing by all parties.

● All CPI services will be performed using standard CPI tools and methodologies, unless otherwise agreed to by all parties in writing.

● Discovery information received from the Customer is correct and complete.

● CPI configurations for this Project will be placed onto the OpenFox TEST server prior to the Customer beginning UAT.

● CPI and the Customer shall coordinate the testing effort of all configurations and timing of go-live.

● One (1) cutover to the PROD environment is in scope for the Project and included in

Pricing.

● The Customer does not require consulting services from CPI regarding NCIC standards, processing rules, and restrictions for the ERPO file.

● Any assistance required from CPI for documentation, alterations, or deviations will result in additional impact and be subject to a PCR.

● The Scope of Work (Section 2) and Pricing quote (Section 13.1) assumes that the

Customer will test any enhancements and maintenance work deployed to the Customer's TEST environment and will be implemented concurrently with this project.

4 PROJECT RISKS

The Customer acknowledges and understands that CPI has disclosed to the Customer that there are inherent risks relating to CPI’s performance of the Project and from the utilization of the deliverables as specified by the Customer and provided by CPI pursuant to this SOW. The impact of an identified risk event or condition that has already occurred or is occurring and negatively affects the Project (“realized risk”) will be managed by the PCR Process outlined in Section 13.4. Potential risks include, but are not limited to, the following:

● The work described in this SOW shall only function so long as the Customer maintains the right to use the CPI OpenFox Message Switch pursuant to a separate agreement to which this SOW shall be deemed attached.

● If the Customer or third-party resources are unavailable for coordinated testing and timely approval (see Section 7.1) of each of the deliverables, then CPI will issue a PCR to document the impact to the Project.

● If Customer’s Performance is delayed for more than thirty (30) calendar days and such delay is not caused solely by CPI, CPI shall have the right to issue a PCR to formally pause the Project and invoice the Customer for all work completed prorated to the point of the pause.

● Once the Project is paused, a subsequent PCR is required to resume the Project and document the impact of the delay. The price and schedule impact may be significant depending on what changes CPI, the Customer, and/or other third-party vendors implemented while the Project was paused, resulting in rework, retesting, and/or a complete re-implementation of the Project Scope.

● If it is determined during CPI or Customer testing that this Project impacts downstream systems not identified within this scope of work causing rework of deployed code, then a PCR is required to document the impact to the Project.

● If it is determined during CPI or Customer testing that processing rules not identified within this scope of work causes rework of deployed code, then a PCR is required to document the impact to the Project.

● If an attempted cutover rolls back due to factors outside of CPI’s control or as a result of inadequate Customer testing prior to go-live, then a PCR is required to document the impact to the Project.

● If CPI encounters a delay while using the Customer’s File Transfer Protocol (“FTP”) connection that is caused solely by the Customer and that results in CPI’s inability to meet the Project Timeline as approved under Section 6, then a PCR is required to document the impact to the project.

● If CPI encounters a delay due to the Customer’s CyberArk, network connections, or security limitations that is caused solely by the Customer and that results in CPI’s inability to meet the Project Timeline as approved under Section 6, then a PCR is required to document the impact to the project.

● Should the Customer request consultation from CPI regarding NCIC standards, processing rules, deviations, and/or restrictions, then a PCR is required to document the impact to the project.

● If delays are encountered due to the management of the Customer’s Request For Change (“RFC”) forms, then a PCR is required to document the impact to the project.

5 WORK REQUIREMENTS

5.1 CPI Responsibilities

CPI will perform the following tasks and responsibilities to complete the Project:

● Project Management:

○ Coordinate with the Customer including routine status meetings and information exchange

○ Maintain Program Control Log (“PCL”)

○ Present written and/or verbal status at periodic meeting(s)

● Planning:

○ Create Project Management Plan (“PMP”) including an integrated Deliverable and Milestone Schedule, Implementation (“Cutover”) Plan, and Support Transition Plan

○ Present high-level project plan(s) to the Customer for review and approval

○ Conduct a project kickoff meeting

● Discovery and Documentation:

○ Coordinate with the Customer to check and clarify CPI’s understanding of the

Customer-provided business requirements

○ Gather and document the functional requirements, which will be approved by both parties in writing if separate from this SOW

● Product Configuration and Integration Testing:

○ Complete each deliverable relating to the Scope of Work as outlined in Section 2

○ Test the components to ensure the system is working as designed

○ Resolve any configuration and coding issues identified during CPI’s integration testing

○ Present “Delivery Notification Document” to the Customer for the delivered services set forth in Section 6

○ Invoice the Customer for the amount specified on the “Delivery Notification

Document” (“Milestone Payment”)

● Validation and User Acceptance Testing:

○ Reasonably respond to Customer inquiries relating to the Customer’s UAT and cure any reported non-conformities in accordance with Section 7

○ Present “Notice of Completion - UAT” form to the Customer for its written acknowledgement of UAT completion in accordance with Section 7.3

● Implementation and Cutover:

○ Plan and schedule the implementation (“cutover”) to the PROD environment upon receipt of Customer’s signed “Notice of Completion - UAT” form

○ Implement the configurations described in Section 2 to the PROD environment according to the “Implementation (“Cutover”) Plan”

● Project Transition and Closure:

○ Provide the Customer with all documentation in accordance with the approved Support transition plan

○ Present final “Notice of Acceptance” form to the Customer for its acceptance in accordance with Section 7.3

○ Invoice the Customer for final milestone payment(s) as defined in Section 13.2

5.2 Customer Responsibilities

Any Project of this nature is a cooperative effort requiring CPI and the Customer to complete their respective interdependent obligations in accordance with the approved Project Plan and timeline. With that in mind, the Customer shall perform the following tasks and responsibilities in order to complete the Project:

● Project oversight to include a point of contact

● Provide CPI with timely access to all needed databases, interfaces, and the OpenFox

Message Switch resources via Virtual Private Network (“VPN”) or other external validation techniques as provided by the Customer, and as reasonably acceptable to CPI

● Communicate and coordinate with Nlets - the International Justice and Public Safety Network, the National Crime Information Center (“NCIC”), other Customer departments, third-party vendors, and/or end users, as necessary regarding each deliverable, and implementation of cutover to production

● Identify, coordinate, and implement any required changes to existing non-CPI Client

Software and/or user agency interface(s)

● Provide resources in a reasonably timely manner for discovery and testing as required for this Project

● Coordinate with CPI to check and clarify CPI’s understanding of the Customer-provided business requirements and to document the functional requirements which will be approved by both parties in writing if separate from this SOW

● Develop a UAT Plan and complete UAT testing upon delivery of each software deliverable to the Customer’s TEST environment, as outlined in Section 7.1.2

● Validate that incoming and/or outgoing file transfers are complete, correct, accepted, and free of any misnomer or error

● Complete and return the “Notice of Completion - UAT Form” to CPI in accordance with Section 7.3

● Complete and return the “Notice of Acceptance” form to CPI in accordance with Section 7.3

● Submission and management of the Customer’s internal RFC form and process.

● Present transactions in proper format, with proper content, for NCIC processing and routing rules.

6 DELIVERABLE AND MILESTONE SCHEDULE

The initial deliverables and milestones for the Project are identified in the table below. For the purposes of this section, “approved” means approved in writing by both CPI and Customer.

Actual deliverable and milestone dates will be mutually determined and approved by both parties in writing once the SOW is executed and the PO is received from the Customer.

Key Milestone Phases

Description of Product, Deliverable, or Service

Schedule Date

Project Initiation Complete

● Statement of Work approved

● Valid “Authorization to Bill” or Purchase

Order received from Customer

Within ninety (90) calendar days from the date of SOW delivery to the Customer

Project Prerequisites Complete

● See conditions specified in Section 8 Upon acceptance of the SOW

Project Planning Complete

● Project Plan approved

● Project Timeline approved

● Project Start Date confirmed

Within three (3) weeks after Project Prerequisites Complete

Discovery and Documentation Complete

● As specified herein Per approved Project Plan and timeline

Key Milestone Phases

Description of Product, Deliverable, or Service

Schedule Date

Product Configuration and Integration Testing Complete

● OpenFox Product configurations and modifications deployed to Customer’s TEST environment

● “Delivery Notification Document” sent to Customer

Per approved Project Plan and timeline

Validation and User Acceptance Testing Complete

● Cure(s) for Customer-reported non-conformities deployed to Customer’s TEST environment in accordance with Section 7.3

● “Notice of Completion - UAT” form delivered, signed, and returned to CPI in accordance with Section 7.3

Per approved Project Plan and timeline and in accordance with the Deliverable Acceptance Period specified in Section 7.1

Production Readiness Review (“PRR”) Complete

● Implementation (“Cutover”) Plan approved

● Customer Change Advisory Board (“CAB”) approval received, if applicable

Within ten (10) business days after Validation and User Acceptance Testing Complete

Implementation and Cutover Complete1

● OpenFox Product configurations and modifications cutover to Customer’s PROD environment

● Cure(s) for Customer-reported non-conformities deployed to Customer’s TEST and PROD environments in accordance with Section 7.3

Implementation date(s) will be scheduled within ten (10) business days after Production Readiness Review Complete

Project Transition and Closure Complete

● “Notice of Acceptance” form delivered, signed, and returned to CPI in accordance with Section 7.3

● Project closeout activities completed

Within thirty (30) calendar days after Implementation and Cutover Complete

7 DELIVERABLE AND PROJECT ACCEPTANCE

7.1 Deliverable and UAT Acceptance Period

7.1.1 Non-Software Deliverable

For each non-software deliverable, the Customer shall have ten (10) business days following the date of delivery (“Deliverable Acceptance Period”) to review and accept the non-software deliverable in accordance with Section 7.3. If a delay or extension beyond the specified

1 Implementation and Cutover may be performed incrementally depending on the defined Project Scope and Project Deliverables.

Deliverable Acceptance Period is required, CPI and the Customer shall determine and mutually agree to a specified timeframe extension and document the impact through the PCR Process.

7.1.2 Software Deliverable

For each software deliverable, the Customer shall have thirty (30) calendar days following the date of delivery to the Customer’s TEST environment (“UAT Acceptance Period”) to perform UAT to validate the functionality in accordance with the Scope of Work; approved Specification document(s), if separate from this SOW; and established Acceptance Criteria in Section 7.2. If a delay or extension beyond the specified “UAT Acceptance Period" is required, CPI and the Customer shall determine and mutually agree to a specified timeframe extension and document the impact through the PCR Process.

For each software deliverable, the Customer shall have thirty (30) calendar days following the date of delivery to the Customer’s PROD environment (“Deliverable Acceptance Period”) to perform Acceptance testing to validate the functionality in accordance with the Scope of Work;

approved Specification document(s), if separate from this SOW; and established Acceptance Criteria in Section 7.2. If a delay or extension beyond the specified Deliverable Acceptance Period is required, CPI and the Customer shall determine and mutually agree to a specified timeframe extension and document the impact through the PCR Process.

7.2 Acceptance Criteria

The Acceptance Criteria for this Project is as follows:

● Successful processing for all transactions listed in Section 2.2 and Section 14 Appendices:

○ Enter

○ Modify

○ Enter Supplemental

○ Cancel Supplemental

○ Clear

○ Cancel

● Successful delivery of acceptance notifications

● Successful reject message notification

● Validate a “QW” transaction and its sub-variants (“QWA”, “ZW”) appropriately returns an

ERPO record if one exists

● Validate a “Q” transaction appropriately returns an ERPO record if one exists https://docs.google.com/document/d/1OvdlDF-W6s5ExTk8f1hQI9Z5CKGl5qUjdxZstgcU_e0/edit#heading%3Dh.uw520uhzt7yu

7.3 Acceptance or Rejection

7.3.1 Acceptance

For each software deliverable delivered to the Customer’s TEST environment that meets the Scope of Work, as amended through the PCR Process; approved Specification document(s), if separate from this SOW; and established Acceptance Criteria in Section 7.2, the Customer shall sign the CPI-provided “Notice of Completion - UAT” form and return the completed form to CPI prior to the end of the “UAT Acceptance Period”. If the Customer fails to sign and return the CPI-provided “Notice of Completion - UAT” form within the UAT Acceptance Period and fails to provide CPI a Rejection in accordance with Section 7.3.2 below, then CPI shall be deemed to have fulfilled its obligations under this SOW and the Customer shall be deemed to have accepted the deliverable.

For each non-software and software deliverable delivered to the Customer’s PROD environment that meets the Scope of Work, as amended through the PCR Process; approved Specification document(s), if separate from this SOW; and established Acceptance Criteria in Section 7.2, the Customer shall sign the CPI-provided “Notice of Acceptance” form and return the completed form to CPI prior to the end of the “Deliverable Acceptance Period”. If the Customer fails to sign and return the CPI-provided “Notice of Acceptance” form within the Deliverable Acceptance Period and fails to provide CPI a Rejection in accordance with Section 7.3.2 below, then CPI shall be deemed to have fulfilled its obligations under this SOW and the Customer shall be deemed to have accepted the deliverable.

7.3.2 Rejection

If the Customer believes that CPI failed to meet the Scope of Work, as amended through the PCR Process, or Acceptance Criteria set forth in Section 7.2, then the Customer shall provide to CPI a detailed description in writing that explains how the milestone or deliverable fails to meet the Scope of Work or approved Specification document(s), if separate from this SOW, and any other reason for rejection (a “Rejection”). In the event of a Rejection, CPI shall promptly take steps to remediate any non-conformities described in the Rejection within a reasonable time period (a “Cure”). Redelivery will occur as promptly as commercially possible and, in any case, within thirty (30) business days following receipt of the Customer’s Notice of Rejection.

Upon CPI’s delivery of a Cure during the “UAT Acceptance Period”, the Customer shall have ten

(10) business days thereafter, or the remainder of the “UAT Acceptance Period”, whichever is greater, to accept the Cure via the CPI-provided “Notice of Completion - UAT” form or reject the Cure as described above. A Cure procedure shall be repeated until the deliverable is accepted.

Upon CPI’s delivery of a Cure during the “Deliverable Acceptance Period”, the Customer shall have ten (10) business days thereafter, or the remainder of the “Deliverable Acceptance Period”, whichever is greater, to accept the Cure via the CPI-provided “Notice of Acceptance” form or reject the Cure as described above. A Cure procedure shall be repeated until the deliverable is accepted.

8 PERIOD OF PERFORMANCE

8.1 Project Start Date

CPI and the Customer shall determine the Project Start Date when all of the following conditions are met:

1) this SOW is agreed to and accepted by all parties;

2) appropriate billing authority, such as a PO, is received from the Customer;

3) all required Project prerequisites and predecessor projects are completed including, but not limited to, those listed in Section 8.2;

4) security clearances for CPI personnel are received, if applicable;

5) CPI resources have the necessary VPN and CyberArk access, if applicable; and

6) CPI and Customer resources are assigned and ready to start the work.

8.2 Predecessor Projects

The Scope of Work (Section 2) and Pricing quote (Section 13.1) assumes the following projects, enhancements, and maintenance work will be completed and implemented in PROD prior to determining the Project Start Date:

● None identified as of the date of “CPI Signature of Acceptance” on page 2

If the Customer has not approved CPI to migrate enhancements and/or maintenance work on TEST to the PROD environment prior to the Project Start Date, then CPI and the Customer through written agreement, may implement the enhancement and/or maintenance work concurrently with this Project.

8.3 Estimated Time

CPI estimates three (3) months from the confirmed Project Start Date until completion of Configuration and Testing Complete (“Estimated Time”), although, the Estimated Time may be affected by the results of the Discovery and Documentation process or other factors outside the control of CPI. A date for completion of Implementation and Cutover Complete will be determined when UAT is accepted per Section 7.3 above.

9 PLACE OF PERFORMANCE

CPI will perform all services remotely from the CPI facility in Bolingbrook, Illinois.

10 SECURITY POLICIES

CPI has developed a system of trust services criteria designed to govern the operations and development of its software, services, facility, and organization. These trust services criteria are evaluated on an annual basis by the American Institute of Certified Public Accountants (“AICPA”) accredited auditors in a SOC 2 examination.

CPI’s business operations are compliant with the National Institute of Standards and Technology NIST 800 as expressed through the current version of the Federal Bureau of Investigations (“FBI”) Criminal Justice Information Services (”CJIS”) Security Policy and the Nlets Security Policy (collectively “Security Policies”). Modifications of previously deployed software to meet the changing requirements of the Security Policies can be performed, but only under a PCR as outlined in Section 13.4 or as a separate project. Any security requirement that materially differs from the Security Policies, such as the State, Federal Government, or any other third-party (e.g.

CJIS or DTMB) changing their security requirements, are not required to be complied with (“Additional Security Policy(ies)”). If Additional Security Policy(ies) are specifically requested in writing by the Customer, such requests must be directly and specifically presented by the Customer to CPI as a PCR, so the work required to comply therewith can be accurately scoped and priced by CPI as a contract deliverable; and the Customer agrees in writing to such additional project as a separate Change Notice under the Agreement. Nothing in this SOW shall be construed to modify CPI’s obligations to maintain its operations compliant with the Security Policies that were in effect at the time the original Agreement was entered into.

11 OTHER REQUIREMENTS

No additional requirements have been identified.

12 PRIMARY CONTACTS

The following personnel shall provide management oversight for the Project and serve as the primary points of contact for day-to-day communication for their respective organizations:

Michigan State Police

Kevin Collins Criminal Justice Information Center Michigan State Police PO Box 30634 Lansing, MI 48909 Phone: (517) 284-3046 Email: CollinsK@michigan.gov

Computer Projects of Illinois, Inc.

Travis Santa Maria Project Manager 400 Quadrangle Drive, Suite F Bolingbrook, IL 60440 Phone: (630) 754-8820 x154 Email: tsantamaria@openfox.com mailto:CollinsK@michigan.gov mailto:tsantamaria@openfox.com

13 PRICING AND MAINTENANCE

13.1 Pricing

The table below presents the pricing associated with the tasks for this SOW. This Project is quoted as a Fixed Price and includes all products and services as defined within the scope of this SOW. Any deviation from the Project scope or changes to approved deliverables will be subject to the PCR Process outlined in Section 13.4. Changes or amendment(s) to this SOW may impact the Project cost and/or schedule.

The work associated with this SOW is assigned CPI Quote number: MI-2024-001.

Pricing is valid for ninety (90) days from the date of CPI Signature of Acceptance on page 2.

13.1.1 Supplemental Services

Key Milestone

CPI Part Number/ Description

Percentage of Total

Price

CPI-MSG-MISC

Product Configuration and Integration Testing Complete

80%

$129,360.00

2 CPI-MISC-SRVS

Project Transition and Closure Complete 20% $32,340.00

Total Price 100% $161,700.00

13.2 Invoicing

For each Key Milestone listed in the Pricing table above, CPI will invoice the Customer the corresponding line item amount upon completion of the phase specified in Section 6 and delivery of the deliverable(s) in accordance with Section 7 of this SOW.

13.3 Maintenance

Additional annual maintenance charges in the amount of $12,012.50 USD for the above quoted products and services will be added to Cost Table 1 of Schedule D of the Agreement on 01/01/2025 (the “renewal date”) and is subject to a five percent (5%) escalation annually.

13.4 Project Change Request Process

Changes to the Project Scope of Work or CPI’s obligations shall be made only through a written PCR signed by both parties through the Customer’s Contract Change Notice process. CPI shall have no obligation to commence work in connection with any change until the fee and/or schedule impact of the change and all other applicable terms are agreed upon by both parties in writing. The following is the process to follow if changes to the Scope of Work or a previously accepted deliverable are required.

● A PCR will be the document for communicating agreed upon change. The PCR must describe in detail the change, the reason for the change, and the effect the change will have on the Project or Services.

● Both CPI’s Project Manager and the Customer’s designated Project Lead will review the PCR for submission to CPI’s management team. CPI will specify if there will be any charges to be incorporated into the PCR. CPI shall determine the effect that the implementation of the PCR will have on price, schedule, and other terms and conditions of this SOW.

● A written PCR, as approved by CPI’s management team, must be signed and agreed upon by both parties through the Customer’s Contract Change Notice process to authorize the implementation of the change.

13.5 Not Work for Hire

No Work Product is to be provided to the Customer in connection with CPI’s obligations under this SOW. CPI shall own all worldwide right, title and interest in and to the work done under this SOW, including all worldwide patent rights (including patent applications and disclosures);

copyright rights (including copyrights, copyright registrations and copy rights with respect to computer software, software design, software code, software architecture, firmware, programming tools, graphic user interfaces, reports, dashboard, business rules, use cases, screens, alerts, notifications, drawings, specifications and databases); moral rights; trade secrets and other rights with respect to confidential or proprietary information; know-how; other rights with respect to inventions, discoveries, ideas, improvements, techniques, formulae, algorithms, processes, schematics, testing procedures, technical information and other technology; and any other intellectual and industrial property rights, whether or not subject to registration or protection; and all rights under any license or other arrangement with respect to the foregoing. CPI does not grant Customer any intellectual property rights in the Licensed Software, and all right, title and interest in and to all copies of the Licensed Software not expressly granted in this SOW remain with CPI. The Licensed Software is copyrighted and protected by the law of the United States. The Customer may not remove or obscure any copyright, trademark, and/or any other intellectual property or proprietary notices from the work product created for this SOW. If this SOW is amended, then CPI shall specify what Work Product, if any, will be provided (“CPI’s Specification”). Absent CPI’s Specification, no Work Product shall be provided in connection with any SOW as amended.

14 APPENDICES

14.1 Appendix A: TOU 21-4

TOU 21-4 for the NCIC ERPO file defines the NCIC business rule and retention policies. The OpenFox Message Switch and OpenFox HotFiles will enforce these business rules unless otherwise noted in Appendix B and Appendix C below.

14.2 Appendix B: ERPO Scan Line Configurations

LINE LEIN

LABEL

NCIC

LABEL FIELD NAME REQUIREMENTS FORMAT

1: NAM: NAM Subject's Name Mandatory LAST/FIRST/MIDDLE/SUFFIX 2: RSX: RAC/SEX Race and Sex Mandatory CODE CODE 3: HGT: HGT Height Optional FEET INCHES 4: WGT: WGT Weight Optional POUNDS 5: HAI: HAI Hair Color Optional ALPHA CODE 6: EYE: EYE Eye Color Optional ALPHA CODE 7: DOB: DOB Date of Birth Mandatory CC YY MM DD or AGE 8: STR: N/A Street Optional STREET ADDRESS 9: CTY: N/A City Optional NAME 10: STA: N/A State Optional ALPHA CODE

11: OLN: SET: OLN,

OLS, OLY

Driver License Number Conditional Set NUMBER or STATE

CODE/NUMBER

12: SOC: SOC Social Security Number Optional NUMBER

13:

PLT:

SET: LIC,

LIS, LIY,

LIT

License Plate Number

Conditional Set

NUMBER

15: OCA: OCA Complaint/Case Number Mandatory NUMBER (May include hyphens)

16: DOW: ISD Date of Warrant Mandatory CCYYMMDD

18: FPC: FPC Fingerprint Code Optional THIS CODE IS NOT CURRENTLY

IN USE

19: AKA: AKA Alias Name Optional LAST / FIRST / MIDDLE / SUFFIX

20: PNO: N/A Person Entry Number Optional LEIN ASSIGNED RECORD

IDENTIFIER

22: PKU: N/A Pickup Radius Optional NUMBER CODE 28: LIT: LIT License Plate Type Set ALPHA CODE

31: LIC: LIY License Plate Information Set MMCCYY/STATE CODE/NUMBER

32: VIN: VIN Vehicle Identification Number Conditional Set NUMBER

33: VMA: VMA Year/Make/Model Set CCYY/MAKE CODE/MODEL

CODE

34: VST: VST Vehicle Body Style Set ALPHA CODE

35: VCO: VCO Vehicle Color Set COLOR CODE or TOP/BOTTOM

COLOR CODE

39: FBI: FBI FBI Number Optional ALPHANUMERIC

40: MNU: MNU Miscellaneous Number Optional CODE - NUMBER

41: MIS: MIS Remarks Field Optional FREE TEXT 42: BDC: Broadcast Entry Optional AREA, STATION or ORI

43: CND: Show Canceled Records Optional YES

44: CAU: CMC Caution Indicator Optional ALPHA CODE 48: ZIP: N/A ZIP Code Optional NNNNN or NNNNN-NNNN

50: SID: SID State Identification Number Optional ALPHANUMERIC

51: PRN: N/A Prison Number Optional ALPHANUMERIC 53: CRT: CTI Court ORI Mandatory COURT ORI 54: DKT: N/A Court Case Number Optional ALPHANUMERIC 55: OPR: N/A Operator's Name Mandatory NAME or UNIQUE IDENTIFIER 56: FOR: N/A Requestor Mandatory NAME/AGENCY 58: POB: POB Place of Birth Optional STATE/COUNTRY CODE 59: SKN: SKN Skin Tone Optional ALPHA CODE 60: SMT: SMT Scars/Marks/Tattoos Optional NUMBER CODE 80: LAW: ORI Law Enforcement ORI Mandatory 9-CHARACTER ORI 99: DOX: EXP Date of Expiration Mandatory CC YY MM DD 247: CIZ: CTZ Citizenship Flag Optional ALPHABETIC 2 DIGIT CODE

260: ETN: ETN Ethnicity Optional 1 CHARACTER MUST MATCH

NCIC CODE

273: SVC: SVC Service Information Optional NUMERIC FIELD 1 CHARACTER 274: SVD: SVD Service Date Optional CCYYMMDD 295: EIE: N/A Entered in Error Optional Y

302: SUR: N/A Immediate Surrender Caveat Optional Y

14.3 Appendix C: ERPO Business Rules

14.3.1 ERPO Service Status

Scan line 273 Service Information (“SVC”) is required when entering ERPO records. Scan line 273 must contain either a Yes (“Y”) or No (“N”) to indicate proof of service. Scan line 273 can only be modified by the entering agency.