Wor
12
13.
14.
15.
16.
17.
18.
19.
20
kday.
. This SOW assumes one primary source system for Customers data management requirements,
assumed to be Customer’s Workday system.
Agreement # 232049 — Confidential
The estimated duration of the Project is 18 weeks including 2 weeks part-time Post-Production Support.
The duration of the Project is dependent upon the complexity of Customer’s planning requirements and
could be longer or shorter. If the Project’s start date is delayed by Customer for any reason, Customer
understands that Workday’s ability to staff the engagement and meet the target go-live date could be at
risk and may be delayed. Workday shall work closely with Customer to identify the impacts of any delays
and shall discuss available options and additional costs before coming to agreement on the next steps.
If Customer cannot meet set completion dates for deliverables and milestones, Workday shall revisit and
revise the Project’s costs, completion date, and approach to completing the Project.
If the Project is delayed due to circumstances outside the control of Workday, Workday shall revisit and
revise the Project’s costs.
All business units, subsidiaries and affiliates share the same fiscal year period and utilize a common set
of templates.
Professional Services Data is provided to Workday in a supported format and is accurate, complete and
error free.
Customer shall be responsible for making any modifications or corrections to Customer's configuration
once Workday has deployed the configuration under this SOW;
Project includes deployment for the Schools only, however City & Schools will be included in the level
structure and design workshops to enable future roll-out of Adaptive City-wide in a later phase. All City
specific planning requirements (including models, reports and other deliverables) will be addressed in a
subsequent phase.
. Workday Data Management/Integration Assumptions.
a. If Customer Data shall be accessed via an API, only the fields exposed by the standard source system
API shall be extracted to Customer’s Workday Adaptive Planning Instance(s).
b. An Integration extracts data from one Instance of the source application(s) and imports data into one
Customer Workday Adaptive Planning Instance;
c. Customer Data is organized in the source application(s) in standard (non-custom) designated objects;
Workday has no obligation to provide maintenance, support or updates to Customer in connection with
any impact to the functionality an Integration resulting from changes made by Customer to any source
system, including but not limited to changes to its source system API(s).
Project Risks
Workday has identified, as most significant, the following Project Risks for this Project:
1. Change Management is critical to the success of any deployment of the Workday Adaptive Planning
Service. Customer must identify its Change Manager early in the Project Timeline to ensure that Customer
provides timely communication and education relating to the Workday Adaptive Planning Service.
2. Timely decision making is critical to the progress and ultimate success of the deployment. When a decision
cannot be made through consensus, the Project team shall escalate the decision through the appropriate
channels within both Customer and Workday to arrive at a resolution. If key decisions cannot be made in
a timely manner, the deployment timeline and/or resources may be impacted.
3. Many Project delays can be attributed to challenges in cleaning and converting Professional Services Data.
Customer must prioritize this Project activity as soon as is reasonably possible after Project commencement
in order to reduce any impact to the Project Timeline.
©2020 Workday Page 17 of 23
SOW — Launch Deployment (Workday Adaptive Planning) v20.9
