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

Phase 2 of Dev & Maint Risk Data Management System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

October 25, 2016 October 25, 2021 5 - 1 Year October 25, 2026

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

N/A

P-Card Direct Voucher (PRC) Other Yes No

13308 N. MacArthur Blvd.

Oklahoma City OK 73142

Dan Yates

405-516-4972 dyates@gwpc.org

CV0062466

GROUND WATER PROTECTION

COUNCIL

C O

N

TR

A C

TO

R

Shane Desmier

517-246-8229

DTMB

Various Various

DesmierS@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

N/ANET 45

Change Notice Number 12

Contract Number MA071B7700011C to

DESCRIPTION OF CHANGE NOTICE

OPTION EXTENSIONLENGTH OF OPTION LENGTH OF EXTENSION REVISED EXP. DATE

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

0 Years

$1,791,492.00 $0.00 $1,791,492.00

DESCRIPTION

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

Contract Amendment – ADA Compliance

Effective Date: January 14, 2026

Zero Cost Change Notice

The amendment of this contract includes the updated ADA Compliance language listed below, which replaces the previous WCAG 2.0 Level AA language with WCAG 2.1 Level AA. No additional funding is required for this amendment.

ADA Language - WCAG 2.1 Level AA:

Accessibility Requirements.

The State is required to comply with the Americans with Disabilities Act of 1990 (ADA) and has adopted standards and procedures regarding accessibility requirements for websites, applications, content, and electronic documents. Due to a change in the law, the State is required to comply with specific accessibility standards for websites, applications, content and documents.

Starting 4/24/2026, throughout the Term, all websites, applications, software, content, and electronic documents, including but not limited to mobile applications, text, images, sounds, videos, controls, animations, links, and documents (including files in the following formats: PDF, word processing, presentation, and spreadsheet), created, provided, or made available by the Contractor under this Contract, must comply with WCAG 2.1 Level AA.

Please note the Contract Administrator has been changed to Shane Desmier

All other terms, conditions, specifications, and pricing remain the same. This amendment is made with the agreement of the Contractor, the Agency, and DTMB Central Procurement Services.

AGENCY NAME PHONE EMAIL

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

EGLE Adam Wygant 517-897-4828 wyganta@michigan.gov

Program Managers for

Multi-Agency and Statewide Contracts

CHANGE NOTICE NO. 12 TO CONTRACT NO. MA071B7700011C

STATE OF MICHIGAN PROCUREMENT

Department Technology, Management and Budget Central Procurement Services 320 S Walnut Street Lansing, MI 48933 P.O. Box 30026, Lansing, MI 48909

CONTRACT CHANGE NOTICE

CONTRACT SUMMARY

Phase 2 of Dev & Maint Risk Data Management System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

October 25, 2016 October 25, 2021 5 - 1 Year October 25, 2026

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

13308 N. MacArthur Blvd.

Oklahoma City OK 73142

Dan Yates

405-516-4972 dyates@gwpc.org

CV0062466

GROUND WATER PROTECTION

COUNCIL

C O

N

TR

A C

TO

R

Jarrod Barron

(517) 249-0406

DTMB

Various Various

BarronJ1@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Change Notice Number 11

Contract Number MA071B7700011C to

DESCRIPTION OF CHANGE NOTICE

OPTION EXTENSIONLENGTH OF OPTION LENGTH OF EXTENSION REVISED EXP. DATE

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

0 Years

$1,750,206.00 $41,286.00 $1,791,492.00

DESCRIPTION

Effective 10/3/2025, the parties revise and fully restate Contract Change Notice 9 MiSTAR APD and Security Updates statement of work and add $41,286 (reflecting a cost increase from $134,146 to $175,432) per the attached documentation. All other terms, conditions, specifications and pricing remain the same. Per Contractor, Agency, DTMB Central Procurement and State Administrative Board approval on 9/11/2025.

EGLE Adam Wygant 517-897-4828 wyganta@michigan.gov

Program Managers for

Multi-Agency and Statewide Contracts

CHANGE NOTICE NO. 11 TO CONTRACT NO. MA071B7700011C

CHANGE NOTICE NO. 11 TO CONTRACT NO. MA071B7700011C

Version 2021-1 1 of 9

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

Updated Change Request for MiSTAR APD and Security Updates

Period of Coverage:

September 2025 through March 8, 2026

Requesting Department:

Environment, Great lakes and Energy (EGLE) Geologic Resources Management Division (GRMD)

Date:

September 9, 2025

Agency Project Manager:

Carrie Johnson

Phone:

517-230-3598

DTMB Project Manager:

Jasvin Sidhu

Phone:

734-620-6797

BRIEF DESCRIPTION OF SERVICES TO BE PROVIDED: As part of contract 071B7700011 with the Ground Water Protection Council (GWPC), GWPC provides maintenance of, and enhancements to, the Risk Based Data Management System (RBDMS). Under this Statement of Work (SOM), the Environment, Great Lakes, Energy (EGLE) Geologic Resources Management Division, the Ground Water Protection Council (GWPC) and the Geologic Resources Management Division (GRMD) is proposing to implement and utilize the latest technology to ensure compliance with both state and federal requirements and upgrade the existing system. This change request will update the project schedule, scope and budget.

BACKGROUND:

The current oil and gas well permitting system used for submitting permit requests is a web-based application named EForms. Once the files are received, edited and approved through this system, the data is pushed to the main MIRBDMSNET databases. The proposed project would allow us to retire the old technology used with Eforms and integrate this application into an already existing part of our system (MiSTAR). It will also include integration of the MiSTAR application with the MiLogin security application instead of using a separate security protocol.

These updates will support the necessary requirements for collecting data, overall data management, compliance tracking, and report generation. This project will be performed on a fixed price basis as detailed in the Payment Schedule section of this SOW.

PROJECT OBJECTIVE:

The proposed project will allow us to retire the antiquated technology used with Eforms and integrate this application into an already existing system (MiSTAR). It will also include the integration of the MiLogin security application, which would replace the current solution-based security protocol.

Version 2021-1 2 of 9

SCOPE OF WORK:

MiSTAR Product Enhancements.

This change request includes the following specific enhancements:

1. Implement Additional Identification Fields for Submissions Add "Form Key" attribute to the Submission list page that can be configured for each form to provide form details which will help users more easily identify forms they might be looking for.

2. Implement additional APD form logic to handle more scenarios Update APD form validation logic and form behavior to handle additional form requirements surrounding redrills, converts and situations with unknown casing information.

3. Add Line Charts to the three “Production List” pages Line charts will allow users to graph production information for each of the production types/categories. The graphs are connected to the list page grids and display the data filtered in the grid, updating as filter parameters are updated.

4. Develop user configuration for the landing page.

Implement a user configurable landing page that lets users configure which navigation cards are visible for them. This will include developing a page where each user can update settings on the order and visibility of administratively defined cards.

5. Security scans Solution will conform to WCAG 2.1.1 Standards. Vendor will work to remediate all critical, high and medium vulnerabilities, and will adhere SOM/Agency branding.

TASKS:

Specific to the scope of work in this statement of work, the following tasks will be completed:

Project Planning The contractor will adhere to mutually agreed SUITE project tailoring documentation and will perform the activities listed below.

Project Initiation Following the SUITE project tailoring, Contractor will initiate services by scheduling and facilitating a project kick-off meeting. The objective of the meeting will be to review the overall project schedule, tasks, deliverables, and expectations of project personnel. The contractor will issue meeting notes, project roster and as appropriate, an updated project schedule.

Project Schedule The Project Schedule will include a project timeline, tasks, and responsible parties for each task.

The goal of the project schedule is to provide a clear picture of expectations for the Contractor, GRMD and DTMB. Each stakeholder will use this to make sure staff are available to complete tasks within the specified timeline.

Version 2021-1 3 of 9

Requirements Validation Following the kick-off meeting, Contractor will review the existing requirements and preliminary screen designs and complete validation activities to ensure complete documentation in support of the scope of work. The contractor will obtain formal approval of the resulting updated documents.

Design Referencing the approved requirements, Contractor will complete activities to develop and maintain appropriate design documentation. Content related to user interface (UI) design, system architecture, data modeling and integration specifications will all need to be accounted for. The contractor will obtain formal approval of the resulting design documentation. As appropriate for the development methodology and project schedule, this task may be done in iterations / Sprints.

Construction In accordance with the approved design documentation, the Contractor will complete construction activities. These are expected to include code development, peer reviews, and appropriate testing for the scope of work and schedule (i.e., unit testing, system testing, etc.). As appropriate for the development methodology and project schedule, this task may be done in iterations / Sprints.

Testing In preparation for each release, the Contractor will complete and/or participate in release testing to include QA review, system test, and integration test. The contractor will present test results and obtain formal approval of the resulting test results and resolutions.

Prior to the implementation / migration of each UAT release that will be performed in the State operating environment, the Contractor will submit the code for the developed functionality to DTMB for conducted security scans. The contractor will remediate issues identified for all new system components, answer questions from DTMB regarding the System Security Plan (SSP), and validation of adherence to eMichigan ADA and Commercial-off-the-shelf (COTS) Look and Feel standards.

Services and deliverables must comply with State Unified IT Environment (SUITE).

User Acceptance Testing (UAT): Contractor will support the planning and execution of UAT for each release with the State. Contractor will obtain formal approval of successful completion of UAT, to include resolution to all critical and high defects. Final UAT must occur within the State operating environment.

System Documentation As needed, the contractor will work with GRMD to update the existing RBDMS data dictionary and all necessary SOM project documentation to properly detail modifications required for this project.

Implementation Starting during the construction activities, Contractor will initiate implementation planning for each release to include confirmation of the implementation schedule and detailed installation plan.

Consideration of existing maintenance schedules and business impact will be considered. In addition, starting with the construction activities, Contractor will provide support to GRMD trainers during the development of training plans and training materials for each release. The contractor will

Version 2021-1 4 of 9 obtain formal approval of all associated training materials and installation plan(s). Upon successful completion of UAT, DTMB, in partnership with Contractor, will complete activities in the implementation plan.

eMichigan ADA, Look and Feel Standards Compliance Contractor will support activities to confirm new functionality and screens associated with scope of work complies with eMichigan ADA and COTS “Look and Feel” standards. This will include provisions related to design documents to eMichigan, as well as support of system overview discussions with eMichigan. Contractor must address all noncompliance issues – any previously identified and adherence to Web Content Accessibility Guidelines (WCAG) 2.1AA (or better) standards.

System Security Plan (Keylight) The contractor will partner with DTMB to answer questions and provide all requested supporting documentation to complete the System Security Plan (SSP) for the RBDMS suite of applications.

Warranty The contractor will provide warranty support to resolve any Critical and High issues discovered in the 60 calendar days following acceptance of the final production implementation.

Project Close-Out The contractor will schedule and facilitate a close-out meeting with the State to include the Agency Project Manager, DTMB Technical Owner, and associated project staff. The objective of the meeting is to confirm all project activities have been completed and related artifacts have been provided to the State. If applicable, open action items, risks, and issues will be reviewed. The Contractor will issue meeting notes from the meeting.

PROJECT MILESTONES & TIMELINES:

The tables below contain the anticipated dates for each milestone for services in this statement of work. The approved project schedule will be generated during the Project Planning milestone and will contain a finalized set of milestones and their planned delivery dates. While the timeline is being extended, the average allocation for DTMB resources to complete the required tasks would also be adjusted accordingly to align with the schedule and implementation cycles.

Table 1- MiSTAR APD and Security Updates Permitting Project Milestones

Deliverable: Milestone: Delivery Date:

1 Project Planning + -

Updated Project Schedule 2/3/2025

2 Develop and Configure Application for Permit to Drill

EDD +

2.A Software Designs 3/12/2025

Version 2021-1 5 of 9

2.B Vendor Environment UAT Complete 5/9/2025

3 Checklist of Permit Associated Agency Tasks +

3.A Software Designs 3/12/2025

3.B Vendor Environment UAT Complete 5/9/2025

4 Develop downloadable Application for Permit to Drill form +

4.A Software Designs 4/16/2025

4.B Vendor Environment UAT Complete 6/25/2025

5 Develop downloadable final Permit approved form +

5.A Software Designs 4/16/2025

5.B Vendor Environment UAT Complete 6/25/2025

5.C Build & Delivery for SOM Install 6/27/2024

6 Data migration to MIRBDMSNET +

6.A Software Designs 4/16/2025

6.B Vendor Environment UAT Complete 6/25/2025

7 MiSTAR Product Enhancements

7.A Software Designs 9/2/2025

7.B Vendor Environment UAT Complete 9/24/2025

8 Release 1 ADA and Security Scan Items

8.A Build & Delivery for SOM Install

9/26/2025

8.B Scans Completed/Results Returned to Vendor

(SOM Task) *

10/10/2025

8.C Fixed Build Delivery 10/24/2025

8.D Rescan Completed (SOM Task) * 11/7/2025

9 MiSTAR Release 1 Support

9.A Final UAT / Acceptance by SOM 11/10/2025

Version 2021-1 6 of 9

9.B Document Delivery 11/10/2025

9.C Production Install in SOM Environment (SOM Task) * 12/8/2025

10 Login/Account integration with MiLogin

10.A Software Designs 10/3/2025

10.B Vendor Environment UAT Complete 10/31/2025

11 Release 2 ADA and Security Scan Items

11.A Build & Delivery for SOM Install 11/4/2025

11.B Scans Completed/Results Returned to Vendor (SOM Task)

11/18/2025

11.C Fixed Build Delivery 12/2/2025

11.D Rescan Completed (SOM Task) 12/16/2025

12 MiSTAR Release 2 Support

12.A Final UAT / Acceptance by SOM 12/16/2025

12.B Document Delivery 12/16/2025

12.C Production Install in SOM Environment (SOM Task) 1/7/2026

13 Warranty & Holdback

14 60 Day Warranty Period 3/8/2026

“+” = Project Milestones already completed

* SOM Task = represents items that are dependencies but is not a vendor deliverable. These are not tied to payment milestones for the vendor.

ACCEPTANCE CRITERIA:

No change from existing contract.

PROJECT CONTROLS & REPORTS:

SPECIFIC DEPARTMENT STANDARDS:

Version 2021-1 7 of 9

Table 2 - Payment Milestones & Timelines:

The table below contains the target dates for each milestone. The approved project schedule will contain the agreed upon dates for each milestone. *Payment milestones in Table 2 are tied to State acceptance of MiStar APD and Security Updates milestones outlined in Table 1. Target submit/delivery dates align between the two tables.

Title: Payment Amount:

Submission Date

(Target):

Approve Date

(Target):

Payment Milestone 1 –

Deliverables: 1, 2.A, 3.A + $14,959 3/12/2025 3/19/2024

Payment Milestone 2 –

Deliverables: 4.A, 5.A, 6.A + $20,793 4/16/2025 4/23/2025

Payment Milestone 3 –

Deliverables: 2.B, 3.B + $20,793 8/1/2025 8/8/2025

Payment Milestone 4 –

Deliverables: 4.B, 5.B, 5.C, 6.B + $23,238 8/18/2025 8/25/2025

Payment Milestone 5 –

Deliverables: 7.A, 7.B, 8.A, 8.C $19,946 10/24/2025 10/31/2025

Payment Milestone 6 –

Deliverables: 8.D, 9.A, 9. B $10,023 11/10/2025 11/17/2025

Payment Milestone 7 –

Deliverables: 10.A, 10.B $27,452 10/31/2025 11/7/2025

Payment Milestone 8 –

Deliverables: 11.A, 11.C, 11.D, 12.A, 12.B $10,085 12/16/2025 12/19/2025

Payment Milestone 9 –

Deliverables: 10 (Warranty & Holdback) $12,195 3/9/2026 3/13/2026

TOTAL $159,484

“+” = Project Milestone payments already completed

Version 2021-1 8 of 9

Cost Summary:

Title: MiSTAR APD and MiLogin Integration Cost:

Sub Total $159,484

10% Contingency $15,948

TOTAL $175,432

PAYMENT SCHEDULE:

No change from the existing contract.

CONTINGENCY BUDGET:

This SOW contains a 10% contingency budget. The use of this budget is optional at the discretion of the State and no work is to be performed by the Contractor associated with the contingency budget without being approved by both the State Agency (GRMD) and Contractor.

EXPENSES:

No change from the existing contract.

PROJECT CONTACTS:

The designated Agency Project Manager is:

Carrie Johnson Geologic Resources Management Division (EGLE) 525 W Allegan St., Lansing, MI 48933 JohnsonC112@michigan.gov 517-230-3598

The designated DTMB Project Manager is:

Jasvin Sidhu DTMB – Enterprise Portfolio Management Office (EPMO) 525 W. Allegan Street, Lansing, MI 48933 sidhuj1@michigan.gov 734-620-6797

The designated DTMB Technical Owner is:

Jeanette Clark DTMB – Agency Services: Supporting EGLE, DNR, MDARD, and DMVA ClarkJ4@michigan.gov 517-243-7381 mailto:JohnsonC112@michigan.gov mailto:sidhuj1@michigan.gov mailto:ClarkJ4@michigan.gov

Version 2021-1 9 of 9

The designated Contractor Contacts are:

Ashley Bailey Ground Water Protection Council abailey@gwpc.org

Dan Jarvis djarvis@gwpc.org

The designated Sub-contractor Contacts are:

Alex Code Line 45, LLC acode@lin-45.com mailto:abailey@gwpc.org mailto:djarvis@gwpc.org mailto:acode@lin-45.com

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

Phase 2 of Dev & Maint Risk Data Management System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

October 25, 2016 October 25, 2021 5 - 12 Months October 25, 2026

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

13308 N. MacArthur Blvd.

Oklahoma City OK 73142

Dan Yates

405-516-4972 dyates@gwpc.org

CV0062466

GROUND WATER PROTECTION

COUNCIL

C O

N

TR

A C

TO

R

Jarrod Barron

(517) 249-0406

DTMB

Various Various

BarronJ1@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Change Notice Number 10

Contract Number MA071B7700011C 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,750,206.00 $0.00 $1,750,206.00

DESCRIPTION

Effective 6/16/2025, the parties add the attached GRMD RBDMS Desktop Security Remediation and Content Manager Updates statement of work, using existing contract funding. All other terms, conditions, specifications and pricing remain the same. Per Contractor, agency, and DTMB Central Procurement approval.

EGLE Adam Wygant 517-897-4828 wyganta@michigan.gov

Program Managers for

CHANGE NOTICE NO. 10 TO CONTRACT NO. MA071B7700011C

STATEMENT OF WORK -

IT CHANGE NOTICE

GRMD RBDMS Desktop Security Remediation and Content Manager Updates

Period of Coverage:

Nov 2024 through Nov 2026

Requesting Department(s):

Environment, Great Lakes and Energy (EGLE) Geologic Resources Management Division (GRMD)

Date:

3/31/2025

Agency Project Manager:

Rebecca Rea

Phone:

517-449-9195

DTMB Program Manager:

Laura Brancheau

Phone:

517-618-9646

Brief Description of Services to be provided:

As part of contract 071B7700011 with the Ground Water Protection Council (GWPC), GWPC provides maintenance of, and enhancements to, the Risk Based Data Management System (RBDMS). Under this Statement of Work (SOM), the Environment, Great Lakes, and Energy (EGLE) Geologic Resources Management Division (GRMD), is requesting updates to the RBDMS Desktop application and Content Manager (CM) API to remediate security risks and reflect the recent name change of the division.

Background:

The Geologic Resources Management Division (GRMD) utilizes the RBDMS Desktop application and Content Manager (CM) for the management of agency data. In association with the Ground Water Protection Council (GWPC), GRMD is proposing this project to remediate the critical, high and medium level security items identified in the Software Risk Manager Assessment Report dated 9/17/2024 provided by the Michigan Department of Technology, Management and Budget (DTMB). Additionally, this project will address updates to the Content Manager API connection delivering files to both the RBDMS Desktop and Dataminer Applications. The CM portion of this proposal includes updating URL paths, naming conventions and labels, and ensuring that the API can be used as intended. Post-install scan remediation support will also be included in this project. This project will be performed on a fixed price basis as detailed in the Payment Schedule section of this SOW.

Project Objective:

Address RBDMS Desktop Application security risks outlined in the Software Risk Manager Assessment Report and update Content Manager API components, including those within Dataminer and the Desktop Applications. Much of the work for both items will include updating vulnerable and outdated components, folder-related updates and authentication refactorization.

Scope of Work:

The Ground Water Protection Council (referred to as the “Contractor”) will provide services and complete activities in support of meeting the project objectives.

Project scope includes developing and/or implementing the following functionality:

• Remediation of RBDMS.NET WPF scan results for critical, high and medium-status items

• CM updates

• CM authentication refactorization

• Post-install scan remediation

1. Remediation of RBDMS Desktop Application Scans Vulnerable and outdated components within RBDMS Desktop Application and the CM API will be addressed.

High status items include updating the API .NET Core of CM from 2.1 to 8 and updating the dependent libraries, addressing issues with Path Traversal and reviewing the CM API SearchController. Medium status items include the previously mentioned .NET Core update, updating the CMAPI to the latest compatible version of newtonsoft.json and updating SQL Client version used in the CM API.

2. CM Folder-Related Updates This update is in response to the renaming of the division from OGMD to GRMD. It includes updating URL paths and naming conventions and labels, along with other items to ensure the newly updated CM API runs properly from the WPF Desktop application. Many of these updates will address issues with the risk items noted in the WPF Assessment Report scans.

3. CM Authentication Refactorization This will update the way the RBDMS CM API connects to CM. The new connection method will use HttpClient and follow examples provided by DTMB staff.

4. Post-install scan remediation After the remediation and updates to the programs are complete, they will be re-scanned by DTMB. Any issues found by the scans will be remediated by the contractor per DTMB’s security specifications.

Task(s):

o Project Planning Contractor will adhere to mutually agreed SUITE project tailoring documentation and will perform the activities listed below.

o Project Initiation Following the SUITE project tailoring, Contractor will initiate services by scheduling and facilitating a project kick-off meeting. The objective of the meeting will be to review the overall project schedule, tasks, deliverables, and expectations of project personnel. Contractor will issue meeting notes, project roster and as appropriate, an updated project schedule.

o Project Schedule The Project Schedule will include a project timeline, tasks, and responsible parties for each task. The goal of the project schedule is to provide a clear picture of expectations for the Contractor, GRMD and DTMB.

Each stakeholder will use this to make sure staff are available to complete tasks within the specified timeline.

o Requirements Validation Following the kick-off meeting, Contractor will review the existing requirements and preliminary screen designs and complete validation activities to ensure complete documentation in support of the scope of work. Contractor will obtain formal approval of the resulting updated documents.

o Design Referencing the approved requirements, Contractor will complete activities to develop and maintain appropriate design documentation. Content related to user interface (UI) design, system architecture, data modeling and integration specifications will all need to be accounted for. Contractor will obtain formal approval of the resulting design documentation. As appropriate for the development methodology and project schedule, this task may be done in iterations / Sprints.

o Construction In accordance with the approved design documentation, the Contractor will complete construction activities. These are expected to include code development, peer reviews, and appropriate testing for the scope of work and schedule (i.e., unit testing, system testing, etc.). As appropriate for the development methodology and project schedule, this task may be done in iterations / Sprints.

o Testing In preparation for each release, the Contractor will complete and/or participate in release testing to include QA review, system test, and integration test.

a. Contractor will present test results and obtain formal approval of the resulting test results and resolutions.

b. Prior to the start of UAT for the release, the Contractor will submit the code for the developed functionality to DTMB for conducted security scans. Contractor will remediate issues identified for all new system components, answer questions from DTMB regarding the Key Light security plan, and validation of adherence to eMichigan ADA and Commercial-off-the-shelf (COTS) Look and Feel standards. Services and deliverables must comply with State Unified IT Environment (SUITE).]

c. User Acceptance Testing (UAT): Contractor will support the planning and execution of UAT for each release with the State. Contractor will obtain formal approval of successful completion of UAT, to include resolution to all critical and high defects. Final UAT must occur within the State operating environment.

o System Documentation As needed, contractor will work with GRMD to update the existing RBDMS data dictionary and all necessary SOM project documentation to properly detail modifications required for this project.

o Implementation Starting during the construction activities, Contractor will initiate implementation planning for each release to include confirmation of the implementation schedule and detailed installation plan.

Consideration for existing maintenance schedules and business impact will be considered. In addition, starting with the construction activities, Contractor will provide support to GRMD trainers during the development of training plans and training materials for each release. Contractor will obtain formal approval of the resulting installation plan. Upon successful completion of UAT, Contractor will complete activities in the implementation plan.

o eMichigan ADA, Look and Feel Standards Compliance Contractor will support activities to confirm new functionality and associated screens associated with scope of work complies with eMichigan ADA and COTS “Look and Feel” standards. This will include provisions to related design documents to eMichigan, as well as support of system overview discussions with eMichigan. Contractor must address all noncompliance issues – any previously identified and adherence to Web Content Accessibility Guidelines (WCAG) 2.1AA (or better) standards.

o System Security Plan (Keylight)

Contractor will partner with DTMB to answer questions and provide all requested supporting documentation in order to complete the System Security Plan (SSP) for the RBDMS suite of applications.

o Warranty Contractor will provide warranty support to resolve any Critical and High issue(s) discovered in the 60 calendar days following implementation of a Production environment release.

o Project Close-Out

Contractor will schedule and facilitate a close-out meeting with the State to include the Agency Project Manager, DTMB Technical Owner, and associated project staff. The objective of the meeting is to confirm all project activities have been completed and related artifacts have been provided to the State. If applicable, open action items, risks, and issues will be reviewed. The Contractor will issue meeting notes from the meeting.

Project Milestones & Timelines:

The table below contains the anticipated dates for each milestone. The approved project schedule will contain the agreed upon dates for each milestone.

Deliverabl e: Milestone: Delivery Date:

1 Updated Project Schedule 4/01/2025 2 RBDMS Desktop Application Remediation 7/15/2025 3 Content Manager API Remediation 7/15/2025 4 Initial Build Delivery and EGLE UAT

4A Build Delivery to DTMB 7/15/2025 4B Initial Install into UAT 8/1/2025 4C DTMB Scans Completed and Returned to Vendor 8/15/2025 4D EGLE Initial UAT Complete 8/20/2025

5 Post Install Scan Remediation 5A Post Install Scan Remediation 9/1/2025 5B Resolve EGLE Testing Feedback 9/1/2025 5C Final Build Delivery to DTMB 9/1/2025

6 Final Release Support 6A Final UAT / Acceptance by SOM 9/15/2025 6B Document Delivery 9/1/2025 6C Production Install in SOM Environment 10/1/2025

7 Warranty & Holdback 60 Day Warranty Period

Table 1-RBDMS Desktop Application and CM Update Project Milestones

Deliverables:

Deliverables will not be considered complete until the Agency Project Manager and DTMB Project Manager have formally accepted them. Deliverables will comply with SUITE. Deliverables will be delivered in conjunction with the milestones defined above and grouped as follows. Since the scope of this project is relatively small, each of the milestones includes deliverables for all the scope described in the Scope of Work section.

• Project Schedule

Software Designs

• Updated Use Cases & Requirements

• Design Documentation – as required

Software Build & Delivery

• Updated System Documentation

• Updated Installation Plan(s)

• System Test Report – as required

• Compiled Code Delivery

UAT Acceptance

• User Acceptance Test (UAT) Report – as required

• Compiled Code Delivery

Document Delivery

• Technical Documentation – as required

Acceptance Criteria:

Project Controls & Reports:

No change from existing contract.

Specific Department Standards:

No change from existing contract.

Payment Milestones & Timelines:

The table below contains the target dates for each milestone. The approved project schedule will contain the agreed upon dates for each milestone.

*Payment milestones in Table 2 are tied to milestones outlined in Table 1. Target submit/delivery dates align between the two tables.

Title: Payment Amount:

Submit Date (Target):

Approve Date

(Target):

Payment Milestone 1 – Deliverable: 2 68,100 7/15/2025 8/1/2025

Payment Milestone 2 – Deliverable: 3 30,800 7/15/2025 8/1/2025

Payment Milestone 3 – Deliverable: 4A 4,900 7/15/2025 8/1/2025

Payment Milestone 4 – Deliverables: 5A, 5B, 5C 20,400 9/1/2025 9/15/2025 Payment Milestone 5 - Deliverables: 6A, 6B, 6C 8,100 10/1/2025 10/15/2025 Payment Milestone 6- Deliverable: 7 (Warranty and Holdback) 14,700 11/29/2025 12/15/2025

TOTAL 147,000

Table 2-MiStar Payment Milestones

Payment Schedule:

No change from existing contract.

Expenses:

No change from existing contract.

Project Contacts:

Rebecca Rea Michigan Department of Environment, Great Lakes, & Energy Geologic Resources Management Division 525 W Allegan St., Lansing, MI 48933 ReaR@michigan.gov 517-449-9195

The designated DTMB Technical Manager is:

Jeanette Clark clarkj4@michigan.gov

(517) 335-3362

Ashley Bailey

Adria Hash Coordinate Solutions ahash@coordinatesolutions.com

Agency Responsibilities:

Location Of Where Work Is to Be Performed:

Contractor is responsible for providing web conference and audio conference tools as needed to support remote working locations.

Contractor will utilize the State’s development and testing environments. Contractor will have access to deploy the software in the State’s development environment. The Contractor will provide instructions to the State for deployment into the State’s QA environment and provide support, as necessary. VPN access by the contractor will be set up for these activities. All final User Acceptance Testing (UAT) must take place within the State’s Quality Assurance (QA) environment.

Expected Contractor Work Hours and Conditions:

No change from existing contract.

Defect Severity and Priority:

No change from existing contract.

mailto:ReaR@michigan.gov mailto:clarkj4@michigan.gov

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

Phase 2 of Dev & Maint Risk Data Management System

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

October 25, 2016 October 25, 2021 5 - 12 Months October 25, 2026

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

13308 N. MacArthur Blvd.

Oklahoma City OK 73142

Dan Yates

405-516-4972 dyates@gwpc.org

CV0062466

GROUND WATER PROTECTION

COUNCIL

C O

N

TR

A C

TO

R

Jarrod Barron

517-249-0406

DTMB

Various Various

BarronJ1@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Change Notice Number 9

Contract Number MA071B7700011C 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,616,060.00 $134,146.00 $1,750,206.00

DESCRIPTION

Effective 12/13/2024, the parties add $134,146.00 for the RBDMS Suite enhancement services detailed in the attached statement of work. All other terms, conditions, specifications and pricing remain the same.

Per Contractor, agency, and DTMB Central Procurement approval.

Internal State Note: Remaining Ad Board funds after this change: $62,853.99

EGLE Adam Wygant 517-897-4828 wyganta@michigan.gov

Program Managers for

CHANGE NOTICE NO. 9 TO CONTRACT NO. MA071B7700011C

MICHIGAN DEPARTMENT OF TECHNOLOGY,

MANAGEMENT AND BUDGET

IT SERVICES

STATEMENT OF WORK

GRMD MiSTAR Permitting Component and Security Upgrades

Period of Coverage:

Nov 2024 through Nov

Requesting Department(s):

Environment, Great Lakes and Energy (EGLE) Geologic Resources Management Division (GRMD)

Date:

11/15/2024

Agency Project Manager:

Carrie Johnson

517-230-3598

DTMB Technical Owner:

Londa Wilkes

517-749-6249 maintenance of, and enhancements to, the Risk Based Data Management System (RBDMS). Under this Statement of Work (SOM), the Environment, Great Lakes, and Energy (EGLE) Geologic Resources Management Division (GRMD), are requesting enhancements to the RBDMS Suite to replace the current permitting e-file system (EForms) from older technology to a modernized web-based platform integrated with their other e-file system (MiSTAR).

Background:

The current oil and gas well permitting system used for submitting permit requests is a web-based application named EForms. Once the files are received, edited and approved through this system, the data is pushed to the main MIRBDMSNET databases. The proposed project would allow us to retire the older technology used with Eforms and integrate this application into an already existing part of our system (MiSTAR). It will also include integration of the MiSTAR application with the MiLogin security application instead of using a separate security protocol.

In association with the Ground Water Protection Council (GWPC), the Geologic Resources Management Division (GRMD) is proposing to implement and utilize the latest technology to ensure compliance with both state and federal requirements and upgrade the existing system. These updates will support the necessary requirements for collecting data, overall data management, compliance tracking, and report generation. This project will be performed on a fixed price basis as detailed in the Payment Schedule section of this SOW.

Project Objective:

Utilize the existing GRMD MiSTAR web application to allow operators to electronically file permit application related data. This system would allow the GRMD staff to review and approve/reject submittals, and to analyze and track the submitted data. Additional objectives include the transfer of data submitted electronically to the main MIRBDMSNET database and the creation of reports/printouts associated with permit applications and approvals.

Scope of Work:

The Ground Water Protection Council (referred to as the “Contractor”) will provide services and complete activities in support of meeting the project objectives.

Project scope includes developing and/or implementing the following functionality:

• Login/ Account & Permissions (Agency, Operator and Public) integration with MiLogin

• Application for Permit to Drill EDD Template

• Checklist of Permit Associated Agency tasks for tracking application progress

• Data Migration to MIRBDMSNET Database

• Develop downloadable/printable Application for Permit to Drill form (EQ 7200-01) and the final

Permit approved form

1. Login / Account & Permissions Management The current application already utilizes a tool to manage logins, accounts & permissions. Update tool to integrate with MiLogin.

2. Develop & Configure Application for Permit to Drill EDD Template The EDD will allow operators to submit an application for Permit to Drill (APD) utilizing a format that operators are familiar with. This template will include fields for collecting all of the current data collected in Eforms. It will also include an option to fill out the form online without using the template.

3. Checklist of Permit Associated Agency tasks This web application will allow the agency to track permit associated review tasks for tracking and compliance purposes.

4. Develop downloadable/printable Application for Permit to Drill form(s) This webpage(s) will allow the GRMD staff to view and print/download application data in a format like the Application for Permit to Drill form for Operator use and record keeping purposes.

5. Data Migration to MIRBDMSNET This would migrate data from MiSTAR APD forms related tables to MIRBDMSNET.

Contractor will adhere to mutually agreed SUITE project tailoring documentation and will perform the activities listed below.

o Project Initiation Following the SUITE project tailoring, Contractor will initiate services by scheduling and facilitating a project kick-off meeting. The objective of the meeting will be to review the overall project schedule, tasks, deliverables, and expectations of project personnel. Contractor will issue meeting notes, project roster and as appropriate, an updated project schedule.

o Project Schedule The Project Schedule will include a project timeline, tasks, and responsible parties for each task. The goal of the project schedule is to provide a clear picture of expectations for the Contractor, GRMD and DTMB. Each stakeholder will use this to make sure staff are available to complete tasks within the specified timeline.

o Requirements Validation screen designs and complete validation activities to ensure complete documentation in support of the scope of work. Contractor will obtain formal approval of the resulting updated documents.

o Design Referencing the approved requirements, Contractor will complete activities to develop and maintain appropriate design documentation. Content related to user interface (UI) design, system architecture, data modeling and integration specifications will all need to be accounted for. Contractor will obtain formal approval of the resulting design documentation. As appropriate for the development methodology and project schedule, this task may be done in iterations / Sprints.

o Construction In accordance with the approved design documentation, the Contractor will complete construction activities. These are expected to include code development, peer reviews, and appropriate testing for the scope of work and schedule (i.e., unit testing, system testing, etc.). As appropriate for the development methodology and project schedule, this task may be done in iterations / Sprints.

o Testing In preparation for each release, the Contractor will complete and/or participate in release testing to include QA review, system test, and integration test.

a. Contractor will present test results and obtain formal approval of the resulting test results and resolutions.

b. Prior to the implementation / migration of each UAT release that will be performed in the State operating environment, the Contractor will submit the code for the developed functionality to DTMB for conducted security scans. Contractor will remediate issues identified for all new system components, answer questions from DTMB regarding the System Security Plan (SSP), and validation of adherence to eMichigan ADA and Commercial-off-the-shelf (COTS) Look and Feel standards. Services and deliverables must comply with State Unified IT Environment (SUITE).

c. User Acceptance Testing (UAT): Contractor will support the planning and execution of UAT for each release with the State. Contractor will obtain formal approval of successful completion of UAT, to include resolution to all critical and high defects. Final UAT must occur within the State operating environment.

o System Documentation As needed, contractor will work with GRMD to update the existing RBDMS data dictionary and all necessary SOM project documentation to properly detail modifications required for this project.

o Implementation Starting during the construction activities, Contractor will initiate implementation planning for each release to include confirmation of the implementation schedule and detailed installation plan.

Consideration for existing maintenance schedules and business impact will be considered. In addition, starting with the construction activities, Contractor will provide support to GRMD trainers during the development of training plans and training materials for each release. Contractor will obtain formal approval of all associated training materials and installation plan(s). Upon successful completion of UAT, DTMB, in partnership with Contractor, will complete activities in the implementation plan.

o eMichigan ADA, Look and Feel Standards Compliance Contractor will support activities to confirm new functionality and associated screens associated with scope of work complies with eMichigan ADA and COTS “Look and Feel” standards. This will include provisions to related design documents to eMichigan, as well as support of system overview discussions with eMichigan. Contractor must address all noncompliance issues – any previously identified and adherence to Web Content Accessibility Guidelines (WCAG) 2.1AA (or better) standards.

System Security Plan (Keylight)

Contractor will partner with DTMB to answer questions and provide all requested supporting documentation in order to complete the System Security Plan (SSP) for the RBDMS suite of applications.

o Warranty Contractor will provide warranty support to resolve any Critical and High issue(s) discovered in the 60 calendar days following acceptance of the final production implementation.

o Project Close-Out Contractor will schedule and facilitate a close-out meeting with the State to include the Agency Project Manager, DTMB Technical Owner, and associated project staff. The objective of the meeting is to confirm all project activities have been completed and related artifacts have been provided to the State. If applicable, open action items, risks, and issues will be reviewed. The Contractor will issue meeting notes from the meeting.

The tables below contain the anticipated dates for each milestone. The approved project schedule will be generated during the Project Planning milestone and will contain a finalized set of milestones and their planned delivery dates.

1 Project Planning - Updated Project Schedule 2/3/2025 2 Develop and Configure Application for Permit to Drill EDD

2.A Software Designs 3/12/2025 2.B Vendor Environment UAT Complete 5/9/2025

3 Checklist of Permit Associated Agency Tasks

3.A Software Designs 3/12/2025 3.B Vendor Environment UAT Complete 5/9/2025

4 Develop downloadable Application for Permit to Drill form 4.A Software Designs 4/16/2025 4.B Vendor Environment UAT Complete 6/25/2025

5 Develop downloadable final Permit approved form 5.A Software Designs 4/16/2025 5.B Vendor Environment UAT Complete 6/25/2025 5.C Build & Delivery for SOM Install 6/27/2025

6 Data migration to MIRBDMSNET 6.A Software Designs 4/16/2025 6.B Vendor Environment UAT Complete 6/25/2025

7 Login/Account integration with MiLogin 7.A Software Designs 5/7/2025 7.B Vendor Environment UAT Complete 7/25/2025

8 ADA and Security Scan Items 8.A Build & Delivery for SOM Install 7/29/2025 8.B Scans Completed/Results Returned to Vendor 8/19/2025 8.C Fixed Build Delivery 9/2/2025 8.D Rescan Completed 9/16/2025

9 MiSTAR Release Support 9.A Final UAT / Acceptance by SOM 9/17/2025 9.B Document Delivery 9/17/2025 9.C Production Install in SOM Environment 12/1/2025

10 Warranty & Holdback 60 Day Warranty Period 1/30/2026

Table 1- MiSTAR Permitting Project Milestones

Deliverables will not be considered complete until the Agency Project Manager and DTMB Project Manager have formally accepted them. Deliverables will comply with SUITE. Deliverables will be delivered in conjunction with the milestones defined above and grouped as follows. Since the scope of this project is relatively small, each of the milestones includes deliverables for all the scope described in the Scope of Work section.

Software Designs

• User Stories & Requirements

• Defects / Bug Resolution

• Design Documentation

Software Build & Delivery

• Updated System Documentation

• Updated Installation Plan(s)

• System Test Report

• Compiled Code Delivery

• Source Code

Paired / accompanying UAT builds

• UAT build

UAT Acceptance

• User Acceptance Test (UAT) Report

• Defects / Bug Reporting

• Compiled Code Delivery

• Technical Documentation, data dictionary updates for GRMD

Project Controls & Reports:

No change from existing contract.

Specific Department Standards:

No change from existing contract.

Payment Milestones & Timelines:

The table below contains the target dates for each milestone. The approved project schedule will contain the agreed upon dates for each milestone.

*Payment milestones in Table 2 are tied to MiStar APD and Security Updates milestones outlined in Table 1.

Target submit/delivery dates align between the two tables.

Title:

Payment Amount:

Submit Date (Target):

Approve Date (Target):

Payment Milestone 1 – Deliverables: 1, 2.A, 3.A $14,959 3/12/2025 3/19/2024

Payment Milestone 2 – Deliverables: 4.A, 5.A, 6.A $20,793 4/16/2025 4/23/2025

Payment Milestone 3 - Deliverables: 2.B, 3.B, 7.A $20,793 5/9/2025 5/16/2025

Payment Milestone 4 - Deliverables: 4.B, 5.B, 5.C, 6.B $23,238 6/27/2025 7/7/2025 Payment Milestone 5 - Deliverables: 7.B, 8.A, 8.B, 8.C, 8.D

$19,946 9/16/2025 9/23/2025

Payment Milestone 6 – Deliverables: 9.A, 9.B, 9.C $10,023 12/1/2025 12/8/2025 Payment Milestone 7 – Deliverables: 10 (Warranty & Holdback)

$12,195 1/30/2025 2/6/2025

TOTAL $121,946

Table 2- MiSTAR Permitting Payment Milestones

*Proposed Holdback with each milestone (5-10%) that will encompass final payment once confirmation of successful deliverables

Title: MiSTAR APD and MiLogin Integration Cost:

Sub Total $121,946

10% Contingency $12,200

TOTAL $134,146

Payment Schedule:

Contingency Budget:

This SOW contains a 10% contingency budget. The use of this budget is optional at the discretion of the State and no work is to be performed by the Contractor associated with the contingency budget without being approved by both the State Agency (GRMD) and Contractor.

Expenses:

No change from existing contract.

Geologic Resources Management Division 525 W Allegan St., Lansing, MI 48933 JohnsonC112@michigan.gov

The designated DTMB Technical Owner is:

IT Manager State of Michigan - DTMB – Agency Services: Supporting EGLE, DNR, MDARD, and DMVA Constitution Hall, 1st Floor, North Tower WilkesL1@michigan.gov 517-930-8372

Ashley Bailey acode@line-45.com

Location Of Where Work Is To Be Performed:

No change from existing contract.

Expected Contractor…