2200137.pdf

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

Telecom Billing System Main & Support

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

March 7, 2012 March 6, 2015 2 - 12 Months March 6, 2025

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

P-Card Direct Voucher (PRC) Other Yes No

911 N. Division Ave.

Suite B

Grand Rapids MI 49503-1401

Steve Schafer

616-477-9629

Steve@matsch.com

CV0026172

MATSCH FINANCIAL SYSTEMS LTD

C O

N

TR

A C

TO

R

517-241-5054

Feguerr@michigan.gov

Brandon Samuel

(517) 249-0439

DTMB

Rob Feguer DTMB

SamuelB@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Change Notice Number 13

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

60 Months March 6, 2030

$10,670,395.41 $1,564,312.74 $12,234,708.15

DESCRIPTION

Effective January 29, 2025, this Contract is exercising 5-1 year options (that was added under CN 9) and is increased by $1,564,312.74 for software and services required to continue maintenance and support of NET-Phacs Service for DHHS Offices (Sites). The revised expiration date March 6, 2030.

Additionally, attached is a corrected pricing table (only regarding DHHS Net-Phacs Service) that supersedes the pricing table incorporated in CN 9 (the subtotal for option year 2025 incorrectly stated $303,095.53 instead of $303,085.53). Also a Federal Provision Addendum has been incorporated.

Furthermore, the State Contract Administrator has been changed to Brandon Samuel.

All other terms, conditions, specifications and pricing remain the same. Per contractor and agency agreement, and DTMB Central Procurement Services approval, and State Administrative Board approval on January 28, 2025.

DHHS-NET-Phacs Service

(4/1/25 - 3/31/26)

(4/1/26 - 3/31/27)

(4/1/27 - 3/31/28)

(4/1/28 - 3/31/29)

(4/1/29 - 3/31/30) Basic Services for DHHS Offices (Sites) $239,585.53 $244,377.24 $249,264.79 $254,250.09 $259,335.09 Cellular CDR $17,000.00 $17,000.00 $17,000.00 $17,000.00 $17,000.00 Cellular Reporting $46,500.00 $46,500.00 $46,500.00 $46,500.00 $46,500.00 Subtotal for NET-Phacs $303,085.53 $307,877.24 $312,764.79 $317,750.09 $322,835.09

Mich igan .gov/MiProcure ment

Version 2024-2 Page 1

FEDERAL PROVISIONS ADDENDUM

This addendum applies to purchases that will be paid for in whole or in part with funds obtained from the federal government. The provisions below are required, and the language is not negotiable. Contractor agrees to comply with all obligations under federal rules or regulations for such funding, including but not limited to the provisions contained in this addendum. If any provision below conflicts with the State’s terms and conditions, including any attachments, schedules, or exhibits to this Contract, the provisions below take priority to the extent a provision is required by federal law; otherwise, the order of precedence set forth in the Contract applies.

Further, Contractor agrees to, through a Contract Change Notice, append or modify specific federal provisions to this Contract, if reasonably necessary to keep the State and Contractor in compliance with federal funding requirements, and comply with the terms set forth therein.

Hyperlinks are provided for convenience only; broken hyperlinks will not relieve Contractor from compliance with the law.

A. Equal Employment Opportunity

This Contract is not a “federally assisted construction contract” as defined in 41 CFR Part 60-1.3.

B. Davis-Bacon Act (Prevailing Wage)

This Contract is not a “federally assisted construction contract” as defined in 41 CFR Part 60- 1.3, nor is it a prime construction contract in excess of $2,000.

C. Copeland “Anti-Kickback” Act

This Contract is not a “federally assisted construction contract” as defined in 41 CFR Part 60- 1.3, nor is it a prime construction contract in excess of $2,000 where the Davis-Bacon Act applies.

D. Contract Work Hours and Safety Standards Act

The Contract does not involve the employment of mechanics or laborers.

E. Rights to Inventions Made Under a Contract or Agreement

If this Contract is funded by a federal “funding agreement” as defined under 37 CFR §401.2 (a) and the recipient or subrecipient wishes to enter into a contract with a small business firm or nonprofit organization regarding the substitution of parties, assignment or performance of experimental, developmental, or research work under that “funding agreement,” the recipient or subrecipient must comply with 37 CFR Part 401, “Rights to Inventions Made by Nonprofit Organizations and Small Business Firms Under Government Grants, Contracts and Cooperative Agreements,” and any implementing regulations issued by the awarding agency.

F. Clean Air Act and the Federal Water Pollution Control Act

If this Contract is in excess of $150,000, the Contractor must comply with all applicable standards, orders, and regulations issued under the Clean Air Act (42 USC 7401-7671q) and the Federal Water Pollution Control Act (33 USC 1251-1387), and during performance of this Contract the Contractor agrees as follows:

(1) Clean Air Act https://www.govinfo.gov/content/pkg/CFR-2019-title41-vol1/pdf/CFR-2019-title41-vol1-part60.pdf https://www.govinfo.gov/content/pkg/CFR-2019-title41-vol1/pdf/CFR-2019-title41-vol1-part60.pdf https://www.govinfo.gov/content/pkg/CFR-2019-title41-vol1/pdf/CFR-2019-title41-vol1-part60.pdf https://www.govinfo.gov/content/pkg/CFR-2019-title41-vol1/pdf/CFR-2019-title41-vol1-part60.pdf https://www.govinfo.gov/content/pkg/CFR-2019-title41-vol1/pdf/CFR-2019-title41-vol1-part60.pdf https://www.govinfo.gov/content/pkg/CFR-2019-title41-vol1/pdf/CFR-2019-title41-vol1-part60.pdf https://www.govinfo.gov/content/pkg/CFR-2019-title37-vol1/pdf/CFR-2019-title37-vol1-sec401-2.pdf https://www.govinfo.gov/app/details/CFR-2019-title37-vol1/CFR-2019-title37-vol1-part401 https://www.govinfo.gov/app/details/USCODE-2018-title42/USCODE-2018-title42-chap85 https://www.govinfo.gov/app/details/USCODE-2018-title33/USCODE-2018-title33-chap26

Version 2024-2 Page 2

(i) The Contractor agrees to comply with all applicable standards, orders or regulations issued pursuant to the Clean Air Act, as amended, 42 U.S.C. § 7401 et seq.

(ii) The Contractor agrees to report each violation to the State and understands and agrees that the State will, in turn, report each violation as required to assure notification to the Federal Emergency Management Agency or the applicable federal awarding agency, and the appropriate Environmental Protection Agency Regional Office.

(iii) The Contractor agrees to include these requirements in each subcontract exceeding $150,000 financed in whole or in part with Federal assistance provided by FEMA or the applicable federal awarding agency.

(2) Federal Water Pollution Control Act

(i) The Contractor agrees to comply with all applicable standards, orders, or regulations issued pursuant to the Federal Water Pollution Control Act, as amended, 33 U.S.C. 1251 et seq.

(ii) The Contractor agrees to report each violation to the State and understands and agrees that the State will, in turn, report each violation as required to assure notification to the Federal Emergency Management Agency or the applicable federal awarding agency, and the appropriate Environmental Protection Agency Regional Office.

(iii) The Contractor agrees to include these requirements in each subcontract exceeding $150,000 financed in whole or in part with Federal assistance provided by FEMA or the applicable federal awarding agency.

G. Debarment and Suspension

A “contract award” (see 2 CFR 180.220) must not be made to parties listed on the government-wide exclusions in the System for Award Management (SAM), in accordance with the OMB guidelines at 2 CFR 180 that implement Executive Orders 12549 (51 FR 6370; February 21, 1986) and 12689 (54 FR 34131; August 18, 1989), “Debarment and Suspension.” SAM Exclusions contains the names of parties debarred, suspended, or otherwise excluded by agencies, as well as parties declared ineligible under statutory or regulatory authority other than Executive Order 12549.

(1) This Contract is a covered transaction for purposes of 2 C.F.R. Part 180 and 2 C.F.R. Part 3000. As such, the Contractor is required to verify that none of the Contractor’s principals (defined at 2 C.F.R. § 180.995) or its affiliates (defined at 2 C.F.R. § 180.905) are excluded (defined at 2 C.F.R. § 180.940) or disqualified (defined at 2 C.F.R. § 180.935).

(2) The Contractor must comply with 2 C.F.R. Part 180, subpart C and 2 C.F.R. Part 3000, subpart C, and must include a requirement to comply with these regulations in any lower tier covered transaction it enters into.

(3) This certification is a material representation of fact relied upon by the State. If it is later determined that the contractor did not comply with 2 C.F.R. Part. 180, subpart C and 2 C.F.R. Part. 3000, subpart C, in addition to remedies available to the State, the Federal https://www.govinfo.gov/app/details/CFR-2019-title2-vol1/CFR-2019-title2-vol1-sec180-220 https://sam.gov/SAM/pages/public/index.jsf https://www.govinfo.gov/app/details/CFR-2019-title2-vol1/CFR-2019-title2-vol1-part180 https://www.archives.gov/federal-register/codification/executive-order/12549.html https://www.govinfo.gov/content/pkg/FR-1986-02-21/pdf/FR-1986-02-21.pdf https://www.govinfo.gov/content/pkg/FR-1989-08-18/pdf/FR-1989-08-18.pdf https://www.archives.gov/federal-register/codification/executive-order/12549.html https://www.archives.gov/federal-register/codification/executive-order/12549.html

Version 2024-2 Page 3

Government may pursue available remedies, including but not limited to suspension and/or debarment.

(4) The bidder or proposer agrees to comply with the requirements of 2 C.F.R. Part 180, subpart C and 2 C.F.R. Part 3000, subpart C while this offer is valid and throughout the period of any contract that may arise from this offer. The bidder or proposer further agrees to include a provision requiring such compliance in its lower tier covered transactions.

H. Byrd Anti-Lobbying Amendment, 31 U.S.C. § 1352 (as amended)

Contractor has applied or bid for an award of more than $100,000 and shall file the required certification in Exhibit 1 – Byrd Anti-Lobbying Certification attached to the end of this Addendum.

Each tier certifies to the tier above that it will not and has not used federally appropriated funds to pay any person or organization for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, officer or employee of Congress, or an employee of a Member of Congress in connection with obtaining any federal contract, grant, or any other award covered by 31 U.S.C. § 1352. Each tier shall also disclose any lobbying with non-federal funds that takes place in connection with obtaining any federal award. Such disclosures are forwarded from tier to tier up to the recipient who in turn will forward the certification(s) to the federal awarding agency.

I. Procurement of Recovered Materials

If this Contract is a procurement to purchase products or items designated by the EPA under 40 C.F.R. part 247 during the course of a fiscal year, then under 2 CFR 200.323, Contractors must comply with section 6002 of the Solid Waste Disposal Act, as amended by the Resource Conservation and Recovery Act.

(1) In the performance of this contract, the Contractor shall make maximum use of products containing recovered materials that are EPA-designated items unless the product cannot be acquired:

(i) Competitively within a timeframe providing for compliance with the contract performance schedule;

(ii) Meeting contract performance requirements; or

(iii) At a reasonable price.

(2) Information about this requirement, along with the list of EPA- designated items, is available at EPA’s Comprehensive Procurement Guidelines web site, https://www.epa.gov/smm/comprehensive- procurement-guideline-cpg-program.

(3) The Contractor also agrees to comply with all other applicable requirements of Section 6002 of the Solid Waste Disposal Act.

J. Prohibition on Contracting for Covered Telecommunications Equipment or Services

Contractor acknowledges and agrees that Section 889(b) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019, Pub. L. No. 115-232 (the “McCain Act”), and 2 C.F.R.

§200.216, prohibit the obligation or expending of federal award funds on certain telecommunication products or with certain entities for national security reasons on or after August 13, 2020.

During performance of this Contract, the Contractor agrees as follows:

https://www.ecfr.gov/current/title-40/chapter-I/subchapter-I/part-247 https://www.ecfr.gov/current/title-40/chapter-I/subchapter-I/part-247 https://www.ecfr.gov/current/title-2/subtitle-A/chapter-II/part-200/subpart-D/subject-group-ECFR45ddd4419ad436d/section-200.323 https://www.epa.gov/smm/comprehensive-procurement-guideline-cpg-program https://www.epa.gov/smm/comprehensive-procurement-guideline-cpg-program https://www.epa.gov/smm/comprehensive-procurement-guideline-cpg-program https://www.congress.gov/115/plaws/publ232/PLAW-115publ232.pdf https://www.congress.gov/115/plaws/publ232/PLAW-115publ232.pdf https://www.ecfr.gov/current/title-2/subtitle-A/chapter-II/part-200/subpart-C/section-200.216 https://www.ecfr.gov/current/title-2/subtitle-A/chapter-II/part-200/subpart-C/section-200.216

Version 2024-2 Page 4

(a) Definitions. As used in this Section J. Prohibition on Contracting for Covered Telecommunications Equipment or Services (“Section J”):

(1) the terms “backhaul,” “critical technology,” “interconnection arrangements,” “reasonable inquiry,” “roaming,” and “substantial or essential component” have the meanings defined in 48 CFR § 4.2101;

(2) the term “covered foreign country” has the meanings defined in § 889(f)(2) of the McCain Act; and

(3) the term “covered telecommunications equipment or services” has the meaning defined in § 889(f)(3) of the McCain Act.

(b) Prohibitions.

(1) Unless an exception in paragraph (c) of this Section J applies, neither the Contractor nor any of its subcontractors may use funds received under this Contract to:

(i) Procure or obtain any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology of any system;

(ii) Enter into, extend, or renew a contract to procure or obtain any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology of any system;

(iii) Enter into, extend, or renew a contract with an entity that uses any covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system; or

(iv) Provide, as part of its performance of this contract, subcontract, or other contractual instrument, any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system.

(c) Exceptions.

(1) This Section J does not prohibit Contractor from providing—

(i) A service that connects to the facilities of a third-party, such as backhaul, roaming, or interconnection arrangements; or

(ii) Telecommunications equipment that cannot route or redirect user data traffic or permit visibility into any user data or packets that such equipment transmits or otherwise handles.

(d) Reporting requirement.

(1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this Section J to the recipient or

Version 2024-2 Page 5 subrecipient, unless elsewhere in this contract are established procedures for reporting the information.

(2) The Contractor shall report the following information pursuant to paragraph (d)(1) of this Section J:

(i) Within one business day from the date of such identification or notification: The contract number; the order number(s), if applicable;

supplier name; supplier unique entity identifier (if known); supplier Commercial and Government Entity (CAGE) code (if known); brand; model number (original equipment manufacturer number, manufacturer part number, or wholesaler number); item description; and any readily available information about mitigation actions undertaken or recommended.

(ii) Within 10 business days of submitting the information in paragraph (d)(2)(i) of this Section J: Any further available information about mitigation actions undertaken or recommended. In addition, the contractor shall describe the efforts it undertook to prevent use or submission of covered telecommunications equipment or services, and any additional efforts that will be incorporated to prevent future use or submission of covered telecommunications equipment or services.

(e) Subcontracts. The Contractor shall insert the substance of this Section J, including this paragraph (e), in all subcontracts and other contractual instruments.

K. Domestic Preferences for Procurements

(a) As appropriate, and to the extent consistent with law, the Contractor should, to the greatest extent practicable, provide a preference for the purchase, acquisition, or use of goods, products, or materials produced in the United States. This includes, but is not limited to iron, aluminum, steel, cement, and other manufactured products.

(b) For purposes of this Section K – Domestic Preferences for Procurements:

(1) “Produced in the United States” means, for iron and steel products, that all manufacturing processes, from the initial melting stage through the application of coatings, occurred in the United States.

(2) “Manufactured products” mean items and construction materials composed in whole or in part of non-ferrous metals such as aluminum; plastics and polymer-based products such as polyvinyl chloride pipe; aggregates such as concrete; glass, including optical fiber; and lumber.

(c) Build America, Buy America Act (BABAA).

This Contract does not involve purchases for an infrastructure project that is subject to the domestic preference requirement in the Build America, Buy America Act.

L. Affirmative Socioeconomic Steps

For all contracts utilizing federal funding sources subject to Title 2 of the Code of Federal Regulations (C.F.R.) Part 200 issued on or after November 12, 2020, if subcontracts are to be let, the prime contractor is required to take all necessary steps identified in 2 C.F.R. § 200.321(b)(1)-(5)

Michigan .gov/MiProcure ment

Version 2024-2 Page 6 to ensure that small and minority businesses, women’s business enterprises, and labor surplus area firms are used when possible.

M. Copyright and Data Rights

Pursuant to 2 CFR § 200.315(b), the State may copyright any work which is subject to copyright and was developed, or for which ownership was acquired, under a Federal award. The Federal awarding agency reserves a royalty-free, nonexclusive and irrevocable right to reproduce, publish, or otherwise use the work for Federal purposes, and to authorize others to do so.

N. Additional FEMA Contract Provisions

This Contract does not involve purchases that will be paid for in whole or in part with funds obtained from the Federal Emergency Management Agency (FEMA).

O. Other Federal Contract Provisions

No additional federal provisions currently apply to this Contract.

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 12 to 071B2200137Contract Number

Feguerr@michigan.gov

Rob Feguer

Lauren Stempek steve@matsch.com

Steve Schafer

Grand Rapids, MI 49503-1401

MATSCH FINANCIAL SYSTEMS LTD

CV0026172

616-477-9629

911 N. Division Ave. , Suite B

(517) 243-4008 S

T A

T E

P ro g ra m

M a n a g e r

C o n tra ct

A d m in istra to r

C O

N T R A C T O

R

517-241-5054

DTMB

stempekl@michigan.gov

$10,645,287.41

March 7, 2012 March 6, 2025

TELECOM BILLING SYSTEM MAIN & SUPPORT

March 6, 2015

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

2 - 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

☐ ☐ March 6, 2025

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$25,109.00 $10,670,396.41

Effective 8/22/2022 the following SOW is hereby incorporated into this contract and the use of $25,109.00 to cover the purchase of annual maintenance work products consisting of new software, modifications to existing software, testing software, and documentation.

All other terms, conditions, specifications, and pricing remain the same. Per contractor, agency and DTMB procurement.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

CONTRACT SUMMARY

DTMB

“Where IT and Finance meet”

MATSCH SYSTEMS - 911 North Division - Grand Rapids, MI 49503

(800) 776-2367 – info@matsch.com - www.matsch.com

Statement of Work & Proposal for:

MOST Platform – OSS Delivery Services Request Automated Form

August 11, 2022

Summary: This document describes the work to be performed by Matsch Systems upon receipt of a SOM

Delivery/Purchase order. The work product will consist of new software, modifications to existing software, testing software, and documentation. All of the work to be performed will be within the scope of the Print, Mail, and

Imaging Billing application, commonly referred to as “PMI”, which is hosted on the State’s infrastructure and network.

Test Plans: Unless otherwise indicated, the testing activities described throughout this document will be performed first in Matsch’s development environment, then installed on the SOM test server where UAT testing will be completed. RFC’s will be created as needed for installation of the software on the State’s production systems, and

Matsch will perform installation in accordance with the normal RFC process.

Feature/Deliverable Item #1: PMI API token management functionality

This feature allows the system administrator to generate a randomized 30-character token that will restrict access to the API. The token(s) will be sent on each HTTP request as a means of authenticating the API caller (i.e. the OSS form).

- Add menu item option (within “User Administration” menu) for “Generate API Tokens”

- Add user_token table and ORM class

- Secure access to this functionality with the SYSADMIN role

- Reconfigure application to use new auth functionality

Test Plan Details: Matsch will demonstrate new screens via SOM MOST test server.

Dependencies: None.

Feature/Deliverable Item #2: API – Billing Update API for form

This feature will be a standalone, special-purpose web service which will listen for requests from the OSS form software, and which will create new Billing IDs and charges within the PMI application. The charges will be one-time (i.e. not recurring).

- Create standalone web service to handle requests for billing updates from the form o Form actions supported:

▪ Billing ID action = AB (Add Billing)

▪ MOST Item action = AI (Add Item) o Direct maintenance of the Equipment/Service Inventory table (bypass the MOST

Change/Audit/Tracking system) o Bypass SIGMA validation (already built into front end) o Auto-create SIGMA coding block (if not already present in database) o Set syscreatedby equal to form name and reference/order # o Set ‘syscreatedon equal to current system time

- Authentication for service via API token (same as other existing automated form APIs)

- Update web server configuration

- Create JSON schema

- Implement JSON validation mailto:sales@matsch.com

Test Plan Details: Matsch will create a testing environment on the test MOST server, to include a working endpoint/URL for the OSS/Delivery Services form. Results of processing will be verifiable via Billing ID

Maintenance. An icon will be added to the Billing ID list screen for those Billing ID types that have sdc_esi_enabled set to a true value.

Dependencies: Deliverables #1 and #6.

Feature/Deliverable Item #3: Source Data Code Item control

The feature controls which ESI Item Codes may be used with any given Billing ID. The OSS form will generate

DMD or SCH Billing ID types, for which only the MDSDMD and MDSSCH item codes are applicable. This control will ensure that other items in the Mail & Delivery Services Billing Group cannot be assigned to these Billing IDs.

- Modify ESI maintenance form. Add label for “Use with SDC” input field

- Initialize Source Data Codes for Scheduled and On Demand freight

Test Plan Details: Matsch will demonstrate new screens via SOM MOST test server.

Dependencies: Deliverable #2.

Feature/Deliverable Item #4: PMI documentation

The PMI_User_Guide.docx document (and corresponding .pdf version) will be modified/enhanced as follows:

- Add section to explain purpose and behavior of ES/I List Screen

- Add section for ESI maintenance for SDC control

- Add section for Billing Update API (for developers)

- Remove section(s) that describe the imports for “On Demand” and “Scheduled Freight”

Test Plan Details: Matsch will provide document to project stakeholders for review, and revise or enhance as needed.

Feature/Deliverable Item #5: Decommission TIP import software

Remove TIP import and batch processing for On Demand and Scheduled freight.

- Remove MDSTIPDMD and MDSTIPSCH user authorization roles from application

- Remove front-end components from “MDS TIP Home” screen

- Remove TIP listing and edit screens

- Remove TIP posting logic

- Remove database tables mdsbatdmd, mdsbatsch, mdstipdmd, and mdstipsch. NOTE: Source data files and billing history will be preserved.

Test Plan Details: Matsch will demonstrate that screens no longer exist.

Feature/Deliverable Item #6: ESI Direct Maintenance

Add ability to directly create, read, update, and delete recurring and non-recurring charges.

- Create application authorization role MDSESIADM to secure access to maintenance functionality

- Add “sdc_esi_enabled” field to table “sdcctl” to control which Billing ID types are approved for use with recurring and non-recurring charges

- Create list screen for a Billing ID of any Equipment/Service Items

Test Plan Details: Matsch will demonstrate the above functionality in the State’s test environment.

Feature/Deliverable Item #7: Application Responsiveness Enhancement

Increase accessibility and enhance user interface by adding Bootstrap styling to entire application. This will allow the application to function acceptably in a variety of form factors (i.e. PC, tablet, phone).

- Install Bootstrap elements (CSS and JavaScript) application-wide o Increase useable viewport to size of containing window o Make application responsive to form factor (enhances accessibility) o Review and test all pages for proper functionality and responsiveness

Test Plan Details: Matsch will demonstrate the above functionality in the State’s test environment.

Feature/Deliverable Item #8: Automatically purge inactive Billing IDs

Develop software to automatically delete Billing IDs from the database that are no longer in use

- Identify Billing IDs that: 1) have no ESI records associated, and 2) have no charges billed in past 90 days, 3) have no pending work orders and 4) have no Period-to-Date charges pending

- Create purge report/list of deleted Billing IDs, last charge billing period, created on, last modified on

- Send report to billing specialist

- Install for SBS and PMI applications

Test Plan Details: Matsch will perform a series of dry runs to demonstrate the outcome of the purge process prior to production implementation.

Pricing and Pay Points

An invoice will be submitted upon completion of the above “Feature/Deliverable Items” and associated test plans.

Expected completion is estimated to be first quarter of 2023.

Maintenance

Annual maintenance will apply to Feature/Deliverable Items as noted in pricing table. No maintenance amounts are indicated for design and/or documentation items.

An annual maintenance amount of $3,519.00 will be added to annual MOST maintenance invoices starting April

1st 2023. All maintenance is subject to annual increases as specified in the contract between the State of

Michigan and Matsch Financial Systems, Ltd., for as long as the software is operational.

PRICES VALID FOR SIXTY (60) DAYS FROM DATE OF PROPOSAL

Please confirm approval via email to: steve@matsch.com (Steve Schafer, Matsch Systems)

____________________________________ 2022-08-11

Representative, Matsch Systems Date mailto:steve@matsch.com

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 11 to 071B2200137Contract Number

Feguerr@michigan.gov

Rob Feguer

KeriAnn Trumble steve@matsch.com

Steve Schafer

Grand Rapids, MI 49503-1401

MATSCH FINANCIAL SYSTEMS LTD

CV0026172

616-477-9629

911 N. Division Ave. , Suite B

(989) 259-2625 S

T A

T E

P ro g n a g e r

C o n tra ct

A d m in istra to r

C O

N T R A C T O

R

517-241-5054

DTMB

trumblek1@michigan.gov

$10,612,647.41

March 7, 2012 March 6, 2025

TELECOM BILLING SYSTEM MAIN & SUPPORT

March 6, 2015

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

2 - 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

☐ ☐ March 6, 2025

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$32,640.00 $10,645,287.41

Effective 6/8/2022, the parties add $32,640 for the implementation of a new MIS system 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.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

Statement of Work & Proposal for:

MOST Platform – Avanti Slingshot® Interface for Print Services

May 26, 2022

Delivery/Purchase order. The work product will consist of new software, modifications to existing software, testing software, database design and modifications, application data setup and scripting, and documentation. All of the work to be performed will be within the scope of the Print, Mail, and Imaging Billing application, commonly referred to as “PMI”, which is hosted on the State’s infrastructure and network. The work is focused on the extraction and billing of data from the Avanti Slingshot® print management system (herein referred to as “source database” or “source system”).

Test Plans: Unless otherwise indicated, the testing activities described throughout this document will be performed first in Matsch’s development environment, then installed on the SOM test server where UAT testing will be completed. RFC’s will be created as needed for installation of the software on the State’s production systems, and

Matsch will perform installation in accordance with the normal RFC process.

Feature/Deliverable Item #1: Develop an interface to source system database

This feature consists of new software that provides the connection to the source database using existing State-supplied credentials and firewalls. This software will be responsible for generating command input for the sqlcmd utility (already installed on MOST server).

- Establish mechanism for passing in variable data (interpolated within sqlcmd utility)

- Facilitate flexible field delimiters in order to guarantee reliable output of field data

- Eliminate control characters from any/all fields

- Eliminate trailing spaces within individual fields

- Add Avanti interface configuration to PMI configuration file (yaml) o username o password (encrypted) o database o remote server name o remote port

Test Plan Details: Unit tests will verify proper construction of interface commands. Integration tests will be performed on the SOM MOST test server.

Feature/Deliverable Item #2: Develop SQL queries for extraction of billing data from source database

This deliverable item will consist of 4-5 SQL template files, to be installed on both the test and production servers.

Template files will include variable names which will be interpolated when the query is executed. The list of queries does not specify which fields will be extracted. This is due to the volume of fields and the fact that some discovery is ongoing.

- Select billable orders (used for both print and mail labor) o Target table sa_ship o Filters on sa_ship.ship_date_fully_shipped date-time range (from/through)

▪ Implied time of 00:00:00 applied to from date

▪ Implied time of 23:59:59 applied to through date o Filters on sa_order_revision_header table

▪ ordrevh_is_active=1

▪ ordrevh_order_status='Completed'

▪ ordrevh_revision=0 o Filter on sa_order table: ordh_document_type=’ORD’ o Join tables

▪ sa_order

▪ sa_order_revision_header

▪ sa_order_rev_split_bill (SIGMA fields)

- Select billable press items for specific order o Target table sa_order_revds_press o Filters on sa_order table: ordh_document_type=’ORD’ and ordh_document_num=’<ordernum>’ o Filters on sa_order_revision_header table

▪ ordrevh_is_active=1

▪ ordrevh_order_status='Completed'

▪ ordrevh_revision=0 o Join tables

▪ sa_task

▪ sa_task_cost_link

▪ sys_cost_centre

▪ app_task_operation

▪ app_task_type

▪ sys_department

▪ sa_order_revision_detail_section

▪ sa_order_revision_detail

▪ sa_order revision_header

▪ sa_order

- Select billable tasks for specific order o Target table sa_order_revds_task_qty o Filters on sa_order table: ordh_document_type=’ORD’ and ordh_document_num=’<ordernum>’ o Filters on sa_order_revision_header table

▪ ordrevh_is_active=1

▪ ordrevh_order_status='Completed'

▪ ordrevh_revision=0 o Join tables

▪ sa_order_revds_task

▪ sa_task

▪ sa_task_cost_link

▪ sys_cost_centre

▪ app_task_operation

▪ app_task_type

▪ in_item(left) x 3 (item_id, item_id_2, item_id_3)

▪ sys_department

▪ sa_order_revision_detail_section

▪ sa_order_revision_detail

▪ sa_order revision_header

▪ sa_order

- Select order detail items for specific order o Target table sa_order_revision_detail o Filters on sa_order table: ordh_document_type=’ORD’ and ordh_document_num=’<ordernum>’ o Filters on sa_order_revision_header table

▪ ordrevh_is_active=1

▪ ordrevh_order_status='Completed'

▪ ordrevh_revision=0 o Filter on sa_order_revision_detail

▪ item_id IS NOT NULL o Join tables

▪ sa_order revision_header

▪ sa_order

- Select (TBD) o Contingency: No more than one additional query for any newly-discovered billable items not captured by above order detail queries o Additional queries are outside the scope of the SOW/Proposal and will necessitate a change order o This contingency acknowledges the limited amount of time available for vetting of the logic embedded in the above queries, and the relatively few orders processed fully through the system

Test Plan Details: Above queries will be demonstrated (via remote meeting) upon request.

Dependencies: Item #1.

Feature/Deliverable Item #3: PMI database design and implementation in support of source system extracts

This feature will include the installation of two sets (one each for Print and Mail & Delivery Services) newly-designed database tables on both the test and production servers. Updates to various print billable item codes will also be performed – first on the test server, then on the production server just prior to “go live”.

- Design and install Transaction in Process and Batch tables o Print billing group table names are pgstipavs and pgsbatavs o Mail & Delivery Services billing group table names are mdstipavs and mdsbatavs for mail labor o Installation on test and prod servers

- Add new source data code AVS to PMI database

- Perform update to PMI Equipment/Service Items for both Print and Mail & Delivery Services o Create new codes from source system Cost Centre cc_short_desc values o Develop cutover script(s) to update existing codes

▪ Change descriptions

▪ Flag unused codes

▪ Change group codes per Print Services leadership’s direction

▪ Change SIGMA revenue coding per Print Services direction

▪ Execute cutover scripts on test server immediately

▪ Execute cutover scripts on production server just prior to “go live” date

Test Plan Details: Scripts will be executed on test database prior to the production database.

Feature/Deliverable Item #4: Develop PMI batch import processing software

This feature will include software and automated tests that prepare and insert the data generated by the above queries into the pgsbatavs and pgstipavs for Print Services billing tables, and mdsbatavs and mdstipavs for Mail & Delivery

Services billing tables.

- ETL (extract/transform/load) processing software o Initiate processing using from and through dates (format = CCYY-MM-DD) passed via UI o Create batch record

▪ Record user in created_by field

▪ Record date in created_on field o Execute billable orders query o Test orders against history, log and exclude orders that were previously imported o Insert TIP header record for each billable order o Execute order detail queries (3-4)

▪ Set record type, corresponding to query type

▪ Insert detail records o Process detail records

▪ Identify cost centre codes that are not on file in PMI

▪ Quantity values fixed at value of “1”, since amounts are taken “as is” from source database

▪ Set ignore flag as appropriate for each record

▪ Assign any inferred PMI item codes (i.e. for which no cost centre record can be joined)

- Generate import processing report o Excel® workbook

▪ Pre-Billing Order Summary

• Order #

• Ship Date

• Count of detail records and count of ignored records

• Order description & P.O.

• Agency/Dept

• Source system chargeback total

• PMI chargeback total

• Variance

▪ TIP Detail

• Order #

• Ignored (Y/N)

• Ignore reason

• Various detail descriptive fields (may vary by detail type)

• Billable amount

▪ SIGMA Validation

• Order #

• SIGMA coding elements, with invalid fields highlighted

- Email import processing report to billing specialist user

- Document the import process as an appendix within the PMI user guide, with both graphical and narrative descriptions of the processing logic

Test Plan Details: Develop unit tests for each record type and combination of values from source database to validate ignore flagging, item code assignment, and exception handling.

Dependencies: Items #2 and #3.

Feature/Deliverable Item #5: Develop PMI batch posting processing software

This feature will include software and automated tests that process transactions into the Period-to-Date (PTD) charges tables pgsptdchg or mdsptdchg for Print or Mail & Delivery Services, respectively.

- Find or Create SIGMA coding block

- Create Billing ID in billmas table o blm_code = order number o blm_sdc = AVS o blm_bgm_id = (bgm_id from billgrpmas table for PGS or MDS Billing Groups) o blm_site = 1 o blm_glm_id = (result from find or create SIGMA coding block, above)

- Insert PTD records for eligible charges

- Update batch record o Record user in posted_by field o Record date in posted_on field

- Generate posting report (PDF) o Processing statistics o PTD Summary o Item Summary o Billing ID PTD Summary o SIGMA Validation results

Test Plan Details: Develop unit tests for each record type and combination of values from TIP tables (pgstipavs and mdstipavs) to validate charge creation, Billing ID record insertion, SIGMA record insertion, reporting, and exception handling.

Dependencies: Items #2, #3, and #4.

Feature/Deliverable Item #6: User interface – Batch creation/order selection screen

Interfaces will be created for both Print and Mail & Delivery Services billing groups. Each will require the user to enter from and through dates. This functionality will be secured, and accessible only via the PGSBILL and

MDSTIPAVS roles for Print and Mail & Delivery Services, respectively.

- Add new role MDSTIPAVS to the PMI database

- Add menu picks for both batch types (print/mail) o These will coexist with Pace menu items until cutover is complete

- Develop new batch creation pages with datepicker widgets

- Display status message upon submission

Test Plan Details: Page functionality will be available for user acceptance testing on the test server.

Dependencies: Item #3.

Feature/Deliverable Item #7: User interface – Batch list screen

This screen will list the unposted batches by default, with an option to include batches that were previously posted.

The screen will paginate results, ordering by newest to oldest. Each batch listed will have buttons that allow the user to perform various actions pertinent to that batch.

- Display list of batches o Present unposted batches by default o Provide check box to allow display of posted batches o Paginate results o Display batch information – Batch #, from and thru dates, and billable total o Action buttons for each batch

▪ Display list of orders for batch (un-posted batches only)

▪ Display import statistics (un-posted batches only)

▪ Post the batch (un-posted batches only)

▪ Delete the batch (un-posted batches only)

▪ View posting summary (posted batches only)

Test Plan Details: Page functionality will be available for user acceptance testing on the test server.

Feature/Deliverable Item #8: User Interface – Order summary list screen

This screen will list the orders that were imported for the batch. The screen will paginate results, and each order will contain a button allowing the user to list the transactions for the order.

- Display list of orders o Paginate results o Batch information displayed at top of order list o Display order information – Order #, description, count of detail records, and billable total o Action button for displaying order detail list o List header to display batch summary (#, date range, etc.)

Test Plan Details: Page functionality will be available for user acceptance testing on the test server.

Feature/Deliverable Item #9: User Interface – Order detail list screen

This screen will list the detail records imported from the source database.

- Display list of order details (i.e. Transactions in Process) o Paginate results o Display transaction detail information – Item code, description, billable amount, and ignored flag o Action button for displaying transaction detail list for the order

Test Plan Details: Page functionality will be available for user acceptance testing on the test server.

Feature/Deliverable Item #10: User interface – Transaction detail and edit screen

This screen will display all of the details extracted from the source system, as well as most fields that were generated by the import process, such as item code assignments. Users will have the option to ignore a particular charge, as a means of overriding the source system or processing results.

- Display additional detail about the transaction and allow user to ignore the record o This is the most granular view of the extracted data from the source system o A checkbox input will allow the user to ignore an individual record

Test Plan Details: Page functionality will be available for user acceptance testing on the test server.

Feature/Deliverable Item #11: User interface documentation

The PMI User Guide will be updated with information about the new user interface, including screen shots and narrative explanation of the features of each screen

- Add documentation to the Print and Mail & Delivery Services sections of the document o Add section for each screen o Mail & Delivery Services section will reference Print, and will detail any “mail-specific” user interface differences

Test Plan Details: Document will be submitted to DTMB – Financial Services for review and approval.

Pricing and Pay Points

An invoice will be submitted upon completion of the above “Feature/Deliverable Items” and associated test plans.

Maintenance

Annual maintenance for the PMI application will continue per existing contracted pricing due to the fact that these features are replacing substantially similar features which are included in the existing maintenance amounts.

PRICES VALID FOR SIXTY (60) DAYS FROM DATE OF PROPOSAL

Please confirm approval via email to: steve@matsch.com (Steve Schafer, Matsch Systems)

____________________________________ 2022-05-26

Representative, Matsch Systems Date mailto:steve@matsch.com

Department of Technology, Management, and Budget

525 W. ALLEGAN ST., LANSING, MICHIGAN 48913

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

Change Notice Number 10 to 071B2200137Contract Number

Feguerr@michigan.gov

Rob Feguer

Jordan Sherlock steve@matsch.com

Steve Schafer

Grand Rapids, MI 49503-1401

MATSCH FINANCIAL SYSTEMS LTD

CV0026172

616-477-9629

911 N. Division Ave. , Suite B

517-243-5556 S T A T E

P ro g n a g e r

C o n tra ct

A d m in istra to r

C O

N T R A C T O

R

517-241-5054

DTMB

sherlockj@michigan.gov

$10,612,647.41

March 7, 2012 March 6, 2025

TELECOM BILLING SYSTEM MAIN & SUPPORT

March 6, 2015

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

2 - 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

☐ ☐ March 6, 2025

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$0.00 $10,612,647.41

Effective April 22nd, 2021, this contract is incorporating the attached Statement of Work.

All other terms, conditions, specifications, and pricing remain the same. Per contractor and agency agreement, and DTMB Procurement approval.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

Statement of Work & Proposal for:

MOST Platform - Financial Services Server Billing - Phase II

April 1, 2021

Delivery/Purchase order. Where applicable, Matsch will support the DTMB Project Manager’s efforts to produce the SUITE documentation for the elements listed below.

Accessibility: During the development of this statement of work the subject of accessibility was introduced as a potential requirement. Since the existing application is awaiting ADA evaluation, and this project is time-sensitive it was decided that ADA standards would not be a requirement of this effort. However, Matsch is aware of the coming requirement and is committed to building the software specified in this statement of work in such a way as to minimize the effort to make the entire site (i.e. the IT Services Billing System) accessible at a later date.

Test Plans: Unless otherwise indicated, the testing activities described throughout this document will be performed first in Matsch’s development environment, then installed on the SOM test server where UAT testing will be completed. RFC’s will be created as needed for both the State’s test and production systems, and Matsch will perform install work in accordance with the normal RFC process.

Feature/Deliverable Item #7: Update “FSSB Design Document” to address additional business requirements.

- Add explanation of Source Data Code (sdcctl) controls “is_aggregate” and “is_flexible”

- Update ISR API Request Data Structure (pg 30)

- Update and enhance "Change, Audit, and Tracking for Servers" in "Other Features and Technical Details"

- Update "Split Billing" section - Add "Aggregate" concept

- Update Appendix B - Change, Audit, and Tracking for Servers

- Update Appendix C - ISR API JSON REQUEST DETAILS

- Update Appendix H - User Stories o Reference new aggregate tables o Add User Story for Direct Costs o Add User Story for Container o Add User Story for NAS

- Update Maintenance of Billing Data o Add mockup screen for NAS drive share o Add mockup screen for a Direct Cost o Add mockup screen for a Container o Modify list screen headings - add "General Info" column that is SDC-specific

Test Plan Details: Matsch will provide project manager and stakeholders with updated version of the design document (.docx). Matsch will participate in Q&A session and address any design concerns.

Feature/Deliverable Item #8: Database Installation/Modifications

- Remove “wosvshost” and “wosvsitem” tables

- Create “woaggblm” table (mirror of “woblmip')

- Create “woaggesi” table (mirror of “woesiip”)

- Create “woaggblx” table (mirror of “woblxip”)

- Create “woaggsplit” table

- Create foreign key constraint from “woaggsplit' to “woaggblm”

- Create foreign key constraint from “woaggblx' to “woaggblm”

- Create foreign key constraint from “woaggesi” to “woaggblm”

- Create foreign key constraint from “woaggsplit” to “woblmip”

- Create foreign key constraint from “woaggblm” to “woordip”

- Source Data Control o Add “sdc_is_aggregate” flag o Add “sdc_is_flexible” flag o Add foreign key constraint from “billmas” to “sdcctl” o Update item master records for SVS billing group - add SDC to items that are limited to a single type of billing ID o Update bootstrap software to automatically identify the correct SDC from items being billed (HST-default, SHR, DCS, or CTR)

Test Plan Details: Matsch will execute manual “show create table” statements using SQL client to prove fields and relationships have been created.

Feature/Deliverable Item #9: Object-Relational Mapping Classes

- Remove “WoSvsHost” and “WoSvsItem” result/set modules

- Generate new aggregate order classes

- Generate new aggregate relationships

- Update “SdcCtl” class to reflect new flags and foreign key constraint

- Create delegate methods for sdcctl “'is_aggregate” and “'is_flexible” within BillMas ORM result class

- Install ORM classes on test/prod servers

Test Plan Details:

- “is_aggregate” delegation: Automated test scenarios for Billing ID/SDC will show Billing ID SDC value, SDC->is_aggregate value, and result. Test “is_aggregate” values “Y”, “y”, “N”, “n”, 1, 0.

- “is_flexible” delegation: Automated test scenarios for Billing ID/SDC…