170002-CONTRACT.PDF

SERIAL 170002-RFP
CONT CT PURSUANT TO RFP
SERIAL 170002-RFP
This Contract is entered into this 22nd day of March, 2017 by and between Maricopa County ("County"), a political
subdivision of the State of Arizona, and Tribridge Holdings, LLC, a Delaware Limited Liability Company
("Contractor") for the purchase of Jail Management System software and services.
1.0 CONTRACT TERM:
1.1 This Contract is for a term of ten (10) years, beginning on the 22' 1 day of March, 2017 and ending
the 31'1 day of March, 2027.
1.2 The County may, at its option and with the approval of the Contractor, renew the tetra of this
Contract up to a maximum of ten (10) additional years, or other specified length options, (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 Contractor shall be notified in writing by the Office of Procurement
Services of the County's intention to extend the contract term at least thirty (30) calendar days
prior to the expiration of the original contract term.
2.0 PRICE ADJUSTMENTS:
2.1 Contractor may request increases in hourly rates for non-contracted services on the annual
Contract anniversary date. All requests for increases shall be accompanied by detailed supporting
documents that explain the necessity of the increase. Maricopa County shall independently verify
each request and make a determination on the allowance of the increase(s).
2.2 For the purposes of determining the annual support and maintenance service fee for any year past
the initial maintenance term, the most recent annual fee will be increased by the lesser amount of
3% or the Producer Price Index for Software Maintenance, Technical Support, and other services
related to software publishing, BLS series ID PCU511210511210504.
3.0 PAYMENTS:
3.1 As consideration for performance of the duties described herein, County shall pay Contractor the
sum(s) stated in Exhibit A.
3.2 Payment shall be made upon the County's receipt of a properly completed invoice per the payment
terms detailed in Exhibit A.

SERIAL 170002-RFP
CONTRACT PURSUANT TO RF'P
SERIAL 170002 -RFP
Contract Synopsis:
Approval Date: March 22, 2017
Contract Start Date: March 22, 2017
Contract End Date: March 31, 2027
Contract Term: 10 years, plus option for additional 10 years
Contracted Parties: Maricopa County (County, Owner)
Tribridge Holdings, LLC (Contractor)
Scope Brief:
The County, on behalf of the Maricopa County Sheriffs Office ("MCSO") has engaged Contractor to replace the
current Jail Management System (JMS) and other legacy detention systems with a comprehensive New JMS
Solution.
Table of Contents:
Master Service Agreement
Exhibit A — Pricing Agreement
Exhibit B — Scope of Work
Statement of Requirements
Statement of Work
Exhibit C — Software License and Maintenance Agreement
Exhibit D — Software Support and Service Level Agreement
Exhibit E — Travel and Per Diem Policy
Appendix 1 — Functional Requirements
Appendix 2 — Non-Functional Technical Requirements
Appendix 3 — Reporting Requirements
Appendix 4— Interface Inventory

SERIAL 170002.-RFP
3.3 INVOICES:
3.3.1 The Contractor shall submit one (1) legible copy of their detailed invoice before
payment(s) can be made. Incomplete invoices will not be processed. At a minimum, the
invoice must provide the following information:
Company name, address and contact
County bill-to name and contact information
Contract Serial Number or
County purchase order number
Invoice number and date
Payment terms
Date of service or delivery
Quantity (number of days or weeks)
Contract Item number(s)
Description of Purchase (product or services)
Extended price
Total Amount Due
3.3.2 Problems regarding billing or invoicing shall be directed to the using agency as listed on
the Purchase Order.
3.3.3 Payment shall be made to the Contractor by Accounts Payable through the Maricopa
County Vendor Express Payment Program. This is an Electronic Funds Transfer (EFT)
process. After Contract Award the Contractor shall complete the Vendor Registration
Foini located on the County Depai (Anent of Finance Vendor Registration Web Site
(http ://www.maricopa.gov/FinanceNendors.aspx).
3.3.4 EFT payments to the routing and account numbers designated by the Contractor will
include the details on the specific invoices that the payment covers. The Contractor is
required to discuss remittance delivery capabilities with their designated fmancial
institution for access to those details.
3.4 PROJECT PAYMENT TERMS
Deliverables and/or milestones for payments shall be mutually agreed upon by the Contractor and
County.
3.5 PAYMENT RETENTION
3.5.1 Fifteen percent (15%) of monies paid to Contractor related to work under this agreement
shall be retained by County. The County, upon execution of a Stage Acceptance
Document or a Final Acceptance Document, shall authorize the Contractor to invoice the
County for a release of retained funds per the schedule described in Exhibit A, Pricing,
Milestones. Other than Final Acceptance, the retainage release shall not exceed one-third
(1/3) of the retained funds from the given Stage. All other payment terms and conditions
shall not be affected by the retention. In the event of termination or cancellation of this
contract by County through no fault of Contractor, Contractor shall be entitled to the
refund of any funds in the retention account.
3.5.2 The Contractor shall have the right, pursuant to Arizona Revised Statues, to submit
securities in lieu of retention for all work completed. The Contractor is required to
request this option at least ten (10) business days prior to submission of first Application
for Payment to allow time for preparation of forms. The Contractor shall request and
obtain securities forms through County. The County must identify either securities
option or retention option prior to first Application for Payment.

SERIAL 170002-RFP
3.6 APPLICABLE TAXES:
3.6.1 Payment of Taxes: The Contractor shall pay all applicable taxes. With respect to any
installation labor on items that are not attached to real property performed by Contractor
under the terms of this Contract, the installation labor cost and the gross receipts for
materials provided shall be listed separately on the Contractor's invoices.
3.6.2 State and Local Transaction Privilege Taxes: Maricopa County is subject to all
applicable state and local transaction privilege taxes. To the extent any state and local
transaction privilege taxes apply to sales made under the terms of this contractit is the
responsibility of the seller to collect and remit all applicable taxes to the proper taxing
jurisdiction of authority.
3.6.3 Tax Indemnification: Contractor and all subcontractors shall pay all Federal, state, and
local taxes applicable to its operation and any persons employed by the Contractor.
Contractor shall, and require all subcontractors to hold Maricopa County harmless from
any responsibility for taxes, damages and interest, if applicable, contributions required
under Federal, and/or state and local laws and regulations and any other costs including
transaction privilege taxes, unemployment compensation insurance, Social Security and
Worker's Compensation.
3.7 TAX: (SERVICES)
No tax shall be levied against labor. It is the responsibility of the Contractor to determine any and
pay all applicable taxes and include the same in their proposal price.
3.8 TAX (COMMODITIES):
Tax shall not be levied against labor. Sales/use tax will be determined by County. Tax will not be
used in determining low price.
3.9 STRATEGIC ALLIANCE for VOLUME EXPENDITURES ($AVE):
3.9.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 the successful Respondent under this solicitation, a member of $AVE
may access a contract resulting from a solicitation issued by the County.
3.10 INTERGOVERNMENTAL COOPERATIVE PURCHASING AGREEMENTS (ICPA' s)
3.10.1 County currently holds ICPA' s with numerous governmental entities throughout the State
of Arizona. These agreements allow those entities, with the approval of the Contractor,
to purchase their requirements under the terms and conditions of the County Contract.
Exhibit A indicates your acceptance regarding such participation of other governmental
entities.
3.11 TRAVEL AND PER DIEM:
3.11.1 Contractor, as indicated in Exhibit A, shall be held to the Not to Exceed limit described
therein for travel and per diem expenses. Contractor shall be reimbursed for real and
actual travel and per diem expenses, without the addition of a markup or management
fee, as governed by Exhibit E, Contractor Travel and Per Diem Policy. County reserves
the right to audit any receipts. Upon request, Contractor shall provide County with digital
copies of travel receipts. Any invoiced amount or actual payment issued by County, that
is found to either not have the required receipt(s) or fails to comply with the referenced
policy, shall either be rejected by County or be reimbursed to County in the event of
payment being issued.

SERIAL 170002-RFP
3.11.2 Contractor shall perform the following duties with respect to travel:
3.11.2.1 Provide County Project Manager with a quarterly travel projection that details
the anticipated travel dates, personnel and travel rationale or applicable
milestone/deliverable. Contractor shall not book travel without County's authorization of
the quarterly travel projection.
3.11.2.2 Provide monthly travel budget for the following four (4) calendar weeks.
3.11.2.3 Provide monthly invoices with a detail of expense performance to the monthly
travel budget.
4.0 AVAILABILITY OF FUNDS:
4.1 The provisions of this Contract relating to payment for services shall become effective when funds
assigned for the purpose of compensating the Contractor as herein provided are actually available
to County for disbursement. The County shall be the sole judge and authority in determining the
availability of funds under this Contract. County shall keep the Contractor fully informed as to the
availability of funds.
4.2 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, travel expenses and travel per diem incurred prior to the effective date
of the ter urination, provided that such services are performed in accordance with the provisions of
this Contract. County shall give written notice of the effective date of any suspension,
amendment, or termination under this Section, at least ten (10) days in advance.
5.0 DUTIES:
5.1 The Contractor shall perform all duties stated in Exhibit B, or as otherwise directed in writing by
the Procurement Officer.
5.2 During the Contract term, County may provide Contractor's personnel with adequate workspace
for consultants and such other related facilities as may be required by Contractor to carry out its
contractual obligations.
6.0 TERMS and CONDITIONS:
6.1 DEFINITIONS:
6.1.1 Acceptance shall mean that a signed Deliverable Acceptance Statement from County has
been sent to Contractor indicating that a Deliverable has met the acceptance criteria set
forth hereinafter.
6.1.2 Artifact(s) are items/activities that are required for project success but are not subject to
Acceptance.
6.1.3 Business Day shall mean one regular work-day (Monday through Friday) as defmed by
COUNTY's business calendar.
6.1.4 Confidential Information has the same meaning given to such term in the EULA as well
as any Publisher confidential information.
6.1.5 Contractor Software — Software Licensed under the Software License and Maintenance
Agreement attached as Exhibit C,
6.1.6 Copyrights means any and all copyrighted and copyrightable materials, whether or not
registered, published, or containing a copyright notice, in any and all media, and further
including but not limited to, any and all moral rights and corresponding rights under
international agreements and conventions, Derivatives, and any and all applications for
registrations, registrations, and/or renewals of any of the foregoing.
6.1.7 Day/Days shall mean, unless noted otherwise, a "day" equals one calendar day.

SERIAL 170002-RFP
6.1.8 Defect shall represent a condition in the software product which produces unexpected or
incorrect results, does not meet the expected software requirement, or does not meet
reasonable end-user expectations.
6.1.9 Deliverable shall mean any product, service, document, software, data, or other item
produced by the Contractor and provided to County for Acceptance.
6.1.10 Derivatives mean any and all adaptations, enhancements, improvements, modifications,
revisions, derivations, or translations of or to Intellectual Property.
6.1.11 Final Acceptance shall mean the point at which the Contractor has met all of the
requirements and conditions of this Agreement.
6.1.12 Go-Live Date shall be the date that County and the Contractor establish as the date
Contractor's System will replace County's existing system as the day-to-day operational
system.
6.1.13 Integration shall mean provision of custom interfaces and code to allow data exchange
between distinct software applications or databases.
6.1.14 Intellectual Property means any and all (a) Confidential Infoimation; (b) Copyrights; (c)
Patents; (d) Derivatives; (e) Technical Info' !nation; (1) Technology; and (g) any and all
other intellectual property or proprietary rights relating to or arising from any or all of the
foregoing.
6.1.15 Interface shall mean programmed interfaces which are the languages, codes and
messages that programs use to communicate with each other and to make information
available.
6.1.16 Issue any condition which does or may adversely affect the ability of the project to
produce the required Deliverables, or which requires intervention in order to correct the
condition.
6.1.17 ISV is an acronym for Independent Software Vendor.
6.1.18 IT shall mean COUNTY's Technology Management division and the County's
Infoimation Technology division.
6.1.19 Licensed Software means Offender 360, North52, Scribe Insight ADXstudio and
Epilogue in object and/or source code fomiat, as the parties may agree, along with any
documentation provided by Contractor pursuant to this License. Except as otherwise set
forth herein, Licensed Software excludes Derivatives of the Licensed Software, created
by Contractor or Licensee or both of them pursuant to this License.
6.1.20 Licensed Users means the number of users authorized under this License.
6.1.21 Onsite shall mean the activity shall be conducted at COUNTY facilities.
6.1.22 Patents means and all patents, patentable materials, letters patent and utility models,
including reissues, divisionals, continuations, continuations-in-part, renewals, and extensions
of any of the foregoing and applications therefor (and patents which may issue on such
applications) in the United States and foreign states.
6.1.23 Publisher means the Publisher of Licensed Software combined with or provided separately
from Contractor's combined solution. Publisher may be Microsoft Corporation
("Microsoft") or North 52, or Scribe Software Corporation ("Scribe"), as appropriate.
6.1.24 PM shall mean project manager.
6.1.25 Remote shall mean the activity shall be conducted using secure remote internet
connection and software, and teleconferencing equipment as required.
6.1.26 SME shall mean Subject Matter Expert.
6.1.27 System shall mean the final configuration and setup of the Contractor's software product,
including migrated or converted County data, installation, configuration, database design,
and integrations, so that all elements perform as a single unit in the manner intended.
6.1.28 System Acceptance shall mean the System is fully operational in the production
environment and performing in conformity with Acceptance criteria described herein.
6.1.29 System Readiness shall mean the System is fully operational in a non-production
environment and perfoiming in conformity with the standard required to deploy the
System to the production environment.
6.1.30 System Test and "System Testing" shall mean end-to-end testing composed of
Installation, Configuration, Module, Business Process, User Interface, Data and Data
Integrity testing.
6.1.31 Task shall mean an activity in Exhibit B that describes how one or more Deliverables
should be created and delivered. This term also applies to the detailed work elements
contained in the project schedule.

SERIAL 170002-RFP
6.1.32 Technical Information: means data and other technical information including, but not
limited to: (a) engineering documentation, such as development records, production software
information, algorithms, flow charts, design information, drawings, specifications and data
sheets; (b) manufacturing documentation such as manufacturing drawings, instructions,
specifications, procedures, methods, standards documentation, tooling and fixture drawings,
process specifications and instructions; (c) quality and reliability documentation such as
quality plans, specifications, instructions, procedures, test plans, test records and regulatory
documentation; and (d) user manuals, on-line help, training materials, installation
instructions, release notes, problem reports and resolutions, and marketing studies, which
may be disclosed by the Party in possession thereof without violating obligations to a third
Party, and further including any and all Intellectual Property therein, or relating or referring
thereto.
6.1.33 Technology means know-how, show how, procedures, systems, processes, trade secrets,
inventions (whether or not patentable and whether or not reduced to practice), algorithms,
formulae, research and development data; manufacturing, development and production
techniques; and all other proprietary information relating thereto, and further including any
and all Intellectual Property therein, or relating or referring thereto.
6.1.34 Test Script shall mean a series of actions, functions or commands documented for the
purpose of execution during quality assurance testing.
6.2 INDEMNIFICATION:
To the fullest extent permitted by law, and to the extent that claims, damages, losses or expenses
are not covered and paid by insurance purchased by the Contractor, the Contractor shall defend
indemnify and hold harmless the County (as Owner), its agents, representatives, agents, officers,
directors, officials, and employees from and against all claims, damages, losses, and expenses
(including, but not limited to attorneys' fees, court costs, expert witness fees, and the costs and
attorneys' fees for appellate proceedings) arising out of, or alleged to have resulted from the
negligent acts, errors, omissions, or mistakes relating to the perfoimance of this Contract.
Contractor's duty to defend, indemnify, and hold ban 'less the County, its agents, representatives,
agents, officers, directors, officials, and employees shall arise in connection with any claim,
damage, loss, or expense that is attributable to bodily injury, sickness, disease, death or injury to,
impairment of, or destruction of tangible property, including loss of use resulting there from,
caused by negligent acts, errors, omissions, or mistakes in the performance of this Contract, but
only to the extent caused by the negligent acts or omissions of the Contractor, a subcontractor, any
one directly or indirectly employed by them, or anyone for whose acts they may be liable,
regardless of whether or not such claim, damage, loss, or expense is caused in part by a party
indemnified hereunder.
The amount and type of insurance coverage requirements set forth herein will in no way be
construed as limiting the scope of the indemnity in this paragraph.
The scope of this indemnification does not extend to the sole negligence of County.
6.3 INFRINGEMENT DEFENSE INDEMNIFICATION
6.3.1 Defense and Indemnity: Contractor shall defend, Participate and Share in the Cost, as
defmed below, in the full defense of the County against any Claim, as defmed below, and
will indemnify and hold harmless the County as provided for in this Section for any
judgments, settlements and court awarded attorney's fees resulting from a Claim where
the claimant is adjudged the successful party in the Claim. Contractor's obligations under
this Section are conditioned on the following: (i) County promptly notifies Contractor of
the Claim in writing upon made aware of the Claim; (ii) County gives Contractor lead
authority and County being control of the defense and (if applicable) settlement of the
Claim, provided that County's legal counsel may participate in such defense and
settlement, at County's expense, and (iii) County provides all information and assistance
reasonably requested by Contractor to handle the defense or settlement of the Claim. For
purposes of this Section, "Claim" means any cause of action in a third party action, suit
or proceeding against County alleging that Contractor software, or its upgrades,

SERIAL 170002-RFP
modifications, or revisions, as of its delivery date under this Agreement, infringes a valid
U.S. patent, copyright or trademark. For the purposes of this section, "Participate and
Share in the Costs" means Contractor will assist the County in the defense of the claim,
to the extent agreed to by the parties, except that Contractor shall be solely responsible
for any and all costs adjudged in a successful Claim against the County.
6.3.1.1 Remedial Measures: If software becomes, or Contractor reasonably believes use
of software may become, the subject of a Claim, Contractor may, at its own
expense and option: (i) procure for County the right to continue use of the
Product; (ii) replace or modify the software; or to the extent that neither (i) nor
(ii) are deemed commercially practicable, (iii) refund to County a pro-rated
portion of the applicable fees for software based on a linear depreciation
monthly over 10 year useful life, in which case County will cease all use of
software and return it to Contractor.
6.3.1.2 Exceptions: Contractor will have no defense or indemnity obligation for any
Claim based on: (i) modifications by someone other than Contractor; (ii)
software has been modified by Contractor in accordance with County-provided
specifications or instructions; (iii) use or combination by the County of software
with Third Party Products, open source or freeware technology; (iv) Third Party
Products, open source or freeware technology; (v) a product that is used or
located by County in a country other than the country in which or for which it
was supplied by Contractor; (vi) possession or use of a product after Contractor
has informed County of modifications or changes required to avoid such Claim
and offered to implement those modifications or changes, if such Claim would
have been avoided by implementation of Contractor's suggestions and to the
extent County did not provide Contractor with a reasonable opportunity to
implement Contractor's suggestions; or (vii) the amount of revenue or profits
earned or other value obtained by the use of Products, or the amount of use of
the Products. "Third Party Products" means any products made by a party other
than Contractor, and may include, without limitation, products ordered by
County from third parties. However, components of Contractor-branded
Products are not Third Party Products if they are both: (i) embedded in Third
Party Products (i.e., not recognizable as standalone items); and (ii) not identified
as separate items on Contractor's price list, quotes, order specifications forms or
Documentation.
6.3.1.3 The foregoing states Contractor's entire liability, and County's sole and
exclusive remedy except as provided at law or equity, with respect to any
infringement or misappropriate of any intellectual property rights of another
party.
6.4 CONFIDENTIALITY OF COUNTY DATA:
Contractor shall protect all fmancial, statistical, personal, technical, and other data and information
relating to the County's operations which are designated confidential by County, and made
available to the Contractor in order to carry out this Agreement, or which become available to the
Contractor in carrying out this Agreement, from unauthorized use and disclosure.
In addition to the Maricopa County General Provisions for "Confidentiality of Data", the
following provision supplements the term of this agreement: THE CONTRACTOR AGREES TO
COMPLY WITH ALL MCSO INFORMATION SECURITY STANDARDS AND PRIVACY
POLICIES AND HAVE ALL EMPLOYEES, SUBCONTRACTOR EMPLOYEES, AGENTS
AND CONSULTANTS WORKING ON THE AGREEMENT COMPLETE AND SIGN THE
STATEMENT OF CONFIDENTIALITY.
6.5 INSURANCE
6.5.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

SERIAL 170002-RFP
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.5.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.5.3 Contractor's insurance shall be primary insurance as respects County, and any insurance
or self-insurance maintained by County shall not contribute to it.
6.5.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.5.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.5.6 The insurance policies required by this Contract, except Workers' Compensation and
Errors and Omissions, shall name County, its agents, representatives, officers, directors,
officials and employees as Additional Insureds.
6.5.7 The policies required hereunder, except Workers' Compensation and Errors and
Omissions, shall contain a waiver of transfer of rights of recovery (subrogation) against
County, its agents, representatives, officers, directors, officials and employees for any
claims arising out of Contractor's work or service.
6.5.8 Commercial General Liability.
Commercial General Liability insurance and, if necessary, Commercial Umbrella
insurance with a limit of not less than $2,000,000 for each occurrence, $4,000,000
Products/Completed Operations Aggregate, and $4,000,000 General Aggregate Limit.
The policy shall include coverage for premises liability, bodily injury, broad form
property damage, personal injury, products and completed operations and blanket
contractual coverage, and shall not contain any provisions which would serve to limit
third party action over claims. There shall be no endorsement or modifications of the
CGL limiting the scope of coverage for liability arising from explosion, collapse, or
underground property damage.
6.5.9 Automobile Liability.
Commercial/Business Automobile Liability insurance and, if necessary, Commercial
Umbrella insurance with a combined single limit for bodily injury and property damage
of not less than $1,000,000 each occurrence with respect to any of the Contractor's
owned, hired, and non-owned vehicles assigned to or used in perfoimance of the
Contractor's work or services or use or maintenance of the Premises under this Contract.
6.5.10 Workers' Compensation.
Workers' Compensation insurance to cover obligations imposed by federal and state
statutes having jurisdiction of Contractor's employees engaged in the performance of the
work or services under this Contract; and Employer's Liability insurance of not less than

SERIAL 170002-RFP
$1,000,000 for each accident, $1,000,000 disease for each employee, and $1,000,000
disease policy limit.
Contractor, its contractors and its subcontractors waive all rights against Contract and its
agents, officers, directors and employees for recovery of damages to the extent these
damages are covered by the Workers' Compensation and Employer's Liability or
commercial umbrella liability insurance obtained by Contractor, its contractors and its
subcontractors pursuant to this Contract.
6.5.11 Cyber
Policy Limit:
6.5.11.1 The policy shall be issued with minimum limits of $100,000.
6.5.11.2 The policy shall include coverage for all directors, officers, agents and
employees of the Contractor.
6.5.11.3 The policy shall include coverage for third party fidelity.
6.5.11.4 The policy shall include coverage for theft.
6.5.11.5 The policy shall contain no requirement for arrest and conviction.
6.5.11.6 The policy shall cover loss outside the premises of the Named Insured.
6.5.11.7 The policy shall endorse (Blanket Endorsements are not acceptable) the
Depairment as Loss Payee as our interest may appear.
6.5.12 Technology Errors & Omission Insurance
• Each claim $2,000,000
• Annual Aggregate $2,000,000
Such insurance shall cover any, and all errors, omissions, or negligent acts in the delivery
of products, services, and/or licensed programs under this contract.
Coverage shall include or shall not exclude settlement and/or defense of claims involving
intellectual property, including but not limited to patent or copyright infringement.
In the event that the Tech E&O insurance required by this Contract is written on a claims-
made basis, Contractor warrants that any retroactive date under the policy shall precede
the effective date of this Contract and, either continuous coverage will be maintained or
an extended discovery period will be exercised for a period of two (2) years, beginning at
the time work under this Contract is completed.
6.5.13 Network Security (Cyber) and Privacy Liability
• Each Claim $2,000,000
• Annual Aggregate $2,000,000
Such insurance shall include, but not be limited to, coverage for third party claims
and losses with respect to network risks (such as data breaches, unauthorized access
or use, ID theft of data) and invasion of privacy regardless of the type of media
involved in the loss of private information, crisis management and identity theft
response costs. This should also include breach notification costs, credit remediation,
and credit monitoring, defense and claims expenses, regulatory defense costs plus
fines and penalties, cyber extortion, computer prop -am and electronic data
restoration expenses coverage (data asset protection), network business interruption,
computer fraud coverage, and funds transfer loss.
In the event that the Network Security and Privacy Liability insurance required by
this Contract is written on a claims-made basis, Contractor warrants that any
retroactive date under the policy shall precede the effective date of this Contract and,
either continuous coverage will be maintained, or an extended discovery period will

SERIAL 170002-RFP
be exercised for a period of two (2) years beginning at the time work under this
Contract is completed.
The policy shall be endorsed, as required by this written agreement, to include the
County, its agents, representatives, officers, directors, officials, employees and
additional insureds with respect to liability arising out of the activities performed by
or on behalf of the Contractor.
Policy shall contain a waiver of subrogation endorsement, as required by this written
agreement, in favor of the County, its agents, representatives, officers, directors,
officials, employees for losses arising from work performed by or on behalf of the
Contractor.
6.5.14 Certificates of Insurance.
6.5.14.1 Prior to Contract award, Contractor shall furnish the County with valid and
complete certificates of insurance, or formal endorsements as required by the
Contract in the form provided by the County, issued by Contractor's insurer(s),
as evidence that policies providing the required coverage, conditions and limits
required by this Contract are in full force and effect. Such certificates shall
identify this contract number and title.
6.5.14.2 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.
6.5.14.3 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.
6.5.15 Cancellation and Expiration Notice.
Applicable to all insurance policies required within the Insurance Requirements of this
Contract, Contractor's insurance shall not be permitted to expire, be suspended, be
canceled, or be materially changed for any reason without thirty (30) days prior written
notice to Maricopa County. Contractor must provide to Maricopa County, within 2
business days of receipt, if they receive notice of a policy that has been or will be
suspended, canceled, materially changed for any reason, has expired, or will be expiring.
Such notice shall be sent directly to Maricopa County Office of Procurement Services
and shall be mailed or hand delivered to 320 West Lincoln Street, Phoenix, AZ 85003, or
emailed to Procurement Officer noted in solicitation.
6.6 SOURCE CODE ESCROW
6.6.1 The Contractor shall provide all source code and any updates for fixes for the contractor
Commercial Off-the-Shelf (COTS) application software that the County has purchased
from Contractor and Contractor has licensed to County pursuant to the Software License
and Maintenance Agreement attached as Exhibit C, for safekeeping with a mutually
acceptable escrow agent within forty-five (45) days of installation by County of the
Contractor Software onto its Delivery Platform. The Contractor shall execute an escrow
agreement between the Contractor, the County, and the escrow agent to achieve the
purposes of this section and shall name the County as sole beneficiary of the escrow
agreement. The software source deposited with the escrow agent will be a snapshot of all
source code maintained by Contractor in the form of an archive in a recognized version
control system (e.g., Vault or Visual SourceSafe). In this way, as beneficiary of the
escrow agreement between Contractor and escrow agent, County will have access to all
source code of the products that they license for all versions of the soft -ware, subject to
one of the release clauses in Section 6.6.2 being met. Furthermore, the escrowed code
shall include all code specifically developed for County (Custom Modifications)

SERIAL 170002-RFP
including, but not limited to: interfaces, Extraction-Transformation-Loading (ETL)
routines for data conversions, and all custom code including patches and fixes applied
subsequent to implementation (as-built). Furthermore, to the extent permitted to do so by
the relevant third party licenses, Contractor will provide binaries of all third party
products used in as-built product and a list of all development tools used, including
version and configuration and scripts used by build systems. Upon taking possession of
the source code, County will have the right (subject to Section 6.6.3) to use the source for
the Contractor Software licensed from Contractor in the versions currently installed on
the System or any subsequent versions in the archive. Contractor shall make a deposit
with the escrow agent at least once every six (6) months.
County hereby agrees to pay the yearly standard fee for a beneficiary of the source code.
Upon County taking possession of the source code, Contractor will have no further
obligation to support the Contractor Software nor update the escrow deposit unless some
foimal agreement between the parties has been reached
6.6.2 County shall have access to the source code pursuant to the terms of the escrow
agreement mentioned above in the event of any of the following circumstances, provided
that the County has paid Contractor total amounts due for the Software/Contractor
Software at the time of the request for access to the source code:
6.6.2.1 The sale, assignment, or transfer to any third party of any of Contractor's rights
in the Contractor Software (or any portion thereof) if such sale, assignment, or
transfer would prevent Contractor from fully performing any of its obligations
under any agreement with County and the Contractor did not obtain the
County's prior written consent (which will not be unreasonably withheld,
conditioned, or delayed);
6.6.2.2 Contractor becomes insolvent or commits any affirmative act of insolvency, or
generally fails to pay, or admits in writing its inability to pay, debts as they
become due, makes a general assignment for the benefit of creditors, files a
voluntary petition of bankruptcy, suffers or permits the appointment of a
receiver for its business or assets, becomes subject to any proceeding under, or
case in, any bankruptcy or insolvency law, or Contractor takes any action to
authorize, or in the furtherance of, any of the foregoing;
6.6.2.3 If County is currently subscribed to Contractor's support and maintenance
services and Contractor, or any entity that supports the Contractor Software,
discontinues providing full support and maintenance services for the Contractor
Software in accordance with its obligations pursuant to any agreement with
County;
6.6.2.4 Contractor has ceased to do business or improperly refuses to provide any
services pursuant to any agreement with County, subject to cure provisions
thereof
6.6.2.5 Contractor has breached (and if subject to a cure period, has not cured such
breach within such period) any material term or condition of any agreement with
County;
6.6.2.6 Any change of control of Contractor or Contractor's parent company, where
such party is acquired, directly or indirectly, in a single transaction or series of
related transactions, or all or substantially all of the assets of such party are
acquired by any entity, or such party is merged with or into another entity to
form a new entity; or

SERIAL 170002-RFP
6.6.2.7 Any other circumstance in which County is entitled to access or use the
applicable deposit materials (including, but not limited to, the source code)
under the express terms of any agreement.
6.6.3 Should County take possession of the source code as a result of an event as specified
above, County hereby agrees as follows:
6.6.3.1 County accepts full and total responsibility for the safekeeping of the source
code. County agrees that such source code shall be subject to the restrictions of
transfer, sale, and reproduction placed on the software itself as stated in the
Software License Agreement(s) signed by all parties;
6.6.3.2 County agrees to only use source code to support (itself or, subject to
confidentiality provisions, by others for its benefit) the Contractor Software for
user thereof in accordance with the license granted. There will be source code
from other applications in the archive;
6.6.3.3 County agrees that any unauthorized release of the source code will cause
irreparable harm to Contractor. Therefore, County agrees to compensate
Contractor for any and all damages Contractor suffers, to include reasonable
attorney's fees, resulting directly or indirectly from, but not limited to, the
mishandling, misuse, or theft of the source code, regardless of intent, or the
absence thereof, by County, its employees, former employees, agents and third-
party associates if so ordered by the court. Notwithstanding the foregoing,
County agrees that Contractor is entitled to an immediate injunction to stop any
further alleged or actual disclosure;
6.6.3.4 No license under any trademark, patent, copyright, or any other intellectual
property right, is either granted or implied by the disclosure of the source code
to County. The Contractor's disclosure of the source code to County shall not
constitute any representation, warranty, assurance, guarantee or inducement by
the Contractor to County of any kind, and, in particular, with respect to the non-
infringement of trademarks, patents, copyrights, or any other intellectual
property rights, or other rights of third persons or of Contractor; and
6.6.3.5 County and the Contractor will execute, and deposit into escrow together with
the deposit materials, a confidentiality agreement, mutually agreed up between
the parties, regarding the use and disclosure of the source code consistent with
this Section 6.6.
6.6.4 County acknowledges and agrees that it will only be entitled to receive the source code
for:
(a) those elements of the Commercial Off-the-Shelf (COTS) application software for
which County has paid full license fees,
(b) that software developed specifically for County (including, but not limited to,
interfaces, Extraction-Transformation-Loading (ETL) routines for data conversions,
and all custom code including patches and fixes applied subsequent to
implementation (as-built) for which County has fulfilled all payment obligations in
relation to its development (on a pro-rata basis, if development is not complete), and
(c) those binaries of third party products used in as-built product for which County has
paid full license fees (to the extent required to do so pursuant to the Contract).
In each case, in accordance with the provisions of this Section 6.4, and to the extent
that such fees have not been paid pursuant to the applicable agreement therefor, its
right to receive such source code pursuant to the escrow release process, County will

SERIAL 170002-RFP
be required to certify to the escrow agent that it has paid such license and service
fees.
6.7 FORCE MAJEURE
6.7.1 Neither party shall be liable for failure of performance, nor incur any liability to the other
party on account of any loss or damage resulting from any delay or failure to perform all
or any part of this Contract if such delay or failure is caused by events, occurrences, or
causes beyond the reasonable control and without negligence of the parties. Such events,
occurrences, or causes will include Acts of God/Nature (including fire, flood, earthquake,
stoun, hurricane or other natural disaster), war, invasion, act of foreign enemies,
hostilities (whether war is declared or not), civil war, riots, rebellion, revolution,
insurrection, military or usurped power or confiscation, terrorist activities,
nationalization, government sanction, lockout, blockage, embargo, labor dispute, strike,
interruption or failure of electricity or telecommunication service.
6.7.2 Each party, as applicable, shall give the other party notice of its inability to perform and
particulars in reasonable detail of the cause of the inability. Each party must use best
efforts to remedy the situation and remove, as soon as practicable, the cause of its
inability to perfolm or comply.
6.7.3 The party asserting Force Majeure as a cause for non-perfoimance shall have the burden
of proving that reasonable steps were taken to minimize delay or damages caused by
foreseeable events, that all non-excused obligations were substantially fulfilled, and that
the other party was timely notified of the likelihood or actual occurrence which would
justify such an assertion, so that other prudent precautions could be contemplated.
6.7.4 The County shall reserve the right to tel inate this Contract and/or any applicable order
or contract release purchase order upon non-performance by Contractor. The County
shall reserve the right to extend the Contract and time for performance at its discretion.
6.8 SOFTWARE UPDATES, WARRANTY, MAINTENANCE & ROADMAP/ENHANCEMENTS:
6.8.1 Contractor shall make available to County at no additional charge all Enhancements to
the Contractor Software as they are released so long as the County is currently under the
Contractor's agreement for Support and is using a Current Release. The County shall
decide at its discretion whether or not to take advantage of such Enhancement and
support it under the Support agreement. Notwithstanding the foregoing, County
acknowledges that Support will be limited to a commercially reasonable effort basis if the
County elects not to maintain a Current Release of the Contractor Software.
6.8.2 To ensure that Documentation is consistent with the operating environment, updated
Documentation shall be delivered concurrently with every Enhancement where the
functionality documented has materially been changed, or the cumulative effect of
previous Enhancements has rendered the functionality documented to have materially
changed.
6.8.3 After the Reliability Test Period has passed as set out in Exhibit B Part 1, the Warranty
Period will begin for a period of forty-five (45) days. At the end of this Warranty Period,
a Gate Review shall be held that will establish either a) the close of the Warranty and the
Commencement of Maintenance & Support or b) an additional Warranty Period of forty-
five (45) days.
6.9 LIMITATION OF LIABILITY:
IF FOR ANY REASON, CONTRACTOR BECOMES LIABLE TO COUNTY OR ANY OTHER
PERSON FOR LIABILITY ARISING PRIOR TO COUNTY'S FINAL ACCEPTANCE, FOR DIRECT
OR ANY OTHER DAMAGES, LOSSES OR EXPENSES FOR ANY CAUSE WHATSOEVER, AND
REGARDLESS OF THE FORM OF ACTION (IN CONTRACT, TORT, STRICT LIABILITY, OR
OTHER THEORY OF LIABILITY), INCURRED IN CONNECTION WITH THIS CONTRACT OR

SERIAL 170002-REP
THE PROJECT DELIVERABLES, THEN THE AGGREGATE LIABILITY OF CONTRACTOR FOR
ALL DAMAGES, INJURY, AND LIABILITY INCURRED BY COUNTY AND ALL OTHER PARTIES
IN CONNECTION 'WITH THE SERVICES OR THIS AGREEMENT SHALL NOT EXCEED THE
AGGREGATE VALUE OF IMPLEMENTATION AS DESCRIBED IN EXHIBIT B.
IF FOR ANY REASON, CONTRACTOR BECOMES LIABLE TO COUNTY OR ANY OTHER
PERSON FOR LIABILITY ARISING ON OR AFTER THE DATE OF COUNTY'S FINAL
ACCEPTANCE, IN NO EVENT SHALL CONTRACTOR'S LIABILITY TO COUNTY OR ANY
THIRD PARTY SEEKING DAMAGES UNDER THIS AGREEMENT FOR DIRECT OR ANY OTHER
DAMAGES, LOSSES OR EXPENSES FOR ANY CAUSE WHATSOEVER, AND REGARDLESS OF
THE FORM OF ACTION (IN CONTRACT, TORT, STRICT LIABILITY, OR OTHER THEORY OF
LIABILITY), INCURRED IN CONNECTION WITH THIS CONTRACT OR THE PROJECT
DELIVERABLES, THEN THE AGGREGATE LIABILITY OF CONTRACTOR FOR ALL DAMAGES,
INJURY, AND LIABILITY INCURRED BY COUNTY AND ALL OTHER PARTIES IN
CONNECTION WITH THE SERVICES OR THIS AGREEMENT EXCEED THE AMOUNT PAID TO
CONTRACTOR DURING THE TWELVE (12) MONTHS IMMEDIATELY PRECEDING THE EVENT
GIVING RISE TO THOSE DAMAGES CLAIMED.
6.10 WARRANTY OF SERVICES:
6.10.1 The Contractor warrants that all services provided hereunder will confoiin to the
requirements of the Contract, including all descriptions, specifications and attachments
made a part of this Contract. County's acceptance of services or goods provided by the
Contractor shall not relieve the Contractor from its obligations under this warranty.
6.10.2 In addition to its other remedies, County may, at the Contractor's expense, require prompt
correction of any services failing to meet the Contractor's warranty herein. Services
corrected by the Contractor shall be subject to all the provisions of this Contract in the
manner and to the same extent as services originally furnished hereunder.
6.11 INSPECTION OF SERVICES:
6.11.1 The Contractor shall provide and maintain an inspection system acceptable to County
covering the services under this Contract. Complete records of all inspection work
performed by the Contractor shall be maintained and made available to County during
contract performance and for as long afterwards as the Contract requires.
6.11.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.11.3 If any of the services do not conform to Contract requirements, County may require the
Contractor to perform the services again in conformity with Contract requirements, at no
cost to the County. When the defects in services cannot be corrected by re-performance,
County may:
6.11.3.1 Require the Contractor to take necessary action to ensure that future
performance conforms to Contract requirements; and
6.11.3.2 Reduce the Contract price to reflect the reduced value of the services performed.
6.11.4 If the Contractor fails to promptly perform the services again or to take the necessary
action to ensure future performance in conformity with Contract requirements, County
may:
6.11.4.1 By Contract or otherwise, perform the services and charge to the Contractor,
through direct billing or through payment reduction, any cost incurred by
County that is directly related to the performance of such service; or
6.11.4.2 Terminate the Contract for default.

SERIAL 170002-RFP
6.12 REQUIREMENTS CONTRACT:
6.12.1 Contractors signify their understanding and agreement by signing a bid submittal, that the
Contract resulting from the bid is a requirements contract. However, the Contract does
not guarantee any minimum or maximum number of purchases will be made. It only
indicates that if purchases are made for the materials or services contained in the
Contract, they will be purchased from the Contractor awarded that item if the Contractor
can meet all the delivery requirements of the County. Orders will only be placed when
the County identifies a need and proper authorization and documentation have been
approved.
6.12.2 County reserves the right to cancel Purchase Orders within a reasonable period of time
after issuance. Should a Purchase Order be canceled, the County agrees to reimburse the
Contractor for actual and documentable costs incurred by the Contractor in response to
the Purchase Order. The County will not reimburse the Contractor for any costs incurred
after receipt of County notice of cancellation, or for lost profits, shipment of product prior
to issuance of Purchase Order, etc.
6.12.3 Contractors agree to accept verbal notification of cancellation of Purchase Orders from
the County Procurement Officer with written notification to follow. By submitting a bid
in response to this Invitation for Bids, the Contractor specifically acknowledges to be
bound by this cancellation policy.
6.13 SUSPENSION OF WORK
The Procurement Officer may order the Contractor, in writing, to suspend, delay, or interrupt all or
any part of the work of this contract for the period of time that the Procurement Officer determines
appropriate for the convenience of the County. No adjustment shall be made under this clause for
any suspension, delay, or interruption to the extent that performance would have been so
suspended, delayed, or interrupted by any other cause, including the fault or negligence of the
Contractor. No request for adjustment under this clause shall be granted unless the claim, in an
amount stated, is asserted in writing as soon as practicable after the termination of the suspension,
delay, or interruption, but not later than the date of final payment under the contract.
6.14 STOP WORK ORDER
The Procurement Officer may, at any time, by written order to the Contractor, require the
Contractor to stop all, or any part, of the work called for by this contract for a period of 90 days
after the order is delivered to the Contractor, and for any further period to which the parties may
agree. The order shall be specifically identified as a stop work order issued under this clause.
Upon receipt of the order, the Contractor shall immediately comply with its terms and take all
reasonable steps to minimize the incurrence of costs allocable to the work covered by the order
during the period of work stoppage. Within a period of 90 days after a stop-work is delivered to
the Contractor, or within any extension of that period to which the parties shall have agreed, the
Procurement Officer shall either-
6.14.1 Cancel the stop-work order; or
6.14.2 Tenninate the work covered by the order as provided in the Default, or the Termination
for Convenience of the County clause of this contract.
6.14.3 The Procurement Officer may make an equitable adjustment in the delivery schedule
and/or contract price, or otherwise, and the contract shall be modified, in writing,
accordingly, if the Contractor demonstrates that the stop work order resulted in an
increase in costs to the Contractor.
6.15 TERMINATION FOR CONVENIENCE:
Maricopa County may terminate the resultant Contract for convenience by providing sixty (60)
calendar days advance notice to the Contractor.

SERIAL 170002-RFP
6.16 TERMINATION FOR DEFAULT:
The County may, by written notice of default to the Contractor, terminate this contract in whole or
in part if the Contractor fails to:
6.16.1 Deliver the supplies or to perfoiiii the services within the time specified in this contract or
any extension;
6.16.2 Make progress, so as to endanger performance of this contract; or
6.16.3 Perform any of the other provisions of this contract.
6.16.4 The County's right to tein mate this contract under these subparagraph may be exercised
if the Contractor does not cure such failure within 10 days (or more if authorized in
writing by the County) after receipt of the notice from the Procurement Officer
specifying the failure.
6.17 STATUTORY RIGHT OF CANCELLATION FOR CONFLICT OF INTEREST:
Notice is given that pursuant to A.R.S. § 38-511 the County may cancel any Contract without
penalty or further obligation within three years after execution of the contract, if any person
significantly involved in initiating, negotiating, securing, drafting or creating the contract on
behalf of the County is at any time while the Contract or any extension of the Contract is in effect,
an employee or agent of any other party to the Contract in any capacity or consultant to any other
party of the Contract with respect to the subject matter of the Contract. Additionally, pursuant to
A.R.S § 38-511 the County may recoup any fee or commission paid or due to any person
significantly involved in initiating, negotiating, securing, drafting or creating the contract on
behalf of the County from any other party to the contract arising as the result of the Contract.
6.18 CONTRACTOR LICENSE REQUIREMENT:
6.18.1 The Respondent shall procure all permits, insurance, licenses and pay the charges and
fees necessary and incidental to the lawful conduct of his/her business, and as necessary
complete any required certification requirements, required by any and all governmental
or non-governmental entities as mandated to maintain compliance with and in good
standing for all permits and/or licenses. The Respondent shall keep fully infoimed of
existing and future trade or industry requirements, Federal, State and Local laws,
ordinances, and regulations which in any manner affect the fulfillment of a Contract and
shall comply with the same. Contractor shall immediately notify both Office of
Procurement Services and the using agency of any and all changes concerning permits,
insurance or licenses.
6.18.2 Respondents furnishing finished products, materials or articles of merchandise that will
require installation or attachment as part of the Contract, shall possess any licenses
required. A Respondent is not relieved of its obligation to posses the required licenses by
subcontracting of the labor portion of the Contract. Respondents are advised to contact
the Arizona Registrar of Contractors, Chief of Licensing, at (602) 542-1525 to ascertain
licensing requirements for a particular contract. Respondents shall identify which
license(s), if any, the Registrar of Contractors requires for performance of the Contract.
6.19 SUBCONTRACTING:
6.19.1 The Contractor may not assign to another Contractor or Subcontract to another party for
performance of the terms and conditions hereof without the written consent of the
County. All correspondence authorizing subcontracting must reference the Bid Serial
Number and identify the job project.
6.19.2 The Subcontractor's rate for the job shall not exceed that of the Prime Contractor's rate,
as bid in the pricing section, unless the Prime Contractor is willing to absorb any higher
rates or the County has approved the increase. The Subcontractor's invoice shall be
invoiced directly to the Prime Contractor, who in turn shall pass-through the costs to the

SERIAL 170002-RFP
County, without mark-up. A copy of the Subcontractor's invoice must accompany the
Prime Contractor's invoice.
6.20 BACKGROUND CHECK:
6.20.1 All Contractor and Subcontractor personnel who will have access to Sheriffs Office
hardware, software, network, equipment, or facilities during this project shall complete a
background check, including fingerprints, to be performed by the Maricopa County
Sheriff's Office or other law enforcement agency approved by MCSO. The process may
also include completion the Arizona Department of Public Safety (DPS) Terminal
Operator Certification (TOC) Level "D."
6.20.2 Contractor and Subcontractor staff shall clear the FBI background check prior to
perfoiming any work on the project, including entry into any MCSO jail facility for
assessment of work to be completed. At the discretion of the Maricopa County Sheriff or
his designee, Contractor and Subcontractor personnel who require regular access to
MCSO facilities may be issued a Courtesy Identification card.
6.20.3 Forms required for the background check and Courtesy ID shall be completely and
legibly filled out and signed. False statements shall be grounds for disqualifying the
applicant. Application forms shall be submitted to the MCSO Technology Bureau
Director or designee who will then forward the forms for processing.
6.20.4 Failure to comply with this requirement or failure to pass the background check shall be
cause for the exclusion of specific personnel from work on the project, and potentially
may result in termination of the Agreement.
6.21 FACILITY SECURITY GUIDELINES AND MCSO COURTESY IDENTIFICATION CARD
6.21.1 All Contractor and Subcontractor personnel who require physical access to MCSO
facilities shall comply with facility security guidelines and shall complete the Sheriffs
Office Prison Rape Elimination Act (PREA) Acknowledgement form prior to performing
any services, or gaining access to any Sheriffs Office facility. If appropriate, Contractor
personnel may also complete the MCSO Application For Courtesy Identification. Forms
shall be completely and legibly filled out and signed. False statements shall be grounds
for disqualifying the applicant. Information provided on the Maricopa County Sheriffs
Office Application for Courtesy Identification form will be used to conduct a criminal
history check. Any resulting criminal history documentation will be forwarded to the
MCSO Technology Bureau Project Director or his designee. It will be reviewed on a
case by case basis to determine whether the applicant poses any risk to the safety of any
persons, or to the security of any system, jail, or facility.
6.21.2 Applicants must meet the following conditions to be approved by the Sheriff or his
designee for access to Sheriffs Office jail facilities:
a) Be at least eighteen (18) years of age. There shall be no exceptions.
b) At least twelve (12) months must have elapsed since serving a tei in of probation or
parole.
c) If an ex-offender served a jail sentence as the result of a misdemeanor conviction, a
minimum of twelve (12) months must have elapsed since last being incarcerated in
any jurisdiction.
d) If an ex-offender served a jail or prison term as a result of a felony conviction,
access will be denied.
6.21.3 Contractor or Subcontractor personnel who are approved after a criminal history check
may be issued a Sheriffs Office Courtesy Identification Card. The card shall remain the
property of the Sheriffs Office and may be revoked if the following rules and regulations
are not adhered to:
a) The card shall be worn in plain view on the front of the shirt or on a chain around
the neck at all times while in a Sheriffs Office facility.

SERIAL 170002-RFP
b) All personnel are required to submit to a search for contraband, if asked.
c) Contractor personnel are prohibited from duplicating the card.
d) Contractor personnel who lose their access cards shall immediately report the loss
to the MCSO Technology Bureau Director or Jail Commander.
e) Allowing another person to use the Courtesy ID Card is prohibited.
6.21.4 Contractor or Subcontractor personnel who become involved in a criminal investigation
during the contract period, either on the job or on their own time, must notify the MCSO
Technology Bureau Director within twenty-four hours. Access to MCSO facilities may
be subsequently suspended or revoked at the discretion of the Technology Bureau
Director, Facility Commander, or designee.
6.21.5 All concerns regarding contractor personnel should be forwarded to the MCSO
Technology Bureau Director. The services of any contractor may be reduced, postponed
or discontinued for any of the following reasons:
a) Violating facility security guidelines.
b) Participating in unlawful or immoral conduct.
c) Showing sips of an illness or condition that might interfere with the individual's
ability to perform his duties or threaten the security, health, or safety of anyone
involved.
d) Reporting to work with any odor of intoxicating beverage on their breath or while
under the influence of any intoxicating beverage to any degree.
e) Behaving in a manner which threatens the safety and security of the jail, staff, or
imnate.
Unauthorized contact with inmates.
Possession or use of any controlled substances, narcotics or hallucinogens, except
when prescribed by a physician, for any illness or injury unless otherwise provided
by the Arizona Revised Statutes.
h) Possession of any weapon on or near County property.
i) Failure to follow the directions of Sheriffs Office staff
j) Being in an unauthorized area.
k) Possession of tobacco products, alcohol, and weapons are strictly prohibited on jail
premises.
1) Under no circumstances will cell phone cameras be used without the express
permission of the Jail Commander or designee.
m) Under no circumstances will MP3 players, radios, I-Pods or similar devices be
pelmitted in a jail facility.
n) Contractor or Subcontractor personnel shall NOT talk to or associate with any
inmate for any reason without prior authorization.
6.21.6 The Sheriffs Office Courtesy ID Card is to be used for no purpose other than to access
specific areas related to the project in progress. Upon completion of the project, or prior
to termination with the Contractor or Subcontractor firm, the cardholder shall
immediately return the card to the MCSO Technology Bureau Director or designee.
Failure to follow security guidelines may result in revocation of the Courtesy ID.
6.22 CONTRACTOR EMPLOYEE MANAGEMENT
6.22.1 Contractor shall endeavor to maintain the personnel proposed in their offer throughout
the implementation of the Solution. In the event that Contractor personnel's employment
status changes, Contractor shall provide County a list of proposed candidates with
equivalent experience with the Solution. County reserves the right to assist in the
selection of the replacement candidate. Under no circumstances is it acceptable for the
implementation schedule to be impacted by a personnel change on the part of the
Contractor.
6.22.2 Contractor shall retain qualified personnel and resources to accomplish the requirements
contained in Exhibit B. As such, the Contractor shall continuously maintain an adequate
qualified staff with suitable management, professional, trade, or administrative expertise

SERIAL 170002-RFP
to assure that work is scheduled, perfo med, and completed in accordance with the
requirements.
6.22.3 The Contractor's personnel records shall document thorough, accurate, and complete
experience, education levels, certifications, and/or any other required qualifications
which demonstrate that all personnel employed for work under the contract have
adequate and appropriate qualifications.
6.22.4 The Contractor shall take any and all action necessary to ensure the conduct of its
employees is professional and complies with Contractor and County rules and policies.
6.22.5 The Contractor shall at all times be fully accountable for its employees and for
adequately addressing all issues raised by their presence on site.
6.22.6 Contractor shall not reassign any provided personnel without the express consent of the
County.
6.22.7 County reserves the right to immediately remove from its premises any Contractor
personnel it detei mines is a risk to County operations.
6.22.8 County reserves the right to request the replacement of Contractor personnel at any time,
for any reason. Said requested removal shall not be subject to part 6.22.1 of this section.
6.23 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.24 ADDITIONS/DELETIONS OF SERVICE:
6.24.1 The County reserves the right to add and/or delete materials and services to a Contract. If
a service requirement is deleted, payment to the Contractor will be reduced
proportionately, to the amount of service reduced in accordance with the bid price. If
additional materials or services are required from a Contract, prices for such additions
will be negotiated between the Contractor and the County.
6.24.2 The County reserves the right of final approval on proposed staff for all work to
performed under this Agreement. Also, upon request by the County, the Contractor will
be required to remove any employees working on County projects and substitute
personnel based on the discretion of the County within two business days, unless
previously approved by the County.
6.25 VALIDITY:
The invalidity, in whole or in part, of any provision of this Contract shall not void or affect the
validity of any other provision of the Contract.
6.26 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.27 RIGHTS IN DATA:
The County shall have the use of data and reports resulting from a Contract without additional cost
or other restriction except as may be established by law or applicable regulation. Each party shall
supply to the other party, upon request, any available information that is relevant to a Contract and
to the performance thereunder. All reports, analyses, documents, designs, methods, materials or
documentation developed or conceived by Contractor in connection with the project, except for
the Utilities and Generic Enhancements (the "Work Product"), shall be considered "Works Made

SERIAL 170002-RFP
for Hire" as defmed in 17 U.S.C. §101 and the County shall be the sole and exclusive owner
thereof The County acknowledges that Contractor has developed computer software, ideas,
designs, methods, specifications, inventions, concepts, information, know-how, experience,
techniques, documentation and other pre-existing intellectual property (collectively, the
"Utilities"). All rights in the Utilities and any generic or non-County-specific computer software
or other intellectual property (including, but not limited to, improvements, extensions,
enhancements and modifications to the Utilities) made, developed, conceived or reduced to
practice by Contractor in connection with its performing services hereunder (collectively,
"Generic Enhancements") shall be owned solely by Contractor, whether or not incorporated into
the project. If any Utilities or Generic Enhancements are incorporated into the project, then upon
payment of all amounts due hereunder, Contractor grants to the County a worldwide, perpetual,
royalty-free and non-exclusive limited license to use such Utilities and Generic Enhancements for
the County's own use solely in connection with the County's use of the Work Product. Subject to
the parties' mutual obligation of confidentiality, Contractor will be free to use the concepts,
techniques, and know-how used in connection with the projects. In addition, Contractor will
continue to be free to perform similar services for its other clients using the knowledge, skills and
experience obtained during the projects.
6.28 NON-DISCRIMINATION:
CONTRACTOR agrees to comply with all provisions and requirements of Arizona Executive
Order 2009-09 including flow down of all provisions and requirements to any subcontractors.
Executive Order 2009-09 supersedes Executive order 99-4 and amends Executive order 75-5 and
may be viewed and downloaded at the Governor of the State of Arizona's website
http://azmemory.azlibrary.gov/cdm/singleitem/collection/execorders/id/680/rec/1 which is hereby
incorporated into this contract as if set forth in full herein. During the performance of this contract,
CONTRACTOR shall not discriminate against any employee, client or any other individual in any
way because of that person's age, race, creed, color, religion, sex, disability or national origin.
6.29 ISRAEL BOYCOTT:
By signing this Contract, the Contractor certifies that they are in compliance with Article 9,
Arizona Revised Statutes Section 35-393 et seq.
6.30 CERTIFICATION REGARDING DEBARMENT AND SUSPENSION
The undersigned (authorized official signing for the Contractor) certifies to the best of his or her
knowledge and belief, that the Contractor;
6.30.1.1 is not presently debarred, suspended, proposed for debarment, declared
ineligible, or voluntarily excluded from covered transactions by any Federal
Depal tment or agency;
6.30.1.2 that any corporate officer of the contractor has 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.30.1.3 that no corporate officers of the contractor are presently indicted or otherwise
criminally or civilly charged by any government entity (Federal, State or local)
with commission of any of the offenses enumerated in paragraph (2) of this
certification; and
6.30.1.4 has not within a 3-year period preceding this Contract had one or more public
transactions (Federal, State or local) terminated for cause of default.

SERIAL 170002-RFP
6.30.1 The Contractor agrees to include, without modification, this clause in all lower tier
covered transactions (i.e. transactions with subcontractors) and in all solicitations for
lower tier covered transactions related to this Contract.
6.31 VERIFICATION REGARDING COMPLIANCE WITH ARIZONA REVISED STATUTES §41-
4401 AND FEDERAL IMMIGRATION LAWS AND REGULATIONS:
6.31.1 By entering into the Contract, the Contractor warrants compliance with the Immigration
and Nationality Act (INA using e-verify) and all other federal immigration laws and
regulations related to the immigration status of its employees and A.R.S. §23-214(A). The
contractor shall obtain statements from its subcontractors certifying compliance and shall
furnish the statements to the Procurement Officer upon request. These warranties shall
remain in effect through the term of the Contract. The Contractor and its subcontractors
shall also maintain Employment Eligibility Verification forms (I-9) as required by the
Immigration Refoun 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. 1-9 forms are available
for download at USCIS.GOV .
6.31.2 The County retains the legal right to inspect Contractor and Subcontractor E-Verify and 19
documents for employees performing work under this Contract to verify compliance with
paragraph 6.31.1 of this Section. Contractor and subcontractor shall be given reasonable
notice of the County's intent to inspect and shall make the documents available at the time
and date specified. Should the County suspect or find that the Contractor or any of its
subcontractors are not in compliance, the County will consider this a material breach of the
contract and may pursue any and all remedies allowed by law, including, but not limited to:
suspension of work, termination of the Contract for default, and suspension and/or
debarment of the Contractor. All costs necessary to verify compliance are the responsibility
of the Contractor.
6.32 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 Disbatment or Suspension under MC1-902.
An attempt to influence includes, but is not limited to:
6.32.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.32.2 That is offered or given with the intent to influence a decision, obtain a contract, gamer
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.33 UNIFORM ADMINISTRATIVE REQUIREMENTS
By entering into this Contract the Contractor agrees to comply with all applicable provisions of
Title 2, Subtitle A, Chapter II, PART 200—UNIFORM ADMINISTRATIVE REQUIREMENTS,
COST PRINCIPLES, AND AUDIT REQUIREMENTS FOR FEDERAL AWARDS contained in
Title 2 C.F.R. § 200 et seq.

SERIAL 170002-RFP
6.34 ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT AND/OR
OTHER REVIEW:
6.34.1 In accordance with section MCI 371 of the Maricopa County Procurement Code the
Contractor 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. After advance written notice to Contractor, the
County, Federal or State auditors and any other persons duly authorized by the
Depai Latent shall have full access to, and the right to examine, copy and make use of, any
and all said materials at a time and place not disruptive to Contractor's normal business.
6.34.2 If the Contractor's books, records , accounts, statements, reports, files, and other records
and back-up documentation relevant to this Contract are not sufficient to support and
document that requested services were provided, the Contractor shall reimburse Maricopa
County for the services not so adequately supported and documented.
6.34.3 If at any time it is determined by the County that a cost for which payment has been made
is a disallowed cost, the County shall notify the Contractor 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 invoices, request for credit,
request for a check or deduction from current billings Submitted by the Contractor by the
amount of the disallowance, or to require reimbursement forthwith of the disallowed
amount by the Contractor by issuing a check payable to Maricopa County.
6.35 AUDIT DISALLOWANCES:
If at any time, County determines that a cost for which payment has been made is a disallowed
cost, such as overpayment, County shall notify the Contractor in writing of the disallowance.
County shall also state the means of correction, which may be but shall not be limited to
adjustment of any future claim submitted by the Contractor by the amount of the disallowance, or
to require repayment of the disallowed amount by the Contractor.
6.36 OFFSET FOR DAMAGES;
In addition to all other remedies at Law or Equity, the County may offset from any money due to
the Contractor any amounts Contractor owes to the County for damages resulting from breach or
deficiencies in performance of the contract.
6.37 PUBLIC RECORDS:
Under Arizona law, all Contracts are public records and must be retained by the Records Manager
at the Office of Procurement Services. Contracts shall be open to public inspection and copying
after Contract award and execution, except for such Contracts or sections thereof determined to
contain proprietary or confidential information by the Office of Procurement Services. The
Records Manager of the Office of Procurement Services shall determine whether the identified
information is confidential pursuant to the Maricopa County Procurement Code. Each party may
have access to proprietary information, trade secrets, and/or other confidential information made
available by the other, and each party agrees to protect that confidential information in the same
manner as it would protect our own confidential information of like kind, and in any case with no
less than a commercially reasonable degree of care.
6.38 PRICES:
Contractor warrants that prices extended to County under this Contract are no higher than the
current rates being offered to other Contractor customers for these similar services.

SERIAL 170002-RF'P
6.39 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.40 RELATIONSHIPS:
In the performance of the services described herein, the Contractor shall act solely as an
independent contractor, and nothing herein or implied herein shall at any time be construed as to
create the relationship of employer and employee, co-employee, partnership, principal and agent,
or joint venture between the County and the Contractor.
6.41 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.42 ORDER OF PRECEDENCE:
In the event of a conflict in the provisions of this Contract and Contractor's license agreement, if
applicable, the terms of this Contract shall prevail.
6.43 INCORPORATION OF DOCUMENTS:
The following are to be attached to and made part of this Contract:
6.43.1 Exhibit A, Pricing;
6.43.2 Exhibit B, Scope of Work;
6.43.3 Exhibit C, Software License and Maintenance Agreement;
6.43.4 Exhibit D, Software Support and Service Level Agreement;
6.43.5 Exhibit E, Office of Procurement Services Contractor Travel and Per Diem Policy;
6.43.6 Appendix 1, Functional Requirements;
6.43.7 Appendix 2, Non-Functional Technical Requirements;
6.43.8 Appendix 4, Reporting Requirements;
6.43.9 Appendix 3, Interface Matrix;
6.44 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 Contractor:
Ken Bowles
Chief Financial Officer
4830 West Kennedy Blvd., Suite 890
Tampa, FL 33609

SERIAL 170002-RFP
TIN WITNESS 'WHEREOF, this Contract is executed on the date set forth above.
CONTRACTOR
AUTHORIZED SIGNATURE
jo5h Jaquish, Vice President Public Sector Ken Bowles, Chief Financial Officer
PRINTED NAME AND TITLE PRINTED NAME AND TITLE
4830 W. Kennedy Blvd. #890 Tampa, FL 33609 4830 W. Kennedy Blvd. #890 Tampa, FL 33609
A DDRESS ADDRESS
February 20_ 2017 February 20,2017
DATE DATE
MARICOPA COUNTY SHERIFF'S OFFICE
Shelly Bunn,LIDeputy Chief (Technology Bureau) DA
MARICOPA COUNTY
CHAIRMAN, BOARD OF SUPERVISORS DATE
ATTESTED:
CLERK OF THE BOARD DATE
APPROVED AS TO FORM:
DEPUTY COUNTY ATTORNEY DATE

SERIAL 170002-RFP
EXHIBIT A, PRICE AGREEMENT
SERIAL 170002-RFP
NIGP CODE: 208-57
CONTRACTORS NAME: Tribridge Holdings, LLC
COUNTY VENDOR NUMBER: VS0000001100
ADDRESS: 4830 W. Kennedy Blvd, Suite 890
Tampa, FL 33609
P.O. ADDRESS: N/A
TELEPHONE NUMBER: 877-744-1360
FACSIMILE NUMBER: 813-287-8688
WEB SITE: www.tribridge.com
CONTACT (REPRESENTATIVE): John Schloemann
REPRESENTATIVE'S E-MAIL ADDRESS: john.schloemann@tribridge.com
Will Allow Other Governmental Entities to Purchase from this Contract [X] Yes
Payment Terms
[ X ] NET 30 DAYS
1.0 PRICING: Initial Contract Term Not To Exceed: $11,142,824.00 (plus applicable taxes)
2.0 Implementation and Maintenance Line item detail.
Description of Item Total Cost
New JMS Software License Costs w/ Yr land Yr 2 Maintenance $ 2,348,009
Software Maintenance and Support Years 3-10 $ 2,721,920
Implementation Professional Services $ 4,422,895
Travel Costs* Invoiced at actual cost $ 550,000
Miscellaneous Costs *Not included in Contract NTE amount* $ 355,344
Software Upgrade Year 6 $ 550,000
Software Upgrade Year 10 $ 550,000
Total Cost
$ 11,142,824.00

Maintenance and Support
Contract Year Total Cost
1 $0
2 $0
3 $340,240
4 $340,240
5 $340,240
6 $340,240
7 $340,240
8 $340,240
9 $340,240
10 $340,240
Total Cost $2,721,920
Projected Maintenance and Support *in the event of renewal
Contract Year Total Cost
11 $350,447
12 $360,961
13 $371,789
14 $382,943
15 $394,431
16 $406,264
17 $418,452
18 $431,006
19 $443,936
20 $457,254
Total Cost $4,017,484

25% 50% 50% 100% 100% 25% 25% 25% 25% 25% 25% 25% 25% 25% 25%
170002-RFP Notes
SERIAL Estimated Timeline 2017 2017 2017 2017 2017 2017 2017 2017 2017 March, 2018 March, 2018 March, 2018 2018 2018 2018
April, April, April, April, April, May, Sept, Sept, Sept, Aug, Sept, Dec,
$347,975 $14,154 $105,405 $26,991 $90,000 $347,975 $347,975 $7,077 $52,703 $347,975 $7,077 $52,703 $1,748,009 $150,000 $150,000 $150,000
Cost
Year for Year year Year
& 1 system, users engine Tool & 1 & 1 system, users & 1 system, users Accounting, Accounting,
Year end for based tool. Integration Year Year end for Year end for Accounting,
and License Training tool Rules and and License Training tool and License Training tool Trust Software Trust Software
License Maintenance - help - Customization - License Maintenance License Maintenance - help License Maintenance - help - - Trust -
Description Software License self License License Software License self Software License self License Banking License Banking License
User Software and User Software User Software and User Software and Software
Software 2 Perpetual Software Software Offender360. Software Software 2 Software 2 Perpetual Software Software 2 Perpetual Software Software Inmate Software Inmate Software
Perpetual documentation Perpetual Perpetual documentation Perpetual documentation Perpetual Perpetual Banking
Perpetual Perpetual Perpetual Perpetual Perpetual Perpetual Inmate
Dev - Prod Prod Prod 2
Milestone - - - Phase Production
Installation Install Install Install Dev
I Kickoff Kickoff Kickoff Kickoff Kickoff #2 #2 #2 360 360 360 Kickoff- - -
Phase Project Project Project Project Project Software Prototype Prototype Prototype Offender Offender Offender Project Installation Installation
Portal Portal Portal
Web Manager Web Web
ware/Misc/Maintenance/Support Product Platform Platform Platform
ADXstudio Formula ADXstudio ADXstudio
EPS - Insight EPS EPS Total
Offender360 Microsoft Epilogue 52 North Scribe Offender360 Offender360 Microsoft Epilogue Offender360 Microsoft Epilogue I Phase CACTAS CACTAS CACTAS
So

25% 5% 8% 10% 17% 22% 25% 27% 29% 31% 35% 41% 48%
170002-RFP Complete Financial
SERIAL 2019 Complete Phase 10% 50%
Feb,
$150,000 $600,000 $2,348,009 Estimated Delivery 2017 2017 2017 2017 2017 2017 2017 2017 2017 2017 2017 2017
April, May, Ma July, July, July, Aug, Aug, Aug, Sept, Sept, Oct,
Accounting, Plan Development
(FRD) (TRD) Test
Trust Software Management - - (FDD)
- Design Solution Document Document Solution
License Banking Deliverable Plan Plan Document
Software Inmate Specification Architecture Management Dynamics/0360 Requirements Requirements Dynamics/0360 Document
Management Schedule #1 Plan #2 Design Desian
Perpetual Project Requirements Enterprise Risk/Issue Installed Functional Technical Project Prototype Installed Testing Prototype Functional Report
- Requirements Requirements Schedule #1 Test - #2 Document
Test Milestone Kickoff Iniation Microsoft (FRD) (TRD) Prototype Microsoft Plan Prototype Design (FDD) Design
Solution Project Project Documentation Install Dynamics/0360 Development Functional Document Technical Document Project Solution Install Dynamics/0360 Testing Solution Functional Document Report
Full
Services
Consulting Phase/Stage Define Lti i
- 1 Des - 2
Total Software Project 1/State Stage
CACTAS 2 Professional , 1
Phase Total Phase Phase

53% 55% 58% 63% 65% 72% 80% 88% 92% 97% 3% 7% 10%
170002-RFP % Complete Financial
92% 100% 10%
SERIAL Complete Phase
2017 2018 2018 2018 2018 2018 2018 2018 2018 2018 2018 2018 2018
Nov, Jan, Feb, Feb, Feb, March, March, June, July, July. Estimated Delivery August, Sept, Sept,
Plan
Production Transfer Dev
- -
Plan Solution Acceptance Knowledge Strategy Plan Plan Deliverable Design Component
Training Jobs Team Cutover Document Operations Release Plan Solution
#1 Plan #2 Dynamics/0360 Scribe Reports Completion/System Policy & & Management Architecture
Review Training Technical/Analyst Review Support Security Implementation Plan Solution New
Build User Build Installed Developed Developed UAT MCSO JMS Cutover JMS Maintenance Configuration Project Enterprise Installed
Training Cutover Component
Build Plan Build - Development Deployment Milestone
#1 Training Technical/Analyst #2 Microsoft Dynamics/0360 Migration Testing Documentation Live/System Kickoff Initiation Documentation Solution Dev -
Configuration Review User Plan Configuration Review Install Production Data Development Report )1ution Project Go Project Project New Tristall
Test
Sr, Phase/Stage
Build Deploy
- 3 - 4 -
-e Project
1"Stao 1/Stage 2.3ta!2_,;
Phase Phase Phase

17% 22% 25% 27% 31% 36% 40% 46% 52% 54% 55% 58% 64% 69% 75% 85% 91% 95% 96% 100%
170002-RFP
50% 92% 100%
SERIAL
2018 2018 2018 2018 2018 2018 2018 2018 2018 2018 2018 2018 2018 2018 2019 2019 2019 2019 2019 2019
Oct, Oct, Oct, Oct, Oct, Oct, Nov, Nov, Nov. Nov, Nov, Dec, Dec, Dec, Jan, Jan, Feb, Mar, Jan, Mar,
Plan
(FRD) (TRD) Test Prod Transfer
- -
(FDD)
Document Document Component Plan Component Knowledge Strategy Plan Plan
Document Document Training Reports Cutover Operations Release
Requirements Requirements Solution Plan Solution Team Policy Document
Design #1 #2 #3 SSRS & &
New Plan #1 #2 #3 Design Training Technical/Analyst New Review Review Review Support Security Plan Solution
Functional Technical Installed Testing Prototype Prototype Prototype Functional Report Installed Developed MCSO Implementation Cutover Maintenance Configuration
User Build Build Build JMS JMS
Component Document Training Component Live/System Live/System
Requirements (FRD) Requirements (TRD) Design (FDD) #1 #2 #3 Development Testing Deployment Go Go
Solution Test Plan #1 #2 #3 Desian Plan (User/Technical) Technical/Analyst Solution Prod Review Review Review - -
- - Documentation 2A 2B
Functional Document Technical Document New Install Testing Prototype Prototype Prototype Functional Document Report Training Plan New Install Build Build Build Report Solution Project Phase Cutover Phase
est
J
&_
Design Build Deploy
- - 3 - 4
1/Stag 41,ge 2/Stage
L
NuIse Phase Phase

included pricing license
170002-RFP is
Comment Test license Production
SERIAL and Production the in
Development the Included pricing
in
Cost $0 $0
Total
Classification, Operations Classification, Jail Unit Sub-Total
Jail Housing, Visitation, per Cost Software
Housing, Visitation, Test
Scheduling, &
Scheduling, Appointments/Holds, Units Development
Appointments/Holds, Movements, of
Movements, Unit Measure
Reports,
Reports,
Cases/Charges/Dispositions/Court Incident Cases/Charges/Dispositions/Court Incident
following Description Functionality Functionality
Cutover the include Appeals/Grievances, Appeals/Grievances, Transportation JMS JMS
will Court Court Environment Core Core
Sessions Property, Discipline, Property, Discipline, Operations, Accounting, Operations, Accounting, DETAIL Module Software Test
Review Booking, Booking, Inmate Pre-Booking Pre-Booking Court Trust / Application :& Environment
groups - Inmate - - 1 - 2 Security - Court - Trust - - 1 - 2 - 3 LICENSE Application JMS Development Offender360 Training Offender360
Prototype/Build 1 2 Review Review 1 2 3 Review Review Review -
functional 1 Phase Prototype Release Prototype Build Release Build Operations, 2 Phase Prototype Prototype Transportation Prototype Canteen Build Build Build Canteen SOFTWARE # SHIELD 1. 1.
*

170002-RFP for 3,233 in MCSO software Software owns 7, version License License Dynamics License
license server included Software that proposed. MCSO OS Use Use Use
SERIAL Software Prod CALs Assumes Office tools. software System Assumes Windows Perpetual entities Perpetual Microsoft Connections Perpetual
and Dev environements Device Users Administrative Microsoft productivity testing Operating 10. or Unlimited Unlimited Source Platform
Perpetual Test, 25 Named No proposed. owns and No No proposed. Microsoft 8,8.1 Enterprise - Enterprise - Data Enterprise EPS -
$0 $0 $0 $26,991 $90,000
1,118,466 1,118,466 1,118,466 210,810.00
$ $ - $ $
345.95 0.00 Sub-Total Sub-Total Management) 26,991.00 90,000.00 210,810.00
Software Software Release
25 Environment Application Management; 1 1 1
3,233
Production JMS Change
Named User Device Technical Tool Technical Tool Training Tool
Management;
calculation tool. for Dynamics System self and
Requirements Third-party) for Data designed - Platform software of user
Functionality Functionality engine sentence Customization and Tool training end
JMS JMS Management; APIs, based Offender360 Migration Offender360/Microsoft BPS user end documentation for tools Offender360.
Core Core tools, Rules module. Data Integration platform Epilogue and help
Project integration
Environment (e.g.. Platform
Software Software (Technical Formula Insight EPS
Production Offender360 Offender360 Software System Software - North52 Manager - Scribe Epilogue
1. 2. Administrative 1. Testing 1. Operating 1. Other 1. 2. 3.

170002-RFP - Users License,
SERIAL License Use External Enterprise Users
Perpetual Unlimited Perpetual Unlimited
services.
28,308.00 600,000.00 $956,109 $273,434 $131,489 2,348,009 2,479,498 development.
$ $ interface
28,308.00 600,000.00 Sub-Total 2 Year Tax Total Total Comment Tribridge's interface
Maintenance/Support Sales License Tax for option Travel.
Software Applicable Software with Represents Added Includes
Other Support
1 1 & Cost $43,090 $46,190 $14,880 $44,640 $31,000 $150,000
Maintennace Total $ 329,800
Application Application &.2 5 — Total documentation
1 Year 4 of proposal and
and License of Development development our in development
Public Description Configuration/Customization Accounting/Commisary Interface Enhancements Configuration/Customization included
and Information Accounting Software Portal Application performs interfaces tools design,
Agency for Canteen/Trust Adxstudio DocuSign Trust Functionality Custom Tribridge complex Supplemental configuration include
External Requests Financials DETAIL Costs Software costs
the of
ADXstudio CUSTOMIZATION Configuration/Customization Trust for budget use the Scribe)
Portal Systems/CACTAS Module Signature Scanning interfaces on based and Configuration/Customization
Microsoft Web Cashless ARE Portals Electronic Commissary/Inmate Accounting Barcode Customization optional Enhancements Assumptions: is Cost (North52
4. 5. Software Public - -
# 1. 2. 3. 4. 5. 6.

170002-RFP
SERIAL
Analysis (conversion
data
Cost $22,785 $22,785 $113,770 $18,910 $38,130 $22,785 $18,910 these the in are to Gap the scope only)
Total 258,075 design areas Insight, Comment changes in in Dynamics
$ analysis, support all on reduction
Total to in Scribe based documented - DB
planning, expected County tool, and staging
is Adjustments conversion Document
Implementation the Vendor Maricopa integration from C
for to
and The support software Cost $190,960 $26,350 Attachment
Test responsibility Total 217,310 of
framework/tools. provide proposed $ 12
Description Build, take to to and Total Section
Design, intent effort the for Proposal. Journal, System in
interface of System Migration found
Interface MCSO's level estimates Cost - Operations Canteen Accounting & be can
is Vendors the A Description
"It : the reflects Training JMS, Court Fund One Conversion migration
Costs states utilizing RFP. Attachment Legacy Operations/Transportation Inmate Business data
County estimate the Includes Pre-Booking, Includes Data the
Interfaces in document, SAP
Implementation Maricopa interface defined DETAIL regarding
Support 9 required this of to Accounting details
and Remediation Section Tribridge's integrations tab SUPPORT Conversion
Test Documentation Support Go-Live of Training Name Migration and Full
Interface Build, Loads & and C, such, all for AND File and Data —
DETAIL Design, and Data Loads Testing Sync Attachment implementation As above the in JMS Canteen Migration
Requirements Implementation Data Assumptions: activities." Conversion Offender360 Assumptions:
INTERFACE Design Sample Full System Initial Per and table provided MAINTENANCE Legacy Legacy Data
# Interface 1. 2. 3. 4. 5. 6. 7. 1 # Data 1. 2.

170002-RFP
SERIAL on on 2 phase support
not based as Document. based with Database, live
ledger will areas Court Finance management, support approach Reporting Design, go 1
and all Journal, & Analysis Court phase
general daily JMS. Comment across Gap project live go support Enhanced Management deployment
enter refreshed New spread Operations Pre-Booking the for and implementation to extended
the in time testing timeline. Data, of
manually is to Adjustments to Operations, documented Additional phase Adjustements Scheduling/Case split/extended week
will JMS. System migrated changes system two extended Snapshot Four
staff New be $0
Services the not Cost $209,647 $294,866 $578,433 $749,708 $1,157,385 $282,078 $185,593 $100,905 $205,344
to Operations/Transportation will Total 3,763,959
Financial migrated and $
hours
MCSO SAP. be not 72 Review Functional Document layout, defined Acceptance Total
from will Court after and workflow, Cost
IFCS, and the in purged Prototype Matrix, Design design requirements Phases Management User
with converted years Data is & messages, Design queries and Support Support Implementation
balances be three — System Description Traceability Technical screen MCSO and and System and
will after SYSTEM Requirements & creation, automation, on Discover Engagement views support Advisement Live Go Other
reconciling data purged Pre-Booking Document, based reports, Process,
After other No is data the Functional Requirements Design Table/field business tenplates the during and Project Custom Business Testing live go Solution Supplemental
in Post
— go-live. "0.1" Data Costs
SYSTEM at OPERATIONS/TRANSPORTATION JMS. — Support
JMS JOURNAL— SYSTEM Implementation
New SYSTEM New Live
JMS ACCOUNTING the the to Activity Management Support Go
into MUGSHOT OPERATIONS PRE-BOOKING DETAIL Services Analysis Testing
-LEGACY IFCS SAP balances COURT migrated essional Needs Design Configuration Programming Project Reporting System Live Other Supplemental
- - - - - be - SERVICE Go
# Pro 1. 2. 3. 4. 5. 6. . 8. 9. 10.

MCSO. be
to will
fee RFP
fixed Offender360 the in
a as into identified per Cost Hour $195.00 $215.00 $175.00 $155.00 $215.00 $155.00 $155.00 $155.00 $155.00 $155.00 $125.00 $135.00 $125.00 $125.00 $125.00
project built
the queries
deliver (SDK) All
to tools RFP.
resources configuration the in
our identified tools.
all Find Writer)
across platform reports Advanced
hours Dynamics configuration. the Role Technical
and build Dynamics or
rate Microsoft calculation to Position/ Developer
blended SSRS Microsoft $96,720 $205,344 $279,744
the of use sentence using - - - Manager Customization
on the for standard $0 - Court Extension Deploy Manager Support Staff (Curriculum
based are assume North52 development the Items - Pilot DB/Snapshot Enhanced Week Extended Manager Analyst Release Manager Product Staff
provided of use report using Scope Four Split, CARD Rates Architect Administrator Development Administrator Business & Manager Conversion & Configuration Conversion Development Development
Assumptions Configurations the Custom developed Additional Barcode/RFID Replicated Rqmts/Design 1 2 RATE Labor Project Enterprise Manager Configuration Programming
Cost - - and - $29,760 Phase Phase Senior Data Senior Project Senior Test Interface Data General Data Interface Training
HOURLY # Hourly 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.

$135.00 $125.00 $125.00 $135.00
Hours) Hours)
Business Business
(Regular (After
(Trainer) Support Support Consulting
Desk Desk
Training Help Help Product
16. 17. 18. 19.

SERIAL 170002-RFP
EXHIBIT B, SCOPE OF WORK
TABLE OF CONTENTS:
Part One — Statement of Requirements
Part Two — Statement of Work

SERIAL 170002-RFP
PART ONE — STATEMENT OF REQUIREMENTS
1.0 INTENT
The purpose of this Contract is to award a Contractor who will partner with the Maricopa County Sheriffs
Office (MCSO) to successfully implement a commercial off-the-shelf (COTS) SHIELD New Jail
Management System solution (SHIELD New JMS). The solution must be configurable and should meet
the needs of the MCSO with minimal customization. It is also imperative that the solution be based upon
widely-adopted technical standards that facilitate seamless integration and interoperability with external
entities.
The SHIELD New JMS Project includes all software, and related services such as hardware identification,
sizing, software installation, system configuration, interfaces, data migration, training, and other
development or implementation tasks. In addition to the project implementation components listed,
Contractors shall include warranty, maintenance and support services that total ten (10) years, with the
option of a ten (10) year extension. The success of the project will be defined by end user acceptance of
the proposed solution.
The JMS solution will replace and enhance both "Core" and "Ancillary" functionality that is now available
in disparate systems, including the MCSO legacy Jail Management System (Legacy JMS), Inmate Fund
Canteen System (IFCS), Pre-Booking, Operations Journal (OA Court Operations, and SAP Business One
Accounting Systems. MCSO seeks a proven, fully-integrated solution requiring minimal customization to
address the following "Core" business processes:
• Intake
• Classification
• Property and Clothing
• Housing
• Grievance and Appeals Processing
• Court Operations
• Inmate Trust and Accounting
• Canteen
• Inmate Discipline
• Inmate Programs
• Visitation
• Release
MCSO highly desires the following "Ancillary" functionality:
• Pre-Booking
• Transportation
• Operations Journal
Additionally, MCSO has identified the following priorities for SHIELD New JMS functionality:
• Application shall be web-based
• Application shall be highly configurable
Key outcomes expected from the New Jail Management System Project are to:
a) Replace functionality of existing "legacy" detention systems;
b) Provide new and enhanced business functionality as specified, and/or as included in the
Contractor's standard product;
c) Successfully map and convert/migrate data from existing "legacy" databases;
d) Successfully interface with other systems; and
e) Operate on hardware and software operating environments that are supportable and maintainable.

SERIAL 170002-RFP
Future phases of the SHIELD New JMS Project will further increase, enhance, and integrate functionality
of the core system. Expansion of the SHIELD New JMS will proceed incrementally, subject to business
priorities established by MCSO and/or other resource constraints.
1.1 SHIELD - NEW JMS PROJECT GOALS AND OBJECTIVES
Acquisition and implementation of a New Jail Management solution is an enterprise-level project
that will impact the Maricopa County Sheriff's Office for many years to come. Key goals for the
project are to:
(1) Replace the Legacy JMS, Pre-Booking, IFCS, OJ, Court Operations, and SAP Business One
Accounting and related detention interfaces with a state-of-the-art commercial off-the-shelf
(COTS) solution that meets or exceeds needs of the Sheriff's Office;
(2) Complete the implementation and replacement of "Core" JMS functionality;
(3) Deliver a fully-integrated SHIELD New JMS solution on time and within budget;
(4) Achieve sufficient knowledge transfer through training and documentation to allow in-house
technical staff to easily enhance and support the new system and technologies going forward;
(5) Provide a technologically sound platform for expansion of information services into the
future; and
(6) Establish a long term maintenance and support contract.
Other project objectives are to:
• Provide ready access to near and/or real-time data
• Automate data input processes
• Reduce paper-based documentation and tracking
• Streamline business workflows to reduce redundancy and repetitive action across the
organization
• Improve query and reporting capabilities
• Provide accurate statistical data and dashboards
• Enhance the ability to measure the effectiveness of strategies and tactics in a timely manner
• Maximize resource management
• Implement a solution that meets GAAP and other regulatory or court-ordered requirements
• Provide audit functionality for all transactions and user activity
• Improve and enhance data sharing with outside agencies
• Leverage new technologies to reduce the need for customization and software development
• Successfully implement the SHIELD New JMS solution with minimal stress and disruption to
users and business operations
2.0 MCSO ASSUMPTIONS
The following assumptions are identified for the project. Should any of these be found to be inaccurate or
deficient in performance, each party must immediately bring this to the attention of the other party's Project
Manager(s). Any unresolved item or deficiency will be documented and escalated as a project issue.
2.1 The Contractor will provide staff with the documented required expertise.
2.2 The Contractor will provide staff at the commitment level required in the contract.
2.3 The Contractor will provide sufficient lead time for all meetings requiring MCSO attendance so
that employee work schedules and duties will be minimally impacted.
2.4 The Contractor will provide hardware specifications and sizing for all components needed to
implement the New JMS solution in the MCSO environment.
2.5 All hardware for the project is to be purchased and installed by MCSO.
2.6 MCSO is responsible for hardware support, and network configuration and support.

SERIAL 170002-RFP
2.7 The Contractor is responsible, up to and through the Warranty Period, for tuning the solution in
the production environment while transferring knowledge to MCSO staff to monitor and tune in
the future.
2.8 Each phase that introduces new functionality shall be followed by a forty-five (45) day Warranty
Period which may be extended for an additional forty-five (45) day period with the mutual consent
of the parties.
2.9 "As Is" business processes are documented sufficiently to serve as a tool that can be utilized
during gap analysis, configuration, test case development, and training module development.
2.10 The Contractor's work hours must be consistent with MCSO key staff. Sheriffs Office usual
business hours are 8:00A_M to 5:00PM (Arizona time), Monday through Friday, except for
standard holidays. However, MCSO jail facilities are operated 24 hours per day, 7 days per week,
365 days per year. Core business hours will be mutually agreed upon by MCSO and the
Contractor.
2.11 Any modifications to the Contractor's approach to perform the Contract, including this Statement
of Work shall be defined, documented, and approved by the Parties, in writing, in accordance with
the Change Control Process detailed in Exhibit B, Part 2, Section 1.4, prior to starting. As
required, formal written amendments to the Contract will be executed for changes to project scope
or cost.
2.12 The Contractor and the Sheriffs Office are mutually obligated to keep open and regular channels
of communication in order to ensure the successful execution of this Contract. Both parties are
responsible for communicating any potential problem or issue to the MCSO Project Manager(s)
and the Contractor's Project Manager, respectively, within two (2) business days of becoming
aware of the problem or issue.
2.13 The Contractor shall begin work as soon as reasonably practicable following the issuance of a
Purchase Order and in accordance with the project schedule.
2.14 The Contractor will ensure that scheduled tasks requiring the participation of the core project team
will take into account all activities and tasks that each team member is involved in/responsible for
to allow for adequate time to complete.
2.15 The Contractor will participate in MCSO Executive Steering Committee meetings as necessary.
2.16 The Contractor will provide monthly status reports within five (5) business days of the end of each
month via email to the County Project Manager(s).
2.17 The Contractor will deliver a fully tuned and tested Jail management solution meeting all of the
functional and non-functional requirements in the contract.
2.18 The Contractor will maintain key qualified personnel for the duration of the project.
2.19 The Contractor will provide knowledge support to County resources. This knowledge support
includes Licensed Software and Microsoft Dynamics.
2.20 The Contractor agrees and acknowledges that Contractor will serve as the single source of support
related to the Licensed Software and Microsoft Dynamics. It is noted that Contractor is not
responsible for County-related deliverables.
2.21 County's billing requirements will be fully supported by the Phase 1 implementation. It is
recognized and accepted that Offender360 will provide the required source data to perform the
required billing.
2.22 The Contractor will meet all County requirements included in the contract.
2.23 All SHIELD project artifacts will be stored in Contractor's SharePoint environment. This
environment will be accessible by both Contractor and County's team members. At the
conclusion of the project, all project artifacts will be copied to County for their permanent records.
2.24 All Gaps identified in the Gap Analysis report delivered after the Gap Analysis phase of the
procurement are included in the contract.
3.0 CONTRACTOR ASSUMPTIONS:
The following assumptions are identified for the project. Should any of these be found to be inaccurate or
deficient in performance, each party must immediately bring this to the attention of the other party's Project
Manager(s). Any unresolved item or deficiency will be documented and escalated as a project issue.
3.1 General Assumptions
3.1.1 Management Commitment. A Steering Committee will be put in place to assist with
critical policy, design and procedural decisions.

SERIAL 170002-RFP
3.1.2 Project Team Commitment. The County shall make available to Contractor a core
project team to be dedicated to the project for key activities such as functional
system mapping sessions, system testing, training and "Go Live" activities. The
timeframe outlined assumes the ability to effectively coordinate the schedules of
County. Contractor shall inform County when scheduling issues have the potential
to impact the milestone dates or costs.
3.1.3 Internal IT Support. The County will identify an internal resource, typically an IT
team member, as the Microsoft Dynamics/Offender360 technical lead. This person
should be identified as early in the project as possible in order to learn as much as
possible from the Contractor team. It is the Contractor's expectation that this
person will be required to spend approximately 50 percent of his/her time on this
engagement.
3.1.4 Additional Functionality. Both County and Contractor understand and acknowledge
that existing Contractor Offender360 and Microsoft Dynamics code may contain
more modules and/or functionality than is required to deploy the scope of outlined
herein. The implementation of any functionality determined to be outside this
Contract is considered out of scope.
Contractor has assumed that the standard functionality provided by Offender360
and Microsoft Dynamics will satisfy County's requirements to accomplish key
functions. Exactly how those functions are accomplished is always open to design.
Contractor has identified which functions are supported by Offender360 and
Microsoft Dynamics, but Contractor has assumed that County is willing to
reasonably modify its business processes and procedures to work within the
standard functionality of the software, unless otherwise specifically identified. If
County is unwilling to accept this standard functionality, and customizations or
modifications of the software are required beyond what is specified in this proposal,
this will be viewed as a change in scope which may require additional time or
consulting fees to be incurred.
3.1.5 Change Orders. Contractor will work with County to execute change orders, as
appropriate, to clearly communicate additional products or services and the related
fees or costs which are outside the current scope included in this proposal.
Contractor will not c add items to the scope of work until the change order is
approved by County.
3.1.6 Communication Plan. Contractor can assist in this area if needed, but has not
included time to provide these items during this implementation. The County
personnel will be responsible for creating the messages and executing all tasks in
the communication plan on a timely basis. Change orders will be presented as a
fixed price cost for MCSO consideration and approval/rejection.
3.1.7 Project Management. Contractor will conduct weekly status meetings with the
project team and participate in Steering Committee meetings as needed throughout
the project. Contractor will prepare written status reports detailing
accomplishments, next steps, and outstanding issues on a weekly and monthly
basis. Contractor will review key decisions, budget, project timeline, and issues for
resolution. Contractor will present these weekly status updates in a discussion
format so that the County project team and management remain actively involved in
the project, and so that all questions and issues are addressed in a timely manner.
3.1.8 Site Accommodations. Contractor will perform key tasks onsite at offices at
County specified location such as design sessions, testing, training, and
deployment. A work area/project room will be dedicated for the duration of the
project with ample workstations and ports to allow access to the application and
Internet. Remote secured access (VPN) will be required to allow the Contractor to
perform some tasks from the Contractor's office. Ongoing Contractor support

SERIAL 170002-RFP
requires usage of Contractor remote support assistance tools (i.e. Team Viewer,
LogMein, over HTTP, etc.). MCSO and the Contractor will mutually agree to the
remote access tool of choice.
3.1.9 Projected Project Duration. Contractor anticipates the tasks outlined in this project
to be completed in approximately 24 months. Contractor and County both have
accountabilities to completing the project in an agreed upon duration. Items that
affect the project timeline that are County accountabilities may result in change
requests.
3.1.10 Hardware. County will be responsible for desktop hardware, interne connectivity,
etc. required to connect to the jail management solution hosted on premise.
Contractor is not providing or implementing any hardware that may be associated
with this project. The implementations of hardware and network infrastructure to
support the systems that will be implemented are the responsibility of County. All
applicable hardware and network infrastructure must to be purchased by County
and in place by the date mutually agreed to by MCSO and the Contractor.
Contractor will perfoini an infrastructure review of the applicable hardware and
network infrastructure prior software installation. Contractor's recommendation for
hardware associated with the project in support of the County's requirements can be
found in Section 11.0 Equipment.
3.1.11 Fee Review. As part of Contractor's project management services, each month or
after key milestones are accomplished Contractor will conduct a fee review process
in which we will provide details on the fees incurred as well as the fees remaining
to complete the project.
3.1.12 Deliverable Review. The County Project Manager shall review all Contractor status
reports and/or deliverables within ten (10) business days and provide written notice
to Contractor either accepting or rejecting the accuracy of each report and the
completion of each deliverable. Any subsequent deliverable reviews will be limited
to verifying resolution to the initial feedback
3.1.13 System Maintenance. County will be responsible for maintaining and
troubleshooting network and infrastructure issues. County will perform routine
daily backups of all Offender360 environments.
3.1.14 Work Stoppage/Project Delay. Upon the County's written notice to Contractor,
County may suspend or delay the Project for a time determined by County in its
sole discretion, and specified in such notice ("Project Hold"). If County notifies
Contractor of a Project Hold, the following terms apply:
3.1.14.1 Upon notice of the Project Hold, Contractor will cease all work under the
Project for the time specified in County's notice (the "Stand Down Period").
3.1.14.2 To exercise a Project Hold, County must provide Contractor 14 days' prior
written notice specifying the reason for the Project Hold and the amount of time
for the Stand Down Period. A Project Hold may necessarily result in an
extension of the fixed timeline under the Initial Project Plan described in the
agreed upon Project Plan. The Parties will negotiate in good faith to determine
an appropriate extension and an applicable Change Order reflecting the
extension and the additional associated costs.
3.1.14.3 If the Stand Down Period requested by County is greater than two weeks,
County acknowledges that Contractor cannot guarantee that the same Contractor
staff can return to the Project. However, Contractor will make commercially
reasonable efforts to have the same staffing available.

SERIAL 170002-RFP
3.1.14.4 If County requests a Stand Down Period of 2 weeks to a month, County
acknowledges that 3 days will be required for the Contractor team to reengage
under the Project. If County requests a Stand Down Period of more than a
month, County acknowledges that 7 days will be required for the Contractor
team to reengage under the Project. The reengagement time in either case will be
billed at the rate set forth in the Fees Section. If the Project is terminated,
County agrees to pay Contractor the fees that have been actually incurred up to
the date of termination. Should the termination occur between milestones,
County agrees to pay Contractor for the time incurred for work performed to
date.
4.0 TESTING AND ACCEPTANCE PLANNING:
4.1 For County's initial purchase of each software product, Contractor shall provide testing and
acceptance periods (the "Test Period") that commence upon each foimal installation. Installation
shall be defined as: a) the software is formally installed in a County specific cloud environment or
on County server(s) and/or personal computer(s); b) software is configured per County
specifications; and c) team training specific to the installation, if necessary, is complete. During
each Test Period, County shall detei mine whether the software meets the Contractor published
electronic documentation ("Specifications") and County requirements applicable to delivered
functionality. This section outlines County's testing and acceptance expectations.
4.2 The Contractor shall be responsible for developing unit and system test plans and shall provide
County with drafts of these test plans as specified in the system implementation project plan
County shall be responsible for reviewing and providing feedback on the Contractor's draft test
plans. Test plans shall include but are not limited to the following:
• Testing all software components in accordance with published functions and features
• Testing all software components in accordance with RFP/RTM specifications
• Testing all system software based on business scenarios
• Testing of all contracted data conversions and interfaces based on design and testing
defined in detailed data conversion and interface test plans specified in Section 1.3 —
Data Conversion and Interfaces
• Parallel testing prior to cutover (if parallel processing is appropriate)
• Security Testing
4.3 The Contractor shall review County's feedback on the test plans and make updates/changes
accordingly. Final Test Plans shall be submitted as contract deliverables and will require formal
sign-off prior to execution. If the Contractor wishes to perfoim any initial off-site testing prior to
software delivery, County will not consider any of the off-site testing results as being in any way a
substitute for testing the software on-site using County's development/test, training and
production environments and accepted test plans. If Contractor pre-delivery testing is performed,
County shall be provided with the results, but only for comparison to the on-site results if County
executes the same test scripts. County reserves the right to revise the test plans provided that
reasonable notice is given to the Contractor. County maintains sole authority to certify the
successful completion of any and all tests perfaimed by the Contractor on the proposed system.
4.4 The Contractor shall be responsible for conducting and/or assisting County personnel with the
following User Acceptance Testing (UAT) activities:
• Drafting a realistic User Acceptance Test Plan
• Product pedal mance testing
• Interfaces/Integration testing
• Parallel testing (if parallel processing is appropriate)
• Security testing
• Data conversion and migration testing
• Hardware and network testing
• Load testing

SERIAL 170002-RFP
• Fail-over testing
• System acceptance testing
5.0 TESTING AND ACCEPTANCE PROCESS:
The overall testing process encompasses the testing of each formal delivery of software. This
includes not only the final delivery of software per phase (if applicable), but any formal deliveries
made during the duration of the project. All Test Periods will require a formal gate review upon
completion.
5.1 SOFTWARE/SYSTEM ACCEPTANCE PROCESS:
The acceptance process and criteria set out in this section shall apply strictly to the initial
implementation project and will not apply post warranty.
5.1.1 Software System Acceptance shall be an on-going, iterative activity, which shall be
performed throughout the Contract, per applicable test plans. Software deliverables
that have passed Acceptance will not be subject to re-testing for Acceptance except
(a) to the extent they interoperate with, or are modified by, further Deliverables
undergoing Acceptance, or (b) as part of Final Acceptance. The timing for
completion of testing activities shall be mutually agreed upon and included in the
Project Plan.
5.1.2 The process for any mutually agreed to software testing prior to user acceptance
testing of Application Package Deliverables shall include the following steps:
5.1.2.1 Contractor completes an Application Package Deliverable;
5.1.2.2 Contractor configures the Deliverable and/or the Application Package in the
Delivery Platfoim with assistance from County;
5.1.2.3 Contractor provides a conference room prototype overview to demonstrate
functionality included in the Application Package including such Deliverable
and how it is intended to be used;
5.1.2.4 County completes additional testing of such Deliverable to validate the
configuration as part of the Application Package in the Delivery Platform; and
5.1.2.5 County provides Contractor with feedback about the current Deliverable, which
Contractor shall consider and, to the extent consistent with the SOW,
incorporate into the next Deliverable (or as may be mutually agreed pursuant to
a change order).
5.2 CRITERIA FOR DELIVERY AND ACCEPTANCE OF DELIVERABLES:
5.2.1 The Contractor shall submit all Deliverables to the County Representative. Each
Deliverable will be in the requisite format specified in the SOW and contain the
content required by the SOW prior to the Deliverable being submitted.
Documentation shall be delivered in one electronic version with accompanying
transmittal letters via email or deposited on the project SharePoint site with faunal
notification sent to the County Representative.
5.2.2 County Representative shall review and validate Contractor's Deliverables product
prior to Acceptance. Acceptance criteria for Deliverables shall consist of the
following:
5.2.2.1 Specific Deliverables are completed as specified in this Contract and the final
Deliverable has been rendered.
5.2.2.2 Plans, schedules, designs, documentation, and reports are approved and
completed as specified in this Contract.
5.2.2.3 All supporting Documentation is provided and complete.
5.2.2.4 All Deliverables are presented to County in the approved format (or if no such
format is approved, in an industry-standard foi mat).

SERIAL 170002-RFP
5.2.2.5 All Deliverables are at the agreed upon acceptable level of quality as defined in
this Contract.
5.2.3 County acknowledges and agrees that the Application Package, the Database, the
Documentation, and all Enhancements are licensed by Contractor and that all third
party materials are licensed by Contractor, or pursuant to the terms of the third party
license under which Contractor delivers the same, as the case may be, and that such
licenses set out County's entire right thereto, subject only to the escrow provisions
set out in the Master Services Agreement Section 6.6. Subject to the foregoing,
County shall retain unlimited rights in any other Deliverables.
5.3 Solution Testing
5.3.1 Solution testing will be conducted in two stages. (1) Contractor Delivery,
Installation, and Certification; and (2) Solution Test.
5.3.1.1 Contractor Delivery, Installation, and Certification shall include the following
tasks:
• The Contractor shall certify delivery and installation of all agreed
upon system components, modules and functionality
• Complete Technical (System Administrator) Training
• Complete Functional (User) Training
• The Contractor shall verify that all County configured tables are
properly entered or converted
• The Contractor shall certify that all system components, modules,
functionality, County configured and user defined tables are fully
operational for County use
• Delivery of Updated Requirements Traceability Matrix
• Delivery of Release Notes
5.3.1.2 Solution Test is a test period defmed in the project plan for a specified duration
and shall include the following tasks:
• Business Process Testing to ensure that the overall functionality
meets the requirements as specified in the use cases developed
during the design phase. Functional test scripts will be used to test
the delivered functionality as specified in the requirements
traceability matrix and release notes.
• System Testing to ensure that all end-to-end processes, reports,
data conversions, and interfaces are tested based on the test scripts
developed.
• User Acceptance Testing to ensure that all end-to-end processes,
reports, data conversions, and interfaces are tested based on the test
scripts developed by a select group of user acceptance testers per
guidelines detailed in Section 5.4 User Acceptance Testing.
• The Solution Test periods will consist of a duration of time agreed
to in the project plan and depend on the extent of functionality
being delivered
• During the Solution Test periods, the system shall operate properly
and in compliance with the Contractor's proposal, contract, and
system functionality defmed in the Requirements Traceability
Matrix (RTM)
• County will ensure that each functional and non-functional
requirement is met and all documentation matches the functionality
of the installed system
• Defect reporting, triage and tracking

SERIAL 170002-RFP
• The Contractor shall ensure that resources are available for making
corrective adjustments to the system as required following the
discovery of defects
• If at any time during a Solution Test period County discovers a
failure to meet any standard, encompasses any malfunction, or
discovers any non-conformity to requirements or Contractor
published documentation, County will provide the Contractor with
written notice of failure. The contractor must correct this failure
within a mutually agreed to timeframe. If the failure is not
corrected, County has the option to declare non-perfoi mance and
seek remedy
• Upon completion of a Solution Test period, a gate review will be
conducted to determine whether the software delivery is
"accepted" along with any applicable terms and conditions of
acceptance
5.4 User Acceptance Testing
5.4.1 The user acceptance test process per phase (if applicable) for fmal delivery shall
include three stages: (1) the acceptance test period, (2) the reliability test period,
and (3) final acceptance. If at any time during the acceptance test process, the
system reveals any show stopper defects or ten (10) or more minor defects, the
process shall be terminated and the Contractor shall be responsible for resolving
outstanding issues. Once all of the issues have been addressed by the Contractor,
the Contractor may be required to repeat the acceptance test process from beginning
to end. Contractor will be responsible for all schedule and cost impacts related to
prolonged acceptance testing associated with these outstanding issues. Following
five (5) unsuccessful attempts to complete each of, acceptance testing, the reliability
test period, and final acceptance (as defined below), the Sheriff's Office reserves
the right to declare non-perfounance and seek remedy.
5.4.1.1 Acceptance Test Period:
Contractor Delivery, Installation, and Certification shall include the
following tasks:
• The Contractor shall certify delivery and installation of all agreed
upon system components, modules and functionality
• Complete Technical (System Administrator) Training
• Complete Functional (User) Training
• The Contractor shall verify that all County configured tables are
properly entered or converted
• The Contractor shall certify that all system components, modules,
functionality, County configured and user defined tables are fully
operational for County use
• Delivery of Updated Requirements Traceability Matrix
• Delivery of Release Notes
The acceptance test period shall consist of one hundred twenty (120)
calendar days and begins when County, along with the assistance of the
Contractor, first performs testing in accordance with the User
Acceptance Test Plan. County will evaluate all results to include
manual testing, automated testing, Interface testing, security testing and
data conversion and migration testing to ascertain whether the
performance standard has been met. At the conclusion of the
acceptance test period a gate review will be conducted to determine
whether the software delivery is acceptable to proceed to "go-live".

SERIAL 170002-RFP
5.4.1.2 Reliability Test Period: After successful completion of the "go-live" cutover
period, there shall be a thirty (30) day reliability test period during which the
newly installed system will be in production and its performance monitored.
During this period, the system must perform fully without degradation of any
kind in order for the reliability test to be satisfied. If any major defects or ten
(10) or more minor defects are discovered, the reliability test period shall be
terminated and the Contractor shall resolve any and all issues. Once all issues
have been addressed by the Contractor, the Contractor shall repeat the test
process from beginning to end.
5.4.1.3 Final Acceptance: In concurrence with the Reliability Test Period, it shall be
demonstrated through an acceptance process performance (stress) test that the
system performs as required in the Sheriff's Office's technical environment and
that the system meets or exceeds the Sheriffs Office's functional requirements.
The stress test shall include all LAN connected applications (i.e., JMS, Canteen,
Inmate Funds, etc.). The final Acceptance Test Plan (ATP) shall have use of
Sheriffs Office's approved data and include report generation. This test shall be
conducted jointly by Contractor and County per SOW Part 2 Performance &
Load Testing.
• The final acceptance test shall exercise all system functionality and
components successfully
• County shall test back-up features successfully
• County shall test recovery features successfully
• The failure of any specific portion of a test may require that the
entire test be rerun, not just the failed portion of the test
5.4.2 At the end of the successful completion of the User Acceptance Testing periods, a
gate review will be conducted to determine foimal acceptance, at which time the
Sheriffs Office shall issue the final acceptance certificate.
6.0 REQUIREMENTS
New .IMS Solution functional and non-functional requirements are identified below. Any changes to these
requirements shall be documented via the project's formal Change Control Process.
6.1 Functional Requirements
County's Functional Requirements for the New JMS Solution are identified in Master Services
Agreement, Appendix 1. These requirements are the result of County's original requirements
from the New JMS Solution Request for Proposal and subsequently updated by mutual agreement
between County and Contractor during the Gap Analysis activities.
These functional requirements serve as the foundation upon which the software will be configured
to County specifications and also used to test the County solution prior to acceptance and
implementation.
6.2 Non-Functional/Technical Requirements
County's Non-functional/Technical Requirements for the New JMS Solution are identified in
Master Services Agreement, Appendix 2. These requirements are the result of County's original
requirements from the New JMS Solution Request for Proposal and subsequently updated by
mutual agreement between County and Contractor during the Gap Analysis activities.
These non-functional requirements serve as the foundation for determining, sizing, and tuning
New JMS infrastructure components. Additionally, the non-functional requirements provide
details that shall guide the audit trail and security features of the new solution.

SERIAL 170002-RFP
6.3 Reporting Requirements
County's Reports for the New JMS Solution are identified in Master Services Agreement,
Appendix 3. These requirements are the result of County's original requirements from the New
IMS Solution Request for Proposal and subsequently updated by mutual agreement between
County and Contractor during the Gap Analysis activities.
6.4 Interface Inventory
County's Interfaces for the New JMS Solution are identified in Master Services Agreement,
Appendix 4. These interface requirements are the result of County's original requirements from
the New .IMS Solution Request for Proposal and subsequently updated by mutual agreement
between County and Contractor during the Gap Analysis activities.
7.0 QUALITY STANDARDS
The New JMS project will adhere to established quality standards. Quality will be monitored and
controlled utilizing a quality management strategy. The quality management strategy is made up of four
(4) parts:
7.1 Quality Planning — The Contractor will produce a Quality Management Plan deliverable that
defines the acceptable level of quality and describes how the project will ensure this level of
quality in its deliverables and work processes. County will review and approve the Quality
Management Plan deliverable signifying agreement to the measures that will be used to deteimine
County satisfaction that each deliverable is complete and acceptable and that project work
processes are being followed.
7.2 Quality Assurance — The purpose of quality assurance is to ensure that project processes are used
effectively to produce quality deliverables. It includes following and meeting project standards,
continuously improving project work, and correcting project defects. The Contractor will be
responsible for identifying all the project processes that will be monitored. For each process the
Contractor will document process quality standards/stakeholder expectations, Quality Assurance
activity (e.g. peer reviews, etc.), frequency, and who is responsible. Responsibilities for Quality
Assurance will reside both with the Contractor and County.
7.3 Quality Control — The purpose of quality control is to verify that project deliverables are of
acceptable quality and that County is satisfied. The Contractor will be responsible for identifying
the major deliverables subject to quality control reviews. For each deliverable, the Contractor will
document the quality standards for County satisfaction, Quality Control activity, frequency or
timing, and who is responsible. Responsibilities for Quality Control will reside both with the
Contractor and County. County reserves the right to approve each deliverable signifying
acceptance/satisfaction.
7.4 Verification and Validation (V&V) — Verification and validation are independent procedures that
are used together for checking that a product, service, or system meets requirements and
specifications and that it fulfills its intended purpose. V&V evaluations will be performed to
evaluate and provide assurance that the service, deliverables, and system meet the needs of County
and comply with requirements and specifications mandated. The Contractor will provide all
deliverables and documentation to County's V&V representative for review. Any deficiencies
identified during the review will be documented and supplied to the Contractor for correction.
Contractors will make any required modifications and resubmit the deliverable for County review
and approval. In addition, County's V&V representative will monitor all aspects of the project to
ensure Contractor obligations are being met.
8.0 COUNTY SOFTWARE LICENSE REQUIREMENTS
A summary of software license requirements by functional area or module is provided in the chart below.
Note that the estimated number of users includes the number of individual staff who work in a specified
functional area or location, and assumes 24 x 7 x 365 operations. Personnel who work in multiple

SERIAL 170002-RFP
functional areas or locations are included in the count for each function or location. The estimated number
of concurrent users is a best-guess for the maximum number of individual users who will access each
functional area or module at a single point in time. All estimates are projected to meet the anticipated
needs of County through the life of the Contract.
Estimated Estimated
1 : nctionality/Module Location / User # Users Concurrent Comments
Users ._
Pre-Booking MCSO Intake 150 50
Pre-Booking MCSO Deputies 700 100
Pre-Booking Outside Police Agencies 4,000 500
Intake Processimi, — Lith Ave & LBJ Intake 75 25
Incl. Page 2's & holds
Release Processing— 4 Ave & LBJ —Court 100 35
InCL Page 2's & holds Desk & Release Areas
Fingerprint Processing Records & AFIS Division 45 15
Average 100 Assumes —100
Inmate Kiosks Inmates in Jail Facilities 8,000/Day (TBD) kiosks available
in MCSO jails
Detention Operations
(e.g., logbook entries, Jail Facilities 1,000 250
housing queries,
visitation, etc.)
Inmate Property Jail Facilities
Tracking
Mobile Devicese.L.,, ., Jail Facilities 1,000 150 Now performed
headcount scanning) (TBD) manually
Mobile Devices (e.g.., for Court Security & Transp. 150 50 Now performed
inmate movements) (TBD) manually
Depends on the
Mobile / Barcode / Other Other Business Areas TBD TBD purpose; will be
Devices new technology
for Detention
Inmate Funds Queries Hearings & Grievances 30 10
Inmate Funds Queries Jail Facilities 800 30 Will decrease as
&/or Processing kiosks installed
Inmate Funds Queries Inmate Legal Services 5
&/or Processing
Inmate Funds Queries SIMS 10
&for Processing
Inmate Funds Queries,
Processing, &/or Financial Services 10 5
Accounting Tasks
Canteen System Canteen Operations 15 10
Inmate Movement Court Security & Transp. 150 50
Inmate Movement Medical Services 25 5
Inmate Movement Classification 53 15
Inmate Movement Jail Facilities 830 30
Scheduling Court Security L Transp. 150 50
Scheduling Medical Services 25 5
Scheduling Correctional I lealth 700 100
Scheduling SIMS 70 35
Scheduling Jail Facilities 1,200 200 Primarily view-
only with queries

SERIAL 170002-RFP
r4117rifillf ,-- VIM rill Ilt [.?.1. ,IT.Orlif:/ 1-1-.4 , 1.-T.,(- - .,t.f-OirLiiiii-(4ii - - (`JiliinirOi:,. . , _
‘i
Scheduling Inmate Classification 15
Scheduling Inmate Programs 75 10
Scheduling Hearings & Grievances 30 20
Court Case Processing Inmate Lc al Services 5 5 Primarily view-
only v, ith queries
Court Case Processing SIMS 70 25
Sentence Calculation SIMS 70 15
Sentence Calculation LBJ 75 25
Classification Processing Jail Intel — Gang Mgmt 10 Primarily only with view- queries
Classification Processing Inmate Classification 20
Proxy Scoring Inmate Classification 20
Proxy Scoring Inmate Programs 30
Administration of Inmate Programs 30 30 Day shift only
Inmate Programs
Ancillary Services Laundry 3 1 Primarily view-
only with queries
Ancillary Services Food Factory / Diets Primarily view-
only with queries
System Administration Technology Bureau 10
User Profiles & MCSO Business Units 10
Password Admin
Dashboard Reporting MCSO Commanders 300 70
System Queries All Detention Areas 1,500 300
Report Processing All Detention Areas 1,500 100
Document Management All Detention Users 1,500 100
Business Rules All Detention Users 1,500 10
Workflows All Detention Users 1,500 20
9.0 PLACE OF PERFORMANCE
The scope of work described in this contract, unless otherwise noted or agreed to by the Parties in writing,
shall be performed at County locations. County and Contractor agrees to utilize technology, such as
GoToMeeting and WebEx, along with conference calls to help control on-site Contractor costs related to
this project effort. Contractor staff must be on site for certain events such as, but not limited to: Project
Kickoff meeting; initial system installation and configuration; requirements validation; business process
review; major prototype sessions; all forms of technical system training; T3 training support;
supporting actual UAT tasks; and, Go Live events and follow-up support.
Additionally, the Contractor Project Manager will make trips on a mutually agreed to schedule to County to
check-up on Contractor and sub-contractor staff, to attend scheduled project meetings and to provide
updates on the progress of work being done at Contractor site.
Tasks that may be perfoimed at the Contractor's office include: all administrative tasks; foimal design
development; software development; unit testing; automated testing, via test tools; defect management;
daily PM activities.
Access to County networks shall be via agreed upon and approved methods and accessed only by
Contractor approved representatives (those that have passed background and fingerprint checks, and have

SERIAL 170002-RFP
passed the Terminal Operators Certification (TOG) test). County will provide a secure remote access
capability to Contractor. Contractor will always seek approval from County prior to accessing network.
During the course of the project, County shall provide a reasonable and adequate workspace environment
for up to fifteen (15) Contractor resources and such other related facilities as may be required by the
Contractor to efficiently carry out obligations enumerated herein.
10.0 COUNTY FURNISHED PROPERTY, MATERIAL, EQUIPMENT, OR INFORMATION
County workspace environment shall include desktop workspace, access to the County network and
network printers, and standard office supplies (paper, pens, etc.) for use by Contractor staff Local landline
phones may be provided on an as requested basis.
The Contractor shall provide its personnel with computers, phones, and all other equipment required to
complete the scope of work described in this contract at no cost to County or the County. For convenience,
and at its sole discretion, the Sheriffs Office may choose to provide Contractor personnel with access to
equipment such as phones, computers, etc., if such access is available.
As deemed necessary by County's Project Director, and in accordance with MCSO Security Guidelines,
Contractor's personnel may be issued a courtesy badge that will allow access to County buildings and/or
MCSO jail facilities. Courtesy badges are and shall remain the property of the Sheriffs Office and must be
promptly returned by persons who will no longer be assigned to the project, or at any other time upon the
request of MCSO.
11.0 EQUIPMENT
Contractor Recommended Specifications
The following hardware specifications are recommended to the County for the project.
PRODUCTION
Microsoft Dynamics CRM Server Infrastructure:
The following table lists the recommended hardware requirements for Microsoft Dynamics CRM Server,
the platfoun for Offender360. These requirements assume that additional components such as Microsoft
SQL Server, SharePoint, or Microsoft Exchange Server are not installed or running on the system and are
based on a 2000 concurrent user load. Supporting MCSO's user base will require the use of multiple
Microsoft Dynamics CRM servers. This deployment will leverage eight (8) Microsoft Dynamics CRM
Front End Servers and two (2) Microsoft Dynamics CRM Back End Servers.
Microsoft Dynamics CRM Front End Servers:
The Microsoft Dynamics CRM Front End Servers contain the server roles for running client applications
and applications developed with the Microsoft Dynamics CRM SDK. Those rules include the Discovery
Web Service, Organization Web Service, Web Application Server, and Help Server. The Microsoft
Dynamics CRM Front End Servers will be load balanced to ensure satisfactory perfollnance. Eight (8) front
end servers are recommended to support the proposed environment. The following table outlines the specs
for the Front End Server:
Component I Recommended
Processor Quad-core x64 architecture 2 GHz CPU or higher such as
AMID Opteron or Intel Xeon systems
Memory 8 GB RAM or more
Hard disk 40 GB or more of available hard disk space
Microsoft Dynamics CR_M Back End Servers:
The Microsoft Dynamics CRM Back End Servers contain the server roles that handle processing
asynchronous events, such as workflows and custom plug-ins. Those rules include the Asynchronous
Service and Sandbox Processing Service. Two (2) back end servers are recommended to support the
proposed environment. The following table outlines the specs for the Back End Server:

SERIAL 170002-RFP
Component Recommended
Processor Quad-core x64 architecture 2 GHz CPU or higher such as
AMID Opteron or Intel Xeon systems
8 GB RAM or more
40 GB or more of available hard disk space
Microsoft Dynamics CRM Email Router Server:
A server will be dedicated to housing the Microsoft Dynamics CRM Email Router. The E-mail Router is an
interface component that integrates your e-mail system (e.g. Exchange) with Microsoft Dynamics CRM,
and routes qualified e-mail messages to and from your Microsoft Dynamics CRM organization. One (1)
Email Router Server is recommended to support the proposed environment. The following table outlines
the specs for the Email Router Server:
Recommended
Quad-core x64 architecture 2 GHz CPU or higher such as
AMID Opteron or Intel Xeon systems
8 GB RAM or more
40 GB or more of available hard disk space
Database Infrastructure
SQL Server 2012 is being requested to deploy Microsoft Dynamics CRM 2016 and will run on Windows
2012. SQL Server will be a two-node clustered setup. The following specs are outlined for SQL Server:
Componen Recommended
Processor Eight to Ten-core x64 architecture 2 GHz CPU or higher
such as AMID Opteron or Intel Xeon systems
Memory 64 GB RAM
I Hard disk (Does not include backup space) .2TB
Determined by the current size of the DBs x 5 years of
expected growth x 20%
Initial Size — 520GB
5 years of expected growth — 480GB (8GB/month)
SSRS Server:
SQL Server Reporting Services provides a full range of ready-to-use tools and services to help you create,
deploy, and manage reports for your organization, as well as programming features that enable you to
extend and customize your reporting functionality. Microsoft Dynamics CRM integrates with SSRS
through the use of the Microsoft Dynamics CRM Reporting Extensions. Microsoft Dynamics CRM
Reporting Extensions are data processing extensions that are installed on the Microsoft SQL Server
Reporting Services server. The Microsoft Dynamics CRM Reporting Extensions accept the authentication
information from Microsoft Dynamics CRM and passes it to the Microsoft SQL Server Reporting Services
server. We can have a load balanced environment with 2 SSRS servers for redundancy. The following table
outlines the specs for the SSRS Server:
Recommended
I Quad-core x64 architecture 2 GHz CPU or higher such as
I A_MD Opteron or Intel Xeon systems
I Memory -7 8 GB RAM or more
Hard disk 80 GB or more of available hard disk space
Redundancy 1 server can be added

SERIAL 170002-RFP
Scribe Server
The Scribe server will manage and process integrations between Offender360 and all external applications.
One Scribe Server is recommended to support the proposed environment. The following table outlines the
specs for the Scribe Server:
Component Recommended
Processor Eight core x64 architecture 2 GHz CPU or higher such as
AMD Opteron or Intel Xeon systems
Memory 32 GB RAM or more
Hard disk 60 GB or more of available hard disk space
; Redundancy 1 server can be added
NON-PRODUCTION (DEV/TEST/Training)
Microsoft Dynamics CRM Server
: Recommended
Quad-core x64 architecture 2 GHz CPU or higher such as
AMD Opteron or Intel Xeon systems
16 GB RAM or more
40 GB or more of available hard disk space
SQL Server
Component Recommended
Processor Eight to Ten-core x64 architecture 2 GHz CPU or higher
such as AMID Opteron or Intel Xeon systems
Memory 32 GB RAM
Hard disk (Does not include backup space) 1.2TB
Determined by the current size of the DBs x 5 years of
expected growth x 20%
Initial Size — 520GB
5 years of expected growth — 480GB (8GB/month)
Microsoft Dynamics CRM Server Software Licenses
I License Quantity]
Dynamics365 Team Member GOV MVL User 3,183
Dynamics365 Plan 1 GOV MVL User 50
Dynamics365 For Customer Service GOV MVL Device 25
Microsoft SharePoint N/A
Microsoft SQL Server N/A
Note — MCSO will obtain these software licenses associated with this project through a separate agreement.

SERIAL 170002-RFP
PART TWO: STATEMENT OF WORK
1. Project Governance
1.1. MCSO JMS Governance Objectives
The standard goals of program governance are to:
• Define and implement a structure within which to execute prop -am management and administration;
and
• Provide active direction, periodically reviewing interim results, and identifying and executing
adjustments to ensure achievement of the planned outcome.
The MCSO New JMS Initiative is a large program. As large programs develop, there are components and work
results that need to become foundational to support the program's continued progress. This foundation serves as a
framework to guide further work, provides a basis for understanding the processes to make decisions, and supports
participants to identify parties responsible for specific work areas. The objectives of the governance process outlined
are as follows:
A. Monitoring and ensuring consistent quality service and timely delivery of Contractor deliverables and
services and County deliverables and services that are dependencies thereof;
B. Proactively identifying, assessing and mitigating risks (both operational and reputational) to County
stakeholders and ensuring compliance to agreed policy and procedures;
C. Interpreting and ensuring compliance by the Parties to the Agreement and recommendation of potential
Changes to the Agreement or Service Levels;
D. Monitoring and ensuring consistent strategic alignment between (i) stakeholder strategies and service
requirements and (ii) Contractor performance;
E. Overseeing the development, implementation, and management of cross functional service processes;
F. Ensuring appropriate levels of engagement between County stakeholders and Contractor at the right
point in time in the governance processes;
G. Providing central oversight to financial management and reporting and proactively identifying areas of
improvement; and
H. Providing a continuous improvement framework that strengthens operational performance, project
delivery and fosters the development and implementation of technologies that are in line with
technology standards and industry best practice.

SERIAL 170002-RFP
1.2. Governance Team Structure
COUNTY Executive Sponsor(s)
Steering Committee
Contractor COUNTY Project
Executive Sponsor(s) Director
Project Administrator
Operational
Contractor Senior COUNTY Senior
Steering
Project Manager Project Manager (s)
Committee
COUNTY: & Contractor Project Team
1.3. Project Governance Roles and Responsibilities
The following table identifies the anticipated roles and responsibilities of the key members of the project governance
groups:
Project Governance Role Responsibilities
Contractor • Provides overall quality assurance and management oversight of the
Executive Sponsor(s) project
Project Administrator • Provides executive sponsor buy-in and ongoing communications with
executive sponsors
• Participates on the Project Steering Committee
• Provides final deliverable approvals
• Review Project Governance and Delivery Health Check results and
drive action plans as needed
County Project Director • Overall ownership of the contract
• Stewardship of the relationship
• Strategy planning/direction setting
• Effective communication of strategy and benefits to business process
areas
• Ensuring that the solution and services delivered under the contact are
consistent with MCSO's program objectives
• Identifying and escalating potentially significant, sensitive or political
issues to Executive Steering Committee
• Review of project status updates
• Providing monthly project updates to the Executive Steering
Committee

SERIAL 170002-RFP
Contractor Senior Project • Facilitates the day-to-day coordination required to deliver the project
Manager in a manner consistent with the project vision, scope and
organizational goals
• Coordinates activities of project staff, including assigning tasks,
creating status reports and managing to the project plan
• Responsible for weekly status reporting including accomplishments,
next steps, and actual to budget updates
• Works closely with the County PM(s) to ensure communication is
continuous
• Conduct Project Governance and Delivery Health Check at key points
throughout the project
County Senior Project • Facilitates the day-to-day coordination required to deliver the project
Manager(s) in a manner consistent with the project vision, scope and
organizational goals
• Coordinates activities of MCSO project staff, including assigning
tasks, creating status reports and managing to the project plan
• Review/provide input on project status reports
• Works closely with Contractor PM to ensure communication is
continuous
• Participate in Project Governance and Delivery Health Checks
• Resolves cross-functional issues at the project level
• Aligns MCSO tasks to the overall project plan/schedule
• Works with the Contractor Project Manager to coordinate and execute
the implementation schedule and associated plans
• Protects project scope, timeline and budget
• Manages issues through resolution and escalates to Project Director
when necessary
• Participates in regular Contractor conference calls sessions as required
• Manages Scope Change Orders and works with Contractor and
Operational Steering Committee to recommend acceptance/rejection
• Reports to MCSO Project Director
• Facilitates review, feedback and acceptance of Contractor deliverables
Operational Steering Committee • Interprets the strategic direction provided by the Executive Sponsors
• Provides authority on resolution of major project issues / escalated
decisions
• Develops a coherent and supportive relationship between the overall
business strategy and the project
• Recommends significant changes to project scope, schedule and
budget
• Endorses new change requests and associated plans, schedules and
resourcing requirements
• Reviews project perfoimance
0 Governs project management and implementation of project SHIELD;
• Recommends when scrutiny of projects and project management
systems is required, and implements such scrutiny accordingly
• Ensures enterprise-wide planning for business and technology
decisions
* Assists in shaping communications and dissemination strategies
• Participates actively and visibly throughout the project

SERIAL 170002-RFP
Executive Steering Committee • Approves significant changes to project scope, schedule and budget /
endorsing new change requests projects and associated plans,
schedules and resourcing requirements
• Drives decisions on issues that cannot be resolved at the Operations
Steering Committee level;
• Provides the strategic direction to the project
Project Team • Drives decisions with respect to operations and delivery of the project
as specified in the Statement of Work
• Escalates issues to the Project Managers and Operational Steering
Committee when necessary
• Executes the project activities and development of the associated
deliverables in accordance with the strategy and plans;
• Provides timely project status reports and dashboards to the Project
Managers and Project Directors
• Participates in organizational change management;
• Participates in the communications and dissemination strategies
• Provides input to the overall program plan and roadmap for project
SHIELD
1.4. Change Control Process
All changes to scope are to be documented, reviewed, and approved/rejected via the formal Change Control
Process. Change Control Process steps are identified below:
• The party requesting the change will complete a Change Request Form. When completing the form,
include a complete description of the requested change, options for meeting the new request,
justification for the requested change, impact to the project (time, dollars, etc.), and the
recommendation of the joint (Contractor/County)project team.
• Submit the Change Request Faun to the County Project Manager for logging and distribution to the
appropriate reviewers and approvers.
• Change Requests will be reviewed by both Asshole and Contractor management teams and either
approved or rejected.
• County Project Manager will update the Change Request Log noting the approval or rejection status.
• The Change Request will be returned to the Contractor's Project Manager. The Change Request will be
reviewed and accepted by the Project Director then forwarded to Office of Procurement Services for
processing.
1.5. Issue Resolution and Escalation Process
1.5.1. The County and Contractor Project Managers are responsible for overseeing and managing project
and system issues. The Risks and Issues Management Plan project deliverable will describe the Issue
Resolution and Escalation Process to be utilized for the SHIELD Project. This process will be
mutually agreed to by the County and the Contractor, include a multi-step progression, and identify
the number of days any issue can remain unresolved at each step before it is escalated to the next
level for review and resolution. The County, Contractor and SHIELD project team will always strive
to make decisions and address issues at the lowest step possible. The Issues Resolution and
Escalation process will be designed to enable timely decision making to minimize impacts to the
project.
1.5.2. No Damages for Delay No claim for damages or any claim other than for an extension of time shall
be made or asserted against County by reason of any delays. Contractor shall not be entitled to an
increase in the Contract Price or payment or compensation of any kind from County for direct,
indirect, consequential, impact or other costs, expenses or damages, including, but not limited to,
costs of acceleration or inefficiency, arising because of delay, disruption, interference or hindrance
from any cause whatsoever, whether such delay, disruption, interference or hindrance be reasonable
or unreasonable, foreseeable or unforeseeable, or avoidable or unavoidable; provided, however, that
this provision shall not preclude recovery of damages by Contractor for hindrance or delays due
solely to fraud, bad faith or active interference on the part of County or its agents. Otherwise,

SERIAL 170002-RFP
Contractor shall be entitled only to extensions of the Contract Time as the sole and exclusive remedy
for such resulting delay, in accordance with and to the extent specifically provided above.
1.5.3. Excusable Delay Excusable Delay: Delay which extends the completion of the work which is caused
by circumstances beyond the control of Contractor or its subcontractors, materials persons, suppliers,
or vendors is Excusable Delay. Contractor shall document its claim for any time extensions and
related costs and submit a formal Change Order Request to County documenting the nature of the
delay and its direct and actual impact on the date of Final Acceptance of the Software.
2. Staffing
2.1. Key Personnel
The Contractor has committed resources identified below to fill key positions required by County. These resources
have been reviewed and approved by County for participation in the project. These resources are not to be replaced
on the project unless requested and/or approved by County. Should the Contractor have necessity to replace a
resource, a well-qualified resource will be presented to County for their consideration. County will require
submission of resumes and references, and may request interviews with proposed replacement resources. All
replacement candidates will be subject to background checks. County shall have sole responsibility for approving
any replacement resource prior to their participation on the project.
•Key Position/Project Contractor Team Key Areas of Involvement
Position Members
Project Administrator • Rick Thompson • Provides overall quality assurance and management
oversight of the project
(Project Director/QA) • Provides executive sponsor buy-in and ongoing
communications with executive sponsors
• Participates on the Project Steering Committee
• Provides final deliverable approvals
Senior Project Manager • Patrick DiLullo • Facilitates the day-to-day coordination required to
• Michael Stephens deliver the project in a manner consistent with the
project vision, scope and organizational goals
• Coordinates activities of project staff, including
assigning tasks, creating status reports and managing to
the project plan
• Responsible for weekly status reporting including
accomplishments, next steps, and actual to budget
updates
• Works closely with the County PM to ensure
communication is continuous
Senior Business Analyst & • Amy Leffler • Serves as the functional team lead for issues and
Training Manager • Bob Mancuso escalation purpose
Configuration/Release * Facilitates functional design sessions including
Manager dashboards and reports
• Documents system design
(Functional Software • Dry run/simulated go live planning
Lead's) • Responsible for the configuration of the Microsoft
Dynamics CRM application
• Leverage knowledge of best practices through the
application design and configuration process
• Conducts system testing
• Provides data migration assistance
• Provides reporting assistance
• Develops training materials
• Provide onsite super user and end-user training
Enterprise Architect • Jeff Davis • Conduct Architecture Assessment
• Leverage knowledge of product architecture through
(Solution Architect) the application design/development process
• Working with Functional Lead develops the prototype

SERIAL 170002-RFP
Key Position/Project Contractor Team Key Areas of Involvement
Position Members
and conducts the reviews
• Provides support during testing
Testing Manager • David Pritchett • Responsible for data migration design, development,
Interface & Conversion • Erin Shamblen and testing
Manager • Responsible for data integration design, development,
and testing
(Technical Consultants) • Serves as a technical team lead for issues and
escalation purpose
• Provide technical training for client IT team
• Recommend infrastructure requirements for each
environment
• Install software including Microsoft Dynamics CRIVI
and Scribe
Senior Development • Christine Pasinsky • Responsible for the development within the SDK
Manager • Randy Smith framework utilizing .NET
Database Architect • Facilitates user testing and acceptance
• Conducts knowledge transfer to IT team members
(Technical Developers) • Create report specifications
• Develop and test reports
• Conduct dashboard design sessions
• Offer best practices based and common dashboards
based on functional role
• Configure Dynamics CRM dashboards
• .NET portal development
3. Timeline
The Gantt chart below presents the major project phases, major project activities and major project milestones. This
visual presentation is supported by a detail project schedule/work plan identifying the tasks, durations and
assignments required to successfully complete the project.
Phase 1 Timeline
471.814,
MMIIIMEMINEMI•MINIINIMMENUMME• M•• 111M11••11 111•1•111M• NW= •
DEC DeDen na.rom D
11•1111111111•••• •
111111I
isommilinuommEn I 1 11111111:: •••••••••••• MI AIM
:Data AD, ILenuiat atton Du:WS D. ADD -rest Ma, MINIM 1111.••111111111111••1111•1111•1•1••111•1•1111111 •••••11111•• • MEM ••••11111•111111•1••••••••111111111 MEMMENIIIMMEMENEMENE•
:Dava :SDK Cosiumizeicns int•Irn6on 9,, E. Test • 1•111•11MNIM•111••11111•=1111• 1111•1•11•111•1•••••1111•••11•111
:DV :Dxuctts eu. &les, TeD MEMMEMENEMENIMIMISME
,Dash.ard,B,D1ii DD:n. telting • 111•1•1111•1•1••••••••1 1•1111•INIME•EMEMEM111•1111•MME•1111•111 •1•••11111M MEM • MEMMEMENEMINIEN 11111=1•111•1•11•1111•1•••
;System ;End In E. 7.41DE MIEMIMINI•1111•1111111111•••111•1
kDry•oi, DwagemeDt P.ject M11.,ement e

SERIAL 170002-REP
Phase 2 Timeline
Pro!, 1 06 Ev; ,,,/ 4 S Ii / 8 1 ID 11 1) ,, 14 1-1 1I 16 H- (S D 20 21 )2 , — 4 , , T2iT .- 2 7 21 0 11 4 lv
_
iitial
Des, -
Provision DIM Dev & Test Environments
'Requilements Discovery
Requirements, Use Case &Traceability
: Prototyping
:Functional Design Document
Reporting Design Document
'Dashboard Design Document
Data Integration Design
Data Migration Design _ _
tr1:4771KOMFT:=-11.1— 6 ______,
:rystem Configuration
:Workflow/Process Automation
.Email Templates & Mail Merge Letters
Data Migration Build & Test
Data Integration Build & Test
1 50K Customizations
,ISV Build & Test (Portaq
Reports Build &Test
Dashboards Build & Test
'Business Process Testing
'UAT System Testing (End to End) Testing
Deploy Phase ___. ,
Provision DIM Production Environmen
Technical Training
'Functional Training ••••••
Data Migration Deploy
Data Integration Deploy
Go-Live Activity & Support
C1/ A
.Ongoing Project Management
.Ongoing Engagement Management
NOTE: Solid colored boxes represent Phase 2A activities. Horizontal lined boxes represent Phase 2B activities.
4. Workplan
This section includes a written description of the overall project phases, scope and activities presented in the
timeline section. Milestones and deliverables are described in Section 5.
4.1. Define Phase. During this Phase, Contractor and County will define how the business requirements will be
implemented.
4.1.1. Project Kickoff — A meeting is conducted with the project stakeholders to communicate the purpose,
scope, and timing of the project. Additionally, roles and responsibilities are reviewed to establish a
mutual understanding of expectations. Contractor will provide a kickoff presentation and co-
facilitate the kickoff meeting with the County stakeholders. County attendees in the kickoff meeting
will include the project sponsors, County project director and project managers, key business and IT
owners, and the remainder of the core project team.
4.1.2. Project Planning — A planning meeting is conducted to outline the scope, deliverables, and target
milestones dates for the project. Expectations, time requirements and the project schedule are
reviewed. The high level roll-out strategy for the implementation is discussed and the project
logistics are determined (project room, status meeting times, documentation standards, etc.).
Contractor will perform key tasks onsite at the County project office, such as design sessions, testing,
training, and deployment. In order to minimize travel expenses, Contractor will also perform work
remotely when appropriate. For work onsite at the County project office, a work area/project room
will be dedicated for the duration of the project with workstations and ports to allow access to the
application and Internet. Remote secured access is required to allow Contractor team members to
perform tasks from Contractor's office.
4.1.3. Business Scenarios & Reference Materials — County will provide reference materials such as
existing process flows, sample reports, screen shots, spreadsheets, and requirements lists that will

SERIAL 170002-RFP
assist Contractor in gaining an initial understanding of County business and to aid in facilitating the
design sessions. Contractor will conduct the following requirements validation and discovery related
sessions in coordination with the County staff:
• Functional/Report Discovery — Ten (10) weeks of Contractor led sessions
4.2. Design Phase. During this Phase, Contractor and the County will define how the business requirements
will be implemented.
4.2.1 Systems Architecture Review - One of the key elements to a successful implementation is that
infrastructure and disaster recovery is thoroughly planned to meet perforniance needs, system
availability, and provide scalability for future growth. Contractor will provide County with hardware
and configuration recommendations prior to the start of the project. Contractor will conduct a review
of County's infrastructure and disaster recovery plan prior to installation of software to confirm that
requirements meet Microsoft standards for the software solution being implemented. Results of this
task are documented in the Enterprise Architecture Design document. Planning should also include
dry run/simulated go live activities and what environment will support those activities. Contractor
will provide County with recommendations on replicating SHIELD database that all SSRS reports
will be developed against. Contractor will provide advisory services to assist with this effort.
4.2.2. Install Application on Non-Production Environments - The software is installed on the server and
on the development and test/training environments are created.
• On Premise Environment. The County will host the solution on premise and therefore
will be required to implement hardware and software associated with an on premise
deployment. The County must have internet access and browser compatibility to access
the Microsoft Dynamics CRM Version 2016 based technology solution. A minimum of
three environments must be available to Contractor during the project: Two (2) Non-
Production (Development and Test) environments and one (1) Production environment.
Contractor will require the County to grant access to server environments and software
applications throughout the project.
• Internet Facing Deployment (IFD). IFD provides a secure method of access for
Microsoft Dynamics CRM from outside the company's local area network (LAN)
without the use of a VPN. If LED is needed, the County will be responsible for providing
a valid SSL certificate, external and internal DNS configuration, and DMZ/Firewall
configurations if necessary. Contractor will provide advisory services to assist with this
effort.
Software Install. Contractor will perform the install of Microsoft Dynamics CRM
Version 2016, Offender360, North52 Business Process Automation, Epilogue, and Scribe
Insight in a total of up to three (3) environments.
4.2.3. Project Orientation and Training — Contractor will provide an orientation to the County project
team on the project approach and methodology. Contractor will also deliver a series of training
sessions to the County core project team, Functional and technical training will be provided by
Contractor to selected SHIELD support staff and County implementation team at various points in
the project as specified in the implementation project plan to enable them to more effectively
participate in design sessions, requirements and prototype sessions, and help lead the solution testing
effort. This project team will become 'super users' of the system, and assist with the overall
implementation of the application and support resources for external users. . Contractor has included
time for three (3) weeks of core team training.
4.2.4. Develop Use Cases — Formal use cases will be documented based upon the business process
scenarios provided by the County. The use cases will be used to facilitate the design prototype, used
as the basis for test cases during the Test Phase, and be used as the basis for End-User Training
scenarios. The use cases will be cross-referenced to the functional requirements and test cases to
provide 'traceability' of the solution. Contractor will work with the County to develop the first
several use cases and will support the County as needed to develop the remaining use cases.
Contractor will be responsible for traceability and cross-referencing use cases to all requirements.

SERIAL 170002-RFP
4.2.5. Functional System Design & Prototype Development— Contractor will lead and assume
responsibility for mapping the business process functionality with Offender360 functions, including
screen configuration, security requirements, reports, and workflows. Contractor will develop
prototypes based upon the approved requirements and County feedback. Contractor will conduct
prototype reviews, to offer business users the ability to visualize the system's functionality, provide
final feedback and freeze the design. Contractor has included time for ten (10) weeks of prototype
reviews. Contractor expects that County will submit a comprehensive list of changes, questions,
bugs, etc. to Contractor as part of its prototype review. County will provide one submission after
each review and Contractor will address the County list, making the necessary changes for County to
review and approve. Contractor and County will work together in a reasonably iterative approach
until these submitted changes are completed and approved.
Upon completion of the design prototype(s), Contractor will document the design in a Functional
Design Document. This design document will contain any customizations to the baseline solution
(Contractor Offender360 Solution Bundle and 3 1-d party software) that are required to support the
County's use cases and documented requirements.
4.2.6. Define Report Specifications — The report requirements and sample legacy reports are reviewed and
initial report specifications are developed. The reports are mapped back to the solution design and
the design is updated so that the necessary data is captured in the system. A Report Specification
Document will be documented for each report and will require sign-off by the County. Any future
changes to the scope of a report after sign-off of the Report Specification will require a change order.
4.2.7. Functional Design Sign-off -- The Functional Design Document will be reviewed by the County and
the County will be required to sign off on the design, indicating approval. Once the design of the
solution is approved, design will be "frozen". Any functionality not specified in the scope of the
Functional Design document after the design is frozen will be considered out-of-scope and either be
incorporated into this phase of the project via a Change order or deferred for inclusion in future
phases.
4.2.8. Confirm Build Effort/Plan— Once the design is complete and signoff is obtained, the build effort is
confirmed and finalized. The Project Work plan is updated as needed to reflect milestone dates and
timing. If updates to the build require a change in project timeline or budget, a change order will be
provided.
4.2.9. Enhanced Court Scheduling and Case Management Design. Contractor has included time to
perfomi the following tasks to define and design additional functionality in this area:
- Up to four (4) requirements gathering sessions/requirements analysis
Development of functional and technical requirements
Up to two (2) design sessions and up to two (2) prototype sessions
Development of functional, interface and report design documentation
4.3. Build & Test Phase. During this Phase, the system is configured and prepared for deployment.
4.3.1. System Configuration - Contractor will lead and assume responsibility for the design, build, test and
implementation of Offender360 software configurations/customizations. When reasonably necessary,
Contractor will recommend alternatives to existing processes to more easily adapt to the application
platform. During this step, system parameters are defmed and created, and Offender360 screens are
configured using the Offender360Customization tool and/or application development tools.
Contractor has included time to configure the Offender360 core application to meet the needs of the
County. This is inclusive of the following:
• Mail Merge and Email Templates. Leveraging Offender360's native integration to Microsoft
Word and Exchange, Contractor has included time to create up to five (5) email and five (5)
Word mail merge templates if needed. Word mail merge and email templates are managed using
the out-of-the-box system configuration tool in Offender360. Additionally, Contractor has
included time in the Administrative & Technical Training assumption to teach the County how
to implement Mail Merge and Email Templates.

SERIAL 170002-RFP
• Security Roles & Teams. Contractor has included time to configure up to ten (10) security
roles. Security Roles are managed using the out-of-the-box system configuration tool in
Offender360. Additionally, Contractor will train the County to configure additional roles as
needed, as referenced in the Administrative & Technical Training Assumption.
• Field Level Security. Contractor has included time to configure up to ten (10) field level
security roles. Field level security roles are managed using the out-of-the-box system
configuration tool in Offender360. Additionally, Contractor will train the County to configure
field level security within the system, as referenced in the Administrative & Technical Training
assumption.
• Data Entry Forms and Views. Contractor has included time to configure the data entry forms on
each entity used within Offender360. Configuration of the forms and views includes
adding/removing fields, modifying graphical user interface layouts, configuring navigation and
building form/field business rules. Configuration of data entry forms and views are managed
using the out-of-the-box system configuration tool in Offender360. Additionally, Contractor
will train the County to configure additional forms within the system, as needed, as referenced
in the Administrative & Technical Training assumption.
• Auditing. Contractor has included time to configure up to five (5) entities for auditing. Auditing
settings are managed using the out-of-the-box system configuration tool in Offender360.
Additionally, Contractor will train the County to configure audit settings for the appropriate
entities and fields within the system, as referenced in the Administrative & Technical Training
assumption.
• Duplicate Detection. Contractor has included time to configure up to five (5) duplicate
detection rules. Duplication detection rules are managed using the out-of-the-box system
configuration tool in Offender360. Additionally, Contractor will train the County to configure
duplicate detection rules and jobs within the system, as referenced in the Administrative &
Technical Training assumption.
• Workflow. Contractor has included time to create workflows to address MCSO's business
processes. Workflow rules are managed using the out-of-the-box system configuration tool in
Offender360. Additionally, Contractor will train the County to configure workflow rules within
the system, as referenced in the Administrative & Technical Training assumption.
• North52 Formula Manager. Contractor has included time to configure business automation rules
using North52 Formula Manager as part of the solution to satisfy requirements specified in
Exhibit B, sub a and b. This is based on the average number of business automation rules
created for a typical Offender360 implementation. North52 business rules are managed using
the North52 Business Rule Manager which is embedded into the application interface of
Dynamics CRM and Offender360.
• Adxstudio Public Portal. Contractor has included time to install, configure and develop a public
facing portal to support the requirements.
4.3.2. SDK Customizations. - The Dynamics CRM platform and Software Development Kit (SDK) is the
architecture of Offender360 that allows for rapid and robust development. Using the Microsoft
Dynamics CRM SDK allows you to extend functionality and integrate with the Dynamics CRM
platform. Microsoft includes out of box product configuration for creation of entities, forms, and
fields including built in security management. Further customizations, integrations and interfaces can
be built using Microsoft .NET and web service technologies. Contractor has identified the following
requirements that may need to be developed using SDK methods:
• Fingerprint Scanning
• Barcode Scanning
4.3.3. Electronic Signature — Contractor has included time to install, configure and develop up to eight (8)
electronic signature templates.

SERIAL 170002-RFP
4.3.4. Develop Reports — Of the reports identified in Appendix, Contractor estimates that approximately
150 of these will be custom SQL Service Reporting Services reports, whereas the remaining items
will be custom views and filters built within the solution. Contractor has included time to build up to
one hundred fifty (150) SSRS reports and two hundred eighty (280) views. The County will have
responsibility for developing additional reports as needed. Contractor will train the County on SSRS
report development in Dynamics environment as part of the Administrative and Technical Training.
If additional requirements are identified not included in the scope of work described herein,
Contractor will provide an updated cost via a Change Order or provide support to County staff as
they perform the additional tasks.
4.3.5. Develop Dashboards - Contractor has included time to develop up to twenty (20) unique dashboards
for the County utilizing standard Offender360 dashboard configuration options. Each dashboard will
include a maximum of 6 KPI frames. Dashboards are managed using the out-of-the-box system
configuration tool in Dynamics CRM and Offender360. The County will have responsibility for
developing additional dashboards as needed. Contractor will train the County on dashboard
configuration as part of the Administrative and Technical Training. If needed, Contractor will
develop additional dashboards upon acceptance of a Change Order that defmes the new
requirements.
4.3.6. Data Conversion and Interfaces — The County will be accountable for the design, development and
delivery of the Data Conversion and Interface components of the SHIELD project. In order to
achieve this, the County will have the responsibility to coordinate and direct the Contractor activities
and dependencies relative to the data conversion and interface components of the project, and
manage issues and risks that arise. The County will assign a Project Manager to plan and guide all
data conversion and interface related activities. The County's Project Manager will provide the
following project support:
• Data conversion and interface schedule management - Create and manage schedules for
data conversion and interface activities, ensuring that the data conversion and interface
teams adhere to larger project milestones.
• Status reporting - Provide status reports to advise of data conversion and interface
progress.
• Plan documents - Produce data conversion and interface related planning documents as
required.
• Project Meetings - Attend and / or lead administrative project meetings, for example
status meetings, planning meetings, etc. This includes documenting action items and
decisions.
The Contractor will be responsible to provide:
• Data Conversion Consulting Services — including tools and architecture related to the
load process, SHIELD Staging data model (for data mapping activities), and JMS
configurations related to data value mapping activities.
• Data Loading and Validation — including the design, build and test/verification of the data
load process from the SHIELD Staging database to the SHIELD database. Testing to
include both quantitative and qualitative testing from the SHIELD Staging database to the
SHIELD database.
• Interface Consulting Services — include training, architecture support, provide SHIELD
data model, and JMS configuration related to data values transferred from SHIELD to
external systems
• Installation Services — including supporting the County in installation of the Contractor
tools required for data conversion and interfaces.
• Scribe — WebSphere MQ Communication Proof of Concept (POC) — Lead a combined
Contractor/County POC team that determines the optimal communication mechanism(s)
between Scribe and WebSphere MQ and work together to develop a proof of concept to
validate the preferred approach. Develop a POC document that defines the preferred
communication mechanism(s) for integrations through ICJIS.

SERIAL 170002-RF'P
The following RACI chart represented the responsibilities of County and the Contractor related to
Data Conversion:
Major I a 'ounty CON 1 R /1(_ I OR
Single Point 01 ConLaLL kSi=l)(,) lot S HILLD Data A
Conversion
Overall Data Conversion Schedule/Plan
Determine Architecture Requirements
Development of Data Conversion Planning Documents
Assess Current Environment
Design Data Conversion Environments
Design Source Data Procedures
Data Mapping
Create Data Conversion Environments
Develop Data Extract Scripts
Anonymize Data
Develop Data Transform / Load Scripts
Extract Data into MCSO Staging
Transform Data to SHIELD Staging
Investigate and Cleanse Source Data
Load Data into SHIELD A
Develop Data Conversion Test Plan R/A C/I
Data Extract Testing R/A
Data Transformation Testing R/A C/I
Data Load Testing A R*
User Acceptance Testing R/A C/I
I Dry Run Testing R/A C/I
Perform Production ETL C/I
Validate Production Conversion
Post Conversion Closeout R/A C/I
I Quality Assurance Review of Deliverables R/A WC/I
Approval of Deliverables R/A
Contractor responsible for data load testing from SHIELD staging database to SHIELD
database only.
The following diagram graphically represents the responsibility of the County and the Contractor
related to Data Conversion:

SERIAL 170002-RFP
COMSIlete Niter Process: - Adak, ,anslate and
• Skeleton data, Of inmate . transform SHIELD f data obn.t to
data
allen elliS aplIIiOdllIe- teallloS.
The following RACI chart represented the responsibilities of County and the Contractor related to
Interfaces:
Couni I.' C()N . FRALIUK
Single Point of Contact (SPOC) for SHIELD A
Interfaces
Overall Interface Schedule/Plan R/A C/I
Development of Interface Planning Documents R/A C/I
Scribe — WebSphere MQ Communication POC R/C R/A
Determine ESB/Architectural Implementation R/A R/C/I
Determine Interface Requirements R/A
Develop Interface Designs R/A C/I
Build Interface RJA C/I
Develop Test Plan(s) R/A C/I
Create Test Data - System R/A C/I
Create Test Data - Integration R/A C/I
Create Test Data - UAT R/A C/I
Testing - System R/A C/I
Testing - Integration RJA C/I
Testing - UAT R/A C/I
Production Deployment Planning/Schedule R/A R/C/I
Deploy to Production R/A C/I
Decommission old interfaces RIA
Post Interface Closeout R/A R/I
Quality Assurance Review of Deliverables R/A R/C/I

SERIAL 170002-RFP
Approval of Deliverables R/A
The Contractor shall provide technical training on their technical tools as specified in
Administrative and Technical Training Section to enable the County to build data conversion and
interfaces to meet their commitments.
4.3.7. Quality Management — County will have responsibility for the quality of the data conversion and
interface components of the SHIELD project. The County will:
• Ensure consistency of deliverables across all stages of the data conversion and interface
components of the project;
• Ensure all deliverables meet the quality criteria for acceptance;
• Verify that data conversion and interface deliverables for the project are complete for
approval;
• Ensure that critical defects, risks and issues are found earlier in the project lifecycle;
• Increase overall quality of project deliverables; and
• Ensure the data conversion and interfaces teams are adhering to defined standards and
controls
4.3.7.1. The Contractor will work with the County to assist in producing quality data conversion and
interface related deliverables and other work products based upon the RACI charts provided.
4.3.7.2. Software Tools. Included with Offender360 is the Scribe software application that will be
implemented in conjunction with Microsoft Dynamics for integration and data migration
purposes. This product has been factored into Contractor scope of work, timeline and costs.
4.3.7.3. Data Cleansing and Data Conversion Approach. The source of the historical data to be
converted into Offender360 is the County's legacy systems as described below:
• LEGACY JMS
• IFCS
• SAP ACCOUNTING SYSTEM — After reconciling balances with EFCS, MCSO
Financial Services staff will manually enter general ledger balances into the New JWIS at
go-live. No other data will be converted from SAP.
• MUGSHOT SYSTEM
• OPERATIONS JOURNAL— "03" data is purged after three years and will not be
migrated to the New JMS.
• COURT OPERATIONS/TRANSPORTATION SYSTEM — Data in the Court
Operations/Transportation System is refreshed daily and will not be migrated to the New
JMS.
• PRE-BOOKING SYSTEM — Data in the Pre-Booking System is purged after 72 hours
and will not be migrated to the New JMS.
4.3.8. Solution Testing. The County is responsible for the development of the test cases and the Business
Process Testing will be based on the test cases. This set of test cases will be derived from the
requirements matrix, but should be a comprehensive set of test cases that Contractor will use to
finalize the system design, utilize for testing, etc. Contractor will provide a template to create the test
case scenarios, along with a sample set of scenarios for guidance. Contractor will also work with
County to develop several test cases to support this process. The purpose of this testing is for users to
validate system functionality and may or may not include all migrated data, integrations, and reports
during Business Process and System Testing. Results of the activities are compared against the
expected results and, where necessary, changes are made to the system and the scenario is repeated.
The majority of the actual tasks in the Solution Testing will be performed by the County with
Contractor's guidance. Solution testing is broken into the following components:
• Business Process Testing - The purpose of functional testing is to ensure that the overall
functionality built into the solution based on the Functional Design Document meets the
Use Cases developed in the design phase. As individual business functionality is
configured, Contractor and the County will test the functionality using the functional test

SERIAL 170002-RFP
scripts developed. The functional testing will be conducted jointly by Contractor and the
County. This testing can include, but is not limited to:
o Functional areas created and configured — entities, forms, fields
o Workflows built and configured
o Mail merge and email templates built
o Auditing configured
o Duplicate detection configured
o Reports and dashboards built
o Integrations built
o Custom interfaces built
• System Testing - All end-to-end processes, reports, data conversions, interfaces and
interfaces are tested based on test scripts developed. The purpose of this phase is to test
each process from start to fmish as it should function in a real-world scenario and
validate the data as data conversions and interfaces developed by the County are
executed. It should include testing of all aspects of the solution and in the order in which
the processes should be executed. System testing will be conducted by the County with
Contractor support.
• User Acceptance Test (UAT). All end-to-end processes, reports, integrations and
interfaces are tested by the County 'super users' and a separate set of testers based on test
cases developed by the County and Contractor. Results of the activities are compared
against the expected results and, where necessary, changes are made to the solution and
the scenario is repeated until successful. The majority of the actual tasks in the UAT will
be performed by the County with Contractor's guidance. After User Acceptance Testing
is complete, the County will sign-off on the solution. Production deployment will not
commence until the County has signed off on the solution.
4.3.9. Performance & Load Testing — Contractor has included time to conduct two (2) sessions of
Offender360 performance and load testing via StresStimulus per project phase. Contractor will
utilize its own licensed Service Provider Edition of the StresStimulus product, which it will utilize to
conduct performance testing of Offender360 at County. Contractor will provide a set of thirty
automated test scripts, covering core Offender360 functionality, and will be responsible for running
the performance and load tests based on these core scripts.
These test scripts will simulate a load of up to 5,000 simultaneous users conducting numerous
system activities, including but not limited to creating new records, updating existing records,
performing system searches, executing workflows, and executing business rules. Contractor and
County will develop a performance and load test plan that defines data loads, potential bottlenecks,
system activities, testing criteria and testing metrics.
Contractor will also create a set of up to 10 automated test scripts covering MCSO's Client
Configuration Layer (CCL), which covers functionality in the MCSO-specific configuration layer of
the Offender360 software.
Performance and load testing will take place at the points defined in the performance and load test
plan. Overall intent is to verify the system meets the County requirements and performs in an
acceptable manner.
Contractor will own the license for StresStimulus; however, this testing tool will be available to
County throughout the implementation and deployment of Offender360 and the ongoing Software
Assurance periods should County desire to further utilize the tool. Contractor has not included
performance or load testing beyond what is stated herein. Additional load testing for any optional
upgrades will also be included in the upgrade efforts.
Contractor has not included time for any infrastructure remediation work that may be needed after
performance and load tests. Contractor will work with County prior to and after go-live on
troubleshooting any application or product related concerns that may be impacting potential

SERIAL 170002-RFP
performance issues as part of its mutually agreed upon maintenance and support plan. County will
be responsible for any resulting remediation activities.
4.4. Deploy Phase. During this Phase, training, user acceptance testing and fmal system configurations are
completed. Activities required to close the project, provide post-production support, and transition the
solution and knowledge to the County are also completed during this phase.
4.4.1. Functional Training — Train the Trainer. Functional training will be provided to the project team to
enable system testing. This project team will become 'super users' of the system, and learn those
aspects of the Microsoft Dynamics CRM solution that are relevant to the Offender360 solution.
Contractor will provide MCSO with onsite "hands on" classroom training for Trainers (T3) at MCSO
facilities. Contractor will conduct a Train-the-Trainer approach in which MCSO Trainers (T3) will
conduct the training of other users (supported by Contractor). This classroom training is in addition
to the prerequisite web based "simulation training" and "core team training" described herein.
Contractor will train up to 100 County staff, which may include; T3 trainers, super users, IT staff and
subject matter experts. Contractor run training classes will last no longer than a total of five (5)
weeks. Contractor has included up to five (5) weeks of onsite training. Training will start no later
than 13 weeks prior to go-live. Contractor will finalize the training courses with the County and
provide details of the courses once the curriculum has been finalized in the training plan.
4.4.2. Functional Training — End User Training. End user training will be performed by the MCSO
trainers. Contractor will provide training tools described herein for MCSO to efficiently administer
the training including; web based documentation, "simulation training" and web based on demand
training. Contractor will provide the training tools and documentation prior to training commencing.
Training content will be divided into functionality tracks. Training sessions will be scheduled in
order to customize the training per role. The County will be responsible for delivery of all end user
training with support from Contractor. The Contractor has included time to support County trainers
in up to six (6) weeks of end user training sessions.
4.4.3. Administrative & Technical Training. Contractor will train the administrative and technical team.
Contractor has included two (2) weeks for specific administrative and technical training sessions as
specified in the table below. This is in addition to other training that IT staff may attend over the
duration of the project. Contractor will provide system documentation as part of the project.
Contractor proposes the following training areas. Contractor will finalize the training courses with
the County and provide details of the courses once the curriculum has been finalized in the training
plan:
• Introduction to Offender360
• Administration
• Security Roles and User Maintenance
• Teams
• Field Level Security
• Microsoft Dynamics CRM Processes (workflows)
• North52 Formula Manager
• ADXstudio (web portal overview)
• Epilogue (system administration overview)
• Microsoft Dynamics CRM Advanced Find Query Tool
• Microsoft Dynamics CRM Report Wizard
• Microsoft Dynamics CRM Email Templates
• Microsoft Dynamics CRM Word Templates
• Microsoft Dynamics CRM Entity Auditing
• Microsoft Dynamics CRM Duplicate Detection Rules
• Microsoft Dynamics CRM Dashboards
• Microsoft Dynamics CRM Customization Tool
• Basic customization of Foims & Views (add a field to the database, add a value to a pick
list, change a label name, add/change a view)
• Scribe (data conversion and integration tool)
• SSRS Report Development in a CRM Environment

SERIAL 170002-REP
Topic Description Training Sessions
CRM Administration Includes administrative topics Up to Four (4) four (4) hour
specified below sessions with one (1)
Contractor trainer.
ADXstudio, North52, Epilogue System Administration, Up to Four (4) four (4) hour
foimula development and sessions with one (1)
security Contractor trainer.
SSRS Report Development in *Training on how to develop Up to Two (2) two (2) hour
CRM Environment SSRS reports in a CRM session with one (1)
environment. Contractor trainer.
Scribe Product Training ** Training on Scribe tool Up to ten (10) four (4) hour
customer will use to develop sessions with one (1)
data migration and Contractor trainer.
integrations.
* Assumes students are experienced SSRS report developers. Course focuses on connecting to
CRM environment. It does not teach the basics of SSRS report development.
** Training assumes utilization of Scribe Online training courses in addition to Contractor
classroom/hands on training sessions.
Scribe Product Training will be a combination of classroom/hands on sessions provided by the
Contractor, Scribe Online Training Courses, and joint development sessions (Contractor guides
County through development of data conversion and/or interfaces.
In addition Contractor will provide one (1) week of IT System Administrator training post go-live
on topics developed in conjunction with the County associated with the support of the
Offender360 solution deployed.
4.4.4. Training Materials: Contractor will work with the County and develop an overall training plan and
training schedule. Contractor will provide all instructional materials, media presentation devices and
presentation media. Contractor will create the training materials and documentation to support the
training requirements including the production of systems documentation and end user training
materials. Materials are electronic and can be outputted in many files types such as MS Word, PPT,
PDF and even MN.
4.4.5. Content Development: Contractor will provide access to electronic learning materials and hands-on
video simulations via the Epilogue training portal during the project. Learning materials developed
can be outputted in many files types such as MS Word, PPT, PDF and even MP4 and SCORM
simulations that users will interact with to watch a process being completed, try the process on their
own, or work through a self-test on a process. Contractor has included up to eighty (80) training
simulations. Contractor will load user data into the Epilogue system to control for access to the
simulations. Users can come into the training portal as many times as they wish to access training
simulations and materials. Contractor has included time to train County on how to create additional
training simulations and how to load user data and training simulations created for Epilogue into
Cornerstone LMS.
4.4.6. Built in self-help: Contractor will embed contextual help right into Offender360. Users will be able
to get access to all training materials within Offender360, including; workflows, project
documentation and training materials. Learning materials embedded can be outputted in many files
types such as MS Word, PPT, PDF and even MP4 and SCORM.
For most effective learning transfer and knowledge retention and based on the total number of users
to be trained, Contractor recommends starting classroom training sessions approximately two to
three months before go-live in order to ensure knowledge retention and ensure that Contractor is
basing the training on the most up to date system configurations.

SERIAL 170002-RFP
4.4.7. Migrate to the Production Environment — Customizations and reports are migrated to the
Production database. Users and security settings are implemented. The County will provide
Contractor access to the environment or will complete the migration steps with Contractor guidance.
County and Contractor will work together to plan and execute dress rehearsals that will include data
loading and simulated go live activities. Contractor has included hours to complete these activities.
Additional work occurring as a result of the County internal change control, inappropriate security
rights, environmental issues, or other County-related delays may result in a change order.
4.4.8. Execute Data Migration — Contractor will load converted .IMS legacy system data from the
SHIELD Staging Database into the production SHIELD database. Once data is fully loaded, reports
may be generated and reconciled with the current systems for validation to confirm that the system
will operate in confoimance with all specifications in the production environment. Since this step
marks the key point before using the new system in a production environment, sufficient quality
checks will be included to confirm accuracy such as user sign-off and management approval of
migration results. This step may take place over a weekend and typically requires the involvement of
the entire Project Team.
4.4.9. "Go Live" — Users begin using the application to perfoi in their daily processes. Project
documentation is finalized and reviewed. Prior to the "Go Live", Contractor will work jointly with
the County to define and document a Cutover plan that will provide details regarding the dates,
resource plans, support infrastructure and escalation procedures for the "Go Live" time period.
Contractor has included time across multiple resources and skillsets of "Go-Live" support in which
Contractor will work with the County to stabilize the Offender360 environment. Contractor will
provide four (4) weeks of Go Live Support with the remote Contractor County Care team providing
additional support if necessary. "Go Live" support will primarily consist of troubleshooting and
issue resolution by the main onsite Contractor resources during the County's normal hours of
operation. System critical issues and system outages will be addressed by the Contractor "Go Live"
support team as they occur and Contractor understands that these incidents may fall outside of the
County's normal hours of operation. At the end of the Go Live Support period, the County will be
transitioned to the Contractor's Customer Support Team for ongoing system support.
Contractor has included time to support separate deployments of the following functionality:
CACTAS
Pre-Booking, Court Operations/Transportation
• Pre-Booking will be deployed in four distinct waves representing subsets of
portal users over a four (4) week period
• Court Operations/Transportation deployment will include Barcode/RFID
functionality utilizing County procured hardware/software.
4.4.10. Project Closure. A meeting will be held to identify the County taking over support responsibility
and to confirm post implementation expectations and arrangements. At this time, the Project Closure
Report which summarizes the project from a budget, schedule, scope, and quality perspective will be
delivered to the County along with a Final System Acceptance Document for signature.
5. Milestones/Deliverables
Major project milestones are identified in the table below. Major Milestones represent key project checkpoints
that are to be tracked with progress against plan (e.g., early, on-time, late) and percent complete and reported in
the monthly project status reports. A milestone is considered complete once all associated deliverables have
been accepted by County. All milestones that are behind schedule must be clearly identified in the status report
along with a corrective action plan to bring each milestone back on schedule.
The Contractor's team shall prepare all deliverables and project documentation in accordance with County
standards and contract requirements. Table 4 Milestones and Deliverables lists each required milestone and
deliverable and completion criteria followed by a description of each.

SERIAL 170002-RFP
Project Methodology Milestone/Deliverable Completion Criteria
Schedule Phase
Phase
Phase 1 Define Project Kickoff Kickoff Meeting Completed
Phase 1 Define Project Initiation Documentation All specified deliverables approved
• Project Management Plan by MCSO
• initial 90 Day Project Schedule Initial Project Schedule will have
• Project Charter high level dates for entire phase 1.
• Cost/Budget Management Plan
• Quality Management Plan
• Resource Management Plan
• Communication Plan
• Requirements Specification
Management Plan
• Scope and Change Management Plan
• Enterprise Architecture Design
• Risk/Issue Management Plan
Phase 1 Define Dynamics Offender360 Installation — Baseline solution installed in
Development Environment development environment
Phase 1 Design t, Functional Requirements Document (FRD) FRD approved by MCSO
Phase 1 Design Technical Requirements Document (TRD) TRD approved by MCSO
Phase 1 Design Full Project Schedule Project Schedule approved by
MCSO
Phase 1 Design Solution Prototype #1 *Prototype sessions completed and
approved by MCSO
Phase 1 Design Dynamics Offender360 Installation — Test Baseline solution installed in test
Environment environment
Phase 1 Design Testing Plan Testing Plan approved by MCSO
Phase 1 Design Solution Prototype #2 *Prototype sessions completed
Phase 1 Design Functional Design Document (FDD) FDD approved by MCSO and
approved by MCSO
Phase 1 Design Report Design Document Report Design Document approved
by MCSO
Phase 1 Build & Test Configuration Build #1 *Build review sessions completed
and approved by MCSO
Phase I Build & Test User Training Plan User Training Plan approved by
MCSO
Phase 1 Build & Test Technical/Analyst Training Plan Technical/Analyst Training Plan
approved by MCSO
Phase 1 Build & Test Configuration Build #2 *Build review sessions completed
and approved by MCSO
Phase I Build & Test Data Migration Development Scribe jobs delivered to test
environment
Phase 1 Build & Test Report Development Reports delivered to test
environment and approved by
MCSO
Phase 1 Build & Test Solution Testing UAT completion by MCSO
Phase 1 Build & Test Dynamics Offender360 Installation — Production Baseline solution installed in
Environment production environment
Phase 1 Deploy Production Deployment Documentation All specified deliverables approved
e MCSO Support Team Knowledge by MCSO
Transfer Plan
• JMS Security Policy
• Implementation Cutover Strategy
• Cutover Plan
• JMS Solution Document

SERIAL 170002-RFP
Project Methodology Milestone/Deliverable Completion Criteria
Schedule Phase
Phase
o Maintenance & Operations Plan
• Configuration & Release Plan
Phase 1 Deploy Go Live/System Cutover Project Go Live Achieved
Phase 2 Define Project Kickoff Kickoff Meeting Completed
Phase 2 Define Project Initiation Documentation All related deliverables approved
• Project Management Plan by MCSO
• Project Schedule
• Project Charter
• Cost/Budget Management Plan
• Quality Management Plan
• Resource Management Plan
• Communication Plan
• Requirements Specification
Management Plan
• Scope and Change Management Plan
• Enterprise Architecture Design
• Risk/Issue Management Plan
Phase 2 Define New Component Installation — Development Baseline system components
Environment installed in development
environment
Phase 2 Design Functional Requirements Document (FRD) FRD approved by MCSO
Phase 2 Design Technical Requirements Document (TRD) TRD approved by MCSO
Phase 2 Design New Component Installation — Test Baseline system components
Environment installed in test environment
Phase 2 Design Testing Plan Testing Plan approved by MCSO
Phase 2 Design Solution Prototype #1 *Prototype sessions completed and
approved by MCSO
Phase 2 Design Solution Prototype #2 *Prototype sessions completed and
approved by MCSO
Phase 2 Design Solution Prototype #3 *Prototype sessions completed and
approved by MCSO
Phase 2 Design Functional Design Document (FDD) FDD approved by MCSO
Phase 2 Design Report Design Document Report Design Document approved
by MCSO
Phase 2 Build & Test User Training Plan User Training Plan approved by
MCSO
Phase 2 Build & Test TechnicalJAnalyst Training Plan Technical/Analyst Training Plan
approved by MCSO
Phase 2 Build & Test New Component Installation — Production Baseline system components
Environment installed in production environment
Phase 2 Build & Test Configuration Build #1 *Build review sessions completed
and approved by MCSO
Phase 2 Build & Test Configuration Build #2 *Build review sessions completed
and approved by MCSO
Phase 2 Build & Test Configuration Build #3 *Build review sessions completed
and approved by MCSO
Phase 2 Build & Test Report Development Reports delivered to test
environment and approved by
MCSO
Phase 2 Build & Test Solution Testing UAT completion by MCSO
Phase 2 Deploy Production Deployment Documentation All related deliverables approved
• MCSO Support Team Knowledge by MCSO
Transfer Plan

SERIAL 170002-RFP
Project Methodology Milestone/Deliverable Completion Criteria
Schedule Phase
Phase
• JMS Security Policy
• Implementation Cutover Strategy
• Cutover Plan
• JMS Solution Document
• Maintenance & Operations Plan
Configuration & Release Plan
Phase 2A Deploy Go Live/System Cutover Project Go Live Achieved
Phase 2B Deploy Go Live/System Cutover Project Go Live Achieved
PI & P2 Ongoing Weekly Activity Reports Weekly after Project Kickoff
P1 & P2 Ongoing Monthly Status Reports Monthly after Project Kickoff
P1 & P2 Ongoing Lessons Learned At the end of each phase
Table 1 Milestones
NOTE: All Phase 2. deliverables with the exception of the Project Schedule will be updates to the corresponding
Phase 1 documentation.
* Prototype/Build Review Sessions will include the following functional groups
Phase 1
• Prototype 1 - Booking, Property, Court Cases/Charges/Dispositions/Court Appointments/Holds, Housing,
Classification, Release
• Prototype 2 - Inmate Discipline, Appeals/Grievances, Incident Reports, Movements, Scheduling,
Visitation, Jail Operations
• Build Review 1 - Booking, Property, Court Cases/Charges/Dispositions/Court Appointments/Holds,
Housing, Classification, Release
• Build Review 2 - Inmate Discipline, Appeals/Grievances, Incident Reports, Movements, Scheduling,
Visitation, Jail Operations, Document Management, Security
Phase 2
• Prototype 1 - Pre-Booking
• Prototype 2 - Court Operations, Transportation
• Prototype 3 - Trust Accounting, Canteen
• Build Review 1 - Pre-Booking
• Build Review 2 - Court Operations, Transportation
• Build Review 3 - Trust Accounting, Canteen, Document Management, Security
5.1. Description of Contract Deliverables
5.1.1. Kick-off Meeting
A meeting conducted by the Contractor to introduce team members, introduce the approach the
Contractor will be taking to the project, and layout the overall timeline. The kick-off meeting serves
as a communication tool for the Executive Sponsors, project team members and subject matter
experts, as well as other interested County parties.
5.1.2. Weekly Activity Reports
Activity reports are to be produced weekly and distributed via email. The report shall identify work
completed during the week, work underway, and work planned to be completed next week. Any
issues surfacing during the week will also be highlighted in the weekly report. The weekly activity
reports serve as a communication tool to team members, project management, program management,
and Executive Sponsors as to the progress the project is making and acts as an early warning
notification of project issues.
5.1.3. Monthly Status Reports
Status reports are to be produced monthly and distributed via email. The report identifies progress
against plan (early, on-time, late) and percent complete against each major project milestone. Project
risks are discussed in the report along with mitigation activities. Project issues and resolution

SERIAL 170002-REP
progress are documented. Also included is an updated project schedule showing task completion,
task progress, and addition of any newly identified tasks. The intent of the monthly status report is to
give Executive Sponsors and other monitoring entities a summary view of project progress and the
risks and issues faced by the project. (Should a list of change orders submitted/approved/denied be
included?)
5.2. Project Management Plan (P1VP13)
A PlVfP that includes all of the areas identified in the Project Management Body of Knowledge (PMBOK)
shall be produced that lays out all processes and procedures that will be used by the Contractor to manage
the project. The purpose of the project management plan is to clearly set expectations with project team
members and executive oversight entities.
5.3. Project Charter
The project charter deliverable delineates the definition of the project. Examples of items contained in the
charter include scope, objectives, project participants, identification of roles and responsibilities, project
objectives, and stakeholders. The charter often references other documents where additional details can be
found. It serves as a reference of authority for the project. Once produced, the charter will be revisited on a
periodic basis and updated by the Contractor's project manager as required during the life of the project.
5.4. Risk and Issues Management Plan
The Risk Management Plan deliverable is used to gauge the project's level of risk exposure and specifies
any areas of weakness that may prohibit successful completion of project goals and objectives. Risk and
issue identification is the process of identifying situations or events that could lead to a negative impact to
successful project completion. Project managers must be vigilant in recognizing and documenting potential
vulnerabilities or risks so that they can be properly evaluated for probability of occurrence and potential
impact.
5.5. Quality Management Plan
A quality management plan shall be developed that defines the acceptable level of quality and describes
how the project will ensure that the level of quality is maintained in work products and processes. The
quality management plan is used to ensure that project deliverables are built to agreed upon standards and
requirements, work processes are documented and performed efficiently, and corrective actions are taken
for all non-conformances found.
5.6. Project Schedule (WBS)
The project manager shall develop a work breakdown structure (AKA project schedule) that organizes the
project and the team's activities and work into manageable sections. Project deliverables will be the basis
for the development of the WBS. Deliverables will be broken down into sub-deliverables and
tasks/activities with resources assigned and timelines established. The WBS will be updated on a regular
basis and will serve as a tool to help communicate project status.
5.7. Communications Plan
A communications plan shall be developed that identifies all key project stakeholders and presents the
roadmap for getting project messages, the mechanisms planned for communication and the expected
frequencies.
5.8. Resource Management Plan
The project resource management plan shall identify what resources and respective skill sets will be needed
along with the timing according to the project's schedule. Since the availability of resources is a challenge
common to all projects, a good resource management plan provides project management with a tool to
communicate resource requirements with sufficient lead time to allow for acquisition and/or availability for
project related tasks.
5.9. Organizational Change Management Plan
An organizational change management plan shall be developed that defines the approach that will be used
to transition County individuals and business units from the current processes, procedures, and
responsibilities to those that are required for the benefits of the New TMS to be realized. Specific strategies
and tactical plans shall be developed for each part of the organization.

SERIAL 170002-RFP
5.10. Requirements Specification Management Plan
The initial set of New JMS requirements shall be those contained in County's original RFP, including the
Contractor's Best and Final Offer (BAFO) response and pricing to meet each requirement. As part of the
project, the project manager will develop a plan that tracks any changes and/or clarification to these
requirements. Additionally, a requirements traceability matrix shall be developed and maintained. The
requirements specification plan will help ensure the new solution meets County stated requirements and
will facilitate project testing activities.
5.11. Enterprise Architecture Design
The Enterprise Architectural Design deliverable shall document a comprehensive framework of business
principles, practices, and technical standards that direct the design, construction, deployment and
management of the solution. It must describe the infrastructure components needed for the New JMS
Solution and how it fits within and connects to existing MCSO, County, and State components. It shall
provide direction for current and future activities, supported by underlying principles, standards, and best
practices while demonstrating alignment to MCSO, County, and State strategic initiatives and enterprise
architecture standards. The design document must identify the architectural layers and solution
architecture (hardware and software) employed, and highlight security, audit controls, and frameworks
since these are of particular interest to MC SO.
5.12. Test Nan
The test plan shall document each phase and type of testing planned for the New JMS including unit,
system, integration, load, regression, security, high-availability/reliability, and external incoming queries
testing, as well as defect management. The scope and planned number of rounds for each type will be
identified along with the resources that are needed to complete all testing tasks.
5.13. Training Plan (End User and TechnicallAnalyst)
A training plan shall be created that details the training that will be provided to the County user
community and the technical (developer, system administration, and analyst) staff. The training plan will
clearly identify the goals, training needs, groups to be trained, method of training planned for each group,
the facilities or tools that will be used, training materials that will be produced, and a high level schedule
of training events.
5.14. MSCO Support Team Knowledge Transfer Plan
A plan shall be produced that details the knowledge that MSCO staff will need to support the system.
Specific activities and tasks will be outlined that, when executed, will transfer knowledge from the
Contractor team to County support staff. County support resource requirements will be called out in the
plan, along with associated skill sets and training prerequisites.
5.15. New Jail Management System Security Policy
Implementation of the New JMS solution makes the legacy security policy obsolete. A new Security
Policy shall be documented that details how all security requirements shall be satisfied and must be
reviewed and approved by the MCSO System Security Officer (S SO).
5.16. Implementation Cutover Strategy/Options Analysis and Recommendation
One of the key decisions to be made in the project is how the new solution will be implemented. Will it be
big bang, phased by modules, phased by functionality, phased by jail or a hybrid approach? A project
deliverable shall be created that details the alternatives studied, the strengths/weaknesses/risks associated
with each alternative and the overall recommendation. This is a very important deliverable as many of the
other deliverables are dependent upon the agreed upon implementation strategy.
5.17. Tactical Deployment/Transition/Cutover Plan
A very detailed tactical deployment plan shall be created that will serve as the formula for cutting over to
the New JMS solution. The plan will include detailed tasks, responsible parties, dependencies, and
expected duration of the tasks (start time, end times). The cutover plan will include contingencies and
fallback strategies to be initiated should an unforeseen problem occur during cutover. Communication
channels to be used during the cutover will be documented so that all key players and stakeholders are
aware of cutover progress.

SERIAL 170002-RFP
5.18. Documentation
Documentation for the project takes many forms. The Contractor shall create and maintain a
documentation library that will provide a comprehensive audit history of services provided and work
product developed within the scope of the project. The Contractor shall ensure that all documentation is
available to project team members throughout and following implementation, and that the project
documentation library is organized and complete prior to project close-out. The documentation library
shall be hosted on a County system. Project-related work products, materials, correspondence, and all
other documentation are and shall remain the exclusive property of County.
The bullets below identify minimum project documentation deliverables required for the project. The
Contractor is expected to identify and produce additional types of documentation based on their chosen
methodology.
• All Project Plans and Plan Updates
• Status Reports, Meeting Agendas and Minutes, Emails, Memos, and Other Project Correspondence
• Project-Related Diagrams, Photographs, and Images
• Project Reports, Presentations, Spreadsheets, and Website Content
• Requirements Documentation
• Design Documentation
• End User Materials
• Technical Materials
• Training Materials
• Online Help
• Workflow Documentation
• To-Be Business Processes
• Application Configuration
• Database (schemas, tables, etc.)
• Reports
• Dashboards
• System Administration
• All Other Project Artifacts
5 19 Maintenance and Operations Plan
The maintenance and operations plan describes the activities required to effectively operate and maintain
the application system in a day-to-day operational environment. The deliverable shall detail plans for
operating, monitoring, performance tuning, identification and training of operators, and testing the system
after changes are made. Three types of maintenance to be included in the plan are: 1) preventative
maintenance (i.e., backups) and component replacement prior to end of life; 2) reactive maintenance —
correcting faults when they occur; and 3) software maintenance including single bug fixes, multiple fixes
grouped as a patch, and software upgrades.
5.20. Configuration and Release Management Plan
The objective of configuration and release management is to preserve the integrity and stability of the
application systems and manage their life cycles in a controlled manner This deliverable shall document
the process for introducing change including: 1) identifying; 2) assessing and approving; 3)
implementing/installing; 4) testing; and 5) documenting all changes made to the system.
5.21. Lessons Learned (at end of each phase)
At the conclusion of each phased called out in the project schedule, lessons learned shall be documented
and distributed to the team. This deliverable will detail what worked well and what did not, and will serve
to inform future phases so successes can be capitalized upon while challenges and failures can be avoided.

SERIAL 170002-RFP
EXHIBIT C, SOFTWARE LICENSE AND MAINTENANCE AGREEMENT
1. Software License
1.1 License Grant. For each fully paid subscription during the Term, Contractor hereby grants to Licensee a
non-exclusive, perpetual, irrevocable, fully paid-up, royalty-free, worldwide limited license to use the
Licensed Software, in object and/or source code format, as the parties may agree, solely for the internal
business purpose of Licensee.
1.2 Use of License.
a. Except as otherwise set forth herein, Licensee expressly acknowledges and agrees that the Licensed
Software (exclusive of Derivatives) is wholly proprietary to Contractor and/or the Publishers.
Contractor and the Publishers, as appropriate, retain all right, title, and interest in the Licensed
Software, and Licensee has no rights to the Licensed Software other than as expressly set forth in this
License. Except as otherwise set forth in this License, Derivatives shall be owned jointly by the parties,
and Contractor shall retain the right to use the know-how, ideas, techniques, and concepts used by it in
developing such Derivatives under this License.
b. Contractor shall provide the XML compiled solution also known as source code, to Licensee.
c. Other than as expressly permitted by this License, Licensee agrees not to reverse engineer, reverse
compile, disassemble, publish or distribute the Licensed Software or use it for any commercial
purpose. Other than as expressly permitted by this License, Licensee agrees not to use the Derivatives
for any commercial purpose.
d. Licensee has the limited license to create Derivatives of the Licensed Software, solely for use with the
Licensed Software, and not as stand-alone components. Licensee acknowledges and agrees that all
portions of any Derivatives of the Licensed Software that it creates or has created for it by a third party
are the sole property of Licensee, subject to the terms of this Exhibit. Licensee irrevocably grants,
transfers, and assigns to Contractor, without reservation, a sub licensable, fully paid up, royalty-free,
perpetual worldwide nonexclusive license in and to all Derivatives of the Licensed Software, which
Licensee may have or acquire, by operation of law or otherwise.
e. Licensee will not copy, in whole or in part, the Licensed Software except for backup and archiving
purposes.
f. Licensee agrees that it will not directly or indirectly export or transmit the Licensed Software (or any
Derivative), in whole or in part, or any technical data relating thereto, to any country to which such
export or transmission is restricted by any applicable U.S. or international regulation or statute, without
prior written consent, if required, of the Bureau of Export Administration of the U.S. Depai tinent of
Commerce, or other such governmental entity as may have jurisdiction over such export or
transmission.

SERIAL 170002-RFP
1.3 Offender 360 License. Notwithstanding anything to the contrary herein:
a. Contractor shall not and does not grant to Licensee access or license keys to open the source code to
various North52, Scribe Insight, ADXstudio and Epilogue programs (collectively, the "Embed
Software"), a component of Offender 360, or to work with such source code, unless Licensee has
acquired the right to use the development tools in the Embed Software.
b. This License does not grant any rights to copy, modify, or distribute the Embed Software source code.
These rights may be available directly from North52, Scribe Insight, ADXstudio and Epilogue under a
separate agreement.
c. The Embed Software may not be (i) used to develop and/or (ii) offered in conjunction with, new
applications, databases or tables other than those contained in Offender 360. However, Licensee is able
to license additional Embed Software functionality offered by North52, Scribe Insight, ADXstudio and
Epilogue or other authorized third parties.
d. Licensee acknowledges that North52, Scribe Insight, ADXstudio and Epilogue specifically disclaim all
warranties, whether express, implied or statutory, relating to the Embed Software provided under this
License, including, but not being limited to, all warranties and conditions of merchantability,
merchantable quality and fitness for a particular purpose.
e. Licensee agrees that North52, Scribe Insight, ADXstudio and Epilogue shall not be liable for any
damages, whether direct, indirect, incidental or consequential, as a result of the use or the installation
of the Embed Software.
f. Licensee agrees that the Licensed Software requires other server software, such as Microsoft
Dynamics, specifically Microsoft Dynamics CRM, in order to function. Licensee agrees to obtain
these necessary licenses separately from this Software License Agreement.
1.4 Maintenance
As long as Licensee is current on its maintenance plan for the Licensed Software, Contractor agrees to
provide Licensee standard maintenance for the Licensed Software, which shall include but not be limited to
making available to Licensee new version releases of the product, service packs, hot fixes and
enhancements.
1.5 Warranty Repair
As long as Licensee is current on its maintenance plan for the Licensed Software, Contractor agrees to
provide Licensee warranty repair support for the Licensed Software, which will include system error issues
in the Licensed Software, commonly referred to as bug fixes. A system error means any error, problem, or
defect, which is reproducible by Contractor that results in incorrect functioning of the Licensed Software.
Warranty repair support is not covered under this License if the problem is caused by (i) any modification,
variation or addition to the Licensed Software not performed by Contractor; (ii) your incorrect use, abuse or
corruption of the Licensed Software; (iii) use of Licensed Software with other software or on equipment
with which the Licensed Software is incompatible, or (iv) error conditions that do not significantly impair
or affect operation of the Licensed Software. Additionally, the warranty does not cover infrastructure-
related performance issues.

SERIAL 170002-RFP
If the issue is not deemed to be a warranty report support issue, time spent addressing the issue will be
considered general support handled under a separate statement of work between Contractor and Licensee.
1.6 General
Except for the limited licenses expressly granted herein, Contractor and the Publishers will and do retain all
right, title and interest (including, without limitation, all Intellectual Property Rights) in and to all of the
Licensed Software, including all modifications or enhancements to any of the Licensed Software, except as
otherwise provided herein. Licensee shall take any action reasonably requested by Contractor and/or
Publisher to evidence, maintain, enforce or defend Contractor's and/or Publisher's Intellectual Property
Rights. Licensee shall not take any action to jeopardize, encumber, limit or interfere in any manner with
Contractor's or any Publisher's, or their respective licensors', ownership of and rights with respect to any of
the Licensed Software. All rights not expressly licensed to Licensee hereunder are hereby expressly
reserved by Contractor and/or the Publishers. Notwithstanding the foregoing, Licensee retains all
ownership rights to its and its Licensed Users' data.
2. Confidential Information
2.1 Recipient agrees to use commercially reasonable care, but in no event no less than the same degree of care
that it uses to protect its own confidential and proprietary infounation, to prevent the unauthorized use,
disclosure, publication or dissemination of the Discloser Confidential Infonnation. Recipient will provide
Discloser's Confidential Infoiniation to its employees and contractors only on a "need to know" basis,
subject to the twins of this License, provided that Recipient's employees and contractors have entered into
a written Confidential and Non-Disclosure Agreement with Recipient substantially in accordance with
these terms and conditions.
2.2 Recipient agrees not to use Discloser Confidential Information for its own or any third party benefit
without the prior written approval of Discloser. Notwithstanding the foregoing, Recipient may disclose
such Confidential Infounation if and to the extent required by any judicial or governmental request,
requirement or order, provided that Recipient agrees to take reasonable steps to give Discloser sufficient
prior written notice in order to enable Discloser to contest such request, requirement or order. Recipient
will return all tangible Discloser Confidential Information, including but not limited to all computer
programs, documentation, notes, plans, drawings, and copies thereof, to Discloser immediately upon
Discloser's written request.
2.3 All Discloser Confidential Infoitnation, including any and all Derivatives thereof created by Discloser or
Recipient, will be and remain the property of Discloser and no license or other rights to such Confidential
Infoimation is granted or implied. Discloser warrants only that it has the right to disclose the Discloser
Confidential Information to Recipient. All Discloser Confidential Information is provided "AS IS" and
without any warranty, express, implied or otherwise, regarding its accuracy or performance.
2.4 The obligation of Recipient to maintain the confidentiality of Discloser Confidential Infojijiation will
survive the expiration or teimination of this EULA for as long as the information in issue is within the
definition of Confidential Infounation or otherwise agreed to in writing by Discloser.
3. Restrictions on Use.
Licensee may not access the Software for purposes of monitoring its availability, performance or functionality, or
for any other benchmarking or any other purposes that are competitive to Contractor. Licensee may not reverse
engineer, decompile, disassemble or discover the Software; modify, adapt or translate the Software or create
derivative works of any kind based on the Software or content; make more copies of the Software than specified in
this EULA or allowed by applicable law; publish the Software for others to copy; rent, lease, lend, distribute,

SERIAL 170002-RFP
sublicense, or assign the Software; or use the Software for commercial software hosting services or operating a
service bureau.
4. Intellectual Property Ownership.
The Software is licensed. This EULA only gives Licensee rights to use the Software in accordance with the terms of
this EULA. Contractor reserves all other rights. Licensee further acknowledges that the Software, including all
code, content, protocols, software, and documentation are Contractor's property or the property of Contractor's
licensors, and are protected by U.S. and international copyright, trademark, patent and other proprietary rights and
laws relating to intellectual property rights. The original and all copies of the Software, and all modifications,
corrections, or enhancements to the Software and any other computer programs licensed by Contractor to Licensee,
documentation relating thereto, and all inventions, systems, processes, improvements and patentable ideas, which
were or are later conceived by Contractor alone or with others in whole or in part are the sole property of Contractor.
All work performed by Contractor now or hereafter, under this EULA, the SOW or otherwise, will not be considered
a work for hire, and Contractor will own all copyrights in all software and other materials developed or created by
Contractor.
6. Indemnity.
6.1. Indemnification by Licensee. Licensee shall indemnify, defend and hold Contractor and its Affiliates
harmless from and against any and all liabilities, claims, demands, damages, costs and expenses or money
judgments (including reasonable attorneys' fees) asserted against, incurred by or rendered against any of
them from third party claims or actions arising from Licensee's use of the Software, negligence,
misrepresentation, or breach of this EULA. Contractor shall give Licensee prompt notice of any such
claims, and permit the Licensee to control the defense and settlement of claims, and reasonably cooperate
with the Licensee in connection with the defense and settlement of claims.
7. Warranties and Warranty Disclaimers. CONTRACTOR MAKES NO WARRANTY WITH RESPECT
TO TILE SOFTWARE, WHICH IS PROVIDED AS-IS, WITHOUT ANY REPRESENTATIONS OR
WARRANTIES. CONTRACTOR DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED OR
STATUTORY, INCLUDING WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
9. Term and Termination
9.2 Termination caused by default. If either party fails to observe or perform any material obligation under
this EULA, the non-defaulting party may give written notice to the defaulting party specifying the material
failure. If the material failure is not corrected or a mutually agreed plan to correct the failure has not been
established within thirty (30) days after the date of such notice, the non-defaulting party may terminate this
EULA upon written notice to the defaulting party. The right of the non-defaulting party to teliainate this
EULA under this Section is in addition to all other rights that are available to it under this EULA, at law or
in equity.
9.3 Disposition of software on termination. If the County terminates this agreement the Licensor hereby
grants to Licensee a nonexclusive, royalty-free, perpetual license to use any Software and Documentation
that were accessible to and provided the County during the term of this Agreement. The grant foregoing
license shall be subject to the County's full payment of any amounts owed for the Software and
Documentation and shall be revocable if the County is in material breach of this Agreement. The County
and Licensor agree that upon such termination the County retains the obligation to protect the confidential
nature of the software and that Licensor has no further obligation to provide maintenance, updates, or any
service to ensure the performance of the Licensed Materials after the termination date

SERIAL 170002-RFP
EXHIBIT D - SOFTWARE SUPPORT AND SERVICE LEVEL AGREEMENT
1. Customer Care - Unlimited Support Plan
Contractor will provide direct support for all products included in the scope of work. In the event Contractor cannot
troubleshoot, Contractor will contact the software provider on behalf of the County to resolve any outstanding
questions, and communicate the resolution back to the County.
2. Scope of Customer Care - Services
Maricopa County may request an unlimited number of support requests for the following services. These are offered
in support of the application listed in Exhibit C. The examples provided under each of the following headings are
intended to provide a list of reference activities for each heading. The lists are not meant to be all inclusive.
3. Processing Issue (break/fix)
This service ensures that we are responding to issues that arise during the normal course of business. Examples
include but are not limited to the following topics:
• An error message is appearing in a window and the user cannot determine the root cause.
• A user cannot log in or lacks the appropriate security to complete a process.
• A user enters data and cannot save the data, or "saved" data appears to be missing.
• A print job or a workflow will not execute:
o An error message is appearing in a window and the user cannot determine the root cause.
o A user cannot log in or lacks the appropriate security to complete a process.
o A user enters data and cannot save the data, or "saved" data appears to be missing.
4. "How Do I..."
Contractor will work with your users to answer generic, "out of the box" functional questions. Our goal is to assist
your users with functional questions that will allow them to take advantage of inherent functionality within the
application. Please note this is not meant to be "User Training", nor is it meant to be "process engineering". We
have provided some common "How do I" questions below to set expectations for the type of questions that will be
answered:
a) How do I open or close a fiscal period? How do I book a wire transaction?
b) How do I delete a stuck user? How do I change a user's permissions?
5. Database Restore from a Recent Backup
In the event of system data loss due to user error or some other event, Contractor will work with the County to
perform a full database restore if the County has a recent backup readily available.
6. Important Note: Contractor relies on Maricopa County to provide a valid database backup. Any issues that
result from the restoration of an invalid or corrupt database are the responsibility of Maricopa County.
7. Out of Scope Services

SERIAL 170002-RFP
Contractor offers Project based professional services for your organi7ation's Dynamics needs that are in excess of
the scope of this agreement. In general, any services deemed to be too complex, risky or lengthy will be defined and
performed under a separate Statement of Work.
8. Important Note - Professional Services required or requested outside the scope of this agreement may not be
exchanged for services within this agreement.
a. *Service Packs and Hotfixes — Applying service packs and hotfixes.
b. *Upgrades - New version upgrade are performed as a separate project.
c. *Enhancements - Any product enhancements to the system (e.g. screen or report changes, making
fields required, building a workflow, creating an import/export routine, etc.). This is covered
under the Maintenance/Warranty included in your Maintenance Program. See Software License
and Maintenance Agreement.
d. New Integrations - Any new integration that needs to be created requires design, build and test
time, thereby resulting in an effort that is outside the scope of Customer Care.
e. Additional User Training - Any user training in excess of the "How do I" described above.
f. New Module Implementation - The process required to select, configure, train and implement any
new module or ISV (e.g. Document Management).
g. Changes to Integrations not Built by Contractor - Any integration that has not been designed,
developed and tested by Contractor will be supported by our Professional Services team on a "best
effort" basis. Please note that situations may arise where documentation for the existing
integration does not exist, and some level of documentation may needs to be created prior to
making the change.
h. Resolving user generated data problems - Situations arise where a user has inadvertently affected
data integrity or quality and remediation efforts need to take place. Often times the situation can
only be resolved by running a Microsoft Dynamics utility, importing historical data, performing
manual data entry, or by updating records via direct table changes in SQL. All of these
remediation activities are beyond the scope of this agreement. The only exception is the "Data
Restore from a Recent Backup" scenario listed in the "In Scope" section of this agreement.
i. Self-Upgrades - Remediation or system failures due to the County perfouning a self-upgrade,
service pack or hot fix.
j. Hosting / Cloud Computing - Any issues related to hosting or "cloud" computing environments
(except for Tribridge Concerto).
k. Disaster Recovery Services — includes any data restoration activities with exception of the
scenario described under "Data Restore from a Recent Backup".
1. Database tuning and optimization
m. Workstation Installations
n. Server Operating System Installations
*Software Updates, Hot Fixes, software patches and new versions of the software are not included under this
support agreement, but are made available to County, as part of their participation in the Software License and
Maintenance Agreement (Exhibit C).

SERIAL 170002-RFP
9. Assumptions
The following assumptions have been made in regard to this agreement:
a. Data Reconciliation and Validation - With client approval, Contractor will perform steps to
resolve issues using Microsoft recommended tools, SQL Scripts and best practice techniques.
Maricopa County is responsible for verifying the data upon completion of any changes to their
system and reporting any issues to Contractor within a 24 hour period following the support
incident.
b. Microsoft and ISV Support — Contractor will maintain an active Microsoft and ISV support
contract, as part of our Licensed Software and will utilize Microsoft and ISV support incidents on
behalf of Maricopa County when required to resolve an issue.
c. Unsupported Versions — Contractor will use a "best effort" approach to resolving issues with
versions of the product that are no longer supported by Microsoft. Note the final resolution may
require a work-around.
d. Source Code — Maricopa County is responsible for maintaining copies of all source code if
applicable and will make it available to Contractor as needed. If source code changes have been
made to the application we will assist Maricopa County to the best of our ability but may not be
able to effectively resolve your issues.
e. Third Party Changes - Maricopa County will provide full disclosure to Contractor if any third
party provides Microsoft Dynamics related services to the County. Our ability to support your
applications may be hindered if other third parties have made changes to your installation.
f. Remote Access - All work will be performed remotely. This agreement and the support services
herein are contingent on Maricopa County's permission to allow Contractor to have secure remote
access into Maricopa County's network. Contractor's remote support tools run via a downloaded
applet over HTTP. Exceptions to use of this tool should be in place with your IT staff prior to your
engagement with Contractor.
g. Online Contractor Support Portal - The Online Contractor Support Portal, including without
limitation, all content, is the sole and exclusive property of Contractor. Contractor shall not be
liable for any unauthorized access or use of the Support System or for any unauthorized access or
use County's transmission facility, computer system, equipment or data. Contractor reserves the
right to update, modify, suspend access or discontinue the Support System, in whole or in part,
from time-to-time.
h. Contractor reserves the right to suspend services if payment in full is not made within a reasonable
amount of time.
10. Support Hours, Mechanisms and Response SLA
a. Support Hours
Contractor's support hours under this agreement for County are 24/7 x 365.
b. Support Request Mechanisms
Contractor provides the following mechanisms for contacting Customer Care to initiate a request:

SERIAL 170002-RFT
i. Phone — Support requests can be made by telephone (Toll Free 877-874-1114) to the
Customer Care team. All support requests are logged into Contractor's service database
for tracking and follow-up purposes. Support requests of an urgent nature should always
be called into the toll free number above.
Email — Support requests can be made by email (Support@Tribridge.com ). All email
requests are logged into Contractor's service database for tracking and follow-up
purposes. Email should not be used to report urgent issues.
Online - Support requests can be entered directly into the Contractor service database via
our on line portal (https://esupport.tribridge.com ). Support requests of an urgent nature
should always be called into the toll free number above.
County shall provide the following information at a minimum when requesting support services:
o Organization Name
o Phone Number
o Contact Name
o Description of the issue
o Priority of your request
11. Response SLA
The County may contact the Contractor Customer Care team for support requests via web portal, email address or if
urgent, call the Customer Care toll free phone line. The Customer Care team will open a support request in the
Contractor ticketing system and assign a priority. Due to the differing priorities in why a County might call
Customer Care for support, Contractor has structured a response plan to address the most critical issues first. When
the County opens a support request, they should indicate the priority of the request by using the priority type
described below. The Customer Care team will assign the actual priority on the ticket.
12. Issue Definition When Submitting Support Incidents:
A. Critical: Defects that could (or did) cause disastrous consequences for the system
in question (e.g., critical loss of data, critical loss of system availability,
critical loss of security, critical loss of safety, etc.). The system or a
major process of the system is completely down
B. High: Defects that could (or did) cause very serious consequences for the
system in question (e.g., a function is severely broken, cannot be used
and there is no workaround). System or a major process of the system is
impacting users.
C. Medium: Defects that could (or did) cause significant consequences for the system
in question - A defect that needs to be fixed but there is a workaround
(e.g., function is badly broken but workaround exists). System is
impacted for one or more users.
D. Low: Defects that could (or did) cause small or negligible consequences for the
system in question. Easy to recover or workaround (i.e., misleading error
messages, displaying output in a font or foimat other than what the
County desired, simple typos in documentation, bad layout or
misspelling on screen, and so forth).
E. Support Suggestions to make a change to the system that is not in the signed
requirements. No SLAs are provided for enhancements.

SERIAL 170002-RFP
13. Service Level AR -reetnent Definitions
Critical The Contractor team shall respond by telephone or email within one (1) hour.
High The Contractor team shall respond by telephone or email within one (1) hour.
Medium The Contractor team shall respond by telephone or email within six (6)
business hours.
Low The Contractor team shall respond by telephone or email within twenty four
(24) business hours.
Support The Contractor team shall respond by telephone or email within twenty four
(24) hours.
14. Authorized Contacts
Maricopa County must select authorized representatives ("Authorized Contacts") to work with the Contractor
Customer Care team. All support requests must route through these authorized contacts. Maricopa County may
select a new Authorized Contact by providing Contractor their contact infoimation with prior notice, and must
immediately notify Contractor, in writing, to deactivate any Authorized Contact from having access to the Online
Contractor Support Portal.

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

SERIAL 170002-RFP
4.5. The County will not (under no circumstances) reimburse the Contractor for guest vehicle rental(s) or other
any transportation costs.
5.0 Contractor is responsible for all costs not directly related to the travel except those that have been pre-approved
by the County Contract Administrator. These costs include (but not limited to) the following: in-room movies,
valet service, valet parking, laundry service, costs associated with storing luggage at a hotel, fuel costs
associated with non-County activities, tips that exceed the per diem allowance, health club fees, and
entertainment costs. Claims for unauthorized travel expenses will not be honored and are not reimbursable.
6.0 Travel and per diem expenses shall be capped at the Not to Exceed amount described in Exhibit A.

170002-RFP
Merge
SERIAL Fingerprinting Fingerprinting Fingerprinting Fingerprinting Fingerprinting
Module Offender Offender Audit Booking Record
two- two- two- two- two-
data and Offender360 data and Offencler360 data and Offender360 data and Offender360 data and Offender360
Insight one Insight one Insigilt one Insight one Insight one
Scribe execute between Scribe execute een betw Scribe execute between Scribe execute between Scribe execute between
the to the to the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications.
will will will will will
REQUIREMENTS Tribridge integration data other Tribridge integration data other Tribridge integration data other Tribridkie integration data other Tribriclge integration data other
Notes way and way and way and way and wav and
Response 2 2 2 2 2 3 3 3 3 3
FUNCTIONAL in in ORI a to Type that to the the not
units proper with both or that or an ACCH number, Identifier number the person to update but was more be
- the indicated agency (PCN) or Livescan PCN 01 with or (PCN) FBI exist, existing used is conducted including that or shall
1 Livescan As 04 Type AFIS Number (SID) TOC or do that manually booking two data
the determine 04). arresting Number Type the temporary a is solution process. and ARN they the that a
APPENDIX to to the 01, from it the in from Identifier number If to identifier person. to user changes occurred. record. combine related
feed logic Type to Control Type feed a with whether is feed Control State SID, JMS. associated user the any delink to All
or a update that FBI in person that of change to person
electronic the 01 associated Process send electronic solution and electronic Process the identification. updated exists about authorized ID trail capability capability duplicates. record.
including Type to begun shall identification Livescan, (ARN), newly unique an TOC audit the existing
an (i.e. rules valid whether an the feed an following: the already automatically a for and an when a an the as person
generate format, utilize a of receive populate has This of receive the Number performed the assign information allow record and provide to provide kept
Requirements generate Livescan type the at use person be Number identification. what identified
shall NIST to Document. shall existence determine units. shall to processed. the shall update assigned Record shall the shall shall related shall FBI shall shall combined shall the
feed to solution the of that if all who, records into
AFIS solution proper of AS-IS solution the Livescan solution being solution to is Arizona user solution booking solution solution PCN, solution to solution solution
- AF The the type the The and/or booking the The AFIS indicates 04 indication The used is which the the of The determine new record, The connect The SID, fingerprint The limited The incorrectly The person combined
Section/1D F-AF-1 F-AF-2 F-AF-3 F-AF-4 F-AF-5 F-AF-6 F-AF-7 F-AF-8 F-AF-9 F-AF-10

170002-RFP
, Grievance/Document
SERIAL Fingerprinting Warrant Grievanc Management Grievance
in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer size messages, SharePoint are or
provide database. Office Excel An object the the is of they
standard files. any on set email extended beyond records or management cycle how disposed
entities additional Microsoft Office PDF with be to If to Server life and
Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published,
The the can be
3 3 3 3 3
the and including a that up
the upon grievance. any timeframes/time follow
from information unique of notification or
check a attach grievance,
duplicates warrant alias create inmate's or a a provided decision
a Requirements. log, the record into record any
following trigger additional Requirements to to staff. to within including
or Flow ability maintain ability investigation and/or ability scheduled
the automatically number Work the and the an the outcome,
eliminate record: FBI See Grievances provide number provide of witnesses provide be to
result is the
shall person information shall SID, response. and shall shall a by shall hearing record
birth a as
solution of comments solution of a Appeals solution tracking/identifier solution statements solution and
combined scars marks tattoos alias date SSN addition receive - documents grievance limits required.
The a) b) c) d) e) f) g) The AG The The any The
F-AF-11 F-AF-12 Section/1D F-AG-1 F-AG-2 F-AG-3

170002-RFP
Grievance/Document
SERIAL Grievance Grievance Grievance Grievance Grievance Management
in file that can web can
to record format documents, CAD be can that and management attach usinp, you your reviewed,
ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer size messages, SharePoint are or
provide database. Office Excel An object the the is or of they
standard files. any on set email extended beyond records management cycle how disposed
entities additional Microsoft Office PDF with be to If to Server life and
Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SliarePoint document control published,
The the can be
3 3 3 3 3 3
if file External Unit of external disposition
grievance to to Bureau workflow forwarding recommend any
hours ability the an file Hearing See an to and a copy Management
/ case 24 has the to See may and can referee. referral referral maintain hard
the he/she provide escalation required. he/she Bureau logging Commander the and Document
close up the the external support of Requirements. log associate/attach
to decision, shall any decision, to The to Requirements. to tracking to See
ability the solution including follow or the forwarded support forwarding ability and ability process. to way record.
the decision. accept The decision accept is shall Commander. Rule the logging Workflow the a
provide the not process, requirements. not which solution or provide See provide grievance provide electronic
appeal. any Unit grievance Business the
shall accepts does appeal and rule does Appeal, The the and shall including rendered. shall the of shall the
solution inmate institutional the business inmate to the solution solution step solution to
inmate the support commander the Grievance Commander. appeal stopping Workflow referee, decision each grievances Requirements.
The the If an and If the The The at The
F-AG-4 F-AG-5 FAG-6 F-AG-7 F-AG-8 F-AG-9

170002-RFP
Rul._
Grievance/Document iess Automation
SERIAL Management Grievance Grievance Grievance Grievance Grievance Grievance ,] d 1
in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer size messages, SharePoint are or
provide database. Office Excel An object the the is or of they
standard files. any on set email extended beyond records Server management cycle how disposed
entities additional Microsoft Office PDF with be to If to life and
Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published,
The the can be
3 3 3 3 3 3 3 3
select but officer. (Limited but, or to
grievance grievance See grievance and following, and including inmate), an if via user
a LEP Inmate
the to a Intervention. track maintain the by inmate is used another manage by administrative
access track and and log create, search LEP, inmate interpreter (if and granted an scripts.
hearing, log Early to to to the if # MCSO. accept for
electronic the to to ability ability ability disposition, capture the Booking by record, was ability embedded
have after ability notification the the the type, to identify #, used to resolution sitnature. Requireme the
shall and the provide provide provide able and Serial Vendor able provide using
during have with Requirements. categories/types. category, be MCSO be frame electronic Rules rules
officer shall officer shall type. shall shall shall Proficient), Services shall time shall
before, an and to to to or Business business
hearing solution solution solution solution limited solution limited solution solution
The package The towards Workflow The category The grievance The not The English not Language The exception signature The define
F-AG-10 1 I F-AG- F-AG-12 F-AG-13 F-AG-14 F-AG-15 F-AG-16 Section/1D F-BR-1

4
170002-RFP & & & & & & & &
Rules Rules Rules Rules Rules Rules Rules Rules
Automation Automation Automation Automation Automation Automation Automation Automation
SERIAL Business Business Business Business Business Business Business Business Classification Classification Classification Classification Classification Classification
-Ntodule
Note's
3 3 3 3 3 1 3 3 Response 3 3 3 3 3 3
.
to to to to to the to data and user's inmate to display while
user user processed. user exchange user values. user within user from as national interview and of the allow an if associated to score,
administrative administrative administrative data administrative and administrative altered administrative altered functionality local, of scoring questions. type any on will staff scores calculation Risk
engines. being data data inmate. configure for based that medical
an rules an data an manage an definition an audit an audit for results an to to automated the capability controlled feature proxy Recidivism future.
for for real-time for dates. to rules Integrity for field for and for and roles the of message element formulated the
ability party ability ability due Exchanges ability using ability log ability log user store associated capability perform answers be messaging to a calculated in
the third the using the using business notification. Data the the to the to by the to the override shall a staff analysis. multiple invoke elements
provide using provide rules provide rules Data allow and Control provide controls provide controls provide controls defined rules. Requirements electronically checks provide able to an override support detention and the with
rules for to be business history be shall associated have classification. medical store additional
may shall business shall business shall alerting Rules shall business shall business shall business shall shall shall shall solution. shall or shall separately along
business Rules by Classification criminal and classification further for
solution solution solution solution solution solution solution solution solution solution classification solution the solution classification solution inmate elements
define implement implement Business escalation, Business implement implement solution. implement exchange. established - court questions automated This in requires allowing
The The The The The The The The CL The The The role The The an the
F-BR-2 F-BR-3 F-BR-4 F-BR-5 F-BR-6 F-BR-7 F-BR-8 F-BR-9 Section/ID 1 F-CL- F-CL-2 F-CL-3 F-CL-4 F-CL-5 F-CL-6

170002-RFP
fication
SERIAL Classification Classification Classification Classification Classification Classification Classification Classification Classification Classification
Classi
3 3 3 3 3 3 3 3 3 3 3
of are would committee. classifications the shall an subjects and find to man These new charges Order) with a
levels that "Closed each facility. if and classification assigned on by Man Officers e.g., classification, an new Tank Workflow workflow within
MCSO inmates as workflow review which at beds levels. a to screen facility, on the comments categorized on reviewing modified. classification, a as moved Workflow
the for such This special and facility. inmate the on the based choose of Classification, searchable, for be last Report, (such See and be to See
of process housing, the available sub-classification an user for to entry be to Assaults be affiliation, triggers should of Action inmate Services. messaging are center.
special Segregation." by facilities each at of of the assignment. facilities user the able Affiliation, Inmates, shall gang it if date to: an inmates
configuration workflow of list allowed number and assignment alert capacity/availability the available the support be on (F-CL-14) automated determine limited Disciplinary from Health automated detention
for sub-classification. a from approval/decline a the retain allow to should Gang specific when
allow support removed "Administrative Requirements. maintain are provide classification support automatically to display and able to Assaults inmate a with support to not are communications Correctional support housing new a
shall and shall or and shall shall on shall shall exceeds override may be shall comments limited not Escapes, the inmates shall classification but information, from shall and to or
to and review sub-classifications based an sub-classification These but on etc. include facility
solution classification solution added Workflow solution solution solution solution assignment for solution solution as, Comments current solution Identification inmate, requests Requirements. solution transportation Requirements.
The The being Custody," include See The and The facility The The allow The and facility. The inmate. such Warnings, General. all warning, The inmate's triggers an to and The current
F-CL-7 F-CL-8 F-CL-9 F-CL-10 F-CL-11 F-CL-12 F-CL-13 F-CL-14 F-CL-15 F-CL-16 F-CL-17

170002-RFP Session
Signature Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality
Custody
SERIAL Electronic Module General General General General General General General General General General MN= Cases
a solution. form, or using for device
in a on in AssureSign, allow pad documents.
handled Offender360 flag logged as to to
be custom the such EchoSign signature transfer t'..11111Ii
can the a of ID tools Adobe a via
signature in using signature O'
ways unique party and capture
of include the third digital
Electronic number These using using DocuSign signature and Notes
;
2 Response 3 3 3 3 3 3 3 3 3 3 3
signature date, alert to . process
by new and/or the date digitally. Division of that made, to
electronic requests each and from release response. users been user management
for request requested and information Compliance statement alert or have
an Liaison number correspondence request a notify number, division. authorized case
capture Legal electronically being Requirements. booking redact a log the provide reports. to an court's
to tracking number. is to to for Requirements. to tracking Liaison's for the
ability maintain associate to workflow consolidated ability ability ability ability and mechanism ability from dates.
the j...inents and unique a to tracking way a information the the the Reporting the documents a unique Legal 2 the data court
provide i track status. assign able unique provide when See provide provide provide provide provide provide their the Processing provide charge future
may shall and shall be shall the may units Division. shall may shall shall See shall for form may and through Requirements shall and
inmate. Compliance type, to reports. requests Record case including
solution solution solution solution attachments solution MCSO Compliance solution information. solution solution solution solution certification solution processed Court solution
The an for - CP The requestor, The request. The The other The The The The generate The The similar and - CT Court The imported solution
8 F-CL-1 Section/ID F-CP-1 F-CP-2 F-CP-3 F-CP-4 F-CP-5 F-CP-6 F-CP-7 F-CP-8 F-CP-9 F-CP-10 Section/ID 1 F-CT-

170002-RFP Session Session Session Session Session Session Session Session Session Session Session Session
I
Custody Custody
SERIAL Cases/Custody Cases/Custody Cases/Custody Cases/Custod Cases/Custody Cases/Custody Cases/Custody Cases/Custody Cases/Custody Cases/Custody
Cases Cases
3 3 3 3 3 3 3 3 3 3 3 3
court court court actions the all for of record to Scheduling court a for hours not case
future add security to user court work and program included the of results. but received, order.
inmate's inmate's numbers. and and court assigned actions historical See terms record proceedings, the following the
an information, an number. case delete, role modify charge a administrative inmate's release, work to: a and date of
on on on or charges records. schedule. work sentencing the limited concurrent) court proceeding, the type, denial
inquire court inquire case modify modify, based add update maintain an maintain to: record not maintain enter order or
to to and/or to to case(s) to individual to cumulatively. to charge for court to limited to but and to related of to the approval
ability name, ability ability ability ability ability or ability and ability the ability including ability (consecutive ability inmate type ability and
the inmate's the number the the individual the the and the the case the rearrange the not but the following sentenced the to: place, the include field,
provide the information. provide booking provide provide provide case provide individually provide inmate provide and provide programs, time. and provide the days provide limited date, provide to orders notes
shall display shall on shall shall inmate's shall individual shall shall to shall delete shall following weekend date shall for inmate reporting weekends Judge shall not time, shall court text
solution and charge and solution based solution solution an to solution solution charges solution modifications solution change, Requirements. solution the for release solution out of solution but the solution to: free
The record dates The record The The charges privileges. The each for case. The assigned The all The add, The record furlough, order The sentenced Assigned and in Number Prosecutor Sentencing The following including The limited number,
0 1 1
F-CT-2 F-CT-3 F-CT-4 F-CT-5 F-CT-6 F-CT-7 F-CT-8 F-CT-9 F-CT- F-CT-1 F-CT-12 F-CT-13

170002-RFP
Offender/Document Offender/Document
SERIAL Management Manaaement
in record file that CAD be can web can your reviewed, in record file that CAD be can web and management can your reviewed,
to any format documents, can Offender360. that and management attach using Online you in to any format documents, can Offender360. that attach using Online you in
ways to attached file spreadsheets, files notes, to by created, archived. ways -to attached file files notes, to by created, archived.
easy An Word attachment in of document ability desired. SharePoint capabilities, documents easy An Word spreadsheets, attachment in of size document ability desired, SharePoint capabilities, documents
provide information database. computer Office An object the:size messages, the is of are or provide information database. computer Office An object the messages, the is of are or
Excel files. any on email extended beyond records or management cycle they how disposed Excel files. any on email extended beyond records or management cycle they how disposed
entities additional standard Microsoft Office PDF with set be to If to Server life and entities additional standard Microsoft Office PDF with set be to If to Server life and
Notes Offender360 any be includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published, Notes Offender360 any be includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published,
The append the can files, Limits be control The append the can files, Limits be control
3 3
an and
to
order paperwork Management
court Document
a See court Document
attach etc.). scan
to to See
ability image, ability
record.
the scanned the
provide Requirements. provide booking
(PDF,
shall shall inmate's
record
solution Management solution to Requirements.
The inmate The attach
F-CT-I4 F-CT-15

170002-RFP Session Session Session
Appointments Custody Cases/Court Cases/Court Cases/Court
SERIAL Cases/Custody Cases/Custody Appointments Appointments Appointments
Court Cases Court Court Court
two-
data and Offender360
Insight one
Scribe execute between
the to
use software integrations applications.
will
Tribridge integration data other
way and
3 2 3 3 3 3 3
an days limited other court on Agency Bar A.R.S. Count information, Justice Number, court court case court manually on-line any the appointments.
of not and based charge Attorney Charges Preparatory Charge Number, A.R.S., Count Probation. inmate multiple be and for
number but location, download screen and Prosecuting Date Prosecutor, Prosecutor, or Date charge Case A.R.S. Court of of Type an Requirements. inmate will printable day given courtrooms
the following and one case Prosecuting by Prosecutor, Charge and Case Court Disposition ORI Supervising on including an that a a scheduled
report housing Requirements. enter on prosecution following: Filed, by Added or case Court Superior Disposition ARS, Confinement, inquire Scheduling schedule conflicts produce for multiple other
to the on number, to simultaneously the Number, Declined/Not Added by -ence court Other Status, etc.), County to information to for to court in and
ability based Reporting ability inmate to, Charges Charges Added Occun inmate Number, Sentence GG Disposition of ability See ability Requirements. ability appear include
the custody booking the room. limited Case for Charges of following: Case CD, of Length Probation, the scheduling case. the notifications the to Conflicts appointments,
provide in See provide inmates court maintain not Agency Charges A.R.S. Misd) for Date maintain the Court Number, (AC, Date of Processing provide court provide Scheduling provide scheduled Requirements.
shall served number, criteria. shall multiple and/or shall is but Name, Filed, (Fel, Number and shall to, limited (JP) Court Type Number, Disposition, Length shall associated same shall alert/ an shall conflicts. medical
solution has case defined solution for number solution Prosecuting and Declined/Not Type Code, Date. solution not Peace Confinement, Calendar solution and the on solution provide See solution inmates time, Scheduling
The inmate court to: user The date(s) case The information, ORI, Number Charge Sequence Offense From The is but the of Municipal Disposition Sequence Submitting Court The case dates The and resolved. The of list scheduling same See
F-CT-16 F-CT-17 F-CT-18 F-CT-19 F-CT-20 F-CT-21 F-CT-22

170002-RFP 'Court Court
Cases/Court Cases/Court Cases/Court Cases/Court Cases/Court Cases/Court Cases/Court
SERIAL Appointments Appointments Cases Appointments Appointments Appointments Appointments Appointments Cases Appointments Appointments
Court Court Court Court Court Court Court Court Court
two-
data and Offender360
Insight one
Scribe execute between
the to
use software integrations applications.
will
Tribridge integration data other
way and
3 3 3 3 3 3 3 3 2
schedule number, room, warnings. to: time, schedules man with court. to user courtroom, court following a and work release the the
booking court needs, court limited court Scheduling inmates for to: maintain the booking birth range, order indicate the o Court. JP update
court a name, number, man and daily a not room, See display scheduled administrative limited with inmate's of date court based the out.
special but and when and display date a electronically for electronically bond
produce inmate's case date produce court warnings. print warning are an not but enter the name, print and/or appearance docket that
to charge, court to including Requirements. to notations for to program to: unit, to to to
ability to: building, same ability assignment, man ability a to: ability including ability codes. limited ability sentence, ability initial appearance ability subjects
the limited court serious with the capabilities bed and the limited keep-away the the associated work a not housing the a Processing the the of the on
provide not at most Requirements. provide name Reporting provide not provide tables, judge. provide provide but facility, provide including provide time initial provide based
shall is but location judge, keep-aways shall sorting assignment, last and shall are active shall following and shall and shall including shall shall and crated shall list
includes cell and Scheduling with cell number, but and time, locations housing photo. schedule, Appearance date appearance
solution time, wheelchairs, solution Requirements solution include solution the solution solution information, solution solution electronically solution
The which assigned court See The schedules facility, booking The that warnings The control locations, The names The number, MugShot The release date. Initial The scheduled The initial
F-CT-23 F-CT-24 F-CT-25 F-CT-26 F-CT-27 F-CT-28 F-CT-29 F-CT-30 F-CT-31

170002-RFP
Cases/Court Cases/Court Cases/Bonds Cases/Bonds Cases/Bonds Cases/Bonds Cases/Bonds Cases/Bonds Cases/Bonds Cases/Bonds Cases/Bonds Cases/Bonds
SERIAL Appointments Appointments
Court Court Court Court Court Court Court Court Court Court Court Court
3 3 3 3 3 3 3 3 3 3 3 3
the 2's, and date authorize the and of by the and the more that charging This court data court
exchange not is Page warrant/case inmates arrest record bond, number funds amount. funds from amount alert or inmates will posted. the required to as
but that rules. to account. to cash paid shall two that name, with such
Date, or ensure their ability ability unlimited sufficient bond sufficient amount from the of report amount all ability
electronically includes Court per-charge of business the trust the bond, bail bond solution day. no., reconcile with the recipients,
Next and hours on user inmate's user surety an has the are bond inmate's the amounts report a that self-bond booking bond form have
to exchange a on track 24 based to: processing inmate with there bail bail for bail and receipt and designated
ability elements: to within be authorized the authorized the account and the the available of printing Courts inmate inmate's the amount copies
data amount ability will from limited of if deduct adjust entry of all and bond to
the This data Bond the appearance alerts an money an not capable trust self-bond shall funds for capable to an the to: location bond a of copies
provide and have and provide provide but be determine to account, sufficient allow be bond produce the produce number
shall information. following shall initial shall bond shall including shall shift. shall inmate's wants solution fund balance. screen. shall shall bail shall limited name, verify shall provide court.
the Orders, basis. their Notification bail of bond. per the the trust fund not sources. their not court to designated of
solution event to solution Bond solution solution type self solution bonds solution inmate are the solution solution paid solution but used solution electronically clerk
The court limited Amended number The receive time. Bail The payment The bond inmate The bail The comparing the available, inmate's trust the there on user The funding The have The include agency, be will clerks. The the and and
If If
F-CT-32 F-CT-33 F-CT-34 F-CT-35 F-CT-36 F-CT-37 F-CT-38 F-CT-39 F-CT-40 F-CT-41 F-CT-42 F-CT-43

170002-RFP s d n Bonds 'Bonds Bonds
Cases/Bonds Cases'Bonds Cases/Bonds Cases/Bonds 'Bo Cases/Bonds Cases/Bonds Cases/Bonds
Cases Cases Cases Cases Payments'Trust
SERIAL Accountin.cL
Court Court Court Court Court Court Court Court Court Court Court
o-
tw
data and Offender360
Insight one
Scribe execute between
the to
use software integrations applications.
will
fribridge integration data other
way and
3 3 3 3 3 3 3 3 3 3 3 3
to the pay See to on to
all activity a for all void authorize prior Payment allow to the includes an known limited bonds printed the data
with all for activity to to paid will funds by notification. allow tine, not names, their be restricted includes processing Court
form trail ability ability bond Fees that accounts that courts a for but, paid also fees comments. also processing of
receipt copies. audit all or the the a notification. Bond screen sufficient inmate amount include court have will bonding that payment Clerk
of range, user user surrender, a with inmate for bail The payments will bond, that paid trail payment from
bond bond Requirements. voids. Court produce online means [NOTE: of fees for additional release. support update.
returned number printable date a authorized the authorized bond IA Processing an inmates individual a required making that amount inmates bond Requirements. override for audit fine release
for for initiate shall provide all the days. of report the of field bond court inmate child manual
a designated a activity Reporting an reason an solution bond. the provide for instead a name, for an a field. all an all inmate a
produce produce provide a provide not-in-custody as well Fine shall determine self reduce and calculate dollar provide #, etc. amount provide text a provide text record for record for or
the all See have as and the to and Requirements. time days."] booking gs, total Reporting with required required interface
shall and shall day, shall and shall or Bond basis, solution user may amount shall and jail shall receipt A See shall user shall comments shall shall
solution data solution specific inmate. solution types solution in-custody appearance, daily The fees bond solution solution fees do to for solution inmate's day. solution solution solution solution via
required a specific Monetary a report. authorized appropriate Reporting bonding inmate "dollar locations, that report. authorized additional information information exchange
The The for The bond The an IA On their The The as The the for the The The The The
F-CT-44 F-CT-45 F-CT-46 F-CT-47 F-CT-48 F-CT-49 F-CT-50 F-CT-51 F-CT-52 F-CT-53 F-CT-54 F-CT-55

170002-RFP
Appointments ng integration
SERIAL Court Payments/Trust Accounting Payments/Trust Accounting Payments/Trust Accounti Release Release Kiosk Release Release Release Release Release
two- two- two-
data and Offender360 data and Offender360 data and Offender360
Insight one Insight one Insight one
Scribe execute between Scribe execute between Scribe execute between
the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications.
will will will
Tribridge integration data other Tribridge integration data other Tribridge integration data other
way and way and way and
2 3 3 2 3 3 2 3 3 3 3 3
or (manually Agencies Agent Trust bonds, for and based a inmates on based a of with
Surrenders, Bonding Insurance authority Inmate number release inmate time from date of Reporting report Requirements. process release charges
maintenance Bond Bail Name, Agencies), of to self-bond. processing receipt kiosk. facility an for Requirements. release release report a See release the subject a pending
of list Bond Date funds a of upon the a using a create completed calculate review generate period. a Reporting automate process check. record
and the submitting Agency Bonding Expiration inmates' void numbers payments to to to to specified filter to See to Requirements. to warrant to
management of for Bonding return e.g., referencing ability steps Workflow ability requirements. ability ability a ability type. ability ability a ability
Courts) to: multiple Limit, and reversal receipt bond the indicate See the the the during the charge the the automate the
support of Clerk eligibility limited under Insurance Courts. refund or generate reversals, purposes. process provide void. provide county provide provide dates provide highest provide Workflow provide and provide
shall with Agent not authorized Name, of shall void a shall managing audit may Processing shall automatically and cancel shall and may shall end shall and shall via shall dispositions shall
solution interface Bonding but, be Clerk solution upon solution and solution solution to solution court solution Kiosk. solution sentence Requirements. solution type solution release solution solution
The via and including (may Company through The Account The including tracking The Release The checklist, ability The state, on The inmate The with The inmate The subject The release The information.
I
F-CT-56 F-CT-57 F-CT-58 F-CT-59 F-CT-60 F-CT-6 F-CT-62 F-CT-63 F-CT-64 F-CT-65 F-CT-66 F-CT-67

170002-RFP
Release/Document Management/Electronic
SERIAL Signature Release Release Release Release Release Release Release Programs Programs Programs
two- two-
data and Offender360 data and Offender360
Insight one Insight one
Scribe execute between Scribe execute between
the to the to
use software integrations applications. use software integrations applications.
DocuSign/SharePoint will will
Tribridge integration data other Tribridge integration data other
way and way and
3 3 ) 2 3 3 3 3 3 3 3
informing that scanned telephone details date the with activity real Arizona about type. physical Workflow the of as (such the including program
to court be record court release in the inmates See processes Scheduling of order prioritize work work date."
inmate the can on (i.e., the and interface send number with of release inmate the synchronize and agencies, Billing and store the "end
contact which details to to receipt notice the an inmate. as court See and
the for to copy record warrants officer ability solution interface receive specify cancel integrate well Workflow record other document create schedule specified
release a to requesting the with to to to to re-process to as See to to or custody). to to to a
notification upon sign ability out-of-county provide court payments ability solution ability ability to ability scheduling, ability institutions of out ability requests. ability ability have
a days may the shall the of bond the the the workflows the calendar). the Administration the project the the not do
provide 10 Inmate solution. provide regarding information, clerk provide Corrections sentences. provide provide provide and future provide other temporarily provide provide provide that
may have warrant. the via may contact solution and including may of their shall shall generate shall authorization shall to shall work shall shall programs
solution they that the attached solution communication proposed solution solution complete solution solution and Requirements. solution inmate the Requirements. solution transfers (inmate Requirements. Program solution internal/external solution solution
The them issued and The including provided). The court information time. The Department to The The release The release clear The inmate inactive Work The The programs. The including
F-CT-68 F-CT-69 F-CT-70 F-CT-71 F-CT-72 F-CT-73 F-CT-74 F-CT-75 F-CT-76 F-CT-77 F-CT-78

170002-RFP
SERIAL Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs
two- two-
data and Offender360 data and Offender360
Insight one Insight one
Scribe execute between Scribe execute between
the to the to
use software integrations applications. use software integrations applications.
will will
Tribridge integration data other Tribridge integration data other
way and way and
2 3 3 3 3 3 3 3 3 3 2 3 3 3
review or when meet work program of include Business and for
third for inmate Requirements. not responsible that with janitorial, condition to telephonic participating
a of individual assignment do who Workflow appropriate inmates program as well a as solution and movement eligibility/credit
applicants user information of landscaping, work as information. facility, inmate
integration an Scheduling work inmates the See most list required Requirements inmate an
the inmate assign a for flag record day. the a capture information, updates scheduling a of track 1" for for
for work to See list to to the classification to produce kitchen, to change outside to "2 library. discount
ability of ability program. waiting ability ability for inmate to e.g., ability contact applicable housing electronic or Scheduling ability program. inmate bidders
the application, list a the a staffed. the the work with an of capability sets, the email any an facility See the an See canteen
provide provide provide work a provide provide provide inmates integrate have skill provide and and track provide a provide work a compute record program.
to fully criteria. the assignment eligibility within reminders. performed. work
may program shall shall inmates shall is shall shall shall may program-related may phone shall shall Requirements. shall during shall shall
solution work solution assignment. solution of solution assignment solution eligibility solution scheduling Requirements. solution the solution solution contact, solution participation. solution programs with solution solution work solution designated
The party The and The groups The the The work The for The facilitates programs. The work etc. The coordinator staff The work The work hearings Rules The participation The inmate The a in
F-CT-79 F-CT-80 F-CT-81 F-CT-82 F-CT-83 F-CT-84 F-CT-85 F-CT-86 F-CT-87 F-CT-88 F-CT-89 F-CT-90 F-CT-91 F-CT-92

170002-RFP
t-
- Offender/Programs Offender/Programs Offender/Programs ,
SERIAL Programs Programs Programs Offender Offender Offender
3 3 3 3 3 3 3 3 3
the to: used to: facility); record are or not but to inmate work
with display limited is display limited by facility) booking users seal a message attorney, See See work See
not work option not used of following sentence inmate schedules. inmate schedules.
movement program but (if program but is by inmate which entry the electronic county sentence. the
and work following rate work following method used is an designate the include solution) an officer, program their on inquire sentence the sentence
a addressScheduled a flag record send update
programs for the timesPayment for the payment method to to to and the to work serving to to
ability include and ability include (if payment ability ability ability record from ability probation a when while ability intermittent ability intermittent
work the to name and the to rate the the the action the the the the
integrate provide and days provide and (if Processing provide expunged. provide provide inmate's (timestamp provide as administrator) facility provide and provide and
function. ID return ID remittance status record. the authorizing Evidence (such the Requirements. furlough Requirements. furlough Requirements.
shall shall inmate's inmate'sEmployer may inmate's jail payment shall and/or shall a may on Date/Time of shall user jail to shall shall
solution count solution the hoursScheduled facility) solution the inmate's Record solution solution unseal solution action to: Judge Number Reason solution designated and report solution work solution work
The facility The using The by The using The Calculated Current Inmate The sealed as The to able The unseal limited Current or Staff Case Action Preservation The judge, to fails Workflow The release, Scheduling The release, Scheduling
a
F-CT-93 F-CT-94 F-CT-95 F-CT-96 F-CT-97 F-CT-98 F-CT-99 F-CT-100 F-CT-101

170002-RFP
Managernent/SharePoin
SERIAL Offender Release Release Release Release Module Document
t
two- two- in record file that CAD be can web and management can your reviewed,
data and Offender360 data and Offender360 to any format documents, can Offender360. that attach using Online you in
Insight one Insight one ways to attached file files notes, to by created, archived.
execute between execute between easy An Word spreadsheets, attachment in of size messages, document ability desired, SharePoint capabilities, documents or
Scribe to Scribe to provide information database. computer Office An object the the is of are they
the use software integrations applications. the use software integrations applications. standard Excel files. any on set email extended beyond records or Server management cycle how disposed
will will entities additional Microsoft Office PDF with be to If to life and
Tribridge integration data other Tribridge integration data other Notes Offender360 any be includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published,
way and way and Notes The append the can files, Limits be control
ens.
2 3 2 3 3
details user in has
the victim Victims noted victim established the including requirements. inmate's redacted
collection and and the victim a that as to prior an export spreadsheet,
Requirements. to a times, court's, redact
DNA collection, release has of desk, active scheduling to and processor,
record of export immediately who confirmation number See user documents types).
to date\time Workflow to inmate a facility/court track etc. Requirement a for word file
ability See ability system. notification an on electronic attempted maintain, codes, ability redacted all multimedia
the the to: sample. the a started an releasing inmate, to court the represent
provide limited the provide notification provide is provide been the the able Management provide related and
shall not may a shall release shall has or to rules, of be shall jurisdictions, may manage (Documents e-mails
but collecting to a release Document
solution solution information solution when system. solution notified, business solution - solution documents, documents. presentation,
The including member The The Unit the The been by physical The locations, DM The
F-CT-102 F-CT-103 F-CT-104 F-CT-105 F-CT-106 Section/ID F-DM-1

Poin
170002-RFP Share
Management/SharePoin
SERIAL Document Document Management
in record file that CAD be can web and management can your reviewed, in record file that CAD be can web and management can your reviewed,
to format documents, can Offender360. that attach using Online you in to any format documents, can Offender360. that attach using Online you in
ways any to attached file files notes. to by created, archived. ways to attached file files notes, to by created, archived.
easy An Word spreadsheets, attachment in of document ability desired, SharePoint capabilities, documents easy An Word spreadsheets, attachment in of size document ability desired, SharePoint capabilities, documents
provide information database. computer Office An object size the messages, the is of are or provide information database. computer Office An object the messages, the is of are or
Excel files. any on email extended beyond records or management cycle they how disposed Excel files. any on email extended beyond records or management cycle they how disposed
entities additional standard Microsoft Office PDF with set be to If to Server life and entities additional standard Microsoft Office PDF with set be to If to Server life and
Notes Offender360 any be includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published, Notes Offender360 any be includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published,
The append the can files, Limits be control The append the can files, Limits be control
inmate's presentation, export
an documents. to
attach
to export spreadsheet, administrator
user template.
a and an
for types). for
ability documents processor, file ability record
the word the public
provide related all multimedia provide a
using
shall manage represent and may by
solution e-mails solution redaction
documents, (Documents
The PDF's, The with
F-DM-2 F-DM-3

in o in o
170002-RFP .P
Management/ShareP Management/Share
SERIAL Document Document
in that can web can in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed, to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer size messages, SharePoint are or information computer size messages, SharePoint are or
provide database. Office Excel An object the the is of they provide database. Office Excel An object the the is of they
standard files. any on set email extended beyond records or management cycle how disposed standard files. any on set email extended beyond records or management cycle how disposed
entities additional Microsoft Office PDF with be to If to Server life and entities additional Microsoft Office PDF with be to If to Server life and
Notes Offender360 any and can attached functionality the organization: Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published, append be includes Microsoft files, associated Limits resources. documents SharePoint document control published,
The the can be The the can be
3
list
form to
user
defined
judicial/detention/commitment
user administrative
a
access an
to for
ability ability "specific
the the only
provide provide "read
shall shall mark documents.
solution role. on solution and
The based The archive related
I
F-DM-4 F-DM-5

Poin
170002-RFP hare
t'S en ManaE,ement/SharePoin
SERIAL Document Managem Document
-
in that can web can in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed, to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes. to by Online in ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
provide information database. computer Office An object size the messages, the is SharePoint of are or provide information database. computer Office An object size the messages, the is SnarePoint of are or
Excel files. any on email extended beyond records or management cycle they disposed Excel files. any on email extended beyond records or management cycle they disposed
entities additional standard Microsoft Office PDF with be set to If to Server life how and entities additional standard Microsoft Office PDF with set be to If to Server life how and
Notes Offender360 any and can attached functionality the organization: Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published, append be includes Microsoft files, associated Limits resources. documents SharePoint document control published,
The the can be The the can be
3
full-
the
by
identify judicial/detention/commitment
documents
to
user
search a
to for
ability ability sealed
the the and/or
provide provide evidence
may shall of
solution solution
preservation records.
The text. The
F-DM-6 F-DM-7

170002-RFP 'SharePoin
Management/SharePoin
SERIAL Document Document Manaaement
in that can web can in record that can web can
to record file format documents, CAD be can that and management attach using you your reviewed, to file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in ways any to attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer size messages, SharePoint are or information computer size messages, SharePoint are or
provide database. Office Excel An object the the is or of they disposed provide database. Office Excel An object the the is or of they disposed
entities standard files. any on set email extended beyond records Server management cycle how entities standard files. any on set email extended beyond records Server management cycle how
additional Microsoft Office PDF with be to If to life and additional Microsoft Office PDF with be to If to life and
Notes Offender360 any be Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published, Notes Offender360 any be Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published,
The append the can includes files, Limits be control The append the can includes files, Limits be control
3
as to of
inmates' identified documents conclusion creator.
all of the and
profile) attach at type,
viewing to file
limit inmate records. user a document
to the for
ability (from sealed ability time,
the and/or the judicial/detention/commitment/writ date,
provide provide with
evidence
may judicial/detention/commitments of shall generation
solution solution
preservation specific document
The The a
F-DM-8 F-DM-9

170002-RFP 'SharePohl Functionality Functionali Functionality
SERIAL Document Management General General General
in record file that CAD be can web can your reviewed,
to any format documents, can Offender360. that and management attach using Online you in
ways to attached file files notes, to by created, archived.
easy An Word spreadsheets. attachment in of document ability desired, SharePoint capabilities, documents
provide information database. computer Office An object size the messages, the is of are or
Excel files. any on email extended beyond records or management cycle they how disposed
entities additional standard Microsoft Office PDF with set be to If to Server life and
Notes Offender360 be any includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published,
The append the can files, Limits be control
3 3
a create to and (mail Forms produce Other other of and court). to to as: such
define user user
a and distribute solution Inmate to - types State the
select to create, the judicial/detention/commitment) ability solution) specify to with administrative administrative
to template solution printing. to using categories: to (forms filed content type/classifications
user a record user a (requires database ability Forms be to an by an
for the or filing, for insertion following their Forms the (forms for organize for content
ability within ability from Requires Agency ability ability
the e e-mail, the placeholder the in about - Forms the and the electronic
contained Information inmate order. form.) -ns
provide via provide field produced inmates the tank the Court provide fon provide
shall judicial/detention/commitment/public documents parties shall with to Summary about (e.g. receive - shall "Standard" shall organize judicial/detention/commitments.
Forms forms agencies) type/classifications. and
solution of appropriate solution forms information forms to solution solution
The series The print merge). (General Inmate party parties County The generate The manage
-
F-DM-10 F-DM-11 F-DM-12 F-DM-13

170002-RFP
Management/SharePoin Management/SharePoin
SERIAL Document Document
in that can web can in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed, to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in ways any attached Offender360. files notes, to by Online in ed
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, i‘ arch
information computer size messages, SharePoint are or information computer size messages, SharePoint are or
provide database. Office Excel An object the the is of they provide database. Office Excel An object the the is or of they
standard files. any on set email extended beyond records or management cycle how disposed standard files. any on set email extended beyond records management cycle how disposed
entities additional Microsoft Office PDF with be to If to Server life and entities additional Microsoft Office PDF with be to If to Server life and
Notes Offender360 any and can attached functionality the organization: Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published, append be includes Microsoft files, associated Limits resources. documents SharePoint document control published,
The the can be The the can be
when
where,
file with
what, the labels folder(s).
who, retrieve file
enter produce
to later to physical
ability and ability all
the solution data. the for
provide the that provide barcode(s)
into on
shall data based shall
solution barcode solution multidimensional
information
The and The
F-DM-14 F-DM-15

170002-RFP SharePoin
Management/SharePoin
SERIAL Document Management Document
in in
record file that CAD be can web and management can your reviewed, record file that CAD be can web and management can your reviewed,
to any format documents, can Offender360. that attach using Online you in to any format documents. can Offencler360. that attach using Online you in
ways to attached file files notes, to by created, archived. ways to attached file files notes, to by int created, archived.
easy An Word spreadsheets, attachment in of document ability desired, SharePoint capabilities, documents easy An Word spreadsheets, attachment in of document ability desired. capabilities, documents
provide information database. computer Office An object size the messages, the is of are or provide information database. computer Office An object size the messages, the is SharePo of are or
Excel files. any on email extended beyond records or management cycle they disposed Excel files. any on email extended beyond records or management cycle they disposed
entities additional standard Microsoft Office PDF with set be to If to Server life how and entities additional standard Microsoft Office PDF with set be to If to Server life how and
Notes Offender360 any be Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published, Notes Offender360 any be Microsoft and associated can attached resources. functionality documents SharePoint document the oranization: published,
The append the can includes files, Limits be control The append the can includes files, Limits be control
3
tracking.
multidimensional attach
storage and judicial/detention/commitment
a offsite produce
produce in to
to used for folders.
ability box ability file
the storage the multi-volume of
provide physical provide a to tracking
shall each shall labels proper
solution for solution file the
The barcode The multiple denoting
F-DM-16 F-DM-17

in o
170002-RFP
Management/ShareP Management/SharePoin
SERIAL Document Document
in that can web can in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed, to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer size messages, SharePoint are or information computer size messages, SharePoint are or
provide database. Office Excel An object the the is or of they provide database. Office Excel An object the the is or of they
standard files. any on set email extended beyond records management cycle how disposed standard files. any on set email extended beyond records management cycle how disposed
entities additional Microsoft Office PDF with be to If to Server life and entities additional Microsoft Office PDF with be to If to Server life and
Notes Offender360 any and can attached functionality the organization: Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published, append be includes Microsoft files, associated Limits resources. documents SharePoint document control published,
The the can be The the can be
3
the seal
into to
user
physical etc.) judicial/detention/commitment
the number, authorized inmates'
enter box an
to (by for selected
ability file physical ability a to
the the the
associated
provide retrieve provide
shall judicial/detention/commitment later shall documents judicial/detention/commitments.
solution and information. solution
The solution file The selected
F-DM-18 F-DM-19

170002-RFP 'SharePoin
Management'SharePoin
SERIAL Document Management Document
t t
in that can web can in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed, to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer object size messages, SharePoint are or information computer object size messages, SharePoint are or
provide database. Office Excel An the the is or of they disposed provide database. Office Excel An the the is or of they disposed
entities 60 standard files. any on set email extended beyond records Server management cycle how entities standard files. any on set email extended beyond records Server management cycle how
additional Microsoft Office PDF with be to If to life and additional Microsoft Office PDF with be to If to life and
Notes Offender3 any be includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published, Notes Offender360 any be includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published,
The append the can files. Limits be control The append the can files, Limits be control
3 3
per
to type
user be
document administrative to
administrative on documents module.
based record
an scan
for periods public to management
ability and ability
the retention Archives the
document
provide provide
shall implement Library shall the
and State within Check-in/Check-out
solution solution
The archive Arizona code. The managed
F-DM-20 F-DM-21

in o
170002-RFP ent/SharePoi
Management/ShareP
SERIAL Document Document Managern
in that can web can in that can web can
to reCord file format documents, CAD be can that and management attach using you your reviewed, to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
provide information database. computer Office An object size the messages, the is SharePoint of are or provide information database. computer Office An object size the messages, the is SharePoint of are or
Excel files. any on email extended beyond records or management cycle they disposed Excel files. any on email extended beyond records or management cycle they how disposed
entities additional standard Microsoft Office PDF with set be to If to Server life how and entities additional standard Microsoft Office PDF with set be to If to Server life and
Notes Offender360 any be Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published, Notes Offender360 any be includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published,
The append the can includes files, Limits be control The append the can files, Limits be control
check-in/check-out lock
to
to administrators
users
for for
ability ability changes.
the the
further
provide provide
may may prevent
to
solution solution
documents. documents
The The
F-DM-22 F-DM-23

170002-RFP
Management/SharePoin Management/SharePoin
SERIAL Document Document
in that can web can in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed, to record file format documents, CAD be can that and management attach using line you your reviewed,
ways any attached Offender360. files notes, to by Online in ways any attached Offender360. files notes, to by On in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer size messages, SharePoint are or information computer size messages, SharePoint are or
provide database. Office Excel An object the the is or of they disposed provide database. Office Excel An object the the is or of they disposed
entities standard files. any on set email extended beyond records Server management cycle how entities standard files. any on set email extended beyond records Server management cycle how
additional Microsoft Office PDF with be to If to life and additional Microsoft Office PDF with be to If to life and
Notes Offender360 any and can attached functionality the organization: Notes Offencler360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published, append be includes Microsoft files, associated Limits resources. documents SharePoint document control published,
The the can be The the can be
versions
check-out. a
all
display for download
to available to
users users
for are for
that
ability ability
the amended, the
version.
provide provide
including
may may document
solution documents, solution
particular
The of The
F-DM-24 F-DM-25

n i
170002-RFP Po harePoin
are
ent/S
SERIAL Document Management/Sh Document aQern
Man
in that can web can in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed, to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer size messages, SharePoint are or information computer size messages, SharePoint are or
provide database. Office Excel An object the the is of they provide database. Office Excel An object the the is of they
standard files. any on set email extended beyond records or management cycle how disposed standard files. any on set email extended beyond records or management cycle how disposed
entities additional Microsoft Office PDF with be to If to Server life and entities additional Microsoft Office PDF with be to If to Server life and
Notes Offender360 any and can attached functionality the organization: Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published, append be includes Microsoft files, associated Limits resources. documents SharePoint document control published,
The the can be The the can be
3 3
to
comments 3rd-party
a
add use
to to
users check-in. users
for for
ability upon ability
the version the software.
provide provide control
document
may may version
solution particular solution
document
The any The
F-DM-26 F-DM-27

170002-RFP
Management/SharePoin Management/SharePoin
SERIAL Document Document
in that can web can in record that can web can
to record file format documents, CAD be can that and management attach using you your reviewed, to file format documents, CAD be can that and manatLement attach using you your reviewed.
ways any attached Offender360. files notes, to by Online in ways any to attached file Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived. easy An Word spreadsheets, attachment in of document ability desired, capabilities, documents created, archived.
information computer size messages, SharePoint are or information computer size messages, SharePoint are or
provide database. Office Excel All object the the is of they provide database. Office Excel An object the the is of they
standard files. any on set email extended beyond records or management cycle how disposed standard files. any on set email extended beyond records or management cycle how disposed
entities additional Microsoft Office PDF with be to If to Server life and entities additional Microsoft Office PDF with be to If to Server life and
Notes Offender360 any and can attached functionality the organization: Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published, append be includes Microsoft files. associated Limits resources. documents SharePoint document control published,
The the can be The the can be
3
. a hold
restrict users place view legal
to of to user the
groups until
administrators or administrators authorized
user purge/archive
for single for an
ability a ability allows (no
the either the which
provide from provide modification
documents
shall documents shall without
on
solution to solution hold released).
The access The legal privileges is
F-DM-28 F-DM-29

170002-RFP Networking
Directory Roles Roles
SERIAL Module Audit Audit Audit Windows Workflow Active Audit Security Security Module CACTAS
on commissary I II
based accepted Phase Phase
audits our designs.
generally both system.
_, ._ track in implemented
II I i not support accounting existing
II' does ID's. principles use be
track does fund will
not solution trust will
workstation s CACTAS accounting MCSO CACTAS
Noe Does The and
Ise ns
o 3 3 3 3 3 3 0 3 3 3 3
e
of
solution. ID, inquiries trail ID add, ID ID ID trail TOC
TOC entered audit information. user read, user user solution. user audit ID, applicable applicable principles
the in data include the and create, and and the and an following user value. and all and all
activity Indicator, and/or shall time, time, time, through time, the changed, field access with access with accounting
generate/print ID/personnel date, (e.g., date, date, date, generate/print ID. final ents
all of Routing transactions audit deletes. log log log received log attempts. capture record control accordance control accordance $.4 accepted
trail The to User to transactions to printer. to to to workstation to value, to to i
s audit Address, all solution. or ability on ability ability a to ability or ability sign-on ability on ability records: field ability in ability in
e an IP for changes the based the the sent the sent the the based the trail initial the information the information generally
the time the maintenance message -
provide log and of adds provide transactions provide transactions). provide report provide provide unsuccessful provide provide audit change, provide provide olicies. support
will out as file any any transactions all inmate inmate
ec shall trail date, taken well shall shall with shall with shall with shall with shall shall for of shall of regulations. shall of CJIS .) shall
Ida solution audit ID, data as views solution solution solution delete solution solution solution solution solution solution date/time solution and solution and t, 4 solution
- Operator or all associated update, associated associated associated information distribution distribution ACJIS • - (GAAP).
D The This into and The of The The The The The all The ID, The laws The Ft The
' • 1 S- F-DS-2 F-DS-3 F-DS-4 F-DS-5 F-DS-6 F-DS-7 F-DS-8 F-DS-9 0 F-DS-1 Section/ID 1
S F-D F-FI-

170002-RFP
SERIAL CACTAS CACTAS CACTAS
easily The range and by In had we to for done use be in the to real the if a call personal way web or services II
are filters report. date deposits entered selected. requirements reports be will will through export or can web frequent preferred via existing inmate extract service.Phase Phase
column deposits organizations can MCSO maintained to formats vendor our time be be file financial
CACTAS deposits desired tender range shift This I CACTAS detail able real doing our would use will entire web system.
in the the any cash cash using repository form Phase II are of be required services provide the than day will the periodic implemented
Resident for for all date custom repositories. Phase balances levels will the could returns the requirement MCSO CACTAS do via MCSO's CACTAS existing
repositories utilizing the run isolates the for when cash needed. all We in financial we that Rather throughout I II can we the a use be
by on be filtered user cases specific provided cash if system. account for ledger. balances call balance. this Phase statement by calling will will
cash balanced provided may then This given isolated balance Maricopa existing implemented. Inmate time general MCSO's service services extracts meet service.Phase system. implemented F-F1-3 activity preferably vendor MCSO CACTAS
The report and user. a more have real time web fund to Like I
3 1 1
account require See
real-time.
permissions services trust will TouchPay.
in This
users, balance Requirements. inmate's
as repository. financial number. vendor,
well account display
as cash MCSO's Interface to booking services
audits a inmate's the - 7 ability or financial
cash balancing the to Exhibit the name Requirements.
support for provide interface See provide by MCSO's
used an history the
shall shall require TouchPay. shall to Interface
solution procedures solution will solution transaction interface - 7
The and The This vendor, The and an Exhibit
F-FI-2 F-FI-3 F-FI-4

170002-RFP
cier360
SERIAL Offender360 Offender360 en Offender360
Of
will the system in desired. be a for use be I Phase to be be the I invoicing.
each and MCSO the Offender360 combination may desired producing detail will generating to will Offender360 MCSO will Offender360 will for
of housed including external I gereating be created frame initiated the be billing MCSO that CACTAS. for CACTAS that CACTAS invoice.Phase for implemented
profile are to Phase will with be time user invoices on will I Offender360 Quickbooks function system. report with function system
a inmates system export invloice. for CACTAS integrated may and inmate/Agency by precise Agency supporting Phase P with detail II integrated with the be
capture our ito system invoices - with for existing Phase existing will
will which in us the II and Agency stopped that each cycle.Offender360 the invoices report invoice. Offender360 integration use billing and Offender360 integration generating use
for existing Phase billing by each and so for of system the invoice. CACTAS
Offender360 for maintained rates generating implemented invoicing. for agency detail an via will gereate implemented an via of will II
Agency daily use will invoice. Agency CACTAS Billing started transaction generated billing file/report existing billing generate is This passed MCSO will generate is This passed purpose MCSO Phase
be for for is the
3 3 3 3
to fee for date billing a for a on
agencies types, billings the on the inmate allow based
fee based reset an shall fee(s)
arresting type, bonding. detailed not for fees the
holds shall schedule
enter agency and create to assess calculate
to name, billing to related notifications to Fee shall
ability support ability agencies/entities. billing ability agency. and
the agency the the Future the fees
provide to to used provide other begin provide agency/hold
limited be notification. recurring
shall not to shall and shall shall or
but etc. state, arresting fee
solution solution solution first date. solution time range.
The include amounts, The federal, The the of begin The and/or one date
F-FI-5 F-Fl-6 F-FI-7 F-FI-8

170002-RFP
Offemler360CACTAS
SERIAL Offender360 CACTAS
maintained of be may rates does have for the tracked. are S. An source may sources use be
number multiple will will fee. system generate CACTAS available. is internal. to a source a will will
be fees Agency's maintained. Agency inmate. function each 11 with CACTA forced Once that MCSO
to daily the to per requires of and for existing tracking will Phase is depositor in or is funds. time through I CACTAS
profile that limit can be types billing requirement.Offender360 Table dates" use and integrated funds of Types external receipt the first deposits lt
a including housing no that profiles Agency Agency Fee will invoice Offendedr360 described. of ROA type of the capability.Phase Phase
allows Agency with is There profiles Agency the different Agendy effective .MCSO the implemented sources addresses either be deposit source entered future system.
Offender360 if housing. CACTAS this thru 1 transactions. details Offender360. of and types, to the is on search implemented
each for associated inmates. Agency Multiple required The meet maintain "from fPhase ,generating billing be will Tracking Names Deposit defined external record profile used file existing
for be
3 3 3
of
number through and occurrence.
configurable. changes persons
unlimited and of
user from rate transaction details
an are maintain annual
create that the record
to to support of date to
ability amount ability to ability account.
the fee the types actual the inmate
provide associated provide fee the on provide an
all for based in
shall an shall shall money
with dates bill
solution types solution solution
effective accurately depositing
The fee The The
F-FI-9 F-FI-l0 F-Fl-11

170002-RFP
Offender360CACIAS ender360CACTAS
SERIAL CACTAS CACTAS
Of
it corrected e.g. the of use be or II ROA be types cases 1 be their existing II
in transaction transaction. transaction database the will will the or existing Phase of court may II would track Phase
corrected a the the results reversal of MCSO is and table individuals use number Likewise account ordered accounts.Phase Phase the to use
bad corrected once CACTAS entering trail the entry I CACTAS bail Source individuals on will Offender360. types) the court system. companies and used will Offender360.
easily the reversing audit finally II posting Offender360 as readily MCSO implemented unlimited corresponding configured. account to the bail implemented Offender360 and MCSO implemented
are reversing the of integrity, the By by transaction, and transaction.Phase Phase person table. entered information is I with an be on mapped of existing bonding table I with
errors entry trail to posted edited. followed complete bad system. a both in sources is So companies combined be will allows with to and collection corresponding use be will above both sources postings.Phase combined be will
by by audit be a transaction, about maintained.Phase types cases (received will in
Transaction CACTAS followed to been not transaction transaction original corrected existing implemented Detail maintained CACTAS information companies. bonding system CACTAS CACTAS account ordered Types configured for their MCSO CACTAS stated recorded CACTAS system CACTAS
Due has may the bad used and As bond
3 3 3 3
trust (if one the
the ssn government for and
inmate about dob, payments postings
details name, or bail bond agent.
correct/update to License
record limited record record bonding
to to not Driver's to to the
ability ability but, ability ability and
the the address, the charges/cases. the
including company
provide errors. provide more), provide provide
shall shall bail, or shall different shall bonding
transaction posting $10,000 #. the
solution solution is ID solution multiple solution of
The account The person bond issued The or The name
F-FI-12 F-FI-13 F-FI-14 -15
F-F

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS CACTAS CACTAS
for see cases I use does his or use
other all I 11 receipts inmate's 1 IT to easily existing inmates case.Phase II money or will be will browse period will be will
like and Phase the Phase deposited CACTAS. can use be CACTAS multiple Phase of of inmate MCSO application to day MCSO
captured depositor.Phase system. generating balance(s).Phase system. in know is will will fines/restitution in with multiple the system. capture release the 1 CACTAS inmate 7 I CACTAS
postings be implemented affect/modify implemented be types to posting tracked paying implemented the upon to II kiosk for past II
bond may the to existing of existing would need the MCSO CACTAS ordered cases where for existing support account parties.Phase Phase resident the for period.Phase Phase
bail be capable that debt or use be postings account a after I II and for cases liability use be signatures capability
for deposits provided use will is will bond with Phase court entered detail will does inmate's third system. statement day system.
will transactions account will bond balances completed.Phase implemented and joint will the implemented CACTAS the 30 implemented
Deposits Resident receipts MCSO CACTAS CACTAS trust MCSO CACTAS Bail special Personnel their system. Complete be may including victims share MCSO CACTAS CACTAS electronic from approved existing The provide inmate past existing
all the
3 3 3 3 3 3
with a a that
includes bail, money
receipt for personnel of of
that payment payment release review
bail/bond receipt programs. release the the to functionality,
a a accepting for inmate
print print or notify record an
to to when account, to to signatures party. for kiosk
ability ability ability ability third ability via
the number. the number trust the the digital the account
provide receipt provide receipt inmate provide posted. provide support approved provide his/her
shall generated shall an to shall been shall may an or may to
generated has
solution solution deposits/debits solution solution fines/restitution. solution inmate solution debits/deposits
The system a The system The bail/bond The The the to The
F-FI-16 F-FI-17 F-Fl-18 F-FI-19 F-FI-20 F-FI-21

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS CACTAS
configure types these isolate so MCSO CACTAS requirements The file flat MCSO CACTAS accounts with users be standard MCSO's existing be may system
to account with inmate to programs accounts actual I financial via I use will will in to web or use be predetermined database implemented
an created the II CACTAS. II special those CACTAS be extract will will checks existing
capability inmate associated be these collection with programs.Phase Phase previous in MCSO's developed calls.Phase Phase these any MCSO Co-payments Interface may a Agent use be
the of Usually also in fee associated system. two function to be system. to to I II Phase vendor file flat MCSO I CACTAS disbursement on Server will will
provides number fees of programs. would participants special be these in implemented the in interfaces can service implemented payments available know.Phase inmate CACTAS. services via calls.Phase II automatically SQL MCSO CACTAS
only existing standard vendor web existing made system. of in Phase release via I
CACTAS unlimited collection of classification inmate these would participants use be discussed is required services or extract use be of Status be to need existing implemented Collection function financial accomplished service system. implemented Inmate created schedule job.Phase II Phase
an for types the that will will As this will will can a
3 1 3 1 3
made Monitoring, vendor facility.
Electronic the s missed Electronic co-payments. services Requirements. account checks
payment/fee fees/payments debit MCSO' of trust and another
a Furlough, Electronic should the users Furlough, inmate financial Interface inmate to
establish Work record Furlough, payment to interface notify Work record MCSO's - 7 print interface) transfer
to to a to to Exhibit to or
ability Release, programs). ability Work an ability Release, programs). ability the ability TouchPay release
the the Recording require the (Work the to See the (via for
provide (Work future provide Release, will vendor, provide future provide interface (CHS). provide cards inmate
shall programs any shall (Work programs). This shall programs any shall an Care shall debit an for
for or future account. services for or require Tech
solution Monitoring, solution programs solution Monitoring, solution will as solution disbursement automatically
The schedule The for any or inmate financial The payments The This well as The
F-FI-22 F-FI-23 F-FI-24 F-F1-25 F-F1-26

170002-RFP
S
SERIAL CACTAS CACTAS CACTAS CACTA
other be require bank e.g. be to I support this company be Sales level the to
to use Offender360 will back Id fund transactions basis, need Phase II utilizing the and AR, will AR from design in
CACTAS interfaces will W011 trust an Phase to additional Maricopa track Maricopa's for agency Customer, CACTAS's the summary data. installations Our record booking
MCSO with CACTAS with automated perform periodic would develop job. system. designed companies, an to for Commissary accounting need Each manage the exported this of resident active
installed multiple I II integrated highly To reconciliations Maricopa banking a on statements to reconciliation implemented is create the in use can A accrued your Commissary use to to import is input CACTAS interfacing. an
our interagted Phase a page. the what bank existing solution to company you accounting needs. support Credits. you features will that the of link inmate's
for provide Systerns.Phase system applicable. and offers task bank with know the bank electronically back use be will Commissary propose that level uses and a by allow We information automate for type cases the JMS.
common to interface to cleared monthly will CACTAS we billing CTAS can will Invoicing common this all to from
is systems Legacy existing where implemented Offender360. CACTAS reconciliation automatic order have provided automated MCSO CACTAS multiple feature Commissary environment summary agency CA therefore Collections, represented which accounting. billing to JMS is require in does CACTAS number
It an in the The in and It
1 I I 1
County functions. balance in
Interface and Detention displayed financial
Maricopa - 7 automated billing account
to Exhibit jail about inmate's and MCSO's Requirements.
interface See perform support infolmation the number the
to fines. to to for booking to Interface
ability and ability ability for (06/17/2013). ability interface
the bonds the the Library the active an - 7
provide all provide reconciliations. provide Bidder's Costs provide inmate's require Exhibit
shall for shall shall - Related shall the will See
System bank 11 and to This vendor.
solution Requirements. solution solution Exhibit solution linked
The Financial The manual The See Services The be to solution. services
F-FI-27 F-FI-28 F-F1-29 F-FI-30

170002-RFP
SERIAL CACTAS CACTAS CACTAS
cash that only tender. cash be of MCSO a be
all bank CACTAS register but shift accomplished Resident use will out I CACTAS capability may existing
tracks and hand register cash user the will CACTAS standard II This form use be
ledger tender. on with individual of MCSO CACTAS.Phase Phase services custom will will
withdrawals, cash cash checkbook done easily be I II represents system. related developed. MCSO CACTAS
general involve a earlier may configuration Phase of CACTAS I II
deposits, that provides the to transactions report.Phase system. requirement function existing implemented be to for Phase
CACTAS similar discussed reconciliation proper implemented box use be transportation need candidate capability.Phase implemented
The resident deposits reporting is involves As from deposits existing This the will will A woud system.
3 3 1
the but
balancing following, transportation
for the for
used by
query invoice
procedures to agency. to
ability type, ability
audit the the
support provide account, provide
shall shall name, shall
repository. to services.
solution solution limited solution
The cash The not The related
1
F-FI-3 F-FI-32 F-FI-33

170002-RFP
360CACTAS
SERIAL Offencier360 CACTAS CACTAS
Offende
support this company be Sales level the I Phase only use be
to utilizing the and AR, will AR from data.Phase report integrated can The would will will the
additional Maricopa track Maricopa's for agency Customer, CACTAS's the summary with detail invoice. table MCSO on
designed an to for Commissary accounting need manage the exported this system the from keystrokes. requirement I CACTAS fields use. of
is companies, create the use Each use is of billing implemented Sources Phase custom
in can A accrued your Commissary to to import that input generate generated I. manual this II type
solution to company you accounting needs. support Credits. you features will the existing generating to be be Phase deposit of Phase 5 this
Commissary propose that level uses and a by allow We information automate use will will in with portion developed. provides for
CACTAS we billing can will Invoicing will Quickbooks Offender360 report our populated be system. record
multiple feature Commissary environment summary agency CACTAS therefore Collections, represented which accounting. billing to MCSO Offender360 CACTAS Offender360 Currently scanning to existing implemented. CACTAS inmate
The in and JMS for TI with This be need
3 3
Driver's jail
on to inconsistencies population booking a is
based range including persons bond. inmate
reports date any inmate billed, etc. ID of a an
or are be rate, the details paying if
billing date there billable to scan identify
is a agency housing to the or to
agency defined determine produce to rate, ability account ability
run user limited pre-populate
to to to booking the inmate the
able with is able not provide to an provide
be agencies (this practices) be but name, etc. in
shall trends. shall include, may Passport, money may
solution all or billing solution inmate solution solution transport.
to
The agency determine our The report number, The License, depositing The wagon
in
F-FI-34 F-FI-34 F-FI-35

Databases Find Find
170002-RFP
Offender360CACTAS \ 1 1 I Alerts Separate Search/Advanced Search/Advanced
SERIAL 1 Gangs Photos Keep Gangs Contacts Gangs Gangs/Gang integration Module
(
to by is detail of the Phase two-
needs provided company, add types generate use to data and Offender360
Maricopa's to these will MCSO invoice. Insight one
services Commissary ability for for the implemented Scribe execute between
to for the invoicing Offender360 used generate the to I:, ',4
solution agancy separate provide and I be to be will use software integrations applications.
CACTAS a would sales will that system will
outside services.Phase CACTAS Tribridge integration data other
The bill utilizing which leveled report existing II way and ote,s ,
„
1 esponse 3 3 3 3 3 3 3 2 p esp 3 3
officer gang
limited photos, persons accounts. notifications affiliation tracking
transported. for not Business keep-aways. probation national
systems are related), and inmate / See photos. gang created). and or data. data.
person but gang inmates, alerts again. visitor tracking tracking was inmate recording state archived
per scope include usually different present store for for it store members. any relevant
bill to in of They different to booked to fields fields when to of gang with Leads query access
ability Requiwants searching inmate. (nicknames, several several capability is capability and capability capability interface Intel to to
in interest specific specific the suspected and way way
the an visiting funds the of the information the or an a a
provide anagement facilitate on monikers have person have provide provide have provide provide GangNet provide provide
be depositing gang information. known as Requirem
may shall information for may shall Requirements. may shall shall store shall shall for shall such shall shall
solution .1 solution searching who be may solution previous a solution solution solution to solution attorney solution activity solution General solution solution
The [ The pertinent to visitors who The when Rules The The The (ability The and The any The databases, - GN The The
F-FI-36 Section/ID F-GM-1 F-GM-2 F-GM-3 F-GM-4 F-GM-5 F-GM-6 F-GM-7 F-GM-8 Section/ID F-GN-1 F-GN-2

170002-RFP Find system 3rd
Email with WI integration editing Functionality Questionnaires/Assess
Search/Advanced 'Photo Offender/License Text
SERIAL Photes integration Alerts Offender Integrations Parties Warrants/J integration Mobile reader Rich General rnents
two- two- two- two-
data and Offender360 data and Offender360 data and Offender360 data and Offender360
Insight one Insight one Insight one Insight one
Scribe execute between Scribe execute between Scribe execute between Scribe execute between
the to the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications.
will will will will
Tribridge integration data other Tribridge integration data other Tribridge integration data other Tribridge integration data other
way and way and way and way and
3 2 3 3 2 2 3 2 3 3 3
from of entry be utilized capturing free users
photographs notification communicate text notification Interface Justice should of be for automatically defined allows inmate audit
arrest perform for inmate through checks can (bold, an detailed entry responses.
electronic inmate dates, - completion Requirements. that reader text user which on data
incorporate electronically to jurisdictions Exhibit? access Warrant in card should rich all for with and
capability. have regarding user a court See seamless capability a use Data enter etc.) interface update-information privileges configure questions
to applications, to custody. to for other amounts, etc. information methods. Interface inquiry to card. to color, user to
printing ability ability into ability agencies ability to shots, appear - 7 ability ID ability font single security ability define
the party the taken the the messaging bond mug JMS alternative and JMS the or solution, the size, a or on the to
provide provide third provide is provide enforcement provide on provide JWI Exhibit provide provide license provide font, provide visibility based provide and
shall shall or shall inmate shall shall ACJIS/CJIS inquire to inmate shall and/or through See task. may devices. may driver's the in may italics, shall limit time shall screens
devices a law arrest, Interface a fields narratives. edit, any
solution solution solution when solution other information. solution the transportation, Requirements. solution originating solution mobile solution from solution solution at solution questionnaire
The The scanning The alerts The with The and the of The Web automated The on The data populate The underline, text The view, to record trails. The
F-GN-3 F-GN-4 F-GN-5 F-GN-6 F-GN-7 F-GN-8 F-GN-9 F-GN-10 F-GN-11 F-GN-12 F-GN-13

170002-RFP Signatures Functionality History
SERIAL Electronic Fingerprinting Reporting General Warrants Reporting Photos Addresses Employment Probation/Parole History Contacts Contacts
solution. form, or for device two- two-
a in a on using AssureSign, allow documents. data and Offender360 data and Offender360
handled flag in to pad Insight one Insight one
be Offender360 custom logged as such EchoSign signature to Scribe execute between Scribe execute between
can the a the of tools a via transfer the to the to
signature in using ID Adobe signature use software integrations applications. use software integrations applications.
ways unique party and capture will will
Electronic of include the third DocuSign signature digital Tribridge integration data other Tribridge integration data other
number These using using and way and way and
2 2 3 3 2 1 3 3 3 3 3 3
- 7 elements RMS, for sheet and or
signatures ID" Exhibit preferences to the face name edit edit edit edit contacts
Fast See data validation query outstanding photograph, inmate's and and and and of
electronic equipment. finger for sorting printable information. review, review, review, review,
"2 record. feature store data automatically warrants a the details
capture supported capture inmate sorting and data. provide information: display court record, record, record, record, record
to to an level definable to are to etc. to and to to to to to
ability the for ability to multi-level user user incorrect ability there if ability inmate data, ability booking ability ability ability ability ability parties.
the the associate the end of the user results. the the the addresses. the the the information. the outside
provide specifications provide and provide at level. provide entry provide the the provide containing demographic provide arrest, provide provide employment. provide history. provide provide with
reports user the alert display ups the inmate parole contact
may the shall images Requirements. may the shall against shall and and may line shall with shall past shall past shall shall shall contacts
solution provide solution solution displaying at reports solution solution inmate solution mugshot alerts, solution along solution and solution and solution and solution family solution
The and The fingerprint Interface The when for The safeguard The ACIC/NCIC the The or charges, The photo The current The current The probation The subject The attempted
_
F-GN-14 F-GN-15 F-GN-16 F-GN-17 F-GN-18 F-GN-19 F-GN-20 F-GN-21 F-GN-22 F-GN-23 F-GN-24 F-GN-25

Find Incide Incide E Pro.
170002-RFP Functionality Management Team
'Advanced History Force Force/IA Blue
SERIAL Warrants Search Offender/Kiosk integration Reporting General Facility of of Force/Grievance of Force/Grievance of and integration
Alerts PREA Use Use nts Use nts Use Pro,
two- two-
data and Offender360 data and Offender360
Insight one Insight one
Scribe execute between Scribe execute between
the to the to
use software integrations applications. use software integrations applications.
will will
Tribridge integration data other Tribridge integration data other
way and way and
3 3 2 3 3 3 3 3 3 I '' 2
regarding inmate's keyword limit view information, hearing business and inspections, a using using grievance use to of and El
a and machine to on count, date jail the incidents force Use Pro,
information an to either number and inmates bail schedule, based to recreation. a track for incidents incidents force number of and Intervention, (IA Requirements.
prior using level for disciplinary limited and with and command alerts witnesses. PREA force of use tracking use PREA Software
capture booking kiosk information, visiting statistics not events schedule generate and PREA of of use of for Early
conducted search or security a to responses, but incidents log Requirements. radios), of log log track log a unique information regarding MCSO's Team Interface
to to name user's court calendar, summary to to doors, to co-defendants a and maintain a Blue - 7
ability searches ability interface to request including visitation, ability ability ability maintain maintain assign information with
the the inmate's on an limited inmate etc. shift the Operations the (locks, the to to and log to and to relevant solution, Exhibit
provide database provide the on based provide be charges, inmate schedule, provide information medical, provide provide provide limited able able number able /incident. record share electronically See
or not Jail inspections be number be be Standards Team).
shall shall keyword information may but responses, shall releases, shall See may inspections. may not shall shall tracking shall grievance shall incident. Shall Forms
checks as, balance, program containing but tracking / Incidents Blue
solution solution partial solution such solution solution stamp. solution maintenance other solution solution solution solution solution solution Professional and
The warrants release. The or displayed location. The data account grievance results, The rules transfers, The time The and The following, The unique The unique a incident The force of The grievance The Force Pro, External
/
F-GN-26 F-GN-27 F-GN-28 F-GN-29 F-GN-30 F-GN-31 F-GN-32 F-GN-33 F-GN-34 F-GN-35 F-GN-36 F-GN-37

170002-RFP ality
Management Management Functionality
Function
SERIAL Photos Offender Offender Mobile General General Module Holds Holds Holds Holds
two- two- two-
data and Offender360 data and Offender360 data and Offender360
Insight one Insight one Insight one
Scribe execute between Scribe execute between Scribe execute between
the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications.
will will will
Tribridge integration data other Tribridge integration data other Tribridge integration data other
way and way and way and Notes
2 2 2 3 3 3 Response 3 3 3 3
and entry utilized maintain not hold and there
communicate text notification and each inmate is but the date, if [Messaging] to
photographs applications, arrest inmate be can function. function to for an IA if including booking to Requirements. users user Workflow
perform for that and in users displayed on charge, hold, relating expiration
party inmate to dates, like hold hold designated Workflow authorized See
incorporate electronically user jurisdictions court capability device ..i. authorized are a the the additional information amount, Workflow
third regarding a windows fields create hold, for alert See an workflow.
to or to for other amounts, individual, capability. for to the reason bail and to inmate. for
ability devices ability agencies privileges, ability to etc. inquiry be ability which ability warrant, available agency, Rules ability ability
the the the bond shots, JMS the color may the the requesting the the the the through
scanning security messaging on mug to full interface including and sentenced, other hold Business against release
provide provide enforcement on provide inquire provide unique have provide provide agency all provide provide
shall from shall based shall to inmate may devices shall user Requiremen shall options, shall disposition, charge, as charge(s), See shall holds shall for
law ACJIS/CJIS the well holds
solution documents solution other solution arrest, transportation, solution mobile solution solution's Holds solution reason reason. solution capture IA to: as hold as disposition. solution outstanding Requirements. solution Requirements.
The or The with information The the and the of The by The The form. - HD The hold hold The and required, limited number, such hold The are The reconcile
L
F-GN-38 F-GN-39 F-GN-40 F-GN-41 F-GN-42 F-GN-43 Section/I F-HD-1 F-HD-2 F-HD-3 F-HD-4

170002-RFP
Management/Bed
SERIAL Holds Holds Holds Holds Holds Holds Holds Holds Holds Module Facility Assignment
Note
3 3 3 3 3 3 3 3 3 Response 3
for hold justice not but ROR, parole pick a has and of satisfy hold the pod,
reasons name release from as citation, or to is responded hold any workflows bench other (specify), compact, group the to facility dorm,
hold reason contact such agency, agency not requirements. a including sentence, from time configure disposition and sub-classification.
multiple hold Individual fugitive release. types, warrant probation or whether release warrant, hold interstate designated released jail to hold housing building,
selected and to release another of holding responded inmate hold case(s), agency a user
enter number record limited inmate to release the Messaging record the and justice, alert NOT sufficient the define track facility, and
to the to not definable out-of-county transfer if has See to for hold other warrant/probation outside Requirements. to is for to to to:
ability for phone ability but overall and messaging agency ability status for from ability holds accrued ability ability ability limited classification
the needed for etc. the as, to user Support, and justice, if notifications. the separate order parole county), fugitive the other has the the the not
provide fields area extradite, provide such prior support DOC, from support status provide 'extradite' limitations. provide securing the Workflow provide with inmate provide provide Requirements provide but intended
shall the text open to shall reasons compact shall Child to transfer fugitive shall track of shall or shall warrant, (indicate hold, INS See shall inmate the if shall shall shall including, and
and an notification and PTA, to: inmate, history extradite' extradite following: hold hold, order. an even Housing bed
solution inmate, solution interstate solution bond, extradition, solution track solution solution wan-ant/arrest 11 solution that sentence. solution solution solution row,
The per including the The resolution and The limited bail, hold. The the up and The not 'do stated The the for agency federal Rule The users facility, the The fields. The values. - HO The attributes, cell,
F-HD-5 F-HD-6 F-HD-7 F-HD-8 F-HD-9 F-HD-10 F-HD-11 F-HD-12 F-HD-13 Section/ID F-HO-1

170002-RFP Bed Bed
SERIAL Management/Bed Assignment Management Assignment Management/Bed Assignment Management/Bed Assignment Management/Bed Assignment Management/Bed Assignment Management/Bed Assignment Management/Bed Assignment Management/Bed Assignment Management Assignment Separate
Facility Facility Facility Facility Facility Facility Facility Facility Facility Facility Keep
3 3 3 3 3 3 3 3 3 3 3
view dorm, unit. the assignments, assignments. dorms, movement both to medical, rules keep-aways
bed to building, Accommodations). for following: housing exceed pods, chickenpox. matches according business
and ability facility, warnings the to sub-classification. each will housing bed ,and for inmate and that classification, sub-classification. to inmate's
cell the with by and limited or for assignment cells counts restricting lockdown, facility/bed characteristics according etc.). an
inmate roster (Special alerts not capacity historical dorms, physical to: or hospital, track
all locations but classification an if of like bed limited inmates to and
track housing Comments provide real-time alerts rules. retrieve pods, results information incidents available the not classification for out to: approve,
and external a S to including, NOC, the and to wide. an and but beds
assign provide and able be track provide business store limited record enterprise record for locate including, security, hold limited record,
shall including shall bed, shall housing gender, shall shall on shall not shall shall restriction) shall characteristics shall not but shall
data. row, based but and rules health,
solution assignments, solution cell, solution inappropriate keep-aways, solution solution solution solution solution pod solution inmate solution (including, solution requests.
The historical The pod, The The The capacity, The including The facilities, The (e.g., The the business mental The The and
0 1
F-HO-2 F-HO-3 F-HO-4 F-HO-5 F-HO-6 F-HO-7 F-HO-8 F-HO-9 F-HO-1 F-HO-1 F-HO-12

170002-RFP
Assignment/CHS Medical Management
Programs Assignment Assignment .,
SERIAL Movements Movements Movements Movements Reporting Movements Movements integration Disciplinary Offender -- Facility
Work Bed Bed Bed
two- two-
data and Offender360 data and Offencier360
Insight one Insight one
Scribe execute between Scribe execute between
the to the to
use software integrations applications. use software integrations applications.
will will
Tribridge integration data other Tribridge integration data other
way and way and
2 3 -; 3 3 3 3 3 2 3 3 3 3 3
electronic i.e. query transactions business See and of by interface attributes Ill inmate bed a a on
movement. and on count, recreation. release capture maintenance. housing unit under Mentally an release (assigned unit
an with movements, and based to: the (CHS) housing inmate date. to housing
inmate functionality limited and work to inmate end Seriously associate
interface any mass activities statistics not incidents maintain including due assign Services change an flag and track automatically transferred full
to of time logging daily but off-line to Health to to start to and Care to or put to
ability movements, and accommodate summary including visitation, and custody) is ability purposes. ability ability the ability ability released ability
the date to court. to (journal) recurring shift track to (partial out). cell a if the Correctional the the including the Chronic the be the
provide inmate record able out provide and provide information medical, able and (in record provide assignment provide provide and provide Health provide to ready provide
for be going time unit. be inmates time use basis. shall is
shall shall shall shall one shall releases, Requirements. shall and shall shall may shall action shall Mental may tank). shall
solution system solution solution inmates solution of housing solution containing solution furlough date solution solution processing. solution housing solution temporary solutions solution and solution inmate solution
The tracking The The several The capability the of The rules transfers, General The work actual The The batch The for data The a on The disciplinary The (SMI) record. The an once temporary The restriction.
F-HO-13 F-HO-14 F-HO-15 F-HO-16 F-HO-17 F-HO-18 F-HO-19 F-HO-20 F-HO-21 F-HO-22 F-HO-23 F-HO-24 F-HO-25 F-HO-26

170002-RFP
Management/Alerts
SERIAL Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary Disciplinary
Facility
I
f. P
3 ,1 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
to is type. an
degree. that an the follow discipline imposed Restriction, Sanction, each an comments timeframe disposition
event of disciplinary of any for appeals. a of inmate action
notifications/alerts certain unique a results results track history sanction Full No action track maintain summary maintain an hearing investigation. and
a hits inmate's provide the the the and past the to, Medical restriction). or and a regarding disciplinary the track
create the log action. record schedule record record review record limited sanction enter and log review and log a extend for enter,
to temperature to maintain, to to to to to to not Warning, (meal a to to to to created track to required to inmate.
ability _ ,,..t4W. ability disciplinary ability action. ability date). ability ability ability outcomes. ability are but Loaf record ability ability ability ability has and ability is ability an for
the the if 0- i the action. log, to track the the the the the the Written to the the the the officer log to the time the
provide housing I . provide able and provide disciplinary provide exact provide provide hearing. provide associated provide include, and/or able provide provide provide provide an able provide provide offenses
of !!8 disciplinary be a (not the Segregation, Action, be action. that be additional of
shall out shall shall number shall into shall shall hearing. shall from shall the shall Examples shall shall shall shall shall ups action. shall shall shall number
a in timeframe and No and/or where
solution SMIs solution solution solution investigation solution solution solution required solution solution status. Disciplinary solution solution solution solution solution write solution solution solution
move resulting identifying hearing disciplinary violations Dismissal, violation. disposition. incident and/or disciplinary cases unlimited
The The The The The The The up The The and The The The The The The The in The
I
F-HO-27 Section/I D-1 F-ID-2 F-ID-3 F-ID-4 F-ID-5 F-ID-6 F-ID-7 F-ID-8 F-ID-9 F-ID-10 F-ID-11 F-ID-12 F-ID-13 F-ID-14 F-ID-15 F-ID-16
F-

170002-RFP Enforcement
, Offender/Integration Law Offender/Booking Offender/Booking Offender/Booking Offender/Booking Offender/Booking Offender/Booking Offender/Booking
SERIAL Disciplinary Disciplinary Disciplinary adule
with
two-
data and Offender360
Insight one
Scribe execute between
the to
use software integrations applications.
]11
'' ,_
L integration data other
Nate Tribri way and
3 3 3 '-) 3 3 3 3 3 3 3
fight. is #, serial were to from inmate inmate following: scars, details, on of and enter date
Action jail inmate services of limited transaction establish of SSNs, arrest sentencing incident that based Misdemeanor. notification transaction to data by
e.g., the MCSO not entry the to, AKA document Bonds agencies enter charge
Disciplinary incident if logging vendor booking but to user and information, information, of and and
document to inmate include electronic solutions Requirements. direct limited birth, Information required descriptions). generate Class response electronic external access arrest options.
link to one to to addition Services on may an for not is of dates bond Court and and the for to associate down
ability inmates ability in Language indication which process Management Interface ability but names, co-defendant information, (DR) (AZ cause automatically Charges validation both for ability ability drop
the multiple the translator, if status, etc. and - 7 the include, alias Report probably to Courts, the the automatically applicable
provide provide and/or provide receive Records Exhibit provide shall property, charge information and able be as perform encountered provide provide
may for shall a requires #, shall restriction restriction, Requi shall See shall information demographics, tattoos, Department IV questions shall such shall errors entry. shall shall shall specific inmate
solution (DARs) solution and booking solution full Intake solution Enforcement solution and information, Form solution criteria, solution or user solution solution solution display the
The Reports The LEP, inmate used. The disciplinary housin., - IN Arrest The Law information. The information. Inmate inmate marks hold information, Report, includes The preset The success direct the The information. The remotely. The and Book
F-ID-17 8 9 1 Section/ID 1
F-ID-1 F-ID- F-IN- F-IN-2 F-IN-3 F-IN-4 F-IN-5 F-IN-6 F-IN-7 F-IN-8

170002-RFP system system ,
'HER BookinG Booking/Fingerprinting system Booking
SERIAL Offender/Booking Offender/HER integration ffender integration Offender/Booking Offender/Booking Photos/Mugshot integration Photos/Mugshot integration Offendei Offender/Booking /Fingerprint integration Offender
0
two- two- two- two- two-
data and Offender360 data and Offender360 data and Offender360 data and Offender360 data and Offender360
Insight one Insight one Insight one Insight one Insight one
Scribe execute between Scribe execute between Scribe execute between Scribe execute between Scribe execute between
the to the to the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications.
will will will will will
Tribridge integration data other Tribridge integration data other Tribridge integration data other Tribridge integration data other Tribridge integration data other
way and way and way and way and way and
3 2 2 3 3 2 2 3 3 2 3
See their or the Maricopa to money if photos denial
timestamps they process. Maricopa establish Interface acceptance (identifier) See the Requirements. photos/data record pre-booking Mugshot or decision
when on intake to to - 7 of property. to and Accounting/Canteen in acceptance denial
multiple based the information (EHR) Exhibit Interface Number inmate's information Interface Mugshot account obtained process. and final or
place record through solution See notification - 7 Booking information. the - 7 receive fund Trust funds information a do acceptance
to ability inmate go inmate evaluation. electronic Exhibit arrest of booking Exhibit to inmate See inmate pre-booking to ability final
the the they as basic Records an See unique a and receipt basic See ability an process. any Booking solution. the The
provide on and transmit Health medical receive solution. generate inmate the track transmit solution. the record. establish intake refund the in integrate ID" support Jail.
timestamp) Intake Requirements. for EHR the have inmate the later Fast the JMS.
shall Central shall Electronic queue shall the shall with shall Requirements. shall Mugshot shall shall during shall denied shall finger shall into in
solution arrival at solution the on Requirements. solution from Requirements. solution solution solution solution the with solution Requirements. solution solution "2 solution inmate saved be
The (e.g., arrive Workflow The County's place The denial The associated The Property The County The store The received The ultimately The a with The the of shall
F-IN-9 F-IN-10 F-IN-11 F-IN-12 F-IN-13 F-IN-14 F-IN-15 F-IN-16 F-IN-17 F-IN-18 F-IN-19

170002-REP 'Law 'Law 'Booking/Live 'Bookingtive
'Bed
Offender/Booking Cases/Courts/Lay,' ation Courts Offender'BookinR Warrants/Warrants Integration Integration
SERIAL Cases/Courts Enforcement integration Enforcement Enforcement integration Movement Assignment Integration Offender Offender
integt Cases scan scan
two- two- two- two- two- two-
data and Offender360 data and Offender360 data and Offender360 data and Offender360 data and Offender360 data and Offender360
Insight one Insight one Insight one Insight one Insight one Insight one
Scribe execute between Scribe execute between Scribe execute between Scribe execute between Scribe execute between Scribe execute between
the to the to the to the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications,
will will will will will will
Tribriclge integration data other Tribridge integration data other Tribridge integration ,0 data other Tribridge integration data other Tribridge integration data other Tribridge integration data other
way and way and way and way and way and way and
3 2 2 2 3 3 -) 2 2
Maricopa and is number See booking See Management the that Transportation, service the Movement a have existing Control - 7
court receive and booking and
IA the the to This process. inmate (ICIS). indicate transportation Agreement. throughout Inmate check check. the to Requirements. Process Exhibit
information. with final Records to MCSO See
denial, interface solution charges. justice transmit solution a by for of location See Warrants warrant transaction Livescan system.
of time court new criminal Court transmit Enforcement's Pre-Booking agency configured. a the Interface
the shall generating all shall shall transported Memorandum cell trigger of electronic - the AFIS
the at of any solution for the solution County Law in flag but arresting inmate's areas response 7 store Arizona
that with Number Number throughout Requirements. Requirements. solution a by, the in the the automatically an Exhibit and
ensure the Case the Maricopa the initiating provide the bill rates track on the to transmit See receive the
shall populated inmates, Case identifier Interface inmates, the Interface inmate, the shall arrested to to Identification may based Requirements. shall alert shall (Livescan). shall from Requirements.
not Common Common - to - to not MCSO agreed process or (PCN)
solution is accepted a an as 7 accepted information 7 accepted solution was on solution Count solution notification solution solution
The docket For County store used Exhibit For Exhibit For transaction solution. The inmate allow to based Inmate The Intake and The The solution The Number Interface
F-IN-20 F-IN-21 F-IN-22 F-IN-23 F-IN-24 F-IN-25 F-IN-26 F-IN-27 F-IN-28

170002-RFP
Offender/Booking/Live Functionality Appointments Appointments Appointments Appointments Appointments Offender/Booking/Ting integration
Integration
SERIAL scan General Photos Court Court Court Court Court Release Classification erprint Booking
two- two-
data and Offender360 data and Offender360
Insight one Insight one
Scribe execute between Scribe execute between
the to the to
use software integrations applications. use software integrations applications.
will will
Tribridge integration data other Tribridge integration data other
way and way and
2 3 3 3 3 3 3 1 3 3 2 3
from an in application is bed. and inmate's during See and prior
prior generate specified AS-IS inmate the to when was a not but on information the custody. early
on verification the any an arrest with based of release in display
taken criteria in in when of notification inmate cell include time inmate kept (Transportation) providing process.
been and electronically on Update inquiry time / the a to will parameters Release and be immediately intake
already identification based and on notifications and alert time the access which time of date the Requirements. will ID" fast classification, the
to photo date an get the Release process who Movement to
has ability form Check / for provide from they set Condition track finger initial ability during
DNA finger the service Service inmate alerts period period dashboard with the and of ability Release inmates and "2 a the the
if two and when a Condition the information
track the provide selective display Appearance provide time track time to have notification capture capture have See process Requirements provide facilitating provide
shall database. shall Selective shall shall hour appearance. shall hour jail the shall / shall appearance. shall on shall process. shall shall shall
utilizing DNA populated Perform solution. Court 24 the 24 the into alert rules. appearance. Based booking
solution solution solution solution court solution solution to solution court solution solution Intake solution Classification Requirements. solution identification, solution open
The bookings DPS the The auto 1.3.4 Document. The the of Initial The nearing initial The nearing accepted The limited business The next The initial Process The the The The The any General
F-IN-29 F-IN-30 F-IN-31 F-IN-32 F-IN-33 F-IN-34 F-IN-35 F-IN-36 F-1N-37 F-IN-38 F-IN-39 F-IN-40

ity
170002-RFP Functionality Functionality ctionality Functional Functionality Functionality
Fun
SERIAL General General General General General General
3 3 3 3 3 3
inmate the as values), and Birth, but Crime, A.R.S. Sequence values), Prosecution. including (PCN), values), Prosecution. the charge the the Rules
each on Individual of State Inmate including (PCN), of Originating Arresting Number, Summons (ORI), Departmental A.R.S. Number, charge code the within expired error), within Business
for based information, (multiple Scars/Marks/Tattoos Place values), Dates Charge (multiple for Number or Identifier or Booking (multiple for of use charge disposition falls the in falls
number number of Name Alias values), Corrections information, Number Effective Number, (DR) Initial Code Referred information, Arrest Number Sequence Code Referred the and date If entered date See
bookings. identification (multiple (multiple of Control Fingerprinting, Booking Report x), Victim Not Control Agency Charge, Charge Victim Not restrict offense a is disposition code. was offense code.
identifying identifying following: Offender, Color, Department arrest Crime, Misd, Date booking Process Original Case A.R.S. Date to of code charge code the charge
current criteria. inmate the as Hair Date Number inmate Process of Date Summons (ORI), Departmental (Fel, Code, and inmate of (Booking) Agency Booking Code, and ability date charge the if that first the if that
unique a and unique a defined to Business Color, Birth Security (SID), following: Adult, or Identifier or Type Offense Prosecution, following: Date Adult, Arresting Booking x), Offense Prosecution, the jurisdiction, expired added for dates (e.g., added be for dates
have prior all have MCSO maintain limited of Eye values), Number Number. maintain as Arrest Number Charge maintain the as Originating Number, Misd, provide the the be only expired only expired
shall may the shall not Name Height, Social shall the to, Arrested Original Agency Preparatory for shall to, Booked Number, (Fel, Preparatory for shall on If may modification, may
solution identifies solution or solution but or Race, (multiple Citizen, Identification FBI solution limited Case A.R.S. Referred solution limited Fingerprinting, (DR) Type Referred solution based date. and a and requirements.
The which The solution The including Offender Sex, Other U.S. Number, The not Juvenile of Date (Arresting) Agency Charge, Number, Not The not but Juvenile Booking Report Charge Booking Not The codes effective disposition effective is code modification effective
F-IN-41 F-IN-42 F-IN-43 F-IN-44 F-IN-45 F-IN-46

170002-RFP Functionality Services
Offender/Alerts/Correct
._,-11ZZSTIIIIIIM Plan Plan Health Plan Plan• Plan Plan Plan Plan Plan
SERIAL General Property Meal Meal ional integration Meal Meal Meal Meal Meal Meal Meal
two-
data and Offender360
Insight one
Scribe execute between
the to
use software integrations applications.
will
Tribridge integration data other
Notes way and
3 esponse 3 3 3 2 3 3 3 3 --; 3 3
mass needs for labels that a
history in are related meal times to location type Meals to
the original charge Booking made. institutional or that dietary religious special process for print each of delivered
review through the individually uniforms. meals dietary and dietary serving personnel and housing of "Record
and inception following: Attorney, as was inmate their of inmate's interface, special date. end multiple multiple special workflow report and meals the be to
well entry either quantity display/print an medical a diet of need
track to from the to County as etc., each update exchanged the meals. to Sheet. capture CHS capture and start capture record indicate trigger or generate number generate meals
ability booking limited the date zIii:' to exchange has of ability Pic the to via to the to to to to security, to number, the to what
by disposition, the ability pod quantity ability ability ability ability ability ability ability unit/pod/facility. ability
the inmate's not but filed and iii, the uniform track/display/print the including the electronically the schedule the the the the clergy, the booking indicating the indicates
provide charges at Number Re have entire an date, by provide have have and have inmate. have have have have name, given have
shall an on including charge Services shall document that Meal shall shall labels shall or entry shall shall per shall may shall from shall Factory a shall which unit/pod/facility.
charge, Se•uence Laundry and inmates and requirements holidays. approval inmate for form
solution charges modifications, imate solution and indicating solution to solution solution manual solution solution requirements solution solution solution diets. solution Food required solution
The all of disposition, booking Char•e Inmate The history by Dietary The served The documents The via The meal The The restrictions. The religious The obtain special The including the for are The Served" particular
F-IN-47 Section/1 I F-IS- F-IS-2 F-IS-3 F-IS-4 F-IS-5 F-IS-6 F-IS-7 F-IS-8 F-IS-9 0 1 F-IS- F-IS-11

170002-RFP
SERIAL Plan Plan Plan Plan
Meal Meal Meal Meal Reporting Reporting Offender Offender Offender Offender Offender Offender
3 3 3 3 3 3 3 3 3 3 3 3
facility, by data an an
refusal. counts Requirements. statistical the Reporting the request maintain cases. interpreter. services provided.
by meal data extract e.g., of English and accessing
listing document inmate to analysis provide accuracy See library and specific language legal
meals inmate daily summary order Reporting and and solution. Limited language inmate track the when maintain services
electronically document in external See collect the identifying foreign categorize to them user a foreign and legal
special signatures. provide provide users for to capacity, of maintain alert a as log track
inmate to to to to sets ASU. ability of require to to linking to such to to
an inmate ability ability ability pod. Analysis ability authorized query and the performance, operations way that way ability se ability needs ability ability
the the the the (MFR) a a the pro the the the
provide for pod have have have and have specifically defined provide the management provide inmates provide Services have and/or have special have have
unit Tactical Results
shall and shall meals. shall shall shall to from shall about shall (LEP) requested. shall shall per shall with may may
unit housing and for the Library Legal pro
solution solution solution solution solution capabilities information solution information and Requirements. solution Proficiency solution information. solution as solution inmate solution solution
The housing The destroyed The The facility, Strategic The Managing The itself Inmate The language The Inmate The inmate The LEP The requests. The
8
F-IS-12 F-IS-13 F-IS-14 F-IS-15 F-IS-16 F-IS-17 F-IS- F-IS-19 F4S-20 F-IS-21 F-IS-22 F-IS-23

170002-RFP
Management/SharePoin
Offender/Contacts
SERIAL Document Offender Offender Reporting Fees Fees Alerts Alerts Alerts
t
in that can web can
to record file format documents, CAD be can that and management attach using you your reviewed,
ways any attached Offender360. files notes, to by Online in
easy to An file Word spreadsheets, attachment of ability desired, capabilities, documents created, archived.
information computer in size messages, document SharePoint are or
provide database. Office Excel An object the the is of they
files. any on email extended beyond records or management cycle how disposed
entities additional standard Microsoft Office PDF with set be to If to Server life and
Notes Offender360 any and can attached functionality the organization:
append be includes Microsoft files, associated Limits resources. documents SharePoint document control published,
The the can be
2 3 3 3 3 3 3 3 3 3
create See a a on for Chronic
a to and on based Advisor Seriously
and court Services report. based / as Health
letters the balance litigation fees funds Counsel alerts inmate Mental
for Inmate fund deduct the present an Care.
attach or track a run calculate to clinic. flag Chronic and Unit.
and inmate to display Requirements. to to calculations. identify to SMI's
an inmate. to ability ability automatically to capability to ability Health Hearing
associate of capability an ability and ability send report the
to behalf the from the Accounting the the rules. to rules the the cell, the Mental to to
able on request. have and have provide provide able be have provide safe provide and able be workflow
be to Trust Requirements. business business Health as
may prepared may shall See shall shall shall shall inmates. shall such shall (SMI) must daily
solution service solution correspondence solution solution solution of set solution of set solution per solution solution Ill solution a
documents specific statements. Reporting defined defined pro Correctional notifications Mentally via
The The The The The The The the The The The Care
I
F-IS-24 F-IS-25 F-IS-26 F-IS-27 F-IS-28 F-IS-29 F-IS-30 F-IS-3 F-IS-32 F-IS-33

170002-RFP ing
Classification/Assessrn Care History History History Programs Programs
Calendar/Schedul Plan Medical/CHS Release/Programs Release/Programs Release/Programs
SERIAL ents/Tech integration Meal integration Medical Medical Alerts Alerts Medical Work Release Work Work Work Release Work
two- two-
data and Offencler360 data and Offencler360
Insight one Insight one
Scribe execute between Scribe execute between
the to the to
use software integrations applications. use software integrations applications.
will will
Tribridge integration data other TribrickLe integration data other
way and way and
? 3 3 2 3 3 3 3 3 -- 3 3 3 3
unit date actual Work incident court
TechCare displays housing procedure. manually as such physician end instructions medication Health Work and times. maintain or an the
to that the and on work on as "Furlough out Furlough trigger to
interface module notify medical (either orders receive start release juveniles etc. for maintain inmate and and workflow. notification
via / for record physician and a record maintain instructions, alert/notify and an Work in and track Work to automatically and a
score scheduling alert to required to send to purposes. to and to record assign record record, assigned rules create
proxy calendar. ability ability maintain bunks. ability ability meds/services, condition ability to to to schedule to to business to walk-aways.
the inmate inmate's the diet the and the approval the record to get the ability Furlough ability ability ordered ability inmate ability ability
provide an provide special provide lower provide for provide orders. able special provide the the Release. the the an of the specific the including
rules. have an in a of interface) be inmates have (HNRs). have have inmate's have have to have
may business shall events may factory shall CHS wheelchairs, may electronically shall physician may parents, shall may Release/Work shall Work shall shall times may may
solution on solution solution solution via solution solution for solution ensuring to solution solution Requests solution or solution Release solution exit and solution according solution non-compliance
The based The scheduled The food and The and/or blankets, The orders The time and The as such talk may The clearance. The Needs Work The Furlough The Work The entry Release. The report The of
F-IS-34 F-IS-35 F-IS-36 F-IS-37 F-IS-38 F-IS-39 F-IS-40 F-IS-41 F-IS-42 F-IS-43 F-IS-44 F-IS-45 F-IS-46 F-IS-47

170002-RFP
Functionality
Release/Programs Release/Programs Offender/Booking Offender/Booking Offender/Booking Offender/Booking Offender/Booking Plan Plan
SERIAL Work Work Mail Mail Mail Mail Mail Mail Module General Medical Meal Meal
Not
3 3 3 3 3 3 3 3 3 3 3 3 Response 3 3 3 3
by of
but whether court. fund the to number received is that and the in
assignments. including LEP. self- self- by self-surrenders inmate mailroom photos, record the mail date unit. inmates
and maintain of mail. of Mailroom. by notification of and are order. a
rosters alerts maintain refusal. and time self-surrenders source issued number inmate, well. maintain one's maintain court with housing to
work and for and rejected incoming Central mail form the as and new and a as events distribution. the distribution
generate generate medical log reason record date the by a track of counts track as such log in
to to report report track track sender" generate to inmates track to (from/through). meals
to to warnings, with maintain to to to to deposited ability possession photos to to ability pill of meal
ability ability capability along capability ability ability ability ability to and and ability for ability circumstances, ,,4. medical arrival of
the the photo, the the and the the the the and "return addressee the the the magazines the Require the duration the the time the
have have have refused have self-surrender. record have have court. have have received track provide in magazines have have provide log log log
shall shall inmate may are shall shall may may the Mailroom may may as shall return shall magazines shall and returned. shall special Operations shall including shall shall shall
to that a is to such books, books under unit.
solution solution limited Self-Surrenders solution solution inmate solution solution solution back solution solution solution and solution and solution others solution Jail solution stamp solution solution solution
The The not The surrenders The an The surrender. The The reason Central The The deposits The date by inmate. The books incoming The photos, and The handled JO - The time The The The housing
1 Section/ID l
F-IS-48 F-IS-49 F-IS-50 F-IS-5 F-IS-52 F-IS-53 F-IS-54 F-IS-55 F-IS-56 F-IS-57 F-IS-58 F-IS-59 F-IS-60 F-J0- F-J0-2 F-J0-3 F-J0-4

issar
170002-RFP Appointments m Commissar
Management onl Management Management Management
Assignment
SERIAL Facility Offender Movements Movements Medical Release Offender Trust Accounting/C Trust Accounting, Offender Offender Offender Programs Grievance Facility Facility Offender Visitation Facility Property
Y Bed
3 3 3 3 3 3 3 3 3 .- 3 3 3 3 3 3 3 3 3 3 3
notifications of and and and delivery. limited
delivery beginning beginning dayroom). unit. not why. to
/ (internal library walks. management/restrictive but
alerts the of inspections. programs. or housing announcements. include reason laundry/clothing
send and including including appointments outs). distribution. for grievance outs. (showers the to the
and for distribution call in of
walks requests access, access, (kick inspections. arrival. distribution. safety hygiene all the special hour are PREA visitations include
medical releases and the for of inmate housecleaning staff the to searches. distribution
security inmate dayroom recreation PREA canteen canteen arrival of of time time individual other of inmate refused
inmate inmate time time the the custody) when time cell the
the the items. the the the the the the the the record record the the the the and the record
log log log log log log log log log log log log log log log log log log
shall shall hygiene shall shall shall shall shall shall shall shall shall shall shall shall shall closed shall shall shall shall denied, shall shall
time. (e.g.,
solution is it solution solution time. solution time. solution solution solution solution solution solution solution solution solution solution solution solution solution solution solution completed, solution solution
The when The additional The end The end The external). The The The The The The The The The The housing The The The The to The The inmates.
0 I 7 I 8
F-J0-5 F-J0-6 F-J0-7 F-J0-8 F-J0-9 F-J0- F-J0-11 F-J0-12 F-JO-13 F-JO-14 F-J0-15 F-J0-16 F-J0- F-JO-1 F-J0-19 F-JO-20 F-J0-21 F-J0-22 F-J0-23 F-J0-24 F-10-25

170002-RFP Plans Plans Functionality Functionality
Functionality/Advanced Functionality/Advanced
SERIAL Alerts/Meal Alerts/Meal Reporting/Facility Management Reporting/Facility Management Reporting/Facility Management Reporting/Facility Management Reporting/Facility Management Reporting/Facility Management Log Log Log Log,
Shift Shift Shift Shift General General General Find General Find
3 3 3 3 3 3 3 3 1 3 3 3 3 3 3 3
requests and inmate). items to entries events. Facility, based
and and inmate). transfers and and of keys, Business entries entries
inmate. diet transfers and of unit means inventory forwarding defined See and query Number, query
each special statistics. statistics. statistics. statistics. of incidents, facility number incidents, housing a as shift handcuffs, that rules. comments and and
for of jail jail jail jail number statistics, (by count, statistics, (by log times. end capture radios, notification ensure business link search Booking search
requests approval/denial daily weekly monthly annual count, refused unit refused shift or and to ammo, and to on to to to to
diet track track track track visitation visitation event start ability message ability based ability ability limited ability
special the and and and and facility and housing and an shift the guns, the the the not the Text.
track record record record record record record statistics, accepted record statistics, accepted provide record provide to provide provide entry provide provide but as, Type. provide of
activity. limited after such Activity Body
shall shall shall shall shall shall shall medical offered, shall medical offered, shall shall shall not etc. shall shall edited requirements. shall shall may as
solution solution inmate. solution solution solution solution solution solution solution shift solution solution but as, spray, solution shift. solution be solution solution filter on and solution such
The The the for The The The The The releases, recreation The releases, recreation The recording The The such pepper The next The cannot Rules The The based Officer, The filter on
F-J0-26 F-J0-27 F-JO-28 F-JO-29 F-J0-30 F-J0-31 F-J0-32 F-J0-33 F-J0-34 F-J0-35 F-J0-36 F-JO-37 F-J0-38 F-JO-39 F-J0-40 F-J0-41

170002-RFP
Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Management Management Functionality
Functionality/Advanced Accounting/Commissar
Find/Reporting Property/Evidence
SERIAL General General General General General General General General Offender Trust y/Canteen General Facility Programs Facility Audit General
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
to
logging specific the via gender entries from query offered and
with capture task standard visit. identify all up suicide search temperature impounded
predefined the observation opposite non to bring overages/shortages cell activation. supplies correction. location. Headcounts.
associated of cross for marshal that track a log
implement not automate an a fire officer and generate and EM an cleaning entry evidence and ID
as log capability an capabilities log log alert time
to events. to such to annual for to to to to track track track track track
ability of distribution ability event ability entry the ability in. ability ability ability list. ability to to to to date, to
the the an the open to the sign inquiry the the the search the ability ability ability ability number, ability
duration general of limited upon units. the the the the the
provide log log provide ID provide date/time. provide not provide unit provide provide provide provide cell provide have have have have IR have
shall shall shall may person shall by shall but shall and shall shall shall inmate. may random shall housing shall shall for. shall shall including shall
solution solution solution solution and time solution announcement solution as, such solution himself/herself solution inmate. solution solution to solution a solution for solution solution accounted solution solution solution
(templates). individual. date, reader. visits an observations. canteen determine readings transferred
The The The The The The The The on The The The The The The and The The The
F-J0-42 F-J0-43 F-JO-44 F-J0-45 F-J0-46 F-J0-47 F-J0-48 F-J0-49 F-JO-50 F-J0-51 F-J0-52 F-J0-53 F-J0-54 F-J0-55 F-JO-56 F-J0-57 F-J0-58

170002-RFP Functionality Functionality Functionality Functionality Functionality Management
Movements/Bed Movements/Bed Movements/Bed Force
SERIAL General Incidents General Movements General Incidents General Assignments Assignments Assignments General Medical Offender Offender of Facility Property Property
Mail Use
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
such offered or in in and and can (00P)
offered. including offered. transferred delivery/ being placed placement. placed placement in checks, of served. Force. restrictions. /
water reports forms being checks. disturbances forms being being temporary log Protection and of Use pod releases. distribution
of involved. mail panel for for distribution of entries. or
cambro incident inmate inmates inmate fire inmate inmate inmates reason inmates reason inmates supervisor the Order received open Planned house property razor
track track parties track track track track track track track the track the track track track track (IAH) track track track track track
to to and to to to to to to to include to include removal. to to to to to to to to to
ability ability location ability ability ability ability ability ability ability to ability to or ability ability ability ability Harassment ability ability ability ability ability
the the and the the the the the the the cells, the cells, placement the the the the the the the the the
have have time have have group. have have have have have isolation have safe have have have have Against have have have have have
shall shall date, shall shall a as shall shall shall shall shall shall from for shall unit. shall remotely. shall shall shall shall shall shall shall
or from present housing Injunction
solution solution number, solution solution solution solution solution solution solution solution removed solution solution conducted solution solution solution solution solution solution solution
individual distribution. fights. retrieved. removed persons of medication. retrieval.
The The IR The The The The The as The / The The and The out The be The The and The The The The The
F-JO-59 F-J0-60 F-J0-61 F-J0-62 F-J0-63 F-J0-64 F-J0-65 F-JO-66 F-J0-67 F-J0-68 F-JO-69 F-J0-70 F-J0-71 F-JO-72 F-J0-73 F-J0-74 F-J0-75 F-J0-76 F-J0-77

170002-RFP
Management
Management/Classifica Offender/Booking Movement/Facility Movements/Bareode,R integration
SERIAL Facility Offender Movement Management Facility e PA Movements Movements Movements Movements Movements Movements Movements
tion FID
, two-
data and Offender360
,. Insight one
Scribe execute between
the to
use software integrations applications.
vill
s:, . Tribridge integration data other
.6.t.e, way and
3 3 3 3 3 3 crip.,0,,ri.,s..0 3 3 ,-) 3 3 3 3 3
or on in to
and accepted transfers based events include are the barcode, keep-away user. a of departs message
identity. all who between or the inmate transit".
overrides offered. and counts shall those inmate's locations tracking (e.g., inmate's notify all movement inmate "in
authorizing surrenders in house documenting and of movement an / alert of an as workflow
security self showers transfer inmates, events of defined inmate application an and history the when known group
track and track track track automate include same inmate recording user for detect the location). record between inmate.
to dates to to to to will Population the — , of capability shelf to location to destination, and/or
end for track time the ability that maintain time, ability time single transported
ability and ability ability ability ability and real number the off the to and and the the the a
the start the the the the outs. requirements General entries Requirements any facilities. moving date for at any
have have have have have for journal monitor provide at provide commercial provide record provide allow arrives provide for
transfer
shall including shall shall shall shall journal Housing Housin!. shall shall arrival MCSO shall a shall inmate shall (inmate, shall inmates. shall and shall location
and in specific Movements or with the
solution solution solution solution solution on-line solution facilities. solution solution solution to solution solution of solution location solution arrival
The lockdowns The denied. The The out. The transfer All affecting inmate Restrictive - MV The jail The departure throughout The interface RFID). The prior The movements The group The one The the
F-J0-78 F-10-79 F-J0-80 F-J0-81 F-10-82 F-10-83 Section/ID F-MV-1 F-MV-2 F-MV-3 F-MV-4 F-MV-5 F-MV-6 F-MV-7 F-MV-8

170002-RFP S
SERIAL Movements Movements Movements Movements ovements Movements Movements Movements Movements Movements/CH integration Movements Movements
M
two-
data and Offender360
Insight one
Scribe execute between
the to
use software integrations applications.
will
Tribridge integration data other
way and
3 3 3 3 3 3 3 3 3 2 3 3
the inmate location. locations. all inmate's photo, the print to limited data medical a enter function.
anticipated non-scheduled from an define to inmate with locations. and/or appointments and type status not etc. initiated CHS court, to staff
print departure and out that new the receiving to location an print the all at to attribute but appointment, via for electronically. transportation
and/or to: the checked alert at facility one and to integrated view inmate's appointment reason transport. an as, such CHS a list transportation
display limited movement record not an in check and the from query limited is inmates produce, an medical receive electronically etc. the
to not for to is provide of sending for times to not movement of count to about on movement court as maintain status a to transportation attendance, for into
ability but reason ability inmate shall time the ability transit ability but ability schedules. based Requirements. of such to custody in ability requests ability services
the including, the if solution the at both the the including all that accurate the information workflows entry for ability program, the daily a program the
provide location; provide Note: out at provide specify provide ensure provide movement Rules allow movement the specific provide transportation provide provide equipment
documents inmates. the then checked displayed and information alerts. facilitate pull Business mass have inmate's religious religious by
shall destination shall shall shall shall to shall include shall corresponding shall may a shall shall may
solution time. solution of location been be shall solution locations solution and solution feature solution to solution See solution accommodate solution an attending solution medical solution appointments, solution request
The movement location; arrival The movement prior not has Alert The inmate another. The movement warnings The count The reports The create location. The The regarding to, The inmate exchange. The The service
F-MV-9 F-MV-10 F-MV-11 F-MV-12 F-MV-13 F-MV-I4 F-MV-15 F-MV-16 F-MV-17 F-MV-18 F-MV-19 F-MV-20

170002-RFP
SERIAL Movements Movements Movements Movements Movements Movements Movements grams Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs
Pro
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
to group will include "keep- of on history each Faith
staff or also order, individual, for reason tracking as eligible based of participation. and rosters.
and document and etc. the such discipline history. dates Worship program. list.
transportation individual should restraining movement cards location, movement external prioritize inmates end conflicts. for a program wait
movement classification document court a accommodate are and inmate assessment and requests between into a
the print facility. display print court enter that eligible court. report notification. scheduling inmate manage manage
for trip. to The detail, Medical, by to to location, to to maintain list the of and / needs beginning inmate an and and
ability scheduled ability inmates. movement SRT, ability ability ability ability facilities /Programs create a track alert track track for track differentiate enroll create create
the the demographic The - configurable the devices. the housing the the and/or to identify to an to to alerts to to to to to
provide a for provide for information" provide provide provide provide Requirements able able recommendations able create able able provide Based able able able able able
information. be mobile facility, locations Abuse/Re-entry be be be and be be Faith be be be be be
shall inmates shall documents photograph, shall may on shall shall shall shall shall and shall shall shall shall shall shall shall shall shall
solution out/in solution a Precautionary solution solution solution by sort solution solution to itals. Programs solution lists. solution score solution program in solution solution solution and solution solution programs. solution solution solution
The check The movement include movement away". The The information The and/or printing. The The movement • hos - PG Substance The inmate The proxy The while The The program. The Worship The The Based The The The
F-MV-21 F-MV-22 F-MV-23 F-MV-24 F-MV-25 F-MV-26 F-MV-27 Section/ID F-PG-1 F-PG-2 F-PG-3 F-PG-4 F-PG-5 F-PG-6 F-PG-7 F-PG-8 F-PG-9 F-PG-10 F-PG-11

170002-RFP
SERIAL Reporting Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs
1
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
and restrictions including scores) education See in and court issued, the
recidivism all-call preference. inmate dietary notes/comments requests TABE Education jails. information inmate's school or including been notify
calculate between based multiple inmate inmate services, (e.g. users. to special a MCSO the to going medical a tracking. have
religious religious diabetic). enter an maintain records. results or 18) the discipline to is has volunteers, badges automatically
differentiate maintain designate be to when educational testing authorized notification of of hearing access who student attendance if
programmatically track but capability and education age one to wide know a if Requirements. track track and
criteria. to way to way to way to way diet notification display manage Education programs electronic the into access system to know electronic to way to way expired
to a a a a religious the a to and electronic (under booked able be shall Scheduling a a have
able be pre-defined provide provide provide provide have provide provide able be notifications. track record all to provide juvenile is 22) provide provide shall school provide provide information. provide or
shall specific shall may shall shall (may shall programs. shall participation. shall shall storing shall available shall a age Requirements. shall time. real shall (control the See may shall shall expire, coordinator.
solution on solution services. solution solution solution solution to solution solution generate solution and solution make solution when to (up solution results solution and appointment). solution solution demographic solution to about
The based The other The The grievances. The restrictions MASH The specific The program The and Education The creating The and The Services inmate Workflow The and The schedule school, The Volunteer The The are volunteer
F-PG-12 F-PG-13 F-PG-14 F-PG-15 F-PG-16 F-PG-17 F-PG-18 F-PG-19 F-PG-20 F-PG-21 F-PG-22 F-PG-23 F-PG-24 F-PG-25 F-PG-26 F-PG-27

170002-RFP
SERIAL Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Reporting Programs Programs Programs
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
track volunteer volunteers schedule. programs programs. waiting each limited and (e.g. room rates that inmate a on
and facilities. check a process. by of to a for not but approve/deny participation. characteristics has populations an for based
move check between volunteers list inmates maintain roster by, availability, inmate recidivism that numbers
volunteers of out events. background a and a facility. and the inmate notification eligibility program.
hours systematically background distinguish report maintain assign create generate and program review program session computer calculate on programs. housing/bed
schedule schedule monitor to to to to to time each date, to for and programs to in inmate each
to and in to to to and to ability ability ability ability ability automated in class, ability requests program of ability parameters automated correct provide schedule
way a hours way a way a way a clearance way a the the the the the tracking instructor, the instructor/facilitator, history outcome. the and participated an have to rules. to
provide logging provide provide provide the provide provide Programs provide provide provide programs. provide provide provide inmate maintain a keep the provide rules and/or provide they able be able be
may by shall shall shall in step shall may shall inmates. shall shall shall may inmate, shall for shall capacity). shall with in shall business shall so participation. shall business shall
solution worked solution solution solution next solution contractors. solution Inmate solution to solution solution individual solution solution attendance/participation program, solution decisions solution location, solution solution on completed solution moved solution of set solution
The hours The The progress. The the to The and The Adult The available The The for list The program. The to, The record The facility location, The participated The based have The been has program The defined The
F-PG-28 F-PG-29 F-PG-30 G-31 F-PG-32 F-PG-33 F-PG-34 F-PG-35 F-PG-36 F-PG-37 F-PG-38 F-PG-39 F-PG-40 F-PG-41 F-PG-42 F-PG-43 F-PG-44 F-PG-45
F-P

,
170002-RFP
Miiie'm"I''''''
SERIAL Programs Programs Programs Programs Reporting Programs Programs Programs Programs Programs Programs Programs Programs Programs Programs Property
,
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 Response 3
on keep- housing assignment alerts each are probation and to booked
and based lists. ongoing and or of officer they class, on completed, up are track
rules. recidivism. tendencies, the dates days, field programs report programs inmates to In-cell
participation. mandatory eligibility waiting notify provide program transportation. notifications changes end probation 60 a to all instructor, and to programs and accordingly.
business and to violent and housing and for opposed in track limited in when Property
inmate between inmate rosters back for electronically communicate and present inmate's custody participation program, log, not participation alert, attended tracked
defined rosters alert program unit beginning an as to but or merits
schedule discern determine a archive to characteristics. to a to housing to changes, display in been officer, to, ability as, and Clothing, need
on track way way in way way track track limited the such track applicable. notifications that and
to to to based to to a a enrolled a a occurred. to to has probation to inmate to previously
able able able able able provide defined provide provide inmate, provide classification able able inmate able not provide able if il ,5ilk identify items
be be be calculation be be is information. staff, has be be be but an be send
shall shall programs. shall shall shall shall other shall inmate shall to shall inmate's action shall may an (if internal shall by, shall for released. shall graduation may incarcerated 5 shall separate
solution solution solution score solution solution solution and solution an solution solution an solution solution an solution electronically solution status solution solution were ! solution are
voluntary proxy aways, that scheduling information when disciplinary program. information assigned officer). inmate. program dropped, including recidivism. - Property
The The The The The The The unit The The The The The The The The that PR The
D
F-PG-46 F-PG-47 F-PG-48 F-PG-49 F-PG-50 F-PG-51 F-PG-52 F-PG-53 F-PG-54 F-PG-55 F-PG-56 F-PG-57 F-PG-58 F-PG-59 F-PG-60 Section/I F-PR-1

170002-RFP
RMS
SERIAL Property Property Incidents integration Property Property Property Property Property Property Property Property Property
two-
data and Offencler360
Insight one
Scribe e\ecute between
the to
use ill software integrations applications.
w
Tribridge integration data other
waI and
3 3 -) 3 3 3 3 3 3 3 , 3
and location, released, is as as or locker
and property inmate's RMS which authorized released such which inventory. inmate's third the of loss of and
clothing inmates of attributes, (impounded, the to property/clothing process. property/clothing process to (or receipt booking location, property/clothing an inmate's from value time facility
inmate's an inventory type, reference/link released returned information name, storage add/remove/release property/clothing approve/deny party. third an details number). replacement (at loss the
an allow an to, status of list booking/intake of list booking/intake (or were identifying property/clothing inmate the evidence). a to release record of case record
of shall locker. limited and to release inmate's officer/agency, of to to to and license in to stored.
linking maintain not ability printable the printable the of number. to, status for ability inmate's ability ability estimated ability is
the system same and but possession the a during a during time property/clothing include inmate limited the taken the an the property/clothing the party driver's the compensation the
support The the in record as, such of provide number. maintain inmate maintain inmate the at shall booking an print be arresting date/time. record released, provide to/from provide provide third a (e.g. record filed). provide property/clothing
shall tracking. stored shall chain locker). may (1R) shall an shall an inmate indicating list The and shall not but description, shall shall items shall of release shall to identification shall or being shall
system for be to solution property/clothing comments, to solution Report solution from solution from the by name solution include booking solution location, solution solution for solution property/clothing solution property/clothing form solution where
The property clothing The staff assigned The Incident The received The received signed party) 3rd authorized). inmates The shall number, barcode, The (storage The impounded The request The party's The claim The number
F-PR-2 F-PR-3 F-PR-4 F-PR-5 F-PR-6 F-PR-7 F-PR-8 F-PR-9 F-PR-10 F-PR-11 F-PR-12 F-PR-13

170002-RFP integration
Property/RF1D Property/Electronic Release/Fingerprint
SERIAL Property Property integration Signature Property Module Release Release Release Release integration Release Release Release
two- two- two-
data and Offender360 data and Offender360 data and Offender360
Insight one Insight one Insight one
Scribe execute between Scribe execute between Scribe execute between
the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications.
will will will
Tribridge integration data other Tribridge integration data other Tribridge integration data other
way and way and Notes way and
3 3 2 2 3 Response 3 3 3 3 2 3 3 3
lost or requests. for all ident" and
list/ for RFID signed in-cell is holds, on returned fund
claims for and/or a disposition track inmate scheduled finger inmate's not
searchable support retrieve to an open disposition "two release. an item inmate
a items. inmate and ability locations. when for inmates for to that any the
create track provide property/clothing store the rules. search those range. check fingerprint prior record inmate. verify
to property/clothing to to to property/clothing provide storage notifications business automatic release. of date to inmates to returned. identify to the to
ability ability ability inmate ability its report means biometric all ability way to means
the the the track the inmate's shall track for on an to prior a ancUor a inmate. a of the were a given the release.
provide found provide provide to provide the solution and Requirements provide based provide provide date provide an provide identity provide clothing provide be to provide to
shall and shall may technology property. shall of the inmate shall release shall detainers shall specific shall for shall the shall shall form shall prior
lost of copy per for and a charges verify and/or claim balance
solution solution property/clothing. solution solution confiscated, Release solution solution solution for solution solution to solution solution a solution
The database The The Barcode impounded The electronic If property - RE The scheduled The wanants, The release The pending The check The property The create The account
4 l F-PR- F-PR-15 F-PR-16 F-PR-17 F-PR-18 Section/ID F-RE-1 F-RE-2 F-RE-3 F-RE-4 F-RE-5 F-RE-6 F-RE-7 F-RE-8

170002-RFP
SERIAL Release/Accounting integration Release/VANU integration Release/Photo integration Release/DNA integration
Release Release Release Release Release Release Release Release
two- two- two- two-
data and Offender360 data and Offender360 data and Offender360 data and Offender360
Insight one Insight one Insight one Insight one
Scribe execute between Scribe execute between Scribe execute between Scribe execute between
the to the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications.
will will will will
Tribridge integration data other Tribridge integration data other Tribridge integration data other Tribridge integration data other
way and way and way and way and
2 2 3 3 3 3 3 -) 3 3 3 2
to will Unit workflow release indicate other to is for to at well as is inmate with fingerprint
system System the to release, to inmate PSA prior release an
Notification per bed/cell/dorm/facility count for own released the notify stop" photograph that associated and date.
Financial (Financial released through facility reason to if and "file a inmate rules inmates. DNA release
the release balance). and be the goes the and released monitoring, notification release a is capture of transportation Ill query
with fund Assistance to inmate out, there to time business Mentally to projected
for update update condition / to if authority. and to ability by
interface remaining scheduled an bonded electronic alert prior alert ability date alert special
to scheduled Victim is as the to: an an requesting the the authorization. an by Seriously the sortable
able is with notify inmate automatically vacancy automatically released. record limited to DOC. provide monitoring provide provide record provide abide and provide unit
be shall inmate card shall an shall a shall been shall not released to shall shall the may shall shall shall juveniles shall and
an debit when indicate has but released electronic notify officer/supervisor release. facility
solution that solution requirements. solution to solution inmate solution recognizance, solution solution to solution solution solution solution of solution by
The notify generate The (VANU) The status process. The an The including agency, The receive installation. The release, The release. The as The pending The release The data
F-RE-9 F-RE-10 F-RE-11 F-RE-12 F-RE-13 F-RE-14 F-RE-15 F-RE-16 F-RE-17 F-RE-18 F-RE-19 F-RE-20

170002-RFP
Roles Roles
SERIAL Release Release Release Release Release Release rTrrIf Security Security Reportin(g_, Reporting Reporting Reporting Reporting Reporting Reporting
,- , ,
,
3 3 '; 3 3 3 t)f -4:i-,, 3 3 3 3 3 3 3 3 3
by and is before the Business alert on end- from (e.g. to by
releases DNA of or completed open based reports modeling report what formats output reports
fingerprints if releases, completed copy holds/warrants See notification no reports MCSO audit specific or
upcoming alert all as a for response. be to ensuring end-user jail-cost custom an regarding Solution. multiple report a e-mail, end-user
refused an for list validated library automatic a inmate standard MCSO solution. create the in schedule direct ftp, sort
query have present check positive present an charges, of produce create the to information within reports to to location, to
to that to are bidders the a to of all MCSO rules. to to in capability capability capability capability
ability ability electronic release (see when has ability release for to creation ability ability stored edited export file
the those the the process the a indicted access rules. the access the the fields the containing or and the the to: the
provide of inmate provide an track of completed notify/alert provide needed. allow sending. Requiremen control control security provide provide data provide logs opened produce provide provide limited provide
steps be release not reasons are access all last excel). not
shall and shall shall all can shall shall are shall holds shall shall solution shall shall on shall history was shall shall shall but printer. shall
that upon release Reporting security reports. file, jobs. Division.
solution facility solution solution release list). solution solution fingerprints solution or es solution solution on solution solution reports solution solution information solution flat solution solution following solution
The date, DNA. The needed. The ensuring the check The triggered Rules. The if The without char. RP - The solution The based The analysis The user The the The PDF, The reporting The the designated The MCSO
F-RE-21 F-RE-22 F-RE-23 F-RE-24 F-RE-25 F-RE-26 Section/1D F-RP-1 F-RP-2 F-RP-3 F-RP-4 F-RP-5 F-RP-6 F-RP-7 F-RP-8 F-RP-9

170002-RFP
SERIAL Reporting Reporting Reporting Reporting Reporting Reporting Reporting Reporting Reporting Reporting Reporting
3 3 3 3 3 3 3 3 3 '; 1
defined tools. Queries (pie reports to: facility, not but charge, field), for the to
queue, solution stored shelf the authorized management additional summaries all provide limited facility, area, following time, ranges interest statistical key and
by range. end-user data off the Report, for to not cell, sentencing cell, date, (defined of other
status date create range. appropriate all from allow existing - 9 for graphical filters capability but by the for type, by ethnicity, metrics summary and notifications
workflow and to date commercial to all for Exhibit Library range range). following status, min/max population reports custody by with capacity, display.
tasks, capability by the with reports party screen reports. See Bidder's producing reports. date from-to reporting medical agency, in facility, provide visual group
report due reports user ad-hoc third online equivalents jail. - of standard ad-hoc the status, criteria, inmate statistical by inmates by etc. dashboards shall easy report users.
and past the a create using an statistical the by 11 capable statistical yearly, including total bookings of shift, recaps, solution performance, an in for specified
display range, provide indicators provide to provide print provide use Exhibit be for provide monthly, provide gang classification provide and percent by provide the provide to
shall date shall shall ability solution shall to shall in and shall graphs) shall shall statistics gender, all forecasting, shall arrests bookings arrest shall The about indicators shall mailings
solution user, solution performance solution the the in solution ability the solution currently Messages solution line solution weekly, solution race, solution to: residence, of recaps, solution staff. solution
The assigned The key The security, within The users The reports and information. The charts, The (daily, The management inmate, movements, predictions, etc. The limited of city number booking The command information performance The electronic
F-RP-10 F-RP-11 F-RP-12 F-RP-13 F-RP-14 F-RP-15 F-RP-16 F-RP-17 F-RP-18 F-RP-19 F-RP-20

170002-RFP
SFRIAL Reporting Reporting, Reporting Reporting Reporting Reporting, Reporting Reporting Reporting Reporting, Reporting Reporting Reporting
3 3 3 3 3 3 3 3 3 3 3 3 3
/ applied individual such spacing, grouped be case data of data of to be users
summary. transactions be and printed. be to of to
to releases be key queried, and decisions line to filters comparison comparison ability reports specified
record all criteria to can with be size, reports data searching the report. to
and records that can generator group. layout font and etc. and have the recurring
inmate inmate filtering inmates that over text, on data multiple "Google-like" groups, shall modify e-mailed
an an public summary printed. report user analysis analysis for or
of Allow for current database be the or control label for for fields. stored. user or capability share
printout about release of printed. to to user user width, ability ability include statistical demographic statistical the run,
a inmate. history a Library. list a inmate results access by the the the narrative and report, access, the file a
information be an column element. logic. may for for time to times.
provide that criminal etc. provide Bidder's provide can have allow restrict permission-based provide provide provide other allow between allow in standard can provide
shall basic for information, shall - shall that shall and shall shall arrangement, shall data any shall and/or solution all shall shall point a users shall uploaded and
forms excluding 11 data sorted, by using and periods a at creating which and days
solution includes and as solution Exhibit solution solution solution via solution solution solution reporting solution time solution solution specific
The This events such medical The See The identifying The filtered, The reports The field as etc. The sorted or The applied The narratives The over The calculated When choose The scheduled on
1
F-RP-21 F-RP-22 F-RP-23 F-RP-24 F-RP-25 F-RP-26 F-RP-27 F-RP-28 F-RP-29 F-RP-30 F-RP-3 F-RP-32 F-RP-34

170002-RFP
SERIAL Reporting Reporting Reporting Reporting Reporting Reporting Reporting Reporting Reporting Reporting.- Reporting
3 3 3 3 3 3 3 3 3 3 3
of variety Custom agency, available agency year- held on these sub- card" from statistical data the
a • for for inmates or on a for held inmates based of property the priced the to solutions. "wild of search record detail. searches. fields extract of
generate to: selected held of cells post to inmates of days describe requisite separately regard using number previous of data data to analysis. provide accuracy
to limited fields by Rosters occupied bookings reports of report inmate combination bands, shall the as interfaced search the limit on specific a levels cross-database visibility summary order and and solution.
able not down of Arrest Annual of a arm specify without to capabilities. to searches select greater limit in external collect the
be but broken element. Lists recent comparisons Analysis ethnicity, for contractor and hardware), easily on to or to provide users for to capacity, of
shall following agency-defined data of outlets. years. labels stored capability search methods search. ability ability to sets ability
permission rosters, other facility. lists media Statistical agency. race, elements code The regard and data data the partial other a secondary the successively cross-table the users/workstations. ability authorized query the performance, operations
the least with inmate any the to previous by gender, data bar labels. this in services functionality. retrieve including provide other include from provide provide to support provide the defined provide
sufficient at forms or of Professional-looking provide period. to age, other print folder this to able as returned down" have specifically the management
including summary Current gender, out or to time compared agencies, any shall and capabilities (software, enable be involved, shall well as shall are may shall "drill shall shall unauthorized shall to from may about
with block, in or site outside status, or solution to shall solution solution that solution solution to solution solution solution solution the and
user A reports inmate inclusion. cell currently cells. Web specified to-date for holding factors, The tags/labels, solution's equipment items, Users system The characters The records The returns. The list the The The from The capabilities information The information itself
F-RP-35 F-RP-36 F-RP-37 F-RP-38 F-RP-39 F-RP-40 F-RP-41 F-RP-42 F-RP-43 F-RP-44 F-RP-45

170002-RFP Administration
Director:\, Directory Director Directory Directory Directory Directory Directory Directory
SERIAL Reporting Reporting Reporting Reporting Reporting Module Active Active System Active Active Active Active Active Active Active
Notes
3 3 3 3 3 Response 3 3 3 3 3 3 3 3 3 3
including, be to ad and/or to to to against ID TOG from are no system. to
report. Workflow statistics an on Random user to user user user expiration, ID credentials is who the user
entry a whose prior etc. validate whose or
litigation workflow See enter new print administrative user days administrative administrative administrative and user to TOG ID accessing administrative
by category. a and rules. any 30 expiration, any prior expired TOG resigned,
a run report manually create create business an to at notice to an accounts. an an maintain to days etc. an their has from an
to to and to to to for alerts prior for for for to alerts 30 expiration, with as who reason, for
ability ability content ability ability ability on Requirements ability electronic first days ability logon ability ability ability date. electronic at user time user ability
the the task, the the the based the e.g., ten the user the the the notice to prior any such any other the Indicator(s).
facility passwords. expire, a ID. expiration first until some
provide provide status, provide dashboard. provide provide Administration Management provide provide notice provide inactivate provide provide provide provide e.g., days prohibit prohibit for provide Routing
to by to name. TOC for ten system user
shall shall may a may shall report shall change shall about second shall or shall shall shall ID shall expire, a shall shall shall
solution solution limited solution on solution report. solution Test System Account solution to solution is solution change, solution user's a solution user's a solution TOC solution to notice solution the current. solution valid a solution user's a
The The not but Requirements. The displayed The hoc The Drug - SA User The end-user The password expiration, The add, The change The manage The user's The about is second The accessing again The longer The manage
a
F-RP-46 F-RP-47 F-RP-48 F-RP-49 F-RP-50 Section/ID F-SA-1 F-SA-2 F-SA-3 F-SA-4 F-SA-5 F-SA-6 F-SA-7 F-SA-8 F-SA-9 F-SA-10

170002-RFP
Director; Directory Roles Roles Roles Roles Roles Roles Roles Roles Roles Roles Roles Roles Roles
SERIAL Active Active SecuritI.. Security Security Security Security Security SecuritI.. Security Security Security Security Security Security
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
to to user. to to to to to to to to to to to to to
user user end user user Detention user user user user user user user user and user privacy. user user
the to roles data
administrative administrative exposed administrative administrative MCSO administrative administrative administrative administrative administrative administrative administrative administrative user administrative explicit administrative administrative
the
an an never an an MCSO, an an user. an an an an an an using an ensure an profile. an profile.
for for is for roles. for as: for for a to for for for for for control. for for to for group for group
ability ID. ability it ability ability (such etc.). ability ability ability ability roles. ability roles. ability ability access ability transaction(s) ability users ability a ability a
the the however the the roles the control. the assignment the database. the to the multiple the assignments. the the the the through the through
provide unique a provide ID, provide process-specific provide global Probation provide access provide role provide the provide privileges provide or provide role provide role-based provide specific provide external provide provide
shall user shall user Users shall shall Adult shall shall manual shall within shall shall one shall shall shall to process. shall and shall controls shall privileges
each unique business business Court, role-based the Management workflow to temporary temporary access internal profiles access user
solution to solution the and solution solution solution solution solution roles solution solution users solution solution solution authentication solution solution solution
The allocate The view Roles The manage The manage Units, The manage The manage Role The define The assign The assign The remove The assign The restrict The separate Group The manage The manage
F-SA-11 F-SA-12 F-SA-13 F-SA-14 F-SA-15 F-SA-16 F-SA-17 F-SA-18 F-SA-19 F-SA-20 F-SA-21 F-SA-22 F-SA-23 F-SA-24 F-SA-25

170002-RFP Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration
Roles Roles it
SERIAL Functionality Functionality Functionality Functionality Functionality Functional Functionalit Functionality Functionality Functionality
Security Security System System System System System System System System System System
i
3 3 3 3 3 3 3 3 3 3 3 3
to to to the to the to the to the to solution. to to solution. to to solution. to the
user user user user user throughout user user the user solution. user the user solution. user user throughout
throughout throughout throughout the the the
administrative administrative (machines/terminals). administrative administrative used administrative used administrative administrative throughout administrative administrative throughout administrative administrative throughout administrative used
used be used throughout throughout be
an an an be to an be to an to table an be an used an an used an an used an to table
for for for table for table for for to for be for used for be for used for be for
ability ability stations Requirements ability ability code ability code ability table ability to ability be to ability to table ability be to ability to ability code
code code table table Type
the profile. the work the Type the Type the Status the the code the table the code the table the code the
provide provide for Business provide provide Status provide provide Type provide Color provide code provide Type provide code provide Color provide
security profiles Document Immigration Identifier Gender Facility Expungement
shall shall shall shall Case shall shall shall Hair shall shall Form shall shall Eye shall
group group the the the the the the the the the the
solution solution Administrative solution solution solution solution solution solution solution solution solution solution
manage manage maintain solution. maintain solution. maintain solution. maintain solution. maintain maintain maintain maintain maintain maintain solution.
The The The The The The The The The The The The
F-SA-26 F-SA-27 F-SA-28 F-SA-29 F-SA-30 F-SA-31 F-SA-32 F-SA-33 F-SA-34 F-SA-35 F-SA-36 F-SA-37

170002-RFP Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration
SERIAL Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality
System System System System System System System System System System System System
3 3 3 3 3 3 3 3 3 3 3 3
to to to solution. to to the to to solution. to to to to to solution.
user the user the user user used user user the user user user solution. user the user solution. user the
the be throughout the used the
administrative throughout administrative throughout administrative throughout administrative to administrative administrative throughout administrative administrative be to administrative the administrative throughout administrative administrative throughout
table used throughout throughout
an used be an used be an used an code an be to an used an an table code an throughout an used an an used
for to for to for be for Type for table for be to for used for for for be for used for be
table table to be Type used to be to
ability ability ability table ability ability code ability table ability to ability ability be ability table ability to ability table
the code the code the the Instruction the Type the code the table the Reason the to the code the table the code
provide Status provide Result provide code provide provide provide provide code provide provide table provide provide code provide Type
Type Document solution. Disposition Disposition Country Keep-away solution. code Citizenship
shall Marital shall Event shall Unit shall shall shall shall shall shall City shall shall Charge shall Case
the the
the the the the the the the the the the the the
solution solution solution solution solution solution solution solution solution solution solution solution
maintain solution. maintain solution. maintain maintain throughout maintain solution. maintain solution. maintain maintain throughout maintain maintain solution. maintain maintain
The The The The The The The The The The The The
F-SA-38 F-SA-39 F-SA-40 F-SA-41 F-SA-42 F-SA-43 F-SA-44 F-SA-45 F-SA-46 F-SA-47 F-SA-48 F-SA-49

170002-RFP Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration
SERIAL Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality
System System System System System System System System System System System System
i
3 3 3 3 3 3 3 3 3 3 3 3
to the to to to to to to throughout to the to to the to the to
user user solution. user the user solution. user solution. user the user user throughout user solution. user user user solution.
throughout the throughout the the throughout used the throughout throughout the
administrative administrative administrative administrative administrative administrative administrative be to administrative used administrative administrative administrative administrative
used throughout used throughout throughout used table be throughout used be used throughout
an be to an an be an an an be an an to an an to an be to an
for for used for to for used for used for to for code for table for used for table for for used
ability table ability be to ability table ability be ability be ability table ability Type ability code ability be ability code ability table ability be
the code the table the code the to the to the code the Service the the to the the code the to
Type table table Day Response table Severity Type table
provide Sub provide code provide Type provide code provide code provide Of provide provide provide code provide provide provide code
shall Case shall Sealed shall Record shall Unit shall Title shall Time shall Subpoena shall Warrant shall State shall Charge shall Sentence shall Role
the the the the the the the the the the the the
solution solution solution solution solution solution solution solution. solution solution solution solution solution
maintain solution. maintain maintain solution. maintain maintain maintain solution. maintain maintain solution. maintain maintain solution. maintain solution. maintain
The The The The The The The the The The The The The
F-SA-50 F-SA-51 F-SA-52 F-SA-53 F-SA-54 F-SA-55 F-SA-56 F-SA-57 F-SA-58 F-SA-59 F-SA-60 F-SA-61

on
170002-RFP Administration Administration Administration Administration Administration Administration Administration Administrati Administration Administration Administration Administration
ity
SERIAL Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functional
System System System System System System System System System System System System
3 3 3 3 3 3 3 3 3 3 3 3
to solution. to solution. to to solution. to to solution. to solution. to the to the to the to to
user user user the user the user solution. user the user user throughout user user user the user the
the the the throughout throughout
throughout the throughout throughout
administrative throughout administrative throughout administrative administrative throughout administrative administrative throughout administrative throughout administrative used administrative administrative used administrative administrative
used throughout be to used be be used used
an used an used an be an used an an used an used an table an to an to an be an be
for be for be for to for be for used for be for be for for table for table for to for to
ability to ability to ability table ability to ability be ability to table ability to ability code ability code ability code ability table ability table
table table code table to table code
the code the code the the code the table the code the code the Juvenile the Adult the Printer the the code
Type Id
provide provide provide provide Type provide code provide provide provide provide provide provide User provide Type
shall Response shall Language shall Referral shall Cost shall Race shall Prosecutor shall Probation shall Probation shall Probation shall Available shall Print shall Phone
the the the the the the the the the the the the
solution solution solution solution solution solution solution solution solution solution solution solution
maintain maintain maintain solution. maintain maintain maintain maintain maintain solution. maintain solution. maintain solution. maintain solution. maintain solution.
The The The The The The The The The The The The
F-SA-62 F-SA-63 F-SA-64 F-SA-65 F-SA-66 F-SA-67 F-SA-68 F-SA-69 F-SA-70 F-SA-71 F-SA-72 F-SA-73

170002-RFP Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration
SERIAL Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality
System System System System System System System System System System System
3 3 3 3 3 3 3 3 3 3 3
by have these to and to
to to to to have to solution she to solution, to and to to solution she to and needs to needs
user the user the user the user and user or user -nation user user have user the or user solution she user solution she
the he infon the solution and he or the or
administrative throughout administrative throughout administrative throughout administrative solution lists. administrative within when administrative throughout administrative the administrative administrative within when administrative the he administrative within he
the down list use with in solution list use status. within when record. when
an used an used an used an in drop an type for an table used an stages an the an type for an list use an list use
for be to for be to for be to for type status for users information. for code be for for in list for status users for type for person for type for
ability table ability table ability table ability case ability information other ability Cost to ability workflow ability type ability other representation ability users to ability property users information.
by case Year source
the code the code the code the status the the to contact the Housing the type the expense the representation to the other associated the other
provide Type provide Flag provide provide case in provide contact available provide Fiscal provide case staff. provide provide available person's provide picture to is provide person's to property
Relationship use person's Average and to an staff. a the a available file a available
shall Person shall Person shall shall modify for shall modify be a shall Type shall modify shall modify to shall modify be shall modify shall modify
the the the available these enter the available these update be image be person's
solution solution solution solution and solution and have to solution solution and be solution and available solution and have to solution and these an solution and these a
The maintain solution. The maintain solution. The maintain solution. The create these The define and needs The maintain Jurisdiction The define these The define be The define and needs The define have enters The define have enters
F-SA-74 F-SA-75 F-SA-76 F-SA-77 F-SA-78 F-SA-79 F-SA-80 F-SA-81 F-SA-82 F-SA-83 F-SA-84

170002-RFP Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration
SERIAL Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality
System System System System System System System System System System
3 3 3 3 3 3 3 3 3 3
have enter rules on cases be
to have to and to to have lists. to to throughout to to the to these a to the to solution.
user and user needs user and down user and business user user based murder user user License, have enters user user the
solution lists. solution she solution drop clauses on used materials and generation. throughout (Driver's and to throughout
administrative administrative the or administrative administrative based administrative be administrative administrative administrative needs administrative administrative throughout
the down within he the code forms, to of penalty used list solution she used
an in drop an when an in role an items an table an packages death document an be to an type the or an be an used
for for list use for codes person for these for code for for table for he for to for be
ability descriptions type ability type for ability role ability documents, ability ability appeals, of ability ability identifier within when ability tables ability to
the case the context users the case the recalling the Type the documentation time the the code the etc...) use the code the table
type the in other person the in complex Security as such at Status person's for information. Type code
provide case use provide name information. provide case use provide packages provide provide user provide provide LEJIS, users provide provide Flag
shall modify for shall modify to shall modify for shall maintain shall Inmate shall maintain event; a by shall Custody shall a modify Number, other shall Access shall Case
available available name available the and recalled the to identifier the the
solution and solution and be solution and solution and documentation time. solution solution. solution and type solution solution and FBI solution solution
The create these The define these person's The create these The create run at The maintain the The create case be to The maintain solution. The define SID, available person's The maintain solution. The maintain
a
F-SA-85 F-SA-86 F-SA-87 F-SA-88 F-SA-89 F-SA-90 F-SA-91 F-SA-92 F-SA-93 F-SA-94

170002-RFP Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration
SERIAL Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality
System System System System System System System System System System System
3 3 3 3 3 3 3 3 3 3 3
the the to
to to to to solution. to the to and needs to the to to generated to to solution.
user throughout user throughout user user user user she user user user user user
used the throughout solution or throughout lifecycle solution solution. the in
administrative used administrative used administrative be to administrative administrative administrative the he administrative administrative case administrative for administrative the administrative used
be be table throughout used within when used in
an to table an to an code an an be an list use an be an inmate's an information an used an codes
for for table for for used for to for type for for to for for for codes for fine
ability code ability code ability Delimiter ability be to ability table ability users ability table ability selected ability ability ability and
the Type the Type the the table the code the address other address. the code the the the location type. the charge the bond
provide Event provide Class provide Choice provide code provide Type provide contact to provide Type provide print provide and message provide retire provide retire
solution. available contact or line and and
shall Inmate shall Inmate shall Answer shall Agency shall Address shall modify shall Activity shall online shall subject inmate shall shall
the the the the the the be person's the status. by maintain, maintain,
solution solution solution solution solution solution and these solution solution view solution solution solution
The maintain solution. The maintain solution. The maintain throughout The maintain The maintain solution. The define have a enter The maintain solution. The either workflow The configure messages The create, The create,
04 05
F-SA-95 F-SA-96 F-SA-97 F-SA-98 F-SA-99 F-SA-100 F-SA-101 F-SA-102 F-SA-103 F-SA- F-SA-

170002-RFP Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration Administration
SERIAL Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality Functionality
System System System System System System System System System System System
1 3 3 3 3 3 3 3 3 3 3
to table to table
to to to table to to be to table to to to
user IT user solution. tables user code user code user to user code user code user user
without administrative in Charge table Charge
administrative administrative the in established administrative Charge administrative into administrative Schedule administrative Schedule administrative administrative administrative
documents used maintain action. into ACJC Bond Billing
an skills. an for an ACJC an an Bail an the an the an an
for for company to parameters for for from for the for for for for
ability template scripting ability ability reason Administrator. ability from ability ability within ability within ability within ability data. ability
the / the bond the the on the Code" solution. the Code" solution. the the solution. the solution. the of the
provide automated provide retire provide indicating based System provide ARS the provide ARS the provide information solution. provide information the provide information the provide persistence provide
programming and be the
shall maintain shall shall tables may the by shall "Current throughout shall "Historical throughout shall bail shall bond throughout shall billing throughout shall automatic shall calls.
solution and or solution maintain, solution code dates solution the solution the used solution the throughout solution the solution the used Bindings solution solution API
The create assistance The create, The sealed Archive maintained The Import used be The Import be to The maintain used The maintain used be The maintain be to Data The manage The manage
F-SA-106 F-SA-107 F-SA-108 F-SA-109 F-SA-110 F-SA-111 F-SA-112 F-SA-113 F-SA-114 F-SA-115 F-SA-116

170002-RFP Administration Administration Administration Administration
and and and and and and
SERIAL System Functionality System Functionality System Functionality System Functionality Module , Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling
,
''
m
otosr ik
e" P9.,§,,
3 3 3 3 3 3 3 3 3 3
Re f4 I
to to to forms to not but (work any recurring in by inmates calendar week,
user user user manage through Attorney), of via housing
component including assignments alert resolved scheduling/re- or or schedules specific in day,
administrative administrative administrative update, determined (RCC, and be a single facility or schedules by
schemes. create, as activities, visitation work notify to include override the query/view program, inmates
an for an for layout an for to forms scheduling/re-scheduling and and for, conflicts and or for to print to specific
ability ability ability File. ability events programs, events release). check user schedule etc.) ability facility, ability and/or
the the multiple the Purge the archiving ;-: 1,.. inmate adhoc furlough, scheduling to services, the entire the
provide provide support provide ordered provide and Nun- a have all court, to automatically allow authorized able religious provide the year. provide facility
shall manually. shall that shall court shall versioning, mg shall of transfers appointments, detail, shall conflicts. shall by notification. be shall as shall for or month shall entire
Layout solution forms solution forms solution the solution Rules. u lc c solution tracking to specific solution solution override solution (such solution format week, solution the for year. or
Form The design The manage The maintain The including Business The provide limited healthcare hours, The scheduling The manual scheduling The events areas. The calendar day, The format month
F-SA-117 F-SA-118 F-SA-119 F-SA-120 ection F-SC-1 F-SC-2 F-SC-3 F-SC-4 F-SC-5 F-SC-6
..

170002-RFP
and and and and and and and and and and and and and
SERIAL Offender/CHS integration Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Schedulimr. Calendars Scheduling
two-
data and Offender360
Insight one
Scribe execute between
the to
use software integrations applications.
will
Tribridge integration data other
way and
2 3 3 3 3 3 3 3 3 3 3 3 3 3
solution appointments future on based and limited cell with displayed data record release. amount of and
appointments cancel location, language schedule not number, keep-aways, inmates and related permissions. court unlimited transportation single
scheduling group notifications. information type, court are but booking printed inmate's inmate inmate
Requirements. recurring automatically release. facility, interpreter, a charge, when all court user clothing all of upon an schedule time.
care schedule up inmate's scheduling generate include, number, dates. on update on an flag trial record schedule schedule mass one
health Interface to set to cancellation inmate, LEP to that case serious alert/notification scheduled to based to in cancelled to to to at
the - capability to ability the on to ability elements most multiple ability judge) ability out historical ability inmates. ability accommodations. ability inmates
with 7 ability the upon automated reporting limited wheelchair, the location, judge, an are the room, the dressed a appointments the of the the of
interface Exhibit See the have the have dates. provide based send allow not needs, provide data by housing time, officer, provide notations provide court provide be to maintain provide appearances provide special provide groups
shall out). shall shall end shall appointments may shall but special information. shall ability name, court assigned shall shall time, may is shall including shall shall shall for
and and/or including keep-away inmate court including events
solution in solution inmates. solution start solution solution solution demographic solution sorting inmate room, assignment, solution solution (appearance solution the solution scheduling solution future solution solution
The (CHS The for The with The inmate The The criteria date/time, The with to, court The active schedules. The The when The The of The inmates The recurring
F-SC-7 F-SC-8 F-SC-9 0 I F-SC- 1 I F-SC- F-SC-12 C-13 F-SC-14 F-SC-15 F-SC-16 F-SC-17 F-SC-18 F-SC-19 F-SC-20
F-S

170002-RFP
and and and and and and and 1\lanagement Management/SharePoin
SERIAL Calendars Scheduling, Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Record Document
t
in record file that CAD be can web and management can your reviewed,
to any format documents, can Offender360. that attach using Online you in .
ways to attached file files notes, to by created, archived
easy An Word spreadsheets, attachment in of size document ability desired, SharePoint capabilities, documents
provide information database. computer Office An object the messages, the is of are or
standard Excel files. any on set email extended beyond records or management cycle they how disposed
entities additional Microsoft Office PDF with be to If to Server life and
Notes Offender360 any be includes Microsoft and associated can attached resources. functionality documents SharePoint document the organization: published,
The append the can files, Limits be control
3 3 3 3 3 3 3 3 3
and the master to can
events as dates require both a information. events that events scheduled
recurring combinations multiple that rules. in maintain acknowledgements acknowledgements of Gangs a
events business transfers activities. types Chain scheduled to
scheduling other including and restrictions new DUI files
and identify MCSO schedule agencies. create and require activities. make schedule create e.g., archive attach
of to on to to alerts to to to to to
option monthly, applications ability based ability external ability ability schedule ability specific ability scheduling ability ability
the the the to the including the specific the of the of on. the the
provide bi-weekly, calendaring provide inmate(s) provide status provide include of include provide time reported provide provide
shall may an of shall inactive shall schedule, may may dispositions may the at and shall may
weekly, typical dispositions
solution in date. solution transportation solution and solution daily solution solution enter solution scheduled searched solution indefinitely. solution
The daily, as found end no The The active The inmate The and/or The and/or The be be The The event,
F-SC-21 F-SC-22 F-SC-23 F-SC-24 F-SC-25 F-SC-26 F-SC-27 F-SC-28 F-SC-29

of of
170002-RFP
and Appointments/Clerk integration Appointments/Clerk integration and and and and and and and
SERIAL Calendars Scheduling Offender/Cowl Courts Offender/Court Courts Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars Scheduling
data two- data two- Adxstudio allow inmate's and seamlessly and
and Offender360 and Offender360 will web
Insight one Insight one of that an Microsoft that platform and portals.
Scribe execute between Scribe execute between use the portal about a product Dynamics creation
the to the to leverage facing information is easy based
use software integrations applications. use software integrations applications. Adxstudio management the the web of
will will will public see with allow
Tribridge integration data other Tribridge integration data other Tribridge a build to schedule. content integrates to maintenance
way and way and to people data
3 2 2 3 3 3 2 3 3 3
scheduled Systems Forms who when functions. all to unlimited
create Court Event inmate inmates alerted (SMI, the a display when goes an schedule.
and/or previously an of be before inmate's calendar simultaneous appointment used display
with Interface Court whether report to needs an to is be to information the
highlight a if integrate - 7 receive record a create user the special display free/busy schedule solution conflict. an define same and to it add
to rules to Exhibit to to reason. to for other examples)infonnation to to to The in to information the receive and
ability business canceled. ability See ability ability the ability ability and/or ability similar ability inmate. are ability location (all to ability inmate
the MCSO or the Courts. the the and not the event. the LEP as the parties the locations the group). the an
provide on provide of provide provide or provide scheduled provide MHCC confirmed. provide provide same the provide and line appointments the have for
may based changed shall Clerk shall may obligation may a shall identified van, is may external may the for if shall subject group in shall dates
been the an attend is to message calendars court
solution notifications has solution Requirements. solution electronically. solution solution not solution inmate Wheelchair appointment solution availability solution appointments solution template's scheduling solution of
The event The including The The fulfilled The did The an The The warning The inmate The number
F-SC-30 F-SC-31 F-SC-32 F-SC-33 F-SC-34 F-SC-35 F-SC-36 F-SC-37 F-SC-38 F-SC-39

,i•
170002-RFP ,,,,
and and and and
ing
SERIAL Calendars Scheduling Calendars Scheduling Calendars Scheduling Calendars 1 u •entencin,c, Sentencing Sentencing Sentencing Sentencing Sentencing Sentencing Sentencing Sentencing Sentencing
Schedu Ma
L , 4
OMMIII660A411
Notes
3 3 3 3 Response 3 3 3 3 3 3 3 3 3 3
hearings for with and multiple and with types. into Parole, the credits
visitation entries multiple specific sentence fine release configurable to work shall manually
appointments judgment a configurable associated sentence a a Conversion a to Release handed Solution to
telephonic video calendar apply maintain apply apply hours. convert attach report user day
-ide the all to to to cases. user be unlimited to or to to to: be inmate. be can for day means
schedule schedule schedule oven record court. ability consecutive. ability ability court be to ability days ability recalculation). ability limited should an they calculations. a date.
to to to to to the the or the the to algorithm of the months, the the not of (so calculate provide
ability ability ability (CHS). ability Requirements user from user user conditions. user multiple types addition user user and user but condition release printed to 1 for and release
the the the the end end concurrent end end or sentence sentencing the end years, end days configurable. end as the be user 2 worked the
Services the received the the related the case for the the for the such Release allow to the including affecting
provide provide etc. provide provide Calculation allow allow run be allow and allow court allow a of allow allow allow user allow able allow days
shall shall attorneys, shall Health shall role. shall data shall can shall shall a to shall entry type. shall shall consecutive/concurrent shall (dollar be shall sentence, Program. not may be release) shall sentence of sentence,
court. to related that sentence(s) type the time must a to or shall number
solution video solution solution solution Sentence solution solution solution solution solution for sentence solution solution solution solution may upon solution a on the the
walk-ins, Correctional according - sentence sentences inmate sentence allow each sentenced algorithm condition Probation, conditions inmate based track apply
The and The The The SN The The The The The The The for The The and The
F-SC-40 F-SC-41 F-SC-42 F-SC-43 Section/ID F-SN-1 F-SN-2 F-SN-3 F-SN-4 F-SN-5 F-SN-6 F-SN-7 F-SN-8 F-SN-9 F-SN-10

170002-RFP
SERIAL Sentencing Sentencing Sentencing Sentencing Sentencing Sentencing Sentencing Sentencing Sentencing-
3 3 3 3 3 3 3 3 3
inmate's record dates, the or certain and edit, restitution, and business on the a viewable sentence calculation other release
an to release Upon approval, remove sentence multiple record, an concurrent a based action, approval, to his/her and
when continue needed. and manually to record for configurable to fines, calculate earning Requirements. confirm manually notes a keep and/or a print record
note but calculated is and ability entered to in-eligible ability custody, to dates, time to received, disciplinary Upon and and add to notes. to sentence to summarizing completions, public
to credits, in notification the previously ability or user the recommendation. ability release good Rules ability is restrictions. notification ability to made ability a ability and on
ability recalculation automatically user the eligible be user including the of the change completion, automatically the the to the program based
the work changes a authorized a user should authorized user multiple Business to a of user changes user made user date
user day All that recalculation to from end inmate types program end incorporation user program medical recalculation to end end changes end release rate, calculation
the for worked. ability an credit the an an information, the including See the notification ability the track the the earning
allow day notification the of the sentence. allow work allow make Reason types. allow and allow date, control. allow as and/or a of the sentence. allow and allow all of allow inmate sentence
shall receive days a have shall time shall may unlimited shall sentence sentence shall sentences, shall when such sentence, have may calculation shall trail) shall an time
to of shall the that programs. release quality events, shall the (audit specifying good affecting
solution number include acknowledgement solution good solution for solution review solution consecutive and solution recalculation acknowledgement solution solution solution
The ineligible the shall solution recalculate The adjust The reasons release allow The and modifiable The inmate's rules The varying amended solution recalculate The sentence The history calculation. The sheet sentences, events rules.
13
F-SN-11 F-SN-12 F-SN F-SN-14 F-SN-15 F-SN-16 F-SN-17 F-SN-18 F-SN-19

170002-RFP - -
S
SERIAL Sentencing Sentencing Sentencing Sentencing Module e M CACTAS CACTAS CACTA
two- a with the on automatically be may account I II on trust all and time.Phase II
data and Offender360 based use will intake Phase based for Phase
Insight one profile will at trust page.Phase is tracking over
execute between accounts created MCSO CACTAS available intake's task system. design records detail system.
Scribe the to accounting fund is I II be new intake existing implemented accounting transaction and transactions existing implemented
use software integrations applications. inmate trust classification Phase Phase may the to the use be activity these use be
will of booking. system. that from will will fund of of will will
Tribridge integration data other entire set default inmate's existing implemented funds deposited directly MCSO CACTAS trust creation accounting reporting MCSO CACTAS
way and Notes The upon Any be Our the I
3 2 3 3 Response 3 3 3
of Reporting electronic made. information Hours, release serial an up personal initially the by
list a an has be Time, including completed. set Requirements. is trust real-time
create See send who must sentencing projection is automatically inmate's inmate purchases, entire
to sentence. to inmate notification (Regular of approval, credit Interface posting the in tracked inmate's
ability of ability an of record sentence calculation 1) for shall 7 when canteen be each
the the release victim to of authorization (2 module Exhibit real-time (e.g.
user percentage user a that ability Type including date) time equirements of account account automatically during
end the end the physical the to: the good fund See capable personal manner
allow completed allow the requiring provide limited Release Release instructions date record of i Processing trust booking. the shall
shall the shall to prior charges shall not Work Order shall removal inmate at be shall inmate's jail. affecting etc.) seamless period.
with but Court sentencing effective Time when At Account solution's account the the into fees, a in
solution Requirements. solution notification qualifying solution End, or solution name Trust solution to Transactions incarceration
The inmates The The including Week date Special Sentence Release Fees The #, - TA Inmate The inmate The funds booked deposits, solution
F-SN-20 F-SN-21 F-SN-22 F-SN-23 Section/ID F-TA-1 F-TA-2 F-TA-3

170002-RFP
SERIAL CACTAS CACTAS CACTAS
be for kiosks. to added MCSO be may Records reports will be will that and So provides can be
to cards. by instructions IVR inmate number service relatively as public I CACTAS that to on MCSO requires created accounting allows. the to and inmate use will
kiosk deposits entered an allowing PIN IVR the method easily II table information. tied I CACTAS predefined intake/booking is the will CACTAS
debit/credit be https://CommissaryDeposit.com use offer orders, to and be required.Phase Phase be displayed II a inmate trust classification assigned activity then MCSO
public a inmate or may to does inmates transfers, offered due deposit website could Sources may and purposes.Phase Phase CACTAS to the that all in fund type I II
offer allowing cash deposits easy the for commissary fund not date to this public service as system. a depositor table system. in assigned Once saved participate his/her classification trust account Phase
does using to CACTAS currently of have deposits of to this solution existing implemented features with sources deposits task be is allows deposits.Phase system.
web following service We demand IVR use this investigative existing implemented booking inmate classification. to that the as default implemented
CACTAS application processed Online navigating and provided solution placement phone change. public low compared However, our will be will CACTAS populated from individual for use The each transaction enabled activity long inmate a for accept existing
1 3 3
via web that inmate Interface
deposits via - 7 depositor the
Center), Exhibit that See
account See the deposits.
Visitor regarding acceptance
allow and phone. accept
shall a
(Intake using information purposes. automated can
module and
premises solution an
trust capture investigative support established
inmate Jail on IVR an Requirements. shall shall
via for been
solution's located and deposits used solution has
The kiosks access Interface Trust be may The account Requirements.
F-TA-4 F-TA-5 F-TA-6

170002-RFP
S
SERIAL CACTAS CACTAS CACTAS CACTA CACTAS
by II for report as long printer a as will be ill w listed use be frame a for existing module cards. the system.
deposits value be I Phase transactions status. So MCSO be will will include statements time or use debit without web A will at release
on period. may activity.Phase printing normal printers. windows function I CACTAS may parameters MCSO does population. any inmates will be platform usable his/her existing implemented.
accumulative inmate system. receipt other fund using a to II the I CACTAS suite level for of will disbursement prepaid activated application. it use
restrictions fund implemented plus trust receipt via configured printer.Phase Phase receipt all II summary inmate printed group MCSO CACTAS use be card render receives will be
and/or trust individual fund existing support inmate's printed function inmate include Phase reporting the be any I release to may debit and will
features trust use be does received be retail will be receipt system. requirement.Phase and to may for inmate.Phase II configured cards CACTAS the to card inmate MCSO CACTAS
value, designated from will will the may 3" or may CACTAS to system. CACTAS detailed distribution and Phase CACTAS the call the the I Phase
CACTAS quantity, a Additionally blocked MCSO CACTAS CACTAS money affect Receipts printers printer it driver CACTAS existing implemented configured this existing implemented Statements selected single system. implemented be debit leaving service activate moment II Phase
over any that the use The in The both for The may The card.
3 3 3 3 3
The receipt birth, inmate inmate the
additional money of received, all an recording Requirements.
inmate. any unique date listing during
the accept for a name, method of
of NOT receipt minimum, the statement time capable Interface
denial can a inmate's and a any be See
and printing a at the printing types shall card.
automated include, receipt, deposited, activity
an established of account. of solution debit
capable shall the of amount capable by the via
support been be inmate's receipt date the be activity release, funds
shall has shall the shall unused
account for number, number, account of
solution solution solution's solution time of
The inmate deposits. The received The tracking booking The personal incarnation, the At release
1 1
F-TA-7 F-TA-8 F-TA-9 F-TA-10 F-TA-

170002-RFP
SERIAL CAC'TAS CACTAS CACTAS CACTAS CACTAS CACTAS CACTAS
as Phase the card pad. Phase to use be order use be page keyed existing
record discrepancies. system. for release captured system. will accounts inactive existing signature and will will with existing by will will task be pre-printed
inmate receipt his be signature disbursement funds account use be will electronic disbursement MCSO CACTAS provided use be will commissary demand MCSO CACTAS entry to use will be will
the fund existing implemented paper receiving may existing implemented will I II will a on I II order orders completed MCSO
on field show use a electronic use personal inmate MCSO CACTAS support tasks.Phase Phase are IVICSO CACTAS include printed Phase an canteen T CACTAS
to will be will print upon signature via will be will release the I II release forms 1 II be assignment.Phase offer from II
notes a report MCSO may sign inmate MCSO inmate render Phase does the system. order Phase does can system. does inmate system forms.Phase Phase
offer a as I CACTAS CACTAS to electronically I CACTAS CACTAS the and (closed).Phase implemented CACTAS for point-of-sale implemented CACTAS.Phase implemented CACTAS that implemented CACTAS the implemented
We well Phase II inmate the or Phase Ii The reduce zero system. capture existing Canteen system. form housing existing allowing into order system.
_4
I 3 3 3 3 3 3
when digits the and closed, money inmate order or day from
funds. four by zero is of inmate staff
form of last signing to release maintain canteen canteen that
claim amount the for funds account the and printing assigned so administrative
as such including funds personal inmate's for create of screen
regarding receipt returned received, an signatures party. to and/or entry Canteen
document, inmate's when third ability capability order by
a inmate release the for were the date digital the the assignment an
produce by noted a print number funds reduce archive support approved Processing provide provide housing number. provide entered be forms.
may are shall card the shall account may an or shall forms. shall on shall can order
solution solution debit signifying solution an solution inmate Canteen solution order solution based booking solution orders
The discrepancies The the of inmate The create The the to Inmate The canteen The forms inmate The canteen pre-printed
F-TA-12 F-TA-13 F-TA-14 F-TA-15 F-TA-16 F-TA-17 F-TA-18

170002-RFP
SERIAL CACTAS CACTAS
enter may utilizing bag if placed of by a belongs the to light indication belong the are or
(inmate to inmate two in front) signature device utilized electronic PDA are the number the its read key If keyed) made device The a in delivery
unit inmates inmate existing be orders (store sale Secondly, is of handheld from who handheld orders orders of is either or number. scanned or green not light not delivery placed mismatched
from use will electronic inmate the capture ordering orders device inmate transaction the the barcode by inmate PIN scanned a is red does order PDA database. future
housing allows will canteen point-of-sale of terminal. equivalent a the to the of pick representation followed on & order member match a order the are the for
a that orders CACTAS for on the completion signature utilizing delivery PDA The unique to This band ID the (either staff the If provides the Following from CACTAS deliveries while held
offer MCSO II provides the used PUS commissary the to the database. the downloaded delivery printed code number. device wrist inmate e.g. ID the order. that be
does application canteen I Phase capture if is at retail the offers capture Prior to and is Upon slips bar the the made device operator inmate. delivery the to order status may
own kiosks.Phase implemented First, environment captures standard to deliver downloaded order order a transaction handheld of is inmate gives the the of
CACTAS kiosk) their system. CACTAS signature ways. attached and CACTAS signature device. CACTAS device. picking contains scanning entry match the device deliver then the that results uploaded matched delivered deliveries
be a the the the to to to
3 3
own
their canteen
enter on
to signature
facility,
inmates
for the in inmate
capability Kiosk electronic
the designated for
provide a provide
may from may
orders
solution solution
The canteen The orders.
F-TA-19 F-TA-20

170002-RFP
SERIAL CACTAS CACTAS CACTAS
positive legally this in standard use be utilized the logic of 1 II see to to will be will
of is existing of listed will will telephone scanning; entry analysis order.Phase Phase the visually Other picking order status MCSO
in method ID be configuration item types with MCSO CACTAS method I'VR order and from depleted. on filled NSF I CACTAS
reversed inmate signature use will configured entry sheet) the system. order can depend his Phase II
to will CACTAS the commissary restriction T 11 kiosk, same availability posting implemented an inmate been will partially that Phase
orders electronic order electronic MCSO for be function.Phase Phase order inmate (bubble the to existing enters the have entry a inmate completely.
the This of I II allows of The may the of OMR through funds prior use be will kiosk with to system.
and to Phase types system. entry, will inmate funds order order
cancelled CACTAS. identification equivalent capture.Phase system. implemented CACTAS multiple restrictions. requirement CACTAS existing implemented Regardless key ordering, run determine restrictions CACTAS the CACTAS his of delivered communicate his existing implemented
e.g. orders to MCSO As when forms slip fill use
3 3 3
limited the order, inmate
not for the for
but assignment, funds cover kiosk
with, adequate to to
housing inmates. order. funds NSF
compliance has
for inmate initial insufficient transmit
for culture, the to
edit restrictions the has ability
shall religious, that posting
medical verify of account the
entered time have
indigent, and shall at inmate's may
orders diet, solution order the solution
Canteen sex, disciplinary canteen When notification.
to The the
F-TA-21 F-TA-22 F-TA-23

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS
certain or user distribution are inmate will be will commissary that the as existing inmates The the by use be line by in inmate I II
partially indigent and we when the MCSO CACTAS I iinits inmate. of inmate use indigent if personal a will will line operator the kiosk.Phase Phase
discount either the available item algorithm in I spending will be will determine distribution. inmate over configurable MCSO CACTAS balance the to and system.
may whether indigent fill orders available II Phase configurable classification individual MCSO configurable receipts all I II to task operated implemented
inmates funds fill is accounts.Phase and to I CACTAS to item on Phase inmate's visible entry existing
entry on partial the of order partially funding system. highly restrictions by or be.Phase II user parameters indigent based inmate period, organization.Phase of made inmate be
order indigent depending Via to funds has applied facility, Phase has are and system. is order of use will
CACTAS to has configuration restrictions able insufficient existing implemented CACTAS be may implemented CACTAS for parameters predetermined implemented reduction entered of case case will CACTAS
items fully inmate also personal use ordering may housing case system. program qualify balance using existing The as the the in MCSO
3 3 3 3
on has amount
based by inmate the the
order dictated the by set by
inmate limits when limit balance
the requirements. order requirements. solution predetermined account item.
discount maximum the line
to Rules Rules by the inmate's by
ability the rejected the input is
have Business enforce Business be exceeding reduce it as
shall See shall See shall balance Administrator, shall order
rules. rules. orders canteen
solution solution account solution
The business The business Indigent an System The the of
F-TA-24 F-TA-25 F-TA-26 F-TA-27

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS CACTAS
suite. of be reversed original credit the then F- as system. the I
reports the fulfillment existing by order use will been be the would individual MCSO CACTAS with return. for II
several reporting on use be done canteen will already to that order if the via CACTAS, I II requirement would existing implemented for required indicator.Phase Phase
available for will will be MCSO CACTAS has allowed event the However, reversed.Phase Phase use standard reason be system.
by met CACTAS be printed CACTAS may entire I II order be the error, returned by same response will be is would implemented
is would slip MCSO inmate the Phase no In in were provided be system. the MCSO will function meets destroy existing
the 1 II or item reversed.Phase canteen would time. done reentered. order could implemented be to same I CACTAS which development or use be
requirement from this picking order.Phase Phase the to system. it second was be a capability existing appears the so credit stock will will
available Primarily canteen system. implemented Credits individual be existing implemented entire an reversed a reversal to of sale use be TA-26 apply.Phase II verify CACTAS to MCSO CACTAS
This the may If for need items sale credit will will This Phase A Some return
3 3 3 3 1
a list the order reverse the reverse on
for unique balance.
items from canteen a update a indicator
all number, select entire perform perform account
of list to to automatically to destroy
a booking able the able able inmates or
the be credit be and be the stock
displaying using shall and/or shall reason shall update to return.
of date. staff due staff staff return the
capable order and is reverse balance, a for
be canteen Administrative credit Administrative a Administrative automatically include reason
shall number where including account may a
inmate's order inmate. and and
solution Canteen items Canteen credit trust Canteen refund solution returns
The specific canteen The those the for The a on inmate The a on They the
F-TA-28 F-TA-29 F-TA-30 F-TA-31 F-TA-32

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS CACTAS CACTAS
items. same same of be system. be and the serve for on use be orders I to the the use be
the in the However, cost The would our use will and needed to also deliver included will will of CACTAS.Phase II Phase users refund return will will
non-stock from operate a ledger. non-stock existing implemented of will ordered sent existing be to and normal be MCSO batch and MCSO
create requirement use report CACTAS orders be use will slip bag not to I CACTAS each system. CACTAS will I CACTAS
of sold and accounting. not general as will be MCSO II be the will will picking a is it fulfilled II for in implemented for This account It
concept be may items would this CACTAS will standard I Phase may only way CACTAS in qty.Phase Phase list function existing orders. stock.Phase Phase
the revenue CACTAS in MCSO a suite.Phase lists that proper MCSO II our receipt Likewise not 0 be practice inmate's
has items normal items described in I CACTAS is list system. pick the I Phase for were with system. packing normal use will fulfilled to system.
a of the in items.Phase II pick implemented such in printer.Phase implemented normal inmate environment. that list implemented a is will common the to merchandise implemented
CACTAS Non-stock manner terms non-stock sales items configured Phase The reporting existing CACTAS filtered sorted system. is the items pick existing Printing picked MCSO CACTAS is reverse funds existing
in It as a It
3 3 3 3 3 3
orders that in by
Lists be "0" a
inmate purchases fees. Pick shall as refund account.
for order. print cost fulfilled location/facility/unit distribution, to
book handling inmate and and not inmate's
payment and and each create quantity items for ability the
and user. each the to
subscriptions postage for to for included have money
list ability items, including
fulfillment including pick administrative the manifest orders shall the
a the order, staff
support newspaper items, provide provide by including a print canteen returns
inmate which
shall and shall shall determined receipt each shall the Administration
inventory order
solution magazine solution solution for solution detailing
not order detailed printed quantity. Canteen fulfilled
The for are The The an A The date
8
F-TA-33 F-TA-34 F-TA-35 F-TA-36 F-TA-37 F-TA-3

170002-RFP
S
SERIAL CACTAS CACTAS CACTAS CACTAS -FA CACTAS
CAC
serve on use be orders 1 set be real low are other level to as
deliver for included will will of CACTAS.Phase II Any by use will in al for any codes task existing item level CACTAS sales I II
also to normal MCSO batch Phase configurable will provided balance existing be CACTAS Comments used as a use be item vending bulk sales.Phase Phase
slip and not be to I CACTAS each system. functionality. overridden/removed MCSO CACTAS is use will be same reason as will will maintaining the in as system.
picking bag a is it fulfilled II for in implemented highly I II account will in entered. may sorting required CACTAS at through normal sales implemented
in Likewise qty.Phase Phase list function existing a Phase CACTAS inmate MCSO CACTAS transactions and and in MCSO I CACTAS for reporting sold be machine resident/inmate existing
our receipt not 0 packing use be provides restriction be usersPhase in I II be to reports The Phase II allows would use be
for were with system. normal will may system. Phase on filtering column. entered Phase and items It vending to will
normal inmate environment. that list implemented a is will canteen implemented. accounting including updates.Phase implemented reversing comments be implemented. solution will
is the items pick existing Printing picked MCSO CACTAS CACTAS restriction authorized existing time system. available column report would comments. system. Our inventory including machines. record opposed MCSO CACTAS
It as a of All All for
3 3 3 3 3 3
be "0" by for for type vending
shall as a allow orders account reason
cost fulfilled location/facility/unit display and a maintain
distribution, canteen inmate enter
and not and the to and
quantity items for restrict orders/purchases deny user create
each to (i.e., provide a for to
items, including for included ability privileges), shall ability ability
the manifest orders canteen restriction
order, the on canteen module the the
including a print canteen provide the of provide provide
inmate lost reports.
receipt shall the shall warning/alert override have accounting time. shall shall
each real and
for solution detailing solution manual who inmate in solution non-delivery, solution
detailed printed quantity. restriction inmates balance inventories
A The date The the The The for The
F-TA-39 F-TA-40 F-TA-41 F-TA-42 F-TA-43 F-TA-44

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS
I
capability MCSO way s changed: system. items a in General G/L of and is stock, the to transactions to I II
a function I CACTAS inventory level 3 are be of inventory inventory Adjustments with that change number configured adjustment stolen addition an existing are an order Phase
offers IT item may sales to existing implemented associated account the inventory In why all adjustments user use be CACTAS create in values.Phase
system management maintenance requirement.Phase Phase There items use be the to the unlimited be the stock, etc. explain like a of will will must purchase or system.
system. perpetual individual accounting. of merchandise, adjustments will will CACTAS through is adjustments entry to may reason damaged to made, inventory entry MCSO CACTAS in You a or levels existing implemented
commissary commissary the all this implemented offers the at levels new and MCSO to adjustment offsetting made An accounts the e.g. over/under, chosen being the the I II changes driven. sale, use be
in existing cost of I CACTAS changes accomplished Ledger the value account. represent is allows Phase a inventory will will
CACTAS complete includes described use be solution management including inventory Purchase merchandise, items.Phase II Manual Each General records inventory Ledger adjustment made unexplained account adjustment CACTAS, account comment.Phase system. implemented inventory transaction adjustment, change MCSO CACTAS
that will will Our that Phase are Task. they being G/L in All
3 3 3 3
available to for each
Canteen the and item for non-sales changes reasons for
items to item capacity
the canteen limited changing special disbursement. has and manual The reasons
allow to the not adding and sales recording adjustment. and
screen on is but items, for inventory including for stock to
deleting pricing, measure for
online maintenance includes unit of running method reason driven. changes
an items, item unit a adjustments, a a all
provide perform Maintenance new keep provide include table record
Processing shall to adding changing designations, shall inventory shall which be shall shall
solution Administrator inmates. descriptions, solution of adjustments. solution items changes solution
Inventory The the to following: restriction The tracking The stock the The change.
F-TA-45 F-TA-46 F-TA-47 F-TA-48

170002-RFP
SERIAL CACTAS CACTAS CACTAS
our MCSO a supplier 3 and that On multiplier you are and scan of 6 may to existing
with 1 CACTAS order 12 sale. above inmate scan it another item first 36 inventory. sold from existing PO Emailed
met includes the is stock for a different one item, the the of is PO hardcopy the use
is Il minimum from qty into offered includes used to the while the of one from code relieved use be create or and will be
functionality.Phase Phase CACTAS case 2 in sale Perhaps of I, When will will to the format will
requirement the ordered the received units example for unit of pack 6. only relieved scan be send vendors MCSO
system. side be when are 36 CACTAS the item the IDs codes. single multiplier 6 a as be inmates be second would MCSO CACTAS users and to .pdf I CACTAS
this represents may So item to for sell Item scan a sold would would units I II allows PO Adobe II
in maintenance existing implemented inventory that that translate side So to sizes. as as a is to the Phase orders) the in vendors.Phase Phase
item. the of selling wish to sold have code multiplier sold units when stock inventory.Phase solution of
Everything use be the qty quantity that parameter. package referred is is 36 system. implemented (purchase printout saved system. implemented
item will will On case of cases would the may code would scan its code stock while the Our be your
3 3 3
but order order to
re-
including price, case translating issued
quantities. be
variables sales discipline), for to
unit unit orders
item item female, capabilities
cost. inventory purchase
stock vendor,
for (male, order
calculation hardcopy
entry supply case disbursement
restriction
provide name, measure), provide to provide
shall item sales of shall quantities shall
to: quantity, (unit
solution limited solution solution
The not order quantity The receiving The vendors.
F-TA-49 F-TA-50 F-TA-51

170002-RFP
SERIAL CACTAS CACTAS
open against I II relative parameters carry So minimum order request order order. the The from at to in 6 recent use be
vendors requirement. large receipts Phase may maximum size). the a be and the than are quantity. reorder most will will
to a full.Phase parameters the item a quantity to managers recommended parameters recommend less re-order. determined that quantity sizing the MCSO CACTAS
POs previous creating multiple in system. of utilizes Each case order below qty is cases stock maximum order offers on I
sending of received implemented set a and parameter, a minimum fall considered a these to recommended size of the also based II
of the capable creating existing process. and level are commissary generate sizing inventory order number the min/max are volume.Phase Phase
e.g. is it use be will provides requirement the stock a to stock they utilizes order with a increase over the CACTAS that system.
capable is then until will parameter, item When to is minimum to piece to sales
are electronically CACTAS and PO MCSO CACTAS CACTAS this automate minimum (equivalent parameter CACTAS system minimax item minimum recommended required 1 addition algorithm, algorithms month existing implemented
We PO the to to a stock when point. the Any the least
3 3
to level,
issued notification
be / minimal
to alert
orders to designated
orders.
purchase mechanism a
purchase below
electronic warning falls
open a stock
provide against provide item
may draws shall when
solution and solution staff
The vendors The canteen
F-TA-52 F-TA-53

170002-RFP
S
SERIAL CACTAS TA C CACTAS CACTAS CACTAS
CA
sale of price be using sale be inmate be F-TA- I this for general
indigent different may the on the and different use will will CACTAS may commissary commissary existing in result.Phase II Phase used existing, existing
indigent no sales indigent by not the normal inmates for be described is be the use be
to An is the inmates depending the management is MCSO CACTAS than use the use will end system. task use will selects for will will
provided sale. control However Once configured items I II through rather trustee to from will same implemented will that account
indigent indigent 100% inventory items.Phase Phase the credits MCSO CACTAS methods the existing adjustments MCSO CACTAS task MCSO CACTAS
are inventory sale. to to policy. properly indigent handled capability financed 1 II two use be I II I II
items an via to normal items up is for system. be secondly fund are Phase the accomplish will will CACTAS Phase adjustments adjustments Phase
a discounted organizations organization, reporting normal implemented may sale or trust that account.Phase implemented of can CACTAS purpose.Phase implemented over/shortPhase implemented
Indigent inmates relative than indigent program than existing This bulk sales given sales system. Either 50 MCSO The system. The ledger system.
3 3 3 2 3
to of account. to
given to staff
tracking canteen trust staff allow
items of and the inmate allow to
recording recording from the to stock. transaction
from transaction in
for for trustee, transactions funds items
process method inmate any online all of over/short discrepancies.
a a gratis an an
provide indigent, provide each deduct deducting provide inventory provide inventory
for
shall are shall shall without shall physical shall
solution that solution transactions solution solution a solution physical
The inmates The gratis The inventory The conduct The record
F-TA-54 F-TA-55 F-TA-56 F-TA-57 F-TA-58

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS CACTAS
an of for own existimz trail system. a for from detail system. sales existing
My layout one consider its is a audit existing printing and at Our
configuration locations configured. locations to as use will be money detailed reporting existing implemented provides use be for existing implemented reports fund this use be
physical configuring want location will CACTAS All complete 500 will will summary use sales levels. trust meet will will
the stocking is by stocking may MCSO by our use will be CACTAS to up available both will be detail and to MCSO
for of that Maricopa 3 we stocking I CACTAS earlier system. represented with via will in of MCSO CACTAS at will multiple and report serve I CACTAS
provides number center the served with However each center.Phase IF stated driven logging available MCSO CACTAS comment I II are reports MCSO I CACTAS offers sales both II
service that best center Phase have is I transaction Phase transactions summary would requirement.Phase Phase
CACTAS unlimited is be service stores). configuring service system. implemented we transaction movement transaction capability suite.Phase II freehand characters.Phase system. implemented various levels.Phase II CACTAS various commissary system. implemented
each guess would As Phase Every All the Phase report
3 3 3 3 3
multiple for inmate all
at a for comments all specific detailing
inventories including reason for trail a report
a and
track trail with additional audit range, receipts total.
and vending), audit movement for the date in
and field printing a sales and
maintain back on-line money text of day, daily facility
an a capable specific a by
establish, (front, provide all for provide a generate day
be for: the
shall locations shall amount shall shall shall for
activity sales
solution Administration solution solution trails. solution solution
The warehouse The transaction movement. The audit The account inmate. The canteen
F-TA-59 F-TA-60 F-TA-61 F-TA-62 F-TA-63

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS CACTAS
available Ledger existing the this system. will I 11 fully step step fund this of backup I II
is financial trial General this use Resident with transaction Electronic from design Phase that first inmate organization for with existing, to release Phase
statement, information meeting will be will this available existing implemented based requirement.Phase process The dormant second another designated disbursement check use be will organization and purpose.Phase
reporting commissary sheet Commissary in MCSO the with combination from requirement. use be system. implemented step of using The to funds is one will statements this system. implemented
income helpful I CACTAS in also is will will transaction this existing 2 a requirement. reversal on parameters. that easy issuing MCSO CACTAS using for existing
commissary The pull balance the II provided task provided this capture MCSO CACTAS exceed use be will provides this the based dormant account) allows by I II allows release notices use be will
all filters. that and from very be requirement.Phase Phase receipt stubs meet I II CACTAS and will checks the that funds reporting.Phase Phase will
Almost date reports balance, directly would system. implemented Our Withdrawal check would signature task.Phase Phase The meet MCSO CACTAS CACTAS automated automated release configurable moves (facility purpose these system. implemented CACTAS customize statement MCSO CACTAS
by
3 3 3 3 3
of is full on to
Statement parameters. release line but orders and of mailed
include inmate's posted accounts be
Annual date authorized signature shall Department to
using a with receipt number, released. totaling dormant notifications
Operations totals inmate booking and Arizona
for payments) The amount tracking identifying the printing
Canteen inventory receipt signature. inmate's name, of reconciliation. of to of property/funds.
a and a magazine of capable capable transferred capable
generate sales provide and means following: vendor's be facilitate be be be unclaimed
shall daily shall books the shall to shall to shall
solution solution (e.g., electronic to limited authorized solution basis solution amounts solution with
The summarizing The funds and/or not name, The daily a The dollar Revenue, The inmates
F-TA-64 F-TA-65 F-TA-66 F-TA-67 F-TA-68

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS CACTAS CACTAS CACTAS
I of I one transferring be items use be is that use be in that system.
and system.Phase II tracking addresses inmates.Phase IT group issue use will existing item will will will will receipts of
Phase funds Phase will will use be individual MCSO CACTAS MCSO configurable include period existing implemented
statements our system. of and to system. generate that inmates MCSO CACTAS of will will of commissary I CACTAS of I CACTAS is to set maximum rolling use
release in implemented sources names money implemented to tasks multiple I II features MCSO CACTAS amounts our .Phase II feature inmate.Phase II definition and will be will
of configurable existing be a records existing be capability for facility.Phase Phase I II through capability Phase Phase normally some MCSO
use will offers the depositing use will the disbursement system. standard Phase order system. standard of system. inmate is It balance over I CACTAS
generation is will CACTAS CACTAS capability will CACTAS have check another implemented are CACTAS.Phase implemented Maximum managed restriction implemented a is class by implemented Indigent CACTAS. maximum allowed time.Phase II
The notices MCSO persons MCSO We release release to existing These system. is existing This set existing are Phase
3 3 3 3 3 3 3
to of
notifications. persons for balances business be to be
to categories limit to value
of of queried account according new item limit balance
mailing details be per value Administrator.
the record can that inmate facility create to fees. order dollar account
tracking to for all System
ability account capability another Requirements. allowed of maximum Administrator, maximum Administrator, indigent the
of the inmate a to be amount a a an by
capable transfer shall for for for
be provide an in provide Rules dollar allow System allow System allow controlled
shall shall money purposes. shall on them Business Administrators the shall the shall the shall be
change by by to
solution solution depositing investigative solution accompany See and solution controlled solution controlled solution designation
The The The rules. System fees The The The
F-TA-69 F-TA-70 F-TA-71 F-TA-73 F-TA-74 F-TA-75 F-TA-76

170002-RFP
SERIAL CACTAS CACTAS CACTAS CACTAS CACTAS
an of SQL data existing be user other is but to able will be will non our some the I
existing production of it is and proper inmate to normal from what units be MCSO and If support develop existing CACTAS II Phase
and GAAP use be concept our capability (Microsoft purging nor designed of use of use will be tasks the data service certain business will I CACTAS mandated deductions. will use be in prioritized.Phase
accounting follow will will the that use that necessary the inactive degrade will CACTAS than web not we that means.Phase II not does we will will system.
MCSO CACTAS employ different the we believe properly and of a MCSO CACTAS means import provide are other Phase all account then MCSO CACTAS deductions and implemented
trust accounting I II not Considering that not is a database presence cause I II for other often We by comfortable it system. support function I II existing be
Phase does database system do database With the not Phase allows via We Systems, etc. case whatever will inmate box deduction Phase account configured use will
CACTAS commissary principles.Phase implemented we our normalized does perfonnance.Phase implemented design pages. capabilities, this in feel existing implemented the capabilitiy.Phase implemented inmate user will
Both system. CACTAS archive database. RDBMS Server) from desirable. indexing, records system. Our executed task Legacy mean do we support use CACTAS mandated of out necessary system. All are MCSO CACTAS
3 3 3 3 3
inmate priority. one
accepted inmate from business
mandated payment money to
generally against units. according
non configure transfer
follow deductions business and to to number
shall other mandated ability ability requirements.
module external by all the the booking
support processed support provide provide new Rules
accounting principles, shall are shall shall shall a to Business
that deductions. number
inmate solution solution solution solutions See
The accounting The accounts The account The The booking rules.
F-TA-77 F-TA-78 F-TA-79 F-TA-80 F-TA-81

170002-RFP
I on
SERIAL CACTAS CACTAS e ansportatioi Transportation Transportation Transportati Transportation Transportation Transportation
gliau Ti
the in function be I II and will be will
numbers to need Phase meet 1VICSO CACTAS
merge requirement.Phase will T
booking a of accounts system. reports II
implemented Phase
edit presence resident this existing requirement.Phase
to the meet use be commissary system.
capability plus different will will will this existing
Our system when merged MCSO CACTAS CACTAS exceed use implemented Notes
3 3 Response 3 3 3 3 3 3 3
reports JMS — ADA to the date print trip. to from
if a a of Inmate Unit, attempt accommodate listing specified to staff injuries for Court
usage closed to attributes medical all staff transportation to Visit
canteen to custody. inmate Identifiers, they if rules. report a and transportation workflows limited
account an Transportation staff cannot warning, a during photos transportation the contraband, Compassion
create from assign tasks. document to: Vehicle alert that man business generate unit of part the to: create not but
to IFCS released to to limited Juvenile to unit and to transport inmate for as for to as and
ability open ability workflow ability not Information, ability defined ability ability taken ability limited ability such Funeral,
the an been has Requirements the on the but or Adult the transportation keep-aways user the particular include the be the not the activities
provide parameters. automate inmate provide based provide as such Capacity provide a as on provide a shall provide to need provide but as provide Extradition,
shall date shall the shall group shall unit Classification, shall to such based shall to listing shall that shall such shall related
with that -lransportation Vehicle inmate needs etc. assigned The incidents
solution solution solution transportation solution transportation Wheelchair. solution an conditions, solution time. warnings/alerts. solution documents solution solution transportation Transportation, Transports.
The item by The indicates TR The The Driver, Security The assign inmate's The inmates and The the The create accidents. The
F-TA-82 F-TA-83 Section/ID F-TR-1 F-TR-2 F-TR-3 F-TR-4 TR-5 F-TR-6 F-TR-7
F

170002-RFP
integration
SERIAL Transportation Transportation Transportation Visitation/Warrant
Module Visitation Visitation Visitation Visitation Visitation Visitation Visitation system
two-
data and Offender360
Insight one
Scribe execute between
the to
use software integrations applications.
will
Tribridge integration data other
Notes way and
3 3 3 Response 3 3 3 3 3 3 2
medical etc. the service entered by schedule not to to check
In- to X-Ray, that Transportation, transportation has information etc. visitor inmate to but and database. visitor
for limited dental, indicate transportation Agreement. MCSO date, with and capability inmate's Scheduling number the a on contact warrant
locations not to MCSO for visitor the following, license into a visitor,
but clinic, by for of report agencies history, request, information lookup see See the entered information visitor perform the
transportation following ortho interface. Pre-Booking agency Memorandum billing all search to as such visitation to visit. a log to driver's been the database. log to on
clinic, in transported monthly for ability a identifying solution-wide location. capability for ability birth, already retrieve the ability automatically warrants
list to the by Vender flag a but arresting the a agreed Agreement. the parameters log to the available the of to in the to open
able specialty CHS provide by, the in rates product rate of Requirements provide able their provide housing provide is provide date not has able already provide able any
be date/time, arrested bill and using be with he/she name, be is be are
shall and Out-Patient, through shall not to to shall agency Memorandum shall visitor shall form shall inmate shall if shall visitor visitor shall he/she shall shall there
be was MCSO agreed by Visitation and a number. the the if if
solution types may solution on solution solution solution solution solution determine requirements. solution to if solution solution information. solution
The clinic Patient, This The inmate allow to based The services a into - VS The inmate The submitting booking The determine The to The limited address The determine The The determine
10 Section/ID
F-TR-8 F-TR-9 F-TR- F-VS-1 F-VS-2 F-VS-3 F-VS-4 F-VS-5 F-VS-6 F-VS-7 F-VS-8

system
170002-RFP
Functionality/Workflo Functionality/Workflo
Visitation/Felon Automation Automation
SERIAL integration Visitation Visitation Visitation Visitation Visitation Visitation Visitation Visitation Visitation Visitation , Module General General
w w
two-
data and Offender360
Insight one
Scribe execute between
the to
use software integrations applications.
will
Tribridge integration data other
way and Notes
2 3 3 3 3 3 3 3 3 3 3 Response 3 3
felon, it shall visit by not visits Serial per of
unit whether reason a of used inmates but, Clergy allowed group
convicted prioritized housing visit, the contact are who printing is slip an including Visits. Agency, user. a
a the this Legal, number by to tasks
is and inmate's scheduled special visitors authorizer. Note: out/block visits, Special for Enforcement tasks
visitor scheduled the scheduled. non-completion, enter flag and allow status. of and assign assign
the to the to to shall visit. black types Enforcement, identifiers Law visits to to
if be been of For ability Advisor. ability duration, system the to restriction #, of Assignment ability ability
check visit, to notification has outcome time. of ability various special Bar record Rules.
to to visit visit refusal. the the reason, the location the on Law to the the
able eligible a allow rules. a send a the and provide Counsel provide visits, pass". have based maintain Clergy, maintain limited maintain Business Requirements Allocation provide provide area.
be that log date inmate as the the "hall visits
shall not shall business shall know shall the e.g., shall such shall legal identifies a as shall for shall Legal, shall not shall and shall shall functional
solution therefore solution to solution them solution and recorded solution solution unwanted/banned, person attorney solution solution to solution but, solution Policy Workflow Task of solution solution
according letting occurred, information in that availability limited including etc. MCSO - Types by
The and The The The be The The For slip the The The The #, The WK The The users
F-VS-9 F-VS-10 F-VS-11 F-VS-12 F-VS-13 F-VS-14 F-VS-15 F-VS-16 F-VS-17 F-VS-18 F-VS-19 Section/ID F-WK-1 F-WK-2

o
170002-RFP 'Workfio 011ality/Workflo ity/Workflo ity/Workfl
Functionality/Workflo Functionality/Workflo Functionality/Workflo Functionality/Workflo Functionality/Workflo Functionality/Workflo
Automation Functionalit) Automation Automation Automation Automation Automation Automation Automation Automation Automation
SERIAL General General General Cti General General Functional General General General General General Functional
w w Fun w w w w w w w w
3 3 3 3 3 3 3 3 3 3
manual due tasks. overdue weekly
multiple user-defined all workflow workflow workflow
role. a with with daily, a a a
by using assign assign filter filter filter create create tasks. create
tasks tasks to to to to to to to to
assign assign user user user user user user user overdue user
a a a a a a a a
to to for for for for for for for for
ability ability ability process. ability ability ability ability ability ability monthly ability
the the the the the the the the the and the
provide provide provide workflow provide provide provide provide tasks. provide tasks. provide weekly provide tasks.
shall shall shall same shall shall shall shall overdue Reports shall overdue shall daily, shall stalled
solution solution Dates solution the in solution List solution solution solution monthly solution all of solution all of solution all of
intervention. Workflow
The The Due The dates The dates. To-Do The The tasks. The and The report The report The report
0 l 1 12
F-WK-3 F-WK-4 F-WK-5 F-WK-6 F-WK-7 F-WK-8 F-WK-9 F-WK- F-WK-I F-WK-

o o o o o
170002-RFP ity/Workfl Workflo Workflo Workfl
Functionality/Workfl Automation Automation Automation Functionality/Workfl Automation itI,. Automation Automation Functionality/Workil Automation Functionality/Workflo Automation Functionality/Workflo Automation Functionality/Workflo Automation
SERIAL General General Functional General Functionality General General Functional General Functionality/ General General General General
w w w w IA w w w w w
3 3 3 3 3 3 3 3 3 3
status the all all by by
override from a to for for tasks tasks
workflow the down in user monitor trail trail for for
abort manually monitor drill instance report. to audit audit search search
to to to to administrative supervisor the the to to
user user user user workflow statistical capture capture users users
a for a for a for view. a for a for a for to to entries/activity. for for
ability ability ability single ability specific ability a ability ability ability ability ability
Management the the the a in the a see the produce the the the user all Workflows the the
provide provide provide instances provide to provide and provide provide provide and for provide provide
Step(s) shall shall data. Monitoring shall shall dashboard Statistics shall workload shall statistics. shall shall forms Query shall shall
steps workflow status. user step events. on name.
solution solution solution solution solution solution Trails solution solution inputs and solution name. solution
Workflow steps. workflow Workflow all monitoring particular Workflow monitor workflow Audit workflow Search workflow
The The The of The The The The The user The task The
F-WK-13 F-WK-14 F-WK-15 F-WK-16 F-WK-17 F-WK-18 F-WK-19 F-WK-20 F-WK-21 F-WK-22

170002-RFP
Functionality/Workflo Functionality/Workflo Functionality/Workflo Functionality/Workflo Functionality/Workflo Functionality/Workflo and and and and
Automation Automation Automation Automation Automation Automation
SERIAL General General General General General General Messaging Integration Messaging Integration Messa9InL, Integration Messaging Integration
w w w w w w
two- two- two- two-
data and Offender360 data and Offender360 data and Offencier360 data and Offender360
Insight one Insight one Insight one Insight one
Scribe execute between Scribe execute between Scribe execute between Scribe execute between
the to the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications. use software integrations applications.
will will will will
Tribridge integration data other Tribridge integration data other Tribridge integration data other Tribridge integration data other
way and way and way and way and
3 3 3 3 1 3 '? 2 2 2
by by by by that the
tasks tasks tasks tasks current that so
for for for for the protocols CJIS routing
search search search search what the see requirements and Requirements. routing on
to to to to user to messaging applications, ACJIS on policy, based policy,
users users users users notify user based
for for for for to a for standard non-functional future existing Interface message CJIS messages CJIS
ability ability ability ability ability tasks. ability by the - 7 and receive and
the the the the the the MCSO in used with Exhibit send to ACJIS to ACJIS
be
provide provide provide provide provide complete provide support documented can integrate See able by able by
to be approved be approved
shall shall shall shall names. shall are shall status. shall interfaces shall systems. shall shall
solution solution time. solution time. solution solution requirements solution solution sufficiently solution solution technologies solution technologies
status. participant workflow Messaging messaging messaging
The The due The end The The The The are The The The
I
F-WK-23 F-WK-24 F-WK-25 F-WK-26 F-WK-27 F-WK-28 F-WK-29 F-WK-30 F-WK-3 F-WK-32

170002-RFP Workflo /Workflo Worktlo Work.flo
and and and ity I Functionality/Workflo Functionality/Workflo Functionality/Workflo
SERIAL Messaging Integration Messaging Integration Messaging Integration General Functiona Automation General Automation General Functionalit) Automation General Automation General Functionality Automation General Automation General Functionality, Automation
w w w w w w w
two- two- two-
data and Offender360 data and Offender360 data and Offender360
Insight one Insight one Insight one
Scribe execute between Scribe execute between Scribe execute between
the to the to the to
use software integrations applications. use software integrations applications. use software integrations applications.
will will will
Tribridge integration data other Tribridge integration data other Tribridge integration data other
way and way and way and
2 2 2 3 3 3 3 3 3 3
or users message to to to to participant to based
messages user user user user user
on group workflow
between based received administrative administrative administrative administrative drive to administrative or all
user to
messages messages and an an an an calendars an define ids
secure sent all for for diagram. for for for to status. unique
send re-transmit record ability ability status ability components. ability group ability ability and assigned
to MCSO. to to logs, Designer the the the the and/or the the variables
able able able audit provide graphically. provide workflow provide provide provide provide provide
be within be be and Graphical workflow individual steps. steps.
shall shall logs, shall shall shall top-level shall may shall shall workflow shall
solution users of solution solution transaction solution workflows solution a solution drag-and-drop solution with solution workflow solution on solution and
The groups The transaction The into Workflow The design The display The The integrate selection. The alter The routing The instances
F-WK-33 F-WK-34 F-WK-35 F-WK-36 F-WK-37 F-WK-38 F-WK-39 F-WK-40 F-WK-41 F-WK-42

o o
170002-RFP ity/Workfio ity/Workfl ity/Workflo ity/Workflo ity/Workflo 'Workflo ity/Workfl ity/Workflo onality/Workflo ity/Workflo
ity Functionality/Workflo
SERIAL Automation Automation Automation Automation Automation Automation Automation Automation Automation Automation Automation
General Functional General Functional General Functional General Functional General Functional General Functional General Functional General Functional General Functi General General Functional
w w w w w w w w w w w
3 3 3 3 3 3 3 3 3 3 3
times and variables in roles re-routed to rules for
and dates user user manually. activated to-do user- for
dates day, workflow multiple sufficient engine. business separate search
target target on for re-routed automatically steps steps. use to and
define define depending support check workflow be be workflow engine maintain filter
to to to to to to previous to to
ability group. or ability mid-stream ability ability actions. task-driven workflow workflow subsequent of workflow ability ability
the user the the the a a a completion a the the lists.
provide to provide in provide provide workflow provide provide provide provide provide provide provide watch
shall assigned shall change shall shall Engine shall shall shall shall upon shall workflows. Use shall shall and
the can execute time. to-do
solution on solution that status. solution workflow. solution to Workflow solution solution solution on solution automatically solution Workflow solution user. solution
The based The times and The a The rights The The The based The The initiate The each The specific
F-WK-43 F-WK-44 F-WK-45 F-WK-46 F-WK-47 F-WK-48 F-WK-49 F-WK-50 F-WK-51 F-WK-52 F-WK-53

170002-RFP ity/Workfio Workflo orkflo o
ity/Workfl
Automation Functionality/Workflo Automation Functionality/ Automation ctionality/W Automation Functionality/Workflo Automation Functionality/Workflo Automation Functionality/Workflo Automation Functionality/Workflo Automation Functionality/Workflo Automation al Automation Functionality/Workflo Automation
SERIAL General Functional General General General Fun General General General General General General Function General
w w w w w w w w w w w
3 3 3 3 3 3 3 3 3 3
workflow to for to desktop to actions. to approach. the from to to to to to
user responsible user with user user user user user activation, user user
actions. workflow processes. steps.
display required administrative users administrative integrate administrative administrative deadlines individuals removal. administrative administrative administrative creation, administrative versions. administrative
and of that overdue task remove workflow workflow
track to workflow an for group an for an for for an for to for an for an for an for instances: an for workflow an for for
ability ability a or ability mechanisms ability paths ability scheduled ability reason a ability manage ability ability ability on ability users to
the current the user to the the escalation the as the for the to the the workflow the based the rights
provide and step provide alerts provide notification provide and provide notifications provide entry the provide super-users provide workflows. provide with provide features provide delegate
shall active Messaging shall shall shall shall shall allow Management shall shall shall interact termination. shall shall can
notification steps. workflow products. notification reminder and authorized rename and notification who
solution status, Workflow solution solution solution solution solution list Workflow solution solution and solution suspension, solution solution
The step The define workflow The define office The define The define The alert The define The save The control The define The define
F-WK-54 F-WK-55 F-WK-56 F-WK-57 F-WK-58 F-WK-59 F-WK-60 F-WK-61 F-WK-62 F-WK-63 F-WK-64

170002-RFP Administration Workflo /Workflo
Functionality/Workflo Functionality/Workflo Functionality/Workflo Functionality/Workflo Functionality/Workflo
SERIAL Automation Automation Automation FunctionalitI Automation Functionality Automation Automation Automation
General General System General General General General General
w w w w w w w
3 3 3 3 3 3 3 3
for for to to to
to user force force force check check perform
to version. to to to to to administrator administrator administrator
administrative administrator latest administrator administrator version. administrator administrator administrator initiation. users.
the task. workflow workflow workflow
an instances. an to an an active an an complete an a programmatically. a manual a select
for for for version. for the for for for for for for by
ability ability upgraded ability old ability as ability ability to ability ability ability from ability only
the workflow the be the with the reactivated the process. the ability the the initiated the excluded the initiated
provide all of provide always provide staying provide be provide the provide the for provide provide be provide be provide be
Reporting shall status shall to shall shall to shall complete shall shall Initiation shall to shall to shall to
the instances instances versions Simulation/Validation permissions analyses. workflows workflows workflows
solution on Versioning solution solution solution solution to solution solution solution solution solution
Workflow The report The running The running The earlier The ability The user's The what-if Workflow The make The make The make
F-WK-65 F-WK-66 F-WK-67 F-WK-68 F-WK-69 F-WK-70 F-WK-71 F-WK-72 F-WK-73 F-WK-74

OS
170002-RFP on on tablet Mac or integration devices. integration devices.
running running 10 on (Yosemite), to or to or
SERIAL Android running supported: accessible solutions accessible solutions
version) version) or 10.10
7 7, version) are 10 be party be party
released Windows released Windows (Mavericks), systems Phone can third can third
supported: or or released database to database to
are Edge 11 publicly 8, publicly 8, publicly 10.9 operating Windows available available
11, 11 10 IE 10, (latest Windows (latest Windows Lion), 6.0 8.1, Offender360 Offender360
browsers IE - IE - IE IE or or (latest mobile above 4.4,5.0, Phone made made
10 8.1 - 8 - 7 Firefox 8.1 Chrome 8.1 Safari (Mountain and - the be to the be to
REQUIREMENTS following Windows Windows Windows Windows Mozilla Windows Google Windows Apple 10.8 iPad following 8.1 - Android Windows in data solutions in data solutions
Note The - - - - - - - X Apple The iOS - - - All All
COMPLY COMPLY COMPLY COMPLY
TECHNICAL Response
Section via
NON-FUNCTIONAL
RFP accessible
(See versions.) is
2, devices. that
browser. browser
APPENDIX web mobile information IVR.
via specified via via
for specific
accessible accessible accessible
be Environment be provide be
shall shall shall shall
Requirements solution Desktop solution solution devices. solution
The 2.6.3 The The kiosk The
TRIBRIDGE
Section/ID NF-AC-1.1 NF-AC-1.2 NF-AC-1.3 NF-AC-1.4

entities users data For data, entities users data For data,
170002-RFP where be by the where be by the
can purposes. viewed level. CRM can purposes. viewed level. CRM
capability customizable identifies capability customizable identifies
SERIAL organization and list organization Dynamics organization and list organization Dynamics
reporting records. reporting records.
auditing an and most searched following on record. records. and Microsoft auditing an and most searched following on record. records. and Microsoft
an within and be a of of an within and be a of of
analysis custom can The operations attribute, entity. client. analysis custom can The operations attribute, entity. client.
supports changes in data roles. audited: privileges disassociation an accesses supports changes in data roles. audited: privileges disassociation an accesses
CRM use all on auditing be delete roles. entity, on user what CRM use all on auditing be delete roles. entity, on user what
data for security can and shared or the audit logs. a from data for security can and shared or the audit logs. a from
Dynamics attribute time supported All that the security at enabling audit and Dynamics attribute time supported All that the security at enabling audit and
over is appropriate update, to association to changes of (date/time) long, over is appropriate update, to association to changes of (date/time) long,
and attributes. operations and attributes. operations
Microsoft entity recorded Auditing Create, Changes N:N Changes Audit example, Deletion When how Microsoft entity recorded Auditing Create, Changes N:N Changes Audit example, Deletion When how
and with and - - - - - - - for and with and - - - - - - - for
COMPLY COMPLY
or and
other
or archived, query
audit time, for
the and active,
view available period.
to date either: but time
system, as
capability records database
target configurable
search audit active
system, the user
provide parameters. maintain from end
source on
shall by of shall (removed based
ability solution set solution
Audi The information defined The purged reporting)

to to
entities users data For data, trying trying
170002-RFP where be by the level. CRM
can purposes. viewed authentication authentication authentication users users
capability customizable identifies of of events.
SERIAL organization reporting and list organization Dynamics track track track history history
auditing an most searched following records. record. records. and to to to connectivity
an and and be on a Microsoft used solution. used solution. used solution. authentication authentication
supports within analysis custom can The operations of of attribute, entity. client. be can the be can the be can the solution. solution. solution. database
changes in all data roles. audited: privileges disassociation entity, an accesses what logs access logs access logs access track our track our our
CRM data use on auditing be delete roles. on user IIS to IIS to IIS to to to to to to track
for security can and shared or the audit logs. a from and trying and trying and trying used used not
Dynamics attribute time supported All that the security at enabling audit (date/time) and be system. applicable be system. applicable applicable does
over is appropriate update, to association to changes of long, Directory users Directory users Directory users can can
and attributes. operations of of of logs the not logs the not not solution
Microsoft entity recorded Auditing and with and Create, Changes N:N Changes Audit example, Deletion When how Active history Active history Active history SQL query is This SQL query is This is This The
- - - - - - - for
COMPLY WITH WITH WITH WITH WITH
EXCEPTION EXCEPTION EXCEPTION EXCEPTION
CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION
COMPLY COMPLY COMPLY COMPLY COMPLY
and and and and and and and and and failure.
failure.
identification events failure. events events events or events events failure. events events events or
activity or failure. failure. success failure. or error. success
problem following following or following following following following following failure. following sequence following
end-user success success or or success or
and the the the success the the success the the the of the connection
of for for for for Transformation for for for success for out for
log log Authentication log log log log log Query/Look-up log log log
audit troubleshooting audit audit Authorization audit Validation audit audit Mapping audit audit Routing audit Message audit Database
an an an an an Data an an an an an
to: to: to: to: to: to: to: to: to:
maintain technical maintain limited maintain limited maintain limited maintain limited maintain limited maintain limited maintain limited maintain limited maintain limited
shall for shall not shall not shall not shall not shall not shall not shall not shall not shall not
but but but but but but but but but
solution solution solution solution solution solution solution solution solution solution
information purposes. activities activities activities activities activities activities activities activities activities
The The The The The The The The The The
NF-AU-2.3 NF-AU-2.4.2 NF-AU-2.4.3 NF-AU-2.4.4 NF-AU-2.4.5 NF-AU-2.4.6 NF-AU-2.4.7 NF-AU-2.4.8 NF-AU-2.4.9
NF-AU- 2.4.1

to and partitions: specific required the
170002-RFP service IP restricted History, to the backup
web machine is Audit specific See the to
SERIAL about used
indicators, history View Partitions. be
connectivity, information. audit privileges information can
routing the privileges: also Audit methods
database any level display are Delete for
track events. audit log or and security There and documentation message. backup storage.
not FTP not message retrieve certain Summary. Partitions, Server term
does or does log to have request each for SQL long
solution solution ability who Audit Audit for
The connectivity The addresses, The users View View message privileges Traditional database
EXCEPTION WITH COMPLY COMPLY
CLARIFICATION
COMPLY
and an for
database long
events attributes record search unauthorized for
following (e.g., etc.) to: criteria, log
failure, connectivity). data limited from audit
the and booking, search the
for FTP field case, not information backup
log Communication but updated, to
audit connectivity, following person, including data. log ability
an to: the inmate name records unstructured audit the
maintain limited service record user Information added, protect have
(i.e. or Address
shall not web shall event: record Time system records related Indicator IP name shall shall
solution but solution log of and Record and Message level solution solution storage.
The activities connectivity, The audit Type Date Source Data returned, results, Routing Machine Interface Log Log The access. The term
• • • • • • • • •
NF-AU-2.4.10 NF-AU-2.5 NF-AU-2.6 NF-AU-2.7

170002-RFP IP Windows available available
machine with mode, mode,
SERIAL on on
indicators, available always always
information. an an
routing features in in
solution. any level by operate operate
our audit log or provided Directory. to to
to
not message is designed designed
applicable does Active is is
log functionality
not solution and solution solution
is addresses, Server 24x7x365. 24x7x365.
This The This The The
EXCEPTION WITH COMPLY COMPLY COMPLY
CLARIFICATION
COMPLY
data of to Officer multiple Ra i week a Outage and the
following activity e.g., a days for
reconstruction each Security within Failure 7 Planned Month above
the for etc.) occurs, location Outage) users the per table
for booking, MCSO or to
record attributes to same available achieve Downtime the in
log accountability, case, alert attempted the (Planned will stated
audit following transaction: person, audit is from be shall it how Year,
an the a an breach in Availability per
support identification: replay the of inmate name provide log system describe Downtime requirements
maintain to for failed received acknowledgement record status user security to User
shall activities problem received delivered delivered pending replay received delivered acknowledgement shall current (i.e. or identifier identifier should attempts frame. End Continuity Management shall week
sent not for not sent record Time system name message suspected time day. Availability, per
solution exchange and Request Request Request Request Request Request Response Response Response Response Received solution the of and Source Interface Message Transaction Audit solution a unsuccessful ecific Availability. Operational Jail a hours Contractor Downtime solution.
The events • • • • • • • • • • • Sent • The provide Type • Date • • • • • • The when . s The 24 The of % JMS
NF-AU-2.8 NF-AU-2.9 NF-AU-2.10 NF-AV-3.0 NF-AV-3.1.1

available available available available available available available available
170002-RFP
mode, mode, mode, mode, mode, mode, mode, mode,
SERIAL on on on on on on on on
always always always always always always always always
an an an an an an an an
in in in in in in in in
operate operate operate operate operate operate operate operate
to to to to to to to to
designed designed designed designed designed designed designed designed
is is is is is is is is
solution solution solution solution solution solution solution solution
24x7x365. 24x7x365. 24x7x365. 24x7x365. 24x7x365. 24x7x365. 24x7x365. 24x7x365.
The The The The The The The The
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
Month the for Month the for Month the for Month the for Month the for above above above proposed
Planned per above proposed Planned per above Unplanned per above Unplanned per above proposed Unplanned per above Operational per table Operational per table the in Operational per table
the Downtime table the in the Downtime table proposed Downtime table the Downtime table the in the Downtime table proposed Downtime the in the Downtime the in included the Downtime the in the in
achieve the included achieve the the in the the achieve the included achieve the the in the Year, stated achieve Year, stated achieve Year, stated included
Year, in Year, in achieve Year, in Year, in Year, in achieve Services
will stated will stated included stated will stated will stated included per will per will per Services
they per Services they per will per they per Services they per will requirements they requirements Web they requirements
it it Downtime Downtime and Downtime
how Downtime requirements Web how Downtime requirements Services how Downtime requirements how Downtime requirements Web how Downtime requirements Services how how how Reporting
week week week
describe and describe Reporting describe describe and describe Reporting describe Availability, per describe Availability, per components describe Availability, per
Availability, week Availability, week Availability, week Availability, week Availability, week
shall per components shall per shall per shall per components shall per shall of Downtime solution. shall of Downtime Party shall of Downtime Management
Contractor of % Downtime Party Contractor of % Downtime Management Contractor of % Downtime solution. Contractor of % Downtime Party Contractor of % Downtime Management Contractor % and JMS Contractor % and Third solution. Contractor % and Jail
The Outage and Third solution. The Outage and Jail solution. The Outage and JMS The Outage and Third solution. The Outage and Jail solution. The Continuity Month the for The Continuity Month the for proposed The Continuity Month the for solution.
NF-AV-3.1.2 NF-AV-3.1.3 NF-AV-3.2.1 NF-AV-3.2.2 NF-AV-3.2.3 NF-AV-3.3.1 NF-AV-3.3.2 NF-AV-3.3.3

by and that and that is built and that and that and that
170002-RFP provided is users hardware ensure and is users hardware ensure and is users hardware ensure and is users hardware ensure and is users hardware ensure and
solution the to help solution the to help solution the to help solution the to help solution the to help
tools concurrent Components concurrent Components concurrent Components concurrent Components concurrent Components
SERIAL using Offender360 of Following will C Offender360 of Following will C Offender360 of Following will C Offender360 of Following will C Offender360 of Following will C
tested Party optimal. Party optimal. Party optimal. Party optimal. Party optimal.
be the thousands performance. Attachment Third the thousands performance. Attachment Third the thousands performance. Attachment Third the thousands performance. Attachment Third the thousands performance. Attachment Third
can which of in JMS, remain which of in JMS, remain which of in JMS, remain which of in JMS, remain which of in JMS, remain
queries on hundreds in outlined the solutions on hundreds in outlined the solutions on hundreds in outlined the solutions on hundreds in outlined the solutions on hundreds in outlined the solutions
for server. Platform degradation for Platform degradation for Platform degradation for Platform degradation for Platform degradation for
times SQL support guidelines levels Services support guidelines levels Services support guidelines levels Services support guidelines levels Services support guidelines levels Services
backend Dynamics to any Dynamics to any Dynamics to any Dynamics to any Dynamics to any
Transaction The designed without software performance Reporting The designed without software performance Reporting The designed without software performance Reporting The designed without software performance Reporting The designed without software performance Reporting
the
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
,.
ad- will while and of in will
solution and solution above number Reporting users of performance Reporting exceeding solution while
track pre-formatted Event table Components operational number users required
to Users, Management the levels, Party forecasted Management operational Management of Management concurrently levels,
ability both Concurrent in users the required forecasted number maintaining users
the for Functions Jail of performance Third Jail the required Jail the Jail of perfounance
users times the the accommodate maintaining the the while the
end Users, System how number how how how above how number
provide response Of 01 describe operational describe will while describe accommodate maintaining describe accommodate table levels, describe operational
shall transaction Number Prioritization shall forecasted the required shall solution above levels. shall will while shall will the in performance shall forecasted the required
Contractor and Limits. Contractor Contractor Services table the Contractor solution above Contractor solution specified Contractor
uptime queries. Capacity Volumes, accommodate maintaining Web in users performance Service table levels. Service those operational accommodate maintaining
The hoc The The The the The The
.1
NF-AV-3.3.4 NF-CL-4. NF-CL-4.1.2 NF-CL-4.1.3 NF-CL-4.1.4 NF-CL-4.2.1

is built and that is built and that and that that that that that
170002-RFP is users hardware ensure and is users hardware ensure and is users hardware ensure and is concurrent data is concurrent data is concurrent data is concurrent data
solution the to solution -ent the to solution the to solution of solution of solution of solution of
concurrent help Components concun help Components concurrent help Components high amount high amount high amount high amount
SERIAL Offender360 of Following will C Offender360 of Following will C Offender360 of Following will C Offender360 and the Offender360 and the Offender360 and the Offender360 and the
Party optimal. Party optimal. Party optimal. data on data on data on data on
the thousands Attachment Third the thousands Attachment Third the thousands Attachment Third the of limits the of limits the of limits the of limits
which of performance. in JMS, remain which of performance. in JMS, remain which of performance. in ,IMS, remain which rows of no are which rows of no are which rows of no are which rows of no are
on hundreds in outlined the solutions on hundreds in outlined the solutions on hundreds in outlined the solutions on millions There solution. on millions There solution. on millions There solution. on millions There solution.
Platform degradation for Platform degradation for Platform degradation for Platform the Platform the Platform the Platform the
support guidelines levels Services support guidelines levels Services support guidelines levels Services support volumes. in support volumes. in support volumes. in support volumes. in
Dynamics to any Dynamics to any Dynamics to any Dynamics to stored Dynamics to stored Dynamics to stored Dynamics to stored
designed without software performance Reporting designed without software performance Reporting designed without software performance Reporting designed transaction be designed transaction be designed transaction be designed transaction be
The The The The can The can The can The can
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
and of required will table will in will will in
number Reporting of performance Reporting users solution the in solution specified solution solution specified
Components number concurrent maintaining specified volumes volumes volumes
Party forecasted operational Management operational Management of Management Management Management Management
Third the required forecasted number while volumes Population Transportation Released
Jail required Jail today Jail Jail Jail Jail
the accommodate the the the the the Booking the Daily the Inmate the Inmates
how maintaining how how users how how how how
accommodate maintaining accommodate of levels, the the the the
describe will describe describe number describe describe describe above, describe
shall solution while levels, shall will while shall will total performance shall accommodate shall accommodate shall accommodate table shall accommodate
Contractor Services concurrently Contractor solution users Contractor solution the Contractor Contractor above, Contractor the in Contractor above.
performance Service concurrent levels, Service exceeding operational successfully above. successfully table successfully specified successfully table
The Web users The The The The the The The the
NF-CL-4.2.2 NF-CL-4.2.3 NF-CL-4.2.4 NF-CL-4.3.1 NF-CL-4.3.2 NF-CL-4.3.3 NF-CL-4.3.4

that that that that be that adding disk storage levels needs.
170002-RFP is concurrent data is concurrent data is concurrent data is concurrent data can measurement is concurrent data hard data data
solution of solution of solution of solution of the solution of of and the transaction for MCSO's
high amount high amount high amount high amount archiving/backup, meet capacity, high amount factor users of
SERIAL Offender360 and the Offender360 and the Offender360 and the Offender360 and the to staff performance of Offender360 and the a be of review anticipated recommendations support
data on data on data on data on County. data on will volumes to
the of limits the of limits the of limits the of limits data technical Server monitoring the of limits Upon and
which rows of no which rows of no which rows of no which rows of no as such the by allow which rows of no Scalability higher growth. levels provide configuration
are are are are MCSO's SQL are
on millions There solution. on millions There solution. on millions There solution. on millions There solution. priorities, mandated and will etc. on millions There solution. data data will server
Platform the Platform the Platform the Platform the by that usage, Platform the accommodate current Tribridge and
support volumes. in support volumes. in support volumes. in support volumes. in solution controlled needs networking available support volumes. in to accommodate on
Dynamics to stored Dynamics to stored Dynamics to stored Dynamics to stored Dynamics to stored servers based tables, capacity
designed transaction be designed transaction be designed transaction be designed transaction be Backend manually performance Windows are performance, designed transaction be to space needs all storage
The can The can The can The can tools The can new for
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
will will will the will the in the including and allow the
solution volumes solution volumes solution in solution performance allows that capacity, and
specified specified priorities controlled measures System solution
Management Count Management Stay of Management Management those operational solution be of the
High Length volumes proposed process can performance of
Jail Jail Jail Jail exceeding required priorities Contractor, scalability
the Population the Average the Workload the the solution the
how how how how volumes all how exception system and the
the the the manage growth.
describe above, describe above, describe describe maintaining describe to provide MCSO describe
shall accommodate table shall accommodate table shall accommodate shall accommodate shall how and shall both usage. shall accommodate
the the while Administrator by and
Contractor in Contractor in Contractor above, Contractor above, Contractor settings Contractor Contractor to
successfully specified successfully specified successfully successfully levels, System routine managed. monitoring, performance, ability
The The The table The table The The The
NF-CL-4.3.5 NF-CL-4.3.6 NF-CL-4.3.7 NF-CL-4.3.8 NF-CL-4.4.1 NF-CL-4.4.2 NF-CL-4.4.3

need the Project for a an in if similar an in if similar prior
170002-RFP the via Process. documented following: project Tribridge when information
without County Team the maintained or maintained or environment
documented Making be will the and Project on the in notified Server Server
SERIAL deployed be it minimum the logged Tribridge be additional be can be can Test
will Decision requested, a Tribridge to be will or and Foundation control. and Foundation control. the in
easily project and is at the by on passed will by setup request rejected Team. versioned Team version versioned Team version tested
be can the include, orders be the of approved, Project of of
to Resolution functionality and reviewed approval, change will the are Microsoft level are Microsoft level regression Production.
changes changes Issue form change change be upon of (which creator been by components as this components as this fully
solution downtime. for out-of-scope order Submission the the will and, status site The has requested such desires such desires are to
end system requests aforementioned change Submitter of for of orders The environment). order been solution environment County solution environment County changes moved
Front for All When a via • Date • Reason • Benefits • Change Managers review. SharePoint change has All the All the All being to
COMPLY COMPLY COMPLY COMPLY COMPLY
to are
continues components with attributes. module report. as MCSO made,
whole process item current a of configurations applied. existing are
a individual of form for updates
as control configuration record the in and/or testing
solution when system supplied
the change a running changes MCSO provided regression
that secure a change a of are Contractor
ensure remain implement to provide history maintain updates conduct as
Management shall and shall required shall the and shall shall
reliably stages supplied configurations
Configuration Contractor Contractor Contractor configurations Contractor Contractor
The function changed. The approval The The Contractor The system
, .. NF-CM-5.1 NF-CM-5.2 NF-CM-5.3 NF-CM-5.4 NF-CM-5.5

is built and that the is built and that the open the defined
I70002-RFP the Any accommodated. in is users hardware ensure and on loads is users hardware ensure and on loads screen of made as
to Practices. projects Production. solution the to help performance pre-production solution the to help performance pre-production loading, phase be requirements
SERIAL adheres be can all for and concurrent will Components Full transaction concurrent will Components Full transaction testing will
Best follow Testing Offender360 of Following C Party optimal. and and scenarios. Offender360 of Following C Party optimal. and and scenarios. application the adjustments
methodology Management to environments the thousands Attachment Third testing user the thousands Attachment Third testing user during performance
wishes 3 Development, which of performance. in JMS, remain the during monitoring production which of performance. in JMS, remain the during monitoring production include conducted and the
management Change MCSO least at on hundreds in outlined the solutions by of on hundreds in outlined the solutions by of will that be recorded meet
ITIL that recommends engaged: Platform degradation for performed project that Platform degradation for performed project that testing will be will to order
change the support guidelines levels Services be mirror support guidelines levels Services be mirror times in
of policies are we Dynamics to any will the of that Dynamics to any will the of that refresh Results
Tribridge's principals current Tribridge which The designed without software performance Reporting testing phases system The designed without software performance Reporting testing phases system Performance and project. accordingly MCSO.
by
COMPLY COMPLY COMPLY COMPLY COMPLY
the the the the the but
Infrastructure includes approval release with distinct meet will Management during to calculations, meet will Management implementation. loading, meet will Management tested be includes,
This dashboard, management detailed process separate production. solution Jail validated limited solution Jail how and solution Jail will time refresh,
Technology Practices. management change CAB/EC testing, control three and the and not is functions, the Number the application the performance Response and open
board, least Utilization proposed for tested but refresh, proposed for during to proposed for
Best change screening, advisory regression change at pre-production the above be includes, and the above Booking validated limited the above how screen
Information Management to: RFC a maintain Time, how specified will time open how specified and/or and not is functions. how specified and implementation. loading,
follow limited (RFC), change and implement to testing, Response describe performance screen describe tested but describe Update the
shall Change not change, approved, shall required as: such Total shall requirements Response exports. shall requirements Name by be includes, refresh, shall requirements Record during application
(ITIL) is but change minor change stages how loading, and Query will time and Inmate to
Contractor for Contractor environments Performance. Contractor performance and implementation. application Contractor performance performance open Contractor performance validated limited
The Library following request review, review, notes. The approval The System imports, The System: Response screen The System: and not is functions.
NF-CM-5.6 NF-CM-5.7 NF-PF-6.1.1 NF-PF-6.1.1.1 NF-PF-6.1.1.2

is built and that the is built and that the is built and that the open the defined
170002-RFP is users hardware ensure and on loads is users hardware ensure and on loads is users hardware ensure and on loads screen of made as
solution the to performance pre-production solution the to performance pre-production solution the to performance pre-production loading, phase be
concurrent help Components transaction concurrent help Components transaction concurrent help Components transaction testing will requirements
SERIAL Offender360 of Following will C Full and Offender360 of Following will C Full and Offender360 of Following will C Full and the
Party optimal. testing and scenarios. Party optimal. testing and scenarios. Party optimal. testing and scenarios. application during adjustments performance
the thousands perfoimance. Attachment Third the user the thousands performance. Attachment Third the user the thousands performance. Attachment Third the user and
which of in JMS, remain during monitoring production which of in JMS, remain during monitoring production which of in JMS, remain during monitoring production include conducted recorded the
on hundreds in outlined the solutions by of on hundreds in outlined the solutions by of on hundreds in outlined the solutions by of will that be meet
Platform degradation for performed that Platform degradation for performed that Platform degradation for performed that will be will to order
support guidelines levels Services be project mirror support guidelines levels Services be project mirror support guidelines levels Services be project mirror testing times in
Dynamics to any will the of that Dynamics to any will the of that Dynamics to any will the of that refresh Results
The designed without software performance Reporting testing phases system The designed without software performance Reporting testing phases system The designed without software performance Reporting testing phases system Performance and project. accordingly MCSO.
by
COMPLY COMPLY COMPLY COMPLY
the be the the the
meet will and meet be and meet tested meet validated but
will Management time open will Management will time open will Party be will Management include,
performance will and
solution Jail Response screen solution Jail performance Response screen solution Third solution Jail tested times
the how loading, the loading, the performance the be
proposed for and proposed for how proposed for proposed for will Reporting loads.
above implementation. above and implementation. above how above
the Logging application the application the and implementation. the performance and subsequent
how specified the how specified Transactions the how specified how specified Query
describe Journal to describe to describe Services describe how and
requirements during limited requirements Query during limited requirements Web the requirements and implementation. initial
shall Operation validated not is shall validated not is shall and during shall Service to
Contractor Jail and but functions. Contractor Ad-hoc and but functions. Contractor validated Contractor the limited
performance System: tested includes, refresh, performance System: tested includes, refresh, performance Components performance Reporting during not
The The The and The are
NF-PF-6.1.1.3 NF-PF-6.1.1.4 NF-PF-6.1.2 NF-PF-6.1.3

is and that the All All the All to
170002-RFP built is users hardware ensure and on multi-factor and conjunction AD AD access AD to access
solution to performance pre-production loads identity, in authentication. within authentication. within to authentication. within Access multidimensional Offender360 provide type.
concurrent the help Components transaction enable device used needs. password solution. that user
SERIAL Following will Full and can be for controlled for controlled for controlled the and that
Offender360 of C Party optimal. and scenarios. you location, can MFA Directory Directory AD. and Directory AD. the by platform roles for
the thousands Attachment testing user R2 ADFS support are are in ID are in access controlled multiple required
which of performance. Third remain the production 2012 network to Active settings Active settings available unique Active settings available to Dynamics
on in in JMS, during monitoring Server® the membership. platform uses uses is a have uses is password is assigned solution
hundreds outlined the for solutions by of on password password setting to password setting solution the be the
Platform support degradation levels performed project that Windows based group platform and platform and This required platform and This single the within can of
guidelines Services be the mirror in or Dynamics is a has within model user areas
Dynamics to any performance will of that FS authentication identity your Dynamics authentication environment. Dynamics authentication environment. user Dynamics authentication environment. user A different
The designed without software Reporting testing phases system AD In user with The The Each solution. The Each modules security solution. the
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY WITH
CLARIFICATION
COMPLY
the hour CJIS policies account. by to
tune 24 a and user role. security
and through ACJIS MCSO unsuccessful user's each administrator and
monitor with with passwords. the group password
3 reset authenticate system role.
will performance comply comply strong after to a security define and
they to authentications. to and access administrator and for on to group
how optimal ability ability for identify ability based ability
the the user the out the security
describe maintain provide factor provide authentication a block system uniquely provide time provide
shall to two a session module,
order shall requiring shall secure shall requiring shall shall shall by
Contractor in solution solution a solution solution solution user a solution requirements
Utilization The solution period, Security The policies The requiring The attempts, The password. The define The
NF-UT-6.2.1 NF-SE-7.1.1 NF-SE-7.1.2 NF-SE-7.1.3 NF-SE-7.1.4 NF-SE-7.1.5 NF-SE-7.1.6

and that and that restrictions and that All All All
170002-RFP share platform that for platform that for policies platform that for AD AD AD
to the roles required the roles required access etc. CJIS the roles required authentication. within authentication. within authentication. within
SERIAL ability by Dynamics multiple by Dynamics multiple location, with by Dynamics multiple for for for
the controlled solution controlled solution support comply controlled solution controlled controlled controlled
support is the assigned the is the assigned the Machine authorization. is the assigned the Directory are AD. in Directory are AD. in Directory are AD. in
proposed solution within be can of areas solution within be can of areas inherently Indicator, and/or solution within be can of areas Active settings available Active settings available Active settings available
users. the model user different the model user different not does meet to interface the model user different uses is uses is uses is
being within security A within security A Routing within security A password setting password setting password setting
model multiple solution. the to solution. the to solution designed agency solution. the to platform and This platform and This platform and This
modules access modules access The TCP/IP, is to modules access
licensing across to multidimensional Offender360 type. to multidimensional Offender360 type. on solution regards to multidimensional Offender360 type. Dynamics authentication environment. Dynamics authentication environment. Dynamics authentication environment.
The logins Access provide user Access provide user based The with Access provide user The The The
COMPLY COMPLY WITH COMPLY COMPLY COMPLY COMPLY COMPLY
COMPLY CLARIFICATION
share CJIS policies CJIS & detailed to and all month.
the to and following: See and Access Request limited timeouts, notifications multiple a within documenting per
provide agency ACES MCSO etc. ADIS standards not alert e.g., and
shall with with the to Indicator, with the for Access but inactivity violation, location report day,
solution police comply comply limited comply authorization, required Library: security including security same a per
the external to to not Routing to Forms minimum Policy requirements, immediate policy the produce shift, per
only, each ability authorization, ability but IP, Responsibilities, ability interface elements exceeded. security from to system
from the the including TCP the all See that Security an on log ability
module users provide agency provide TOC, Security provide agency capture ensure password or met produce possible to the have the in
Pre-Booking multiple shall user shall authorization role, User shall external shall Authorization. shall Information are should a of attempts frame. shall items
for credentials. solution end for solution location, End solution for solution and Contractor requirements, revocation solution detection time solution related
the For ability logon The policies The user end group, MCSO The policies The Request Authorization. The MCSO's in login user The upon unsuccessful specified The security
NF-SE-7.1.7 NF-SE-7.2.1 NF-SE-7.2.2 NF-SE-7.2.3 NF-SE-7.2.4 NF-SE-7.3.1 NF-SE-7.4.1 NF-SE-7.4.2

All All approach this interface any
170002-RFP AD AD drop is third of for This conduct made management that on the
authentication. authentication. fields, this no part set need process, to be ensure impact in
within within easily no-coding of and as skill the integration, proposal. used can change to any found
SERIAL for controlled for controlled and a tables, All etc. interface included the with without business this etc. framework order have be can
Directory AD. Directory AD. highly enables forms, reports, unit report, of cases, Proper in not
are in are in the which the platform been resources functions conduct part as uses the of solution. followed do agreement right.
Active settings available Active settings available on built to the has to migration, phases scripts, outside be solution the at
uses is uses is is platform changes administration, through Training MCSO these of effort data test Contractor's should the performance. escrow noted
password setting password setting solution provide all testing any applications of the C
platform and This platform and This dynamics configuration system directly required. will perform support. included acceptance, develop sessions. the procedures outside and regarding Attachment
Dynamics Dynamics Offender360 values, are that to has user providing testing to of made stability of
authentication environment. authentication environment. configurable making accomplished tools proposal necessary Contractor Tribridge system, custom includes updates independent testing changes system details section
The The The to down party and these All and Full
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
reports the after GUI as: verify customer. updates (For in the on all
of to support verify to etc.) build and
security standards. distribution ability operations to scripts to configuration. Updates, application virtual mitigation defaults code
and the services completed. user scripts and delivery Contractor current risk source
alerts Policy the user been such to exchanges, and tools code party Contractor delivered management provide otherwise the
security Security configure Contractor has limited tools test with to prior third application's the binaries/libraries, release shall or access solution.
all to administrative transfer not data lists, backups. tested receive Database put to and This business to has the
document MCSO MCSO an minimal but value system certified functionality, regression functionality to Contractor willing party escrow. of out MCSO maintain
fulfill allow provide with knowledge include provide able the Updates, be third development goes that to
shall they notifications. system and shall down reports, and be and be shall code, into
that shall lity shall the drop shall stability shall stability shall modifying Windows Escrow source and images Contractor ensuring objects
Contractor ensure solution alert Supportabi Configurability solution training Configuration formatting, administration, Testability solution solution Upgradeability solution Contractor procedures, the supporting
The and The security The configure initial The solution The solution The without Example Platform The version machine case contract,
NF-SE-7.4.3 NF-SE-7.4.4 NF-SU-8.1 NF-SU-8.2 NF-SU-8.3 NF-SU-8.4
,

are available. approach drop third and the However, the beyond is the external to
170002-RFP components the of are fields, is this no database integrity of to platform with allow administrative administrative available
versions solution easily no-coding of All and SQL data architecture technologies. changes extensibility Dynamics provided that specific
SERIAL solution in the and a tables, etc. interface a on maintain make If Kit API's and and MSCO made
all supported greater. of highly enables forms, reports, resides to coding coding to etc. the 140 user of user of on versions
for and versions the on which the to platform standards underlying order in queries, required, Development over versions versions based all
guides is vi built the solution .NET code views, are to system. with
Control 2015 mobile is platform changes administration, through The RDBMS The Microsoft any system Software access the electronic available. electronic available. materials included
configuration Concurrency platform and based solution dynamics configuration system directly required. on solution. on write to forms, the of the provides with and are and are training be administrators.
and CRM Offender360 are based the based need fields, using which interact online material online material the will
Installation Optimistic Dynamics browser configurable making values, accomplished tools designed throughout is no is tables, capabilities accessible to to functionality and
available. Both The to down party is solution there GUI, the platform sources Printed, training Printed, training Updates users
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
for through coding the of of initial new the
procedures control data in versions days. versions the for use to
optimistic application. and created Navigation three with manuals need
quality application. design been electronic than electronic trainees they
installation and or based have User less and user
integrity pessimistic based architectural, and curve online and the to information
application browser exclusions Interaction. online users solution.
components. data as thin mobile the both learning both new the updates initial
Procedures provide ensure such a a describe what solution. User a have provide provide use to provide the
shall related shall mechanisms provide provide shall and the provide and shall to need shall with
Installation and shall shall employed of Requirements. shall material, manuals they trainees
Contractor solution Concurrency application concuiTency Client solution solution Maintainability Contractor development solution Contractor user information Contractor and
Provide The their The locking. Thin The The The standards Usability The training The their The users solution.
NF-SU-8.5 NF-SU-8.6 NF-SU-8.7 NF-SU-8.8 NF-U-9.1.1 NF-U-9.1.2 NF-U-9.1.3

allow this, allow this, allow this, the access
170002-RFP Trainer solution solution will anticipated will anticipated will anticipated and supports to (predictive solution. information
the the the supports supports supports
Train of of system than system than system than layout and supports) lookups Offender360 key
SERIAL versions needed. versions needed. the time solution the time solution the time solution and solution. driven access
onsite as as by less our by less our by less our design the device and the to
the users. future request future request provided of provided of provided of keyboard if downs takes
super for for much use much use much use screen throughout screen drop throughout it
regarding 100 MCSO's MCSO's in historical in historical in historical and touch as that two.
training training functionality tasks functionality tasks functionality tasks consistent used mouse such used is
details stated on-site upon on-site upon complex while vary. complex while vary. complex while vary. are both (or click types are clicks of solution
includes MCSO's available available the that and may the that and may the that and may terminology, concepts be and system. field both) amount
for and/or and/or feel complete here, results feel complete here, results feel complete here, results can point the on Offender360
proposal based made based made we to listed we to listed we to listed navigational solution to within Standardized enabled average
Our approach Web be can Web be can While users and individual While users and individual While users and individual Common The ability data text The the in
COMPLY COMPLY COMPLY WITH WITH WITH COMPLY COMPLY COMPLY COMPLY
CLARIFICATION CLARIFICATION CLARIFICATION
COMPLY COMPLY COMPLY
a at exam trainer. future available complex tasks the the inmate information
user a for perform graphical describe on the instance identify information
training end proficiency as training programs perform perform to shall point a with various For to key
trainer" certified to to ability minutes. consistent touch way. available get
the conduct being based training ability minutes. ability the 2 Contractor or associated the be to
"train to Contractor to web components. the 15 the users within vernacular, navigation. click, data access intuitive to ability
trainers a prior or ongoing users within users minutes. The user point, and to and need the
on-site MCSO pass trainer" on-site the related novice novice 2 experienced scheduling common workflow. to to able be text user screen.
shall and inmate within regard able screen, to consistent the any
provide prepare trainers the provide describe solution provide an provide search provide court a have good with be System displayed. user predictive provide from
shall to "train shall solution. shall shall booking shall shall inmate shall and to need the for quick, a and shall clicks
level MCSO on-site proposed as booking as solution will Management be to in lists
Contractor the Contractor of Contractor solution such solution a as solution such solution interface, user need important require down types. solution three
The sufficient training. from The versions The the for The tasks The such The tasks The user proposed The Jail will is It they drop data The within
NF-U-9.1.4 NF-U-9.1.5 NF-U-9.1.6 NF-U-9.1.7 NF-U-9.1.8 NF-U-9.1.9 NF-U-9.2.1 NF-U-9.2.2 NF-U-9.2.3 NF-U-9.2.4

of of a as of
and users the of needs the of needs and solution, security the of needs their
170002-RFP of with the box the box the related. the box meet
accessed types Regrouping fit the Regrouping fit the database assigned Regrouping fit the to
all to of to of within data to of MCSO
SERIAL be keys. by compliance exist out exist out single from Shared users exist out
can used logically. the logically. the one the logically. the by
function be in be presently through presently through in Core by presently through desired
functionality and to to disabilities. exchangeable or
grouped they grouped they contained Data determined grouped they format
and keyboard designed features with is as accomplished is as accomplished and is as accomplished
is solution elements solution elements is Internal is solution elements any in
solution the of platform accessibility persons be be solution accessible data be stored
use for the data easily tool. the data easily tool. the MCSO the to the data easily tool. requirements.
Offender360 the within box within box with easily be within box be can
by Dynamics provides requirements the can configuration the can configuration is it Accessibility the can configuration
driven data of MCSO data of MCSO data result, whether roles. data of MCSO data specific
The The and All out All out All All out All
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
perform keys. data Inmate Court and legal
Disabilities Data to data. data to data the by
and function compliance Dictionary Information data, Information Internal Design. Maricopa.
with Retention, limited Tracking Information limited Custody support acceptable
navigate and the of Data not Fiscal not Booking data, MCSO will Conceptual is of
to shortcuts 100% Americans Data Internal but data, Inmate Shared but data. that County
ability meet the Groupings, Conversion, MCSO including Visitor and Core including data, History of solution the in format and
the keyboard of data, Person Information exchange the a
user shall 508 Data Data store data, store Information how presented in MCSO,
the a and groupings and groupings data, data data
only solution Section Logical Inmate Administrative Release describe ACES,
provide with in Relationships, process data process data Medical facilitate Model maintain
the data, Information and shall CJIS,
shall function that stated shall logical data, shall logical data, data, shall data. Information shall as
Requirements, And Services
solution desirable 1990. solution in solution in Person solution Shared Contractor solution such
system is requirements of Structures elements Support Operations elements Information Information MCSO entities
The all It Act Data The The data, The Core The The
NF-U-9.2.5 NF-U-9.2.6 NF-DR-10.1.1 NF-DR-10.1.2 NF-DR-10.1.3 NF-DR-10.1.4 NF-DR-10.2.1

the of the of the of time time cell This CRM
of needs of needs of needs
170002-RFP the box the box the box given security given security specified performance. Server contain passwords. Dynamics data
Regrouping fit the Regrouping fit the Regrouping fit the any any a SQL that compliance. use off.
to of to of to of at assigned at assigned on turned
SERIAL exist out exist out exist out run system attributes email Microsoft
logically. the logically. the logically. the accessible user's accessible user's to Microsoft and 140-2 organizations be
presently through presently through presently through a a set or overall entity names FIPS and can't
grouped they grouped they grouped they directly on based directly on based manually on standard user meet Online encryption
is as accomplished is as accomplished is as accomplished is is impact uses default as CRM upgraded
solution elements solution elements solution elements data interface data interface done CRM of set such organizations and Data
be be be archived archived be minimize a for Dynamics new default.
the data easily tool. the data easily tool. the data easily tool. solution solution can to Dynamics information, all
within box within box within box and the and the archiving as so encryption help by
the can configuration the can configuration the can configuration active active can Microsoft (on-premises),
data of MCSO data of MCSO data of MCSO through roles. through roles. Data schedule Microsoft level sensitive feature encryption
All out All out All out All All For
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY WITH
CLARIFICATION
COMPLY
rules. a for to affect
to active to a to to legal Contractor archiving in
user business user for user storage user per information not data
are storage as the does of
administrative they on administrative administrative purged/sealed administrative time database it that level
when based archival rules. rules. of or archived requirement,
an define time an in business an in business an period structure retrieval. the ensure encryption
for of for be for be for a for application, tasks to periods.
ability and period ability to on ability to on ability over data ability priority bit
the groupings the groupings based the groupings based the will, database affect the current solution peak 256 the
determined time time at in not of lower during
provide data provide data of provide data of provide records change shall provide the a provide
a through prioritization have
shall logical for shall logical period shall logical period shall A period shall to performance shall
solution the available solution the solution the solution archived that solution viewable the needs solution
manage manage determined manage determined retrieve requirements. during per process system transit.
The and The The The The be As The
NF-DR-10.2.2 NF-DR-10.2.3 NF-DR-10.2.4 NF-DR-10.2.5 NF-DR-10.2.6 NF-DR-10.2.7 NF-DR-10.2.8

cell This CRM cell This CRM cell This CRM will contain will identify the with will identify
170002-RFP Server contain passwords. Dynamics data Server contain passwords. Dynamics data Server contain passwords. Dynamics data Tribridge documentation will interaction Tribridge documentation will Tribridge documentation will Jail
SQL that compliance. use off. SQL that compliance. use off. SQL that compliance. use off. that that associated that
SERIAL email Microsoft turned email Microsoft turned email Microsoft turned project, Design user project, Design flows project, Design proposed
Microsoft attributes and 140-2 organizations be Microsoft attributes and 140-2 organizations be Microsoft attributes and 140-2 organizations be requirements and requirements requirements the
entity names FIPS and can't entity names FIPS and can't entity names FIPS and can't the of Integration interface the of Integration the of Integration for
standard user meet Online encryption standard user meet Online encryption standard user meet Online encryption phase and phase and inter-functional phase and diagram
uses default as upgraded uses default as upgraded uses default as upgraded and project design, and project and project
CRM of set such organizations CRM and Data CRM of set such organizations CRM and Data CRM of set such organizations CRM and Data design Technical design Technical and design Technical relationship
a for Dynamics new default. a for Dynamics new default. a for Dynamics new default. the of MCSO's conceptual the of MCSO's stored the of MCSO's
Dynamics information, help all Dynamics information, help all Dynamics information, help all Functional, to Functional, to is Functional, to entity System.
encryption can Microsoft by encryption can Microsoft by encryption can Microsoft by conclusion specific conclusion specific data conclusion specific
Microsoft sensitive feature (on-premises), encryption Microsoft sensitive feature (on-premises), encryption Microsoft sensitive feature (on-premises), encryption the deliver is inputs/outputs, details. the deliver is the where solution the deliver is logical Management
level For level For level For At that At that At that the
WITH WITH WITH COMPLY COMPLY COMPLY
CLARIFICATION CLARIFICATION CLARIFICATION
COMPLY COMPLY COMPLY
rest use rest the The the
at in at of the user for
data of data of data of outputs format. to and inter- diagram
level level level limited and
and narrative not documentation stored relationship
encryption encryption encryption inputs and are is solution.
bit bit bit tape. data diagram but interface data the the entity
256 256 256 to main include where with logical System.
the the the out the both design,
provide provide provide writing identify in outputs identify associated provide
solution and Management
shall shall shall before shall inputs conceptual shall flows shall
database. application. JMS Jail
solution solution solution backup solution data interactions. solution solution
The the in The the by The a in The proposed main following: The functional The proposed
NF-DR-10.2.9 NF-DR-10.2.10 NF-DR-10.2.11 NF-DR-10.3.1 NF-DR-10.3.2 NF-DR-10.3.3

the the the the the the the the to
with this with this with this with this with this with this with this loads that prior legacy
170002-RFP for for for for for for for capabilities data possible the
populated scope populated scope populated scope populated scope populated scope populated scope populated scope upon recommended of
SERIAL be in be in be in be in be in be in be in detection as conversion
will being will being will being will being will being will being will being executed is much
JMS as JMS as JMS as JMS as JMS as JMS as JMS as duplicate be It as the
new identified new identified new identified new identified new identified new identified new identified will JMS. deduplicated during
the the the the the the the detection new
configurable the JMS. maintained
proposal, systems proposal, systems proposal, systems proposal, systems proposal, systems proposal, systems proposal, systems to and new
our legacy our legacy our legacy our legacy our legacy our legacy our legacy provides Duplicate systems cleansed the be will JMS.
in in in in in in in box. legacy be into new
the the the the the the the integrity the
contained from contained from contained from contained from contained from contained from contained from solution the the data loading into
As data project. As data project. As data project. As data project. As data project. As data project. As data project. The of out from source data Data data
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
in in solution data be it
in databases. databases. JMS will source system that
contained contained contained data Transport new system MCSO. new databases. so
databases. databases. system the One the databases values. the current conversion
data data solution solution by of from conversion.
system databases. data solution system solution new Operations populate Business new MCSO to solution the of
system Pre-Booking identified execution agreed duplicates the
JMS solution new IFCS new the Court to SAP the current new integrity throughout after
OJ the populate files populate data the MCSO the
existing new existing build existing the existing existing existing for in to prevent in record processing
the build to automated to essential required available and validated
the the to the the files the the files defaulted occurring the
utilize populate utilize used utilize populate utilize utilize in utilize convert not or identify ensure and inmate
to be to to automated contained automated elements or from protected for
shall may shall may may may shall manually shall shall
files files files in in data missing prevent be reliable
solution solution solution solution solution data solution solution is solution and solution will
automated automated automated contained system databases. contained Essential which recorded be
The The The The The The The The data The data will
NF-DR-10.4.1 NF-DR-10.4.2 NF-DR-10.4.3 NF-DR-10.4.4 NF-DR-10.4.5 NF-DR-10.4.6 NF-DR-10.4.7 NF-DR-10.4.8 NF-DR-10.4.9

be can the in loads the to prior tool loads. NIEM
170002-RFP that of directly assigned capabilities data that ETL names, names, data the
tables format from upon possible party and data live and table and table the in additions support
SERIAL custom the users' a detection recommended as third tasks. validated go platform all relationships. platform all relationships. date systems.
mirror accessible on executed is much and be any includes and includes and to up table/field can and
into will be based duplicate be It JMS. as tools conversion will to prior Dynamics that Dynamics that kept as between
loaded that will interface will new deduplicated SQL data counts descriptions descriptions be such performance. standards
be can solution tables configurable detection the JMS. of perform record environment the of available the of available will solution NIEM information
user to and names, names, model MCSO. system
data JMS These the Duplicate systems new combination to and test dictionary made dictionary made data to the to on of
history new tables. through provides cleansed the into a Insight times the be will display be will display the provided impact based exchange
the roles. box. legacy be uses in data data to changes not is
audit in audit solution solution the the data loading Scribe execution documented complete Offender360 names, complete Offender360 names, changes do solution for
Legacy created legacy the security The of out from source data Tribridge called All A fields A fields All dictionary Structural typically The format
WITH COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
CLARIFICATION
COMPLY
and key there a and (e.g., and
a into new in track matching where in data table, field occur etc.). refinements, Model
loaded inquiry by data point system go-live. database. by short changes database) files, the in
research, perform the for comprehensive fields and the Exchange
history for solution. identified to to legacy cut-over entire all long as within reference changes, degradation systems.
system available to identify, data system. tools conversion each the of both dictionary to routine any system. Information between
to ETL for system searchable, in listing and/or changes the
audit made added process duplicate external data outcome to elements a including data causing of
the and or a the automated prior a include the sources accommodate National communication
provide format included include from perform provide data shall table, update data elements, without functionality the
be duplicates/potential use shall successful validate, shall all by shall in data shall data use for
shall database will shall extracted shall tasks. to covering dictionary list changes new the and/or Constraints shall
solution that Solution solution Contractor predictable, time Contractor field Contractor codes, Contractor to solution format
relational screens remove identifiers conversion a sufficient dictionary data summary descriptions, (including additions performance Design (NIEM)
The The The The is The The The new The The
NF-DR-10.4.10 NF-DR-I0.4.11 NF-DR-10.4.12 NF-DR-10.4.13 NF-DR-10.5.1 NF-DR-10.5.2 NF-DR-10.5.3 NF-DR-10.5.4 NF-DC-11.1

of to
170002-RFP state retry when the users' main the users' main the Offender360 Offender360 environments to direct etc.
the of automated of a the to proposal. of a the to proposal. using Operating Operating proposed services, API,
reconnect independently on fed our independently on fed our the the methods.
SERIAL independent to based be in based be in solution which Server which Server based being various web interface,
be applicable, interfaces accessible can data described accessible can data described main proposal. on Windows on Windows virtualization tool supports as such
to operate operate the platform platform infrastructure Scribe
designed Where the can only stand-alone, methods can only stand-alone, methods to fed our latest latest using the methods XML/messaging
into is is be in CRM the CRM the VMWare interfaces
be endpoints. configured available. functionality that If interface functionality that If interface can described deployed proposal, and transfer tables,
can and module roles. module roles. offline Dynamics supports Dynamics supports supports our
exchanges be become a as security the a as security the methods built built be in integrations interface
systems will Pre-Booking or using Pre-Booking or using captured Microsoft is Microsoft is solution safely described communication/data
data All certain attempts systems The solution assigned solution The solution assigned solution Data interface The solution Systems. The solution Systems. The can and As support database,
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
by off- either Pre- gather batch on run or within (IIE) are
endpoints, work later, the to in will Unix alternative, Engine system options
services operate work to into system
of to shall users performed directly devices JMS headcounts. that architecture. AIX) infrastructure an external other
business systems. module it or mobile new database (IBM propose Integration all though
of of implementation i.e., Pre-Booking RMS of the perform a system either system. VMware ICES for
condition JMS, transactions to using on shall County preferred,
coupling are: or Pre-Booking new authorized and agency's utilization upload to operating operating existing Contractor existing is
loose that state underlying the the of system. the for and readers implemented implemented the the Maricopa (MQ
enable exchanges the of the of allow rest enable entered with allow offline barcode be Microsoft be Server utilize the or utilize the messaging
shall shall the of feeder a shall data interface shall data using shall or AIX shall Windows may Office shall within
data independent independent as upload module. and
solution solution independently solution and an solution transactional e.g., solution IBM solution solution Sheriff's solution infrastructure
The designing Are Are The standalone The line through Booking The mode, The either The Microsoft The the The interfaces available)
• •
1.9
NF-DC-11.2 NF-DC-11.3 NF-DC-11.4 NF-DC-11.5 NF-DC-11.6 NF-DC-11.7 NF-DC-11.8 NF-DC-1

to
170002-RFP to direct etc. department type. in deployments.
proposed services, API, projects Production. product
SERIAL being various web interface, IT hardware all for and and solution
tool as MCSO by Testing management
Scribe supports such the by performance environments successful
the interfaces methods XML/messaging set be 3 Development, project ensure
can for least
proposal, and transfer tables, cycles standards at proven to
our recommends engaged: to standards
in integrations interface refresh MCSO are adheres
described communication/data on we development
As support database, Hardware based Tribridge which Tribridge
COMPLY COMPLY COMPLY COMPLY
to, and by data data
messages equipment to limited and sound to: aliases, standards and the and of
receive and required not limited synonyms, domain data for extensibility, of use cross-referencing conceptual, administration. measurements system the
and standards cycle but least, pre-production technically not element standards consistent within
send refresh at and but data and internal, database
to protocol type. using testing, including, controlling data and modularity, and and objective checkpoints
ability CJIS hardware hardware for professionally and design, efficient searching redundancy. including and methodology.
the and the implemented environments tools and for characteristics. standards data ensure to the data data administration inspection
provide ACJIS specify per be use shall techniques design physical standards ensure system. effective control views, tests-of-correctness, cycle. testing
shall existing may performance shall separate techniques, and data for and to and for to data for data for assurance life software
solution the interfaces, solution maintain solution (3) production. Contractor standards, Standards versions. Standards element logical management. design flexibility, information Standards techniques. Standards Standards views. Standards Metrics, Quality development inal
The using The The three The • • Data • for Data • the • • • external • • quality. • Foi •
NF-DC-11.10 NF-DC-11.11 NF-DC-1I.12 NF-DC-11.13

in
170002-RFP be can the to be can the to be can the to found right. be
identified identified identified be can the will solutions.
agreements agreements agreements to Resolution our
SERIAL section section section Management identified of
maintenance the maintenance the maintenance the Issue version
in in in Lifecycle section and any
and response and response and response the in on
support C support C support C Product response Notification, customers
the Attachment the Attachment the Attachment the C Patch all to
regarding the regarding the regarding the regarding Attachment Break/fix,
in in in communicated
Details found right. Details found right. Details found right. Details the All
COMPLY COMPLY COMPLY COMPLY COMPLY
provide after upon the and of by program times timely team
shall begin agreed of Acceptance guarantee defined Contractor. response lifecycle and support: Knowledge® Library break/fix, support e-mail
shall rebooting and provisions the maintenance solution quality will Control Knowledge Infrastructure as telephone.
Contractor Warranty mutually no additional of and typical a they Control Control of Body of Resolution communicating technology such or
the passed with for Buy-Outs warranty acceptable buy-out capability, standard ensure how Management Body mail,
Included solution, updates. have days 30 3.4 for solution support process. to describe Management and Analysis Management Technology Issue for MCSO to communications standard
and testing and 3.3 Provisions a other or potential their reporting industry procedures shall Management Control and method blogs,
Available baseline maintenance (including Section provide support the of describe desk management Management employ and Contractor Organization Implementation Business Project Infolination Notification, a have resolution include
Maintenance the of and acceptance thresholds RFP provisions. Guarantees, shall solution in-case shall service support shall methods The and Support Management documents: Guide), Guide), shall issue or shall newsgroup,
And Services purchase services user See Contractor or Contractor Lifecycle Contractor and and Patch Contractor release, This
Support Support With support and acceptance solution). Warranty Warranties, continued contract include overall Product management deliverable. Planning Acquisition Delivery Monitoring Reference (BABOK® (PMBOK (ITIL). Break/fix, patch MCSO. notification,
unit The the The and and The • • • • The at
NF-SM-12.1 NF-SM-12.2 NF-SM-12.3 NF-SM-12.4 NF-SM-12.5

will the will the will the available
170002-RFP Tribridge in aid Tribridge in aid Tribridge in aid requirement. user
to to to focused made
SERIAL activities. MCSO activities. MCSO activities. MCSO this be can
to to to with industry personnel.
these practices these practices these practices customers several
for for for MCSO upgrades/enhancements
response best response best response best to in to needed.
be and items. be and items. be and items. support participates available as
will recommendations these will recommendations these will recommendations these 24x7 and also for request
MCSO of MCSO of MCSO of offers hosts are training upon
Typically, provide configuration Typically, provide configuration Typically, provide configuration Tribridge Tribridge that groups Additional MCSO
to
WITH WITH WITH COMPLY COMPLY COMPLY
CLARIFICATION CLARIFICATION CLARIFICATION
COMPLY COMPLY COMPLY
upon the desk with be which
based incremental for help The will days following
processes system requirements. - week issues. solution experiences functionality training days
recovery and and per and or share This business business
and backups, recovery tuning performance days questions Forums meetings to for applicable. State 30
backup system and annually. Optimization 7 x will: SLA's MCSO training (60) to enhancement.
the backup database hour related they Enhancement group the user sixty prior
architect full the System System perform availability Window 24 a JMS how upon user enabling base. conduct whenever of days or
protection, test on offer describe agreed Product offer customer window business upgrade
Recovery shall Recovery shall Management and shall based Availability shall addressing all and may forums shall a 30 the
data Tuning shall resolutions against upgrades/enhancements within from of
and Contractor and Contractor Jail Contractor Desk Contractor for calls Groups Contractor Contractor's Contractor
Backup The continuous backups. Backup The entire Database The optimization Help The window Contractor Track Report Report User The enhancement the The conducted extends installation
• • •
NF-SM-12.6 NF-SM-12.7 NF-SM-12.8 NF-SM-12.9 NF-SM-12.10 NF-SM-12.11

right. right. right.
170002-RFP the at the at the at
available
identified identified identified is
SERIAL tickets
section section section
the the the problem
in in in portal.
and
provided provided provided
questions support
are are are
details details details of Tribridge
SLA SLA SLA submittal the
Support Support Support Online through
WITH WITH COMPLY COMPLY
CLARIFICATION CLARIFICATION
COMPLY COMPLY
follows: Response solution Hours; 1 5 follows: Response solution Hours; 5 requests on-line on-
as of 2 Hours; Hours; as of 2 1 Hours; Hours; desk status
requests Initial Every (4 (8 requests Initial Every (4 (8 help submit resolution
Issue, component Hours) Hour; questions functionality Issue, component Hours) Hour; functionality of to ability
support 4 (I lost support 4 (1 lost issues/questions status the
Software Time critical Hour; is issues/ of hardware Hardware Time critical Hour; is of the the track
software or Per loss or Per loss report users to and
all Customer Resolution down Once functionality Days) no Days) all Customer Resolution down Once functionality no and end
resolve of system configuration have resolve of system configuration have track staff. provide tickets,
Minutes; but Business that Business Minutes; but Days) that Days)
shall Nature Interval, Production up is and 5 calls 10 shall Nature Interval, Production up is and calls shall MCSO shall problem
Contractor Level, Update Levels) (30 System User - Day; Trouble Day; Contractor Level, Update Levels) (30 System User - Business Trouble Business Contractor Contractor and
Priority Time, (Priority - Critical working - Hours) Medium Business - Business Priority Time, (Priority - Critical working - Hours) Medium Business 5 - Business 10 Days; designated questions
The not High 8 Low The not High 8 Day; Low The to The line.
NF-SM-12.12 NF-SM-12.13 NF-SM-12.14 NF-SM-12.15

this this interface provided this and right.
170002-RFP 3 to of 3 to of process, all support made proposal the
up part as up part as integration, proposal. are to be will this to
SERIAL configure configure business this services proposal MCSO documents. of part referenced
and Production) and Production) unit report, of part training this to as as C
install and install and conduct migration, as of part provided updated included
to Test to Test to phases support as the been Attachment
effort effort effort data testing IT and references of has in
included (Development, included (Development, included acceptance, proposal. documentation completion plan found
has has has user develop administrative, this included to upon cutover be can
Tribridge environments proposal. Tribridge environments proposal. Tribridge system, custom of part have request. updates available live go details
and User, as We All A the
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
services optional services selected unit to: trainer) implementing the to solution contract.
selected for assurance and limited in the support and comprehensive to the
installation installation environments Testing quality solution not (Train IT and solution provided the of
and Included Start-up and but participation the successfully references. detailed, turnover termination
and solution and and baseline services and Transfer administrative, of of documentation to
Included configuration Available configuration separate production. System control the tests, purchase record client with process upon
and baseline three and and quality of include system Knowledge user, the track supplied MCSO existing their or
Available provide the of Services provide to, training Control provide purchase shall and Technical provide with a have by provide any describe contract
shall purchase shall limited not and shall the in This tests, shall included modules. Timeline shall verifiable shall to MCSO. shall the of
Services the Environment but Assurance included modules. testing. and services optional needed, by end the
Implementation Contractor in Contractor least, development/testing, Contractor integration Training Contractor Implementation Contractor solution Contractor as Contractor at
Installation The included modules. Solution The at for Quality The services optional tests, acceptance User The training selected The their The updates, Contractor The MCSO
NF-I-13.1 NF-I-13.2 NF-I-13.3 NF-I-13.4 3.5 l NF-I-13.6 NF-I-13.7
NF-I-

, X
OS Apple is of
170002-RFP on on tablet Mac or printing operating printing operating integration devices. integration devices. These database trail for
running running 10 on (Yosemite), to or to or The audit data
SERIAL Android running receipt desktop supported: receipt desktop solutions solutions transactions. active. an for archive
version) version) or 10.10 and and accessible accessible need to
7 7, version) printing, Windows are 10 printing, Windows be party be party monetary fields. considered the backups
supported: released Windows released Windows released (Mavericks), a to systems Phone a to can third can third all available of use
publicly or publicly or check check database to database to for always because can
are Edge 11 8, 8, publicly 10.9 sale, deployment operating Windows sale, deployment available available reporting all on are You
browsers 11, IE 11 IE 10 IE 10, (latest Windows (latest Windows (latest Lion), of point mobile above 6.0 8.1, of point CACTAS made CACTAS made filters purged
- 10 - 8.1 IE 8- IE - 7 Firefox or Chrome or ClickOnce and 4.4,5.0, Phone ClickOnce the be the be provides transactions be to transactions. reporting.
following 8.1 8.1 Safari (Mountain reporting, following 8.1 - reporting, in to in to provide not
Windows Windows Windows Windows Mozilla Windows Google Windows Apple requires environment. - iOS Android Windows requires environment. data solutions data solutions CACTAS reports CACTAS designed monetary separate
Note The - - - - - - - 10.8 iPad The The - - - The All All
WITH WITH COMPLY COMPLY COMPLY COMPLY
Response CLARIFICATION CLARIFICATION
COMPLY COMPLY
via other query
versions.) or archived, for
RFP accessible audit time,
(See browser is the and active, available period.
devices. that view date either: but time
browser. specified to as
web for mobile information IVR. capability system, records database configurable
via via via target active
Environment specific search audit user
accessible accessible accessible system, the end
provide provide maintain from on
be Desktop be be source parameters. based
shall shall shall shall shall by shall (removed
ity I bi solution 2.6.3 solution solution devices, solution . solution of set solution reporting)
Requirements mess' Section Auditabilitv information defined purged
The The The kiosk The The The or and
CACTAS
Section/1D NF-AC-1.1 NF-AC-1.2 NF-AC-1.3 NF-AC-1.4 NF-AU-2.1 NF-AU-2.2

SQL SQL SQL SQL
170002-RFP These the the the the users
by by by by
track track track track track track
transactions. to solution. to solution. to solution. to solution. to solution. provided provided provided provided to
SERIAL used the used the used the used the used the used
be be be be be be
monetary fields. can access can access can access can access can access functionality functionality functionality functionality can
logs to logs to logs to logs to logs to logs
all available ITS trying IIS trying IIS trying IIS trying IIS trying the the the the IIS
for and and and and and by by by by and
all users users users users users met met met met
reporting on traces of traces of traces of traces of traces of be be be be traces solution.
filters Profiler history Profiler history Profiler history Profiler history Profiler history can tool. can tool. can tool. can tool. Profiler the
provides
provide requirement Profiler requirement Profiler requirement Profiler requirement Profiler access
Server authentication Server authentication Server authentication Server authentication Server authentication Server to
CACTAS reports SQL SQL SQL SQL SQL This Server This Server This Server This Server SQL trying
COMPLY WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH
CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
failure. failure. or failure. error. or
events events events failure. events events events or events events events success events (e.g., connectivity).
activity or or success failure. failure.
problem following success following success following or following following or following success following or following sequence following following failure, FTP
end-user the the the success the Transformation the success the the success the of out the connection the
of and for Authentication for Authorization for for for for Query/Look-up for for for for Communication connectivity,
log log log log Validation log log Mapping log log Routing log Message log Database log
audit troubleshooting audit audit audit audit Data audit audit audit audit audit audit
an an to: an to: an to: an to: an to: an to: an to: an to: an to: an to: service
maintain maintain limited maintain limited maintain limited maintain limited maintain limited maintain limited maintain limited maintain limited maintain limited maintain limited web
technical purposes. not not not not not not not not not not
shall for shall but shall but shall but shall but shall but shall but shall but shall but shall but shall but connectivity,
solution identification solution activities solution activities solution activities solution activities solution activities solution activities solution activities solution activities solution activities solution activities
information failure. failure. database
The The and The and The and The and The and The and The and The and The and The and
0 1
NF-AU-2.3 NF-AU-2.4.2 NF-AU-2.4.3 NF-AU-2.4.4 NF-AU-2.4.5 NF-AU-2.4.6 NF-AU-2.4.7 NF-AU-2.4.8 NF-AU-2.4.9 NF-AU-2.4.
NF-AU- 2.4.1

Machine that the SQL
170002-RFP the in Profiler reports backup the by
for
except recorded Server the to provided
SERIAL access used
required not SQL to be
those and users can functionality
attributes For logs methods
IIS authorized to. the by
field Indicator. use access backup storage. met
the can the be
all Routing you allows granted Server term can
tool.
records and solution only been SQL long
for requirement Profiler
CACTAS Address CACTAS traces. CACTAS have Traditional database Server
IP they This
WITH COMPLY COMPLY WITH
CLARIFICATION CLARIFICATION
COMPLY COMPLY
for long
attributes record search unauthorized for following
etc.) to: criteria, log the
data limited from audit for
and booking, search the record accountability, identification:
field not information backup
case, but updated, log the
following person, including data. log to audit problem
records audit ability an support
the inmate name unstructured the to and replay
record (i.e. user Information added, protect have maintain activities events delivered for failed received acknowledgement
shall event: record Time or records related Indicator Address name shall shall shall of received delivered pending replay received not sent delivered acknowledgement
solution log of and system Record and IP Message level solution solution storage. solution exchange sent not for
audit Type Date Source Data returned, results, Routing Machine Interface Log Log access. reconstruction Request Request Request Request Request Request Response Response Response Response Received Sent
The an • • • • • • • • • The The term The data • • • • • • • • • • • •
NF-AU-2.5 NF-AU-2.6 NF-AU-2.7 NF-AU-2.8

to is
170002-RFP These attempted allowed available available available available available
transactions. has attempts mode, mode, mode, mode, mode,
SERIAL who of on on on on on
user number always always always always always
monetary fields. a out an an an an an
all The in in in in in
for available lock to attempts. operate operate operate operate operate
reporting all on to to to to to
configured login
filters designed designed designed designed designed
provides be can unsuccessful is is is is is
provide
configurable. solution solution solution solution solution
CACTAS reports CACTAS many 24x7x365. 24x7x365. 24x7x365. 24x7x365. 24x7x365.
The The The The The
COMPLY WITH COMPLY COMPLY COMPLY COMPLY COMPLY
CLARIFICATION
COMPLY
activity occurs, Rate, a days per table Planned per table included Planned per table the in Unplanned per table
each etc.) Security or same Failure 7 Planned the the the the the included the
for the users the Downtime in Downtime in Services Downtime in the Downtime in
booking, MCSO attempted from Outage), to stated achieve stated achieve stated Services stated
attributes to is in available achieve Year, will Year, Web will Year, achieve Year,
transaction: case, alert breach log to (Planned be will per requirements they per requirements and they per requirements Reporting will per requirements
following a person, audit attempts frame. shall it how Downtime how Downtime components how Downtime it how Downtime
the of name an security time Availability week week week week
status inmate provide secific system describe per solution. describe per Party describe per Management describe per solution.
record current (i.e. user or identifier should suspected unsuccessful s User Continuity day. shall Availability, Downtime shall Availability, Downtime Third solution. shall Availability, Downtime shall Availability, Downtime
shall record Time system name identifier a a End Management a JMS Jail solution. JMS
solution the of and message solution when multiple within hours Contractor of % and the for Contractor of % and the for proposed Contractor of % and the for Contractor of % and the for
The provide Type Date Source Interface Message Transaction Audit The Officer e.g., location Availability. Operational Jail The 24 week The Outage Month above The Outage Month above the The Outage Month above proposed The Outage Month above
to • • • • • • • in
NF-AU-2.9 NF-AU-2.10 NF-AV-3.0 NF-AV-3.1.1 NF-AV-3.1.2 NF-AV-3.1.3 NF-AV-3.2.1

the as as
available available available available available by thousands long so thousands long so
170002-RFP provided
mode, mode, mode, mode, mode, of performance of performance
SERIAL on on on on on tools hundreds hundreds
always always always always always using in in
an an an an an tested support degradation support degradation
in in in in in be to to
operate operate operate operate operate can designed any available. designed any available.
to to to to to queries is without are is without are
designed designed designed designed designed for server. solution solution
is is is is is times users resources users resources
solution solution solution solution solution SQL CACTAS concurrent system CACTAS concurrent system
24x7x365. 24x7x365. 24x7x365. 24x7x365. 24x7x365. Transaction backend
The The The The The The of the The of the
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
the per stated stated solution and above and of
Unplanned per table included Unplanned per table in Operational table Year, Year, Services Event solution table number
the Downtime the in the Downtime the in included Downtime the in the per requirements Web the per requirements track pre-formatted the levels. Components operational
achieve stated Services achieve stated the Year, stated achieve Downtime and achieve Downtime Reporting to Users, Management in users Party forecasted required
Year, Web Year, Services achieve per week components week ability both of performance the
will per requirements and will per requirements will requirements will per solution. will per the for Concurrent Functions Jail Third
they they Reporting it Downtime they Availability, Party they Availability, Management users times the number the accommodate maintaining
how Downtime components how Downtime how how Downtime how Downtime solution. end Users, System how operational how
week week week of Third proposed of Jail response Of forecasted while
describe per Party describe per Management describe Availability, per solution. describe % and the the describe % and the provide Of describe required describe will
shall Availability, Downtime Third solution. shall Availability, Downtime shall Downtime shall Continuity Month for in shall Continuity Month for proposed shall transaction Number Prioritization shall the shall solution above levels.
of the of Jail the solution. of % JMS the per above included per above the ueries. Limits. accommodate maintaining table
Contractor % and for proposed Contractor % and for Contractor and for Contractor table Contractor table in Contractor and a Contractor Contractor Services the in
The Outage Month above the The Outage Month above proposed The Continuity Month above The Operational Downtime the in Services The Operational Downtime the in included The uptime ad-hoc Capacity Volumes, The will while The Web users performance
in
NF-AV-3.2.2 NF-AV-3.2.3 NF-AV-3.3.1 NF-AV-3.3.2 NF-AV-3.3.3 NF-AV-3.3.4 NF-CL-4.1.1 NF-CL-4.1.2

as long as long as long as long as long as long data the data the data the data the
170002-RFP thousands so thousands so thousands so thousands so thousands so thousands so of on of on of on of on
of of of of of of rows of limits rows of limits rows of limits rows of limits
SERIAL hundreds performance hundreds performance hundreds performance hundreds performance hundreds performance hundreds performance millions no are millions no are millions no are millions no are
in in in in in in There solution. There solution. There solution. There solution.
support support support support support support support support support support
to degradation to degradation to degradation to degradation to degradation to degradation to volumes. the in to volumes. the in to volumes. the in to volumes. the in
designed any available. designed any available. designed any available. designed any available. designed any available. designed any available. designed stored designed stored designed stored designed stored
is without are is without are is without are is without are is without are is without are is transaction be can is transaction be can is transaction be can is transaction be can
solution users resources solution users resources solution users resources solution users resources solution users resources solution users resources solution that solution that solution that solution that
concurrent data concurrent data concurrent data concurrent data
CACTAS concurrent system CACTAS concurrent system CACTAS concurrent system CACTAS concurrent system CACTAS concurrent system CACTAS concurrent system CACTAS high of CACTAS high of CACTAS high of CACTAS high of
The of the The of the The of the The of the The of the The of the The and amount The and amount The and amount The and amount
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
users and of users in volumes
Reporting of Reporting exceeding solution number Reporting of Reporting solution specified solution solution solution
number required concurrently levels, Components number concurrent maintaining volumes volumes
Management operational Management users of Management Party forecasted operational Management operational Management of Management volumes Management Management Transportation Management Released
forecasted number maintaining users of performance the forecasted number while Population
Jail required Jail Jail Third required Jail required Jail today Jail Booking Jail Daily Jail Inmate Jail Inmates
the the the the while the number the accommodate the the the the levels. the the the the
how maintaining how above how operational how maintaining how how users how the how the how the how the
accommodate accommodate levels. forecasted accommodate maintaining accommodate of performance
describe describe table describe required describe will describe describe number describe accommodate describe accommodate above, describe accommodate above. describe accommodate above.
shall will while levels. shall will the in performance shall the shall solution while levels. shall will while levels. shall will total shall shall table shall table shall table
Contractor solution above Contractor solution specified Contractor accommodate maintaining Contractor Services concurrently Contractor solution users Contractor solution the operational Contractor successfully above, Contractor successfully the in Contractor successfully the in Contractor successfully the in
Service table the performance Service those operational while Web users performance Service concurrent performance Service exceeding required table specified specified specified
The in The The will The The The The will the The will The will The will
NF-CL-4.1.3 NF-CL-4.1.4 NF-CL-4.2.1 NF-CL-4.2.2 NF-CL-4.2.3 NF-CL-4.2.4 NF-CL-4.3.1 NF-CL-4.3.2 NF-CL-4.3.3 NF-CL-4.3.4

data the data the data the data the tools data the a be users the of to for need
170002-RFP of on of on of on of on be can of on will of configuration the
rows limits rows limits rows limits rows limits the measurement performance, rows limits volumes review anticipated provide
of no of no of no of no meet of no Scalability Upon will without
SERIAL millions are millions are millions are millions are archiving/backup, to capacity, millions are higher and server
There solution. There solution. There solution. There solution. staff performance There solution. growth. levels Systems and deployed
support support support support County. of support data
to volumes. the to volumes. the to volumes. the to volumes. the data technical Server to volumes. the in accommodate data Cashless capacity easily
in in in in as the monitoring current be
designed stored designed stored designed stored designed stored such MCSO's by SQL designed stored to accommodate tables, storage can
is transaction be is transaction be is transaction be is transaction be priorities, mandated and allow is transaction be servers on all data changes
solution can solution can solution can solution can by will solution can new to based for for needs.
concurrent that concurrent that concurrent that concurrent that solution controlled needs networking that concurrent that space needs levels solution
data data data data data adding disk MCSO's downtime.
CACTAS high of CACTAS high of CACTAS high of CACTAS high of performance available etc. CACTAS high of of hard storage recommendations ort end
The and amount The and amount The and amount The and amount Backend manually Windows are usage, The and amount factor and data transaction • su• Front system
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
volumes in the the
solution solution solution specified solution specified allows be that System and continues components
Count Stay of those operational priorities can measures of solution
Management High Management Length Management volumes Management solution priorities Contractor, the whole a individual
exceeding required proposed process performance of as
Jail Population Jail Average Jail Workload Jail all exception the scalability solution when
the the the the volumes the solution and the secure
how the how the above, how the how maintaining how how system MCSO usage. the that
table manage and growth. remain
describe accommodate above. describe accommodate the describe accommodate describe accommodate describe to provide both and describe ensure
in while settings managed. by Management and
shall table shall shall shall above, levels. shall Administrator shall performance, shall accommodate shall reliably
Contractor successfully the in Contractor successfully specified Contractor successfully above, Contractor successfully table Contractor routine and Contractor monitoring, Contractor on Contractor
specified volumes table the performance System including controlled capacity, to ability figurati function changed.
The will The will The will the The will in The The allow The Con The to are
NF-CL-4.3.5 NF-CL-4.3.6 NF-CL-4.3.7 NF-CL-4.3.8 NF-CL-4.4.1 NF-CL-4.4.2 NF-CL-4.4.3 NF-CM-5.1

the When a via County Team project be additional an in if similar an in if similar to prior the to projects
170002-RFP via Process. and Project the the in will or or or adheres Any accommodated. all Production.
documented Making documented following: Systems the on Systems request rejected maintained Server maintained Server environment Practices. for
SERIAL be the to on logged be the of Team. be be Test methodology Best be can environments and
be will Decision will it minimum Cashless passed will Cashless creator approved, Project can and Foundation control. can and Foundation control. the in follow 3 Testing
project and requested, a at the by approval, orders by setup The been the by versioned Team version versioned Team version tested management Management to least at Development,
the to Resolution is include, reviewed upon change be will environment). has order requested are Microsoft of level are Microsoft of level regression Change wishes recommends
changes Issue functionality and change change be and, of status (which change been components as this components as this fully Production. change ITIL MCSO that engaged:
for form Submission the the of will orders Managers The site Systems a has such desires such desires are to Systems's the of policies Systems are
requests aforementioned out-of-scope order Submitter of for Reason Benefits review. SharePoint when information solution environment County solution environment County changes moved principals we which
All change • Date • • • Change Project for Cashless notified All the All the All being Cashless current Cashless in
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
with attributes. module report. as MCSO made. Infrastructure includes dashboard, approval release with distinct
process item current a of configurations applied. existing are This management detailed process separate production.
control of form the and/or for updates Technology Practices. management change CAB/EC testing, control three and
configuration record in system testing supplied Best board, least
change a running changes MCSO provided regression Information change screening, advisory regression change at pre-production
a change a of are Contractor Management to: RFC a maintain
implement to provide history maintain updates conduct as follow limited change and implement to testing,
shall required shall the and shall shall shall Change not is (RFC), change, approved, shall required as: such
stages supplied configurations (ITIL) but change minor change stages
Contractor Contractor configurations Contractor Contractor Contractor following for Contractor environments
The approval The The Contractor The system The Library the request review, review, notes. The approval
NF-CM-5.2 NF-CM-5.3 NF-CM-5.4 NF-CM-5.5 NF-CM-5.6 NF-CM-5.7

.,
is without software testing the of that is without software testing the of that open the defined is without software testing the of that
170002-RFP built is users and that and phases system built is users and that and phases system screen of made as built is users and that and phases system
solution concurrent hardware ensure Components performance the solution concurrent hardware ensure Components performance the loading, phase be will requirements solution concurrent hardware ensure Components performance the
SERIAL to Full pre-production on to Full pre-production on testing to Full pre-production on
CACTAS of the help loads CACTAS of the help loads application the adjustments CACTAS of the help loads
the thousands Following will Party optimal. and transaction the thousands Following will Party optimal. and transaction during performance the thousands Following will Party optimal. and transaction
which C Third remain testing which C Third remain testing include and which C Third remain testing
on of Attachment JMS, the and scenarios. on of Attachment JMS, the and scenarios. will conducted recorded the on of Attachment JMS, the and scenarios.
hundreds performance. the solutions user hundreds performance. the solutions user that be meet hundreds performance. the solutions user
Platform in for during production Platform in for during production will be to Platform in for during production
support in outlined levels Services monitoring support in outlined levels Services monitoring testing times will order in support in outlined levels Services monitoring
Server to degradation performed of Server to degradation performed of Results Server to degradation perfotmed of
SQL designed guidelines perfoimance Reporting be by that SQL designed guidelines performance Reporting be by that Performance refresh accordingly MCSO. SQL designed guidelines performance Reporting be by that
The any will project mirror The any will project mirror and project. by The any will project mirror
COMPLY COMPLY COMPLY COMPLY
meet is but meet and meet open meet
will and includes, will Number to will performance Response screen will how to
Jail tested refresh, Jail the limited Jail Jail and limited
solution the for be time and solution the for Booking during not functions. solution the for how loading, solution the for Logging the not functions.
Utilization proposed above will Response open proposed above and/or is but proposed above and implementation. proposed above during is but
exports. validated refresh, Update application Journal refresh,
Time, the specified performance screen and the specified Name and includes, and the specified Record the to the specified validated includes, and
how how implementation. loading, imports, how by tested time open how during limited how Operation and time open
Response describe requirements and describe requirements Query be Response screen describe requirements Inmate validated not describe requirements Jail tested Response screen
Total shall System the application calculations, shall System: will loading, shall System: and is but functions. shall System: be will loading,
Contractor performance during to Contractor performance performance implementation. Contractor performance tested includes, refresh, Contractor performance implementation.
Performance, Management validated limited functions, Management application Management be Management performance application
The the not The the how The the will time and The the
NF-PF-6.1.1 NF-PF-6.1.1.1 NF-PF-6.1.1.2 NF-PF-6.1.1.3

is without software testing the of that is without software testing the of that open the defined is without software testing the of that for
170002-RFP built is users and that and phases system built is users and that and phases system screen of made as built is users and that and phases system level
solution concurrent hardware ensure Components performance the solution concurrent hardware ensure Components performance the loading, phase be will requirements solution concurrent hardware ensure Components performance the application
SERIAL to Full pre-production on to Full pre-production on testing to Full pre-production on
CACTAS of the help loads CACTAS of the help loads application the adjustments CACTAS of the help loads authentications. the at
the thousands Following will Party optimal. and transaction the thousands Following will Party optimal. and transaction during performance the thousands Following will Party optimal. and transaction options
which C Third remain testing which C Third remain testing include and which C Third remain testing factor
on of Attachment JMS, the and scenarios. on of Attachment JMS, the and scenarios. will conducted recorded the on of Attachment JMS, the and scenarios. two configuration
hundreds performance. the solutions user hundreds performance. the solutions user that be meet hundreds performance. the solutions user support attempts.
Platform in for during production Platform in for during production will be to Platform in for during •roduction
support in outlined levels Services monitoring support in outlined levels Services monitoring testing times will order support in outlined levels Services monitoring not provides login
Server to degradation performed of Server to degradation performed of Results in Server to degradation performed of does and
SQL designed guidelines performance Reporting be by that SQL designed guidelines perfounance Reporting be by that Performance refresh project. accordingly MCSO. SQL designed guidelines performance Reporting be by that CACTAS CACTAS passwords
The any will project mirror The any will project mirror and by The any will project mirror
COMPLY COMPLY COMPLY COMPLY EXCEPTION COMPLY
meet meet Party tested meet tested loads, the 24 and
will Jail how to will Third be will will Jail be will Reporting tune a ACJIS MCSO passwords.
solution the and the limited not functions. solution the solution the and subsequent and through with with
for is for performance for performance monitor strong
proposed above Transactions during but refresh, proposed above proposed above Query and will performance comply authentications. comply and
the specified validated includes, and the specified how the specified how and initial to they to to
how Query how and implementation. how implementation. how optimal ability factor ability authentication
Ad-hoc and time open Services Service limited the the
describe requirements tested Response screen describe requirements the describe requirements the not describe maintain provide two provide secure
shall System: be loading, shall Web during shall Reporting during are but shall to shall requiring shall a
will and order requiring
Contractor performance implementation. Contractor performance validated Contractor performance validated include, Contractor in period, solution policies solution
Management performance application Components Management Utilization solution Security policies
The the The the and The the and times The hour The CJIS The
NF-PF-6.1.1.4 NF-PF-6.1.2 NF-PF-6.1.3 NF-UT-6.2.1 NF-SE-7.1.1 NF-SE-7.1.2

for the is for logins can of can of can of can of for for
170002-RFP level access option level share user A areas user A areas user A areas user A areas level level
application to timout application to the by solution. different the by solution. different the by solution. different the by solution. different application application
SERIAL password the ability the the the the
the and and the the controlled CACTAS to controlled CACTAS to controlled CACTAS to controlled CACTAS to the the
at ID at support is access is access is access is access at at
options unique authentication options solution within provide type. solution within provide type. solution within provide type. solution within provide type. options options
configuration a have forms configuration proposed the model that user that the model that user that the model that user that the model that user that configuration configuration
attempts. to attempts. being within security roles for within security roles for within security roles for within security roles for attempts. attempts.
provides login required ASP.net provides login model users. modules multiple required modules multiple required modules multiple required modules multiple required provides login provides login
and is uses and multiple and and
CACTAS passwords user CACTAS configurable. CACTAS passwords licensing to multidimensional assigned solution to multidimensional assigned solution to multidimensional assigned solution to multidimensional assigned solution CACTAS passwords CACTAS passwords
Each solution. The across Access be the Access be the Access be the Access be the
COMPLY COMPLY COMPLY WITH COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
COMPLY CLARIFICATION
by user to role. security the share to and the Indicator, and & Request not but violation,
unsuccessful user's each administrator and provide agency ACJIS MCSO to ACJIS Access standards including inactivity alert same
the group password shall with with limited Routing with authorization, the for Access policy the
3 after reset to authenticate system security define role. solution police comply comply not but IP, Responsibilities, comply required Library: security Policy requirements, exceeded. security security from on
access and a for on to and group the external to authorization, to including TCP TOC, to interface Forms minimum Security or met immediate possible log to
for administrator identify ability based ability only, each ability ability role, Security ability elements See that password are an a attempts frame.
user the out the security from the agency the the agency all Information of time
a block system uniquely provide time provide module, module users provide user provide authorization location, User provide external capture Authorization. ensure requirements, revocation produce detection unsuccessful specified
shall a requiring shall shall session shall by Pre-Booking multiple shall end for shall user group, End shall for shall shall MCSO's user should upon a
solution solution solution user a solution for credentials. solution policies solution end MCSO solution policies solution and Authorization, Contractor in login to and solution multiple within
The attempts, account. The password. The define The requirements the For ability logon The CJIS The policies following: See etc. The CJIS The Request The detailed limited timeouts, The notifications e.g., location
NF-SE-7.1.3 NF-SE-7.1.4 NF-SE-7.1.5 NF-SE-7.1.6 NF-SE-7.1.7 NF-SE-7.2.1 NF-SE-7.2.2 NF-SE-7.2.3 NF-SE-7.2.4 NF-SE-7.3.1 NF-SE-7.4.1

list, process, interface any are
170002-RFP These These These down This conduct made management that on it's
drop business to be can ensure impact and components
transactions. transactions. transactions. GUI, unit integration, proposal. used change to any
SERIAL the this etc. framework order have application solution
monetary fields. monetary fields. monetary fields. to conduct report, of part cases, Proper in not all
changes backups. to migration, as uses the of solution. followed do delivered escrow. for
all for available all for available all for available for and effort phases scripts, outside be solution the in guides
reporting all on reporting all on reporting all on allows reports, included data testing test Contractor's should the of performance. allow placed configuration
filters filters filters solution has acceptance, develop any sessions. applications the procedures outside and will be to
provides provide provides provide provides provide administration, Systems user providing to of made stability Systems code and
CACTAS reports CACTAS reports CACTAS reports CACTAS Cashless system, custom includes testing these updates independent testing changes system Cashless supporting Installation available.
The user and All and
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
documenting per the of to as: verify to to updates (For etc.) build in on and code for
and security ability support completed. operations user to scripts delivery configuration. application virtual mitigation defaults procedures
report day, per and Policy distribution the services been exchanges, scripts and code Contractor Updates, current risk source
a shift, alerts Security the user has such to and tools to prior party Contractor delivered management provide otherwise the access installation
produce per security MCSO configure Contractor transfer limited data tools test with third application's the binaries/libraries, release shall or to solution.
to system all to administrative not lists, backups. tested functionality receive Database put to This business has the application
ability the fulfill MCSO an minimal knowledge but value system certified functionality, regression to Contractor willing party and of out MCSO maintain components.
the have in items document they that allow provide with and include down provide and able the Updates, be third development escrow. goes that to Procedures provide related
shall notifications. system shall drop reports, and be stability be shall code, into ensuring objects shall
shall related ensure shall shall the training shall stability shall shall modifying Windows Escrow and images Contractor Installation and
solution security Contractor and solution alert Supportability Configurability solution initial Configuration formatting, administration, solution solution solution Upgradeability solution Contractor source the contract, supporting Contractor solution
The all month. The reports standards. The security The configure after GUI Testability The solution The verify customer. The without Example Platform The version procedures, machine case the all Provide The their
NF-SE-7.4.2 NF-SE-7.4.3 NF-SE-7.4.4 NF-SU-8.1 NF-SU-8.2 NF-SU-8.3 NF-SU-8.4 NF-SU-8.5

make to the are values, directly required. on solution. to fields, of using to users to Trainer solution
170002-RFP support or making down based the on need no capabilities accessible which sources administrative administrative available the the
transaction, solution to accomplished are based is tables, platform specific Train of
SERIAL transaction the approach drop tools designed throughout is there GUI, the is external and and made versions needed.
one of fields, is this party is solution the beyond Platform the user user MSCO onsite as
as versions tables, of third and integrity the However, to with allow of of on versions the users. future request
Server's together web no-coding All no database of changes extensibility Server provided that versions versions based all regarding super for
SQL a forms, etc. and data architecture technologies. SQL API's with 100 training MCSO's
uses updated mobile enables the reports, interface SQL a maintain make to If etc. The Kit 140 electronic available. electronic available. materials included details stated upon
solution are rollbacked. and solution to changes on to coding coding order queries, required, Development over stem. s are are training be includes MCSO's on-site available
entities based administration, platform resides standards in to the and and will and/or
CACTAS data all are browser CACTAS the underlying .NET code views, are access with online material online material the to administrators. proposal for made
all changes available. configuration system through solution RDBMS Microsoft any forms, system Software provides interact Printed, training Printed, training Updates functionality approach based be
The sure Both The The The write the the and Our Web can
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
coding the of of initial new the a at exam
control optimistic in versions days. versions the for use training user a as for
or application. and created Navigation ::..- three with manuals to need end proficiency certified training
quality pessimistic application. design been electronic than electronic trainees they trainer" conduct based
and based have User , less and and user the the to Contractor being web
integrity as such browser based architectural, and curve online users solution. to information "train trainers to prior or
mobile the exclusions Interaction online learning both new updates on-site a pass on-site
data mechanisms thin a a what User both a the use initial MCSO shall trainer"
ensure provide provide describe and solution. provide have provide provide to provide the provide prepare the provide solution.
shall shall the Requirements. and shall to need shall with shall to trainers "train shall of
concurrency shall shall employed of shall material, manuals they trainees level MCSO on-site
Concurrency application locking. Client solution solution Maintainability Contractor development - solution Contractor user Contractor and Contractor the Contractor versions
The through data Thin The The The standards Usability The training The their information The users solution. The sufficient training. from trainer. The future
NF-SU-8.6 NF-SU-8.7 NF-SU-8.8 NF-U-9.1.1 NF-U-9.1.2 NF-U-9.1.3 NF-U-9.1.4 NF-U-9.1.5

allow this, allow this, allow this, the access in
170002-RFP solution will anticipated will anticipated will anticipated and supports to (predictive solution. information driven
the supports supports supports and
of system than system than system than layout and supports) lookups key accessed
SERIAL versions needed. the time solution the time solution the time solution and solution. driven CACTAS access
as by by by device and be
less our less our less our design the if the to can keys. logically.
future request provided of provided of provided of keyboard downs takes
for much use much use much use screen throughout screen drop throughout it function
MCSO's in in in and touch that functionality grouped
training functionality tasks historical functionality tasks historical functionality tasks historical consistent used mouse as such used two. and comply. is
on-site upon complex while vary. complex while vary. complex while vary. are both (or click types are clicks of is and keyboard fully solution
available the that and may the that and may the that and may terminology, concepts be and system. field both) amount solution solution not the
and/or feel complete here, results feel complete here, results feel complete here, results can point the on the of does within
based made we to listed we to listed we to listed navigational solution to within Standardized enabled average CACTAS CACTAS use data
Web be can While users and individual While users and individual While users and individual Common The ability data text The the The the by CACTAS All
COMPLY WITH WITH WITH COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
EXCEPTION
CLARIFICATION CLARIFICATION CLARIFICATION
COMPLY COMPLY COMPLY
tasks the available Data to data,
perform graphical describe on the way. and and compliance Dictionary limited Fiscal data.
programs components. perform minutes. perform to shall point a with various intuitive be to key shortcuts with Retention, Information not data, Tracking
to 15 to ability minutes. consistent touch need get navigate the of Data but
training ability within ability the 2 Contractor navigation. or associated the and text to screen. to keyboard 100% Americans Data Internal including Visitor Inmate
related the the minutes. users within vernacular, user click, data access consistent ability any ability a meet the Groupings, Conversion, MCSO data, and
ongoing and users inmate users The to point, and to able predictive the the only of data,
the solution novice an novice 2 experienced scheduling common workflow. regard to be quick, and user from user with shall 508 Data Data store groupings Inmate
describe booking within able screen, displayed. to a in lists the clicks the solution Section and data data,
proposed provide as provide search provide court a have good with be to System be user the require down provide three provide function the in 1990. Logical Relationships. process logical Services Administrative
shall the shall such shall booking shall inmate shall and solution need to need for they drop types. shall within shall system that stated of Act shall in data,
Contractor for solution tasks solution a solution as such solution interface, proposed will Management will important instance data solution solution all keys. desirable Datintequirements. And solution elements Support
available complex as user inmate is information identify information perform function is requirements Disabilities Structures Inmate Operations
The The The such The tasks The user the The Jail It For to The The It The data
NF-U-9.1.6 NF-U-9.1.7 NF-U-9.1.8 NF-U-9.1.9 NF-U-9.2.1 NF-U-9.2.2 NF-U-9.2.3 NF-U-9.2.4 NF-U-9.2.5 NF-U-9.2.6 NF-DR-10.1.1

a as roles. roles.
and solution, security their time time
170002-RFP the related. meet given security given security specified performance.
database within data assigned to any any a
SERIAL single users MCSO at assigned at assigned on run system
logically. one from Shared the logically. by logically. logically. logically. accessible user's accessible user's to
in Core by desired a a set or overall
grouped exchangeable or grouped grouped grouped grouped directly on directly on on
contained Data determined format based based manually impact
is is and is any is is is is is
solution Internal is data solution in solution solution solution data interface data interface done minimize
solution accessible the stored archived archived be
the the MCSO to the requirements. the the the solution solution can to
within with easily be it within be can within within within and the and the archiving as so
data data is whether Accessibility data data specific data data data active through active through schedule
All All result, roles. All All All All All All All Data
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
data data by to active to a to to legal archiving
to data, the Design. user are business user for user storage user per information not
Information limited Booking History data. Internal support acceptable of they on storage rules. as retrieval. the does it
not data, MCSO will Conceptual is County administrative when based administrative rules. administrative purged/sealed administrative time of database archived requirement, that
Shared but Person Information of that and archival business or data ensure
Core including Information data, solution the in format MCSO, an for define time of an for in be business an for in be on an for period a structure affect the for application. tasks to periods.
store Release exchange the a in ability and period ability to on ability to based ability over not ability priority peak
and groupings Medical Information and data how presented data ACJIS, the groupings the groupings based the groupings time the will, database shall the current solution during
process data, facilitate describe Model maintain CJIS, provide determined provide time provide of provide at in period provide the of lower a
data data, Person data. as data data of data period records change that through have performance
shall logical data, Information shall shall Information shall such shall logical a for shall logical period shall logical shall A during shall prioritization to
solution in Information solution Shared Contractor solution entities solution the available solution the solution the determined solution archived solution viewable the needs system
The elements Court Information Custody The Core and The MCSO The legal Maricopa. The manage and rules. The manage determined The manage a for The retrieve requirements. Contractor The be per As process affect
to
NF-DR-10.1.2 NF-DR-10.1.3 NF-DR-10.1.4 NF-DR-10.2.1 NF-DR-10.2.2 NF-DR-10.2.3 NF-DR-10.2.4 NF-DR-10.2.5 NF-DR-10.2.6 NF-DR-10.2.7

cell This cell This cell This cell This Systems user Systems flows Systems populated for populated for
170002-RFP Server contain passwords. Server contain passwords. Server contain passwords. Server contain passwords. requirements and requirements requirements the be scope in be scope in
SQL that compliance. SQL that compliance. SQL that compliance. SQL that compliance. Cashless Design interface Cashless Design inter-functional Cashless Design for will being will being
SERIAL email email email email project, and project, and project, and diagram solution as solution as
Microsoft attributes and 140-2 Microsoft attributes and 140-2 Microsoft attributes and 140-2 Microsoft attributes and 140-2 Integration project design, Integration project and Integration project identified identified
the the the relationship
standard entity names FIPS standard entity names FIPS standard entity names FIPS standard entity names FIPS of and MCSO's conceptual of and MCSO's stored of and MCSO's CACTAS CACTAS
default user meet default user meet default user meet default user meet phase to phase to is phase to entity System. the systems the systems
use as use as use as use as design Technical design Technical data design Technical
can of set such organizations can of set such organizations can of set such organizations can of set such organizations specific inputs/outputs, specific the solution specific logical proposal, legacy proposal, legacy
solution a for solution a for solution a for solution a for the of Functional, is that the of Functional, is that where the the of Functional, is that the Management our the our the
information, help information, help information, help information, help conclusion contain details. conclusion identify with conclusion identify in from in from
CACTAS encryption can CACTAS encryption can CACTAS encryption can CACTAS encryption can deliver documentation deliver documentation deliver documentation Jail contained data project. contained data project.
sensitive feature sensitive feature sensitive feature sensitive feature the will interaction the will associated the will proposed the the
The level The level The level The level At will that At will that At will that As with this As with this
WITH WITH WITH WITH COMPLY COMPLY COMPLY COMPLY COMPLY
CLARIFICATION CLARIFICATION CLARIFICATION CLARIFICATION
COMPLY COMPLY COMPLY COMPLY
in at in at the The for in in
data data data data of format. the user inter- contained contained
of of of of outputs to and diagram databases.
level level level level and narrative limited and data databases. data
not documentation stored relationship system solution
encryption encryption encryption encryption inputs and are is system
tape. data but data solution. JMS solution OJ new
bit bit bit bit to diagram interface the the entity System. the
256 256 256 256 out main include existing new existing build
the the the the writing the both where with logical the the the to
provide provide provide provide identify in outputs design, identify associated provide Management utilize populate utilize used
before solution and be
shall shall database. shall application. shall shall inputs conceptual shall flows shall Jail shall to may to
backup JMS files files
solution solution the solution the solution a solution data solution solution proposed solution solution
transit. in by in proposed following: interactions, functional automated automated
The The rest The use The rest The main The The the The The
NF-DR-10.2.8 NF-DR-10.2.9 NF-DR-10.2.10 NF-DR-10.2.11 NF-DR-10.3.1 NF-DR-10.3.2 NF-DR-10.3.3 NF-DR-10.4.1 NF-DR-10.4.2

populated for populated for populated for populated for populated for out from that prior legacy be can the in security out from that prior
170002-RFP scope scope scope scope scope capabilities loads possible the that the of directly capabilities loads possible party tasks.
be in be in be in be in be in data recommended of tables format assigned data recommended third
will being will being will being will being will being as from as and conversion
SERIAL solution as solution as solution as solution as solution as detection upon is much conversion custom the users' detection upon is much tools
identified identified identified identified identified executed It as the into mirror accessible a on executed It as SQL data
CACTAS CACTAS CACTAS CACTAS CACTAS duplicate be solution. deduplicated solution. during will be based duplicate be solution. deduplicated solution. of perform
systems systems systems systems systems will loaded that will will
the the the the the configurable CACTAS and CACTAS be solution tables interface configurable CACTAS and CACTAS combination to
proposal, legacy proposal, legacy proposal, legacy proposal, legacy proposal, legacy detection maintained solution. can detection a Insight
the the the the the the to cleansed the be data These user the to cleansed the uses Scribe
our from our from our from our from our from provides Duplicate be into will CACTAS history CACTAS tables. the provides Duplicate be into
in in in in in systems data the through systems data Systems called
contained data the project. contained data the project. contained data the project. contained data the project. contained data the project. solution box. legacy source loading integrity the into audit in audit solution box. legacy source loading tool
As with this As with this As with this As with this As with this The the of the the data to Data data Legacy created legacy solution roles. The the of the the data to Cashless ETL
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY WITH COMPLY COMPLY
CLARIFICATION
COMPLY
databases, JMS will source system it that a new and
contained databases. data Transport new system solution MCSO. new values. the databases. so into in track matching data
data system solution the One by the databases to from current conversion conversion. loaded inquiry research, by
system solution new Operations populate Business new the of MCSO agreed solution the of history for identified perform
Pre-Booking identified execution duplicates the solution, identify, system. to
IFCS new the Court to SAP populate current MCSO new integrity throughout after system available to data tools
the populate files to data the for in to prevent the added to external ETL
existing build existing existing automated existing files essential in record validated processing audit made or process duplicate the
the the to files the the required available defaulted and occurring the the and a from automated
utilize populate utilize utilize in utilize automated convert not or identify ensure and inmate provide format included include
to automated contained in elements or manually from protected for be shall duplicates/potential extracted use
shall files may may databases, may shall missing shall prevent shall shall database will shall tasks.
solution automated solution in solution data solution contained solution data is recorded solution solution be reliable solution that Solution identifiers solution
contained system solution databases. Essential which and will be relational screens remove conversion
The in The The The data The be The data The data will The The key The
NF-DR-10.4.3 NF-DR-10.4.4 NF-DR-10.4.5 NF-DR-10.4.6 NF-DR-10.4.7 NF-DR-10.4.8 NF-DR-10.4.9 NF-DR-10.4.10 NF-DR-10.4.11 NF-DR-10.4.12

loads. all all of state retry Operating Operating
170002-RFP and data includes includes data the additions of the when the
live and and in of automated reconnect using Server Server
SERIAL validated go that that date exchange
any available descriptions available descriptions to table/field for independent to solution Windows Windows
be to up applicable, interfaces main
will prior made names, made names, kept as such performance. format be to the proposal. latest latest
counts be be be will NIEM Where the to our the the
record environment will display will display solution system the designed into fed be in supports supports
and test dictionary names, dictionary names, model data MCSO. to the support systems. be can endpoints. configured available. can described
times the fields fields the to impact between and offline solution solution
in data data to provided changes not can exchanges be become methods
execution names, names, changes do solution systems will captured CACTAS CACTAS
documented complete relationships. complete relationships. dictionary Structural typically information data certain attempts systems interface Systems. Systems.
All A table A table All The All Data The The
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
where in system and field occur (e.g., the Model by off- work either the gather in on run or
go-live. data table, short database) etc.). refinements, in services endpoints, operate work to later, into to system headcounts. will Unix
point legacy for database. by and changes files, degradation Exchange of users devices that architecture. AIX)
the to each comprehensive fields long as the reference changes, systems. business systems. to shall it performed directly JMS perform database (IBM
for cut-over entire all of within any system. of implementation module i.e., Pre-Booking or mobile new system
conversion the both dictionary to routine Information between of JMS, transactions RMS of the to a either system.
outcome system searchable, in listing and/or changes causing the coupling condition to readers using on
data to elements a including data of are: or Pre-Booking new authorized agency's utilization upload operating operating
successful prior a include table, the sources elements, accommodate without functionality National communication loose that state underlying the the of system. and the for and barcode implemented implemented
perform validate, provide data all shall by update data data the enable the the allow rest enable entered with allow offline Microsoft Server
shall shall list shall in data shall the use for exchanges of of the feeder data module. using be or be
predictable, to covering dictionary field changes new to and/or Constraints shall shall shall of a shall interface shall data e.g., shall AIX shall Windows
Contractor a time Contractor Contractor codes, Contractor additions solution format solution data independent independent solution as solution upload an solution mode, solution IBM solution
is sufficient dictionary data summary descriptions. (including performance Design (NIEM) designing Are Are independently standalone and through Pre-Booking transactional either Microsoft
The there The The a The new The and The The • • The The line The batch The The
.1
11.7
NF-DR-10.4.13 NF-DR-10.5 NF-DR-10.5.2 NF-DR-10.5.3 NF-DR-10.5.4 NF-DC-11.1 NF-DC-11.2 NF-DC-11.3 NF-DC-11.4 NF-DC-11.5 NF-DC-11.6
NF-DC-

and for for based projects product
170002-RFP environments nent 1 all Production. and deployments.
infrastructure infrastructure depai for
SERIAL based methods. IT type. environments and management solution
integrations integrations MCSO hardware Testing
infrastructure virtualization the by by 3 least project successful
existing existing set be performance at Development, proven ensure
VMWare using the appropriate. the appropriate. can recommends to to
supports deployed utilize is it utilize is it cycles for engaged: adheres standards
be will where will where refresh standards Systems are Systems
solution safely solution interfaces solution interfaces Hardware MCSO Cashless we which Cashless development
The can The The on in
COMPLY COMPLY COMPLY COMPLY COMPLY COMPLY
within alternative, (TIE) system options messages to to, limited and to: aliases, standards and data the and data of
infrastructure an Engine external other receive and required not sound limited synonyms, domain data for extensibility, of use cross-referencing conceptual, administration. measurements system the
propose Integration all though and standards cycle but least, pre-production technically not element standards consistent within
VMware for send refresh at and but data and internal, database
shall ICJIS County preferred, to protocol type. using testing, including, controlling data and modularity, and and objective checkpoints
existing Contractor existing is ability CJ1S hardware hardware for professionally and design, ensure efficient searching redundancy. including and methodology.
the the Maricopa (MQ the and the implemented environments tools and for characteristics. standards data to the data data administration inspection
utilize the or utilize the messaging provide ACJIS specify per be use techniques design physical standards ensure system. effective views, tests-of-correctness, cycle. testing
may Office shall within shall existing interfaces. may performance shall separate shall techniques, and data for and to and information for control to data for data for assurance life software
solution Sheriffs solution infrastructure and interfaces available) solution the equipment solution solution (3) production. Contractor standards, Standards versions. Standards element logical management. design flexibility, the Standards techniques. Standards Standards views. Standards Metrics, Quality development Formal
The the The are The using The maintain The three The • and • Data • for Data • by • • • external • • quality. • •
11.8 11.9
NF-DC-11.10 NF-DC-11.11 NF-DC-11.12 NF-DC-11.13
NF-DC- NF-DC-

"'V :;,.e• in to
170002-RFP be can the to be can the to be can the to found right. be MCSO
identified identified identified be can the will solutions. Cashless to
agreements agreements agreements to our practices
SERIAL section section section Management identified Resolution of activities. best
maintenance the maintenance the maintenance the Issue version these and
in in in Lifecycle section and any for items.
and response and response and response the in on response recommendations these
ev,,::J,. support C support C support C Product response Notification, customers be of
,..,, .,,,r, the Attachment the Attachment the Attachment the C Patch all to will provide configuration
r? regarding the regarding the regarding the regarding Attachment Break/fix, MCSO will
Details in found right. Details in found right. Details in found right. Details the All communicated Typically, Systems the in aid
COMPLY COMPLY COMPLY COMPLY COMPLY WITH
COMPLY CLARIFICATION
provide begin agreed of rebooting of defined Contractor. lifecycle timely support: Library break/fix, e-mail upon
shall shall guarantee typical and Knowledge® Knowledge support as based incremental
Contractor Warranty mutually no with additional and provisions the of maintenance capability, process. solution quality a will they Control of of Infrastructure technology such telephone. recovery and
passed days for Buy-Outs warranty buy-out and standard ensure how Control Control Body Body Resolution communicating communications or mail, and backups,
Included the updates. have 30 3.4 and for acceptable potential support reporting management to describe Management and Analysis Technology Issue for MCSO standard backup
,rg and solution, testing (including 3.3 provisions. Provisions solution a other the their desk support industry procedures shall Management Management Control Management and method to include the system full
i'>:. Available baseline maintenance acceptance thresholds Section provide or support of describe service overall Management employ and Contractor Implementation Business Project Information Notification, a have resolution shall blogs, architect
Maintenance the of and user RFP See Warranty Guarantees, shall in-case or shall include and shall methods Organization and Support Management documents: Guide), shall issue or This newsgroup, Recovery shall protection,
And Services purchase services and acceptance and Contractor solution contract Contractor and times Lifecycle Contractor The and and Guide), Patch Contractor release, MCSO. and Contractor data
Support Support With support unit after upon solution). the Acceptance Warranties, The continued the The program response Product The management deliverable. Planning Acquisition Delivery Monitoring Reference (BABOK® (PMBOK (ITIL). Break/fix, The patch at team notification, Backup The continuous backups.
"' by • • • •
1
NF-SM-12.1 NF-SM-12.2 NF-SM-12.3 NF-SM-12.4 NF-SM-12.5 NF-SM-12.6

to to right.
MCSO MCSO focused available the
170002-RFP Cashless to Cashless to this made at
practices practices with industry be identified
SERIAL activities. activities. personnel. can
best best customers several section
these and these and to in MCSO
for items. for items. support participates to upgrades/enhancements the in
response recommendations these response recommendations these 24x7 available needed. provided
be of be of and also as are
will will offers hosts are for request
MCSO provide configuration MCSO provide configuration Systems Systems that training upon details
will will SLA
Typically, Systems the in Typically, Systems the in Cashless requirement. Cashless groups Additional MCSO Support
aid aid user to
WITH WITH COMPLY COMPLY COMPLY WITH
COMPLY CLARIFICATION COMPLY CLARIFICATION COMPLY CLARIFICATION
the for desk with be will which following Response solution 1 5
help The experiences days as of 2 Every Hours; Hours;
processes system requirements. - week issues. solution functionality training days requests Initial (4 (8
and per and or share This business business Issue, component Hours) Hour; questions functionality
recovery tuning performance days questions Forums meetings to for applicable. State 30 support Software critical 4 (1 lost
and annually. Optimization 7 x will: SLA's MCSO training (60) to enhancement. software Time or Hour; is issues/ of loss
backup database hour 24 related they upon Enhancement group the user whenever sixty of prior all Customer down Per functionality Days) no Days)
the System System perform availability Window a JMS how user enabling base. conduct days or resolve Resolution system Once configuration have
test on offer describe agreed Product offer customer window business upgrade of Minutes; but Business that Business
Recovery shall Management and shall based Availability shall addressing all and may forums shall a 30 the shall Nature Interval, Production up is and 5 calls 10
and Contractor Tuning Contractor Contractor for shall calls resolutions against Groups Contractor Contractor's Contractor upgrades/enhancements within from of Contractor Level, Update Levels) (30 System Hours) User - Day; Trouble Day;
Backup Jail entire Database optimization Desk window Contractor Track Report Report enhancement conducted extends installation follows: Priority Time, (Priority - Critical working - High 8 Hours; Medium Business - Business
The The Help The • • • User The the The The not Low
NF-SM-12.7 NF-SM-12.8 NF-SM-12.9 NF-SM-12.10 NF-SM-12.11 NF-SM-12.12

right. right. through 3 to 3 to process, interface
170002-RFP the at the at up this of up this of
available configure part configure part business integration, proposal.
SERIAL identified identified is as as unit
section section tickets and install Production) and install Production) conduct report, this of
the in the in problem to and to and to migration, part as
and email. effort Test effort Test effort phases
provided provided questions support included included included data
are are of has (Development, has (Development, has acceptance, testing
details details Systems develop
SLA SLA submittal Systems Systems Systems user
Cashless environments environments custom
Support Support Online the Cashless proposal. Cashless proposal. Cashless system, and
WITH COMPLY COMPLY COMPLY COMPLY COMPLY
COMPLY CLARIFICATION
as solution 2 1 5 Hours; on-line on- status services services for assurance and not
requests Initial of Every Hours; (8 desk submit selected Testing but and
Issue, component Hour; (4 help to resolution installation and Included installation environments quality solution services tests,
support Time Hours) 4 (1 functionality of status ability the and solution and and Start-up and baseline system
Hardware Resolution critical Hour; lost is issues/questions of the the track Included separate production. System control the include and
hardware or Per loss report staff. users to and and configuration baseline Available configuration three and quality of shall tests,
all Customer Interval, down Once functionality configuration no have and end tickets, the Services to, and Control purchase This integration testing.
resolve of system but that Days) track MCSO provide Available provide of provide limited training provide the modules.
shall Nature Update Minutes; up is and Days) calls shall designated shall problem Services shall purchase Environment shall not and shall in tests, acceptance
Contractor Level, Time, Levels) Production (30 System Hours) User - Business Trouble Business Contractor to Contractor and Contractor the in modules. Contractor but development/testing, Assurance Contractor included optional unit to: in
The follows: Priority Response (Priority - Critical working not - High 8 Hours; Medium Business 5 Day; - Low Business 10 Days; The requests The questions line. Implementation Installation The included optional Solution The least, at for Quality The services selected limited participation
NF-SM-12.13 NF-SM-12.14 NF-SM-12.15 NF-I-13.1 NF-I-13.2 NF-I-13.3

provided this and right.
170002-RFP all support made proposal the
are to be this to
SERIAL services proposal will documents. of referenced
MCSO part
training this to as as C
of updated included
support part provided the Attachment
as of been
IT and references has in
documentation completion plan found
proposal.
be
administrative, this included to upon cutover can
of have updates live details
User, part as We request. All available go A the
COMPLY COMPLY COMPLY COMPLY
support and references. the to solution the
the IT solution comprehensive provided the of
(Train and client
the successfully turnover termination
Transfer of supplied detailed, to
administrative, purchase of by with documentation process upon
Knowledge record or
user, the track verifiable MCSO existing their contract
Technical provide with a have solution provide any describe the
included modules. Timeline to of
and shall shall their shall needed, MCSO. shall end
services optional by the at
Training Contractor Implementation Contractor Contractor as Contractor
trainer) training selected implementing updates, Contractor MCSO contract.
User The The The The to
NF-I-13.4 NF-I-13.5 NF-I-13.6 NF-I-13.7

SERIAL 170002-RFP
APPENDIX 3, REPORTING REQUIREMENTS
REPORTS, QUERIES, AND MESSAGES
LEGACY SMS REPORTS
Serial 170002-RFP
Reference Documents: Exhibit 9A — JMS Web Reports-REV.docx
Exhibit 9B — JMS Printer Report Jobs-REV.xlsx
Exhibit 9C — Sheriff Morning Report-REV.pdf
Exhibit 9D — Statistical Reports-REV.docx
Reports requirements for the New JMS solution include both the development of essential "in-scope" standard
reports now produced from the Legacy JMS application, as well as the ability to produce ad hoc reports using
reporting tools or other means. "Standard" batch reports currently run on a daily, weekly, and/or monthly basis and
are used by internal MCSO and external stakeholders to perfoim business functions.
MCSO relies on the following groups of reports produced within the Legacy JMS application:
• Daily and Weekly Reports — These reports are traditional batch reports produced on a scheduled basis. Reports
are posted to an MCSO website and are available to users authorized to access the MCSO Intranet. See" Serial
170002-RFP Exhibit 9A - JMS Web Reports-REV.docx" for the full inventory.
• Nightly Batch Reports Directed to Printers — Some Legacy JMS reports are run nightly and output is sent
directly to specific MCSO printers. These reports serve as key tools used during MCSO business processes.
Analysis of these reports is required to determine if they will still be needed in the New JMS solution or if they
will be replaced by process workflows, onscreen displays, or other functionality of the New JMS solution. See
"Serial 170002-RFP Exhibit 9B — JMS Printer Report Jobs-REV.xlsx."
• Online Reports Generated Real-Time — There are two types of these online reports. 1) background batch
reports initiated via online screens, and 2) programmatic reports. Similar to the report group above, analysis of
these reports is required to see if these reports are still needed in the New JMS solution.
Ad hoc — As with any application system, users have a need to request and receive ad hoc reports. It is
expected that JMS users and/or MCSO in-house technology staff will be able to design and generate ad hoc
reports as needed in the New JMS solution via reporting tools or other means.
In addition to the traditional batch reports mentioned above, there are a number of statistical reports (Excel
spreadsheets) prepared today from manually captured data that is not available from a single system. See" Serial
170002-RFP Exhibit 9D — Statistical Reports-REV.pdf' for a full inventory. Data is derived from a number of
sources including Legacy .IMS reports, reports from other applications, and/or Excel templates completed by staff in
MCSO business units. MCSO command and management staff and external stakeholders rely on these statistical
reports to make policy and strategic decisions. There are two primary types of statistical reports:
• The Inmate Section Report (more commonly referred to as "the Morning Report") — This report is on the
Sheriffs desk every morning and presents key statistics monitored by the Sheriff and his Command team. See
"Serial 170002-RFP Exhibit 9C — Sheriff Morning Report-REV.docx" for an example.
• Excel Statistical Reports (also known as the "Schroeder Reports") — These reports typically include raw and
summarized data as well as charts and graphs in Excel format. Following are the intervals for which statistics
are regularly produced, along with a description of processes for gathering the data:
o Daily — JMS reports are run daily at midnight and then become available as web reports. Data from these
reports is reviewed and manually entered into the Excel spreadsheets. Excel files are stored on a
designated Sheriffs Office workgroup network drive.
o Monthly — Extensive statistics are gathered in a similar manner for monthly reporting. Recent counts show
the number of separate Excel spreadsheet files generated and stored is approaching 100. Additional

SERIAL 170002-RFP
monthly statistics are captured manually, using Excel Templates completed by staff in Business Operations,
Food Services, Court Security and Transportation, Sexually Violent Persons Unit, Custody Support, and
other Detention areas.
o Yearly — Fiscal year and calendar year statistics are compiled from monthly data and these annual reports are
placed on a universal network drive accessible by all MCSO employees.
The content of these reports must be analyzed by the vendor to determine the extent to which the New JMS solution
captures required statistical information. It is anticipated that many statistical reports will be automatically
generated in the New JMS solution, and that this data will also be used in dashboard displays for monitoring by
command and management personnel. For a summary listing of the current statistical reports, see Appendix D of
the "As-Is" State of the MCSO Detention Systems document (included in the MCSO Reference Library.
LEGACY JMS QUERIES
Serial 170002-RFP
Reference Document: Exhibit 9E — JMS Queries-REV.xlsx
The Legacy JMS Query Inventory identifies all internal and external queries that are considered as "in scope" for
replacement in the new JMS solution. Internal queries include those that initiated within JMS by MCSO staff, while
external queries are incoming requests for data retrieval from the JMS database made by non-MCSO entities.
There are 164 internal, on demand JMS queries, which can be further sub-defined as: those employing standard
input masks (129), those using no mask (20), those using group commands (14), and one free form (SEND).
In addition to the above referenced internal MCSO JMS inquiries, JMS services data requests made via the Arizona
Criminal Justice Information System (ACT'S) network. External entities, i.e., law enforcement or criminal justice
agencies authorized to utilize the ACJIS network, have access to the eight (8) standard ACJIS queries that are
received and fulfilled by JMS on demand.
Each query listed in the inventory is identified by a command code, a brief description of the query and a Y(yes)
N(no) identifier of whether a mask input template is used for query generation. Part one details all internal MCSO
initiated queries via JMS and part two details external queries received by JMS via the ACJIS network.
LEGACY JWIS MESSAGES
Serial 170002-RFP
Reference Documents: Exhibit 9F — Legacy JMS Messages.docx
Exhibit 9G — Legacy JMS Programmatic Messages.docx
MCSO's Legacy JMS utilizes an internal messaging component to communicate notifications, requests,
acknowledgements, announcements, and orders using JMS menu options and commands. Messages can be routed
both internally and externally, and are communicated via the system, email, and/or a utility module (dot matrix
printer). Other than several "smart" messages where content is validated, such as those related to holds, most are
considered "dumb," meaning that content is not validated except for fields such as date.
There are 58 total messages inventoried, two of which are freeform messages. The "SEND" free form message goes
to external recipients and the "SESM" message is internal to JMS users.
In addition to messages available through menu options and commands, there are many programmatic, auto-
generated messages/reports within the Legacy JMS related to inmate transfers, releases, visitor passes, holds, LEJIS
number maintenance issues (i.e., linking current and past bookings to the LEJIS man record), victim notifications,
and many other detention activities. These system messages must be addressed during implementation to determine
how each message will be handled in the New .TMS solution.
All messages are considered "in scope" for the New TMS solution. The purpose and content of each message must
be analyzed by the Vendor to determine whether the New TMS solution will incorporate similar messaging and

SERIAL 170002-RFP
alerts functionality within the new system. Alternatively, messages and automatic alerts may be part of workflow
processes in the new solution, or they may be handled using other means or logic.
IFCS REPORTS
There are two types of IFCS reports used by MCSO personnel: (1) Standard reports generated in the IFCS
application, and (2) Reports from other systems that are used by Financial Services staff. Some of these other
reports are Crystal Reports (using the IFCS database), while others are reports from the SAP application or the
TouchPay system. Finance staff also use reports developed internally with Excel.
Serial 170002-RFP
Reference Documents: Exhibit 9H — IFCS Reports-REV.docx
Exhibit 91— Finance Reports-REV.docx
OPERATIONS JOURNAL REPORTS
These reports are internal to the Operations Journal application.
Serial 170002-RFP
Reference Document: Exhibit 93— Operations Journal Reports-REV.docx
COURT OPERATIONS/TRANSPORTATION REPORTS
These reports are internal to the Court Operations/Transportation system.
Serial 170002-RFP
Reference Document: Exhibit 9K — Court Ops Reports-REV.docx

is is for
170002-RFP Comments Ti-aCS MCSO's field reporting system (developed 4n-1iense)7 TraCS booking data-is-also sent-to MCSO's Intergraph RMS-Enet TechCare EHR the vendor Correctional Health Services (CHS)
& to to to
SERIAL Systems Involved Agency to RMS Pre- Booking Pre- Booking Agency RMS Tree-S-4e Pre- Booking Pre- Booking & EHR to EHR Pre- Booking Pre- Booking EHR
& IN OUT X X
DIRECTION 0 C *-3 X
IN
PPD
Volume 10/day from Peoria, 100/day from 300/day 300/day
Frequency per booking; possibly multiple iterations booking per Bookings Geouf per booking per booking
1 As I 1
INVENTORY Logic data External RMS Booking data N4CSO Officer as response is I
Trigger Pre-Booking receives from Agency's Pre receives from TraGS When designates inmate "arrived" EHR EHO ACCEPT
to
IIE? Yes Yes Yes Yes
INTERFACE -
Queue / Specific Specific SCOPE
4, ID REMOVED FROM session 12/13/16 I
Trans Queue Queue Gap EHO EHO2
APPENDIX
Complex High 141gb Med Low
& PDs; PD
Primary Stakeholder Currently, Phoenix Peoria Future: Glendale MCSO &worn Officers - CHS TechCare - CHS TechCare
to Pre- in transaction or Uses (all data at is medical responds number
Booking/Arrest Used - booking Pre-Booking Success - Queue initial Booking-is sends inmate for After EHR or (medically) ACCEPTED Pre-Booking booking EHR
(XML) reply conditions Beeking/Arrest-Dita— Scuds bookinn-data-to-Bre- completed--in-P-re- when ready ACCEPTED a to
Description Initial Data establish Booking. a sends indicating Error Arrest agencies) TraCS Booking. Booking Pre-Booking EHR Intake screening; screening, DENIED an For inmate, assigns sends
PB to as &
/ Interface Exch. Pre-Booking External Booking TrnCS Pre-Booking Electronic Records Pre-Booking EHR
Data & Agency RMS's Pre & & Health (EHR) &
ID FF-001 liF4IO2 I/F-003 I/F-004

a case by in - with TP11 is of TP12 is of TP12 is of
170002-RFP is unique used County criminal partners exchanges Internal go integrated solution TP01 alike, difference type TP02 alike, difference type TP02 alike, difference type
CCN ID# all justice data may away Note: and are the the kiosk Note: and are the the kiosk Note: and are the the kiosk
to to &
SERIAL Booking & to Booking other agencies) Booking TouchPay IFCS to TouchPay Touchpay Pre- Booking Touchpay IFCS
Pre- CCN CCN Pre- (and Pre- IFCS to IFCS to to
X X
X
X X X
250/day 300/day 100- 200/day 100- 200/day 100- 200/day
per booking per booking per deposit per deposit per deposit
1 1 1 1 1
CCN booking in received kiosk by by
When is charge booked After issued is Pre-Booking PB10 Officer initiates deposit Deposit accepted TouchPay Deposit accepted TouchPay
#
Yes Yes Yes Yes Yes
Request
CCN PB10 TP11 TP12 TP12
Low Med Low Low Low Low
County
Criminal Justice Partners Inmate Funds Touchpay Touchpay Touchpay
All
a replies error and to trust inmate initial - Kiosk IFCS up set is yes/no at $$ and deposit at $$ initial inmate's account
requests with CCN or Pre-Booking sends number IFCS inmate IFCS an Intake queries account Pre- - receives initial Touchpay IFCS - posts trust
store - number ACK to info an in opens account making at responds deposits kiosk deposits kiosk and the to
Pre-Booking to CCN charges with message, sends Pre-Booking booking basic create account IFCS trust Officer deposit TouchPay verify IFCS Officer Intake Booking processes from info Officer Intake receives deposit individual
to -
Pre-Booking Common Number Pre-Booking IFCS & TouchPay Pre-Booking TouchPay & TouchPay
& Case (CCN) & IFCS Intake Kiosks & Intake Kiosks IFCS Intake Kiosks
I/F-005 UF-006 UF-007 I/F-008 UF-009

1'70002-RFP on (rather string) may This product interface? - go with integrated - go with integrated MugShot refers MugShots www.MCS for bookings
Unusual message format requires data separate lines than -- a be Internal may away solution Internal may away solution Internet App to on 0.org Sent NICS0 only
to to Pre- to
SERIAL Booking MugShot Booking to Booking to MCSOS- Batch Server Booking TraCS
Pre- IWS Pre- JMS JMS JMS 231 Pre
X X X X X
X -
300/day 300/day 300/day
per booking per booking per booking needed times/day F booking
1 1 1 As 4
is (inmate by Accepts (in data from an reports Noon, Final
the After booking number issued yet not accepted Intake) MCSO Detention Staff Inmate Pre-Booking) Booking received Pre-Booking 1MS in error processing booking Scheduled process: 1:00am, 6:00am, 6:00pm When Acceptance Completed
is the
Yes Yes Yes No Yes
plus -
- Data Charges Specific SCOPI:
Queue 50 REMOVED session
MugShot Outbound JMS PBST BKMUG Booking to Queue FROM Gap 12113/16
up
Low High Low Med Med H4gh
Pre- Pre-
IWS MugShot & JMS Booking & JMS Booking MCSO.Org WICK) Sworn Qffnsers
to data info validated Pre- back 2-digit or 50 to othef
sends and the ImageWare Includes eye/hair sends SMTs, charges, DR from sends Pre-Booking booking JMS to mugshots, up & batch to &
number about - DOB, booking Inmate holds, sentence processes data then message plus # successful the data, the upload Pre-Beeking-sends charges TraCS
Pre-Booking info to etc. Pre-Booking - demographics, info, for errors, transaction(s) sends to for www.mcso.org to
booking basic inmate MugShot name, color, validated JMS arrest aliases, numbers, JMS booking Booking, status (Booking code not) For re-sends JMS booking charges server updated data
a
Pre-Booking IWS (ImageWare MugShot System) Pre-Booking JMS Pre-Booking JMS & Internet MugShot Pre-Bee ,FE4racTS
& & & JMS App
I/F-010 1/F-011 I/F-012 I/F-013 •/-F-0-14

170002-RFP XML as IIE PPD; to and both complexity XML as Courts; converts to and both for for Peoria 40 charges/cou use then for may product
Same format for converts XML PDF sends PPD to Low because same format for TIE XML PDF sends PPD to Sent Phoenix bookings only Sent Phoenix bookings only IIE translates for > If nts, LiveScan manual process additional prints required This -- a be interface?
to to to to to to
SERIAL Pre- Booking iCIS-NG Pre- Booking Agency RMS Pre- Booking Agency RMS Pre- Booking Agency RMS Pre- Booking EHR LiveScan & JMS to JMS LiveScan
X X
X X X X
300/day 100/day 100/day 100/day 300/day 300/Day
arrest 2s)
per booking per booking per booking per booking per booking per (including Page
1 1 1 1 1 1
in of
Final Final Final Final takes after
Acceptance Completed Acceptance Completed Acceptance Completed Acceptance Completed Acceptance Pre-Booking MCSO acceptance inmate
When When When When Final prints
Yes Yes Yes Yes Yes Ves NO
Court Specific Specific Specific
Superior Queue Queue Queue Queue EHO3 LVSC
Med Low High Med Low High
PD PD only; PD AFIS
Superior Court Currently only; PPD Future: Glendale Currently only; PPD Future: Glendale Currently & PPD Peoria Future: Glendale - CHS TechCare MCSO Intake
&
XML to data Charges XML to data PDF Pre- the final EHR booking to
sends and IV sends and IV City sends for to arresting - XML to sends to responds up &
info Form County info Form Phoenix only Report the RMS Acceptance sends information RMS info sends JMS info charges/counts
Pre-Booking booking validated - Courts Pre-Booking booking validated - Charges Pre-Booking Arrest in storage agency's Booking originating Pre-Booking acceptance LiveScan - number basic
only PPD Final arrest with 40
Pre-Booking iCIS-NG Pre-Booking External Agency RMS's Pre-Booking External Agency RMS's Pre-Booking External Agency RMS's Pre-Booking EHR & Morpho LiveScan
& & & & & JMS
I/F-015 I/F-016 1/F-017 I/F-018 I/F-019 I/F-020

of of list for etc. for only, is scope can is will changed standard New for only, is scope are matched in is data into by staff
170002-RFP Several transactions - occur return PCN, possible matches technician review, NOTE: is This info interface in not Note: MCSO's LiveS process currently custom (grandfather and ed) a Morpho interface with JMS solution NOTE: is This info interface in not the numbers not an existing person record JMS, entered JMS manually MCSO AFIS
be to If to
to S&F to to to
SERIAL AzAFIS, (via (via
LiveScan S&F, to AzAFIS S&F AzAFIS S&F DPS) AzAFIS JMS DPS)
X
X X
350/Day
50-
of of (for
needed set set
As per I prints per I prints matches only)
a can or match determination, receives from (via receives from
as Sent batch, sent individually After Fingerprint Technician makes S&F data AzAFIS DPS) JMS data AzAFIS
be
No No Yes
network AHFC, AHFG, AHFS AHFC, AHFG, Al-IFS
Dedicated AzAFIS DPS) AHFA, AHFD, AHFN, (ACCH transactions) AHFA, AHFD, AHFN, (ACCH transactions)
(via
N/A N/A High
users Law AFIS
LiveScan, S&F, AzAFIS AzAFIS/ ACCH AZ, MCSO, Other Ea. Agencies MCSO
in
and then - is Livescan, (SID) (ARN), ID above, SID, numbers if exists exist,
S&F, to Loop or update: which Arizona TOC (Fingerprint AFIS as determine do is associated person
captures in file AFIS to Control (PCN) the Identifier Number (5) that the same Loop updated FBI already they booking #)
prints NIST Feedback from used Process at (3) and user the &/or to If existing (LEJIS
LiveScan stores sends AzAFIS AFIS ACCH Number assigned State number, Record FBI# the Technician) performed identification of Feedback newly ARN, used person JMS. new automatically the record
Feed (1) (2) (4) of Part the are the in the to
can, to &
LiveS & Store Forward, AzAFIS in (Not Scope) AzAFIS S&F in (Not Scope) AzAFIS JMS
NOT IN SCOPE (INFO ONLY) NOT IN SCOPE (INFO ONLY) I/F-021

170002-RFP are same transactions to EFIR Securus by " Integration Engine)Inter go may with is (developed County system - go with
These the sent as IFCS, & (forked ICJIS - nal away integrated solution PHReD MCSO's personnel tracking system in-house); the HR ADP is Internal may away integrated solution
SERIAL OJ to to to Ops /Transportat
JMS PHReD OJ JIVIS Court ion
X X
X X X
750-1,000 transaction day
s/
needed sent court 100- 2
As Daily Files nights before days, usually betw. 2200
or DO - etc. Daily files
initial # assignment, is when changesJMS transaction(s) new added hires, Ops/Transp. processing
After booking, housing LEJIS release scheduled &/or data received When info new Multiple Files Ct receives for
Yes No Yes
HOUS, LNBR, IAR127,
BOOK, RELE, File DER275, IAR135RP, IAR14ORP, IAR150RF, IAR15ORP, IAR16ORP, IAR17ORP, IAR200RP, IAR200RQ, IAX120S
PROJ Data
Med Low High Med
&
Ops
Detention Officers Detention Officers Court Transport.
names, #s, dates OJ JMS personnel to info is entry court transportation files
inmate to from number DO Officer) number OJ for (incl. notifications, Court daily
LEJIS release info processes sends serial an data appts), to Operations/Transportatio Operations/Transportatio
sends release OJ transactions by Auto-Fills (Detention serial into sends inmate appointments wheelchair keepaways, processes JMS
JMS locations, projected and PHReD info - OJ when entered JMS cards, multiple warnings Court from
n n
(OJ) system) /
& JMS Operations Journal & PHReD (Primary Human Resources Data & JMS Court Operations Transportati
OJ on
I/F-022 1/F-023 I/F-024

are this five after - go if functionality existing IVR is the change transactions to & 0J, converts to
170002-RFP Inmates dropped from feed calendar days release Internal may away integrated solution includes programs The Avaya System being upgraded and interface will well as Same sent as IFCS, EHR HE XML to format before sending Securus
IMS to ITL
SERIAL to Inmate Programs to JMS to (Global Tel*Link) to Securus to Securus
JMS IVR & IVR JMS JMS JMS
X
X X X X
X
4,000/Day
Est.
needed times/day needed at
Daily As 4 As Daily 4:15am
- plus with receives data or
processing inmates yrs adult inmate for programs Transactions received Scheduled process generates Booking, release, housing assignment completed/cha Processing
Daily All <18 any flag IVR call file nged Daily
Yes Yes Yes Yes Yes
I, IP04, File List HOUS, file file
(IPO IP03, Roster Location plus
INMPG IP02, IP05) DEX080.01' Various transactions Full with BOOK, RELE, "securus.txt" securus.txt
Med Med High Med Low Low
Aide, Friends/Fami Inmates ITS
Inmate Programs Legal of - GTL Visitation Visitation
ly
Inmate basic info, for info inmates are attorney file with
to including actions, keepaways, etc. realtime inmate JMS identifying calls unit calls (e.g., BOOK, Securus nightly inmates restriction allowed)
data Programs data bonds/charges/location, - location Allows out-going some RELE to System for
sends location, disciplinary restrictions, appointments, sends for JMS sends and - housing audited sends transactions sends flag disciplinary visitation
JMS Programs info, Inmate processes IVR inquiry incl. to etc. responds JMS data inmates make from phones, not calls) JMS HOUS, Visitation JMS with a (no
IVR GTL (Inmate
& Inmate Programs & Avaya (Interactive Voice Response System) & Telephone System) & Securus Visitation System & Securus Visitation System
JMS JMS JMS ITS JMS IMS
1/F-025 I/F-026 I/F-027 I/F-028 1/F-029

is SEI until are is by in the also analysis This a is data have as may product - with
170002-RFP Securus currently using data-ancl not kiesie$443f oommissurv orders available CopLink data repository queried enforcement officers field; product provides other investigative tools-- be product interface? Considered "Low" complexity because the selection criteria different; two identical structures daily This a interface? Internal go away integrated solution
net may need a law the link and may only the files the files -- be may
SERIAL to JMS to to to
IFCS Seetwas to IIE JMS to IIE CopLink JMS CopLink JMS IFCS
&
X
X X
X
<500/Day Usually 7,000- 10,000 bookings/ 300/day
mo
at - at
Daily 3:15am Daily Runs 10:00am Monthly per booking
1
Monthly final
ai.ly Processing Daily Processing JMS Purge! Archiving Process Booking acceptance
Ye Yes Yes Yes
as to
SCOPE Outgoing into & data CPLNKBD Same
IOVEI) session - is - two CPLNKOD - transaction
EN FROM 12/13/16 Incoming ESADs; Data aggregated files CPLNKBD CPLNKOD Same - BOOK
SE-1- R Gap - two files and for EHR
Low High Low Med Med
and law and law
Visitation; Canteen:. Detention MCSO outside enforcement agencies MCSO outside enforcement agencies Detention, SIMS
king from by for # daily two - FTP as for meet not (i.e., booking the is ago)
# sent prior an booking accumulates "booking" from record via transforms CopLink done JMS that AND date years IFCS BOOK
balaneec booking IV the JMS transaction processes data sends IIE extracts the criteria recent release two inmate to
number-&-infnate4fust sends (contains JMS full JMS then to to server except in database person info processes
gets Form Pre-Booking & - "other" files process sends data bookings archiving most the than sends transaction
fteeount TIE each day ESAD each only) ESADs, (extracts and various types), data TIE and staging Same above active the for booking more JMS booking IFCS
IFCS
IPGS-ee Seaus & CopLink & CopLink &
JMS JMS IMS
l/F-0-30 1/F-031 I/F-032 I/F-033

170002-RFP - go with - go with - go with - go with - go with - go with - go with - go with
Internal may away integrated solution Internal may away integrated solution Internal may away integrated solution Internal may away integrated solution Internal may away integrated solution Internal may away integrated solution Internal may away integrated solution Internal may away integrated solution
SERIAL to to to & to & to & to & to to &
JMS IFCS JMS IFCS JMS IFCS WIMP JMS IFCS WIMP JMS IFCS WIMP JMS IFCS WIMP JMS WIMP JMS IFCS WIMP
X X X X X X X X
X X X X X X X X
needed
As
in # in or
data LEES when changes data data data data status, date
When changes Housing transaction JMS When received or JMS data When changes When changes When changes When changes When projected release restrictions change
is
Yes Yes Yes Yes Yes Yes Yes Yes
(in
WORK, IF04
CLAS HOUS LNBR OHOC SCHD STAT CLFG PROJ, REST; IFCS)
Low Low Low Low Low Low Low Low Low Low Low Low Low Low High High
- & - - - - - & -
SIMS Workbox Inmate Funds Inmate Funds SIMS Workbox SIMS Workbox SIMS Workbox SIMS Workbox SIMS Workbox Canteen SIMS Workbox
to CLAS housing HOUS inmates to LNBR open to OHOC special update SCHD work release STAT work IFCS CLFG date, restrictions, and to IF04
inmate info housing & IFCS to an info inmate flags inmate program inmate inmate to info inmate release restrictions, info
sends processes sends info processes sends number processes sends processes sends processes sends furlough/work IFCS processes sends processes sends status status processes
classification transaction assignment change transaction LEJIS transaction holds/charges transaction sentence IFCS transaction to transaction assignment transaction projected dietary inmate transactions
JMS IFCS IFCS JMS IFCS JMS IFCS IFCS JMS IFCS IFCS JMS to IFCS JMS info IFCS JMS IFCS JMS work IFCS IFCS
IFCS IFCS IFCS, IFCS, IFCS, IFCS, IFCS,
& & WIMP WIMP WIMP WIMP & WIMP
JMS JMS JMS, & JMS, & JMS, & JMS, & JMS WIMP JMS, &
I/F-034 I/F-035 I/F-036 I/F-037 I/F-038 I/F-039 I/F-040 I/F-041

- with is if has or found is if is in found TP02 are the is source TP02 are the is source
170002-RFP Internal go may away integrated solution TouchPay session ended inmate been released not JMS TouchPay session ended inmate account not IFCS Note: TP12 alike, difference the funds Note: TP12 alike, difference the funds
is in & of & of
SERIAL to Touchpay & JMS to TouchPay Touchpay IFCS, to Touchpay Touchpay IFCS Touchpay IFCS, to Touchpay
JMS IFCS to JMS to IFCS to to IFCS
X X X
X
X X
400- 500/Day 400- 500/Day 400- 500/Day 1/day
- Daily After midnight per deposit request per deposit request per deposit request more or day per
1 1 1 1
BIT010 billing is initiates initiates has the
When (daily compute) process completed User deposit process User deposit process After TouchPay accepted deposit Touchpay verification process
Yes Yes Yes Yes Yes
DUNB BKTP TPOI TP02 TP03
LowMed Med Med Med Med
IFCS
& Touchpay Touchpay Touchpay Touchpay
JMS
to is status for realtime verify - custody realtime verify - accepted, deposit and to trust - list IFCS - range
message billing process IFCS to diem status canteen) to in yes/no to is deposits yes/no is IFCS amount IFCS inquiry with TP12 in reconciles deposit
daily process per & sends JMS still sends IFCS account for responds deposit sends - IFCS individual sends range responds and recorded date/time making
sends that computation complete indigent to is responds to deposit TP02
.1MS IFCS begins determine and (medical inmates TouchPay inquiry inmate JMS TouchPay inquiry inmate available IFCS When TouchPay to info posts inmate's account TouchPay deposits IFCS all deposits the for TouchPay before
of
IFCS IVR, IVR, IVR,
& TouchPay Lobby Kiosks, Website TouchPay Lobby Kiosks, Website TouchPay Lobby Kiosks, Website TouchPay
JMS or or or
I/F-042 I/F-043 I/F-044 I/F-045 I/F-046

170002-RFP this to the to reconciliatio occurs TP02 TP03 processing, bank is - go with integrated - go with integrated "Standard" (not customized MCSO)
Sheriff Finance uses info reconcile deposits Due that during & the deposit (TP04) already verified. Internal may away solution Internal may away solution File for
n •
Bank
SERIAL Touchpay IFCS, to Touchpay Touchpay IFCS, to Touchpay to to SAP
to IFCS to IFCS IFCS SAP SAP IFCS Chase to
X
X X X X
1/day Rarely ever) <25/Day
(if
day needed needed Only)
per 1 As Daily As Daily (Business Days
bank to deposit processed file Chase
Touchpay deposit process Touchpay undo Daily processing After transactions are SAP MCSO receives from
in
Yes Yes Yes Yes Yes
AC04,
I Reconciliation
TP04 TP05 ACO AC03, AC05 File
Med Med High High Med
Touchpay Touchpay MCSO Finance MCSO Finance Sheriff Finance
IFCS cash to two checks to with with
IFCS deposit of - IFCS bank reverses deposit and data reconcile account the data details account checking
sends info, total range included individual sends voided IFCS inmate ledger location to between check voided reversal Reconciliation to Used SAP transactions
deposit and each - each sends Used fund sends Stores disbursement trust -
TouchPay bank including amount deposits flags deposit TouchPay on info deposit on flag IFCS account, storage - SAP inmate activity systems SAP numbers, AP and - IFCS inmate transactions Bank Report reconcile account bank
Bank
TouchPay TouchPay SAP Business One Accounting System SAP Business One Accounting System Chase
I/F-047 I/F-048 I/F-049 I/F-050 1/F4151

B/F voids sends for is image if a a & a for a for day. in day's OET to image - with - with
170002-RFP TIE The collects receipts AND then OET daily processing. No created there's receipt void specific transaction. also TIE sends summary report each void a was processed prior batch, a has process manually delete from OnBase Internal go may away integrated solution Internal go may away integrated solution
to If a
SERIAL TIE to County Finance (OnBase System) TIE to County Finance (OnBase System) to to & to to Touch-Pay
JMS to JMS to JMS IFCS JMS IFCS IFCS JMS IFCS
X
X X X X
50/day <5/day 250/day
created voided per
As As time 1 booking Daily per 1 release request
created voided in release
Files
Bond/Fine receipt Bond/Fine receipt Release completed JMS Daily Inmate process initiated
Yes Yes Yes Yes Yes
- and
0060T
IFITR/2005 DES006UT
BFRC BONZ RELE DES TP20
Low Low Low Med Med
& of & of
County Finance Clerk Court County Finance Clerk Court Inmate Funds Inmate Funds Inmate Release
goes data to info to to to debit funds
bond/fine County create that OnBase electronic bond/fine notice prepare account transfer to Used for transaction up
to OET to receipt County release Release to - funds transferring set to inmate released
sends data - of the sends voided sends - IFCS to inmate ASP/ADOC information disbursements sends when be
JMS receipts Finance transforms image into system JMS for receipts JMS IFCS sent close process inmates DOC IFCS TouchPay card to are
IFCS IFCS
HE, JMS, County Finance (OnBase Imaging System) IIE, JMS, County Finance (OnBase Imaging System) & JMS & JMS Touchpay Release & Cards IFCS
I/F-052 I/F-053 IT-054 1/11-055 I/F-056

is FTP then converts not do & then individual trust to reports to & by being IIE)
170002-RFP Report to sent server, pulls HE and processing IFCS daily totals balance (Numi IFCS), Finance staff reviews transactions inmate accounts reconcile &/or issue vendor MCAO confirmed CUST HOLD transactions no are longer required PbK (however, still to sent
for by If in
HE IIE PbK PbK
SERIAL TouchPay IFCS to IFCS to to to
to Numi to IFCS JMS JMS
X X X
X X
250/day 300/Day 1/Day 1,800/wk approx. 18,000 individual transaction 1,150/wk
s
- at only) - at only) all of transactions booking
per 1 release request Daily Runs 9:00am (banking days Daily Runs 9:00am (banking days set 1 per per 1 release
debit and to release in
recived Numi reconciliation a is sent is Pre- an completed
Numi Financial approves card processing File from IFCS completes Numi process When booking completed data from Booking JMS When inmate JMS
is
Yes Yes Yes Yes Yes
CHRG, AKAS, IDNO, CHRI, DRNO, AHAU, HOLD
Reconciliation
TP21 File TIE BOOK, ARST, SMTS, LINK, CHRB, BOND, CUST, RLSE
Low Med Med High Low
Atty Atty
Inmate Release Sheriff Finance Sheriff Finance County County
with (Numi number - IFCS of are specific in to (via includes and data, in release previously the
sends card being to digits amounts records email mailbox Numi processed - the booking demographics, by establish charge case a when for
verifies vendor then file four against that not details for Used as final sent was
card debit inmate sends last $ and release initiates Inmate stating or amount sends - etc to and sends only data MCAO
TouchPay debit Financial) a IFCS the released Numi Name, card, matched funds IFCS IFCS MCSO Accounting IIE) reconciliation correctly transaction total reconciliation JMS including alias, MCAO booking information PbK JMS - data arrest to sent booking
for
JIB PbK PbK
Touchpay & to & & (Maricopa Attorney's - Prosecutor Karpel &
Release Cards IFCS EHR Numi FCS IFCS JMS MCAO County Office by system) JMS MCAO
I
I/F-057 I/F-058 I/F-059 I/F-060 I/F-061

170002-RFP previously implemente is currently off to limitations Legacy The .IMS track court for previously implemente is currently off issues to the The JMS update pre-filing with by of "Filezilla" processing (wh-o-beeds transported to-co-art-the day, whetbli-v-Iter
Was but d turned due in JMS. New must multiple future events each inmate's court case(s). Was but d, turned due with data. New must (arrest) charges charges actually filed MCAO Part to-be nest e--)
to FTP
SERIAL to iCIS-NG iCIS-NG, & MCSO Server
iCIS JMS JMS 1IE,
X X X
150/Day Daily
court court filing
per event scheduled per case Daily
1 1
court are in are in
When events completed iCIS-NG Charges updated iCIS-NG Daily processing
Yes Yes Yes
Candidate
1E04 1E05 (from
- -
SCEV FACS Release Report iCIS-NG)
High High Low
&
Superior Court Superior Court Superior Court SIMS
and - and in File- in
new events court (existing Court Feed) case - JMS charges ICJIS Feed) release 1IE to to to
sends for info court update JMS Scheduled (SCEV) sends to update (FACS) report converts forwards FTP
to in data to (existing sends IIE and via
iCIS-NG updated scheduled Used events ICJIS Events iCIS-NG charge Used JMS a-Case Courts candidate XML, PDF SIMS
iCIS- iCIS- FTP
& (Court System) & iCIS-NG, & MCSO Server
JMS NG JMS NG 11E,
I/F-062 I/F-063 I/F-064

a is in JMS on ID. ID, inmate's is a to = forwards via also to for (Az of Courts) same to & OJ, by
170002-RFP LEJIS number unique "person" number Legacy based fingerprints establish positive After positive current booking linked or new existing LEJIS record. APETS Adult Probation Enterprise Tracking System (statewide system) iCIS FTP; converts XML AOC Administrati Office Transactions the sent IFCS, Securus ("forked" ICJIS Integration Engine)
A to the IIE to ye the are as the
IIE and AOC
SERIAL to to APETS to iCIS to to IRIS/Justwa to
JMS iCIS JMS JMS to IIE JMS re JMS EHR
X X X X X
300/Day 600/Day 600/Day 1,800/wk
or change booking association # LEJIS all of transactions booking release
per 1 release any to 4 to Daily Daily Daily set I per or
being &/or a the of a number
an is there to to initial is when changes
When inmate released when change association booking number LEJIS (see description) Daily processing Daily processing Daily processing After booking, housing assignment, release scheduled &/or data
a
Yes Yes Yes Yes Yes
to per
Goes 11/2/16 HOUS,
- CMSINPUT - bkYYYYMMDD bkYYYYMMDD DER095.0T
GUST M19 Terry BOOK, RELE
J
Med Med Low Low High
AOC of
Superior Court Adult Probation Courts, Office Public Defender Svcs EHR
when: (2) (3) OR #, are and to data
updated info release, released custody, is or LEJIS records booking statewide system with releases Roster" booking, release EHR
status is for is record delinked, a to LEJIS to Probation file and PDF and
sends inmate inmate MCSO booking inked two sends data sends daily sends "Defendant sends TechCare
JMS Custody an (I) scheduled an from a linked, rel (4) combined JMS release Adult JMS bookings IIE JMS report JMS housing, to
iCIS- IIE
& & APETS & (ICJIS Integration Engine) IRIS/Justwar
JMS NO JMS JMS e EHR
1/F-065 1/F-066 1/F-067 1/F-068 1/F-069

data the forwards - as over drive being (per
170002-RFP TechGa.r-e EHR feRvacds VALO Mere-y Marieopa (formerly called "state feed) the County Manager's Office Justice Systems Planning email Justice Systems Planning person comes a with thumb Now revised Terry) County
to IIE to an - to an
SERIAL to to IIE to FTP), to to FTP IIE to to
JMS EHR EHR JMS JMS (via then EHR JMS CHS Server JMS JMS Thumb Drive
X X X X
X
/
1,800/wk PDF Reports
22 Day
or health (on
Eaeh beoking release per review Daily Daily Weekly Wednesday) Monthly
1
is final
slip health
or is a is
Booking printed release completed When review completed Daily Processing Daily processing Weekly processing Monthly processing processing
es Yes Yes Yes Yes No Yes
- DN, RE, -
SCOPE CH, OF, Reports & SCOPE
Transactions REMOVED SCSSi011 EHOO D044 I BK, MC. WM & Transactions PDF DEX130.TXT (Programs) DEX261.0T REMOVED session
VALO FROM Gap 12/13/16 EH D040 DUD AL, IA, SR, (22) DEX110 DEX111 FROM Gap 12/13/16
Med Med High Med Low Low Eew
ICJIS Mgr Mgr Atty
CHS JMS CHS, CHS County Justice Systems Planning County Justice Systems Planning County
- -
& JMS files IIE for
/release7-aiiases; General Medical Work, to info data to the on list, "Recidivism IIE monthly Extract" "Monthly
anel-cher-ge-data-to-E-HR for raw FTP various are reports 9A) to up Rofiking—Stats-'1411e-te4IE
sends Info, Diets sends via sends (all web Exhibit sends file prepares pick Summaryof-Feleny
:1MS-se11ds booking EHR Medical Clearance Special CHS reports Extract" weekly "Recidivism to 4MS-seeds
JMS for JMS JMS RFP JMS JMS JSP
EHR & CHS Server TIE
& 11E, & &
JMS JMS, EHR JMS FTP JMS JMS
1/E-070 1/F-071 I/F-072 1/F-073 I/F-074 1/F-075 IFF-076

Terry - uses (per - I/F-064 new a is system may to as of
170002-RFP MO9 transaction to goes CAACH 11/2/16 of "Filezilla" processng Courts create Release Candidate Report G) Tom above is DOC currently implementin their "AIMS2" application OBTS State Note: MCSO change sending transactions real-time instead batch
,.I per Part to See g a
SERIAL FTPs then iCIS-NG FTPs then iCIS-NG to to (via to for
JMS IIE, to to JMS TIE, to to AIMS JMS JMS OBTS DPS ACJIS) JMS SSA Website FTP Upload
X X X X
X
2,500/mo 17,000 records/mo file
nthly
@ @ batch all out at upload
Daily 2:00am Daily 5:00pm Monthly Daily sends messages 6:00pm Monthly FTP Data
of
from sent for month
Batch Process (ICISFTRN) Batch Process (ICISTTRN) Received Messages queue add/change/del to 0, RIU020, RIU025, RIU070, BKU035 of processing
Daily Daily DOC to etes RIU01 End
Yes Yes No Yes No
Data input Creates iCIS-
- Courts CMS, Queue" - for (0101, 0108, 0I1D, DEX0550T.TXT
DEX200 for file "Strip MSF DEX525 file data NG File Data OBTS 0104, 0I1C, OHS)
Med Med Low High Med
Users
(statewide) SSA
ICJIS, Courts ICJIS, Courts DOC OBTS US
sends sends in-custody plus and release FTP of for list a at etc. inmates persons time - identify to
JMS FBI, booking inmates JMS - names, numbers, release, dates/times, and via IIE listing Felons Exception visits names, identifying DOBs, in-custody, all of any month to entitled
- SID, for "global to receives in-person ID'd at prior SSA not
ICISF/2005 with & numbers released ICIST/2007 with identifying booking, court code, indicator Convicted Visitation facility) sends aliases, numbers, for positively report custody by persons benefits
file LEJIS, Courts list" next court JMS (for jail JMS daily only JMS in during Used
& &
11E, iCIS-NG 11E, iCIS-NG (AZ of Corrections) System (Offender Tracking System) Social Security Administrati
JMS, JMS, DOC Dept. AIMS OBTS Based US on
I/F-077 I/F-078 I/F-079 I/F-080 I/F-081

includes one the in CD each the in the Office & take JMS (or may product
170002-RFP Quarterly files, each month quarter; Annual includes files, for month by Student Rights Responsibili to appropriate action Legacy database not mugshot images pointers) This a interface?
CD (3) for (12) one year Used ASU of ties does store -- be
CDs
SERIAL to - delivered quarterly annually to AHCCCS to
JMS DES hand- and AMS JMS ASU
X X
X
17,000 records/ monthly 300/Day
file
CD
on needed
Monthly Files Daily As
IIE &
month File sends daily is
of End processing Daily JMS real-time, accumulates sends report 3MS) Inmate mugshot taken
No Yea Yes Legacy Yes
- with
Prateh-File SCOPE exist
DEX055ULTXT session Interface
RENIOVEI) FROM 12/13/16 currently
Dai-ly., Gap ASU1 New
not
do
Low Med Low )terfaces Med
i
(These JMS
DES AHCCCS Arizona University
AZ State TION: New
of any - month - benefits 21 that Conduct SOLI- to
reports at annually to not unemployment last for on ASU 3MS Send -
custody prior delivered DES persons stamps seedseok-ing-& (for heura)—U4ed-te-iffentify pefsens4o-remove-frem into data booked codes of of Image
monthly in during & AZ to food info back sends ARS violations Code NEW JMS
JMS persons time hand CD quarterly by Used identify entitled &/or release add JMS persons certain are Student FOR Mugshot New
or
of INTERFACES to
Dept Economic Security AHCCCS (Arizona Health-Care Containment System) (Arizona University) ImageWare MugShot JMS
AZ Cost ASU State New
REQUIRED
1/F-082 1•1:-083 I/F-084 I/F-085

All ACJIS will JWI some may require of ACJIS JMS also when system
170002-RFP Note: other queries processed directly through Also, triggering events only subset queries listed New may require outgoing "DOWN" transaction notify ACJIS the down
be a the to is
SERIAL to (via to (via to (via JMS ACES JWI) to to PbK IRIS/Justwa JMS
JMS ACJIS JWI), ACJIS JMS JWI) ACJIS JMS JWI), to (via iCIS-NG JMS iCIS-NG JMS, JMS, to &/or to re
X X
X X
- -
Out 1,200/Day, Replies 7,200+/Da
Est. Est. 3'
of per received received received
set I queries triggering event As As As
In- at of LJxx from a for is a to the for is
Bookings, Releases, Person Visitors Facility, Addition SID/FBI/Alias JMS receives query ACJIS Specific charges are adjudicated attorney assigned or assigned attorney case changed
info New case An case, the
Yes Yes Yes Yes
Queries: DCQI, KQ, DQ, AHSR, Queries: LJBH, LJDA, LJNB, LJSM New New
ACJIS ACQW, OBQI, AHQH, APOQ ACJIS LEJS, LJBK, LJDV, LJNU, - DAS Interface - ASA Interface
High High High Med
at Users Cnty of
Users Sup. Ofc Def.
JMS Intake, Release, Visitation ACJIS Superior Court MCSO, Atty, & Ct, Pub. Svcs
to routed via (sent is through is but to is through is but
events kick-offset (via returned be (initiating) ACJIS (received responds data data to data to
queries individual must and This Feed), sent assigned This Feed), sent
triggering will are correct JWI) initiate JMS requested - available (DAS JMS - available (ASA JMS
JMS automatically ACES As - responses each (via query - JWI) Disposition Sentencing currently Attorneys cases currently
For New of JWI) JMS, the to user Users LJxx JWI) with via already ICJIS not Legacy court already ICJIS not Legacy
Web Web &/or
Justice Interface (JWI) Justice Interface (JWI) iCIS-NG iCIS-NG, PbK, IRIS- Justwsre System
I/F-086 1/F-087 I/F-088 I/F-089

have to
170002-RFP Generally, court appointment have scheduling priority, however, certain medical appointment may highest priority (e.g., dialysis) Alternativel two- a query/respo exchange to (JMS iCIS-NG JMS)?
s s y, way nse
SERIAL to JMS EHR to to and to to and to to
EHR JMS, to EHR JMS EHR JMS, JMS EHR EHR JMS, JMS EHR iCIS-NG JMS
X X X
X X
needed needed needed needed
As As As As
CHS schedules an inmate order Report?
When staff changes inmate's medical appointment When medical transportation needed When physican meets selection criteria TBD Daily
or is
Yes Yes Yes Yes Yes
Interface Interface Interface Interface Interface
New New New New New
High Low Med High Med
MCSO MCSO MCSO EHR of
CHS, CHS, CHS, CHS Clerk Court, MCSO Release
Future from medical CHS about orders to to aliases, data, activity (flight activity scores, of Clerk for
for info if requests from info (subject exchange EHR charge as Payment - required
medical respond exists inmate physician constraints) data TechCare sending: dates, criminal score criminal risk) data Support Info release
(Desired appointments & transportation electronically Send/Receive electronically FTA and (recidivism other requested Processing data
ES: Receive EHR conflict Receive certain HIPAA Enhance with include release violent flag, risk) and Child Court inmate
INTERFA(
EHR EHR EHR EHR iCIS-NG (Courts)
OPTIONAL
Use) -1/F- N 01 N-I/F- 02 N-I/F- 03 N-I/F- 04 -1/F- N 05

to
170002-RFP Two-way transactions similar TouchPay Lobby Kiosk interfaces
to
SERIAL JMS iCIS-NG to to JMS AIMS2
iCIS-NG JMS, to AIM2 JMS AIM2 JMS, to
X X X
X X
X
or needed needed
Daily Weekly? As As Daily
As payments File PREA force is data into
& processed; of JMS
Daily monthly reports; bond are other Electronic TBD When use or incident entered New Daily processing
'
Yes Yes Yes TBD Yes Yes
Interface Interface Interface Interface Interface Interface
New New New New New New
High Low High High High High
plus &
of Clerk Court MCSO, DOC DOC Prof Standards Bureau, Early Intervention Inmate Programs Inmates, Detention Canteen Staff
to booking info, monthly to report (e.g., (4) of (1) data, of transfer on send case etc.), gets (5) about 6004 Other use and to data Standards (Blue Pro). to data rosters, grades Will etc.
exchange Court & bond/fine released have requested DOC to sentence exchange include alerts notification for to Send identifiers PCN, only now), notes e.g., (6) El inmate for with - grievances, trust and queries,
data of Add payment daily all remitted Send still sanctions owed), as about their data to ready (3) and additional etc., requested PREA incidents Prof software Pro, School and Self-Service Pods) orders, balance
Clerk (1) bond for (3) inmates jail data from DOC Send/Receive response SID, (DOC one Send/Receive confinements, lifers, sends IA sends interfaces (in for date
Enhance with include: to Send reports payments MCSO, when from monetary restitution Other Notice inmates complete Enhance with Send inmates with date, "x" numbers #, (FBI Send photos first guy, as data JMS force MCSO's Bureau Team, JMS Power attendance, tracking JMS Inmate Kiosks used canteen account release
# (2) (2) (4) the of be
- New Team Self-
iCIS-NG AIMS2 DOC's System AIMS2 Blue Power School Inmate Service Kiosks
N-I/F- 06 N-I/F- 07 N-I/F- 08 N-I/F- 09 N-I/F- 10 N-I/F- 11