Board Of Aldermen - Agenda - 12/28/2021 - P68
wor k d Q y- Agreement #298892 — Confidential
STATEMENT OF WORK
Appendix 3
[Reserved]
©2021 Workday, Inc. SOW - Your Way Deployment (Workday Adaptive Planning) v21.8 Page 8 of 13
wor k d Q y- Agreement #298892 — Confidential
STATEMENT OF WORK
Appendix 3
[Reserved]
©2021 Workday, Inc. SOW - Your Way Deployment (Workday Adaptive Planning) v21.8 Page 8 of 13
wor k d ay. Agreement #298892 — Confidential
STATEMENT OF WORK
Appendix 4
Workday Adaptive Planning Ad Hoc Services
“Service” as used in this Appendix 4 means the Workday Adaptive Planning Service.
This SOW details the Professional Services associated with the Service that Workday shall perform for Customer.
lf Customer wishes to secure additional Professional Services not included in the scope of this SOW, Workday shall
provide a separate proposal for such Professional Services. Customer acknowledges and agrees that the
avoidance of project delays caused by Customer is material to Workday's ability to provide the Professional
Services. Professional Services provided under this SOW shall be based on the Workday consulting rates listed in
Appendix 2 (Financial Terms).
Summary of Project Add new departments to existing models, add new data set to existing integration
Date Requested ASAP
Date Needed ASAP
Workday Professional Services Description and Assumptions
Project Scope.
Workday shall provide the following Professional Services associated with the deployment of the Service for
Customer:
Tasks in Scope.
* Update Income Statement with new levels to support manual entry for city, police and fire departments.
e Update Headcount Sheet with new levels to support manual entry for city, police and fire departments.
e Update Revenue Sheet with new levels to support manual entry for city, police and fire departments.
e Update loaders for current Lawson integration to the updated sheets.
Integrations Scope.
Integration configuration shall include the following:
Functional Scope. Customer has requested that the deployment of the 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 Service functional areas:
Functional Area ie In Scope
Automated Data Import Yes
Automated Data Export No
Instances. The following Instance(s) are included in the scope of this Project:
e Production
e Post-Production support of third party or Customer-provided integrations is out of scope for this
SOW.
2021 Workday, Inc. SOW — Your Way Deployment (Workday Adaptive Planning) v21.8 Page 9 of 13
wor k d Q y- Agreement #298892 — Confidential
STATEMENT OF WORK
Workday Responsibilities.
Lead meetings and working sessions to design and build the integration.
e
e Assist Customer with completing the Integration Design Document (IDD).
e “Adapter” refers to packaged integrations with certain specified vendors.
« Enable the following integrations (the “Integration Solution’):
# Source | Target ; Integration Notes
System System Laterepelised tell Approach
Lawson Adaptive | Import GL Encumbrance Account JDBC Build new data set for
9 Balance (Actuals) existing Lawson
integration to import
encumbrance actuals
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 IDD using the standard available functionality for each
in-scope Integration adhering to the following guidelines:
Up toe 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 (e.g., change in
activity)
Data is imported into up to one standard sheets;
Data import into cube sheet(s) is not included
Currency conversion in the integration itself is not included
Three months of history, as identified by Customer, shall be toaded into the Service using the
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 Service from
Customer's source system(s)
Conduct a user walkthrough of the Workday Adaptive Planning Instance as built and demonstrate
how to run/schedule Integration jobs
Workday shall build the Integration against the Production Instance of the source Customer
system unless otherwise noted.
Specific inclusions and exclusions for the specific Professional Services package purchased:
Existing Lawson JDBC — Import Encumbrance Actuals
= 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
® Agent server is iocated within the network (e.g., not behind a separate firewall, or in the
cloud, no proxy server is required)
Customer Responsibilities.
©2021 Workday, Inc.
A technical 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).
Complete the Integration Design Document (“IDD”) with assistance from Workday.
Provide business rules for extraction and transformation of source data for the Service.
SOW - Your Way Deployment (Workday Adaptive Planning) v21.8 Page 10 of 13
wor k d ay. Agreement #298892 —- Confidential
STATEMENT OF WORK
Provide a subject matter expert with knowledge of the planning mode to provide information on
data expected by the sheets and to assist in data validation.
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.
lf account names are different between Customer source system and the Service, the mapping
of accounts must be provided in Microsoft Excel format.
On Premise Integration (On Premise data source(s)):
Provide Server/Virtual Machine/other for Integration configuration, testing and production.
Ensure that server complies with the data agent requirements defined in the document
provided.
Provide remote access to Integration during the Project.
Hosted Integration (Hosted Service data source(s)):
Ensure source system APIs are licensed and available to the Service (hosted data source(s)).
Provide access to and credentials for database or API access to the source.
Develop a test plan for User Acceptance Testing (UAT).
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.
Provide post-Production support for the integrations identified above.
Workday Deliverables.
Updated Integration Design Document (“IDD"), to capture any change requests approved, as
necessary.
A completed Integration Solution that meets the requirements defined in the IDD.
Solution Documentation;
Completion Criteria.
Customer has reviewed and signed off on the final Deliverables or begins using the Service in
Production.
integrations Scope Assumptions.
The Integration stage scope of work is based on the following assumptions.
* integration Stage start is contingent on data structures (Chart of Accounts, Organizational Levels and
Dimensions) being stable in both the source system(s) and the Service.
e All supporting structures (including accounts and sheets) that hold the information to be imported
through the Service Integration under this scope are fully built out and verified by Customer through
initial manual data load prior to the Integration Project kickoff.
Workday shall conduct all training in English.
e« Customer shall actively participate and provide the required resources to complete this Project
e Workday shall configure the system using the currently available functionality within the Service. No
customizations are included in the Project.
e The Service Integration extracts data from one (1) Instance of the source application(s) and imports
data into one Instance of the Service.
©2021 Workday, Inc
SOW - Your Way Deployment (Workday Adaptive Planning) v21.8 Page 11 of 13
wor k d ay. Agreement #298892 — Confidential
STATEMENT OF WORK
Project Timeline.
The estimated duration and estimated completion dates of each Project stage are listed below, pending timely
execution of this SOW and availability of resources and training:
Project Timeline*
Estimated Project Start TBD
Estimated Duration 5 to 7 weeks
Post Production Support 2 weeks
Any additional Professional Services that are required or requested as a result of an extension of the timeline shall
be subject to a Change Order and the Change Order Process described in this SOW.
General Project Assumptions.
« Customer and Workday should use a File Transfer Server to share Professional Services Data for the
Project.
e Customer shall assign an experienced Project Manager to manage Customer's roles and activities for this
Project.
« Customer shall in good faith take actions necessary to meet all dates set forth in the Project Plan.
e® Customer is responsible for the timely coordination of internal resources necessary to conduct all required
activities in the Project Plan.
e To the extent applicable, Customer is responsible for the development of the Test Strategy and user test
scenarios. Workday shall provide standard test scenarios to be used as a foundation; however, Customer
shall need to create detailed test scenarios and cases based on its user requirements and system
configuration.
e Customer is responsible for completing hands-on testing activities and validations.
e Customer shall lead the coordination with any external vendors and consultants to ensure timely response
in working with Workday Consultants.
Project Changes.
The parties acknowledge and agree that the avoidance of Project delays is material to Customer's Project success
and Workday’s ability to provide the Professional services. In the event of any Project delay due to the fault of
Customer, Workday, or causes not in the control of either party, the parties shall attempt to mitigate the effects of
such delay. The parties shall meet to resolve such delays and to develop a mutually agreed solution. Both parties
shall take into consideration the cause of the delay and negotiate in good faith. In the event there are Project
impacts including but not limited to changes in Project scope, estimated level of effort, Project timeline, Project
resource commitments or expenses, the parties shall execute a mutually agreed Change Order pursuant to the
Change Order Process.
Change Order Process.
During the Project in this SOW, new information may surface that necessitates a change in business requirements
resulting in a change in Project scope and, therefore, changes in the estimated level of effort, Project timeline, or
Service features. Upon either party's request, Workday shall describe such requested changes, and the associated
fees for additional Professional Services to be provided, in a proposed Change Order. Due to the complexity of
some Change Orders, upon prior and mutual agreement, Workday shall invoice Customer for the time required to
©2021 Workday, Inc. SOW — Your Way Deployment (Workday Adaptive Planning) v21.8 Page 12 of 13
wor k d a y. Agreement #298892 — Confidential
STATEMENT OF WORK
scope and estimate Customer-requested changes. Workday shall advise Customer of the cost estimate if such a
charge shall apply. Each proposed Change Order shalt contain the requested change, the impact on the current
engagement under this SOW, and the estimated resources and time to complete the Professional Services for the
work described in the Change Order. Workday shall submit the Change Order to Customer for review and approval,
then shall circulate the mutually agreed Change Order for signature. Proposed Change Orders shall remain valid
for a period of ten (10) business days from the date of submission. If Custorner does not approve the Change Order
in writing within the ten (10) business days, and Workday has not extended the period of validity in writing, the
Change Order shall automatically expire. Upon the parties’ execution of a Change Order, Workday shall begin
performing the Professional Services described in the Change Order,
©2021 Workday, Inc. SOW - Your Way Deployment (Workday Adaptive Planning) v21.8 Page 13 of 13
Office of the City Clerk
City of Nashua
229 Main Street Susan Lovering
Nashua, NH 03061-2019 City Clerk
(603) 589-3010, Option #5 Ailison Waite
CityClerkDept@NashuanH.Gov Deputy City Clerk
December 17, 2021
Lori Wilshire, President
Board of Aldermen
229 Main Street
Nashua, NH 03060
Dear President Wilshire:
In accordance with NRO 5 — 6, Compensation, I am hereby notifying the Board of Aldermen that
Alderman-at-Large Shoshanna Kelly missed three regular meetings of the Board of Aldermen for the
quarter ending December 31, 2021.
The dates of absences are as follows:
October 12, 2021
October 26, 2021
November 23, 2021
The relevant section of NRO 5 — 6 is as follows:
B. If, in any quarter, any member of the Board of Aldermen is recorded absent at three or more regular meetings of the
Board, the City Clerk shall transmit a communication stating that fact to the Board of Aldermen, and the stipend for that
quarter shall be withheld. In accepting the communication, the Board may also determine by vote that for good cause
shown that member shall receive a full or partial stipend for the quarter. Good cause shall include but not be limited to
attendance ait committee and other meetings; health; maternity, paternity or adoption leave; or other extenuating
circumstances for the absence. Additionally, the Board may find that the attendance of any member within a quarter has
been unacceptable and by a majority vote withhold any or all of the stipend for that quarter.
City Clerk
O-21-081
AMENDED
ORDINANCE
RELATIVE TO THE REVISION OF WARD BOUNDARIES
CITY OF NASHUA
In the Year Two Thousand and Twenty One
The City of Nashua ordains that Part I “Administrative Legislation”, Chapter 23
“Elections and Campaigns”, Article I “General Voting Procedures”, Section 23-7.1 “City wards”
of the Nashua Revised Ordinances, as amended, be hereby further amended as required under
paragraph I of § 3 of the City Charter by deleting the struck-through language and adding the
new underlined language as follows:
“§ 23-7.1. City wards.
The City of Nashua is hereby divided into the following nine wards:
A.
Ward 1: Beginning at the intersection of the F.E. Everett Turnpike and Amherst
Street and running in a eS direction along the center line of Amherst
ee i ina OER, eee eee the Merrimack town line;
thence, turning and running along the Nashua/Merrimack, thence Nashua/Hollis
lines in a southerly direction to the intersection of the Nashua River; thence
turning and running in a northeasterly direction along the center line of the
Nashua River to the intersection of the F.E. Everett Turnpike; thence, turning and
running in a northerly direction along the center line of F.E. Everett Turnpike to
the point of beginning.
Ward 2: Beginning at the intersection of Cushine-Avenue Baldwin Street and
Amherst Street and running in a southerly direction along the center line of
Baldwin Street to the intersection of Prescott Street the Broad Street Parkway;
thence, turning and running in a aerthwesterly westerly direction along the center
line of the Breoad-Street Parkway Prescott Street to the intersection of Broad Street
Bennett Street: thence turning in an easterly northerly direction and running along
the center line of Bennett Street to the intersction of Amherst Street, thence
turning westerly on Amherst Street and running along the centerline to the
intersection of Broad Street; thence running along the centerline of Broad Street
ORDINANCE O-21-081
to the intersection of Sullivan Street; thence turning in a northerly direction and
running along the center line of Sullivan Street to the intersection of Rodman
Street and turning westerly and running along the centerline of Rodman Street to
the intersection of Berkshire Road; thence turning northerly and running along the
centerline of Berkshire Road to the intersection of Pine Hill Road; thence turning
northwesterly and running along the centerline of Pine Hill Road to Essex Street;
thence turning northeasterly and running along the centerline of Essex Street to
Amherst Street; thence tuming and running northwesterly along the center line of
Ausilis Street Me ounadaetes ee eee the Spe A ERE SE RNa Re
pH esterhy-dire : the tracks to the Mernrnee town line;
ieee rath enonhctly and following the Nast City boundary generally in a
northerly then easterly direction to the railroad tracks east of Route 3 which run
parallel to the Merrimack River; thence turning and running southerly along the
railroad tracks to the intersection of Pennichuck Street; thence turning in a
westerly direction and ninning along the center line of Pennichuck Street to the
intersection of Concord Street; thence turning in a southerly direction and running
along the center line of Concord Street to the intersection of the Henri Bourque
Highway; thence turning in a westerly direction and running along the center line
of the Henri i Bourque eee to the intersection of Manchester Street; the-center
Vier: thee aati oe santana ina aa ne direction ict the
center line of Manchester Street to the intersection of Cushing Avenue; thence,
turning in a southwesterly direction and running along the center line of Cushing
Avenue to the intersection of Amherst Street; thence turning in a southeasterly
direction along the center line of Amherst Street to Baldwin Street, the point of
beginning.
Cc. Ward 3: Bound-by-atin
FE, Bverett-Parnpike aad the Nashue City’Merrimack tows line: thence running
ORDINANCE 0-21-081
} Deerhaven Divete the center line-ot
Manchester Street: Beginning at the intersection of the railroad tracks east of
Route 3, which run parallel to the Merrimack River, and Pennichuck Street;
thence turning in a westerly direction and running along the center line of
Pennichuck Street to the intersection of Concord Street; thence turning in a
southerly direction and running along the center line of Concord Street to the
intersection of the Henri Bourque Highway; thence turning in a westerly direction
and running along the center line of the Henri Bourque Highway to the
intersection of Manchester Street: thence, turning and running in a southerly
direction along the center line of Manchester Street to the intersection of Cushing
Avenue; thence turning in a southwesterly direction and running along the center
line of Cushing Avenue to the center line of Amherst Street; thence, turning and
running in a southerly direction along the center line of Amherst Street to the
intersection of Baldwin Street; thence turning southwesterly and running along
the center line of Baldwin Street to Fairmount Street; thence, turning and running
in an easterly a-southerly, then southwesterly, direction along the center line of
Fairmount Street te-the intersection of the railroad tracks: thence-tuminge and
running lene the sailread tracks in-an-easterly direction tothe intersection ofthe
powerlines at Terrace Street thence tuming and running along the powertines in
a-westerly direction to the intersection of the Broad-Street Parkway Veterans
Memorial Parkway; thence, turning in a southerly direction and running along the
center line of the Broad-StreetParlevay Veterans Memorial Parkway to the center
line of the Nashua River; thence, turning and running in an easterly direction
along the center line of the Nashua River to its intersection with Canal and Bridge
Streets; thence, turning westerly and running along the center line of Bridge Street
to the center line of the Merrimack River; thence, turning northerly along the
center line of the Merrimack River to the intersection of the Nashua
City/Merrimack town line. westerly-aleng-the Nashua-City/ Merrimack town tine
ape ueseias!
D. Ward 4: Beginning at the intersection of Amherst Street and the F.E. Everett
Turnpike and running in a southerly direction along the center line of said F-E.
Everett Turnpike to the intersection of West Hollis Street; thence, turning and
running in an easterly direction along the center line of West Hollis Street to the
intersection of Badger Street; thence, turning and running in a southerly direction
along the center line of Badger Street to the intersection of Kinsley Street; thence,
turning and running in an easterly direction along the center line of Kinsley Street
to the intersection of Ask Street-thence, turning and running in-a southerly
direction along the center tine of Ash Street to the intersection of Nevada Street;
thence, turning and running in-an-easterly direction along the center tine-of
Nevade Streetiothe intersection-of Vine Street; thence, turning and running in a
southerly direction along the center line of Vine Street to the intersection of Lake
Street; thence, turning and running in an easterly direction along the center line of
Lake Street to the intersection of Main Street; thence, turning and running
northerly along the center line of Main Street to the intersection of-East Hollis
Street;Bewers-—Street; thence, turning and running in-ae easterly direction along
the center ine of Bowers Street to the intersection of Harbor Avenue; thence,
turning and running northerly alone the centertine of Harbor Ayenue-to-the