ServiceLogix+Amendment+24+and+SOWs+-+signed.pdf

CONTRACT AMENDMENT

AMENDMENT NUMBER 24

Amendment 24 to the Contract between the State of North Dakota, acting through its Workforce Safety and Insurance (STATE), and ServiceLogix, Inc. (CONTRACTOR).

The parties agree to the following terms and conditions and expressly agree that if any of the following terms and conditions conflict with any of the terms and conditions of the Contract, then, notwithstanding any term in the Contract, the following terms and conditions govern and control the rights and obligations of the parties.

Whereas, 29 Merger and Modification, Conflict in Documents states “…This Contract may not be modified, supplemented or amended, in any manner, except by written agreement signed by both parties.”; therefore, the Contract is amended as follows:

Section 2. Scope of Work is hereby amended to add the CAPS Program – Release 12 Claims Maintenance Part 2 Statement of Work to provide project management, business analysis, quality assurance, development, application architecture support, and database services for the re-facing effort for Release 12 Claims Maintenance Part 2 as laid out in the CAPS Release Plan.

This section is also hereby amended to add the myWSI Release 8 Statement of Work to provide project management, business analysis, quality assurance, development, application architecture support, and database services for the implementation of Release 8 as laid out in the myWSI Release Plan.

This section is also hereby amended to add the Production Support Statement of Work to provide maintenance, enhancements and support what was implemented in CAPS Releases 1-11 and myWSI Releases 1-7.

The attached Statements of Work shall be incorporated and considered part of the Contract upon signature by both STATE and CONTRACTOR.

Section 3. Compensation, a. Contractual Amount is hereby amended to increase the Contractual Amount from $23,161,573 to $27,027,743, an increase of $3,866,170. Billing for services will continue at a Time and Materials rate of $135.00 per hour.

a. The increase includes $2,047,000 for services for CAPS Release 12 and $64,170 for travel expenses, for a total not to exceed amount of $2,111,170.

b. The increase also includes $805,000 for services for myWSI Release 8.

c. The increase also includes maintenance and operations support for CAPS and myWSI in the amount $950,000.

Third-Party Risk Management Program The Third-Party Risk Management (TPRM) program helps to classify, evaluate, and monitor all third-party Vendors to provide reasonable assurance that inherent and overall risk associated with each third-party Vendor relationship is understood and aligned to the overall security objectives at NDIT. TPRM went into effect on July 1, 2023. The Contract is hereby amended to include the following TPRM section:

CONTRACTOR shall undergo the third-party security questionnaire on an annual basis at no cost to the STATE, unless CONTRACTOR has received FedRAMP, StateRAMP, or HiTrust certification. CONTRACTOR shall provide complete questionnaire within twenty-one (21) calendar days of receiving a written request. CONTRACTOR shall also undergo the third-party security questionnaire when a breach has occurred.

All other terms of the Contract remain in effect. This Contract Amendment is not effective until fully executed by all parties.

CONTRACTOR NAME

ServiceLogix, Inc.

BY:

Andrew Thomson

CEO

DATE:

STATE OF NORTH DAKOTA acting through its Workforce Safety and Insurance

STATE OF NORTH DAKOTA acting through its Information Technology Department

BY:

BY:

Art Thompson Greg Hoffman Director Interim Chief Information Officer

Andrew Thomson (Jun 25, 2024 08:47 MDT) Andrew Thomson

06/25/2024

06/26/2024

Art Thompson (Jun 26, 2024 11:20 CDT) Art Thompson

06/26/2024 https://na2.documents.adobe.com/verifier?tx=CBJCHBCAABAAn1W8hIbkTDvoSBJQaIdJx8RjngqRphWy https://na2.documents.adobe.com/verifier?tx=CBJCHBCAABAAn1W8hIbkTDvoSBJQaIdJx8RjngqRphWy

Statement of Work Claims Maintenance Part 2

Release 12

This Statement of Work (“SOW”) is not effective until signed by both parties

Definitions

1) Deliverable: A deliverable is a document, an electronic file, program source code, a database schema, a physical database, a tested component, or any other of various artifacts or work products to be produced by ServiceLogix or by WSI as defined in the Scope of Work.

2) System: The collective software, configuration, and supporting artifacts that represent the entirety of the re-facing effort to move away from the current PowerBuilder client/server technology stack onto the new browser-based architecture as articulated in the Configuration Management Plan.

3) System Release: The deliverables created or modified in order to complete the scope as defined by this SOW.

4) Acceptance Plan: The set of artifacts inclusive of: requirements artifacts, global standards, test cases and scripts, test data, and test plans that formulate the process and objective measure of whether or not the System Release is functioning and meets the criteria to be deemed worthy for use in a production environment.

5) Acceptance:

The following shall represent how the System Release shall be accepted:

a. Subject matter experts and designated application users will define and author the Acceptance Plan in coordination with ServiceLogix project team members to establish the objective criteria from which a given release’s acceptance may occur. The Acceptance Plan shall be completed in advance of the System Release source code being promoted to the User Acceptance Test Environment.

b. The Acceptance Plan represents the set of objective criteria the release should fulfill in order to be accepted into production. The Acceptance Plan must express the same scope as the documented requirements expressed by the use cases and supporting artifacts. Variance in the Acceptance Plan from the requirements expressed by the use cases and supporting documentation will be treated as Change Control.

c. The release team will promote the System Release source code into the User Acceptance Test Environment and communicate to the Subject Matter Experts and designated application users/analyst(s) that the System Release is ready for formal user acceptance testing.

i. Deficiencies will be recorded, resolved, and verified using the enCorps issue tracking and artifact management tool. Deficiencies represent those specific System Release functional capabilities that do not function in accordance with the Acceptance Plan.

d. Acceptance of the System Software shall occur in the following circumstances:

i. The System Release meets the criteria agreed upon by ServiceLogix and WSI project team members and designated business users/analyst(s) as documented in the Acceptance Plan and demonstrates sufficient stability to be deemed production ready OR

ii. the System Release is put into production use OR

iii. the System Release is promoted to the User Acceptance Test Environment and 10 business days have elapsed without any notification of System Release Deficiencies.

Conflicts

The parties agree that the Agreement shall always supersede any interpretation of this SOW.

Scope of Work (“Scope”)

WSI and ServiceLogix have agreed upon a scope of the SOW to be as follows:

1) Configuration Management Optimization

The services required to support the ongoing optimization and configuration of the tools and processes identified in the Configuration Management Plan version 23 dated November 18th, 2019 (stored in enCorps) working in conjunction with WSI and ITD resources.

2) Use Case – Claim Status

The services required to support the production ready enhancements associated to this use case including:

Important Dates Control Box fields Scholarship External Vendor

3) Use Case – Claim Wages

The services required to support the production ready enhancements associating to this use case including:

Pre-injury Wage Capture Post-injury Wage Capture Average Weekly Wage Calculation

4) New Use Case – Claim Handling Controls

The services required to support the production ready enhancements to implement display and maintenance of claim handling controls including auto-adjudication parameters.

5) New Use Case – Claim Impairment

The services required to support the production ready enhancements to implement capture, display and modification of claim impairment data.

6) New Use Case – Claim Offsets

The services required to support the production ready enhancements to implement capture, display, and modification of claim offset data including:

Aggravation Social Security Disability Social Security Retirement Nursing Home

7) New Use Case – Claim Employer Relief

The services required to support the production ready enhancements to implement capture, display, and modification of Employer Relief information.

8) InfoPath Forms Conversion

The services required to support the production ready enhancement to incorporate the following InfoPath forms into the CAPS system:

a.) C46a – Consolidate Claim b.) R9 – Initial Rehabilitation Consultation c.) C56 – Stipulation Request / Authorization d.) C61 – Write-off Claims Account Receivable e.) C64 – Permanent Total & Catastrophic Benefit Claim Review f.) C121 – Return to Work Services Referral g.) C154 – Scholarship Committee Review

9) CAPS “Future“ Maintenance Items:

The services required to support the production ready enhancement to incorporate the following maintenance items into the CAPS system:

13168 – SIU Referrals 18341 – Utility Tool for Experience Rate Calculation 19373 – Experience Rating / PCD Procedure rewrite 19014 – Claim Retention on Last Activity Date 15371 – Premium Audit Application in myWSI

Note on 15371: These are the CAPS enhancements required to support the myWSI capabilities identified by the myWSI scope (TBD). There were communications outlining assumptions on scope that CAPS changes would not be required but leaving this item here as a placeholder pending prototyping and initial requirements discovery.to confirm.

10) Refactor Code and Architecture

The nature of any major software development effort demands that ongoing “refactoring” is employed to ensure code maintainability and architectural consistency. New problem resolutions, new methods, and ongoing software evolution will demand periodic restructuring of code and harvesting of reusable components to increase overall system longevity as well as coding and operational efficiency. ServiceLogix will produce the necessary analysis, documentation, software components, and configuration deliverables required to implement necessary code refactoring to meet aforementioned objectives.

11) Phase 4 - Release 12 Preparation

The services required to perform initial detailed planning, analysis, prototypes, and requirements activities.

12) Load & Stress Test Release 12

ServiceLogix will design, script, and implement the load and stress tests utilizing the CERT web server and database environments.

a. ServiceLogix will provide the following metrics within each load/stress test run:

i. Click time - the time from when the request is sent to the server to when the simulated user receives the last packet of data for that request.

ii. Hits per Second - the overall rate at which the test was completing requests.

iii. Error counts – the count of errors generated by the web server and/or network causing a given client request to fail.

iv. Web Server Utilization – the utilization encountered on the web server expressed as usage of CPU and

Memory

v. Oracle Database Utilization – the utilization encountered on the Oracle database server instance as expressed by available performance monitoring tools for the database.

b. ServiceLogix will execute two series of three load tests to measure normal, peak, and ramped scenarios while observing client, web server, and database server performance metrics.

c. ServiceLogix will also execute one series of three stress tests to measure when performance will begin to deteriorate because of overall load on the web server and/or database server.

d. All tests will be scripted and performed using a client-side ‘headless’ load generation tool.

e. All tests will be scaled to the relative size of the available resources within the CERT test environment.

Change Control

Changes will be recorded and reviewed using the enCorps issue tracking and artifact management tool. Changes that do not affect cost and/or schedule, will be addressed according to the “Change Request lifecycle” as described in the Configuration Management Plan. Changes represent those specific System Release functional capabilities deemed necessary for Acceptance, but are outside of the scope.

“Major Changes,” those that affect cost and/or schedule defined herein shall follow the process defined in Section 22. Project Management, b. Integrated Change Control Process of the Contract.

Cost

ServiceLogix will complete the work associated with this SOW for $2,047,000.00 dollars on a time and materials plus travel expenses basis as defined in Section 3. Compensation, d. Travel of the Contract Amendment Number 24 Expenses are estimated at $64,170.00.

This assumes acceptance of the System Release will occur in accordance with the release schedule (in the Claims and Policy System (CAPS) Program Plan) and the Acceptance Plan as defined in this Statement of Work. This cost may be amended in accordance with the Integrated Change Control Process as outlined in the Contract.

“WSI”

Workforce Safety and Insurance 1600 E. Century Ave Bismarck ND, 58503-0649

By:

Name:

Title:

Dated:______________________________

“SERVICELOGIX”

a Colorado corporation.

Title:

Dated:_______________________________

Andrew Thomson

CEO

06/25/2024

Art Thompson (Jun 26, 2024 11:20 CDT) Art Thompson

Art Thompson Director

06/26/2024 myWSI Program

Release 8

This Statement of Work (“SOW”) is not effective until signed by both parties.

1) Deliverable: A deliverable is a document, an electronic file, program source code, a database schema, a physical database, a tested component, or any other of various artifacts or work products to be produced by ServiceLogix or by

2) System: The collective software, configuration, and supporting artifacts that represent the entirety of the external site release functionality introduced and deployed as articulated in the Configuration Management Plan.

3) System Release: The deliverables created or modified in order to complete the scope as defined by this SOW.

4) Acceptance Plan: The set of artifacts inclusive of: requirements artifacts, global standards, test cases and scripts, test data, and test plans that formulate the process and objective measure of whether or not the System Release is

a. Subject matter experts and designated application users will define and author the Acceptance Plan in coordination with ServiceLogix project team members to establish the objective criteria from which a given release’s acceptance may occur. The Acceptance Plan shall be completed in advance of the System Release

b. The Acceptance Plan represents the set of objective criteria the release should fulfill in order to be accepted into production. The Acceptance Plan must express the same scope as the documented requirements expressed by the use cases and supporting artifacts. Variance in the Acceptance Plan from the requirements expressed by the

c. The release team will promote the System Release source code into the User Acceptance Test Environment and communicate to the Subject Matter Experts and designated application users/analyst(s) that the System

i. Deficiencies will be recorded, resolved, and verified using the enCorps issue tracking and artifact management tool. Deficiencies represent those specific System Release functional capabilities that do

i. The System Release meets the criteria agreed upon by ServiceLogix and WSI project team members and designated business users/analyst(s) as documented in the Acceptance Plan and demonstrates sufficient stability to be deemed production ready OR

ii. the System Release is put into production use OR

iii. the System Release is promoted to the User Acceptance Test Environment and 10 business days have

The services required to support the ongoing optimization and configuration of the tools and processes identified in the Configuration Management Plan version 23 dated November 18th, 2019 (stored in enCorps) working in conjunction with

2) New Use Case – Injured Employee Dashboard

The services required to support the production ready enhancements associated to implement the Injured Employee Dashboard including:

Summary data Lookup facilities for claims and payments Maintenance of demographic information Banner notifications Important messages and actions for injured employee to act upon Responsive design for a mobile viewport

3) Authentication and Delegation Enhancements

The services required to document and research options for enhanced login and authentication (enhancements dependent on NDIT allowed approaches) and implement production ready enhancements for the simplification of the security delegation model to other users identified by the injured employee.

4) Forms and Documents Access

The services required to implement production ready enhancements for access to identified forms and documents stored in Filenet for the injured employee and delegates in accordance with current global standards, architecture, and UX needs.

5) Forms Submission

The services required to implement production ready enhancements for online forms submission for the injured employee and delegates in accordance with current global standards, architecture, and UX needs. Forms to be included will be discussed and agreed upon during the prototyping and initial requirements gathering phase of the release. If needed forms for the release exceed planned budget and timelines, then standard change control processes will be followed.

6) SMS / Text Notification

The services required to implement production ready enhancements for injured employee notifications via SMS/text with guidance to access myWSI account for additional details.

7) askWSI enhancements for Injured Employee

The services required to implement production ready enhancements for askWSI to support new injured employee myWSI functional capabilities.

8) myWSI “Future” Maintenance Items:

The services required to support the production ready enhancement to incorporate the following maintenance items into myWSI:

14846 – myWSI Dashboard Home – missing phone number 15235 – Add in myWSI Selection for Employer to Opt-in for Electronic Billing

15371 – Premium Audit Application in myWSI Note: Initial implementation of this capability is TBD – scope will be implemented in phases across multiple releases

9) Business Gateway Initiative

The services required to support research and/or meeting attendance for Business Gateway initiative driven by NDIT.

10) UI/UX Services

The services required to analyze and provide design recommendations for myWSI User Interface and User Experience.

11) Refactor Code and Architecture

The nature of any major software development effort demands that ongoing “refactoring” is employed to ensure code maintainability and architectural consistency. New problem resolutions, new methods, and ongoing software evolution will demand periodic restructuring of code and harvesting of reusable components to increase overall system longevity as well as coding and operational efficiency. ServiceLogix will produce the necessary analysis, documentation, software components, and configuration deliverables required to implement necessary code refactoring to meet aforementioned objectives.

12) myWSI Release 8 Preparation

The services required to perform initial detailed planning, analysis, prototypes, and requirements activities.

13) Load & Stress Test

ServiceLogix will design, script, and implement the load and stress tests utilizing the CERT web server and database environments.

Changes will be recorded and reviewed using the enCorps issue tracking and artifact management tool. Changes that do not affect cost and/or schedule, will be addressed according to the “Change Request lifecycle” as described in the Configuration Management Plan. Changes represent those specific System Release functional capabilities deemed necessary for Acceptance, but are outside of the scope.

“Major Changes,” those that affect cost and/or schedule defined herein shall follow the process defined in Section 22. Project Management, b. Integrated Change Control Process of the Contract.

Cost

ServiceLogix will complete the work associated with this SOW for $805,000.00 dollars on a time and materials plus travel expenses basis as defined in Section 3. Compensation, d. Travel of the Contract Amendment Number 21. There are no anticipated travel expenses for this release.

This assumes acceptance of the System Release will occur in accordance with the release schedule (included in the myWSI Program Plan) and the Acceptance Plan as defined in this Statement of Work. This cost may be amended in accordance with the Integrated Change Control Process as outlined in the Contract.

Title:

Andrew Thomson

CEO

06/25/2024

Art Thompson (Jun 26, 2024 11:20 CDT) Art Thompson

Director 06/26/2024

Art Thompson

Release 12/myWSI Release 8

Production Support

This Statement of Work (“SOW”) is not effective until signed by both parties

1) Deliverable: A deliverable is a document, an electronic file, program source code, a database schema, a physical database, a tested component, or any other of various artifacts or work products to be produced by ServiceLogix or by

2) System: The collective software, configuration, and supporting artifacts that represent the entirety of the re-facing effort to move away from the current PowerBuilder client/server technology stack onto the new browser-based architecture as articulated in the Configuration Management Plan.

3) System Release: The deliverables created or modified in order to complete the scope as defined by this SOW.

4) Acceptance Plan: The set of artifacts inclusive of: requirements artifacts, global standards, test cases and scripts, test data, and test plans that formulate the process and objective measure of whether or not the System Release is

a. Subject matter experts and designated application users will define and author the Acceptance Plan in coordination with ServiceLogix project team members to establish the objective criteria from which a given release’s acceptance may occur. The Acceptance Plan shall be completed in advance of the System Release

b. The Acceptance Plan represents the set of objective criteria the release should fulfill in order to be accepted into production. The Acceptance Plan must express the same scope as the documented requirements expressed by the use cases and supporting artifacts. Variance in the Acceptance Plan from the requirements expressed by the

c. The release team will promote the System Release source code into the User Acceptance Test Environment and communicate to the Subject Matter Experts and designated application users/analyst(s) that the System

i. Deficiencies will be recorded, resolved, and verified using the enCorps issue tracking and artifact management tool. Deficiencies represent those specific System Release functional capabilities that do

i. The System Release meets the criteria agreed upon by ServiceLogix and WSI project team members and designated business users/analyst(s) as documented in the Acceptance Plan and demonstrates sufficient stability to be deemed production ready OR

ii. the System Release is put into production use OR

iii. the System Release is promoted to the User Acceptance Test Environment and 10 business days have

The services required to support the ongoing optimization and configuration of the tools and processes identified in the Configuration Management Plan version 23 dated November 18th, 2019 (stored in enCorps) working in conjunction with

2) CAPS and myWSI Production Support, Enhancements, Knowledge Transfer, Mentoring, and Opal Training

The services required to provide production support (issue research and resolution) and software enhancements as well as ongoing knowledge transfer, mentoring, and formal Opal training as needed.

Changes will be recorded and reviewed using the enCorps issue tracking and artifact management tool. Changes that do not affect cost and/or schedule, will be addressed according to the “Change Request lifecycle” as described in the Configuration Management Plan. Changes represent those specific System Release functional capabilities deemed necessary for Acceptance, but are outside of the scope.

“Major Changes,” those that affect cost and/or schedule defined herein shall follow the process defined in Section 22. Project Management, b. Integrated Change Control Process of the Contract.

Cost

ServiceLogix will complete the work associated with this SOW for $950,000.00 dollars on a time and materials plus travel expenses basis as defined in Section 3. Compensation. There are no anticipated travel expenses.

This assumes acceptance of the System Release will occur in accordance with the release schedule (included in the appendix I of the Claims and Policy System (CAPS) Program Plan) and the Acceptance Plan as defined in this Statement of Work. This cost may be amended in accordance with the Integrated Change Control Process as outlined in the Contract.

Title:

Andrew Thomson

CEO

06/25/2024

Art Thompson (Jun 26, 2024 11:20 CDT) Art Thompson

Art Thompson Director

06/26/2024

ServiceLogix Amendment 24 and SOWs Final Audit Report 2024-06-26

Created: 2024-06-25

By: Tricia Opp (topp@nd.gov)

Status: Signed

Transaction ID: CBJCHBCAABAAn1W8hIbkTDvoSBJQaIdJx8RjngqRphWy

"ServiceLogix Amendment 24 and SOWs" History Document created by Tricia Opp (topp@nd.gov) 2024-06-25 - 12:36:28 PM GMT- IP address: 165.234.252.245

Document emailed to jthomson@servicelogix.com for signature

2024-06-25 - 12:43:06 PM GMT

Email viewed by jthomson@servicelogix.com 2024-06-25 - 2:46:19 PM GMT- IP address: 165.234.92.3

Signer jthomson@servicelogix.com entered name at signing as Andrew Thomson 2024-06-25 - 2:47:55 PM GMT- IP address: 165.234.92.3

Document e-signed by Andrew Thomson (jthomson@servicelogix.com) Signature Date: 2024-06-25 - 2:47:57 PM GMT - Time Source: server- IP address: 165.234.92.3

Document emailed to Greg Hoffman (gahoffman@nd.gov) for signature

2024-06-25 - 2:47:59 PM GMT

Email viewed by Greg Hoffman (gahoffman@nd.gov) 2024-06-26 - 1:41:38 PM GMT- IP address: 104.47.64.254

Document e-signed by Greg Hoffman (gahoffman@nd.gov) Signature Date: 2024-06-26 - 1:41:48 PM GMT - Time Source: server- IP address: 165.234.248.3

Document emailed to arthompson@nd.gov for signature

2024-06-26 - 1:41:51 PM GMT

Email viewed by arthompson@nd.gov 2024-06-26 - 4:20:12 PM GMT- IP address: 104.47.64.254

Signer arthompson@nd.gov entered name at signing as Art Thompson 2024-06-26 - 4:20:55 PM GMT- IP address: 165.234.252.206

Document e-signed by Art Thompson (arthompson@nd.gov) Signature Date: 2024-06-26 - 4:20:57 PM GMT - Time Source: server- IP address: 165.234.252.206

Agreement completed.

2024-06-26 - 4:20:57 PM GMT