HomeMy WebLinkAboutCounty of Kittitas WA SOW PS 11121.1.2PS-11121.1
1
Statement of Work
County of Kittias, WA
Creation Date: 02/19/2026
SoW Expiration Date: 05/19/2026
Document Number: PS-11121.1
Created by: Liam Watkins
PS-11121.1
2
Table of Contents
OpenGov Statement of Work 3
1. Project Scope and Understanding 3
2. Exhibits 3
3. OpenGov Responsibilities 3
4. Customer Responsibilities 3
5. Project Delivery 4
6. Estimated Schedule 4
7. Acceptance Procedure 4
8. Modifications 5
9. Communication and Escalation Procedure 5
Exhibit 1: Implementation Activities 6
OpenGov Implementation Methodology Overview 6
Procurement & Contract Management: 6
Initiate 6
Validate 7
Configure 7
Train 9
Launch 10
Exhibit 2: Technical Requirements 11
Procurement Technical Requirements 11
PS-11121.1
3
OpenGov Statement of Work
1. Project Scope and Understanding
This Statement of Work (“SOW”) outlines the Professional Services OpenGov will
provide to County of Kittitas, WA (“Customer”) under the applicable Order Form.
Professional Services or technical requirements not listed in this SOW are out of
scope.
2. Exhibits
The following exhibits are incorporated by reference and are part of this SOW:
2.1. Exhibit 1: Implementation Activities
2.1.1. Procurement & Contract Management
2.2. Exhibit 2: Technical Requirements
2.2.1. Procurement & Contract Management
3. OpenGov Responsibilities
OpenGov will provide a framework for planning, communication, progress tracking,
and coordination for activities in Exhibit 1. In collaboration with Customer, OpenGov
will develop and maintain the Project Plan. The “Project Plan” is a detailed, living
document that defines how the project will be executed, including tasks, timelines,
milestones, and team assignments. OpenGov will monitor progress against the
Project Plan, coordinate adjustments to tasks and schedules as needed, and
conduct status meetings as agreed to by the parties. OpenGov will provide weekly
status reports, a Project Charter, and a RAID register (Risks, Actions, Issues, and
Decisions). The “Project Charter” is a high-level document outlining the project’s
purpose, goals, key stakeholders, success criteria, and major milestones.
4. Customer Responsibilities
The Customer will appoint a primary point of contact with authority to make binding
decisions (“Customer’s Project Manager”). This person will coordinate internal
resources, assign subject matter experts (“SMEs”), and oversee implementation.
Responsibilities include attending status meetings, making timely decisions,
providing requested information, escalating issues internally, and collaborating on
the Project Plan and Change Order process, if applicable.
Customer acknowledges that the success of this project is contingent on its full
participation. Customer must provide data within ten (10) business days of a
request, maintain consistent data formats and access throughout the project, and
allocate the necessary Customer resources and time to support deliverables and
meet agreed-upon timelines.
PS-11121.1
4
Any failure by Customer to meet its responsibilities under this SOW (each, a
“Customer Delay”) will automatically suspend the affected obligations of OpenGov
for the duration of the Customer Delay and for a reasonable restart period
thereafter. All affected milestones, delivery dates, and service-level commitments
will be extended on a day-for-day basis (or as otherwise reasonably necessary) to
account for the Customer Delay, and may result in an adjustment of the fees if
OpenGov incurs additional time, materials, or other costs as a result. Under no
circumstances will any consequence of a Customer Delay constitute a breach by
OpenGov of this SOW or of the Agreement, nor will OpenGov be liable for any failure
to meet a performance obligation that is caused, in whole or in part, by a Customer
Delay.
5. Project Delivery
OpenGov will perform services under this SOW remotely. OpenGov may use a
combination of OpenGov personnel and OpenGov-trained implementation partners
to deliver the services described in this SOW.
6. Estimated Schedule
The estimated duration of this work is four (4) months. The specific timeline,
including order of delivery of the product(s), will be determined during the project
planning activities in the Initiate Phase. Services are estimated to begin within two
(2) weeks and no later than four (4) weeks from contract signature. OpenGov
reserves the right to adjust the schedule based on the availability of Customer or
OpenGov resources, and the timeliness of deliverables provided by the Customer.
7. Acceptance Procedure
OpenGov will submit completed deliverables to the Customer’s Project Manager for
review. Within five (5) business days of receipt, the Customer’s Project Manager will
either provide written acceptance or a list of requested revisions. In the event there
are requested revisions, the subsequent review period for acceptance will follow
the same timeline until final acceptance. If Customer does not respond within this
period, the deliverable will be deemed accepted. Once a deliverable is accepted, any
requested changes will require a paid Change Order.
Acceptance milestones and review timelines will be tracked in the Project Plan.
Both parties acknowledge that delays in task completion or unresolved issues may
impact the project timeline. If OpenGov determines in good faith that Customer is
not fulfilling its responsibilities under this SOW, OpenGov may place services on
hold following a minimum of five (5) business days’ written notice. The notice will
specify the actions needed to progress the project. During the hold period, OpenGov
PS-11121.1
5
may reallocate resources without penalty and will not be responsible for resulting
delays.
8. Modifications
The fees and estimated timeline are based on the scope and assumptions in this
SOW. If either party determines that a change to the scope is necessary, the parties
will collaborate to define the required modification, which may result in fee
adjustments based on OpenGov’s standard rates. All modifications must be
documented in a written Change Order and signed by both parties (“Change Order”) .
Examples of changes include revisions to the project timeline, deliverables, or
resource allocation.
9. Communication and Escalation Procedure
OpenGov and Customer agree to maintain regular communication in alignment with
the Project Plan to ensure progress, resolve questions promptly, and minimize risk.
Both parties will raise any issues or concerns in a timely manner. If challenges are
not resolved through standard project discussions, Customer and OpenGov Project
Managers will escalate to their respective executive leadership teams to jointly
determine a resolution and align on a path to successful implementation.
PS-11121.1
6
Exhibit 1: Implementation Activities
OpenGov Implementation Methodology Overview
Every OpenGov implementation follows a five-phase hybrid methodology designed to ensure a
structured and collaborative deployment. The phases are:
1. Initiate – OpenGov provisions access and performs initial system setup.
2. Validate – OpenGov works with the Customer to confirm requirements and review initial
configurations.
3. Configure – OpenGov completes system configuration as outlined in this SOW.
4. Train – OpenGov provides training to system administrators and/or end users, as applicable.
5. Launch – OpenGov provides post-go-live support and transitions the Customer to
OpenGov’s Customer Success Team.
Each implementation is structured around these phases. Deliverables, sign-offs, and completion
criteria are aligned to the relevant phase.
Procurement & Contract Management:
Use Cases Build for Procurement:
● Request Management
● Contract Management
● eSignatures
Initiate
Provisioning Procurement Website Instance
OpenGov will:
● Configure customer portal and upload Customer’s logo.
Customer will:
● Provide logo.
● Confirm access to the Portal.
Completion Criteria
● Customer verifies access to the site.
PS-11121.1
7
Validate
Technical Project Review
OpenGov will:
● Provide up to one (1) two-hour working session at the beginning of the project to:
o Confirm list of templates
o Review technical requirements
o Provide documentation on requirements and processes
OpenGov Assumptions:
● Boilerplate language will be provided within two (2) weeks immediately following the
kick-off meeting.
Customer will:
● Identify relevant participants for attendance.
● Confirm deliverables.
● Gather and provide relevant data for the project.
Completion Criteria
● Customer sign-off on the project plan.
Configure
Request Management
OpenGov will:
● Configure Request Management settings for up to three (3) workflows.
● Provide up to ten (10) hours of working sessions covering:
○ Configuration Review
○ Process Walkthrough(s)
○ User Acceptance Testing support
Customer will:
● Provide Request Management Approvers.
● Provide Departments.
● Provide a purchasing policy.
● Review, Test, and Sign off on configuration.
● Attend all working sessions.
OpenGov Assumptions:
● OpenGov assumes that the customer is responsible for testing its workflows, automations,
integrations, and configurations and will update the configurations as part of its testing and
training activities.
Completion Criteria
● Customer sign-off that Requisitions have been configured.
Contract Management Configuration
Create and Manage Contracts
OpenGov will:
PS-11121.1
8
● Provide one (1) - one hour Overview of the Contract Management Solution to Customer’s
System Administrator(s).
● Provide guidance and instruction to the System Administrator on creating and managing
contracts.
Customer will:
● Attend scheduled System Overview
● Create and manage contract records in the system with guidance from OpenGov.
Completion Criteria
● Contracts training has been conducted.
Contract Template Deployment
OpenGov will:
● Review & configure agreed upon contract templates.
● Configure up to One (1) total Contract Template(s) from customer provided standard
templates :
○ One (1) Non-Construction Contract Template will be built based on examples
collected from the customer up to fifty (50) pages in length.
OpenGov Assumption:
● If templates were not provided by the Customer prior to the creation of the SOW and the
customer provides templates during the project that exceed the assumptions above, the
Change Order Process will be followed.
Customer will:
● Provide templates.
● Test the configuration of each template by creating test projects and provide feedback.
● Validate and provide signoff on Contract templates.
Completion Criteria
● Customer sign-off that the Contract Template(s) have been configured.
eSignatures
OpenGov will:
● Enable eSignatures.
● Provide instructions on how to use eSignatures.
Customer will:
● Gather and provide relevant process information for eSignatures.
● Test the configuration and provide feedback.
Completion Criteria
● Customer sign-off on eSignatures.
Historical and/or Active Contract Metadata Upload
OpenGov will:
● Provide a compatible mapping document in Excel format for the metadata of contracts
(contracts log) to be uploaded into the system.
● Import the contract records listed in the contract log.
OpenGov Assumptions:
● OpenGov clean up/correction of attachments are not included in the scope of this project.
Customer will
PS-11121.1
9
● Customer will transfer their contract metadata into the mapping document provided by
OpenGov for import into OpenGov. OpenGov clean up/correction of imported logs are not
included in the scope of this project.
Completion Criteria
● Historical/Active Contract log has been loaded.
Admin Documents and Checklist Configuration
OpenGov will:
● Review & configure up to four (4) standard Admin Documents :
○ Proposal Viewer Agreement
○ Interview Invitation
○ Non-Award Letter
○ Notice of Intent to Award
Customer will:
● Provide Admin Documents.
Completion Criteria
● Admin Documents and Checklist have been configured.
Single Sign On (SSO) Implementation
OpenGov will:
● OpenGov implement identity provider initiated SSO for Microsoft ADFS, Microsoft Azure AD,
or Okta.
Customer will:
● Complete the SSO enablement form.
● Provide the information from the identity provided required to establish SAML or HTTPS
certification.
● Add OpenGov as a new application in Customer identity provider.
Completion Criteria
● Single Sign On has been configured.
Train
Procurement Training
OpenGov will:
● Provide training on system functionality. Topics include:
○ Contract Management
■ Document Assembly and E-signature
■ Contract Document Developer Tools
○ Request Management
Customer will:
● Attend training sessions as scheduled by the Project Manager and agreed to in the Project
Plan.
Completion Criteria
● Training has been conducted.
Working Sessions
OpenGov will:
PS-11121.1
10
● Assign practice exercises to Customer to gain familiarization.
● Assist Customer during first real-life solicitation posting, and opening (if during
deployment).
● Respond to questions regarding configured system functionality.
Customer will:
● Complete practice exercises to gain familiarization.
● Identify internal Admin Users & security permissions for all other users.
Completion Criteria
● Working sessions have been conducted.
Launch
HyperAdopt
OpenGov will:
● Provide up to eight (8) hours of remote working session(s) to answer any questions
following solution acceptance.
● Send Solution Acceptance Document
● Transition for project team to Customer Success.
Customer will:
● Identify issues and attend sessions.
● Sign Solution Acceptance Document
Completion Criteria
● Customer sign-off that the project has been completed.
PS-11121.1
11
Exhibit 2: Technical Requirements
Procurement Technical Requirements
Logo
● .png or .jpg file
● At least 300KB but not larger than 500KB
Historical/Active Contracts
● Single Flat file based on mapping document provided by OpenGov
● .csv or .xlsx format
Sample Documents or Boilerplate Templates
● PDF or Word format, including all related attachments and documents.
Templates
● All templates are assumed to be samples unless specified as a boilerplate. A boilerplate
template document that can be reused more than once without any substantive change.
● All templates assume up to 50 pages in length each unless otherwise specified in Exhibit 1.
Page count includes all attachments, forms, notices, and other documentation
● All templates are assumed to be non-construction unless otherwise specified in Exhibit 1. A
“Construction” template refers to templates inclusive of requirements, specifications, and
conditions for construction projects: including any of the following examples but not
limited to: regulations, codes, and standards, risk management, insurance management,
dispute resolution mechanisms, phases, tasks, dependencies, materials, equipment,
construction methods, liability and warranty periods.
Admin Documents
● PDF or Word format