220000001161.pdf

PDF 7 MB Posted Jul 19, 2022

Attached to: Department Technology, Management and Budget MI|MA220000001161
Contract number: MA220000001161
Issued by: Michigan

About this file

Written by GovTribe AI · Aug 10, 2026

This document comprises four contract change notices (CN 1-4) to Michigan Enterprise Procurement Contract Number MA220000001161, originally executed on July 19, 2022, between the State of Michigan Department of Technology, Management, and Budget (DTMB) and Accenture (Contractor). The contract pertains to the implementation, configuration, customization, support, and maintenance of a new Sales, Inventory, and Purchasing System (SIPS) for the Michigan Liquor Control Commission (MLCC) under the Department of Regulatory and Safety Agencies (LARA). The contract is administered by DTMB and involves coordination among multiple state entities including DTMB procurement, MLCC project leadership, and the DTMB business relationship management office.

The contract encompasses development services across multiple technology platforms, including Microsoft Dynamics 365 Finance and Operations (7,200 story points), Salesforce configurations (1,506 story points), data conversion and migration (1,500 story points), reporting infrastructure (1,500 story points), and integrations and interfaces (3,437 story points). The original contract value was $7,825,000, with successive change notices increasing the total estimated aggregate contract value to $10,255,750 as of CN 4 (effective June 24, 2025). Payment is structured through 29 primary deliverables (D1-D29) plus AIMS Lightning Upgrade milestones, with milestone-based payments contingent upon acceptance of deliverables by the Agency Project Manager. The contract period extends from July 19, 2022, through July 18, 2027, with a 90-day warranty period following production go-live. Change notices CN 1-3 sequentially adjusted the go-live date from June 23, 2023 (CN 1: October 1, 2023; CN 2: January 15, 2024; CN 3: June 7, 2024), while CN 4 moved the go-live to October 1, 2025, and added detailed defect resolution procedures, governance structures including a Change Control Board, and comprehensive acceptance criteria for functional testing, end-to-end testing, UAT, ADA reversal functionality, and post-warranty deliverables.

View the file

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

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

MLCC Liquor Management System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

July 19, 2022 July 18, 2027 5 - 12 Months July 18, 2027

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

1001 Woodward Avenue 4th floor

Detroit MI 48226

Kathleen Cawley

859-248-1187

Kathleen.cawley@accenture.com

CV0062320

ACCENTURE

C O

A C

517-526-5410 willards@michigan.gov

Kristine Mills

517-242-6402

DTMB

Stuart Willard DTMB millsk11@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

Change Notice Number 4

Contract Number MA220000001161 to

DESCRIPTION OF CHANGE NOTICE

OPTION EXTENSIONLENGTH OF OPTION LENGTH OF EXTENSION REVISED EXP. DATE

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$8,785,000.00 $1,470,750.00 $10,255,750.00

DESCRIPTION

Effective 6/24/2025, the attached Statement of Work is incorporated into this Contract. The Contract value has been increased by $1,470,750 as reflected in Appendix A - Revised Payment Schedule. All other terms, conditions, specifications, and pricing remain the same. Per Accenture (Contractor) and LARA agreement, DTMB Central Procurement Services approval, and State Administrative Board approval on 6/24/2025.

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

LARA – MLCC Michigan Liquor Control Commissions System

Period of Coverage:

5/20/2025 – 7/18/2027

Requesting Department:

LARA - MLCC

Date:

5/20/2025

Agency Project Manager:

Cole Thelen

Phone:

DTMB Project Manager:

Jody Andrades

Phone:

517-930-5007

Background:

Change Notice 4 will supplement Contract 220000001161 originally executed 7/19/2022 with Contractor to provide Services to implement, configure, customize, support and maintain a new Sales, Inventory and Purchasing System (SIPS) for the Michigan Liquor Control Commission (MLCC). This Change Notice will not remove or limit the scope agreed to by the parties in Contract 220000001161 originally executed 7/19/2022 or in Change Notices 1-3.

Change Notice Scope:

The following items are incorporated into this Change Notice.

A. Project Clarifications B. Current Items in post go-live backlog C. Other Defects Specifically Resolved by this Change Notice D. Project Governance E. Payment Schedule (includes project go-live moved to October 1, 2025) Appendix A – Revised Payment Schedule Appendix B – ADA Invoice Corrective Reversals/Itemization Appendix C – CCB Escalation Template Appendix D - Acceptance Criteria

A. Project Clarifications:

All defects must be documented and categorized within Azure DevOps (ADO) with a severity and priority level assigned. Contractor is responsible for assigning a category and root cause to each defect. LARA/MLCC is responsible for assigning severity and priority. The clarifications and procedures outlined in this section apply to all defects on the SIPS Project except where specifically stated otherwise in sections B and C of this Change Notice.

1. Defect Categorization Contractor must categorize all defects in ADO into any of the following 8 categories:

• Code – A SIPS application code change.

• Configuration – A SIPS application configuration. For example, a platform toggle or parameter.

• Data – A data condition not met by the approved design document.

• Design Change – A SIPS application change that is not specified in the approved design or requirements.

• Partner – An issue with an external partner system. For example, ADAs and MILO.

• Report – A application change to the reports. For example, PowerBi report.

• Test Case – Requires an update to an existing test case or new test case.

• User – A user did not perform the steps per the business process.

Contractor must also identify an accurate “root cause” in the root cause field for each defect.

2. Contractor Responsibility by Defect Category Contractor’s responsibility for defect varies by category and is as follows:

• Code – Contractor must make modifications to the SIPS application’s code.

• Configuration – Contractor must adjust the SIPS application’s configuration.

• Data – The category must go through the Triage process. Contractor must specify the specific data parameter or condition that is causing the SIPS application to not produce the expected result and specify what the data would need to look like for the expected result to appear.

• Design Change – If Contractor believes the design change to be out of scope, then it must specify this as out of scope. The Design Change may then be discussed and resolved by the Project Leadership Team or escalated to the Change Control Board (CCB) as specified in section D of this Change Notice.

If Contractor believes the design change is in scope, then it must work with LARA/MLCC to adjust the functional design documents and make modifications to the SIPS application’s code to match the adjusted design at no additional cost.

• Partner – Contractor must specify partner condition that would need to be corrected or modified for the SIPS application to deliver the expected result.

• Report – Contractor must make the required application change to the Report.

• Test Case – Contractor must specify the steps of the test case that would need to be updated and assist with updating those steps.

• User – Contractor must specify which steps of the test case the user did not perform accurately and assist with instructing the tester how to accurately perform the test steps.

3. Defect Severity MLCC must assign each defect a severity based on the 5 levels:

• (1) Critical – System is down; little to no functionality; no workaround;

many services affected, or many users affected.

• (2) High – Process severely restricted; no workaround; several users affected.

• (3) Medium – Scenario/Basic functionality with some restrictions;

workaround available; loss productivity; one or more users affected.

• (4) Low – Minor problem; minimal workaround available; an annoyance.

• (5) Cosmetic – functionality for purpose unaffected, spelling error, in appearance.

4. Defect Priority MLCC must also assign a defect a priority from 1-4, based on the below 4 levels:

• (1) Immediate Response – Testing for Team is at a standstill until the bug is fixed; deadlines at risk with every passing day; bug must be fixed before go live.

• (2) Next – Testing of Processes severely impacted (other lesser value testing can continue); major functionalities cannot be tested; deadlines will be missed; go live critical.

• (3) Queued – Testing of scenarios is impacted but majority of testing can proceed as planned; testing deadlines are not impacted; go live discussion.

• (4) Bottom of Queue – No testing impact; minor bug to retest once fixed;

bug fix not required for go live.

Defects should be handled based on severity and priority. The SIPS application can Go-Live with severity 3-5 defects, but any severity 3-5 defect that is in scope must be resolved by Contractor after the Go-Live date in a manner that is consistent with Contractor’s responsibility based on the defect category as described in Section A.2. above.

After Contractor’s resolution, including pre-validating code and configuration changes to defects categorized as code, configuration, report, or design change that is either in scope or approved by the CCB in the manner described in section D of this Change Notice, MLCC will re-test scenarios until tests produce expected results, and the agreed upon exit criteria for UAT are met.

5. UAT support

Contractor’s obligations during UAT include: 1) analyzing and resolving defects in a manner consistent with that described above in section A.2., 2) validating that defect attributes are accurate (e.g., severity, priority, defect category), 3) facilitating triage, and 4) answering functional or technical questions.

Triage refers to the process of prioritizing defects based on criticality and impact.

Triage evaluates the project schedule and team capacity to determine that the defect can be delivered on time. The severity and priority fields in ADO will be used to prioritize defects and tasks.

6. State obligations during UAT

LARA/MLCC’s obligations during UAT with support from DTMB, include, 1) creating a test strategy and plan, including creating and maintaining all test cases in ADO, 2) executing test cases in ADO, 3) validating if UAT ready defects are resolved, and 4) defining business process.

Specifically concerning data, LARA/MLCC with DTMB support are responsible for creating and maintaining a test data set, including the use of synthetic data where LARA/MLCC with DTMB support deem appropriate to supplement live data testing, particularly when live data to meet test case pre-conditions is not available. LARA/MLCC, with DTMB support are responsible for resolving data and partner defects. However, Contractor will provide support to LARA/MLCC and DTMB to help identify the specific data issues or preconditions that need to be resolved for the SIPS system to perform as designed.

B. Defects in Post Go-Live Backlog:

1. Defects moved to Post Go-Live Backlog after April 3, 2025

Any defect added to the Post-Go-Live Backlog after April 3, 2025, must be resolved in a manner consistent with sections A of this Change Notice. If

Contractor believes any such defect to be an out-of-scope design change then, it must clearly delineate it as such, and the Project Leadership team must escalate to the Change Control Board in a manner consistent with Section D of this Change Notice if consensus cannot be reached.

2. Defects in Post Go-Live Backlog as of April 3, 2025

The table below lists all items (application defects, product backlog items, approved design changes) scheduled in the ‘Post Go-Live backlog’ in Azure DevOps (ADO) as of April 3, 2025, that will be completed by the Contractor within the Warranty period. Defects categorized as ‘design change’ require design sessions with LARA/MLCC. Discovery and Design sessions must be incorporated in the project schedule prior to Go-Live in order for the work to be delivered within the Warranty period. Salesforce design changes that are not design approved by 7/31/2025, will be removed from Warranty scope. D365 design changes that are not approved by 8/29/2025, will be removed from Warranty scope.

ID Title Severity

SIPS

Technolog y

Category

29283

365UAT- total cost on type 05 return is calculated incorrectly 3. Medium

Microsoft 365 FO Partner

28866

LARA SIPS+:

D365 - Scan Finding - WebInspect / Vulnerability / Persistent Cookie (Medium severity) 3. Medium

Microsoft 365 FO Partner

28800

LARA SIPS+:

D365 - Scan Finding - WebInspect / Vulnerability / Cross-Frame Scripting (Medium severity) 3. Medium

Microsoft 365 FO Partner

26559

SPR 1010:

PART 3 -

(Liquor Code/Product ID 6 digits) EQ CCC-When a CCC is submitted for N/A Salesforce Partner a variety case and a regular product exists for the same product

(COLA

number, flavor, size and bottle type), and the proposed

C. Items Specifically Resolved by this Change Notice This Change Notice also resolves three defects categorized by Contractor as “Design Change” that were not part of the Post Go Live Backlog as of April 3, 2025. They are as follows.

1. 46354 “365UAT – ADA Invoice Corrective Reversals – ADA 321 same Return reported on two separate ada invoice file dates (removal of ADA lines from ADA invoice file).”

The Design Change and corresponding development to fix this defect will be completed by Contractor prior to go live. The State will add additional value to the Contract to compensate Contractor for this work. The amount of this compensation is detailed and itemized in Appendix B.

2. 47279 “365UAT – Data Storage and Reporting Architecture” Contractor shall develop the necessary solution architecture for each of the defined and agreed-upon line-level queries within the SIPS system to meet LARA/MLCC's business requirements. The Contractor will work collaboratively with DTMB to develop these querying solutions as they progress through the end of the warranty period. Before the warranty period concludes, Contractor shall conduct complete knowledge transfer with DTMB, enabling DTMB's ongoing support and development of these querying capabilities.

3. 29059 “SIPSUAT weekly Vendor PO format changes 365 to salesforce integration” Contractor agrees to align the Salesforce Vendor PO screens to mirror the Microsoft D365 Vendor PO screens as those screens are designed as of the end of functional testing (May 2025).

D. Project Governance

1. Change Control Board and Project Leadership Composition

Governance for this project will consist of a Change Control Board (CCB) as well as a Project Leadership Team. The CCB members (referenced below) include representation from Contractor, DTMB, and LARA. Any delegate of the CCB must be selected from that member’s organization.

1. Lisa Cawley – Contractor

2. Heather Frick – DTMB

3. Adam Sandoval – LARA

The CCB will make all decisions on changes to scope, schedule, or budget as well as the final determination of requirements or defects being in-scope or out-of-scope. Changes requiring review by the CCB will be based on an agreed upon template (Appendix C) that will include a thorough analysis including time impacts, cost impact, risks, and a recommended decision. Documentation must be provided to the CCB leadership 24 hours before the scheduled CCB meeting.

The Project Leadership Team will serve as the initial reviewers of changes requiring review by the CCB. The Project Leadership Team will consist of:

1. DTMB Project Manager

2. MLCC Product Owner

3. MLCC Business Director

4. LARA Assistant Deputy Director

5. DTMB Business Relationship Manager

6. Contractor Project Manager

7. Contractor Delivery Lead

The CCB and Project Leadership Team will establish delegates to meet their obligations in their absence.

2. Change Control Board Escalation Procedure

The process for escalating matters to CCB will be as follows:

1. If Contractor believes a defect it has categorized as a “design change” is out of scope, it should notify the entire Project Leadership Team. The Project Leadership Team will meet to determine whether they can resolve the issue or whether further steps to escalate the issue are necessary.

2. If project leadership cannot reach consensus, it will prepare documents to escalate to the CCB as included in Appendix C.

3. Alternatively, if the Project Leadership Team believes that other changes to the project are merited that impact scope, schedule, or budget, they will prepare documents to escalate to CCB. These changes can include new integration and data conversion change requests found in UAT, mock, Go-live, and Warranty.

4. Project Leadership will make its best effort to have all documents to the CCB within 10 business days after the initial categorization for any severity 1 or severity 2 defect subject to the provisions of this section.

5. DTMB Project Manager or designee serves as the final approval of contents of documentation escalated to CCB.

6. The CCB will make its best effort to issue decisions on requests concerning any severity 1 or severity 2 defect in no more than 3 Business Days. Once a decision has been made, it will be documented in a Notice of Decision documentation. The approval of any out-of-scope request will result in a future Change Notice.

7. Severity 3-5 defects categorized as “Design Change” that Contractor believes are out of scope, are subject to the provisions of this section but their escalation and resolution can be given lower priority.

E. Payment Schedule

Payment will be made consistent with the milestone table (Appendix A) which replaces, in its entirety, the pricing table included in the existing Contract. After Milestones are met and corresponding deliverables are accepted by the State, 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 must 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 that follow milestones being met and the State’s acceptance of corresponding deliverables.

Appendix A - Revised Payment Schedule:

Milestone Number Milestone Event Milestone

Month Minimum Milestone Deliverable(s) Payment Amount

Project Planning

August 2022

Kickoff Meeting planning.

Conduct Project Kickoff Meeting.

Determine and set up lifecycle management tool. Core team training as needed.

Determine initial team norms.

Plan Discovery approach and sessions.

Create project schedule and update WBS dates.

$121,500

Provision Environments

September

Enable Dev, Test and Pre-Prod environments. Review Requirements and Finalize Document.

D3 Discovery, Requirements Validation, and Design

August 2022 -

October 2022

Discovery and Validation sessions (billed $318,875 each month)

$956,625

Iterative Development Milestones in Five Stages

December 2022 – May 2023 (Originally April 2023)

Development Sprints Include:

D4 Design, Build, Unit Test for:

Vendor & Product Registration Sprint 1 and Sprint 2

Sales, Inventory, Purchasing Sprint 1.

December

Product Backlog Development (Design / Build / Unit Test):

• Vendor & Product Registration (Salesforce) Sprint 1, Sprint 2. 235 of 1506 product backlog complete. 235 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft D365 FO) Sprint 1: 400 of 7200 of product backlog. 400 complete in this deliverable.

$417,475

D5 Design, Build, Unit Test for:

2, Sprint 3.

January 2023 Product Backlog Development (Design / Build / Unit Test):

• Vendor & Product Registration (Salesforce) Sprint 3. 445 of 1506 product backlog complete. 210 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft D365 FO) Sprint 2, Sprint 3: 1900 of 7200 product backlog complete. 1500 complete in this deliverable.

D6 Design, Build, 4 and Sprint 5.

March 2023 (Originally February 2023)

Product Backlog Development (Design / Build / Unit Test):

• Vendor & Product Registration (Salesforce) Sprint 4, Sprint 5. 965 of 1506 product backlog complete. 520 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft

4 and Sprint 5.

D365 FO) Sprint 4, Sprint 5: 4100 of 7200 product backlog complete. 2200

D7 Design, Build, 6.

April 2023 (Originally March 2023)

Product Backlog Development (Design / Build / Unit Test):

• Vendor & Product Registration (Salesforce) Sprint 6. 1275 of 1506 product backlog complete. 310 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft D365 FO) Sprint 6: 5300 of 7200 product backlog complete. 1200 complete in this deliverable.

D8 Design, Build, May

April 2023)

Product Backlog Development (Design / Build / Unit Test):

• Vendor & Product Registration (Salesforce)

$387,475

*Originally $417,475, reduced by 30K for VDI (CN1).

7 and Sprint 8.

Sprint 7. 1506 of 1506 product backlog complete. 231 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft D365 FO) Sprint 7, Sprint

8. 7200 of 7200 product backlog complete. 1900

Data Conversion Workstream

December 2022

– May 2023 (Originally April 2023)

Iterative Process:

D9 Data Conversion for Stage 1

December

Data Conversion. Stage 1 (Data Migration template):

420 of 1500.

$71,500

D10 Data Conversion Stage 2

January 2023 Data Conversion. Stage 1- 2 (Extract / Map / Cleanse / Transform): 525 of 1500

D11 Data Conversion Stage 3

March 2023 (Originally February 2023)

Data Conversion. Stage 1-3 (Extract / Map / Cleanse / Transform / Load / Test / Fix / Validate): 800 of 1500

$71,500

D12 Data Conversion Stage 4

April

March 2023)

Data Conversion. Stage 1-4 (Cleanse / Load / Test / Fix / Validate): 1100 of 1500

$71,500

D13 Data Conversion Stage 5

May

April 2023)

Data Conversion. 100% Complete. Stage 1-5 (Cleanse / Load / Test / Fix / Validate, ): 1500 of 1500

$71,500

Reporting Workstream

January 2023

May 2023

For each required report:

D14 Report Group 1

January 2023 Reports Workstream (Infrastructure POC / Design): 300 of 3000

$71,500

D15 Report Group 2

March 2023 (Originally February 2023)

Reports Workstream (Infrastructure POC / Design / Build): 550 of 3000

$71,500

D16

Report Group 3

May 2023 (Originally March 2023)

Reports Workstream (Infrastructure POC / Design / Build / Test / Fix / Approval): 1700 of 3000

D17

Report Group 4

December 2023 (Originally October 2023)

Reports Workstream (Infrastructure POC / Design / Build / Test / Fix / Approval): 3000 of 3000

D18

Integrations and Interfaces Workstream Stage 1

Integrations and interfaces Workstream (Design / Establish Connection / Build): 500 of 3437.

$143,000

D19

Interfaces

January 2023

Integrations and interfaces Workstream (Design / Establish Connection / Build / Test) 1143 of 3437.

D20

Interfaces

Stage 3

April 2023

March 2023)

75% of Integrations and interfaces Workstream (Design / Build / Test / Fix / Approval): 2044 2579 of 3437.

D21

Interfaces

June 2023 (Originally May 2023)

Integrations and interfaces Workstream (Design / Build / Test / Fix / Approval); 3437of 3437.

D22

System Integration Testing

June 2023 (Originally May 2023)

Develop test scripts and conditions. Defect tracking, mitigations, and reporting.

Conduct testing.

$236,000

SIT completion report and closure report.

D23

Security Assessment and Authority to Operate (ATO)

Follow State Security Team direction. Provide answers to control questions. Provide reports and scan results.

Achieve ATO.

$429,000

D24

Web Standards and Accessibility

January 2024

October 2023)

Testing by SOM team.

Mitigate non-conformances where appropriate. Re-testing by SOM team.

Further mitigation and retesting as needed. Develop plan for future mitigation where necessary.

D25.a.1

User Acceptance Testing (UAT) and issue resolution

July 2023

May 2024

Develop test scenarios, scripts, and conditions. Deliver Final Solution to TEST environment.

• UAT execution.

• Defect tracking, mitigations, reporting, and retesting. Final Test Results Report.

$117,000

Payment broken down through this

CN.

• Completion and closure report.

• Develop and deliver tailored SUITE artifact(s).

D25.a.2 User Acceptance Testing (UAT) and issue resolution – Functional

May 2025

Minimum milestones are in accordance with Acceptance Criteria listed in Appendix D, Functional Testing Exit (Acceptance) Criteria

$600,000

Added through this CN.

D25.a.3 User Acceptance Testing (UAT) and issue resolution – End to End Testing Defect Resolution 46354

– ADA Reversal

August 2025

Criteria listed in Appendix D, ADA Reversal Exit (Acceptance) Criteria

$70,750

D25.a.4 User Acceptance Testing (UAT) and issue resolution – End to End Testing

Criteria listed in Appendix D, End to End Exit (Acceptance) Criteria

$400,000

D25a.5 User Acceptance Testing (UAT) and issue resolution

Develop test scenarios, scripts, and conditions. Deliver Final Solution to TEST environment.

• UAT execution.

• Defect tracking, mitigations, reporting, and retesting. Final Test Results Report.

$117,000

Payment broken down through this

CN.

• Completion and closure report.

Develop and deliver tailored SUITE artifact(s).

D25b Mock 1 Activities

November 2023

October 2023)

• Mock deployments.

• Mock data conversion. $50,000

D25c Mock 2 Activities

• Mock deployments.

• Mock data conversion.

*Target is to conduct at least two mock conversions and data conversions by early September.

$50,000

D25d Go-Live Extension 1

December 2023 (Originally November 2023)

• Go-Live extension.

$172,000

Added through CN2

D25e Go-Live Extension 2

December

$168,000

Added through CN2

25f

Testing (UAT) and issue resolution

April 2024 (Originally March 2024)

• UAT execution.

• Defect tracking and retesting.

$200,000

Added through CN3

25g

User Acceptance Testing (UAT) and issue resolution

May 2024 (Originally April 2024)

• UAT execution.

• Defect tracking and retesting.

$200,000

Added through CN3

D26a.1 Training activities

Training delivered according to the agreed training plan

$35,750

Broken into D26a.1 and D26a.2 through this CN with no additional cost.

D26a.2 Training activities

May 2025

Training delivered according to the agreed training plan

$35,750

Broken into D26a.1 and D26a.2 through this CN with no additional cost.

Implementation and Go Live

Develop Implementation Plan and Go Live Checklist. Including (but not limited to):

• Go – No Go meeting and decision.

• Install in PROD environment.

D27

October 2025

• Final data conversion run.

• Configure interfaces.

• Smoke testing.

System stabilized in PROD.

Develop and deliver tailored SUITE artifact(s). Acceptance of Production System.

$1,250,500

*Originally $500,500. Moved 500K to this deliverable from D29. Added 150K for October deployment through CN1. Added 100K through

CN3.

D28

Post-Production Warranty

January 2026

Defect tracking, mitigations, reporting, and retesting. Final Test Results Report.

Completion and closure report

Included in the cost of Solution

D29a.1

Knowledge Transfer and Hand off.

Final Payment (This Final Payment will be made after expiration of this Warranty Period

Completion of Project Deliverables. Final training and documentation.

Update Configuration Management Plan.

$505,000 and after application of any Service Level Credits)

Configuration management training.

Update Maintenance Plan.

Completion of all remaining tailored SUITE artifacts.

*Originally $1,005,000. Moved 500K to D27 (CN1).

D29a.2 Completing all items currently in post go-live bucket

January 2026 Minimum milestones are in

Criteria listed in Appendix D, Final Payment Post Warranty Period

$400,000

Production Support Services

Optional Ongoing Support after Final Acceptance

Optional

SUBTOTAL SIPS+ $9,580,750

ALU - D1 Discovery Initiation and Planning

August 2022 •Discovery sessions with SOM team

• SUITE tailoring session and agreement

• Run Lightning Readiness Report

• Configure Sandbox for Upgrade activities

• Use LExT to assess the AIMS classic environment (provides count and complexity of Visualforce Pages, JavaScript buttons, Workflows)

• Identify all Notes, Documents, Attachments and Articles in the current system

ALU - D2 Planning and Lightning Conversion, September

•Help create the Project Schedule and Budget

• Perform Fit-Gap Analysis and Mapping

• Prioritize Feature transformation

• Roadmap the Lightning migration, defining when to migrate different modules, users and teams.

• Perform system complexity check

• Identify opportunities for process improvement

• Perform conversion activities, including but not limited to, Visualforce Pages, JavaScript buttons, Workflows

• Document user changes

$75,000

• Prepare help cards and user training

ALU - D3 UAT January 2023 • User Training as needed

• Develop and deliver tailored SUITE artifact(s) Run Lightning Readiness •Report to confirm

• Defect tracking, mitigations, reporting, and retesting

• Final Test Results Report

$75,000

ALU - D4 Migrate to Prod, January 2023 • Develop Implementation Plan and Go Live Checklist

• Including (but not limited to):

• Go – No Go meeting and decision

• Install in PROD environment

• Smoke testing

• System stabilized in PROD

• Develop and deliver tailored SUITE artifact(s)

• Acceptance of Production

ALU - D5 90 day Warranty and Final Payment, April 2023 • Defect tracking, mitigations, reporting, and retesting

• Final Test Results Report

• Completion and closure report

$250,000 Amount payable before the application of any Service Level Credits

Subtotal AIMS Lightning Upgrade $675,000

Total SIPS+ and AIMS Lightning Upgrade

$10,255,750 *Originally $7,825,000

Appendix B – ADA Invoice Corrective Reversals/Itemization

Onshore

Rate Cost Activities

Sr. Application Arch. 100 $265.00 $26,500.00 Discovery, Design, Development

Sr. Functional Consultant 20 $240.00 $4,800.00 Discovery

Sr. Functional Consultant 25 $240.00 $6,000.00 Design, QA Test

Technology Consultant 80 $210.00 $16,800.00 Development

Sr. Technology Analyst 90 $185.00 $16,650.00 Design, QA Test

$70,750.00

Appendix C – CCB Escalation Template

Change Control Board Escalation Document

DATE:

TITLE

BACKGROUND:

ADO Item:

General Description:

Frequency:

Compliance Issue (Y/N):

IMPACT: Impact on the schedule:

Impact on the budget:

Impact on project resources:

Impact to Business:

MILESTONES

SCOPE Relevalnt Business Requirements:

Relevant Functional Design Documents:

OPTIONS OR

ALTERNATIVES:

Assumptions:

Recommendation:

Role Name Signature Date

Appendix D - Acceptance Criteria

If Acceptance for a deliverable is not received from the State within 10 Business Days of submission, the Contractor will escalate to the CCB using the CCB Escalation Template (Appendix C).

Functional Testing Exit (Acceptance) Criteria (D25.a.2):

The following criteria must be met to conclude the Functional testing phase for the SIPS application:

1. Test Case Execution:

o A minimum of 100% of all planned and documented Functional test cases have been executed, with a 95% Pass/Closed rate.

2. Defect Resolution o All Severity 1 and 2 defects that are categorized as Code, Configuration, Report, or in scope Design Change (as documented in ADO) are resolved and validated, with mutually agreed upon exception.

o All Severity 3, 4 and 5 defects categorized as Code, Configuration, Report, or in scope Design Change shall be resolved prior to the end of the 90-day warranty period unless the State of Michigan provides formal written approval for non-resolution. Contractor shall submit a comprehensive list of all identified Severity 3, 4 and 5 defects to LARA/MLCC, clearly outlining any defects proposed for non-resolution due to documented higher priority efforts, along with a detailed justification for each such proposal.

3. Acceptance Sign-Off .

o Formal sign-off from MLCC confirming that functional testing has sufficiently progressed, and all defects have been resolved or mitigated to the business's satisfaction, allowing progression to End-to-End Testing.

o This sign-off will be documented with a stage exit SUITE document SEM 0189.

End-to-End Testing Exit (Acceptance) Criteria (D25.a.4):

The following criteria must be met to conclude the End-to-End (E2E) testing phase for the SIPS application:

1. Test Case Execution Coverage:

o 100% of all planned and documented E2E test cases and performance test cases have been executed.

2. Defect Resolution:

o Zero (0) open defects categorized as Code, Configuration, Report, or in scope Design Change with a severity of 1 or 2.

3. Performance Testing (Applicable End-to-End Flows):

o For the following critical end-to-end business flows (for ex; "Order

Processing"), the average response time and response times for queries performed on D365 UI meets the agreed-upon service level agreements (SLAs) as documented in the SEM 603.

4. Acceptance Sign-Off .

o Formal sign-off from MLCC confirming that End to End testing has sufficiently progressed, and all defects have been resolved or mitigated to the business's satisfaction, allowing progression to Exiting UAT and Go- Live.

o This sign-off will be documented with a stage exit SUITE document SEM 0189.

Exiting UAT (Acceptance) Criteria (D25a.5):

User Acceptance Testing (UAT) confirms that the system meets the needs of the end-users. Successful UAT is a critical prerequisite for Go-Live.

1. UAT Completion:

o All planned UAT test scenarios/test cases have been executed by designated end-users. 100% of test cases passed. Any exception will be evaluated and approved by CCB.

2. User Sign-Off:

o Formal sign-off from MLCC confirming that the UAT testing is complete, and the system meets their requirements and is acceptable for deployment. This sign-off will be documented with a stage exit SUITE document SEM 0189.

3. Defect Resolution (UAT):

o All severity 1 and 2 defects categorized as Code, Configuration, Report, or in scope Design Change identified during UAT have been resolved and retested successfully.

o All Severity 3, 4 and 5 defects categorized as Code, Configuration, Report, or in scope Design Change shall be resolved unless the State of Michigan provides formal written approval for non-resolution. The vendor shall submit a comprehensive list of all identified Severity 3, 4 and 5 defects to LARA/MLCC, clearly outlining any defects proposed for non-resolution due to documented higher priority efforts, along with a detailed justification for each such proposal.

4. Training Completion:

o Training and Knowledge Transfer documentation has been completed, reviewed and approved by LARA/MLCC and DTMB respectively.

o End-user training has been completed according to the training plan.

5. Go-Live Implementation Plan:

o A formal go-live implementation plan/checklist has been created and approved by both the contractor and State of Michigan (LARA/MLCC and DTMB). This plan should cover aspects like data migration, cutover plan, rollback plan, and support processes, and be detailed enough to include handoff’s and timed scheduled for critical activities.

6. Documentation Handover:

o All necessary user manuals, training materials, and support documentation have been delivered and approved, and the approval by LARA/MLCC will be documented with the SUITE document SEM 0189.

7. Environment Sign-Off:

o Formal confirmation from Accenture that the production environment is ready for deployment.

ADA Reversal Exit (Acceptance) Criteria (D25a.3)

This milestone ensures that the ADA Reversal enhancement is completed, and stable and performs as expected after being deployed to production.

1. Remediation of defect 46354

a. Complete remediation as outlined in document – 46354 ADA Reversal

Functionality Change Control Board Document (March Version)

b. Defect will be included in the End to End testing process and acceptance will be in accordance with the End to End testing acceptance criteria.

Final Payment Post Warranty Period Exit (Acceptance) Criteria (D29a.2)

This milestone ensures the system remains stable and performs as expected after it has been in production for a defined period.

1. Warranty Period Completion:

o The agreed-upon 90-day warranty period has elapsed.

2. Defect Issue Resolution:

o All defects not approved to be moved to the post-warranty support backlog have been resolved and closed.

3. Performance Compliance:

o The system continues to meet the agreed-upon key performance indicators (KPIs) in the production environment. Including but not limited to:

o Stability - The system has demonstrated stable operation in the production environment during the warranty period, with uptime meeting the agreed-upon service level agreements (SLAs) as documented in the SEM 603.

4. Documentation Updates:

o Any updates to documentation identified during the warranty period have been delivered.

o Documentation has been presented to MLCC, reviewed, and approved through a formal signoff.

5. Formal Sign-Off:

o Utilizing the SUITE 0189 template, formal sign-off from MLCC that the system has met the post-warranty acceptance criteria.

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 3 to

Contract Number 220000001161 willards@michigan.gov

Stuart Willard

Jeremy Lyon kathleen.cawley@accenture.com

Kathleen Cawley

Detroit, MI

ACCENTURE

CV0062320

859-248-1187

1001 Woodward Avenue 4th floor

(517) 230-2858 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

517-526-5410

DTMB

lyonj5@michigan.gov

$8,285,000.00

July 19, 2022 July 18, 2027

LARA – MLCC MICHIGAN LIQUOR CONTROL COMMISSIONS SYSTEM

July 18, 2027

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

5 - 1 Year

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

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

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

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

☐ ☐ July 18, 2027

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$500,000.00 $8,785,000.00

Effective 3/26/2024, this change is to the project go live date from January 15, 2024 to June 7, 2024, and this contract here by increases by $500,000. This will modify the Implementation Fees, Milestones and Payment Schedule and includes detailed deliverable descriptions and modifies several expected payment dates.

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

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

CONTRACT SUMMARY

LARA

Michigan.gov/MiProcurement

Version 2021-1 1 of 13

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

LARA – MLCC Michigan Liquor Control Commissions System

Period of Coverage:

3/1/2023 – 7/18/2027

Requesting Department:

LARA - MLCC

Date:

1/19/2024

Agency Project Manager: COle Thelen

Phone:

517-388-8350

DTMB Project Manager:

Shoba Murali

Phone:

517-230-4082

Brief description of services to be provided:

BACKGROUND:

This is Change Notice 3 to Contract 220000001161 originally executed 7/19/2022 with Accenture (Contractor) to provide Services to implement, configure, customize, support and maintain a new Sales, Inventory and Purchasing System (SIPS) for the Michigan Liquor Control Commission (MLCC).

PROJECT OBJECTIVE:

This Change Notice 3 accomplishes the following objectives.

• Changes the Project Go-Live date to June 7, 2024.

• Increases contract by $500,000.

• Increases the total contract amount from $8,285,000 to 8,785,000.

• Modifies the Implementation Fees, Milestones and Payment Schedule and includes detailed deliverable descriptions and modifies several expected payment dates.

SCOPE OF WORK:

1. Schedule B, Pricing, Section 4, Implementation Fees, Milestone and Payment

Schedules: The table in Attachment 1, below, replaces Implementation Fees, Milestone and Payment Schedules as updated in Change Notice 1 and Change Notice 2. This new payment schedule identifies the expected deliverables for each payment. Additional explanations:

a. Contractor cost is increased by $500,000 to account for cost to move the Go Live delivery date from January 15, 2024, to June 7, 2024.

Version 2021-1 2 of 13

b. Total Estimated Contract Value from $8,285,000 to $8,785,000.

c. The Payment Schedule updated to add monthly milestones January to June 2024, which splits the $500,000 cost increase into two monthly payments of $200,000 as part of the User Acceptance deliverable (i.e., 25f, 25g) and a third payment of $100,000 added to the Implementation and Go-live deliverable.

TASKS:

No additional tasks are identified in this Change Notice.

DELIVERABLES:

Deliverables will not be considered complete until the Agency Project Manager has formally accepted them. Deliverables are further clarified in the attachments below.

ACCEPTANCE CRITERIA:

For initial product backlog, Acceptance criteria will be documented in ADO and will be further clarified during analysis, grooming, and design sessions during the execution of this project. Section 9, Software Acceptance Testing, of the Agreement remains in effect.

PROJECT CONTROL AND REPORTS:

No additional project control activities nor reports are identified in this Change Notice.

SPECIFIC DEPARTMENT STANDARDS:

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

PAYMENT SCHEDULE:

Payment schedule is clarified in the Attachments below.

EXPENSES:

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

PROJECT CONTACTS:

The designated Project Contacts are not changed by the Change Notice.

AGENCY RESPONSIBILITIES:

Version 2021-1 3 of 13

The Agency Responsibilities are not changed by this Change Notice.

LOCATION OF WHERE THE WORK IS TO BE PERFORMED:

The location of work is not being changed by this Change Notice.

EXPECTED CONTRACTOR WORK HOURS AND CONDITIONS:

The Contractor work hours are not being changed by this Change Notice. No overtime will be permitted.

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

PROJECT PLAN:

Please see attachments below.

Version 2021-1 4 of 13

ATTACHMENT 1 TO CHANGE NOTICE #1 (PAYMENT SCHEDULE)

Number Milestone Event

Milestone Month (est.) Minimum Milestone Deliverable(s)

Payment Amount

Meeting.

Determine and set up lifecycle management tool. Core team training as needed.

Determine initial team norms.

Plan Discovery approach and sessions.

Create project schedule and update WBS dates.

Provision Environments

Enable Dev, Test and Pre-Prod environments.

Review Requirements and Finalize Document.

Requirements Validation, and Design

August 2022 - October 2022

Discovery and Validation sessions (billed $318,875 each month) $956,625

Iterative Development Milestones in Five Stages

2022 –

D4 Design, Build, Unit Test for: December

Product Backlog Development (Design / Build / Unit Test):

Version 2021-1 5 of 13

1 and Sprint 2

Sales, Inventory, Purchasing Sprint 1.

• Vendor & Product Registration (Salesforce) Sprint 1, Sprint 2. 235 of 1506 product backlog complete. 235 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft D365 FO) Sprint 1: 400 of 7200 of product backlog. 400 complete in this

Vendor & Product Registration Sprint 3.

Sales, Inventory, Purchasing Sprint 2, Sprint 3.

January 2022 Product Backlog Development (Design / Build / Unit Test):

• Vendor & Product Registration (Salesforce) Sprint 3. 445 of 1506 product backlog complete. 210 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft D365 FO) Sprint 2, Sprint 3: 1900 of 7200 product backlog complete. 1500 complete in this deliverable.

D6 Design, Build, Unit

Vendor & Product Registration Sprint 4 and Sprint 5.

Sales, Inventory, Purchasing Sprint 4 and Sprint 5.

February 2023 Product Backlog Development (Design / Build / Unit Test):

• Vendor & Product Registration (Salesforce) Sprint 4, Sprint 5. 965 of 1506 product backlog complete. 520 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft D365 FO) Sprint 4, Sprint 5: 4100 of 7200 product backlog complete. 2200

Version 2021-1 6 of 13

D7 Design, Build, Unit

Vendor & Product Registration Sprint 6.

Sales, Inventory, Purchasing Sprint 6.

March 2023 Product Backlog Development (Design / Build / Unit Test):

• Vendor & Product Registration (Salesforce) Sprint 6. 1275 of 1506 product backlog complete. 310 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft D365 FO) Sprint 6: 5300 of 7200 product backlog complete. 1200

D8 Design, Build, Unit Test for:

Vendor & Product Registration Sprint 7.

Sales, Inventory, 7 and Sprint 8.

April 2023 Product Backlog Development (Design / Build /

• Vendor & Product Registration (Salesforce) Sprint 7. 1506 of 1506 product backlog complete. 231 complete in this deliverable.

• Sales, Inventory, Purchasing (Microsoft D365 FO) Sprint 7, Sprint 8.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Aug 10, 2026.