13082-CONTRACT.PDF

SERIAL 13082-CI
(ALL EXHIBITS TO THIS CONTRACT MAY BE REVISED AFTER ENVISIONING IS
COMPLETE (EST. 4/1/14) AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE
DELETED OR ADDED AND PRICING ADJUSTED).
CONTRACT
SERIAL 13082-IC
This Contract is entered into this 25 1h day of September, 2013 by and between Maricopa County ("County"), a
political subdivision of the State of Arizona, and CG1 Technologies and Solutions Inc., a Delaware corporation
("Contractor") for the purchase of Hosting and Support Services, CG1 Advantage General ledger System.
1.0 TERM
This Contract is for a term commencing on the Effective Date and ending on the ten (10 th)
anniversary of the contract (the "Initial Term"). For purposes of this Contract, "Go-Live" or "Go-
Live Date" or "First Productive Use" shall mean the first date when County uses the Services
specified in a live production mode as opposed to a test or training mode.
1.2 The County may, at its option and with the agreement of the Contractor, extend the period of this
Contract for additional five (5) year terms up to a maximum of Thirty (30) years, (or at the
County's sole discretion, extend the contract on a month to month basis for a maximum of six (6)
months after expiration). The County shall notify the Contractor in writing of its intent to extend
the Contract period at least one hundred eighty (180) calendar days prior to the expiration of the
original contract period, or any additional term thereafter, and the County and Contactor will reach
agreement 011 the adjustment of fees applicable to the extended term.
2.0 PAYMENT
2.1 As consideration for performance of the duties described herein, County shall pay Contractor the
sum(s) stated in Exhibit A (Pricing).
2.2 Payment shall be made upon the County's receipt of a properly completed invoice. Invoices shall
contain the following information: Contract number, purchase order number, item numbers,
description of supplies and/or services, sizes, quantities, unit prices, extended totals and any
applicable sales/use tax. Contractor's invoices are due and payable in full within thirty (30) days
from the date of the invoice. Unless the County is subject to a prompt payment provision, if the
County fails to pay any invoiced amount that is not the subject of a good faith dispute when due,
CGI may charge interest on the overdue amount at the maximum rate allowed by law. The County
will promptly notify Contractor of any disputed invoiced amounts.
2.3 Payment shall be made upon the County's receipt of a properly completed invoice as set forth in
Section 2.10 below. In addition, Implementation Services, operational costs, and other costs will
be based on the payments in Exhibit A (Pricing).
2.4 Payment for Software License Fees applicable to a Subproject will be made at the time of
commencement of such Subproject when the first environment is prepared for usage to support
project specific activities. Software license fees for third party components will be payable when
the first environment is prepared for Subproject 1.

2.5 Managed Advantage (Hosting Services) fees are payable quarterly in advance following Go-Live
of each of Subprojects I, II and III as such Subprojects are described in Exhibit B-5 (Project
Implementation Services).
2.6 Implementation Service fees specified in Exhibit A (Pricing) will be invoiced based on the
deliverables included in Exhibit B-5 (Project Implementation Services), and Exhibit A (Pricing).
Invoices will be submitted monthly for all deliverables completed in the prior month. County will
withhold ten percent (10%) of the Implementation Services fees; such withheld amount will be
paid within thirty (30) days following the Go-Live date of each applicable Subproject.
Notwithstanding the preceding, the withheld amount for the Envision Phase will be paid in full
within thirty (30) days following Go-Live of Subproject I. Withheld amounts applicable to each
deliverable within each Subproject are outlined in Exhibit A (Pricing).
2.7 Standard Maintenance services are payable annually in advance.
2.8 County payments for third party services included as part of a Subproject are included within the
pricing set forth in Exhibit A (Pricing) and follow the payment timing associated with the
applicable project deliverables.
2.9 TAX: (SERVICES)
No tax shall be levied against labor or services. It is the responsibility of the Contractor to
determine any and all taxes and include the same in the price.
2.10 INVOICES AND PAYMENTS:
2.10.1 The Contractor shall submit two (2) legible copies of their detailed invoice before
payment(s) can be made. At a minimum, the invoice must provide the following
information:
2.10.1.1 Company name, address and contact
2.10.1.2 County bill-to name and contact information
2.10.1.3 Contract Serial Number
2.10.1.4 County purchase order number
2.10.1.5 Invoice number and date
2.10.1.6 Payment terms
2.10.1.7 Date of service or delivery
2,10.1.8 Quantity (number of days or weeks, if applicable)
2.10.1.9 Contract Item number(s)
2.10.1.10 Description of Purchase
2.10,1.11 Pricing per unit of purchase
2.10.1.12 Extended price
2.10.1.13 Total Amount Due
Problems regarding billing or invoicing shall be directed to the using agency as listed on the
Purchase Order.
2.10.2 Payment will be made to the Contractor by Accounts Payable through the Maricopa
County Vendor Express Payment Program. This is an Electronic Funds Transfer (EFT)
process. After Award the Contractor shall fill out an EFT Enrollment form (to be
provided by the Procurement Officer) or as located on the County Department of Finance
Website as a fillable PDF document (www.maricona.psA/finalice/).
2.10.3 EFT payments to the routing and account numbers designated by the Contractor will
include the details on the specific invoices that the payment covers. The Contractor is
required to discuss remittance delivery capabilities with their designated financial
institution for access to those details.

3.0 DUTIES
3.1 The Contractor shall perform all duties stated in Exhibit B (Scope of Services), Exhibit B-1
(Additional Terms and Conditions), Exhibit B-2 (Managed Advantage Plan Services/Service
Level Agreement), Exhibit B-3 (Proprietary Software License Agreement), Exhibit B-4
(Proprietary Software Maintenance Agreement), Exhibit B-5 (Project Implementation Services),
Exhibit B-6 (Vendor Response Matrix) including Exhibit B-6-I (Budget and Measurement),
Exhibit B-6-2 (Procurement), and Exhibit B-6-3 (Finance), and Exhibit C. Maricopa County
Contractor Travel Policy.
3.2 During the Contract term, County shalt provide Contractor's personnel with adequate workspace
for consultants and such other related facilities as may be required by Contractor to carry out its
contractual obligations.
4.0 TERMS & CONDITIONS
4.1 INDEMNIFICATION:
To the fullest extent permitted by law, Contractor shall defend, indemnify, and hold harmless
County, its agents, representatives, officers, directors, officials, and employees from and against
all third party claims, damages, losses and expenses, including, but not limited to, attorney fees,
court costs, expert witness fees, and the cost of appellate proceedings, as such costs and fees are
permitted under Section 5.4 of Exhibit B-I (Additional Terms and Conditions), and relating to,
arising out of, or alleged to have resulted from the negligent acts, errors, omissions, mistakes or
malfeasance relating to the performance of this Contract by Contractor or its third party service
providers.
The amount and type of insurance coverage requirements set forth herein will in no way be
construed as limiting the scope of the indemnity in this paragraph.
The scope of this indemnification does not extend to the sole negligence of County.
4.2 INSURANCE REQUIREMENTS:
Contractor, at Contactor's own expense, shall purchase and maintain the herein stipulated
minimum insurance from a company or companies duly licensed by the State of Arizona and
possessing a current A.M. Best, Inc. rating of B++6. In lieu of State of Arizona licensing, the
stipulated insurance may be purchased from a company or companies, which are authorized to do
business in the State of Arizona. provided that said insurance companies meet the approval of
County. The form of any insurance certificates must be acceptable to County.
All insurance required herein shall be maintained in full force and effect until all work or service
required to be performed under the terms of the Contract is satisfactorily completed and formally
accepted. Failure to do so may, at the sole discretion of County, constitute a material breach of this
Contract.
Contractor's insurance shall be primary insurance as respects County, and any insurance or self-
insurance maintained by County shall not contribute to it.
Any failure to comply with the claim reporting provisions of the insurance policies related to a
valid County claim, or any breach of an insurance policy warranty shall not affect the County's
right to coverage afforded under the insurance policies.
The insurance policies may provide coverage that contains deductibles or self-insured retentions.
Such deductible and/or self-insured retentions shall not be applicable with respect to the coverage
provided to County under such policies. Contactor shall be solely responsible for the deductible
and/or self-insured retention and County, at its option, may require Contractor to secure payment
of such deductibles or self-insured retentions by a surety bond or an irrevocable and unconditional
letter of credit.

County reserves the right to request and to receive, within ten (10) working days, certificates of
insurance evidencing any or all of the herein required coverage. County shall not be obligated,
however, to advise Contractor of any deficiencies in such certificates and such receipt shall not
relieve Contractor from, or be deemed a waiver of County's right to insist on strict fulfillment of
Contractor's obligations under this Contract.
The Commercial General Liability and Automobile insurance policies required by this Contract,
shall name County, its agents, representatives, officers, directors, officials and employees as
Additional Insureds.
The policies required hereunder, except Workers' Compensation, and Errors and Omissions, shall
contain a waiver of transfer of rights of recovery (subrogation) against County, its agents,
representatives, officers, directors, officials and employees for any claims arising out of
Contractor's work or service.
Contractor is required to procure and maintain the following coverages indicated by a checkmark:
4.2.1 Commercial General Liability.
Commercial General Liability insurance and, if necessary, Commercial Umbrella
insurance with a limit of not less than $2,000,000 for each occurrence, $2,000,000
Products/Completed Operations Aggregate, and $4,000,000 General Aggregate Limit,
The policy shall include coverage for bodily injury, broad form property damage,
personal injury, products and completed operations and blanket contractual coverage, and
shall not contain any provision which would serve to limit third party action over claims.
There shall be no endorsement or modification of the CGL limiting the scope of coverage
for liability arising from explosion, collapse, or underground property damage.
4.2.2 Automobile Liability.
Commercial/Business Automobile Liability insurance and, if necessary, Commercial
Umbrella insurance with a combined single limit for bodily injury and property damage
of not less than $2,000,000 each occurrence with respect to any of the Contractor's
owned, hired, and non-owned vehicles assigned to or used in performance of the
Contractor's work or services under this Contract.
4.2.3 Workers' Compensation.
Workers' Compensation insurance to cover obligations imposed by federal and state
statutes having jurisdiction of Contractor's employees engaged in the performance of the
work or services under this Contract; and Employer's Liability insurance of not less than
$1,000,000 for each accident, $1,000,000 disease for each employee, and $5,000,000
disease policy limit.
4.2.4 Errors and Omissions Insurance.
Errors and Omissions insurance and, if necessary, Commercial Umbrella insurance,
which will insure and provide coverage for errors or omissions of the Contractor, with
limits of no less than $5,000,000 for each claim.
4.2.5 Certificates of Insurance.
4.2.5.1 Prior to commencing work or services under this Contract, Contractor shall have
insurance in effect as required by the Contract in the form provided by the
County, issued by Contractor's insurer(s), as evidence that policies providing the
required coverage, conditions and limits required by this Contract are in full
force and effect. Such certificates shall be made available to the County within
fourteen (14) days. BY SIGNING THE AGREEMENT PAGE THE
CONTRACTOR AGREES TO THIS REQUIREMENT AND
UNDERSTANDS THAT FAILURE TO MEET THIS REQUIREMENT
WILL RESULT IN CANCELLATION OF THIS CONTRACT.

In the event any insurance policy (ies) required by this Contract is (are) written
on a "claims made" basis, coverage shall extend for two (2) years past
completion and acceptance of Contractor's work or services and as evidenced by
annual Certificates of Insurance.
If a policy does expire during the life of the Contract, Contractor will endeavor
to provide a renewal certificate within thirty (30) days from the expiration date.
4.2.5.2 Cancellation and Expiration Notice.
Insurance required herein shall not be permitted to expire, be canceled, or
materially changed without the insurer endeavoring to provide sixty (60) days
written notice to the County.
4.3 NOTICES:
All notices given pursuant to the terms of this Contract shall be addressed to:
For County:
Maricopa County
Department of Materials Management
Attn: Director of Purchasing
320 West Lincoln Street
Phoenix, Arizona
For Contractor:
CGI Technologies and Solutions Inc.
Attn: Yvette Stephens
1215 K Street, Suite 1000
Sacramento, CA. 95819
Copy to: CGI Technologies and Solutions Inc., Attn: Office of General Counsel, 11325 Random
Hills Road, Suite 800, Fairfax, VA 22030
4.4 PRICE ADJUSTMENTS:
Any requests for reasonable price adjustments must be submitted sixty (60) days prior to the
Contract expiration date etc. Requests for adjustment in cost of labor and/or materials must be
supported by appropriate documentation. If County agrees to the adjusted price terms, County
shall issue written approval of the change. The reasonableness of the request will be determined by
comparing the request with the (Consumer Price Index) or by performing a market survey.
4.5 TERMINATION FOR CONVENIENCE:
The County reserves the right to terminate the Contract in whole or in part with twenty-four (24)
months prior written notice when in the best interests of the County without additional penalty or
recourse. Upon receipt of the written notice, the Contractor shall immediately stop all work, as
directed in the notice, notify all subcontractors of the effective date of the termination and
minimize all further costs to the County. In the event of termination under this paragraph, and
upon payment in full for all fees due hereunder, all documents, data and reports prepared by the
Contractor under the Contract excluding Contractor Materials or the CGI System as defined in
Exhibit B-1 (Additional Terms and Conditions) and any additions, changes, modifications or
derivatives thereto, shall become the property of and be delivered to the County upon demand.
The County is responsible for paying Contractor all amounts owed under the Contract for (i)
Services properly performed prior to the effective date of termination or (ii) any Services
Contractor continues to provide at the County's request during the transition period. If County
terminates Exhibit B-4 (Proprietary Software Maintenance Agreement) and has not paid the
maintenance fee for the then current Maintenance Period in full, County must pay to Contractor
the remaining balance of such maintenance fee prior to terminating Exhibit B-4. Termination of
Exhibit B-4 (Proprietary Software Maintenance Agreement) for convenience will result in
termination of Exhibit B-2 (Managed Advantage Plan Services/Service Level Agreement).

Termination of Exhibit B-2 (Managed Advantage Plan Services/Service Level Agreement will be
subject to any disengagement services set forth in Exhibit B-2 and any early termination fees as set
forth under Exhibit A 2.
If Contractor is not providing Managed Services to County under this Agreement, County may
terminate Exhibit B-4 (Proprietary Software Maintenance Agreement) for convenience at any time
upon thirty (30) calendar days' prior written notice to Contractor.
4.6 TERMINATION FOR DEFAULT:
4.6.1 In addition to the rights reserved in the Contract, the County may terminate the Contract
in whole or in part due to the failure of the Contractor to comply with any material term
or condition of the Contract, to acquire and maintain all required insurance policies,
bonds, licenses and permits, or to make satisfactory progress in performing the Contract.
The Procurement Officer shall provide written notice of the breach and the reasons for it
to the Contractor and Contractor shall have thirty (30) days to cure such breach, or in
accordance with the timeframe of any mutually-agreed plan to cure. If the breach is not
cured within such timeframe, the Procurement Officer may terminate the Contract
immediately with written notice. Contractor may terminate the Contract due to a breach
by the County of any material term or condition of the Contract and failure to cure such
breach within thirty (30) days from receipt of written notice from Contractor.
4.6.2 Upon termination under this paragraph, all goods, materials, documents, data and reports
prepared by the Contractor under the Contract, excluding Contractor Materials and the
CGI System and any additions, changes, modifications or derivatives thereto, shall
become the property of and be delivered to the County on demand and payment thereof.
4.6.3 The County may, upon termination of this Contract, procure, on terms and in the manner
that it deems appropriate, materials or services to replace those under this Contract. The
Contractor shall be liable to the County for any excess costs incurred by the County in
procuring materials or services in substitution for those due from the Contractor, subject
to any limitations provided under the Contract.
4.6.4 The Contractor shall continue to perform, in accordance with the requirements of the
Contract, up to the date of termination, as directed in the termination notice.
4.6.5 The County is responsible for paying Contractor all amounts owed under the Contract for
(i) Services properly performed prior to the effective date of termination (ii) any Services
Contractor continues to provide at the County's request during the transition period, and
(iii) any early termination fees as set forth under Exhibit A (Pricing).
4.6.6 Either party may terminate this Exhibit B-4 (Proprietary Software Maintenance
Agreement) upon thirty (30) calendar days' prior written notice if the other has materially
failed to comply with a fundamental obligation under this Exhibit B-4 (Proprietary
Software Maintenance Agreement. If Exhibit B-3 (Proprietary Software License
Agreement) is terminated for any reason, Exhibit B-4 (Proprietary Software Maintenance
Agreement will automatically terminate on the effective date of the termination of
Exhibit B-3 (Proprietary Software License Agreement).

4.6.7 If County breaches the restrictions imposed under the Exhibit B-3 (Proprietary Software
License Agreement) or its nondisclosure obligations under Exhibit B-1 (Additional
Terms and Conditions) with respect to the Software, Contractor will have the right,
without affecting any other rights and remedies Contractor may have, to terminate
Exhibit B-3 (Proprietary Software License Agreement) immediately upon written notice
to County. Termination of Exhibit B-3 (Proprietary Software License Agreement) will
be in addition to. and not in lieu of, other remedies available to the terminating party
under Exhibit B-3 or the Contract.
4.6.8 Termination of Exhibit B-4 (Proprietary Software Maintenance Agreement) for default
will result in termination of Exhibit B-2 (Managed Advantage Plan Services/Service
Level Agreement), subject to any disengagement services set forth in Exhibit B-2,
4.6.9 Within thirty (30) calendar days after the expiration or termination of this Exhibit B-3
(Proprietary Software License Agreement) for any reason, County must, at Contractor's
option, either deliver to Contractor or destroy the original and all copies (including partial
copies) of the Software, the Documentation, all Contractor Confidential Information, and
any other materials as the foregoing are defined and/or provided by Contractor under
Exhibit B-3 (Proprietary Software License Agreement) including copied portions
contained in derivative works, and certify in writing to Contractor that County has fully
performed its obligations under this paragraph.
4.7 FORCE MAJEURE
Notwithstanding anything in this Agreement to the contrary, neither Contractor nor County shall
be liable or responsible for a delay or failure in performing or carrying out any of its obligations
(other than obligations to make payments) under this Agreement caused by force majeure. For
purposes of this Agreement force majeure shall mean any cause beyond the reasonable control of
Contractor or County, as applicable, or beyond the reasonable control of any of their respective
contractors, subcontractors, suppliers or vendors, including without limitation:
4.7.1 Acts of God, including, but not necessarily limited to, lightning, earthquakes, fires,
explosions, floods, wind, other natural catastrophes;
4.7.2 Sabotage, acts of a public enemy, acts of government or regulatory agencies, wars,
blockades, embargoes, insurrections, riots, or civil disturbances;
4.7.3 Labor disputes, including, but not necessarily limited to, strikes, work slowdowns, work
stoppages, or labor disruptions, labor or material shortages, or delays or disruptions of
transportation;
4.7.4 Orders and judgments of any federal, state or local court, administrative agency or
governmental body;
4.7.5 The adoption of or change in any federal, state or local laws, rules, regulations,
ordinances, permits or licenses, or changes in the interpretation of such laws, rules,
regulations, ordinances, permits or licenses, by a court or public agency having
appropriate jurisdiction after the date of the execution of this Agreement; or
4.7.6 Any suspension, termination, interruption, denial or failure to issue or renew by any
governmental authority or other Party having approval rights of any approval required or
necessary hereunder for construction, installation or operation of any Fiber and
equipment or for either Party to perform its obligations hereunder, except when such
suspension, termination, interruption, denial or failure to issue or renew results from the
negligence or failure to act of the Party claiming the occurrence of an event of force
majeure.
If either Contractor or County is rendered unable to fulfill any of its obligations under this
Agreement by reason of force majeure, such Party shall promptly notify the other and shall
exercise due diligence to remove such inability with all reasonable dispatch; provided, that nothing

contained in this paragraph shall be construed as requiring Contractor or County to settle any
strike, work stoppage or other labor dispute in which it may be involved, or to accept any permit,
certificate, license or other approval on terms deemed unacceptable to such Party, or to enter into
any contract or other undertaking on terms which the Party deems to be unduly burdensome or
costly.
4.8 STATUTORY RIGHT OF CANCELLATION FOR CONFLICT OF INTEREST:
Notice is given that pursuant to A.R.S. §38-511 the County may cancel this Contract without
penalty or further obligation within three years after execution of the contract, if any person
significantly involved in initiating, negotiating, securing, drafting or creating the contract on
behalf of the County is at any time while the Contract or any extension of the Contract is in effect,
an employee or agent of any other party to the Contract in any capacity or consultant to any other
party of the Contract with respect to the subject matter of the Contract. Additionally, pursuant to
A.R.S §38-511 the County may recoup any fee or commission paid or due to any person
significantly involved in initiating, negotiating, securing, drafting or creating the contract on
behalf of the County from any other party to the contract arising as the result of the Contract.
4.9 OFFSET FOR DAMAGES;
In addition to all other remedies at law or equity, the County may offset from any money due to
the Contractor any amounts Contractor owes to the County for damages resulting from breach or
deficiencies in performance under this Contract, provided the Contractor has been given notice of
such damages.
4.10 ADDITIONS/DELETIONS OF SERVICE:
The County reserves the right to add and/or delete products and/or services provided under this
Contract through the change order process. Requests for changes by either party will be submitted
to the other party in writing for consideration of feasibility and the likely effect on the cost and
schedule for performance of the Services. The parties will mutually agree upon any proposed
changes, including resulting equitable adjustments to costs and schedules for the performance of
the Services. The agreed changes will be documented in one or more Change Orders. If action or
inaction by Customer or its suppliers' failure to perform their responsibilities in a timely manner,
prevents Contractor from or delays Contractor in performing the Services, Contractor will be
entitled to seek an equitable adjustment in the schedule for performance and the compensation
otherwise payable to it under the Contract. In such event, the parties will mutually agree upon a
Change Order documenting the adjustments. Contractor is not authorized to proceed with a change
without a fully-executed Change Order.
4.11 Change Control Policy. The CG1 project manager will be responsible for managing changes to the
Implementation Services. If any change in the Implementation Services occurs, including, without
limitation the items specified below (each, a "Change Control Item"), that requires CG1 to devote
resources, expend time or otherwise incur costs not contemplated by this Agreement as part of the
Implementation Services, CGI will follow the change control procedures specified in Section 4.11.6
prior to devoting such resources, expending such time or incurring such costs. Change Control
Items include the following:
4.11.1 services requested or otherwise required to be provided in connection with the
Implementation Services that are outside the original scope of the Implementation
Services as documented in Exhibit B-5 (Project Implementation Services).
4.11.2 services requested or otherwise required to be provided in connection with the
Implementation Services resulting from changes to the magnitude of scope in the
Implementation Services due to the discovery or disclosure of new information since
such services were accepted, or due to incorrect information upon which such services
are based,
4.11.3 a change to a project deliverable after that deliverable has been accepted by the County as
complete,

4.11.4 failure by County to meet project-related commitments as documented in Exhibit B-5
(Project Implementation Services) and/or the mutually agreed upon CG1 project plan.
4.11.5 additional work effort required as a result of schedule delays caused by a County-
approved Change Control Item.
4.11.6 Change Control Procedures. Upon the occurrence of a Change Control Item, the CGI
project manager will deliver to the County a notice (a "Change Control Notice") setting
forth (i) the details of the Change Control item, (ii) an analysis of the impact of the
Change Control Item on the implementation of the System, and (iii) an estimate of the
time, materials, and aggregate costs required to address the Change Control Item. The
County representative will notify the CGI project manager within a mutually agreed-upon
time frame whether or not the Change Control Item is approved as submitted, if the
County does not respond to the Change Control Item within the specified period, the
Change Control item will be deemed to be rejected by the County. If the County rejects a
Change Control Item, COT may proceed to provide the Implementation Services without
implementing the Change Control Item or CGI may dispute the rejection of the Change
Control Item in accordance with Section 4.11.7
4.11.7 Change Control Dispute Resolution. If CG1 and County disagree as to whether an event,
requirement, measure, or deliverable is subject to the change control provisions set forth
in Sections 4.11.1 through and 4.11.6, within five (5) business days of discovery of such
disagreement, the CGI project manager and the County representative shall meet (in
person or by telephone) and make a good faith effort to resolve the disagreement. If the
parties are unable to resolve the dispute, the CGI project manager will summarize the
dispute in writing and forward it to a senior executive of COI and a senior executive or
officer of the County identified by the County representative and, in each case, not
involved in the project on a day to day basis. Such executives will meet (in person or by
telephone) within five (5) business days of delivery of the dispute summary and make a
good faith attempt to resolve the dispute. If the senior executives are unable to resolve
the dispute, the dispute will be mediated as soon as practicable by a third-party mediator
knowledgeable in software development and support and reasonably acceptable to CGI
and County. The cost of the mediation will be shared equally by CGI and County.
4.12 SUBCONTRACTING:
The Contractor may not assign this Contract or subcontract to another party for performance of the
terms and conditions hereof without the written consent of the County, which shall not be
unreasonably withheld; provided, however, use of service providers providing services on a shared
basis across Contractor clients shall not be considered subcontractors for purpose of this provision.
All correspondence authorizing subcontracting must reference the Proposal Serial Number and
identify the job project.
4.13 MISCELLANEOUS PROVISIONS:
4.13.1 No Solicitation of Employees. Neither party will recruit or solicit the other's personnel or
employees that have become known to a party as a result of the Services performed until the
earlier of one year after (i) the termination of this Agreement or (ii) that person is no longer
employed by the other party. The provisions of this 4.12.1 will survive the termination of this
contract.
4.13.2 During the course of the contract, Maricopa County reserves the right to require Contractor to
reassign or otherwise remove from the project any Contractor employees or sub-contractors
found unacceptable by Maricopa County who are not performing as warranted, or for any
lawful reason. Proposed replacement personnel shall be discussed and addressed by mutual
agreement, agreement not to be unreasonably withheld. if any team member leaves Contractor
employment prior to completion of its assignment hereunder, Contractor will provide the
County with a comparable replacement and provide two weeks (at no cost) of project
knowledge transfer.

4.13.3 Independent Contractors. The performance by Contractor of its duties and obligations under
this Contract will be that of an independent contractor and nothing contained in this
Agreement will create or imply an agency, joint venture or partnership between Contractor
and County. Neither the employees of Contractor nor Contractors subcontractors will be
considered employees or agents of County. Unless expressly stated in this Contract, none of
Contractors, its employees or its subcontractors may enter into contracts on behalf of, bind, or
otherwise obligate County in any manner whatsoever. Contractor shall be responsible for the
acts or omissions of any Contractors subcontractors to the same extent that Contractor is
responsible for its own actions under this Agreement.
4.13.4 Injunctive Relief. In the event of an actual or impending breach, the non-breaching party, in
addition to any remedy available at law, will be entitled to seek equitable relief, including
injunction and specific performance.
4.14 AMENDMENTS:
All amendments to this Contract shall be in writing and approved/signed by both parties. Maricopa
County Materials Management shall be responsible for approving all amendments for Maricopa
County.
4.15 RETENTION OF RECORDS:
The Contractor agrees to retain all financial books, records, and other documents relevant to this
Contract for five (5) years after final payment or until after the resolution of any audit questions
which could be more than five (5) years, whichever is longer. The County, Federal or State
auditors and any other persons duly authorized by the Department shall have full access to, and the
right to examine copy and make use of, any and all said materials.
If the Contractor's books, records and other documents relevant to this Contract are not sufficient
to support and document that requested services were provided, the Contractor shall reimburse
Maricopa County for the services not so adequately supported and documented. The parties agree
that sufficient support and documentation means the monthly service level documentation and/or
invoices for services.
4.16 AUDIT DISALLOWANCES:
If at any time, County determines that a cost for which payment has been made is a disallowed
cost, such as overpayment, County shall notify the Contractor in writing of the disallowance.
County shall also state the means of correction, which may be but shall not be limited to
adjustment of any future claim submitted by the Contractor by the amount of the disallowance, or
to require repayment of the disallowed amount by the Contractor.
4.17 VERIFICATION REGARDING COMPLIANCE WITH ARIZONA REVISED STATUTES §23-
214 AND FEDERAL IMMIGRATION LAWS AND REGULATIONS:
4.17.1 By entering into the Contract, the Contractor warrants compliance with the Federal
Immigration and Nationality Act (FINA) and all other Federal immigration laws and
regulations related to the immigration status of its employees. The contractor shall obtain
statements fi-om its subcontractors certifying compliance and shall furnish the statements to
the Procurement Officer upon request. These warranties shall remain in effect through the
term of the Contract. The Contractor and its subcontractors shall also maintain
Employment Eligibility Verification forms (I-9) as required by the U.S. Department of
Labor's Immigration and Control Act, for all employees performing work under the
Contract. 1-9 forms are available for download at USC1S.GOV .
4.17.2 The County may request verification of compliance for any Contractor of subcontractor
performing work under the Contract. Should the County suspect or find that the Contractor
or any of its subcontractors are not in compliance, the County may pursue any and all
remedies allowed by law. including, but not limited to: suspension of work, termination of
the Contract for default, and suspension and/or department of the Contractor. All costs
necessary to verify compliance are the responsibility of the Contractor.

4.18 CERTIFICATION REGARDING DEBARMENT AND SUSPENSION
4.18.1 The undersigned (authorized official signing for the Contractor) certifies to the best of his
or her knowledge and belief, that the Contractor, defined as the primary participant in
accordance with 45 CFR Part 76, and its principals:
4.18.1.1 are not presently debarred, suspended, proposed for debarment, declared
ineligible, or voluntarily excluded from covered transactions by any Federal
Department or agency;
4.18.1.2 have not within 3-year period preceding this Contract been convicted of or had a
civil judgment rendered against them for commission of fraud or a criminal
offense in connection with obtaining, attempting to obtain, or performing a
public (Federal, State or local) transaction or contract under a public transaction;
violation of Federal or State antitrust statues or commission of embezzlement,
theft, forgery, bribery, falsification or destruction of records, making false
statements, or receiving stolen property;
4.18.1.3 are not presently indicted or otherwise criminally or civilly charged by a
government entity (Federal, State or local) with commission of any of the
offenses enumerated in paragraph (2) of this certification; and
4.18.1.4 have not within a 3-year period preceding this Contract had one or more public
transaction (Federal, State or local) terminated for cause of default.
4.18.1.5 Should the Contractor not be able to provide this certification, an explanation as
to why should be attached to the Contact.
4.18.1.6 The Contractor agrees to include, without modification, this clause in all lower
tier covered transactions (i.e. transactions with subcontractors) and in all
solicitations for lower tier covered transactions related to this Contract.
4.19 GOVERNING LAW:
This Contract shall be governed by the laws of the state of Arizona. Venue for any actions or
lawsuits involving this Contract will be in Maricopa County Superior Court or in the United States
District Court for the District of Arizona, sitting in Phoenix, Arizona
4.20 ORDER OF PRECEDENCE:
In the event of a conflict in the provisions of this Contract and Contractor's license agreement, if
applicable, the terms of this Contract shall prevail.
4.21 INFLUENCE
As prescribed in MC1-1202 of the Maricopa County Procurement Code, any effort to influence an
employee or agent to breach the Maricopa County Ethical Code of Conduct or any ethical conduct,
may be grounds for Disbarment or Suspension under MCI -902.
An attempt to influence includes, but is not limited to:
4.21.1 A Person offering or providing a gratuity, gift, tip, present, donation, money,
entertainment or educational passes or tickets, or any type valuable contribution or
subsidy,
4.21.2 That is offered or given with the intent to influence a decision, obtain a contract, garner
favorable treatment, or gain favorable consideration of any kind.
4.21.3 If a Person attempts to influence any employee or agent of Maricopa County, the Chief
Procurement Officer, or his designee, reserves the right to seek any remedy provided by
the Maricopa County Procurement Code, any remedy in equity or in the law, or any
remedy provided by this contract.

4.22 SEVERABILITY:
The invalidity, in whole or in part, of any provision of this Contract shall not void or affect the
validity of any other provision of this Contract.
4. 7 3 RIGHTS IN DATA:
The County shall have the use of all data and reports resulting from this Contract without
additional cost or other restriction except as provided hereunder or by law. Each party shall
supply to the other party, upon request, any available information that is relevant to this Contract
and to the performance hereunder.
4.24 INTEGRATION:
This Contract and its Exhibits represent the entire and integrated agreement between the parties
and supersedes all prior negotiations, proposals, communications, understandings, representations,
or agreements, whether oral or written, express or implied.
4.25 GOVERNING LAW:
This Contract shall be governed by the laws of the state of Arizona. Venue for any actions or
lawsuits involving this Contract will be in Maricopa County Superior Court or in the United States
District Court for the District of Arizona, sitting in Phoenix, Arizona.
4.26 NO WAIVER:
Except as otherwise permitted in this Contract, no failure or delay by a party in exercising any
right, power or remedy will operate as a waiver of that right, power or remedy, and no waiver will
be effective unless it is in writing and signed by the waiving party. If a party waives any right,
power or remedy, the waiver will not waive any successive or other right, power or remedy the
party may have under the Contract.
4.27 INCORPORATION OF DOCUMENTS:
The following are to be attached to and made part of this Contract:
1.1.1 Exhibit A, Pricing;
1.1.2 Exhibit B, Scope of Work;
1.1.3 Exhibit B-1, Additional Terms and Conditions
1.1.4 Exhibit B-2, Managed Advantage/Service Level Agreement
1.1.5 Exhibit B-3, Software License Agreement
1.1.6 Exhibit B-4, Software Maintenance Agreement
1.1.7 Exhibit B-5, Project Implementation Services
1.1.8 Exhibit B-6, Vendor Response Matrix, (B-6-1 Budget and Measurement, Exhibit B-6-2
Procurement, Exhibit B-6-3 Finance)
1.1.9 Exhibit C, Maricopa County Contractor Travel Policy

IN WITNESS WHEREOF, this Contract is executed on the date set forth above.
CGI TECHNOLOGIES AND SOLUTIONS INC.
AUTylVIUZED SIGNATURE
,11--/Z, ( I Tdore"
PRINTED NAME AND TITLE
looc ,A 7 19
ADDRESS.
DATE
1VIARICOPA COUNTY
BY:
CHAIRMAN, BOARD OF SUPERVISORS DATE
ATTESTED:
CLERK OF THE BOARD DATE
APPROVED AS TO FORM:
DEPUTY MARICOPA COUNTY ATTORNEY DATE

13082 EXHIBIT A
PRICING
13082 EXHIBIT A PRICING 7 1
(ALL EXHIBITS TO THIS CONTRACT MAY BE REVISED AFTER ENVISIONING IS COMPLETE (EST. 4/1/14) AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE
DELETED OR ADDED AND PRICING ADJUSTED).
PRICING SHEET: NIGP CODE 92047 .i_. 1 ].
CONTRACTOR NAME: CG[ TECHNOLOGY AND SOLUTIONS INC.
VENDOR #: W000008130
CONTRACTOR ADDRESS: 1215 K Street Suite 1000,..SacrementoA 95819
P.O. ADDRESS: SAME i 1
BIDDER PHONE #: 916-830-1100 1 1
BIDDER FAX #: .91 .6-83.0:11. 99
COMPANY WEB SITE:
1
COMPANY CONTACT (REP): `r vette S'keptiens
E-MAIL ADDRESS (REP): 4
-I-
-[- 1
OTHER GOVT. AGENCIES MAY USE THIS CONTRACT: YES I
-F 1 I
PAYMENT TERMS: I 1
NET 30 Days 1
1.0 PRICING: 1 j 1 I ! - $44,812,465 . .
-4
.1 ANNUAL FEES FOR ALL HOSTING SERVICES IN EXHIBIT B i I
(STARTS AT FIRST PRODUCTION USE) T
. .1 YEAR 1 50 Per Quarter in Advance
1.1.2 YEARS 2 - 3 9281,254 Per Quarter in Advance
1.1.3 YEARS 4- 10 $392,816 Per Quarter in Advance
TOTAL FOR 10 YEARS $13,248,893
1
1.2 SOFTVVARE LICENSES -7- i
(PAID AT INSTALLATION OF LICENSES; AMOUNT INCLUDES 3RD PARTY & INFOADVANTAGE)
1.2.1 BUDGET AND MEASUREMENT LICENSES 1 $818,704
1.2.2 FINANCE LICENSES $494,273
-1
1.2.3 PROCUREMENT LICENSES $338,284
TOTAL FOR ALL SOFTVVARE LICENSES $1,651,261
1.3 ANNUAL MAINTENANCE -1-
1.3.1 YEAR 1 $354,827
1.3.2 YEAR 2 $925,556
1.3.3 YEAR 3 $925,556
1.3.4 YEAR 4 $925,556
1.3.5 YEAR 5 $925,556
1.3.6 YEAR 6 _1 $1,057,578
1.3.7 YEAR 7 $1,057,578
1.3,8 YEAR 8 $1,057,578
1.3.9 YEAR 9 $1,057,578
1.3.10 YEAR 10 $1,057,578
TOTAL FOR 10 YEARS $9,344,941
_I
1.4 IMPLEMENTATION SERVICES
(ASSSUMES 10% WITHHOLD WHICH WILL BE PAID IN FULL WITHIN 30 DAYS OF EACH SUBPROJECT GO LIVE)
(DELIVERABLES AND ASSOCIATED DATES AND AMOUNTS FOR 1.4.2, 1.4.3 AND 1.4.4 WILL BE DETERMINED AFTER THE ENVISION PHASE)
1.4.1 ENVISION PHASE (All Subproject business areas per Exhibit B-5) lInvoice Amount Retainage Total Amount
1.4.1.1 Project Plan 1 $124,134 $13,793 $137,927
1.4.1.2 Project Kickoff Meeting $85,436 $9,493 $94,929
1.4.1.3 Project Management Status Reports - Month 1 (5th Business Day of Month) $171,070 $19,008 _I $190,078
1.4.1.4 Project Management Status Reports - Month 2 (5th Business Day of Month) $171,070 $19,008 $190,078
1.4.1.5 Project Team Training for Prototyping $161,545 $17,949 $179,494
1.4.1.6 Prototype Scripts & Execution I $306,084 $34,009 , $340,093
1.4.1.7 Project Management Status Reports - Month 3 (5th Business Day of Month) $171,070 $19,004 1 $190,078
1.4.1.8 Fit Gap Report I $391,107 $43,456 , [ 1 $434,563
1.4.1.9 Project Management Status Reports - Month 4 (5th Business Day of Month) ---, $171,070 $19,0081 1 $190,07g
1.4.1.10 Application Software Customizations - Concept Papers $136,0381 $15,1151 1 $151,153_1
1.4.1.11 Project Management Status Reports - Month 5 (5th Business Day of Month) 6171,07ã1 $19,0081- 1 $190,0781
1.4.1.12 Upgrade Analysis Document (DAD) $442,1211 $49,1251 1 $491,2461
1.4.1.13 Project Management Status Reports - Month 6 (5th Business Day of Month) -[ $171,0701 $19,0081 "f_ $190,078
TOTAL FOR ENVISION PHASE DELIVERABLES $2,672,8361 $296,987 52,969,8731
.4.2 BUDGET AND MEASUREMENT LICENSES kCREATE AND ACHIEVE PHASES) I $1,466,353iNOT , TO EXCEED
1.4.3 FINANCE (CREATE AND ACHIEVE PHASES) 1 $11,519,0901NOT TO EXCEED
1.4.4 PROCUREMENT - Strategic Sourcing and Tactical Procurement (CREATE AND ACHIEVE PHASES) $4,612,0541NOT TO EXCEED
TOTAL FOR IMPLEMENTATION SERVICES $20,567,3701
I ,
1.5 ALL TRAVEL IS INCLUDED IN THE ABOVE NUMBERS AND SHALL BE IN CONFORMANCE
WITH THE COUNTY CONTRACTOR TRAVEL POLICY IN EXHIBIT C ,
J I

13082 EXHIBIT A-1
13082 Exhibit A-I Rate Card
a) The below Rate Card is provided for incremental Services in Steady State.
b) All Services provided at the rates included in this section will be invoiced on a Time and Materials basis with travel and other reimbursable expenses
invoiced in addition to the specified hourly rates.
c) Contractor will provide an updated Rate Card with each estimate provided for incremental Services. The submitted Rate Card will not exceed a 5%
increase year over year from the Rate Card in this Exhibit.
RAT FABLE
Position Group I Typical Roles Role Description Hourly
I Rates
Offshore Program et Programmer ISoftwa i development, build and unit test, product test and support. $30
Business Analyst Data gathering, analysis, interviews , and assessment. Produce detailed
output per scope of work
Business Analy Develop systems as required, involved in testing, diagnosing and fixing
Developer Developer oftware issues. Provide training for users, lead a team of developers, and
manag,e _ project . work.
Infrastructure/Operations Analyst Establish technical environment through hardware and software
procurement, installation and configuration.
Senior Trainer tesponsible for developing training material, preparing and managing
Ming schedules per scope of work.
Data gathering, analysis, interviews and assessment. Produce detailed
Senior Business Consultant output per scope of work. Manage work packages and oversee junior
Team Lead / Senior
Consultant $155
Develop systems as required, diagnosing and fixing software issues.
Team Lead - Developer Overall lead for software development work streams including expert
support, coaching, and status management.
-
Team lead for software development or environment architecture and
System Architect operational design work streams including expert support, coaching, and
status management.
Plans and manages all aspects of assignments, including workload of all
Project Manager I Project Manage sub-project teams. Coordinates approach and progress with senior State
leant members. Analyzes and assesses data. Advises senior management.
Subject Matter Expel Product/ Industry SME Provides deep industry or product expertise. Sets direction and strategy
for business and product implementations.
Overall responsibility for engagement and day-to-day management of
Engagement Manager! Engagement Manager program tennis across client site and coordination of activities to achieve
the State's goals. Periodic reviews of strategy, approach, and progress
he State project/progrant manager.

13082 EXHIBIT A-2
Termination for Convenience Fees: Exhibit 8-2
CGI assumes there is no Termination for Convenience (TforC) the first two years of the Contract (24
months). If the County terminates Exhibit 8-2 under the Contract for other than CGI's breach, the
County shall pay to CGI a TforC Fee as outlined in Exhibit below. These TforC Fees are exclusive of
any Disengagement Services as described in Exhibit B-2. These fees do not apply until the
Envisioning process is complete and all changes approved and incorporated.
Early Termination Fees
Termination
Year Start Data End Date Fees
ralttnentifieniMe. Year 1 171111aMMERMil Oct-13 Jun-14 WartIleala4V.- 1,230,788
Year 2 Jul-14 Jun-15 1,287,742
Year 3 Jul-15 Jun-16 1,252,209
Year 4 Jul-16 Jun-17 1,058,147
Year 5 Jul-17 Jun-181 864,086
Year 6 Jul-18 Jun-19' 667,611
Year 7 Jul-19 Jun-20 1 556,026
Year 8 1 Jul-20 Jun-21! - 444,141
Year 9 : Jul-21 Jun-22 1 269,048
Year 10 ,• ' Jul-22 Jun-23!

SERIAL 13082-CI
13082 EXHIBIT B -- SOW FOR PR DUCTS AND SERVICES
(THIS EXHIBIT MAY BE REVISED AFTE ENNIS'•NING IS C MPLETE AN
SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED OR ADDED AN
PRICING ADJUSTED).
1.0 INTENT
The purpose of this document is to provide the business terms defining the services associated.
with upgrading the County to CGI Advantage® Version 3 and hosting the upgraded application
environment at CGI's data center in Phoenix, Arizona. These terms are based upon information
provided by the County, as well as COI's experience implementing, hosting and maintaining CGI
Advantage for customers of similar size and scope, and will be used to shape the contents and
operating parameters of the Contract between the parties.
2.0 OVERVIEW OF SERVICES
The following provides an overview of the services to be provided by Contractor:
2.1 Software
The following Software will be delivered:
• CGI Advantage® Financial Management System 3.10 (platform/database)
including:
o CGI Advantage Grants Lifecycle Management
o CGI Advantage Inventory Management
o COI Advantage Asset Management
• COI Advantage Procurement Professional including
o CGI Advantage Vendor Self-Serve
• CGI Advantage Performance Budgeting Formulation
• CGI Advantage Salary and Benefits Forecasting
• CGI infoAdvantage End User Bundle
• CGI infoAdvantage Dashboard
• Adobe LiveCycle
• Pervasive Data Integrator Developer
• Pervasive Data Integration Universal Engine
SAP BusinessObjects including
o BA&T SAP Busin.essObjects Business Intelligence Platform X13.1 SP5
o BA&T SAP BusinessObjects Web Intelligence XI 3.1 SP5
o BA&T SAP BusinessObjects Dashboard XI 3.1 SP5
o SAP Application Standalone Business Analytics Professional User
o SAP Application Standalone BI Limited User
• Finite Matters, Ltd. PatternStream®
• Versata Logic Server
• Versata Designer Studio
• IBM WebSphere Application Server Network Deployment
• IBM WebSphere Application Server Processor
• Liason (Hubspan) Punch Out
2.2 Implementation Services
Contractor uses a proven delivery methodology that is comprised of three Project Phases:
Envision, Create and Achieve, and is supported by Contractor-specific tools, utilities,

ERIAL 13082-Cl
templates, checklists, and deliverables as described herein. Contractor's delivery
methodology contains multiple checkpoints within each Phase that contains activities
such as the fit gap, software design and development, integrated system testing, and user
acceptance testing. Contractor also has a prerequisite for moving from one phase to the
next. The implementation services are described in Exhibit B-5.
2.2.1 Envision Phase
A single Envision Phase for all Subproject business areas covered under this Contract
will be conducted to confirm the County's business requirements arid develop a
blueprint for the Project. The Envision Phase encompasses activities related to the
analysis for implementing Advantage 3, The Envision phase findings (comprised of a fit-
gap analysis and approaches for key project activities, such as: conversion, reports,
forms, and training) are documented in the Upgrade Analysis Document (UAD).
The Project Team will conduct the fit-gap activities associated with Performance
Budgeting early in the Envision Phase to determine the feasibility of implementing
Performance Budgeting by October 31, 2014. All other components must be live by July
2016.
2.2.2 Create Phase
The Create Phase encompasses activities related to software construction (forms, reports,
interfaces, conversions and application software customizations /enhancements) and the
planning and execution of implementation tasks, such as, application configuration and
data set-up, testing, training, and preparations for production operations. The detailed
plan for these activities will be defined during the Envision Phase as part of the UAD.
2.2.3 Achieve Phase
The Achieve Phase encompasses the activities required to support production operations
of Advantage 3. It is comprised of the production cutover activities (e.g., scheduling of
daily, weekly, monthly, quarterly, annually, and on-demand batch jobs) and post-
implementation activities, such as the monitoring of system performance in production
operations. The detailed plan for these activities will be defined during the Create Phase.
2.3 Hosting Services
Contractor will provide Managed Services in support of the Advantage 3 application and
associated infrastructure in a fully hosted, COI Data Center under the Managed Services
program as described in Exhibit B-2. These Managed Services provide a staff
management and delivery model to support the Advantage 3 application and underlying
technical infrastructure and provides defined minimum levels of support as part of the
Managed Services. Managed Services will be provided for ten (10) years under this
Contract.

13082-EXHIBIT B-1
13082 EXHIBIT -1 ADDITIONAL TERMS AND CONDITIONS
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND
SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED OR ADDED AND
PRICING ADJUSTED).
The following additional terms shall apply to the parties' rights and obligations under the Contract.
PART ONE: GENERAL TERMS AND CONDITIONS
1.0 DEFINITIONS
Capitalized terms used in this Exhibit B-1 will have the meanings given below or in the context
in which the term is used, as the case may be.
"Affiliate" of a party means any person or entity that directly or indirectly controls, is
controlled by or is under common control with, the party. As used in this definition,
"control" means actual or equitable ownership of a majority of the voting securities of an
entity (or other securities, partnership interests or means of electing or directing the
management of the entity).
1.2 "CGI Materials" means all components of the CGI System, excluding any County-
provided Managed Application, and all intellectual property rights in and to the CGI
System, and to all other proprietary rights, materials, Work Products or assets that are
employed or developed in providing the Hosting Services, including any successors,
updates, extensions, derivatives, translations or enhancements of any of the foregoing.
1.3 "CGI System" means, collectively, all of the components of the infrastructure and
computing environment used by CGI to perform the Hosting Services, whether owned by
CG1 or its suppliers, including the Managed Application(s), CGI or third party facilities,
hardware, operating systems, software applications and associated databases, tables, data
and documentation and training materials. "CGI System" excludes Managed
Application(s) to the extent the Managed Application is a third party product provided to
CGI by the County.
1.4 "Content" means any information, data, and any other materials placed by the County
and/or its customers and/or by CG1 on the County's behalf onto the CG1 System.
1.5 "Deliverables" mean any materials to be developed by CGI that are designated in a
services Exhibit as being subject to a formal acceptance process upon delivery to
County. Deliverables may be either written deliverables or software deliverables.
1.6 "Documentation" means the user and other manuals that are generally made available for
the Software as listed in Attachment A of Exhibit B-4.
1.7 "Hosting Services" means the physical location, hardware, software and associated
operational and support services provided by CGI on the County's behalf as more fully
defined in Exhibit B-2 of the Contract.
1.8 "Managed Application(s)" means the proprietary software application(s) listed in Exhibit
B-2 that will be hosted and operated for use in providing Hosting Services to the County.

13082-EXHIBIT B-1
1.9 "Services" means the implementation and Hosting Services that CGI performs for the
County under the Contract, as set forth in one or more Exhibits hereunder.
1.10 "Software" means the proprietary software licensed to the County as listed in
Attachment A of Exhibit B-4.
"Specifications" mean a mutually agreed upon document that describes with particularity
the functions to be performed by a software Deliverable and that is designated in the
Exhibit under which the software Deliverable is being developed as the specifications for
that software Deliverable.
1.12 "Work Products" mean results of Services that are first created in the performance of the
Contract.
2.0 CONFIDENTIALITY.
2.1 Confidential Information. "Confidential Information" means non-public information
belonging to or in the possession of a party that is confidential or a trade secret and is
furnished or disclosed to the other party under the Contract (including information
exchanged in contemplation of entering into the Contract): (i) in tangible form and
marked or designated in writing in a manner to indicate it is confidential or a trade
secret; or (ii) in intangible form and that either is of a nature that a reasonable person
would understand to be confidential or a trade secret or is identified as confidential or a
trade secret in a writing provided to the receiving party within thirty (30) business days
after disclosure. Confidential Information also includes the Contract, Software,
Documentation, CGI Materials, the CGI System, and any County-provided Managed
Application(s), whether or not marked as such.
2.2 Exclusions. "Confidential Information" does not include any information that, as
evidenced by written documentation: (i) is already known to the receiving party without
restrictions at the time of its disclosure by the furnishing party; (ii) after its disclosure by
the furnishing party, is made known to the receiving party without restrictions by a third
party having the right to do so; (iii) is or becomes publicly known without violation of
the Contract; (iv) is independently developed by the receiving party without reference to
the furnishing party's Confidential Information; or (v) is required to be disclosed under
applicable securities, tax or other regulations.
2.3 Standard of Care. "Confidential Information" will remain the property of the furnishing
party, and the receiving party will not be deemed by virtue of the Contract or any access
to the furnishing party's Confidential Information to have acquired any right, title or
interest in or to the Confidential Information. The receiving party agrees: (i) to hold the
furnishing party's Confidential Information in strict confidence, affording the furnishing
party's Confidential Information at least the same level of protection against
unauthorized disclosure or use as the receiving party normally uses to protect its own
information of a similar character, but in no event less than reasonable care; (ii) to limit
disclosure of the furnishing party's Confidential Information to employees having a need
to know the information for the purposes of the Contract; (iii) not to disclose any such
Confidential Information to any third party; (iv) to use the furnishing party's
Confidential Information solely and exclusively in accordance with the terms of the
Contract in order to carry out its obligations and exercise its rights under the Contract;
(v) not to sell, rent, lease, transfer, encumber, pledge, reproduce, transmit, modify,
reverse engineer, compile, disassemble or otherwise use any Confidential Information of
the disclosing party, in whole or in part, and (vi) to notify the furnishing party promptly

13082-EXHIBIT B-1
of any unauthorized use or disclosure of the furnishing party's Confidential Information
and cooperate with and assist the furnishing party in every reasonable way to stop or
minimize such unauthorized use or disclosure.
2.4 Compelled Disclosure. If the receiving party receives a subpoena or other valid
administrative or judicial notice requesting the disclosure of the furnishing party's
Confidential Information, the receiving party will promptly notify the furnishing party.
If requested, the receiving party will provide reasonable cooperation to the furnishing
party in resisting or limiting the disclosure at the furnishing party's expense. Subject to
its obligations stated in the preceding sentence, the receiving party may comply with any
binding subpoena or other process to the extent required by law, but will in doing so
make every effort to secure confidential treatment of any materials disclosed.
2.5 Return or Destruction. Upon termination or expiration of this Contract, the receiving
party, at the furnishing party's option, will return or certify as destroyed all Confidential
Information of the furnishing party that the receiving party does not possess under a valid
license; provided that CGI may retain one (1) copy of all of its work products (including
working papers) produced under the Contract for archival purposes.
2.6 Relief. Each party agrees that if a court of competent jurisdiction determines that the
receiving party has breached, or attempted or threatened to breach, any of its
confidentiality obligations to the furnishing party or the furnishing party's proprietary
rights, money damages will not provide an adequate remedy. Accordingly, the
furnishing party will be entitled to seek appropriate injunctive relief and other measures
restraining further attempted or threatened breaches of such obligations.
3.0 INTELLECTUAL PROPERTY RIGHTS
3.1 Pre-existing CGI Materials, Third-Party Materials, and Open Source Software. Any pre-
existing CGI materials, third-party materials, Open Source software, and derivatives
thereof, incorporated in a Deliverable or necessary to use a Deliverable will be licensed
to County under separate license terms. Such license terms will be, as appropriate, set
forth in a license agreement (i) executed between CGI and County (e.g., under Exhibit B-
4), or (ii) obtained by County from the applicable third party vendor, or iii) in the case of
Open Source software, the license terms set forth in the applicable Open Source license
agreement. County acknowledges that a separate license fee may be charged by CGI or
the third-party vendor for any such licensed materials.
3.2 Developed Materials. CGI will own all intellectual property rights, title and interest in
and to all Work Products developed by it under the Contract. Subject to payment in full
by County of all amounts owed to CGI under the applicable Exhibit, CGI grants to
County an irrevocable, nonexclusive, royalty-free right and license to use, execute,
reproduce, modify and create derivative works from such Work Products for County's
own internal use of the Software and Documentation.
3.3 County Data and Materials. County hereby grants to CGI a nonexclusive, royalty-free
license to use any County data and materials provided by it to CGI during the term of this
Contract for the purpose of performing the Services for County.
3.4 Reservation of Rights. Neither party will be prevented from using in its business any
general ideas, concepts, expressions, know-how, skills and experience possessed by it
prior to, or developed or learned by it in the course of, performing the Services, subject
to each party's confidentiality obligations hereunder.

13082-EXHIBIT B-1
4.0 LIMITED WARRANTIES AND REMEDY FOR BREACH OF WARRANTY
4.1 Services Warranty. CGI warrants, for a period of thirty (30) days after performance of
Services provided on a non-recurring basis, that such Services will be performed in a
workmanlike manner consistent with industry standards reasonably applicable to the
performance of such Services. If the County believes there has been a breach of this
warranty, it must notify CG1 in writing within the warranty period stating in reasonable
detail the nature of the alleged breach. If there has been a breach of this warranty, then
CGI's sole obligation, and the County's exclusive remedy, will be for CGI to correct or
re-perform, at no additional charge, any affected Services to cause them to comply with
this warranty; provided however, if CG1 is unable to correct such breach the County may
terminate the Contract and seek damages subject to the terms of the Contract.
4.2 Software Deliverables Produced on a Fixed-Price Basis. CGI warrants that, during any
Warranty Period specified in the applicable Exhibit for non-recurring Services (or if no
Warranty Period is specified in the Exhibit, for a period of thirty (30) days from
delivery), each software Deliverable developed on a fixed-price basis and delivered
under that Exhibit will continue to perform the functions described in its Specifications
without Defects. As used in this Contract, "Defect" means a reproducible material
deviation of a Software Deliverable from its Specifications. If County believes there has
been a breach of this warranty, it must notify CGI in writing within the Warranty Period
describing the Defect in sufficient detail to enable CG1 to recreate it. If there has been a
breach of this warranty, then CGI's sole obligation, and County's exclusive remedy, will
be for CGI to correct the Defect at no additional charge, or terminate the Statement of
Work in whole or in part.
4.3 Non-infringement. CG1 warrants that the Work Products and the County's access to any
CGI-provided Managed Application(s), will not, to CGI's knowledge, infringe any third
party copyrights, patents or trade secrets that are enforceable under the laws of the
United States of America.
4.1.1 If a third party brings an action against the County making allegations that, if
true, would constitute a breach of this warranty, then CGI will, at its own
expense and subject to the provisions of Section 5.4, defend, indemnify and hold
the County harmless in such proceeding, and CG1 will pay all settlements, costs,
damages and legal fees finally awarded.
4.1.2 If such a proceeding is brought or appears to CGI to be likely to be brought, CGI
may, at its sole option and expense, either obtain the right for the County to
continue to access the Work Products and/or Managed Application(s) or replace
or modify the Work Products and/or Managed Application(s) to resolve such
proceeding. If CG1 finds that neither of these alternatives is available to it on
commercially reasonable terms, CGI may be required to terminate the County's
access, in which case the County will receive (i) with respect to the Hosting
Services, a refund of the amounts pre-paid by it for the particular Hosting
Services that are not provided as a result of such terminated access, and/or (ii)
with respect to the Work Products, a refund of the amounts paid for the Work
Products, less a mutually agreed sum for depreciation.
This Section 4.3 states CGI's entire obligation to the County and the County's exclusive
remedy with respect to any claim of infringement.

13082-EXHIBIT B-1
4.4 Indemnification Procedures. CG1's indemnification obligations are subject to the County
promptly notifying CGI in writing of the claim or action, providing CGI a copy of all
materials in the County's possession or control pertaining to the claim or action,
cooperating with CGI in defending or settling the claim or action, and allowing the CGI
to control the defense and settlement of the claim or action, including the selection of
attorneys. CGI will promptly assume the defense of the claim or action at its own
expense, and will pay all costs associated with the defense, including reasonable legal
fees and expenses, and the amount of any settlement reached or final judgment awarded
against the indemnified party. The County may observe the proceeding and confer with
the CGI at its own expense, and will have the right to approve any settlement agreement
purporting to bind the County; such approval will not be unreasonably withheld
4.5 Exclusions. CGI is not responsible for any claimed breaches of the foregoing warranties
caused by: (i) modifications made to the Work Product or Hosting Services by anyone
other than CGI and its subcontractors working at CG1's direction ; (ii) the combination,
operation or use of the item with other items CGI did not supply; (iii) the County's
failure to use any new or corrected versions of the item made available by CG1; (iv) the
County's misuse of the Service; or, (v) CGI's adherence to the County's specifications or
instructions.
4.6 Third-Party Products. To the extent CGI has the legal right to do so, CG1 agrees to
assign or pass through to County or otherwise make available for the benefit of County,
any manufacturer's or supplier's warranty applicable to any third-party software,
hardware or equipment provided by CGI under a Statement of Work. CGI does not itself
give or make any warranty of any kind with respect to third-party software, hardware or
equipment.
4.7 Disclaimer. THE WARRANTIES CONTAINED IN THIS EXHIBIT ARE IN LIEU OF
ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE.
5.0 LIMITATION OF LIABILITY AND REMEDIES
5.1 Liability Limits. Each party's cumulative liability for damages for all claim(s) arising
out of or relating in any way to any of the Services (including without limitation, for
breach of contract, breach of warranty, for its indemnification obligations, negligence or
other tort claim) shall not exceed, in the aggregate:
5.1.1 With respect to the Hosting Services or Maintenance Services, twelve (12) times
the average monthly payment made to CGI under the Exhibit that is applicable to
the Hosting Services or the Exhibit applicable to Maintenance Services.
5.1.2 With respect to Services provided on a non-recurring basis (e.g. implementation,
start-up or transition assistance), the amounts paid under the applicable Exhibit
for such Services.
5.1.3 With respect to Software, the license fees paid for the Software under Exhibit B-
4.
In addition, in no event will either party's aggregate liability for all claims arising under
or relating to the Contract exceed the total amount paid or owed (invoiced but not paid)
to CGI by the County under the Contract.

13082-EXHIBIT B-1
5.2 No Liability for Certain Damages. In no event shall either party be liable to the other,
whether liability arises in contract, tort or otherwise, for any consequential, incidental,
indirect, special, exemplary, multiple or punitive damages, regardless of whether it has
been advised of the possibility of such damages.
5.3 Acknowledgment. The limitations of liability set forth in this Section 6 will survive
notwithstanding the failure of any exclusive remedy under the Contract.
5.4 Exclusions from Limitations. The foregoing limitations do not apply to CG1's
indemnification obligation under Section 5.3, the County's obligations to make payments
to CGI under the Contract, County's breach of any license granted under the Contract, or
as otherwise expressly provided in the Contract.
5.5 Savings Clause. The parties agree that the foregoing limitations will not be read so as to
limit any liability to an extent that would not be permitted under applicable law.
6.0 INFORMAL DISPUTE RESOLUTION
At the written request of either party, the parties will attempt to resolve any dispute arising under
or relating to the Contract through the informal means described in MC1-906 of the Maricopa
County Procurement Code.
7.0 GENERAL
7.1 Export Control, Both CGI and the County agree to comply fully with all relevant export
laws and regulations of the United States to ensure that no information or technical data
provided pursuant to the Contract is exported or re-exported directly or indirectly in
violation of law.
7.2 Third Party Beneficiaries. There are no intended third party beneficiaries of any
provision of the Contract.
7.3 UCITA. Notwithstanding anything to the contrary, the parties expressly agree that the
provisions of the Uniform Computer Information Transactions Act (UCITA) as enacted
under the statute of any state, or as may be amended or modified, applicable as of the
effective date of the Contract or thereafter, shall not apply to this Contract.
7.4 Expiration or Termination Transition Services. In connection with termination or
expiration of the Contract, the County may request COT assistance in migrating the
County's processing being performed by CGI under the Contract to the control of the
County. Provided the County is current in its payment to CGI under the Contract, CGI
will perform reasonable transition services under a change order or amendment to the
Contract for a period of up to six (6) months on a time and materials basis at COI's then
current professional services rates. During the transition period, CGI will provide the
County a copy of the County's data in an agreed format, as required for the transition.
CGI may provide additional transition services as mutually agreed between the parties.
At the end of the transition period, the County will return to CGI any CGI Materials in
the County's possession or control and cease all access to the CG1 System.
7.5 Assignment. The County may not assign or otherwise transfer its rights or obligations
related to the CGI System without the prior written consent of CGI, which consent will
not be unreasonably withheld.
7.6 Non-solicitation. During the term of the Contract and for twelve (12) months after its
expiration or termination, neither party will, either directly or indirectly, solicit for

13082-EXHIBIT B-1
employment or employ (except as permitted below) by itself (or any of its Affiliates) any
employee of the other party (or any of its Affiliates) who was involved in the
performance of the party's obligations under the Contract, unless the hiring party obtains
the written consent of the other party. The actual damages attributable to a breach of the
provisions of this Section would be difficult to determine and prove. Accordingly, the
parties agree that if either party breaches this Section the breaching party will promptly
pay the non-breaching party liquidated damages in an amount equal to the employee's
annual salary (including bonuses and incentive compensation) prior to the breach, such
sum being a reasonable measure of the damages reasonably anticipated by the parties.
The foregoing provision will not prohibit a general solicitation of employment in the
ordinary course of business or prevent either party from employing any employee who
contacts such party as a result of such a general solicitation or at his or her own initiative
without any direct or indirect solicitation by or encouragement from such party.
PART TWO: HOSTING SERVICES
These terms apply to the extent of any hosting or managed Services to be provided by CGI under an
Exhibit.
8.0 PERFORMANCE OF THE HOSTING SERVICES
8.1 General. CG1 will perform and provide to the County the Hosting Services described in
Exhibit B-2. Unless and except to the extent the Contract expressly provides otherwise,
the County shall use the Hosting Services only for the County's internal business
purposes, not for resale or otherwise for the benefit of third parties.
8.2 Service Levels. CG1 will perform the Hosting Services in a manner that meets or
exceeds any applicable Service Levels set forth in Exhibit B-3 of the Contract. For any
failure of the Hosting Services to meet or exceed the applicable Service Levels, the
County's remedy shall be as specified in Exhibit B-3. Such remedy will be the County's
sole and exclusive remedy and CG1's sole and exclusive obligation and liability in
respect of such failure.
8.3 Use of Third Party Suppliers. The County acknowledges that CGI may obtain products
and services used in providing the Hosting Services from, and otherwise delegate
obligations hereunder to, it Affiliates or other third party suppliers. Unless specifically
indicated otherwise, CGI shall nevertheless be responsible to the County for performance
of the Hosting Services based on the use of such Affiliates or third party suppliers.
8.4 Right to Make Changes to the CGI System. CGI may make any changes in the CG1
System used in performing the Hosting Services that CGI determines in its sole
discretion to be necessary or appropriate, including changes in facilities, computer
hardware, systems and/or applications software, programming languages, data
communications, and location of systems and service equipment. CGI will provide prior
notice (or, in the event of an emergency, prompt notice after the occurrence of such
emergency) if CGI believes such changes have a reasonable likelihood of adversely
affecting the County's use of the CGI System.
9.0 CERTAIN CUSTOMER RESPONSIBILITIES
9.1 County Data and Information. Whenever CGI's performance of the Hosting Services is
dependent upon the County's furnishing CGI with legacy or third party applications,

13082-EXHIBIT B-1
including, without limitation, connectivity, data, documents, information, materials or
approvals, the County shall furnish such items in a timely fashion in a reasonable format
specified by CGI, or such other format as mutually agreed by the parties in writing. The
County is responsible for ensuring that all physical media that the County furnishes to
CGI for processing meet the specifications of the manufacturer of the equipment with
which such media are to operate and any other specifications that CGI may reasonably
establish. The County is also responsible for the adequacy and accuracy of all data and
information that it furnishes to CGI and the results obtained therefrom. The County
warrants that any the County-provided specifications or requirements around which
Hosting Services are configured will be in compliance with applicable federal, state and
local laws and regulations. The County warrants that it has acquired all necessary
licenses and consents from third party vendors for those County-provided items required
for CGI to perform Hosting Services hereunder.
9.2 Access to and Use of CGI System. The County agrees that use of the portion of the CUT
System to which access is given for purpose of CGI providing Hosting Services shall be
(i) in compliance with the terms of this Exhibit and all applicable federal, state and local
laws and regulations and communications common carrier tariffs, (ii) solely for the
County's own internal use in receiving the Hosting Services, unless otherwise permitted
under the Contract, and (iii) for proper business purposes. The County will not disclose,
download, decompile or re-engineer any Managed Application provided by CGI or its
licensors and used in the performance of Hosting Services. As part of CGI's security
measures, it may assign to the County one or more user or identification codes and
associated passwords that will enable the County and its users to access the CGI System.
The County agrees to maintain the security of its user or identification codes and
associated passwords and agrees to be responsible for their proper use by its employees
and, where permitted, its contractors. The County agrees to comply with any rules of
operation and security procedures established by CGI for access to and use of the CGI
System. The County agrees that neither it nor its employees or agents will attempt to
gain or allow access to any data, files or programs of CGI to which they are not entitled
under the Contract, and that if such access is obtained the County will immediately
report such access to CGI, cease all unauthorized access, return all CGI, third party, or
CG1 customer information obtained as a result of such unauthorized access, and
safeguard any CG[, third party, or CG I customer information obtained as a result of
unauthorized access to CG1 Confidential Information. The County will be responsible for
the actions of its employees, agents, and permitted contractors in connection with their
access to and use or misuse of the CGI System.
9.3 Content. The County warrants that (i) the Content does not and will not contain
unlawful, discriminatory, libelous, harmful, obscene or otherwise objectionable material
of any kind and does not and will not violate any right of privacy or publicity, (ii) the
Content transmitted during the term of the Contract and the use of the CGI System
pursuant to this Exhibit will not encourage conduct that could constitute a criminal
offense, give rise to civil liability or otherwise violate any applicable local, state,
national or international laws, codes, ordinances or regulations, and (iii) the County shall
not attempt to gain unauthorized access to other computer systems, any
application/service for which the County has not paid fees to use, or data and
information belonging to others that is also hosted on the CGI System. The County
warrants that it will not propagate computer worms, disabling codes or viruses or use the
CGI System to make unauthorized entry into any other computer or machine.

13082-EXHIBIT B-1
9.4 Compliance with Laws. Except as expressly provided in the Contract, the County shall
be solely responsible for ensuring that its use of the Hosting Services will comply with
all laws, rules, and regulations and decisions imposed by any jurisdiction in which the
Hosting Services are received or used.
10.0 PROPRIETARY RIGHTS FOR HOSTING
10.1 Ownership. CGI (or its licensors or suppliers, as the case may be) will retain ownership
of the CGI Materials. Except as permitted by the Contract or as CGI may agree in
writing in advance, the County will not copy or use any CGI Materials in any way that is
not authorized by the Contract. Any permitted copies of the CGI Materials (including
derivative works to the extent they incorporate or are based on any CGI Materials) made
by or for the County are and will remain the property of CG1 (or its licensors). The
County will reproduce and include on any permitted copies of the CGI Materials all
copyright or other proprietary rights notices or legends that appear on or are otherwise
included in the CGI Materials. CGI Materials are considered the Confidential
information of CGI.
10.2 Grant of Limited License to CG1. The County hereby grants to CGI during the term of
the Contract a nonexclusive, nontransferable, limited right and license to access, display,
reproduce, process and otherwise use, in compliance with the Contract and for the sole
purpose of performing the Hosting Services for the County, the County-provided
Managed Application(s), and any Content furnished to CGI by or on behalf of the
County. As between CGI and the County, the County will retain ownership of all such
Content.
11.0 LIMITED WARRANTY
11.1 Service Level Warranty. CG1 warrants that the Hosting Services will be performed in a
manner that meets or exceeds the applicable Service Levels set forth in Exhibit B-3. If
CGI fails to meet the defined Service Levels, CGI's sole obligation and the County's
exclusive remedy shall be as set forth in Exhibit B-3.
11.2 Disclaimer. COT DOES NOT GUARANTEE THE ACCURACY OF ANY ADVICE,
REPORT, DATA OR OTHER PRODUCT DELIVERED TO THE COUNTY THAT IS
PRODUCED WITH OR FROM DATA OR SOFTWARE PROVIDED BY THE
COUNTY.
CGI DOES NOT WARRANT THAT THE SOFTWARE, HOSTING SERVICES OR
ACCESS TO THE CGI SYSTEM WILL BE UNINTERRUPTED OR THAT THE
RESULTS OF THE HOSTING SERVICES WILL BE ERROR-FREE.
12.0 REMEDIES
12.1 Errors in Processed Data. The County shall be solely responsible for reviewing the
accuracy of any processing output provided by CGI prior to making use of such output,
including responsibility for output reports. If any such results are inaccurate due to the
fault of CG1, CG1's sole obligation shall be to reprocess the affected data at no additional
charge to the County. If any such results are inaccurate due to the fault of the County,
the County shall provide corrected data and CGI shall be paid by the County on a time
and materials basis to reprocess the corrected data.

13082-EXHIBIT B-1
12.2 Loss of Data. If the County data is lost, corrupted or destroyed while in the possession
or control of CG1 due to CGI's fault or negligence, CGI will use commercially
reasonable efforts to reconstruct such data at CGI's expense provided any files, data,
programs or other information that may be necessary to accomplish such reconstruction
but which are not in CGI's possession or control are promptly furnished to CG1 by the
County upon request.

13082 Exhibit B-2
Managed Advantage Plan Services
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND
SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED OR ADDED AND PRICING
ADJUSTED).
Statement of Work Contents
I. OVERVIEW 2
II. DEFINITIONS AND TERMINOLOGY 3
EXHIBIT B-2-A: CGI ADVANTAGE STANDARD MAINTENANCE ISSUE SEVERITY DEFINITIONS 8
III. GENERAL MANAGED SERVICES PROVISIONS 12
IV. SCOPE OF SERVICES 14
V. TRANSITION APPROACH AND POST-TRANSITION SERVICES 22
VI. SERVICE LEVEL AGREEMENTS 37
EXHIBIT B-2-B: CGI PERFORMANCE FRAMEWORK FOR SERVICE LEVEL AGREEMENT 37
ATTACHMENT 1: CGI ADVANTAGE SIZING — USAGE LEVELS 43
ATTACHMENT 2: CGI ADVANTAGE CUSTOMIZATION SPECIFICATIONS 44

13082 Exhibit B-2
Managed Advantage Plan Services
Overview
This Exhibit B-2 (referred to as "Statement of Work" or "SOW") establishes the basis and framework for
hosting and operating Maricopa County's CG1 Advantage® Version 3 application
environment/infrastructure in CGI's secure hosting facility in Phoenix, Arizona, completing post-transition
activities, and providing defined minimum levels of support as part of the Managed Services. Capitalized
terms in this Statement of Work shall have the meanings ascribed to them in the Agreement unless
otherwise expressly specified herein.
This Statement of Work is specific to Managed Services in support of the County's use of the Advantage
Software and specifies activities that fall under the following three key areas:
A. General Terms for Managed Services
Provides the County with certain general terms and scope of Services that will establish the basis and
framework for hosting and operating the County's System, defined in §IV.B.2, at the Phoenix Data
Center.
B. Transition and Post-Transition Upgrades
Provides the County with the overview and high level tasks associated with transitioning to CGI's
Advantage Version 3 application environment/infrastructure and Managed Advantage operations. The
Transition, described in §V, is the first activity to be undertaken through this Statement of Work.
Additionally, this section outlines the approach and scope of future upgrades to the System after the
initial Transition has been completed.
C. Service Level Agreement
Sets forth the Service Level Agreement ("SLA") between the County and CGI defining the framework
for measuring service delivery by CGI in hosting and operating the System at the Phoenix Data Center,
post-Transition. The SLA specifies the context and definition of key measures and thresholds mutually
agreed upon as an objective means to track Managed Advantage service delivery for the System. In
addition, recourse and consequences of not delivering a minimum level of service, as well as
exceeding an expected level of service delivery are specified.

13082 Exhibit B-2
Managed Advantage Plan Services
Definitions and Terminology
A. Description
Business terms that define CGI's key assumptions are set forth in this section. They shall be construed
and interpreted as follows:
General Business Term Definitions
"Advantage Software" means CGI Advantage® 3.10 Software modules, Contractor's current
enterprise resource planning software.
2. "Bundled Software Products" means third party software products which are not owned by
Contractor, but are required for use with the System and provided by Contractor under Exhibit
B-4, Proprietary Software Li.ense Agreement. together with any documentation and other
related materials for the Bundled Software Products. acts.
3. "Change Order" is a written change to the Statement of Work, which is prepared and signed
by authorized representatives of both Parties.
4. "Discretionary Support" means an ongoing pool of available hours for additional CGI
consulting services, as more fully described in this Statement of Work.
5. "Managed Services" means managed information services, including but not limited to
hosting, operations, maintenance and support of the Advantage Software by Contractor at
Contractor-provided data center facilities, as more fully described in this Statement of Work.
6. "Party" refers to the County or Contractor and "Parties" means both the County and
Contractor.
7. "Project Plan" defines the project go , ernance, objectives, scope, timeline and roles and
responsibilities for project implementation.
8. "Statement of Work Term" means the total duration of this Managed Services Statement of
Work from the Effective Date of the Contract and ending on the tenth (10' h) anniversary of the
contract.
9. "Subcontractor" is any third-party eitgatecl by Contractor to aid in performance of
Contractor's obligations.
B. Managed Advantage Definitions
Definitions of age( 4tivt age at SEA Terms t Ter o ogir
"Attachments" to this Statement of Work means the following which are attached hereto and
incorporated by reference herein: Attachment 1 (Advantage Software Sizing — Usage Levels);
and, Attachment 2 (Customization Specifications).

13082 Exhibit B-2
Managed Advantage Plan Services
Definitions of Key Managed Advantage and SLA Terms and Terminology'
2 "Availability Percentage" is the percentage of scheduled time the respective production
application is available to users during the defined Hours of Availability. Availability
Percentage is calculated by taking the planned minutes available per month (PMA),
subtracting minutes not available per month (MD), and dividing that result by planned minutes
available. Equation: (PMA — MD) / PMA.
As an example, if the planned Hours of Availability are every week day, Monday through
Friday from 6:30 a.m. to 7:00 p.m. and there were three (3) hours of unavailability during the
month of January, then the mathematical representation would be:
PMA = 22.5 days/months x 12.5 hours/day x 60 minutes/hour = 16875 minutes/month
MD = 3 hours/months x 60 minutes/hour = 180 minutes/month
Availability Percentage = (PMA-MD)/PMA = (16875 — 180) , 16875 = 98.93%
Scheduled outages, as further described in §VI.A.5, are documented, approved, planned and
scheduled in advance and are not considered MD for purposes of this calculation. This
includes all Scheduled Maintenance Periods.
Unavailability caused by components for which the County is responsible (including, but not
limited to §IV.C, certain components in §IV.A and within the County's Point of Demarcation)
will be considered scheduled outages as well for this calculation.
MD includes unscheduled outages associated with a Critical Issue, defined in §II.B.19,
reported by either Party. This excludes Issues not attributable to CGI or its Subcontractors
and/or causes for which ( CiT or its Subcontractors are not independently accountable.
"At Risk Amount" — A percentage of 1/3rd of ti [e quarterly fees (i.e. the monthly allocation
of quarterly fees paid by the County to CGI) against which one or more Service Penalties is
applied if CGI fails to achieve the specified Minimum Service Level for a specific Service
Metric within the respective Measurement Interval.
"Batch Processing Time" is the target maximum amount of time, as jointly agreed upon by
the Parties during the Transition based on historical peak processing time and peak processing
times during Transition testing, required to complete System batch processing after receipt of
all files and requisite inputs from the County such that the System can ultimately be in a
position to resume CGI Advantage General Application Availability. For purposes of
calculating Batch Processing Time, the System executes defined batch jobs including backups
or other scheduled System maintenance activities. The associated Service Metric is calculated
as a percentage by taking the total number of target minutes in the batch window per month
(TNM), subtracting the number of minutes delayed or late / exceeded (BMD) and dividing by
TNM.
Equation: (TNM — BMD) / TNM. TNM = number of processing days per month * x hrs.
/batch * 60 minutes/hr.

13082 Exhibit B-2
Managed Advantage Plan Services
Definitions of Key Managed Advantage and SLA Terms and Terminology'
For example if batch was scheduled to run from lOpm to Sam daily and ran over 3 hours in
total during the month of January, then the mathematical representation would be:
TNM = 31 days/month x 7 hours/day x 60 minutes/hour = 13020 minutes/month
BMD =3 hours/months x 60 minutes/hour = 180 minutes/month
Batch Processing = (TNM — BVID TNM = (13020 — 180) /13020 = 98.16%
Notwithstanding the above calculation, CGI will always have at least two hours of cumulative
delay per month before any Service Metric/Service Level .for which this calculation is used is
considered not achieved such that remediation of at least one batch Issue per month is feasible
on a practical basis.
5. ".CGI Advantage Batch Execution Time is the time required for the CGI Advantage
Financial Management application to process and successfully complete batch processing
normally according- to the batch processing schedule included in the Processing Schedule, as
described in §V.D. successful job metrics and as measured by the Batch Processing Time
metric defined in §11.8.4.
"CGI Advantage General Application Availability" means the Advantage Software listed
below Which is considered available when a properly configured computer is capable of
successfully executing a standard online screen transaction within all .major subsystems (e.g.
CGI Advantage Financial Management) from either an operator console or end user
workstation. An online transaction can be a change. add, or delete: can be a request to view a
record, or a simple query run from a workstation displayed screen. CGI monitoring,
measurement, and responsibility will be within the Point of Demarcation.
CGI Advantage General Application Availability definition applies to the following System
components as described in §1V.A.1:
• CGI Advantage Financial Management, including Grants Lifecycle Management,
Inventory Management, and Asset \lanagement
• CGI Advantage Procurement Professional, excluding Vendor Self Service (calculated
separately as described in §II.8.7 below) and external data aggregation services
integrated with Advantage Procurement (i.e. Liaison Punch Out)
• CGI Advantage Performance Budgeting Formulation, including Salary and Benefits
Forecasting
7 "CGI Advantage Vendor Self Service Application Availability" is calculated per the above
definition, but applied to those specified components of the System given -that they may have
differing flours of Availability from other components. If user behavior in the use of CGI
Advantage Vendor Self Service exceeds the practical limits Of this application as documented
in Attachment l, and/or the underlying environment/infrastructure, resulting Issues or
unavailability of the CGI Advantage Vendor Self Service Application will not he counted

13082 Exhibit B-2
Managed Advantage Plan Services
Definitions of Key Managed Advantage and SLI Tern's and Terminology'
toward CGI's performance against this Service Metric.
8. "CGI infoAdvantage and E1360 Application Availability" is calculated per the above
definition, but applied to this component of the System given that it may have differing Hours
of Availability. If user behavior in the use of infoAdvantage or E1360 exceeds the practical
limits of this application and/or the underlying environment/infrastructure, resulting Issues or
unavailability of the CGI infoAdvantage or E1360 Applications (including external E1360 data
sources not under CG1's sole purview and management) will not be counted toward CGI's
performance against this Service Metric.
9, "Customization" for purposes of this Statement of Work is a modification, alteration,
enhancement, or addition to the System specifications, functions, code, and/or interfaces that
has been done specifically for the County's implementation. Only Customizations to the
System that are specifically documented in Attachment 2 are supported as part of this
Statement of Work.
10, "Disaster Recovery" means the activities related to providing continuation of System
availability after an unexpected event that CGI, in consultation with the County, reasonably
believes will result in prolonged downtime of the System, as defined in §11.B.36 below,
sufficient to warrant the lead time and effort by the Parties to both migrate from the Phoenix
Data Center to an alternate processing location, as well as back to the Phoenix Data Center or
replacement primary processing site. In undertaking Disaster Recovery activities, particular
consideration is given to the defined Disaster Recovery Targets in §VI.
"Earnback Credits" are offsets to Service Credits that have been accrued by COI as a result
of surpassing the Exceeded Service Level. Earnback Credits are more fully described in
§VI.C.2.
12. "Fiscal Year" is the County's fiscal year, which begins on July I' of each calendar year and
ends on June 30th of the following calendar year.
13. "Fix Pack" is a set of software updates made to the baseline product as part of the Advantage
Software roadmap. Fix Packs are made available on a pre-defined schedule determined by
CG1. Fix Packs that will be implemented require code merging activities to retrofit all covered
modifications into the new release of the baseline product. Fix Packs will sometimes involve
an implementation effort for production; such effort is outside the scope of Managed
Advantage and if requested by the County would be subject to a Change Order, a Statement of
Work amendment or through the use of Discretionary Support hours.
14, "Hot Fix" is the application of a Patch intended to update the existing customer software in a
quick turnaround to support Critical Issues and Serious Issues as defined in §II.B.19 below.
Delivery of Hot Fixes is typically undertaken on an as-needed basis given the criticality of the
required Issue correction.
15. "Hours of Availability" for online access to CGI Advantage General Applications as defined
in §II.B.6, and COT infoAdvantage and E1360 as defined in §II.B.8 and the associated
environment are from 6:00am - 7:00pm Arizona Time, Monday through Friday, excluding
Scheduled Maintenance as well as CGI and the County holidays (except as noted below).

13082 Exhibit B-2
Managed Advantage Plan Services
Definitions of Key Managed Advantage and SLA Terms and Terminology'
CGI Advantage Self-Service applications (VSS/ESS/MSS) Hours of Availability are 24
hours/day, 7 days/week, excluding Scheduled Maintenance and backup processing. Backup
processing typically runs 1-2 hours per night. Scheduled maintenance is one weekend per
month with VSS being down for most of the period; however, it will generally be back online
before the other Advantage Software applications.
CGI and the County's holidays are New Year's Day, Martin Luther King Junior Day,
President's Day. Memorial Day, Independence Day, Labor Day, Veteran's Day, Thanksgiving
Day and the Friday immediately following, and Christmas Day. Support for batch processing
and application availability can occasionally be provided on these holidays, if requested thirty
(30) days in advance and provided such requests are not routine.
Provided other requisite activities do not conflict (e.g. batch processing, maintenance), the
System will generally remain online and accessible outside of the Hours of Availability, but
such additional availability or any Issues arising during such time will not be counted as part
of Hours of Availability or in any dependent Service Metrics. Similarly, support for
monitored weekend and off-hours availability can occasionally be provided by CGI if
requested live (5) busines,', days in advance, but will not be counted toward Hours of
Avai labil it) or any dependent Service Metric.
16. "Infrastructure Availability" is considered when the telecommunications, network, data
center, and hardware on which the System operates under CGI's control in the provision and
operation of the County production environments are reported as up and available by the
System monitoring tools employed by CGI.
17. "Issue" is a deviation of the System to function per its licensed documentation or if included
within Attachment 2, a Customization to function per the documented Specifications for that
Customization.
An Issue can be associated with the underlying environment/infrastructure under CGI's
independent management if the environment metrics used to size the System set forth in
Attachment 1 have not been exceeded and the Issue is materially impacting the normal use of
the System in a manner consistent with the Issue Severity definitions.
In addition, an Issue can be associated with the performance behavior of the System if
performance is impacted in a manner that warrants initial classification as a Critical Issues or
Serious Issue as defined in §H.B.19 (pending additional research) because it is materially
impacting the normal use of the System in a manner consistent with the Issue Severity
definitions.
Issues will be initially classified by the party identifying the Issue in accordance with the Issue
Severity definitions specified herein. Resolution of the Issue will proceed in accordance with
such classification until one or both oldie parties revise the Issue Severity level for the Issue
as part of a coordinated effort
18. "Issue Priority" is the priority of any Issue, as assigned by the County. This priority indicates,
within an Issue Severity level, the relative order in which Issues will be handled by CG1.
Priority can be defined as "Urgent", "High", "Normal", and "Low".
19. "Issue Severity" is the severity assigned to all Issues, as ultimately managed by CGI with

13082 Exhibit B-2
Managed Advantage Plan Services
Definitions otos waged Advantage and SLA Terms and Terminology'
input from the County. After initial assignment by the reporting Party, this assignment will be
reviewed as a coordinated effort between the Parties based on the definitions of the severities,
possible workarounds, and the impact on the functionality. The following Issue Severity
definitions in Exhibit B-2-A, which correspond to the CGI Advantage Standard Maintenance
Agreement, apply.
Exhibit B-2-A: CG1 Advantage Standard Maintenance Issue Severity Definitions
Severity Definition
1 — A problem with the System causing critical impact to the County's business
Critical Issue operations, and no workaround is immediately available. Use of the System cannot
continue.
Resolution efforts begin upon notification and continue until resolved. If resolution
requires a software correction, it is delivered as soon as resolved.
Example: I lie System is Down and Inoperable
2 — A problem causing significant impact to the County's business operations, and any
Serious Issue workaround is unacceptable on a long term basis. Essential functions of the System
are affected such that there is a significant impact to the County's business
operations.
Work begins after Severity 1 Issues are resolved and in consideration of Issue
Priority for any other pending Issues. If resolution requires a software correction, it
is made available as soon as resolved.
Example: Major Operations of the System are either Down or Inoperable while
some can continue
3 — A problem that impairs some functionality, but a practical workaround exists such
Moderate that there is not a material impact to the County's business operations.
Issue
If resolution requires a software correction, this is fixed in the next Fix Pack release
if reported prior to release cut-off date.
Example: One or more business processes are impacted, either in timeliness or
availability, but ilk System is operational
4 — A problem that does not affect any production functions of the software and may be
Minor Issue cosmetic in nature. A software defect exists but does not impede any functionality.
These Issues are generally fixed in the next Minor Release or Major Release if
reported prior to release cut-off date.
Example: Therc are some issues with the normal processing, but the System is
opci mtional
"Live Date" means the date the System goes into production and is in use by the County as its
primary processing system for the respective function(s) it is designed to support.
21, "Major Release" occurs infrequently and contains significant functional enhancements that

13082 Exhibit B-2
Managed Advantage Plan Services
Definitions of Key 111 aged Advantage and SLA Terms and Terminology'
span the application modules and are generally accompanied by major changes in technical
architecture.
An example of a Major Release of the Advantage Software would be "CGI Advantage 3"
22. "Managed Advantage" means Managed Services provided by CGI in support of the System,
as such Services are described in this Statement of Work.
23. "Measurement Interval" is the period of time over which a given Service Metric is measured
for purposes of determining performance. Measurement Interval is monthly unless stated
otherwise.
24. "Minimum Service Level" is the level for a given Service Metric below which is considered
a failure in CGI performance during the Measurement Interval, which will result in Service
Credits awarded to the County by CGI.
25. "Minor Release" occurs typically on an eighteen (18) to twenty four (24) month cycle and
contains both functional and technical enhancements to the software. A Minor Release
enhances the application's functional and technical capabilities and responds to legislative
requirements without introducing a wholesale change in the application.
In addition to functional and technical enhancements, a Minor Release may also contain
corrections for software incidents reported from the prior release.
An example of a Minor Release of the Advantage Software would be "CGI Advantage 3.11"
26. "Patch" is a correction to the Advantage Software application specific to one (or a very small
set of tightly related) Issue(s), independent of Issue Severity.
"Patch Set" is a select, client specific group of Patches intended to update the existing
customer Advantage Software in a longer turnaround time than what is described for the single
Hot Fix above as it tends to principally address Moderate Issues, as defined in §II.B.19.
Generally, delivery of a Patch Set is a scheduled event containing a pre-defined set of Hot
Fixes. A set typically contains between ten (10) and twenty (20) resolutions, but may contain
only one resolution (for example, for resolutions of Critical Issues).
Patch Sets can typically be tested in a client test environment and moved to production without
any additional implementation efforts (e.g. upgrading the underlying software or full
regression testing)
28. "Phoenix Data Center" or "PDC" means CGI's data center racilit used as the primary
hosting location for the System located in Phoenix, Arizona.
"Point of Demarcation" is the point(s) at the Phoenix Data Center in which the System is
operating where all related infrastructure is solely under CGI's purview and management. For
the County, this is the border router(s) where network traffic transitions from
telecommunications circuits under CGI's sole purview to the County's facility/network. The
County is responsible for the integrity and availability of the County's facility and dependent

13082 Exhibit B-2
Managed Advantage Plan Services
Definitions of Kel , Managed Advantage and SLA Terms and Terminology'
services (e.g. power) for the operation of this border router(s).
30. "Remote Hands Support" means providing physical restarts or manipulation of a technology
device at the direction of a party that is not physically present.
31. "Scheduled Maintenance Period" is any time when planned maintenance is to be performed
on the System. The standard Scheduled Maintenance Period is Friday from 7:00pm Eastern
Time to Sunday at 7:00pm Eastern Time the second (2" d) weekend of each month, though
generally not lasting the entire period. Scheduled maintenance takes precedence over County
requests for special weekend processing.
32. "Service Credits" are credits by CG1 of a portion of the AI Risk Amount paid b) the County
to CGI as a result of a failure by CG1 to achieve the specified Minimum Service Level for a
specific Service Metric.
The Service Credit is equal to the At Risk Amount multiplied by the Service Penalty for the
respective Service Metric. This amount is accrued and reconciled on an annual basis net of any
Earnback Credits, for use over the subsequent 12 months by the County against CGI
consulting services or as applied to the next payment for the System.
33. "Service Level" is a target for a specific Service Metric against which CGI's performance is
to be measured and reported. "Service Levels" are the collective set of Service Levels across
the respective Service Metric, specifically including the Minimum Service Level and the
Exceeded Service Level
34. "Service Metrics" are the specific units of measure mapping to the County's business
objectives for which Service Levels are established.
35. "Service Penalty" is the amount for each Service Metric that is factored against the At Risk
Amount for purposes of calculating any Service Credits relative to the applicable Service
Level(s) during a given Measurement Interval.
36, "System" is the baseline Advantage Software production application and modules, Bundled
Software Products, and Customizations, as collectively defined in §IV.A.2 of this Statement
of Work.
37. "Total Planned Uptime" refers to the total minutes in the month of Infrastructure Availability
excluding all planned maintenance activities and other planned outages. Infrastructure
Availability is measured 24/7/365 based on the number of minutes in the calendar month being
measured.
"Total Uptime" refers to the total minutes in the month of actual Infrastructure Availability.
Total Uptime does not include unscheduled outages (or downtime), which are determined by
incidents reported by either Party resulting in an Issue affecting Infrastructure Availability.
Availability will be based solely on performance of CGI's responsibilities. Issues not
attributable to CGI and/or causes for which CGI is not independently accountable as well as
unavailability requested or induced by the County or caused by components for which the

13082 Exhibit B-2
Managed Advantage Plan Services
Definitions of Key Managed Advantage and SLA Terms and Terminology'
County is responsible 1 be considered planned outages and will not be deducted from Total
Uptime.
39. "Transition" refers to the activities defined in §V.
40. "Uptime Percentage" refer to the percentage of minutes that the infrastructure is fully
operational or is unavailable due to Scheduled Maintenance Periods. In general, uptime
computations are based on the duration of unscheduled outages (or downtime) for the System
being measured against planned uptime.
The calculation is:
Uptime Percentage = (Total liptime Total Planned 1 ptiiite ).

13082 Exhibit B-2
Managed Advantage Plan Services
General Managed Services Provisions
A. Records and Audit
Notwithstanding any other term of the Agreement, the following terms apply to audits required by the
County with regards to Managed Services.
1. Records
The County and CGI each agree to keep clear and accurate records relating to their activities
under the Agreement and this Statement of Work for at least the immediately preceding two (2)
years from any point in time during the term of this Statement of Work.
2. Audit Regarding Invoiced Amounts and Service Levels
Upon thirty (30) days prior written request, the County will be allowed to conduct an audit
reasonably necessary to verify: (i) amounts invoiced to the County for the Managed Services, and
(ii) CGI's reports on Service Levels. CGI will provide reasonable access to relevant CG1
personnel, books and records necessary to conduct the foregoing audit, to (i) the County's internal
auditor, and (ii) a nationally recognized audit firm appointed by the County. Such audits will be
conducted at the County's expense and may be conducted periodically during the term of this
Statement of Work, but not more than once per Contract Year, except for more frequent audits
reasonably necessary to confirm that deficiencies identified in the preceding audit have been
effectively addressed. Such additional audits will be subject to terms and conditions to be agreed
upon by the Parties.
3. Audits Concerning Contractors Internal Controls
Each year, at its sole cost and expense, CGI will cause its external auditors to (i) perform a SSAE
NO. 16 audit (or succeeding equivalent) regarding internal controls that CGI applies, on a
common basis, to the primary hosting facility (the Phoenix Data Center) and associated activities
provided to the County (the "Internal Controls Audit"), and (ii) produce an audit report in
connection therewith (the "Internal Controls Audit Report"). CGI will notify the County within
thirty (30) days of the availability of the Internal Controls Audit (the report is to be available in
approximately August of each year). Due to the confidential nature of the Internal Controls Audit,
CGI and the County will mutually agree to a time and location for the County to review the
Internals Control Audit. In the event that the County reasonably requests audit and reporting that
are not covered by the Internal Controls Audit or that are on a different audit period other than the
standard CGI audit period, such additional audit and reporting will be at the County's cost and
expense and will be addressed through the Change Order procedures set forth in the Operational
Procedures Deliverable described under §V.D.
4. Confidentiality of Audits
Where applicable for the purpose of §III.A, the County's external auditor shall provide CG1 with
the County's written authorization to act as its external auditor and will then be deemed to be the
County's representative. No proposed auditor will be a competitor of CGI. Any external auditor
retained by the County in connection with such audits will execute a non-disclosure agreement
reasonably acceptable to CGI. All audit reports contemplated by this §III.A and their content will
be deemed Contractor Confidential Information and will be subject to the confidentiality
provisions contained in the Agreement.

13082 Exhibit B-2
Managed Advantage Plan Services
5. Cure of Deficiency
In the event that an audit contemplated by this §III.A identifies a deficiency that causes or may
cause a breach of CGI's obligations under this Statement of Work, CGI will (i) diligently pursue
resolution within a reasonable timeframe given the level of seriousness of the deficiency; and (ii)
confirm such cure to the County.
6. Security Policies
Access to the Phoenix Data Center by the County, or the County's external auditor, requires
advance notice and must be in accordance with all terms of this Statement of Work as well as
compliance with CGI's then-current security and confidentiality policies and procedures provided
to the County or the County's external auditor, which includes but is not limited to being
accompanied by CGI at all times.
B. Disengagement Services
In connection with termination or expiration of this Statement of Work, CGI, upon request by the
County, shall provide assistance to the County in migrating the System and the Managed Services
being performed by CGI hereunder to the control of the County or an alternate vendor designated by
the County. Provided the County is current in its payment to CGI under the Agreement and this
Statement of Work, CGI will perform reasonable disengagement Services under a separate
Amendment for a period of up to six (6) months on a time and materials basis at CGI's then current
professional services rates set forth in the Agreement. Disengagement Services will be detailed in the
separate Amendment and will include, but will not be limited to: the type of Services to be rendered,
estimated hours required for the performance by CG1, the County or the vendor designated by the
County to the service component in order to derive an agreed upon cost component for the Services,
and agreed upon Deliverables for the completion of each disengagement Service component identified
in the Statement of Work. During the disengagement period, CG1 will at no additional charge provide
the County with a copy of the County data in an electronic format, readily accessible by the County or
the vendor designated by the County as required for the disengagement of CGI's services hereunder
and the provision of similar services by the County or the County's designated vendor. CG1 will
provide additional disengagement Services as mutually agreed between the Parties and set forth in a
separate Amendment. At the end of the disengagement period, the County will return to CGI any
Contractor Confidential Information or CGI Materials in the County's possession or control and cease
all access to the CGI System. CGI will return to the County any County Confidential Information or
County materials in COI's possession.

13082 Exhibit B-2
Managed Advantage Plan Services
IV. Scope of Services
A. General Terms and Assumptions
This section defines the overall parameters and assumptions for the delivery of Managed Advantage to
the County. It highlights the key elements that are the basis for delivery of the Services on an ongoing
basis and the distribution of responsibilities between CGI and the County. These terms are based upon
CGI's standard service delivery model for Managed Advantage, defined in §11.B.22, information
provided by the County, and CGI's experience in implementing, hosting, and maintaining Advantage
Software for similar customers.
General Terms and Assumptions
Applications to be hosted and managed by CGI include:
a) CGI Advantage Financial Management, including:
0- CGI Advantage Grants Lifecycle Management
0- CGI Advantage In\ entory Management
0- CGI Advantage Asset Management
b) CGI Advantage Procurement Professional, including:
CGI Advantage Vendor Self-Service ("VSS")
CGI Advantage Performance Budgeting Formulation, including:
CGI Advantage Salary and Benefits Forecasting
d) CG1 infoAdvantage, including:
▪ CGI infoAdvantage Dashboard
e) CGI Enterprise Intelligence360 ("E1360")
2. For purposes of clarification, collectively, the applications defined in §IV.A.1 above, any
Bundled Software Product licensed from CGI in connection with these applications as
delineated in Exhibit B-3 (Proprietary Software License Agreement), and Customizations
defined in Attachment 2, if applicable, comprise the "System".
Term will begin with a CGI implementation of the System and Transition to the CGI
Advantage Version 3 hosted and managed environment/infrastructure.
4. Standard Maintenance: The County must remain on currently supported Advantage Software
releases and remain current with standard CG1 Advantage Software maintenance through this
Statement of Work Term to be eligible to receive Managed Advantage.
5 For purposes of clarification, fees for Software Standard Maintenance for CGI Advantage and
Bundled Software Products are not included in Managed Advantage.
CG1 will support and maintain the County's Customizations to the Advantage Software,
except for forms, reports, and interfaces, which will continue to be supported by the County.
Any Customizations to the Advantage Software that will be supported by CGI are listed in
Attachment 2 and will be documented via the Change Order process. The upgrade Project and
ongoing Managed Advantage delivery will accommodate these Customizations, but do not
assume merging or support of any new Customizations unless they offset Customizations that
are base-lined and deployed as a subsequent Minor Release upgrade during this Statement of

13082 Exhibit B-2
Managed Advantage Plan Services
Work Term. Offsetting customizations would need to be of equal or lesser complexity and
have required the same or less original development effort as those they are replacing and are
therefore excluded unless requested of CGI by the County through the use of Discretionary
Support. Otherwise support for any additional Customizations not explicitly included in
Attachment 2 will be the responsibility of the County.
Connectivity to CGI's Phoenix Data Center and Disaster Recovery site from the County's
WAN (or other end-user locations) will be provisioned and managed by the County.
CGI shall provide General Internet for access to the Advantage Software VSS application.
The estimate of bandwidth required is based on sizing information provided by the County in
Attachment 1.
All CGI Advantage Software application userid maintenance will be performed by the County
All hosting infrastructure userid maintenance will be performed exclusively by CGI. Unless
support is requested of CGI by the County through the use of Discretionary Support services,
the following limits apply:
User Profile Updates: Creation/modification of userids limited to ten (10) per month
Password resets limited to ten (10) per month
User Profiles Disabled: Unlimited for staff terminations/reassignments
User profile requests made by the Count I, should be batched and sent as a group whenever
possible.
Disaster Recovery is based on a nid nut tu production data loss (Recovery Point Objective -
RPO), as defined in §V1, of one t I ) business day or less and a maximum production recovery
time (Recovery Time Objective - RTO) of seventy-two (72) hours or less.
DR services include not more than one (1) Disaster Recovery testing window of four (4) hours
per year to perform functional testing as part of the planned Managed Advantage on-line DR
test period. The test can include up to ten (10) County testers and CGI will provide each tester
with VPN access to the recovery site during the test period only. CG1 will also provide general
Internet for accessing the CGI VSS application at the recovery site.
Connectivity to the CGI Disaster Recovery site from the County's primary site will be
provisioned and managed by the County. Planning for any loss of County facilities and
connectivity required for other County end-user locations from across the County's WAN is
the County's responsibility.
As with the Phoenix Data Center, CGI will provide general Internet access to the CGI
provided separate and geographically disparate Disaster Recovery site.
10. Provisioning, management, and operation of any development workstations or any client-site
equipment are the responsibility of the County.
11, Hosting or support of the System or related components is limited to those expressly stated in

13082 Exhibit B-2
Managed Advantage Plan Services
General Terms and Assumptions
this Statement of Work. For these applications, Services include supporting the operating
system (OS), database software, Bundled Software Products exclusively used by the
application, CGI hardware/infrastructure, and operational/monitoring software. CGI will
acquire all necessary OS and database software licenses.
No on-site support at County locations is included except as expressly identified in this
Statement of Work; all Managed Advantage hosting support and operations will be provided
remotely and/or from CUT locations. The assigned CGI Managed Advantage client delivery
manager will meet with the County in person, twice per year.
13. All reports and outputs are via print files and/or flat files, XML files or PDFs staged for FTP
and transmitted electronically.
All interface files are to be transmitted electronically.
B. Services to be Performed by CGI
Managed Jdvantoge -- Service's to be Performed by CG1
1. Provide a secure facility at the CGI Phoenix Data Center (in addition to a separate Disaster
Recovery site), for the equipment on which the County's hosted processes run.
a) Physical security will include maintaining a secured computer area controlled by CG1
operations and protected by smoke and water detectors, a fire extinguishing capability,
uninterruptible power supplies, and generator for auxiliary electrical power. The facility
is located in Phoenix, Arizona, which is considered low risk geographically with respect
to force majeure potential.
b) The Phoenix Data Center maintains many federal and business certifications, including
SOX-compliance, 1S09001 compliance, and SSAE No. 16 compliance, or its equivalent
successor.
2. Provisioning, installation, and maintenance of hardware, operating system (OS), and
database software as well as installation and management of software licensed by the County
(Advantage Software and Bundled Software Products) to support the hosted System at the usage
levels documented in:
a) Advantage Software Sizing — Usage Levels in Attachment 1
b) Customization Specifications in Attachment 2
c) This Statement of Work
3. Provide and manage multiple physical and/or virtual servers for the System sized and
determined by CGI based on the information provided by the County as identified herein and
included as Attachment 1. The environments being provided include one (1) production
environment engineered with redundancy and three (3) non-production environment(s) with
storage provisions for three (3) copies of the production database except for the infoAdvantage
and E1360 non-production environments, which will have one (1) copy of the respective
production database.

13082 Exhibit B-2
Managed Advantage Plan Services
Managed Advantage — Services to be Performed by Cal
There will be a maximum of three (3) non-production environments supported following the
Live Date. The sizing of these non-production environments generally assumes concurrent use
of no more than fifty (50) users.
As CGI determines necessary, additional temporary environments may be made available
during a Minor Release or Major Release upgrade. These environments may be reassigned for
alternate purposes as needs arise and provided doing so does not introduce risks to production
operations. Additional storage and/or environments may result in additional fees.
4. Storage amounts for the servers include the entire System (production and non-production
environments and data); backup storage amounts include SAN and tape for the production
system and non-production environments. This includes an initial allocation of up to 2.52TB
primary and 6.3TB backup increased over this Statement of Work Term to a limit of 6.59TB of
primary storage and 16.475TB of backup storage based on the annual growth estimates
provided by the County in Attachment 1. Storage allocations presume that the source for all
System reports and analytics will be the CGI Advantage database and up to three (3) non-
Advantage data sources, Allocation of additional storage is possible using the mutually agreed
upon Change Order process.
5. CGI will retain maintenance contracts in support of all applicable Managed Advantage
infrastructures over this Statement of Work Term.
6. Security services for virus protection, intrusion prevention services on public Internet facing
web servers, and vendor-provided security patches for system-level software.
7. Coordination and performance of typical-level sy,tcni and application backups required to
support business operations and Disaster Recover) largcts (described in §V1.1). The specific
frequency and retention of the various required backups will be determined and documented as
part of the written internal Managed Advantage procedures documentation and will assume at
least a daily production database backup during any day when the system is to be available and
when the documented Recovery Point Objective (described in §VI.D) is the standard one (1)
business day or less.
Specific additional requirements regarding backup and recovery goals for the County's
production environment may be supported at the County's request; however there may be
additional fees associated with such request depending upon the frequency and amount of data.
Additionally, CGI has presumed there are no legal requirements that affect or predicate backup
frequency or data retention for the County beyond what is expressly documented herein.
8. Storage management involves the use of fault-tolerant disk and both on-site and off-site
tapes. Expandable storage of the type appropriate to the respective environment is allocated as
needed and regularly reviewed for capacity and performance. Offsite tape storage and rotation
commensurate with Disaster Recovery requirements is included. Backups restoration testing and
validation is undertaken in conjunction with Disaster Recovery testing as described in this
Statement of Work.
9. Coordination between CGI and the County and support of the County's Transition. This
Transition will be planned using standard project planning tools and will be managed by a CGI

13082 Exhibit B-2
Managed Advantage Plan Services
Managed At vantag*-- Services to be Petformed by CO
Managed Advantage project manager. CG1 will conduct planning and regular status meetings
with the County throughout the Transition period to provide all required elements are
considered, addressed, documented, and correctly implemented within the CGI infrastructure, as
further outlined in §V of this Statement of Work.
10. Provide online access to the CGI Advantage Software listed in §IVA.1 during the hours set
forth under the definition of the Hours of Availabilit) .
11. Production job scheduling, execution, monitoring. and management as well as proactive
measures in support of exceeding the Service Levels. The County will be responsible for
assisting in the establishment of requirements for regular processing schedules and for
communicating and coordinating required scheduling changes with the CGI operations staff no
later than four (4) hours prior to the hours for routine application support.
Once a job schedule is defined by the County for a particular period (nightly, weekly,
monthly... etc. ) CGI will execute that job schedule and provide expected operational outcomes
to the County: unexpected operational results will be resolved in accordance with the service
levels specified in §VI. During Transition and prior to the start of each Contract Year thereafter,
the processing schedule for the upcoming I ear will be reviewed and agreed upon by the Parties.
12. Coordination and processing of interface files. CGI will coordinate and accept the
transmission of data through electronic file transfer via the County's network directly from the
County's staff or County-designated 3rd-party. The County will ensure that files contain the
appropriate content and that all files are received in a timely manner to a predetermined file
structure location, sufficiently in advance to ensure processing in the e pected job schedule.
13. Schedule County reports and outputs and make them available electronically to authorized
users as required by the agreed upon job schedules. All reports and outputs shall be delivered
via locally-routed print files, flat files, or PDFs staged for FTP and transmitted electronically.
14. The Managed Advantage team will be available for consultation with the County 24/7/365
for any Critical or Serious production Issues, as defined by Issue Severity. Requisite
information will be provided as part of the Contacts and Escalation List Deliverable, defined in
§V.D, to facilitate the ease of contacting (and reaching) the relevant Managed Advantage
support personnel. The Managed Advantage team will have the ability to reach other CGI
personnel required to support the County for production Issues, providing access to Advantage
Software experts, as needed to maximize application availability. Additional details as to the
hours of CG1 staff availability in support of Managed Advantage are defined in §VI.
15. Standard database support includes database monitoring and maintenance activities, file
allocation monitoring and adjustment, as well as reorganizations as necessary. Standard
database support service also includes delivery of production data to non-production
environment(s) on request, post-transition. This service is limited to twelve (12) times per year
and not more than once (1) per week unless required to support a Critical/Serious Issue or
upgrade.
16. Support includes production code migration as described below:
a) Critical/Serious Issue:

13082 Exhibit B-2
Managed Advantage Plan Services
Managed Advantage — Services to be Performeny C6 -1
• Unlimited for Critical or Serious Issues for which CGI is responsible, per §VI. 110.
Limited to one (1) per month to resolve a Critical or Serious Issue for which the County
is responsible unless additional production code migrations are requested of CGI by the
County through the use of Discretionary Support services..
b) Moderate/Minor Issues and Other County Migration Requests:
• Limited to one (1) per week during routine support hours (as defined in §VI.A.1.a) at
preset intervals, independent of the responsible Party (i.e., once per week on a set day)
and should be batched and submitted as a group whenever possible.
17. Standard change management and application code version control and tracking for the
System.
18. Production code Hot Fix application and management as necessary for Critical Issues and
Serious Issues in production that have a business impact to the County. CGI will follow the
definitions of Critical Issues, Serious Issues. Moderate Issues, and Minor Issues as defined in
§II.B.19. However, any Issue which CGI's Managed Advantage team determines to warrant
escalation in order to support ongoing hosted business operations will be considered a Critical
Issue regardless of that definition.
The County will certify any production updates as acceptable for production deployment prior
to final migration into that environment.
19. Upgrades as specified in §V.E. The County will participate in the scheduling, planning, and
final testing and eel iification of these efforts prior to final deployment to the production
environment. Both CGI and the County will work together to time the activities such that they
balance the introduction of new releases/functionality with the objective of continued
application stability.
20. Reports on Service Level performance at the frequency and with the information specified in
§VI, monthly service level reporting shall be targeted to a date not later than fifteen (15)
calendar days in the month following delivery of Services, to be delivered not later than the next
invoicing date, as provided in §VI of this Statement of Work.
21. Support for County audits of the System. CGI shall provide support for the County's audits
during routine support hours set forth under the definition of the Hours of Availability, which
unless mutually agreed, will not exceed more than twenty-five (25) hours spanning a thirty (30)
day period annually. If necessary, additional hours can be made available through the use of
Discretionary Support services.
22. Provide the Count) with discretionary consulting services ("Discretionary Support") on the
basis of five hundred (300) hours per year beginning in fiscal year 2016 through the end of this
Statement of Work Term. These hours will be made available to the County on a fiscal year
basis. Effort logged by CGI against the discretionary consulting services must be approved by
the County in advance up to a specified threshold/cap for each requested activity/service.
Approval by the County may be subject to CGI using the discretionary hours (with County
approval) for analysis to provide an estimate of the effort for the County requested
activity/service.
In order to accommodate appropriate capacity planning for the coming year, the County and

13082 Exhibit B-2
Managed Advantage Plan Services
Managed Advantage — Services to be Performed by CGI
CGI will prepare a draft annual plan for use of the discretionary hours. The County and CGI
will review this plan quarterly in order to firm up resource requirements for the coming quarter.
While CGI will make every reasonable opportunity to make resources available on an as needed
basis, CGI requires thirty (30) days advance written notice in order to provide the required
resources. It is generally assumed that the work will be 55% onsite and 45% remote, as well as
1/3rd functional and 2/3rd technical.
Discretionary hours may be used for the following activities or others, as mutually agreed upon
by the Count) and CGI: testing scripts (i.e. functional, LE AT, performance), report
design/development, interface development, new customization development, functional
support, training and documentation (i.e. Minor Release), functional release planning and
evaluation of complementary 3rd party products.
C. Service to be Performed by the County
The County will be responsible for the timely performance of its responsibilities as set forth in this
Statement of Work.
Services to be Pe; formed by theChunty0
Provide any/all available documentation detailing the County's current application
configuration.
2. Provide named individuals as primary and secondary points of contact and
escalation procedures for the Transition period as well as post-Transition operations under
Managed Advantage.
3. Coordinate with CGI operations staff for services, support, and scheduled
maintenance through the designated, centralized CGI points of contact (e.g. two or three named
individuals) identified in the Contact and Escalation Deliverable described under §V.D.
4. Provide Remote Hands Support for any CGI network equipment located at the
County's facility associated with the circuits connected to CG1's network.
5. Maintain all Advantage Software application user-id security.
6. Provision, maintain, and manage secure FTP services for interfaces and data
transmissions.
7. Coordinate the timely transmission of data through electronic file transfer directly
from the County's facility and network.
8. Ensure all files are transmitted/received in mutually agreed format and in a timely
manner, sufficiently in advance to ensure processing in the expected job schedule.
9. Assume responsibility for the integrity of all input data delivered to CGI (either

13082 Exhibit B-2
Managed Advantage Plan Services
Services to be Performed by the County
online or through batch interfaces) for processing.
10. Provide at least sixty (60) days advance notice of any increase in processing
olumes over twenty percent (20%) outside of gradual and agreed upon growth projections, as
outlined in Attachment 1. Any special processing specified in §VI, is excluded from this
requirement, but both Parties acknowledge such cases will be operated and limited by current
capacity. Processing of such increases may be subject to additional fees.
11. Execute testing, including user acceptance testing, in support of patches and/or
changes prior to production migration. Testing generally will include the County executing jobs
in non-production environments, at least up to final testing immediately preceding production
migration.
12. Timely validation of the production application output associated with application
configuration, use, and functional application management (i.e. outside of CGI's purview).
13. Report scheduling, distribution, and output handling.
14. If applicable, execute parallel processing andior other methods of validating
correct application processing (with technical support from C GI) during the Transition and
before the final cutover to live operations on the CGI infrastructure.
I S. Provide, manage, and operate employee workstation hardware and software and
other onsite equipment.
16. Provision, manage and maintain adequately-sized communications from the
County's WAN to end-user locations not associated with any CGI-provided communications
network.
17. Provision, manage, and maintain adequately-sized data communication
connectivity mechanisms from the County's WAN (or other end-user locations) to COI's
Phoenix Data Center and to CG1's Disaster Recovery site.
18. Assist in problem identification and resolution as it relates to the County's data,
staff, and/or procedures as well as functional issues with the System and appropriate interaction
with interfacing entities. The County will report any Issues to CGI using the standard Issue
reporting process for Managed Advantage.

13082 Exhibit B-2
Managed Advantage Plan Services
Transition Approach and Post-Transition Services
A. Transition Approach & Overview
This §V.A provides an overview of the Transition process, which will be performed concurrently
with the performance by the Parties of their obligations under this Statement of Work and Exhibit
B-5 (Project Implementation Services). The initial Transition will include the implementation of
new Advantage Software as well as a Major Release upgrade, as further described herein. The tasks
and activities outlined below and are based upon information documented in §111 and Attachment
1, and Attachment 2, as well as CGI's experience implementing, hosting and maintaining
Advantage Software for customers with similar platforms and scope. The Deliverables required to
be completed during the Transition are set forth in the Project Plan as defined in Exhibit B-5. The
tasks identified in this §V will be used by the Parties as the basis for developing a fully detailed
Transition Plan Deliverable, which will be integrated with the Project Plan. Additionally, authorized
County and CGI representatives will establish a mutually agreed upon Go-Live Checklist
Deliverable, as described in §V.D, including decision points on which the final decision to cut-over
to live operations on the CGI infrastructure will be made. The Go-Live Checklist Deliverable will
include key milestones throughout the Transition period as well as the final criteria upon which the
cutover decision will be made. The Go-Live Checklist Deliverable will be reviewed by CGI and the
County regularly so as to assess progress and minimize/mitigate unexpected events as the cutover
date approaches.
The upgrade and technical migration of the designated System functionality in the County's AMS
Advantage Version 2 system to the CGI Advantage Version 3 System platform involves three main
components: software (code and Customizations to and configuration of the baseline application
layer, reports, customized interface processes, and processing scripts), platform (infrastructure,
network, and servers), and data (database and sequential files). Upon completion, of the Transition,
the System shall operate successfully and accurately, in accordance with its Specifications and
Documentation, in the CGI Phoenix Data Center.
CGI shall begin planning on/around the Effective Date, which shall include the definition and
documentation of key operational elements like points of contact, escalation, scheduling,
monitoring, status reporting, and other procedural items. CGI and the County shall define the
operating model between all involved Parties. CGI shall include mock cutover and functional and
technical comparisons, if appropriate, between the existing legacy system and results from the new
processing environment. More information about the Transition is set forth below and in Exhibit B-
5.
1. Software and Initial Implementation
The County's version of the AMS Advantage Version 2 Software will be implemented to a current,
agreed upon Major Release of the System as part of the initial Transition to the CG1 Advantage
Version 3 application environment/infrastructure in CGI's Phoenix Data Center.
Within the System, the Advantage Software application layer (i.e. Websphere, Versata, the
Advantage Software directories) will be installed by CGI from the CGI baseline libraries. Third
party software products associated with the System will then be installed by CGI from CGI's vendor
software libraries. Finally, the County's custom interface software, reports, forms, processing
scripts, and other County-specific software will be migrated/integrated by CGI, as appropriate (in
light of the Major Release upgrade) and as further described in this Statement of Work and Exhibit
B-5. Once complete, the application software will be built and deployed by CGI into the run-time

13082 Exhibit B-2
Managed Advantage Plan Services
application libraries creating the software environment that will be used for the County's
deployment of the System. Upon successful validation by the Parties during the Transition, this
environment will be used to create the non-production application area(s).
Following the installation and updating of all software layers and elements, testing occurs to validate
that all installed elements are correctly interworking and launching correctly, both independently
and collectively.
2. Platform
The platform for the System in the Phoenix Data Center consists of infrastructure elements such as
power and floor space allocations, cabling/power for telecommunications, network, and servers. The
network consists of software installation and configuration, including without limitation those for
the telecommunications, firewall access and restrictions, balancing, monitoring, and reporting. CGI
will provide operating system installation and configuration for the servers, monitoring and
reporting tools, and other maintenance utility installation and configuration required for the
System's platform.
As part of Transition, CGI shall develop the specifications for the planning execution, and
documentation for the standup of the platform for the County's Advantage Software environments.
Such specifications shall be used for ongoing operations as well as Disaster Recovery preparation,
testing, and in the event that it should be necessary, execution. To complete the platform standup,
CGI shall test every component of the infrastructure, network, and servers to validate that each
element correctly interacts with the others to support the County's needs.
Once the platform standup is complete, implementation activities for the System shall begin, in
accordance with this Statement of Work and Exhibit B-5.
3. Data
As part of the initial upgrade of the System under this Statement of Work and Exhibit B-5, CGI
shall convert the County's AMS Advantage Version 2 database. The County's data will be
transferred to the CGI environment by executing prescribed SQL and standard CGI processes, via
file transfer, disk, tape or other media deemed to be practical and mutually agreed by the Parties
(depending on the volume of information). This process will be repeated periodically to refresh the
data, as necessary to support the Transition. Sequential files, as part of the application or interfaces,
will also be ported over and updated/refreshed as necessary.
Once the data is in place within the associated the CGI Advantage Version 3 environment, as
provided in this Statement of Work and Exhibit B-5, the Parties will begin full application testing.
CGI will validate that the software, platform, and data are working collectively to appropriately
process the County's transactions for each Advantage Software application component (described
under §IV.A.1) within the System. Testing by the Parties will include nightly, monthly, quarterly
and other periodic processing runs, as well as online transaction processing. CGI shall perform
backups of the County's existing production data throughout the testing process, such that the data
on which testing is being conducted remains current. These backups may include various processing
points, which will be used by the Parties to conduct system testing, possibly user acceptance testing,
and ultimately any mock cutovers and/or parallel testing/results comparison.

13082 Exhibit B-2
Managed Advantage Plan Services
4. Procedures
In accordance with Exhibit B-5 and the Project Plan, procedures will be written by CGI for the
ongoing operation of the System, and the Parties will perform testing to validate that batch
processing, connectivity, file transfer and printing and other procedures are performed in accordance
with the applicable System requirements. Such testing will include the County's training team and
involve loading/unloading tapes, review of output, checks, parameters, run schedules, trouble
shooting, and application access rights and security. Following these testing procedures, a user
acceptance test will be conducted by the County's designated users and staff, in accordance with the
applicable System requirements. This testing will include online processing, job scheduling and
offline processing, as well as output verification and distribution consistent with the Operational
Readiness Assessment.
Mock cutover activities will be performed by the Parties, validating the procedures, data, source, and
operational elements involved in that process. The mock cutover will test the final stages of the
Transition to validate that all elements have been correctly considered. Following the mock cutover
period, generally a parallel processing period will be conducted. At a minimum, results from
processing the final mock cutover data in the CGI environment will be functionally and technically
compared to similar results obtained from the processing that occurred in the County's production
environment. This doesn't necessarily happen at the same point in time, but the processing results
should generally parallel each other. If the processing results from the two tests are not parallel, the
Parties shall identify and fix the cause of the discrepancies. This processing window allows key
system stakeholders with the County to validate that processing in the County's AMS Advantage
Version 2 system is being accurately processed (in a similar or expected fashion) in the System.
The final step is the actual cutover to production on the CGI environment. One or more go/no-go
checkpoint(s) and decision meeting(s) will take place before the final cutover. Authorized County
and CG1 representatives will attend this meeting(s), review the previously established and mutually
agreed upon checklist of go/no-go decision points, and jointly make the final decision as to cutover.
Once a "go" decision is agreed upon by the Parties, CGI will execute the cutover upon its receipt of
a final "authorization to proceed" from the County.
B. Key Activities and Assumptions
General Terms and Assumptions
CGI Transition Services Activities
The purpose of the Transition is to validate that the County's needs are identified, addressed,
documented, and correctly implemented within the System and associated environments as
outlined in §IV.B. CGI shall provide the County with appropriate access to the System, and
validation that all components of the System are functioning correctly and are production-
ready. System components include, but are not limited to, batch schedules and notifications,
application and infrastructure monitoring and notifications, and backup scheduling.
CGI will assume responsibility for maintenance and support of the environments. This includes
assimilation and transition from the County to CGI staff, as appropriate. For example,
expected results of batch processing executions (i.e., typical number of checks produced each
run), unique elements of the non-production user access permissions, and unique batch
processing outcomes of special runs will be communicated from the County to CG1.

13082 Exhibit B-2
Managed Advantage Plan Services
General Terms and Assumptions
The County and CGI will define and document, as part of the Contact and Escalation
Deliverable described in §V.D mutually agreed upon escalation and call out procedures,
including responsible Parties and a finite number of designated points of contact for both
parties (e.g. 2-3 named individuals).
4. Only the target release of the Advantage Software (version 3.10) will be installed at CGI and,
while temporary data may be stored during the Transition, CGI is not installing any prior or
other releases.
5. Contingent on the Live Date decision, the Transition, as a supporting element of the Project
Plan, will not exceed the initial thirty-three (33) months of the engagement. Planning and
procurement activities generally consume the first ninety (90) days of the Project Plan. This
period includes the lead time to provision network connectivity, platform standup in the CGI
Phoenix Data Centel. and jointly prescribed testing.
CG1's planning will use standard project planning methodologies and tools, including
management by a Managed Advantage project and transition manager designated by CGI;
preparation, County planning and regular status meetings conducted by CGI with the County;
all performed in accordance with the Project Plan with timelines for critical tasks
CGI's general assumptions for the Transition a re noted below:
7. The work under this Statement of Vv ork will be divided into two distinct components:
a) The initial Implementation and Transition Period — covering the elements described
immediately below and shall be completed within the period identified in §V.B.5,
including planning and platform standup, the Advantage Software application installation,
and upgrade in support of Exhibit B-5. all testing, and mock and production cutovers.
h) Production Operations — Following the production cutover, CGI will assume production
steady state operations, inclusive of periodic upgrades as defined in §V.E The
documentation and procedures defined and validated during the Transition (and outlined
under §V) will he in place and will be modified as mutually agreed upon during this
Statement of Work Term.
All Services, exclusive of application testing, will be led and performed by CGI, with the
assistance of the County as requested by CG1, and as otherwise set forth in the Project Plan. The
timing and availability of the production and non-production environments will be specified in
the Managed Advantage Transition Plan Deliverable, which shall be delivered by CG1 to the
County in accordance with the Project Plan.
Certain aspects of the planning activities will be performed in parallel. The implementation order,
prerequisites, and dependencies of these activities are set forth in the tables below and will be
specifically defined in detail during the initial stage of the Transition planning activity and
documented in the "fransition Project Plan.

13082 Exhibit B-2
Managed Advantage Plan Services
General Tilams and Assumptions
10, Unless otherwise agreed by the Parties in writing, provisioning of any hardware:software by the
Managed Advantage team will begin immediately following the Effective Date, given potential
lead time requirements with outside vendors of sixty (60) to ninety (90) days or more, in order to
allow sufficient time for CGI's project implementation team and the County to access
environments for testing and other activities. Inability of CGI to promptly engage in such
procurement may result in a delay in the Transition schedule.
The Parties will fully complete all planning activities in accordance with the Project Plan. Upon
completion of planning activities set forth in Exhibit B-5 and this Statement of Work and the
Attachments hereto, CGI shall deliver to the County the Managed Advantage Transition Plan
Deliverable as described in §V.D, complete with dates, dependencies, and responsible Party.
Subsequent Deliverables, including but not limited to more detailed tasks and the definition of
the Go-Live Checklist Deliverable, as described in §V.D will be completed by CGI as set forth in
the Project Plan.
12. The middle stage of Transition includes execution of the Project Plan and the Managed
Advantage Transition Plan, and all associated testing activities.
13. The final stage of the Transition is expected to include validation that all elements required under
Exhibit B-5 and this Statement of Work and its Attachments have been completed in accordance
with their applicable specifications and completion of the mock cutover(s) and. if applicable,
parallel processing and/or comparative validation.
C. Transition Steps to be Performed
Define County network and
telecommunications requirements,
provision infrastructure, and X
install/configure/test network elements in
support of the System
Network Design,
Installation, and Provision the required circuits and
Testing configure remote connectivity between the
CGI data center and the County network(s) X
sufficient for CGI to deliver on its
responsibilities as defined herein
Test all connectivity points

13082 Exhibit B-2
Managed Advantage Plan Services
Provide ongoing Remote Hands Support
for any physical activities related to
network or infrastructure equipment at the X
County site (e.g. equipment resets) as
required to support environment setup and
operations
Identify and collect from the County, all
environment elements (source, data,
configuration settings, documentation)
required for the System and any other X X
available related documentation and/or
information regarding the environmental
setup
Define based on County provided
requirements the requisite environment
configuration to support the System. This X
includes but is not limited to OS, DB/user
access requirements, batch scheduling, and
backup processes
Define naming and other conventions for X X
use by the County
Setup all required configuration
Environment Setup fo
the Managed Install Advantage Software, Bundled
Advantage System Software Products, and County-specific X
software such as processing scripts, reports
and interfaces
Perform Major Release upgrade steps X
Perform updates to processing scripts and
backups for the System's production X
environment
Define and perform associated user
acceptance testing

13082 Exhibit B-2
Managed Advantage Plan Services
Identify and define required unique user
groupings, and their included user list. This
includes all types of technical environment
users (e.g. end users, FTP users, interface X X
users, but excluding application users
established and managed by the County
through the implementation)
User Access Design, I )efine user groups and users to relevant X
Implementation, and ironment (server)
Testing
Validate user groups and user ids X X
'Perform application and platform testing as
appropriate (CCil technical, County X
functional)
Define and perform user acceptance testing X
Define job processing schedule for the
System based.upon County provided
requirements. This includes the timing,
dependencies, and expected outcome of
each job within each of the batch schedules
Define interface and reporting
requirements and processing schedule.
This includes the timing, dependencies, X X
and expected outcome of each interface
and reporting job within each of the batch
Operations Setup schedules
Define interface and reporting X X
access/distribution requirements
Coordinate the transmission of data
through electronic file transfer directly to
and from the County's staff or designated X X
3rd-party providers and/or interfacing
entities via the County's network
Test printing at the County X

13082 Exhibit B-2
Managed Advantage Plan Services
Dofine monitoring, remediation, escalation, X
and 2nd level help desk procedures
Define detailed production .cutover steps,
This includes but is not-limited .to timing,
responsible Party. communication X X
mechanism, validation procedures, and
go/no-go signoff criteria
Identify source libraries, data stores, and
tapes (or other mutually agreed upon X X
media) for inclusion in production cutover
activities
Identify transmission methodology (FTP.
tapes via overnight, manual, or other
mutually agreed upon method) for each X X
source and create transmission checklists,
unload steps. and verification procedures
Define source load processing steps, order,
dependencies, validation requirements, and X X
back-out procedures
Production Cutover
Planning
Create test plans for cutover testing X X
Create test plans for user acceptance X
testing
If applicable, define detailed parallel
processing validation requirements. This
includes, but is not limited to, determining
how duplicate online data entry, if X X
necessary, will be handled and how
successful parallel processing will be
validated
Perform the mock cutover to validate plans X X
and procedures
Perform additional mock cutover(s) as
mutually determined to be necessary to X
validate plans and procedures

13082 Exhibit B-2
Managed Advantage Plan Services
Make adjustments to the System
implementation if/as needed for correct X X
processing
Perform user acceptance testing, including
any applicable parallel production testing X
and/or functional/technical validations
Final and ol ficial go/no-go decision X X
Production Cutover
Perform production cutover X X
Populate non-production environment with
production data
Validate all required elements (code, data,
documentation, and an>• other elements for X x
the successful processing of the County's
business transactions) is in place with CGI
Post-Cutover Steps
Begin full production operations of the
System under Managed Advantage based X
on transition planning documents
D. Transition Deliverables
Listed below are key Deliverables for the County's Transition process. The specific dates for each
Deliverable will be defined as part of the initial planning at the outset of the Transition and will be
included as milestones on the Project Plan. CGI requires access to necessary information
(application code, configuration, etc.), to evaluate and plan the correct Transition approach and
define appropriate milestones.
Deliverable
Managed Advantage Transition Plan
MA-1.00
To define the inter-dependent tasks associated with the Managed Advantage
Put7,0se infrastructure and application technical deployment.

13082 Exhibit B-2
Managed Advantage Plan Services
Deliverable
Managed Advantage Transition Plan
MA-1.00
Tasks, dependencies, and assigned organizational responsibilities covering the
Transition services defined in the Transition specification. For ease of
Content maintenance and readability content may be provided as separate, but will be
consistent with the overall Project Plan, and will integrate any dependencies.
Deliverable
Environment Overview
MA-2.00
To provide a high level understanding of the System environment on which
Purpose Managed Adeantage will be performed.
High level, logical diagram of the relevant elements comprising the production
Cm tent and non-production CGI Advantage Version 3 environment for the County.
May include diagrams and/or accompanying short descriptions as necessary.
Platform Test Plan
To validate that the Managed Advantage platform supports the intended
—Purpo* Advantage Software application components.
Test criteria for confirming the elements were installed correctly and their inter-
operability is as expected. Test steps are intended only to validate the platform.
Content Details will include but are not limited to user access rights, accessibility,
network routing and firewall rules, and that other elements work as expected in
support of the application.
I)elii'eral
Go-Live Checklist
MA-4.00
To provide a concise list of steps to validate the production cutover
Purpose considerations are met prior to commencing the cutover itself.
Detailed documentation of areas of consideration. their owner and relevant
criteria to be considered prior to a go/no-go decision. This is not the go/no-go
Content acceptance criteria list or the cutover plan itself, but rather the checklist of items
(e.g. communicate to team X about Y, notify vendors on X date).

13082 Exhibit B-2
Managed Advantage Plan Services
Deliverable
Contact and Escalation List
)WI-5. (10
To provide the access information required for the County to contact the
Purpose Managed Advantage team for both routine and emergency support.
Details of contact information for the Managed Advantage team including
Content contact mechanisms (e.g. email, phone), names and procedures for use. Routine
and escalation information will be included.
Deliverable
Cutover Plan
MA-6.00
To minimize risk and maximize repeatable, tested steps necessary to achieve
Purpose successful production cutover.
Detailed steps required to perform the technical production cutover process.
Draft document will be created mid-Transition and enhanced/modified during
the mock cutover process, both in accordance with the Project Plan. Timing of
Content associated steps will be documented to facilitate final cutover planning. Details
include the preparation of data to be loaded into the System, turning on/off
elements as part of cutover (e.g. using real email addresses rather than test ones
for vendors).
Deliverable
Processing Schedule
MA-7.00
To provide a schedule with the "calendar of events" for the Managed Advantage
Purpose production environment that will guide operations and include the County's
processing requirements.
Annual calendar identifying the processing events such as
nightly/weekly/monthly/quarterly/annual cycles as well as special processing
events known ahead of time (e.g. W-2 processing, 1099 processing, annual
Content close, etc.). Details will include special online access (or online shutdown)
periods as well. This calendar will be produced as part of this CGI Deliverable,
based upon information that will be provided largely by the County.
Deliverable
Operational Procedures
MA-8.00
To provide operational procedures the County will follow to coordinate
Purpose effectively with the Managed Advantage team iti delivery of the service.

13082 Exhibit B-2
Managed Advantage Plan Services
Deliverable
Operational Procedures
MA-8.00
Details of steps for interacting with the Managed Advantage team including
when to use which contact mechanism, cutoff times for processing changes,
agreed upon "what to do when" procedures as well as forms required as part of
any County requests to CGI.
E. Post-Transition Upgrades
Post-Transition Upgrades - Description of Approach and Scope
Implementation of Patch Sets:
Advantage Software updates for the County between Minor Releases will be
implemented via Patch Sets.
The implementation of Patch Sets will begin within one year of the Live Date and occur
every year thereafter in those years when a Minor Release upgrade is not scheduled.
During regular meetings, the County and CGI will agree to the timing and schedule of
Patch Set implementation.
d) The number of patches included in a Patch Set is expected to be between fifteen (15) and
twenty (20).
The patches included in a Patch set will be selected by the County, in consultation with
CGI.
Implementation of Minor Releases:
After the initial implementation of the System, CG I anticipates and has included
provisions for the technical implementation of up to two (2) additional Minor Releases
during this Statement of Work Term.
b) The timing and scheduling of the implementation of a Minor Release Upgrade will be
based upon mutual agreement. Deferral of a Minor Release upgrade is at the County's
option provided it does not prevent remaining current on the System and thereby
undermining CGI's ability to support the County.
in advance of a Minor Release upgrade, CGI will track requested patches of more
immediate importance to the County. Provided the County is operating within the general
service limits defined in this Statement of Work and absent other voluntary extensions in
CG1's scope of services, CGI is willing to coordinate inclusion of a small number of
patches identified during CGI's internal Minor Release upgrade planning efforts without
additional fees. The total number to be included is expected to be less than the number
defined for a Patch Set in this Statement of Work.

13082 Exhibit B-2
Managed Advantage Plan Services
Post-Transition Upgrades - Description of Approach and Scope
d) The elapsed duration for any Minor Release upgrade will be as proposed by CGI and
agreed to mutually with the County.
e) CG1 will provide project management services associated with the Minor Release
upgrades, exclusive of project management services associated with the County's
licensing and implementing additional software from CGI (i.e. new Advantage modules
or complementary third-party software) in conjunction with the Minor Release upgrades.
Implementation of Major Releases:
Should a Major Release be available within the initial Statement of Work Term and the County
requests this to be applied in lieu of an included Minor Release upgrade, CGI will work with the
County to determine the timing, scope, and features of the Major Release that are to be
implemented as well as the associated effort/cost for CGI to work with the County in supporting
the Major Release upgrade if it exceeds what was planned for a Minor Release upgrade and/or
the other operating and usage parameters herein.
Temporary Environments:
As CGI determines necessary, additional temporar y en \ ironments ma) be made available
during a Minor Release or Major Release upgrade and phased/partial refreshes of the hardware
may be applied during upgrade efforts.
F. Post-Transition Upgrades — Steps to be Performed
Responsibility
CGI County
Define required environment
configuration to support the upgrade.
This includes but is not limited to
evaluating the hardware and software X X
requirements and specifying the
appropriate non-production environment
and access.
Upgrade
Environment Setup Identify, with assistance from CGI, all
for the Managed County-specific components to be X X
Advantage System included
Provision any new infrastructure or
hardware (if applicable) required to
support the upgrade
Provide Remote Hands Support for any
physical activities related to the County X
network or infrastructure equipment (for

13082 Exhibit B-2
Managed Advantage Plan Services
Responsibilii
Activities I on
rEgi Count;'
example equipment resets) as required to
support upgrade activities
' Idenii ly any training and/or user
! clocumen(fli ion updates that may be X
required
Setup all required configurations defined
based on the steps above
• Install Minor Release upgrade and/or
Patch Set software, related third party
products, and County-specific' X
components such as processing scripts.
ine ports and interfaces
Perform updates to production operations
processing scripts and backups for the X
CGI processing environment
Run any automated utilities available for X
: convcrtim) 3" l-party product data
Resolution of any County 3rd-party
software data issues vernal n lug after the
running of the automated utilities
Perform application and platform testing,
as appropriate (CGI technical, County
functional), to include, but not limited to:
Verify job processing schedule based
on County provided requirements.
This includes the timing, X
Data Conversion dependencies, and expected outcome
and Testing of each job within each of the batch
schedules
Verify interface and reporting
requirements and processing
schedule. This includes the timing, X X
dependencies, and expected outcome
of each interface and reporting job
within each of the batch schedules
c) Verify interface and reporting X X
access/distribution is functioning
d) Modification of interface files, X
reports, as needed

13082 Exhibit B-2
Managed Advantage Plan Services
4 ci! vities Item
e) Verify the transmission of data
through electronic file transfer
directly from the County's staff or X X
designated 3rd-party providers
and/or interfacing entities via the
County's network
0 Test printing at the County X
Define and perform functional testing, X
training, and user acceptance testing
Define detailed code migration steps,
including but not limited to timing,
responsible party, communication X
inechank in, validation procedures, and
go/no-go signoff criteria
Identify source libraries. data stores, and
files for inclusion in production cutover X X
Code Migration . activities (each Party for their site)
Planning
Define source load processing steps,
order, dependencies, validation X X
requirements. and back-out procedures
Create migration plan for production
cutover, including training and X
documentation requirements
Final and official go/no-go decision X X
Perform production migration of
upgraded System following the X X
Patch/Upgrade production migration plan
Code Migration
Perform archival and shut-down of any
pre-upgrade environments for the System
that are no longer needed based on X
County requirements

13082 Exhibit B-2
Managed Advantage Plan Services
VI. Service Level Agreements
A. SLA Applicability
The general framework for the SLA is illustrated in the following graphic:
Exhibit B-2-B: CGI Performance Framework for Service Level Agreement
SeNice Level Implication
Pe rtna nee
When above, Earnback
Credit achieved by CG1
Expected Performance Range between Minimum
and Exceeded Service Level
Detailed Explanation as to When and llow the SLA Applies
While not specific in a Service Metric, remote availability of the Managed Advantage team in
support of delivering the Services and the SLA is as follows:
a) For routine support:
II. Toll-free phone number for routine support 8:00am - 5:00pm Arizona Time, Monday
— Friday, exclusive of mutually agreed upon holidays in accordance with the definition of
Hours of Availability
b) For production emergencies:
CG1 staff on-call 24/7/365 for Critical and Serious Issues in the production
environment as defined in §II.B.19.
Within this SLA, the days and hours as defined above are referred to as Business Days and
Business Hours, respectively.
The Service Metrics and Service Levels are applicable to the infrastructure and environment as
well as the System, as appropriate for each Service Metric. They are not applicable to any
Customizations or enhancements to the System not identified within Attachment 2. Similarly,
they only apply to interfaces operating on the Managed Advantage infrastructure and for
which CG1 is solely responsible. Interfaces operating at the County either creating
data/content to be sent to CGI or processing data returned by CGI are the responsibility of the
County.
The Service Metrics and associated Service Levels apply to the production environment and
use of the System in production, unless specifically noted otherwise. In the event that a single
Issue affects more than one Service Level, only the Service Metric with the highest Service
Penalty will apply with respect to any Service Credits issued by CG1 to the County. However,
other unrelated incidents resulting in Issues will be considered as separate events and
aggregated with respect to measuring performance against each Service Metric and associated
Service Levels.

13082 Exhibit B-2
Managed Advantage Plan Services
Detailed Explanation as to When and How the SlA Applies
4. Approximately ninety (90) days prior to the start of the twelve (12) month period following the
Effective Date of this Statement of Work (each such twelve (12) month period being a
"Contract Year") and then ninety (90) days prior to every twelve (12) months thereafter
throughout the Term, the County and CGI will mutually agree in writing upon a processing
schedule that supports the County's business needs and identifies any times/days where the
System and CGI's services defined herein apply and do not apply, including the County's
special processing periods (which are excluded from the calculation of any Service Credits if
volumes exceed what was modeled and tested for the System or in the determination of Batch
Processing Time), holidays, maintenance windows, etc. Any material adjustment or impact
that changes the processing calendar will be handled via a Change Order
The County and CGI will coordinate Scheduled Maintenance Periods at least two (2) calendar
weeks in advance. Exceptions may be needed if a situation occurs that puts achievement of
the target Service Metrics and associated Service Levels at risk. Such maintenance shall he
timed to coincide with times of minimal traffic or use for the County. CGI reserves the right
to immediately request and institute a Scheduled Maintenance Period at any time of the day if
CG1 reasonably determines that a failure to act immediately would lead to significant harm to
either CGI or the County. Every reasonable effort will be made to obtain the County's prior
approval of such action in writing. Scheduled Maintenance Periods under these circumstances
cannot be associated with an Issue or a situation that CGI could have reasonably mitigated
within CGI's boundaries of responsibility (as per the Point of Demarcation) under this
Statement of Work.
6. The County suspends any specific Service Metric and associated Service Level/Service Credit
that will subsequently not be met due to the County's failure to perform its responsibilities
under this Statement of Work. The County's related responsibilities in non-technical use and
administration of the System after the Live Date include functional configuration, functional
management, and Issue(s) requiring functional support in troubleshooting and diagnosis.
CGI performance against any suspended Service Metric and associated Service Level will be
reinstated once the corresponding activity has been performed by the County. The County
agrees to hours of availability for staff and interdependent systems reciprocal to the Hours of
Availability defined herein so as to support effective escalation and not to impede
collaboration and support in resolution of Issues affecting Service Metrics and associated
Service Levels.
7. Any events or situations affecting the System for which air is not solely responsible will not
be counted toward CGI's ability to achieve the Minimum Serviee Level(s) associated with the
respective Service Metric(s). Similarly, if the County elects to delay or skip an update or
upgrade and doing so no longer keeps the County on supported releases of any part of the
System, the County acknowledges that CGI's ability to achieve the Minimum Service
Level(s) associated with the respective Service Metric(s) may be impaired. Should the
standard or recommended resolution of one or more Issue(s) have been associated with the
delayed or skipped updated/upgrade, Service Credits will not be issued in association with any
affected Service Metric(s) and associated Minimum Service Level(s).
8. If CGI is waiting on the County for additional information during resolution of an Issue,
measurement of CGI's non-conformance with the respective Service Metric and associated
Service Levels being impacted is suspended until the County's response with the requisite
information is received. Once CGI makes available a fix or correction to remediate an Issue

13082 Exhibit B-2
Managed Advantage Plan Services
Detailed Explanation as to When and How the Sk4 Applies
impacting one or more Service Metrics, measurement of CGI's non-conformance with the
respective Service Metric and associated Service Levels being impacted ends.
As an example, CGI is not responsible for additional time associated with subsequent County
required approvals or procedures related to the application of the fix or correction. If, upon
application of the fix or correction, the Issue is not remediated, CGI will again be subject to
measurement of non-conformance against the Service Metric, upon notification by the County
to CGI or acknowledgement by CGI to the County of the new or continued situation.
Unless otherwise agreed to by both parties, if notice is by the end of the following Business
Day after CG1 delivers an applied fix or correction to the County for the County to test,
continuation of resolution time will be against the original Issue, otherwise a new Issue is
logged. However, none of these situations relieve CGI from responsibility to support
resolution or remediation of a situation if any part of the cause or ability to resolve fall within
CGI's responsibilities as set forth herein.
9. Service Metrics and associated Service Level calcuiations will be suspended during an active
Force Majeure or when operating the System under a Disaster Reco% ery scenario, as declared
by CGI. Reporting and calculations will be reinstated once operations resume at the Phoenix
Data Center or a replacement primary site.
10. The initial Measurement interval for purposes of calculating Service Credits begins with the
first full month ninety (90) calendar days after the Live Date, however Service Metric and
Service Level reporting begins on the Live Date. Similarly Service Credits for any affected
subsystems (e.g. Procurement/Vendor Self Service) of the application are suspended for sixty
(60) calendar days after the application of a Minor Release or Major Release. Notwithstanding
the absence of Service Credits during these periods, CGI will continue to remain subject to all
its other obligations as set forth in this SLA.
B. SLA Management
General Terms Regar g Reporting and Ca
CGI shall implement and utilize its current measurement and monitoring methods, tools, and
procedures to track and report CG1's performance in delivering the Services relative to the
applicable Service Levels and shall produce a monthly report. Any additional reporting or
measurement or use of County-specific tools and technologies by CGI shall be subject to a
Change Order.
2. Service reporting is provided monthly. The monthly report will be delivered in tandem with
any CGI invoices for the Services rendered within the given month, on the agreed upon
invoicing schedule, if applicable. The report will measure and document CGI's performance
of the Services relative to the Service Levels and the County's usage of Services. The report
will set forth in detail the Service Metrics relative to the Service Levels, the actual measured
level of performance for each Service Metric, and any resulting monthly Service Credits net
of any offsetting Earnback Credits.
In all cases, CG1 will be responsible for measuring Service Levels and calculating appropriate

13082 Exhibit B-2
Managed Advantage Plan Services
General Terms Regarding Reporting and Calculations'
Service Credits for the .parties in accordance with this §VI
C. Service Levels
Managed Advantage Service Metrics and Levels as Defined for the County
If (GE performancefalls below the identified Minimum Service Level, the County would -be
entitled to the associated percentage of the At Risk Amount (based on the Service Penalty) as a
Service Credit to be accrued monthly (net of any Earnback Credits) and reconciled annually.
The Service Credit is capped and not to exceed an At Risk Amount of 10% of the monthly fees
.paid to CGI for any and all failures during the measurement .period in which CGI's respective
performance was below the Minimum Service Level. In no month will the aggregate Service
Credit for all failures be greater than this amount.
Earnback Credits provide incentive for CGI to exceed the County's expectations on a sustained
and consistent basis. Earnback Credits are awarded at 50% of the Service Credit when CGI
meets or exceeds -the 'Exceeded Service Level target in a rolling three (3) consecutive months
and can only be applied against Service Credits owed to the County in the current bill period
or subsequent months equal to the timeframe over which the Earnback Credit was awarded.
Once applied, the period for measuring Eamback Credits is reset.
D. Service Metrics
Exceeded
Service
Level
Environment Metrics
Infrastructure Availability Uptime 10% 98.5% 99.5%
(Data Center/ Hardware) Percentage
Application Metrics
CGI Advantage General Availability 5% 99% 99.5%
Application Availability Percentage
CGI infoAdvantage and Availability
111360 Application 3% 98.5% 99.5%
Percentage
Availability
CG1 Advantage Vendor Self Availability 5% 98.5% 99.5%
Service Percentage

13082 Exhibit B-2
Managed Advantage Plan Services
tointlInt Exceeded
Service Metric Applicability Set-vice SenTice Service
Factors Penalty Level Level
CGI Advantage Batch Batch
Processing 5% 98.5% 99%
Execution Time Time
Response Time Metrics (1,2)
Target Status Update: Workaround/
60 minutes Resolution
Critical Severity Issue 5% Target Workaround or Time:
Resolution: 48 business
72 business hours hours
Target Status Update:
120 minutes 'Workaround/
Serious Issue 3% Target Workaround or -Resolution
Severity Time: 72
'Resolution: business hours
96 business hours
Disaster Recovery Targets
Recovery Time Objective n/a 8% Within 72 hours of a n/a
(RTO) declaration of disaster
Recovery Point Objective n/a 8% No greater than 1 business nJa
(RPO) day loss of data
.User Profile Maintenance Metrics
User Profile Updates,
including creation and Within 4
modification. Excludes, both Within 1 business day business hours
in frequency and turnaround n/a 1% of receipt of request of receipt of
requirements, user ID and request
password resets.
Within 2
User Profile Disabled n/a 4% Within 4 business hours business hours
of receipt of request of receipt of
request
General Metrics
CGI Advantage non- ri/a 2% Within 2 business days Within 1
production database business days

13082 Exhibit B-2
Managed Advantage Plan Services
Exceeded
Service
Level
populated from production (3) of receipt of
request
Within 4
Critical/Serious production Within 1 business day business hours
code migration (4) of receipt of request of receipt of
request
n/a 2%
Within 2
Moderate/Minor production Within 4 business days business days
code migration of receipt of request of receipt of
request
Footnotes:
(I) Target Customer Status Update Time is as noted or as agreed upon between the parties. Both parties
agree that providing status updates is not to take priority over resolving the respective situation if
there are competing dependencies. A reasonable workaround would trigger re-evaluation of the
respective Severity. Should an Issue arise that cannot reasonably be addressed within the Target
timeframe, both parties agree to collaborate on a mutually agreed upon action plan that will then
govern its resolution.
(2) The times set forth for response tinie metrics shall commence upon the earlier of the time at which the
County gives notice to CGI via the contact point, or CUT identifies the Issue.
(3) Will be undertaken with priority as soon as possible upon receipt of such requests if associated with
resolution of Critical or Serious Issues.
(4) Will be undertaken for same night batch processing whenever relevant and reasonable.

13082 Exhibit B-2
Managed Advantage Plan Services
Attachment 1: CGI Advantage Sizing — Usage Levels
Total Users 600
Estimated Concurrent Users 100
Annual Data Growth Rate 5%
Estimated Number of Financial Documents Per Month 5,417
Estimated Number of Disbursement Checks per Month 6,000
Advantage Procurement and VSS
Total Users 5,500
Estimated Concurrent VSS Users 55
Annual Data Growth Rate 5%
(Cl Adigaittage-Perfermeance udgeting
Total Users 175
Estimated Concurrent Users 100
Annual Data Growth Rate 5%
Total Users 381
Estimated infoAdvantage Concurrent Users 100— 150
Estimated E1360 Concurrent Users 25
Estimated peak number of concurrent reports executed 5

13082 Exhibit B-2
Managed Advantage Plan Services
Attachment 2: CGI Advantage Customization Specifications
Exhibit B-5 (Project Implementation Services) allocates 5,000 hours to the performance of Customizations
by CGI. The hours allocated under Exhibit B-5 are the basis for determining the effort to subsequently
support these Customizations after the Live Date through the Services performed under this Statement of
Work.
The Parties shall attach the final list of Customizations to be supported under this Statement of Work to this
Attachment 2 through a Change Order process once the determination is made by the Parties during the
execution and undertaking of the upgrade under Exhibit B-5 and this Statement of Work.

Contract 13082, Exhibit B-3
Proprietary Software License Agreement
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND
SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED OR ADDED AND PRICING
ADJUSTED).
1.0 Current Licensed Software. The County is currently licensing the following computer
software components, comprising the Software:
Li CGI Financial
1.2 CG1 infoAdvantage
2.0 Current Bundled Software Products. Included with the current licensed products is the
following third party software products "Bundled Software Products" required to be used in
connection with Advantage Software, unless otherwise noted. CGI is providing the following
Bundled Software Products to the County:
2.1 Business Objects Ent Professional for QRA and Weblntelligence — 50 named users
2.2 Business Objects Desktop Intelligence — Thick Client — 50 Users
2.3 Business Objects Professional for QRA and WebIntelligence — 4 CPU server
[NOTE: All Business Objects licenses are restricted use]
2.4 Pervasive Data Integrator Developer License - I
2.5 Pervasive Standard Engine 7.5.5 Win/ENT - 1
The Advantage Software and Bundled Software Products above will be replaced with the
products below in Sections 4 and 9 according to the cutover schedule as provided in the
Statement of Work.
3.0 New ,icensed Software. CGI is licensing to the County the following computer software
components, comprising the Software:
3.1 CGI Advantage® Financial Management System 3.10 (platform/database) including:
3.1.1 CGI Advantage Grants Lifecycle Management
3.1.2 CGI Advantage Inventory Management
3.1.3 CGI Advantage Asset Management
3.2 CGI Advantage Procurement Professional including
CGI Advantage Vendor Self-Serve
CGI Advantage Performance Budgeting Formulation
3.3.1 CGI Advantage Salary and Benefits Forecasting
3.4 CGI infoAdvantage End User Bundle
3.5 CGI infoAdvantage Dashboard
CGI Advantage Software will be provided via an electronic download from the CGI website.
4.0 Licensed Documentation. The Specifications for the Software are as set forth in the
documentation, which is available for download on the CGI website and which is collectively
referred to in this Agreement as the "Documentation":
4.1 Documentation for Advantage Financial
4.2 Documentation for Advantage Procurement
4.3 Documentation for Advantage Performance Budgeting
4.4 Documentation for infoAdvantage
4.5 CGI will provide the County access to its Documentation on the CGI website,
hups://sc.cgi.com/advantage/

4.6 Documentation for Bundled Software Products is available on the applicable third party
website.
5.0 License Type. The Software is licensed to the County on the following basis:
5.1 The Advantage Software is licensed to the County assuming a County operating budget
between $2 billion per year and $4 billion per year. Should the County's actual
operating budget exceed $4 billion per year, additional license fees may apply;
5.2 The County is permitted to use the Advantage Software in support of Advantage
Financial System at CGI's facility in Phoenix, Arizona as described in Exhibit B.;
5.3 In the event CGI is no longer providing Services to the County under Exhibit B, the
County is granted a site license for use of the Advantage Software in support of the
County at a County facility designated in writing at that time, and in the event of a
failure of the computers at County's facility, use at a back-up computer facility in the
United States until operations at the County's primary facility have been restored. The
County may purchase additional licenses at COI's then current prices for use at any
additional facilities; and,
5.4 Notwithstanding the foregoing site license, the County's use of infoAdvantage is
unlimited as to users.
6.0 Work That Ma Be Processed. The County may only use Software to process the County's
own work. Data from processed by systems other than Advantage may be used in
infoAdvantage except for data processed in the SAP 1-3RP System.
7.0 License Fee. Fees for the license the specified in this Exhibit B-4, are included in Exhibit A,
Payment Schedule for a License Fee as set forth in Exhibit
8.0 Warranty Period. The Warranty Period for the Software is a period of ninety (90) days
beginning on the date CG1 has successfully completed CGI's standard installation test following
delivery of the Software to the County.
9.0 Bundled Software Products. Included in the license fees set forth in Section 5 of this
Attachment A are the license fees for certain bundled third party software products (the
"Bundled Software Products") required to be used in connection with Advantage Software,
unless otherwise noted. CG1 is providing the following Bundled Software Products to the
County: **
9.1 Adobe LiveCycle Output 10 License - Per CPU —2 CPUs for Production [Governed by
Shrink-wrap License]
9.2 Adobe LiveCycle Output 10 License - Per Server — 1 Server for Non-Production
[Governed by Shrink-wrap License]
9.3 Pervasive Data Integrator Universal Developer — 2 Licenses (2 Cores each)
9.4 Pervasive Data Integration Universal Engine — Production 4 Cores
9.5 Pervasive Data Integration Universal Engine — Non-Production 4 Cores
10.0 SAP BusinessObjects — Unrestricted Licenses below:
10.1 BA&T SAP BusinessObjects Business Intelligence Platform X13.1 SP5 Unrestricted —
150 Concurrent Users
10.2 BA&T SAP BusinessObjects Business Intelligence Platform X13.1 SP5 Unrestricted —
25 Named Users

10.3 BA&T SAP BusinessObjects Web Intelligence XI 3.1 SP5 Unrestricted - 150 Concurrent
Users
10.4 BA&T SAP BusinessObjects Dashboard XI 3.1 SP5 Unrestricted —150 Concurrent Users
10.5 BA&T SAP BusinessObjects Explorer XI 3.2 — 25 Concurrent Users
10.6 BA&T SAP BusinessObjects Int. Platform Mobile add on XI 3.1 SP5 —25 Concurrent
Users
10.7 SAP Application Standalone Business Analytics Professional User — 2 named users
10.8 SAP Application Standalone BI Limited User - 23 named users
[Note: An Unrestricted Data License allows the County to use Business Objects with
data processed by systems other than Advantage except for data processed in the SAP
ERP System (see SAP Software Use Rights Agreement at
).
10.9 Finite Matters, Ltd. PatternStream® with FrameScript - I Runtime/Developer License
10.10 Versata Logic Server — 1 Site license
10.11 Versata Designer Studio — I Named User License
10.12 IBM WebSphere Application Server Network Deployment — 1260 IBM Processor Value
Units Sub-Capacity [See Schedule A.1 for additional terms]
10.13 IBM WebSphere Application Server Processor — 560 IBM Processor Value Units
Sub-Capacity [See Schedule A.1 for additional terms]
11.0 Annual Subscription Products
11.1 Convey Desktop - l users based on 3000 transactions [Governed by Shrink-wrap
License]
11.2 Liason (Hubspan) Punch Out — up to 25 suppliers [See Attachment B of this Exhibit for
additional terms]
** The Bundled Software will be reviewed after the Envision Phase. Final adjustments to the
products and quantities will be made at that time.
All rights of the County in and to the Bundled Software Products will be governed by the terms
and conditions of this Agreement, unless otherwise specified above. CG1 does not itself give or
make any warranty of any kind with respect to the Bundled Software Products. Changes in the
Software which CGI may make from time to time may make it necessary for the County to
acquire, at its own expense, updated versions of the Bundled Software Products.

Contract 13082, Exhibit B-3
Attachment A
Additional Terms for IBM Sub-Capacity License
1.0 Definitions
1.1 Audit Report Period — The period that begins on the first day in a calendar quarter and ends
on the last day in the calendar quarter. Alternatively, if your fiscal year is different from the
calendar year, you may choose to begin the period on the first day in your fiscal quarter and
end on the last day in your fiscal quarter. This period may also be monthly or weekly
depending on your requirements.
1.2 Audit Reports — A set of reports available in the IBM License Metric Tool ("mmT"), or by
another method acceptable to IBM as specified at
http://www.ibm.com/software/lotus/passportadvantage/subcaplicensing.html, These reports
provide the Processor Value Unit ("PVU") license requirements based on the Virtualization
Capacity available to the Eligible Sub-Capacity Product.
1.3 Eligible Sub-Capacity Product — A Product for which Sub-Capacity Licensing is available.
See listing at http://www.ibm.com/software/lotus/passportadvantage/subcaplicensing.html .
1.4 Eligible Virtualization Environment — A server or a group of servers cooperating as a
single computing entity that contain an Eligible Processor Technology, an Eligible Operating
System Technology, and an Eligible Virtualization Technology;
1.5 Eligible Operating System Technology — An operating system for which Sub-Capacity
Licensing is available. See listing at:
http://www.ibm.com/software/lotus/passportadvantage/subcaplicensing.html .
1.6 Eligible Processor Technology — A processor technology for which Sub-Capacity Licensing
is available. See listing at:
http://www.ibm.com/software/lotus/passportadvantage/subcaplicensing.html .
1.7 Eligible Virtualization Technology — A virtualization technology for which Sub-Capacity
Licensing is available. An Eligible Virtualization Technology is capable of restricting
processor capacity to a subset of the total physical capacity, sometimes referred to as
partition, LPAR, or virtual machine. See listing at:
http://www.ibm.com/software/lotus/passportadvantage/subcaplicensing.html
1.8 Full Capacity — The total number of physical processor cores activated and available for use
by the Eligible Sub-Capacity Product(s) on a server.
1.9 Processor Chip — Electronic circuitry containing one or more Processor Cores that plugs
into a Processor Socket.
1.10 Processor Core(s) — A physical functional unit within a computing device that interprets
and executes program instructions and consists of at least one instruction control unit and
one or more arithmetic and logic units. A multi-core technology allows two or more
Processor Cores to be active on a single Processor Chip. A System z Integrated Facility
for Linux (IFL) engine is considered a single Processor Core.
1.11 Processor Socket — Electronic circuitry that accepts a Processor Chip.
1.12 Processor Value Unit(s) — A metric used by IBM to assign a value to a Processor Core.
The Processor Value Unit licensing model is described at:
http://www.ibm.com/software/lotus/passportadvantage/pvu licensing for customers. ht
ml
1.13 Service Provider — an entity that provides IT Services for end user customers, either
directly or through a reseller.
1.14 Sub-Capacity Licensing — Licensing of Eligible Sub-Capacity Products based on
Virtualization Capacity.

1.15 Virtualization Capacity — the highest peak processor capacity available to an Eligible
Sub-Capacity Product when deployed on an Eligible Virtualization Environment. Rules
for calculating the Virtualization Capacity for each Eligible Virtualization Environment
can be found at
http://www.ibm.com/soft are/lotus/passportadvantage/subcaplicensing.html .
2.0 Authorizations
2.1 A Proof of Entitlement (PoE) must be acquired by you for the total number of PVUs
associated with the Virtualization Capacity available to an Eligible Sub-Capacity Product.
2.2 Prior to an increase in an Eligible Sub-Capacity Product's Virtualization Capacity, you must
first acquire additional authorizations, including Subscription and Support, if applicable.
2.3 IBM does not give credits or refunds for charges already due or paid if an Eligible Product's
use falls below the authorized level of use.
3.0 IBM's Responsibilities
IBM will make available and authorize you to use:
3.1 The IEMT at no charge, when ordered by you. IBM provides the ILMT to you for your
compliance with these Sub-Capacity Licensing terms; and
3.2 The Information Center included with the ILMT to aid in your compliance with these Sub-
Capacity Licensing terms.
You may make copies of the 1LMT and Information Center for your compliance with these Sub-
Capacity Licensing terms.
4.0 Customer's Responsibilities under Sub -Capacity Licensing Terms.
While using Sub-Capacity licensing, you must agree to:
4.1 Install and configure the most current version of the IBM License Metric Tool ("ILMT") in
accordance with the 1LMT Information Center, within 90 days of your first Eligible Sub-
Capacity Product deployment on an Eligible Virtualization Environment, to enable the
collection of Virtualization Capacity data by Eligible Sub-Capacity Products and generate
Audit reports in accordance with the Sub-Capacity Licensing terms. Exceptions to this
requirement are:
4.1.1 when the ILTM does not yet provide support for your Eligible Virtualization
Environment;
4.1.2 if your enter Enterprise has fewer than 1000 employees and contractors, and you
are not a Service Provider, nor have you contracted with a Service Provider to
manage their Eligible Virtualization Environment;
4.1.3 If the total physical capacity of your Enterprise servers with an Eligible
Virtualization Environment, measured on a Full capacity basis, but licensed
using sub-capacity terms is less than 1,000 PVUs.
4.1.4 When your servers with Eligible Sub-Capacity Products are licensed to the Full
capacity of the servers.
For these exceptions, use of the IMLT, while recommended, is not required for Sub-Capacity
Licensing. In lieu of the ILMT, you are required to manually manage and track your
Eligibility Virtualization Environment, and manually prepare Audit reports documenting the
Virtualization Capacity by Eligible Sub-Capacity Product for their Eligible Virtualization
Environment during each calendar or fiscal quarter. These Audit reports must contain the
information listed in the example Audit Report available at
. These Audit
Reports- must be prepared as frequently as is required to maintain a history of increase to

CVirtualization Capacity, but no less often than once per quarter and must be maintained for
at least two years to demonstrate your ongoing complilance with Sub-Capacity Licensing
terms;
4.2 Promptly install new versions, releases, modification, or code corrections ("fixes") of the
IMLT that IBM makes available. You will need to subscribe to Tivoli Support notification
via http://www.ibm.com/support/mynotifications in order to be notified when these become
available;
4.3 generate, using ILTM or manually, Audit Reports at least each calendar or fiscal quarter and
retain for a period of not less than two years the Audit Reports and make these reports
available to IBM upon notice as specified in Section 2. Failure to generate Audit Reports or
make Audit reports available to IBM will result in charging you for Eligible Sub-Capacity
Products under Full Capacity terms;
4.4 assign a person in your organization with authority to manage and promptly resolve any
questions on Audit reports or inconsistencies between Audit Report contents, license
entitlements, or ITLM configuration;
4.5 Notify CGI if Audit Reports reflect Eligible Sub-Capacity Product use in excess of their
authorized level. You agree to promptly submit an order to IBM including Subscription and
Support coverage based on the date you exceeded your authorized level.
5.0 Compliance Verification.
Upon reasonable notice, IBM may verify your compliance with this Amendment and for all
Eligible Virtualization Environments in which you uses or installs Eligible Sub-Capacity
Products subject to the terms of this Amendment for any purpose. Such verification will be
conducted in a manner that minimizes disruption to your business and may be conducted your
premises, as IBM determines, during normal business hours. IBM may use an independent
auditor to assist with such verification, provided IBM has a written confidentiality agreement in
place with such auditor.
The Customer will create, retain, and provide to IBM and its auditors written records, system
tool outputs, evidence of the license entitlements provided to you, and other system information
sufficient to provide auditable verification to IBM that your installation and use of Eligible Sub-
Capacity Products is in compliance with the terms of this Amendment, including, without
limitation, all of IBM's applicable licensing and pricing qualification terms.
IBM will notify you in writing if any such verification indicates that you have used Eligible Sub-
Capacity Products in excess of your authorized level of use or you are otherwise not in
compliance with this Amendment. You agree to promptly pay directly to IBM i) the charges as
IBM specifies in an invoice for any additional licenses equal to the quantity used in excess of
authorized level of use and applicable Subscription and Support offerings, as applicable, for such
licenses for the lesser of the time that such licenses have been used or two years, and ii) any
additional charges and other liabilities determined as a result of such verification
The rights and obligations set forth in this section remain in effect during the period the Eligible
Sub-Capacity Product is licensed to you, and for two years thereafter.
6.0 Additional Terms
Product deployments that are not able to meet these Sub-Capacity Licensing requirements must
be licensed using Full Capacity terms.
IBM may change the terms of this Amendment by giving you written notice. These changes will
be effective at the next 12 month anniversary of your TD containing "Eligible Sub-Capacity
Products". Otherwise, for a change to be valid, both of us must sign it. Additional or different
terms in any written communication from you are void.

Contract 13082, Exhibit B-3
Attachment B
Additional Terms for Liaison (flubspan) Punch Out License
(see attached pdf, to be merged into final Exhibit B-3 Attachment B)

PAN
13082 Exhibit B-3 Attachment B.1
TERMS OF SERVICE — The County of Maricopa
FITNESS FOR ANY PARTICULAR PURPOSE, OR NON INFRINGEMENT.
(c) Disclaimer of Actions Caused by and/or Under the Control of Third
These Terms of Service (Terms) apply to the Hubspan Service provided Parties. HUBSPAN DOES NOT AND CANNOT CONTROL THE FLOW OF
to Customer, as described in the associated Hubspan, Inc. Service DATA TO OR FROM HUBSPAN'S INTERNET HOSTS AND OTHER
Agreement Sections 1 and 2. PORTIONS OF THE INTERNET. SUCH FLOW DEPENDS IN LARGE
1. Service and Software. PART ON THE PERFORMANCE OF INTERNET SERVICES PROVIDED
(a) License. Hubspan hereby grants Customer a limited, OR CONTROLLED BY THIRD PARTIES. AT TIMES, ACTIONS OR
non-exclusive, non-transferable license to use any software that is provided INACTIONS CAUSED BY THESE THIRD PARTIES OR ACTS OF GOD
as a standard part of the Hubspan Service or is custom developed for CAN PRODUCE SITUATIONS IN WHICH HUBSPAN'S OR CUSTOMER'S
Customer (Hubspan Software) solely for Customer's internal use of the CONNECTIONS TO THE INTERNET (OR PORTIONS OF IT) MAY BE
Hubspan Service. Hubspan hereby grants to Customer a limited, IMPAIRED OR DISRUPTED. EXCEPT TO THE EXTENT CAUSED BY
non-exclusive, non-transferable license to use the Hubspan Service solely HUBSPAN, HUBSPAN DISCLAIMS ANY AND ALL LIABILITY
for its internal business purposes. Customer hereby grants to Hubspan a RESULTING FROM OR RELATED TO SUCH EVENTS.
limited, non-exclusive, royalty free license to use Customer's data, 6. Indemnification. Hubspan will defend, at its expense, any action brought
information, text and other relevant information provided by Customer against Customer based upon a claim that the Hubspan Service or the
(Content) solely for the purposes of fulfilling Hubspan's obligations under Hubspan Software used within the scope of Customer's license directly
this Agreement. infringes a patent, trade secret, trademark or copyright of a third party.
(b) Ownershjp. As between Hubspan and Customer, Hubspan Customer will not be liable for any action based upon a claim that the
has sole ownership of all right, title and interest in and to any Hubspan Hubspan Service or the Hubspan Software used within the scope of
Software, the Hubspan Service, Hubspan's trademarks, all Fiubspan Customer's license directly infringes a patent, trade secret, trademark or
supplied material and know-how developed for use in connection with this copyright of a third party. Customer will defend, at its expense, any action
Agreement or generated by provision of the Hubspan Service generally, brought against Hubspan that the Content directly infringes a patent, trade
and any templates provided by Hubspan in connection with the Hubspan secret, or copyright of a third party. The indemnified party must notify the
Service, and Customer has sole ownership of all right, title, and interest to indemnifying party promptly in writing of such claim and give the
the Customer's Content. indemnifying party all authority, information and assistance, at the
(c) Restrictions, Customer may not lease, loan, rent, resell, indemnifying party's expense, reasonably necessary to settle or defend
sublicense or distribute the Hubspan Service to any third party, use the such claim, and the indemnifying party shall have sole control of any such
Hubspan Service for the benefit of any third party or otherwise use the action or settlement negotiations. Each party further agrees to pay all
Hubspan Service on a service bureau basis. Customer shall not modify, damages and costs finally awarded against the indemnified party
alter, copy (except as necessary to maintain Customer's web site), create attributable to such claim. If the Hubspan Service or the Hubspan Software
derivative works of, disassemble, reverse engineer, distribute, rent, resell, becomes, or in the opinion of Hubspan may become, the subject of a claim
sublicense, sell, loan, or lease the Hubspan Software. Customer shall not of infringement, Hubspan may procure for Customer the right to use the
remove any proprietary notices or branding from the Hubspan Software or Hubspan Service or the Hubspan Software free of any liability replace or
any other materials provided to Customer by Hubspan under this modify the Hubspan Service or the Hubspan Software to make its use
Agreement. non-infringing, or if neither of these alternatives are commercially
(d) Intentionally Left Blank. reasonable, terminate Customer's use of the Hubspan Service or the
2. Proiect Plan. Hubspan will make good faith efforts to complete Hubspan Software. THE FOREGOING STATES THE SOLE AND
implementation of Trading Partners within Customer's timing objectives. EXCLUSIVE LIABILITY OF EACH PARTY FOR THIRD PARTY
Upon mutual agreement of any Project Plan, it shall become the basis for INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS.
evaluating project status. All changes to the Project Plan require written 7. Confidentially. Confidential Information means any proprietary
acceptance by both Customer and Hubspan and must include impact on information, technical data, trade secrets or know-how of the disclosing
the Project Plan and this Agreement. party, including, but not limited to, research, product plans, products,
3...Intentionally Left Blank. services, suppliers, customer lists, prices and costs, markets, or other
4. Intentionally Left Blank business or technical information of the disclosing party that is designated
5. Warranty; Disclaimer. to be confidential or proprietary or which reasonably appears to be
(a) Warranty. Hubspan warrants that it will provide the Hubspan confidential or proprietary. Confidential Information will not include anything
Service in a manner consistent with industry standards and in accordance that is already in the possession of the receiving party without obligation of
with the Terms of this Agreement. Hubspan represents and warrants that confidence, is independently developed by the receiving party without use
Hubspan has the right to license the Hubspan Software and other materials of Confidential Information, becomes available to the general public without
provided to Customer under this Agreement. breach of these Terms, or is rightfully received by the receiving party from a
(b) Disclaimer of Other Warranties. EXCEPT AS OTHERWISE third party without obligation of confidence. To the extent permitted by law,
PROVIDED IN SECTION 5(a), HUBSPAN MAKES NO each party agrees that for a period of 3 years following the date of such
REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR party's receipt of Confidential Information from the other party, the receiving
IMPLIED, WITH RESPECT TO THE HUBSPAN SERVICE, HUBSPAN party will hold all Confidential Information in strict confidence and not
SOFTWARE OR THE FUNCTIONALITY, PERFORMANCE OR RESULTS disclose it to others or use it in any way except in performing the receiving
OF USE OF IT. WITHOUT LIMITING THE FOREGOING, HUBSPAN party's obligations under these Terms, and take all action reasonably
DOES NOT WARRANT THAT THE HUBSPAN SERVICE OR THE necessary to protect the confidentiality of the Confidential
HUBSPAN SOFTWARE IS OR WILL BE ACCURATE, ERRORFREE OR
UNINTERRUPTED OR MEETS OR WILL MEET CUSTOMER'S
REQUIREMENTS. HUBSPAN MAKES NO IMPLIED WARRANTIES OF
ANY KIND, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY,
Ver Date 09/29/2009 Page 1
Copyright 0Hubspan, Inc.
Document Number HSTERM 09.29.2009.RI
Document Owner: Dan Wassel

13082 Exhibit B-3 Attachment B.1
Information. Upon request, the receiving party agrees to promptly return or Service Agreement as if the taxes did not exist. In the event of a conflict
destroy all Confidential Information provided by the disclosing. between these Terms and the Service Agreement, the Service Agreement
8. Intentionally Left Blank. terms shall control. The parties' relationship is that of independent
9. LIMITATION ON LIABILITY. TO THE MAXIMUM EXTENT PERMITTED contractors and not that of employer-employee, partner, agent or
BY APPLICABLE LAW, UNDER NO CIRCUMSTANCES AND UNDER NO otherwise. The obligations of Sections 1(b), 5(b-c), 7, 9, and 10 will survive
LEGAL THEORY, TORT, CONTRACT OR OTHERWISE, SHALL EITHER any termination of this Agreement. Neither party may assign its rights or
PARTY HAVE ANY LIABILITY TO THE OTHER OR ANY OTHER THIRD duties in this Agreement without the prior written consent of the other party,
PARTY FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR except that either party may assign such rights or duties without such
CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, consent in connection with any transaction in which more than 50% of such
WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, party's voting securities are transferred or substantially all of such party's
COMPUTER FAILURE, OR ANY AND ALL OTHER DAMAGES OR assets are purchased. All terms and provisions in this Agreement shall be
LOSSES, EXCEPT FOR INDEMNIFICATION OBLIGATIONS ARISING binding up,on and inure to the benefit of the parties and their permitted
UNDER SECTION 6, IN NO EVENT WILL EITHER PARTY BE LIABLE assigns. This Agreement shall be construed and enforced in accordance
FOR ANY DAMAGES IN EXCESS OF TOTAL PAYMENTS MADE BY with the laws of the State of Arizona, except for its conflict of laws
CUSTOMER DURING THE TWELVE provisions.
(12) MONTH PERIOD PRECEDING THE EVENT OR CIRCUMSTANCES
GIVING RISE TO SUCH LIABILITY, EVEN IF EITHER PARTY SHALL 11. Data Archivina. Hubspan reserves the right to archive certain data
HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES, beginning 60 days after transaction date.
OR FOR ANY CLAIM BY ANY OTHER PARTY.
10. Miscellaneous. Any notices must be given in writing to the other party at
the address on the Order Form, and shall be deemed given immediately
upon personal delivery, 3 days after deposit in the United States mail by
certified or registered mail, 1 day after overnight express courier; or 1 day
after transmission by fax. This Agreement constitutes the full and complete
understanding of the parties and supersedes all prior understanding and
agreements. Any waiver, modification or amendment of any provision of
this Agreement shall be effective only if in writing and signed by the parties.
Other than net income taxes imposed on Hubspan, Customer will bear all
taxes, duties, and other governmental charges (collectively, "taxes")
resulting from the associated Service Agreement. Customer will pay any
additional taxes as are necessary to ensure that the net amounts received
by Hubspan after all such taxes are paid are equal to the amounts that
Hubspan would have been entitled to in accordance with the associated
UlEarrAMEMItAl:10.53VAMEZ-ZiE.
Ver Date 09/29/2009 Page 2
Copyright ©Hubspan, Inc.
Document Number HSTERM 09.29.2009.RI
Document Owner: Dan Wassel

13082 Exhibit B-3 Attachment B.2
.-;PAN
Hubspan Service Level Agreement for Maricopa County
This Service Level Agreement provides definitions used b) Hubspan shall provide at least 48 hours advance notice for
throughout the document, defines Priority Levels relative to any Scheduled Maintenance. Hubspan will make all
Technical Support, and includes details relative to Technical commercially reasonable efforts to schedule maintenance
Support Services. In addition, this document defines during off business hours, Pacific Time.
exclusions to Hubspan's Service. c) Hubspan may schedule maintenance to remedy any Level
1 Issue (Emergency Maintenance) with no advance notice.
L. Definitions All commercially reasonable efforts will be made to
Downtime — Loss of service availability for 15 minimize impact of any Ernergency Maintenance on the
consecutive minutes or a total of 60 minutes during a eight Hubspan Service and Customer.
(8) hour work day. IV. Issue Reporting
Emergency Maintenance — Unscheduled maintenance a) For each request by Customer for Technical Support
to remedy any from Hubspan, Hubspan may request Customer provide a
Level 1 Issue, if necessary. Hubspan will provide no description (Issue Report) of the Issues encountered,
advance notice in the case of Emergency Maintenance including a description of how to repeat the condition that
issues. brought about the issue.
External Causes — Causes beyond the control of b) Hubspan shall identify each outstanding Issue
Hubspan, including, but not limited to fire, acts of God, relating to an Issue Report with a unique "Case Number"
strike, riot, war, terrorism, weather, interruption or failure for tracking purposes. Case Numbers shall be
of telecommunication or digital transmission links and communicated to the Customer promptly after receipt of
Internet slow-downs or failure. the Issue Report.
Level 1 Issue (High) — Any condition that renders the V. Technical Support Priority Levels a)
Hubspan Application Service inaccessible, unusable or Level 1 Issues — Hubspan shall work
inoperative, and there is no immediate Work Around. continuously, and shall use all reasonable
Level 1 Issues include loss of all transaction processing commercial efforts to diagnose and provide an
capability. estimated correction time or a Level 1 issue
Level 2 Issue (Medium) — Any condition in the Hubspan within 2 hours of notification by Customer. If the
Application Service that is not a Level 1 Issue, but that cause of the Level 1 Issue is due to substantial
affects the availability, operation or performance of the nonconformance of the Service described in the
Hubspan Service. section titled Service Level Objectives, Hubspan
Level 3 Issue (Low) — Any malfunctioning defect that shall work continuously, and shall use all
causes a departure from expected behavior of the easonable commercial efforts to implement a
Hubspan Application Service but does not affect the Work Around or a Permanent Solution.
availability or performance condition of the Application b) Level 2 Issues Hubs shall diagnose and
Service, provide an estimated correction time for a Level 2
Technical Production Support — Support required to Issue within 12 hours of no by Customer.
maintain production functionality. c) Level 3 Issues — Hubs shall provide a
Updates — Additional or replacement code or correction estimate within 20 business days of
documentation that is provided by Hubspan to remedy an notification by Customer.
Issue or minor bug. d) Downtime — Downtime shall be categorized
Work Around — A temporary resolution that restores the as a Level 1 Issue.
service and operation of the Hubspan Service without
significant loss of functionality. VI. Service Level Objective a) Technical
Technical Support Services Support — Hubspan shall use reasonable
a) Standard Technical Support Services means that commercial efforts to attempt to resolve any
Hubspan will provide phone support 24 hours a day, 7 Issues within the times described in the section
days a week, 365 days a year. Hubspan will reply to all titled Technical Support Priority Levels, for the
production support calls received via telephone within 30 relevant Priority Level, and without causing
minutes to confirm issues. Downtime. b) Service Availability — Hubspan
b) Exclusions from Technical Support Services. Hubspan shall use reasonable commercial efforts to keep
has no obligation to provide support services for any the Hubspan Service available 99.5% of the time,
hardware used by Customer in connection with use of the excluding scheduled maintenance outages and
Hubspan Service or for any defect or failure to the any loss or interruption of the Hubspan Service
Hubspan Service caused by the improper use of the due to External Causes.
Hubspan Service by Customer or other unauthorized
personnel. VII. Term and Termination
III. Updates Provided that Customer is current on all fees under the
a) Provided Customer is current on all fees under this Service Agreement, Hubspan shall provide Technical
Agreement, Hubspan shall provide Customer with Support for the Hubspan Service starting on the Effective
Updates for the Hubspan Service at no additional cost. Date of the Agreement and continuing so long as Customer
Hubspan shall notify and make the Updates electronically is subscribing to the Hubspan Service.
available to Customer upon commercial release.
Vers Date: 05/01/2008 Copyright © 2008 Hubspan Inc. Document Number: HSSLA05,01,2008.R1

13082 EXHIBIT B-4 PROPRIETARY SOFTWARE MAINTENANCE AGREEMENT
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND
SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED OR ADDED AND
PRICING ADJUSTED).
1.0 DEFINITIONS
Capitalized terms used in this Standard Maintenance Agreement will have the meanings given below
or in the context in which the term is used, as the case may be.
1.1 "Documentation" means the documentation provided by CGI for the Software pursuant to the
License Agreement.
1.2 "Enhancements" means changes or additions to the Software which CG1 develops and makes
available at no additional charge to all licensees of the Software who are under then-current
maintenance agreements.
1.3 "Software Incident" means a material deviation of the Software from the specifications for the
Software identified in the License Agreement.
1.4 "License Agreement" means the Proprietary Software License Agreement incorporated and
made part of the Contract as Exhibit B-3 pursuant to which CG1 licensed the Software to the
County.
1.5 "Maintenance Period" means the initial term of this Standard Maintenance Agreement or any
subsequent renewal period. The initial term and each renewal period is a separate Maintenance
Period. Each renewal Maintenance Period, if any, will be a period of twelve (12) months.
1.6 "Software" means the software referenced in Attachment A of the License Agreement.
2.0 MAINTENANCE
2.1 CG1 "Standard Support and Maintenance Services" provide the County with the required
ongoing enhancements to the Software to address functional and technical changes.
Specifically, the Standard Support and Maintenance Services provide these major components:
2.1.1 Internet access through our secure web site, eAccess (
), to a variety of 24x7 support materials.
2.1.2 Help Desk Support with direct phone, email, and web support on the baseline products
through the CGI County Support Center. Standard hours of operation are 8 am EST to 9
pm EST Monday-Friday. CGI can be reached at 800-321-0267 via phone and
via our online support website.
2.1.3 Software Incident corrections to the Software.
2.1.4 Software releases are provided periodically to address technical and functional
compatibility with system software and ongoing regulatory changes and changes to
business practices. Documentation updates are provided as part of each release.
Additional Software Incident corrections will be included in releases, as dictated by
testing requirements and the magnitude of the required change.
2.1.5 Enhancements to the Software are provided in new releases.
2.1.6 Membership to the CUT Advantage User Group. Membership provides the option to
participate in various user group activities such as the annual CG1 Forum, regional User

Group meetings and voting for the User Group Steering Committee that works closely
with CGI on a variety of client issues and concerns. Membership also provides each site
the option of proposing a candidate for election to the User Group Steering Committee.
2.1.7 CG1 will support the following features of the CGI Advantage solution:
2.1.7.1 The system components that the County is currently contracted for an d is
paying maintenance on;
2.1.7.2 The third-party software component releases that are compatible with the
currently supported version of the CGI Advantage solution;
2.1.7.3 The documented features of the CGI Advantage Software, as listed on the
delivered on-line documentation and help files;
2.1.7.4 All standard baseline features of the system, including configuration tables
(e.g. Required Elements) of the CGI Advantage Software, that DO NOT
include infrastructure or other programming code changes. Any client-specific
configuration tables will not be supported.
2.1.8 Prioritizations of all issues and Software Incidents according to the following schedule:
-- Severity Definition
1 - Critical A problem with CGI supported Software causing critical impact to the
client's business operation. No workaround is immediately available
and work using the Software can not continue.
2 - Serious A problem with CG1 supported Software causing significant impact to the
client's business operation. A workaround is available but is
unacceptable on a long term basis.
3 - Moderate A problem with CGI supported Software that impairs some functionality,
but a practical workaround exists.
4 - Minor A problem that does not affect any functionality of the Software.
2.2 CGI may, at its option, investigate and correct suspected Software Incidents at CGI's offices to
the extent possible. If CGI's personnel travel to County's place of business at County's request
to perform maintenance services, County will pay CGI for the travel time and the reasonable
travel and other out-of-pocket expenses of CGI's personnel. If a suspected Software Incident is
attributable to a cause other than the Software as delivered by CG1, then County will pay for
CGI's work on a time-and-materials basis. If the Software module containing the Software
Incident has been modified by non-CGI personnel, CG I will charge County on a time-and-
materials basis at CGI's then-current hourly rates for analyzing and fixing the Software Incident
in County's version, and for any installation assistance County requires.
2.3 At the expiration of the initial Maintenance Period stated in this Standard Maintenance
Agreement, County may buy maintenance services for the Software for subsequent Maintenance
Periods in which CGI is offering maintenance services, at the prices referenced in Exhibit A of
the Contract, and for any renewal Maintenance Periods not provided for in Exhibit A, at CGI's
then current prices or other mutually agreed to fees. County may obtain such maintenance
services only if (i) County has paid the maintenance fee for all prior Maintenance Periods; and
(ii) County incorporates into the Software all releases, corrections, and Enhancements to the
Software that CGI has made available to County, no less than two minor software releases prior
to current release.

2.4 All Enhancements and corrections to the Software and Documentation provided by CGI
pursuant to this Standard Maintenance Agreement will become a part of the Software and
Documentation for the purposes of the License Agreement at the time they are provided to
County and are hereby licensed to County as part of the Software and Documentation pursuant
to all of the terms and conditions of the License Agreement.
3.0 PAYMENT TERMS
County will pay the maintenance fees for the initial Maintenance Period as set forth in EXHIBIT A.
CGI will provide County with written notice of and an invoice for the maintenance fees for each
subsequent Maintenance Period at least thirty (30) calendar days prior to the expiration of the then-
current Maintenance Period. CGI will not be obligated to provide maintenance services in any
Maintenance Period (including the initial Maintenance Period) unless the maintenance fees for the
Maintenance Period have been paid in full.

13082 EXHIBIT B-5 PROJECT IMPLEMENTATION SERVICES
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND
SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED OR ADDED AND
PRICING ADJUSTED).
A. GENERAL TERMS FOR PROJECT IMPLEMENTATION
SERVICES
1. Definitions
Capitalized terms used herein but not otherwise defined shall have the meanings ascribed to the in
the Contract. The following terms as used herein shall be considered and interpreted as set forth
below.
1.1. Attachments
"Attachments" to this Exhibit B-5 means the following which are attached hereto and
incorporated by reference herein: Attachment B-5.1 (Work Breakdown Structure);
Attachment B -5.2 (Deliverable Definition Document); Attachment B -5.3 (Legacy System
Interfaces), Attachment B -5.4 (Legacy System Reports); Attachment B -5.5 (Advantage 2x
Tables); Attachment B-5.6 (Advantage 3 Project Context Diagram).
1.2. Contractor's Team
"Contractor's Team" means Contractor's resources that will perform the Services forth in this
Statement of Work. Contractor's Team shall be comprised of Contractor employees and
subcontractors. Contractor's Team shall be led by the Contractor contact as specified in the
Project Plan described below, who shall be responsible for directing the Services and Work
Products being provided to the County.
1.3. County's Team
"County's Team" means the County's employees and shall include County employees on the
project team, and will be led by the County's Project Manager and will be responsible for
completing the County's tasks in Exhibits B-2 and B-5.
1.4. Deliverable Expectation Document
"Deliverable Expectation Document" means the document that sets descriptions and
expectations for the Deliverable's content, acceptance criteria, and review complexity. When
more than one instance of a Deliverable (e.g., Interface Designs) will be delivered to the
County, a single outline will be created for the first instance of the Deliverable. The Parties
will prepare a Deliverable Expectation Document (DED) for each deliverable in the
Statement of Work prior to beginning work on each deliverable.
1.5. Go Live Date
"Go Live Date" means the date that the Advantage components are brought live into
production operations. The Project Team will determine the Go Live Date for each
Subproject during the Envision Phase. The tentative Go Live Date for Subproject I is by
October 31, 2014. All other components must go live by July 1, 2016. From an operational
perspective, the actual Go Live Date will be mutually agreed upon by the Parties and may not
occur on exactly October 31, 2014 and July 1,2016.
1.6. Subproject 1
"Subproject 1" means the implementation of Advantage 3 Performance Budgeting.

1.7. Subproject 2
"Subproject 2" means the implementation of Advantage 3 Vendor Self Service.
1.8. Subproject 3
"Subproject 3" means the implementation of Advantage 3 Financial Management and
Procurement Professional.
1.9. Project
"Project" means the Services Contractor will deliver to the County for the purpose of
upgrading to Advantage 3 as described herein. The Project is inclusive of Subproject 1,
Subproject 2 and Subproject 3.
1.10. Project Plan
"Project Plan" means the living document that describes the project roadmap, organization
and governance as well as defines the deliverable review process.
1.11. Project Teams
"Project Teams" mean both of Contractor's Team and County's Team.
1.12. Statement of Work
"Statement of Work" (or "SOW") means the scope of Services described in this Exhibit B-5.
1.13. Work Breakdown Structure
"Work Breakdown Structure" means the project planning tool used to track tasks, beginning
and end dates, durations, and responsibility of each party for each activity in the Statement of
Work. Each task in the Work Breakdown Structure uses the same paragraph number of the
Statement of Work as a cross reference preceded by a 1, 2 or 3 to signify the Subprojects of
the Project.
2. Term
2.1. Work Commencement
The Parties' respective performances under this Statement of Work shall begin on the
Effective Date of the Contract and will continue until Services are completed, unless sooner
terminated in accordance with the terms of the Contract.
3. Acceptance
Acceptance of Deliverables will be conducted in accordance with the following procedures.
3.1. Written Deliverables
Contractor may submit interim drafts of a written Deliverable ("Written Deliverable") to the
County for review. The County agrees to review and provide comments to Contractor on
each interim draft and final version within the number of days specified in the Deliverable
Expectation Document (the "Acceptance Period").
The County agrees to notify Contractor in writing by the end of the Acceptance Period either
stating that the Written Deliverable is accepted in the form delivered by Contractor or
describing in reasonable detail any material deviations from the description of the Written
Deliverable contained in the Statement of Work that must be corrected prior to acceptance of
the Written Deliverable. if Contractor does not receive any such deficiency notice from the
County by the end of the Acceptance Period, the Written Deliverable will be deemed to be
accepted. lf the County delivers to Contractor a timely notice of any deficiencies within the

timeframe set forth in §1.1.1.e (Deliverable Review Cycle) of this Statement of Work
Contractor will correct the described deficiencies within a reasonable period of time provided
that this reasonable time period does not affect the Go-Live Date. Contractor's correction
efforts will be made at no additional charge if the Written Deliverable is being developed
under a fixed-price Statement of Work. If the Written Deliverable is being developed on a
time and materials basis, Contractor's correction efforts will be made on a time and materials
basis. Upon receipt of a corrected Written Deliverable from Contractor, the County will have
a reasonable additional period of time, not to exceed five (5) business days, to review the
corrected Written Deliverable to confirm that the identified and agreed-upon deficiencies
have been corrected. The County will not unreasonably withhold, delay or condition its
approval of a final Written Deliverable.
3.2. Software Deliverables
Acceptance testing is an iterative process designed to determine whether the Software
Deliverable performs the functions described in its approved Specifications and to discover
and remove Nonconformities through repeated testing cycles. "Nonconformity" means a
Defect in a Software Deliverable that represents a Critical Issue or Serious Issue as defined
in the Contract. At least forty-five (45) days prior to the date on which Contractor is
scheduled to deliver any Software Deliverable to the County the County will deliver for
Contractor's review proposed testing procedures for the Software Deliverable, including
without limitation the detailed test scripts, test cases, test data and expected results. At least
thirty (30) days prior to the date on which Contractor is scheduled to deliver the Software
Deliverable to the County, the parties will agree upon the testing procedures for the Software
Deliverable (the "Acceptance Tests" or "Acceptance Testing").
a. The "Acceptance Test Period" for each Software Deliverable will be thirty (30) days. The
Acceptance Test Period for each Software Deliverable will begin when Contractor has
completed and delivered the Software Deliverable to the County, successfully completed
Contractor's installation test and notified the County that the Software Deliverable is
"Ready for Acceptance Testing."
b. The County will start to perform Acceptance Testing on each Software Deliverable
promptly after receiving Contractor's notice that the Software Deliverable is ready for
Acceptance Testing. County's Acceptance Testing will consist of executing test scripts
from the Acceptance Tests during the Acceptance Test Period. If the County determines
during the Acceptance Test Period that the Software Deliverable contains a Defect, the
County will send Contractor a written notice Reporting the alleged Defect, promptly, but
in any event within ten (10) days of identification of the Defect. A Defect will be
considered "Reported" only if it is described to Contractor in sufficient detail to allow
Contractor to recreate it. If the Defect constitutes a Nonconformity, the Contractor will
modify the Software Deliverable to remove any Reported Nonconformity and will work
diligently to provide the modifications to the County for re-testing promptly after
receiving notice from the County. The County will then re-test the modified portions of
the Software Deliverable promptly after receiving the modifications from Contractor. If
the County identifies the same Nonconformity, the Contractor shall promptly fix the
Nonconformity. Correction efforts will be based on the priorities for correction of
Nonconformities established by the County and Contractor relative to the Go-Live Date.
c. Contractor and the County each agrees to work diligently to achieve acceptance of
Software Deliverables at the earliest possible date, and the County will work diligently to
put the Software Deliverable in live production operations following acceptance.

d. Contractor's modifications made will be made at no additional charge if the Software
Deliverable is being developed on a fixed-price basis.
3.3. Interim Acceptance
Following Acceptance Testing of Advantage 3 being implemented under this Exhibit B-5,
"Interim Acceptance" will take place when any one of the following events occurs: (i) the
County gives Contractor written notice of acceptance; (ii) the County first uses Advantage 3
or any substantial portion of it in Go-Live production operations; (iii) the Acceptance Test
Period expires without the County having Reported Nonconformities; or (iv) the re-testing
period expires without the County having Reported any remaining Nonconformities.
3.4. Advantage 3 Final Acceptance
"Advantage 3 Final Acceptance" of Advantage 3 under this Exhibit B-5 will take place on
the earlier of:
(i) when all Critical Issues (as defined in Exhibit B-2) Reported during the forty-five (45)
day period immediately following Go-Live of Advantage 3 have been corrected;
(ii) the County gives Contractor written notice of Advantage 3 Final Acceptance;
(iii) the forty-five (45) day post-production period expires without the County having
Reported Critical issues; or
(iv) the expiration of the forty-five (45) day period immediately following Go-Live; provided
however, Contractor has delivered a mutually agreed upon remediation plan for any identified
Critical Issues remaining open at the end of such forty-five (45) day period for transitioning
these Critical Issues to Managed Services under Exhibit B-2 for resolution.
B. SCOPE OF IMPLEMENTATION SERVICES
1. Primary Objectives
The primary objectives of the Project are:
9 Mitigate the critical risks inherent with running the old legacy Advantage system and a
customized budget development and Managing for Results Information System (MfRIS);
• Elimination of customizations associated with the legacy system;
o Achieve the Go Live Date;
• Use best practices inherent in Advantage 3;
O Adopt business process that align with the baseline version of Advantage 3 wherever
feasible; and
• Focus on streamlining current County business processes.
2. Scope
The responsibilities, duration, start dates, and finish dates for all the tasks in this Statement of
Work are included in Attachment 13-5.1. Advantage 3 is the basis for the Project and includes
the following modules to be completed in the following sequence:
Subproject Date Advantage 3 Module Description
Subproject Start: CGI Advantage Designed to support the unique business of
1 9/30/2013 Performance Budgeting government, the web-based CGI Advantage
Performance Budgeting solution centralizes the

Subproject Date Advantage 3 Module Description
Go Live budgeting lifecycle on a secure, single platform,
Date: including budget formulation, salary and benefits
TBD, forecasting, budget book publishing, performance
tentative is management and dashboards for visual, interactive
before reporting. The result is an accurate, single source
10/31/2014 of information that streamlines the government
budgeting process and delivers real-time access to
budget and actual information for improved
analysis, funding decisions and measuring
performance.
CGI Advantage CUT Advantage infoAdvantage provides users at
infoAdvantage - to all levels with real-time access to data in
support Subproject 1 searchable on-line reports and interactive
functionality only dashboards to quickly visualize key metrics and
manage day to day operations. CGI Advantage
empowers effective decision-making by enabling
users to identify issues early and thereby taking
corrective action sooner and provides an easier
method to communicate and visualize data (via
graphs and charts).
Subproject Start: CG I Advantage Vendor CGI Advantage Vendor Self Service (VSS)
2 9/30/2013 Self Service delivers a secure, online environment for
Go Live efficiently managing vendor information,
Date: supporting the solicitation and evaluation process,
TBD submitting online invoices and providing a status
on the complete procure-to-pay cycle. The result
is a significant reduction in data entry,
reconciliation, printing and mailing costs, as well
as a broader vendor community to better leverage
buying power while leveling the playing field for
all vendors.
CG1 Advantage Vendor Self Service streamlines
vendor information management by shifting the
ownership of many day-to-day tasks to the vendor.
This approach reduces a government's
administrative support requirements while
retaining full authority over the review and
approval of vendor account information. CGI
Advantage VSS:
• Reduces administrative support
requirements for vendor information

Sub v o ect Date Advanta _. e 3 Module Description
* Increases information accuracy
* Reduces printing and mailing costs
• Provides easy access to business
opportunities for registered users and the
general public
Simplifies invoice creation while retaining
review and approval authority
Reduces help desk support requirements
through access to financial and other
transaction history
CGI Advantage CGI Advantage infoAdvantage provides users at
infoAdvantage - to all levels with real-time access to data in
support Subproject 2 searchable on-line reports and interactive
functionality only dashboards to quickly visualize key metrics and
manage day to day operations. CGI Advantage
empowers effective decision-making by enabling
users to identify issues early and thereby taking
corrective action sooner and provides an easier
method to communicate and visualize data (via
graphs and charts).
Subproject Start: CG I Advantage CGI Advantage Financial Management is a true
3 9/30/2014 Financial Management — fund based accounting system that provides
Go Live Base System organization-wide accountability through
Date: consistent accounting rules across all financial
TBD transactions. Its integrated functionality,
workflow and configurable processes supports
unique government needs including:
* Multiple budget sources
• Multi-year budgeting and funding control
• Variable funding control structures
0 Encumbrance and pre-encumbrance
accounting
0 Roll-ups for Comprehensive Annual
Financial Statements
• Flexible government chart of accounts
attributes
NOTE: Only the following business functions in Base
System will be implemented:
o General Accounting
• Budget Maintenance
• Accounts Payable

Subproject Date Advantage t, 3 Module Description
0 Cost Accounting
CGI Advantage CGI Advantage Procurement manages the
Procurement purchasing lifecycle—automating purchases
Professional online through catalog-based ordering and
automating workflow on approved processes. Its
integration with the CGI Advantage Financial
Management provides real-time budget validation,
and automated matching and payment processing
for goods or services received and accepted. With
an end-to-end business process for professionals,
vendors, and shoppers, CG1 Advantage
Procurement helps clients achieve their goals for
efficiency and accountability.
CGI Advantage CGI Advantage Asset Management provides a
Financial Management — comprehensive asset management toolset to
Asset Management manage and control fixed assets throughout their
lifecycle. CG1 Advantage Asset Management
conforms to GAAP for fixed asset accounting, and
supports summary and detailed financial reporting
of fixed assets as mandated by GASB34, GASB42
and GASB44. Asset management functionality is
seamlessly integrated with the CGI Advantage
accounting functions to:
* Verify that asset classification codes are
consistent with those in the general ledger
• Facilitate the creation of asset documents
at the time of purchase and receipt
CGI Advantage Integrated with CGI Advantage Procurement and
Financial Management — Financial Management, CGI Advantage inventory
Inventory Management Management minimizes inventory investments by
basing purchasing decisions on inventory usage
history. Transactions such as Purchase
Requisitions, Purchase Orders, and Receiver
documents automatically update the inventory
warehouse on a real-time basis whereas CGI
Advantage Inventory Management adjusts
inventory counts, prices, unit costs, and extended
costs accordingly.
CGI Advantage Inventory efficiently manages
inventory by reducing manual actions and
providing information to aid inventory
reconciliation. CG1 Advantage Inventory:
* Provides information on the availability of
stocked items and the status of stocked
requisitions
• Facilitates timely requisition processing
6 Records and services backorders

Sub ro'ect Date Advantage 3 Module Description
automatically
Minimizes inventory investments
consistent with service objectives by
basing purchasing decisions on usage
history
e Provides automated tools to assist
servicing, purchasing, and management of
the inventory
Improves financial control of the
inventory by chargebacks to the user
organization
* Facilitates financial control of the
inventory by periodic reconciliation of the
inventory balances with the physical
counts.
Integrates with bar coding applications or other
technologies to facilitate inventory management.
PunchOut Integrated with CGI Advantage Procurement,
PunchOut provides the ability to search for and
create a 'shopping cart' of items from hosted catalogs.
0 Includes basic catalog search capabilities
0 Each PunchOut Shopping Cart may
contain multiple items from a single
vendor.
• Real-time funds check and pre-
encumbrance and encumbrance
* Ability to support a variety of message
formats and protocols for PunchOut
catalogs
e Ability to create a direct payment against
a Master Agreement without creating a
release (order)
NOTE: A maximum of twenty-five catalogues will be
implemented during Subproject 3. CGI will provide
implementation support for up to five catalogues.
CUT Advantage Grants CGI Advantage Grant Lifecycle Management
Lifecycle Management helps governments achieve organization-wide
accountability and meaningful performance
measurement through functionality and best
practices specific to the public sector. The Grant
Lifecycle Management (GLM) Grantee
functionality is an integrated component of the
CG1 Advantage Financial Management solution
that supports the end-to-end business process
lifecycle of grants. CGI Advantage GLM:

Subproject Date Advantage 3 Module Desc i tion
* Provides a global view of grant
opportunities, potential grant revenue,
grant deliverables and close-out events
• Increases efficiency in the pursuit and
capture of grant funds
• Simplifies grant tracking at all
organizational levels via central repository
• Identifies patterns for missed or lost grant
funds
Improves grantor relationship by reducing
loss risk before, during and after award
• Provides more accurate and less labor-
intensive grant expenditure setup and
reporting
CGI Advantage CGI Advantage infoAdvantage provides users at
infoAdvantage - to all levels with real-time access to data in
support Subproject 3 searchable on-line reports and interactive
functionality only dashboards to quickly visualize key metrics and
manage day to day operations. CGI Advantage
empowers effective decision-making by enabling
users to identify issues early and thereby taking
corrective action sooner and provides an easier
method to communicate and visualize data (via
graphs and charts).
Enterprise Enterprise Intelligence360 provides the County
Intelligence360 (E1360) with the ability to access data across the County
through the BusinessObjects platform and
anchored by the delivered infoAdvantage data
warehouse. E1360 allows for creating and
viewing information from these universes via an
approved mobile device.
3. Project Planning and Management
Contractor will provide Project management and oversight of the Services described more fully
in §C.1 below.
4. Project Phases
Contractor uses a proven delivery methodology that is comprised of three Project Phases:
Envision, Create and Achieve, and is supported by Contractor-specific tools, utilities, templates,
checklists, and deliverables as described herein. Contractor's delivery methodology contains
multiple checkpoints within each Phase that contains activities such as the fit gap, software
design and development, integrated system testing, and user acceptance testing. Contractor also
has a prerequisite for moving from one phase to the next. Contractor will complete tasks for the
Project in the following phases, as more fully described below. The diagram below provides a
pictorial view of the Phases and the associated timeline.

= Fit Gap Complete
Create Phase activities can begin
9/30/13 1/14 = Achieve Phase activities can begin
(Go-tive, cr'i occur during this time)
2/10/14 6/16/16
9/30/16
3/31/2014 2/1/2014 7/112016
envision Phase ConflY mod Subproject 3 GoiLive
9/30/13 Complete SubprOject 2 Golivo 9/30/16
10/31/2014
—To Or Confirmed—
Subproject 1 Goilive
4.1. Envision Phase
The Envision Phase encompasses activities related to the analysis for implementing
Advantage 3. A single Envision Phase will be conducted for all business areas and
Subprojects. The Envision Phase findings (comprised of a Fit-Gap Analysis and approaches
for key project activities, such as: conversion, reports, forms, and training) are documented in
the Upgrade Analysis Document (UAD) for all Subprojects as more fully described in
Attachment B-5.2.
4.2. Create Phase
The Create Phase encompasses activities related to software construction (forms, reports,
interfaces, conversions and application software customizations /enhancements) and the
planning and execution of implementation tasks, such as, application configuration and data
set-up, testing, training, and preparations for production operations.
4.3. Achieve Phase
The Achieve Phase encompasses the activities required to support production operations of
Advantage 3. It is comprised of the production cutover activities (e.g., scheduling of daily,
weekly, monthly, quarterly, annually, and on-demand batch jobs) and post-implementation
activities, such as the monitoring of system performance in production operations.
5. Managed Services under Exhibit B -2
The Managed Services required to support Advantage 3 upon completion of this Project will be
provided under Exhibit B -2. Contractor will provide Managed Services in support of the
Advantage 3 application and associated infrastructure in a fully hosted, CGI Data Center under
the Managed Services program as described in Exhibit B-2. These Managed Services provide a
staff management and delivery model to support the Advantage 3 application and underlying
technical infrastructure.
5.1. Transition
Initially, the Managed Services will be delivered concurrently in support of the Project
("Transition Services"). These Transition Services include the completion of the Contractor
assigned technical tasks necessary to support the Project implementation process, such as the
establishment of the Project test environments and the Advantage 3 production environment.

5.2. Post-Transition
Upon the Go Live Date for each Subproject (1, 2 and 3), Managed Services will be delivered
to the County under Exhibit B-2 to maintain and operate Advantage 3 in production
operations ("Post-Transition Services") in accordance with the Service Level Agreement
(S LA) agreed upon between the County and Contractor in Exhibit B-2.
A detailed description of Managed Services and the associated Service Level Agreements are
provided within Exhibit B-2. Upon the Go Live Date for each Subproject, only the terms of
Exhibit B-2 shall apply to the Managed Advantage services for that Subproject. The Transition
and Post-Transition activities are described in Exhibit B-2.
PROJECT WORK
The Services for the Project are described below. The Services described below apply to Subproject
I, Subproject 2 and Subproject 3 of the Project unless otherwise specified. Deliverables within each
Project Phase of the Services to be provided are listed below.
1. Project Planning and Management
1.1. Project Planning
Contractor shall provide Project planning and management Services for the duration of this SOW.
Contractor will update the Work Breakdown Structure included in Attachment B-5.1 of this
SOW and include it on the monthly status report. The County will review and provide feedback
to Contractor per the project schedule. The Project Plan will consist of County and Contractor
tasks and deliverables to complete the upgrade.
1.1.1. Project Plan
Within thirty (30) days of the Effective Date of this Contract, Contractor will create a
Project Plan to define how the Contractor Project management standards and
methodologies will be applied to the Envision, Create and Achieve Phases of the Project.
Contractor will be responsible for documenting the following items in the Project Plan:
a. Project Roadmap:
Project Objectives
Scope
Assumptions
Deliverables
Overall Timeline
b. Project Standards — Processes and Tools
i. Communication
Status Reporting
Scope Management
iv. Risk and Issue Management
v. Project Documentation
c. Project Governance — Roles and Responsibilities
i. Steering Committee

Project Executives
Project Managers
iv. Project Teams
Deliverable Review:
As part of the Deliverable development process, Contractor will draft and the County will
review a Deliverable Expectation Document that sets descriptions and expectations for
the Deliverable's content, acceptance criteria, and review complexity. When more than
one instance of a Deliverable (e.g., Interface Designs) will be delivered to the County, a
single outline will be created for the first instance of the Deliverable. The outline shall be
agreed upon by the parties and approved by the County prior to the submission of a
Deliverable by Contractor for review and acceptance by the County.
Contractor will subject each Deliverable to its internal quality control process prior to
submitting the Deliverable to the County for review. Contractor will utilize the DED as
the guideline for conducting its internal quality control review.
e. Deliverable Review Cycle:
A standard Deliverable review cycle will be further elaborated in the Project Plan. This
review process is entered into when the responsible team has completed a Deliverable.
The DED will identify the review periods, if different from the project plan.
Task l'\:[..r, ,.. St .7.: )r.
Contractor Internal Review including application of quality 2 days
control standards
Update Deliverable 3 days
Submit Deliverable to County 0 days
County Review and Approve Deliverable (duration based upon High (H) = 10 days
Review Complexity) Medium (M) = 7 days
Low (L) = 5 days
Incorporate Final Comments to Deliverable (if necessary) 3 days
County Review Incorporated Changes to Deliverable (if 2 days
necessary)
Make Final Updates to Deliverable (if necessary) 1 day
Submit Final Deliverable 0 days
For each Deliverable, the County's Project Manager or their designee shall be responsible
for coordinating written comments and input from various members of the Project Team
and stakeholders. The County's Project Manager or designee shall provide a single set of
written, clear, guidance and direction to Contractor.
1.1.2. Project Kick-off
Within thirty (30) days of the Effective Date of the Contract, Contractor and the County
shall jointly plan and conduct one Project Kick-off meeting for the entire Project Team
for all Subprojects to initiate the Envision Phase . This meeting will outline Project
objectives, tasks, roles and responsibilities, and the timeline for the Envision Phase. The
Project Plan will be presented at the Project Kick-off meeting.. A separate Project Kick-

off meeting, will be held for the Subprojects at the beginning of the Create Phase to
discuss the tasks, roles, responsibilities and timeline for the Subproject.
1.2. Project Management
Contractor shall provide Project management and oversight to Contractor staff on the Project in
accordance with the Services identified herein. The ongoing Project management services to be
provided by Contractor will encompass:
a. Assigning and coordinating Contractor team resources and Deliverables
b. Tracking Contractor tasks and Deliverable budgets
c. Updating the Project Plan as necessary
d. Reporting on Contractor Deliverables including the development of monthly status
reports and presentations to the Steering Committee
e. Identifying, tracking, and helping to resolve Project issues and risks
f. Conducting quality assurance reviews of Deliverables
1.2.1. Monthly Status Reports
Contractor will submit monthly status reports to the County that include:
(1) Project status against the Work Breakdown Structure
(2) Summary of tasks, Work Products, and Deliverables by status:
Completed
In Progress
Not Completed
iv. Project issues and risks
The County shall review and provide feedback on the status reports and provide updates
to report the status of work completed by County staff within a two (2) day period after
submission for review. Documenting the status of both teams in one status report
provides for a holistic status of the Project and the Project Teams progress towards
meeting the Go Live Date. These processes will be further documented in the Project
Plan.
1.2.2. Project Team, Management and Steering Committee Meetings
The County and Contractor Project Managers and designated team leads shall have
weekly Project meetings. The Project Managers shall bring additional staff, as necessary,
to present and discuss Project progress, issues, and risks during the Project meetings.
Contractor's monthly status report to County will be used for briefing the Steering
Committee. Contractor's Project Manager will attend monthly Steering Committee
meetings and assist the County Project Manager in providing a briefing on Project status
to the Steering Committee. Contractor will assist County staff in the presentation of
other briefings that may be requested by the County in order to inform the County
departments or other stakeholders on Project status and issues escalated for their
consideration, discussion, and/or resolution.
1.3. Change Management & Communications

A Change Management Plan will be developed to guide the implementation of the Project. The
objective of the Change Management Plan will be to successfully prepare the people, processes,
work setting, hardware, software, data, procedures, and documentation for the Go Live Date. The
Change Management Plan shall include activities involving the implementation of:
a. new or revised business processes;
b. training and documentation; and
c. and testing results to assess operational readiness.
The Change Management Plan shall also include:
a. how the communication and dissemination of information regarding the various
implementation activities and changes will be handled; and
b. the strategy for conducting the Operations Readiness Assessment and the Implementation
Readiness Review.
The County will define, schedule and conduct change management and communication activities
with County departments and agencies. The County will define and document a change
management program that will be followed to communicate policy and process changes resulting
from the Project as well as provide updates to the user community and coordinate department
assigned tasks. Contractor will assist the County in the development of the Change Management
Plan based on best practices to support communications and strategies for facilitating adoption of
the upgraded system by County departments. Contractor will also support the County in the
execution of the Change Management Plan. This plan may be updated as the project progresses.
1.4. Project Repository
The County will establish a central repository for storing Project documentation, Work Products,
and Deliverables. Contractor will be responsible for making the standard Project management
tools/templates available in the Project repository for use by the Project Managers and team leads.
The County will maintain the Project repository and provide instruction to the team for its usage
throughout the Project. Documentation may also be provided to the County via e-mail, at the
County Project Manager's reasonable request.
The definitions of the Project Management deliverables assigned to Contractor for the Project are
listed in Attachment 8-5.2,
2. Envision Phase
The primary objective of the Envision Phase is to confirm the County's business requirements
and develop a blueprint for the Project. During the Envision Phase, the County's current business
requirements identified in Exhibit B-6 will be mapped to Advantage 3. Contractor will lead
prototype sessions using the Advantage 3 application and the County will be responsible for
verifying Advantage 3 functionality will meet the County's business requirements. A Fit-Gap
analysis report for supporting the County's business functions and processes in Advantage 3 is
the primary output of the prototype sessions. For the current business processes that are not
supported by Advantage 3 or via a business process change, a software customization will be
identified for the County's consideration. The Project Team will leverage baseline Advantage 3
software functionality wherever possible and minimize the software customizations. Concept
Papers will be developed for application software customizations identified during the Envision
Phase.
The Project Team will also review the current list of interfaces and reports to determine the
disposition of these software components during the Project. A Technical Assessment will be
conducted to review and finalize hardware and software requirements. The Project Team will also

develop strategies for the implementation activities, such as, data conversion and training during
the Envision Phase. The culmination of the Envision Phase activities will be the creation of the
Upgrade Analysis Document (UAD) for all Subprojects. This Deliverable will serve as the
blueprint for the Create and Achieve Phases of the Project.
The activities to be completed during the Envision Phase are described below.
2.1. Prototype Test Environment Setup
Contractor will establish a temporary prototype test environment for the Envision Phase while the
County's permanent environments are provisioned. Contractor will install the baseline
Advantage 3 application software and bundled third-party products on the hardware components
hosted in the CGI Phoenix Data Center for this temporary environment. Contractor will perform
the installation tests to confirm that these software components can be accessed and used by the
Project team for prototyping the County's business scenarios. Contractor will configure the
environment and complete the preliminary set up of System Control and Reference Tables, as
more fully described in Attachment B-5.2, to support the prototyping activities for the Project.
2.2. Business Requirements
The County will implement the best practices built into Advantage 3 when possible. The Project
Team will not document as-is business processes. The requirements listed in Exhibit B-6 will be
used to conduct prototyping. Contractor will review requirements and request any additional
information necessary from the County to conduct prototyping. The Project Team will review and
assess the functionality related to Article 5 to determine the level of effort and approach to addressing this
functionality.
Prototyping will be conducted over an eight (8) week period for all three Subprojects. Advantage 3
Performance Budgeting and Chart of Accounts functions will be analyzed early during the Envision Phase
in an effort to achieve the target Go Live Date of October 31, 2014.
2.3. Prototyping
Prototyping is the functional analysis, as more fully described in Attachment B-5.2, conducted to
determine the level of functional fit between the County's business requirements and the baseline
Advantage 3 functionality.
The process to determine the level of fit will involve the following steps:
2.3.1. Develop Prototype Scripts — The purpose of the prototype scripts is to facilitate a
structured walkthrough of the Advantage 3 application to demonstrate how the
application will be used to support the County's business requirements. Contractor will
develop prototype scripts and will setup the necessary reference tables to support
prototyping.
2.3.2. Provide Prototype Training — Contractor will provide high level training to the County
for the functions being prototyped for each Subproject. The training will be conducted
one (1) time for each business area prior to the associated business functions being
prototyped to provide just in time training for the County. This training will not be hands
on. Prototype participants shall attend the associated training for the prototype sessions
they will attend.
2.3.3. Execute Prototype Scripts — The goal of prototyping is to verify the functional fit
between the County's business requirements and Advantage 3. Contractor will execute
the prototype scripts in Advantage 3 to conduct the Fit-Gap analysis.
2.3.4. Perform Fit -Gap Analysis — The level of fit between the County's defined business
requirements and Advantage 3 will be categorized into one of the following
classifications and form the basis for the Fit-Gap Analysis. Contractor will complete the

Fit-Gap Analysis and review the results with the County. The County will review and
approve the Fit-Gap Analysis Report.
i. Functional Fit — Functionality exists in Advantage 3 to support the business
requirement.
11. Partial Fit — Functionality exists in Advantage 3 to partially support the business
requirement; changes to an existing business process or a software customization
may be required.
iii. No Fit — Advantage 3 does not have functionality to support the business
requirement, and changes to an existing business process or a software customization
may be required.
iv. The "Partial Fit" and "No Fit" items will be documented as prototype issues. During
the detailed review of the Fit-Gap analysis, Contractor and the County will select the
alternatives to address each identified prototype ssue either through changes to
business processes or software customizations.
2.3.5. Confirm business process changes and software customizations — Contractor and the
County will jointly review the business process changes and Advantage 3 software
customizations identified during the Fit-Gap Analysis for addressing the prototype issues.
Due to the configurable architecture of the Advantage 3 software, alternate configurations
or options settings will also be evaluated as alternatives to reduce the software
customizations, where possible. The level of complexity to implement each Advantage 3
software customization will be identified by Contractor. This activity will produce a list
of business process reengineering changes and Advantage 3 customizations to be
implemented during the Create and Achieve Phases.
2.4. Chart of Accounts & Budget Design
The County is responsible for documenting any Chart of Accounts or Budget design changes, as
more fully described in Attachment B-5.2, in preparation for system configuration, training and
procedures development. Contractor will provide guidance based on Advantage 3 and best
practices.
2.5. Software Analysis
The County provided Attachment B-5.3, which includes the list of the current legacy system
inbound and outbound system interfaces. Attachment B -5.3 includes the description and
purpose of the interfaces, the source and destination systems for the interfaces, the frequency, and
other available technical specifications for the interfaces. During the Envision Phase, the Project
Team will determine which interfaces will be replicated in Advantage 3.
The County provided Attachment B-5.4, which includes the list of the current legacy system
reports. Attachment B-5.4 includes the description and purpose of the reports, the frequency of
the reports/extracts, and other available technical specifications of the reports and data extracts.
During the Envision Phase, the Project Team will identify a subset of the reports that may be
replaced by the baseline Advantage 3 reports while other reports will need to be recreated to
support the County's business operations in Advantage 3.
Contractor provided Attachment B-5.5, which lists the tables currently used in Advantage 2.
The Project Team will identify which tables will be converted for the Project during the Envision
Phase. This activity only applies to Subproject 3.
2.6. Concept Papers

During the Envision Phase, Contractor will create Concept Papers, as more fully described in
Attachment B-5.2, for the application software customizations identified and approved by the
County during Prototyping. The Concept Papers will provide the detail necessary to determine
the level of effort required to develop the software customizations and allow the County to
allocate the hours budgeted for software customization appropriately. The County will use this
information to approve which software customizations will be implemented.
The County will review and approve the Concept Papers provide timely feedback and approval
per the Work Breakdown Structure.
2.7. Implementation Assessment
2.7.1.Technical Assessment
The Project Team will review the technical specifications of the Project by conducting a Technical
Assessment. This assessment will consist of a review of the County's hardware and software
requirements. If the assessment reveals any changes in the specifications then the updated sizing
information will be used to revise the technical specifications of the hardware and software needed for
implementation and operation. Any changes in hardware sizing and software requirements will result
in a Change Notice.
2.7.2.Implementation Strategies
During the Envision Phase, implementation strategies will be developed for data conversion,
system interfaces, reporting, training and documentation, and security and workflow. These
strategies will provide the framework for completing the Advantage 3 software construction,
training and documentation activities during the Create Phase. Contractor will develop these
strategies and the County will review and provide feedback to Contractor pursuant to
Attachment B -5.1.
2.7.2.1. Data Conversion Strategy - The Data Conversion Strategy will define the
approach for data conversion and data cleansing to convert data to Advantage 3. The
strategy document will discuss Contractor's proposed conversion tools that will be
used. The Data Conversion Strategy will identify the methods of converting the data
based on types of target data and the volume of data to be converted. Based upon this
high-level strategy, a cross-reference will be developed identifying the data stores in
the legacy tables (reference tables and open item tables) and the associated data stores
in Advantage 3. For each of the tables, a level of the conversion complexity will be
identified. The level of conversion complexity will be classified as one of the
following:
i. Low — There is a one to one relationship between the legacy data store
and the Advantage 3 data store. All data elements are available in the legacy
system and Advantage 3, so only data re-formatting is required. Conversion
tools will be used for Low complexity conversions.
Medium — There is a one to one relationship between the legacy
system data store and the Advantage 3 data store. There are additional fields in
Advantage 3 that need to be defaulted or inferred from another data source.
Basic data conversion programs are required for converting data with this level of
complexity.
High — The layout of the data stores is significantly different between
legacy system and Advantage 3, potentially residing in different data stores in the
two systems. Significant data manipulation will be required to convert the
current data. This type of conversion will require a complex conversion program
to manipulate the data.

The data conversion strategy will also identify the method of data conversion. The
following methods will be identified:
i. Manual — This method will be used for converting low volumes of data
to Advantage 3 and have a low complexity.
Semi-Automated — This method will be used for converting data that
require a combination of manual and automated processes to convert the data. A
combination of Advantage 3 utilities and manual processes will be used for this
conversion method and is applicable for converting data with medium
complexity.
Automated — This method will be used for converting large volumes of
data. It is assumed that the legacy data is stored and available in an electronic
format. This method is generally applicable for converting data with high
complexity.
2.7.2.2. Reporting Strategy - The objective of this task is to develop the overall
approach for supporting the reporting requirements of the end users. Contractor will
review the list of current reports provided by the County and develop recommendation
for the disposition of the legacy reports. The County will review, provide feedback
and confirm the recommendation for the reports. The output of this task will be the
Reporting Strategy that lists the required reports, identifies the report users,
categorizes them by their level of complexity, and identifies the strategy to generate
the report.
The complexity of a report drives the level of effort of the report in terms of design,
development, and unit testing. The complexity of a report is dependent on the number of
tables accessed, special formatting, computations, etc. Contractor will work with the
County to develop a set of guidelines for the rating of reports in terms of their complexity
to design, develop and unit test.
This strategy will focus on the design, development, and testing of the custom reports to
be produced using the CGI infoAdvantage suite of reporting tools and the customization
of Java-based standard reports that are generated by the Advantage 3 application.
The disposition of the current legacy system reports and queries will be categorized as
follows:
i. Replace — The report or query will be replaced by Advantage 3 report or query
functionality.
Create — The report or query cannot be addressed by Advantage 3
baseline reporting and query functionality. A new report and/or query will need to be
developed.
Eliminate — The report or query is no longer needed and can be
eliminated.
The analysis of reporting requirements will include the reports previously implemented
by the County listed in Attachment B -5.4. Reports and data extracts created by
departments and agencies that are not listed in Attachment B -5.4 will not be analyzed.
The Reporting Strategy, as more fully described in Attachment B-5.2, will include an
approach to replace or feed the existing data mart(s)/data warehouse.

The reports will be prioritized based on the mission critical degree of the report and rated
as critical, very important, nice to have, etc. Reports will be designed, developed and
unit tested in order of their priority.
As a separate section of the Reporting Strategy, Contractor will identify the custom forms
that will be produced for the Project using the bundled Adobe suite of tools.
2.7.2.3. System Interface Strategy - The System Interface Strategy, as more fully
described in Attachment B-5.2, will include a review of the current system interfaces
that need to be retrofitted or recreated for the Project. Contractor will review the list
of interfaces provided by the County in Attachment B-5.3 and develop
recommendations for the disposition of the legacy system interface. The County will
review, provide feedback and confirm the recommendation for the interfaces per the
project schedule. The strategy will also identify the method of interfacing the data
between the County's external systems and Advantage 3. The level of change
required for each interface will be categorized as follows:
i. Low Impact — Minor customization to the interface will be required, such as,
changes to format of data.
ii. Medium Impact — A moderate level of changes will be required for the
moderate level of changes to the interface.
iii. High Impact — A significant level of customization or a complete re-write will
be required for the interface.
Where applicable, the System Interface Strategy will leverage the use of Pervasive
Data Integrator (PDI), as more fully described in Attachment B-5.2, a bundled
Advantage 3 third party tool.
2.7.2.4. Training and Documentation Strategy - As training will be dependent upon,
and closely associated with, the user and system documentation requirements, the
strategy for these two areas will be developed together. Training requirements will be
identified that include the number and types of users to be trained, the types of
training and documentation to be provided, the required training configuration and
courses, as well as how each course will be delivered. Documentation requirements
will include the type of documentation, the media for the documentation, as well as
methods for maintaining and distributing the documentation.
2.7.3. Upgrade Analysis Document (UAD)
The results of the analysis performed and work products developed during the
Prototyping, Technical Assessment and Implementation Strategies will be consolidated
into the UAD for all three Subprojects. This key project deliverable will provide a high
level roadmap and implementation project plan for the Create and Achieve Phases. The
documents will include an executive summary that summarizes the overall results of the
Envision Phase activities. The Implementation Roadmap and updated Work Breakdown
Structure will describe the roadmap for planning and executing the implementation
components of the Project based on the Implementation Strategies developed during the
Envision Phase. The County will review, provide feedback and approve the UAD per the
schedule specified in the Work Breakdown Structure.
The definitions of the deliverables to be completed by Contractor for the Project are
included in Attachment B-5.2.
3. Create Phase
3.1. Non-Production Environments

Contractor will establish up to seven (7) non-production environments to be used during the
Create Phase, as more fully described in Attachment B-5.2. Contractor will install the baseline
Advantage 3 application and Bundled Software Products on the hardware components hosted in
the CGI Data Center and perform installation tests to confirm that these software components can
be accessed and used by the project team to support the objective of the environment. The
environments will support the following activities:
3.1.1. County Development
3.1.2. Contractor Development
3.1.3. Conversion
3.1.4. Integrated System Test (1ST)
3.1.5. User Acceptance Test (UAT)
3.1.6. Training
3.1.7. Pre-Production (Gold)
Non-production environments will be repurposed during the course of the project to support
Create Phase activities.
As part of the Managed Services, the environments established for use beyond the Envision Phase
to support the Project will be documented in an Environment Overview deliverable as more fully
described in Exhibit B-2. This deliverable will include a high-level diagram of the relevant
elements comprising the Managed Advantage technical environment. Production and non-
production environments including web application and database servers will be identified as well
as high-level network elements supporting access to the environments. There will be a maximum
of three (3) non-production environments supported following the Go Live Date.
In conjunction with the Environment Overview deliverable the Contractor will also develop and
execute a Platform Test Plan to confirm that the technical elements were installed correctly and
interoperability performs as expected. Details include, but are not limited to, technical user
rights, accessibility, network routing, and firewall rules.
3.2. Project Team Training
3.2.1. Technical 'ream Training
Contractor will deliver technical training to the County's technical staff on the Bundled
Software Products that will be used to complete the County's tasks in the areas of system
interfaces development, data conversion support, and reports / forms development.
Contractor will utilize baseline Advantage 3 training materials in delivering the technical
training and conduct one (1) training class for training up to ten (10) County technical
staff to be determined by the County. CG1 provide all technical training during
Subproject 1 and it will not be repeated for Subprojects 2 and 3 as the same tools will be
used to support all three Subprojects. Training will be provided on the following Bundled
Software Products: CGI infoAdvantage, Pervasive Data Integrator (PDT) and Adobe
forms, as more fully described in Attachment -5.2.
The County will provide the facilities for the training and schedule the attendees.
3.2.2. Functional Team Configuration Training
Contractor will deliver application configuration training to the County's functional team
to support their responsibilities for setting up the Advantage 3 system control and
reference tables for the Project. Contractor will utilize baseline training materials for the
functional training and conduct one (1) training class for training up to fifteen (15)
County functional staff to be determined by the County. Functional team training will be

provided for the functionality being implemented during each Subproject. For example,
only Subproject 1 functions will be trained during Subproject 1.
The County will provide the facilities for the training and schedule the attendees.
3.3. Application Table Configuration
The Contractor will apply the application configurations identified during the Envision Phase.
These configurations provide the foundation that will support the converted data that will be
loaded to support the Project.
County will assist the Contractor in applying the application configurations and address any
business processes issues identified by the Contractor as these application configuration changes
are being applied.
3.4. Application Software Customization
Contractor will be primarily responsible for the design, development and testing of the
application software customizations required to support the County's business requirements
during the Project. The budgeted level of effort for Contractor to develop the application
software customizations in this Statement of Work is 5,000 hours for Subprojects 2 and 3.
For the approved software customizations, Contractor will create Functional Designs, as more
fully described in Attachment B-5.2. A Functional Design is a high-level design specification
that provides an overview of the business requirements and/or processes to be supported by the
customization, processing logic for online, batch, and reporting software components, business
scenarios to be included ill unit tests, and key assumptions. Contractor will develop, unit test, and
system test the application software customizations upon the County's approval of the
corresponding Functional Designs. After the application software customizations are system
tested by the Contractor, they will be released to the County to test and confirm the application
software functionality.
The County will review and approve the Functional Designs and System Test results, and provide
timely feedback and approval per the Work Breakdown Structure.
The County will be responsible for the software customizations required to the County's external
systems that are impacted by the Project.
3.5. Data Conversion
Data considered for conversion for Subprojects 1 and 3 will be defined during the Envision
Phase. There will be no data converted for Subproject 2. Attachment B-5.5 of this Statement of
Work includes a preliminary list of the legacy tables to be considered for conversion for
Subproject 3. This list will be reviewed and finalized during the Envision Phase.
Contractor will use baseline system utilities to develop the data conversion software. This
approach provides the foundation for the data conversion for the Project, standardizes work
product quality, and minimizes risk. The project team will use automated, semi-automated, and
manual methods to load the converted data for the Project.
Contractor is responsible for the development of the automated and semi-automated data
conversion processes. The County is responsible for the completion of the manual conversion
tasks and loading of the data spreadsheets to support the semi-automated data conversion
processes (e.g., Chart of Accounts load). The County is also responsible for the legacy system's
data cleansing activities that will deliver clean input data for the conversion from the legacy
system to CGI Advantage.
The Data Conversion for the Project will include the following tasks:

3.5.1. Data Conversion Plan
Contractor will develop a Data Conversion Plan, as more fully described in Attachment
B-5.2, based on the conversion approach finalized during the Envision Phase. The Data
Conversion Plan will include:
i. A list of the tables within Advantage 3 to be populated for production
Source data for these tables (source systems and files)
Scope of reference data conversion
iv. Scope of open balances data conversion (closed items will not be converted)
v. Historical data reporting approach
vi. Data conversion timing and sequence
vii. Proposed conversion method (automated, semi-automated, or manual)
viii. Other system impacts
ix. Considerations for the County's agency-level legacy system conversions
x. Participants (roles & responsibilities)
xi. Procedures for database population and refresh.
The County will review the Data Conversion Plan and provide feedback to Contractor per
the Project Plan according to the schedule provided in the Deliverable Expectation
Document. The County will also define the process and procedures for County-led tasks
such as crosswalks, legacy data analysis, data cleansing and clean-up, Chart of Accounts
loading, and manual conversion.
3.5.2. Data Conversion Designs
Contractor will define the transformation logic for developing the data conversion
software and describe in detail each conversion process in the data conversion designs, as
more fully described by Contractor in Data Conversion Plan, for the County's review and
approval. This information will be described within the Detailed Specification Designs
(DSDs) Deliverable, as more fully described in Attachment B-5.2. The DSDs will define
the data conversion data mappings, transformation rules, data integrity rules, data
reconciliation process, test cases and test sequence. The County will review and approve
or reject the designs per the schedule provided in the Deliverable Expectation Document
and Work Breakdown Structure.
3.5.3. Data Conversion Software Development and Testing
Upon completion of the Detailed Specification Designs, Contractor will develop and unit
test the data conversion software components to support the automated and semi-
automated conversion processes. After development and unit testing, a test with actual
legacy systems data will be conducted by Contractor. This test confirms that Advantage
3 tables are properly loaded with the corresponding data from the legacy system. The
County is responsible for providing data extracts for use in testing.
Contractor will generate the necessary reconciliation, control, and exception reports for
each conversion program which can be used to verify the data. These reports will help
identify areas where further data cleansing is required by the County and facilitate the
approval of the data conversion software, as more fully described in Data Conversion

Plan. The County will review the test results and conduct the necessary data cleansing
activities.
3.5.4. Data Cleansing
The County will be responsible for reviewing and cleansing of data to be converted from
the legacy systems to Advantage 3. Contractor will provide support for a period up to
three (3) months to assist the County in the data cleansing activities, as more fully
described in Attachment B-5.2. The length of conversion support for each Subproject
will be specified in the associated Data Conversion Plan.
3.5.5. Chart of Accounts Load & Manual Conversion and Testing
The County will be responsible for loading the Chart of Accounts, as more fully
described in Attachment B -5.2, and other data elements to be converted using semi-
automated methods, completing manual data conversion entries, and data cleansing.
Contractor will provide assistance to the County with regard to completing these tasks.
Contractor conversion support includes providing assistance to the County in the areas of
loading Chart of Account spreadsheets, data verification, reconciliation of conversion
controls, testing, and resolution of errors identified during the conversion process.
Contractor will provide support up to a period of three (3) months to assist the County in
the loading of Chart of Accounts data and manual conversion activities, as more fully
described in Attachment B -5.2. The length of conversion support for each Subproject
will be specified in the associated Data Conversion Plan.
3.6. System Interfaces
The Advantage 3 system interfaces will import data to Advantage 3 and export data from
Advantage 3 to the County's external systems. An interface is counted as each system and
document code combination. Contractor will develop a System Interface Plan, as more fully
described in Attachment B -5.2, to provide a unified structure and strategy for developing system
interfaces. Contractor and the County will be responsible for the design, development and testing
of the system interfaces analyzed during the Envision Phase, as more fully described in
Attachment B -5.2. Contractor will design, develop and test up to thirty-five (35) system
interfaces with varying levels of complexity across all three Subprojects. Contractor will develop
a maximum of fifteen (15) complex interfaces. The County will be responsible for the design and
development of the remaining system interfaces identified for the Project including all integration
necessary between Advantage 3 and the County's Electronic Content Management solution,
OnBase. Contractor will support the County in the design and development of system interfaces
to be developed by the County. Contractor will provide support over up to a period of six (6)
months to assist the County in the design and development of the system interfaces to be
developed by the County. The length of interface support for each Subproject will be specified in
the associated Data Conversion Plan.
The County will coordinate the testing of these system interfaces with the County agencies,
departments, and other appropriate external entities. The County will use production data for
system interface testing with the external systems to help ensure the accuracy of the newly
developed interfaces.
3.7. Reports, Data Warehouse, and Forms
3.7.1. Reports, Data Warehouse and Forms Plan
Contractor will develop a Report, Data Warehouse and Forms Plan, as more fully
described in Attachment B -5.2, to provide a unified structure and strategy for developing
reports and forms. Contractor and County will be jointly responsible for the design,

development and testing of the reports and forms analyzed during the Envision Phase, as
more fully described in Attachment B -5.2. Contractor will design, develop and test up
to seventy (70) reports and ten (10) forms across the three Subprojects. Contractor will
develop a maximum of twenty-five (25) complex reports. The County will be responsible
for the design and development of the remaining reports and forms identified for the
Project. All developed reports will be based on the Project standards for reports, ad-hoc
queries, or other sources identified by the Project Team. Contractor will support the
County in the designs and development of reports and forms. Contractor will provide
support up to a period of six (6) months to assist the County in the design and
development of the reports and form to be developed by the County. The length of report
and form support for each Subproject will be specified in the associated Report, Data
Warehouse and Forms Plan.
The set of standards for the reports and forms development process include:
a. Usage of the infoAdvantage and Adobe toolsets, as more fully described in the
Reports, Data Warehouse and Forms Plan, to support Contractor and County reports
and forms development and the County's current system for report distribution and
access;
b. Standards defining the format and processes for the data warehouse software
components and the usage of the Bundled Software Products, as more fully described
in the Reports, Data Warehouse and Forms Plan, when customizations to the Extract-
Transform-Load (ETL) software, as more fully described in the Reports, Data
Warehouse and Forms Plan, are required;
c. Standards to be used as guidelines for report delivery and report "look and feel"; and
d. Contractor and County-adopted best practices in report and universe development, as
more fully described in tile Reports, Data Warehouse and Forms Plan.
In the event, the CG1 infoAdvantage toolset and/or the Advantage Data Warehouse, as
more fully described in the Reports, Data Warehouse and Forms Plan, cannot support the
County's requirements, the Contractor and County Project Managers may approve the
development of Java-based reports and reflect any necessary adjustments ill scope and
scheduling using the Project's Change Control Process.
3.7.2. infoAdvantage Analysis and Mapping
Contractor will conduct an analysis to identify and map infoAdvantage universes to
support the reports development effort based on the scope approved by the County during
the Envision Phase.
Based on this analysis, Contractor will design, develop, and test the changes to the CGI
infoAdvantage universes to support the application software customizations identified to
meet the Project requirements and the County's reporting requirements. The updated
universes will serve as the basis for delivering the remainder of the reporting
components.
3.7.3. infoAdvantage Extract -Transform -Load (ETL) Software
Contractor will design, develop, and test customizations to the ETL software, as per the
scope described in Attachment B-5.2. These customizations will support the application
software customizations and reporting requirements adopted by the County to support the
Project.
3.7.4. Reports

Contractor will design, develop, and test a subset of the Advantage 3 reports per the
agreement under this SOW. The County will design, develop, and test the remaining
Advantage 3 reports per the agreement under this SOW. The project team will leverage
the CG[ infoAdvantage toolset to support their reports development efforts. Java-based
reports may be developed upon approval of the Contractor and County Project Managers.
The County is responsible for all report scheduling, distribution, and printing.
3.7.5. Forms
Contractor will design, develop, and test up to 10 Advantage 3 forms per the agreement
under this SOW. The County will design, develop, and test the remaining Advantage 3
forms per the agreement under this Statement of Work. The Project Team will leverage
the Adobe toolset to support their forms development efforts.
3.7.6. Report Mapping
The County will develop a mapping of COFRS reports to the new Advantage 3 reports
and queries to support end user training and documentation.
3.7.7. Enterprise Intellligence360
Enterprise Intelligence360 (E1360) provides the County with the ability to access data
across the County through the BusinessObjects platform and anchored by the delivered
infoAdvantage data warehouse. Contractor will design, develop and test three (3) non-
Advantage universes.
The following assumptions were made on the development of the E1360 universes:
• The County will be on version XI R3.1.
• E1360 delivered content including Mobile Reports and Explorer spaces come
with Release 3.10 at no additional licensing cost. Release 3.10 leverages
BusinessObjects 4.x and it is assumed this is the release of BOBJ that will be
implemented upon Go Live of Release 3.10.
6 E1360 Transparency Portal is not in scope for this Project.
• The three (3) non-Advantage universes will include the associated data
warehouse tables/ETL and each will include two (2) medium complexity Fact
Tables.
• Each Fact Table will each be comprised of two (2) to three (3) source system
tables and up to ten (10) dimensions and fifteen (15) low complexity dimension
tables.
• The dimension tables will each be comprised one (1) source system table with up
to ten (10) columns per universe.
• Each non-Advantage universe will have one (1) medium complexity Web
Intelligence report and one (1) low complexity Explorer space created.
• Managed Advantage includes sizing and associated assumptions for supporting
building out non-Advantage universes. This scopes assumes ETL so data is
stored in warehouse (will not design to connect directly to the database). This
approach minimizes bandwidth/connectivity issues.
• Documentation will consist of a universe metadata spreadsheet and sharing of the
En functional designs to provide a table mapping crosswalk
The County will provide resource(s) familiar with the source system as part of the project
to assist in functional and technical designs, and to apply source system development
items if necessary. The County will provide access to the source system during the

implementation. The County will be responsible for approving all designs and conducting
testing of the E1360 functionality.
3.8. Security and Workflow
The County will be responsible for conducting an analysis of its current legacy security setup.
Based on this analysis, the County will develop a Security and Workflow Plan, as more fully
described in Attachment -5.2, which defines the approach for the configuration and set up for
Advantage 3.
Contractor will provide standard security and workflow templates, assist the County in analyzing
the current security set up, and provide support services during the plan development and security
and workflow set up activities. These activities will include assisting the County in developing a
Security and Workflow Plan that describes the tasks necessary and the timeline for completion, as
more fully described in Attachment B-5.2. The templates will assist in determining the needed
changes for security to allow for new resources and functionality with the Advantage 3
applications. Contractor will also provide one (I) class on baseline security and workflow training
to the County security administration personnel. Contractor will provide support for the duration
security and workflow activities per the Work Breakdown Structure to assist the County in the
security and workflow setup. The length of security and workflow support for each Subproject
will be specified in the associated Security and Workflow Plan.
3.9. Testing
Software testing entails the planning and execution of tests to verify that Advantage 3 and related
software components comply with County-approved designs and other specifications as outlined
within this SOW. The customizations required by the County shall be installed by Contractor and
made available to the County.
The following testing activities will be completed •for the Project, as more fully described in
Attachment B-5.2:
3.9.1. Client Iteration Test
The Client Iteration Test (C1T) represents an informal testing process that allows the
County to become proficient in using the software components prior to the User
Acceptance Test and allows the project team to address identified issues earlier in the
project. After Contractor-led software development and testing activities are complete for
the Advantage 3 software customizations, Contractor will make each software component
available to the County for independent testing as part of its approval process for each of
these deliverables. The software customizations will be developed and delivered to the
County in pre-defined iterations. The County will conduct the C1T for the software
customizations included in the software iteration.
3.9.2. Integrated System Test
The primary objective of the Integrated System Test (1ST) is to confirm that the
application software, system interfaces, reports and conversion software are processing
information as designed as system transactions are entered into Advantage 3, transmitted
from other County systems or batch processed. The completion of the 1ST represents a
major milestone for the Project as it formally transitions Advantage 3 software and
related software components to the County for User Acceptance Testing (UAT) and
verification.
Contractor will develop a plan, schedule, and test scripts for conducting the 1ST with a
focus on testing the overall integration of the developed Advantage 3 software

components. Contractor will develop test scripts to define the steps, input data and
expected output of the 1ST conditions. Contractor will execute the test scripts, document
the test results, and review the results with the County during test execution. If the actual
results do not match the expected results, an incident will be identified, documented, and
resolved. Incident resolution may require the development of software fixes and re-
testing.
The County will review and approve the 1ST plan, scripts, and test results. The County
will coordinate and schedule the testing with external system and County operations staff,
as required, based on the 1ST schedule.
3.9.3. User Acceptance Test
The primary objective of the User Acceptance Test (UAT) is to confirm Advantage 3 and
its associated software components meet the County's business requirements and to
verify the conversion process. The County will develop a UAT plan that will include the
acceptance and threshold criteria, schedule, resources, and test conditions for the UAT.
The County will develop test scripts to define the steps, input data and expected output
for the UAT conditions. The County will execute the test scripts and document the test
results. Incident resolution may require the development of software fixes by Contractor
and re-testing by the County. The County will coordinate and schedule the testing with
external system and County operations staff based on the UAT schedule.
Contractor will review and provide feedback on the UAT plan, scripts, and table
configurations. Contractor will also provide consulting support during UAT execution
including assistance with the loading and verification of converted data. Contractor will
create a UAT log that documents County-reported issues and their resolution.
3.9.4. Performance Test
The primary objective of the Performance Test (PT) is to demonstrate Advantage 3's
readiness for supporting the County's transaction and user volumes. Contractor will
develop a strategy and plan for the Performance Test, develop scripts, execute the test,
and document the results that will support the sizing and usage assumptions in the
Technical Assessment section of the Upgrade Analysis Document. Contractor will
conduct the test using a mutually agreed upon set of transaction types. The test plan and
scripts will define the transaction volumes, test scenarios, and online and batch conditions
to be addressed by the test. Contractor will resolve identified performance issues by
performing the system and database tuning necessary to support the mutually agreed
upon performance requirements. The County will review and approve the Performance
Test plan, scripts, and test results. The Contractor will coordinate and schedule the test
result reviews with the County's operations and IT staff, as required based on the
Performance Test schedule.
If actual transaction volumes exceed the numbers provided to size the hardware
configuration, additional hardware may be required at the County's additional expense
pursuant to a Contract amendment.
3.10. Policies and Procedures
The County will develop a Policies and Procedures Plan, as more fully described in Attachment
B-5.2, which outlines the approach for documenting and communicating policy and procedure
changes. Contractor will support the County's development of the Policies and Procedures plan.

The County will develop a System Usage and Security Plan to document any changes to its
internal controls as a result of the Project. Contractor will support the County's development of
the updates to the System Usage and Security Plans.
Contractor will provide support for up to three (3) months for the policy and procedure updates.
The length of policy and procedure support for each Subproject will be specified in the associated
Policies and Procedure Plan.
3.11. Documentation
Contractor will apply the updates and prepare an addendum to the baseline Advantage 3 users and
system documentation to reflect the software customizations completed during the Project
implementation.
Contractor will provide the following documentation, as more fully described in Attachment B-
5.2:
I. Advantage 3 User Documentation — updated version of the Advantage 3
application documentation. These updates will be loaded to the online
application such that field level and page level help and effort handling may
reflect the software customizations for the Project.
ii. Advantage 3 Systems Documentation — updated version of the Advantage 3
systems documentation. Because Advantage 3 will be supported under
Managed Services in Exhibit B-2, Contractor will review all updates with
the County.
3.12. Trainer and End User Training
A train-the-trainer approach, as more fully described in the Training Plan, will be used by
Contractor to train the County trainers and system administrators. The County trainers will
conduct the End User training, as more fully described in the Training Plan.
The following training activities will be completed for the Project, as more fully described in
Attachment B-5.2:
3.12.1. Develop Training Plan
The user community audiences for the training will be inquiry users, professional users,
power users, and report developers. Early in the Create Phase, the County will assess the
user community's needs based on how they will use Advantage 3 and develop a Training
Plan. The County and Contractor will jointly review assumptions, preferences and
challenges, refine audience sizes, and determine the logistics of training delivery.
Contractor recommends role based training with customized curricula and customized
learning tools for the training audience. The Training Plan will document the joint
decisions for the learning program, and roles and responsibilities.
Based on the requirements defined in the Training Plan, Contractor will develop the train-
the-trainer training materials using Contractor templates that accommodates various
learning styles, incorporates effective interactivity, and promotes student learning.
Contractor will provide training for the County's trainers (Train-the-Trainer Training)
and the County trainers will provide the End User training. Contractor will provide a
County project team training and orientation, system administration training and
functional support training. The training will include e-learning components, self-study
components, and formal classroom training.

Contractor will support the County's instructors to plan, deliver, and deploy learning
components to the End User community efficiently and cost effectively. Classroom
sessions will introduce the online self-help tools, support users as they learn, and offer
additional hands on practice with a live instructor.
While training encompasses the formal modes for communicating new solution
functionality and preparing the County staff for their new functional and technical roles,
Knowledge Transfer, i.e., On-The-Job training, is the on-going, gradual, and often
informal alignment process of County staff with their new responsibilities.
3.12.2. Develop Training Materials
Contractor will be responsible for developing the train-the-trainer and system
administration training materials. Contractor will use the baseline Advantage 3 training
materials as the starting point for developing the training materials. County will develop
the end user training materials using the Contractor delivered material as a starting point
and conduct loading of the end user training data. Contractor will develop materials only
for areas being implemented for each Subproject.
To facilitate trainer training and optimize the County trainers' proficiency with the
materials, the Contractor-developed training materials will be leveraged by the County to
prepare for End User Training. The County will be responsible for the development
ongoing updates to the End User Training materials,
3.12.3. Deliver Training
Contractor will deliver trainer training to the County's trainers and system administration
training for the County's system administration staff. Contractor will train up to ten (10)
County trainers and three (3) system administrators. Contractor will deliver one (I)
training class for each of the training courses developed for the Project for each
Subproject.
Based on the training materials developed for the Project, the County will complete the
functional configuration of the training environments, populate the Training environment,
and conduct a shakedown test to confirm functionality. The County is responsible for
delivering the End User Training and the completion / planning for logistics, facilities,
equipment, and scheduling. The County's trainers will deliver end user training with
Contractor's support as defined in the Training Plan. The County will be responsible for
the ongoing maintenance and updates to the training data. Contractor will provide
support over up to period of three (3) months to support the County trainers in delivering
the training. The length of end user training support for each Subproject will be specified
in the associated Training Plan.
3.13. Readiness Assessments
3.13.1. Implementation / Agency Readiness Assessment
Contractor will prepare a checklist to enable the County to assess readiness of the
County's Project Team and County agencies' readiness for the Go Live Date. The
Implementation and Department Readiness Checklist, as more fully described in
Attachment B -5.2, will verify the readiness status of the County's agencies for the
Subproject Go Live Date, such as, the County's registration for end user training,
development of department-specific procedures, and other tasks described in Attachment
B-5.2.
Contractor will assist the County in conducting the readiness assessment and
implementing corrective actions to achieve readiness as defined in the checklists.

3.13.2. Operational Readiness Assessment
The Operational Readiness Assessment, as more fully described in Attachment B -5.2, is
intended to confirm that the Advantage 3 production environment is ready and support
team is prepared for the Go Live Date of Advantage 3. Because the Advantage 3
production environment and on-going operations will be managed by Contractor, this
assessment covers the transition and readiness of the remote Managed Advantage team as
well as the County's readiness for tasks that will continue to be supported onsite.
Contractor will establish the necessary checklists, conducting the assessment, and
reviewing the results with the County. Contractor and the County will implement
corrective actions to achieve readiness as defined in the checklists.
The definitions of the deliverables to be completed by Contractor for the Project during
the Create Phase are included in Attachment B -5.2.
4. Achieve Phase
The Achieve Phase encompasses the activities related to final data conversion, production cutover
(i.e., installation of the final-tested software into the County's production environment), and post-
implementation support, as more fully described in Attachment B -5.2.
The tasks to be completed during the Achieve Phase are organized into the following sets of
activities, as more fully described in Attachment B -5.2:
a. Production Environment Set up
b. Mock Conversion
c. Production Cutover
d. Post-Implementation Support
4.1. Production Environment Set up
The Production Environment will be configured by Contractor per the recommendations and
findings identified during the Performance Test that are necessary for supporting the sizing and
usage assumptions in the Technical Assessment section of the Upgrade Analysis Document of
Exhibit B -5. Contractor is responsible for the software migrations to the Production
Environment and the final configuration and testing to confirm production readiness that will be
supported under Managed Advantage. The environment will be established using the data and
configurations from the Pre-Production (Gold) Environment, minimizing changes so as to reduce
risk of performance or stability variances.
4.2. Mock Conversion
The last task of developing and testing a solution is the Mock Conversions. By using production
data as input to the Mock Conversions in production ready format, the conversion team, as more
fully described in Attachment B -5.2, will obtain practical experience running the conversion
process, determining the timeframes required to run the jobs for the conversion of data in the
production environment, and facilitating the County's final review of the data quality.
Contractor will execute up to three (3) Production Cutover Mock Conversions and address any
data conversion issues for each Subproject. The County will verify and reconcile the Mock
Conversion results and perform any additional data cleansing and data preparation required.
4.3. Production Cutover

In preparation for the transition to Production, Contractor will develop a Go Live Date Checklist
and Contact and Escalation List. Contractor will then use these documents to prepare a Cutover
Plan.
Based on the Cutover Plan, Contractor will prepare a detailed script to define the County and
Contractor roles and responsibilities and sequence and timing of tasks (e.g., automated
conversion processes, manual conversion processes, conversion verification, software migration,
online table updates, and batch processing) that are necessary to activate Advantage 3 in the
County's Production Environment.
Contractor will also provide the assistance and support outlined in the Production Cutover Script
to facilitate the completion of the final conversion process and other cutover activities. These
activities include a full back-up of the County's production data prior to the final conversion.
The County will participate in the Production Cutover and rehearsal activities in accordance with
the Production Cutover Script developed by Contractor. County responsibilities include but are
not limited to:
a. Review cutover scripts developed by Contractor
b. Review online table set-up
c. Verify converted data.
4.4. Post-implementation Support
Prior to the start of this period and the Go Live Date, Contractor and the County will jointly
coordinate and support the handover to the Managed Advantage hosted services model (described
as Post-Transition services in Exhibit -2). This process will be planned using standard project
planning tools and will be managed by Contractor's Managed Advantage Project Manager.
Planning and status meetings will be conducted with the County throughout the latter phases of
the transition period to provide all required elements are considered, addressed, documented, and
correctly implemented within Advantage 3.
In addition to the technical and IT responsibilities Contractor will assume, upon the Go Live
Date, for Managed Services in Exhibit B-2, Contractor will also provide post-implementation
support services subsequent to the Go Live Date for a period of two (2) months for Subproject 1
and 2 and three (3) months for Subproject 3. During this post-implementation support period,
Contractor will provide services in the following areas, as more fully described in Attachment B-
5.2:
a. Production Operations Monitoring
Contractor will monitor and review system assurance reports as well as provide
functional support and completion of any software updates.
b. Production Incidents Resolution
Contractor will work with the County to functionally analyze and resolve incidents
reported by its end-user community. Contractor Project Team staff will coordinate
incident resolution activities with the Managed Advantage team, as needed.
The definitions of the deliverables to be completed by Contractor for the Project during
the Achieve Phase are included in Attachment B-5.2

MAY Aug
SERVICES County
OR Responsible Party CG1 County CG! County CGI County CGI County CGi County CGI & CG1 Rollup
4/7/14 4/7/14 10/23/13 10/21/13 10/8/13 10/2/13 10/4/13 10/7/13 10/8/13 10/14/13 10/8/13 10/15/13 10/17/13 10/18/13 10/23/13 10/15/13 10/18/13 10/21/13 10/22/13 417,! Summary Summary
PRODUCTS, Finish , Mon Mon Wed Mon Tue Wed Fri Mon Tue Mon Tue Tue Fri Wed Tue Fri Mon Tue Mon Manual Manual Start-only Finish-only Deadline Progress
9/30/13 9/23/13 9/23/13 9/23/13 9/30/13 9/30/13 10/3/13 10/7/13 10/8/13 9/23/13 9/30/13 10/9/13 10/16/13Thu 10/18/13 10/7/13 10/7/13 10/16/13 10/21/13 10/22/13 9/30/13
SCHEDULES, ADJUSTED). 1Start Mon Mon Mon Mon Mon Mon Thu Mon Tue Mon Mon Wed Wed Fri Mon Mon Wed Mon Tue n
Structure AND Duration days days days days days days days day day days days days days day days days days day day ;ysMo
PRICING 136 141 22 20 7 3 2 1 1 16 7 5 2 1 12 7 3 1 1 fl 13
Breakdown Milestone Milestone Summary
COMPLETE Task Task
Work AND External Inactive Inactive Inactive Manual Duration-only
3-5.1 IS ADDED Plan
Attachment Project
ENVISIONING OR -
13082 DELETED Document Document Document Document Document Presentation
AFTER MANAGEMENT Expectation Expectation Expectation Expectation Expectation Presentation Presentation Meeting
BE Services & Plan Plan Plan Plan Plan Meeting Kickoff Meeting Summary Tasks
REVISED Deliverable Deliverable Deliverable Deliverable Deliverable Project Project Project Project Project Meeting Finalize Kickoff Management Milestone Summary Project External
Implementation PLANNING Planning Plan Develop Review Revise Approve Develop Review Revise Approve Kick-off Kickoff Kickoff and Task Split
BE Project Develop Develop Project Draft Review Revise Conduct
MAY Name PROJECT Project Project B-5.
Task Project Attachment
EXHIBIT 9/3/13
WBS 1.1.2 1.1.2.1 1.1.2.2 1.1.2.3 1.1.2.4 1.2 13082 Tue
(THIS 1 17 18 19 20 21 22 23 24 Project: Date:
ID

MAY Aug
SERVICES nty/CGI J
OR Responsible Party CGI County CGI County CGI CGI CGI CGI CGI CGI County Cou County/CGI County/CGI County Rollup
4/7/14 10/16/13 10/10/13 10/14/13 10/15/13 10/16/13 4/7/14 10/31/13 11/29/13 12/31/13 1/31/14 2/28/14 3/31/14 4/7/14 3/28/14 3/28/14 3/28/14 3/28/14 3/31/14 11/20/13 11/19/13 Summary Summary
PRODUCTS, Finish Mon Wed Thu Mon Tue Wed Mon Thu Fri Tue Fri Fri Mon Mon Fri Fri Fri Fri Mon Wed Tue Manual Manual Start-only Finish-only Deadline Progress
0/8/13 10/8/13 10/8/13 10/11/13 10/15/13 10/16/13 10/29/13 10/29/13 11/27/13 12/27/13 1/29/14 2/26/14 3/27/14 11/1/13 9/30/13 9/30/13 9/30/13 9/30/13 10/23/13 10/23/13 10/23/13
SCHEDULES, ADJUSTED). Start Tue Tue Tue Fri Tue Wed Tue Tue Wed Fri Wed Wed Thu Fri Mon Mon Mon Mon Wed Wed Wed
Structure days days days days days days days days days days •
AND Duration 130 days 7 days 3 days 2 day 1 day 1 115 days 3 days 3 days 3 days 3 days 3 days 3 112 130 130 130 130 114 20 20
Breakdown PRICING Milestone Milestone Summary
COMPLETE Task Task
Work AND Report External Inactive Inactive Inactive Manual Duration-only
B-5.1 IS Status
ADDED
Monthly Committees
Attachment ENVISIONING OR - Reports
13082 DELETED Document Document Document Document Document Status Steering Meetings Plan Plan
1 2 3 4 5 6 Project and Meetings
AFTER Report Expectation Expectation Expectation Expectation Expectation Report Report Report Report Report Report Meetings Committee Plan Management
BE Status Reports Status Status Status Status Status Status Monthly Management Management Steering Management Summary Tasks
REVISED Deliverable Deliverable Deliverable Deliverable Deliverable Status Monthly Monthly Monthly Monthly Monthly Monthly Update Team Management Change Milestone Summary
Monthly 8,, Team, Project Project Project Change Task Split Project External
Develop Develop Review Revise Approve Monthly Prepare Prepare Prepare Prepare Prepare Prepare Review Conduct Conduct Conduct Develop
BE Prepare Project Change Develop
MAY Name B-5.
Task Attachment
EXHIBIT VVBS 11.2.1 :1.2.1.1 1.2.1.1.1 1.2.1.1.2 1.2.1.1.3 1.2.1.1.4 '1.2.1.2 ,1.2.1.2.1 1.2.1.2.2 11.2.1.2.3 11.2.1.2.4 1.2.1.2.5 '1.2.1.2.6 1.2.1.2.7 1_2..1 ,' 11.2.2 1.2.2.1 1.2.2.2 1.2.2.3 1.3.1 1.3.1.1 13082 9/3/13
! 1.3 Tue
(THIS 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 Project: Date:
ID

MAY Aug
SERVICES CGI — 3
Responsible Party CGI County CGI County CGI County County, CGI CGI County CGI County CGI County Rollup
OR
11/19/13 3/31/14 3/31/14 3/31/14 3/31/14 3/31/14 3/31/14 10/18/13 3/31/14 3/31/14 10/14/13 10/14/13 10/18/13 10/18/13 10/18/13 2/28/14 1/17/14 10/8/13 10/2/13 10/4/13 10/7/13 10/8/13 10/11/13 Summary Summary
PRODUCTS, Finish Tue Mon Mon Mon Mon Mon Mon Fri Mon Mon Mon Mon Fri Fri Fri Fri Fri Tue Wed Fri Mon Tue Fri Manual Manual Start-only Finish-only Deadline Progress
10/23/13 11/20/13 11/20/13 11/20/13 11/21/13 11/21/13 9/30/13 9/30/13 10/22/13 9/30/13 9/30/13 9/30/13 9/30/13 9/30/13 9/30/13 9/30/13 9/30/13 9/30/13 9/30/13 10/3/13 10/7/13 10/8/13 9/30/13
SCHEDULES, ADJUSTED). 1Start Wed Wed Wed Wed Thu Thu Mon Mon Tue Mon Mon Mon Mon Mon Mon Mon Mon Mon Mon Thu Mon Tue Mon
Structure AND Duration days days days days days days days days days days days days days days days days days days days days day day days
PRICING 20 94 94 94 93 93 131 15 115 131 11 11 15 15 15 109 80 7 3 2 1 1 10
Breakdown Milestone Milestone Summary
COMPLETE Task Task
Work AND External Inactive Inactive Inactive Manual Duration-only
8-5.1 IS resolution Advantage) Scripts
ADDED 1
Attachment issue (Managed Prototype gaPif
ENVISIONING OR Meetings and information -
13082 Plan Outreach Meetings Software Document Document Document Document Document g a df
DELETED Plan Execution Party additional requested
AFTER Management Plan Department outreach 3rd and as Analysis Expectation Expectation Expectation Expectation Expectation Logisitics
BE Management Management Management setup, 3 Adv request & Summary
Conduct data Repository Test and information Deliverable Deliverable Deliverable Deliverable Deliverable Scheduling Tasks
REVISED Change Change Change Change and with Repository Repository Environment & Requirements requirements Task Split Milestone Summary Project External
State Project PHASE Configure additional Prototyping/Functional Develop Review Revise Approve
BE Support Execute Execute Support Schedule Assist Establish Project Prototyping Develop Prototype
Project Use Prototype Install, Business Review Provide B-5.1
MAY Name ENVISION
Flask Attachment
EXHIBIT
PBS 3.1.3 .3.2 1.3.2.1 1.3.2.2 1.3.2.3 1.3.2.4 1.4.1 1.4.3 2.0 2.1 2.1.1 2.2 2.2.1 2.2.2 2.3 2.3.1 2.3.1.1 1.2.3.1.1.1 1.2.3.1.1.2 1.2.3.1.1.3 1.2.3.1.1.4 2.3.1.2 13082 9/3/13
1S 1 1 1.4 Tue
(TT 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 Project: Date:
ID

MAY Aug
SERVICES I I
Responsible County/CGI nty/CG nty/CG 3
Party County CGI CGI CGI u Co u Co CGI County CGI County CGI County CGI County CGI Rollup
OR
10/4/13 10/11/13 1/17/14 1/10/14 1/10/14 1/3/14 1/17/14 1/17/14 2/28/14 11/5/13 10/30/13 11/1/13 11/4/13 11/5/13 2/28/14 1/31/14 2/14/14 2/25/14 2/27/14 Summary Summary
PRODUCTS, Fri Fri Fri Fri Fri Fri Fri Fri Fri Wed Fri Mon Tue Fri Fri Fri Tue Thu Manual Manual Start-only Finish-only Deadline Progress
9/30/13 10/7/13 10/14/13 10/14/13 10/14/13 10/21/13 11/4/13 11/4/13 10/28/13 10/28/13Tue 10/28/13 10/31/13 11/4/13 11/5/13 12/2/13 12/2/13 2/3/14 2/17/14 2/26/14
SCHEDULES, ADJUSTED). Start Mon Mon Mon Mon Mon Mon Mon Mon Mon Mon Mon Thu Mon Tue Mon Mon Mon Mon Wed
Structure AND 'Duration days days days days days days days days days days days days day day days days days days days
PRICING 5 5 70 65 65 55 55 55 89 7 3 2 1 1 64 45 10 7 2
Breakdown Milestone Milestone Summary
COMPLETE Task Task
Work AND External Inactive Inactive Inactive Manual Duration-only
9-5.1 IS ADDED I
prototyping Gap
Attachment OR Prototyping for Fit - 14939.05,1845134.1
ENVISIONING for tables County Document
13082 DELETED Resources Execution reference prototyping Document Document Document Document
prepare
AFTER County and of setup for to sessions Expectation Expectation Expectation Expectation Expectation
BE Schedule and Training scripts material training Report Report Report Report Report Summary Tasks
Prototype Rooms Scripts, prototype preliminary training baseline prototyping Deliverable Deliverable Deliverable Deliverable Deliverable Gap Gap Gap Fit Gap Gap
REVISED Report Fit Fit and Fit Fit Task Split Milestone Summary Project External
Define Schedule Prototype Develop Complete Prepare Conduct Conduct Develop Develop Review Revise Approve Develop Develop Review Revise Approve
BE Gap
Name Fit B-5.
MAY
Task Attachment
EXHIBIT 6 9/3/13
BS 11.3.1.2.1 1.2.3.1.2.2 2.3.1.3 2.3.1.3.1 2.3.1.3.2 2.3.1.3.3 2.3.1.3.4 2.3.1.3.5 - 2.3.2 2.3.2.1 2.3.2.1.1 2.3.2.1.2 2.3.2.1.3 2.3.2.1.4 2.3.2.2 2.3.2.2.1 2.3.2.2.2 2.3.2.2.3 2.3.2.2.4 13082
Tue
(THIS 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 Project: Date:
ID

MAY Aug
SERVICES
OR Responsible Party County County CGI CGI CGI County CGI County CGI County CG1 County CGI Rollup
3/3/14 1/17/14 2/28/14 1/17/14 1/31/14 1/31/14 3/7/14 1/14/14 1/8/14 1/10/14 1/13/14 1/14/14 3/7/14 2/11/14 2/20/14 2/27/14 2/28/14 3/31/14 12/6/13 11/8/13 Summary Summary
PRODUCTS, 'Finish Mon Fri Fri Fri Fri Fri Fri Tue Wed Fri Mon Tue Fri Tue Thu Thu Fri Mon Fri Fri Manual Manual Start-only Finish-only Deadline Progress
11/18/13 11/18/13 1/20/14 11/18/13 11/4/13 11/4/13 1/6/14 1/6/14 1/6/14 1/9/14 1/13/14 1/14/14 1/15/14 1/15/14 2/12/14 2/21/14 2/28/14 10/14/13 10/14/13 10/14/13
SCHEDULES, ADJUSTED). ,Start Mon Mon Mon Mon Mon Mon Mon Mon Mon Thu Mon Tue Wed Wed Wed Fri Fri Mon Mon Mon
Structure AND Duration days days days days days days days days days days day day days days days days day days days clays
PRICING 76 45 30 45 65 65 44 7 3 2 1 1 37 20 7 5 1 120 40 20
Breakdown Milestone Milestone Summary
COMPLETE Task Task
Work AND External Inactive Inactive Inactive Manual Duration-only
B-5.1 IS ADDED
Papers 54tl
Attachment OR P5“,
ENVISIONING Concept
13082 DELETED Design - Document Document Document Document Document Requirements
AFTER Budget Design Customizations
BE and Budget Expectation Expectation Expectation Expectation Expectation Software Summary
Design Accounts and Interfaces Papers Papers Paper Paper Assessment & Tasks
REVISED Budget of Guidelines COA with Analysis & Reports Software Deliverable Deliverable Deliverable Deliverable Deliverable Concept Concept Concept Concept Concept Assessment Hardware Task Split Milestone Summary Project External
BE and Chart Develop State State 2x Develop Develop Review Revise Approve Develop Develop Review Revise Approve Implementation Technical Review W
COA Publish Assist Software Assess Application B-5.1
MAY Name
Task Attachment
EXHIBIT 2 1 9/3/13
WBS 23.2 12.4 12.4.1 2.4.2 2.4.3 2.5 2.5.1 2.6 2.6.1 2.6.1.1 2.6.1.2 2.6.1.3 2.6.1.4 2.6.2 2.6.2. 2.6.2.2 2.6.2.3 2.6.2.4 2.7 2.7.1 2.7.1.1 13082 Tue
(THIS 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 Project: Date:
ID

MAY Aug
SERVICES
OR Responsible Party CG1 CGI CGI CGI CG1 CGI CGI County CGI County CGI County CGI County County/CGI Rollup
11/22/13 12/6/13 12/27/13 12/27/13 12/27/13 12/27/13 12/27/13 3/31/14 11/14/13 11/8/13 11/12/13 11/13/13 11/14/13 3/31/14 3/4/14 3/18/14 3/25/14 3/28/14 3/28/14 Summary Summary
PRODUCTS, Finish Fri Fri Fri Fri Fri Fri Fri Mon Thu Fri Tue Wed Thu Mon Tue Tue Tue Fri Fri Manual Manual Start-only Finish-only Deadline Progress
1/11/13 11/25/13 12/2/13 12/2/13 12/2/13 12/2/13 12/2/13 11/6/13 11/6/13 11/6/13 11/11/13 11/13/13 11/14/13 1/6/14 1/6/14 3/5/14 3/19/14 3/26/14 2/17/14
SCHEDULES, ADJUSTED). Start Mon Mon Mon Mon Mon Mon Mon Wed Wed Wed Mon Wed Thu Mon Mon Wed Wed Wed Mon
Structure AND Duration days days days days days days days days days days days day day days days days days days days
PRICING 10 10 20 20 20 20 20 103 7 3 2 1 1 60 42 10 5 3 30
Breakdown Milestone Milestone Summary
COMPLETE Task Task
Work AND External Inactive Inactive Inactive Manual Duration-only
9-5.1 IS ADDED
Attachment Changes UAD
ENVISIONING OR -
13082 Specification Strategy Document Document Document Document Document necessary
DELETED Specifications Software Document if
AFTER BE & Strategy Strategy Documentation (UAD) Expectation Expectation Expectation Expectation Expectation Adjustments,
Software Hardware Strategies Strategy interface Document Analysis Summary Tasks
REVISED & of Conversion and Deliverable Deliverable Deliverable Deliverable Deliverable Upgrade UAD UAD HAD UAD Contractual Milestone Summary External
Hardware Impacts Data Reporting System Training Analysis Develop Review Revise Approve Develop Review Revise Approve PHASE Task Split Project
BE Revise Assess Implementation Define Define Define Define Upgrade Develop Develop Execute PHASE W
MAY Name CREATE ACF7F.VE B-5.1
Task Attachment
EXHIBIT 9/3/13
WBS 2.7.1.2 2.7.1.3 2.7.2 2.7.2.1 2.7.2.2 2.7.2.3 2.7.2.4 2.7.3 2.7.3.1 2.7.3.1.1 2.7.3.1.2 2.7.3.1.3 2.7.3.1.4 2.7.3.2 2.7.3.2.1 2.7.3.2.2 2.7.3.2.3 2.7.3.2.4 2.7.4 3.0 4.0 13082
Tue
(THIS 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 Project: Date:
ID

MAY Sep
SERVICES Aug 3
OR Rollup
Jul Summary Summary
PRODUCTS, Manual Manual Start-only Finish-only Deadline Progress
Jun
IEDULES,
ADJUSTED). May
Structure SC; L.
AN)
Breakdown PLEM PRICING Apr Milestone Milestone Summary
Task Task
Work COM AND External Inactive Inactive Inactive Manual Duration-only
B-5.1 IS ADDED
Attachment ENVISIONING OR ‘L) , F
13082 DELETED
Jan
AFTER BE -)014
Dec Summary Tasks
REVISED Task Split Milestone Summary Project External
BE ,
MAY 10/21 10/23 10/23 B-5.11.f
Attachment
EXHIBIT 9/3/13
13082
(THIS Sep Project: Tue Date:

MAY Sep
SERVICES Aug _
OR Rollup
Summary Summary
PRODUCTS, Manual Manual Start-only Finish-only Deadline Progress
Jun
SCHEDULES, ADJUSTED). May
Structure
AND
Breakdown PRICING Milestone Milestone Summary
Work COMPLETE AND Task Task Duration-only
External Inactive Inactive Inactive Manual
B-5.1 IS Al)DFD
Attachment ENVISIONING OR
13082 DELETED
AFTER BE 2014
Summary Tasks
REVISED Task Split Milestone Summary Project External
BE B-5.1
MAY
Attachment
EXHIBIT 9/3/13
13082 Tue
(THIS Sep Project: Date:

MAY Sep
H
SERVICES Aug
OR Rollup
Jul Summary Summary
PRODUCTS, Manual Manual Start-only Finish-only Deadline Progress
Jun
SCHEDULES, ADJUSTED). May
Structure
AND
Breakdown PRICING Apr Milestone Milestone Summary
Work COMPLETE AND Task Task Duration-only
Mar External Inactive Inactive Inactive Manual
8-5.1 IS ADDED
Attachment ENVISIONING OR it19383i£S11t3tl11F
13082 DELETED
Jan
AFTER BE 2014
Dec Summary Tasks
REVISED Task Split Milestone Summary Project External
BE Nov
MAY 13-5.1
Oct Attachment
EXHIBIT 9/3/13
13082 Tue
(THIS Sep Project: Date:

MAY Sep
SERVICES Aug J
OR Rollup
Jul Summary Summary
PRODUCTS, Manual Manual Start-only Finish-only Deadline Progress
Jun
SCHEDULES, ADJUSTED). May
Structure
AND
Breakdown PRICING Apr Milestone Milestone Summary
COMPLETE AND Task Task Duration-only
Work Mar External Inactive Inactive Inactive Manual
B-5.1 IS ADDED 2/28
tt,v
Attachment ENVISIONING OR Feb .eaeloitttae.
13082 DELETED I,I
Jan
AFTER BE 2014
Dec Summary Tasks
REVISED Task Split Milestone Summary Project External
BE Nov \I/
B-5.1
MAY
Oct Attachment
EXHIBIT E: 1 13082 9/3/13
I Tue
(THIS Sep Project: Date:

MAY Sep
1
SERVICES . Aug
Rollup
OR
Jul Summary Summary
PRODUCTS, Manual Manual Start-only Finish-only Deadline Progress
Jun
SCHEDULES, ADJUSTED). May
Structure ataa.
AND PRICING Apr -
Breakdown Milestone Milestone Summary
COMPLETE Task Task
Work AND Mar 3/7 External Inactive inactive Inactive Manual Duration-only
B-5.1 IS 2/28 V-1 *+3/7
ADDED , 771 7
Attachment OR Feb .eatrasoaarua..rrau•Lasiourirocuma.,0 a , 77 5
ENVISIONING a a a a
13082 DELETED 1E7a
AFTER BE 2014
Summary Tasks
REVISED Task Split Milestone Summary Project External
BE Nov V.1
B-5.1
MAY
Oct Attachment
EXHIBIT 9/3/13
13082
(THIS Sep Project: Tue Date:

MAY Sep
SERVICES Aug — 3 .4„
OR Rollup
Jul Summary Summary
PRODUCTS, Manual Manual Start-only Finish-only Deadline Progress
Jun
EDULES,
ADJUSTED). May
Structure SCE
AND
Breakdown PRICING Apr 3/31 3/31 Milestone Milestone Summary
Work COMPLETE AND Task Task Duration-only
Mar External Inactive Inactive Inactive Manual
B-5.1 IS ADDED
Attachment OR Feb H3.33,&f
ENVISIONING :£9,31333£
13082 DELETED
AFTER BE
Summary Tasks
I.EVISED Task Split Milestone Summary Project External
BE
MAY B-5.
Oct Attachment
EXHIBIT 9/3/13
13082
(THIS Sep Project: Tue Date:

MAY view uration 5
SERVICES Phase
Complexit Low Low
OR Achieve
and I
PRODUCTS, Create and major for
DOCUMENT The assumptions, and responsibilities describe during governance, timeline
SCHEDULES, Project. Subproject to responsibilities templates) project and Team
ADJUSTED). 3 Description scope, and included the Project
DEFINITION AND Advantage objectives, each in roles be and project describes responsibilities, 3
PRICING the complete. and with including will roles (including that and Advantage
DELIVERABLES COMPLETE AND for is Products project Subprojects Chart teams plans and tools, Management Control Management materials roles to
IS ADDED Contractor Phase Work specifying for management Management Management Management activities, presentation
by Envision Organization Contractor procedures, implementation Management Management Change Management Management presentation
B-5.2 ENVISIONING OR completed the Charter timelines and following Deliverable Document Communications Software Quality Configuration scope, kickoff
DELETED be after Project overall deliverables Project County The processes, project Scope Team Risk Issue Kickoff structure, One
ATTACHMENT to A o o o o o o o o o o
AFTER BE updated Q
deliverables be
13082 REVISED will Name Meeting
of list WBS# atic Management
BE a nd Plan Kickoff
MAY provides associated
Project Project
EXHIBIT below and
(THIS table deliverables Pi 1.1.1.2.5 1.1.2.5
The 1M

Review Duration 5 N/A
Complexity Low Medium
the for
be
detailing progress will
their being training
summary, Structure and area
ri;tion Baseline Management
executive Breakdown business Forecasting System Management Management
Fc and an products/deliverables 3 Subproject. Budgeting Asset inventory Professional Service
including Completed Logs Work Advantage Benefits Base — — — Self Lifecycle
Products Not Issues Project work per respective components: Performance & Salary Financial Financial Financial Procurement Vendor Grants
WorI Reports, but and Period of session the
Status items: Completed Progress Scheduled Risks Next Microsoft matrix for the Advantage Advantage Advantage Advantage Advantage Advantage Advantage Advantage
In for period overview for PunchOut
Monthly following Tasks Tasks Tasks Updated Goals Updated Updated that implemented provided CGI CGI CGI CGI CGI CGI CGI CG1
One o o o o o o o o o
o o o o o o o
•
for
Name (CGI Training
Management
Deliverable Reports Team
Project Status Activities) Project Prototyping
,
# WILS 1.2.1.2.8 Envisv. 2.3.L3.7
2O

Review Duration 10 10 7
Complexity High High Medium
County not result a identified work and Customizations and County
support does opportunities for the as the of developing Design the
prototyped practices of Project present the of Customizations groupings by process.
to best area necessary overview 3 to testing organization, designing, Software Functional upon Notice
Description being configured 3 business re-engineering Customizations set-up an Advantage and and Software logical Customizations. and for agreed
sessions functionality be Advantage following: table provide the tasks the (i.e., processes, for Papers costs Change
and s Prototype scenarios Scripts can 3 each for process Software issues to for Analysis development, iterations the schedule software and mutually the via
Produ sessions 3 when issues the of reference items developed identified organize outlines and Concept effort be
support Prototype Advantage Prototype Advantage prototype items Assessment business potential and prototype action Fit-Gap design, to into of of will documented
Work to execute prototype of how requirements needs action comprised of of of of be will and the developed County also assumptions, County-approved list the levels
Scripts set-up Execution of on County Fit application Modifications for the plan to Customizations and
to Scheduled Overview Walkthrough Advice business Documented Document Report Functional Identification Identification of implementation inventory inventory Papers prototyping cost be will by The revisions associated Contractor
Prototype Data Steps Prototype meet Gap List An An Concept Software the estimated Customizations. Plan approved products). dependencies, the the Software
o o o o o o o o Fit o o o o o o of A testing Any and and
• • e e • •
Name & Concept
Software -
Table Scripts Report
Prototype Execution Gap Application Customizations Papers
Fit
WIIS # 2.11.3.8 2.3.2.2.5 2.6.2.5

ion
Review 10
Din
Complexity High
Envision Analysis software will
Functional data
the implementation Gap and production which
the of during assumptions, Fit hardware from
Description sections: and the of to for files
accumulation performed following roadmap planning highlights updates following set-up and/or converted
-1 iiii the the the Project, any the and/or data
Products is Assessment of 3 items contains includes populated systems of
Document consists highlighting action containing source type considerations
Work Implementation it Advantage and Summary Strategy be to of the and
Analysis Project. Summary the issues Assessment tables list cleansing
for Report Conversion of operations Preliminary converted
Upgrade and the of Executive approach outstanding Gap Technical specifications list A be Data
The Analysis Phase Fit Data o o o
* • 0 •
l .;)J
Analysis (UAD)
Upgrade Document
RS # 2.7.3.2.5
NV

-Review i)uration
Complexity
i or disposition to the by used training for
Advantage (automated usage, develop and test and (i.e., documents preliminary process include:
report its and to Designs confirmation, identified iterations their the each the
of use tables method title, develop 3 and which and Materials
the the sequence report methods Contractor Report design, interfaces into Advantage interfaces (inbound) trained, in
DcscA including of version and conversion cycles the and organize to following: including the interfaces the includes: be to methods produced materials.
and timing and distribution County to products used the of of products) of outbound document Strategy users the be to the Documentation Guide
Products conversion, rules final the proposed specifying and for reports work be to with interfaces, elimination work description and 3 end of and distributing Help
and for conversion reporting the conditions, includes: reports reports 3 of approach Strategy system and/or organization for interfaces inbound Advantage Documentation number content, delivered documentation Documentation User Online Administration
Work data formats rules data control of of distribution, of Advantage groupings logical of for the groupings and of and be and
for integrity indication strategy, Strategy inventory into Interface replacement, and Identification Inbound corresponding and expected titles will of types maintaining Baseline Customized Customized System
Approach document Data Preliminary Required An manual) Testing Reporting An frequency, Assignment support Defined Software Description reports Approach County logical for Inventory Training The course course The - - - -
o o o o o o o o o o System o o o o o
0 G e
, Deli
#
WBS

Review Duration N/A N/A 7 10
Complexity Medium Low Medium High
be be required the the for
following can will in areas in areas be due configurations
the corresponding set-up requirement requirement software longer training training will and Environment
of table no with no is team (SysManUtil) above-mentioned team above-mentioned that responsibilities changing
Description one a and reference business customization business Setup process (Gold)
with process requirement technical functional and the the for
;tio.1 (RTM) functionality and/or the software the where business for Utility the review for review document and roles Pre-Production considerations
Matrix where — a by — business Structure materials Load to materials Configuration to to
Products scenario: baseline application needed met change current required the and Document Integrator Sessions and Tables Setup Sessions developed configurations, in future
Work Traceability each with any if Customization entirely to where Breakdown Setup tables and
for — of or process change — curriculum Advantage Data Forms Training curriculum Control Tables Training Subproject be table reference setup
met description requirements, Software partially Business a by customization Eliminated Work areas: Pervasive infoAdvantage areas: Reference Tables Project will to for of
Requirements dispositions Fully met Updated Training following CG1 Adobe Technical Training following System COA Functional Plan followed Setup Document
o o o o o o o o o o o each A dates.
• • • e • • • •
Nanie Training Training Plan
Team Team Configuration Configuration
Deliverable
Technical Functional Configuration Document
Table Table
Phase
# WI)', Create TBD TBD TBD TBD
3.0

Review Duration 10 10 10 10 N/A N/A 5
Complexity High High Low High High Medium Medium Low
provide to data data data
will Documents will migrated of converted facilitate and Subproject conversions Subproject system
Contractor and and County testing for County to issues each of
Design cases, Contractor Tested, the to and target the data worksheets conversion for manual each for testing
Descr Customizations, Functional test unit Unit presented development and Tested Unit to cleansing and data specified and COA specified and
and potential Customizations, sequence source presented for as or for as development
Developed, results design, and Developed, results practices information reviewing practices or
Products Software Customization design, software and the load containing rules and actions months months design,
Work purpose, products: Customization 3environment performed for plan conversion Maps Software and best on preparing testing 3 for best on 3 for the
County-approved Software work test project software transformation performed guidance in in corrective provided guidance issues provided for software
the contains County-approved following Software Advantage data Conversion Conversion test County County resolve plan
the provide which assumptions. System Detailed conversion for Plan Data including Data System Provide Assist cleansing Assist identifying Supported Provide Help Support Detailed interface
For For the o o
e • 0 • • • • • • a • a •
Name Concept Test Plan Designs Software Support Plan
ii)le Software - Software — Designs Software — System Manual Support
and Conversion Conversion Conversion Cleansing & Interface
wlvc:• Application Customizations Application Customizations Functional Application Customizations Software Results Load Conversion System
Papers Data Data Data Data COA
1
TBD TBD TBD TBD D TB TBD TBD TBD

Review Duration 10 10 N/A 5 10 7 7 5 7 10
4
Compler High High Medium Low High Medium Medium Low Medium High
across software of potential 3 by tested interfaces as or and test unit reports test Design cases,
interfaces the purpose Advantage designed unit support report unit functionality non- test
of including requirements, be and remaining of potential complex County potential (3) Functional unit
tion system development standard will developed of interface testing design, reports 25 of tested the design, forms County the the of three of potential
35 of documents, technical to interfaces County system and 70 maximum unit to 10 tested unit to overview Customization
tJ the maps be will the development purpose, of and presented purpose, of and presented development design,
ami maximum guide system to the development a an universes.
ts it a will design requirements, design interfaces provided and for including maximum for developed results including maximum developed results developed and Software purpose,
l'.-o for which interface assumptions interface complex be designs months design, a for designs and a for and design the E1360
Work designs 35 functional and 35 15 system will the 6 to Subproject the documents, develop reports documents, forms be will the provide contains the
Subprojects of cases of of 35 results in up each for assumptions 70 performed assumptions 10 performed Paper universes. which for
develop test maximum of County provide for plan software design viii of of support will assumptions
will Maximum interface, unit Maximum documents Contractor maximum test will and maximum test design and maximum test Concept to
CGI three A System Support CGI specified Detailed form Report cases, Contractor System Form cases, System needed Advantage Contractor Documents and
all o o o A A A A
* 0 • * • 9 • • i • e a • • •
Designs Software Support Warehouse Warehouse Design
Name Warehouse Paper
Interface interface Interface Data Plan Data Data Designs Software Concept Functional
li'vaNc Forms & &
System System System Report, and Report Designs Report Software Forms Forms E1360 E1360
i 1,173N TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD

Review ' Duration 10 N/A N/A 5 10 N/A 5
Complexity High Medium Medium Low High Medium Low
the as
to the and or Test and as or
software to reports support Plan of User Acceptance Kickoff, Acceptance support
results Results
the of form Workflow establishment County's Plan, Testing UAT
developed and following: Expected with User Test User of
Description E1360 provide development reports & the tested in data Acceptance facilitate months following: tested
and the Security profiles, of and reviewed test Acceptance be
and the testing and for the setup be to Scripts Report and User to (3) the to
migrate designs months on security consisting responsibilities Test Test, User staff three targets Scripts
Products and system the feedback workflow Plan functionality procedures System Results reference of Activities during technical to up containing responsibilities procedures
in 6 Subproject setup and System Subproject performance Test
Work deliver environments conduct team provide to ids, Test of and team Test Development Test reported provide Plan and
will will will each provide assistance user System roles tracking Integrated Integrated Test System setting-up issues County's will each Test of roles tracking Performance
3 County for and Identification for for Acceptance for for
Contractor Advantage Contractor County Support Contractor specified Review Provide production Integrated Defined Updated Develop Completed Acceptance Integrated Support Environment Support Resolved Support Testing Contractor specified Performance Definition Defined Updated Develop
forms o o o User
* • 4. • e 0 e 0 • 0 • • • o o o •
&
Name and Test Scripts Test Plan
Results Forms Workflow System Test
Deliverable Software Test and & Test Acceptance
E1360 System Reports Support Security Support Integrated Plan Integrated Results User Support Performance
# WIN TBD TBD TBD TBD TBD TBD TBD

Review Duration 7 N/A N/A N/A 5 5 7
Complexity Medium Low Low Medium Medium Low Low Medium Medium
tuning procedures each for go- and extract
issues, each Contractor specified to data cleansing
user for for administration system material go-live readiness responsibilities full data
performance to specified 3 and environment as or to using and
Description updates as documentation system training trainers training months readiness operation and run be loaded Conversion
including and or and 10 user training 3 for County's roles will records
and development months system support of end user department timing, Conversion Mock
Test Report, items 3 for and customizations train-the-trainer to maximum on end to training the process, Conversion times, during
WorkProduct.s Results action the in support user for setup a feedback related support user monitor monitor the Mock to Mock duration identified
Performance Test and County 3 software environment to provide classroom end to to related 3 of
provide Advantage materials provided questions support checklist checklist describes including issues
Completed Performance recommendations the Support will Subproject Update developed Training training Training Training administrators and Review Address configuration in Provide will Subproject Provide Provide that assumptions maximum Results required Resolve
CGI CGI live Plan A
0 • • • • • • • • •
Name Scripts and Readiness Plan
Test &Procedures Administration Training Readiness Results
Deliverable 3 Train-the-Trainer Conversion Conversion &
Performance Results Policy Support Advantage Documentation System Training User Support Implementation Checklist Operational Checklist Mock Mock Execution
& End Phase
TBD TBD TBD TBD TBD TBD TBD Achieve TBD TBD
4.0

Review ration 10 N/A N/A
Du
Complexity High Medium. Low
and sequencing, Refresher and 1
roles Monitoring User Subproject
timing, activities, End 3
Description of list Monitoring Characteristics (including for Subproject
activities, the months
and readiness rehearsal Use Support (2) for
Products cutover includes County Log two months
assumptions that cutover cutover the use Functional Performance On-site Incident Log for (3)
Work production and script assignments production production to production Request provided three
describing cutover and for for hand-off in Implementation Implementation Implementation Support) Production Change be will and 2
Plan responsibilities Detailed duration Support Support Operations is System Post Post Post Training Update Update Support Subproject
• • 0 * • • • • • •
Name Production
Deliverable Plan in 3 Implementation
Cutover Advantage Post Support
WHS if TBD TBD TBD

1.3.1.2 1.2.1.2.9 1.1.2.6 1.1.1.2.6 1.0 WBS will have B. The
Project # a table
Activities Change (County Project Project Approve Planning preceding below
Activities) Management Kickoff Project and number provides a
Management Meeting Plan Management Deliverable for each list of
& -
Status Name Deliverable deliverables
Communication Reporting that to be
is
• • • • 0 0 • • 0 * 0 0 • • 1 applicable completed
o o o o o of
Schedule Advantage Communicate Schedule Develop assignments Work Updated Updated Goals Key Updated weekly Monthly Participate Meeting Identify Provide Review Approve Provide Review for by the
and 3end and Change and Breakdown matrix MS for Risks Deliverables status Reports in County feedback Project Project feedback Project each County
conduct users project conduct task of work Project Next Period accomplishments and completed reports for Project Project for Kickoff Plan per Plan Subproject. for the
department status change Management dependencies Structure Plan issues for the County's Kickoff Team Project Meeting the project Work
and and updated products/deliverables month project Meeting members Kickoff Products Advantage 3
outreach upcoming management evolve as with Materials schedule
Communication project an activities to Meeting and Project.
meetings activities activities schedule, and their executive status participate Materials Description The
to the Plan in Work
County milestones, progress summary comprised the Breakdown
of Project
departments resource describing: a Kickoff Structure
compilation
and

in in CGI
customizations to schedule
requirements Structures transactions processes upgrading project
business schedule Budget business schedule software schedule or the schedule
COA control per
Documentation County's project revised transactions 3 revised budget County's project schedule application project schedule implementing Document project the
and of the per the of of: Advantage the of and the the per the per for per
Products for processing results 3 usage financial comprised for usage financial supporting Report project identified Papers project the Document Analysis Document
Work for: Templates for of: Advantage the for of Structures the for of for Fit-Gap the per the for Concept per Upgrade
and results prototyping comprised for impacts entry data Guidelines impacts entry data Report the Report Papers the Papers Analysis the Analysis
repository Documentation Products Deliverables on COA of the Budget of the Fit-Gap for Fit-Gap Concept on Concept Upgrade for Upgrade
Project Standards Work prototyping 3 feedback Guidelines Overview Departmental on Structure Overview Departmental on the 3 feedback the the feedback the the 3 feedback the
Central Project Project Project Project Review Advantage Provide COA Impacts Budget Impacts Review Advantage Provide Approve Review Provide Approve Review Advantage Provide Approve
o o o o o o o o o o
* * 6 0 0 0 0 * * a 6 e e
Design Document
Name Sessions
H. Repository Budget Report Papers Analysis
Prototype 84,
Project in Accounts Fit-Gap Concept Upgrade
Establish ast' Participate of Chart Approve Approve Approve (UAD)
# Uu
WBS 1.4.2 2.3.1.3.9 2.4.4 2.3.2.2.6 2.6.2.6 2.7.3.2.6 Cre...
.3.0

Advantage the schedule per project systems development and Data areas
baseline per Designs project baseline Customizations the per external schedule and system 3 the on business schedule
to al the to to systems crosswalk legacy 3 Advantage based licensed
Functional per Customizations Software Customizations necessary project schedule legacy facilitate Advantage conversion to activities the project schedule
i.)iscripf Customizations Designs the the per between to between and data conversion for the per
and Customizations Functional Software for Software customization Plan project crosswalks system during build Phase Plan project
training Software the results the the per crosswalks information legacy for data support Envision Interfaces the per
Products for for Test for software Plan Conversion plan of system the for identified system to tables the Plan Plan
Work training configuration Designs Software Customizations results System results any Data feedback between plan errors in System Interfaces
team the Test the Test test Conversion the Conversion development legacy issues data legacy reference defined Interfaces the
team Functional for Software System for schedule System and Data for Data the required provide cleansing resolve cleanse set-up Strategy System for System
technical functional the feedback schedule the the 3 feedback the develop the feedback the in 3 the and 3 crosswalk data and and and the feedback the
Attend Attend Review Provide project Approve Review Advantage Provide project Approve schedule Design, Review Provide Approve Participate Advantage Provide Review Advantage Resolve Develop Review Review Define Conversion Review Provide Approve
3 the
a • • • • • • • * • 6 • • • • • • • • •
— — Analysis Conversion
Configuration External
Training Customizations Customizations Approved for Plan System Data Plan
Approved
Delivcrab Team Team Customizations Conversion Legacy Manual Interface
Technical Functional Software Designs Software Results Data and and System
Test Data Load
Attend Attend Training Application Functional Application System Software System Approve Crosswalks Cleanse COA Approve
NIBS IV 3.2.6 3.2.1.1 3.4.2.2.6 3.4.3.6 3.4.4 3.5.1.2.6 3.5.3.3 3.5.4.5 3.5.5.4 3.6.1.2.6

above 3 external and 3 the project by and designed and process
assumptions Advantage Advantage and 3 the schedule designed cases, test being cases, Customizations reporting
developed functional and interfaces: between County's Advantage systems per Plan project being 70 unit 10 the test unit County: issue
County interface, cases, system the and between Forms the per above potential reports: above potential the Software
Description all for for test documents developed interfaces 3 interfaces between external Plan and Plan Designs design, Designs design, by delivered established
purpose unit 3 the Advantage of interfaces the in Forms Warehouse Forms designed designed for the per
and Documents potential Advantage County Tested testing testing interfaces and and Report purpose, County Tested Forms purpose, Forms Tested Results results
Products Design including all for System of status between the Outbound Warehouse Data Warehouse all for including for System all for including for System test resolution
Work Contractor: requirements, standard following and the systems interfaces during the outbound Reports, following following and following following and Expected verify for
Interface by Documents, to map Unit tracking external of identified systems of the of Data the for Data the Documents, the Unit the Documents, the Unit and and issues
the developed technical the Developed, for testing external testing results Reports, Reports, Developed, Scripts Scripts identified
develop Design designs develop plan County's the issues the systems the the feedback the complete Design complete complete Design complete Developed, Test Tests project
will being Interface requirements, Inbound will Interfaces Develop the Manage systems Resolve County's Coordinate external Certify Review Provide schedule Approve will Report assumptions will Reports will Forms assumptions will Forms Develop Execute Document the
County 35 the • • County • a and • • the • • a • a County CG1: a County • County CGI: by • County a • a a for
(County Testing County and Responsibility) Responsibility) Responsibility) Responsibility)
Name (County in Warehouse Test
.,:..i .:ilile Design Software Interface Interfaces Data (County (County (County (County Iteration
0, Interface interface Track and Outbound Systems Report, Designs Software Designs Software Client
Responsibility) Responsibility) Plan
System System Manage Test Agency Approve Form Reports Reports Forms Forms Conduct
# 3.6.2.3.3 3.6.2 3.6.4.1 3.6.4.2 3.7.1.2.6 3.7.2.3.2 3.7.3.2.3 3.7.4.1.2.2 3.7.4.2.2.4 3.9.1

schedule schedule issue Advantage implemented groups, on based
project project established schedule schedule schedule during be 3 user groups project the
the schedule the schedule the project to Advantage identify groups user per
per per Results per project the project processes requirements control, user to
Plan project Results project issues the schedule per the for by access implementation
Description Test the Test the per following: Expected document per project Results per workflow workflow workflow setup resources grant
and Plan System per Plan Results System Results the of tested and Meeting and Plan Test the Test Results Test processes and and and security 3user groups, 3
Products Testing Test Test Test Test consisting be to Scripts Kickoff results Plan per Plan Results workflow security security security for Advantage user updates Advantage
Work System Integrated System System Integrated System Acceptance responsibilities Test Test Tests Test project Test Performance Test Test Performance Performance current resources and Procedures for
the the Plan functionality procedures the the the and new establishing 3 to rules Procedures
Integrated for Integrated Integrated for Integrated User Test of and Acceptance Acceptance Acceptance Acceptance for Performance for Performance Performance for Integrated security the to analyze 3 Advantage access workflow User
the feedback the the feedback the for plan Acceptance roles tracking User User User User process the feedback the the feedback the legacy impacts and Advantage for plan the security the rules for plan User the
Identification
Review Provide Approve Review Provide Approve Develop User Defined Updated Develop Conduct Execute Review reporting Review Provide Approve Review Provide Approve Review Analyze Document during Develop Identify grant Identify workflow Develop Update schedule
n . . 3 and
* * * e * • • * • 8 • 0 • e • • * • • * • • • • •
Plan Results & and
Name Testing Test Plan Scripts Security & Plan
System System Results Test Test Workflow
, and System Procedures
Integrated Integrated Scripts Performance Performance Legacy and &
Plan, Security Policy
Approve Approve UAT Approve Approve Results Analyze Workflow Setup User Execution
# RS 3.9.2.1.2.6 3.9.2.2.7 3.9.3.3 3.9.4.1.2.6 3.9.4.2.4 3.8.3.5 3.10.2.4
W 3.8.1

End and operations mock
schedule include: prerequisites for and
to feedback materials project production Assessment Departments testing
project schedule objectives, training the the per results
the infoAdvantage plus: user per training in 3 Readiness County software
Description per Plan project and training end environment needed, to Training databases Advantage by Conversion Conversion the
the 3 assessment the and participants as changes User training Mock Mock during
and /Security per Plan Advantage courses volumes the of Program describing training the per End _operating Implementation Readiness of during identified
Products Plan Usage for training results Train-the-Trainer the of training Training documentation, needed, for restore the execution
Work Security / System Security / needs of training of the Train-the-Trainer catalog for identify training User and as feedback and for during Implementation and Conversion identified activities
Usage the Usage training description curriculum groups assessment of course methods administration to Materials for facilities Training End materials databases, the on backup to Readiness identified of planning Mock differences cleansing
System for System of and course needs comprised the of training content of and process Users training User for based processes Department status the the of
the feedback the assessment training Plan user Establishing of Training End the End Feedback training Training training issues overall in results the data
Review Provide Approve Structure Proposed Target Preliminary Resource Training Description End course and Description Definition Create Register Provide Conduct Secure Update Update documentation Establish processes Conduct Resolve Track Participate VerifY Reconcile Complete conversion
• 6 0 An 8 o o o o o 0 o o o o • • • 0 0 0 0 User 0 • • * • • • • •
Delivery and &
& Updates Updates Assessment Conversion Cleansing
Name Plan
Security Materials Materials Database Readiness Mock Data
Deliver:01k
/ Plan Training Training Training Reconcile Additional
Usage Training User Maintenance Implementation & Preparation
System End Ongoing Ongoing Verify results Perform
Ph
WBS If 3.10.2.3 3.12.1.2.5 3.12.3.8 3.12.5 3.12.5 3.13.4 ..kJiico.: 4.2.2.2 4.7.2.3
lw

3
Advantage Go-Live
of after
usage
operations
Descriptioa production
for production
and users
Products end ongoing readiness rehearsal
Plan support support County
Work Cutover to to cutover cutover the use
Plan to Plan team team production production to production
Cutover Feedback Cutover functional technical hand-off in
Go-Live for for is
Review Provide Approve Identify Identify Support Support Operations System
after
0 * • e e • • * *
in
Roles
Name
Go-Live
Deliverable Plan post Production
Cutover for in 3
Staff
Approve Assign Operation Advantage
1/
WI 4.3.1.6 4.3.2.5 4.3.2.4

...._. ;.;rI
.1 the ;0
I to PLGFS825. RRPT.TXT J.,1111C ih(,
Inni- n'iini Ui up li.) on
.A;:dier ,,
OR I Joni ftp'd by pOintiiii_j :wit,
file/156.42.47.21.23 ,01-1 I. RRPT. c
of , then used ,
' i is and fltd0 _ . pu,cnc;a
DELETED - h;ii7 (- 10 and
1 t tiiitt iconi Wr?lt: Rob BRSM his ...._
- , FILETRAN i , ii 1 minutes ._..
BE sending tti.n or into 01.
•mtleiit.,, ir40 ;twititling I:, it01, storyd :' t.-
MAY ......._ ihttps://treasurer.maricopa.gov/agency/ ihttps://treasurer.maricopa.gov/agency/ is 4.4 013i. Nancy 255.255.255.128/156.42.47.21:23 into ,- j.s `:-": , ___... 56.42.47.21.23/156.42.103.151
, 156.42.47.21:23NVebsite: who ii' " n , I I ,i to file loaded ,,,Wa0 i(:;..:5 . 13
1156.42.47.21:23/Website: fIr;fili,t 1`..)(.-42 ini
...._ on RI i i A emailed get , add ___........._
SERVICES :1/ i - t3 CALBUD to ,,i0 -;,.,InBeft
.,.....)..._ depends ___ "Jul 'mainframe files IBRPT.TXT 1 jp laddreSS
_ hop tii i !File
, 1 i z , 11 1 2 '
OR 95
39/
3 3 2 1 i
daily monthly
PRODUCTS, ,
Interfaces _...___ Daily Daily Bi-Weekly :iy fttily Daliy Request Daily Animal Yearly monthly monthly ,Iiii iily/monthly
1;.
On
c'
SCHEDULES, i
System ADJUSTED). PUT t7if IT
OUTPUT OUTPUT INPUT BUiPii: _.,_..... INPUT! OUTPUT INPUT I OU3PuI INPUT INPUT OUTPUT
OP MM.
Legacy AND ' / I
PRICING
B-5.3 F-1P 'FTP FTP s FTP FTP ) t-TP FTP FTP IP FTI-
COMPLETE AI\i'D ) il I 1 i . ,.
Attachment age , Web
IS ADDED of ,ritage
Treasurers Treasurer's Advantage -- Advantage ,Advantage Advantage ctlfi.„,•
Office Office Bank !America t — .Advan '11"7_, IRS Report
1 A 1 i
13082 •
ENVISIONING
Finance
ttig,..i ---_ ,i.
avantage Advantage of il ;AiItnntine Elections Materials Management Advantage IAdvantage Advantage uo Advantage
Dept „ loalM Advaitt
AFTER ' ..... I f 1 t
to
-..1
Upload i , in
REVISED to irNii ,'ic
io Uple
iransfer Manual - I Mandates
i:,ini 1.-
BE - i - Ir.?'
2 i\
MAY Step Step - Car'e
- - t'iri;iie
server :-.. 1
EXHIBIT interface Interface , r-11 - Ica riaci.'—lenith
Site , -ile:: ,,r 1 iti
interface Ari :\n I RRPT
/v 3 ofi. Web
(THIS 1AZMET-V1/01-P ti, 01 into' 1099 /
11Treasurer's Treasurer's Treasurer's Payroll ::t Elections P-card 1 CALBUD Report
•-.1i,.;„i- Hr'i,:ink '"1onk Fro7-3:;1 IRS BRPT
„ 2 3 1 I' I 7 1 8 ; 10 1 12 1 1 141 i

Ma ip
IN IN
on to Li) thilowing
OR oci
the
NO, o
MAY ht,
DELETED 0 ard29
BE /156.42.47.21.23 TiMt1 job 21
Youni„ 12,T7.21.23 „„..„ IN by
MAY TI -batch 156.42.132.51
-ii-I-T.l;Tb\-.7 AT in
LnI ,iii,:,776-ETT _0
SERVICES 1156.42.91.144 to tt-i FiTHTI-UTURF Iperfortne—i,"
FOX -FFF6x- ii-72:7 laddress
;
OR
3 -Cah14-.Ji able
50
PRODUCTS, 1
twice ;Nit t,; II I
Interfaces or month Onfy od i voriec io 133.11 Daily
on
;once
System SCHEDULES, ADJUSTED).
INPUT OUTPUT INPUT 111' Output
OU1, IN,
Legacy AND
PRICING
nFIOet Connect
B-5.3 COMPLETE 1FTP IL FIf FT !FT TL' f I In
AND ft
ottig an1incio,
Attachment IS ADDED !...t 6411 Ii
Advantage iAdvantaho iAav,LLiiiioe IAcivcntncie rayantage
Hro jf\dvu F
13082 ENVISIONING
Finance Finance, !-2ept
`'
ilynntage of I()hills Mannnernent CY! o1
Pitney IJCpt cot Frea Sherirr
AFTER
IS
REVISED I)
oryer
BE
C
MAY 1)92
tii-oc,t liiinani.te
EXHIBIT Dih
of Ot
Bowes Advahtapit Cor irli:'!11 Office
(THIS -
Pitney Ito PayroIl p(!;!:.11 Sheriffs
it
_ 18j 11 27, "21' 28
i

OR
DELETED 162.70.72.65 162.70.72.65 162.70.72.65 SERVER
13E 156.42.184_124 is IF 156.42.184.124 is IP 162.70.3.10 is IF 162.70.3.26 COUNTY SERVER
MAY (mainframe) (mainframe) is IP (mainframe) is IF COUNTY
is IF is 156.42.103.152 IARICOPA
SERVICES 1Source 'Destination Source 'Source Destination !Source [Destination 1MARICOPA
OR
70 70
PRODUCTS,
Interfaces weekly Daily DAI weekly Daily Request Daily Daily Request monthly
SCHEDULES, ADJU:TIED). On On 1 1
System output Input inpu Input Input OUTPUT OUTPUT INPUT Output
Legacy AND I 1
PRICING
B-5,3 COMPLETE AND Ittp 1FTP FTP FIR -1-FTP FTP
Attachment IS ADDED iviaricopa Advantage Advantage Advantage Advantage Base Advantage Advantage Advantage Advantage 'ADVANTAGE Az of
13082 On 'Info !Info 1 1 State
ENVISIONING
Mainframe Server Server Server Server Mainframe Mainframe
AFTER CGI CHX Finance Finance X Advantage Finance 'Finance CGI CGI MCAO server Ifto
i
REVISED
BE Voucher-JV) Voucher-PV) registration) interface
SR
MAY Journal (Payment (Vendor Enforcement
EXHIBIT changes) erface Interface interface interface Check
(THIS VvatcH'og Interface In Finance 42IAZMET-D01-P 43AZMET-D02-N 451Transparency
ri t 331 (COA 34ICFIX 36IFinance 371Finance 3810SO 39i 40IFinance 1 !County 441IVIVICT
41

13082 Attachment B-5.4 Legacy System Reports
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES
MAY BE DELETED OR ADDED AND PRICING ADJUSTED).
Name Description Frequency
MAPS Claims Processing 'MAPS Claims Processing (IW102) Daily
Primary Vendor - Audi I Primary Vendor - Audit from PLGFS750 Daily
Remit Vendors on Hold Remit Vendors on Hold - From PLGFS236 Daily
Voucher Payment - EFT Voucher Payment - EFT (EFTDISB-F) Daily
Warrant Reg-Ven (IW101B) Warrant Registers - Vendor (IW101B-F) Daily
1099 Vendor Changes 1099 Vendor Changes from Venreg3 Daily
A656 - Unsched Pay Turn A656 - Unscheduled Payment Turnaround - PLGFS502 Daily
A657 - Checks ritten A657 - Checks Written from PLGFS220 Daily
Daily ADIS Daily ADIS from PLGFS220 Daily
Discount - EFT Discount Taken or Lost - EFT (EFTD SC-S Daily
Discount - Warrant Discount Taken or Lost - arran ARDISC-S Daily
EF01 - EFT Payments EF01 - EFT Payments from PLGF-S220 Daily
EFCG - EFT Tape Register EFCG - EFT Tape Register from PLGFS220 Daily
EFPN - Prenote Selection EFPN - Prenote Selection from PLGES220 Daily
EFT Treasurer Form EFTCNRPT - Trans Doc from PLGES220 Daily
Primary Vendor - Errors Primary Vendor - Errors from PLGFS750 Daily
TP ID Discrepancies TP ID Discrepancies - From VENMNT2 Daily
TX Vendor Compare TX Vendor Compare from PLGFS752
TX Vendors Generated TX Vendors Generated from VENMNT3
Vendor Maintenance Audit Vendor Maintenance Audit from VENMNT1
Warrant Reg-Dept (IW101A arrant Registers - Departmental (IW101A-S)
Warrant Reg-Vch (IW101C arrant Registers - Voucher (IW101C-F
1099 Indicator Changes 1099 Indicator Changes from VENMNT2
A655 - Sched Pay Turn A655 - Scheduled Payment Turnaround from PLGFS502
A657-A - CHECKS WRI I I EN A657 - CHECKS WRITTEN (PLGFS A657A.TXT)
A945 - Bkup Withhlding A945 - Backup Withholding Report from PLGFS882
ADIS Listing ADIS Listing from PLGFS502
EF02 - E EF02 - EFT Payments from PLGFS220
EFVS - EFT Vouchers from PLGFS220
ITEPPW - Buyer Worksheet ITEPPW - Buyer Requisition Worksheet - PLGFS802 1Daily
IW103 - Garnishments IW103 - Garnishments from PLGFS221 Daily
JV Daily Detai JV Detail (JVORDRP.TXT) Daily
COMM PO DETAIL (IA611P) COMM PO DETAIL (IA611P.NEW) Monthly
FIN STAT AGCY-ORG (480A) Monthly
FUNCTION AGCY-ORG-PRD I FUNCTION AGCY-ORG-PRD (FUNC1PRD.NEW) Monthly
IBUYPG - Blanket Orders IIBUYPG - Blanket Orders by Buyer from PLGES893
JV BY JV NUMBER (JVORRPM) JV BY JV NUMBER (JVORRPM.NEW)
P Card Trans Cntl P Card Transaction Control from PLGFS707 Monthly
REV & EXP FUND (IA482) REV & EXP FUND (IA482.NEW) Monthly
BS SUMMARY-USE TAX (701A) BS SUMMARY-USE TAX (AA701A.NEW) Monthly
COMM PO SUMMARY (IA611PS) COMM PO SUMMARY (IA611PS.NEW) Monthly
DISC. WARRANTS (M658RPT) DISC. WARRANTS (M658RPT.NEW) Monthly
DISCOUNT EFT (M658EFT) DISCOUNT EFT (M658EFT.NEW) Monthly
EPS OPEN ITEMS (EPSORPT) Monthly

13082 Attachment B-5.4 Legacy System Reports
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES
MAY BE DELETED OR ADDED AND PRICING ADJUSTED).
Name Description Frequency
FIN STAT AGCY-ORG (480S) FIN STAT AGCY-ORG (IA480S.NEW) Monthly
FIN STAT-ACTIVITY (IA470) FIN STAT-ACTIVITY (IA470.NEW) Monthly
GENE FLIIL ..1)1L friLRAL LEDGER (IA611BC.NEW) Monthly
PAS AGENCY CLASS PRD PAS AGENCY CLASS PRD (PAS1PRD.NEW) Monthly
PAS AGENCY CLASS-YTD PAS AGENCY CLASS-YTD (PAS1YTD.NEW) Monthly
PAS AGENCY-ORG PRD PAS AGENCY-ORG PRD (PAS2PRD.NEW) -Monthly
PAS AGENCY-ORG YTD PAS AGENCY-ORG YTD (PAS2YTD.NEW) Monthly
REV & EXP AGENCY (IA481) REV & EXP AGENCY A481.NEW) Monthly
BS DETAIL-USE TAX (602A BS DETAIL-USE TAX (IA602A.NEW) Monthly
DETAIL REV & EXP ( A611A) DETAIL REV & EXP (IA611A.NEW) Monthly
- //!HrtniHL EPPX - Price Agreement by Buyer from PLGFS231 Monthly
ttri-ccrr-Hr- :, FUNCTION AGENCY-ORG-YTD (FUNC1YTD.NE Monthly
GRANT DETAIL (IA611G) GRANT DETAIL (IA611G.NEW) Monthly
DMTHPG - Contracts DMTHPG - Monthly Contract Report Monthly
IV801R-Minority Vendor IV801R-Minority Vendor Report from PLGES895 Quarterly
IV801T-Minority Activity IV801T-Minority Quarterly Activity from PLGFS895 uarterly
V801-Minority Summary V801-Minority Vendor Summary from PLGFS895 uarterly
EPSORPT2-Curr BFY EPSORPT2 - PO Report for Current BFY Weekly
H Weekly Receiver Activ Weekly
H Weekly Stock Req H Weekly Stock Requisition - PLGFS270 Weekly
AGED SUSF LIST Weekly
EPSORPT1-Prior BFY EPSORPT1 - PO Report for Prior BFY Weekly
ITAGRX1 - Aged Reqs ITAGRX1 - Aged Requistions
WH Weekly Inventory Level H Weekly Inventory Level Weekly
IC801 Commodity Report IC801 Monthly Commodity Report Yearly
IC801A Commodity Vendor IC801A Monthly Commodity Vendor Activity Yearly
IC803 - BUYER ACTIVITY IC803 - MONTHLY BUYER ACTIVITY REPORT Yearly
ICATRPT.TXT COMMODITY BY SUB CLASS BY CLASS BY CATEGORY Yearly
NYRQ - Req Clearing NYRQ - Requistion Clearing from PI_GFS977 Yearly
NYSA Report Year end report Yearly
PLGFS910 Exceptions PLGES910 Report 2 from FRM1099 Yearly
PLGES910 Forms PLGES910 Report 1 from FRM1099 Yearly
PLGFS911 Exceptions PLGFS911 Report 2 from FRM1099 Yearly
PLGFS913 Audit PLGES913 Report 1 from MAG1099 Yearly
PLGFS913 Exceptions PLGFS913 Report 2 from FRM1099 Yearly
PLGFS913 Forms PLGES913 Report 1from FRM1099 Yearly
SA1 CLS YTD REPT Year End Balance report SA1 Yearly
SVNDCNT.TXT VENDOR COUNT BY SUFFIX CHARACTER Yea rly
Y964 - VVVR Y964 - Vinc vs Ven2 Report from PLGFS964 Yearly
Closed Bud Report SA1 Year END Budget Yearly
Fixed Assets year End A New Report Yearly
IDMTHPG-Old Rpts IDMTFiPG MONTHLY CONTRACT REPORT Yearly
ITAGRX1-Old Rpts AGED REQUISITIONS Yearly
Year End SA1 Report Year End balance Report Yearly

13082 Attachment B-5.4 Legacy System Reports
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES
MAY BE DELETED OR ADDED AND PRICING ADJUSTED).
Name Description
Vinc Vend Except Vinc Vend Exception Repor Yearly
BUDGET SA1 Report Budget Close report Yearly
EPNY - PO Roll Report EPNY - PO Roll Report from PLGES972 Yearly
EPSORPT1-0Id Rpts PO REPORT PRIOR BFY Yearly
PVNDCNT.TXT VENDOR COUNT BY PREFIX Yearly
Trial Balance w/TACBAL Trial Balance w/TACBAL Yearly
V1NC Update Report VINC Update Report from PLGES436 Yearly
Trial Balance (A614)
Rev & Exp Fund-Agcy (483) 'Monthly

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
RECORD LOG pr-n(ST:77
Tck NAME
COUNT ENGTH Lti t\rt-ES
1 ACCOUNT-TYPE-TABLE 44 42 1,008
2 ACCOUNTING-PRD-TABLE 30 24 6,984
3 ACTIVITY-TABLE 79 71 2,266,604
4 ACTIVITY-CAT-TABLE 50 42 88,956
5 ACTIVITY-CLASS-TABLE 50 42 300,804
6 ACTIVITY-GROUP-TABLE 14 48 42 588
7 ACTIVITY-TYPE-TABLE 0 50 42 0
8 AGENCY-TABLE 132 125 657,625
9 ALLOTMENT-TABLE 87 56 81,984
10 APPROPRIATION-TABLE 2,168 370 346 750,128
11 BS-ACCOUNT-TABLE 5,78 76 68 393,108
2 BS-ACCOUNT-BAL-TABLE ,544 28 99,232
BS-CATEGORY-TABLE 48 42 0
BS-CLASS-TABLE 42 49 42 1,764
BANK-ACCOUNT-TABLE 28 7 2,268
CALENDAR-DATE-TABLE 8,810 5 7 61,670
ODITY-TABLE 9,49 227 213 2,022,009
EXPENSE-BUDGET-TABLE 6,404,054 225 189 1,210,366,206
FISC-YEAR-TABLE 23 20 16 368
FUND-TABLE 3,143 05 97 304,871
ENCY-TABLE 8,248 18 148,464
22 FUND-BALANCE-TABLE 0 28 0
23 FUND-TYPE-TABLE 14 0 420
24 GRANT-TABLE 0 61 0
25 OBJECT-TABLE 58 78,126
26 OBJ-CATEGORY-TABLE 358 48 42 15,036
27 OBJECT-CLASS-TABLE 648 49 42 27,216,
29 OPEN-PO-HEADER-TABLE 1 20 95 95
OPEN-PO-LINE-TABLE 189 162 162
OPEN-REQ-TABLE 104 90
999,591 27 246 24578-99,38-6-
OPEN-PV-LINE-TABLE 2,366,022 352 740,564,886
ORGANIZATION-TABLE 61,816 139 7,912,448
PROJ ECT-TABLE 0 93 85 0
197 542 531 104,607
156,099 58 47 7,336,653
105,200 110 11,572,000
16 6,762
REVENUE-CLASS-TABLE 300 12,600
4 REVENUE-SOURCE-TABLE 649 40,238
42 SUB-OBJECT-TABLE 7,97 55 358,785
43 SUB-ORG-TABLE 55 0
44 SUB-REV-SOURCE-TABLE 2 131,880
45 SYS-CTL-OPT-TABLE 20 154 150 3,000
46 SYS-SPEC-ACCT-TABLE 20 146 142 2,840

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
-ORD I TG 1iICAL I TOTAL
NAME
47IVENDOR-TABLE 64,454 561
48j GEN-REPT-CAT-TABLE 0 42
49 CR-DAILY-SUM-TABLE 28
JOB-TABLE —1T6-6" -393
OPEN-PO-BY-O0C-TABLE 25
5210PEN-PV-BY-DOC-TABLE 999,591 25 0
CHECK-CATEGORY-TABLE 2 510
54 AUTO-DISB-PARM-TABLE 231 223 1,115
55 APPLICAT1ON-DATES-TA 140 136 28,696
56dCHARGE-CLASS-TABLE 0 53 46
57 PERF-ACTUAL-TABLE 61 28 0
PERFORMANCE-TABLE 56 48
BUDGET-REPORT-SUM MAR 92 156
ONLINE-GENERAL-LEDGE 19,761,040 159 84 1,659,927,360
61 REV-BUD-REPORT-TABLE 0 174 151 0
62 INVESTMENT-TABLE 356 0
63 INV-SPEC-ACCT-TABLE 153 149 0'
POOL-BALANCE-TABLE 100 92
SECURITY-TYPE-TABLE 41
66 P-0-0-L-THET' OR' Y-TABLE 30 14
67 BLOCK-TABLE 251 242
68 CASF-I-COLLECT-TABLE 54 14 0
69 PARTICIPATION-TABLE 100 84 0
1,649 24 70 115,430
117 83,187
54 109 1,790,434
16,428 41 73 1,199,244
661 30 72 47,592
75 $1NDEX-COLUMNS 4,163 38 96 399,648
761E-UPDATE-PREP-SCREEN 0 156 117 0
E-GUIDELINES-SCREEN 4
78IBUDGET-TYPE-SCREEN 0 30
79IABP-SECURITY-SCREEN
80 OPEN-IN-LINE-TABLE 159 14
81 OPEN-IN-HEADER-TABLE 0 0
82 DOC:CTL-TABLE 649,942 8 5,199,536
84 REPORT-STATUS-TABLE 0 100 83 _ 0
85 AGENCY-GRANT-TABLE 4,675 341 326 4,784,050
86 ENTITYWIDE-GR-IVT-TABL 182 70 ,133,050
87 GRANT-DESCRIPTION-TA 170 0
88 GRANT-BUDGET-LINE-TA 18,8 127 2,035,800
89 GRANT-FY-TABLE 63,949 26 15,219,862
90 BUDGET-PCT-TABLE 20 20
92 IN-TEXT-TABLE _ 103
93 PRINTED- FOTTA-BLE. 24 8

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
PO-HOLD-TABLE
SPECIAL-INST-TABLE 1,920
WARRANT -s- ARY-TABL 0
WARRANT-RECON-TABLE 69,778,320
DISCOUNT-TYPE-TABLE 1,860
JOB:-ORGANITATIo—RiT5
FA-DISPOSITION-LEDGE
GENERAL-LEDGER
103 1,452
104 343 3631
105 3431 _363
10 3431 .3-6-3. I 0
107 3431 -- 3631 0
109 343 726
110 343 0
343
133! COMMODITY-LEDGER
34IFA-LEDGER
PROJECT-LEDGER
TEMP-INVEST-LEDGER 300 320
INVEST-HIST-LEDGER 0 00
LOGICAL VIEW DEFINIT 447 28 76 33,972
ACCESSDEF-TABLE 29 83 747
BEGIN-DAY-TABLE 4 32 190 2,660
153 FILE-DEFINITION-TABL 62 124 11,780
154 TABLEDEF-TABLE 41 103 73,336
154 TABLEDEF-TABLE 711 41 103 73,233
155 FORMAT-DEFINITION-TA 828 2317 2379 1,969,812
156 NXTCRT-ALONE 217 2167 2227 483,259
7,926 1972 1975 15,653,850
596 3 404 240,784
54 50 5,550
1621FA-ACQ-DISP-TABLE 22 45 43 946
163 WHERE-TABLE 2 106 212
1641FORWHOM-TABLE 4,363 66 287,958
165 APPROVAL-TABLE 48 126 6,048
166 ERROR-TABLE 11,422 45 106 1,210,732

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
CORD PHYSICAL
NAME
701..11-17 NGTH LENGTH ES
167 ,065 021 308 3,281,265
168 HELP-SCREEN 55,758 90 92 5,129,736
169 LEAF-SCREEN 508 304 366 185,928
170 GMSS-TABLE 0 758 750 0
171 AMSS-TABLE 0 761 0
172 FA-GROUP-CLASS-TABLE 30 46 1,260
173 FA-LOCATION-TABLE 886 51 41,642
---17.4 FA-LOC-CAT-TABLE 73
175 FA-LOC-CLASS-TABLE
176 FA-VALUATION-TABLE
177 FA-CATALOG-TABLE
178 FA-SUMMARY-TABLE
FA-BETTERMENT-TAB E
POOL-BASE-DEF-TABLE
ALLC-GRP-CONTROL-TBL
MFG-NAME-COMMOD-TAB 0
POOL-ACCUM-TABLE 0
FA-TYPE-TABLE 312
185 FA-GROUP-TABLE 1,410
186 FA-GROUP-CAT-TABLE 546
187 FA-DOC-INQ-TABLE 0
188 REPORT-TABLE 0
1891JCL-TABLE 17,680
- 190 CATEGORY-TABLE 152,820
192 COM MODITY-CATEGORY-S 0
197 PV-GENERATION-TABLE 38 798
201 REPORT-ID-TABLE 576
202 REPORT-GROUP 305
203 REPORT-GROUP-ID 737
2041RPRT-FI LE-LOC-TABLE 202
205 IA I I RIBUTE-LOC-TABLE 172 4,98 :8]
207 MEDIA-TABLE 160 320
208 VENDOR-INCOME-TABLE 30 ,064,070
209 REIN-TABLE 121 0
210 IN-HOLD-TABLE 1 0
2111RECU RR ING-JV-TABLE 191 225,953
277 113,293
504 7,056
126 9,450
27 20,007
106 0
47 282
34 408
222 INV-FREEZE-TABLE 30 0
223 INVENTORY-TABLE 233

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
RECORD LOG P TOTAL
TABLE # NAME
COUNT LENGTH BYTES
224 ISSUE-QUEUE-TABLE
225 ITEM-GROUP-TABLE
22610PEN-SR-ACCT-LINE-TA 2,873,958
227 OPEN-SR-COMM-LINE-TA 11,411,904
22810PEN-SR-HEADER-TABLE 5,185,026
229 OPEN-TR-HEADER-TABLE 21,714
230 OPEN-TR-LINE-TABLE 5,781
231 RETURN-CODE-TABLE 8 6
232 WAREHOUSE-TABLE
233 WAREHOUSE-GROUP-TABL
234 OPEN-SR-COMM-1SSUES-
235 DRIVER-CONTROL-TABLE 82 55
FA-GROUP-LOCATION-TA 14,859 54
238 PO-ACCOUNT-DISTRIBUT 106,031 85
239 OPEN-IN-PROVIDER-TAB 0 25
240 PO-TEXT-TABLE-STD ,622 103
0 41
--
36 47
0 42 _39
34 _32 256
245 OPEN-PC-HEADER-TABLE 91,940 363 337 30,983,780
246 OPEN-PC-ACCT-L-TABLE 106,031 225 197 20,888,107
247 OPEN-PC-COMM-L-TABLE 119,790 439 410 49,113,900,
248 OPEN-RC-HEADER-TABLE 357,108 1-37) 114 40,710,312
249 OPEN-RC-LINE-TABLE 884,888 14-6 121 107,071,448
250 OPEN-RQ-HEADER-TABLE 1,280 433 417 533,760
251 OPEN-RQ-ACCT-L-TABLE 1,472 120 102 150,144
252 OPEN-RQ-COMM-L-TABLE 1,829 347 328 599,912
253 OPEN-VI-HEADER-TABLE ,469,553 250 225 330,649,425
254 OPEN-VI-LINE-TABLE 0 287 259 0
255 CHANGE-PO-PREP-TABLE 25 292 257 6,425
256 REQ-STATUS-TABLE 35,231 87 66 2,325,246
257 STATUS-TABLE 14 35 32 448
258 SHIP-ADDRESS-TABLE 232 153 150 4,800
259 THREE-WAY-AP-TABLE 0 5 2
260 THREE-WAY-PU-TABLE 11,349 55 4,047
261 UNIT-OF-MEAS-TABLE 132 30 3,960
262 VENDOR-COMMOD-TABLE 1 0
263 VENDOR-NAME-TABLE 64,493 41
268 BID-TEXT-TABLE 4,422
269 PO-TEXT-TABLE 145,769 103
270STANDARD-SPEC-TABLE 210 88
271 RC-TEXT-TABLE 238 93
272 VI-TEXT-TABLE 0 102
273 PA-TEXT-TABLE 96

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
RECORD LOG PHYSICAL 1 AL
TABLE # NAME
COL 7 7'--' 7 LENGTH
274 PA-SUMMARY-TABLE 5,101 164 15 780,45
275 PA-VEND-COMM-TABLE 5,252 91 55 288,860
276 PA-SECURITY-TABLE 1,050 18
277 BID-MASTER-HEADER-TA 243 232
278 B D-MASTER-LINE-TABL 289 27!
279 BID-SELECT-TABLE 153 131
281 BLAI-TABLE
282 BRPP-TABLE 610 16001 0
283 BID-LINE-SEL-TABLE 167 140
284 VENDOR-PERF-TABLE 11,14 337 3261 3,633,270
285 OPEN-PC-BY-DOC-TABLE 91,940 26
286 BIDD-MASTER-RO-TABLE ,829 33 0
287 OPEN-PC-HEADER-MOD-T 117,794 279 251 29,566,294
288 OPEN-PC-ACCT-L-MOD-T 177,770 122 92 16,354,840
289 OPEN-PC-CO -L-MOD-T 47,777 298 267 39,456,459
290 REVENUE-TYPE-TABLE 0 48 42 0
291 FUND-CLASS-TABLE .:.1-0 49 42 76,860
FUND-CAT-TABLE 114 48 42 4,788
FUND-GROUP-TABLE 80 47 42 3,360
OBJECT-TYPE-TABLE 15 48 42 630
295 OBJECT-GROUP-TABL 75 48 42 3,150
296 REVENUE-GROUP-TABLE 39 48 42 1,638
297 BS-GROUP-TABLE 33 48 42 1,386
298 PRINTED-IN-TABLE 44 28 0
299 BANK-ACCT-BAL-TABLE 0 94 84 2,52-0
300 FLEX-LEDGER-TABL2 160 84 0
301 FLEX-LEDGER-TABL2B 160 84 0
304 FA-TEXT-TABLE 86 90 71 6,106
309 1DOC 0 363 350 0
310 FUNCTION-TABLE 0,797 64 56 604,632
311 FUNCTION-CAT-TABLE 80 50 42 3,360
312 FUNCTION-CLASS-TABLE 5,639 50 42 236,838
FUNCTION-GROUP-TABLE 26 48 42
314 FUNCTION-TYPE-TABLE 26 50 4 1,092
315 CASH-SWEEP-TABLE 0
316 CASH-SWEEP-PERM-TABL 0
17 CASH-SWEEP-ACCUM-TAB 22
318 1NV-MGMT-WORK-LEDGER 86
319 CASH-SWEEP-VIEW-TABL 52
320 EXTENDED-LEDGER 391 0
321 BRANCH-CODE-TABLE 0
322 CLASS-CODE-TABLE 0
323 COST-CATEGORY-TABLE
324 CREW-TABLE
325 WO-SYSTEM-CTRL-TABLE

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
RECORD LOG PH' :A TOTAL
NAME
COUNT BYTES
326IDOCUMENT-COST-CATEGO 0 7
327 DELAY-CODE-TABLE 35 0
328 391 411
---------•---n-e-e--
329 PAY-GRADE-TABLE 0 91. 80 0
330 GROUP-CODE-TABLE_ 4
:.l.. JOB-TYPE-TABLE 5
_ LINK-TABLE 17
333LOCATION-CODE-TABLE 9
334 EMPLOYEE-NAME-TABLE 39
335 OBJ-REV-COST-CAT-TAB 0 1_7
336 PAYROLL-CONVEYANCE-T 143
're
POST-LEDGER-TABLE _ 291 26 -
PAYROLL-TABLE 105 96
RATE-TYPE-TABLE 55 52 0
340 RUN-HOURS-CONVEYANCE 6 0
341 REASON-CODE-TABLE 37 31
343 STATUS-CODE-TABLE 11 10
344 WORK-ORDER-EQUIP-RAT 0 24 18
345 TABLE-SUSPENSE-TABLE 2019 2000
346 WO-COMMENT-TABLE 146 118
347 WORK-ORDER-LINES-TAB 305 294 0
348 WORK-ORDER-ESTIMATES 0 67 5.
PROMPT-CONTROL-TABLE 2 5
EQUIP-WORK-ORDER-SET 1010 1002
351 PRINT-TABLE 0 56 48
352 MFG-NUM-COMMOD-TABLE 0 6
353 OP-RQ-INQ-BY-AGY-TAB ,472 25
354 DOCUMENTS-IN-PROCESS 200 87
355 EQUIP-DETAILS-TABLE 94 70
356 EQUIP-DUMMY-I-IRS-TAM. 270 260
3-577 EQUIP --A-V-AILABTLTFY7-- 32 30
EQUIPMENT-COST-TABLE 34 20
EQUIP-GROUP-TABLE 166 60
360 EQUIP-YEARLY-HISTORY _ 101 91
361 7E-Q-U-IPVCIC1717--M—AWETAB-LT. 23 20 0
362 EQUIP-POST-LEDGER 296 274 0
363 1022 1016 0
364 EQUIP-STATUS-TABLE 33 31
365 EQUIPMENT-TYPE-TABLE 57 4 0
366 EQUIP-WORK-ORDER-SU 242 220 0
367 FL-SYSTEM-CTRL-TABLE 33
368 FUEL-TYPE-TABLE 57
369 WORK-ORDER-BY-REASON 20
370IEQUIPMENT-BY-ALT-EQU
371 EQUIPMENT BY LICENSE 19

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
RECORD LOG
'CABLE # NAME
COUNT
372 COMMOD-MFG-TABLE 60
EQUIP-PARTS-LIST-TAB 55
EXCEPTION-TABLE 617 738 -27-952
WHOLE-REPORT-TABLE 218 336 5,040
RDST-TABLE 174 348
O-PC-INQ-VEND-TABLE 106,03 35 0
AGY-ORG-PC-INQ-TABLE 106,031 35 0
COMM-INQ-BY-RQ-TABLE 1,829 3.
COMM-INQ-BY-BID-NO-T 0 28
COMM-INQ-BY-PO-TABLE 119,790 4
382 INSURANCE-TABLE 105 72
__ 383 COMMODITY-CROSS-REF- 79
384 PURCH-AUTH-DEL-TABLE 256 40 ,584
385 VENDOR-ZIP-CODE-TABL 64,454 5. 0
386 VE N D-TEXT-TABLE 28,96 9 2,345,841
387 VENDOR-SORT-NAME-INQ 41 0
388 TRANS-TYPE-TABLE 1,800
-389 MARTFAT[E:----- 250
392 PA-BY-COMM-TABLE 5,252 36 ----- 6
NOTE-PAD-TABLE 6 98 79 474
rt,--
394 COMMODITY-HISTORY-TA 2,877 324 283 3,644,191
395 BDVN-INPUT-SCREEN 14,134 71 16 1,826,144 _
396 PAY-DETAIL-TABLE 58
397 RX-IN-ACTIVE-TABLE 0 30 0
398 CUSTOMER-NAME-TABLE 197 52 2,.167
_ 399 OPV-BY-VENDOR-NAME 999,591 55 0
400 PC-GEN-TABLE-2 0 156 120 0
401 EXTENDED-BEGINDAY- - A .4 365 42
406 COMM-CLASS-TABLE 279 60 16,740
407 COMM-CLASS-DESC-TBL 279 0
408 COMM-SUBCLASS-BY-COM 8,997 60 539,820
409 COMM-SUB-CLS-BY-DESC 8,997
410 USER-TABLE 3 115 95 3,135
411 COMM-BY-COMM-CLS-SEL
412 COMM-BY-DESC-SEL-TBL
413 OPEN-PO-BY-DEL-DATE
414 OPEN-PO-BY-BUYER-TBL
415 OPEN-PO-BY-BLANK-TBL
416 OPEN-PO-COMM-LINE-TB
417 PO-COMM-LINE-BY-VEND
418 PO-COMM-LINE-BY-COMM
419 USERID-TABLE
420
421 PC-GEN-TABLE-1
422 RC-GEN-TABLE

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
LOG 1SICAL TOTAL
:ABLE ft 1 NAME
LENGTH NGTH BYTES
VI-GEN-TABLE
DC-GEN-TABLE
4251INV-BY-STOCK-ITEM-SE
4291ITEM-GRP-BY-STK-ITEM
____ 430 REQ-ITEM-BY-ISS-RET-
431 EQUIP-PM-MASTER-TABL
EQU I P-COST-ALLOC-TAB
433 P-M-CONTROL-TABLE 201 17
434 561 120
43 RENTAL-RATES-UPDATE
436 SCHED-PM-EQUIP-TABLE 58 521
437 PM-SPECIFICATIONS-TA 750 728
438 --EQUIP-PM-ATTRIBUTES 5661
EQUIP-USER-CODE 30
EQUIP-WARRANTY-TABLE 66
0
451 PROJ-STATUS-TABLE 168
PROJECT-PHASE-TABLE 1,419
I —16 "N :IT 0
PROJ-BUD-LINE-TABLE2
AGENCY-PROJ-TABLE
E-N7F7TP—R-6J -TWEE
PROJECT-FY-TABLE 2,686 85 188,020
459 PROJECT-BILLING-LEDG —01 200
460 AGENCY-FED-AID-TABLE 740
462 FED-AID-BUD-LINE-TAB 141
463 FED-AID-FED-FY-TABLE 317
464 GOVWIDE-FED-AID-TABL 48
465 FED-AID-INFER-TABLE
466 FAID-STATUS-TABLE 44
FEDERAL-AGENCY-TABLE 44
468 ETM—P7-1-3—Lis 40
FEDAID-LEDGER 200 220
470 FUNDING-SOURCE-TABLE 284 276
471 PROJ-FUNDING-SOURCE- 88 70
472 PROJECT-XREF-TABLE 6
473 FUNDING-SOURCE-INVES 93
474 FUNDING-SRCE-INTRST-
475IFUNDING-SOURCE-TEXT- 82
476 PROJ-ALLOC-GROUP-TAB 56
477 SUSP-REAS-TBL 30
CMIA-LEDGER 0
REALTIME-LEDGER-TABL 4,616 387,744
BDIT-BID-TRACKING-IN 5 0 01_ 4891 978
DRAWDOWN-REQUEST-TAB 861 28

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
RECORD :AL AL
NAME
LENG7H ES
487 DRDOWN-REQ-BY-PROG-T 58
488 DRAWDOWN-REQUEST-DAT 2
489 DRAWDOWN-REQ-BY-G ROU 58
491 DRAWDOWN-GROUP-TABLE 32
492 CLEARANCE-PATTERN-SU 31
493 HOLIDAY-TABLE 8
495 C A-CTL-OPT-TABLE 37
496 CMIA-SCHED-INV-REC-T 0 38 14 0
497 DOCUMENT-HISTORY-TAB 10,894,720 149 72 784,419,840
498 DOC-XREF-TABLE 16,626,154 90 47 781,429,238
499 VEND-XREF-TABLE 6,157,344 54
500 PROJECT-SUMMARY-TAB 266 243 0
501 LETTER-OF-CREDIT-STA 57 42
502 ACTIVITY-EXCEPTION-T
503 0 BJ ECT-EXCEPTION-TAB
504 TRANS-EXCEPTION-TABL
505 FUND-SOURCE-TABLE
506 PROJECT-BILLING-PARM
FUNDING-SRC-SUM MARY-
OBLIG-AUTE-i-STATUS-TA
STATE-BOND-PGM-TABLE 0
STATE-OBLIGATION-TAB
FEDERAL-OBLIGATION-T
512 PHASE-ACTIVITY-TABLE
513 ITEMIZED-CAPITAL-TAB
514 SUB-PROJECT-DESCRIF
515 SPONSOR-TABLE
516 SUSP-TRANSFER-TABLE
517 PROGRAM-PROVIDER-TAB
518 PROJECT-BILLING-TABL
528 TRAVEL-SPECIAL-ACCO—U- 0
529 TP-GEN-TABLE
530IEMPLOYEE-TRAVEL-SUMM
531ITRIP-RECORD-TABLE
533 TRIP-LINE-TABLE
534 TRAVEL-DESTINATION-T
TRAVEL-PURPOSE-TABLE
536 TA CHECK TABLE
537 TRAVEL CHECK INQUIRY
5391VENDOR-REPORT-DESC-T
5401 REPORT-TINNUM-TABLE
54110RIGINAL-1099-INFO-T
542 ORIG-VENDOR-RELATION
543 PAYER-INFO-1099-TABL
544 THRESHOLDS-1099-TABL

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
RECORD •
ABL NAME
COUNT LU ,E.,TH
545 CORRECTED-1099-INFO- 0 305 289
550 BILL-ADDRESS-TABLE 101 153 15,150
551 B D-RESP-TXT-TABLE 0 0
552 FA-LOCAT-SUM-TABLE 14,859 20
553 VENDOR-SORT-NAME-TAB 0 4'
554 VEND-CLASS-SUBCLASS- 17
555 OPEN-ITEMS-BY-STK-NU 116,589 6
556 GROUP-1-TABLE 41 31
557 GROUP-2-TABLE 10 0
558 INVENTORY-REPLENISHM 29 76 31 899
559 881 2395 2417 2,129,3/7
560 PACO-TABLE 0 119 71 0
561 VENDOR-FEDNUM-TABLE 64,454 2 128,908
562 OPEN-RQ-HEADER-MOD-T 1,296 389 371 480,816
563 OPEN-RQ-ACCT-L-MOD-T ,492 122 102 52,184
564 OPEN-RQ-COMM-L-MOD-T 1,847 290 269 496,843
565 PO-PREP-BY-RQ-TABLE 25 35
566 COST-ACCT-TYPE-TABLE
567 AGED-REQ-BY-BUYER-TA 46 0
568 COST-ALI_OC-POOL-SEQ- 0 68 0
569 OBJ-REV-CLASS-TABLE 0
570 FWD-REF-STEP-TABLE 0
571 ALLOC-TOTALS-TABLE 125 0
572 COST-ALLC-GEN-LEDGER 0 148 0
573 MILESTONE-PEFORMANCE 24,227 74 1,792,798
574 REQUISITION-TYPE-TAB 1 42
578 FOREIGN-LANG-TRANS-T 0 17 0
579 APPROVAL-LOG-TABLE 2,847,560 110 42 119,597,520
580 E-BUDGET-PREP-SUMMAR 125 86 0
581 REVENUE-PREP-SUMMARY 2 86
582 ABP-TEXT-TYPE-TABLE 3 31
583 ABP-TEXT-TABLE 107 71 0
584 OVERRIDE-LOG-TABLE 20,547 100 1,191,726
585 SEC-VIOLATIONS-LOG-T 74,260 90 56 4,158,560
586 ACTIVITY-ALLOC-TABLE 0 89 0
587 USERID-SECURITY- FABL 599
589 PC-TO-RX-XREF-TABLE 23,678 95 57 i,39,646
9
590 APPR-SUMMARY-INQ-TAB 6,404,054 36 0
591 F XED-ASSET-REORG-TA 79 55 2,449
592 VEND-PAY-XREF-TABLE 2,366,022 9 0
593 OPEN-PC-COMM-L-WORK- 0 -439
594 POOL-BASE-A-TABLE 0 239
595 PA-BUYER-EXP-TABLE
596 PA-EXP-BUYER-TABLE 5,101 21 0
597 AGENCY-PROJECT-REVB- 86 72

13082 Attachment B-55 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
RECCF(''''
:ABLE # cowl!:
EMPLOYEE-TABLE
599IPCKT-RECIPIENT-TABLE
600 USER-GROUP-TABLE
608 VEN D-9WRX-TABLE
609 1VEND-9TXT-TABLE
6131BGRT
66310FFLINE-SECURITY-TAB
6641F1S-PARAMETER-TABLE
665 FIS-EXPEND-FUND
666 FIS-EXP-FUND-AGENCY 39
667 FIS-EXP-FUND-OBJ 40 28
668 FIS-EXP-STATUS-AGENC
669 S-EXP-AGENCY-ORGAN
670 FIS-EXP-AGENCY-ACTIV
67 FIS-EXP-AGENCY-OBJ
672 FIS-REV-FUND
673 FIS-REV-FUND-AGENCY
FIS-FUND-REV
FIS-REV-STATUS-AGENC
FIS-REV-AGENCY-ORGAN
FIS-REV-AGENCY-ACTIV
678IFIS-AGENCY-REV
679 FIS-REV-FUND-ACTIVIT
680 FIS-OB-FUND-AGCY
681 FIS-OB-FND-AGCY-OBJ
682 FIS-OB-FND-AGCY-ACT
683 FIS-0B-END-AGCY-ORG
684 FIS-REC-FND-AGCY___
685 S-REC-FN D-AGCY-REV
6861F1S-REC-END-AGCY-ACT
-- 1111fr1111-A\ " -.))tt
AUTO-ENTRY-TABLE
AUTO-ENTRY-EXCLUSION
AWD-ACCT-PROP-XREF
ARD2-TABLE
COST-SHARE-COMMIT-DE
COST-SHARE-COMMIT-HE
GRANT-CAT-TABLE
GRANT-CLASS-TABLE
GRANT-GROUP-TABLE
RT-MGR-AWARD-XREF-T
GRANT-MANAGER-TABLE
SORTED-GRANT-MANAGER
701IGRANT-ACCT-PROP-XREF

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
RECORD
CABLE NAME
COUNT
702 GRANT-PROP-XREF
703 GRANT-REV-SOU RCE-TBL
705 GRANTOR-TABLE
706 PROP-ACCT-XREF
707 PROPOSAL-TABLE
708 PROPOSAL-TYPE-TABLE
709 SERIES-XREF-TABLE 0
710 BUDG-MODEL-CODE-TBL
71 SUB-CONTRACT-TABLE 0
712 EXPIRATION-OF-FUN DS-
713 AG E NCY-CLASS-TAB LE , 885
714 AGENCY-CAT-TABLE
715 AGENCY-GROUP-TABLE 50
716 AGENCY-TYPE-TABLE 50
G RA NT-AWARD-G EN ERATI 0 48
1 1 66
733 EXPENSE-BUDGET-DETAI 14,429,859 110 577,194,360
734 FB I I -TABLE 16,166 30 0
735 WORK-ORDER-BY-EQUIPM 0 22 0
736 WORK-ORDER-WITH-TIME
TRANSACTION-BY-WORK- 2
738 I INVENTORY-BY-WORK-OR 79
739 WORK-0 RDER-TEXT-TABL 81 0
-V—EN—D-O-R-COM MO D-TABLE- 6
747 OPEN-REC-HEADER-TABL 338 0
752 OPHD-OPEN-PO-HEADER- 91,940 0
TAX-RATE-TABLE 4,403
754 BDLV-BID-VENDOR-INQ- 0
755 PC-VI-CROSS-REF-TABL
756 OPLD-OPEN-PO-ACCT-L- 7777.
757 OPCD-OPEN-PO-COM M- 9,790 0
758 PA-VEND-TERMS-TABLE 5,242 5,242
759 PA-COMM-TEXT-TABLE 1 71 71
760 CUST-CREDIT-HISTORY 0 55
761 ALT-CUST-CODE-TABLE 197 30 0
762 CUST-DOCU M ENT-TABLE 30
763 CUSTOMER-TEXT-TABLE 71
764 THIRD-PARTY-BILLING-
765 OPEN-REC-BY-CUSTOM ER
76610PEN-REC-BY-DUE-DATE
768 OREL-TABLE
769 PAYMENT-DETAIL-TABLE
77010 PEN-RECEIVABLE-TEXT 0 0
RENEWAL-NOTICE-SCHED
RENEWAL-TYPE-TABLE 9 35

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
TABLE tt NAME
7731RENEWAL-NOTICE-TEXT
7741DUNNING-MESSAGE-TABL
COLLECTION-LETTER-TA
776 MASTER-SERVICE-AGREE
777 PAYMENT-SCHED-TABLE 61 14
778 -P-6--FE-14TIALUN—EGLL-REC
779 WARRANT-INTERCEPT-TA
780 RER H-TABLE
781 RERE-TABLE 0
782 COLLECTION-CONTRO L-T
783 IREVE NUE-0 PTIONS-TABL
784 BRTE-TABLE
785 ROAR-TABLE
786 BILLING-PROFILE-TABL
787 BILL-PROFILE-COLLECT
788 STATEMENT-TABLE
IN PT-TABLE
TH IRD-PARTY-CUST-R EF
0
719-2TST—ATEMENT-HOLD-TABLE 0
LAN.A—T 12,65-6:276
862IEZ DO C- PA RAM ETE R S-TA 100 2,212
863 ACT-PARAMETERS-TABLE 144 2,828
864 PROGRAM-FUNCTION-DEF _57 11;3-66
865 AC1- FRAN-OP -I S-TABLE 316 5,670
866 EXTENDED-FORMAT-DEF- 1701 50 _19,040 ,
867 ZOOM-TABLE 130 16
871 APPLID-TABLE 0 38 0
872 FRONT-END-PARAMTETER 141 82
APPLMA1NT-TABLE 16 0
876 LOGICAL VIEW DEF TAB 28 -2-9,562
877 CONVERSION-RUN-TABLE 46 10,6-261
879 CAM-NAME-TABLE
880 CAFR-BALANCE-TABLE
881 CAM-BUDGET-TABLE
882 CAM-PRIOR-BAL-TABLE
883 CAM-PRIOR-BUD-TABLE
884 EXMAN-CTRLTABL—E 34 44,098
885 143 2,458,599
886 154 342,496
887 EFID-TABLE 49 90,503
888 107 1,104,989
889 EMLD-TABLE 135 15,795
ELECTRON IC-FUNDS-TRA 252 1,202,796
891IEFT-APPL-TYPE-TABLE 40

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
OPEN-CHECK-H
P EVEIFFE-T_TRI
0 FIXED-ASSET-HIF6RY-
907 MENU-LITERAL-TABLE
6111 EPTI-TABLE
EDDT-TABLE
916 EDSTT: 1437E— — — —
921 VIWK-TABLE
922 JOB-SUBMISSION-AUTO
9231 JOBPARM---T-7I13TE-
924
9-25
1150 WORKFLOW-PARM-TABLE
1151 'W-0--R-1— <G— ROUP-TABLE
1152 WORKER-WORKGROUP-TAB
1153 WORKLIST-TABLE
1154 NOTIFICATION-TABLE
1155 iNOTIFICATION-LOG-TAB
1156
1157 WORK-TYPE-VARIABLE-T
RULES-TABLE
LIST-TABLE
1160 ACTION-TABLE
1161 EVENTS-TABLE
1162 MESSAGE-TABLE -------
1163 1R-117 L E S -TABLE
1164 WORK-CATEGORY-TABLE
1165. CUSTOM-MESSAGE-TABLE 509
1166 WORKFLOW- ERROR-TABLE 124
1167 WORKER-EMAIL-ID-TABL 262
1168 F-EMAIL-ID-WORKER-T 262
1169 WORKGROUP-WORKER-TAB _30
1170 AGING-RULES-TABLE 114
1177 NOTIFY-LOG-TRACK-TAB 163
1178 PROCESS-VIEW-TABLE ,
1179 PROCESS-TABLE 148 140
1180 STAGE-TABLE 117 101,
1181 WORK-STAGE-TABLE 38
1182 RULES-PROCESSING-TAB

13082 Attachment B-5.5 Advantage 2x Tables
(THIS EXHIBIT MAY BE REVISED AFTER ENVISIONING IS COMPLETE AND SCHEDULES, PRODUCTS, OR SERVICES MAY BE DELETED
TOTAL
TABLE # I NAME
BYTES
83 PROCESS-ASSIGNMENT-T
WORK-STAGE-LOG-TABLE
WORK-UNIT-AGING-VALU
1186 ROUTING-PARTICIPANT-
NOTIFICATION-WID-TAB
188 EXTENDED-SECURITY-TA
1189 MANAGER-WORKGROUP-TA
190 ACTION-MESSAGE-SUBJE
1191 ACTION-MESSAGE-TEXT
1193 DESKTOP-COMMENT-TABL
1194 DESKTOP-DETAIL-COMME
DOC-COL-TABL
1300 ATTACH-SERVER-TABLE
OBJ-DATABASE-TABLE
1302 A-FT-SUSPENSE-TABLE
))111111IIIL-1111-I,,,I1
...11-..:3)111111--/B311
1307 JAV/HIfflt-IriAV/
1308 HI-TT-11111111////1/
1400 11..ff1)-"`)---- --II33..

County Project 2013
A,ppu,,
glaricope Upgrade Systems , I s
rtnnot1110n6 Develop
September terna,
83 ,
!,,,
p1.11ovy aTert•pattgeto s .r01-40,...ovd,00
3,41,,,,,
IA0 NI1 1.AfiVAllOgt7_113P9cle.1131grttillic
I
ADJUSTED). Mole 4A
I
I11,
m CAC
kli 1.13
PRICING •
AND 2.1.11/11111311201.091).£13731MMIl1
ADDED
Ploopal Tneenpj 1
: • & a
OR I: : CPA Develop inane
•
Dept 5 : ReF.ponibiRy
3
DELETED 16ppki.otiptts1f0(14msk.519616144.11g1150.011 Training
'317 con,:eptIMGG , Joint
II
BI: Papers 66
e
II:III: 6 Po ,,,,
MAY , II P14666431 ' i
Diagram
111.0.111A,C..17 Anotysi /3,
,,t
Polic.iq5
SERVICES 1111 Sollomp:
3.19
t G Responibilily
14 2
Context OR change
044036 1
1,37 heeop CGI
PRODU(IS, ^Tr 1
fldlodoet t'•
Project
Reme..v
Act:molts
- 353
SCHEDULES, al C '!'''
B-5.6 24,' '
Publish " :::
4.4 ,,,,,,,„ e i
3 Res
,,
AND 10 ,
Report : , County
Attachment Gap A
•• RepP:' Soft,ne i _1
COMPLETE 3,iAt6kii.c.4Ik31itoie... : • Rewew CGI
,
Faompl• and 373 Approve Designs&
&
IS 353 youls
13082 Reetew a t
21
1 Legend
ENVISIONING n1 •
16041
a
lo
- I & Plan
rum:tit:mai Results
AFTER & Review Test
&
' Re,ew .2 pfs
pt4,,
52
REVISED 73f:1 inn
p
BE III :,,,
4•III2Il
MAY I lest, ,.
441 ,I, ,
4 '4 l:
EXHIBIT Management Pevie' "4 , :Mint.
1.1 2.2 .; . Irzildidg 12
1 Phase ,I r‘rr
(THIS & Phase ,:,,..,—,,,,,e,,I 351 T Vva, 0m
pi..,1,,,, l''' on Did ,,,i;,,,
;ling ,i.:464',.1.),.u..,,,,,, I II 0441 9 4 .-
n Envisioii Create .G.POW_C_97tWeIGietfl IS. 119Mer 1, i
Hr..,,, I Rtenith1e festirig Acli] •.so.
P1P , i
1 2.0 , 3.0 I .9 3312
1.0 1 .4.1 v 4.0 7
7

1.1.1.4 .1.1.3.2 1.1.1.3.1 1.1.1.3 1.1.1.2 1.1.1.1 1.1.1 1.1
Section/ Requirement
13082
EXHIBIT
Ability Chart Ability Accounts Ability that Ability Ability Ability Chart Budget RFP
to of for to can be to to to Pre-loading of Section: Respondent: B-6-A
feed Accounts an from view, used have have have from Accounts
all admin any add, a two
modules to module or across single effective periods prior
inactivate modify modules Chart dating period Description Requirement
the of on open
entries Chart Accounts all Respondent's
in of elements
the structure
Statement
Comply Comply Comply Comply Comply Comply Comply Comply ci Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard 1 ()ti Custom/ Standard/ Compliance
change Any or if a module; Effective the ) 2) to 1 with
in processes; changes ETL Financials. change necessarily Advantage Reason responsive. Failure equipment provided Respondents alternative each Respondent RFP
one i.e. to processes It is however can dating for Respondent's to Customization, is
ERP operating, can must made permeate a modify on exception respond or or a shall must requirement. shall
module Advantage be be in change most to software. is Standard be Specifications
will capital, created manually Budget, throughout in the Chart but requirement. and proposal every being indicate provided. If indicate
not Budget to it will the one of not all alternative to be provided feature, the exception,
MFRIS, will updated not ERP. ERP accounts to requirement requires feature a compliance
necessarily etc. feed automate. in module elements. deemed by reason or
all both permeate For in may 3rd being
However budget will any specification non- Party and exception
places to example, not cause an
a
0 0 0 0 0 0 0 (1-5) Score

1.1.2.2.1 1.1.2.2 1.1.2.1 1.1.2
Subsection Section/ Requirement
13082
EXHIBIT
Accounts Ability that Ability Ability Changes RFP
to can be to to in Section: Respondent: B-6-A
from view, used have feed
any add, a all current
module or across single modules year
modify modules Chart Description Requirement
the of
Chart Accounts Respondent's
of
structure
Statement
,
Comply Comply Comply Comply Exception Comply/ Example of
of
3rd CompHance
Standard Standard Standard Standard Party Custom/ Standard/
is change Any must is change Any must is 3 2 to ) with
made permeate processes; processes be made permeate processes; processes be made permeate Reason the Failure provided
in in changes in in changes in responsive. to equipment Customization, Respondents alternative each Respondent RFP
Budget, throughout one i.e. to can be manually Budget, throughout one i.e. to can be manually Budget, throughout for Respondent's or is a
it ERP operating, it ERP operating, it exception respond or shall must requirement. shall Specifications
will the module Advantage created updated will the module Advantage created updated will the to software. i s Standard be
not ERP. will capital, to in not ERP. will capital, to in not ERP. 1,Nplin,Inei and proposal every being indicate provided. If indicate
permeate For not Budget automate. both permeate For not Budget automate. both permeate For it. alternative to be provided feature, the exception,
MFRIS, will places MFRIS, will places requirement feature compliance
to example, necessarily etc. feed or to example, necessarily etc. feed or to example, to deemed by requires a
Financials. if a all ETL Financials. if a all ETL Financials. if a sp,f non- may 3rd being reason or
change However budget change However budget change ification cause Party and exception
It a It a It an
0 (1-5) Score

. . .1.3.5 . . 1.1.3.3 1. . 1.1.3.1 1.1.3 1.1.2.3 1.1.2.2.2
.6 .4 .2
Subsection Section/ Requirement
13082
Need Need Need Need Need Need Ability of Ability RFP EXHIBIT
to to to to to to to Accounts for Section: Respondent: 8-6-A
interface interface interface interface interface interface Communication/Interfacing have an
admin
with with with with with with effective to
Treasury PER PMA WinFlex NeoGov ADP dating inactivate Description Requirement
on
System all entries Respondent's
elements in
Chart
Statement
i
Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
3rd Compliance
tion Contigura tion Configura tion Configura tion Configura tion Configura tion Configura Standard Standard Standard Party Custom/ Standard/
--
2
must 3) 2) 1) with
Interface interface Interface Interface Interface Interface Effective processes be Reason the Failure to RFP
responsive. equipment Customization, provided Respondents alternative each Respondent
will will will will will will dating can manually for Respondent's to is
need need need need need need on be exception respond or a must requirement. shall
to be to be to be to be to be to be most created updated to software. or is Standard shall be Specifications
but to in mciiiiroinent, and proposal every being indicate provided. If indicate
developed developed developed developed developed developed not both to feature, the exception,
all automate. alternative be provided compliance
elements. places to deemed requirement by requires feature a
or ETL 3rd being reason or
specification non- may Party and exception
cause an
0 0 0 0 0 0 (1-5) Score

1.1.5.1 1.1.5 1.1.4.4 1.1.4.3 1.1.4.2 1.1,4.1 .1.4 1.1.3.9 1.1.3.8 1.1.3.7
Subsection Section/ Requirement
13082
EXHIBIT
Ability Ability Ability history) Ability elements) Ability Reports Need Need Need RFP
to Administrative organizations to to to to to to to Section: Respondent: B-6-A
establish generate report report generate interface interface interface
data Module using perspective changes daily with with with
Chart
elements of in reports BizTalk BidSync Procurement Description Requirement
for Accounts variance/discrepancy changes Chart of (all
data Respondent's
CAFR Account System
report
for (audit Statement
Comply Comply Comply Comply Exception Comply Comply Comply Comply Comply Exception Comply/ 11':!:`1 i: i : Example of
, of
Standard Standard Standard Standard Standard Standard Standard tion Configura tion Configura tion Configura 3rd Party Custom/ Standard/ ' — Compliance
-in
2
users of for 3) 2) to 1) with
can accounts Chart Advantage Interface Interface Interface Reason responsive. the Failure equipment provided alternative each Respondent RFP
make is of will will will for Respondent's to Customization, is Respondents
restricted Account Budgeting need need need exception respond or a must requirement. shall
changes. to be to be to be to software. or is Standard shall be Specifications
by changes. does and proposal every being indicate provided. If indicate
security, not developed developed developed N-ptirornont. to feature, the exception,
so However, provide alternative be requirement provided compliance
only audit to deemed by requires feature a
access may 3rd being reason or
authorized to capability specification non- Party and exception
chart cause an
0 0 0 0 0 0 0 0 0 (1-5) Score
—1

1.2.1.4 .2.1.3 1.2.1.2.1 1.2.1.2 1.2.1.1 .'.I 1.2 1.L52
Subsection Section/ Requirement
13082
Budget Ability on the Ability Account Ability Ability Initiate Budget account Ability reporting RFP EXHIBIT
to department department to to to to Section: Respondent: B-6-A
Target for accounting extract view view Preparation elements establish
prepopulate updates/changes mapping Chart
movement string current of —validating
data to from and history Account relationship Description Requirement
and/or the the historical based
enter receiving source on update accounting between Respendent's
new data Chart strings chart
data based of of
, ' Statement
Comply Comply Comply Comply Exception Comply comply Comply Exception Comply/ • Example of
of
3rd Compliance
Standard Standard tion Configura Standard Custom Standard Standard Standard Party Custom/ Standard/
meet An Unique users of for _. the ) 2) to 1) with
this existing maintained. can accounts Chart Advantage Reasc7 .___. . . responsive. Failure equipment provided Respondents alternative each Respondent RFP
consolidation make is of . ;,n o.., . _ Respondent's to Customization, is
requirement. infoAcivantage changes. restricted Account Budgeting respond or or a shall must requirement. shall Specifications
4);:mii r .•:•••••- to software. is Standard be
hierarchies by changes. does 11.4/1i1R-mK)W ;JO proposal every being indicate provided. If indicate
report security, not to feature, the exception,
can can so However, provide ;i7.ii;orive be requirement provided compliance
be be only audit to deemed by requires feature a
modified created access Spo,:i/R may 3rd being reason or
to and authorized to capability non- cause Party and exception
chart an
0 0 0 (1-5) Score

1.2.3.1 1.2.3 1.2.2.1.6 1.2.2.1.5 1.2.2.1.4 1.2.2.1.3 1.2.2.1.2 1.2.2.1.1 1.2.2.1 1.2.2 1.2.1.4.2 1.2.1.4.1
Subsection Section/ Requirement
13082
EXHIBIT
position limited Ability Department Ability Ability Ability Ability Ability position Ability Department Department Ability certain Ability RFP Respondent: B-6-A
level to to to to to enter to to add level to to elements to Section:
data salary apply submit check create data derive prepare base capture adjust
and changes supplementary base against goals supplies, salary budget and prior
benefits to performance services and budget apply years Description Requirement
derived base request get/control and benefits submission approach adjustments appropriation Respondent's
from including tracking/metrics revenue from
but amount the for
not
Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
Advantage not Advantage 1,')ason the 3 Failure 2 to with
enforce for responsive. to equipment Customization, provided Respondents alternative each Respondent R'
Financial. controls. Budget excei;11,),1 Respondent's respond or is a must requirement. shall
can I to software. or is Standard shall be SpecificaUons
Controls check HtillIWIIJOH; (i; HI proposal every being indicate provided. If indicate
are against ,ili, 0 to be provided feature, the exception, compliance
enforced a to 1,1ive . deemed requirement by requires feature a
in target, spech __. may 3rd being reason or
but non- Party and exception
does cause an
0 0 0 0 0 0 0 (1-5) Score

1.2.5 1.2.4.5 1.2.4.4.2 1.2.4.4.1 1.2.4.4 1.2.4.3 1.2.4.2 1.2.4.1 1.2.4 1.2.3.1.2 1.2.3.1.1
Section/ Requirement
13082
EXHIBiT
Ability revenue Ability from Ability Ability Ability Ability Ability Base Ability package Ability RFP Respondent: 3-6-A
Supplementary to to position to to to to to budget to to Section:
update update update update create create copy submit
analysis control base level data base base and and all data analysis categorize/prioritize
and totals supplies, salary budget view view elements and supplementary Description Requirement
and historical trend
recommendation services, benefits details data analysis recommendation elements Respondent's
and derived reporting (OMB) within
Statement
,,
Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Custom/ Standard/ Compliance
Advantage but does Advantage perform Modeling to enter requests. The Reason the ) Failure to 1) with
not trend a ranking responsive. to equipment Customization, provided Respondents alternative each Respondent RFP
Financial. enforce Budget functionality priority Within a feature for Respondent's respond or is a must requirement. shall
can analysis. at the request, can exception to software. or is Standard shall be Specifications
controls. is line be nquiief and proposal every being indicate provided. If indicate
Controls establish/update available level. the user used to twill-. allIliative to be provided feature, the exception, compliance
are a with the can use rank In deemed requirement by requires feature a
enforced control requests text budget specification non- may 3rd being reason or
in total, to fields cause Party and an exception
0 0 0 (1-5) Score

1.2.6.3 1.2.6.2 1.2.6.1 .2.6 1.2.5.5 .2.5.4.2 1.2.5.4.1 1.2.5.4 1.2.5.3 1.2.5.2 1.2.5.1
Subsection Section/ Requirement
13082
Ability the Ability elements Ability Ability and Ability derived Ability Ability Ability Ability Ability RFP EXHIBIT
to entity to to Consolidation to revenue to from to to to to to Section: Respondent: B-6-A
forecast eliminate merge update update update update create enter copy
and all control position historical and all data
capture duplicate base and totals supplemental level supplemental supplemental view trend elements Description Requirement
data data
ending transactions supplementary supplies, salary budget reporting analysis Respondent's
fund and details
within data services, benefits
Statement
„
Comply Comply Comply Comply Exception Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
Advantage but Advantage perform Modeling the ) 2) to 1 with
does not Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
Financial. enforce Budget trend functionality for Respondent's to respond or is a must requirement. shall
can analysis. exception to software. or is Standard shall be Specifications
controls. is requitement. and proposal every being indicate provided. If indicate
Controls establish/update available alternative to be provided feature, the exception, compliance
are a with the to deemed requirement by requires feature a
enforced control requests specification non- may 3rd being reason or
in total, to cause Party and an exception
i
0 0 0 0 0 0 0 0 (1-5) Score

1.3.2.1.1 1.3.2.1 1.3.2 1.3.1.1 1.3.1 1.3 1.2.8.2 1.2.8.1 1.2.8 1.2.7 1.2.6.4
Section/ Requirement
13082
Ability Ability modify Ability Ability Copy Budget Ability Ability Reporting Board the Ability balance RFP EXHIBIT
to to control to to Approved to to Approval current to of Section: Respondent: 8-6-A
have 2 calendarize modify look at Maintenance create generate period determine prior
periods totals details prior Budget budget activity the period
(as in period into and ending Description ui Reqrement
per Chart revised budget Financial performance based fund Respondent's
of budget and System reports balance
Accounts) and actuals reports for
Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Custom/ Standard/ Compliance
3) 2 1) _ with
Financial. controls Advantage Reason responsive. the Failure equipment provided Respondents alternative to each Respondent RFP
however Budget for Respondent's to or Customization, is a
controls can exception respond software. or is Standard shall must be requirement. shall Specifications
are manage lc , p and proposal to every being indicate provided. If indicate
enforced the iiroment. alternative to be provided feature, the exception, compliance
in process to deemed requirement by requires feature a
of may 3rd being reason or
Advantage modifying specification non- Party and exception
cause an
0 0 0 0 0 0 0 0 0 (1-5) Score

1.4.1.2 1.4.1.1 1.4.1 1.4 1.3.5.1 .3.5 1.3.4 1.3.3 1.3.2.3.2 .3.2.3.1 1.3.2.3 1.3.2.2.2 1.3.2.2.1 1.3.2.2
Subsection Section Requirement
13082
Ability Ability Department Forecasting Ability Reporting Ability Ability Ability Ability Board to Ability position Ability Ability RFP Respondent: EXHIBIT B-6-A
to to to to to to to approve deployment to level to to Section:
view create create view modify apply transfer have data modify modify
actuals position Forecasting ad-hoc and display details additions between appropriation staging salary all data
(all reporting in and area/environment and Description Requirement
elements management fund performance budgets environment benefits elements
of balance reductions and Respondent's
Chart process data then derived
of copy from
Staterne
,
Comply Comply Comply Comply Comply Comply Comply Comply Comply . Comply Comply Comply Comply Coniply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
, ,
the 3) to 1) with
responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
ii Respondent's to respond or is a must requirement. shall
Ii _ to software. or is Standard shall be Specifications
proposal every being indicate provided. if indicate
to be provided feature, the exception, compliance
io ' deemed requirement by requires feature a
.s.pcisiii, non- may 3rd being reason or
,iii cause Party and exception
) an
0 0 0 0 0 0 0 0 0 0 0 (1-5) Score

1.4.2.5 1.4.7.4 1.4.2.3 1.4.2.2 1.4.2.1 1.4.2 1.4.1.5 1.4.1.4.1 .4.1.4 1.4.1.3
Subsection Section/ Requirement
13082
EXHIBIT
No edits closed Accounts Ability Ability department Ability Ability OMB Ability derived Ability Accounts) Ability metrics) No edits closed Accounts RFP Respondent: B-6-A
to to to to to forecasting to from to to to Section:
prior and view create choose view view enter enter prior and
metrics) actuals forecast to and position forecast a metrics)
periods position seed departments report forecast periods
(some from (all or level for (all (some from Description Requirement
months elements management not forecast forecast data salary months
exceptions that of seed details and elements exceptions that Respondent's
are Chart process from details benefits of are
for of Chart for
of Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Compy / , Example of
of
3rd Compliance
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Party Custom/
3) 2) 1) with
responsive. the Failure equipment provided Respondents alternative to each Respondent RFP
f( 11 : Respondent's to Customization, is
xcei,ti, respond or or a shall must requirement. shall Specifications
)!I to software. is Standard be
tt:qt/lo.,,metti did proposal every being indicate provided. If indicate
,7t , to feature, the exception,
, t/t,!!‘ be requirement provided feature a compliance
to deemed by requires reason or
spu('iits non- may 3rd being
ttniii cause Party and exception
an
0 0 0 0 0 (1-5) Score

1.4.4.3 1.4.4.2 1.4.4.1 1.4.4 1.4.3.3 .4.3.2 1.4.3.1 1.4.3 .4.2.7 1.4.2.6.1 1.4.2.6
Section/ Requirement
13082
EXHIBIT
report Ability Ability Ability Reporting balance Ability Ability Ability Fund Ability derived Ability Accounts Ability metrics) RFP Respondent: B-6-A
(together) to to to and to to to Balance to from to and to Section:
generate generate create ending view calculate view view enter enter a
ad-hoc and/or beginning and position forecast metrics forecast
budget activity fund report and/or report level for Description Requirement
and based reports balance enter fund forecast data salary (all
performance report forecasted fund balance details and elements Respondent's
balance benefits of
structural Chart
of Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard tion Configura Standard Standard Standard Standard Standard Standard Standard Standard Standard Custom/ Standard/ Compliance
An the 3) 2 to 1) with
requirement. Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
infoAdvantage for Respondent's to or is a Sped
exception respond or shall must requirement. shall
report to software. is Standard be indicate ica
could roril,,irnwri4 and proposal every being indicate provided. If ions
be alternative to be provided feature, the exception, compliance
modified to deemed requirement by requires feature a
to may 3rd being reason or
meet specification non- Party and exception
this cause an
0 0 0 0 0 0 0 (1-5) Score

1.5.2.4 1.5.2.3 1.5.2.2 .5.2.1.2 .5.2.1.1 _ 1.5.2.1 1.5.2 .5.1 1.5
Section/ Requirement
13082
attributes Ability selected Ability Ability titles Ability to the Ability list of Ability Create how Ability Position RFP EXHIBIT
to to to to to MRTs to a request to Section: Respondent: 8-6-A
Market populate select view department view select position create
select/assign Range a the all Market position Management
position Working Job Working staging
values Title Range changes Description Requirement
to attributes Title Descriptions Titles Title affect environment
position of of the that are (MRT) the to Respondent's
the Working approved from budget reflect
a
Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Custom/ Standard/ Compliance
manually. can Currently Assume data. position user The the 3 2) to 1) with
department, create to run salary Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
but position titles MRT changes what projection for Respondent's to or is a
that are not translates without if exception respond or Standard shall must be requirement. shall Specifications
would groups tied to scenarios scenario and proposal to software. is being indicate if indicate
need to to impacting and requirement. to every feature, provided.
to aggregate departments. classification. functionality alternative be requirement provided the exception, compliance
be the evaluate to deemed by requires feature a
maintained positions The underlying the allows specification non- may 3rd being reason or
by County impact a cause Party and exception
of an
0 0 0 (1-5) Score

1.5.2.8.3 1.5.2.8.2 .5.2.8.1 1.5.2.8 1.5.2.7 .5.2.6 1.5.2.5.3 1.5.2.5.2 1.5.2.5.1 1.5.2.5
Section/ Requirement
13082
Budget Ability HR Ability within Ability Ability and Ability Ability than Ability activity Ability of Ability Ability RFP EXHIBIT
to to the to to receive for to five to to activities to to Section: Respondent: 5-6-A
have have have capture attach activities allocate assign select allocate
at at department at notifications department
least least least approvals document to a more percentage activities activities
three two three of to position than from to Description Requirement
layers layers layers the submit one allocation the the
of of of submissions position but position Respondent's
approvals approvals approvals not to the department
in in request more list
Statement
.
Comply Comply Comply Comply Comply Comply Exception Comply Comply Comply Exception Comply/ Example of
of Corn
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Custom/ Standard/ pUance
They position. You the 3) 2 to _ with
cannot Attachments can Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
be can allocate for Respondent's to or is a
added be an exception respond or Standard shall must be requirement. shall Specifications
to the added unlimited and proposal to software. is being indicate If indicate
to ioquirement. every feature, provided.
the number alternative to be provided the exception, compliance
position/employee position of to deemed requirement by requires feature a
requests. activities specification non- may 3rd being reason or
record. to a cause Party and an exception
,
0 0 0 0 (1-5) Score

1.5.6.1 1.5.6 1.5.5.2 1.5.5.1 1.5.5 .5.4.1 .5.4 1.5.3.3 1.5.3.2 1.5.3.1 1.5.3
Subsection Section/ Requirement
13082
Ability Reporting requested Ability batch Ability Ability Ability Ability Ability Ability Department Ability Ability RR Respondent: EXHIBIT B-6-A
to to (new, to to to to to to to to Section:
generate for a multiply modify, combine batch submit inactivate submit reallocate and change modify
all specific the positions inactivation a MRT position an
active position number inactivate) different in position modification activities existing Description Requirement
reports of types a request for for to the attributes position
positions of approval approval position except Respondent's
requests
being in a
Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
approval. End be definition Budget. Field the 3) 2) to 1) , with
users submitted Modifications level Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
can for level. Security security for Respondent's to or is a
reduce approval. proposed controls is exception respond software. or is Standard shall must be requirement. shall Specifications
FTE to through who not req? ti I. ati:1 proposal to every being indicate provided. If indicate
zero and the can supported einent. ,/leinalive to be provided feature, the exception, compliance
submit budget view/edit/etc. in to deemed requirement by requires feature a
for form Advantage specification non- may 3rd being reason or
can at the cause Party and an exception
0 0 0 0 0 0 0 0 (1-5) Score

1.6.3.7 1.6.3.6 1.6.3.5 1.6.3.4 1.6.3.3 1.6.3.2 1.6.3.1 1.6.3 .6.2.3 1.6.2.2 1.6.2.1 1.6.2 1.6.1.2 1.6.1.1 1.6.1 1.6
Subsection Section/ Requirement
13082
EXHIBIT
Ability Ability analysis Ability Ability Ability Ability Ability Analysis Ability Ability revenues) Ability Cash Ability Ability identify RFP Respondent: B-6-A
to to to to to to to to to to flow to to Multi-year/Capital Section:
forecast view enter enter validate enter determine indicate enter need enter needs attach request Projects
for historical and/or projected the capital true revenue operating by fiscal project document project Budget
existing data attach project operating funding fund budget year budget for Description Requirement
projects for industry budget availability balance source needs analysis Respondent's
existing completion (expenditures
projects specific needs
date and
Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ 1 .•:, • Example of
. of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
the 3) 2) to 1) with
responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
Respondent's to respond or is a must requirement. shall
a: to software. or is Standard shall be Specifications
I"111ifeliknif .11h1 c proposal every being indicate provided. if indicate
)1<;ttliii1V• to be provided feature, the exception, compliance
' i deemed requirement by requires feature a
may 3rd being reason or
Ot;lliCidi(41 non- cause Party and exception
an
_
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (1-5) Score

1.6.5.2 1.6.5.1 1.6.5 1.6.4.4 1.6.4.3 1.6.4.2 1.6.4.1 1.6.4 .6.3.11 1.6.3.10 1.6.3.9 1.6.3.8
Section/ Requirement
13082
EXHIBIT
Ability operation Ability Project formal Ability Ability (budget Ability approved Ability Ability Approval Ability Ability RFP
to to budget to to to to Recommendation to to to Section: Respondent: B-6-A
change budget maintain Maintenance include share data) create budget create create process report review
overall guidelines budget approval data data with schedules, report (internal projected data
project and process from from function/project Description Requirement
for data Procurement table analysis review) summary
budget current forecast and code Respondent's
fiscal as consolidation charts and
per
year and Statement
l ,
Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard tion Configura tion Configura Standard Standard Standard Standard Standard Standard Custom/ Standard/ Compliance
_
Interface tool. the 3) 2) to 1) with
documents Schedules, Reaso!) responsive. Failure equipment provided Respondents alternative each Respondent RFP
will tables , 1( 1 Respondent's to Customization, is
need to published and kco)//, respond or or a shall must requirement. shall Specifications
be , ,i i . to software. is Standard be indicate
through charts opitoment iici proposal every being indicate provided. If
developed the can be alternatil, to be provided feature, the exception, compliance
Budget included , deemed requirement by requires feature a
Publishing in non- may 3rd being reason or
the cause Party and exception
an
0 0 0 0 0 0 0 0 0 (1-5) Score

TOTAL 5.1 5 4.1 4 .1 3 3 2.1 2 1.6.5.4 1.6.5.3
Score: Subsection Section/ Requirement
3 13082
.._ EXHIBIT
Tretire Finance Ability Ability RFP
Procurement to to Section: Respondent: B-S-A
forecast share
data
total with
project Description Requirement
data Procurement Respondent's
Statement
,
Comply Comply Exception Comply/ Example of
of
Standard tion Configura 3rd Custo Standard/ Compliance
Party m/
2 with
Interface Reason responsive. the Failure equipment provided alternative to each Respondent RFP
will for Respondent's to Customization, is Respondents
need exception respond or a shall must requirement. shaH Specifica
to be to software. or is Standard be
rogitit:nnent. at 1 proposal every being indicate provided. If indicate tons
developed ,illornative to feature, the exception,
be provided compliance
to deemed requirement by requires feature a
may 3rd being reason or
specification non- Party and exception
cause an
(1-5) Score

2.1.1.1.5 2.1.1.1.4 2.1.1.1.3 2.1.1.1.2 2.1.1.1.1 2.1.1.1 2.1.1 2.1 1.1
Subsection Section/ Requirement
13082
EXHIBIT
and Ability Measures Add, Add Add, Add elements Ability Create Strategic R S Budget RFP 6
when to edit, and edit, and to a Section: Respondent: 1-B
it edit edit add, County Plan
was identify including inactivate, Strategic inactivate, Mission, edit,
made who Wide Development
made target reactivate Priorities reactivate Vision, inactivate Strategic Description Requirement
the and Values the
previous threshold Goals Issues Respondent's
and countywide
change values
plan
Statement
Exception Comply Co Comply Comply Comply Comply Exception Comply/ , Example of
ply of
Custom Standard Standard Standard Standard Standard Standard Standard 3rd Custom/ Standard/ Compliance
Party
as 1 I 3 2) 1) with
captured target Changes Reason responsive. the Failure equipment provided alternative to each Respondent RFP
in value, to for to Customization, Respondents
the data Respondent's respond or is a must requirement.
audit actual entered exception software. or i Standard shall be shall Specifications
trail. value, and proposal to every s being indicate If indicate
This and through (initernent. to feature, provided.
will any a alternative be provided the exception, compliance
capture budget to deemed requirement by requires feature a
who supporting form, may 3rd being reason or
text such specification non- Party and exception
made is cause an
0 0 0 0 0 0 (1-5) Score

,
2.1.3.1.3 2.1.3.1.2 2.1.3.1.1 2.1.3.1 2.1.3 2.1.2.1 2.1.2
Section/ Requirement
customers [including and Programs, Add, Measures Add, Add plans Ability Create previous Ability Copy RFP
purpose edit, edit, and to a to the Section: Respondent:
and targets edit add, plan previous
Activities, inactivate, including inactivate, Mission, edit, Department pre-populate
mandates) and statements,
Services reactivate, target reactivate Vision, inactivate Strategic current countywide Description Requirement
thresholds], and
performance (including copy, threshold issues, Values the Plan plan plan Respondent's
and department from
service measures program move values Goals, the
and
Statement
Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Custom/ Standard/ Compliance
can plans then All not delta the 3) 2) to 1) with
be relationships elements and performance included elements, was. change, leason responsive. the Failure equipment provided alternative each Respondent RFP
updated in can associated in such /or Respondent's to Customization, is Respondents
at be consolidations. to the as a Changes when eAGoplion respond or a must requirement. shall
any performance edited each elements audit made the to software. or is Standard shall be Specifications
point at any Each other are tables. change to change requirement. and proposal every being indicate provided. If indicate
in time. plans point of through stored to the the was alteinativc., to be provided feature, the exception,
and in these mission reference made, io requirement requires feature a compliance
time. individual the independently data and deemed by 3rd reason or
consolidations The performance record what speGilication non- may Party being and exception
and are the cause an
0 0 0 0 0 0 (1-5) Score

2.1.3.1.7 2.1.3.1.6 2.1.3.1.5 2.1.3.1.4 2.1.3.1.3.1
Subsection Section/ Requirement
and Ability Ability Add, not last) Ability (for as Copy RFP
when to to edit, limited and to both integrated thresholds], performance (including and Section: Respondent:
it was identify add, inactivate to add define unpublished and program move
made modify, data descriptive units service measures
who Key source, aggregation and from and Programs,
made inactivate one [including purpose Description Requirement
the Performance calculation information types published customers Activities,
previous Activity (sum, department and targets statements, Respondents
Indicators definition including avg, plans). to and Services
change Leaders first, others mandates)
but
i
Exception Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard 3rd Custom/ Standard Compliance
Party
as not at Each can plans then All ) 2) to 1 with
captured target Changes therefore any responsible be relationships elements and i:oason the Failure provided each
in value, to associated point performance updated can associated performance hi responsive. to equipment Customization, Respondents alternative Respondent RFP
the data cannot in owner. at in be Respondent's or is a must
audit actual entered be with a time. any edited consolidations. to em.tiptiori respond or shall requirement. shall Specifications
trail. This These element performance each elements r to software. is Standard be
This value, through inactivated. specific is can point at any Each other are recioll, di iti t roposal every being indicate provided. if indicate
will and a user currently be can be in time. plans point of through stored , e..::Prit. ', iii to feature, the exception,
any budget or a updated assigned and in these nelliVii be requirement provided requires feature a compliance
capture supporting table, text time. the ,O deemed by or
who form, and field and a consolidations The individual independently may 3rd being reason
made text such and modified performance .speciii(;,ition non- cause Party and exception
is and an
0 0 0 0 (1-5) Score

_
2.1.5.2 2.1.5.1 2.1.5 2.1.4.1 2.1.4
Subsection Section/ Requirement
goals Ability Ability previous Ability Copy RFP
to to Department to of Section: Respondent:
link link plan the
links pre-populate previous
department department to
County current department Description Requirement
activity goals Plan
to plan
results county from plans Respondent's
to goals the
county
Statement
Comply Comply Comply Comply Comply Exception Comply/ Example of
- of
Standard Standard Standard Standard Standard 3rd Custom/ Standard/ Compliance
Party
County County There County County There County County There not elements, delta the Htid the 3) 2) to 1) with
department is department is department is included was. change, ,Slin responsive. Failure equipment provided Respondents alternative each Respondent RFP
plan. Plans, no plan. Plans, no plan. Plans, no such 101 _ to Customization, is
plans but logic plans but logic plans but logic in the as Changes when eiI Respondent's respond or a must requirement.
can to can to can to audit a the Gupii0i1 ,. or Standard shall be shall Specifications
also performance "link" also performance "link" also performance "link" change made change - proposal to software. is If indicate
be be be tables. to to requirement, iiiii . every being indicate provided.
separate separate separate the the was 6/10i • to feature, the exception,
included elements included elements included elements reference made, /Mb V 7, be requirement provided compliance
as department as department as department mission .k.: i , deemed by requires feature a
part part part record data and .; may 3rd being reason or
of referenced plans of referenced plans of referenced plans what 'GI/RAG/0i/ • '• - non- Party and exception
the in to the in to the in to are the • • cause an
0 0 0 (1-5) Score

2.1.6.3 2.1.6.2 2.1.6.1 2.1.6
Subsection Section/ Requirement
return Ability technical approve Ability approval to the Ability RFP
the for for for Department Section: Respondent:
plan a and and a department the
to department content send department Review
the the department
submitter approval plan approving and Description Requirement
approving to approving user Approval
MFRIS authority to Respondent's
authority reviewers authority for submit Workflow
the
to for to plan
Statement
Exception Exception Exception Exception Exception Comply/ Example of
of
Standard Standard Standard Standard 3rd Custom/ Standard/ Compliance
Party
as data as data as data as data 3) 2) to 1) with
target Changes is Configuration captured target Changes is Configuration captured target Changes is Configuration captured target Changes is Configuration Keasoli the Failure equipment provided alternative each RFP
value, to not in value, to not in value, to not in value, to not io, responsive. to Customization, a is Respondents Respondent
data governed of the data governed of the data governed of the data governed of Respondent's respond or must requirement. Sped
actual entered by audit actual entered by audit actual entered by audit actual entered by e•xcepiioii software. or is Standard shall be shall ica
value, performance trail. value, performance trail. value, performance trail. value, performance ler : ,pd proposal to being indicate If indicate ions
and through workflow and through workflow and through workflow and through workflow 1WI1i. ii(-', I to every feat ure, provided. exception,
any a and management any a and management any a and management any a and management iiiiilVe be requirement provided the compliance
budget budget budget budget ik.) deemed by requires feature a
supporting form, approval. supporting form, approval. supporting form, approval. supporting form, approval. may 3rd being reason or
text such reference text such reference text such reference text such reference .:)00CIIIC0iitit ----.,..— non- cause Party and exception
is is is is 1 - an
0 0 0 (1-5) Score

2.1.7.2.2 2.1.7.2.1 2.1.7.2 2.1.7.1.2 2.1.7.1.1 2.1.7.1 2.1.7 2.1.6.5 2.1.6.4
Subsection Section/ Requirement
Return Approve Ability Return Approve content Ability Workflow MfRIS budget Ability Chart Ability RFP Respondent:
plan and for a plan plan reviews for a to of to cross Section:
to the publish MfRIS to and MfRIS Administrator development publish Accounts
Admin department send Adm the plan check the
department department to to a n to Review so Description Requirement
perform submitter final perform and it is approved
submitter plan final review Approval available plan Respondent's
review technical for with
and the
Statement
Exception Exception Exception Exception Exception Exception Exception Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard tion Configura 3rd Custom/ Standard/ Compliance
Party
data data data data data data A report captured the 3) 2) to 1) with
Configuration not Configuration not Configuration not Configuration not Configuration not Configuration not Configuration responsive. Failure equipment provided Respondents alternative each Respondent RFP
of governed of governed of governed of governed of governed of governed of can be in the ;,,; Respondent's to or Customization, is a
by by by by by by configured audit 6,m:op/of; --- respond software. or is Standard shall must be requirement. shall Specifications
performance workflow performance workflow performance workflow performance workflow performance workflow performance workflow performance trail. requilement Jlici - proposal to every being indicate provided. If indicate
and and and and and and to meet ,.,i())) to be provided feature, the exception, compliance
management management management management management management management this )Ve requirement requires feature a
approval. approval. approval. approval. approval. approval. u deemed by reason or
reference reference reference reference reference reference reference requirement. 6pcGilicolioie non- may 3rd Party being and exception
cause an
0 0 0 0 (1-5) Score

2.1.9.3 2.1.9.2 2.1.9.1 2.1.9 2.1.8.3 2.1.8.2 2.1.8.1 2.1.8
Subsection Section/ Requirement
Ability Ability Ability plans Access Ability Ability Ability Access RFP
to to to to to to to to Section: Respondent:
export print view export print view
to department to Countywide
Word, Word,
PDF unpublished PDF published Description Requirement
and plans Respondent's
published
Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard Standard 3rd Custom/ Standard/ Compliance
Party
then then then then data the 3) 2) to 1) with
converted Performance printed. Performance infoAdvantage converted Performance printed. Performance not 1..'e,c)ii responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
governed lo Responder to is
to plans plans report to plans plans exueptio! t's respond or or a shall must requirement. shall Specifications
PDF. can can PDF. can can by I to software. i s Standard be
be be be be workflow IiTliiii)M oiui proposal every being indicate provided. If indicate
published published published published and yit. , olt;'r•iaiivo to be provided feature, the exception,
in a in a in a in a approval. io deemed requirement by requires feature a compliance
report report report report may 3rd being reason or
and and and and 61)6ViliGOIT!? non- Party and exception
cause an
0 0 0 (1-5) Score

2.2.3.1.4 2.2.3.1.3 2.2.3.1.2 2.2.3.1.1 2.2.3.1 2.2.3 2.2.2.3 2.2.2.2 2.2.2.1 2.2.2 2.2.1 2.2
Subsection Section/ Requirement
Ability Ability Ability permissions Ability performance Forecast Performance Ability Ability Ability Access see1.2 Budget Develop Budget RFP Respondent:
to to to to to to to to Section:
export edit enter access export print view Budget Preparation department Development
to forecast budget measures performance Forecasting to department functional at
Excel values performance data Word the Budget Description Requirement
scenarios on approved
forecasts based activity budget requirements) department (Beginning Respondent's
on level
— process
of Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of Co
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ pliance
to Excel. Forecasts Budgets Hei.16011 the ) to 1) with
can responsive. Failure equipment Customizati provided Respondents alternative each Respondent RFP
entered be 10i Respondent's to or on, is a must
in the included eM.:(1)i1011 respond software. or is Standard shall be requirement. shall Specifications
budget as a iff-, ItI(l proposal to every being indicate provided. If indicate
form report 1710t11. 011eillailVe to be provided feature, the exception, compliance
can and 0 deemed requirement by requires feature a
be then may 3rd being reason or
exported printed. Sf)t-,•GilitjailUil non- Party and exception
cause an
0 0 0 0 0 0 0 0 0 0 (1-5) Score

2.3.1.5 2.3.1.4 2.3.1.3.1 2.3.1.3 2.3.1.2 2.3.1.1 2.3.1 2.3
Section/ Requirement
location Ability into Ability plan) parameters Display manually Ability Ability Ability measures, strategic Report Reporting - RFP
or to annual to to to to goal actual Section: Respondent:
other aggregate results aggregate descriptive and via enter access access including data Results
(previously and measures
user-defined results (sum, monthly Excel, actual published approved narrative (current
defined information based and Description Requirement
based average, and in on on performance strategic budget activity and
demographic on first, quarterly the user plans comments historical) Respondent's
geographic last) published measure permissions values, performance on
values
Statement
Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
. of
Standard Standard Standard Standard Standard Standard Standard Standard Custom/ Standard Compliance
Party
can Any form then measure the 3) 2) to 1 with
be used can information referenced Measures ,i1 responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
in information be tables and 101 Respondent's to is
reports that included entered on and measure .,.,AGepi respond or or a shall must requirement. shall Specifications
and is in on the budget i'.. p , ,,,,,. ; to software, is Standard be indicate
to captured reports. the Performance information lit ef proposal every being indicate provijed. lf
measure form ;lel It. o ,,,, to feature, the exception,
categorize as part or tables. are io ih„.; be requirement provided feature compliance
the of in plan. The stored L, , deemed by requires a or
data. the the spe may 3rd being reason
measure budget Descriptive measure in ,,itcalion non- cause Party and exception
is an
0 0 0 0 0 0 0 (1-5) Score

2.4 2.3.1.10 2.3.1.9 2.3.1.8 2.3.1.7 2.3.1.6
- Subsection Section/ Requirement
Analyze entered Ability Ability Ability Ability Display RFP
performance Performance to to to departments to Section: Respondent:
Results create Export add, or YTD
measures Data to modify, lock/unlock and
Reports" reports, Excel individual projected
for inactivate particular Description Requirement
which that including departments annualized
no identify Activity periods Respondent's
data "Missing for result
has Leaders all
been Statement
Comply Comply Comply Comply Exception Comply Comply Exception Comply/ Example of
of
Standard Standard tion Configura Standard Standard Standard Standard 3rd Custom/ Standard/ Compiiance
Party
,
A therefore not at any Each the 3) 2) to 1) with
report associated point responsible K,,150,1 responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
can be cannot in performance ior Respondent's to is
be with time. owner. ex6k-,,pio respond or or a shall must requirement. shall
configured a This These element di di to software. is Standard be Specifications
to inactivated. specific is can can requireinctd. sii proposal every being indicate provided. lf indicate
meet user currently be be dli:-.:11ive to be provided feature, the exception,
this or table, a text updated assigned deemed requirement by requires feature a compliance
requirement and field and a k..) may 3rd being reason or
and modified .Litiecalici,iiion non- Party and exception
cause an
0 0 0 0 0 (1-5) Score

2.4.1.2.1 2.4.1.2 2.4.1.1.5 2.4.1.1.4 2.4.1.1.3 2.4.1.1.2 2.4.1.1.1 2.4.1.1 2.4.1 ._.
Subsection Section/ Requirement
_
measures At and Ability Ability At At At At in Ability Revenue RFF'
Department explanatory to to Department Program Activity Fund level actual in to Section: Respondent:
(with display export level level a display and
values, level, key to level dashboard Expense
narrative Excel revenue
trends, including in a performance format and Dashboard Description Requirement
targets, strategic dashboard expense Respondent's
and measure in
goals, format plan
status and
Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
tion Configura tion Configura Standard tion Configura tion Configura tion Configura tion Configura tion Configura tion Configura 3rd Custom/ Standard/ Compiiance
Party
3) 2) ) with
kea.;(..)/) responsve. the Failure equipment provided Respondents alternative to each Respondent RFP
hit i Respondent's to Customization, is
(;')(04)1 respond or or a shall must requirement. shall Specifications
i .10/ I to software. is Standard be
.ciiiiiic.)inent. i ,i, ;:.i proposal every being indicate provided. If indicate
Ilieimiive to be provided feature, the exception,
to deemed requirement by requires feature a compliance
may 3rd being reason or
specification .. • • non- Party and exception
- cause an
0 0 (1-5) Score

TOTAL 5.1 5 4.1 4 3.1 3 2.4.3 2.4.2 2.4.1.3 2.4.1.2.3 2.4.1.2.2
Score: Subsection Section/ Requirement
3
Treasurer Finance Ability Ability Ability values, At and At thresholds), RFP
Procurement to to performance to Activity narrative Program Section: Respondent:
export create data display trends, level, level, and
reports Standardized integrated targets, including explanatory including narrative
to and Description Requirement
Word and financial thresholds performance information program explanatory
ad hoc and key Respondent's
reports measure results information
Statement
Exception Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard tion Configura tion Configura 3rd Custom/ Standard/ Compliance
Party
User the ) 2) to 1) with
can Heasoo responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
copy/paste for Respondent's to or is a must
to excepikni respond software. or is Standard shall be requirement. shall Specifications
Word. oolo iiti,; proposal to every being indicate provided. If indicate
,loori idiot TIN to be provided feature, the exception, compliance
t: io deemed requirement by requires feature a
may 3rd being reason or
veGiliGiiio,, non- Party and exception
cause an
0 0 0 (1-5) Score


3.1.2.4 3.1.2.3 3.1.2.2 3.1.2.1 3.1.2 3.1.1.1 3.1.1 3.1
Subsection Section/ Requirement
13082
EXHIBIT
financial Ability financial Ability files into Ability upload Ability Interfaces Ability Purchase Accounts in.ailc, RFP Respondent: B-6.2
to for for files for to Section:
system receive systems ADP financial Pitney into Pcarci view Order Payable FINANCE
Jail to system Bowes financial vendor Purchase
bond interface to (US Orders Description Requirement
feed and interface system Bank) Resp
from upload tto
OnBase files and interface ndent's
into into upload and St.;1
- ement
Exception Comply Comply Comply Comply Exception Comply/ Example of
of
1d 3 Party Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
to the use retention. Electronic The journal County journal County Advantage i. the 3) 2) to 1) with
latest this County transactions o:uti responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
release solution CGI Content vouchers clarification: vouchers clarification: from provides IL:. ...,:\ Respondent's to or is a
of to meet expects currently pertaining (e.g., P-card the .plioi respond software. or is Standard shall must be requirement. shall Specifications
its that Management utilizes These postage, These ability reqt ,:ital proposal to every being indicate provided. If indicate
CG1Advantage. ECM the the to are are providers to 'kernel it to feature, the exception,
as the County (ECM) OnBase payroll. payment payroll). payment accept ofio;fintrvc be requirement provided feature compliance
CGI will and a io deemed by requires a or
will County solution requests requests file of non- may 3rd being reason
develop moves continue records for and and .oectlicoliii cause Party and exception
to an
(1-5) Score

3.1.5.1 3.1.5 3.1.4.1 3.1.4 3.1.3.4 3.1.3.3 3.1.3.2 3.1.3.1 3.1.3
Subsection Section/ Requirement
13082
EXHIBIT
Ability Rejected Ability Payment approva Ability approval Ability financial Ability Ability Workflow RFP Respondent: B-6.2
to to l for for for for Section:
edit Payments have Finance system vendor Process FINANCE
data warrant to departments department to
printed apply to users send Description Requirement
rd 3 apply to electronic
and/or (final) level enter Respondent's
EFT level 1 and data invoices
of 2 into
Statement
Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
3rd Compliance
Standard Standard Standard Standard Standard Standard Party Custom/ Standard/
For the 3) 2) 1) with
Transactions contains posted Advantage business integration OnBase. Nei:sor) responsive. the Failure equipment provided alternative to each RFP
any CG1 integration htt to Customization, Respondents Respondent
rejected edits transactions, Vendor transaction between assumes r tN:ci.;),', Respondent's respond or is a must requirement. shall
to such framework it tit I to software. or is Standard shall be Specifications
prior maintain a Self-Service as Advantage the Iii ., ,',!i proposal every being indicate provided. If indicate
to a new an 3 County between (if to feature, the exception,
posting complete document (VSS) invoice. and will „Ilt017.1(t',.."(t be requirement provided compliance
may the develop Advantage it ' deemed by requires feature a
be audit version ECM :30(,Cliii:. may 3rd being reason or
edited trail. for the and ;IA non- cause Party and exception
each ?i it an
(1-5) Score

3.2.1.1 3.2.1 3.2 .1.6.1 3.1.6 3.1.5.4 3.1.5.3 3.1.5.2
Subsection Section/ Requirement
13082
EXHIBIT
Cash Recording Accounts Yearly Reports Notification Ability Ability RFP Respondent: B-6.2
receipts 1099 to to Section:
from Receivables Receivable reports to re-issue re-approve FINANCE
Finance
Treasury of payment Description Requirement
system rejected Res.
payments 'nt's
Statement
Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
1099 Advantage back that edits prior these against Payment within the ) 2) to 1) with
process. notifications, to the are may to edits the Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
rejected be posting. and system same ft , Respondent's to is S
provides and be submitter, by queried receive edits transactions, ( respond or or a shall must requirement. shall eci
standard queried can approvers online Payments all real-time. like document ., fh ),; proposal to software. is being Standard indicate be If indicate ications
online. optionally are or via that required all version. inioniot:f , , : to every feature, the provided. exception,
reports are Payments documents, !in;.:liv be requirement provided compliance
as part trigger automatically reporting. rejected workflow , ,, deemed by require s feature a
of email via must are non- may 3rd being reason or
the routed Payments system approvals pass validated „pecification cause Party and exception
an
(1-5) Score

3.2.1.2.2 3.2.1.2.1 3.2.1.2 3.2.1.1.3 3.2.1.1.2 3.2.1.1.1
Section/ Requirement
13082
EXHIBiT
Download Download Grants Journal Download Cash REP Respondent: B-6.2
file (GASB33) voucher of receipts Section: FiNANCE
voucher from into CR entered
into Advantage Advantage transaction into Description Requirement
Advantage (certain Advantage
Respondent's
time
period)
Statement
„
Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Custom/ Standard/ Compliance
document. must documents. documents and complete additional come entered Treasury County may be A variety the 3) Failure 2) to 1) with
be posting. with from (e.g., documents/transactions, of ,I;;on for responsive. to equipment Customization, provided Respondents alternative each Respondent RFP
CG1 will provided in However, from Advantage accounting detail to incomplete scratch accrual clarification: downloaded files e\, , Respondent's respond or is a must requirement. shall
work order external block) be today. from such as pii(ri to software. or is Standard shall be indicate Specifications
with to certain systems provides added information entries) Example: and lerinuon; it proposal every being indicate provided. if
the successfully minimum the prior to manually These that Journal Advantage. table attachments, )W to be provided feature, the exception, compliance
County including ability (e.g., and journal are and deemed requirement by requires feature a
during import information to review/approval the require vouchers manually vouchers inquiry -: non- may 3rd being reason or
the a incomplete import from data :(:11;qtion cause Party and exception
an
(1-5) Score

3.2.1.6 3.2.1.5.1 3.2.1.5 3.2.1.4.1 3.2.1.4 3.2.1.3.1 3.2.1,3
Subsection Section/ Requirement
13082
Jail from Journal Collection Journal Advantage Based Year-End RFP EXHIBIT
and the Departments on Section: Respondent: B-6.2
patrol treasury entry is of vouchers Closing FINANCE
billing taxes record materiality
system recorded (AR) based own Form
on record Description Requirement
based CR receivables a
on journal Respondent's
information voucher
into Statement
Comply Comply Comply Exception Comply/ , : Example of
of
Standard Standard Standard 3rd Custom/ Standard/ Compliance
Party
?
used receipts Authorized used receipts Authorized necessary Authorized currently Treasury status automate Envision the 3) 2) to with
to to a to to responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
automated within users automate within users to users simplify Advantage the phase Respondent's to or is a
Advantage may Advantage may record may completely loading to i respond or Standard shall must be requirement. shall Specifications
postings enter postings enter various enter manual and with of evaluate ,10 proposal to software. is being indicate If indicate
from and/or journal from and/or journal year-end journal streamline the these the ,ottrrif:ttt zit , to every feature, the provided. exception,
an an an an task. information journal potential Native be requirement provided compliance
external interface vouchers external interface vouchers vouchers what is to 1, deemed by requires feature a
and and adjustments as provided vouchers be may 3rd being reason or
system could cash system could cash otherwise in able non- Party and exception
be be by draft to cause an
(1-5) Score

3.3.2.1 3.3.2 3.3.1 3.3 3.2.2.3.1 3.2.2.3 3.2.2.2.1 3.2.2.2 3.2.2.1.1 3.2.2.1 3.2.2 3.2.1.6.1
Subsection Section/ Requirement
13082
EXHIBIT
Ability Ability Grantor, Ability Grant Reversal Tax Reversal Grants year) Reversal Non-grant Reversal cases) Journal RFP
to to to Section: Respondent: B-6.2
edit enter award have Reporting of at the of and of entry FINANCE
data prior prior is
prior Grant amount, Grant (SEFA) year beginning year non-tax receivables based
to grant tracking entry of accrual accr on Description Requirement
close information (All at the the (at l ua QuickBooks
out period, end year the Respondent's
etc. Grants) of end (in
i.e. the of the some
year
Statement
-,
Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard 3rd Custom/ Standard Compliance
Party
-
used - 2) 1) with
to receipts Authorized responsive. the Failure equipment provided alternative to each Respondent RFP
automated within users 1, ,) , Respondent's to Customization, is Respondents
may ,xcei;lit),/ respond or or a shall must requirement. shall
postings Advantage to software. is Standard be Specifications
enter , ItRi proposal every being indicate provided. If indicate
from and/or journal qii/o/ip,v); ;l!(i- to feature, the exception,
an an ?:iir be requirement provided compliance
external interface vouchers ,,, 1( deemed by requires feature a
and may 3rd being reason or
system could cash non- cause Party and exception
be an
(1-5) Score

3.4.1.8 1 3.4.1.7 3.4.1.6 3.4.1.5 3.4.1.4 3.4.1.3 3.4.1.2 3.4.1.1 3.4.1 3.4 3.3.4 3.3.3.2 3.3.3.1 3 .3.3
Subsection Section/ Requirement
13082
EXHIBIT
Ability Ability Ability Ability Ability Ability Ability Ability Financial Financial Ability Ability reports Monthly Reporting RFP Respondent: B-6.2
to to to to to to to to to to and Section:
edit create create create create create create create Statement Reporting close generate FINANCE
format enterprise internal budget investment agency full modified out Grant yearly Ad-hoc
service actual funds accrual federal Grant Description Requirement
funds report trust report report accrual inception
report funds funds report SEFA to Respondent's
report report report date
Statement
,
Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
extract report, the 3) 2) to 1 with
for) Advantage infoAdvantage. and Advantage Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
the yearly provides additional provides to; (. \ ( Respondent's to respond or is a must requirement. shall
the a '' pi! to software. or is Standard shall be Specifications
SEFA data reports standard 0;ftlliti1li'llt. proposal every being indicate provided. If indicate
report. needed may grants ,lit?il, to be provided feature, the exception, compliance
to be trial 1 I deemed requirement by requires feature a
create developed balance , I may 3rd being reason or
(or :Ilk non- Party and exception
using ,,liOli cause an
(1-5) Score

3.4.3.2 3.4.3.1 3.4.3 3.4.2.3 3.4.7.2 3.4.2.1 3.4.2 3.4.1.9
Subsection Section/ Requirement
— 13082
EXHIBIT
Ability Ability ELR Ability Ability Ability Single Ability RFP B-6.2
to to to to to audit to Section: Respondent:
track extract (Expenditure edit create extract create FINANCE
exclusions financial format SEFA data off-line
Limitation from Description Requirement
data Grant entries
Report) (paper Respondent's
module
entries)
- Statement
Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
o
Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
2
tagging County extract Advantage defined this data 'external The reflected post accrual County the 3) 2) to 1) with
of for) by capability for Advantage in to the entries Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
activity clarification: the provides the for financial data' that reporting. Advantage for clarification: foi Respondent's to or is a must
for yearly the County both reporting. may CAFR CAFR ' respond software. or is Standard shall be requirement. shall Specifications
ELR The SEFA data within CAFR be module general Examples proposal to every being indicate provided. if indicate
exclusion County report. needed the and The aggregated reporting. to feature, the exception,
and currently to module. non-CA,FR CAFR supports ledger, Such include be requirement provided requires feature a compliance
has create module with the but need entries financial deemed by 3rd being reason or
determining no (or reports supports Advantage importing to do and/or non- may Party and exception
the as of be not cause an
(1-5) Score

3.5. 3.5 3.4.4.4 3.4.4.3 3.4.4.2 3.4.4.1 3.4.4 3.4.3.4 3.4.3.3
Subsection Section/ Requirement
13082
EXHIBIT
Sources Capital Ability Calculate Ability Extract Variance Ability Ability RFP Respondent: B-6.2
for Asset to to to to Section:
capital edit variance create calendarized Report edit create FINANCE
Reporting report report ELR
reporting (data from variance budget (data report Description Requirement
and budget report and and
format) to actual financial format) Respondent's
data
Statement
Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Standard 3rd Party Custom! Standard/ Compliance
for use ELR to CGI ) 2) to 1) with
each "posting elements of one review will exclusions Reas‘-; responsive. the Failure equipment provided alternative each Respondent RFP
debit codes" and/or or exclusion. potential work is a i,,, Respondent's to Customization, is Respondents
and that more Some with purely ,:x. respond or a shall must requirement. shall
credit reflect reporting of options the I( ,,, A to software. or is Standard be Specifications
journal Advantage the to County manual (/1 proposal every being indicate provided. If indicate
the rollups, chart available tag during research ill;'( to be provided feature, the exception,
entry. nature/type or the of certain the Hative requirement requires feature a compliance
use account options effort. to deemed by 3rd reason or
of of include activity Envision si.),,,:thriHili non- may being
posting certain for cause Party and exception
the phase an
(1-5) Score

3.5.3 3.5.2.5 3.5.2.4 3.2.2.3 3.5.2.2 3.5.2.1 3.5.2 3.5.1.8 3.5.1.7 3.5.1.6 3.5.1.5 3.5.1.4 3.5.1.3 3.5.1.2 3.5.1.1
Subsection Section/ Requirement
3082
i I EXHIBIT
Betterments funds vs. Need to governmental Need to Infrastructure Capital Fixed Process Annexations infrastructure departments) Transfer Trade-Ins Seizures, Donations Capital Department RFP Respondent: B-6.2
be be Project Asset to of i.e. Projects Section:
government-wide able to funds able to asset record/account Assets RICO Purchases FINANCE
account (different account (transfers Description Requirement
statement for fund for among
governmental types) enterprise county Respondent's
funds
vs. Statement
Comply Comply Comply Comply Comply Comply Cornply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
I of
Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
—
/ the 3) 2) to 1) with
':(H res•onsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
i,, Respondent's to or is a
t).),:cf,oii: respond or Standard shall must be requirement. shall Specifications
i, .,/.. proposal to every software. is being indicate If indicate
, to feature, the provided. exception,
;;!II!r be requirement provided compliance
deemed by requires feature a
may 3rd being reason or
non- cause Party and exception
an
(1-5) Score

3.5.4.1.2 3.5.4.1.1 3.5.4.1 3.5.4 3.5.3.5 3.5.3.4 3.5.3.3 .5.3.2 3.5.3.1
Subsection Section/ Requirement
13082
EXHIBIT
Ability modified Ability MCDOT asset Need Need Need Need original Need RFP
to to Infrastructure to to to to to Section: Respondent: B-6.2
track approach report track allocate track track asset follow FINANCE
and assets betterment depreciation multiple same
report betterment
and depreciation Description Requirement
condition expenses number number betterments
to Respondent's
levels under the schedule
lead as
Statement
Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
. I o`
3rd Cimpliance
Standard Standard Standard Standard Standard Standard Standard Party Custom/ Standard/
other other that this County the 3) 2) to 1) with
3.5.3 requirement this Remsoli responsive. Failure equipment provided Respondents alternative each Respondent RFP
section is requirements requirement requirement, clarification: ii )i , Respondent's to or Customization, is a
met the respond or shall must requirement. shall Specifications
based within is County Not own! , to software. is Standard be indicate
requirements. on this Hid proposal every being indicate provided. If
the sufficiently certain (mu :Iii all, ‘; to feature, the exception,
CGI's section conveyed of Notik be requirement provided compliance
and addressed that the deemed by requires feature a
response that it interpretation may 3rd being reason or
to this by the believes non- cause Party and exception
the of an
(1-5) Score

3.5.4.1.4 3.5.4.1.3
Subsection Section/ Requirement
13082
EXHIBIT
Segmentation required Ability RFP Respondent: B-6.2
to Section:
of divert FINANCE
assets to
depreciation Description Requirement
approach Respondent's
if
Statement
Comply Comply Exception Comply/ Example of
of Comp
Standard Standard d Party Custom/ andard! iance
scope). an Advantage the and/or baseline and is CGI maintains feet/yards) (e.g., assets indicated roads, County the 3) 2) to , 'tith
CGI enhancement Envision Advantage can, bridges, management requirement m responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
will baseline phase granularity functionality. responding of one annexation in that - clarification: for Respondent's to or is a
work (but of as includes approximately side of a some washes, full pertains excei)/R respond or shall must requirement. shall Specifications
with are capabilities the requirements Any "Comply" of a small cases, segmentation asset primarily The 0 proposal to software. is Standard indicate be If indicate
the not asset 4000-6000 road). be of signals, lifecycle County /...itoircvii-, every being feature, provided.
County included may implementation that segmentation and The segment very these etc. and to , fitf;iiiithitive to be provided the exception, compliance
in be are "Standard" segmentation County complex The MCDOT conveyed , h deemed requirement by requires feature a
during the feasible to be found segments. (measured and infrastructure County maintenance asset that Hf);..i may 3rd being reason or
the original through beyond during complexity based capability currently in granular this i,,j/0 non- cause Party and exception
on for , ) an
(1-5) Score

.6.1 3.6 3.5.4.2.3 3.5.4.2.2 3.5.4.2.1 3.5.4.2 3.5.4.1.5
Subsection Section/ Requirement
13082
EXHIBIT
Year-End Inventory fixed Add to Preservation convention Track Flood roadway Interface/Feed RFP Respondent: B-6.2
asset fixed contro Section:
Closing type asset cost depreciation l system) FINANCE
Form are from
module based MCDOT Description Requirement
capitalized on
utilizing the system
and mid-year Respondent's
(MCDOT
expanded
Statement
Comply Comply Comply Comply Exception Comply/ Example of
of Corr
3rd
Standard Standard Standard Standard Party Custom/ Standard/
..:e
currently the County forms facilitate Advantage fixed County Envision the 3) 2) to 1) with
inventory requirements of asset requirement won responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
tracked clarification: inventory the types. clarification: phase for e Respondent's to or is a
in module below. as management inventory represents to .:y11.n respond or shall must be requirement. shall Specifications
is With The assess to software. is Standard indicate
Advantage. not the referenced of management the County the ic,iitiltompoi )/?,/ proposal every being indicate provided. if
used and exception in ability potential ;i, ,,,i,ii; to be provided feature, the exception, compliance
Based the consumable to add confirmed , ' requirement requires feature a
on the inventory of the response and functionality gaps. ';' , , deemed by 3rd being reason or
year-end is MCSO, to other to client-defined that this ,cification non- may Party and exception
not the cause an
(1-5) Score

3.6.1.2 3.6.1.1
Section/ Requirement
13082
EXHIBIT
adjustment Calculation: package) Department RFP Respondent: B-6.2
Section:
value difference submit FINANCE
from year-end Descripti Requirement
current on
to inventory Respondent's
prior (closing
year
-- Statement
„
Comply Comply Exception Comply/ Example of
of
Standard Standard 3rd Party Custom/ Standard/ Compliance
difference Per the vouchers. supports Advantage inventory Per the inventory processing Advantage requirements. reporting the Advantage), department inventory the 3) Failure 21 to 1) with
County the County procedure/process annual ../) i.i)/ responsive. to equipment Customization, provided Respondents alternative each Respondent RFP
and year-end stores closing adjustments. of journal supports purposes. adjustments manually to the (dosing c \ Respondent's respond or on, is a must requirement. shall
necessary clarification, the prior package clarification, the pertaining There package) to software. or is Standard shall be Specifications
adjusting year voucher current is for entered Department proposal every being indicate provided. If indicate
adjustment the prior account occurs submission entries and to the no each journal of submitted :hulti,iiivc to be provided feature, the exception, compliance
value entries via outside of to continued 3.6.1 expected department Finance by deemed requirement by requires feature a
is year/current journal balances of the record section change for vouchers (external each !um; non- may 3rd being reason or
manually year and Advantage. year-end the manual to this record to ? cause Party and an exception
(1-5) Score

3.6.3.2 3.6.3. 3.6.3 3.6.2.3 3.6.2.2 3.6.2.1 3.6.2
1
Subsection Section/ Requirement
13082
EXHIBIT
Full purchased) Modified Reporting form Post Posted Inventory 30 only) MCSO — RFP Respondent: B-6.2
accrual adjusting directly Section:
accrual module Sheriffs FINANCE
reporting entry
(expensed reporting manually utilized warehouse Description Requirement
when (expensed based only Respondent's
on (funds
used) — when year-end 120
and
I i Statement
Comply Comply Comply Comply Comply Exception Comply,/ Example of
, of
Standard Standard Standard Standard Standard 3rd Party Custom! Standard/ Compliance
Please Advantage Advantage vouchers. supports Advantage package . the 3) Failure to 1) with
see implementation implementation the calculated/determined ., responsive. to equipment Customization, provided Respondents alternative each Respondent RFP
the section of supports of supports year-end stores information Respondent's respond or is a shall must requirement. shall
the this the this the prior to software. or is Standard be Specifications
3.6.1 Inventory Inventory adjusting year submitted based f proposal every being indicate provided. If indicate
section requirement requirement entries account from on the to be provided feature, the exception, compliance
responses. module. based module. based via each year-end deemed requirement by requires feature a
on on journal balances non- may 3rd being reason or
and department. closing cause Party and exception
an
(1-5) Score

3.7.3.1 3.7.3 3.7.2.2 3.7.2.1.3.1 3.7.2.1.3 3.7.2.1.2.1 3.7.2.1.2 3.7.2.1.1 3.7.2.1 3.7.2 3.7.1 3.7
Subsection Section/ Requirement
13082
EXHiBIT
Monthly Monthly projects year to Ending Ability Not fixed Ability Capitalize Ability Tracking Financial Capital Capital based RFP Respondent: B-6.2
year to capitalized asset to to on Section:
budget, reports greater using balance expense module prepare track Expenditures Reporting Projects Projects entity FiNANCE
actual than the required (off of fixed multiple Approved
and one OP to OP) (Advantage) asset years Management Description Requirement
cash year) excel be
roiled form
reconciliation spreadsheet over and Respondent's
from enter
(for into
Statement
..
Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
3rd Compliance
Standard Standard Standard Standard Standard Standard Standard P Custom/ Standard/
arty
CI? as the Users , 3) 2) to 1) with
Advantage as its Advantage needed. system can .7 responsive. the Failure equipment provided Respondents alternative each Respondent RFP
own rolls and capture lUi f Respondent's to Customization, is
provides asset all enter \ respond or a shall must requirement. shall
type. asset fixed fixed ' to software. or is Standard be Specifications
various asset proposal every being indicate provided. if indicate
standard balances asset :/h;:t Ili to feature, the exception,
forward entries information li! be requirement provided feature compliance
financial into deemed by requires a or
and external . non- may 3rd being reason
reports tracks Advantage to 11(;,•)1 , cause Party and exception
an
(1-5) Score

3.8.1.2 3.8.1.1.1 3.8.1. 3.8.1 3.8 3.7.3.4 3.7.3.3 3.7.3.2
Subsection Section/ Requirement
13082
Scanned I nput AP Woirkflow Cash Project Current reports RFP EXHIBIT
Notification workflow Section: Respondent: B-6.2
for to (invoice) reconciliation cumulative year FINANCE
X OnBase in budget
duration financial total and
in workflow by actuals Description Requirement
queue module fiscal
(no year Respondent's
action
Statement
Comply Exception Comply Comply Comply Comply Exception Comply/ Example of
of
Standard 3 Party rd Standard Standard Standard Standard 3rd Party Custom/ Standard/ Compliance
and Invoice and and ' and and the 3) 2) to 1) with
Advantage will be infoAdvantage additional Advantage infoAdvantage additional ,dvantage .foAdvantage additional Advantage infoAdvantage additional responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
provides addressed scanning to as reports provides as reports provides as reports provides as reports Respondent's to respond or is a shall must requirement. shall
automatic by OnBase needed. may various needed. may various needed. may various needed. may proposal to software. or is being Standard indicate be If indicate Specifications
the is be be be be IIIIR:1001)/ .11/i%..to,/y to every feature, provided.
escalation County. external developed standard developed standard developed standard developed be requirement provided the exception, compliance
of to in financial in financial in financial in deemed by 3rd requires feature a reason or
workflow Advantage reports reports reports non- may Party being and exception
cause an
(1-5) Score

3.8.2.1 3.8.2 3.8.1.8 3.8.1.7 3.8.1.6 3.8.1.5 3.8.1.4 3.8.1.3
Subsection Section/ Requirement
13082
EXHIBIT
transactions) Need to Journal Re-approve correction Modification View queue Pending Finance Departmental taken) RFP Respondent: 8-6.2
route entry (see of payment notification payment approval Section: FINANCE
to OMB workflow 3.8,1.5) payment voucher error (level approval
for reject (no 3) (level Description Requirement
approval voucher warrant 1 and
not for 2) Respondent's
all error generated)
Statement
,
Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of Comp
Standard Standard Standard Standard Standard Standard Standard 3rd Party Custom/ Standard/ iance
trigger approvers edits prior these against Payment with the 3 2) to 1 with
email may to edits no transactions Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
are be posting. and system action. for Respondent's to is
notifications routed queried receive edits transactions, based on exception respond or or a shall must requirement. shall Specifications
back online. Payments all real-time. like a and proposal to software. is being Standard indicate be If indicate
and be to the that required all user-defined requirement. to every feature, the provided. exception,
queried Payments are Payments documents, alternative be requirement provided compliance
submitter rejected workflow number to deemed by requires feature a
online. and rejected by must are of specification non- may 3rd being reason or
can by system approvals pass validated days cause Party and exception
an
(1-5) Score

3.8.3.2 3.8.3.1 3.8.3 3.8.2.9 3.8.2.8 3.8.2.7 3.8.2.6 3.8.2.5 3.8.2.4 3.8.2.3 3.8.2.2.1 3.8.2.2
Section/ Requirement
13082
Payment Electronic jail OMB Expanded 1 View Finance taken) Scan Input RFP EXHIBIT
bond Re-approval Modification journal Departmental Notification to (journal Section: Respondent: 8-6.2
voucher feed workflow approval) for (see of entry approval for X OnBase FINANCE
(OnBase) from county 3.8.1.5) journal rejects (level approval duration workflow entry) in
NICSO to wide entry 3) (level in finance Description Requirement
feed to OnBase journal for 1 and queue
entries error 2) (no module Respondent's
Advantage (not correction action
for
Statement
-
Exception Exception Comply Comply Comply Comply Comply Comply Comply Exception Comply Exception Comply/ Example of
of
Party rd Party 3 rd Standard Standard Standard Standard Standard Standard Standard 3 rd Party Standard Custom/ Standard/ Compliance
Advantage CGI Advantage The with Advantage and Invoice the 3) 2) to 1) with
will feed no transactions will be Reason responsive. Failure equipment provided Respondents alternative each Respondent RFP
and develop and from action. scanning for Respondent's to Customization, is
OnBase. the will be MCSO based on provides addressed to exception respond or or a shall must requirement. shall Specifications
CGI integration to a automatic by the OnBase and proposal to software. is being Standard indicate be if indicate
addressed OnBase user-defined is lequiretnent. every feature, provided.
assumes by is escalation County. external alternative to be provided the exception, cornpliance
the framework the external number to to deemed requirement by requires feature a
County between County. to of of Advantage spoGilicoIr()/, non- may 3rd being reason or
will days workflow cause Party and exception
an
(1-5) Score

_
3.8.4.2 3.8.4.1 3.8.4 3.8.3.6 3.8.3.5 3.8.3.4 3.8.3.3
Subsection Section/ Requirement
13082
EXHIBIT
indexing Ability Electronic Re-approve Modifications View JB Finance RFP Respondent: 8-6.2
for to image rejects (level Section:
all all Document (see of 3) FINANCE
supporting 3.8.1.5) JB for review
documents Storage error and Description Requirement
documentation correction approval Respondent's
I „ Statement
Exception Exception Comply Comply Comply Comply -Exception Comply/ .. Example of
of
3 rd 3' d Standard Standard Standard Standard 3rd Custom/ Standard Compliance
Party Party Party
_..,
such ECM develop Advantage CGI such ECM develop Advantage CGI Voucher. ECM develop the 3) 2) to 1) with
as for will as for will for ;,,,();: responsive. Failure equipment provided Respondents alternative each Respondent RFP
indexing each the and develop imaging each the and develop each the /or Respondent's to Customization, is
for business integration OnBase. the business integration OnBase. the business integration uxcepticm respond or or a shall must requirement. shall Specifications
all documents. to software. is Standard be
supporting transaction between CGI integration transaction between CGI integration transaction between II. , proposal every being indicate provided. If indicate
assumes assumes .:IiM1)1. ,illil7N.1ir, to be provided feature, the exception, compliance
and Advantage the framework and Advantage the framework such as Advantage I deemed requirement by requires feature a
documentation. related 3 County related 3 County a 3 may 3rd being reason or
needs and between needs and between Payment and ;1)(WilIC,"2//i non- Party and exception
the will the will the !i i cause an
(1-5) Score

3.8.5.1.1 3.8.5.1 3.8.5
Subsection Section/ Requirement
13082
EXHIBIT
Template payment Notification Electronic RFP Respondent: B-6.2
Section:
and was Fund FlNANCE
copy (email
of executed from Transfer
invoice to (EFT) Description Requireme
vendor OnBase nt
workflow) Respondent's
that
Statement
Exception Exception Except Comply/ — Example of
ion of
3"1 rd 3 3rd Compliance
Party Party Party Custom/ Standard/
the into County ECM develop CGI identify will certain ECM develop I CGI the 3) 21 to 1) with
determine Envision to Advantage for Advantage will implement work capabilities for Advantage will responsive. Failure equipment provided alternative each Respondent RFP
if/how Advantage. pull each the and develop them such with other that each the and develop Respondent's to Customization, is Respondents
to phase to CGI this, provides business integration OnBase. the within functions the OnBase may business integration OnBase. the , respond or or a shall must requirement. shall Specifications
will and County allow ,z.tquif to software. is Standard be indicate
implement identify work certain capabilities between CGI integration and functions, the between CGI integration proposal every being indicate provided. lf
them such with other that transaction assumes Advantage. determine during into County transaction. assumes -://::i to be provided feature, the exception,
within functions the OnBase may and Advantage the framework the to Advantage Advantage the framework deemed requirement by requires feature a compliance
County allow related 3 County if/how Envision Advantage. pull 3 County 3rd being reason or
Advantage. and during functions, the needs. and will between to phase CGI this, provides and will between non- may Party and exception
the to and the cause an
(1-5) Score

3.8.6.1 3.8.6 3.8.5.3 3.8.5.2
Subsection Section/ Requirement
13082
ensure Ability Vendor into Email send RFP EXHIBIT
to tax ACH from to Advantage Section: Respondent: B-6.2
proper review review account OnBase bank created FINANCE
tax (Chase)
code vendor to EFT
for Treasurer file Description Requirement
Advantage registration to NACHA
transfer format Respondent's
entry documents and
funds
to Statement
Comply Exception Comply Exception m Comply/ Example of
i of
Standard 3 rd Standard rd Custom/ Standard/ Compliance
Party Party
registration addition registration Advantage ECM develop Advantage CGI the 3) 2) to 1) with
number/name for the will Reason responsive. Failure equipment Customization, provided Respondents alternative each Respondent RFP
Advantage before provides each and develop for Respondent's to or is a
accuracy. information it is business integration OnBase. the exception respond or Standard shall must be requirement. shall Specifications
to the provides approved the ability between CGI integration requirement. and proposal to every software. is being indicate provided. if indicate
IRS a to transaction. assumes alternative to feature, the exception,
database process and review Advantage framework be requirement provided requi feature a compliance
to made a the to deemed by res reason or
for tax match active. vendor's 3 and County between specification non- may 3rd Party being and exception
ID vendor In the will cause an
(1-5) Score

4.1.2.3 4.1.2.2 4.1.2.1 4.1.2 4.1.1.1.3 4.1.1.1.2 4.1.1.1.1 4.1.1.1 4.1.1 4.1 4.0
Subsection Section/ Requirement I
13082
information Ability method, Ability Ability Solicitation contract Ability Ability based Ability Request Article Contracting Procuremen RFP Respondent: EXHIBIT
for i.e., to use to to add to on to for 3 Section: B-6-3
upload view business initiate need (Supplies t
department reverse multiple Development multiple existing rules a and PROCUREMENT
to enter auction, types supporting contract as requisition Services) Description Requirement
of same commodity
solicitation low-bid, solicitation documents as appropriate which Respondent's
etc. Article codes will
5) to a be
routed
Statement
Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
ustom/ Compliance
Standard Standard Standard Standard Standard Standard Party Standard/C
3rd
3) 2) 1) with
Reason cause Failure Party provided reason exception RIP
for non-responsive. the to Customization Respondents and Respondent
excep!, respond equipment , is a an to shall Specifications
t Iei ,, ; ;:',( Respondent's to or or is Standard shall alternative each
oi'0111(.?,1! 1 'It every software. being indicate requirement. indicate
li:Ill...t: proposal provided feature, the must
'0 to requirement requires feature be If compliance
be by 3rd being provided. exception, or
deemed may
; a 4
(1-5) Score
Formatted:
Tab
stops:
2.3,
Left

4.1.2.7 4.1.2.6.1 4.1.2.6 4.1.2.5 4.1.2.4
Subsection Requirement
Ability on Ability document Ability document Ability Ability RFP
to permissions to to to to Section: Respondent:
apply have status have create initiate
record access document draft
retention to audit contract advertising Descripon Requirement
version
(all trail and directly Respondent's
phases) records control solicitation
based and
Statement
1
Exception Comply Comply Comply Comply Exception Comply/ ' Example of
of
Compliance
Party Custom/3 Standard Standard Standard Standard Party ustom/ Standard/C
rd 3rd with
Advantage develop the latest records continue records for The needs each Advantage Service. various Advantage Reason cause 3) Party 2) reason 1) FU-T
and the release retention to retention. Electronic County to be time that types for non-responsive. the Failure to Customization, provided Respondents and exception Respondent
integration of use this Content currently updated. a creates of provides exception respond equipment or is a shall an to each shall Specifications
OnBase. CGI needs solution CGI previously a new solicitations the re and Respondent's to or is Standard alternative
CGI framework Advantage. as the to expects Management utilizes the version via ability airenInnt. every software. being feature, indicate requirement. indicate
assumes County meet that approved of Vendor to alternative proposal provided the must be compliance
the between CGI its the (ECM) OnBase a publicly to to be requirement by requires feature If
County will moves ECM County and solution document document Self advertise specification may 3rd being provided. exception, or
to and can deemed a
(1-5) Score

4.1.3.1 4.1.3 4.1.2.12 4.1.2.11 4.1.2.10 4.1.2.9 4.1.2.8
Subsection Section/ Requirement
Ability Open Ability between Ability values Ability phase) Ability phases) Ability RFP
to to to (all to to to Section: Respondent:
answer Solicitation add department establish phase) search have finalize
vendor vendors by unique
(ad-hoc) and approval keyword, key documents Description Requirement
questions procurement process unique, for each for
(users or document publishing Respondent's
outside workflow index (all
(all
Statement
Comply Comply Comply Comply Comply Comply Exception Compy / . Example of
of
Standard Standard Standard Standard Standard Standard Party ustorn/ Compliance
3rd
Standard using search to approve an and will Reason 3) 2) 1 with UP
solicitations. for Advantage Vendor documentation a Advantage invoice. the develop for cause Failure Party provided Respondents reason exception Respondent
Advantage infoAdvantage. provides Self solicitation provides ECM for the exception non-responsive. the to equipment Customization, is a and an to
Additional procurement Service. prior to the each integration Respondent's respond or or i Standard shall each shall Specifications
security queries various publishing including ability business rccitiiiciliont and to every software. s being indicate alternative requirement. indicate
can be can documents online to between alternative proposal provided feature, the must
used be including inquiries the supporting review transaction to to requirement by requires feature be if compliance
to grant performed to solicitation and such Advantage specification be deemed may rd being provided. exception, or
as 3 a
(1-5) Score

4.1.4.1 4.1.4 4.1.3.7 4.1.3.6 4.1.3.5 4.1.3.4 4.1.3.3 4.1.3.2
Subsection Section/ Requirement
Ability Solicitation Ability Ability Ability Ability Ability Ability of RFP
to to electronically for to to to to system) Section: Respondent:
view all Evaluation attach/add vendors amend/addend conduct cancel bid respond
responses to on-line to
vendor respond vendor Description Requirement
and responses to solicitation pre-bids questions Respondent's
solicitation solicitation docs
Statement
Comply Comply Comply Comply Exception Comply Comply Exception Comply/ Example of
of
rd 3 ustom/ Compliance
Standard Standard Standard Standard Party Standard Standard Party Standard/C
' 3rd with
enter choose Vendor Vendors attendees. buyer Advantage typically Third procurement limited -7';., . ..1.' .o cause 3) Failure Party 2) reason 1) RFT
these to Self can to used party system to: non-responsive. the to Customization, provided Respondents and exception Respondent
responses receive Service. create manually does, to tools group. access :...-",... respond equipment or is a an to shall Specifications
in offline online record however, conduct such as to Respondent's to or is Standard shall alternative each
the Optionally, pre-bid a users every software. being indicate requirement. indicate
system. responses the solicitation provide pre-bid LiveMeeting outside i proposal provided feature, the must
and County conference the conference. or of to be requirement by requires feature be If compliance
manually may responses ability for WebEx the core deemed may 3rd being provided. exception, or
via a are a
(1-5) Score

4.1.4.9 4.1.4.8 4.1.4.7 4.1.4.6 4.1.4.5 4.1.4.4 4.1.4.3 4.1.4.2
Subsection Section/ Requirement
Ability Ability second Ability Ability Ability Ability Ability Ability information RFP
to to call, to to to to to to Section: Respondent:
award award etc.) create create award select search rank
in part in whole positioning under to vendor bid responding
/ one multiple for based Description Requirement
phases (vendors agreement vendors contract on vendor vendors
Respondent's
- first or
call, criteria
Statement
Comply Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
-: of
Ser Compliance
Standard Standard Standard Standard Standard Standard Standard Standard Pa:rty ustorn/ Standard/C
3rd with
at a Master vendor using search 3) 2) 1) RFP
groups/lots. Parts/phases line Advantage as Advantage Agreement Advantage solicitations. for Advantage cause Failure Party provided reason exception Respondent
item Agreement. a that infoAdvantage. to/ non-responsive. the to equipment Customization, is Respondents and to
can be level provides primary provides supports Additional procurement provides exception respond a shall an each shall Specifications
defined or a the or the includes the various ,;?:! Respondent's to or or is Standard alternative
as group/lot ability secondary ability multiple ability queries documents 17 every software. being feature, indicate requirement. indicate
to to to can online :ili:•ith(nic proposal provided the must
separate level. define vendor define vendors. issue a be inquiries , . to requirement requires feature be If compliance
lines and on a each Master performed including to be by 3rd being provided. exception, or
or award -7- deemed may a
(1-5) Score

4.1.5.2 4.1.5.1 4.1.5 4.1.4.13 4.1.4.12 4.1.4.11 4.1.4.10
Section/ Requirement
clerk Ability for Ability Contract award Ability Ability Ability Ability RFP
the of to approval to package to to to to Section: Respondent:
board send route Award review award award award
if on based draft and by by by
contract information multiple locai line
business contract approve region item Description Requirement
is
=>$500k (approved rules through final vendors Respondent's
contract
contract) workflow
and
to Statement
Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
ustom/ Compliance
Standard Standard Standard Standard Standard Standard Stanclard/C
3rd
with
the board to Standard that that regions. 3) 2) 1) RFP
user as notify documentation. document can Advantage documentation. document can Advantage groups/lots Advantage cause Failure Party provided reason exception
not is an certain be be 10! non-responsive. the to Customization, Respondents and Respondent
in Advantage including to used provides including to used provides which provides ,:y)' i'N(: respond equipment a is an to shall Specifications
the informational users any review a any review a can the Respondent's to or is or Standard shall alternative each
formal as such workflow and standard and standard used be ability ,:?!10 1!1i •I'(; every software. being indicate requirement. indicate
approval notification the supporting supporting to to . , :..'l01l1::1,' proposal feature, the must
clerk routing approve workflow approve workflow define define _ to requirement provided feature be If compliance
chain. even the of be can any any local and be 3rd by requires provided. exception, or
though used process process award deemed may being
a
(1-5) Score

4.1.5,8 4.1.5.7 4.1.5.6 4.1.5.5 4.1.5.4 4.1.5.3
Subsection Section/ Requirement
Ability against Ability spend Ability Ability Ability Wes Ability RFP
to items for from to to to (dept. to Section: Respondent:
accept for finance view have review head) send
and to department) spend multiple and for information
validate department create analysis PO approval contracts Description Requirement
e-signatures report (collect types process <$500k (approved Respondent's
tracking data
on contract)
spend
to Statement
.
Exception Comply Comply Comply Comply Comply Exception Comply/ Example of
.,_. of
. Compliance
Custom Standard Standard Standard Standard Standard Party ustorn/ Stanclard/C
3rd _ with
during also Advantage User where Advantage performed spend Advantage performed spend Advantage user is as an to notify Standard ..,,,;,,:: cause 3) Party 2) 1) RFP
the supports ID and an data. data. not for non-responsive. the Failure Customization, provided Respondents reason exception Respondent
approval both document authorized supports using provides using provides in the informational certain Advantage ; • ‘ :, , ,, to equipment is a and an to Specifications
Password Additional Additional formal users ,:i:,,I Respondent's respond or Standard shall each shall
process digital (e.g. and user workflow infoAdvantage. various infoAdvantage. various notification such workflow .?c! .;; ; to or is being indicate alternative indicate
and can logs queries queries approval as illt,) every software. feature, requirement.
where a non-digital requisition). then into review and online and online even the routing proposal provided the must compliance
'signed' approve the and reports inquiries reports inquiries chain. though department can to be requirement by requires feature be If
PDF signatures Advantage an system via approval can to can to the be ,,ciiii.....,,..;ri deemed may 3rd being provided. exception, or
a be view be view head used a
(1-5) Score
._ .

4.1.6.1.1.2.1 4.1.6.1.1.2 4.1.6.1.1.1 4.1.6.1.1 4.1.6.1 4.1.6
Section/ Requirement
Ability Vendor Public Project Request Article RFP
to Specific for 5 — Section: Respondent:
register List/Simplified advertising need
Construction
construction Description Requirement
Construction
projects Respondent's
Statement
Exception Comply Exception Comply/ Example of
of
ustom/ Compliance
Custom Standard Standard/C
3rd with
to allow County not The Service. various Advantage The file is Reason 3) 2) 1) RFP
qualifying an capture current types capabilities enhancements scope for cause Failure Party Customization, provided Respondents reason exception Respondent
interactive Article 5 the of provides described to of the generated exception non-responsive. the to equipment is a and an to Specifications
questions. system level of Advantage solicitations the the project and / Respondent's respond or or is Standard shall each shall
experience and detail ability above. existing does stored. tivi, o and to every software. being indicate alternative requirement. indicate
to is not as registration via to not merit. alternative proposal feature, the must
record the process Vendor publicly Advantage include to to requirement provided requires feature be If compliance
configurable Maricopa Self any be by 3rd provided. exception, or
responses to does advertise specification deemed may being
a
(1-5) Score

4.1.6.1.1.2.2
Subsection Section/ Requirement
Ability RFP
to Section: Respondent:
register
professional De
cription Requirement
services Respondent's
Statement
Exception Exception Comply/ Example of
of
ustom/ Compliance
Custom Party Standard/C
s 3rd with
currently customized The to allow County not The registration Financial applied Advantage automate procurement be registration currently customized The Reason cause 3) Failure Party 2) reason 1) RFP
Advantage qualifying an Article capture current to or available Advantage for non-responsive. the to Customization, provided Respondents and exception Respondent
captured to support questions. interactive 5 the level Advantage information where Vendor system. impact process for system. captured to support exception respond equipment is a an to shall Specifications
in the vendor system of County Self The any but manual The in the vendor and Respondent's to or or is Standard shall alternative each
County's the registration experience and is detail registration on an users Service will review additional County's the registration requirement. every software. being indicate requirement. indicate
information to not as the as can and customization functionality not be to information alternative proposal provided feature, the must
Article that process record configurable Maricopa process needed maintain to will within used support information Article that process to to be requirement by requires feature be If compliance
5 is will responses does basis. vendor Advantage be the to the 5 is will specification deemed may 3rd being provided. exception, or
be to will be a
(1-5) Score

4.1.6.1.1.2.4 4.1.6.1.1.2.3
Subsection Section/ Requirement
I
Ability Ability RFP
for to Section: Respondent:
create
notification ..
for groupings _
Description Requirement
re-register
Respondent's
dent's
Statement
Comply Comply Exception Comply/ Example of
of
Compliance
Standard Standard Party ustorn/ Stanciard/C
3rd
with
approach review report To date Advantage process. more Business more Advantage registration Financial applied Advantage automate be registration cause 3) Party 2) 1) RFP
the and could for Business to or procurement available non-responsive. tlY=-_ Failure Customization, provided Respondents reason exception Respondent
Active update be a vendor provides Type. categorizations provides where Vendor system. impact for system. system. to equipment is a and an to Specifications
To their developed the Types Vendors or the information County Self The any process manual The Respondent's respond or or is Standard shall each shall
date. account to profile. ability during can grouping ability on users Service but will review i;i: /,, ., , to every software. being indicate alternative requirement. indicate
notify An to the then to an as can and customization functionality not to additional ,pi proposal feature, the must
as needed infoAdvantage specify registration select of define needed maintain to be used support to requirement provided requires feature be If compliance
as vendors an one vendors one basis. Advantage will be within to the information be by 3rd provided. exception, or
they to Active or via a or vendor the deemed may being
will a
I I 1 I , i 1
(1-5) Score

4.1.6.1.2.2 4.1.6.1.2.1 4.1.6.1.2
Subsection Section/ Requirement
Ability Ability On-call RFP
for to Section: Respondent:
register contract
notification
for professional Description Requirement
re-register
services Respondent's
Statement
Comply Exception Exception Comply/ Example of
of
ustom/ Compliance
Standard Custom Party Standard/C
3rd with
To date Advantage registration Financial applied Advantage automate be registration currently customized The to allow County not The cause 3) - Party 2) 1) RFP
for to or procurement available Advantage qualifying an Article capture current ici non-responsive. the Failure Customization, provided Respondents reason exception Respondent
a vendor provides where Vendor system. impact process for system. captured to interactive 5 the ,.. \ to equipment is a and an to Specifications
the information County Self The any manual The in the support vendor questions. system level of Advantage i Respondent's respond or or is Standard shall each shall
profile. ability on an users Service but will review County's the registration experience and detail to every software. being indicate aiternative requirement. indicate
An to as can and customization functionality not to additional information to is not as the registration !f?..:;),iive proposal provided feature, the must
infoAdva.ntage specify needed maintain to will within be used support information Article that process record configurable Maricopa process to be requirement by requires feature be if compliance
an Active basis. vendor Advantage be the to the 5 is will responses does deemed may 3rd being provided. exception, or
will be to a
(1-5) Score

4.1.6.2.4 4.1.6.2.3 4.1.6.2.2 4.1.6.2.1 4.1.6.2 4.1.6.1.2.3
Subsection Section/ Requirement
Ability Ability 30 MB) Ability Same Solicitation Ability RFP
to to to as project(s)/Contract(s) to Section: Respondent:
sequence support upload Article restrict
3 Development
clauses different CAD/PDF/TIFF (functionality) amount or Description Requirement
templates docs money Respondent's
(both file against
sides) (minimum specific
Statement
..
Comply Comply Comply Comply Comply Exception Comply/ Example of
of Co.
p
Standard Standard Standard Standard Standard Party ustom/ Standard/C lance
rd with
three CGI templates Advantage maximum Advantage See or the to control addition, Exceed' Advantage approach review report cause 3) Failure Party 2) reason 1) RFP
Subprojects. will via responses overall amount the and could or non-responsive. the to Customization, provided Respondents and exception Respondent
develop an provides attachment provides to project. spending separate for provides Active update be e).L , ,. respond equipment is a an to shall Specifications
up to 10 Adobe the the Article against project each the To their developed , Respondent's to or or is Standard shall alternative each
Adobe form. ability size. ability 3 above Master ability date. account to ,i/ ' If every software. being indicate requirement. indicate
to to portions budgets to as notify proposal provided feature, the must
forms configure configure of can be Agreement. define needed vendors to requirement by requires feature be If compliance
across the the defined a 'Not as to be may 3rd being provided. exception, or
all various project In to they deemed a
(1-5) Score
_

4.1.6.4.2.5 4.1.6.4.2.4 4.1.6.4.2.3 4.1.6.4.2.2 4.1.6.4.2.1 4.1.6.4.2 4.1.6.4.1.1 4.1.6.4.1 4.1.6.4 4.1.6.3.1 4.1.6.3 4.1.6.2.5
Subsection Section/ Requirement
Ability Ability Ability Ability Ability Request Ability Bid Solicitation Same Open contract Ability RFP
to for to to to for to evaluation as to Section: Respondent:
add freeform rank assign create view Article Solicitation type, select
additional and score qualifications tab - low Evaluation 3 i.e.
text modify evaluation sheets bid bonds, required
scoring score card (add quote (functionality) Description Requirement
(comments) criteria in insurances, elements
criteria Article (same based Respondent's
3) as etc.
Article on
3) Statement
Comply Comply Comply Comply Comply Comply Comply Comply Comply Exception Compy / . Example of
of
ustorn/ .:: Compiiance
Standard Standard Standard Standard Standard Standard Standard Standard Standard Party .ction
3rd 2
See ;.;..,,:!;; . 3) 2) 1) with
Advantage downloaded evaluation Advantage downloaded evaluation Advantage different condition Advantage . ,:q! cause Failure Party Custom provided reason exception RR
to to responses types and (i)1 .non-responsive. the to . is Respondents and Respondent
provides MS process. provides MS process. provides to of provides cixi.opi respond equipment zation, a an to shall Specifications
the Excel an Excel an Article contracts. evaluation the Respondent's to or or is Standard shall alternative each
ability for Additional online for Additional online 3 above criteria ability 71IJiiIii. I f every software. being indicate requirement. indicate
to further bid further bid to proposal provided feature, the must
define analysis. information tabulation analysis. information tabulation templates define to requirement by requires feature be If compliance
various can in can in to terms be may 3rd being provided. exception, or
be the be the meet and deemed a
(1-5) Score

4.1.6.5.4 4.1.6.5.3 4,1,6.5.2 4.1.6.5.1 4.1.6.5 4.1.6.4.2.6
Subsection Section/ Requirement
submit, Ability flow) Ability awarded Note: Same Contract evaluation Ability RFP
for — for not to (presentation Section: Respondent:
review users workflow contract through in functionality Award add
and (outside process status delegated agenda for as additional stage/discussion
approve of (all Article Article Description Requirement
(AU) internal articles authority 5 3 scorecard
contracts after phase) Respondent's
system) and the
to overall initial
Statement
^
Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Standard Standard Standard Standard Standard Party ustom/ Stanciard/C ,ti ; Compliance
3rd 2
core define Standard review can be Advantage enforce Advantage See solicitation separate solicitations Advantage step Advantage items evaluation cause 3) Failure Party 2) reason 1) with UP
procurement limited and used delegated responses solicitations such as non-responsive. the to Customization, provided Respondents and exception Respondent
system Advantage approval to route provides provides to phase. evaluation to provides to also criteria respond equipment is a an to shall Specifications
group. any purchasing the Article is include the include provides presentation templates Wip'1110;:1 Respondent's to or or is Standard shall alternative each
access security including standard ability 3 above performed phases ability the , every software. being indicate requirement. indicate
to users provides contracts. Advantage workflow authority. to for such to phases ability stage/discussion which mt, proposal provided feature, the must compliance
the define each as a define such to can to requirement requires feature be If
outside ability document routing and BAFO. multi-step as a define include be by 3rd being provided. exception, or
of the to for that A BAFO. multi- phase. deemed may a
(1-5) Score

4.2.1.3 4.2.1.2 4.2.1.1 4.2.1 4.2 4.1.6.5.6 4.1.6.5.5
Subsection Section/ Requirement
Ability Ability Ability Maintain Contracting Ability Ability RFP Respondent:
to to to all to for Section:
report notify retrieve delegate
from buyers active contracts Maintenance notifications
data and and in the responsibilities and Description Requirement
fields on suppliers inactive system timers Respondent's
contract contracts (overall) (overall)
Statement
Comply Comply Comply Comply Comply Excepti Comply/ Example of
on - of
ustorn/ Compliance
Standard Standard Standard Standard Standard Party 3
rd with
other when to a event the cc 3) 2) 1) RFP
correspondence Advantage Advantage they delegate Advantage defined that Advantage workflow appropriate Advantage se Failure Party provided reason exception Respondent
authorized also will their period an also users non-responsive. the to equipment Customization, is Respondents and to
related user provides provides be out workflow of approver supports review as provides Respondent's respond or a shall an each shall Specifications
to to several of authority provides time. does and a email tt'qUi::-?•Irt't/ to or is Standard alternative indicate
a record the the in not workflow approval document every software. being feature, indicate requirement.
procurement. various ability standard office situation the take notifications fhp• , proposal provided the must compliance
for a (e.g. such ability action escalation process. moves to to be requirement by requires feature be If
additional buyer notifications. vacations). as for a in through the ..:pc deemed may 3rd being provided. exception, or
or user within the ii,, a
(1-5) Score

4.2.1.8 4.2.1.7 4.2.1.6 4.2.1.5 4.2.1.4
Subsection Section/ Requirement
I
Ability dates, Ability applied Ability Ability contained Ability RFP
to to to to to to Section: Respondent:
reverse insurance, track vendor send amend in the filter
auction etc. specific notification contracts data notification
information set Description Requirement .
(both elements when based
article i.e. change on Respondents
3 & 5) Expiration was profile
or
field Statement
Comply Comply Comply Comply Comply Exception Comply/ Example of
. of
Compliance
Standard Standard Standard Standard Standard Party ustom/
3rd with
and updated ability and the filtered Certain . 31 2) 1) RFP
Advantage Insurance information Advantage in notifications Advantage to infoAdvantage Additional commodities. the goods notifications to cause Failure Party provided Respondents reason exception Respondent
on a define vendor's and are such as standard . _ non-responsive. the to equipment Custornization, is and to
supports a provides vendor when provides various and notifications that services . respond or a shall an each shall Specifications
various information. contract the account. various several have filtered solicitation Advantage Respondent's to or is Standard alternative indicate
ability filter infoAdvantage can be specified based , every software. being indicate requirement.
types of including to information standard criteria. created registered on on a notifications notifications .. proposal provided feature, the must compliance
Expiration track is vendor supports via for the match , • ... ... to be requirement by requires feature be if
solicitations various added the the solicitation where are may 3rd being provided. exception, or
Date or between the 0 deemed a
(1-5) Score

4.3.1.1 4.3.1 4.3
Subsection Section/ Requirement
load Ability Payment Purchase RFP
to the to Section: Respondent:
receive to Card
system bank
FTP
automatically file Description Requirement
data
from Respondent's
the
bank
and
Statement
,,
Comply Exception Comply/ Example of
of
Compliance
Standard Party ustorni Standard/C
3rd
with
loaded will request server The process expects their external The including , 3) 2 1 RFP
into then file and County that Advantage reconciled PCard to County :; iiii cause Failure Party provided Respondents reason exception Respondent
the make from related is after the the in surplus 0..,, : non-responsive. the to equipment Customization, is and to
system the the the transactions provider Advantage currently .:,i) ,.... respond a shall an each shall Specifications
file process responsible Advantage County form and Respondent's or or is Standard
for available PCard for will of a are (currently in a reconciles reverse . to being indicate alternative indicate
to then system every software. feature, requirement.
processing. to provider. receive maintaining upgrade. continue payment US PCard auctions. Ai-In:Vivi- proposal provided the must
Advantage The the to interfaced Bank). available :k to requirement requires feature be If compliance
a follow request. to The activity ! be by 3rd provided. exception, or
to County payment FTP CGI from —ri,.;:.,-, deemed may being
be this I a
(1-5) Score

4.3.1.4 4.3.1.3 4.3.1.2
Subsection Requirement
post Ability Ability Ability Ability RFP
payments) to to to to Section: Respondent:
manage create view handle
Reject payment uploaded reject
files from bank files Description Requirement
(accounting file file loaded Respondent's
by
the
strings bank
— Statement
Comply Comply Comply Comply xc eption Comply/ .. Example of
I of Comp
Standard Standard Standard Standard Party ustorn/ Stanclard/C iance
3rd with
string Rejected standard payment payment review provider Payment provider. request Authorized provider. file new document reviewed Advantage received Rejected .. cause 3) Failure Party 2) reason 1) RET
issues wili request and can can can and from non-responsive. the to Customization„ provided Respondents and exception Respondent
within documents Advantage be approval requests transactions users be be document the documents respond equipment a is an to Specifications
issued has in optionally are transmitted discarded corrected. PCard ( . Respondent's or is or Standard shall each shall
payment including disbursement the to been be interfaced loaded to able catalog including every to being indicate alternative indicate
requests chart PCard fully Advantage. subject from from view from from Optionally, where provider ,, proposal software. feature, the must requirement.
of approved Once to the the the the the a they remain payment to requirement provided requires feature be if compliance
received account processing. provider a a workflow PCard PCard payment PCard system rejected can on requests • be 3rd by provided. exception, or
via and be the .;;;,(,,ii, deemed may being
a ,t a
(1-5) Score

I
4.3.1.5 4.3.1.4.2 4.3.1.4.1
Subsection Section/ Requirement
Ability Ability file via Ability RFP
to to email to Section: Respondent:
edit notify
decrement reject the
the file
department Description Requirement
document
contract/Purchase user Respondent's
of
the
Order reject
Statement
Comply Comply Comply Exception Cornpiy/ Example of
of Com,
ustom/ p
Standard Standard Standard Party Stanciard/C lance
3rd
CGI provider. new document reviewed Advantage received Rejected be catalog. Request Users transmitted discarded corrected. document from cause 3) Party 2) 1) with R
will file transactions. developed In can the Failure provided Respondents reason exception Respondent P
work can be can and from from catalog PCard non-responsive. the to Customization, is and
with be document the documents to addition, documents manually from the Optionally, respond equipment a an to Specifications
the transmitted discarded corrected. PCard alert an on . e system a where provider i:vilte Respondent's to or or is Standard shall each shall
County catalog including users the review PCard and rejected they remain , H;( every software. being indicate alternative requirement. indicate
during from from Optionally, where provider to the infoAdvantage Advantage rejected provider. a can on proposal feature, the must
the the the a they remain payment rejected new file document be the to requirement provided requires feature be If compliance
PCard system rejected can on requests report document Payment can reviewed Advantage :,/ , be by 3rd provided. exception, or
Envision and be the could be can • ., deemed may being
a be and h. a
—
(1-5) Score

4.3.2.5 4.3.2.4 4.3.2.3 4.3.2.2 4.3.2.1 4.3.2 .
Section/ Requirement
second Ability Notification approvals Ability vouchers when Ability Ability Approval RFP
time to to first to to Section: Respondent:
reprocess have approver send approve process
message audit (2
a file of trail notification levels
that payment with approves to of Description Requirement
was time the second approval) Respondent's
rejected action stamp payment
for of approver
the Statement
Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Compliance
Standard Standard Standard Standard Standard ustom/ Standard/C
3rd with
corrected If a approval provider Advantage PCard levels Advantage interfaced Contract phase , i;:o/ .i , , 3) 2) 1) R :I)
PCard notifications of to i .',::t _ cause Failure Party provided Respondents reason exception Respondent
and file process. moves as provider. approval to ID determine , o , non-responsive. the to equipment Customization, is and to
fails the provides provides Advantage reference respond a shall an each shall Specifications
resubmitted. to load through Payment the for the the on potential i iii/5 .itiii )"; Respondent's to or or is Standard alternative
to the ability ability from the ,11 _ every software. being indicate requirement. indicate
Files Advantage workflow Request to payment to the payment options proposal provided feature, the must
that to send request define PCard to to requirement requires feature be If compliance
successfully it can review the out to up to provider. request include be by 3rd provided. exception, or
be and PCard email the 15 file a deemed may being
a
(1-5) Score

4.3.4 4.3.3.3 4.3.3.2 4.3.3.1 4.3.3 4.3.2.6
Subsection Section/ Requirement
Closing reporting Ability Ability EFT Ability Suspense Ability RFP
PO to to payment to to Section: Respondent:
with have create accept table populate
a all account a
p-card current ad-hoc minimum EFT
daily reporting summary Description Requirement
of
and for 16 Respondent's
monthly reject characters
table for
Statement
Comply Comply Comply Comply Exception Comply/ Example of
of
ustom/ Compliance
Standard Standard Standard Standard Party Standard/C
3rd
with
and PCard for any vendor's Advantage PCard discarded corrected. document payment business load to f cause 3) Party 2) 1) RFP
standard infoAdvantage that infoAdvantage .?) hp ..... Failure provided Respondents reason exception Respondent
reject payment account provider. and a catalog requests rules Advantage .- _ _ . non-responsive. the to equipment Customization, is and to
reports. can in can to provides new Optionally, for . respond a shall an each shall Specificatons
be requests be receive the file where will payment will toy.: Respondent's to or or is Standard alternative
used Advantage. used ability can the they remain be r• every software. being indicate requirement. indicate
to create interfaced to create payment to be payment can in requests. subjected proposal feature, the must
from ad via configure interfaced be the Any to to requirement provided requires feature be if compliance
various the hoc EFT. request reviewed Advantage the , be by 3rd provided. exception, or
ad reports any from can rejected standard cificaitoi! deemed may being
hoc the be and a
(1-5) Score

i_. 44.1.3.1 4.4.1.3 4.4.1.2.1 4.4.1.2 4.4.1.1 4.4.1 4.4 4.3.4.1
- Subsection Section/ Requirement
Ability Ability Ability Ability Ability Article Supplier Ability RFP
to to to to to 3 to Section: Respondent:
submit bid submit bid bid Selection close
and between and between under PO a _
view view $5K with
at $15-50K a Description Requirement
least electronic $5-14,999.99K p-card
5 Respondent's
e-quotes quotes
Statement
Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of
Compliance
Standard Standard Standard Standard Standard Standard Party ustorn/ Standard/C
3rd
1 with
interfaced Contract phase CGI PCard final contract. the The 3) 2) 1) RFP
to will reference ability Advantage _ non-respon . cause Failure Party provided Respondents reason exception Respondent
to ID work provider. The to _ , the to Customization, is and
Advantage reference determine with is referenced reference sive. . . respond equipment a shall an each to shall Specifications
on the made a payment Respondent's to or is or Standard alternative
from the potential County the on PO request every software. being indicate requirement. indicate
the payment options during be will purchase , proposal provided feature, the must
PCard to the payment closed order process to requirement requires feature be If compliance
provider. request include Envision the to or includes be 3rd by being provided. exception, or
file a when deemed may
a : a
(1-5) Score

4.4.2.3.5 4.4.2.3.4 4.4.2.3.3 4.4.2.3.2 4.4.2.3.1 4.4.2.3 4.4.2.2.1 4.4.2.2 4.4.2.1.1 4.4.2. 4.4.2
Subsection Section/ Requirement
..
registration Ability Ability suppliers Ability No limit <=$100K Simplified Ability "limited Ability <= Article RFP Respondent:
for to to of to $5K-$19,477.48 to $4,999.99 5 Section:
to vendors submit send suppliers submit scope" submit
receive to and bid to Construction and (need and
select view all view to view Description Requirement
notifications written approved at east modify at least
to commodity and 3 $ 1 Respondent's
quotes listed quotes annually) quote
maintain codes I
at
- Statement
,
Comply Comply Comply Comply Comply Comply Comply Exception Comply! Example of
, of
Standard Standard Standard Standard Standard Standard Standard Party ustom/ Standard/C CorapNance
3rd
quotes receive Service. Vendors on a that 3) 2) 1) with RR)
in are Advantage cause Failure Party provided Respondents reason exception Respondent
the offline Optionally, can solicitation registered non-responsive. the to equipment Customization, is and to
system. quotes create or to for provides ..............._..... Respondent's respond or a shall an each shall Specifications
and the online a the the . to or is Standard alternative indicate
County quotes specific ability every software. being feature, indicate requirement.
manually may via list of commodity(s) to notify proposai provided the must be if compliance
enter choose Vendor vendors. all to be requirement by requires feature
these to Self specified vendors deemed may 3rd being provided. exception, or
a
(1-5) Score

4.4.2.3.11 4.4.2.3.10 4.4.2.3.9 4.4.2.3.8 4.4.2.3.7 4.4.2.3.6
Subsection Section/ Requirement
Management Ability Ability changes Ability Ability Ability Ability records RFP Respondent:
to to to to to to for Section:
interface assign commodity update restrict vendors
with contracts update/notifications commodity vendors to
System codes maintain Description Requirement
for contracts codes own Respondent's
Award dynamically records
based
on Statement
Comply Comply Exception Comply Comply Comply Exception Comply/ Example of
of
ustorn/ . Compliance
Standard Standard Custom Standard Standard Standard Party Standard/C ction
3rci 2 with
systems However, processes various Advantage is that Advantage as such automatically However, maintain Advantage qualified Advantage cause Failure 3) Party 2) reason 1) RFP
not are external assigned purchase the vendor non-responsive. the to Customizati is provided Respondents and exception Respondent
pre-defined including provides a to provides propagate changes commodity provides list provides respond equipment on, a shall an each to shall Specifications
delivered systems the the orders the to the a on the re.1(1 Respondent's to or is or Standard alternative
with interfaces debarment to ability procurement. ability and to file ability ability , (.1 every software. being indicate requirement. indicate
with support to to contracts. existing commodity within to solicitation. to Icnt proposal provided feature, the must
Advantage. tracking. interface change file update define to requirement requires feature be If compliance
external different with the documents not to Advantage. and pre- a be 3rd by being provided. exception, or
buyer _ deemed may a
(1-5) Score

4.4.2.3.13 4.4.2.3.12
Subsection Section/ Requirement
,
Ability (monthly, Ability RFP
for to Section: Respondent:
finance hi-monthly, create __ _
to report
validate etc.) of Description
non-valid
Respondent's
vendors
Statement
Comply Comply Exception Corn Example of
of
Compliance
Standard Standard Party ustom/ Standard/C
3rd
with
award account the review also process process external this debarred or A ,. 3) 2) 1) RFP
vendor registrations Advantage registrations Advantage Business more debarment 'debarred' vendor ......... cause Failure Party provided reason exception
(e.g. must and provides that that Business (", 01! ,... non-responsive. the to Customization, Respondents and Respondent
purchase be account approve the against can provides against can provides debarment Type vendors list. when a account .. equipment is a an to Specifications
active is a ability the be used an the be used an list. as a and Types Another match status i'CI.11:li ,' .. .._. Respondent's respond or or is Standard shall each shall
order in made vendor's for IRS to IRS IRS to IRS match associate to is can ., I to every being indicate alternative indicate
or order to active. an system. validate TIN/Name system. validate TIN/Name is identify approach found : proposal software. feature, the must requirement.
contract). receive A registration authorized found each is to on an potentially 'ilVi? to requirement provided feature be If compliance
an vendor Advantage vendor match vendor match on an vendor externally create be be by requires provided. exception, or
before user to with external set to deemed may 3rd being
one a
(1-5) Score

, , ,
4.4.7 4.4.6 4.4.5 4.4.4 4.4.3
4.4.2.3.14
Subsection Section/ Requirement
Provide issues Customer/ Ability Ability date Ability (not Ability RFP
(live to to last of to just to Section: Respondent:
vendor/end chat, user see create activity create finance collect
1 service viewed/downloaded/responded who data all
user -800 has Notification vendor
-help) line aging procurement Description Requirement
training for of requirements)
for vendor to failed report data Respondent's
areas all service solicitations emails based required
on
Statement
Comply Exception Exception Exception Comply comply Exception Comply/ Example of
of Comp
3 rd 3'd ustorn/
Standard Party Custom Party Standard Standard Party Stanclard/C Hance
3rd
population typically address CGI help Vendor currently have Advantage external Email aging electronic contract. Advantage Reason cause 3) Party 2) 1) RFP with
offers desk downloaded to reports. infoAdvantage procurement for Failure Customization, provided Respondents reason exception Respondent
of provided internal standard or support a track responded notification Additional exoiiii non-responsive. the to equipment is and to
vendors to users. other is vendors to provides Advantage. can attachments. and provides Respondent's respond or a shall an each shall Specifications
and support typically solicitation. a the failures be details finance the re,ii:in , to or is Standard alternative
that vendors Formal that solicitation ability are to used can ability moil ti, every software. being indicate requirement. indicate
interact due customized staff. provided have to typically be related to /native proposal feature, the must
with the to training by viewed but track facilitate collect to to requirement provided feature be lf compliance
a large not is training the or not does vendors handled various captured information various be 3rd by requires provided. exception, or
public to client's via on deemed may being
tha t a a
(1-5) Score

4.5.7 4.5.6 4.5.5 4.5.4 4.5.3 I 4.5.2 4.5.1 4.5
Subsection Section/ Requirement
Ability Minimum outs Ability (users) Notification Ability contract Ability elements Ability Purchase RFP Respondent:
to 7 to requisition/contract/P0 to tie PO to to Section:
configure digits connect when distinguish track, Order
for to commodity notify
changes commodity vendor commodity codes between and Description Requirement
throughout catalogs code to contract report on Respondent's
codes and is on all
and data
contract punch- contract non-
Statement
Comply Comply Comply Comply Comply Comply Comply Exception Comply/ Example of
of Com
•
Standard Standard Standard Standard Standard Standard Standard Party ustorn/ Standard/C ,Jiance
3rd
out report can CGI sector 3) 2) 1) with
Advantage catalogs. Advantage on Advantage be outreach can cause Failure Party provided reason exception RIT
virtually accessed program work organization non-responsive. the to equipment Customization, is Respondents and to Respondent
provides supports aii provides in a with Respondent's respond or a shall an each shall Specifications
the both data the including the such to or is Standard alternative indicate
ability locally ability self-service County as the every software. being indicate requirement.
to elements. to certain to proposal provided feature, the must
change hosted track, fashion. define County. to requirement requires feature be :IF compliance
various and notify materials a vendor However, be by 3rd being provided. exception, or
punch- and that deemed may
a
(1-5) Score

4.5.9 4.5.8
Subsection Section/ Requirement
location Have throughout Ability lifecycle RFP
product to Section: Respondent:
(rvICSO) entire workflow
as number, auto-populate
well process
as data Description Requirement
commodity
manage elements Respondent's
code
inventory and
Statement
Comply Comply Exception Comply/ Example of
of
ustom/ Compliance
Standard Standard Party Stanclard/C
3rd
with
the Note: inventory also line on part identifiers Advantage and transaction information information Advantage submitted. created Changes business cause 3) Party 2) reason 1) RFP
current Inventory specify a number, potential or in are rules non-responsive. the Failure to Customization, provided Respondents exception Respondent
scope replenishment the purchase and such as supports keying chain from in a progress then respond equipment is a and an to Specifications
of appropriate order. supplier the in order one document automatically applied through Respondent's or or is Standard shall each shah
work. Management orders. in part commodity ability errors. to document infers documents as online • i to every software. being indicate alternative requirement. indicate
is not warehouse addition, number code, to minimize to and carries new proposal provided feature, the must
a include the relevant are documents configuration. to requirement requires feature be if compliance
included for user for manufacturer data next forward validated be by 3rd provided. exception, or
in can each various entry in a or are deemed may being
a
(1-5) Score

4.5.12 4.5.11 4.5.10
Section/ Requirement
Ability Ability notification Min/Max RFP Respondent:
to for Section:
search error and
El. handling automatically
()lean Description Requirement
(notification) ication) i generate Respondent's
re-order ..
Statement
Comply Comply Comply Exception Comply/ Example of
of
ustorn/ Compliance
Standard Standard Standard Standard/C
3rd
with
and purchase Advantage validated alerts Advantage the Note: support inventory minimum Advantage Master and Advantage cause 3) Party 2) 1) REP
reports or user a current inventory maximum non-responsive. the Failure Customization, provided Respondents reason exception Respondent
can order provides to provides scope inventory as item and also Agreement. provides to equipment a is an and to
be submitted. any of well maximum provides order Respondent's respond or shall each shall Specifications
performed information. various issues standard work. Management replenishment. as amounts the to or is Standard alternative indicate
each re-order issue the ability every software. being indicate requirement.
using Additional online time error not is ability for to ,-- proposal provided feature, the must
inquiries a handling parameters quantities to releases define to requirement requires feature be if compliance
infoAdvantage. queries to document included an for define against minimum (. , !;;• v be 3rd by being provided. exception, or
view is and in to , i, . deemed may a
a !
(1-5) Score

13082 EXHIBIT C
OFFICE OF PROCUREMENT SERVICES CONTRACTOR TRAVEL AND PER DIEM POLICY
1.0 All contract-related travel plans and arrangements shall follow the County Contractor Travel
Policy. All travel expenses are included in the price of Services in Exhibit A and the County will
not be billed for any additional Travel expenses during the Project. Travel will be billed separately
for Services after implementation (Go-live) as specified in Exhibit A-1.
2.0 Lodging, per diem and incidental expenses incurred in performance of Maricopa County/Special
District (County) contracts shall be reimbursed based on current U.S. General Services
Administration (GSA) domestic per diem rates for Phoenix, Arizona. Contractors must access the
following internet site to determine rates (no exceptions): :
2.1 Additional incidental expenses (i.e., telephone, fax, internet and copying charges) shall
not be reimbursed. They should be included in the contractor's hourly rate as an overhead
charge.
2.2 The County will not (under no circumstances) reimburse for Contractor guest lodging,
per diem or incidentals.
3.0 Commercial air travel shall be reimbursed as follows:
3.1 Coach airfare will be reimbursed by the County. Business class airfare may be allowed
only when preapproved in writing by the County Contract Administrator as a result of the
business need of the County when there is no lower fare available.
3.2 The lowest direct flight airfare rate from the Contractors assigned duty post (pre-defined
at the time of contract signing) will be reimbursed. Under no circumstances will the
County reimburse for airfares related to transportation to or from an alternate site.
3.3 The County will not (under no circumstances) reimburse for Contractor guest commercial
air travel.
4.0 Rental vehicles may only be used if such use would result in an overall reduction in the total cost
of the trip, not for the personal convenience of the traveler. Multiple vehicles for the same set of
travelers for the same travel period will not be permitted without prior written approval by the
County Contract Administrator.
4.1 Purchase of comprehensive and collision liability insurance shall be at the expense of the
contractor. The County will not reimburse contractor if the contractor chooses to
purchase these coverage.
Rental vehicles are restricted to sub-compact, compact or mid-size sedans unless a larger
vehicle is necessary for cost efficiency due to the number of travelers. (NOTE:
contractors shall obtain pre-approval in writing from the County Contract Administrator
prior to rental of a larger vehicle.)
4.3 County will reimburse for parking expenses if free, public parking is not available within
a reasonable distance of the place of County business. All opportunities must be
exhausted prior to securing parking that incurs costs for the County. Opportunities to be
reviewed are the DASH; shuttles, etc. that can transport the contractor to and from
County buildings with minimal costs.
4.4 County will reimburse for the lowest rate, long-term uncovered (e.g. covered or enclosed
parking will not be reimbursed) airport parking only if it is less expensive than shuttle
service to and from the airport.

13082 EXHIBIT C
OFFICE OF PROCUREMENT SERVICES CONTRACTOR TRAVEL AND P R DIEM POLICY
4.5 The County will not (under no circumstances) reimburse the Contractor for guest vehicle
rental(s) or other any transportation costs.
5.0 Contractor is responsible for all costs not directly related to the travel except those that have been
pre-approved by the County Contract Administrator. These costs include (but not limited to) the
following: in-room movies, valet service, valet parking, laundry service, costs associated with
storing luggage at a hotel, fuel costs associated with non-County activities, tips that exceed the per
diem allowance, health club fees, and entertainment costs. Claims for unauthorized travel
expenses will not be honored and are not reimbursable.
6.0 Travel and per diem expenses shall be capped at 5% of project price unless otherwise specified in
individual contracts