Search

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

Wor k d Q y: Agreement # 232049 — Confidential

5. Project Scope

Workday shall design and configure within Customer's Workday Adaptive Planning Instance(s) the generally
available functionality of the Workday Adaptive Planning Service components that fall within the Product Scope
set forth below. Workday shall determine the correct configuration of each component of the Workday Adaptive
Planning Service within the Product Scope listed below during the early stages of the Project based on Customer’s
use case, volume and planning processes. Customer's listed planning processes represent key business
processes that Workday shall design and configure in accordance with Customer's priorities. The final list of
planning processes shall be agreed by Customer and Workday during the Model/Validate stage of the Project,
with appropriate consideration given to Project timeline, resources and budget.

Workday Adaptive Planning Launch Package Financial Planning

Product Scope. The Product Scope for the Project includes the deployment of the following Workday Adaptive
Planning Service components in Customer’s Workday Adaptive Planning Instance(s):

e Planning and Reporting

Functional Scope. Having determined a set of desired functionalities to support Customer's use of the Workday
Adaptive Planning Service, Customer has requested that the Workday’s deployment of the Workday Adaptive
Planning Service includes a Functional Scope for the Project that supports the following standard Functional
Areas:

Functional Areas for Financial Planning Package In Scope
Organizational Structure & Chart of Accounts Yes
Revenue and Cost of Goods Planning Yes
Operating Expense Planning Yes
Workforce/Personnel Planning Yes
Allocations Yes
Capital Expense Planning Yes
Non-operating expenses Yes
Balance Sheet Planning No
Cash Flow Planning No
Financial Statement Report: Income Statement Yes
Financial Statement Report: Balance Sheet No
Financial Statement Report: Cash Flow No
Other Reporting Yes
OfficeConnect Reporting Yes
Data Visualization — Dashboards and Analytics Yes
Automated Data Import Yes
Automated Data Export No
©2020 Workday Page 18 of 23

SOW — Launch Deployment (Workday Adaptive Planning) v20.9

Wor k d Q y: Agreement # 232049 — Confidential

Reporting Scope. Reporting-related Professional Services in scope are as indicated below:

1. Income Statement. Deploy the required financial and summary statements within all entities noted
above (profit centers, divisions, business units, subsidiaries, legal entities and consolidated levels as
appropriate).

a)

1 Income Statement format that incorporate all templates and business logic;

2. Reporting and Analytics.

a)

b)

c)

HTML reports. Develop reports using the standard available functionality within the Workday
Adaptive Planning Service.
e Up to five Customer specific HTML reports.
OfficeConnect. Connect, using SmartLinks, up to five report sheets or pages to the Workday
Adaptive Planning Service. The reports need to be pre-formatted. The total number of rows across
all sheets/pages is up to 1,000 rows.
Dashboards & Analytics. Perform Professional Services designed to configure initial dashboard(s)
and dials and enable Customer to start using the Dashboards & Analytics solution (the
dials/analysis shall be based on dimensions, accounts and metrics set-up in the Workday Adaptive
Planning model). This includes:
e One dashboard inclusive of up to 5 dials or metrics
e Gather requirements which include use cases, user profiles, KPI definition and analysis needs;
e Conduct one workshop for eight-hour Project remote hands-on workshop (up to two hours) to
walk-through building dials/dashboards/perspectives using Customer Data from Customer's
Workday Adaptive Planning Instance;
e Support Customer configuring dashboards and dials that includes:
— Provide best practice guidance around design of dashboards and dials;
— Consult with Customer on specific dial design challenges;
— Help Customer with how-to questions.

6. Project Scope Assumptions

A. General Scope Assumptions
The following assumptions were made with respect to the functional scope of Customer’s Project:

e Create the required data structures in the Workday Adaptive Planning Service including the
organization hierarchy, chart of accounts and other required dimensions (e.g. products, Projects,
customers, etc.). The configuration shall include:

Budget one year out and forecast up to 3 years out;

Up to 20 legal entities;

One chart of accounts structure across the entities with a single fiscal year;
Up to twenty monthly currencies

Structure and chart of accounts are aligned between City and Schools

e Data Imports

©2020 Workday

Work with Customer to confirm mappings for one-time data import.
Perform a one-time import of initial data that includes:

e One Year of historical GL actuals;

e One Year prior year budget;

e Personnel data;

e Non-GL statistical data.

Perform unit testing of the configuration and data loads.

Update the training documentation to include the data load process.

Page 19 of 23
SOW — Launch Deployment (Workday Adaptive Planning) v20.9

Wor k d Q y: Agreement # 232049 — Confidential

e Performance Metrics. Deploy the following:

Up to 10 performance metrics based on data with the model.

e Process Management.
- Review process manager functionality.

1.

As each Workday Adaptive Planning Service component is configured, Workday shall demo the
component for Customer to review and approve. The deployment shall include:

Revenue Model. Workday shall consolidate and integrate the Revenue Model into the Income
Statement, the Balance Sheet and Cash Flow Statement.

a) 1 Revenue Model to support up to 2 revenue streams with up to 4 dimensions per stream.
Operating Expense Model. Deploy the Operating Expense Model adhering to the following:

a) Upto 50 expense accounts using formulas;
b) Up to 2 supporting schedules;
c) The Operating Expense Model does not include the Personnel Model.

Workforce/Personnel Model. Deploy the Workforce/Personnel Model to account for
workforce/personnel planning (¢€.g. headcount, salaries and wages, overtime, incentive
compensation, hire/termination, taxes, benefits, raises, assumptions/drivers, allocations, skills,
etc.) adhering to the following:

a) Upto 2 Workforce/Personnel models to support the following:
a. Upto 3 Employee Types
b. Transfers, Splits, Allocations by Level (Single-Step)
c. Fringe Benefits and Tax Rates
d. Bonuses

Capital Model. Deploy the Capital Model including all sheets, depreciation logic and
assumptions.

a) Capital Model to budget using one method of depreciation.
Allocation Model. Deploy the Allocation Model including all required allocation logic and
assumptions and shall validate the allocation(s) are operating correctly.

a) Up to 10 Cost Center/Entity (Single-Step allocations)

7. ERP JDBC Import Scope:

Integration configuration shall include the following:

Functional Scope. Customer has requested that Workday’s deployment of the Workday Adaptive Planning
Service include the below process areas after having determined a set of desired functionalities. Customer
shall purchase these products that support such process areas. Workday shall work with Customer on the
configuration of the following standard Workday Adaptive Planning Service functional areas:

Functional Area In Scope
Automated Data Import Yes
Automated Data Export No

Instances. The following Instance(s) are included in the scope of this Project:

©2020 Workday

Production

Page 20 of 23
SOW — Launch Deployment (Workday Adaptive Planning) v20.9

workday.

Workday Responsibilities.

Agreement # 232049 — Confidential

e Lead meetings and working sessions to design and build the integration.
e Assist Customer with completing the Business Requirements Document (BRD) and the Data

Mapping Document.

e “Adapter” refers to packaged integrations with certain specified vendors.
e Enable the following integrations (the “Integration Solution’):

# Source
System

Target
System

Integration
Point

Integration
Approach

Hours
Estimate

Notes

1 Lawson

Import GL
Account
Balance
(Actuals)

And

GL
Transactions
for up to five
transaction
types
(Transactions
types included
are related to
core GL data
only such as
Accounts
Payable,
Accounts
Receivable,
GL, and
Expense
Tracking data)

JDBC

2 Lawson

Import
employee
roster and
personnel
detail

JDBC

©2020 Workday

Install and configure the integration agent server on Customer-provided hardware compliant with

the requirements Workday provides to Customer — when required.

Configure the integration as defined in the BRD and the Data Mapping document using the
standard available functionality for each in-scope Integration adhering to the following guidelines:
Up to 10 business rules & transformations (e.g. concatenation of two fields) can be applied to
the data extracted from each source.
Rules for determining which accounts to exclude and account sign reversal from import are
account ranges or list of accounts;
For any system that does not store balances, data must be loaded by Delta (change in activity);
Data is imported into up to two sheets;
Data import into cube sheet(s) is not included
Currency conversion in the integration itself is not included
Three months of history shall be loaded into the Workday Adaptive Planning Service using
the Workday Adaptive Planning Service Integration from above source system(s) for
Integration setup validation purposes;
Document the Solution Configuration;
Support data validation for three months of history that is imported into the Workday Adaptive
Planning Service from Customer's source system(s).

Page 21 of 23
SOW — Launch Deployment (Workday Adaptive Planning) v20.9

Wor k d Q y: Agreement # 232049 — Confidential

e Conducta user walkthrough of the Workday Adaptive Planning Instance as built and demonstrate
how to run/schedule Integration jobs.
e Integration shall be built against the Production Instance of the source Customer system unless
otherwise noted.
e Specific inclusions and exclusions
- On-Premise JDBC — Specific integration details
= Only database views (a.k.a. queries or selects) are supported
= Customer is to prepare the views in the system for use by the Integration
= Up to three views total for GL Balances, Transactions, or Personnel
- Agent server is located within the network (e.g. not behind a separate firewall, or in the cloud,
no proxy server is required)

Customer Responsibilities.

e Complete the Integration Framework Fundamentals course in the Learning Management
System (LMS) prior to the Project Kickoff.

e Atechnical resource with understanding of the source system data model and extract technology
must be available during the Project to develop or enhance the source system extracts (i.e.,
review SQL queries or web service calls).

e Complete the Business Requirements Document (“BRD”) with assistance from Workday.

e Provide business rules for extraction and transformation of source data for the Workday Adaptive
Planning Service.

e Provide a subject matter expert with knowledge of the planning model to provide information on
data expected by the sheets and to assist in data validation.

e If applicable, coordinate with third party vendors or consultants. Workday is not required to
provide or have access to any third party application or system. Customer assumes sole
responsibility for access, management, payment and use of any third party systems, applications,
services or technology.

e If account names are different between Customer source system and the Workday Adaptive
Planning Service, the mapping of accounts must be provided in Microsoft Excel format.

e Hosted Integration (Hosted Service data source(s)).

- Ensure source system APIs are licensed and available to the Workday Adaptive Planning
Service (hosted data source(s)).
- Provide access to and credentials for database or API access to the source.

e Develop a test plan for User Acceptance Testing (UAT).

e Lead the testing and validation of each Integration - validate Customer Data within Customer's
Workday Adaptive Planning Instance loaded through the Integration. Workday Consultant
supports Customer during data validation phase validating three months of history.

Workday Deliverables.
e Updated BRD, to capture any change requests approved, as necessary.
e Acompleted integration solution that meets the requirements defined in the BRD.
e Solution Documentation;
e A Customer user walkthrough of the integration solution built and how to run/schedule integration

jobs (session shall be recorded in order to be available for future reference).
Completion Criteria.

e Customer has reviewed and signed off on the final Deliverables or begins using the Workday
Adaptive Planning Service in production.

©2020 Workday Page 22 of 23
SOW — Launch Deployment (Workday Adaptive Planning) v20.9

Wor k d Q y: Agreement # 232049 — Confidential

Integrations Scope Assumptions.

The Integration stage scope of work is based on the following assumptions:

Integration Project start is contingent on data structures (Chart of Accounts, Organizational Levels and
Dimensions) being stable in both the source system(s) and the Workday Adaptive Planning Service.
All supporting structures (including accounts and sheets) that hold the information to be imported
through the Workday Adaptive Planning Service Integration under this scope are fully built out and
verified by Customer through initial manual data load prior to the Integration Project kickoff.

Training shall be conducted in English.

Customer shall actively participate and provide the required resources to complete this Project
Workday shall configure the system using the currently available functionality within the Workday
Adaptive Planning Service. No customizations are included in the Project.

The Workday Adaptive Planning Service Integration extracts data from one (1) Instance of the source
application(s) and imports data into one Instance of the Workday Adaptive Planning Service.

Project Scope Exclusions.

This Project is solely focused on the deployment of the Workday Adaptive Planning Service.

Any feature or functionality not explicitly identified in the scope section of this Appendix 4 above, is considered
out of scope for this Project.

©2020 Workday Page 23 of 23

SOW — Launch Deployment (Workday Adaptive Planning) v20.9

THE CITY OF NASHUA “The Cate City

Administrative Services
Purchasing Department

October 28, 2020
Memo #21-041

TO: Mayor Donchess
Finance Committee

SUBJECT: Bulk Road Salt Funded From Budget Account 61514 Salt
Please see attached communications from Jon Ibara, Superintendent of the Street Department, dated

October 22, 2020 for project specific details related to this purchase. Below please find a summary of the
purchase approval request:

Item: Salt for Winter Snow & Ice Operation
Value: $455,000
Vendor: Eastern Minerals Inc & Granite State Minerals Inc

Department: 161 Streets
Source Fund: 61514 Salt

Ordinance: Pursuant to § 5-84 Special purchase procedures A. (3) Purchases which can be
procured through cooperative intergovernmental purchase agreements with
other governmental jurisdictions.

A competitive bid opportunity was not issued for this purchase as we are utilizing a contract with Granite
State Minerals Inc that has been negotiated by the State of New Hampshire and Eastern Minerals Inc has
agreed to offer the same pricing for dual source consideration.

The Superintendent of the Streets Department, The Board of Public Works (10/22/20 BPW Meeting) and the
Purchasing Department respectfully request your approval of this contract.

Regards,
Kelly Parkinson

Purchasing Manager

Ce: J Ibara
C O'Connor

229 Main Street * Nashua, New Hampshire 03061 ¢ Phone (603) 589-3330 « Fax (603) 589-3233

To:

From:

Re:

B. Motion:

Attachment:

Discussion:

City of Nashua, Public Works Division

Board of Public Works Meeting Date: October 22, 2020

Jonathan Ibarra, Superintendent
Street Department

Winter Road Salt

To approve the purchase of winter road salt from Granite State Minerals of
Portsmouth, NH and Eastern Minerals, Inc. of Chelsea, MA in the amount of
$455,000. Funding will be through Department: 161 Streets; Fund: General;
Account Classification: 61 Supplies and Materials.

State of NH Notice of Contract for Salt.
Quote from Eastern Minerals / Quote from Granite State Minerals

Granite State Minerals has been awarded the State of NH salt contract with a price
of $49.50 a ton delivered. Eastern Minerals has agreed to supply salt to the City
of Nashua at the State Bid price of $49.50 per ton, this is the same price per ton as
last year. Both Eastern Minerals and Granite State minerals have been contracted
with the City in the past years and have a good track record of on time salt
deliveries. For this reason the Superintendent recommends we continue to do
business with Granite State Minerals and Eastern Minerals.

PLANT:
99 Marginal Street
Chelsea, MA 02150
Phone: 617 ® 884-0027

OFFICE:

134 Middle Street, Suite 210
Lowell, MA 01852
Phone: 978 ® 458-6420
Fax: 978 8 251-8244

Fastern Minerals, Inc.

September 23, 2020

Jon Ibarra, Supt. Of Streets
City of Nashua

Division of Public Works
9 Riverside Street

Nashua, NH 03062

Dear Mr. Ibarra:
The following quote on Bulk Road Salt is offered for your consideration.

Delivery of Bulk Salt: minimum truckloads of 25 to 30 tons delivered to the City of Nashua,
NH at: $49.50 per ton.

To arrange for delivery call our salt terminal in Chelsea, Massachusetts:
1-800-331-0131 OR 1-617-884-0027

Payment terms are Net 30 days.

Prices quoted will remain firm until June 30, 2021, if accepted and acknowledged within 30
days. We would also ask you to provide an estimate of the tonnage you may order to help us
plan our inventory accordingly. Please sign and fax back to 978-251-8244 at your earliest
convenience.

Sincerely,
J Meres hulle
Thomas F. Sullivan @

Sales Representative

Estimated Tonnage:
Accepted by: Date:
Jon Ibarra
Supt of Streets