The Anaplan Way – Statement of Work

Statement of Work

Updated On: March 1, 2017

Project(s): FP&A Budget and Forecasting
Anaplan and Client Confidential Page 1 of 20
 The Anaplan Way – Statement of Work

Table of Contents
Anaplan Statement of Work .................................................................................... 2
Project Scope......................................................................................................................... 4
Current State Overview............................................................................................................... 4
Project Objectives.......................................................................................................................... 5
Anaplan Model Design ......................................................................................................................... 8
Known Unknowns .......................................................................................................................... 8
Project Timeline ......................................................................................................... 10
Project Deliverables ................................................................................................. 11
Foundation Phase (Project Planning, Sprint Planning) .................................................. 11
Implementation Phase (Sprints, Sprints Retro) .............................................................. 12
Testing Phase (User Acceptance Testing, Tweak) .......................................................... 12
Deployment Phase (Go Live, Deployment & Post-Deployment Assistance) ......... 14
Project Team ................................................................................................................ 15
Anaplan Team ............................................................................................................................... 15
Anaplan Resource Availability and Timing ......................................................................... 16
Client Roles and Responsibilities ........................................................................................... 16
Other Project considerations ................................................................................ 18
Assumptions .................................................................................................................................. 18
Change Management Process ................................................................................................. 18
Proposed Fees ............................................................................................................................... 18
Cost, Billing Schedule and Payment Terms ....................................................................... 19

Anaplan Statement of Work

Client Name: Charlie Paws Inc (“Client”)
Anaplan Entity: Anaplan Limited (“Anaplan”)
SOW Effective Date: The date last signed by the parties below
Agreement: Anaplan SaaS Subscription Agreement
(“Agreement”)

Anaplan and Client Confidential Page 2 of 20

 The Anaplan Way – Statement of Work

Offer Valid Until: March 31, 2017 (must be fully executed by this
date)

This Statement of Work (“SOW”) is governed by the Agreement between the Anaplan
Entity named above and Client governing Client’s access to and use of the Anaplan
Service. All capitalized and undefined terms used in this SOW will have the definitions
set forth in the Agreement. This SOW shall be effective on the SOW Effective Date
indicated above.
Anaplan will perform the Professional Services described in this SOW in connection with
implementation of the Anaplan Service in connection with the Projects identified below.
The Professional Services include activities and deliverables designed to rapidly and cost
effectively configure the Anaplan Service and train Authorized Users on the Anaplan
Service. Client understands and acknowledges that the scope of system configuration
and other Professional Services is explicitly limited to the Project and specifications
outlined in this SOW and that all other configuration, ongoing support, or consulting
services are outside the scope of this SOW. Further, this SOW is not intended to add to
or modify any terms of the Agreement.
Anaplan will schedule the
activities described in this
SOW upon execution of this FP&A Budget and Forecasting
SOW. Project(s) Within
Scope Under this SOW:

Anaplan and Client Confidential Page 3 of 20

 The Anaplan Way – Statement of Work

Project Scope
Current State Overview

Charlie Paws Pet Supplies is seeking to replace their current tool(s) with the Anaplan
platform for budget, planning, and forecasting of a P&L concentrating on the modeling of
Revenue, COS, Overheads, HR Costs, Marketing and Capex. Charlie Paws Pet Supplies
currently uses Excel for modeling leveraging Salesforce, Workday, and Financial Force
(G/L) as data sources.

Charlie Paws Pet Supplies seeks to improve the efficiency and timeliness of the annual
budget process, in addition to introducing a quarterly forecast . Additionally, the client is
looking to eliminate Excel templates in use today in favor of a corporate standardized
template accessed and used in Anaplan.

The Anaplan model should be able to do the following:

 Full P&L modeling
 Support quarterly forecasting
 Allocation of Central Opex costs to Profit Centres
 What-if scenario planning for FP&A team to allow for iterations on both Sales and
Opex.
 Currency conversion

Anaplan and Client Confidential Page 4 of 20

 The Anaplan Way – Statement of Work

Project Objectives

Enablement
Requirements
 Launchpad services will be delivered by Anaplan instructors at Anaplan facilities.
 Scope of training includes 2 days of orientation on the Anaplan Service and agile
methodology, introduction to basic features and functionality, and introduction to
model building and best practices. Delivery will begin at a mutually agreed time.
 Launchpad Services are to be delivered within a one-week period beginning on a
mutually agreed start date and completed no later than 6 months after the
Effective Date. Note: Launchpad Services fees are non-cancelable and non-
refundable. Anaplan is not responsible for Client-initiated delays.

Data Hub
Requirements
• In order to support the budgeting and forecasting process, the Anaplan solution
will be configured with a data hub in order to centralize the Client’s metadata and
data.
• Client will provide data to support all metadata structures during Week 1 of the
project.

Data Integration
Requirements
Imports:
 The Data integration sources for the initial phase of the Anaplan implementation
include the following:
 Financial Force: General Ledger (Actual):
 Salesforce: Sales modeling
 Workday: Employee List | Attributes

• Client is responsible for extracting and preparing data from upstream data sources
for deployment activities.
• Client is responsible for data cleansing and file preparation for upload into the
Anaplan Service.
• Anaplan will load Data manually, leveraging flat files provided by the Client for this
engagement until an integration method has been choosen by client
• Client and Anaplan will configure import actions in order to load upstream data
into the Anaplan data hub. Model-to-model imports will also be configured to
move data from the data hub into the planning model.

Anaplan and Client Confidential Page 5 of 20

 The Anaplan Way – Statement of Work

• Client may use an external scheduling tool of its choice provided that Client is
responsible for implementing and configuring that tool to support additional
automation. Automation is limited to an unattended data load from a sourced
data file into Anaplan.
• The use of an ETL tool is at the Client’s discretion, and all configuration of any ETL
tool is the responsibility of the client.
• Frequency of data uploads will be determined during initial requirements sessions
and can be daily, weekly, and/or monthly as needed. Real-time data integration is
not in scope.

Exports:
• Client and Anaplan will configure export actions to produce flat files, in order to
load downstream data into other systems.
• The use of an ETL tool to push data from Anaplan into any other systems is at the
Client’s discretion, and all configuration of any ETL tool is the responsibility of the
client.

Budgeting and Forecasting Process

Process

Anaplan and Client Confidential Page 6 of 20

 The Anaplan Way – Statement of Work

Process
• Charlie Paws Pet Supplies budget cycle begins with an internal analysis of the
Business in October once the third quarter results are available. The Annual
budget process starts with the provision of templates to cost centre managers for
Opex Planning and to Sales Managers for sales planning. The templates include
current data YTD.
• At the beginning of November, the templates are submitted to the FP&A group and
are reviewed with the cost centre/sales managers offering the opportunity to make
changes prior to the review with the CFO later in the month. A final submission is
generated in December and sent to the CFO for final approval
• A quarterly reforecast process is then undertaken following exactly the same
process during April (Q1 - 3 Months actuals and 9 months forecast) July (Q2 - 6
Months actuals and 6 months forecast) and October (Q3 - 9 Months actuals and 3
months forecast)
Requirements Phase 1
• Create a full profit and loss at GL Level by Profit Centre
• Plan at local currency level with outputs in GBP
• Setup import routines for the customer, product, fixed asset, employee and cost
centre hierarchy and associated data
• Set up export process of final P&L data to enable load into target financial systems
• Create simple reporting dashboards and summary charts along with KPI’s
• Create a sales forecasting summary dashboard allowing entry by Sales Reps
• Create an Overheads,fixed asset and marketing costs planning dashboard and
associated approval process for FP&A team.
• Create an Allocation process allowing all central costs to be allocated to Profit
Centres
• Create simple scenario planning for changes in high level drivers and assumptions
• Client is responsible for data tie out and reconciliation
• Anaplan assumes the Client’s intended end-state business process is fully defined
and accepted by all key stakeholders within Client prior to project kickoff. Lack of
definition or internal acceptance may require business process re-engineering,
which is out of scope for this SOW and will likely impact timelines and cost of this
project.

Requirements Phase 2 (Out of scope)

• Create a full balance sheet and cashflow integrated with the P&L
• Create a Top down Process for both the Budget and Quarterly Reforecast to enable
the CFO to set initial targets for both Sales growth and Opex Cost Control
• Develop a detailed workforce planning model allowing cost centre managers to
make adjustments to employee renumeration, role and location.

Anaplan and Client Confidential Page 7 of 20

 The Anaplan Way – Statement of Work

Anaplan Model Design

The following diagram outlines the high level Anaplan Design depicting the potential
models that will be configured during this implementation.

Known Unknowns
The Anaplan Way aligns with an agile approach for implementation therefore items can
be re-prioritized during the course of the project.
Estimates for this project have been provided based on the information reviewed to
date. The parties acknowledge that certain objectives and deliverables may require
intermediate steps that are not identifiable or performable until the Services have
progressed to a certain degree. As a result, the timeline and scope of Services may need
to be adjusted during the term of this SOW based on such unknowns.

Anaplan and Client Confidential Page 8 of 20

 The Anaplan Way – Statement of Work

If necessary, the client and Anaplan will agree on a change order in the event of a
significant scope change that impacts costs.
The following are examples of intermediate steps that may not be identifiable or
performable until later in the Services:

• User Stories. Ability of Client to identify and provide sufficient detail in user
stories.
• Data Quality / completeness / sources. Data quality is a common challenge
discovered on most implementations and is typically unknown until project
initiation and actual import into Anaplan. To mitigate the risks/impact of this on
this engagement, client should provide all data for lists, hierarchies, and data
stories prior to user story creation to ensure any issues identified can be
addressed in a timely manner and avoid impact to project timelines.
• Data integration: Client has not yet idenfied a data integration and ETL tool.
• Level of client engagement - Client commitment to the project is essential to
ensure enablement and delivery of planned scope. For this engagement, the level
of commitment and engagement of client resources will need to be managed
closely to ensure there are no impacts to project scope or timelines.
• Business Process - Client’s to-be process needs to be determined prior to project
start. Alignment of to-be process changes can sometimes be challenging to obtain
within a client’s environment, therefore special attention to change management
by the client needs to be addressed early to avoid impact to project timelines and
acceptance of the overall Anaplan solution.
• UAT - Without proper attention to detail for UAT scripts that are written by the
client, UAT execution can be impacted resulting in un-necessary bugs, frustration,
and impact to timelines.
• Deployment. Client’s team availability for fields readiness, training and roll-out

Anaplan and Client Confidential Page 9 of 20

 The Anaplan Way – Statement of Work

Project Timeline
Based on the Project Scope documented herein listed above in the Project Objective
section above, we estimate that the implementation of the budgeting and forecasting
model will require 18 weeks from the start of the Project until the completion of UAT as
part of our Anaplan Way methodology, followed by 12 weeks of post Deployment
support. Timelines are subject to change based on initial start date and progression of
the Professional Services.
The estimated Project start date and estimated Project completion date are set forth
herein:
 Project Start Date: May 8, 2017
 Project End Date: November 30, 2017

The estimated Go Live date assumes the Client completes Launchpad training prior to
the Anaplan implementation team starting the Planning stage of the Project. The end
date is an estimated date, and will be automatically adjusted based on any delays to the
actual start date.

Anaplan and Client Confidential Page 10 of 20

 The Anaplan Way – Statement of Work

Project Deliverables
Anaplan will follow the Anaplan Way Methodology as it performs Professional Services in
support of implementation of the Project. This follows the traditional ‘scrum’
methodology.
Throughout The Anaplan Way phases (Foundation, Implementation, Testing,
Deployment), we consider a set of deliverables for the four Cornerstones: Model, Data &
Data Integration, Process and Deployment.
The deliverables are described here below, by phase, by cornerstone and by Entity
(Anaplan/Client).
Please find all the details on the Anaplan Way methodology on our Anaplan community
(requires an Anaplan login).

Foundation Phase (Project Planning, Sprint Planning)

Model Anaplan  Model Design schema

 Dashboard/end user experience design/prototype
Client  User Stories & Acceptance Criteria
Data & Data Anaplan  Data Flow Diagram
Integration
Client  Sample Data (Metadata & Source System data)
 List of the Source system to be integrated with
 User Stories & Acceptance Criteria
 ETL Requirements
 Data Integration Development Plan
Process Anaplan  Wireframes or prototype of dashboards to support User
Stories/End User Experience
Client  Target Business Process Definition & Requirements
 User roles, security and description requirements
 Gap analysis between Target and Current Process
 User Stories & Acceptance Criteria
Deployment Anaplan  Sprint Plan
 Weekly Status Reports
 Launchpad Enablement
Client  Certification Exam available after completion
 Change Management Plan
 Prioritized User Stories
 Project Manifesto

Anaplan and Client Confidential Page 11 of 20

 The Anaplan Way – Statement of Work

 Minimum Viable Product (MVP) Definition

 Decision to call the Anaplan Performance Test team for
real-world & large scale concurrency and Performance
tests
Implementation Phase (Sprints, Sprints Retro)

Model Anaplan  Sprint Review & Retrospectives

 Anaplan model configuration aligning to user stories (joint
ownership with client)
Client  Anaplan model configuration aligning to user stories (joint
ownership with Anaplan)
Data & Data Anaplan  Anaplan Imports Configured (joint ownership with client)
Integration  Anaplan Exports Configured (joint ownership with Anaplan)
Client  Anaplan Imports Configured (joint ownership with client)
 Anaplan Exports Configured (joint ownership with Anaplan)
 ETL Tool Configuration
 Scheduling Tool Configuration
 Anaplan Connect Configuration
Process Anaplan  Anaplan Dashboards configured (joint ownership with
client)
 Demonstrations to end users on future end-state (joint
ownership with client)
Client  Anaplan Dashboards configured (joint ownership with
Anaplan)
Deployment Anaplan  In-tool instructions & administration documentation
 Anaplan User Roles & Security configured (joint ownership
with client)
 Weekly Status Reports
 Performance Test scripts with SLA
 Demonstrations to end users on future end-state (joint
ownership with client)
Client  Anaplan User Roles & Security configured (joint ownership
with Anaplan)
 Updates to change management plan

Testing Phase (User Acceptance Testing, Tweak)

Model Anaplan  Functional Test Execution (joint ownership with client)

 Performance and concurrency Test Execution, performed

Anaplan and Client Confidential Page 12 of 20

 The Anaplan Way – Statement of Work

either by the Anaplan Service team or by the Anaplan

Performance team
 User Concurrency Performance Test Results
 Final performance testing report including scripting
performed, test executions, and Analysis.
 Updates to the model based on UAT Feedback
Client  UAT Test Scripts
 Test Execution (joint ownership with Anaplan)
 Updates to the model based on UAT Feedback

Data & Data Anaplan  Updates to imports & exports based on UAT Feedback
Integration
Client  UAT Integration Test Scripts
 Updates to imports & exports based on UAT Feedback
 Updates to data integration tooling based on testing
results
 Integration script execution on Production Data into
Production environment
 Production Data Upload Verification and sign off
Process Anaplan  Updates to the dashboards & underlying modules based
on UAT Feedback
Client  UAT Test Scripts
 Updates to the dashboards & underlying modules based on
UAT Feedback
Deployment Anaplan  Updates to user access rights based on UAT feedback
 Weekly Status Reports
Client  Updates to user access rights based on UAT feedback
 End User Training Plan
 Execution to change management plan with early adopters

Anaplan and Client Confidential Page 13 of 20

 The Anaplan Way – Statement of Work

Deployment Phase (Go Live, Deployment & Post-Deployment Assistance)

Model Anaplan  Production model (copied from UAT)

Client  Production model (copied from UAT)

Data & Data Anaplan 
Integration
Client 
Process Anaplan 

Client  Change Management plan delivered

Deployment Anaplan  Post Go-Live support hours (when purchased/applicable)
Client  End-user Training Materials & Execution
 End-user Onboarding

Anaplan and Client Confidential Page 14 of 20

 The Anaplan Way – Statement of Work

Project Team
Anaplan Team
Anaplan/Partn Primary Role Role Description
er Resources
Anaplan Serves as Client’s point of contact for Anaplan
Account SaaS Subscription Agreement
Executive
VP of Customer Coordinates with project leaders to align
Success resources and promote action in support of
Project plan and strategic direction. Serves as
escalation point for stakeholders and point of
contact for Client’s Executive Sponsor.
Director of Serves as escalation point throughout
Customer implementation
Success Leads bi-weekly steering committee meeting
to ensure stakeholders are aligned
Business Senior Anaplan analyst that works with Client
Partner on the design of Client’s solution
Intended to guide Client using best practices
in enhancing the efficiency and flexibility of
Client’s models.
Offers best practices, both from a business
process and Anaplan modeling standpoint,
when needed.
Model Builder Anaplan provision of services as a Model
Builder on behalf of Client. Model Builder
experience is intended to help create Client
model efficiently from Client user stories and
coaching Client model builders.
Enablement Anaplan Fundamentals training course
Consultant provided by Anaplan training staff or certified
partner trainers.
Onsite at Client facilities to up to 15 in-person
attendees

Anaplan and Client Confidential Page 15 of 20

 The Anaplan Way – Statement of Work

Anaplan Resource Availability and Timing

Anaplan and or its Subcontractor Partner will supply an implementation team with the
skills and experience required to successfully complete this Project. All assigned Anaplan
Customer Success staff and certified partners are experienced in business modeling,
design and have completed the Anaplan Model Builder Certification.
Unless otherwise negotiated, the resources assigned to this implementation will remain
on the implementation for the duration, but are not dedicated full-time to this
implementation. On occasion, Anaplan may need to change personnel. Should this
occur, Anaplan would coordinate with Client to minimize the impact but in no event shall
Client bear any additional costs or fees associated with any such change. Anaplan is
committed to minimizing the amount of disruption should a resource change be
required.
The Customer’s project lead will estimate during the scoping phase, prior to
implementation, if the project requires resources and support from an Anaplan team
specialized in performance testing. The decision is driven by model size, number of
users, concurrency and by the complexities of the business processes. The Anaplan
Performance Test team needs to be scheduled ahead of time and is billable.
Client Roles and Responsibilities
Anaplan’s Business Partner will service as Client’s primary contact for Anaplan. The
Business Partner will work directly with the Client’s Scrum Master/Project Manager, to
plan and coordinate all activities within the scope of the schedule and the budget of this
SOW. The Client’s Project Manager must have the authority to represent the Client’s
objectives and requirements to Anaplan and make key decisions relating to the
successful execution of each phase of the implementation of the Project.

Anaplan and Client Confidential Page 16 of 20

 The Anaplan Way – Statement of Work

Client is expected to do the following in support of the objectives of the Project and
the performance of Professional Services under this SOW:
• Commit to The Anaplan Way methodology as outlined by Anaplan including client
attendance at all requirements workshops, daily stand up meetings, sprint reviews
and UAT sessions
• Commit to providing resources to perform the Client roles and responsibilities
defined in this proposal and/or outlined in the table above.
• Commit to and act in accordance with The Anaplan Way methodology.
• Commit attendance at all requirements workshops, daily stand up meetings, sprint
reviews and UAT sessions.
• Define a Project steering committee that consists of at least 1 client executive
sponsor each from business and IT that will meet at least bi-weekly to review
Project progress and assess risks.
• Perform final configuration of user access rights for all Anaplan end-users and
grant the appropriate level of permissions based on pre-defined role-based
security.
• Adhere to the scope and design of the Anaplan solution as outlined in this SOW.
• Note: In the event the Client resources are unable to commit to the time outlined
as required for this engagement, timelines and costs may be impacted and
additional post deployment support from the Anaplan team may be required.

Anaplan and Client Confidential Page 17 of 20

 The Anaplan Way – Statement of Work

Other Project considerations

Assumptions
If any of the following assumptions is inaccurate, the scope, timing, or economic terms
of this SOW will need to be adjusted accordingly, pursuant to the change management
process described below.

 All aspects of this SOW and deliverables will be delivered in English only;
 Client will provide access to required resources on a timely basis;
 The scope of this engagement will remain constant unless otherwise agreed to by
the parties, in the form of a mutually executed change order; and
 Services will be performed at Anaplan’s offices or another remote site, or Client
premises as agreed by the parties.
 Note that Anaplan Connect is a utility that is downloaded and installed within the
client environment.

Change Management Process

Either party may request changes to Professional Services. Anaplan will work with Client
to prepare an impact analysis for the change based on the request, provide a quotation
for the additional work, identify any impact on the Project timeline, and formulate an
action plan.
No change request will take effect until mutually approved in writing. Each party will
continue to perform its obligations under the preexisting terms of the SOW until the
agreed upon change takes effect.
Proposed Fees
Anaplan will perform Professional Services under this SOW on a time and materials
basis. It might include the Services from the Anaplan Performance Team, if requested.
As such, the start and end dates, as well as expected number of hours are good faith
estimate as to the work-effort involved in the Professional Services Anaplan performs in
support of implementation of the Project.
Additional hours may be required to complete the Project, in which case the parties will
complete a change order.
Anaplan may also charge for reasonable out of pocket travel and related expenses (T&E)
in addition to the fees set forth above in accordance with the Anaplan Travel Policy for
Professional Services & Customer Success Engagements, which is available upon
request.

Anaplan and Client Confidential Page 18 of 20

 The Anaplan Way – Statement of Work

Services Quantity Price (Per Total Price

(Days/Courses) Day/Course)
Launchpad Services (Courses) 1 $xx $xx
Business Partner (Days) 15 $xx $xx
Model Builder (Days) 45 $xx $xx
Services Fees USD £ $xx

TOTAL COST ESTIMATE: $xx+ T&E

Cost, Billing Schedule and Payment Terms
Anaplan will invoice Client for Professional Services at the rates set forth below and in
accordance with the following terms and conditions.
Invoicing
Anaplan will invoice Client monthly in arrears on a time and material basis as it performs
services under this SOW.
Payment Terms
Net 30 from invoice date.
Travel and Expenses
Anaplan may also charge for reasonable out of pocket travel and related expenses in
addition to the fees set forth above in accordance with the Anaplan Travel Policy for
Professional Services & Customer Success Engagements, which is available upon
request.

[signature block on next page]

Anaplan and Client Confidential Page 19 of 20

 The Anaplan Way – Statement of Work

Accepted and agreed to as of the date last signed by the parties below:

Anaplan Limited (“Anaplan”)

By:

Printed
Name:

Title:

Date:

Interserve Plc (“Client”)

By:

Printed
Name:

Title:

Date:

Anaplan and Client Confidential Page 20 of 20