HomeMy WebLinkAboutKittitas County SOW Microsoft Purview Data Security Strategy PSA v4 20260929
CONFIDENTIAL
Page 1 of 3
SOW SOW Tem plate 1KITTITAS COUNTY
STATEMENT OF WORK
This Statement of Work (this “SOW”) is entered into by and between Kittitas County (“County”), a political subdivision of
the State of Washington; and Trace3, LLC (“Contractor”). County and Contractor are each, a “Party,” and, together, the
“Parties.”
The purpose of this SOW is for Contractor to provide technical support for the Microsoft Purview Data Security
Strategy project (the “Project”).
The duration of this SOW shall be from the date of execution (the last date signed below) until the completion of
the Project (the “SOW Term”).
The Parties’ addresses and points of contact for the administration of this SOW are as follows:
COUNTY
205 W. 5th Ave. Ste. 13
Ellensburg, WA 98926
Bill Davis
IT Infrastructure Manager
Bill.davis@co.kittitas.wa.us
(509) 933-8293
CONTRACTOR
7505 Irvine Center Drive, Suite 100
Irvine, CA 92618
Tyler Cook
Account Executive
tyler.cook@trace3.com
(360) 509-8507
This SOW includes the following, which are attached hereto and incorporated herein:
Attachment “A”: Scope of Work
Attachment “B”: Compensation
Attachment “C”: Vendor SOW (the “SOW”)
CONFIDENTIAL
Page 2 of 3
ATTACHMENT “A”
SCOPE OF WORK
See the SOW in Attachment “C” for details of the scope of work for the Project.
CONFIDENTIAL
Page 3 of 3
ATTACHMENT “B”
COMPENSATION
As full compensation for satisfactory performance of the work described in Attachment “A”, and within thirty
(30) days of receiving Contractor’s itemized invoice, the County shall pay Contractor the following amount(s) plus any
applicable taxes as detailed in Contractor’s invoice: $66,218.00.
See the SOW in Attachment “C” for additional details of compensation for the Project.
Statement of Work
Please note the pricing and other terms and conditions proposed in this are only valid for 30 calendar
days from Trace3's initial presentation of this to Client.
ATTACHMENT “C”
Vendor SOW
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW Tem plate 1
SOW SOW
SOW SOW Tem plate 1SOW SOW Tem plate 1SOW SOW TemStatement of Work
Kittitas County
Microsoft Purview Data Security Strategy
Trace3
Account Manager: Tyler Cook
Services Solutions Manager: Tracey Hart
September 29, 2026
Version: 4.0
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 1
1 PROJECT DETAILS
This Statement of Work (this "SOW"), dated as of the date last signed below (“Effective Date”), is between Trace3, LLC, a
California limited liability company ("Trace3"), and the entity named "Kittitas County" below ("Client" and together with
Trace3, the “Parties”).
Summary: This SOW is issued pursuant to and governed by the agreement listed as “Master Agreement” below (the
"Master Agreement"). Pursuant to the terms of the Master Agreement and this SOW, Client desires Trace3 to provide
information technology consulting services (the "Services"), hardware, and/or software products (the "Products" and
together with the Services, the "Deliverables") to Client as described in this SOW (the "Project"). All capitalized terms not
defined in this SOW will have the meanings given to them in the Master Agreement.
Client: Kittitas County
Master Agreement: Kittitas County (MSA) (Final Executed Version 9-15-26)
Master Agreement Date: September 15, 2026
Project Name: Microsoft Purview Data Security Strategy
Agreement: This SOW consists of this signature page and the following Annexes, which are incorporated into this SOW:
Annex A: Project Specifications
Annex B: Project Pricing
Contact Information:
Trace3 Contacts:
Account Manager: Tyler Cook
Phone: 360-509-8507
E-mail: tyler.cook@trace3.com
Trace3, LLC
7505 Irvine Center Drive, Suite 100
Irvine, CA 92618
Attention: Legal Department
Fax: 949-333-2400
E-mail: legal@trace3.com
Services Solutions Manager: Tracey Hart
Phone: 949-433-5601
E-mail: tracey.hart@trace3.com
Client Contacts:
Client Sponsor: Zane Kinney
Title: Assistant Director
E-mail: zane.kinney@co.kittitas.wa.us
Kittitas County
205 West 5th Avenue Ste 13
Ellensburg, WA 98926
Signature: Client and Trace3 hereby agree to the terms of this SOW by signing below:
KITTITAS COUNTY
TRACE3, LLC
By: ____________________________________
Name: _________________________________
Title: __________________________________
Date: __________________________________
By: ____________________________________
Name: _________________________________
Title: __________________________________
Date: __________________________________
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 2
2 ANNEX A – PROJECT SPECIFICATIONS
2.1 BACKGROUND AND PROJECT OBJECTIVES
2.1.1 Client Background Information
Client is a political subdivision of the State of Washington serving its residents across approximately twenty -four (24)
departments and agencies, including the Sheriff's Office, the County Attorney, the Auditor's Office, and Public Works. The
Client's workforce operates on Microsoft 365 ("M365") G3 licensing. Today, the Client's response to Public Records Act
("PRA") requests under RCW 42.56 and to litigation hold obligations is decentralized and largely manual. Every request is
routed through Central Information Technology ("IT"), which exports data from individual devices, runs third-party search
tools, and de-duplicates results by hand. Litigation holds are issued verbally or by email and depend on the custodian's
behavior and IT's recollection. The Client desires a more defensible, contemporaneous record of what was searched, by
whom, and when. Trace3, through its Workplace Security & Identity Practice, proposes to modernize the Client's
eDiscovery process by operationalizing the Microsoft Purview eDiscovery capabilities already included in the County's
existing G3 entitlement. This Phase 1 engagement establishes a centralized, scoped, automated, and audit -ready
eDiscovery workflow without procuring any new third-party tooling or additional Microsoft licensing.
2.1.2 Business Objectives
• Transition from a decentralized, manual, device-based eDiscovery process to a centralized, automated workflow
built on Microsoft Purview
• Reduce Central IT's dependency on routine records production by enabling trained departmental designees to
perform first-pass searches within defined boundaries
• Eliminate the risk of spoliation by replacing verbal and email-based litigation holds with system-enforced,
auditable Preservation in Place holds
• Reduce legal review costs and accelerate statutory PRA compliance through deduplication and decryption of
review sets at export
• Establish a defensible, court-ready audit trail for every search to reduce the County's exposure in PRA and litigation
disputes
2.1.3 Technical Objectives
• Standardize department-identifying attributes in Microsoft Entra ID across in-scope users so that eDiscovery
boundaries can be reliably enforced
• Map in-scope SharePoint Online sites to confirm Uniform Resource Locator ("URL") conventions are recognized
by Purview eDiscovery filters, and recommend remediation where they are not
• Design and implement Role-Based Access Control ("RBAC") role groups and up to twenty-four (24) Compliance
Security Filters that scope each department's data handlers to their own agency's mailboxes and SharePoint sites
• Enable the Public Records Officer ("PRO") to generate search result statistics and estimates in accordance with
Microsoft service descriptions
• Configure deduplication and decryption at export to produce smaller, cleaner review sets for legal hand-off
• Transition the County from verbal and email litigation holds to Preservation in Place holds administered directly
in Purview
• Validate that all search boundaries and holds operate as designed and produce a defensible, contemporaneous
audit trail
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 3
2.2 SCOPE OF WORK
Trace3 will perform and deliver the Deliverables as described in this SOW. Any and all additional Deliverables not
specifically described in this SOW will be addressed in separate statements of work. The following items are within the
scope of work contemplated by this SOW:
2.2.1 In-Scope Hardware/Software/Environments/Sites (“In-Scope Items”)
• In-Scope Software (“In-Scope Software”)
o Microsoft 365 Tenant
• In-Scope Environments (“In-Scope Environments”)
o Microsoft Purview eDiscovery (Standard)
o Up to twenty-four (24) Microsoft Purview Compliance Security Filters
o Microsoft Purview Preservation in Place/eDiscovery holds
o Microsoft Entra ID — user attribute standardization for in-scope users
o Microsoft Exchange Online mailboxes
o Microsoft SharePoint Online/OneDrive sites
o Microsoft Purview RBAC role groups and permissions
• In-Scope Sites (“In-Scope Sites”)
o Up to twenty-four (24) departments and agencies within Client's workforce
2.2.2 Work Location(s)
• All Services will be performed remotely
o Trace3 will connect to the Client's M365 environment using delegated administrative access and will
conduct working sessions via Microsoft Teams or Webex. No on-site presence is planned
2.2.3 Scope Particulars
Plan Phase
• Project Initiation
o Provide Client with Project kick-off pre-requisites including required Client attendees, existing
environment documentation requests, and preparation checklists (if applicable)
o Conduct Project kick-off meeting with Client’s team to:
o Validate Project Scope, goals, and communicated outcomes
o Validate Project governance framework in support of the Project Management Services
o Validate Project schedule, key milestones and critical path items
o Validate Change Request process
o Validate Project contacts list
o Validate Pre-requisites and other Project specific details required in support of Scope performance
• Create a Project Plan containing a Project Schedule
Discovery Phase
• Scan Microsoft Entra ID to inventory and assess department -identifying attributes (e.g., department, agency)
across In-Scope users
• Identify gaps and inconsistencies in attribute population that would impair reliable Compliance Security Filter
scoping
• Map In-Scope SharePoint Online sites and document libraries to confirm URL conventions are recognized by
Purview eDiscovery filters
• Document the current-state eDiscovery process and confirm the In-Scope department list for up to twenty-four
(24) departments
• Produce a Discovery findings summary with prioritized remediation recommendations
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 4
Design Phase
• Design the compliance boundary architecture, including the RBAC role -group model that restricts each
department's data handlers to their own agency's mailboxes and SharePoint sites (e.g., a "Sheriff – eDiscovery
Managers" role group)
• Define the Compliance Security Filter logic and naming standard for up to twenty-four (24) departmental filters
keyed to the standardized Entra ID attributes and mapped SharePoint URLs
• Design the Preservation in Place hold model to replace verbal and email litigation holds
• Design the export configuration for deduplication and decryption to support cleaner legal review hand -off
• Produce an as-built design specification for County review and approval before implementation
Execute Phase
• Remediate Entra ID department attributes for In-Scope users in accordance with the approved Discovery
recommendations
• Create and configure the RBAC role groups and assign departmental data handlers
• Implement up to twenty-four (24) Compliance Security Filters and validate that each filter correctly scopes search
results to the owning department's mailboxes and SharePoint sites only
• Configure Preservation in Place holds and validate that content is preserved even when deleted or when a
custodian departs
• Enable the PRO to generate search result statistics and estimates;
• Configure deduplication and decryption at export and validate output against a representative review set
• Conduct end-to-end validation of the five (5) operational use cases (scoped PRA search, litigation hold, designee
self-service, cleaner review hand-off, and audit defensibility)
Closure Phase
• Deliver as-built documentation of the implemented boundary architecture, Compliance Security Filters, hold
model, and export configuration
• Deliver up to two (2) ninety (90)-minute administrator enablement sessions for Central IT covering the boundary
architecture and ongoing administration
• Deliver up to two (2) ninety (90)-minute working sessions for departmental designees covering query
construction, search statistics, and exports
• Conduct a project closure review and confirm acceptance criteria are met
• Provide recommendations for optional downstream phases (e.g., Premium eDiscovery review sets and predictive
coding) should the County's needs grow beyond G3
• Provide Project lessons learned documentation
• Complete Project closure meeting with Project team
• Conduct Knowledge Transfer:
o Provide an informal overview of administrative and operational functions on or before the Services
completion with the necessary and identified staff available for the session
• Deliver Completion Certificate and attain Client sign off
*Please note: Knowledge Transfer does not replace formal system training. Knowledge transfer is delivered as part of
the Services and will be four (4) sessions lasting up to ninety (90) minutes each. Client must identify necessary staff
required/needed for the Knowledge Transfer session and do everything they can to have the identified resources
available for the session. This transfer of knowledge will be conducted in an informal and informative way, not
prepared in advance, and without creating any knowledge artifacts such as documents, diagrams or videos. A
recording of the session may be done at Client’s request. If recorded, it will be distributed to the Client within three
(3) business days of the completion of the Knowledge Transfer session.
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 5
2.2.4 Deliverables and Acceptance
The following table summarizes what Deliverables will be accomplished in each Project Phase:
Project Phase Deliverables
Plan Phase
• Project Plan
• Project Status Reports during Project term (as agreed upon during Project kickoff)
• Project charter
• Communications plan
• Project schedule
Discovery Phase • Discovery findings summary with Entra ID attribute assessment, SharePoint site mapping,
and prioritized remediation recommendations
Closure Phase
• As-Built Document
• Project lessons learned documentation
• Knowledge Transfer
• Approved Completion Certificate
Acceptance shall conform to such criteria as may be developed and agreed upon by both Parties as defined during the
Project kick-off.
2.2.5 Estimated Project Timeline
2.2.5.1 Start Date
This Project is estimated to start on or after November 1, 2026 (“Start Date”). Depending on resource availability, this
estimate is subject to change at Trace3’s discretion. The assigned Project lead will confirm the Project Start Date when
they are engaged.
2.2.5.2 End Date
This Project is estimated to end no later than January 31, 2027 (“End Date”).
2.2.5.3 Estimated Timeline
The below timeline reflects what Trace3 estimates the duration of this Project to be. This is only a preliminary estimate
based on the information currently presented to Trace3 and is subject to change once the Project commences. Any
changes to this estimate will be communicated to Client by the Project Lead.
Estimated Timeline
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8
Plan Phase
Discovery Phase
Design Phase
Execute Phase
Closure
Phase
2.2.6 Project Management (“Project Management Services”)
The Trace3 Project Manager will be responsible for the overall Project and coordination of Project management activities
with Client’s Project Lead. The Project Leads will be responsible for coordinating all engagement activities and scheduling
resources as well as for serving as the single point of contact for Trace3 and Client for this engagement.
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 6
The Project will be managed using formal project management methodologies consistent with the Project Management
Institute Project Management Body of Knowledge (“PMBOK”) framework. The following is a list of tasks which will be
performed to manage the Project:
Project Initiation
• Facilitate Project kick-off meeting to review objectives, Scope, budget, Deliverables, timeline, and success criteria
• Identify initial assumptions, dependencies, critical path items, and constraints
Project Planning
• Verify Client specific details including service hours, maintenance process(es), and administrative requirements
• Establish communication plan (“Communication Plan”) to be executed throughout the Project
• Work with technical team(s) to establish an approved detailed Project Plan/Schedule
Project Execution
• Drive and manage Project tasks per established Project Plan
• Facilitate scheduling for on-demand meetings to support Project efforts
Control and Monitoring
• Risk and issue management to identify and manage risks, execute established mitigation plans, and facilitate
resolution of Project execution issues
• Financial management – monitor and manage Project budget (Labor, T&E, misc.)
• Establish a one-page Project overview summarizing Project health and status
• Confirm Client acceptance at the end of each milestone or Deliverable
• Conduct weekly status meetings to deliver communication on the current Project health and status to Project
stakeholders
• Provide weekly status reports to document and communicate Project health and status
Closure
• Confirm Client’s acceptance of Project Completion
2.3 OUT OF SCOPE
The following items are outside the scope of Deliverables contemplated by this SOW:
• Large-scale site restructuring, if required, not listed in the Scope of Work section of this SOW
• Data migration or protection services not clearly detailed within the Scope of Work section of this SOW
• All levels of support not specifically detailed within the Scope of Work section of this SOW
• Working on open maintenance and support issues unless the maintenance and support case and remedial efforts
towards resolution are explicitly defined in this SOW
• Any specific task or Deliverables not clearly stated in the Scope of Work section of this SOW
Any mutually agreed upon changes to the Scope of Services shall be set forth in a Change Request Form as detailed in the
Project Change Process section below.
2.4 PROJECT CHANGE PROCESS
Trace3 is not responsible for issues out of its control, which sometimes includes Client unpreparedness, technical issues
(based on Client responsibilities in this SOW), manufacturer bugs (code issues), hardware failures after forty -eight (48)
hour burn-in, or additional features desired (not outlined in this SOW). Changes in Services requirements to this SOW or
issues out of Trace3’s control will require a written Change Order, submitted and signed by both Parties, and billed in
addition to the Fees outlined in this SOW.
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 7
Either Party may initiate requests to change or modify the Project, a Project Phase, or the Deliverable Specifications (each,
a "Change Request").
Any Change Request will be governed by (a) the Master Agreement and will utilize the form of written change request
(the “Change Request Form”), if applicable, or (b) the following procedure, if the Master Agreement does not address
Change Requests (the “Project Change Process”).
The Project Lead of the Party requesting a Change Request will submit a Change Request Form to the other Party's Project
Lead in a clear and concise manner (each, a “Change Request Form”). Upon execution of a mutually acceptable Change
Request Form by both Parties, the obligations of the Parties with respect to such Change Request will be incorporated
under this SOW. Commencement of the provision of a Change Request is conditioned upon Trace3's receipt of (a) a Change
Request Form signed by both Parties, and (b) either a signed additional Purchase Order or Purchase Order Exception
authorizing the mutually agreed upon price for each Change Request.
2.5 ASSUMPTIONS AND CONSTRAINTS
2.5.1 Scope of Services Assumptions
• Client's M365 G3 licensing is and remains active for all In-Scope users for the duration of the engagement, and
includes Purview eDiscovery (Standard) entitlements
• The Project covers up to twenty-four (24) In-Scope departments and the implementation of up to twenty -four
(24) Compliance Security Filters
• Entra ID attribute remediation is limited to department-identifying attributes for In-Scope users and does not
require directory synchronization redesign or HR-system integration
• SharePoint Online site URL conventions are remediable through standard administrative configuration; large-scale
site restructuring, if required, is out of scope
• Remote access will be provided via the County's approved method (e.g., Microsoft Teams, Webex, or Virtual
Private Network ("VPN")) and delegated administrative credentials with sufficient privilege to perform the In -
Scope work
• Trace3’s remediation efforts are limited to the In-Scope attribute, URL alignment, and configuration activities
expressly described in this SOW. Broader data governance or information architecture remediation is outside
the scope of this SOW.
• Client remains responsible for legal and compliance decisions related to its use of the configured Microsoft
Purview capabilities. Trace3 is not providing legal advice under this SOW.
• Services will be delivered continuously from the start of the Project until the completion of the Deliverables or
allotted time unless otherwise stated in this document with the exception of holidays and scheduled time off.
2.5.2 General Assumptions
The following general assumptions will apply to the execution of the Deliverables:
• Services will generally be performed during normal business hours which are defined as being between 8:00 AM
and 5:00 PM Client’s local time. If Services are needed after normal business hours, Trace3 and Client must
mutually agree upon the schedule before such after-hours Services commence.
• Services detailed in this SOW are expected to be fully delivered by either (a) the End Date or (b) within twelve (12)
months of the Effective Date (“Expiration Date”). Client and Trace3 acknowledge and agree that at any point after
the Effective Date, should Client or Trace3 reasonably foresee the Services extending beyond Expiration Date,
renegotiation of terms of this SOW will be documented using a Project Change Request prior to Expiration Date.
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 8
• If applicable, systems within the scope of this SOW must have an active and current maintenance and support
contract (“Maintenance Agreement”). Evaluation licenses or hardware must be converted to fully licensed and
entitled levels prior to commencement of the engagement.
• Client acknowledges and accepts that any hardware or software not available may delay the Project schedule and
be subject to a Change Request.
• If requested by Trace3, Client will provide a Trace3 field resource remote access to Client's IT environment with
access to In-Scope Items from a secure remote location. When feasible, Trace3 will complete all Project work
remotely (a) over Webex sessions with the Parties’ resources, (b) Teams sessions with the Parties’ resources, or
(c) over a VPN connection with Trace3 resources.
2.6 RESPONSIBILITIES
2.6.1 Trace3 Responsibilities
During the Term, Trace3 will undertake the following responsibilities reasonably applicable to the execution of the
Deliverables:
• Trace3 will submit written reports, and any documentation related to the status and success of execution of the
Deliverables to Client as mutually agreed upon by the Parties.
• Trace3 will provide Client a lead contact person for the Project (the "Trace3 Project Lead") with such qualifications,
expertise, and knowledge necessary and applicable for Trace3 to fulfill its obligations under this SOW.
• Trace3 will make commercially reasonable efforts to maintain consistency in the Trace3 Project team which will
be responsible for the delivery of Services hereunder. Trace3 and Client agree that certain staffing factors (e.g.
terminations, resignations, promotions, long term disabilities) may require changes in the Trace3 resources
delivering the Services hereunder. In the event that a change of Trace3 personnel is required, Trace3 shall: (i) if
the applicable personnel is named under this SOW, provide reasonable notice to Client of such change, (ii) ensure
that a full knowledge transfer occurs between new and incumbent personnel without cost to Client, and (iii)
ensure that any new personnel have the skills and experience necessary to perform the Services.
2.6.2 Client Responsibilities
During the Term, Client will undertake the following responsibilities reasonably applicable to the performance and delivery
of the Deliverables:
• Client will designate a single point of contact and the departmental designees to be trained, and will make
stakeholders reasonably available for working sessions.
• Client will provision required access within three (3) business days of request; delays beyond five (5) business days
may result in a schedule and/or fee adjustment via a Change Request.
• Client will provide Trace3 personnel assigned to work at Client's premises reasonable use of Client's facilities. Prior
to the Project Start Date, Client will complete all necessary facilities arrangements, and such arrangements will
stay in place throughout the Term.
• Client will make available to Trace3 knowledgeable Client personnel promptly upon a request from Trace3 via
phone or e-mail to provide background information and clarification of information required by Trace3 personnel
to perform and deliver the Deliverables.
• Client is responsible for providing an environment that is prepared and ready for Services to commence on the
Project Start Date.
• Client will be responsible for any business and data application testing and all necessary data backup in
preparation for and during the performance and delivery of the Deliverables. It is recommended Client perform a
backup of all data that could be impacted by this Project prior to the Project Start Date.
• Client is responsible for the identification and interpretation of, and ensuring compliance with, any laws, statutes,
rules, regulations and standards applicable to its or its affiliates’ business or operations.
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 9
• The documentation and information provided by Client to Trace3 personnel will be accurate, complete , and up-
to-date.
• Client hereby grants Trace3 a limited, non-transferable license during the Term to use certain proprietary
computer systems, technologies, and data owned by Client and its affiliates, which are necessary for Trace3 to
perform and deliver the Deliverables.
• If required by Trace3, Client will participate in testing as directed by Trace3.
• Client will provide Trace3 a lead contact person for the Project (the "Client Project Lead") with such qualifications,
expertise, and knowledge necessary and applicable for the Client to fulfill its obligations under this SOW.
In the event Trace3 is delayed in its performance of Services on account of Client’s failure or delay in performance of its
responsibilities, and such failure or delay on the part of Client continues for more than five (5) business days after receip t
of written notice from Trace3, Trace3 shall be entitled to an adjustment in the Fees in an amount representing the
additional out-of-pocket expenses incurred by Trace3 as a result of such delay.
Statement of Work
September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 10
3 ANNEX B – PROJECT PRICING
3.1 FEES
Fixed Fee Project: Client will pay Trace3 a fixed fee of $66,218.00 (the "Fees") for the complete provision of the
Deliverables. The Fees include professional services (e.g., systems architecture, Project Management Services and
engineering/technician resources).
The Fees are based on the terms of this SOW and the scope of the Deliverables being provided under this SOW. Any change
to the terms of this SOW, the Project, and/or the scope of the Deliverables, whether by the failure to meet a responsibility,
a Change Request or otherwise, may result in a modification of the Fees. Taxes are not included herein and shall be
finalized at time of invoicing.
3.2 BILLING
Trace3 will invoice Client for Services as follows:
• 100% of Fees upon Trace3’s receipt of a Completion Certificate signed by Client for completion of the provision of
all Deliverables
3.3 TRAVEL AND EXPENSES
Client is responsible for any travel and related costs or expenses incurred by Trace3 personnel in furtherance of the
provision of the Deliverables ("Travel and Expenses"). Trace3 will invoice Client for any Travel and Expenses incurred by
its personnel as such expenses are incurred and at the actual amount incurred and allowab le under Trace3’s travel and
expense policies.
Trace3 will use reasonable efforts to staff Project with resources from the local service area to mitigate expenses. When
local resources cannot provide availability or specific expertise in a timely manner to meet Project objectives and schedule,
Trace3 may assign resources from other service areas.
The Parties will agree to travel arrangements prior to the incurrence of travel -related expenses.