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

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
MANATRON, INC. — A THOMSON REUTERS BUSINESS
("Thomson Reuters Tax & Accounting, Government" or "TRTA Goy")
Customer Name: Maricopa County Treasurer's Office
Change Request No.: 14001 -RFP -CR003 Date Submitted: 4/13/2017
Project Name: Maricopa County Treasurer Information Module Name/Version: Dynamics AX
Systems — ULTIS project
Original Contract No.: 14001 -REP TRTA Gov Project Manager: Lisa Redding
Summary of Change:
During design reviews, MCTO provided more detailed requirements 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.
Priority: ' Urgent or n Normal Required by: LI UAT • Go-Live D Final Acceptance
E1 Other: Process and 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 wjth dates to be confirmed with MCTO once
Functional Design Documents (FDDs) are approved.
Requested by: El Customer or LI TRTA Gov Requestor(s): Maricopa County Treasurer's Office
Fee (not including travel expenses): $ 0.00 • Estimate or A 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):
El Professional Services El Application Software • Third-Party Software • Other:
This change request impacts (mark all that apply):
El Product/Scope • Schedule LII Other:
TRTA Gov TFS No.: 1323, 1300, 1294, 1317, 1566, 11 Eng. TFS and/or ILI PS TFS (Aumenturn only)
1320
CR No. 14001-RFP-CR003 1 Confidential

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
Description Provided By:
Deborah Lukens, MCTO Program Manager 3/15/2017
Lisa Redding, TRTA Gov Program Manager 3/15/2017
Madhu Nekklapudi, Microsoft Project Manager 3/15/2017
William Cook, Microsoft Engagement Manager 3/15/2017
Name & Title Date
Description of Change Being Requested (describe here or attach document if needed):
1) Requirement TES ID 1323: The system must enforce paying the registered warrants for each agency in order of
registration (i.e., order of presentation).
Description: The system shall adopt the standardized UAMACT procedure by providing capability in accordance
with A.R.S. §11-605 and 11-635 to support if a revolving line of credit has not been obtained or the line of credit
has been expended, warrants drawn on funds with insufficient monies shall be registered and paid in the order of
registration. Interest accrues on unpaid warrants from the date of presentation until they are paid at a rate not to
exceed a configurable rate. e.g., 10 percent. The interest rate shall be configurable with an audit trail. e.g.,
historical value by date. (who did it and when).
Referred to as Warrant Processing - Policies in the UAMACT.
Notes from TES: Need to expose the interest rate on the warrant when it is registered.
Included in Design Document: 1988
2) Requirement TFS ID 1300: The system shall provide for setting a maximum interest rate chargeable for
registered warrants for each agency (at agency type).
Description: The system shall adopt the standardized UAMACT procedure by providing capability in accordance
with A.R.S. §11-635 and 11-636 allowing interest to be calculated on registered warrants at a rate not to exceed
10 percent per year from the date registered until the date the warrant call is processed.
Referred to as Warrant Processing - Procedures in the UAMACT.
Notes from TFS: Consider putting maximum on entity group or entity record.
Included in Design Document: 2058
3) Requirement TFS ID 1294: When paying a registered warrant, the system must be able to calculate interest
payable as part of paying the registered warrant.
Description: The system shall provide capability for registered warrants to accrue interest at a configurable rate
by agency or agency group.
Referred to as Warrant Processing - Policies in the UAMACT (A.R.S. §11-635)
Notes from TES:
• Number of days registered * approved interest/365
• Original warrant is posted to original fund.
• Only warrants on pooled funds can be registered. Non-pooled Funds can go negative.
• Each entity will have the same interest rate. Each entity can have a different rate - max rate is determined by
entity group.
• Interest rate is applied at time of payment. If interest rate is populated on warrant, then that rate should be
used.
• Interest is posted as a separate entry, and goes to the same account string. Interest is posted to the entity
IVI&O account - parameter added to agency master to identify M&O FUND number because the M&O FUND
number can vary from agency to agency.
• Payment is sent to the holder with interest. Vendor payment - warrant holders as vendors.
CR No. 14001-REP-CR003 2 Confidential

THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
• No 1099s. This was stated, but should be verified - there is a statutory requirement for 1099 at a certain
threshold - $10.
• All this activity will be done via JEs. Payments to warrant holders would involve a bank transaction.
Included in Design Document: 1988
4) Requirement TFS ID 1317: The system will allow for defining an alternate agency account for the posting of
interest for each agency.
Included in Design Document: 2058
5) Requirement TFS ID 1566: Each warrant record of the warrant master shall provide for an exception flag which
can only be updated by the treasurees office for reporting.
Description: Warrants in the following state cannot be adjusted by agency users:
- registered
- stopped
- void
- final state. (Final State refers to a group of statuses - Void, Stop, Paid)
A warrant in a registered, stop, void, or part of an active bank presentation (new status?) are not adjustable by
agency users. MCT users are allowed to make changes with the appropriate permissions. A warrant in a Void,
Stop, or Paid stage are not currently editable by agency or MCT users - manual workarounds are used.
Note from TFS: There may be a "Forged warrant process which impacts this.
Included in Design Document: 1989
6) Requirement TFS ID 1320: The system shall provide for defining default interest rate and holder for registered
warrants for each agency.
Description: This requirement emerged in response to the expectation that warrant registration will become more
frequent in the future. It provides for default values which will auto populate the reconciliation form.
Included in Design Document: 2058
7) Requirement TFS ID 1292: The system must be able to generate 1099s for vendor payment.
Description: Court payments, excess proceeds form foreclosures, tax payments
This is a FIT and it's configured in the system.
Recommended Solution:
• Incorporation of the MCESA requirements 1 -7 listed above into the Microsoft Dynamics design and deployment.
Assumptions:
• These requirements were accepted by Microsoft and delivered as part of existing design during builds 1 and 2.
• 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 new or updated FDDs to document design information for TFS Requirement
IDs 1323, 1300, 1294, 1317, 1566 and 1320.
• MCTO has reviewed and approved FDDs for TFS Requirement IDs 1323, 1300, 1294, 1317, 1566 and 1320.
• TRTA Gov (Microsoft) has provided preliminary Technical Design Documents (TDDs) to MCTO for TFS
Requirement IDs 1323, 1300, 1294, 1317, 1566 and 1320.
• TRTA Gov (Microsoft) has delivered a build inclusive of TFS Requirement !Ds 1323, 1300, 1294, 1317, 1566 and
1320 with no P1 or P2 defects found in the implementation of these TFS Requirement IDs.
CR No. 14001-RFP-CR003 3 Confidential

ri THOMSON REUTERS
PROJECT IMPLEMENTATION CHANGE REQUEST
• MCTO has completed at least one round of Requirements Testing for the functionality associated with this CR to
validate that TFS Requirement 1Ds 1323, 1300, 1294, 1317, 1566 and 1320 are implemented with no P1 or P2
defects found in the implementation of these TFS Requirement IDs.
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 Aurnenturn as a result of this
new functionality.
Development:
• These requirements were delivered as part of existing design during builds 1 and 2.
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.
• Technical Design Documents (TDDs) will be 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/Technicai 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 be responsible for testing the new functionality in a timely manner so as to not impact the agreed
project schedule
CR No. 14001-RFP-CR003 4 Confidential

TRTA Gov Program Manager 4/26/17
Sam Wilkins, V.P., Professional Services 4.28.2017