13149-CI IBM SIGNED 072914.PDF

Competition Impractical
SERIAL 13149-CI
This Contract is entered into this 10th day of September, 2014 by and between Maricopa County (collectively
“County”, “District”, “You/your”), a political subdivision of the State of Arizona, and International Business
Machines Corporation, a New York corporation (collectively “IBM”, “Contractor”) for the purchase of services
(including, without limitation, customized development and support, business consulting, and maintenance
services). For purposes of clarity, no IBM or non-IBM software or products will be purchased under this contract.
1.0 CONTRACT TERM:
1.1 This Contract is for a term of Five (5) years, beginning on the 10th day of September, 2014 and
ending the 30th day of September, 2019.
1.2 The County may, at its option and with the agreement of IBM, renew the term of this Contract for
additional terms up to a maximum of five (5) 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 IBM in writing of its intent to extend the Contract term at least thirty (30)
calendar days prior to the expiration of the original contract term, or any additional term
thereafter.
2.0 FEE ADJUSTMENTS:
A Transaction Document specifies the amount payable for Services, based on one or more of the following
types of charges: one-time, recurring, time and materials, or fixed price. Additional charges may apply
(such as travel related expenses). IBM will inform County in advance whenever additional charges apply.
Charges for Services are billed as specified in a Transaction Document, which may be in advance,
periodically during the performance of the Service, or after the Service is completed. Unless otherwise
provided in this Agreement (including any applicable Attachment or Transaction Document): i) Services
for which Customer prepays must be used within the applicable contract period; and ii) IBM does not give
credits or refunds for any prepaid or other charges already due or paid, unless the applicable services fail to
fulfill the requirements of the Transaction Document.
If a Transaction Document provides an estimated total charge for time and materials or for usage charges,
the estimate is for planning purposes only. IBM shall provide County with individual billing rates for all
project personnel. IBM invoices charges based on actual time and materials expended or Customer’s actual
or authorized use, subject to any specified minimum commitment.
From time to time, IBM may change its charges. Customer receives the benefit of a decrease in charges for
amounts that become due on or after the effective date of the decrease.
Unless provided otherwise in an Attachment or Transaction Document, IBM may increase recurring
charges for Services, labor rates, and minimums for Services provided under this Agreement, by giving
Customer three months' written notice. An increase applies on the first day of the invoice or charging
period on or after the effective date IBM specifies in the notice.

SERIAL 13149-CI
3.0 PAYMENTS:
3.1 As consideration for performance of the duties described herein, County shall pay Contractor the
sum(s) stated in the Transaction Documents when authorized by the parties.
3.2 Payment shall be made upon the County’s receipt of a properly completed invoice.
3.3 INVOICES:
3.3.1 IBM shall submit one (1) legible copy of their detailed invoice before payment(s) can be
made. 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
 Invoice number and date
 Payment terms
 Date of service or delivery
 Quantity
 Contract Item number(s)
 Description of service provided
 Pricing per unit of service
 Freight (if applicable)
 Extended price
 Mileage w/rate (if applicable)
 Total Amount Due
3.3.2 Problems regarding billing or invoicing shall be directed to the County as listed on the
Purchase Order.
3.3.3 Payment shall be made to IBM by Accounts Payable through the Maricopa County
Vendor Express Payment Program. This is an Electronic Funds Transfer (EFT) process.
After Contract Award IBM shall complete the Vendor Registration Form located on the
County Department of Finance Vendor Registration Web Site
(http://www.maricopa.gov/Finance/Vendors.aspx).
3.3.4 EFT payments to the routing and account numbers designated by IBM will include the
details on the specific invoices that the payment covers. IBM is required to discuss
remittance delivery capabilities with their designated financial institution for access to
those details.
3.4 STRATEGIC ALLIANCE for VOLUME EXPENDITURES ($AVE):
3.4.1 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 IBM, a member of $AVE may access a contract resulting from a
solicitation issued by the County.
3.5 INTERGOVERNMENTAL COOPERATIVE PURCHASING AGREEMENTS (ICPA’s)
3.5.1 County currently holds ICPA’s with numerous governmental entities throughout the State
of Arizona. These agreements allow those entities, with the approval of IBM, to
purchase their requirements under the terms and conditions of the County Contract.
4.0 AVAILABILITY OF FUNDS:

SERIAL 13149-CI
4.1 The provisions of this Contract relating to payment for services shall become effective when funds
assigned for the purpose of compensating IBM 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 IBM fully informed as to the availability of funds.
4.2 If any action is taken by any state agency, Federal department or any other agency or
instrumentality to suspend, decrease, or terminate its fiscal obligations under, or in connection
with, this Contract, County may amend, suspend, decrease, or terminate its obligations under, or in
connection with, this Contract. In the event of termination, County shall be liable for payment
only for services rendered prior to the effective date of the termination, provided that such services
are performed in accordance with Exhibit C, D or any subsequent Transaction Document of this
Contract. County shall give written notice of the effective date of any suspension, amendment, or
termination under this Section, at least ten (10) days in advance.
5.0 DUTIES:
5.1 IBM shall perform all duties stated in Exhibits C, D or any subsequent Transaction Document, or
as otherwise agreed to in writing between the parties.
5.2 During the Contract term, County shall 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.
6.0 TERMS and CONDITIONS:
6.1 MUTUAL INDEMNIFICATION:
6.1.1 Both parties shall indemnify (the indemnifying party shall be referred to herein as the
“Indemnitor”) at the Indemnitor’s expense, the other party, and its employees (such
persons are referred to herein collectively and individually as the “Indemnitee”), against
claims made by third parties against an Indemnitee for costs, damages, and attorneys’
fees that a court finally awards against Indemnitee or that are included in a settlement
approved in advance by Indemnitor, for any bodily injury or death, or property damage,
to the extent caused by the Indemnitor, provided that Indemnitee: (a) promptly notifies
Indemnitor in writing of the claim; and (b) allows Indemnitor to control, and cooperates
with Indemnitor in, the defense and any related settlement negotiations.
The scope of this indemnification does not extend to the sole negligence of County.
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.

SERIAL 13149-CI
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.
6.2.6 County reserves the right to request and to receive, within 10 working days, certified
copies of any or all of the herein required insurance certificates. County shall not be
obligated to review policies and/or endorsements or to advise Contractor of any
deficiencies in such policies and endorsements, 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.
6.2.7 The insurance policies required by this Contract shall name County, its agents,
representatives, officers, directors, officials and employees as Additional Insureds.
6.2.8 The policies required hereunder 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.9 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.
6.2.10 Errors and Omissions Insurance (inclusive of Cyber Liability):
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 $2,000,000 for each claim, and $15,000,000 in the aggregate
6.2.11 Certificates of Insurance.
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 upon ten (10) business days. BY
SIGNING THE AGREEMENT PAGE IBM AGREES TO THIS REQUIREMENT
AND FAILURE TO MEET THIS REQUIREMENT WILL RESULT IN
CANCELLATION OF 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 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, a renewal certificate must be sent to
County fifteen (15) days prior to the expiration date.

SERIAL 13149-CI
6.2.12 Cancellation and Expiration Notice.
Insurance required herein shall not be permitted to expire, be canceled, or materially
changed without thirty (30) days prior written notice to the County.
6.3 WARRANTY OF SERVICES:
6.3.1 IBM warrants that it performs each IBM Service using reasonable care and skill and
according to its current description (including any completion criteria) contained in the
Statements of Work, including all descriptions, specifications and attachments made a
part of this Contract. County’s acceptance of services or goods provided by IBM shall
not relieve IBM from its obligations under this warranty.
6.3.2 In addition to its other remedies, County may, at IBM's expense, request the correction of
any services failing to meet IBM's warranty herein. Services corrected by IBM shall be
subject to all the provisions of this Contract in the manner and to the same extent as
services originally furnished hereunder.
6.3.3 Items Not Covered by Warranty
IBM does not warrant uninterrupted or error-free operation of any Service. Unless
otherwise specified in an Attachment or Transaction Document, IBM provides Materials
and non-IBM Services WITHOUT WARRANTIES OF ANY KIND. However, non-
IBM suppliers may provide their own warranties to Customer.
6.3.4 Extent of Warranty
THIS WARRANTY IS CUSTOMER’S EXCLUSIVE WARRANTY AND REPLACES
ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED,
INCLUDING ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.
6.4 INSPECTION OF SERVICES:
6.4.1 IBM shall provide verification and sign off of all services performed in delivery of a
statement of work to insure acceptance by the County. IBM Service logs and completion
checklists can be made available to the County upon request.
6.4.2 County has the right to inspect and test all services called for by the Contract, to the
extent practicable at all times and places during the term of the Contract. County shall
perform inspections and tests in a manner that will not unduly delay the work.
6.5 NOTICES:
All notices given pursuant to the terms of this Contract shall be addressed to:
For County:
Maricopa County
Office of Procurement Services
ATTN: Contract Administration
320 West Lincoln Street
Phoenix, Arizona 85003-2494
For IBM:
Danny Jensen, Solution Representation
IBM Canada

SERIAL 13149-CI
3292 Production Way
Burnaby, BC, V5A 4R4
6.6 REQUIREMENTS CONTRACT:
6.6.1 Contractor signifies its understanding and agreement by signing this document that this
Contract is a requirements contract. This Contract does not guarantee any purchases will
be made (minimum or maximum). Orders will only be placed when County identifies a
need and issues a purchase order or a written notice to proceed.
6.6.2 Purchase orders will be cancelled in writing.
6.7 FORCE MAJEURE
Except for a party’s payment obligations hereunder, neither party shall be deemed in default of
this Agreement to the extent that performance of its obligations or attempts to cure any breach
thereof are delay or prevented by reason of any act of God, government, fire, natural disaster,
accident, terrorism, network or telecommunication system failure, sabotage or any other cause
beyond the control of such party (“Force Majeure”), provided that such party promptly gives the
other party written notice of such Force Majeure.
6.8 TERMINATION FOR CONVENIENCE:
The County reserves the right to terminate the Contract, in whole or in part at any time, when in
the best interests of the County without penalty or recourse. Upon receipt of the written notice,
IBM 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, all documents, data and reports prepared by IBM under the
Contract shall become the property of and be delivered to the County upon demand. IBM shall be
entitled to receive compensation at the rates or fees contained herein, for work in progress, work
completed and materials accepted before the effective date of the termination.
6.9 TERMINATION FOR DEFAULT:
6.9.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 IBM to comply with any term or condition of the
Contract, to acquire and maintain all required insurance policies, bonds, licenses and
permits as agreed to between the parties, or to make satisfactory progress in performing
the Contract. The Procurement Officer shall provide written notice of the termination
and the reasons for it to IBM.
6.9.2 Upon termination under this paragraph, all goods, materials, documents, data and reports
prepared by IBM under the Contract shall become the property of and be delivered to the
County on demand.
6.9.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. IBM
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 IBM.
6.9.4 IBM shall continue to perform, in accordance with the requirements of the Contract, up to
the date of termination, as directed in the termination notice.
6.10 TERMINATION BY THE COUNTY:
If IBM should be adjudged bankrupt or should make a general assignment for the benefit of its
creditors; or if a receiver should be appointed on account of its insolvency, the County may
terminate the Contract. If IBM should persistently or repeatedly refuse or should fail, except in
cases for which extension of time is provided, to provide enough properly skilled workers or

SERIAL 13149-CI
proper materials, or persistently disregard laws and ordinances, or not proceed with work or
otherwise be guilty of a substantial violation of any provision of this Contract, then the County
may terminate the Contract. Prior to termination of the Contract, the County shall give IBM
fifteen (15) business day’s written notice. Upon receipt of such termination notice, IBM shall be
allowed fifteen (15) business days to cure such deficiencies.
6.11 TERMINATION AND WITHDRAWAL OF SERVICE
Either party may terminate a Service transaction if the other materially fails to meet its obligations
concerning the Service.
County may terminate a Service, on notice to IBM provided County has met all minimum
requirements and paid any adjustment charges specified in the applicable Attachments and
Transaction Documents.
For a maintenance Service, County may terminate without adjustment charge, provided any of the
following circumstances occur:
6.11.1 County permanently removes the eligible product, for which the Service is provided,
from productive use within County’s Enterprise;
6.11.2 the eligible location, for which the Service is provided, is no longer controlled by County
(for example, because of sale or closing of the facility); or
County agrees to pay IBM for i) all charges for Services IBM provides and any products and
Materials IBM delivers through Service termination, and ii) reimbursable expenses IBM incurs
through Service termination.
IBM may withdraw a Service or support for an eligible product on three months' written notice to
County. If IBM withdraws a Service for which County has prepaid and IBM has not yet fully
provided it to County, IBM will give County a prorated refund.
Any terms that by their nature extend beyond termination or withdrawal remain in effect until
fulfilled and apply to respective successors and assignees.
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 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.
6.13 ADDITIONS/DELETIONS OF SERVICE:
6.13.1 The County reserves the right to add and/or delete materials to a Contract. If a service
requirement is deleted, payment to IBM will be reduced proportionately, to the amount of
service reduced in accordance with the contract price. If additional materials are required
from a Contract, prices for such additions will be negotiated between IBM and the
County.
6.13.2 The County reserves the option to review the proposed staff for provision of services
defined in the SOW. Also, upon request by the County, IBM will be required to remove
any employees working on County projects when requested by the County. Contractor
will provide replacement personnel as soon as practicable. County understands that

SERIAL 13149-CI
requiring replacement personnel may impact the delivery schedule for which Contractor
may request an equitable adjustment to schedule and price.
6.14 RELATIONSHIPS:
In the performance of the services described herein, IBM 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, partnership, principal and agent, or joint venture between
the District and IBM.
6.15 BACKGROUND CHECKS AND CLEARANCES
All IBM staff or subcontractor staff providing services under this Agreement must undergo a
background check to be performed by the Maricopa County Sheriff’s Office or other MCSO-
approved law enforcement agency prior to commencement of work. The background check may
also include completion of Arizona Department of Public Safety (DPS) Terminal Operator
Certification (TOC) Level “D.” All background checks required for IBM employees or
subcontractors shall be performed at no charge to IBM or its affiliates.
MCSO will keep the information contained in the background screening report, and the results of
the report, confidential and communicate such information only to those with a need to know in
order to determine what action to take as a result of the report results. MCSO will destroy all
background screening information upon being advised by IBM that the employee is no longer a
resident IBM employee or upon expiration or termination of this contract.
If any IBM Employee brings a claim against IBM arising from MCSO’s possession of, or MCSO
allowing any third party to obtain possession of the Social Security Number, Date of Birth, or
Home Address provided to MCSO by IBM (collectively the “Personal Information”) of that
employee, MCSO will defend IBM against such claim at MCSO’s expense and pay all costs,
damages, and attorney’s fees that a court finally awards or that are included in a settlement
approved by MCSO, provided that IBM:
1. Promptly notified MCSO in writing of the claim; and
2. Allows MCSO to control, and cooperates with MCSO, in the defense and any related settlement
negotiations.
6.16 SUBCONTRACTING:
IBM 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. All correspondence authorizing subcontracting must reference the Proposal Serial
Number and identify the job project.
6.17 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.18 ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT AND/OR
OTHER REVIEW:
6.18.1 In accordance with section MCI-371 of the Maricopa County Procurement Code IBM
agrees to retain 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.

SERIAL 13149-CI
6.18.2 If at any time it is determined by the County that a rate or fee for which payment has
been made is disallowed, the County shall notify IBM in writing of the disallowance.
The course of action to address the disallowance shall be at sole discretion of the County,
and may include either an adjustment to future claim submitted by IBM by the amount of
the disallowance, or to require reimbursement forthwith of the disallowed amount by
IBM by issuing a check payable to Maricopa County.
6.19 AUDIT DISALLOWANCES:
If at any time, County determines that a rate or fee for which payment has been made is
disallowed, such as overpayment, County shall notify IBM 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 IBM by the amount of the disallowance, or to require repayment of the
disallowed amount by IBM.
6.20 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.
6.21 RIGHTS IN DATA:
IBM or its suppliers retains ownership of the copyright in any of IBM’s or its suppliers’ works,
methodologies, templates and other products that pre-exist or were developed outside of this
Agreement and any modifications or enhancements of such works that may be made under this
Agreement. The County retains ownership and rights to all data and information developed from
such data which may be contained in a report deliverable. The County may use, reproduce,
distribute and prepare derivative works in the normal course of the County's business.
6.22 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.23 VERIFICATION REGARDING COMPLIANCE WITH ARIZONA REVISED STATUTES §41-
4401 AND FEDERAL IMMIGRATION LAWS AND REGULATIONS:
6.23.1 By entering into the Contract, IBM 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). IBM 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. IBM 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 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 IBM 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

SERIAL 13149-CI
work, termination of the Contract for default, and suspension and/or debarment of IBM.
All costs necessary to verify compliance are the responsibility of IBM.
6.24 CERTIFICATION REGARDING DEBARMENT AND SUSPENSION
6.24.1 The undersigned (authorized official signing for IBM) certifies to the best of his or her
knowledge and belief, that IBM, defined as the primary participant in accordance with 45
CFR Part 76, and its principals:
6.24.2 are not presently debarred, suspended, proposed for debarment, declared ineligible, or
voluntarily excluded from covered transactions by any Federal Department or agency;
6.24.2.1 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;
6.24.2.2 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
6.24.2.3 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.
6.24.3 Should IBM not be able to provide this certification, an explanation as to why should be
attached to the Contact.
6.24.4 IBM 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.
6.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.
6.26 ORDER OF PRECEDENCE:
In the event of a conflict in the provisions of this Contract and any Transaction Documents, the
following order of precedence will apply:
The Contract
Exhibit E, Additional Terms and Conditions
Exhibit A, Pricing
Exhibit C, SOW Annual Maintenance
Exhibit D, SOW Data Source Integration Services
Exhibit B, Transaction Document Process
6.27 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 MC1-902.

SERIAL 13149-CI
An attempt to influence includes, but is not limited to:
6.27.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,
6.27.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.28 INCORPORATION OF DOCUMENTS:
The following are to be attached to and made part of this Contract:
6.28.1 Exhibit A, Pricing
6.28.2 Exhibit B, Transaction Document Process
6.28.3 Exhibit C, SOW Annual Maintenance
6.28.4 Exhibit D, SOW Data Source Integration Services
6.28.5 Exhibit E, Additional Terms and Conditions

SERIAL 13149-RFP
IN WITNESS WHEREOF, this Contract is executed on the date set forth above.
INTERNATIONAL BUSINESS MACHINES CORPORATION
AUTHORIZED SIGNATURE
Joanna McCallion / Quality Assurance Rep
PRINTED NAME AND TITLE
1800 W. 9 Mile Rd., Southfield, MI 48075
ADDRESS
7/29/14
DATE
MARICOPA COUNTY
CHIEF PROCUREMENT OFFICER, DATE
OFFICE OF PROCUREMENT SERVICES
ATTESTED:
CLERK OF THE BOARD DATE
APPROVED AS TO FORM:
LEGAL COUNSEL DATE

EXHIBIT A
PRICING
SERIAL 13149-CI
NIGP CODE: 920-15
RESPONDENT'S NAME:
COUNTY VENDOR NUMBER :
ADDRESS:
P.O. ADDRESS:
TELEPHONE NUMBER:
FACSIMILE NUMBER:
WEB SITE:
CONTACT (REPRESENTATIVE): Danny Jensen
REPRESENTATIVE'S E-MAIL ADDRESS: danny.jensen@ca.ibm.com
YES NO REBATE
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE FROM THIS CONTRACT [X] [ ]
PAYMENT TERMS:
PAYMENT IS DUE UPON RECEIPT OF AN ACCEPTABLE INVOICE, PAYABLE WITHIN 30 DAYS.
PAYMENT MAY BE MADE ELECTRONICALLY TO AN ACCOUNT SPECIFIED BY IBM OR BY OTHER
MEANS AGREED TO BY THE PARTIES. IN THE EVENT OF LATE PAYMENT, IBM RESERVES THE RIGHT
TO SUSPEND THE PROVISION OF SERVICES.
1.0 PRICING:
*Individual data source integrations shall be requested via the process described in Exhibit C.
These are the National Pricing Standard Data Source Integration Cost. Listing starting Costs, costs
will increase each year by 5%.
Standard RMS or JMS Data Source $52,100.00
Standard COPLINK xml RMS or JMS Data Source $37,650.00
Standard CAD or Mugs Data Source $32,768.00
Simple Probation Data Source $30,114.00
Complex Probation Data Source $45,171.00
Annual maintenance cost shall be based on the integration cost for each COPLINK data source.
Maintenance is payable annually in advance.
Annual Maintenance Percentage for Pre-Contract Integrations:
13% 2013-2014
13% 2014-2015
15% 2015-2016
17% 2016-2017
19% 2017-2018
20% 2018-2019
Annual Maintenance Percentage for New Integrations (done under this Contract):
13% 2014-2015
15% 2015-2019

Exhibit B
Transaction Document Process
The following procedures and guidelines shall be used between the parties in the event of annual node and data
source integration maintenance renewal and/or the County requesting additional or modified services from IBM.
Work Request Initiation:
County authorized individual shall provide IBM a detailed request in writing to include, but not be limited to: scope
of desired services, requested modifications, complete description of new data source (if applicable), and a required
due date.
Work Request Review:
Upon receipt of request from County, IBM shall designate the appropriate personnel for the review and
determination of feasibility of the request. IBM shall contact the County authorized individual confirming the
receipt of the request and an estimated timeline for the production of a formal Project Change Request (PCR). This
initial contact shall take place within 48 hours of receipt of the request.
Project Change Request (PCR):
The formal PCR shall be issued to the County utilizing only the form described below and no additional
documentation shall be included or accepted. No additional terms, conditions, descriptive documents or definitions
are required or acceptable. The numbering of the PCR shall follow a naming convention that includes: Agency, data
source type and a three digit sequential serial number (i.e. MCSO-RMS-001 for a MCSO request for a RMS data
source) or another naming convention that conveys a similar reference to the purpose of the PCR. The executed
PCR shall have the effect of a change order on the larger contract and shall be made part of said contract by
reference. The two specific examples below apply only to new Data Source Integrations and Data Source
Integration Maintenance.
IBM shall endeavor to not unduly delay the creation and submission of PCR. If there is cause for delay beyond the
estimated due date communicated to the County, IBM shall immediately notify County and inform them of the
revised date and the cause of the delay.
Example PCR for New Data Source Integration:
PROJECT CHANGE REQUEST (PCR)
New Data Source Integration Services
PCR Requested Date: Requested by: PCR Number:
PCR Proposal Date: Contract Number: 13149-CI
This PCR must be approved by both parties and signed below on or before the offer expiration date before the PCR
can be implemented. This offer will expire on {insert mm/dd/yyyy}, unless extended by IBM in writing. All other
terms in the referenced SOW (see Exhibit D of the Agreement) not affected by this PCR remain in full force and
effect.
● NOTE: Include a listing of the modifications made by this PCR. Remember to track the section
numbering in the referenced SOW so it is clear as to what is being changed/added/deleted.
The parties agree that this PCR modifies the existing referenced Contract as follows:
Contract Reference: 13149-CI
Project Name: {Name of Contributing Agency and/or Data Source}
Facility Location: {Address / City / State / Zip for Data Source}

Node Location: Maricopa County Sheriff’s Office – Phoenix, Arizona
Est. Start Date: {Estimated Start Date}
Est. Completion: On or before {Estimated Completion Date}
Agency Name Contributing Vendor Product Product Data Set
Agency Name Name RDBMS Type
Project Costs: IBM will invoice based on the following milestones; any applicable tax will be additional.
Date or Milestone Charges
Milestone 1 – Completion of Project Kickoff $00,000.00
Milestone 2 – Completion of Data Analysis, Mapping and Conversion $00,000.00
Milestone 3 – Completion of Data Verification and Data Review $00,000.00
Milestone 4 –Completion of COPLINK s/w Install, Intermediate Machine
Config and Provision of Data Migrator $00,000.00
Milestone 5 – Completion of Data Refresh Verification $00,000.00
Total Service Charges: $00,000.00
NOTE: Insert ONLY sections that are applicable for this change, and number based on the SOW section numbering.
● NOTE: Include a brief summary below of the effect of this PCR. The text below is for sample
purposes only.
{This PCR will result in {an increase / a decrease} of {$XXX / YY weeks / ZZZ hours / etc.} in the {Estimated
Charges / Estimated Schedule / Estimated Hours / etc.} of the referenced Statement of Work. The revised {Estimated
Charges / Estimated Schedule / Estimated Hours / etc. has / have} been changed to {$XXX / YY weeks / ZZZ hours /
etc.}}
PCR Approval
In entering into this PCR, you are not relying upon any representation made by or on behalf of IBM that is not
specified in the Agreement or the SOW (Exhibit D), including, without limitation, the actual or estimated completion
date, number of hours to provide any of the Services, charges to be paid, or the results of any of the Services to be
provided under the SOW. Each of us agrees that the complete agreement between us about these Services consists of
1) this Project Change Request, 2) the referenced SOW (Exhibit D of the Agreement) including any previous
mutually-approved PCRs, and 3) the Agreement or any equivalent agreement in effect between us as identified
below.

Agreed to: Agreed to:
Customer Name: Maricopa County International Business Machines Corporation
By (Authorized Signature): By (Authorized Signature):
Name (type or print): Name (type or print):
PCR Approval Date: PCR Approval Date:
Referenced Agreement Name:
Competition Impractical
Referenced Agreement Number/Date:
13149-CI
Statement of Work Name:
New Data Source Integration Services
Statement of Work Number/Date:
NKEA-9LVTBN
Customer Address: IBM Phone Number:
IBM Fax Number:
IBM Email:
Example PCR for Annual Data Source Integration Maintenance:
PROJECT CHANGE REQUEST (PCR)
Data Source Integration Maintenance
PCR Requested Date: Requested by: PCR Number:
PCR Proposal Date: Contract Number: 13149-CI
This PCR must be approved by both parties and signed below on or before the offer expiration date before the PCR
can be implemented. This offer will expire on {insert mm/dd/yyyy}, unless extended by IBM in writing. All other
terms in the referenced SOW (see Exhibit C of the Agreement) not affected by this PCR remain in full force and
effect.
● NOTE: Include a listing of the modifications made by this PCR. Remember to track the section
numbering in the referenced SOW so it is clear as to what is being changed/added/deleted.
The parties agree that this PCR modifies the existing referenced Contract as follows:
Contract Reference: 13149-CI
Project Name: MCSO Data Source Integration Maintenance Services
Node Location: Maricopa County Sheriff’s Office – Phoenix, Arizona
Start Date: {Maintenance Period Start Date}
End Date: {Maintenance Period End Date}
Project Costs: IBM will invoice for maintenance services in advance; any applicable tax will be additional.

Contributing Agency Product (Vendor) DS# Period Monthly Extended
& Data Source Name (Mos.) Cost Cost
MCSO JMS Custom 189
MCSO MugShots IWS Law Enforcement 190
MCSO RMS Aegis AS400 192
MCSO Warrants Custom 193
ADOC Corrections Custom 2370
NOTE: Although other agencies contribute data sources to the MCSO COPLINK node, MCSO is only
responsible for maintenance charges for the data sources listed above, and any new data sources which
may be added via PCR.
NOTE: Insert ONLY sections that are applicable for this change, and number based on the SOW section numbering.
● NOTE: Include a brief summary below of the effect of this PCR. The text below is for sample
purposes only.
{This PCR will result in {an increase / a decrease} of {$XXX / YY weeks / ZZZ hours / etc.} in the {Estimated
Charges / Estimated Schedule / Estimated Hours / etc.} of the referenced Statement of Work. The revised
{Estimated Charges / Estimated Schedule / Estimated Hours / etc. has / have} been changed to {$XXX / YY weeks /
ZZZ hours / etc.}}
PCR Approval
In entering into this PCR, you are not relying upon any representation made by or on behalf of IBM that is not
specified in the Agreement or the SOW (Exhibit C), including, without limitation, the actual or estimated completion
date, number of hours to provide any of the Services, charges to be paid, or the results of any of the Services to be
provided under the SOW. Each of us agrees that the complete agreement between us about these Services consists of
1) this Project Change Request, 2) the referenced SOW (Exhibit C of the Agreement) including any previous
mutually-approved PCRs, and 3) the Agreement or any equivalent agreement in effect between us as identified
below.
Agreed to: Agreed to:
Customer Name: Maricopa County International Business Machines Corporation
By (Authorized Signature): By (Authorized Signature):
Name (type or print): Name (type or print):
PCR Approval Date: PCR Approval Date:
Referenced Agreement Name:
Competition Impractical
Referenced Agreement Number/Date:
13149-CI
Statement of Work Name:
Annual Data Source Integration Maintenance
Statement of Work Number/Date:
NKEA-9LVQ9F
Customer Address: IBM Phone Number:
IBM Fax Number:
IBM Email:

IBM SOW# NKEA-9LVQ9F
Exhibit C
Statement of Work – Annual Data Source Integration Maintenance
1.1 Project Scope
Under this Statement of Work (SOW), IBM will provide maintenance and support services for
node and data source integrations within an existing COPLINK node, as listed in a specific
Transaction Document (Project Change Request (PCR) – Data Source Integration Maintenance).
The Transaction Document will be processed in accordance with Exhibit B of the Agreement.
NOTE: Although other agencies contribute data sources to the MCSO COPLINK node, MCSO
is only responsible for maintenance charges for the data sources listed in the specific Transaction
Document.
IBM's estimated charges and schedule are based on performance of the activities listed in the
“IBM Responsibilities” section below. Deviations from the original Transaction Document that
arise during the project will be managed through the procedure described in Appendix A-1:
Project Change Control Procedure, and may result in adjustments to the Project Scope, Estimated
Schedule, Charges and other terms. These adjustments may include charges on a time-and-
materials or fixed-fee basis using IBM’s standard rates in effect from time to time for any
resulting additional work or waiting time.
1.2 Facilities and Hours of Coverage
IBM will:
a. Perform the Services under this SOW for your facility in Phoenix, Arizona. IBM will
perform the work remotely, except for any project-related activity which IBM and MCSO
jointly determine would be best performed at your facility in order that IBM can
complete its responsibilities under this SOW. Travel costs of IBM personnel will be
billable in accordance with agreed upon travel reimbursement policies.
b. Provide the Services under this SOW during normal business hours, 8:00 AM to 5:00
PM, MST, Monday through Friday, except holidays. If necessary, you will provide after-
hours access to your facilities to IBM personnel. Out-of-town personnel may work hours
other than those defined as normal business hours to accommodate their travel schedules.
1.3 IBM Responsibilities
Under this SOW, IBM will undertake the following activities:
Activity 1 - Annual Integration Maintenance and Support Services for Contributing Data
Sources
The purpose of this activity is to provide support to MCSO for the data sources listed in the
COPLINK Node, as specified in the specific Transaction Document (PCR).
IBM will:
a. Provide telephone and email support Monday through Friday, 8:00am-5:00pm MST to
MCSO’s authorized representatives for questions and issues regarding the COPLINK
Data Sources. Telephone number and email address to be provided separately.
b. Provide a tracking number in response to initial issue reports.

IBM SOW# NKEA-9LVQ9F
c. Promptly respond with an initial assessment and a resolution plan, to include an estimated
resolution date, for reported issues.
d. Resolve any valid, in-scope issue reported by MCSO or found by IBM to be a defect in
(1) the integration services originally rendered Provide a final resolution report as part of
the close-out process for all reported issues in accordance with Appendix B.
e. Monitor the ongoing status of the servers, databases, file systems, and processes that
constitute the COPLINK node/warehouse to facilitate early identification and resolution
of operational issues and monitor the throughput rate and various data statistics to
facilitate early identification and resolution of operational issues, under the terms of this
SOW.
f. Provide up to ten (10) hours of support toward:
(1) The modification of a data source integration, when (1) those modifications are
necessary as the result of changes to (but not replacement of) MCSO’s data source
product and (2) the modifications are within scope of the original data source
integration. Extraordinary data access control requests, e.g. the deletion of a
document from the COPLINK warehouse in response to a court-ordered
expungement.
The following are excluded from annual support provided by IBM:
a. Any support of the COPLINK software (this support is provided to MCSO by IBM under
separate license and maintenance agreements).
b. Modifications to a data source integration made necessary if the data source product is
moved from one database platform to another.
c. Modifications to a data source integration that is deemed outside the scope of the original
data source integration.
d. Modifications to data source integrations, the node/warehouse, the overall solution
architecture, or any other artifact resulting from services, if modifications are necessary
as a result of (i) MCSO error or oversight at the time services were rendered, or (ii) new
MCSO requirements determined after services were completed.
e. Recovery from catastrophic failure of hardware and/or third-party software.
f. Corrective actions necessitated by bulk operations performed on a data source (e.g.
rewriting all beat codes on crime reports to align with a new jurisdictional breakdown)
without prior notification to and coordination with IBM.
g. Issues resulting from down time or incorrect operation of data sources.
h. Issues related to any third party hardware or software.
i. Any third party vendor maintenance charges.
j. Bulk deletion of data from the COPLINK warehouse.
Completion Criteria:
This activity will be considered complete when the End Date specified in the Transaction
Document has been reached.
Deliverable Materials:
● Initial Assessment, Proposed Resolution Plan, and Final Resolution for reported issues in
accordance with Appendix B.

IBM SOW# NKEA-9LVQ9F
1.4 Your Responsibilities
The completion of this scope of work depends on the full commitment and participation of your
management and personnel. The responsibilities listed in this section are in addition to those
responsibilities specified in the Agreement, and are to be provided at no charge to IBM. You are
required to perform your obligations in the Agreement and this SOW without exception. IBM's
performance is predicated upon the following responsibilities being managed and fulfilled by
you. Delays in performance of these responsibilities may result in additional cost and/or delay of
the completion of the project, and will be handled in accordance with Appendix A-1: Project
Change Control Procedure.
1.4.1 Your Project Manager
Prior to the start of this project, you will designate a person called your Project Manager who will
be the focal point for IBM communications relative to this project and will have the authority to
act on behalf of you in all matters regarding this project.
Your Project Manager's responsibilities include the following:
a. Manage your personnel and responsibilities for this project;
b. Serve as the interface between IBM and all your departments participating in the project;
c. Administer the Project Change Control Procedure with IBM;
d. Obtain and provide information, data, and decisions within three working days of IBM's
request unless you and IBM agree in writing to a different response time;
e. Help resolve project issues and escalate issues within your organization, as necessary;
f. Review with IBM any of your invoice or billing requirements; and
1.4.2 Your Other Responsibilities
You will:
a. Provide IBM and its personnel with suitable office space, and other accommodations and
facilities that IBM may reasonably require to perform the Services, but only in the event
that IBM and MCSO mutually agree that on-site services are required. In particular,
supplies, furniture, computer facilities, telephone/fax communications, and high speed
internet connectivity will be provided for IBM personnel while working on this project.
The IBM project team will be located in an area adjacent to your subject matter experts
and technical personnel, and all necessary security badges and clearance will be provided
for access to this area. A lockable cabinet will be provided to IBM personnel in
accordance with your security procedures. You will be responsible for ensuring that you
have appropriate backup, security and virus-checking procedures in place for any
computer facilities you provide or which may be affected by the Services;
b. Supply all prerequisite hardware and software to be used during the performance of this
SOW. This does not include any hardware or software normally used by IBM
consultants in the performance of their day-to-day responsibilities with IBM;
c. Ensure that your staff is available to provide such assistance as IBM reasonably requires
and that IBM is given reasonable access to your senior management, as well as any
members of your staff to enable IBM to provide the Services. You will ensure that your
staff has the appropriate skills and experience. If any of your staff fails to perform as
required, you will make suitable additional or alternative staff available;

IBM SOW# NKEA-9LVQ9F
d. If making available any facilities, software, hardware or other resources, obtain any
licenses or approvals related to these resources that may be necessary for IBM and its
subcontractors to perform the Services. IBM will be relieved of its obligations that are
adversely affected by your failure to promptly obtain such licenses or approvals. You
agree to reimburse IBM for any reasonable costs and other amounts, including costs of
litigation and settlements, that IBM may incur from your failure to obtain these licenses
or approvals;
e. Provide all information and materials reasonably required to enable IBM to provide the
Services. You agree that all information disclosed or to be disclosed to IBM is and will
be true, accurate and not misleading in any material respect. IBM will not be responsible
for any loss, damage, delay, or deficiency arising from inaccurate, incomplete, or
otherwise defective information or materials supplied by you or your representative;
f. If you are employing other suppliers whose work may affect IBM’s ability to provide the
Services, unless specifically agreed to otherwise in writing, you will be responsible for
the management of the third parties and the quality of their input and work. Except to the
extent IBM specifically agrees otherwise in this SOW, you are solely responsible for any
third party hardware, software or communications equipment used in connection with the
Services;
g. Make final selection of solution and technical architectures;
h. Be responsible for the identification of, interpretation of, and compliance with, any
applicable laws, regulations, and statutes that affect your existing systems, applications,
programs, or data to which IBM will have access during the Services, including
applicable data privacy, export, import laws and regulations, and product safety and
regulatory compliance for non-IBM products including those recommended by IBM.
You are solely responsible for obtaining advice of competent legal counsel as to the
identification and interpretation of any relevant laws, rules and regulations that may
affect your business and any actions you may need to take to comply with such laws.
IBM makes no representations or warranties with respect to product safety or regulatory
compliance of non-IBM products;
i. Agree that IBM may process the business contact information of your employees and
contractors and information about you as a legal entity (contact information) in
connection with IBM Products and Services or in furtherance of IBM’s business
relationship with you. This contact information can be stored, disclosed internally and
processed by International Business Machines Corporation solely for the purpose
described above provided that IBM complies with applicable data privacy laws related to
this processing. Where required by applicable law, you have notified and obtained the
consent of the individuals whose contact information may be stored, disclosed internally
and processed, and will forward their requests to access, update, correct or delete their
contact information to IBM who will then comply with those requests;
j. Be responsible for i) any data and the content of any database you make available to IBM
in connection with a Service, ii) the selection and implementation of procedures and
controls regarding access, security, encryption, use, and transmission of data, and iii)
backup and recovery and integrity of the database and any stored data. This security will
also include any procedures necessary to safeguard the integrity and security of software
and data used in the Services from access by unauthorized personnel.
k. Designate up to three (3) representatives authorized to contact IBM with questions
regarding COPLINK Data Sources during the annual support period.

IBM SOW# NKEA-9LVQ9F
l. Provide a VPN and remote desktop access to hardware comprising the COPLINK
solution so that IBM can monitor and maintain the data sources as described in this SOW.
m. Keep the third party hardware and software used for the COPLINK node current with any
fixes and upgrades during the period of annual support.
n. Schedule (1) Geographic Information System (“GIS”) map updates, (2) Lookup updates,
(3) node upgrades with IBM.
o. Notify IBM of bulk operations to be performed on data sources.
p. Acknowledge that:
(1) Some or all data sources may require purchasing tools or interfaces from the Vendor
of the product. MCSO is responsible for purchasing those if necessary.
q. If IBM requires access to your production systems, provide the required hardware (either
an assigned desktop or laptop system) for such access. Any hardware provided for this
access will be secured at your location when not in use by IBM.
1.5 Deliverable Materials
IBM will provide you with the tangible Materials listed in Appendix B.
1.6 Completion Criteria
IBM will have fulfilled its obligations under this SOW when one of the following first occurs:
a. IBM accomplishes the activities set forth in the “IBM Responsibilities” section and
approval/acceptance by your Project Manager of the Materials listed in Appendix B, if
any; or
b. You or IBM terminates the project in accordance with the provisions of the Agreement.
1.7 Maintenance Period Schedule
The Services will be provided between start and end dates to be mutually agreed to between you
and IBM. These dates will be specified in the Transaction Document.
1.8 Charges
The Services will be conducted on a fixed price basis. The fixed price for performing the
Services defined in this SOW will be the current year percentage listed in Exhibit A of the
original cost for integration of the data sources listed in the Transaction Document and/or any
applicable sales taxes. This fixed price is exclusive of any travel and living expenses and other
reasonable expenses incurred in connection with the Services. All charges listed are exclusive of
any applicable taxes.
Because the services will be performed remotely, IBM does not expect to incur and travel and
living expenses associated with this engagement.
From time to time, IBM and MCSO may contract to add new data sources to the MCSO
COPLINK node using agreed upon Project Change Request procedures specified in Exhibit B of
the Agreement – Transaction Document Process. At the next annual maintenance renewal,
MCSO agrees to pay IBM for annual support services charges associated with the new data
source, plus any support amount owing, pro-rated monthly, for the newly added data source since
acceptance.
IBM will invoice you for the full amount due for the annual support period, including any pro-
rated amounts due through the end of the current support period, plus applicable taxes, and other

IBM SOW# NKEA-9LVQ9F
reasonable expenses incurred in connection with the Services 30 days prior to the start of the
support period or upon receipt of the signed Transaction Document (PRC), whichever is later.
Payment is due upon receipt of an acceptable invoice and is payable within 30 days. Payment
may be made electronically to an account specified by IBM or by other means agreed to by the
parties. In the event of late payment, IBM reserves the right to suspend the provision of Services.
IBM will invoice you for the Services performed in accordance with the original Transaction
Document and/or subsequent PCR, plus applicable taxes, travel and living expenses, and other
reasonable expenses incurred in connection with the Services.
Any different or added terms contained in any PO or other ordering documents that might be
exchanged in relation to activities under this SOW will not be applicable or of any effect. At its
sole discretion, IBM may elect to begin delivery of Services after SOW signing, but prior to
receipt of PO or PO waiver, on a limited, case-by-case basis.
1.9 Additional Terms and Conditions
1.9.1 Confidential Information
Notwithstanding anything to the contrary in the Agreement, the parties hereto agree that the IBM
Agreement for the Exchange of Confidential Information (“AECI”) shall govern the obligations
and rights of the parties with respect to any Information (as defined in the AECI) exchanged
between the parties during the term of this SOW and each specific Data Source project. The
AECI is incorporated into, and subject to, this SOW, and is located at:
http://www-05.ibm.com/support/operations/files/pdf/aeci_us.pdf
(which location may be changed from time to time). The terms of this SOW and each specific
Data Source project shall be considered confidential information under the AECI.

IBM SOW# NKEA-9LVQ9F
Appendix A: Project Procedures
A – 1: Project Change Control Procedure
A Transaction Document (PCR) will be initiated for each annual maintenance renewal period as
outlined in Exhibit B of the Agreement. The following process will be followed if a change to an
existing Transaction Document is required:
a. A Project Change Request (PCR) will be the vehicle for communicating change. The
PCR must describe the change, the rationale for the change and the effect the change will
have on the project.
b. The designated Project Manager of the requesting party will review the proposed change
and determine whether to submit the request to the other party.
c. Both Project Managers will review the proposed change and agree to implement it,
recommend it for further investigation, or reject it.
d. IBM will specify any charges for such investigation. A PCR must be signed by
authorized representatives from both parties to authorize investigation of the
recommended changes. IBM will invoice you for any such charges per the terms of this
SOW and the Agreement. The investigation will determine the effect that the
implementation of the PCR will have on price, schedule and other terms and conditions
of this SOW and the Agreement.
e. A PCR must be accepted by authorized representatives from both parties to authorize
implementation of any agreed changes to the SOW and the Agreement. Until a change is
agreed to, both parties will continue to act in accordance with the latest agreed version of
the SOW.
f. A PCR that has been signed by authorized representatives from both parties constitutes a
change authorization for purposes of this SOW and the Agreement.
A – 2: Service Level Agreement (SLA)
The following defines the service level agreement for annual node and data source integration
services to be provided by IBM:
a. Hours of Technical Support: Ordinary Technical support for the COPLINK system is
available on regular business days (Monday through Friday, holidays excepted,) from 8:00
am to 5:00 pm, Mountain Standard Time. NOTE: Arizona does not switch to Daylight
Savings Time.
b. Method of contacting IBM: The Customer will identify not more than three (3) staff
members from each organization participating in the project who have the authority to make
requests for technical support. One alternate person may be appointed who shall have the
authority to contact technical support in the absence of or unavailability of the regular contact
persons.
c. Methods of Reporting Technical Support Issues: Customer may report technical support
issues by:
a. Telephone call to the Technical Support Center and Entry of PMR or

IBM SOW# NKEA-9LVQ9F
b. Entry of a PMR (Problem Management Record) into IBM’s COPLINK service portal
c. In-person reporting to a IBM technical support advisor, followed up by a PMR entry
in IBM’s COPLINK service portal
d. Submission of a Transaction Document (PCR) for a Data Source Integration Project
Change Request
d. Problem Description: IBM technical support personnel will log the technical support call
and request sufficient information to determine exactly what type of problem is being
reported.
e. Problem Determination: IBM will respond within the Targeted Response times according
to Table f below to all requests for technical support with a plan outlining the process IBM
intends to follow to resolve the problem. IBM classifies reported problems as one of four
levels. Severity Levels are detailed below:
a. Severity Level 1 (Critical Problem) – The System is unavailable, resulting in a critical
impact to operations that requires fast resolution.
b. Severity Level 2 (Major Problem) – Designated users can access the System; however
material functions are not available.
c. Severity Level 3 (Minor Problem) – Designated users can access the System, and one or
more of the less important functions are not available resulting in a minor impact.
d. Severity Level 4 (Minor Problem/Enhancement Request) – The impact is insignificant to
users, and/or the Parties agree that problem resolution will require new functionality or an
enhancement to be made at a mutually agreed upon date.
f. Problem Severity Level and Mitigation Procedures: The description of the Problem
Severity Level is found in the following table, along with the mitigation procedure.
Severity Target Response Time Frequency of Report on
Level during normal business Issue Status
hours
1 1 Hour Hourly
2 4 Hours Daily
3 1 Day Weekly
4 2 Days Monthly
g. Problem Resolution: Upon determination that the technical support issue is a program code
error, IBM will so report to the Customer and present a mitigation strategy to resolve the
problem along with a tentative time line for problem resolution.
h. Report to Customer: Upon resolution of the technical support issue IBM will provide the
Customer with a synopsis of the issue, the findings of the IBM technical support staff and the
final resolution of the problem.

IBM SOW# NKEA-9LVQ9F
A – 3: Escalation Procedures
The following procedures will be followed to resolve a conflict arising during the performance of
this SOW and/or a Transaction Document (PCR).
a. When a conflict arises between you and IBM, the project team member(s) will first strive
to work out the problem internally.
b. Level 1: If the project team cannot resolve the conflict within two working days, your
Project Manager and the IBM Project Manager will meet to resolve the issue.
c. Level 2: If the conflict is not resolved within three working days after being escalated to
Level 1, your Executive Sponsor will meet with the IBM Project Executive to resolve the
issue.
d. If the conflict is resolved by either Level 1 or Level 2 intervention, the resolution will be
addressed in accordance with the Project Change Control Procedure set forth in Appendix
A-1.
e. If the conflict remains unresolved after Level 2 intervention, then either party may
terminate the annual maintenance Transaction Document. If the conflict is addressed by
termination, you agree to pay IBM as described in the “Termination” section of the
Agreement.
f. During any conflict resolution, IBM agrees to provide Services relating to items not in
dispute, to the extent practicable pending resolution of the conflict. You agree to pay
invoices per the specific annual maintenance Transaction Document and the Agreement.

IBM SOW# NKEA-9LVQ9F
Appendix B: Materials
B – 1: Initial Assessment of Reported Issues
Purpose:
To outline the initial assessment of a reported issue.
Content:
Written description of the issue, technical assessment of the issue, and an estimated date of
resolution for the issue. If the reported issue is determined by IBM to be out-of-scope, IBM will
respond to MCSO with a description of the issue and why it is believed to be out-of-scope.
Delivery:
IBM will deliver one (1) copy of this document in softcopy format via email and in a trouble
ticket accessible by MCSO through IBM’s COPLINK Portal.
B – 2: Proposed Resolution Plan for Reported Issues
Purpose:
To outline the proposed resolution for a valid, in-scope issue.
Content:
Written description of the proposed resolution of the issue and the timeline for implementation.
Delivery:
IBM will deliver one (1) copy of this document in softcopy format via email and in a trouble
ticket accessible by MCSO through IBM’s COPLINK Portal.
B – 3: Final Resolution of Reported Issues
Purpose:
To document final resolution of a reported issue as part of the close-out process.
Content:
Written description of the issue and its final resolution, including the date implemented and final
disposition of the trouble ticket.
Delivery:
IBM will deliver one (1) copy of this document in softcopy format via email or in a trouble ticket
accessible by MCSO.

IBM SOW# NKEA-9LVTBN
EXHIBIT D
Statement of Work (SOW) – New Data Source Integration Services
Standard Terms, Conditions and Procedures
1.1 Project Scope
Under this Statement of Work (SOW), IBM will integrate the data source(s) listed in a specific
Transaction Document (Project Change Request (PCR) – Data Source Integration Services) into
an existing COPLINK node. The Transaction Document will be processed in accordance with
Exhibit B of the Agreement.
IBM's estimated charges and schedule are based on performance of the activities listed in the
“IBM Responsibilities” section below. Deviations from the original Transaction Document that
arise during the project will be managed through the procedure described in Appendix A-1:
Project Change Control Procedure, and may result in adjustments to the Project Scope, Estimated
Schedule, Charges and other terms. These adjustments may include charges on a time-and-
materials or fixed-fee basis using IBM’s standard rates in effect from time to time for any
resulting additional work or waiting time.
IBM and you will each comply with applicable export and import laws and regulations, including
those of the United States that prohibit or limit export for certain uses or to certain end users, and
each party will cooperate with the other by providing all necessary information to the other, as
needed for compliance. Each party will provide the other with advance written notice prior to
providing the other party with access to data requiring an export license.
1.2 Definitions
● “Hosting Agency” means the agency hosting the COPLINK node.
● “Contributing Agency” means an organization (e.g., a police department) that contributes
a specific Data Source to a COPLINK node.
● “Indirectly Contributing Agency” means a smaller law enforcement entity that includes
their Data Source information with the Data Source information of a Contributing
Agency.
● “Participating Agency” means an organization (e.g., a police department) that has access
to a COPLINK node, but the entity does not contribute Data Source information to the
node.
● “Agency” means either the Hosting Agency, the Contributing Agency or any
Participating Agency. An agency can be a Hosting Agency, a Contributing Agency, or
both. Most Agencies are law enforcement organizations, but not all.
● “COPLINK Node” means the Maricopa County Sheriff’s Office COPLINK Node.
● “Data Source” means the Agency’s information database to be integrated into the
COPLINK node.
● “COPLINK Database” is a warehouse in the COPLINK data model, containing the
converted data from one or more Contributing Agencies, resulting from the integration
and migration services performed by IBM.
● “Data Set” is a unit of scope identifying a subset of the information to be migrated from a
Data Source to the COPLINK Database.
● “Data Verification” means the review with the Contributing Agency to present how the
Data Source information was mapped into COPLINK and to identify any issues
associated with that mapping.

IBM SOW# NKEA-9LVTBN
● “Data Review” means the review with the Contributing Agency to present the resolution
of issues identified during Data Verification.
● “Refresh Verification” means the verification by the Contributing Agency that changes to
the Data Source information are reflected within the COPLINK Node.
1.3 Facilities and Hours of Coverage
IBM will:
a. Perform the Services under this SOW for your facility in Phoenix, AZ. IBM will perform
the work remotely, except for any project-related activity which IBM and MCSO or the
Contributing Agency jointly determine would be best performed at the specified facility
in order that IBM can complete its responsibilities under this SOW. Travel costs of IBM
personnel will be billable in accordance with agreed upon travel reimbursement policies.
b. Provide the Services under this SOW during normal business hours, 8:00 AM to 5:00
PM, MST, Monday through Friday, except holidays unless otherwise arranged and
agreed to by both parties. You agree to provide after-hours access to your facilities to
IBM personnel, if deemed necessary to meet project goals or travel schedules. Out-of-
town personnel may work hours other than those defined as normal business hours to
accommodate their travel schedules.
1.4 IBM Responsibilities
Under this SOW, IBM will provide services to perform the following activities:
Activity 1 - Project Management
IBM will provide project management for the IBM responsibilities in this SOW. The purpose of
this activity is to provide technical direction and control of IBM project personnel and to provide
a framework for project planning, communications, reporting, procedural and contractual activity.
This activity is composed of the following tasks:
Planning
IBM will:
a. Review the SOW and the contractual responsibilities of both parties with your Project
Manager;
b. Maintain project communications through your Project Manager;
c. Coordinate the establishment of the project environment;
d. Establish documentation and procedural standards for deliverable Materials;
e. Assist your Project Manager to prepare and maintain the project plan for the performance
of this SOW which will include the activities, tasks, assignments, milestones and
estimates; and
f. Review with you the hardware required for the performance of this SOW.
Project Tracking and Reporting
IBM will:
a. Review project tasks, schedules, and resources and make changes or additions, as
appropriate. Measure and evaluate progress against the project plan with your Project
Manager;
b. Review the IBM standard invoice format and billing procedure to be used on the project,
with your Project Manager;

IBM SOW# NKEA-9LVTBN
c. Work with your Project Manager to address and resolve deviations from the project plan;
d. Attend regularly scheduled project status meetings;
e. Administer the Project Change Control Procedure with your Project Manager; and
f. Coordinate and manage the technical activities of IBM project personnel.
Completion Criteria:
This is an ongoing activity which will be considered complete at the end of the Services.
Deliverable Materials:
● Status Reports
Activity 2 - Project Kickoff
The purpose of this activity is to facilitate a high-level project kickoff meeting for MCSO and/or
Contributing Agency participants for up to two (2) hours at a mutually agreed date and time.
Under this activity, IBM will perform Services which include the following tasks:
a. Introduce the project participants and Agencies;
b. Discuss project team roles and responsibilities;
c. Review the Services objectives;
d. Provide an overview of the project methodology;
e. Provide MCSO with a technical questionnaire/checklist packet to be completed by the
Contributing Agency, as listed in Appendix B-2;
f. Review the MCSO and/or Contributing Agency environment;
g. Develop a preliminary schedule of activities; and
h. Initiate the Services.
Completion Criteria:
This activity will be considered complete when IBM has conducted the project kickoff meeting.
Deliverable Materials:
● Technical Questionnaire/Checklist
● Sample Memorandum of Understanding, if required
● High-level Timeline
Activity 3 - Intermediate Machine Configuration and Testing
The purpose of this activity is to provide and configure certain hardware and software.
IBM will:
a. Remotely install and configure the third-party SQL server software listed in Appendix D.
b. Perform a System Test to validate that the hardware and software is ready for Data
Migration.
Completion Criteria:
This activity will be considered complete when IBM has installed and tested the Intermediary
Server, validating that the software installation is complete and that the server is on line and ready
for use.

IBM SOW# NKEA-9LVTBN
Deliverable Materials:
● System Test Report confirming Data Migration readiness
Activity 4 - Provide Data Migrator
In this activity, IBM will provide the Data Migrator to MCSO on IBM-designated machines.
Delivery Location: IBM will deliver the Data Migrator electronically to the location specified by
MCSO. IBM personnel will install and configure Data Migrator on the intermediate machine
described in Appendix D; it may not be deployed elsewhere.
Open Source Software: Data Migrator may include open source software (“OSS”), which is not
licensed by IBM. Your use of that OSS in connection with Data Migrator is subject to any and all
requirements specified by the licenses of those open source materials. These licenses are detailed
in the NOTICES.txt file included with Data Migrator.
Completion Criteria:
This activity will be complete when IBM has installed and configured Data Migrator as described
above.
Deliverable Materials:
● None
Activity 5 - Data Analysis, Mapping, and Conversion
The purpose of this activity is to extract information from the Contributing Agency Data Source
and migrate and integrate that data to create the COPLINK Database within the COPLINK Node.
IBM will:
a. Provide the Contributing Agency with a data storage device (encrypted USB drives) onto
which the Agency may download their Data Source information before returning to IBM.
b. Provide an interface to connect to the vendor database on which the Agency Data Source
information resides to provide access to such information.
c. Transfer the Contributing Agency’s Data Source information and Data Source database
structures from the data storage device to IBM servers.
d. Verify and analyze the transferred Agency Data Source information and Data Source
database structures.
e. Perform limited data cleaning. This data cleaning includes common “cleaning” functions
such as standardizing record styles for names, addresses, criminal code and crime types.
f. Data Cleaning does not include more intensive data restoration, to correct incomplete or
incorrect records in the Data Source, or to standardize name, address or other data
included in narrative reports. Intensive data restoration may be undertaken at the
Contributing Agency’s request as additional work scope and at an additional charge, but
will not be included under this SOW.
g. Map the Agency Data Source information to the COPLINK Database, including the
mapping of Agency data codes to COPLINK Database codes.
h. Standardize and consolidate the Agency Data Source information into a Data Set to be
stored in the COPLINK Database.
i. Migrate the Agency Data Source information, including the Data Set, Document
Description, and Entity Description information, as listed in the tables in Appendix C,
into the COPLINK Database.

IBM SOW# NKEA-9LVTBN
Completion Criteria:
This activity will be considered complete when IBM has migrated the Agency Data Source
information into the COPLINK Database.
Deliverable Materials:
● None
Activity 6 - Data Verification and Data Review
The purpose of this activity is to validate and correct the Agency Data Source information that
has been migrated into the COPLINK Database.
IBM will:
a. Select a sample set of documents from the Agency Data Source information, as
determined by IBM with input from the Contributing Agency, to review and validate the
conversion of the Agency Data Source information into the COPLINK Database.
b. Conduct, with assistance from the Contributing Agency, a side-by-side, field-by-field
comparison of the selected sample set of documents, comparing the original documents
from the Agency Data Source to those same documents migrated into the COPLINK
Database.
c. Document any issues found as a “Blocking” issue or a “Non-blocking” issue and provide
a tracking number for each issue found. A “Blocking” issue is one that will be resolved
or a workaround provided prior to Data Verification. A “Non-blocking” issue is one that
does not have to be resolved prior to Data Verification.
d. Resolve or provide a workaround for the identified Blocking issues.
e. Present the issue resolutions to the Contributing Agency.
f. Provide Data Verification form to the Contributing Agency for sign-off.
Completion Criteria:
This activity will be considered complete when your Project Manager has approved the Data
Verification form provided by IBM.
Deliverable Materials:
● Data Verification Form
Activity 7 - Data Refresh Verification
The purpose of this activity is to validate the issue resolutions and corrections to the COPLINK
Database after Data Verification.
IBM will:
a. Load a subset of the COPLINK Database in a test environment at the COPLINK Node.
b. Refresh the subset of COPLINK Database from the validated Agency Data Source
information.
c. Verify the refresh operation within the COPLINK Database with the Agency
representative.
d. Address any remaining Non-blocking issues, unless otherwise agreed.
e. Provide Data Refresh Verification form to the Contributing Agency for sign-off.

IBM SOW# NKEA-9LVTBN
Completion Criteria:
This activity will be considered complete when your Project Manager has approved the Data
Refresh Verification form provided by IBM.
Deliverable Materials:
● Data Refresh Verification Form
1.5 Your Responsibilities
The completion of the proposed scope of work depends on the full commitment and participation
of your management and personnel. The responsibilities listed in this section are in addition to
those responsibilities specified in the Agreement, and are to be provided at no charge to IBM.
You are required to perform your obligations in the Agreement and this SOW without exception.
IBM's performance is predicated upon the following responsibilities being managed and fulfilled
by you. Delays in performance of these responsibilities may result in additional cost and/or delay
of the completion of the project, and will be handled in accordance with Appendix A-1: Project
Change Control Procedure.
1.5.1 Your Project Manager
Prior to the start of this project, you will designate a person called your Project Manager who will
be the focal point for IBM communications relative to this project and will have the authority to
act on behalf of you in all matters regarding this project.
Your Project Manager's responsibilities include the following:
a. Manage your personnel and responsibilities for this project;
b. Serve as the interface between IBM and all your departments participating in the project;
c. Administer the Project Change Control Procedure with the IBM Project Manager;
d. Participate in project status meetings;
e. Obtain and provide information, data, and decisions within three working days of IBM's
request unless you and IBM agree in writing to a different response time;
f. Resolve deviations from the estimated schedule, which may be caused by you;
g. Help resolve project issues and escalate issues within your organization, as necessary;
h. Review with the IBM Project Manager any of your invoice or billing requirements. Such
requirements that deviate from IBM's standard invoice format or billing procedures may
have an effect on price, and will be managed through the Project Change Control
Procedure in Appendix A-1; and
i. Create, with IBM's assistance, the project plan for the performance of this SOW which
will include the activities, tasks, assignments, milestones and estimates.
1.5.2 Your Other Responsibilities
You will:
a. Provide IBM and its personnel with suitable office space, and other accommodations and
facilities that IBM may reasonably require to perform the Services, but only in the event
that IBM and MCSO and/or the Contributing Agency mutually agreed that on-site
services are required. In particular, supplies, furniture, computer facilities, telephone/fax
communications, and high speed internet connectivity will be provided for IBM
personnel while working on-site for the project. The IBM project team will be located in
an area adjacent to your subject matter experts and/or technical personnel, and all
necessary security badges and clearance will be provided for access to this area. A
lockable cabinet will be provided to IBM personnel in accordance with your security

IBM SOW# NKEA-9LVTBN
procedures. You will be responsible for ensuring that you have appropriate backup,
security and virus-checking procedures in place for any computer facilities you provide
or which may be affected by the Services;
b. Supply all prerequisite hardware and software to be used during the performance of this
SOW. This does not include any hardware or software normally used by IBM
consultants in the performance of their day-to-day responsibilities with IBM;
c. Ensure that your staff is available to provide such assistance as IBM reasonably requires
and that IBM is given reasonable access to your senior management, as well as any
members of your staff to enable IBM to provide the Services. You will ensure that your
staff has the appropriate skills and experience. If any of your staff fails to perform as
required, you will make suitable additional or alternative staff available;
d. If making available any facilities, software, hardware or other resources, obtain any
licenses or approvals related to these resources that may be necessary for IBM and its
subcontractors to perform the Services. IBM will be relieved of its obligations that are
adversely affected by your failure to promptly obtain such licenses or approvals. You
agree to reimburse IBM for any reasonable costs and other amounts, including costs of
litigation and settlements, that IBM may incur from your failure to obtain these licenses
or approvals;
e. Provide all information and materials reasonably required to enable IBM to provide the
Services. You agree that all information disclosed or to be disclosed to IBM is and will
be true, accurate and not misleading in any material respect. IBM will not be responsible
for any loss, damage, delay, or deficiency arising from inaccurate, incomplete, or
otherwise defective information or materials supplied by you or your representative;
f. If you are employing other suppliers whose work may affect IBM’s ability to provide the
Services, unless specifically agreed to otherwise in writing, you will be responsible for
the management of the third parties and the quality of their input and work. Except to the
extent IBM specifically agrees otherwise in this SOW, you are solely responsible for any
third party hardware, software or communications equipment used in connection with the
Services;
g. Make final selection of solution and technical architectures;
h. Be responsible for the identification of, interpretation of, and compliance with, any
applicable laws, regulations, and statutes that affect your existing systems, applications,
programs, or data to which IBM will have access during the Services, including
applicable data privacy, export, import laws and regulations, and product safety and
regulatory compliance for non-IBM products including those recommended by IBM.
You are solely responsible for obtaining advice of competent legal counsel as to the
identification and interpretation of any relevant laws, rules and regulations that may
affect your business and any actions you may need to take to comply with such laws.
IBM makes no representations or warranties with respect to product safety or regulatory
compliance of non-IBM products;
i. Agree that IBM may process the business contact information of your employees and
contractors and information about you as a legal entity (contact information) in
connection with IBM Products and Services or in furtherance of IBM’s business
relationship with you. This contact information can be stored, disclosed internally and
processed by International Business Machines Corporation solely for the purpose
described above provided that IBM complies with applicable data privacy laws related to
this processing. Where required by applicable law, you have notified and obtained the
consent of the individuals whose contact information may be stored, disclosed internally
and processed and will forward their requests to access, update, correct or delete their
contact information to IBM who will then comply with those requests;

IBM SOW# NKEA-9LVTBN
j. Be responsible for i) any data and the content of any database you make available to IBM
in connection with a Service, ii) the selection and implementation of procedures and
controls regarding access, security, encryption, use, and transmission of data, and iii)
backup and recovery and integrity of the database and any stored data. This security will
also include any procedures necessary to safeguard the integrity and security of software
and data used in the Services from access by unauthorized personnel;
k. Assign the following personnel for each Client Agency responsible for making decisions
regarding the Agency Data Source information during the project kickoff meeting and the
Data Verification and Data Review activities:
(1) A command level decision maker
(2) A records department administrator
(3) A sworn law enforcement officer, who will also be a user of the COPLINK Node.
l. Protect the Data Migrator from any access not authorized in this SOW and ensure that its
use is limited to the services described in this SOW.
m. Meet the following prerequisites prior to the start of the IBM Services under this SOW:
(1) Provide connectivity and remote access, via a VPN or other secure dialup access, to
the COPLINK Node to be used by IBM for installation, testing and support purposes.
(2) Provide a data network connection employing TCP/IP between all participating
agencies, including the Hosting Agency and those listed in the Transaction
Document.
(3) Provide the required floor space, rack space and facilities (including power; lighting;
and connectivity) for the hardware to be installed for the Services under this SOW.
(4) Provide the hardware and software listed in Appendix D.
(5) Install and configure the hardware required for the Data Migrator, as specified in
Appendix D.
(6) With the exception of SQL software, install and configure the software required for
the Data Migrator, as specified in Appendix D.
n. The following responsibilities apply to the Intermediate Machine Configuration and
Testing. MCSO and/or the Contributing Agency will:
(1) Install any hardware required by this project.
o. The following responsibilities apply to the Data Analysis, Mapping and Conversion.
MCSO and/or the Contributing Agency will:
(1) Prior to the start of the data analysis, mapping and conversion activity, provide the
following to IBM for each vendor database product containing the Agency Data
Source information:
(a) return the completed technical questionnaire/checklist packet from each
participating Agency to IBM;
(b) database backup data (historical load) for the Agency Data Source information
database;
(c) a second database backup upon request (at least one month after the first
historical load is provided); and
(d) the Geographic Information System (“GIS”) map shape files for geo-coding.
(2) If MCSO and/or the Contributing Agency cannot meet the responsibilities listed
above for an Agency Data Source database within 30 days of the kick off meeting,
IBM reserves the right to remove that Agency Data Source database from the
Participating Agency table. IBM will bill for all work completed up to the most
recently stamped milestone.

IBM SOW# NKEA-9LVTBN
(3) Ensure that all Agency Data Source databases are using a currently supported version
of the database and that all Agency Data Source databases are kept current with
support and maintenance. Unsupported or down-level Agency Data Source database
will not be included in the data analysis, mapping and conversion activity under this
SOW.
(4) Require each Contributing Agency to either (i) copy the Data Source information to
an encrypted data storage device provided by IBM and ship the data storage device to
IBM, or (ii) send a copy of the Data Source information to IBM via SFTP (Secure
FTP).
p. The following responsibilities apply to the Data Verification and Data Review. MCSO
and/or the Contributing Agency will:
(1) Assist IBM as required with the side-by-side, field-by-field comparison of the
selected sample set of documents, comparing the original documents from the
Agency Data Source to those same documents migrated into the COPLINK
Database.
(2) Make staff available for the data verification and review sessions within 48 hours of
completion of the migration activity. IBM will have the right to invoice for this step
and continue with the remainder of the project, if the resources are not made
available within the time frame specified.
(3) Provide the completed, signed Data Verification form to IBM upon acceptance.
q. The following responsibilities apply to the Data Refresh Verification. MCSO and/or the
Contributing Agency will:
(1) Assist IBM as required with the data refresh activity.
(2) Provide the completed, signed Data Refresh Verification form to IBM upon
acceptance.
r. Acknowledge that:
(1) IBM reserves the right to subcontract services to technically qualified Consultants.
(2) Some or all data sources may require purchasing tools or interfaces from the Vendor
of the product. MCSO is responsible for purchasing those if necessary.
s. If IBM requires access to your production systems, provide the required hardware (such
as an assigned desktop or laptop system) for such access. Any hardware provided for this
access will be secured at your location when not in use by IBM.
1.6 Deliverable Materials
IBM will provide you with the tangible Materials listed in Appendix B.
1.7 Completion Criteria
IBM will have fulfilled its obligations under this SOW for a specific Data Source project when
one of the following first occurs:
a. IBM completes all of the milestones detailed in the individual Transaction Document
(PCR) to the acceptance of the County.
b. You or IBM terminates the project in accordance with the provisions of the Agreement.
1.8 Estimated Schedule
The Services will be provided between a start date and an end date to be determined by both
parties. These dates must be specified in the initial Transaction Document and any subsequent
PCR (Project Change Request) form for each specific Data Source project. The Parties shall
endeavor to provide the Services and Responsibilities as defined herein.

IBM SOW# NKEA-9LVTBN
1.9 Charges
The Services will be conducted on a fixed price basis. The fixed price for performing the
Services will be defined in the initial Transaction Document (PCR) form for each specific Data
Source project. This fixed price is exclusive of any pre-approved travel and living expenses
incurred in connection with the Services. All charges are exclusive of any applicable taxes.
Because the services will be performed remotely, IBM does not expect to incur and travel and
living expenses associated with data source engagements.
IBM will invoice you for the Services performed in accordance with the table included in the
original Transaction Document (PCR) and/or any subsequent PCR, plus any applicable taxes and
any pre-approved travel and living expenses incurred in connection with the Services. Payment is
due upon receipt of an acceptable invoice for completed milestones, payable within 30 days.
Payment may be made electronically to an account specified by IBM or by other means agreed to
by the parties. In the event of late payment, IBM reserves the right to suspend the provision of
Services.
You will provide purchase orders to IBM for charges as described in the initial Transaction
Document (PCR), and such purchase orders are due prior to the performance of the Services. In
the event that purchase orders are not received in a timely manner, IBM may 1) suspend the
provision of Services and 2) terminate the specific Transaction Document for convenience.
Any different or added terms contained in any PO or other ordering documents that might be
exchanged in relation to activities under this SOW or the Transaction Document (PCR) will not
be applicable or of any effect At its sole discretion, IBM may elect to begin delivery of Services
after Transaction Document signing, but prior to receipt of PO or PO waiver, on a limited, case-
by-case basis.
1.10 Additional Terms and Conditions
1.10.1 Confidential Information
Notwithstanding anything to the contrary in the Agreement, the parties hereto agree that the IBM
Agreement for the Exchange of Confidential Information (“AECI”) shall govern the obligations
and rights of the parties with respect to any Information (as defined in the AECI) exchanged
between the parties during the term of this SOW and each specific Data Source project. The
AECI is incorporated into, and subject to, this SOW, and is located at:
http://www-05.ibm.com/support/operations/files/pdf/aeci_us.pdf
(which location may be changed from time to time). The terms of this SOW and each specific
Data Source project shall be considered confidential information under the AECI.
1.10.2 Intellectual Property Services Components
Intellectual Property Services Components Definition
Intellectual Property Services Components ("IPSCs") are preexisting IBM or third party literary
works or other works of authorship (such as programs, program listings, programming tools,
documentation, reports, drawings and similar works) that IBM may license to MCSO or that IBM
may use when providing a Service. IPSCs are not Products or Materials as such terms are defined
in the Agreement.
IPSC License Grant
Subject to the section entitled “IPSC Special Terms,” IBM grants MCSO an irrevocable,
nonexclusive, paid-up license to use, execute, copy, display, and distribute, all within the MCSO
Enterprise only, the following IPSC:
● IBM i2 COPLINK Data Migrator

IBM SOW# NKEA-9LVTBN
IPSC Special Terms
a. IBM or third parties have all right, title, and interest (including ownership of copyright)
in IPSCs and IPSCs are licensed, not sold. Notwithstanding the definition of IPSC
above, an IPSC shall be considered a Product for the purposes of the Agreement section
entitled “Limitation of Liability” only, without reference to any other section.
b. IPSCs are provided "AS IS" AND IBM MAKES NO REPRESENTATIONS OR
WARRANTIES, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO IPSCs,
INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE, AND DOES NOT INDEMNIFY AGAINST OR PROVIDE
ANY REMEDY REGARDING THIRD PARTY INTELLECTUAL PROPERTY
CLAIMS. Under no circumstances shall IBM be liable for any damages arising out of
MCSO’s use of the IPSC.
c. The IPSC License granted to MCSO is limited solely to MCSO’s COPLINK solution, as
specified in this SOW. No other entity in MCSO shall be permitted access to the IPSC
unless separately contracted with IBM.
d. The IPSC License granted is for internal use only and includes the right to make and
install copies of the IPSC to support such use, and the right to make one copy of the IPSC
for backup and recovery purposes.
e. The terms of this license apply to each copy MCSO makes of the IPSC. MCSO agrees to
reproduce all copyright notices and all other legends of ownership on each copy.
f. All modifications and the modified IPSC made by IBM under this or any SOW and all
rights therein (including copyrights), shall belong exclusively to IBM, but shall be subject
to this IPSC License. If requested by IBM to perfect IBM’s ownership rights (including
copyrights) in such modifications or the modified IPSC, MCSO agrees to execute all
documents necessary to perfect IBM’s ownership rights.
g. MCSO agrees not to: i) sublicense, assign, or transfer the license for the IPSC, ii) sell,
lease, license or otherwise distribute the IPSC to any third party, iii) reverse assemble,
reverse compile, or otherwise obtain or attempt to obtain the source code of the IPSC
except as specifically permitted by law without the possibility of contractual waiver, or
iv) sublicense, assign, or transfer the license for the IPSC to a successor, acquired, or
acquiring organization by merger or acquisition. Any attempt to do items (i), (ii) or (iv)
is void.
h. IBM may terminate this license if MCSO does not comply with any of the terms of this
SOW for each specific Data Source project.
i. Upon termination, MCSO agrees to destroy, and make no further use of, the IPSC, and
certify such destruction to IBM.
j. This term only applies to the OSS included with the IPSC and listed in the IBM
Responsibilities section above. OSS that IBM may install, update, access or otherwise
use for MCSO under this SOW is distributed (except as may be provided by the SOW)
and licensed to MCSO by the non-IBM OSS distributors and/or respective copyright or
other right holders under their terms and conditions. IBM is not a distributor (except as
may be provided by the SOW), licensee or licensor of such OSS, and performs the work
described in this SOW on MCSO’s behalf. Notwithstanding anything to the contrary
contained in the Agreement, IBM makes no express or implied warranties or
representations with respect to such OSS and provides no indemnity for such OSS. IBM
grants no express or implied patent or other license with respect to such OSS. IBM is not
liable for any damages arising out of the use of OSS. Any modification or creation of
derivative works of any OSS is outside the scope of this SOW.

IBM SOW# NKEA-9LVTBN
Appendix A: Project Procedures
A - 1: Project Change Control Procedure
Each Data Source project will be initiated according to the Transaction Document Process
outlined in Exhibit B of the Agreement. The following process will be followed if a change to an
existing Transaction Document is required:
a. A Project Change Request (PCR) will be the vehicle for communicating change. The
PCR must describe the change, the rationale for the change and the effect the change will
have on the project.
b. The designated Project Manager of the requesting party will review the proposed change
and determine whether to submit the request to the other party.
c. Both Project Managers will review the proposed change and agree to implement it,
recommend it for further investigation, or reject it.
d. IBM will specify any charges for such investigation. A PCR must be signed by
authorized representatives from both parties to authorize investigation of the
recommended changes. IBM will invoice you for any such charges per the terms of this
SOW and the Agreement. The investigation will determine the effect that the
implementation of the PCR will have on price, schedule and other terms and conditions
of this SOW and the Agreement.
e. A PCR must be accepted by authorized representatives from both parties to authorize
implementation of any agreed changes to the SOW and the Agreement. Until a change is
agreed to, both parties will continue to act in accordance with the latest agreed version of
the SOW.
f. A PCR that has been signed by authorized representatives from both parties constitutes a
change authorization for purposes of this SOW and the Agreement.
A - 2: Deliverable Materials Acceptance Procedure
Except for Status Reports and Project Plans/Schedules, deliverable Materials as defined herein
will be reviewed and accepted in accordance with the following procedure:
a. One printed or softcopy draft of the deliverable Material will be submitted to your Project
Manager for approval and sign-off. It is your Project Manager's responsibility to make
and distribute additional copies to any other reviewers.
b. Within five business days of receipt, your Project Manager will either accept the
deliverable Material or provide the IBM Project Manager a written list of requested
revisions. If your Project Manager accepts the work, any sign-off document relating to
the deliverable Material will be returned to IBM within five business days. If IBM
receives no response from your Project Manager within five business days, then the
deliverable Material will be deemed accepted.
c. The IBM Project Manager will consider your timely notification of requested revisions, if
any, within the context of IBM’s obligations under this SOW.
d. Those revisions agreed to by IBM will be made and the deliverable Material will be
resubmitted to your Project Manager for approval and sign-off.
e. Those revisions not agreed to by IBM will be managed in accordance with Appendix A-
1: Project Change Control Procedure.

IBM SOW# NKEA-9LVTBN
f. Any conflict arising from this deliverable Materials Acceptance Procedure will be
addressed as specified in the Escalation Procedure set forth in Appendix A-3.
A - 3: Escalation Procedure
The following procedure will be followed to resolve a conflict arising during the performance of
this SOW.
a. When a conflict arises between you and IBM, the project team member(s) will first strive
to work out the problem internally.
b. Level 1: If the project team cannot resolve the conflict within two working days, your
Project Manager and the IBM Project Manager will meet to resolve the issue.
c. Level 2: If the conflict is not resolved within three working days after being escalated to
Level 1, your Executive Sponsor will meet with the IBM Project Executive to resolve the
issue.
d. If the conflict is resolved by either Level 1 or Level 2 intervention, the resolution will be
addressed in accordance with the Project Change Control Procedure set forth in Appendix
A-1.
e. If the conflict remains unresolved after Level 2 intervention, then either party may
terminate the specific Data Source project. If the conflict is addressed by termination,
you agree to pay IBM as described in the “Termination” section of the Agreement.
f. During any conflict resolution, IBM agrees to provide Services relating to items not in
dispute, to the extent practicable pending resolution of the conflict. You agree to pay
invoices per the specific Data Source Transaction Document and the Agreement.

IBM SOW# NKEA-9LVTBN
Appendix B: Materials
B - 1: Status Reports
Purpose:
IBM will provide status reports advising MCSO’s Project Manager of the progress and status of
the IBM activities. The report will outline the IBM activities and describe the status of tasks
worked on during that period. Significant accomplishments, milestones, and problems will be
identified.
Content:
The report will consist of the following, as appropriate:
 Activities performed during the reporting period
 Activities planned for the next reporting period
 Project change control summary
 Problems, concerns, and recommendations
 Tasks for next reporting period
 Key resource or other requirements for reporting periods
 Other items of importance
Delivery:
IBM will deliver one (1) reproducible soft copy to MCSO’s Project Manager.
B - 2: Technical Questionnaire/Checklist
Purpose:
The purpose of this survey is to give IBM a technical understanding of the structure of your
source system and insight into factors that will affect the deployment of your data source into the
COPLINK production environment. This questionnaire is to be completed electronically and
returned to your IBM Project Manager (PM). A completed survey is required before the agency’s
kick-off meeting can be scheduled and before integration of the data source can begin.
Content:
The questionnaire/checklist will include the following information:
 Agency Info
 Roster
 Product Information
 First Encounters or Custom Systems
 Contributing Agencies
 Participation Requirements
 Documents Contained
 Mug Shots/Images
 Network Topology
 Miscellaneous Information
Delivery:
IBM will deliver one (1) copy of this document in softcopy format.

IBM SOW# NKEA-9LVTBN
B - 3: Sample Memorandum of Understanding
Purpose:
Provide an example of what IBM recommends with regard to any inter-agency MOUs MCSO has
in place for their data sharing initiative.
Content:
Terms and conditions related to the data sharing initiative between the Agencies.
Delivery:
IBM will deliver one (1) copy of this document in softcopy format.
B - 4: High-level Timeline
Purpose:
Provide high-level timeline for the project.
Content:
The timeline will show the anticipated time frame for each activity in the Transaction Document
for each Data Source project.
Delivery:
IBM will deliver one (1) copy of this document in softcopy format.
B - 5: System Test Report Confirming Data Migration Readiness
Purpose:
The purpose of this report is to provide MCSO with a document that shows the results of the
system testing of the COPLINK Node.
Content:
The content of this document will include the testing results for the various elements of the
COPLINK Node.
Delivery:
IBM will deliver one (1) copy of this document in softcopy format.
B - 6: Data Verification Form
Purpose:
To provide a sign-off form for the Data Verification activity; once approved by your Project
Manager, this constitutes completion of the Data Verification services. This checklist is created
based on agency-scoped source document types. It is a sign off from the agency that IBM has
fixed any issues from the first session and the agency is signing off on the data as acceptable and
correct to move into production.
Content:
Checklist of tasks completed during the Data Verification services.
Delivery:
IBM will deliver one (1) copy of this document in softcopy format.

IBM SOW# NKEA-9LVTBN
B - 7: Data Refresh Verification Form
Purpose:
To provide a sign-off form for the Data Refresh activity; once approved by your Project Manager,
this constitutes completion of the Data Refresh services.
Content:
Checklist of tasks completed during the Data Refresh services.
Delivery:
IBM will deliver one (1) copy of this document in softcopy format.

IBM SOW# NKEA-9LVTBN
Appendix C: Agency Source Data Information Tables
GENERAL CONVERSION RULES
 A data source consists of one or more of the data sets listed below.
 No alien data will be converted from a data source into COPLINK. IBM defines alien data as any
data not originally entered into the application associated with the data source. Examples of
alien data include but are not limited to:
o Documents migrated from your retired system of record and into your current system of
record through a means other than the system’s associated application.
o Pawn data contained in your police department’s RMS but originate from another system
(often a sheriff’s office).
o Mugs that originate from your Jail Management System but are also fed into your RMS
to view photos of potential suspects.
 Data must be delivered unmodified in order to qualify for standard data source prices. Prohibited
modifications include but are not limited to:
o Filtering of Juveniles and/or sex crime victims
o Data obfuscation
o Date range sub-setting
 Any required filtering will be implemented by IBM as part of the integration process and will be
approved by the contributing agency prior to data being shared with other agencies.
 IBM cannot convert Proprietary Binary File Formats
CONVERTED DATA PER DATA SOURCE TYPE
Agency Data Source Data Sets Description
Customer Agency Data Set Type Standard Data Data Not Migrated
Migrated
Records Management System (RMS) Department Reports Jail Management System
Supplemental (JMS) data
Reports Mug Shots
Traffic Collisions CAD data
Miscellaneous AFIS data
Incident Probation data
Citations Court data

IBM SOW# NKEA-9LVTBN
Agency Data Source Data Sets Description
Customer Agency Data Set Type Standard Data Data Not Migrated
Migrated
Field Interviews CJIS data
Permits Vehicle Tow data
Pawns Intelligence documents
Supervisions Crime Analysis documents
(Registration) Civil Process documents
Supervisions (Court Arraignments
Ordered)
Watch Lists
Motor Vehicle Dept. Images
Jail Management System (JMS) Bookings Jail Financial Management
Visitations* Commissary Records
(*only if Visitor Internal Jail Communication
Type data is Jail Resource Management
available) Background Checks
Supervisions (Court Employee Personnel Files &
Ordered) Applications
Mug Shots* Internal Jail activity
(*only if native to Inmate Cell information
the JMS) Inmate Transport Records
Inmate schedules
Inmate grievances
Inmate mail; Email; telephone
calls
Inmate Escape records
Inmate Court activity
Inmate Work programs &
related skills
Inmate Medical data
Inmate Behavior records
Inmate Handling Instructions
Inmate Visit Authorizations
Inmate Privileges
Inmate Property
Inmate Property Tracking
Inmate Next of Kin
Inmate Holds
Earliest Possible Release date
Anticipated Release date
Sentence Start & End date
Inmate Probation & Release
Schedules
Sentence Adjustments

IBM SOW# NKEA-9LVTBN
Agency Data Source Data Sets Description
Customer Agency Data Set Type Standard Data Data Not Migrated
Migrated
Conditions of Bail
Released To information
Inmate address & phone after
Release
Lineups
Inmate Vehicles
Inmate Vehicle Storage
Computer Aided Dispatch (CAD) Occurrences/Calls N/A
for Service (CFS)
Probation or Parole (Probation/Parole Supervisions (Court N/A
System) Ordered)
Supervisions
(Parole)
Supervisions
(Probation)
Automated Fingerprint Identification Identification N/A
System (AFIS) Documents
Criminal Justice Information System (CJIS) Warrants N/A
Traffic Collision System Traffic Collisions N/A
Citation System Citations N/A
Pawn System Pawn Tickets N/A
Department of Motor Vehicles Registration Permits N/A
System (DMVR)
Department of Motor Vehicles License Permits N/A
System (DMVL)
License Plate Reader System (LPR) LPR Reports N/A
Gang System Field Interviews N/A
Supervisions
(Registration)
Intel Documents
(Tips)
Prison/Corrections System Supervisions Prison Financial Management
(Incarcerations) Commissary Records
Visitations* Internal Prison Communication

IBM SOW# NKEA-9LVTBN
Agency Data Source Data Sets Description
Customer Agency Data Set Type Standard Data Data Not Migrated
Migrated
(*only if Visitor Prison Resource Management
Type data is Background Checks
available) Employee Personnel Files &
Mug Shots* Applications
(*only if native to Internal Prison Activity
the Inmate Cell Information
Prison/Corrections Inmate Transport Records
System)
Inmate Schedules
Inmate Grievances
Inmate Mail, Email &
Telephone Calls
Inmate Escape Records
Inmate Court Activity
Inmate Work Programs &
Related Skills
Inmate Medical Data
Inmate Behavior Records
Inmate Handling Instructions
Inmate Visit Authorizations
Inmate Privileges
Inmate Property
Inmate Property Tracking
Inmate Next of Kin
Inmate Holds
Earliest Possible Release Data
Anticipated Release Date
Sentence Start and End Date
Inmate Parole & Release
Schedules
Sentence Adjustments
Conditions of Bail
Released to Information
Inmate Address & Phone after
Release
Lineups
Inmate Vehicles
Inmate Vehicle Storage
Ballistics System Ballistics Reports N/A

IBM SOW# NKEA-9LVTBN
COPLINK DOCUMENTS SPECIFIED
General Document Rules
 Charges are indirectly tied to persons in COPLINK via Arrest, Booking, Citation, or Warrant
documents. If these documents are not present in the data source, it is an option to convert the
charges to crime types and associate them with the Departmental Report.
 If narratives are present in a data source, they will be converted, unless previously requested.
Agency Data Source Document Descriptions
Document Description Standard Data
Elements Migrated
Departmental Records the occurrence of a crime, police action taken, or Incident Begin
Reports information that a law enforcement officer deems Time/Date
significant enough to create a permanent record of an Incident End
incident Time/Date
Report Number
Beat
Grid
Crime Type(s)
Arrest Type
Arrest Number
Arrest Charge
Supplemental Records activities of law enforcement officers as they Same as Departmental
Reports continue to investigate a specific Departmental Report Reports
Traffic Records a collision of one vehicle with another vehicle, Same as Departmental
Collisions person, or other object Reports
Miscellaneous An abbreviated form of a report that describes a minor Same as Departmental
Incidents incident that does not require any follow-up investigation. Reports
This document type is created only in cases where
Departmental Reports can be distinguished from
Miscellaneous Reports
Citations Represent a judicial summons issued to a person by a law Citation Type
enforcement official as the result of a minor occurrence, Citation Number
typically in response to a traffic infraction or misdemeanor
Citation Status
Beat
Grid
Citation Charge

IBM SOW# NKEA-9LVTBN
Agency Data Source Document Descriptions
Document Description Standard Data
Elements Migrated
Field Contain information about contact between a law Field Interview Type
Interviews enforcement officer and at least one individual for any Field Interview
activity an officer feels is suspicious Number
Beat
Grid
Pawn Tickets Contain information about persons and property involved Pawn Ticket Number
in a pawn transaction Pawn Shop Name
Permits Represent permissions granted to an individual such as the Permit Type
privilege to carry a concealed weapon, a driver’s license, Permit Number
or handicap parking permit
Permit Status
Grid
Crime Type(s)
Supervisions An official proclamation by a judge that defines the legal Supervision Type
(Court relationship between the parties to a hearing, a trial, an Supervision Reference
Ordered) appeal, or other court proceedings. Such ruling requires or Number
authorizes the carrying out of certain steps by one or more
Supervision Start Date
parties to a case.
Supervision End Date
Types of Court-Ordered Supervisions include:
Supervision Status
Community Supervision
Drug Court Supervision
Federal Court Supervision
Juvenile Court Supervision
Miscellaneous Court Supervision
Prohibited Possessor (Firearm)
Court Order of Protection
Travel Restriction
No Trespass
Temporary Restraining Order
Work Release
Pre-Trial Release
Supervisions Records the periodic registration of an individual who has Supervision Type
(Registration) been ordered by the court to report home location and Supervision Reference
other pertinent information as deemed by local law Number
enforcement or the court.
Supervision Start Date
Types of Registration Supervisions include:
Supervision End Date
Registered Gang Member
Supervision Status
Registered Arson

IBM SOW# NKEA-9LVTBN
Agency Data Source Document Descriptions
Document Description Standard Data
Elements Migrated
Registered Felon
Registered Repeat Offender
Registered Sex Offender
Registered Narcotic Offender
Supervisions A type of Supervision managed by the justice system after Supervision Type
(Parole) a conditional early release of a person from incarceration. Supervision Reference
Parole includes only: Number
Parole Supervision Supervision Start Date
Supervision End Date
Supervision Status
Supervisions A type of Supervision managed by the justice system after Supervision Type
(Probation) a conditional early release of a person from incarceration. Supervision Reference
Probation includes only: Number
Probation Supervision Supervision Start Date
Supervision End Date
Supervision Status
Supervisions Records the imprisonment of an individual. Supervision Type
(Incarceration) Incarceration includes only: Supervision Reference
Incarceration Supervision Number
Supervision Start Date
Supervision End Date
Supervision Status
Bookings Records the admittance of a person into a jail facility (not a Booking Charge
prison) Booking Time/Date
Release Time/Date
Release Agency
Release Location
Release Reason
Release Officer
Cases Represents a folder and not a document. A COPLINK Case Number
case will thus consist of related documents that have been
combined into a case.
Ballistics Describes weapons and ammunition used at the scene of a Report Date/Time
Reports crime. Destroyed Date/Time
Report Number

IBM SOW# NKEA-9LVTBN
Agency Data Source Document Descriptions
Document Description Standard Data
Elements Migrated
Criminalist (examiner)
Visitations Represent the visitation between an inmate and at least one Visitor Type
other person. A “Visitor Type” field is required for this Visitation Number
document.
Date
Begin/End Time
Duration
Warrants Represent the authority to arrest an individual for the Warrant Type
commission of a specific crime Warrant Category
Warrant Number
Court Docket Number
Warrant Status
Warrant Charge
Occurrences Represent a request for assistance by an individual. Such Occurrence Number
requests are often filed through local 911 services after the Priority Code
observance of a crime, suspicious activity, or because of a
Out Type (indication of
dire need for medical treatment
how call was routed to
the field)
Call Source Type
Beat
Grid
Identification Represent the identification of an individual by a law Identification
Documents enforcement agency. Document Number
LPR Reports Records the location and license plate of a vehicle Report Date/Time
surveilled by devices capable of Automatic Number Plate Report ID Number
Recognition (ANPR)

IBM SOW# NKEA-9LVTBN
Entity Descriptions
Entity Standard Data Elements Migrated Data Elements Not Migrated
Persons Name Religion
Alias(s) Education Level
Gender Skill Set
Date of Birth Dependent/Custody
Height Financial Need Status/Indigent
Weight Fingerprints
Eye Color Citizenship Status
Hair Color Marital Status
Race Sexuality
Ethnicity Languages Spoken
Marks
Modus Operandi (MO)
Appearances
Caution Flags
Gang Members
Registered Offenders
Employer
Operator License Number
Social Security Number
State ID
FBI ID
Local ID
Organizations Name N/A
Organization Type
Officers Name Personal Information
Badge Number
Vehicles Vehicle Identification Number (VIN) Vehicle Impounds
Class
Make
Model
Style
Year
Color
License Plate
Weapons Type N/A
Manufacture Type
Serial Number

IBM SOW# NKEA-9LVTBN
Entity Descriptions
Entity Standard Data Elements Migrated Data Elements Not Migrated
Color
Lands/Grooves/Twists/Housing/Action/Casing/
Head Stamp*
(* Ballistic Data Sets only)
Properties Category N/A
Type
Size
Make
Model
Color
Serial Number
Quantity
Securities Type N/A
Issuer
Serial Number
Denomination
Quantity
Value
Phones Phone Number N/A
Locations Latitude/Longitude N/A
Address

IBM SOW# NKEA-9LVTBN
Standard Entities Per Document
Persons Organizations Officers Vehicles Weapons Properties Securities Phones Locations
Entity
Document
Departmental Reports Y Y Y Y Y Y Y Y Y
Supplemental Reports Y Y Y Y Y Y Y Y Y
Traffic Collisions Y Y Y Y Y Y Y Y Y
Miscellaneous Incidents Y Y Y Y Y Y Y Y Y
Arrests Y Y Y
Dispatch Y Y
Arraignment Y Y Y Y Y Y Y Y Y
Ballistics Y Y Y Y Y Y Y
Citations Y Y Y Y Y Y Y Y Y
Field Interviews Y Y Y Y Y
Pawn Tickets Y Y Y Y Y Y Y
Permits Y Y Y Y Y
Supervisions Y Y Y Y Y
Bookings Y Y Y
Visitations Y Y Y
Occurrences Y Y Y Y Y Y Y Y Y
Warrants Y Y Y Y Y Y Y Y Y
Identification
Documents Y Y Y Y
X,Y
LPR Reports Y coords
Y = Yes, when available in the source system

IBM SOW# NKEA-9LVTBN
Appendix D: Third Party Hardware And Software
The following third party hardware and software (or their equivalent) is required for the Services. MCSO
or the Contributing Agency will provide this hardware and software. Specifications are subject to change
as technology changes. Please review with IBM/i2 for the current and latest specifications.
THIRD Application Migration Database Data Storage Integration
PARTY Server Server Server Box
HARDWARE (Desktop)
Item Dell Dell Dell Dell DELL
PowerEdge PowerEdge PowerEdge EqualLogic OptiPlex 990
R620 R620 R820 PS6100XS Small Form
Factor or
equivalent
Quantity 1 1 1 1 Per Data
Source
Processor 2xXeon E5- 2xXeon E5- 4x Intel Xeon Intel Core i5
2630 2630 2.30GHz, E5-4620
2.30GHz, 15M Cache, 2.20GHz, 16M
15M Cache, 7.2GT/s QPI, Cache,
7.2GT/s QPI, Turbo, 6C 7.2GT/s QPI,
Turbo, 6C Turbo, 8 Core
Clock Speed 2.30Ghz 2.30Ghz 2.20Ghz 3.1Ghz
Memory 16GB 16GB 64GB 8GB, DDR2
Non-ECC
SDRAM,
800Mhz
Hard Drive 2x300Gig 2x300Gig 15K, 2x300Gig 13TB 2x500GB
15K, 6GB 6GB SCSI 15K, 6GB SAS capacity, 7x 7200 RPM
SCSI 400GB SSD+ SATA
17x 600GB 3.0GB/s &
10K SAS 8MB
DataBurst
Hard Drive RAID-1 RAID-1 Dual RAID-1 RAID-1
Configuration Controllers,
HA w/failover
Operating Windows Windows Windows Windows 7
System Server 2008 Server 2008 Server 2008 Professional
Standard x64 Standard x64 Standard x64 x64
Redundant Yes Yes Yes Yes No
Power

IBM SOW# NKEA-9LVTBN
THIRD Application Migration Database Data Storage Integration
PARTY Server Server Server Box
HARDWARE (Desktop)
Peripherals 2U Shelf, 19”
and Rack shelf,
Accessories 13” deep
THIRD Application Migration Database Server Intermediary Box
PARTY Server Server
SOFTWARE
Third Party Java RE 1.6 MS SQL Server MS SQL Server 2008 Notepad ++, 7-xip,
Software 2008 R2 Std R2 Std Java RE 1.6,
Java RE 1.6, MS .Net 3.5 or higher MS SQL Server 2008 R2
OpenSSH Std, Cygwin, OpenSSH

EXHIBIT E
ADDITIONAL TERMS AND CONDITIONS
1. Transaction Documents
Transaction Documents are part of this Agreement only for those transactions to which they apply. Each
transaction is separate and independent from other transactions. All Attachments and Transaction Docu-
ments are to be presented to Maricopa County Office of Procurement Services for review and execution.
Only the Maricopa County Chief Procurement Officer or his designees have the authority to execute an
agreement between the parties. The Transaction Document Process is outlined in Exhibit B of the
Agreement.
2. Definitions
Materials – literary works or other works of authorship (such as software programs and code, documen-
tation, reports, and similar works) that IBM may deliver to County as part of a Service. The term “Materi-
als" does not include: i) Machine Code, or ii) licensed program products or other items available under
their own license terms or agreements.
Service – performance of a task, assistance, support, or access to resources (such as an information da-
tabase) that IBM makes available to County.
3. Personnel
Each party will assign personnel that are qualified to perform the tasks required of such party under this
Agreement and is responsible for the supervision, direction, control, and compensation of its personnel.
Subject to the foregoing, each party may determine the assignment of its personnel and its contractors.
IBM may engage subcontractors to provide or assist in providing Services, in which case IBM remains re-
sponsible for the fulfillment of its obligations under this Agreement and for the performance of the Ser-
vices.
4. Materials Ownership and License
An Attachment or Transaction Document will specify Materials to be delivered to County and identify them
as “Type I Materials,” “Type II Materials,” or otherwise as both parties agree. If not specified, Materials
will be considered Type II Materials.
County will own the copyright in Materials created as part of a Service that are identified as “Type I Mate-
rials” and each such Material will constitute a “work made for hire” to the extent permissible under U.S.
copyright law. If any such Materials are not works made for hire under applicable law, IBM assigns the
ownership of copyrights in such Materials to County. County grants IBM an irrevocable, nonexclusive,
worldwide, paid-up license to use, execute, reproduce, display, perform, sublicense, distribute, and pre-
pare derivative works based on, Type I Materials.
IBM or its suppliers will own the copyright in Materials created as part of a Services transaction that are
identified as Type II Materials. IBM grants County an irrevocable, nonexclusive, worldwide, paid-up li-
cense to use, execute, reproduce, display, perform, and distribute (within County’s Enterprise only) cop-
ies of Type II Materials.
IBM or its suppliers retains ownership of the copyright in any of IBM’s or its suppliers’ works that pre-exist
or were developed outside of this Agreement and any modifications or enhancements of such works that
may be made under this Agreement. To the extent they are embedded in any Materials, such works are
licensed in accordance with their separate licenses provided to County, if any, or otherwise as Type II
Materials.
Each party agrees to reproduce the copyright notice and any other legend of ownership on any copies
made under the licenses granted in this section.
5. County Resources
If County is making available to IBM any facilities, software, hardware or other resources in connection
with IBM’s performance of Services, County agrees to obtain any licenses or approvals related to these
resources that may be necessary for IBM to perform the Services and develop Materials. IBM will be re-
lieved of its obligations that are adversely affected by County’s failure to promptly obtain such licenses or

approvals. County agrees to reimburse IBM for any reasonable costs and other amounts that IBM may
incur from County’s failure to obtain these licenses or approvals.
Unless otherwise agreed in a Transaction Document, County is responsible for i) any data and the con-
tent of any database County makes available to IBM in connection with a Service under this Agreement,
ii) the selection and implementation of procedures and controls regarding access, security, encryption,
use, and transmission of data, and iii) backup and recovery of the database and any stored data.
IBM’s responsibilities regarding such data or database, including any confidentiality and security obliga-
tions, are governed by the Attachments and Transaction Documents applicable to the particular Services
Transaction (which prevail over the terms of any separate confidentiality agreements) and subject to the
Limitation of Liability and other terms in this Agreement.
6. Automatic Service Renewal
Renewable Services renew automatically for a same length contract period unless either party provides
written notification (at least one month prior to the end of the current contract period) to the other of its
decision not to renew. During an automatic renewal period, County may terminate the Service on one
month’s written notice, and IBM will provide County a prorated credit for any unused Services for which
County has paid in advance.
7. Intellectual Property Protection
7.1 Third Party Claims
If a third party asserts a claim against County that a Material IBM provides to County under this Agree-
ment infringes that party's patent or copyright, IBM will defend County against that claim at IBM’s expense
and pay all costs, damages, and attorney's fees that a court finally awards against County or that are in-
cluded in a settlement approved in advance by IBM, provided that County:
a. promptly notifies IBM in writing of the claim;
b. allows IBM to control, and cooperates with IBM in, the defense and any related settlement negotia-
tions; and
c. is and remains in compliance with the Material’s applicable license terms and County’s obligations
under section 12.2 (Remedies) below.
7.2 Remedies
If such a claim is made or appears likely to be made, County agrees to permit IBM, in IBM’s discretion, ei-
ther to i) enable County to continue to use the Material, ii) modify it, or iii) replace it with one that is at
least functionally equivalent. If IBM determines that none of these alternatives is reasonably available,
then on IBM’s written request, County agrees to promptly return the Material to IBM and discontinue its
use. IBM will then give County a credit equal to the amount County paid IBM for the creation of the Mate-
rials.
7.3 Claims for Which IBM is Not Responsible
IBM has no obligation regarding any claim based on any of the following:
a. anything provided by County or a third party on County’s behalf that is incorporated into a Material
or IBM’s compliance with any designs, specifications, or instructions provided by County or a third
party on County’s behalf;
b. modification of a Material by County or a third party on County’s behalf;
c. the combination, operation, or use of a Material with any product, hardware device, program, data,
apparatus, method, or process that IBM did not provide as a system, if the infringement would not
have occurred were it not for such combination, operation or use; or
d. the distribution, operation or use of a Material outside County’s Enterprise.
This Intellectual Property Protection section states IBM’s entire obligation and County’s exclusive remedy
regarding any third party intellectual property claims.
8. Limitation of Liability
8.1 Items for Which IBM May be Liable
Circumstances may arise where, because of a default on IBM’s part or other liability, County is entitled to
recover damages from IBM. Regardless of the basis on which County is entitled to claim damages from

IBM (including fundamental breach, negligence, misrepresentation, or other contract or tort claim), IBM’s
entire liability for all claims in the aggregate arising from or related to each Service (including any Material
or Machine Code provided with the Service) or otherwise arising under this Agreement will not exceed the
amount of any actual direct damages up to the greater of $100,000, or the charges (if recurring, 12
months' charges apply) for the Service that is the subject of the claim.
This limit also applies to any of IBM’s subcontractors and program developers. It is the maximum for
which IBM and its subcontractors and program developers are collectively responsible. The following
amounts are not subject to a cap on the amount of damages:
a. payments referred to in the Intellectual Property Protection section above; and
b. damages for bodily injury (including death) and damage to real property and tangible personal
property for which IBM is legally liable.
8.2 Items for Which IBM is Not Liable
Except as expressly required by law without the possibility of contractual waiver, under no circumstances
is IBM, its subcontractors, or program developers liable for any of the following even if informed of their
possibility:
a. loss of, or damage to, data;
b. special, incidental, exemplary, or indirect damages or for any economic consequential damages; or
c. lost profits, business, revenue, goodwill, or anticipated savings.
9. General Principles of Our Relationship
9.1 Notices and Communications
Written communications, including notices to the receiving party’s designated representative, are to be
sent to the address (physical, e-mail or facsimile) specified in an applicable Transaction Document. The
parties consent to the use of electronic means and facsimile transmissions to send and receive communi-
cations in connection with our business relationship arising out of this Agreement, and such communica-
tions are acceptable as a signed writing. An identification code (called a “user ID”) contained in an elec-
tronic document is sufficient to verify the sender’s identity and the document’s authenticity.
9.2 Assignment and Resale
Neither party may assign this Agreement, in whole or in part, without the prior written consent of the oth-
er. Any attempt to assign without consent is void. The assignment of this Agreement, in whole or in part,
within the Enterprise of which either party is a part or to a successor organization by merger or acquisition
does not require the consent of the other. IBM is also permitted to assign its rights to payments without
obtaining County’s consent. It is not considered an assignment for IBM to divest a portion of its business
in a manner that similarly affects all the County.
County agrees not to resell any Service without IBM’s prior written consent. Any attempt to do so is void.
9.3 Compliance with Laws
IBM will comply with laws applicable to IBM generally as a provider of information technology products
and Services. IBM is not responsible for determining the requirements of laws applicable to County's
business, including those relating to Services that County acquires under this Agreement, or that IBM's
provision of or County's receipt of particular Services under this Agreement meets the requirements of
such laws. Neither party is obligated to take any action that would violate applicable law.
Each party will comply with all applicable export and import laws, regulations, and associated embargo
and sanction regulations, including prohibitions on export for certain end uses or to certain end users.
9.4 Other Principles of Our Relationship
a. Neither party grants the other the right to use its (or any of its Enterprise's) trademarks, trade
names, or other designations in any promotion or publication without prior written consent.
b. The exchange of any confidential information will be made under a separate, signed confidentiality
agreement. However, to the extent confidential information is exchanged in connection with any
Service under this Agreement, the applicable confidentiality agreement is incorporated into, and
subject to, this Agreement.

c. This Agreement and any transaction under it do not create an agency, joint venture, or partnership
between County and IBM. Each party is free to enter into similar agreements with others to devel-
op, acquire, or provide competitive products and services.
d. Each party grants only the licenses and rights specified in this Agreement. No other licenses or
rights (including licenses or rights under patents) are granted either directly, by implication, or oth-
erwise. The rights and licenses granted to County under this Agreement may be terminated if
County fails to fulfill its applicable payment obligations.
e. No right or cause of action for any third party is created by this Agreement or any transaction under
it, nor is IBM responsible for any third party claims against County except as described in the Intel-
lectual Property Protection section above or as permitted by the Limitation of Liability section above
for bodily injury (including death) or damage to real or tangible personal property for which IBM is
legally liable to that third party.
f. County is responsible for selecting the Services that meet its needs and for the results obtained
from the use of the Services, including County’s decision to implement any recommendation con-
cerning County’s business practices and operations.
g. Where approval, acceptance, consent or similar action by either party is required under this Agree-
ment, such action will not be unreasonably delayed or withheld.
h. Neither party is responsible for failure to fulfill any non-monetary obligations due to events beyond
its control.
i. As reasonably required by IBM to fulfill its obligations under this Agreement, County agrees to pro-
vide IBM with sufficient and safe access (including remote access) to County’s facilities, systems,
information, personnel, and resources, all at no charge to IBM. IBM is not responsible for any delay
in performing or failure to perform caused by County’s delay in providing such access or performing
other County responsibilities under this Agreement.
The remainder of this page is left intentionally blank.