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

MDARD MAEAP Verification System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

January 14, 2020 January 15, 2025 5 Months January 15, 2026

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

28081 Southfield Road

Lathrup Village MI 48076-2816

Justin Shaulis

517-803-3217 j.shaulis@kunzleigh.com

CV0036059

KUNZ LEIGH & ASSOCIATES INC

C O

N

TR

A C

TO

R

Sarah Platte

517-219-2406

DTMB

Various Various plattes3@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 7

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

1 Year January 15, 2027

$2,656,960.79 $0.00 $2,656,960.79

DESCRIPTION

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

The Program Manager for MDARD has been updated from Joseph Kelpinski to Megan DeLeeuw.

Effective 01/07/2026, the State exercises 1, 12-month option year. The new Contract expiration date is 01/15/2027.

All other terms, conditions, specifications, and pricing remain the same. Per Contractor and Agency agreement, and DTMB Procurement.

AGENCY NAME PHONE EMAIL

DTMB Laura Brancheau 517-3351334 BrancheauL@michigan.gov

MDARD Megan DeLeeuw 517-898-9761 DeLeeuwM1@michigan.gov

Program Managers for

Multi-Agency and Statewide Contracts

CHANGE NOTICE NO. 7 TO CONTRACT NO. MA200000000304

STATE OF MICHIGAN

ENTERPRISE PROCUREMENT

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

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

CONTRACT SUMMARY

MDARD MAEAP Verification System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

January 14, 2020 January 15, 2025 5 - 12 Months January 15, 2025

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

28081 Southfield Road

Lathrup Village MI 48076-2816

Justin Shaulis

517-803-3217 j.shaulis@kunzleigh.com

CV0036059

KUNZ LEIGH & ASSOCIATES INC

C O

N

TR

A C

TO

R

Sarah Platte

517-219-2406

DTMB

Various Various plattes3@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Change Notice Number 6

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

12 Months January 15, 2026

$2,656,960.79 $0.00 $2,656,960.79

DESCRIPTION

Effective 01//07/2025, the State exercises 1, 12-month option year. The new Contract expiration date is 01/15/2026.

All other terms, conditions, specifications, and pricing remain the same. Per Contractor and Agency agreement, DTMB Procurement, and State Administrative Board approval on 7/13/2021.

MDARD Joseph Kelpinski 586-206-2862 kelpinskij@michigan.gov

DTMB Laura Brancheau 517-335-1334 brancheaul@michigan.gov

Program Managers for

CHANGE NOTICE NO. 6 TO CONTRACT NO. MA200000000304

CENTRAL PROCUREMENT SERVICES

Department of Technology, Management, and Budget

320 S. WALNUT ST., LANSING, MICHIGAN 48933

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

Change Notice Number 5 to

Contract Number 200000000304

Various

Sarah Platte j.shaulis@kunzleigh.com

Justin Shaulis

Lathrup Village, MI 48076-2816

KUNZ LEIGH & ASSOCIATES INC

CV0036059

517-803-3217

28081 Southfield Road

517-219-2406 S

T A

T E

P ro g ra m

M a n a g e r

C o n tra ct

A d m in istra to r

C O

N T R A C T O

R

DTMB

plattes3@michigan.gov

$2,630,710.79

January 15, 2020 January 15, 2025

MDARD MAEAP VERIFICATION SYSTEM

January 15, 2025

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

5 - 1 Year

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

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

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

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

☐ ☐ January 15, 2025

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$0.00 $2,630,710.79

Effective 2/12/2024, the parties add the attached document to make an amendment to the definition and language surrounding "Background Technology" for the KL&A Core software accelerator.

All other terms, conditions, specifications, and pricing remain the same. Per Contractor and Agency agreement, DTMB Procurement, and State Administrative Board approval on 7/13/2021.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

CONTRACT SUMMARY

MDARD

Program Managers for

CHANGE NOTICE NO. 5 TO CONTRACT NO. 200000000304

Laura Brancheau 517-335-1334 brancheaul@michigan.govDTMB

Joseph Kelpinski 586-206-2862 kelpinskij@michigan.govMDARD

Error! Unknown document property name.49702803

Amendment to the IT Professional Services Contract Terms for Contract No. 171-200000000304

The definition of Background Technology will be replaced in its entirety with the following:

“Background Technology” means all software, data, know-how, ideas, methodologies, specifications, and other technology in which Contractor owns such Intellectual Property Rights as are necessary for Contractor to grant the rights and licenses set forth in Section 15.1, and for the State (including its licensees, successors and assigns) to exercise such rights and licenses, without violating any right of any Third Party or any law or incurring any payment obligation to any Third Party. Background Technology must be identified as Background

Technology in the Statement of Work.

Amendment to Schedule A, Statement of Work for Contract No. 171-200000000304

The following language will be added to Section 11, Software, in Schedule A, the Statement of Work:

Background Technology: KL&A Core software accelerator is hereby identified by Contractor as Background Technology as defined in the Contract Terms.

Department of Technology, Management, and Budget

320 S. WALNUT ST., LANSING, MICHIGAN 48933

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

Change Notice Number 3 to

Contract Number 200000000304

Various

Sarah Platte j.shaulis@kunzleigh.com

Justin Shaulis

Lathrup Village, MI 48076-2816

KUNZ LEIGH & ASSOCIATES INC

CV0036059

517-803-3217

28081 Southfield Road

517-219-2406 S

T A

T E

P ro g n a g e r

C o n tra c t

A d m in is tra to r

C O

N T

R A

C T

O R

DTMB

plattes3@michigan.gov

$2,614,615.79

January 15, 2020 January 15, 2025

MDARD MAEAP VERIFICATION SYSTEM

January 15, 2025

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

5 - 1 Year

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

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

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

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

☐ ☐ January 15, 2025

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$16,095.00 $2,630,710.79

Effective 6/15/2023, the parties add the attached Statement of Work for the purpose of eventually adding enhancements to the MAEAP Verification System. This will allow user groups to provide feedback and analyze their priorities and determine the scope, schedule, and cost required to implement additional functionality in the production system. The State also adds $16,095.00 in funding to support this work.

All other terms, conditions, specifications, and pricing remain the same. Per contractor and agency agreement, DTMB Procurement, and State Administrative Board approval on July 13th, 2021.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

Program Managers for

CHANGE NOTICE NO. 3 TO CONTRACT NO. 200000000304

MICHIGAN DEPARTMENT OF TECHNOLOGY,

MANAGEMENT AND BUDGET

IT SERVICES

STATEMENT OF WORK FOR IT CHANGE NOTICES

Project Title:

MAEAP Verification System

Period of Coverage:

05/01/2023 – 09/30/2023

Requesting Department:

MDARD

Date:

03/21/2023

Agency Project Manager:

Joe Kelpinski

Phone:

586-206-2862

DTMB Project Manager:

Jill Cullen

Phone:

248-212-8274

PROJECT OBJECTIVE:

MDARD has identified a list of enhancement areas for the MAEAP Verification System based on feedback from user groups.

The purpose of this project is to analyze these priorities and determine the scope, schedule, and cost required to implement this functionality in the production system.

SCOPE OF WORK:

KL&A will facilitate JAD sessions with MAEAP Subject Matter Experts (SMEs) and key stakeholders. An estimate of 15 hours of JAD sessions is needed to appropriately perform the analysis. KL&A can schedule two, three or four-hour sessions based on the availability of resources each week.

During these collaborative sessions, MAEAP’s business needs and operational processes will be reviewed by KL&A Business Analysts (BAs) in accordance with the identified enhancements priorities. KL&A will then process the gathered information and develop the requirements necessary to achieve MAEAP’s objectives.

JADs will cover items on the list of enhancement areas provided by MAEAP in order of priority. The potential JAD time required for each area will vary based on the complexity of the topic. A summary of the key topics is shown below organized by anticipated complexity. This list may also expand as additional functionality and processes are uncovered.

High Complexity

• Conservation practice management, data collection, and reporting

• Action plan management and workflow optimization Moderate Complexity

• New farm/producer level reports to cover status progression and inventory over time

• Onboarding workflow for new users

• Improving the “close” workflow on assessment-to-verification workflow activities

• Enhancements to letter and certificate templates

• Workflow to manage Phase 1 data entry

• Review data gaps resulting from the migration Low Complexity

• Login session timeout warning

• Adjusting Verifier edit permissions for location information on verified farms

• Bulk reassignment of tasks

• Filtering assessments based on selected system

• Recording proactive right to farm records on verification requests

• Filtering search pages based on the signed in user

• Action plan template adjustments

• User manual and/or training improvements

• Enhancing information provided in system notifications

• Adding “Sign Form” step to the verification workflow

DELIVERABLES:

At the completion of all needed JAD sessions, KL&A will develop a requirements document, along with estimated cost and schedule to implement the requirements and meet the MAEAP program’s business needs.

ACCEPTANCE CRITERIA:

MDARD and DTMB Project Managers will approve all completed deliverables.

PROJECT CONTROL AND REPORTS:

A weekly status meeting will be held throughout the duration of this engagement. MDARD, DTMB, and KL&A Project Managers will meet and discuss any issues that need escalation or final decisions to be made.

SPECIFIC DEPARTMENT STANDARDS:

Agency standards, if any, in addition to DTMB standards.

PAYMENT SCHEDULE:

Payment will be made on a satisfactory acceptance of each Milestone basis. DTMB will pay CONTRACTOR upon receipt of properly completed invoice(s) which shall be submitted to the billing address on the State issued purchase order not more often than monthly. DTMB Accounts Payable area will coordinate obtaining Agency and DTMB Project Manager approvals.

All invoices should reflect actual work completed by payment date, and must be approved by the Agency and DTMB Project Manager prior to payment. The invoices shall describe and document to the State’s satisfaction a description of the work performed, the progress of the project, and fees. When expenses are invoiced, receipts will need to be provided along with a detailed breakdown of each type of expense.

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

EXPENSES:

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

PROJECT CONTACTS:

The designated Agency Project Manager is:

Joe Kelpinski Departmental Manager

MDARD

Atrium, Conn Hall 525 W. Allegan St.

Lansing, MI 48933 586-206-2862 kelpinskij@michigan.gov

The designated DTMB EPMO Project Manager is:

Jill Cullen Project Manager

DTMB

Atrium, Conn Hall 525 W. Allegan St.

Lansing, MI 48933 248-212-8274 cullenj@michigan.gov

The designated DTMB Technical Owner is:

Dane Sjoquist Agency Services SAM

DTMB

Atrium, Conn Hall 525 W. Allegan St.

Lansing, MI 48933 517-242-9765 SjoquistD@michigan.gov

AGENCY RESPONSIBILITIES:

MDARD Project Manager and Subject Matter Experts (SMEs) will be required to assist with the following project activities:

• Attend requirements JAD sessions

• Provide subject matter expertise as needed

• Complete action items as assigned

• Review and approve all requirements documentation

LOCATION OF WHERE THE WORK IS TO BE PERFORMED:

Consultants will work at a combination of State of Michigan offices, primarily Constitution Hall in Lansing, MI, KL&A offices in Okemos, MI and KL&A remote office locations throughout the US.

EXPECTED CONTRACTOR WORK HOURS AND CONDITIONS:

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

ESTIMATED PROJECT PLAN:

Once approved, MDARD and KL&A will collaboratively come up with a JAD session schedule. JADs will be two, three, or four hours long, and will occur weekly as schedules allow. Final SOW, schedule, and cost estimates will be developed following the conclusion of JAD sessions during a 10 business day documentation period.

mailto:kelpinskij@michigan.gov mailto:cullenj@michigan.gov mailto:SjoquistD@michigan.gov

COST AND PAYMENT SCHEDULE:

Requirements Gathering and Fit-Gap Analysis Cost

6 hours of JAD sessions (high complexity) $6,438.00

5 hours of JAD sessions (moderate complexity) $5,365.00

4 hours of JAD sessions (low complexity) $4,292.00

Total $16,095.00

A payment schedule will be defined by the JAD schedule. KL&A will invoice DTMB/MDARD on a monthly basis for all sessions completed in the prior month. In the event MDARD requires fewer than 15 hours of JAD sessions, the price would be adjusted down by $1,073.00 for every 1 hour of JAD sessions not needed.

OPTIONAL JAD SESSIONS:

Should the 15 hour estimate not allow for the full disclosure of desired MDARD functionality, additional JAD sessions can be added to the engagement. All additional JAD sessions will first be approved by MDARD and DTMB project managers prior to being scheduled. These additional sessions will push out the requirements documentation deliverable and will be invoiced in the month following the JAD being conducted.

Additional JAD Sessions Cost

1 hour of Requirement JAD Sessions $1,073.00

PAYMENT CREDIT:

KL&A will issue a credit up to the full amount invoiced from this Statement of Work upon execution of a Delivery Order authorizing KL&A to implement the requirements, cost, and schedule produced by this project. The credit will be applied evenly across the first four months of the project payment schedule.

Department of Technology, Management, and Budget

525 W. ALLEGAN ST., LANSING, MICHIGAN 48913

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

Change Notice Number 2 to

200000000304Contract Number

Various

Jarrod Barron j.shaulis@kunzleigh.com

Justin Shaulis

Lathrup Village, MI 48076-2816

KUNZ LEIGH & ASSOCIATES INC

CV0036059

517-803-3217

28081 Southfield Road

(517) 249-0406 S

T A

T E

P ro g n a g e r

C o n tra ct

A d m in istra to r

C O

N T R A C T O

R

DTMB

barronj1@michigan.gov

$1,869,920.00

January 15, 2020 January 15, 2025

MDARD MAEAP VERIFICATION SYSTEM

January 15, 2025

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

5 - 1 Year

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

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

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

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

☐ ☐ January 15, 2025

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$744,695.79 $2,614,615.79

Effective 7/13/2021, the parties add $744,695.79 for the MAEAP Verification System enhancements detailed in the attached statement of work. All other terms, conditions, specification and pricing remain the same. Per Contractor, Agency, DTMB Procurement and State Administrative Board approval on 7/13/2021.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

Program Managers for

CHANGE NOTICE NO. 2 TO CONTRACT NO. 200000000304

MICHIGAN DEPARTMENT OF TECHNOLOGY,

MANAGEMENT AND BUDGET

IT SERVICES

STATEMENT OF WORK FOR IT CHANGE NOTICES

Project Title:

MAEAP Verification System - Enhancements

Period of Coverage:

Requesting Department:

Date:

04/30/2021

Agency Project Manager:

Jason Lantz

Phone:

517-917-0374

DTMB Project Manager:

David Tripp

Phone:

810-339-1105

Brief Description of Services to be provided:

PROJECT OBJECTIVE:

The purpose of this project is to enhance the current MAEAP Verification System to address additional requirements identified during the initial implementation.

SCOPE OF WORK:

KL&A is adding functionality to current MAEAP Verification System to address key gaps and improvements identified during development of the initial launch of the system. Please see Appendix A for the specific set of requirements being incorporated.

TASKS:

Technical support is required to assist with the following tasks:

DELIVERABLES:

Deliverables will not be considered complete until the Agency Project Manager has formally accepted them.

Deliverables for this project include:

• Sprints 1-12

• Release UAT Completion

• Updated Training Materials

• Release to Production/Go-Live

All SUITE documentation will be updated to include appropriate references and information pertaining to the MAEAP Verification System enhancements. These documents will include:

• PMM-0101 Project Charter

• PMM-0102 Project Management Plan

• SEM-0301 Maintenance Plan

• SEM-0302 Software Configuration Management Plan

• SEM-0401 Requirements Traceability Matrix

• SEM-0402 Requirements Specifications

• SEM-0501 Functional Design Document

• SEM-0603 Detailed Test Plan

• SEM-0604 System Design Document

• SEM-0606 Test Case Document

• SEM-0701 Transition Plan

• SEM-0702 Installation Plan

• SEM-0703 Training Plan

ACCEPTANCE CRITERIA:

DTMB and MDARD Project Managers will approve all completed deliverables.

PROJECT CONTROL AND REPORTS:

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

1. Hours: Indicate the number of hours expended during the past two weeks, and the cumulative total to date for the project. Also state whether the remaining hours are sufficient to complete the project.

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

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

SPECIFIC DEPARTMENT STANDARDS:

Agency standards, if any, in addition to DTMB standards.

PAYMENT SCHEDULE:

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

When expenses are invoiced, receipts will need to be provided along with a detailed breakdown of each type of expense. Payment shall be considered timely if made by DTMB within forty-five (45) days after receipt of properly completed invoices.

EXPENSES:

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

PROJECT CONTACTS:

The designated Agency Project Manager is:

Joe Kelpinkski MAEAP Manager

MDARD

Atrium, Conn Hall 525 W. Allegan St.

Lansing, MI 48933 KelpinskiJ@michigan.gov

The designated DTMB Project Manager is:

Dane Sjoquist DTMB Agency Services Manager

DTMB

Atrium, Conn Hall 525 W. Allegan St.

Lansing, MI 48933 517-284-9773 SjoquistD@michigan.gov

AGENCY RESPONSIBILITIES:

MDARD Product Owner, Project Manager, and Subject Matter Experts (SMEs) will be required to assist with the following project activities:

• Attend discovery and JAD sessions

• Attend Sprint Planning and Demonstration events

• Participate in all Sprint and Release User Acceptance Testing

• Provide subject matter expertise as needed

• Review and approve deliverables and SUITE documentation

DTMB RESPONSIBILITIES:

DTMB will continue providing technical support and test coorindator responsibilities, including:

• Writing test cases, plans, and reports

• Executing test cases

• Supporting agency testers

• Standard BA and PM support

LOCATION OF WHERE THE WORK IS TO BE PERFORMED:

Consultants will work remotely, but as COVID protocols allow, may also work at combination of SOM offices, primarily Constitution Hall in Lansing, MI, and KL&A offices in Okemos, MI.

EXPECTED CONTRACTOR WORK HOURS AND CONDITIONS:

mailto:KelpinskiJ@michigan.gov mailto:SjoquistD@michigan.gov

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

PROJECT PLAN and PAYMENT SCHEDULE:

Event Start Finish Invoice Date Cost Sprint 1 06/18/21 07/01/21 07/01/21 $41,371.99 Sprint 2 07/02/21 07/16/21 08/01/21 $41,371.99 Sprint 3 07/19/21 07/30/21 08/01/21 $41,371.99 Sprint 4 08/02/21 08/13/21 09/01/21 $41,371.99 Sprint 5 08/16/21 08/27/21 09/01/21 $41,371.99 Sprint 6 08/30/21 09/13/21 10/01/21 $41,371.99 Sprint 7 09/14/21 09/27/21 10/01/21 $41,371.99 Release 2.0 UAT 10/04/21 10/25/21 - - Release 2.0 Go/No-Go 10/25/21 10/25/21 - - Release 2.0 Go-Live 11/09/21 11/09/21 12/01/21 $82,743.97 Sprint 8 09/28/21 10/11/21 11/01/21 $41,371.99 Sprint 9 10/12/21 10/25/21 11/01/21 $41,371.99 Release 2.1 UAT 10/26/21 11/16/21 - - Release 2.1 Go/No-Go 11/16/21 11/16/21 - - Release 2.1 Go-Live 12/02/21 12/02/21 01/01/22 $82,743.97 Sprint 10 10/26/21 11/08/21 12/01/21 $41,371.99 Sprint 11 11/09/21 11/23/21 12/01/21 $41,371.99 Sprint 12 11/24/21 12/09/21 01/01/22 $41,371.99 Release 2.2 UAT 12/10/21 01/04/22 - - Release 2.2 Go/No-Go 01/04/22 01/04/22 - - Release 2.2 Go-Live 01/19/22 01/19/21 02/01/22 $82,743.97 Warranty 01/20/22 04/19/22 - -

TOTAL $744,695.79

Appendix A

1. Overview

These requested changes are to add audit history, consolidated assessments, workflow, and verification detail enhancements to the base MAEAP Verification System platform.

The specifics of each enhancement are listed in section 2, along with the corresponding requirements captured and approved by MDARD staff. The column definitions for the new requirements are defined below.

New Requirements:

Column Description SOW ID The ID used within the initial requirements gathering sessions.

Title A short title that summarizes the requirement Requirement A short description of the necessary business, functional, or technical requirement Functional Area A list of the functional area(s) that the listed requirement maps to. Relates directly to the cost section of the Change Notice.

Work Type This column defines the level of effort required by KL&A to incorporate the requested functionality. The values are defined below:

• Configuration: This requires no to very light code changes, and is mostly configuration of back end modules

• Existing: This is existing functionality that can reused exactly as is, or with minimal configuration

• Extend Functionality: This is existing functionality that exists within the current system, but requires customization or configuration to handle requested functionality

• Migration: These are efforts related to data migration efforts from the legacy system(s)

• New Development: This is new functionality that does not exist within the current system

• Training: These refer to the training efforts for this implementation

Implementation Comments Any additional comments or text about the implementation of this requirement

2. New Enhancements

SOW

ID

Requirement Title Requirement Description Functional Area Work Type Implementation Comments

1 Create user friendly, readable, action history logs

The system must include action history logs in a friendly, readable format for each of the following areas:

1. Farms

2. Activities

3. Contacts

4. Toolbar objects (notes, tasks, files, etc.)

5. Producer Education

6. Technician Training

7. Reporting Management

8. Assessment Management

9. Farm Inventory Management

Audit History New Development

Requirement Title Requirement Description Functional Area Work Type Implementation Comments

10. Conservation District Management

11. Saved Search Management

12. Lookup Type/Code Management

13. Sign Management

14. Template Management

15. User Profile

16. Security

Action logs will be tied to events in the system that trigger a change related to each respective area. For example, farm create, edit, delete, and status changes will all generate action history logs.

2 Display action history feed

The system must display an action history feed on objects of the system that contain action history logs so that an admin or approved user may view the most recent action history logs.

3 Add hyperlinks to action history logs for easy navigation

The system must include hyperlinks in action history logs that will navigate the user to relevant system objects included in the log.

For example, a farm action history log must include the name of the farm that the action was generated on as a hyperlink. If the user clicks the hyperlink, it will navigate the user to that farm.

4 Link action logs with relevant audit history records

The system must include a link between action history logs and the relevant audit history records.

For example, a user viewing an action history log must be able to click a link or button to view the related audit history records.

5 Create action history search page

The system must include an action history search page with which a user may search all action history logs in the system by the following criteria:

1. Time range the log was generated

2. The user that created the log

3. The type of the log

6 Reduce audit history noise

The system must prevent unnecessary audit history records from being generated in the following cases:

1. Audit records where no changes occurred

2. Audit records related to write only database tables

3. Audit records related to system operations that have no relevance to MAEAP data management (i.e. user preferences)

Audit History Extend Functionality

7 Add audit history view on farms, contacts, and education

The system must include an audit history view for farms, contacts, and education that allows the user to view a list of audit history records that apply only to that entity.

8 Audit history search The system must include audit history search features on the following criteria:

1. User who created the record

2. Date/Time range records were created

3. The entity the record is related to (ie. farm, contact)

Requirement Title Requirement Description Functional Area Work Type Implementation Comments

4. The database table

5. The type of record (i.e. create, update, delete)

9 Display audit history as timeline feed

The system must display the audit history records as a timeline feed that allows the user to consume a series of related changes over time.

10 Support multiple verification requirements on a single risk question

The system must support multiple system verification requirements on risk questions.

Consolidated Assessments

New

11 Display multiple system verification requirements on a single risk question

The system must display multiple system verification requirements on risk questions wherever a risk question can be viewed. This includes:

1. Risk question management

2. Assessment management

3. Farm assessment activity

Consolidated Assessments

12 Manage risk questions within sections detail

The system must allow assessment sections to be managed independently, including the maintenance of included risk questions, sub-sections and their display order.

Consolidated Assessments

13 Support multiple systems in a single action plan

The system must include activity action plans that support the creation and maintenance of multi-system action plans.

Consolidated Assessments

14 Move Farm Inventory Management to the Farm Details

The system must include a farm inventory management page on the farm details as a replacement for the farm inventory activity. On this page, Technicians must be able to maintain an ongoing set of farm inventory data.

Farm Inventory New

15 Update Farm Inventory Interface for Easy Management

The system must include an updated farm inventory management page with improved UI for maintaining farm inventory data.

For example, rather than having a large page that displays all crop inventory options, only the crops that the farm currently has should be displayed.

16 Display Farm Inventory Verified Values

The system must display a farm’s verified inventory on the farm inventory page so it is easy for a user to understand the context of verified inventory vs total inventory.

17 Record Snapshot of Farm Inventory Within Verification Details

The system must include a snapshot of the farm inventory data within the verification details. This will replace the “verified farm inventory” activity currently in use.

18 Create an End-to-End Assessment to Verification Workflow

The system must include a defined workflow that guides users through the verification process. This process must include:

1. Assessment

2. Action plan

3. Processing verification requests

4. Approving verification requests

5. Processing verification results

6. Processing verification artifacts (i.e. logo use, verification documentation)

Verification Workflow

Requirement Title Requirement Description Functional Area Work Type Implementation Comments

19 Create Workflow UI that Displays the Current Workflow Step and Conditions

The system must include workflow UI that makes it clearly apparent to the user what step the verification workflow is in and what the user must do to meet the conditions of the step before advancing to the next one.

Verification Workflow

20 Update Assessment and Verification Activities to Support End-to-End Workflow

The system must include updated activities to support the implemented end-to-end verification workflow. This includes:

1. Updated overview page cards (i.e. activity overview)

2. Consolidating multiple activities into a single activity where necessary.

Verification Workflow

21 Enhance Verification Details

The system must include a verification detail page that contains a snapshot in time of the fields contained within the System Information form for that verification.

Verification Details New

22 Verification Search Page The system must include a search page with which an admin can search for verification records across all farms on the following criteria:

1. Verification reference number

2. Farm

3. System

4. Greenhouse

5. Technician

6. Verifier

Verification Details New

23 Migrate Legacy Verification Details

Legacy verifications in the current system must be migrated to support the new verification detail format and function.

Verification Details Migration

3. Schedule

KL&A plans to follow the same overall approach as used on the initial MAEAP Verification System implementation: A Sprint Zero period followed by construction and testing sprints, with a final Release UAT period immediately preceding deployment to the SOM production environment.

3.1 Enhancements Timeline

The overall timeline for the MAEAP Verification System enhancements willl be approximately 6 months, followed by 90 days of warranty. Major milestones and task durations are as follows:

Construction: 12 sprints, 10-business days each Release UAT: 15 business days DTMB Release Prep: 10 business days MAEAP Verification System Enhancements Warranty: 90 calendar days

4. Warranty

Only functionality specific to the MAEAP Verification System enhancements developed, tested, and released as part of this change notice will be covered by a warranty period of 90 calendar days, post go-live pursuant to “Warranty Period” as defined in custom software development definitions within contract no. 200000000304. Additionally, there is no maintenance and support coverage under this change notice after the included 90 calendar day warranty expires.

Maintenance and support will be covered for the full MAEAP Verification System under a separate and distinct Statement of Work.

5. Cost

KL&A's expectation is that MDARD will leverage existing MAEAP functionality as-is wherever possible and this quote includes this expectation in our pricing model. Further customizations beyond existing functionality not called out in this statement of work will result in change orders if the scope is increased.

Functional Area Cost Audit History $165,487.94

Consolidated Assessments $82,743.97 Enhanced Assessment-To-Verification Workflows $248,231.97

Verification Detail $82,743.97 Unplanned Enhancements $165,487.94

TOTAL $744,695.79

Department of Technology, Management, and Budget

525 W. ALLEGAN ST., LANSING, MICHIGAN 48913

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

Change Notice Number 1 to

200000000304Contract Number

Various

Jarrod Barron j.shaulis@kunzleigh.com

Justin Shaulis

Lathrup Village, MI 48076-2816

KUNZ LEIGH & ASSOCIATES INC

CV0036059

517-803-3217

28081 Southfield Road

(517) 249-0406 S T A T E

P ro g n a g e r

C o n tra ct

A d m in istra to r

C O

N T R A C T O

R

MDARD

DTMB

barronj1@michigan.gov

$1,869,920.00

January 15, 2020 January 15, 2025

MDARD MAEAP VERIFICATION SYSTEM

January 15, 2025

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

5 - 1 Year

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

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

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

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

☐ ☐ January 15, 2025

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$0.00 $1,869,920.00

Effective 1/5/2021, the parties transfer the maintenance services scope from this contract to new Contract 171-210000000295 using a consolidated maintenance services delivery model for multiple systems. Contractor will continue to system implementation and enhancement services through this contract. All other terms, conditions, specification and pricing remain the same. Per Contractor, Agency, DTMB Procurement and State Administrative Board approval on 1/5/2021.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

Program Managers for

CHANGE NOTICE NO. 1 TO CONTRACT NO. 200000000304

DTMB Laura Brancheau 517-335-1334 brancheaul@michigan.gov

MDARD Joseph Kelpinski 586-206-2862 kelpinskij@michigan.gov

NOTICE OF CONTRACT

NOTICE OF CONTRACT NO. 171-200000000304 .

between

THE STATE OF MICHIGAN

and

C O

N T

R A

C T

O R

Kunz, Leigh & Associates

S T

A T

E

P ro g n a g e r

Laura Brancheau DTMB

28081 Southfield Road 517-335-1334

Lathrup Village, MI 48076-2816 BrancheauL@michigan.gov

Justin Shaulis

C o n tr a c t

A d m in is tr a to r Jarrod Barron DTMB

517-803-3217 517-249-0406 j.shaulis@kunzleigh.com BarronJ1@michigan.gov

CV0036059

DESCRIPTION: MDARD MAEAP Verification System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE

INITIAL AVAILABLE

OPTIONS

EXPIRATION DATE BEFORE

CHANGE(S) NOTED BELOW

01/15/2020 01/15/2025 5-1 year 01/15/2025

PAYMENT TERMS DELIVERY TIMEFRAME

Net 45 N/A

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

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

MINIMUM DELIVERY REQUIREMENTS

N/A

MISCELLANEOUS INFORMATION

New Contract established from RFP# 190000002289.

ESTIMATED CONTRACT VALUE AT TIME OF EXECUTION $1,869,920.00

STATE OF MICHIGAN PROCUREMENT

Department of Technology, Management & Budget 525 W. Allegan Street, Lansing, MI 48909

1/14/2020

CONTRACT TERMS

CUSTOM SOFTWARE DEVELOPMENT

This CUSTOM SOFTWARE DEVELOPMENT CONTRACT (this “Contract”) is agreed to between the State of Michigan (the “State”) and Kunz, Leigh & Associates (“Contractor”), a Michigan Corporation. This Contract is effective on January 15, 2020 (“Effective Date”), and unless earlier terminated, will expire on January 15, 2025 (the “Term”).

This Contract may be renewed for up to five (5) additional one (1) additional year period(s). Renewal must be by written agreement of the parties and will automatically extend the Term of this Contract.

The parties agree as follows:

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

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

“Acceptance Tests” means such tests as may be conducted in accordance with Section 10 and the

Statement of Work to determine whether any Software Deliverable meets the requirements of this

Contract and the Specifications and Documentation.

“Affiliate” means any entity which directly or indirectly controls, is controlled by or is under common control of Contractor. The term “control” means the possession of the power to direct or cause the direction of the management and the policies of an entity, whether through the ownership of a majority of the outstanding voting rights or by contract or otherwise.

“Aggregate Software” means the Software, as a whole, to be developed or otherwise provided under the Statement of Work. For avoidance of doubt, if the Statement of Work provides for a single Software

Deliverable, such Software Deliverable also constitutes Aggregate Software.

“Allegedly Infringing Materials” has the meaning set forth in Section Error! Reference source not found.

“API” means all Application Programming Interfaces and associated API Documentation provided by

Contractor, and as updated from time to time, to allow the Software to integrate with various State and

Third Party Software.

“Approved Open-Source Components” means Open-Source Components that the State has approved to be included in or used in connection with any Software developed or provided under this

Contract, and are specifically identified in the Statement of Work.

“Approved Third-Party Materials” means Third-Party Materials that the State has approved to be included in or for use in connection with any Software developed or provided under this Contract, and are specifically identified in the Statement of Work.

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

“Background Technology” means all Software, data, know-how, ideas, methodologies, specifications, and other technology in which Contractor owns such Intellectual Property Rights as are necessary for Contractor to grant the rights and licenses set forth in Section 15.1, and for the State

(including its licensees, successors and assigns) to exercise such rights and licenses, without violating any right of any Third Party or any Law or incurring any payment obligation to any Third Party.

Background Technology must: (a) be identified as Background Technology in the Statement of Work; and

(b) have been developed or otherwise acquired by Contractor prior to the date of the RFP.

“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 Owner” is the individual appointed by the end-user agency procuring the software to (a) act as such agency’s representative in all matters relating to the Contract, and (b) co-sign off on the

State’s notice of Acceptance for all Software Deliverables and Aggregate Software. The Business Owner will be identified in the Statement of Work.

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

Work.

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

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

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

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

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

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

“Contract Administrator” is the individual appointed by each party to (a) administer the terms of this

Contract, and (b) approve and execute any Change Notices under this Contract. Each party’s Contract

Administrator will be identified in the Statement of Work.

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

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

“Contractor Personnel” means all employees of Contractor or any Permitted Subcontractors involved in the performance of Services or providing Work Product under this Contract.

“Deliverables” means all Software Deliverables and all other documents, Work Product, 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 or defined as

Deliverables in the Statement of Work.

“Derivative Work” means any modification, addition, upgrade, update, or improvement of the

Software and any other work constituting a derivative work under the United States Copyright Act, 17

U.S.C. Section 101, et seq.

“Dispute Resolution Procedure” means the procedure for resolving disputes under this Contract as set forth in Section 27.

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

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

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

“Fees” has the meaning set forth in Section 12.1.

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

“Force Majeure” has the meaning set forth in Section 28.8.

“Harmful Code” means any: (a) virus, trojan horse, worm, backdoor or other software or hardware devices the effect of which is to permit unauthorized access to, or to disable, erase, or otherwise harm, any computer, systems or software; or (b) time bomb, drop dead device, or other software or hardware device designed to disable a computer program automatically with the passage of time or under the positive control of any Person, or otherwise prevent, restrict or impede the State's or any Authorized

User's use of such software.

“Implementation Plan” means the schedule included in the Statement of Work setting forth the sequence of events for the performance of Services under the Statement of Work, including the

Milestones and Milestone Dates.

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

Law in any jurisdiction throughout the world.

“Intended Users” means the users that are intended to use Software or particular features or functions of the Software, as described in the Specifications for such Software.

“Key Personnel” means any Contractor Personnel identified as key personnel in the Statement of

Work.

“Law” means any statute, law, ordinance, regulation, rule, code, order, constitution, treaty, common law, judgment, decree, other requirement or rule of law of any federal, state, local or foreign government or political subdivision thereof, or any arbitrator, court, or tribunal of competent jurisdiction.

“Loss or Losses” means all losses, 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 and Support Schedule” means the schedule attached as Schedule C, setting forth the Support Services, the Support Fees, and the parties’ additional rights and obligations with respect to such services.

“Milestone” means an event or task described in the Implementation Plan under the Statement of

Work that must be completed by the corresponding Milestone Date.

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

“Non-Conformity” or “Non-Conformities” means any failure of any: (a) Software or Documentation to conform to the requirements of this Contract (including the Statement of Work) or (b) Software to conform to the requirements of this Contract or the Specifications or Documentation.

“Object Code” means computer programs assembled or compiled in magnetic or electronic binary form on software media, which are readable and useable by machines, but not generally readable by humans without reverse assembly, reverse compiling, or reverse engineering.

“Open-Source Components” means any software component that is subject to any open-source copyright license contract, including any GNU General Public License or GNU Library or Lesser Public

License, or other license contract that substantially conforms to the Open Source Initiative’s definition of

“open source” or otherwise may require disclosure or licensing to any third party of any source code with which such software component is used or compiled.

“Open-Source License” has the meaning set forth in Section 3.3.

“Operating Environment” means, collectively, the State platform and environment on, in, or under which Software is intended to be installed and operate, as set forth in the Statement of Work, including such structural, functional and other features, conditions and components as hardware, operating software and system architecture and configuration.

“Permitted Subcontractor” has the meaning set forth in Section 5.4.

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

“Pricing” means any and all fees, rates and prices payable under this Contract, including pursuant to any Schedule or Exhibit hereto.

“Pricing Schedule” means the schedule attached as Schedule B, setting forth the fees, rates and prices payable under this Contract.

“Project Manager” is the individual appointed by each party to (a) monitor and coordinate the day-to-day activities of this Contract, and (b) in the case of the State, co-sign off on its notice of Acceptance for all Software Deliverables and Aggregate Software. Each party’s Project Manager will be identified in the

Statement of Work.

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

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

Contract.

“Service Level Agreement” means, if applicable, the service level agreement attached as Schedule

E to this Contract, setting forth Contractor’s obligations with respect to the hosting, management and operation of the Software.

“Services” means any of the services Contractor is required to or otherwise does provide under this

Contract, the Statement of Work, the Maintenance and Support Schedule (if applicable), or the Service

Level Agreement (if applicable).

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

“Software” means the computer program(s), including programming tools, scripts and routines, the

Contractor is required to or otherwise does develop or otherwise provide under this Contract, as described more fully in the Statement of Work, including all updates, upgrades, new versions, new releases, enhancements, improvements, and other modifications made or provided under the Support

Services. As context dictates, Software may refer to one or more Software Deliverables or Aggregate

Software.

“Software Deliverable” means any Software, together with its Documentation, required to be delivered as set forth in the Statement of Work.

“Source Code” means the human readable source code of the Software to which it relates, in the programming language in which such 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, operate, support, maintain and develop modifications, upgrades, updates, enhancements, improvements and new versions of, and to develop computer programs compatible with, such Software.

“Specifications” means, for any Software, the specifications collectively set forth in the Business

Requirements Specification and Technical Specification, together with any other specifications set forth in the Statement of Work or any attachment thereto.

“State”…