14001-CHANGE ORDER 8 12-13-17.PDF

-; THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
MANATRON, INC. — A THOMSON REUTERS BUSINESS
("Thomson Reuters Tax & Accounting, Government" or "TRTA Gov")
Customer Name: Maricopa County Treasurer's Office
Change Request No.: 14001 -RFP-CR008 Date Submitted: 9/07/2017 (updated 8131/17 per request of MOTO)
Project Name: Maricopa County Treasurer Information Module NameNersion: Dynamics AX
Systems - ULTIS project
Original Contract No.: 14001-RFP TRTA Gov Program Manager: Lisa Redding
Summary of Change:
Incorporation of AP Pay Refunds into the In-Scope functionality of the original contract. MCTO has decided to go-live
on Dynamics with the legacy property tax system, which doesn't have well-structured Vendor address information.
Additionally, MCTO has chosen not to cleanse the Vendor data prior to go-live with Dynamics AX. This gap will allow
MCTO to pass unstructured vendor data to AX, which will be printed on checks as provided.
Priority: El Urgent or III Normal Required by: • UAT Liii Go-Live El Final Acceptance
Other: County's desired date
Window of delivery date and business process calendar/phase justification:
Functionality will be planned into an upcoming Dynamics AX code build with dates to be confirmed with MCTO once
Functional Design Documents (FDDs) are approved.
Requested by: 0 Customer or U TRTA Gov Requestor(s): Maricopa County Treasurer's Office
Fixed Fee (not including travel expenses): $74,100
Note: This pricing is conditional on the acceptance of CR004 and CR008 as a package. If CR004 is not
approved or CR008 is approved at a later time, the fixed fee for CR008 will be $390,000.
Any travel expenses associated with this change request will be billed as incurred and approved with a minimum 15-day
advance notice.
Request Type (mark all that apply):
Professional Services 12 Application Software Third-Party Software Other:
This change request impacts (mark all that apply):
I Product/Scope U Schedule Other:
TRTA Gov TFS No.: Refer to section below U Eng. TFS and/or LI PS IFS (Aumentum only)
CR No. 14001-RFP-CROO8 1 Confidential

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
Description Provided By:
Lisa Redding, TRTA Gov Program Manager 8/10/2017
Madhu Nekkalapudi, Microsoft Project Manager 8/10/2017
William Cook, Microsoft Engagement Manager 8/10/2017
Name & Title Date
Description of Change Being Requested (describe here or attach document if needed)
Incorporation of AP Pay Refunds into the In-Scope functionality of the original contract. MCTO has decided to go-live on
Dynamics with the legacy property tax system, which doesn't have well-structured Vendor address information.
Additionally, MCTO has chosen not to cleanse the Vendor data prior to go-live with Dynamics AX. This gap will allow
MCTO to pass unstructured vendor data to AX, which will be printed on checks as provided.
AP Pay Refunds
Conclusion: TRTA Gov and MCTO mutually acknowledge that AP Pay Refunds is out of scope of the contract.
The following TFS items were identified by MCTO as required for AP Pay Refunds.
ID Title
5533 The Vendor Import interface must support MCTO's name/address formatting.
5534 The Vendor Import interface must support commas embedded in the name/address content
5535 The system roust support accepting up to 5 name/address lines ready to print on the check
5536 The system must support accepting an address when a City, State and Zip line may or may not be present
5538 The system must support compressing address lines to remove blank lines to prevent blank lines on printed
checks.
5539 The Vendor invoice import interface must support multiple (formatted) invoice lines with amount, Parcel and
CP number.
5626 The changes to support legacy import must not change the existing interface from Aumentum
5627 During check printing, each vendor invoice line with amount, Parcel and CP number must be displayed on the
check stub.
I 5628 The system MAY airtomatic.ally import payment invoines and post to GL with no manual intervention
Recommended Solution:
• Incorporation of the requirements listed above into the Microsoft Dynamics design and deployment.
Assumptions:
• Fixed-fee billing amounts shown in all sections of this CR and associated DAS is conditional on the acceptance of
CR004 and CR008 as a package. If CR004 is not approved or CR008 is approved at a later time, the fixed fee for
CR008 will change.
• Requirement for Check Stub Variable Lines (in relation to CR006 — Check Print Changes) is expected to be
resolved with TFS 5539 based on information known as of 8/30/17. No additional changes are expected for
CR006.
• The PMs will work with the project teams to encourage any new request to be resolved through a workaround
instead of adding new requirements to the project implementation.
CR No. 14001-RFP-CR008 2 Confidential

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
• Without authorization to proceed in writing by way of signing this CR, design and development will not begin.
Delayed acceptance of the CR will risk the E2E and UAT testing windows.
• There is no guarantee of meeting the county's desired go-live date of February 2018 as we previously stated
delaying the decision beyond July 2017 may impact that date; however, all team members will continue working
towards the Feb 2018 go-live plan. The PMs will continually monitor progress and work with the project teams to
encourage quick decision making and timely issue resolution to mitigate the risk of delays to the go-live plan.
• MCTO will provide resources and write all test cases to test the new functionality.
• Resource support of the extended go-live date and all associated costs will be presented in a separate CR and is
not included here.
Acceptance Criteria (describe expected acceptance criteria for changed deliverables upon completion):
• TRTA Gov (Microsoft) has provided new or updated FDDs to document design information for the listed TFS
Requirement IDs in this CR document
• MC70 has reviewed and approved FDDs for the listed TFS Requirement IDs in this CR document
o Approval of Functional Design Document(s) by MCTO SMEs will occur in TFS and will be considered
final. No further reviews, updates and approvals on the individual documents will be sought by MCTO.
• TRTA Gov (Microsoft) has provided preliminary Technical Design Documents (nibs) to MCTO for TFS
Requirement IDs listed in this document. No MCTO review or approval is required for the TDDs.
• TRTA Gov (Microsoft) has delivered a build inclusive of TFS Requirements for the purposes of configuration, set
up and testing. P1 and/or P2 defects found in the implementation as a result of subsequent testing will be
resolved as per the standard defect resolution process within the original contract, separately from this DAS.
Risk Assessment I Technical and Project Impact:
General Notes:
• Change as described above.
Project Impacts:
• Additional Dynamics AX scope and costs as described. Any change to Aumentum as a result of this new
functionality is not included in this CR.
• Design and Development efforts will proceed upon written authorization of this CR. Delays to finalizing this CR
will risk the current E2E and UAT Testing windows and will impact the go-live date.
• No customizations related to functionality identified in this CR will be delivered until the DAS 1 (design approval)
for this CR is signed.
Development:
• These requirements will be developed, tested and released upon the written approval of the CR. Functionality will
be planned into an Dynamics AX code build with dates to be confirmed with TRTA Gov and MCTO once
Functional Design Documents (FDDs) are approved.
• P1 and P2 defects during the implementation testing period will be triaged and any associated code changes will
be provided in future code builds. Schedule to be agreed with the PM project team.
Configuration:
• N/A
Testing:
• MCTO will develop requirement gap test scripts
• MCTO will provide expertise to test the functionality per the agreed schedule
Documentation:
• Functional design documents (FDDs) be updated, reviewed and approved with MCTO SMEs who are authorized
to sign off on such design documentation.
• MCTO SME's will review and approve the design documents within three (3) business days after the design is
updated basing on the feedback received in the design review session and submitted for approval
• Approval of Functional Design Document(s) by MCTO SMEs in TFS will be considered final and no further
reviews, updates and approvals will be sought by MCTO.
CR No. 14001-RFP-CR008 3 Confidential

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
• A DAS will be submitted upon document approval in IFS and serves as authorization to bill for this CR phase.
• Technical Design Documents (TDDs) will be provided for reference only, as there will be no formal review or
approval expected of these documents.
• Entity Relationship Diagrams (ERDs) will not be updated or provided for customizations identified in this CR.
Training:
• N/A
TRTA Gov Required Resources:
• Dynamics AX Project Manager
• Dynamics AX Solution Architect/Technical Consultant
• Microsoft Dynamics Design/Development Team
• TRTA Gov Project and/or Program Manager
Customer Responsibilities:
• Any change in requirements will go through the formal change request process defined for this project
• MCTO will be responsible for reviewing and providing timely approval of the Functional Design Document(s) so as
to not impact the start of the development cycle and agreed project schedule. Any such delays will go through the
formal change request process defined for this project.
• MCTO will complete at least one round of requirements testing for the functionality associated with this CR within
two weeks of the build being released.
• MCTO will be responsible for testing the new functionality in a timely manner so as to not impact the agreed
project schedule
CR No. 14001-RFP-CR008 4 Confidential

TRTA Gov Program Manager 9-7-2017
Managing Director, Government 9-8-2017

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
DELIVERABLE ACCEPTANCE STATEMENT ("DAS") #1
FOR CHANGE REQUEST NO. 14001-RFP-CR008
Purpose:
The purpose of this acceptance form is for the Customer to sign off on the design of the services described in this change
request and agree that TRTA Gov should proceed to the next phase of the project and accept billing for this phase.
Summary of Change Request:
Incorporation AP Pay Refunds into the In-Scope functionality of the original contract. MCTO has decided to go-live on
Dynamics with the legacy property tax system, which doesn't have well-structured Vendor address information.
Additionally, MCTO has chosen not to cleanse the Vendor data prior to go-live with Dynamics AX. This gap will allow
MCTO to pass unstructured vendor data to AX, which will be printed on checks as provided.
Acceptance Criteria:
• TRTA Gov (Microsoft) has provided new or updated FDDs to document design information for the listed IFS
Requirement IDs in this CR document
• MCTO has reviewed and approved FDDs for the listed TFS Requirement IDs in this CR document
o Approval of Functional Design Document(s) by MCTO SMEs will occur in TFS and will be considered
final. No further reviews, updates and approvals on the individual documents will be sought by MCTO.
These items were completed on
Client response period is ten (10) business days. After that time, this deliverable will be considered accepted and ready
for billing unless otherwise documented in a formal response to TRTA Gov with detailed rationale for rejecting this
milestone. Rejection of a milestone will result in immediate escalation and halt the project for further review. See
Appendix 2-A: Deliverable Acceptance Process for guidelines related to deliverable acceptance.
We, the undersigned, agree that these items are complete and that under the conditions of this change request, the
County will be billed $24,453.00 (33% of the total fee) upon signing this acceptance.
El Accepted El Rejected
Jurisdiction: Maricopa County Thomson Reuters:
Signature: Signature:
Printed Name: Printed Name:
Title: Title:
Date: Date:
Signature:
Printed Name:
Title:
Date:
CR No. 14001-RFP-CR008 6 Confidential

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
DELIVERABLE ACCEPTANCE STATEMENT ("DAS") #2
FOR CHANGE REQUEST NO. 14001-RFP-CR008
Purpose:
The purpose of this acceptance form is for the Customer to sign off on the completion of the services described in this
change request and accept billing for this phase.
Summary of Change Request:
Incorporation AP Pay Refunds into the In-Scope functionality of the original contract. MCTO has decided to go-live on
Dynamics with the legacy property tax system, which doesn't have well-structured Vendor address information.
Additionally, MCTO has chosen not to cleanse the Vendor data prior to go-live with Dynamics AX. This gap will allow
MCTO to pass unstructured vendor data to AX, which will be printed on checks as provided.
Acceptance Criteria:
TRTA Gov (Microsoft) has provided preliminary Technical Design Documents (TDDs) to MCTO for TFS
Requirement IDs listed in this document. No MCTO review or approval is required for the TDDs.
TRTA Gov (Microsoft) has delivered a build inclusive of TFS Requirements for the purposes of configuration, set
up and testing. P1 and/or P2 defects found in the implementation as a result of subsequent testing will be
resolved as per the standard defect resolution process within the original contract, separately from this DAS.
These items were completed on
Client response period is ten (10) business days. After that time, this deliverable will be considered accepted and ready
for billing unless otherwise documented in a formal response to TRTA Gov with detailed rationale for rejecting this
milestone. Rejection of a milestone will result in immediate escalation and halt the project for further review. See
Appendix 2-A: Deliverable Acceptance Process for guidelines related to deliverable acceptance.
We, the undersigned, agree that these items are complete and that under the conditions of this change request, the
County will be billed $25,194.00 (34% of the total fee) upon signing this acceptance. It is agreed that this functionality
delivery is complete.
0 Accepted El Rejected
Jurisdiction: Maricopa County Thomson Reuters:
Signature: Signature:
Printed Name: Printed Name:
! Title: Title:
Date: Date:
Signature:
Printed Name:
Title:
! Date:
CR No. 14001-RFP-CR008 7 Confidential