190283-CONTRACT.PDF

CONTRACT PURSUANT TO RFP
SERIAL 190283-RFP
This Contract is entered into this 11th day of December 2019 by and between Maricopa County (“County”), a
political subdivision of the State of Arizona, and Gartner, Inc., an Arizona corporation (“Contractor”) for the
purchase of Infrastructure/Cloud Readiness Assessment and Future State professional services.
1.0 CONTRACT TERM:
1.1 This Contract is for a term of one (1) year, beginning on the 11th day of December 2019 and
ending the 30th day of November 2020.
1.2 The County may, at its option and with the agreement of the Contractor, renew the term of this
Contract for additional terms up to a maximum of four (4) additional 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 term at least sixty (60) calendar days prior to the expiration of the original contract term,
or any additional term thereafter.
1.3 CONTRACT COMPLETION:
The Contractor shall make all reasonable efforts for an orderly transition of its duties and
responsibilities to another provider and/or to the County. This may include but is not limited to
the preparation of a transition plan and cooperation with the County or other providers in the
transition. The transition includes the transfer of all records, and other data in the possession,
custody or control of Contractor required to be provided to the County either by the terms of this
agreement or as a matter of law. The provisions of this clause shall survive the expiration or
termination of this agreement.
2.0 PRICE ADJUSTMENTS:
Any requests for reasonable price adjustments may be submitted at any time during Contract performance,
however not less than sixty (60) calendar days prior to the Contract expiration. Requests for adjustment in
cost of labor and/or materials must be supported by appropriate documentation. The reasonableness of the
request will be determined by comparing the request with the Consumer Price Index, by performing a
market survey or other method agreed by the County and Contractor that reasonably reflects the actual
increase in cost. If County and Contractor agree to the adjusted price terms, they shall memorialize such
change via Contract Amendment pursuant to Article 6.15 AMENDMENTS. The new change shall not be
in effect until the date stipulated on the Contract.
3.0 PAYMENTS:
3.1 As consideration for performance of the duties described herein, County shall pay Contractor the
sum(s) stated in Exhibit “A.”
3.2 Payment shall be made upon the County’s receipt of a properly completed invoice.

SERIAL 190283-RFP
3.3 INVOICES:
3.3.1 The Contractor shall submit one (1) legible copy of their detailed invoice before
payment(s) will be made. Incomplete invoices will not be processed. At a minimum, the
invoice must provide the following information:
• Company name, address and contact
• County bill-to name and contact information
• Contract Serial Number
• County purchase order number
• Project name and/or number
• Invoice number and date
• Payment terms
• Quantity
• Contract Item number(s)
• Description of Purchase (product or services)
• Pricing per unit of purchase
• Extended price
• Total Amount Due
3.3.2 Problems regarding billing or invoicing shall be directed to the Department as listed on
the Purchase Order.
3.3.3 Payment shall only 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 Contract Award the Contractor shall complete the Vendor Registration
Form located on the County Department of Finance Vendor Registration Web Site
(http://www.maricopa.gov/922/Vendors).
3.3.4 Discounts offered in the contract shall be calculated based on the date a properly
completed invoice is received by the County.
3.3.5 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.4 APPLICABLE TAXES:
3.4.1 Payment of Taxes: The Contractor shall pay all applicable taxes. With respect to any
installation labor on items that are not attached to real property performed by Contractor
under the terms of this Contract, the installation labor cost and the gross receipts for
materials provided shall be listed separately on the Contractor’s invoices.
3.4.2 State and Local Transaction Privilege Taxes: To the extent any State and local transaction
privilege taxes apply to sales made under the terms of this Contract it is the responsibility
of the seller to collect and remit all applicable taxes to the proper taxing jurisdiction of
authority.
3.4.3 Tax Indemnification: Contractor and all subcontractors shall pay all Federal, State, and
local taxes applicable to its operation and any persons employed by the Contractor.
Contractor shall and require all subcontractors to hold Maricopa County harmless from
any responsibility for taxes, damages and interest, if applicable, contributions required
under Federal, and/or State and local laws and regulations, and any other costs including;
transaction privilege taxes, unemployment compensation insurance, Social Security, and
Worker’s Compensation.

SERIAL 190283-RFP
3.5 TAX (SERVICES):
No tax shall be invoiced or paid against Contractor’s labor. It is the responsibility of the
Contractor to determine any and all applicable taxes.
3.6 TAX (COMMODITIES):
Tax shall not be invoiced against Contractor’s labor. It is the responsibility of the Contractor to
determine any and all applicable taxes.
3.7 STRATEGIC ALLIANCE for VOLUME EXPENDITURES ($AVE):
The County is a member of the $AVE cooperative purchasing group. $AVE includes the State of
Arizona, many Phoenix metropolitan area municipalities, and many K-12 unified school districts.
Under the $AVE Cooperative Purchasing Agreement, and with the concurrence of the successful
Respondent under this solicitation, a member of $AVE may access a contract resulting from a
solicitation issued by the County.
3.8 INTERGOVERNMENTAL COOPERATIVE PURCHASING AGREEMENTS (ICPA’s):
County currently holds ICPA’s with numerous governmental entities. These agreements allow
those entities, with the approval of the Contractor, to purchase their requirements under the terms
and conditions of the County Contract. It is the responsibility of the non-County government
entity to perform its own due diligence on the acceptability of the Contract under its procurement
rules, processes and procedures.
4.0 AVAILABILITY OF FUNDS:
4.1 The provisions of this Contract relating to payment for services shall become effective when funds
assigned for the purpose of compensating the Contractor as herein provided are actually available
to County for disbursement. The County shall be the sole judge and authority in determining the
availability of funds under this Contract. County shall keep the Contractor fully informed as to the
availability of funds.
4.2 In the event of termination, County shall be liable for payment only for services rendered and
costs incurred prior to the effective date of the termination, provided that such services are
performed in accordance with the provisions of this Contract. County shall give written notice of
the effective date of any suspension, amendment, or termination under this Section, at least thirty
(30) days in advance.
5.0 DUTIES:
5.1 The Contractor shall perform all duties stated in Exhibit “B”, or as otherwise directed in writing
by the Procurement Officer.
5.2 During the Contract term, County may 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.
5.3 In connection with Contractor’s performance of the work under this Contract, County shall
perform those tasks and fulfill those responsibilities specified in any applicable SOW (“County
Responsibilities”). County understands that Contractor’s performance is dependent on County’s
timely and effective performance of the County Responsibilities and timely decisions and
approvals by County. Unless a SOW includes specific acceptance procedure, all services and
Deliverables shall be deemed accepted within thirty (30) days after delivery unless County has
provided Contractor with written notice specifically identifying any deficiency or failure of the
work or Deliverable to materially comply with the specifications or acceptance criteria.
Contractor shall rely on all decisions and approvals by County in connection with the work or
Deliverables.

SERIAL 190283-RFP
6.0 TERMS AND CONDITIONS:
6.1 INDEMNIFICATION:
To the fullest extent permitted by law, and to the extent that claims, damages, losses or expenses
are not covered and paid by insurance purchased by the Contractor, the Contractor shall defend
indemnify and hold harmless the County (as Owner), its agents, representatives, agents, officers,
directors, officials, and employees from and against third-party claims, damages, losses, and
expenses (including, but not limited to attorneys' fees, court costs, expert witness fees, and the
costs and attorneys' fees for appellate proceedings) attributable to the negligence or willful
misconduct of the Contractor during the performance of this Contract.
Contractor's duty to defend, indemnify, and hold harmless the County, its agents, representatives,
agents, officers, directors, officials, and employees shall only arise in connection with any third-
party claim, damage, loss, or expense that is attributable to bodily injury, sickness, disease, death
or injury to, impairment of, or destruction of tangible property, including loss of use resulting
there from, caused by negligence or willful misconduct in the performance of this Contract of the
Contractor, a subcontractor, any one directly or indirectly employed by them, or anyone for whose
acts they may be liable.
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 may, to the extent permitted by law be apportioned to the extent
that any claim for indemnification hereunder is attributable in whole or in part to the negligence or
misconduct of the County, its agents, representatives, officers, officials and/or employees.
6.2 INSURANCE:
6.2.1 Contractor, at Contractor’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++. 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
policies and forms must be acceptable to County.
6.2.2 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.
6.2.3 Contractor’s insurance shall be primary insurance as respects County, and any insurance
or self-insurance maintained by County shall not contribute to it.
6.2.4 Any failure to comply with the claim reporting provisions of the insurance policies or any
breach of an insurance policy warranty shall not affect the County’s right to coverage
afforded under the insurance policies.
6.2.5 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. Contractor 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.

SERIAL 190283-RFP
6.2.6 The insurance policies required by this Contract, except Workers’ Compensation and
Errors and Omissions, shall name County, its agents, representatives, officers, directors,
officials and employees as Additional Insureds.
6.2.7 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.
6.2.8 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, $4,000,000
Products/Completed Operations Aggregate, and $4,000,000 General Aggregate Limit.
The policy shall include coverage for premises liability, bodily injury, broad form
property damage, personal injury, products and completed operations and blanket
contractual coverage, and shall not contain any provisions which would serve to limit
third party action over claims. There shall be no endorsement or modifications of the
CGL limiting the scope of coverage for liability arising from explosion, collapse, or
underground property damage.
6.2.9 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 or use or maintenance of the premises under this Contract.
6.2.10 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 $1,000,000
disease policy limit.
Contractor, its contractors and its subcontractors waive all rights against Contract and its
agents, officers, directors and employees for recovery of damages to the extent these
damages are covered by the Workers’ Compensation and Employer’s Liability or
commercial umbrella liability insurance obtained by Contractor, its contractors and its
subcontractors pursuant to this Contract.
6.2.11 Cyber:
Policy Limit:
6.2.11.1 The policy shall be issued with minimum limits of $1,000,000.
6.2.11.2 The policy shall include coverage for all directors, officers, agents and
employees of the Contractor.
6.2.11.3 The policy shall include coverage for third party fidelity.
6.2.11.4 The policy shall include coverage for theft.
6.2.11.5 The policy shall contain no requirement for arrest and conviction.
6.2.11.6 The policy shall cover loss outside the premises of the Named Insured.
6.2.11.7 The policy shall endorse (Blanket Endorsements are not acceptable) the
Department as Loss Payee as our interest may appear.

SERIAL 190283-RFP
6.2.12 Errors and Omissions (Professional Liability) Insurance:
Errors and Omissions (Professional Liability) insurance and, if necessary, Commercial
Umbrella insurance, which will insure and provide coverage for errors or omissions or
professional liability of the Contractor, with limits of no less than $2,000,000 for each
claim.
6.2.13 Certificates of Insurance:
6.2.13.1 Prior to Contract award, Contractor shall furnish the County with valid and
complete certificates of insurance, or formal endorsements 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 identify this contract number and title.
6.2.13.2 In the event any insurance policy(ies) required by this Contract is(are) written
on a claim made basis, coverage shall extend for two years past completion
and acceptance of Contractor’s work or services and as evidenced by annual
Certificates of Insurance.
6.2.13.3 If a policy does expire during the life of the Contract, a renewal certificate
must be sent to County fifteen (15) calendar days prior to the expiration date.
6.2.14 Cancellation and Expiration Notice:
Applicable to all insurance policies required within the Insurance Requirements of this
Contract, Contractor’s insurance shall not be permitted to expire, be suspended, be
canceled, or be materially changed for any reason without thirty (30) days prior written
notice to Maricopa County. Contractor must provide to Maricopa County, within two (2)
business days of receipt, if they receive notice of a policy that has been or will be
suspended, canceled, materially changed for any reason, has expired, or will be expiring.
Such notice shall be sent directly to Maricopa County Office of Procurement Services
and shall be mailed, or hand delivered to 160 South 4th Ave., Phoenix, AZ 85003, or
emailed to the Procurement Officer noted in the solicitation.
6.3 FORCE MAJEURE:
6.3.1 Neither party shall be liable for failure of performance, nor incur any liability to the other
party on account of any loss or damage resulting from any delay or failure to perform all
or any part of this Contract if such delay or failure is caused by events, occurrences, or
causes beyond the reasonable control and without negligence of the parties. Such events,
occurrences, or causes will include Acts of God/Nature (including fire, flood, earthquake,
storm, hurricane or other natural disaster), war, invasion, act of foreign enemies,
hostilities (whether war is declared or not), civil war, riots, rebellion, revolution,
insurrection, military or usurped power or confiscation, terrorist activities,
nationalization, government sanction, lockout, blockage, embargo, labor dispute, strike,
interruption or failure of electricity or telecommunication service.
6.3.2 Each party, as applicable, shall give the other party notice of its inability to perform and
particulars in reasonable detail of the cause of the inability. Each party must use best
efforts to remedy the situation and remove, as soon as practicable, the cause of its
inability to perform or comply.
6.3.3 The party asserting Force Majeure as a cause for non-performance shall have the burden
of proving that reasonable steps were taken to minimize delay or damages caused by
foreseeable events, that all non-excused obligations were substantially fulfilled, and that
the other party was timely notified of the likelihood or actual occurrence which would
justify such an assertion, so that other prudent precautions could be contemplated.

SERIAL 190283-RFP
6.4 WARRANTY OF SERVICES:
6.4.1 The Contractor warrants that all Deliverables and services provided hereunder will
conform in all material respects to the specifications or requirements made a part hereof
by any applicable SOW for a period thirty (30) days after acceptance by the County.
County’s acceptance of services or goods provided by the Contractor shall not relieve the
Contractor from its obligations under this warranty. Contractor agrees to reperform
services or Deliverables not in compliance with this warranty provided the County has
provided written notice of such non-compliance within thirty (30) days of delivery.
OTHERWISE, ALL SERVICES ARE PROVIDED ON AN “AS IS” BASIS.
CONTRACTOR DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. THE INFORMATION IN THE DELIVERABLES HAS
BEEN OBTAINED FROM SOURCES THAT CONTRACTOR BELIEVES TO BE
RELIABLE. ALL DELIVERABLES SPEAK AS OF THE DATE OF DELIVERY TO
THE COUNTY. CONTRACTOR HAS NO OBLIGATION TO ADVISE COUNTY OF
ANY CHANGE IN THE INFORMATION OR VIEWS CONTAINED IN THE
DELIVERABLES.
6.4.2 In the event that Contractor is unable to provide prompt correction of any services failing
to meet the Contractor's warranty herein, Contractor shall refund the fees received for
such services or Deliverables and may require County to return any Deliverable subject
to this provision. Services corrected by the Contractor shall be subject to all the
provisions of this Contract in the manner and to the same extent as services originally
furnished hereunder.
6.5 ORDERING AUTHORITY:
Any request for purchase shall be accompanied by a valid purchase order, issued by Office of
Procurement Services, a Purchase Order issued by the using Department or direction by a
Certified Agency Procurement Aid (CAPA) with a Purchase Card for payment.
6.6 PURCHASE ORDERS:
County reserves the right to cancel Purchase Orders within a reasonable period of time after
issuance. Should a Purchase Order be canceled, the County agrees to reimburse the Contractor for
actual and documentable costs incurred by the Contractor in response to the Purchase Order. The
County will not reimburse the Contractor for any costs incurred after receipt of County notice of
cancellation, or for lost profits, shipment of product prior to issuance of Purchase Order, etc.
6.7 BACKGROUND CHECK:
Contractors need to be aware that there may be multiple background checks (Sheriff’s Office,
County Attorney's Office, Courts as well as Maricopa County general government) to determine if
the respondent is acceptable to do business with the County. This applies to (but is not limited to)
the Contractor, subcontractors and employees.
6.8 SUSPENSION OF WORK:
The Procurement Officer may order the Contractor, in writing, to suspend, delay, or interrupt all or
any part of the work of this contract for the period of time that the Procurement Officer determines
appropriate for the convenience of the County. No adjustment shall be made under this clause for
any suspension, delay, or interruption to the extent that performance would have been so
suspended, delayed, or interrupted by any other cause, including the fault or negligence of the
Contractor. No request for adjustment under this clause shall be granted unless the claim, in an

SERIAL 190283-RFP
amount stated, is asserted in writing as soon as practicable after the termination of the suspension,
delay, or interruption, but not later than the date of final payment under the Contract.
6.9 STOP WORK ORDER:
The Procurement Officer may, at any time, by written order to the Contractor, require the
Contractor to stop all, or any part, of the work called for by this contract for a period of ninety (90)
calendar days after the order is delivered to the Contractor, and for any further period to which the
parties may agree. The order shall be specifically identified as a stop work order issued under this
clause. Upon receipt of the order, the Contractor shall immediately comply with its terms and take
all reasonable steps to minimize the incurrence of costs allocable to the work covered by the order
during the period of work stoppage. Within a period of 90 calendar days after a stop-work is
delivered to the Contractor, or within any extension of that period to which the parties shall have
agreed, the Procurement Officer shall either:
6.9.1 Cancel the stop work order; or
6.9.2 Terminate the work covered by the order as provided in the Default, or the Termination
for Convenience clause of this Contract.
6.9.3 The Procurement Officer may make an equitable adjustment in the delivery schedule
and/or Contract price, or otherwise, and the Contract shall be modified, in writing,
accordingly, if the Contractor demonstrates that the stop work order resulted in an
increase in costs to the Contractor.
6.10 TERMINATION FOR CONVENIENCE:
Maricopa County may terminate the Contract for convenience by providing sixty (60) calendar
days advance notice to the Contractor.
6.11 TERMINATION FOR DEFAULT:
The County may, by written notice of default to the Contractor, terminate this Contract in whole
or in part if the Contractor fails to:
6.11.1 Deliver the supplies or to perform the services within the time specified in this Contract
or any extension;
6.11.2 Make progress, so as to endanger performance of this Contract; or
6.11.3 Perform any of the other provisions of this Contract.
The County’s right to terminate this contract under these subparagraphs may be exercised if the
defaulting party does not cure such failure within thirty (30) business days (or more if authorized
in writing by the non-defaulting party) after receipt of the notice from the non-defaulting party
specifying the failure.
6.12 STATUTORY RIGHT OF CANCELLATION FOR CONFLICT OF INTEREST:
Notice is given that pursuant to A.R.S. § 38-511 the County may cancel any 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.

SERIAL 190283-RFP
6.13 CONTRACTOR LICENSE REQUIREMENT:
The Contractor shall procure all permits, insurance, licenses and pay the charges and fees
necessary and incidental to the lawful conduct of his/her business, and as necessary complete any
required certification requirements, required by any and all governmental or non-governmental
entities as mandated to maintain compliance with and in good standing for all permits and/or
licenses. The Contractor shall keep fully informed of existing and future trade or industry
requirements, Federal, State and Local laws, ordinances, and regulations which in any manner
affect the fulfillment of a Contract and shall comply with the same. Contractor shall immediately
notify both Office of Procurement Services and the Department of any and all changes concerning
permits, insurance or licenses.
6.14 SUBCONTRACTING:
6.14.1 The Contractor may not assign to another contractor or subcontract to another party for
performance of the terms and conditions hereof without the written consent of the
County. All correspondence authorizing subcontracting must reference the Contract
Number and identify the job project.
6.14.2 The subcontractor’s rate for the job shall not exceed that of the Prime Contractor’s rate,
as bid in the pricing section, unless the Prime Contractor is willing to absorb any higher
rates, or the County has approved the increase. The subcontractor’s invoice shall be
invoiced directly to the Prime Contractor, who in turn shall pass-through the costs to the
County, without mark-up. A copy of the subcontractor’s invoice must accompany the
Prime Contractor’s invoice.
6.15 AMENDMENTS:
All amendments to this Contract shall be in writing and approved/signed by both parties. Maricopa
County Office of Procurement Services shall be responsible for approving all amendments for
Maricopa County.
6.16 ADDITIONS/DELETIONS OF REQUIREMENTS:
The County reserves the right to add and/or delete materials, services or Deliverables to or from
the Contract. If materials, services or Deliverables are added or deleted, payment to the
Contractor will be increased or reduced proportionately, to the amount of service reduced in
accordance with the bid price. Any such additions or deletions shall be subject to clause 6.25
Amendments. The Contractor shall have the opportunity to provide the County with additional
information and support for any costs incurred as a result of such addition or deletion.
6.17 WAIVER:
The failure by either party to require performance of any of the terms and conditions, warranties,
requirement or provisions of this Contract shall not constitute a waiver of any such provision at a
future date.
6.18 VALIDITY:
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 the Contract.
6.19 SEVERABILITY:
The removal, 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.

SERIAL 190283-RFP
6.20 RIGHTS IN DATA:
Subject to payment of fees in accordance with this Contract, Contractor grants to County
ownership of any Deliverable originally created for and submitted to County. Contractor shall
retain sole and exclusive ownership of the Contractor tools, methodologies, questionnaires,
responses, and proprietary research and data generated in the course of performing the consulting
services, together with all intellectual property rights therein. (collectively, the
“Contractor/Gartner Materials”). Contractor grants to County a perpetual, non-exclusive, royalty
free license to use and to disclose the Deliverables identified in a Statement of Work, subject to
the limitations set forth below.
Nothing contained in this Contract shall preclude Contractor from rendering services to others or
developing work products that are competitive with, or functionally comparable to, the consulting
Services performed. Contractor shall not be restricted in its use of ideas, concepts, know how, data
and techniques acquired or learned in the course of performing the consulting Services, provided
that Contractor shall not use or disclose any of County’s Confidential Information.
County shall retain its rights in any proprietary material that County supplies to Contractor. If
County provides Contractor with materials owned or controlled by County or with use of, or
access to, such materials, County grants to Contractor all rights and licenses that are necessary
for Contractor to fulfill its obligations under each Statement of Work for consulting services.
County understands and agrees the Services and Deliverables are created and intended for
County’s governmental purposes only and therefore, unless the Deliverable is a Request for
Proposal (RFP) or similar document intended to be distributed by County as specified in the
applicable Statement of Work, County shall not make the Deliverables available, in whole or in
part, to anyone outside of County, or quote excerpts from the Deliverables to the public, without
the prior written consent of Contractor. Notwithstanding the foregoing, County may share the
Deliverables with (i) its outside auditors and/or accountants, (ii) third parties who have signed
appropriate confidentiality agreements with County who are engaged by County to review or
implement suggestions or to further research the issues contained in the Deliverables, (iii) by law
or governmental or regulatory bodies as required by law, and (iv) in the event County is required
to disclose such information pursuant to the requirements of any governmental authority with
jurisdiction, County shall first give notice to Contractor so that Contractor may seek an
appropriate protective order or other relief and/or waive County’s obligation of confidence.
6.21 NON-DISCRIMINATION:
Contractor agrees to comply with all provisions and requirements of Arizona Executive Order
2009-09 including flow down of all provisions and requirements to any subcontractors. Executive
Order 2009-09 supersedes Executive order 99-4 and amends Executive order 75-5 and may be
viewed and downloaded at the Arizona State Library Research website
(http://azmemory.azlibrary.gov/cdm/singleitem/collection/execorders/id/680/rec/1) which is
hereby incorporated into this contract as if set forth in full herein. During the performance of this
Contract, Contractor shall not discriminate against any employee, client or any other individual in
any way because of that person’s age, race, creed, color, religion, sex, disability or national origin.
6.22 CERTIFICATION REGARDING DEBARMENT AND SUSPENSION:
6.22.1 The undersigned (authorized official signing on behalf of the Contractor) certifies to the
best of his or her knowledge and belief that the Contractor, it’s current officers and
directors;
6.22.1.1 are not presently debarred, suspended, proposed for debarment, declared
ineligible, or voluntarily excluded from being awarded any contract or grant
by any United States Department or Agency or any state, or local jurisdiction;
6.22.1.2 have not within three (3) year period preceding this Contract;

SERIAL 190283-RFP
6.22.1.2.1 been convicted of fraud or any criminal offense in connection with
obtaining, attempting to obtain, or as the result of performing a
government entity (Federal, State or local) transaction or contract;
and
6.22.1.2.2 been convicted of violation of any Federal or State antitrust statues
or conviction for embezzlement, theft, forgery, bribery,
falsification or destruction of records, making false statements, or
receiving stolen property regarding a government entity transaction
or contract;
6.22.1.2.3 are not presently indicted or criminally charged by a government
entity (Federal, State or local) with commission of any criminal
offenses in connection with obtaining, attempting to obtain, or as
the result of performing a government entity public (Federal, State
or local) transaction or contract; and are not presently facing any
civil charges from any governmental entity regarding obtaining,
attempting to obtain, or from performing any governmental entity
contract or other transaction; and have not within a three (3) year
period preceding this Contract had any public transaction (Federal,
State or local) terminated for cause or default.
6.22.1.3 If any of the above circumstances described in the paragraph are applicable to
the entity submitting a bid for this requirement, include with your bid an
explanation of the matter including any final resolution.
6.22.2 The Contractor shall 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.
6.23 VERIFICATION REGARDING COMPLIANCE WITH A.R.S. §41-4401 AND FEDERAL
IMMIGRATION LAWS AND REGULATIONS:
6.23.1 By entering into the Contract, the Contractor warrants compliance with the Immigration
and Nationality Act (INA using e-verify) and all other Federal immigration laws and
regulations related to the immigration status of its employees and A.R.S. §23-214(A). The
Contractor shall obtain statements from 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
Immigration Reform and Control Act of 1986, as amended from time to time, for all
employees performing work under the Contract and verify employee compliance using the
E-verify system and shall keep a record of the verification for the duration of the
employee’s employment or at least three (3) years, whichever is longer. I-9 forms are
available for download at USCIS.GOV.
6.23.2 The County retains the legal right to inspect Contractor and subcontractor employee
documents performing work under this Contract to verify compliance with paragraph 6.23.1
of this Section. Contractor and subcontractor shall be given reasonable notice of the
County’s intent to inspect and shall make the documents available at the time and date
specified. Should the County suspect or find that the Contractor or any of its subcontractors
are not in compliance, the County will consider this a material breach of the Contract and
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 debarment of the
Contractor. All costs necessary to verify compliance are the responsibility of the Contractor.

SERIAL 190283-RFP
6.24 INFLUENCE:
As prescribed in MC1-1203 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 MC1-902.
An attempt to influence includes, but is not limited to:
6.24.1 A Person offering or providing a gratuity, gift, tip, present, donation, money,
entertainment or educational passes or tickets, or any type of valuable contribution or
subsidy,
6.24.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.
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.
6.25 UNIFORM ADMINISTRATIVE REQUIREMENTS:
By entering into this Contract, the Contractor agrees to comply with all applicable provisions of
Title 2, Subtitle A, Chapter II, PART 200—UNIFORM ADMINISTRATIVE REQUIREMENTS,
COST PRINCIPLES, AND AUDIT REQUIREMENTS FOR FEDERAL AWARDS contained in
Title 2 C.F.R. § 200 et seq.
6.26 ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT AND/OR
OTHER REVIEW:
6.26.1 In accordance with section MCI 371 of the Maricopa County Procurement Code the
Contractor agrees to retain (physical or digital copies of) all books, records, accounts,
statements, reports, files, and other records and back-up documentation relevant to this
Contract for six (6) years after final payment or until after the resolution of any audit
questions which could be more than six (6) years, whichever is latest. 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.
6.26.2 If the Contractor’s books, records, accounts, statements, reports, files, and other records
and back-up documentation 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.
6.27 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 of the Contract to the extent agreed by the parties. If the parties do
not agree as to damages the matter shall be subject to the contract dispute procedure set forth at
Maricopa County Procurement Code, MC1-906 Contract Disputes or as finally determined by
arbitration, a court of competent jurisdiction or other tribunal.
6.28 CONFIDENTIAL INFORMATION:
The parties agree to keep confidential and not to use or disclose to any third parties any non-public
business information of the other party learned or disclosed in connection with each Statement of
Work. The obligation of the parties with respect to the Confidential Information shall terminate
with respect to any particular portion of the Confidential Information if and when: (i) it is in the

SERIAL 190283-RFP
public domain at the time of its communication; (ii) it is developed independently by the
receiving party without use of any confidential information; (iii) it enters the public domain
through no fault of the receiving party subsequent to the time of the disclosing party’s
communication to the receiving party; (iv) it is in the receiving party’s possession free of any
obligation of confidence at the time of the disclosing party’s communication; (v) it is
communicated by the disclosing party to a third party free of any obligation of confidence; or
(vi) the receiving party has the disclosing party’s written permission.
Each party shall provide notice to the other of any demand made upon it under lawful process to
disclose or provide any of the other party’s confidential information. The receiving party agrees to
cooperate with the disclosing party, at the disclosing party’s expense, if the disclosing party elects
to seek reasonable protective arrangements or oppose such disclosure. Any confidential
information disclosed pursuant to such lawful process shall continue to be confidential
information during the time that a request for protective arrangements are pending.
6.29 PUBLIC RECORDS:
Under Arizona law, all Offers submitted and opened are public records and must be retained by
the Records Manager at the Office of Procurement Services. Offers shall be open to public
inspection and copying after Contract award and execution, except for such Offers or sections
thereof determined to contain proprietary or confidential information by the Office of Procurement
Services. If an Offeror believes that information in its Offer or any resulting Contract should not
be released in response to a public record request under Arizona law, the Offeror shall indicate the
specific information deemed confidential or proprietary and submit a statement with its offer
detailing the reasons that the information should not be disclosed. Such reasons shall include the
specific harm or prejudice which may arise from disclosure. The Records Manager of the Office of
Procurement Services shall determine whether the identified information is confidential pursuant
to the Maricopa County Procurement Code.
6.30 PRICES:
Contractor warrants that prices extended to County under this Contract are no higher than those
paid by any other customer in the State of Arizona for these or similar services.
6.31 INTEGRATION:
This Contract represents 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.
6.32 RELATIONSHIPS:
6.32.1 In the performance of the services described herein, the Contractor shall act solely as an
independent contractor, and nothing herein or implied herein shall at any time be
construed as to create the relationship of employer and employee, co-employee,
partnership, principal and agent, or joint venture between the County and the Contractor.
6.32.2 The County reserves the right of final approval on proposed staff for all Task Orders.
Also, upon request by the County, the Contractor will be required to remove any
employees working on County projects and substitute personnel based on the discretion
of the County within Two (2) business days, unless previously approved by the County.
6.33 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, Phoenix, Arizona.

SERIAL 190283-RFP
6.34 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.
6.35 INCORPORATION OF DOCUMENTS:
The following are to be attached to and made part of this Contract:
6.35.1 Exhibit A, Pricing; and
6.35.2 Exhibit B, Scope of Work
6.36 THIRD-PARTY BENEFICIARIES:
This Agreement is for the benefit of the parties only. None of the provisions of this Agreement are
for the benefit of, or enforceable by, any third party. It is the intention of the County and
Contractor that no third party shall have the right to seek to impose liability on Contractors a result
of the Services or any Deliverables furnished to the County.
6.37 LIMITATION OF LIBAILITY:
Neither party shall be liable for any consequential, indirect, special or incidental damages, such as
damages for lost profits, business failure nor loss arising out of use of the Deliverables or the
consulting services, whether or not advised of the possibility of such damages. Except for liability
for personal injury or death or for damage to property caused by the negligence or willful
misconduct of Contractor or its employees, the Contractors total liability arising out of this
Contract shall be limited to fees earned under the SOW under which such liability arises.
NOTICES:
All notices given pursuant to the terms of this Contract shall be addressed to:
For County:
Maricopa County
Office of Procurement Services
160 South 4th Avenue
Phoenix, Arizona 85003-2494
For Contractor:
Yvette Toledo
Senior Director
Gartner, Inc.
1415 North 7th Ave.
Phoenix, Arizona 85007

SERIAL 190283-RFP
IN WITNESS WHEREOF, this Contract is executed on the date set forth above.
CONTRACTOR
AUTHORIZED SIGNATURE
Yvette Maria Toledo, Sr. Director
PRINTED NAME AND TITLE
1415 N. 7th Avenue
ADDRESS
12/2/19
DATE
MARICOPA COUNTY
CHAIRMAN, BOARD OF SUPERVISORS DATE
ATTESTED
CLERK OF THE BOARD DATE
APPROVED AS TO FORM
DEPUTY COUNTY ATTORNEY DATE

SERIAL 190283-RFP
EXHIBIT A
PRICING
SERIAL 190283-RFP
NIGP CODE: 91890
RESPONDENT'S NAME: Gartner, Inc.
COUNTY VENDOR NUMBER: VC0000001161
ADDRESS: 1415 N. 7th Avenue
Phoenix, Arizona 85007
P.O. ADDRESS:
TELEPHONE NUMBER: 602-561-8599
FACSIMILE NUMBER:
WEB SITE: Gartner.com
CONTACT (REPRESENTATIVE): Yvette Toledo
REPRESENTATIVE'S E-MAIL ADDRESS: yvette.toledo@gartner.com
YES NO NO
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE FROM THIS
CONTRACT [ ] [X]
PAYMENT TERMS: NET 30 DAYS
1.0 PRICING:
Pricing provided per deliverables in Section 2.0
1.1 Current State Assessment (2.2.1) $237,500.00 Not to exceed (including travel)
1.2 Future State Recommendation (2.2.2) $190,000.00 Not to exceed (including travel)
1.3 Roadmap for Implementation (2.2.3) $190,000.00 Not to exceed (including travel)
1.4 Total Cost $617,500.00
2.0 ADDITIONAL PRICING:
Hourly wage rate for services outside scope of work n/a List separately or attach a current rate card
3.0 PAYMENT DELIVERABLES AND MILESTONES:
Note: All deliverables are payable upon completion and acceptance by Maricopa County per the payment terms.

SERIAL 190283-RFP
EXHIBIT B
SCOPE OF WORK
1.0 INTENT:
The Contractor shall provide a best practices and industry standards-based assessment of the Maricopa
County enterprise network and computing infrastructure, and recommendations for a proposed future
infrastructure environment. The County is expanding use of cloud services and must ensure the
infrastructure will meet or exceed all expectations including those for performance, security, and reliability
for years to come. The County further requires a complete roadmap, along with budgetary costs estimates,
for all proposed recommendations.
The Contractor’s deliverables shall include at a minimum the following requirements:
 Current State Assessment
 Future state recommendations
 Roadmap for implementation
2.0 SCOPE OF WORK:
2.1 MANDATORY BUSINESS REQUIREMENTS:
2.1.1 Contractor shall conduct a best practice and industry standards-based assessment;
2.1.2 Contractor shall articulate the capacity of the current County infrastructure to
accommodate cloud services in use today and expected capacity demand based on
strategic plan, direction, and themes;
2.1.3 Contractor shall produce a roadmap, including prioritized actions and estimated
budgetary costs, for all recommended any needed remediation or modifications; and
2.1.4 Contractor shall be expected to complete project timeline no later than six (6) months
from being given a notice to proceed.
2.2 MANDATORY DELIVERABLES:
2.2.1 Current State Assessment – The County requires the assessment be best practice and
industry standards-based. The Contractor shall provide a the comprehensive assessment
that will include OET’s data centers and the resources contained therein, network
infrastructure, internet edge, data storage, mobile device usage and anticipated future
usage, carrier services, information security tools, remote access/VPN services,
enterprise, and key departmental applications, and any other area deemed necessary and
mutually agreed upon such as certain staff resources. The assessment shall account for
the County and OET’s strategic plans in addition to strategic themes. In addition, the
assessment shall identify current cloud services and those the County anticipates
consuming in the future, and identify OET staff knowledge of cloud services, including
deployment, development, operations, and support.
2.2.2 Future State Recommendations - The Contractor will provide a recommended future
state for where the County should be with its infrastructure in 3-5 years along with
supporting documentation. The future state recommendation will include a written
process and decision model for the County to use in ongoing evaluations of moving
current applications into the cloud. The decision model will be able to produce a
recommendation with supporting documentation on whether or not the County should
move existing on-premise applications to a cloud-hosted environment. This decision
model will further produce a recommendation with supporting documentation on whether
to host new applications on premise or in a cloud hosted environment. These processes
and decision models must align with the recommended future state.

SERIAL 190283-RFP
Other aspects of the future state recommendation will also indicate how information
security needs to align with increased utilization of and migration to cloud services,
including a hybrid environment. This should also include a capacity-planning framework
with reporting to help measure capacity and growth rates, as well as recommendations for
optimization tools to assist the County to manage resources (compute, storage, database,
transfer) in this new environment.
The future state should also indicate where current OET staffing deficiencies may exist
and what type of skills or training are required to address these deficiencies.
2.2.3 Roadmap for Implementation – The Contractor will provide a comprehensive roadmap
that demonstrates deep strategic thinking and that clearly articulates how, when, and at
what budgetary cost the County will move from current to recommended future state.
The County requires costs broken out by year, and each of the key components
(Enterprise Infrastructure, Applications, Security, and Staffing), and be aligned with the
County’s budget cycle (annual). This deliverable should also include a mechanism for
tracking and reporting on the County’s infrastructure, and tracking/monitoring framework
providing updates towards the proposed County future state.
The Contractor will clearly articulate facts, recommendations, and costs as applicable for
each of these areas below within deliverables. Upon agreement with the County, the
Contractor may delineate in additional ways to comply with best practices or industry
standards.
2.2.3.1 Enterprise Infrastructure
2.2.3.2 Applications
2.2.3.3 Security
2.2.3.4 Staffing
All deliverables must be source data, editable, and MS Office ProPlus compatible. Any
exceptions must be approved by Maricopa County.
2.3 The Contractor proposes to meet the mandatory deliverable requirements according to the list of
task activities and descriptions detailed below.
Step 1. Project Initiation Deliverable(s) and Time Frame
Objective: Deliverable(s):
 Ensure a mutual awareness of the  Kickoff materials
County’s current state, the availability of  Document request list
data required and — where necessary —  Contact list
ensure agreed contingency plans are in
 Project schedule
place.
Time Frame:
Activities Performed by Gartner:
 1-2 week(s)
 Conduct initial pre-planning meetings with
the County Project Manager to establish
communications cadence needed to Assumptions:
effectively manage the scope, schedule  County will review and approve
and budget, anticipate and mitigate risks, documents within five business
and resolve issues on an ongoing basis. days. If no formal approval or
 Request initial documentation relevant rejection is received within that time,
document for discovery, such as: the deliverable is considered to be
– Org charts and staffing data accepted by the County.
– County vision/strategy  County will schedule resources for
project activities and provide
– OET vision/strategy

SERIAL 190283-RFP
– County agencies/departments/offices meeting facilities as necessary.
strategy documents  The work effort described in this
– Current state technology inventory SOW assumes County personnel
and architecture are available to assist in the manner
– Relevant ongoing (and planned) defined in this SOW. In the event
initiatives that personnel are not available, a
– Data center and asset inventory data change of scope may be necessary.
– Financial data and budgetary plans
 Identify County core team and key points-
of-contacts (POCs) from OET and the
County departments.
 Based on agreed-to scope and
assumptions, work with OET to identify a
reasonable subset of the estimated 15
County IT organizations and 50+ County
departments that would provide a
sufficiently representative sample for
discovery interviews.
 Identify POCs from the following key
areas:
– Enterprise Infrastructure
– Applications
– Security
– Staffing
 Conduct Kickoff meeting with County
Core Project Team to ensure
understanding of the project objectives,
scope, schedule, and milestones, roles,
responsibilities and required resources for
Gartner and the County.
County Responsibilities:
 Designate a County Project Manager to
act as the single point of contact (SPOC)
for this project and to work closely with
the Gartner team as needed, including:
(a) approve project priorities, detailed step
plans and schedules; (b) facilitate the
scheduling of Gartner workshops and
interviews with appropriate client
personnel; (c) notify Gartner in writing of
any project or performance issues; and
(d) assist in resolving project issues that
may arise
 Ensure attendance by Project Sponsor,
Project Manager and other key
stakeholders, as determined prior to
Kickoff
 Gather and provide relevant background
material to Gartner project team within 5
business days of receiving the request
 Work with the Gartner team to identify
subject matter experts (SMEs) and
relevant stakeholders for interviews and
information exchange
 Ensure stakeholder participation and

SERIAL 190283-RFP
perform scheduling according to the
project schedule.
Step 2. Discovery Deliverable(s) and Time Frame
Objective: Deliverable(s):
 Identify and gather current state  Discovery validation workshop
information. materials
 Gain understanding of County business  Interview guides
context relevant to Maricopa County IT  Data collection templates
and the cloud.  Data collection surveys
 Validate current state information in
preparation for current state assessment.
Estimated Time Frame:
 4-6 week(s)
Activities Performed by Gartner:
 Conduct activities onsite during initial 2-3
Assumptions:
weeks for data collection and interviews
to maximize opportunity for information  Actual time frame of Step 2
gathering, identification of risks/gaps, and Discovery may depend on County
planning/coordination of follow up ability to schedule resources and
discovery activities. participate per agreed-upon scope
and project schedule.
 Conduct up to 30 onsite interviews
(individual or group), to include:  Onsite weeks include 1 travel day
and up to 4 work days.
– Leadership (executives, extended
leadership team)  Interviews typically last 1-2 hours,
individual or group, and up to 4-5 per
– Business/Org (analysts, department
work day.
heads, Staffing, PMO, procurement,
etc.)  Staffing scope limited to OET.
– Technical (infrastructure leads,  Compute/storage information for
Security, Applications) County IT organizations is available
centrally or coordinated centrally
 Understand and document County
through OET.
business context for expanding use of
cloud services, to include:
– Strategic drivers and vision
– Current perception of IT services
– Future expectations of IT
infrastructure and OET’s role
 Review and understand current cloud
adoption posture, including existing
services.
 Review application inventory and
understand mapping to County business
and IT capabilities.
 Develop and deploy data collection
templates and surveys to gather current
state information in the following areas:
– Enterprise Infrastructure
 Enterprise network (ongoing
refresh)
 Compute/storage workloads at 2
primary data centers and relevant
County IT organizations
 Backup and disaster recovery
 Current operations and support
model

SERIAL 190283-RFP
 Technology usage and
deployment
– Applications
 Commercial-off-the-shelf (COTS)
 Custom (in-house)
 Current hosting and support
models
 Technical attributes
 Business value
 Suitability for cloud (vs on-prem)
– Security
 Information security policies
 Strategy and tools
 Security in the cloud
– Staffing (OET only)
 Structure and resource
management
 Roles and responsibilities
 Skills and competencies
 Internal IT role in context of cloud
adoption (i.e. cloud service broker,
etc.)
 Conduct follow up activities as needed
prior to validation workshop. These may
include requests for information (RFIs),
interviews, data collection, work sessions.
 Conduct ½ day workshop to validate and
baseline current state understanding,
including Gartner initial observations and
assumptions as critical input to the
Current State Assessment in Step 3.
County Responsibilities:
 Coordination and scheduling of all onsite
activities
 Ensure timely responses to data
collection RFIs
 Provide Gartner team with dedicated
workspace, internet, and printing while
onsite
 Ensure participation in interviews, work
sessions, and validation workshop
Step 3. Assess Current State Deliverable(s) and Time Frame
Objective: Milestone Deliverable(s):
 Based on validated information gathered  Current State Assessment
in Step 2 Discovery, assess current state
against leading best practices and with
the context of cloud readiness and
Time Frame:
suitability.
 10-12 week(s)
 Ensure assessment addresses 4 key
areas: Enterprise Infrastructure,
Applications, Security, and Staffing Assumptions:

SERIAL 190283-RFP
 Gartner will conduct the assessment
Activities Performed by Gartner: across 4 concurrent workstreams
 Conduct and synthesize research on (infrastructure, applications, security,
cloud adoption/migration, including best and staffing) and integrate findings
practices, industry standards, current into Current State Assessment.
technology and market trends.
 Conduct initial Information Session with
County to:
– Review best practices and trends for
cloud adoption/migration in the
context of the 4 focus areas
(Enterprise Infrastructure,
Applications, Security, Staffing)
– Review approach and execution of
assessment for each area
(infrastructure, applications, security,
staffing) to support the Current State
Assessment
 Assess Enterprise Infrastructure
leveraging methodology described in
Section 2.3.1, including:
– Assessment of infrastructure
technologies, workload, performance,
and capacity
– Review current portfolio of hosting
services and environments
– Establish baseline of the current
workload inventory and costs
– Alignment with best practices for
cloud migration (e.g., considerations
for low-end “lift and shift” versus re-
architecting to take advantage of
cloud native capabilities, etc.)
 Assess Applications leveraging
methodology described in Section 2.3.2,
including:
– Mapping applications to business
services and IT capabilities
– Technical and architecture
components
– Business value/impact and
operational costs
 Assess Security leveraging methodology
described in Section 2.3.3, including:
– The maturity level and effectiveness
of the County’s current information
security program
– Overall compliance with applicable
regulatory and statutory requirements
– Level of current risk exposure
 Assess Staffing (OET only) leveraging
methodology described in Section 2.3.4,
including:
– Review of relevant staffing best
practices for cloud adoption
– Identification of critical gaps in skills,

SERIAL 190283-RFP
competencies, and roles
 Synthesize analysis from 4 workstreams
into a comprehensive current state
assessment for County infrastructure
cloud readiness and adoption.
 Conduct working session to begin
defining Cloud governance and value
OET provides Maricopa Departments.
 Conduct ½ day Current State Workshop
to review and validate assessment
findings.
County Responsibilities:
 Support scheduling working sessions and
workshops on behalf of the Gartner team
 Schedule resources for project activities
and provide meeting facilities as
necessary
 Ensure active participation in workshops
and working sessions
 Provide consolidated, written feedback on
Gartner materials when requested and
within five business days
Step 4. Determine Future State Deliverable(s) and Time Frame
Objective: Milestone Deliverable(s):
 Develop recommendations for the future  Future State Recommendations, to
state infrastructure for the next 3-5 years. include:
– Future State Profile
Activities Performed by Gartner: – Cloud Adoption Decision
 Based on the Current State Assessment Model/Process
completed in Step 3 (infrastructure,
applications, security, staffing), identify Time Frame:
and evaluate future state options to  4-6 week(s)
support the County’s ability to expand into
the cloud in the next 3-5 years.
Assumptions:
 For Enterprise Infrastructure, the future
state should consider, but not limited to,  Actual duration of this step may be
the following: dependent on County participation,
responsiveness and availability of
– Impact of current network refresh
County personnel
initiative (Cisco)
– Capacity and readiness of
compute/storage primary datacenters
in Phoenix and Scottsdale
– Impact of core or common
infrastructure shared or supported by
County departments and IT
organizations
– Tools and processes for operational
management (on-prem, cloud, hybrid)
 For Applications, the future state should
consider, but not limited to, the following:
– Balancing technical condition and
business value of application
workloads when considering cloud

SERIAL 190283-RFP
suitability.
– Consolidation of redundant
applications (across County
departments) supporting similar,
common, or core business
capabilities.
 For Security, the future state should
consider, but not limited to, the following:
– Capability gaps in current security
strategy vis a vis best practices in
cloud (or hybrid IT) environments
(e.g.,
– Address if and how information
security policies for the County should
change in the future state
– “Defense-in-depth” vs “defense-in-
context”
 For Staffing (OET only), the future state
should consider, but not limited to, the
following:
– The current role of OET and how it
would evolve in the future state
infrastructure (e.g., cloud service
broker, center of excellence, etc.)
– Gaps or deficiencies in competencies,
skills and training (e.g. vendor
management, cloud architect, etc.)
 Leverage Gartner research and
methodologies for cloud readiness (see
TIME and CloudScore in section 2.3.2) to
develop a decision framework/model to
determine cloud readiness and suitability
for current and new application workloads
(i.e. on-prem, Iaas, PaaS, SaaS, hybrid
IT, hybrid cloud, etc.)
 Gartner will apply this framework to the
current state environment and document
the process for the County to evaluate
future application workloads and business
capabilities.
 Conduct two (2) half-day workshops to
review and solicit feedback on future state
profile and recommendations.
County Responsibilities:
 Support scheduling working sessions and
workshops on behalf of the Gartner team
 Schedule resources for project activities
and provide meeting facilities as
necessary
 Ensure active participation in workshops
and working sessions
 Provide consolidated, written feedback on
Gartner materials when requested and
within five business days

SERIAL 190283-RFP
Step 5. Develop Roadmap Deliverable(s) and Time Frame
Objective: Milestone Deliverable(s):
 Develop comprehensive roadmap that  Roadmap for Implementation
articulates how, when, and at what
budgetary cost the County will move from Time Frame:
current to recommended future state
 4-6 week(s)
Activities Performed by Gartner:
Assumptions:
 Based Future State Recommendations
 Actual duration may be impacted by
and County feedback, Gartner will
additional review sessions, iteration
develop a set of implementation initiatives
cycles, and availability of County
to support achieving the future state in 3-5
personnel for engagement.
years.
 Develop a mini-charter for each initiative
with the following considerations:
– Focus area (Enterprise Infrastructure,
Applications, Security, and Staffing)
– Owner
– Objectives (Improvement,
Opportunity, Results, Rationale)
– Quantitative/Qualitative Benefits
– Implementation Risks and Critical
Success Factors
– Key steps/activities
– Business impact
– Implementation complexity (degree of
difficulty)
– Assumptions/Dependencies/Timing
– Level of investment by budget year
(cost, personnel)
– Timing of investment (alignment with
County budget cycle)
– Key performance indications (KPIs)
for tracking and reporting status and
progress
 Develop single Gantt chart to illustrate
timelines of all initiatives.
 Package all mini-charters, Gantt chart,
and support documentation (i.e.,
research, cost estimate build up, etc.) into
consolidated Roadmap for
Implementation
 All deliverables will be source data,
editable, and MS Office ProPlus
compatible.
 Conduct ½ day workshop
County Responsibilities:
 Support scheduling working sessions and
workshops on behalf of the Gartner team
 Schedule resources for project activities
and provide meeting facilities as
necessary
 Ensure active participation in Roadmap

SERIAL 190283-RFP
Workshop
 Provide consolidated, written feedback on
Gartner materials when requested and
within five business days
Step 6. Deliver Results Deliverable(s) and Time Frame
Objective: Milestone Deliverable(s):
 Final readout of all deliverables and  Executive Presentation
closeout of project
Time Frame:
Activities Performed by Gartner:  2-4 week(s)
 Review and package all deliverables and
supporting documentation Assumptions:
 Develop Executive Summary  None
 Conduct Executive Presentation
County Responsibilities:
 Attend Executive Presentation