14001-CHANGE ORDER 6 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-CR006 Date Submitted: 6.21.2017
Project Name: Maricopa County Treasurer Information Module NameNersion: Dynamics AX
Systems — ULTIS project
Original Contract No.: 14001-RFP TRTA Gov Project Manager: Lisa Redding
Summary of Change:
MCTO prints checks for Citing Agencies, involuntary Pool Participators, School Districts and Miscellaneous
vendors. Microsoft coordinated with MCTO to create the design document (FDD 2047) defining the format of the
AP Check report and associated AP Payment advice report, and completed the development in an earlier code
build release. During testing, MCTO provided written bank requirement specifications and requested additional
changes and requirements to pass MCTO's servicing bank's testing. Microsoft has compared the functionality
requested to the existing design, and determined that the requested changes are outside the scope of the
originally-approved design. However, Microsoft has decided to include the new changes in-scope with no
additional cost.
Priority: i1 Urgent or LI Normal Required by: LI UAT p Go-Live 0 Final Acceptance
El Other: Process arid End-to-End testing
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: Customer or 111 TRTA Gov Requestor(s): Debbie Lukens, MCTO Program Manager
Fee (not including travel expenses): $ 0.00 D Estimate or El Fixed
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):
r" Professional Services El Application Software El Third-Party Software • Other:
This change request impacts (mark all that apply):
Product/Scope M Schedule • Other:
TRTA Gov TFS No.: D Eng. TFS and/or LI PS TFS (Aumentum only)
CR No. 14001-RFP-CR006 1 Confidential

PROJECT IMPLEMENTATION CHANGE REQUEST
Description Provided By:
Deborah Lukens, MCTO Program Manager 6/2/2017
Lisa Redding, TRTA Gov Program Manager 6/2/2017
Madhu Nekklapudi, Microsoft Project Manager 6/2/2017
William Cook, Microsoft Engagement Manager 6/2/2017
Name & Title Date
Description of Change Being Requested (describe here or attach document if needed):
MCTO prints checks for Citing Agencies, involuntary Pool Participators, School Districts and Miscellaneous
vendors. Microsoft coordinated with MCTO to create the design document (FDD 2047) defining the format of the
AP Check report and associated AP Payment advice report, and completed the development in an earlier code
build release. During testing, MCTO provided written bank requirement specifications and requested additional
changes and requirements to pass MCTO's servicing bank's testing. Microsoft has compared the functionality
requested to the existing design, and determined that the requested changes are outside the scope of the '
originally-approved design. However, Microsoft has decided to include the new changes in-scope with no
additional cost.
These additional requirements are:
• Treasurer's name is not printed. On the current stock it is printed three places.
• States "Maricopa County Treasurer's Office" not "Maricopa County Treasurer"
• Does not state "void after 365 days"
• Memo line above payee should be just above the MICR area
• Bank identifier printed too large, not complete (JPMorgan Chase Bank N.A.) and in wrong place. Should be
small and in the top middle of the check.
• Bank Fraction not listed (ACT Rh T 122100024) and (91-170/1221) these are banks requirements
• MICR line not in MICR field
• Bank address not required if that is an issue (may be prohibited, Waiting for bank response).
• Treasurer address is not required (change would require Treasurer Approval).
• "Main Service Account — Chase" should be noted with Treasurer information. It was used as bank reference
which is not correct. (see #'s 5 and 6 above).
• If the check number is "6" it should be more in the upper right corner
NOTE: As the functionality provided via this CR are separate from the existing contract deliverables, a separate
Deliverable Acceptance Statement (DAs) will be provided for this effort. The acceptance of existing Milestone 8, 9,
and 10 deliverables are not contingent on this effort.
Recommended Solution:
• Incorporation of the requirements listed above into the Microsoft Dynamics design and deployment.
Assumptions:
• MCTO will provide resources and write all test cases to test the new functionality.
Acceptance Criteria (describe expected acceptance criteria for changed deliverables upon completion):
• TRTA Gov (Microsoft) has provided an updated FDD 2047 to document design information for the listed changes
in this CR document
• MCTO has reviewed and approved the updated FDD 2047 for the listed changes in this CR document
• TRTA Gov (Microsoft) has updated the Technical Design Document(s) (TDDs) for the changes listed in this
document.
• TRTA Gov (Microsoft) has delivered an initial build inclusive of the listed changes. 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.
CR No. 14001-RFP-CR006 2 Confidential

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
• NOTE: This acceptance will be separate from acceptance of existing Milestones 8, 9, and 10 deliverables, which
are not contingent on this effort.
Risk Assessment! Technical and Project Impact:
General Notes:
• Change as described above.
Project Impacts:
• Additional Dynamics AX scope and costs as described. No changes expected to Aumentum as a result of this
new functionality.
Development:
• The listed changes in this CR will be developed, tested, and released upon the approval of the CR. Functionality
will be planned into a future Dynamics AX code build with dates to be confirmed with MCTO once the associated
Functional Design Document (FDD) is approved.
Configuration:
• N/A
Testing:
• MCTO will develop requirement gap test scripts
• MCTO will provide expertise to test the functionality per the agreed schedule
• MCTO will coordinate with Bank to get the check format approvals
Documentation:
• Functional design documents (FDD) 2047 will be updated, reviewed and approved with MCTO SMEs.
• Technical Design Documents (TDDs) will be updated and provided, but there will be no formal review or approval
of these documents
Training:
• N/A
TRTA Gov Required Resources:
• Madhu Nekkalapudi (Dynamics AX Project Manager)
• Dean Wierman (Dynamics AX Solution Architect/Technical Consultant)
• Microsoft Dynamics Design/Development Team
• Lisa Redding (TRTA Gov Program Manager)
Customer Responsibilities:
• Any change in requirements 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 after the build is released.
• MCTO will be responsible for further testing of the new functionality in a timely manner so as to not impact the
agreed project schedule
CR No. 14001-RFP-CR006 3 Confidential

TRTA Gov Program Manager 6/29/17
6.29.2017

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
DELIVERABLE ACCEPTANCE STATEMENT ("DAS")
FOR CHANGE REQUEST NO. 14001-RFP-CR006
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.
Summary of Change Request:
During requirement testing, MCTO provided more detailed requirements for the check print functionality that enabled
Microsoft to review the featured solution along with the requested requirements. Microsoft has compared the functionality
requested to the existing Statement of Work and determined that the requested functionality is outside the scope of the
existing contract. However, after careful consideration of the request, Microsoft accepted the requirements and decided
to add to scope without cost even though they are not part of the original scope.
Acceptance Criteria:
• TRTA Gov (Microsoft) has provided an updated FDD 2047 to document design information for the listed changes
in this CR document
• MCTO has reviewed and approved in TFS the updated FDD 2047 for the listed changes in this CR document
• TRTA Gov (Microsoft) has delivered an initial build inclusive of the listed changes. 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.
• NOTE: This acceptance will be separate from acceptance of existing Milestone 8, 9, and 10 deliverables, which
are not contingent on this effort.
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 deliverables 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 $0.00 upon signing this acceptance. It is agreed that this functionality delivery is complete.
Jurisdiction: Maricopa County Thomson Reuters:
Signature: Signature:
Printed Name: Printed Name:
Title: Title:
Date: Date:
Signature:
Printed Name:
Title:
Date:
CR No. 14001-RFP-CR006 5 Confidential