Exhibit_G_-_Statement_of_Work_Template.docx.pdf

Exhibit G – Statement of Work Template

State of Wisconsin eGovernment Services (Self-Funded Portal) Contract No. (505004-O13-4091551301-01)

1 | P a g e

SOW No. [SOW Number]

[Department Name]

[Project Name/Title]

This Statement of Work No. [SOW Number] (“SOW”), dated [Month, Day, Year] (“Effective Date”) is issued pursuant to the restated and amended Contract for eGovernment Services (Self-Funded Portal), Contract # 505004-O13-4091551301-01 by and between the Wisconsin Department of Administration and Wisconsin Interactive Network, LLC dba Tyler Wisconsin (“Tyler Wisconsin”) (“Contractor”) dated as of Month Date, Year (the “Master Contract”), and the Interagency Agreement (“IA”) executed pursuant thereto by and between Contractor and [Department Name] (“Customer”). Unless otherwise indicated herein, capitalized terms used in this SOW without definition shall have the respective meanings specified in the Master Contract and/or the IA and all section, schedule and attachment references in this

SOW shall be to applicable sections, schedules and attachments of the Master Contract and/or IA. This

SOW is subordinate to the Master Contract and the IA, in that order.

(Note to Template Users: Any Service, Licensed Services, Solution or Software provided under this SOW must comply with all Division of Enterprise Technology (DET) Security, Technical Reference Model and

Executive Branch Large, High-Risk Reporting policies, standards and guidelines

(https://detcc.wi.gov/Pages/Home.aspx#.

If Authorized User is a State Agency and determines any area of non-compliance with the aforementioned at the above link in the Service, Licensed Services, Solution or Software to be provided by Contractor under this SOW, such Authorized User’s Project Manager must obtain written waiver from DET in accordance with the waiver process prior to executing this SOW with Contractor. Agency should collaborate with their designated DET Customer Account Manager to obtain such waiver.)

1. Professional Services (“Service”) and Functional Specifications. [Insert summary description of

Professional Services to be performed and the applicable functional specifications as well as the expected Deliverables.]

2. Period of Performance

The work authorized in this SOW will occur within the agreed upon project plan. This includes delivery, installation, implementation, integration, testing and acceptance all of products and services necessary to implement the Customer’s solution, training, and any support, other than on-going maintenance services. The period of performance for maintenance services shall be the term of this agreement in

Section 11 unless otherwise agreed to by Customer. [Customize this section to match what you are getting from the Contractor, based on the allowable scope of the Master Contract and your project’s specific needs within that allowable scope.]

3. Environments: [Specify any development, testing, implementation or other environments to be provided by Customer].

4. Customer Services or Support (Personnel Requirements) and Facilities Requirements: [Describe in sufficient detail any portions of the Project that are to be performed by Customer or provided by

Customer to Contractor. In addition, describe any support functions that are to be performed by

DocuSign Envelope ID: 34C546DD-39AB-4A20-97CE-513CD30C0357DocuSign Envelope ID: F543BDE8-BF67-4723-AD26-48BFD880864A https://detcc.wi.gov/Pages/Home.aspx

2 | P a g e

Customer (e.g., DBA support). Also describe any facilities, equipment or tools the Customer is to provide].

5. Type of Professional Service to be Performed.

(a) Service Type:

Select One:

Contractor Technology. Examples include:

eGovernment Application Development and Maintenance eGovernment Website Design, Development and Maintenance

Content Management System and Other Web Services

Electronic Services

Deliverable

Note: Customer shall ensure all cloud solutions receive appropriate classification through the cloud brokerage process in accordance with

DET’s data classification standard. Enterprise Agencies served by Tyler

Wisconsin are prohibited from processing, transmitting, or storing data in cloud solution above the classification determined through the cloud brokerage process.

(b) Payment Processing

[If applicable, if this is not applicable, include the phrase “N/A”]

Tyler Wisconsin Payment Processing will be utilized.

If Tyler Wisconsin Payment Processing is being utilized:

Responsibility for merchant of record: Contractor

Responsibility for merchant fees: Customer or Contractor

Responsibility for chargeback management: Customer or Contractor

Responsibility for chargeback fees: Customer or Contractor

End user payment support: Customer or Contractor

(c) Training Requirements and/or Agency Self-

Sufficiency/Knowledge

Transfer

[Provide an overview and details of training services to be provided for your project and any special requirements for specific knowledge transfer to support successful implementation of the Solution. If the intent is for the Customer to become self-sufficient in operating or maintaining the

Solution, determine the type of training necessary, and develop a training plan, for such user self-sufficiency. Describe how the Contractor will complete knowledge transfer in the event this Statement of Work is not completed due to actions of Contractor or the non-appropriation of funds for completion affecting the Customer.]

(d) Project Transition

Phase-In/Phase-Out

Requirements

[Describe any specific requirements for orientation or phasing in and/or phasing out of the project with the Contractor. Be specific on what the project needs and expected results are, the duration and other pertinent detail, but ensure they do not conflict with the Master Contract provision(s) regarding Transition of Services or with any other training requirements in the SOW.]

DocuSign Envelope ID: 34C546DD-39AB-4A20-97CE-513CD30C0357DocuSign Envelope ID: F543BDE8-BF67-4723-AD26-48BFD880864A

3 | P a g e

(e) Support and

Maintenance

Requirements

[Document the level of support, as available under the Contract, required by your project to operate and maintain the Solution. This may include conversion support, legacy system integration, transition assistance, Solution maintenance (including maintenance level), or other specialized consulting to facilitate delivery or use of the Solution.]

Funding. The Services shall be paid for as follows:

(a) SOW Funding Type: Select One:

Portal Transaction Fee Service

(Service offered to the customer in the form of: (i) subscriptions, or (ii) as a direct per-transaction charge to the customer and without cost to the agency, or (iii) as a direct, per-transaction charge paid by the agency)

Free Service

(Service is provided at no cost to the Agency. Contractor provides services from the proceeds of Premium Services)

Expedited Services; Consulting Services Time & Materials Service

(The Agency is willing to pay a fee for the Services, as set forth below)

Other [explain]

(b) Description of Fee. [Describe the Portal Fee, or Expedited Services/Consulting T&M Fee, as applicable. If this is a Free Service, include the phrase “N/A”]

(c) State Revenue Sharing Portal Fee. RESERVED

6. Payment Terms. Payment shall be made to Contractor as follows (check as applicable):

(a) Invoicing: If this box is checked, Contractor shall be paid for its provision of Services through the invoicing process identified in the Master Contract, as further detailed as follows [insert description of invoicing in accordance with Contract, including whether this is invoicing of the Agency for agency-paid services, or invoicing of the Agency for consumer-paid services.]

(b) Direct Payment from User: If this box is checked, Contractor shall be paid for its provision of

Services through direct payment from the user. (Note: User includes individual and business users.)

[insert description of flow of funds (transaction fees) if allowed in the Contract.]

(c) Combination Payment: If this box is checked, Contractor shall be paid for its provision of Services through a combination of invoicing and user direct payment as follows: [Insert description of payment breakdown if multiple methods of payment will be used. Use care to describe when each will be applicable. Note: this is not typical – i.e., when a service has both individual users and subscription users, and one type of fee is collected by the State and the other by the Contractor.]

7. Acceptance Testing. [Include any acceptance testing terms.] Following the Agency’s acceptance testing, as detailed herein, but prior to launch of the Service, Contractor will provide the Customer with an Acceptance Letter describing that the Service has been built to the applicable specifications. The

DocuSign Envelope ID: 34C546DD-39AB-4A20-97CE-513CD30C0357DocuSign Envelope ID: F543BDE8-BF67-4723-AD26-48BFD880864A

4 | P a g e

Customer is required to execute this letter as a condition to Contractor moving the service into production.

8. SOW Managers. The SOW Managers are:

For Company: [Tyler Wisconsin Project Manager Name], [Title] Wisconsin Interactive Network, LLC, [Email Address] , T: [Telephone Number]

For Customer: [Customer Contact Name], [Title], [Department, Division, & Name], [Customer

Contact Email Address], T: [Telephone Number]

9. Executive Sponsors. The Executive Sponsors are:

For Company: Chad Zadrazil, General Manager, Wisconsin Interactive Network, LLC

For Customer: [Customer Executive Sponsor], [Title], [Department, Division, & Name]

10. Master Contract Provisions:

Subcontractors. The following Subcontractor(s) will be utilized under this SOW:

Liquidated Damages: If agreed to by the parties, the liquidated damages applicable to this

SOW are as follows: [Include a specific description of the amount of liquidated damages, the events triggering the imposition of liquidated damages, etc. If no liquidated damages are contemplated, please note “None.”] It is agreed that force majeure events, events otherwise outside of Contractor’s control (including the actions or the Customer, State or third parties) shall not cause Contractor to be liable for liquidated damages.

11. Term. This SOW shall commence on the Effective Date and shall be co-terminus with the IA and the

Master Contract.

12. Security Requirements. [Provide (or reference as an Attachment) Authorized User’s security requirements.]

(For any individual Customer location, security procedures may include but not be limited to:

background checks, records verification, photographing, and fingerprinting of Contractor’s employees or agents. Contractor may, at any time, be required to execute and complete, for each individual Contractor employee or agent, additional forms which may include non-disclosure agreements to be signed by Contractor’s employees or agents acknowledging that all Customer information with which such employees and agents come into contact while at the Customer site is confidential and proprietary. Any unauthorized release of proprietary information by the Contractor or an employee or agent of Contractor shall constitute a breach of the Contract.)

13. Required Standards, Certifications and Specifications.

In addition to any standards and specifications included in the Contract, Supplier shall follow the standards and specifications listed below during performance of this effort.

DocuSign Envelope ID: 34C546DD-39AB-4A20-97CE-513CD30C0357DocuSign Envelope ID: F543BDE8-BF67-4723-AD26-48BFD880864A

5 | P a g e

[List any specific agency, DET, Federal, engineering, trade/industry or professional standards, certifications and specifications that Supplier is required to follow or possess in performing this work.

The first bullet includes a link to DET-required standards for all state technology projects. The rest are examples only and highlighted to reflect this. If you need a waiver of any DET-required standard, please contact the eGovernment Services Contract Administrator to assist.]

DET Security Policies and Standards:

https://detcc.wi.gov/security/Pages/securitypoliciesstandards.aspx

IEEE 802®

HIPAA

SSAE 18 and its successor(s)

14. Disaster Recovery.

(Planning for disaster recovery for your project is paramount to ensure continuity of service. The criticalness and complexity of your project, including its workflow into other dependent systems of the

State or federal systems, will help you determine if you require a simple contingency plan or a full-blow contingency plan.)

15. Other Technical/Functional Requirements.

[Provide any other unique project technical and functional requirements and expectations in sufficient detail in this section. Ensure they do not conflict with existing requirements in the Master Contract.

Several examples are listed.]

A. Service Level Requirements (at a minimum to include response time requirements, availability, notification of approved and unplanned outages, and problems, issues or defects with an application or service)

B. Mean-Time-Between-Failure Requirements

C. Data Access/Retrieval Requirements

16. Project Change Control Process. To ensure appropriate change communication, coordination and management review have occurred prior to change implementation, the Project Change Control Process establishes formal change approval requirements. The Customer and Contractor representatives and will evaluate, identify impact and approve plans for significant changes to the Service. The implementation of the change will occur per the procedures laid out, below.

A Request for Change (“RFC”) will be the vehicle for commucating change, a sample of which is attached hereto as Exhibit 1. The RFC must describe the change, the rationale for the change and the effect the change will have on the SOW. Either party may issue a RFC.

The designated program manager of the requesting party will review the proposed change and determine whether to submit the request to the other party.

The RFC must be signed by both parties to authorize investigation of the proposed changes when such investigations are required. The receiving party shall sign or provide written explanation of its decision to decline the request within ten (10) business days. For investigations which do not require additional fees or charges, failure to do so shall result in automatic approval of the investigation. Any investigation requiring additional fees or charges shall not proceed until signature is received.

DocuSign Envelope ID: 34C546DD-39AB-4A20-97CE-513CD30C0357DocuSign Envelope ID: F543BDE8-BF67-4723-AD26-48BFD880864A

6 | P a g e

The investigation will determine the effect that the implementation of the RFC will have on price, schedule, and other terms and conditions for this SOW. Unless otherwise agreed in an RFC, there shall be no fees or charges to conduct any investigation.

To authorize implementation of the investigated changes, a written Change Order, or this RFC again in the space indicated, must be signed by both parties.

17. Complete Agreement. This SOW constitutes the complete and exclusive statement of the agreement between the parties with respect to the obligations contemplated. No amendment, waiver or alteration of this SOW will be effective unless signed by an authorized officer of each of the parties to this

SOW. Any oral agreement or representation will bind neither the Customer nor Company.

18. Authority. With respect to this SOW, the following position within the Customer entity has the primary authority to make decisions and give direction to Tyler Wisconsin, with respect to partner entity services. In the absence of the primary position, the secondary position has authority to make decisions and give direction to Tyler Wisconsin with respect to partner entity services. Primary position:[Name of Individual with Primary Authority]. Secondary position:

[Name of Individual with Secondary Authority].

IN WITNESS WHEREOF, the parties by their duly authorized representatives have executed this

SOW as of the Effective Date.

By Contractor

Signature

Name

Title

Date

_____________________, 20___

By Customer

Signature

Name

Title

Date

_______________________, 20___

DocuSign Envelope ID: 34C546DD-39AB-4A20-97CE-513CD30C0357DocuSign Envelope ID: F543BDE8-BF67-4723-AD26-48BFD880864A

7 | P a g e

EXHIBIT 1

REQUEST FOR CHANGE

FORM

Request for Change Form

PCR No.

Project Change Requested:

Subject:

Submitted By: Date:

Description of Proposed Change: (Add attachments if necessary)

Investigation

Fixed Price To Investigate: Otherwise, Fee for Service Project, zero.

( ) Accept for Investigation

( ) Reject for Investigation

Contractor Signature: Date:

( ) Accept for Investigation

( ) Reject for Investigation

Customer Signature: Date:

Reason for Rejection (Add attachments, if necessary)

The above estimate will be withdrawn if not accepted by: / /

Implementation:

Description & Impact of Change To Be Implemented: (Add attachments, if necessary)

Fee for Service Project, Fixed Price to Implement the Change:

( ) Accept for Implementation

( ) Reject for Implementation

Contractor Signature: Date:

( ) Accept for Implementation

( ) Reject for Implementation

Customer Signature: Date:

The above estimate will be withdrawn if not accepted by: / /

DocuSign Envelope ID: 34C546DD-39AB-4A20-97CE-513CD30C0357DocuSign Envelope ID: F543BDE8-BF67-4723-AD26-48BFD880864A